Table Of Contents
Functional Organization
SVC Command Suite
SPVC Command Suite
PNNI Command Suite
PNNI Addressing
Shelf Operation Commands
Functional Organization
This chapter provides a functional organization for the following groups:
•
SVC Command Suite
•
SPVC Command Suite
•
PNNI Command Suite
•
Shelf Operation Commands
Each table lists the command, complete name of the command, and the page number.
SVC Command Suite
This section lists the commands that apply to the switched virtual circuits (SVCs). The SVC commands allow you to add, delete, configure, display status, and specify statistics.
The SVC commands consist of the suite shown in Table 2-1.
SPVC Command Suite
This section lists the commands that apply to the semi-permanent virtual circuits (SPVCs). The SPVC commands allow you to add, delete, configure, display status, and specify statistics. The following are the functions used for SPVC:
•
Adding a connection.
•
Modifying an existing connection.
•
Deleting a connection.
•
Displaying one connection or all connections.
•
Downing and upping a connection in the course of maintenance or troubleshooting.
SPVC commands consist of the suite shown in Table 2-2.
PNNI Command Suite
This section lists the private network-to-network interface (PNNI) commands specific to node addressing and routing. The PNNI commands allow you to add, delete, configure, display status, and create statistics for PNNI nodes.
The following are the functions used for PNNI:
•
Configuring:
–
Link selection
–
Node addresses and identifiers
–
Packet size
–
PNNI interface
–
PNNI timers
–
RCC variables
–
Routing policies
–
Scope map table
–
PNNI summary address
•
Deleting:
–
A logical node
–
A PNNI summary address
•
Displaying:
–
Debug information
–
Learned nodes
–
Link information
–
Neighbor addresses
–
Node addresses and identifiers
–
Packet information
–
Paths
–
Reachable addresses
–
Routing policy
–
System address tables
–
Timers
PNNI Addressing
The PNNI addresses and identifiers contain fields that are common to each other and should match each other. If you change a field in one item, Cisco Systems advises you to change the corresponding field in the other item. For example, if you change the ATM address, you should change corresponding fields in the PNNI summary address and node identifier.
Note
The peer group identifier does not share in this recommendation.
The name and graphic represent each address and identifier as well as the common information that appears in Figure 2-1. The central and lower parts show the breadth of each item. Applicable command descriptions point out where you should modify common fields. The following fields also go into the construction of the ATM addresses and PNNI-related identifiers:
•
The Initial Domain Identifier (IDI) identifies the domain.
•
The Initial Domain Part (IDP) identifies the country.
•
The Authority and Format Identifier (AFI) identifies the address format and who provided it.
•
The Data Country Code (DCC) identifies the country.
Figure 2-1 Cisco Factory-shipped Node-Addressing Defaults Mapping into Both NSAP and DCC Address Formats
PNNI commands consist of the suite shown in Table 2-3.
Shelf Operation Commands
This section lists the shelf operation commands along with some commands that belong to other logical entities running on the switch, for example, PNNI. The shelf operation commands allow you to add, delete, configure, display status, and create statistics for node-level features.
The following are the functions used for shelf operation:
•
Node-level parameters used for node name, date, time, time zone, and so forth.
•
Firmware downloading.
•
Network synchronization.
•
SNMP configuration.
•
User account creation (and associated password).
•
IP connectivity to support user-control of the switch.
•
Saving and restoring node configuration information.
Shelf operation commands consist of the suite shown in Table 2-4.