-
Cisco MGX 8850 Routing Switch Command Reference
-
About this Manual--Command Ref. for MGX8850, rel.2
-
CLI Overview--Command Ref. for MGX8850, rel.2
-
Shelf Commands--Command Ref. for MGX8850, rel.2
-
Provisioning Commands--Command Ref. for MGX8850, rel.2
-
ILMI Commands--Command Ref. for MGX8850, rel.2
-
PNNI Commands--Command Ref. for MGX8850, rel.2
-
Logical Node, Port, and Signaling Commands--Command Ref. for MGX8850, rel.2
-
SPVC Commands--Command Ref. for MGX8850, rel.2
-
Network Optimization--Command Ref. for MGX8850, rel.2
-
Trouble-Shooting Commands--Command Ref. for MGX8850, rel.2
-
Feedback
Table Of Contents
Position-Dependent and Keyword-Driven Parameters
Identifying Physical and Logical Elements
PNNI Commands
This chapter describes the private network to network (or node to network) interface (PNNI) commands. These commands apply to node addressing and routing on the Cisco MGX 8850 switch, Release 2.0. (For PNNI port and signaling commands, see the chapter, "Logical Node, Port, and Signaling Commands.") The commands in this chapter have the following applications:
•
Configuration
–
–
–
–
–
–
–
–
–
•
–
–
•
–
–
–
–
–
–
–
–
–
–
–
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 that the peer group identifier does not share in this recommendation.
The name and graphic representation of each address and identifier as well as the common information appears in Figure 5-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:
•
•
•
•
Figure 5-1 Cisco Factory-shipped Node-Addressing Defaults Mapping into Both NSAP and DCC Address Formats
Position-Dependent and Keyword-Driven Parameters
A command can include parameters that are keyword-driven or position-dependent.
For position-dependent parameters, you must type parameters in the order they appear in the syntax description or on-line help. To create a logical port, for example, the position-dependent syntax is:
addport <ifNum> <bay.line> <guaranteedRate> <maxrate> <sctID> <ifType> [vpi]
For a keyword-driven parameter, a keyword must precede the value. The keyword is preceded by a dash and followed by the parameter (-timeout <secs>, for example). The order you enter keyword-driven parameters does not matter—although any preceding or succeeding, position-dependent parameters must appear as they do in the command syntax description.
In the following syntax example, the command is to delete more than one connection at a time. The mandatory, position-dependent connection identifier consist of a logical port (ifNum) and the VPI and VCI of the first connection to delete. After the connection identifier, the line shows two optional, keyword-driven parameters. These keyword-driven parameters let you enter the number of connections to delete and specify verbose mode:
delcons <ifNum> <vpi> <vci> [-num <num.conns to del>] [-verbose < 1 | 0 >]
Command Entry
When you enter a command with the current version of the product, you must type all intended arguments before you press the Return key or Enter key.
If you press the Return key or Enter key with incorrect parameters or no parameters (if the command requires parameters), a message displays the syntax and parameter ranges. The returned message may also suggest what the problem is. For example, the message may warn of too few parameters. No error messages or warnings appear until you complete the command.
Identifying the AXSM Models
The model number of an AXSM identifies the line speed, line count, and number of bays (see Table 5-1.) Note that the number of lines applies to an individual back card, so the total number of lines supported by the front card equals the highest line number times the number of bays. The OC-48 card AXSM-1-2488 has the lowest number of lines—one. The highest number of lines exist on the AXSM-16-155 and AXSM-16-T3E3—16, as the name indicates.
The MGX 8850 node use the concept of a bay. The bay refers to the upper or lower location of a single-height card. (The switch has a double-height card cage, so a single-height back card necessarily occupies either an upper or lower position.)
The T3/E3, OC-3, and OC-12 versions of the AXSM can have two back cards, one in bay 1 (upper location of the back slot) and the second in bay 2 (lower slot). The MGX-AXSM-1-2488 (OC-48 AXSM) can have a back card in bay 1 only. For further descriptions and illustrations of the card sets, refer to the Cisco MGX 8850 Routing Switch Hardware Installation Guide, Rel 2.0.
Table 5-1 Valid Line Numbers and Number of Bays for AXSM Card Types
AXSM-1-2488
OC-48
1
1
AXSM-4-622
OC-12
1-4
1-2
AXSM-16-155
OC-3
1-8
1-2
AXSM-16-T3E3
T3, E3
1-8
1-2
Identifying Physical and Logical Elements
The Private Network-to-Network Interface (PNNI) control protocol and the service modules use different formats to identify the same entity. For example, the format of a logical port that you enter on an AXSM is different from the format you would enter on the PXM45. This section describes these formats in the PNNI and AXSM contexts and how they correspond to each other. The parallel actions of configuring or displaying logical elements on different cards is broadly illustrated in the Cisco
MGX 8850 Routing Switch Software Configuration Guide, Release 2.0.Apart from the way PNNI and the lower levels of logic identify the same element, the sequence of commands also needs explanation. When you configure logical ports—for just one example—you must complete certain tasks on the AXSM CLI before or after related PNNI tasks. For certain commands, this manual lists prerequisite commands or tasks. For more details on the sequence of tasks, refer to the Cisco MGX 8850 Routing Switch Software Configuration Guide, Release 2.0, for more details of this sequence.
AXSM Format
On a service module, you identify the follow when you provision the capabilities of the card:
•
•
•
•
•
•
Not all of these elements correspond to elements you specify on the PXM45. Subsequent paragraphs describe only the common elements that are visible on the CLI of the PXM and the service module. The preceding elements are further defined in the Cisco MGX 8850 Routing Switch Software Configuration Guide, Release 2.0.
For a UNI or NNI, one logical interface (or logical port) exists per physical line. For virtual network to network interfaces (VNNIs), you can configure multiple ports on a line. The maximum number of logical ports on an AXSM is 60 regardless of the AXSM model or the number of lines on the back cards. The range of logical port numbers is 1-60 for an AXSM regardless of whether the interface type is UNI, NNI, or VNNI.
PNNI Format
The PNNI controller requires the following format to identify a physical port:
[shelf.]slot[:subslot].port[:subport]
The PNNI physical port identifier (physical port ID) consists of a series of mandatory elements. Note the period or colon associated with each element inside the square brackets. The elements of the physical port ID are as follows:
•
•
•
•
•
For each physical port number, PNNI also generates a logical port number as an encrypted form of the physical port number. The logical port number appears as an unformatted numerical string. For example, a PNNI physical port ID may have the form 1:1.2:2, so the PNNI logical port number would be 16848898. Where needed, the descriptions in the PNNI command chapter define the need for this logical port number. (This section does not define a PNNI logical port number, nor does it describe the correspondence between an AXSM port and a PNNI logical port number.) For the correspondence between a PNNI physical port and the port identifier on an AXSM, see Table 5-2.
Table 5-2 Mapping PNNI Port ID to AXSM Elements
Shelf
N/A
Slot
Slot
Subslot
Bay (for upper or lower back card)
Port
Line
Subport
Logical interface (or port)
As Table 5-2 shows, a port to PNNI is a line on the AXSM, and a subport to PNNI is a logical interface (or logical port) on an AXSM. An example of a PNNI physical port identifier is 1:2.1:1. This portid corresponds to an AXSM, with the following particulars:
•
•
•
•
addpnni-node
Add PNNI Node—creates a PNNI logical node.
The addpnni-node command creates an instance of a PNNI logical node on the switch. Use addpnni-node to add a node in the following circumstances:
•
•
For a single-peer network, you do not initially need to execute addpnni-node because the node comes with a factory-set default. You can use cnfpnni-node to modify logical node values as needed.
Note
To modify an existing PNNI node, use cnfpnni-node. For some of the node parameters, you first must disable the node by executing cnfpnni-node -enable false. The following are applicable parameters:
•
•
•
•
The sections that follow define the preceding fields. Refer to the description of cnfpnni-node for the actual instructions to modify these items. Also, the Syntax Description section for addpnni-node provides details about these parameters.
Constraints in the Current Release
For some of the addpnni-node parameters, only one value is allowed because the current release supports only single-peer groups. The following list introduces these constraints, and the Syntax Description provides more details.
•
•
•
Address Field Descriptions
The addpnni-node parameters include two types of identifiers and an ATM address. These identifiers and the ATM address have similar formats and overlapping information. The sections that follow describe these parameters.
ATM Address of the Node
A switch-level ATM address consists of:
•
•
•
•
19 th. byte. The selector byte differentiates between these applications:–
–
–
Note
Figure 5-2 Switch-Level ATM Address
PNNI Logical Node Identifier
A PNNI logical node identifier (node ID) consists of:
•
•
•
•
Figure 5-3 PNNI Logical Node Identifier
Peer Group Identifier
A peer group identifier (pgID) consists of:
•
•
Figure 5-4 Peer Group Identifier
Cards on Which This Command Runs
PXM45
Syntax
addpnni-node <level>[lowest | other]][-atmAddr atm-address][-nodeId node-id][-pgId pg-id][-enable {true | false}][-transitRestricted {on | off}][-complexNode{on | off}][-branchingRestricted {on | off}]Syntax Description
level
The level specifies the level of the node in a PNNI hierarchy and does so by indicating the number of valid bits for a node ID (-nodeId parameter) or peer group ID (-pg-id parameter). In the current release, you can configure only one level. The level must be the same within the network.
The maximum number of levels you can configure on a switch 10. This limit is meaningful only in a multi-peer group. Although the level can any value, selecting an 8-bit boundary makes network planning and address management easier. Four example, using 56 for a level is more expedient than using a level of 59.
Range: 1-104 bits
Default = 56 bitslowest | other
Indicates whether the logical node you are adding is the lowest node in the hierarchy or exists at a level other than the lowest. Type the entire word "lowest" or "other."In the current release, you can specify only a single-peer group, so any node you add must be the lowest. In this case, this parameter must remain the default of "lowest."
If you are adding the node at the lowest level of the switch, you must also specify -atmAdd atm-address.
Default: lowest
-atmAddr
The ATM address of a PNNI logical node consists of 20 hexadecimal, 8-bit bytes (2 hexadecimal characters per byte).
If you are adding the lowest node in the switch, you must include an ATM address. For all levels above the lowest level, this ATM address is meaningless. The current release supports only a single peer group, so you must specify an ATM address for the one time that you execute addpnni-node. The first byte of atm-address indicates the address plan. For example, 47 is reserved for NSAP ICD, as in the following example:
47.00918100000000309409f1f1.00309409f1f1.01
Default: Figure 5-1 shows the Cisco default.
-nodeId
The PNNI logical node identifier (node ID). The node-id consists of the following logical elements, starting at the most significant byte:
•
•
•
Default: The Cisco default appears in Figure 5-1.
-pgId
The peer group ID (pg-id) identifies a PNNI peer group. (A PNNI peer group consists of all logical nodes with matching pg-ids. In a group of single-peer nodes, each switch has one logical PNNI node.)
The number of 8-bit bytes in the peer group ID (pg-id) is 14. However, the value of the level parameter is the number of bits that are actually used for the peer group ID. For example, with the default level of 56 bits (7 bytes), only the first 7 bytes of the peer group ID are relevant. Regardless of the number relevant bytes, the applicable display commands always show 14 bytes for a peer group ID and fill in the irrelevant byte positions with 0s.
Default: The Cisco default appears in Figure 5-1.
-enable
Specify the administrative state of the PNNI node. Most applications use the default—node enabled. However, you can add a node in the disabled state according to the necessities of your implementation. For example, you might want to configure the PNNI protocol but not be ready to enable. Later, you can enable it by executing cnfpnni-node -enable true.
true: Enable this logical node.
false: Disable this logical node.
Default: true-transitRestricted
Specifies whether this node can act as a transit node. You can restrict transit to secure the node or to minimize the traffic on a node that either has low-capacity or is high-priority.
on: Allow calls to transit this node.
off: Allow only call that terminate on this node.
Default: off-complexNode
The current release supports only SPGs, so this parameter currently has no effect. The complexNode parameter specifies whether the node is complex. Complex nodes exist only above the lowest node in the hierarchy.
on: This node is a complex node.
off: This node is not a complex node.
Default: off-branchingRestricted
The current release does not support point-to-multipoint branching, so this parameter has no effect. The branchingRestricted parameter specifies whether the PNNI node disallows point-to-multipoint branches. To enable or disable branching, this parameter actually turns on or off the restriction:
•
•
on: Do not allow point-to-multipoint branches.
off: Allow point-to-multipoint branches.
Default: on
Usage Guidelines
All nodes ship with a default ATM address, node ID, and peer group ID. Cisco uses these defaults to set up and test the switch. Before the switch carries live traffic, you should specify new addresses. For this purpose, you can either use the cnfpnni-node command or clear the configuration then use the addpnni-node command. (You can clear the PNNI configuration by using either clrcnf or clrallcnf.) The Cisco MGX 8850 Routing Switch Software Configuration Guide explains node-addressing in the section, "Guidelines for Creating an Address Plan."
Related Commands
cnfpnni-node, delpnni-node, dsppnni-node
Attributes
Example
Add a PNNI node with the following configuration then use dsppnni-node to check the configuration:
•
•
•
•
•
•
•
Enter the parameters in a contiguous line. The CLI allows wrapping (not apparent in the example).
SanJose.7.PXM.a > addpnni-node 56 -lowest true -atmAddr 47.00918100000000309409f1f1.00309409f1f1.01 -nodeId 56:160:47.0091 81000000 00309409f1f1.00309409f1f1.01 -pgId 56:47.00.9181.0000.0000.0000.0000.00 -enable true -transitRestricted offSanJose.7.PXM.a >Display the PNNI node configuration.
SanJose.7.PXM.a > dsppnni-nodenode index: 1 node name: SanJoseLevel............... 56 Lowest.............. trueRestricted transit.. off Complex node........ offBranching restricted onAdmin status........ up Operational status.. upNon-transit for PGL election.. offNode id...............56:160:47.00918100000000309409f1f1.00309409f1f1.01ATM address...........47.00918100000000309409f1f1.00309409f1f1.01Peer group id.........56:47.00.9181.0000.0000.0000.0000.00SanJose.7.PXM.a >addpnni-summary-addr
Add PNNI Summary Address—create a PNNI summary address to specify a range of addresses.
The addpnni-summary-addr command lets you create a summary address for a logical node. The result of this operation is a range of addresses. The controller uses this summary to accept or reject calls that arrive at an address within the address range. Using a summary address decreases both the provisioning time and the call setup time for an address within the range.
Cards on Which This Command Runs
PXM45
Syntax
addpnni-summary-addr <node-index> <address-prefix> <prefix-length>[-type {internal | exterior}][-suppress {true | false}]Syntax Description
The defaults for address prefixes and the peer group ID share values with the ATM address. If you change the peer group ID (-pgId) you should change the corresponding fields in the PNNI summary address. (See Figure 5-5.)
Figure 5-5 Cisco Factory-shipped Defaults for PNNI Peer Group Identifier, PNNI Summary Address, ATM Address, and PNNI Node Identifier
node-index
The node index indicates the relative position of the logical node within a multi-peer group on the switch. The range is 1-10, and the lowest level is 1. If you do not have the node index, use dsppnni-node to see a list of all logical nodes and node indexes on the current switch. In the current release, the value of node-index must be `1'.
Range: 1-10
Default: 1addressprefix
The summary address assigned to the node. The length of addressprefix is the value of prefixlength.
As shown in Figure 5-5, addressprefix is a formatted hexadecimal string.
Default: The default is the first 13 bytes of the atm-addr.
prefixlength
Specify the length of the address-prefix in bits. The range is 1-152 bits. You configure PNNI routing to look at a specific length in the address, so the length of the PNNI summary address is also configurable. For example, if you configure a node with an 88-bit PNNI summary address, that node sets up a call from any addresses that matches the first 88 bits. The number of addresses that a PNNI summary address can include is inversely related to the length of the PNNI summary address—a shorter summary address can include more addresses than a shorter prefix.
In the current release, the zero-length summary address is not supported.
Range: 1-152 bits
Default: none-type
Specify the type of the PNNI summary address, either exterior or internal.
internal: The summary address includes only addresses that are within the peer group.
exterior: The summary address includes addresses that are outside the peer group.
Default: internal
-suppress
Specify whether the summary address is advertised to other nodes
false: The summary address is advertised (is not suppressed).
true: The summary address is not advertised (is suppressed).Default: false
Usage Guidelines
The PNNI summary address table information comes from the internal data base (IDB). If you change or create a PNNI summary address, a topology state packet carries the information to the IDB. The summary address table updates itself from the IDB.
Related Commands
delpnni-summary-addr, dsppnni-summary-addr
Attributes
Example
This example shows the addpnni-summary-addr command line that adds a PNNI address prefix, configured as follows:
•
•
•
•
Use dsppnni-summary-addr to display the PNNI address prefixes.
SanJose.7.PXM.a > addpnni-summary-addr 1 47.0091.8100.0000.0030.9409.f1f1 104 -type internal -suppress falseSanJose.7.PXM.a > dsppnni-summary-addr 1node index: 1Type.............. internal Suppress.............. falseState............. advertisingSummary address........47.0091.8100.0000.0030.9409.f1f1/104SanJose.7.PXM.a >aesa_ping
ATM End Station Address Ping—confirm the connection from a node to an ATM End Station.
The aesa_ping command lets you ping any ATM end station address (AESA) connected to a PNNI network. Use this command to check PNNI connectivity to the given destination address. You can use the optional arguments -setupcall, -qos, -trace, and -data to send packets and provide greater granularity to the information that the command sends to the screen.
The parameters that you enter in the aesa_ping command don't specify anything except the execution of the command itself. All behaviors started by the command stop when the interval -timeout expires.
Cards on Which This Command Runs
PXM45
Syntax
aesa_ping <destination address>[-setupcall {yes | no}][-qos {ubr | abr | cbr}][-trace {yes | no}][-data {enable | disable}][-timeout {time out in secs}][-interval {time}][-pcr {peak cell rate}][-scr {sustain cell rate}]Syntax Description
Related Commands
dsppingatmaddr
Attributes
Example
This example shows the aesa_ping command line that pings the ATM end station with the address 47.00918100000000d058ac23ac.00d058ac23ac.01. The ping is configured as follows:
•
•
•
•
•
•
•
•
SanJose.7.PXM.a > aesa_ping 47.00918100000000d058ac23ac.00d058ac23ac.01 -setupcall no -qos ubr -trace no -data disable -timeout 6 -interval 60 -pcr 5 -scr 5Ping Got CLI message, index=0PING:from PNNI—SOURCE ROUTEDTL 1 :Number of (Node/port)elements 2DTL 1:NODE 1::56:160:71:0:145::238:238:238:238:Port 1:262656DTL 1:NODE 2::56:160:71:0:145::88:172:35:172:Port 2:0Port List :no of ports = 1Port ID 1:262656SanJose.7.PXM.a >cnfpnni-election
Configure PNNI Election—configure a rank and other parameters for electing a peer group leader.
The cnfpnni-election command lets you specify the priority of a node for the purpose of electing a peer group leader (PGL). By using this ranking, you can promote or prevent certain nodes for consideration for election as PGL.
Note
In a multi-peer group environment, each peer group can elect one PGL. Such an election takes place for every level of the hierarchy. (For example, if three levels exist, three PGL elections occur.) To ensure that a node cannot win the PGL election, you can assign 0 for the priority.
Every node in a peer group runs the election algorithm—with one exception: a node with the Non-Transit for PGL E;ection Flag set.
In addition to the priority, cnfpnni-election lets you specify the:
•
•
•
Cards on Which This Command Runs
PXM45
Syntax
cnfpnni-election <node-index>[-priority priority][-initTime init-time][-overrideDelay override-delay][-reelectionTime reelection-time]Syntax Description
Related Commands
dsppnni-election
Attributes
Example
In the current release, this command has no meaning.
cnfpnni-intf
Configure PNNI Interface—specify administrative weight or logical link aggregation for a port.
The cnfpnni-intf command lets you specify two distinct PNNI parameters. The aggregation token applies to a logical node, and the administrative weight (AW) applies to a port.
Note
Aggregation Tokens
An aggregation token is a marker that indicates which up-links (links going out of the peer group) can be bundled or aggregated at the next logical level. For example, if four links a, b, c, and d connect to peer groups X and Y, no aggregation exists for the links by default. The LGNs of these peer groups could have hypothetical names x02 and y02. They would be connected by a single logical link. You could use the cnfpnni-intf command to configure aggregation tokens.
If you configure the aggregation token of link c as 1, then x02 and y02 would have two logical links. One link would correspond to aggregation token 0, and the other link would correspond to aggregation token 1. In summary:
An aggregation token is the number of links between a peer group leader and the lowest level of a PNNI hierarchy. The range for tokens is 1-32.
Administrative Weight
The administrative weight (AW) is a number that serves as a cost-based determinant of a route. Each port in a PNNI network has a default AW for the egress direction. Whether it uses the default AW or an AW you specify, PNNI adds all the AWs in a prospective route then determines whether the route is too expensive. For an SPVC, you can specify the maximum cost with the addcon or cnfcon command.
You can specify that all classes of service on the port have the same AW, or you can specify an AW for each service class on the port. If you specify the same AW for all, it overrides the default AW or the AW you might specify for individual services types.
The AW for a path is the sum, in both directions, of the individual weight of each link on the path. See "Usage Guidelines" section for details about AW.
Cards on Which This Command Runs
PXM45
Syntax
cnfpnni-intf <portid>[-aggregationToken token][-awcbr aw][-awrtvbr aw][-awnrtvbr aw][-awabr aw][-awubr aw][-awall aw]Syntax Description
If you enter -awall to specify an AW, it overrides the AW for all individual service types.
portid
The PNNI physical port ID. The portid has the format [shelf.]slot[:subslot].port[:subport]. For more details about portid, see PNNI Format.
Default: none
-aggregationToken
Specify a 32-bit number for logical link aggregation between a peer group leader and the lowest level.
Range: 0-2147483648
Default: 0The current release does not support multiple PNNI levels, so this parameter has no meaning.
-awcbr
Specify the administrative weight for constant bit rate (CBR) on this interface.
Range: 0-4194304
Default: 5040-awrtvbr
Specify the administrative weight for real-time variable bit rate (rt-VBR) on this interface.
Range: 0-4194304
Default: 5040-awnrtvbr
Specify the administrative weight for non-real-time variable bit rate (nrt-VBR) on this interface.
Range: 0-4194304
Default: 5040-awabr
Specify the administrative weight for available bit rate (ABR) on this interface.
Range: 0-4194304
Default: 5040-awubr
Specify the administrative weight for unspecified bit rate (UBR) on this interface. UBR connections can include SVC ping connections.
Range: 0-4194304
Default: 5040-awall
Specify the administrative weight for all service types on this interface. If you use -awall, this aw becomes the AW for every service type on this port.
Range: 0-4194304
Default: 5040
t
Usage Guidelines
PNNI includes a protocol for routing the topology state. This protocol advertises details about the peer group links and nodes. Links and nodes are assigned attributes that can be used to diagnose and tune network behavior.
The administrative weight (AW) for a port is an integer that has no units of measure. The switch compares the sum of all AWs along a path with the sum of all AWs along another path to determine which path is more cost-effective. You can specify one AW for all classes of service, or you can specify an AW for each class of service. The AW for all (-awall) overrides the AW for an individual class.
The AW parameter influences how PNNI selects a path within a peer group and therefore how it distributes SVCs and SPVCs. PNNI route selection can also use AW to exclude certain links from routing. For example, it can define a backup link for use only when insufficient bandwidth is available on the primary link.
Related Commands
dsppnni-intf
Attributes
Example
Specify the following AWs on port 4:1.1:11.
•
•
•
Use the dsppnni-intf command to display the configuration.
SanJose.7.PXM.a > cnfpnni-intf 4:1.1:11 -awrtvbr 11040 -awnrtvbr 20040 -awubr 1040SanJose.7.PXM.a > dsppnni-intf 4:1.1:11Physical port id: 4: 1.1:11 Logical port id: 17045515Aggr token.......... 0 AW-NRTVBR........... 20040AW-CBR.............. 5040 AW-ABR.............. 5040AW-RTVBR............ 11040 AW-UBR.............. 1040SanJose.7.PXM.a >cnfpnni-link-selection
Configure PNNI Link Selection—specify the routing policies for parallel links.
The cnfpnni-link-selection command specifies which routing policies are used to select one of the parallel links that connect a neighboring PNNI node. Neighboring node in this case means a directly connected node. The cnfpnni-link-selection command applies only if parallel links exist between the specified port and neighboring nodes.
Cards on Which This Command Runs
PXM45
Syntax
cnfpnni-link-selection <portid> {minaw | maxavcr | maxcr | loadbalance}Syntax Description
portid
The portid is the PNNI physical port. The format is [shelf.]slot[:subslot].port[:subport]. See also PNNI Format.
Default: no default port ID
minaw
The routing protocol selects the link with the least administrative weight (AW). The AW is a numeric value that every logical port ingress has. The total cost of a route is the sum of all ingress port AWs in both directions of the route.
The minaw policy is the default.
maxavcr
The routing protocol selects the link with the largest available cell rate (AvCR). The AvCR is the remaining bandwidth after the total utilized bandwidth is subtracted from the maximum cell rate (MaxCR).
The maxavcr policy works well for traffic that consistently requires a large amount of bandwidth.
maxcr
The routing protocol selects the link with the largest maximum cell rate (MaxCR). Typically, the MaxCR is the maximum speed of the line (or trunk). Therefore, if one link traverses an OC3 line and another link traverses a T3 line, the MaxCR policy dictates that PNNI select the OC3 line. Only when sufficient bandwidth does not exist on a line does the routing protocol switch to AvCR.
The maxcr policy works well for bursty traffic.
loadbalance
The routing protocol alternates the link it selects for routing new calls. The load balance policy works well with links that have identical or very similar AW or bandwidth characteristics.
Related Commands
dsppnni-link-selection
Attributes
Example
Specify maximum available cell rate as the routing policy for the link with port ID 4:1.1:11. Use dsppnni-link-selection to see the link selection policy on this port. Note that dsppnni-link-selection shows the logical port number for the physical port ID.
SanJose.7.PXM.a > cnfpnni-link-selection 4:1.1:11 maxavcrSanJose.7.PXM.a > dsppnni-link-selection 4:1.1:11physical port id: 4:1.1:11 link selection: maxavcrlogical port id: 17045515SanJose.7.PXM.a >cnfpnni-mtu
Configure PNNI Maximum Transfer Unit—specify the maximum data packet size that the node supports.
The cnfpnni-mtu command specifies the maximum data packet size in number of bytes. This command is useful for internetworking compatibility, for which you must match the maximum packet size of your peer group to a size that another peer group can support. Although this command applies primarily to internetwork compatibility, you can also use it in trials to test the affect of various packet sizes on the performance of the peer group.
Use dsppnni-mtu to display the PNNI packet size configuration.
Cards on Which This Command Runs
PXM45
Syntax
cnfpnni-mtu <mtu>Syntax Description
Related Commands
dsppnni-mtu
Attributes
Example
This example shows the cnfpnni-mtu command line that specifies the maximum PNNI packet size to 3002 bytes. Use dsppnni-mtu to display the specified information.
SanJose.7.PXM.a > cnfpnni-mtu 3002SanJose.7.PXM.a > dsppnni-mtumax packet size: 3002SanJose.7.PXM.a >cnfpnni-node
Configure PNNI Node—modify parameters for an existing PNNI node.
The node-level cnfpnni-node command lets you:
•
•
–
–
The node configuration and state parameters you can modify are as follows:
•
•
•
•
•
•
•
•
•
The preceding parameters appear as optional parameters in the syntax. The only required parameter for this command is the local node index. In the current release, the only node index is "1."
Note
Disabling a Node When Required
For some of parameters, you must first disable the node. Applicable parameters are the:
•
•
•
•
For these parameters, three executions of cnfpnni-node are necessary:
1.
2.
3.
Be sure to synchronize applicable changes (such a change in level) throughout the network and follow up with dsppnni-node or other applicable display commands.
Cards on Which This Command Runs
PXM45
Syntax
cnfpnni-node <node-index>[-atmAddr atm-address][-level level][-nodeId node-id][-pgId pg-id][-lowest {true | false}][-enable {true | false}][-transitRestricted {on | off}][-complexNode{on | off}][-branchingRestricted {on | off}]Syntax Description
node-index
The node index specifies the relative position of a logical node within the hierarchy of a multi-peer group. The lowest level is 1. In the current release, the only node-index is `1'. Each new logical node added to the hierarchy automatically gets the next higher index number, so you cannot configure the node index.
Range: 1-10
Default: 1-atmAddr
Specify the ATM address for this logical node. For you to change the ATM address, the node must be disabled. For details, see the section, "Disabling a Node When Required." Note that only the lowest node in the hierarchy requires an ATM address.
Default: Figure 5-6 shows the factory-set default.
-level
This parameter specifies the level of the node within the PNNI hierarchy. The level of the node is the number of bits in the node ID (-nodeId parameter) or peer group ID (-pg-id parameter). For example, the default level of 56 means that the node ID is 56 bits long. If you specify a level of 48, the node ID has a length of 48 bits.
The maximum number of levels you can configure on a switch 10. This limit is meaningful in a multi-peer group only. Although the level can be any value within the 1-104 range, selecting an 8-bit boundary makes network planning and address management easier. Four example, using 56 for a level is more expedient than using a level of 59.
Range: 1-104 bits
Default: 56 bits-nodeId
Specify the PNNI node identifier assigned to a PNNI node. The node-id consists of the PNNI hierarchy level (-level) followed by the length of the ATM address (addaddr length) followed by the ATM address (-atmAddr).
Note
As shown in Figure 5-6, -nodeId is a 22-byte, formatted hexadecimal string. Like all PNNI addresses, identifiers, and prefixes, this value is portrayed as a string of hexadecimal "nibbles." One or several pairs of nibbles entail each parameter field.
Default: Figure 5-6 shows the factory-set default.
-pgId
All members of a peer group have the same peer group identifier (pgID) and exist on the same level. (The level is either the existing number of bits or whatever you specify with -level level).
The default value of level is 56 (7 bytes), which specifies the length of -pgId to 7 bytes. However, the maximum length of -pgId is 14 bytes, so display commands always show -pgId as 14 bytes with trailing zeros filling the undefined fields. If you increase the value of level, you change the length, and therefore the value, of -pgId, but it will always be displayed as 14 bytes.
Before you change the value of pg-id, disable the node by entering cnfpnni-node -enable false.
This is a 14-byte, formatted hexadecimal string.
Default: Figure 5-6 shows the factory-set default.-enable
Specify the administrative status of the PNNI node. Before you change a node ATM address, node ID, peer group ID, or hierarchical level, the node must be disabled.
true: Enable the node.
false: Disable the node.Default: true
-transitRestricted
Specify whether connections can transit this node. You can disallow via connections for security reasons, to minimize traffic supported by either a low bandwidth node or a highly critical node, and so on.
on: This node allows via connections.
off: Via connections cannot transit this node.Default: off
-complexNode
Specify whether this node is a complex node. The lowest-level node cannot be a complex node.
on: This node is a complex node.
off: This node is not a complex node.Default: off
Note
-branchingRestricted
Specify whether the PNNI node allows point-to-multipoint branches.
on: This node does not allow point-to-multipoint branches.
off: This node allows point-to-multipoint branches.Default: on
Note
Note
Caution
Figure 5-6 Cisco Factory-shipped Defaults for PNNI Peer Group Identifier, PNNI Summary Address, ATM Address, and PNNI Node Identifier
Usage Guidelines
All MGX 8850 cards ship with default addresses. These defaults are provided for evaluation of the switch. Before or while you deploy a switch, you should change the default addresses by executing either cnfpnni-node or addpnni-node. The Cisco MGX 8850 Routing Switch Software Configuration Guide explains node addressing in the section Guidelines for Creating an Address Plan.
The ATM address, address prefixes, and peer group ID share some default field values, as shown in Figure 5-6.
Related Commands
addpnni-node, delpnni-node, dsppnni-node, addaddr
Attributes
Example
This example shows the cnfpnni-node command line that specifies the PNNI configuration values for a node that already exists on the network. The command line configures the PNNI node as follows:
•
•
•
•
•
•
•
•
•
Use dsppnni-node to display the PNNI configuration values.
SanJose.7.PXM.a > cnfpnni-node 1 -level 56 -nodeId 56:160:47.0091 81000000 00309409f1f1.00309409f1f1.01 -atmAddr 47.0091 81000000 00309409f1f1.00309409f1f1.01 -pgId 56:47.00.9181.0000.0000.0000.0000.00 -lowest true -enable true -transitRestricted on -complexNode off -branchingRestricted offSanJose.7.PXM.a > dsppnni-nodenode index: 1 node name: SanJoseLevel............... 56 Lowest.............. trueRestricted transit.. on Complex node........ offBranching restricted offAdmin status........ up Operational status.. upNon-transit for PGL election.. offNode id...............56:160:47.00918100000000309409f1f1.00309409f1f1.01ATM address...........47.00918100000000309409f1f1.00309409f1f1.01Peer group id.........56:47.00.9181.0000.0000.0000.0000.00SanJose.7.PXM.a >cnfpnni-pkttrace
Configure PNNI Packet Trace—specify the parameters to trace packets.
This command applies to debugging. It causes the switch to check the PNNI packets transmitted and received at each peer. For example, if an interface is not receiving user-traffic, you can execute dsppnni-pktrace to display packet information that can help you find the level and type of blockage.
The cnfpnni-pkttrace command specifies the trace command examines the contents of PNNI packets exchanged between two neighboring nodes. A PNNI packet consists of a Hello packet and the topology information packets.
Note
If you plan to use the optional -portId parameter but do not have the logical format of the port ID, use dsppnport. For details, refer to the Syntax Description of cnfpnni-pkttrace.
Cards on Which This Command Runs
PXM45
Syntax
cnfpnni-pkttrace {tx {on|off} | rx {on|off} } [node-index [-portId port-id | -svcIndex svc-index]]Syntax Description
Usage Guidelines
PNNI trace commands have characteristics that standard debug commands lack, namely:
•
•
•
Related Commands
dsppnni-pkttrace, dsppnport, dsppnports
Attributes
Example
Configure then display a trace that examines the contents of PNNI Hello packets, as follows:
•
•
•
Geneva.7.PXM.a > cnfpnni-pkttrace tx 17504PNNI/tx_packet on port 17504 at level 56> 01:00010064 01010100 000038a0 47009181 00000000 309409f3 b8003094> 02:09f3b801 47009181 00000000 309409f3 b8003094 09f3b801 38470091> 03:81000000 00000000 000038a0 47009181 00000000 001a531c 2a00001aGeneva.7.PXM.a > dsppnni-pkttrace tx -portId 17504Node Index :1 Port id: 17504 Tx Pkt Trace onGeneva.7.PXM.a >cnfpnni-routing-policy
Configure PNNI Routing Policy—specify the routing policy parameters.
The cnfpnni-routing-policy command specifies which routing policy values are used during UNI call setup. Routing policies control PNNI routing for your network.
The cnfpnni-routing-policy command specifies which routing policies are used for:
•
•
•
The two dynamic routing protocols are shortest path and on-demand routing.
Background Routing Tables
The background routing tables contain all routes within the peer group. The routes are calculated from information in the internal data base (IDB). When a topology change affects usable routes within the peer group, a PNNI topology state packet carries the formation to each node so it can update its IDB. The background routing tables are updated to reflect the change in routing parameters.
Routing tables are generated (or pre-computed) to support routing based on the shortest path.
•
•
•
On-demand routing is used if any of the following occur:
•
•
•
Caution
Cards on Which This Command Runs
PXM45
Syntax
cnfpnni-routing-policy[-sptEpsilon epsilon][-sptHolddown holddown][-bnPathHolddown bn-path-holddown][-loadBalance {random | maxbw}][-onDemand {firstfit | bestfit}][-awBgTable {on|off}][-ctdBgTable {on|off}][-cdvBgTable {on|off}]Syntax Description
Related Commands
dsppnni-routing-policy
Attributes
Example
Specify the following routing policy:
•
•
•
•
•
•
•
You can confirm your settings with the related command dsppnni-routing-policy.
Geneva.7.PXM.a > cnfpnni-routing-policy -sptEpsilon 0 -sptHolddown 1 -loadBalance random -onDemand bestfit -awBgTable on -ctdBgTable on -cdvBgTable onGeneva.7.PXM.a > dsppnni-routing-policySPT epsilon......... 0 Load balance........ randomSPT holddown time... 1 On demand routing... best fitSPT path holddown time 2 AW Background Table onCTD Background Table on CDV Background Table onGeneva.7.PXM.a >cnfpnni-scope-map
Configure PNNI Scope Map Table—specify the table that maps the UNI 4.0 values to the PNNI hierarchy levels.
The cnfpnni-scope-map command specifies how UNI 4.0 address scope values are mapped to PNNI hierarchal levels. These parameters are stored in the scope map table.
Note
Cards on Which This Command Runs
PXM45
Syntax
cnfpnni-scope-map <scope> <level>Syntax Description
Related Commands
dsppnni-scope-map
Attributes
Example
This command is not supported by the current release.
cnfpnni-svcc-rcc-timer
Configure PNNI Switched Virtual Connection Routing Control Channel (SVCC-RCC) Timer—specify the parameters for any PNNI RCCs between logical nodes.
The current release does not support this command. The cnfpnni-svcc-rcc-timer command lets you specify the initial PNNI SVCC-based variables for a network node. Logical group nodes (LGNs) use SVCC-RCCs to exchange routing information.
Cards on Which This Command Runs
PXM45
Syntax
cnfpnni-svcc-rcc-timer <node-index>[-initTime init-time][-retryTime retry-time][-callingIntegrityTime calling-integrity-time][-calledIntegrityTime called-integrity-time]Syntax Description
Related Commands
dsppnni-svcc-rcc-timer
Attributes
This command is not supported by the current release.
cnfpnni-timer
Configure PNNI Timers
The cnfpnni-timer command specifies the initial PNNI timer values and significant change thresholds of a PNNI node in the network.
Note
Cards on Which This Command Runs
PXM45
Syntax
cnfpnni-timer <node-index>[-ptseHolddown ptse-holddown][-helloHolddown hello-holddown][-helloInterval hello-interval][-helloInactivity-factor hello-inactivity-factor][-horizontalLinkInactivityTime horizontal-link-inactivity-time][-ptseRefreshInterval ptse-refresh-interval][-ptseLifetimeFactor ptse-lifetime-factor][-retransmitInterval retransmit-interval][-ptseDelayedAckInterval ptse-delayed-ack-interval][-avcrPm avcr-pm][-avcrMt avcr-mt][-cdvPm cdv-pm][-ctdPm ctd-pm]Syntax Description
Usage Guidelines
PTSE packets update the peer group when network changes occur. Your network should run fine with the defaults PTSE timing parameters. Networks that have properties significantly different from the norm may perform better if you optimize some of the PTSE parameters, but you should change these parameters carefully, and test the network before introducing live traffic.
For example, if no one is permitted to change a network topology (perhaps for test purposes), you may decide that the default -ptseHolddown value (1 sec) is too small, causing sequential broadcasts of identical PTSE packets. Further reason for making such a change would be given if the network was a small and it's connections were short. Inversely, it may warrant a smaller -ptseHolddown value if many changes are being made to a network, or if it was large, or if it had many long connections. These are only examples—these changes should only be made be network experts.
Related Commands
dsppnni-timer
Attributes
Example
This example shows the cnfpnni-timer command line that is set with the following parameter values:
•
•
•
•
•
•
•
•
•
•
•
•
You can confirm your settings with the related command dsppnni-timer.
SanJose.7.PXM.a > cnfpnni-timer 1 -ptseHolddown 120 -helloHolddown 120 -helloInterval 15 -helloInactivity-factor 5 -horizontalLinkInactivityTime 10 -ptseRefreshInterval 1800 -ptseLifetimeFactor 200 -retransmitInterval 50 -ptseDelayedAckInterval 10 -avcrPm 3 -avcrMt 50 -cdvPm 25 -ctdPm 50SanJose.7.PXM.a > dsppnni-timer 1node index: 1Hello holddown(100ms)... 12 PTSE holddown(100ms)... 12Hello int(sec).......... 15 PTSE refresh int(sec).. 1800Hello inactivity factor. 5 PTSE lifetime factor... 200Retransmit int(sec)..... 5AvCR proportional PM.... 3 CDV PM multiplier...... 25AvCR minimum threshold.. 50 CTD PM multiplier...... 50Peer delayed ack int(100ms)................... 10Logical horizontal link inactivity time(sec).. 10Geneva.7.PXM.a >dbgpnni
Debug PNNI Messages—specify which PNNI debug messages are enabled.
The dbgpnni command lets you specify the types of debug messages that appear in the display of the dsppnni-dbg command.
Note
Cards on Which This Command Runs
PXM45
Syntax
dbgpnni[-all {on | off}][-hello {on | off}][-election {on | off}][-nbr {on | off}][-itf {on | off}][-timer {on | off}][-lgn {on | off}][-spt {on | off}][-nodereachability {on | off}][-address {on | off}][-itdb {on | off}][-ra {on | off}][-cp {on | off}][-linkselection {on | off}]Syntax Description
Related Commands
dsppnni-dbg
Attributes
Example
Specify the following PNNI debug message-options:
•
•
Use dsppnni-dbg to check which debug messages types appear on the terminal.
SanJose.7.PXM.a > dsppnni-dbgpnni debugging option:hello election nbr itf timer lgn spt node reachability----- -------- --- --- ----- --- --- -----------------off off off off off off off offaddress itdb ra cp link selection------- ---- --- --- --------------off off off off offSanJose.7.PXM.a > dbgpnni -itf on -address onSanJose.7.PXM.a > dsppnni-dbgpnni debugging option:hello election nbr itf timer lgn spt node reachability----- -------- --- --- ----- --- --- -----------------off off off on off off off offaddress itdb ra cp link selection------- ---- --- --- --------------on off off off offIn the second example, the parameters are changed as follows:
•
•
SanJose.7.PXM.a > dbgpnni -itf off -address offSanJose.7.PXM.a > dsppnni-dbgpnni debugging option:hello election nbr itf timer lgn spt node reachability----- -------- --- --- ----- --- --- -----------------off off off off off off off offaddress itdb ra cp link selection------- ---- --- --- --------------off off off off offSanJose.7.PXM.a >delpnni-node
Delete PNNI Node-delete a PNNI node from the PNNI network topology.
The delpnni-node command removes a PNNI node from the PNNI network topology. A node that this command deletes can be restored with the related command addpnni-node. Confirm the deletion of nodes with the dsppnni-node command.
Cards on Which This Command Runs
PXM45
Syntax
delpnni-node <node-index>Syntax Description
Related Commands
addpnni-node, cnfpnni-node, delpnni-node
Attributes
Example
Delete the node with the node-index of 3. Execute dsppnni-node and specify a node index of 3. The last line of the d display shows the error "node does not exist," indicating you successfully deleted the node.
SanJose.7.PXM.a > delpnni-node 3SanJose.7.PXM.a > dsppnni-node 3Unknown Error CodeSyntax: dsppnni-node [node-index]nodeIndex -- node-index: 32 bit number starting from 1, Optional parameterpossible errors are:node does not existSanJose.7.PXM.a >delpnni-summary-addr
Delete PNNI Summary Address—delete a PNNI summary address from the node.
The delpnni-summary-addr command deletes a PNNI summary address for a PNNI node.
Cards on Which This Command Runs
PXM45
Syntax
delpnni-summary-addr <node-index> <address-prefix> <prefix-length>Syntax Description
Related Commands
addpnni-summary-addr, dsppnni-summary-addr
Attributes
Example
Delete a summary address, as follows:
•
•
•
If necessary, use dsppnni-summary-addr to confirm the deletion.
SanJose.7.PXM.a > delpnni-summary-addr 1 47.0091.8100.0000.0030.9409.f1f1 104SanJose.7.PXM.a >dsppnni-bn-path
Display PNNI Border Node Paths—display the PNNI border node paths.
This debugging command displays the border node-to-border node paths of the immediate child-peer-group of the logical group nodes (LGN).
Note
Cards on Which This Command Runs
PXM45
Syntax
dsppnni-bn-path <node-index>Syntax Description
node-index
The node index indicates the relative level of the logical node within the hierarchy on the switch. The range is 1-10, and the lowest level is 1.
Range: 1-10
Default: none
Contents of the dsppnni-bn-path Output
Related Commands
None
Attributes
Example
Enter dsppnni-db-path and specify node index 2.
mpg2.7.PXM.a > dsppnni-bn-path 2node index:2source node IDB index source node id--------------------- --------------------------------------------------1 56:160:47.009181000000003071f80e56.003071f80e56.01destination node IDB index destination node id-------------------------- --------------------------------------------------12 56:160:47.009181000000003071f80e52.003071f80e52.01CBR RTVBR NRTVBR ABR UBR------ ------ ------ ------ ------AW 5040 5040 5040 5040 5040MaxCR 250000 250000 250000 250000 250000AvCR 248759 248759 248759 248759 248759CTD 17 17 17 17 17CDV 4167 52954 52954 104912 104912CLR0 8 8 8 8 8CLR0+1 8 8 8 8 8dsppnni-bypass
Display PNNI Bypasses—display the PNNI complex node bypass table.
This debugging command displays the PNNI bypass table for a logical group node (LGN) that uses the complex node representation of its peer group. The bypass table contains the topology and Hello information of every node in the peer group.
Note
Cards on Which This Command Runs
PXM45
Syntax
dsppnni-bypass <node-index>Syntax Description
Display Contents
The display contains the following fields for each node.
Related Commands
None
Attributes
Example
Display the bypass table for an LGN using complex node representation in the peer group.
Geneva.7.PXM.a > dsppnni-bypassnode index: 1Input portId........ 376 Output portId........ 399Ptse id............. 12 Flags................ a3CBR RTVBR NRTVBR ABR UBR----- ------ ------ ------ ------ ------AW 5040 5040 5040 5040 5040MCR 0 0 0 0 0AvCR 100000 100000 100000 100000 100000CTD 0 0 0 0 0CDV 0 0 0 0 0CLR0 0 0 0 0 0CLR0+1 0 0 0 0 0CRM 10 10 10 10 10VF 5 5 5 5 5Geneva.7.PXM.a >dsppnni-dbg
Display PNNI Debug Flags—display the settings of all PNNI debug flags.
The dsppnni-dbg command displays which PNNI debug options are enabled and which are disabled.
Cards on Which This Command Runs
PXM45
Syntax
dsppnni-dbgDisplay Contents
This section describes the content of the display for each node. The right column shows the label for each value that appears in the dsppnni-dbg command. The left column maps each value to the corresponding keyword in the dbgpnni command, and explains the argument function.
Related Commands
dbgpnni
Attributes
Example
Display the active PNNI debug options.
Unknown.1.1.PXM45.a > dsppnni-dbgpnni debugging option:hello election nbr itf timer lgn spt node reachability----- -------- --- --- ----- --- --- -----------------off off off off off off off offaddress itdb ra cp link selection------- ---- --- --- --------------off off off off offGeneva.7.PXM.a >dsppnni-election
Display PNNI Election—display information for election a peer group leader.
The dsppnni-election command displays parameters and current status related to the election of a peer group leader (PGL). This command and related information applies to multi-peer groups only. The cnfpnni-election command lets you specify election parameters.
In a multi-peer group environment, each peer group can elect one PGL. Such an election takes place for every level of the hierarchy. (For example, if three levels exist, three PGL elections occur.)
Cards on Which This Command Runs
PXM45
Syntax
dsppnni-election[node-index]Syntax Description
Objects Displayed
The following parameters are displayed for each node.
Related Commands
cnfpnni-election, cnfpnni-node, dsppnni-node, dsppnni-node-list, dsppnni-summary-addr
Attributes
Example
Display the information about peer group leader election for all nodes in the hierarchy.
8850_NY.7.PXM.a > dsppnni-electionnode index: 1PGL state...... OperNotPgl Init time(sec)....... 15Priority....... 150 Override delay(sec).. 30Re-election time(sec) 15Pref PGL...............56:160:47.0091810000020004c113ba75.0004c113ba75.01PGL....................56:160:47.0091810000020004c113ba75.0004c113ba75.01Active parent node id..0:0:00.000000000000000000000000.000000000000.00node index: 2PGL state...... Starting Init time(sec)....... 15Priority....... 0 Override delay(sec).. 30Re-election time(sec) 15Pref PGL...............0:0:00.000000000000000000000000.000000000000.00PGL....................0:0:00.000000000000000000000000.000000000000.00Active parent node id..0:0:00.000000000000000000000000.000000000000.00dsppnni-idb
Display PNNI Internal Data Base—display the PNNI link-state information for the node.
The dsppnni-idb command applies solely to debugging. It lets you see all the nodes and links that the current node has discovered. If a node or link should be in the internal database (IDB) but is missing, you can check the PTSEs (dsppnni-ptse) to begin tracing the missing topology information.
An IDB stores all the logical nodes known to the local node (its own levels and the network nodes in each logical node's view) and the outgoing links from all of them. The IDBs are the source of all address and routing tables in the peer group. When a node advertises PNNI topology state elements (PTSEs), the updated information goes into the IDB updates. The system address table, local network reachable address table, background routing tables, and PNNI summary address table receive updates from the IDB as appropriate.
The dsppnni-idb command can display all the contents or a subset of the IDB. You can specify the granularity of the display by using the optional parameters:
•
•
•
•
Cards on Which This Command Runs
PXM45
Syntax
dsppnni-idb [node-index] [-nodeNumber node-number [-portId port-id]]Syntax Description
node-index
The node index is the system-generated number of the local logical node. In a multi-peer group hierarchy, the range is 1-10. In the current release, the only node index is 1.
Range: 1-10
-nodeNumber
A number that uniquely identifies a node in the network. For a list of the remote node numbers that are visible to the local node, use dsppnni-node-list.
Range: 1-256
-portId
The logical number for a PNNI port. Use this optional parameter if you have specified a node number (-nodeNumber) and want to narrow the scope of the display.
You can obtain the logical number for the port ID by executing dsppnports for all PNNI ports or dsppnport a:b.c.d for a specific port (where a,b,c, and d are the values corresponding to the physical portID. For more details, see the "PNNI Format" section.)
Range: 1-2147483648
Related Commands
none
Attributes
Examples
Display the link-state information for the following:
•
•
•
Geneva.7.PXM.a > dsppnni-idb 1 -nodeNumber 1 -portId 16848901node index:1Local port id....... 16848901 Remote port id....... 16848901Local link index.... 1 Remote link index.... 1Local node number... 1 Remote node number... 2PGL node index...... 0 LGN node index....... 0Transit restricted.. off Complex node......... offBranching restricted on PGL.................. falseAncestor............ false Border node.......... falseVP capable.......... true Link type............horizontalNon-transit for PGL election.. offnode id...............56:160:47.00918100000000107be92f46.00107be92f46.01node name.............pswmgx2-2Geneva.7.PXM.a >dsppnni-inducing-uplink
Display PNNI Inducing Uplink—display the PNNI inducing uplink database.
The dsppnni-inducing-uplink command displays the uplink-inducing database. The only application of dsppnni-inducing-uplink is debugging.
Note
The display shows:
•
•
•
•
•
•
The child node number is the number of a node at a lower level (as shown by dsppnni-node-list) from which the uplink comes. The child port ID is the local port ID of the child node from which the uplink comes. You can see the details of this uplink by executing dsppnni-idb. (In the display for dsppnni-idb, the child node index is the local node number.)
The uplink node or upnode is the node at the upper end of the uplink. It is the neighboring peer of the ancestor of the node from which the uplink originates.
The extent of the dsppnni-inducing-uplink display depends on whether you specify an individual logical node in the hierarchy, as follows:
•
•
Cards on Which This Command Runs
PXM45
Syntax
dsppnni-inducing-uplink [node-index]Syntax Description
Related Commands
None
Attributes
Example
Display the inducing uplink for the level whose node index is 2.
mpgses3.2.PXM.a > dsppnni-inducing-uplink 2node index:2Token................ 0 Child node portId.... 66560Child node number.... 1Upnode id.............32:56:47.009181001100000000000001.003071f80e56.00Upnode ATM addr.......47.009181000000003071f80e56.003071f80e56.02Upnode PG id..........32:47.00.9181.0000.0000.0000.0000.00CBR RTVBR NRTVBR ABR UBR------ ------ ------ ------ ------AW 10000 10000 10000 10000 10000MaxCR 348207 348207 348207 348207 348207AvCR 347419 347419 347419 347419 347419CTD 17 17 17 17 17CDV 4167 52954 52954 104912 104912CLR0 8 8 8 8 8CLR0+1 8 8 8 8 8dsppnni-intf
Display PNNI Interface—display the PNNI aggregation token and AW for a port.
This command displays the following information for a PNNI port:
•
•
•
Cards on Which This Command Runs
PXM45
Syntax
dsppnni-intf <portid>Syntax Description
portid
The portid is the PNNI physical port. The format is [shelf.]slot[:subslot].port[:subport]. See also PNNI Format.
Default: none
Display Contents
The following parameters are displayed for each node. The right column shows the label for each value that appears in the dsppnni-intf command. The left column maps each value to the corresponding keyword in the cnfpnni-intf command and explains the argument function.
Physical port Id
Display the physical PNNI identifier on the interface. The portid variable is entered and displayed as a numeric string formatted as [shelf.]slot[:subslot].port[:subport]. For more details including the ranges, see PNNI Format.
Logical port Id
Display the logical PNNI port identifier. The -portId parameter displays the logical PNNI port identifier on the interface.
Range: 1-2147483648.
Aggr token
Display the 32 bit number used for link aggregation purpose.
AW-NRTVBR
Display the AW for non-real-time variable bit rate (nrtvbr) connections on this interface. nrtvbr accounts for the bursty traffic that is caused by some non-real-time applications. This category is characterized in terms of a PCR, SCR, and MBS.
Range: 0-4194304
AW-CBR
Display the AW for constant bit rate (CBR) connections on this interface. While a cbr connection is active, this option limits its bit rate to a static value that remains available until the connection is torn down. The bit rate is characterized by the peak cell rate (PCR) value.
Range: 0-4194304
AW-ABR
Display the AW for available bit rate (ABR) connections on this interface. While an ABR connection is active, that connection changes its permitted bit rate (bandwidth) in response to ATM layer transfer characteristics. PNNI periodically polls for the unused bandwidth at the ATM level, then adjusts the ABR connection bit rate in direct relation to the available bandwidth.
Displays the 24 bit number AW for ABR on this interface.Range: 0-4194304
AW-RTVBR
Display the AW for real-time variable bit rate (rt-vbr) connections on this interface. rtvbr is intended for real-time applications requiring tightly constrained delay and delay variation (voice/video applications). rtvbr is characterized by peak cell rate (PCR), sustainable cell rate (SCR), and maximum burst size (MBS).
Range: 0-4194304
AW-UBR
Display the AW (QoS) used for unspecified bit rate (UBR) connections—this includes switched virtual connection (SVC) ping connections.
While a UBR connection is active, this option limits only the maximum bit-rate (bandwidth) of the connection—no bit rate is guaranteed.Range: 0-4194304
Display Contents
PNNI includes a topology state routing protocol, which advertises detailed information about the peer groups links and nodes. Links and nodes are assigned metrics and attributes that can be used to diagnose or tune network behavior.
The administrative weight (AW) is the cost to traffic that traverses a port. The AW for a path is the sum, in both directions, of the individual AWs the egress of each port on the path.
The AW can be specified on the interface and by the service class (or QoS class), and it is associated with each port. AW is a defining factor when routes are selected. The AW parameters influence how PNNI selects paths in the peer group and therefore how it distributes each SVC and SPVC. PNNI route selection can also key on AW to exclude certain links from routing. The application of such exclusion can be to defining a backup link for use only when no bandwidth is available on the primary link.
Related Commands
cnfpnni-intf
Attributes
Example
Display the interface configuration for port 4:1.1:11. The current release does not support the link aggregation parameter (displayed as "Aggr token"), so it appears as a 0.
SanJose.7.PXM.a > dsppnni-intf 4:1.1:11Physical port id: 4: 1.1:11 Logical port id: 17045515Aggr token.......... 0 AW-NRTVBR........... 5040AW-CBR.............. 5040 AW-ABR.............. 5040AW-RTVBR............ 5040 AW-UBR.............. 5040SanJose.7.PXM.a >dsppnni-link
Display PNNI Link Table-display the values of the PNNI link table.
The dsppnni-link command displays the parameters of all PNNI links.
•
•
•
Cards on Which This Command Runs
PXM45
Syntax
dsppnni-link[node-index [port-id]]Syntax Description
node-index
A system-generated value that corresponds to a logical node in an MPG hierarchy. For every PNNI node that you add through CWM or the addpnni-node command, the system associates the next available integer in the range 1-10.
Note
Range: 1-10
portID
The portid is the PNNI physical port. The format is [shelf.]slot[:subslot].port[:subport]. See also PNNI Format.
Display Contents
The dsppnni-link command displays the address, link, and Hello packet information of each link. In a multi-peer group, it also displays the upnode ATM address and node ID. For an explanation of upnode, see the description of dsppnni-inducing-uplink.
Related Commands
Attributes
Example
Specify node index 1 and port 1:1.2:2.
p2spvc5.7.PXM.a > dsppnni-link 1 1:1.2:2node index :1Local port id: 16848898 Remote port id: 16848898Local Phy Port Id:1:1.2:2Type. lowestLevelHorizontalLink Hello state....... twoWayInsideDerive agg........... 0 Intf index........... 16848898SVC RCC index........ 0 Hello pkt RX......... 2Hello pkt TX......... 2Remote node name.......p2spvc6Remote nodeid.........56:160:47.00918100000000309409f1ef.00309409f1ef.01Upnodeid..............0:0:00.000000000000000000000000.000000000000.00Upnode ATM addr........00.000000000000000000000000.000000000000.00Common peer group id...00:00.00.0000.0000.0000.0000.0000.00dsppnni-link-selection
Display PNNI Link Selection—display the PNNI link setting, physical port identifier, and logical port identifier.
The dsppnni-link-selection command displays the link selection and both the physical and logical identifiers for that link. Refer to the description of cnfpnni-link-selection for information about the criteria PNNI uses to choose between two parallel links.
Cards on Which This Command Runs
PXM45
Syntax
dsppnni-link-selection <portid>Syntax Description
portid
The PNNI physical port identifier. portid is entered and displayed as a 32-bit string formatted as [shelf.]slot[:subslot].port[:subport]. For more details, see PNNI Format.
Display Contents
The display shows the following information for each node.
physical port id
The portid is the PNNI physical port. The format is [shelf.]slot[:subslot].port[:subport]. See also PNNI Format.
link selection
The ASCII string displaying the link routing policy.
logical port id
The PNNI port identifier in the form of a logical number.
Range: 1-2147483648
Related Commands
dsppnni-link
Attributes
Example
Displays the link selection for a parallel link on port 4:1.1:11. This link uses the default of minaw. Note that the display also shows the logical port number for the physical port ID.
SanJose.7.PXM.a > dsppnni-link-selection 4:1.1:11physical port id: 4:1.1:11 link selection: minawlogical port id: 17045515SanJose.7.PXM.a >dsppnni-mtu
Display PNNI Maximum Transfer Unit—display maximum supported size of the PNNI data packet.
The dsppnni-mtu command displays the maximum PNNI packet size in number of bytes. This command is primarily for configuring internetwork compatibility, but you can use it in lab trials to test the affect of various packet sizes on the performance of the peer group.
Use cnfpnni-mtu to specify the PNNI packet size configuration.
Cards on Which This Command Runs
PXM45
Syntax
dsppnni-mtuDisplay Contents
The following parameters are displayed for each node. The right column shows the label for each value that appears in the dsppnni-mtu command. The left column maps each value to the corresponding keyword in the cnfpnni-mtu command, and explains the argument function.
Related Commands
dsppnni-idb, cnfpnni-mtu
Attributes
Example
Displays the maximum packet size.
SanJose.7.PXM.a > cnfpnni-mtu 3002SanJose.7.PXM.a > dsppnni-mtumax packet size : 3002SanJose.7.PXM.a >dsppnni-neighbor
Display PNNI Neighbor—display all PNNI nodes that directly connect to this node.
The dsppnni-neighbor command displays all the PNNI nodes that are directly connected to the switch.
•
•
Cards on Which This Command Runs
PXM45
Syntax
dsppnni-neighbor[node-index [rmt-node-id]]Syntax Description
Note that the optional parameters are nested.
Display Contents
The following parameters are displayed for each node.
Related Commands
None
Attributes
Example
Display information about all neighboring PNNI nodes (with no optional parameters).
Geneva.7.PXM.a > dsppnni-neighbornode index : 1node name : ParisRemote node id: 56:160:47.00918100000000107b65f27c.00107b65f27c.01Neighbor state: FULLPort count.......... 4 SVC RCC index....... 0RX DS pkts.......... 3 TX DS pkts.......... 3RX PTSP pkts........ 6032 TX PTSP pkts........ 2061RX PTSE req pkts.... 2 TX PTSE req pkts.... 1RX PTSE ack pkts.... 345 TX PTSE ack pkts.... 2282node index : 2node name : SanJoseRemote node id: 56:160:47.00918100000000309409f1f1.00309409f1f1.01Neighbor state: FULLPort count.......... 2 SVC RCC index....... 0RX DS pkts.......... 4 TX DS pkts.......... 3RX PTSP pkts........ 23107 TX PTSP pkts........ 32978RX PTSE req pkts.... 3 TX PTSE req pkts.... 0RX PTSE ack pkts.... 13673 TX PTSE ack pkts.... 12532Geneva.7.PXM.a >dsppnni-node
Display PNNI Node—display the PNNI node information address and routing information.
The dsppnni-node command displays the PNNI logical node information on the local switch. If you do not provide an index number, the output shows all logical nodes on the switch. However, in the current release, the display always shows only one logical node—with index number 1.
Cards on Which This Command Runs
PXM45
Syntax
dsppnni-node[node-index]Syntax Description
Related Commands
addpnni-node, cnfpnni-node
Attributes
Display Contents
Cisco factory-set defaults for address prefixes and the peer group ID share field-values with the ATM address. (See Figure 5-7.)
Figure 5-7 Cisco Factory-shipped Defaults for PNNI Peer Group Identifier, PNNI Summary Address, ATM Address, and PNNI Node Identifier
The following parameters are displayed for each node. The right column shows the label for each value that appears in the dsppnni-node command. The left column maps each value to the corresponding keyword in the cnfpnni-node command, and explains the argument function.
node index
The node-index is a numeric node identifier assigned by the software—it is not user-configurable.
Range: 1-10
In the current release, the only node-index is "1," so the display always shows "1."
node name
Display the PNNI node name assigned to a PNNI node. Each node name must be unique in the peer group-choose names that all fit into an obviously similar group, for example: names of states, names of universities, and such.
Level
Display the PNNI hierarchical level by defining the length of the pg-id value. For example, the default values 56 indicates that the pgId value extends 56 bits from the leftmost bit. Therefore, pg-id = 47 01 00 8100 0000. If you specify the value of level to 40, pg-id = 47 01 00 8100.
Lowest
This field indicates whether the node is the lowest logical node on the switch. In a single-peer group, "Lowest" is always true. In a multi-peer group, it can be true or false.
Restricted transit
Display the flag that indicates whether transit is restricted across this node. This value can be set to off to secure the node, or to minimize traffic handled by the node if it is of either low-capacity or high-criticality.
on: Calls can transit across this node.
off: Only calls terminating on end-systems supported by this node can access this node.Complex node
Indicates whether this node is a complex node. A node at the lowest level cannot be a complex node. Therefore, in the current release, this field always contains "off."
on: This node is a complex node.
off: This node is not a complex node.Branching restricted
Indicates whether the node supports point-to-multipoint branching.
on: This node does not support point-to-multipoint branching.
off: This node supports point-to-multipoint branches.Admin status
Display the administrative status of the node. You can disable or enable a node by executing the cnfpnni-node command with appropriate parameters.
up: The logical PNNI node is enabled.
down: The logical PNNI node is disabled.Operational status
Display the operational status of the node. The software determines the operational state, so you cannot configure it.
Non-transit for PGL election
Display whether transit is restricted across this node. This value is set by the software and is not user-configurable.
on: Only calls that terminate on this node can access this node.
off: Calls can transit this node.Node id
For the constituents of the node ID, see the description of addpnni-node or cnfpnni-node. Before you change the node ID, you must disable the node by entering cnfpnni-node -enable false. See description of cnfpnni-node.
ATM address
For the constituents of the ATM address, see the description of addpnni-node or cnfpnni-node. Before you change the ATM address, disable the nod by executing cnfpnni-node -enable false. See description of cnfpnni-node
Peer group id
Display the -pgId of length level that is assigned to the PNNI node. The peer group is the PNNI local group.The peer group consists of all PNNI nodes with matching pg-id values.
The default value of level is 56 (7 bytes), which specifies the length of -pgId to 7 bytes. However, the maximum length of -pgId is 14 bytes, so display commands always display -pgId as 14 bytes with trailing zeros filling the undefined fields. If you increase the value of level, you change the length, and therefore the value, of -pgId, but it will always be displayed as 14 bytes.
This is a 14-byte, formatted hexadecimal string. Like all PNNI addresses, identifiers, and prefixes, this value is portrayed as a string of hexadecimal "nibbles." One or several pairs of nibbles entail each parameter field. (See Figure 5-7.)
Example
Display details about the current node. This example reflects a node in a single-peer group.
SanJose.7.PXM.a > dsppnni-node 1node index: 1 node name: SanJoseLevel............... 56 Lowest.............. trueRestricted transit.. off Complex node........ offBranching restricted onAdmin status........ up Operational status.. upNon-transit for PGL election.. offNode id...............56:160:47.00918100000000309409f1f1.00309409f1f1.01ATM address...........47.00918100000000309409f1f1.00309409f1f1.01Peer group id.........56:47.00.9181.0000.0000.0000.0000.00SanJose.7.PXM.a >dsppnni-node-list
Display PNNI Nodes List—display a list of all learned PNNI nodes in the network.
The dsppnni-node-list command lists the PNNI nodes in the network that are visible to the current switch. For a single-peer group (SPG), the displayed nodes exist at one level. For a multi-peer group (MPG), the list contains all nodes on the current switch and all nodes that are visible to every node on the current switch. The display for an MPG shows an ascending order of nodes based on the node number. From the node list, you can create a graphical representation of the network. The display contains the following information for each node:
•
•
•
•
•
Note
Cards on Which This Command Runs
PXM45
Syntax
dsppnni-node-listSyntax Description
This command takes no parameters.
Related Commands
addpnni-node, cnfpnni-node, cnfname, dsppnni-path, dsppnni-reachable-addr
Attributes
Display Contents for the dsppnni-node-list Command
This section describes the contents of a node list. For a multi-peer group (not applicable in the current release), it also describes how the display changes from one level of a hierarchy to a higher level. Although the description relates primarily to the example of a multi-peer network diagram in Figure 5-8, the information also substantially applies to the example SPG that follows the MPG example. The diagram in Figure 5-8 reflects the MPG display in the Example section.
node #
The node number (node #) is a reference to the nodes in the network—not a node in the hierarchy of an MPG on a switch (see the dsppnni-node description for details about node index). The entity that has this view and compiles this list of node numbers is a local logical node. The node numbers have a range of 1-256. Node # 1 is the logical node that is making its list of network nodes. In an MPG list, multiple instances of node # 1 appear because the logical node at each level sees itself as node # 1. Also, each node in a multi-peer group has information for nodes in its peer group but also for all nodes on the level of its parent, grandparent, and so on. See Figure 5-8 and the Example section.
Whether a node belongs to a single-peer group or a multi-peer group, each logical node increments node # by 1 according to the sequence that it discovers other nodes. The paragraphs that follow this list give more details about the node number sequence for a multi-peer group.
You can only view a node number in applicable displays or provide it as a command parameter. For example, you can provide a node number to the dsppnni-path command.
node id
The node-id consists of the level, the length of the ATM address, and the ATM address itself.
node name
The name of the switch (not the name of a logical node). The root of this node name results from the cnfname command. If a dash number follows the node number, that number is the node index that pertains to the hierarchy of nodes on the switch. For this command, a number is appended only for nodes above the lowest level on the switch.
level
The level is set through addpnni-node or cnfpnni-node. It has a range of 1-104 and a default of 56.
The paragraphs that follow describe the progression in node numbers, levels, and the node index appended to the switch name in an MPG network.Refer to Figure 5-8.
1.
The numbers in the "node #" column begin with 1—which is the local node itself—then continues with the next learned node, and so on. The node# increases by 1 with each discovered node.2.
3.
Figure 5-8 Multi-Peer Group
Example of MPG
Display all network nodes that are known to the logical nodes on the current switch. This multi-per group is the basis of Figure 5-8. In fact, Figure 5-8 was constructed from this list. Note that node # 2 has been either disabled or deleted from the network.
The first graphical representation in this example is Figure 5-9. It illustrates where the view of a particular level begins and ends. As Figure 5-9 shows, the number of nodes visible at each higher level decreases. After acquiring a visual grasp of the dsppnni-node-list display, the screen capture that follows Figure 5-9 provides a more readable list to examine.
The first series of node numbers is node # 1 through node # 6 and is the list complied by the lowest level node. As reflected in Figure 5-8, mpglax1 is the only node in its peer group, so the first series shows only one node at level 56. The remainder of the nodes in the first series are the members at the level of its parent and grandparent, as Figure 5-8 illustrates. At the levels other than the lowest, the node index is appended to the switch name.
For the switch named mpglax4, only levels 56 and 40 were configured. Therefore, the display shows the last node name at level 40 of "mpglax4-02."
Figure 5-9 A List of Nodes in a Multi-Peer Group
mpglax1.1.PXM.a > dsppnni-node-listnode # node id node name level------- -------------------------------------------------- ---------- -------1 56:160:47.009181000000003071f80e4a.003071f80e4a.01 mpglax1 56node # node id node name level------- -------------------------------------------------- ---------- -------3 48:56:47.339181000000000000000000.003071f80833.00 mpglax1-02 48node # node id node name level------- -------------------------------------------------- ---------- -------4 40:56:47.229181000000000000000000.003071f80e52.00 mpglax4-02 40node # node id node name level------- -------------------------------------------------- ---------- -------5 40:48:47.559181000100000000000000.003071f80833.00 mpglax1-03 40node # node id node name level------- -------------------------------------------------- ---------- -------6 48:56:47.119181000000000000000000.003071f80e56.00 mpglax2-02 48node # node id node name level------- -------------------------------------------------- ---------- -------1 48:56:47.339181000000000000000000.003071f80833.00 mpglax1-02 48node # node id node name level------- -------------------------------------------------- ---------- -------2 40:48:47.559181000100000000000000.003071f80833.00 mpglax1-03 40node # node id node name level------- -------------------------------------------------- ---------- -------3 48:56:47.119181000000000000000000.003071f80e56.00 mpglax2-02 48node # node id node name level------- -------------------------------------------------- ---------- -------4 40:56:47.229181000000000000000000.003071f80e52.00 mpglax4-02 40node # node id node name level------- -------------------------------------------------- ---------- -------1 40:48:47.559181000100000000000000.003071f80833.00 mpglax1-03 40node # node id node name level------- -------------------------------------------------- ---------- -------3 40:56:47.229181000000000000000000.003071f80e52.00 mpglax4-02 40mpglax1.1.PXM.a >Example of SPG
Display the node list for a single-peer group. Note that the level for each node is 56.
Geneva.7.PXM.a > dsppnni-node-listnode # node id node name level------- -------------------------------------------------- ---------- -------1 56:160:47.009181000000001029300121.001029300121.01 pswpop6 56node # node id node name level------- -------------------------------------------------- ---------- -------2 56:160:47.00918100000000c043002de1.00c043002de1.01 pswpop7 56node # node id node name level------- -------------------------------------------------- ---------- -------3 56:160:47.009181000000000000000000.001029300121.00 pswpop6-02 56node # node id node name level------- -------------------------------------------------- ---------- -------4 56:160:47.00918100000000500ffde80b.00500ffde80b.01 orses18 56Geneva.7.PXM.a >dsppnni-path
Display PNNI Path—display the pre-computed path tables.
The dsppnni-path command displays the pre-computed paths between the source (the current node) and the destination nodes. The system has determined these paths to be the best or optimal paths for various service classes according to one of three metrics. These metrics are the administrative weight (AW), the cell transfer delay (CTD), or the cell delay variation (CDV). The service class that each metric supports for the purpose of routing varies. For a list of metrics and service classes, see Table 5-3. For dsppnni-path, you must specify a combinations of routing metric and service class.
Table 5-3 Routing Criteria and Service Classes
AW
CBR, ABR, UBR, rt-VBR, nrt-VBR
CTD
CBR, rt-VBR, nrt-VBR
CDV
CBR, rt-VBR
You can also specify a node index. If you specify a node-index, the command displays the paths from the source node to the node whose index you specify. To see a list of node indexes, execute dsppnni-node-list. (The dsppnni-node-list command displays network-level node indexes under the heading "node #.")
Cards on Which This Command Runs
PXM45
Syntax
dsppnni-path {aw {cbr|rtvbr|nrtvbr|ubr|abr} | ctd {cbr|rtvbr|nrtvbr} | cdv {cbr|rtbvr}}[node-index]Syntax Description
Note
Note
Display Contents
Related Commands
None
Attributes
Examples
The routing criteria for both examples is UBR service with routing metric AW. First, display the pre-computed paths between the current source and the node with index number 5. Thereafter, enter dsppnni-path but do not include an index number so the display shows all paths.
SanJose.7.PXM.a > dsppnni-path aw ubr 5node #/PortId node id node name--------------- -------------------------------------------------- ----------D 5/ 0 56:160:47.00918100000000309409f160.00309409f160.01 ChicagoS 1/ 17045505 56:160:47.00918100000000309409f1f1.00309409f1f1.01 SanJosenode #/PortId node id node name--------------- -------------------------------------------------- ----------D 5/ 0 56:160:47.00918100000000309409f160.00309409f160.01 ChicagoS 1/ 17045506 56:160:47.00918100000000309409f1f1.00309409f1f1.01 SanJosenode #/PortId node id node name--------------- -------------------------------------------------- ----------D 5/ 0 56:160:47.00918100000000309409f160.00309409f160.01 ChicagoS 1/ 17045507 56:160:47.00918100000000309409f1f1.00309409f1f1.01 SanJosenode #/PortId node id node name--------------- -------------------------------------------------- ----------D 5/ 0 56:160:47.00918100000000309409f160.00309409f160.01 ChicagoS 1/ 17045508 56:160:47.00918100000000309409f1f1.00309409f1f1.01 SanJoseThe example for all paths in the network with AW as the routing metric and UBR as the service class, the display is very large and so is truncated. Note that this display shows multiple paths to the source.
SanJose.7.PXM.a > dsppnni-path aw ubrnode #/PortId node id node name--------------- -------------------------------------------------- ----------D 2/ 0 56:160:47.00918100000000309409f2aa.00309409f2aa.01 TorotonS 1/ 17504257 56:160:47.00918100000000309409f1f1.00309409f1f1.01 SanJosenode #/PortId node id node name--------------- -------------------------------------------------- ----------D 3/ 0 56:160:47.00918100000000301a431c19.00301a431c19.01 Boston2/ 17176577 56:160:47.00918100000000309409f2aa.00309409f2aa.01 TorotonS 1/ 17504257 56:160:47.00918100000000309409f1f1.00309409f1f1.01 SanJosenode #/PortId node id node name--------------- -------------------------------------------------- ----------D 3/ 0 56:160:47.00918100000000301a431c19.00301a431c19.01 Boston2/ 17438721 56:160:47.00918100000000309409f2aa.00309409f2aa.01 TorotonS 1/ 17504257 56:160:47.00918100000000309409f1f1.00309409f1f1.01 SanJosenode #/PortId node id node name--------------- -------------------------------------------------- ----------D 4/ 0 56:160:47.00918100000000309409f23c.00309409f23c.01 London3/ 17111041 56:160:47.00918100000000301a431c19.00301a431c19.01 Boston2/ 17438721 56:160:47.00918100000000309409f2aa.00309409f2aa.01 TorotonS 1/ 17504257 56:160:47.00918100000000309409f1f1.00309409f1f1.01 SanJosenode #/PortId node id node name--------------- -------------------------------------------------- ----------D 4/ 0 56:160:47.00918100000000309409f23c.00309409f23c.01 London3/ 16848897 56:160:47.00918100000000301a431c19.00301a431c19.01 Boston2/ 17176577 56:160:47.00918100000000309409f2aa.00309409f2aa.01 TorotonS 1/ 17504257 56:160:47.00918100000000309409f1f1.00309409f1f1.01 SanJosenode #/PortId node id node name--------------- -------------------------------------------------- ----------D 4/ 0 56:160:47.00918100000000309409f23c.00309409f23c.01 London3/ 16848897 56:160:47.00918100000000301a431c19.00301a431c19.01 Boston2/ 17438721 56:160:47.00918100000000309409f2aa.00309409f2aa.01 TorotonS 1/ 17504257 56:160:47.00918100000000309409f1f1.00309409f1f1.01 SanJosenode #/PortId node id node name--------------- -------------------------------------------------- ----------D 5/ 0 56:160:47.00918100000000309409f160.00309409f160.01 ChicagoS 1/ 17045505 56:160:47.00918100000000309409f1f1.00309409f1f1.01 SanJosenode #/PortId node id node name--------------- -------------------------------------------------- ----------D 5/ 0 56:160:47.00918100000000309409f160.00309409f160.01 ChicagoS 1/ 17045506 56:160:47.00918100000000309409f1f1.00309409f1f1.01 SanJosenode #/PortId node id node name--------------- -------------------------------------------------- ----------D 5/ 0 56:160:47.00918100000000309409f160.00309409f160.01 ChicagoS 1/ 17045507 56:160:47.00918100000000309409f1f1.00309409f1f1.01 SanJosenode #/PortId node id node name--------------- -------------------------------------------------- ----------D 5/ 0 56:160:47.00918100000000309409f160.00309409f160.01 ChicagoS 1/ 17045508 56:160:47.00918100000000309409f1f1.00309409f1f1.01 SanJosenode #/PortId node id node name--------------- -------------------------------------------------- ----------D 6/ 0 56:160:47.00918100000000309409f2a3.00309409f2a3.01 Paris4/ 17438721 56:160:47.00918100000000309409f23c.00309409f23c.01 London3/ 17111041 56:160:47.00918100000000301a431c19.00301a431c19.01 Boston2/ 17176577 56:160:47.00918100000000309409f2aa.00309409f2aa.01 TorotonS 1/ 17504257 56:160:47.00918100000000309409f1f1.00309409f1f1.01 SanJosenode #/PortId node id node name--------------- -------------------------------------------------- ----------D 6/ 0 56:160:47.00918100000000309409f2a3.00309409f2a3.01 Paris4/ 17438721 56:160:47.00918100000000309409f23c.00309409f23c.01 London3/ 17111041 56:160:47.00918100000000301a431c19.00301a431c19.01 Boston2/ 17438721 56:160:47.00918100000000309409f2aa.00309409f2aa.01 TorotonS 1/ 17504257 56:160:47.00918100000000309409f1f1.00309409f1f1.01 SanJosenode #/PortId node id node name--------------- -------------------------------------------------- ----------D 6/ 0 56:160:47.00918100000000309409f2a3.00309409f2a3.01 Paris4/ 17438721 56:160:47.00918100000000309409f23c.00309409f23c.01 London3/ 16848897 56:160:47.00918100000000301a431c19.00301a431c19.01 Boston2/ 17176577 56:160:47.00918100000000309409f2aa.00309409f2aa.01 TorotonS 1/ 17504257 56:160:47.00918100000000309409f1f1.00309409f1f1.01 SanJosenode #/PortId node id node name--------------- -------------------------------------------------- ----------D 6/ 0 56:160:47.00918100000000309409f2a3.00309409f2a3.01 Paris4/ 17438721 56:160:47.00918100000000309409f23c.00309409f23c.01 London3/ 16848897 56:160:47.00918100000000301a431c19.00301a431c19.01 Boston2/ 17438721 56:160:47.00918100000000309409f2aa.00309409f2aa.01 TorotonS 1/ 17504257 56:160:47.00918100000000309409f1f1.00309409f1f1.01 SanJosenode #/PortId node id node name--------------- -------------------------------------------------- ----------D 7/ 0 56:160:47.00918100000000001a531c01.00001a531c01.01 LA11/ 16848918 56:160:47.00918100000000001a531c83.00001a531c83.01 Jup-13/ 16848917 56:160:47.00918100000000301a431c19.00301a431c19.01 Boston2/ 17176577 56:160:47.00918100000000309409f2aa.00309409f2aa.01 TorotonS 1/ 17504257 56:160:47.00918100000000309409f1f1.00309409f1f1.01 SanJosenode #/PortId node id node name--------------- -------------------------------------------------- ----------D 7/ 0 56:160:47.00918100000000001a531c01.00001a531c01.01 LA11/ 16848918 56:160:47.00918100000000001a531c83.00001a531c83.01 Jup-13/ 16848917 56:160:47.00918100000000301a431c19.00301a431c19.01 Boston2/ 17438721 56:160:47.00918100000000309409f2aa.00309409f2aa.01 TorotonS 1/ 17504257 56:160:47.00918100000000309409f1f1.00309409f1f1.01 SanJosenode #/PortId node id node name--------------- -------------------------------------------------- ----------D 8/ 0 56:160:47.00918100000000309409f213.00309409f213.01 A4b7/ 16848897 56:160:47.00918100000000001a531c01.00001a531c01.01 LA11/ 16848918 56:160:47.00918100000000001a531c83.00001a531c83.01 Jup-13/ 16848917 56:160:47.00918100000000301a431c19.00301a431c19.01 Boston2/ 17176577 56:160:47.00918100000000309409f2aa.00309409f2aa.01 TorotonS 1/ 17504257 56:160:47.00918100000000309409f1f1.00309409f1f1.01 SanJoseSanJose.7.PXM.a >dsppnni-pkttrace
Display Packet Trace—display the parameters of a particular packet trace configuration.
This command applies to debugging only.
The dsppnni-pkttrace command displays the packet-trace settings. These settings are configured by the cnfpnni-pkttrace command. You can use a packet trace to examine the contents of the PNNI Hello packets that are exchanged between two neighboring peers.
Note
Cards on Which This Command Runs
PXM45
Syntax
dsppnni-pkttrace <rx | tx>[node-index [ -portId port-id | -svcIndex svc-index]]Syntax Description
Related Commands
cnfpnni-pkttrace
Attributes
Example
First, configure the following packet trace parameters through cnfpnni-pkttrace:
•
•
•
Next, check the packet trace you have configure by executing dsppnni-pkttrace.
Geneva.7.PXM.a > cnfpnni-pkttrace -tx 17373186PNNI/tx_packet on port 17373186 at level 56> 01:00010064 01010100 000038a0 47009181 00000000 309409f3 b8003094> 02:09f3b801 47009181 00000000 309409f3 b8003094 09f3b801 38470091> 03:81000000 00000000 000038a0 47009181 00000000 001a531c 2a00001a...Geneva.7.PXM.a > dsppnni-pkttrace tx 1 -portId 17373186Node Index :1 Port id: 17504 Tx Pkt Trace onGeneva.7.PXM.a >dsppnni-ptse
Display PNNI topology state element—displays PTSE tables.
The dsppnni-ptse command displays PNNI topology state elements (PTSEs). The purpose of this command is troubleshooting, and it requires familiarity with the ATM Forum PNNI 1.0 specification. Without knowledge of this specification, the usefulness of dsppnni-ptse is minimal.
PTSE Types
A node indicates its characteristics (such as all its ATM addresses) to all other nodes in the peer group by broadcasting numerous PTSEs. A node periodically sends (or floods the group with) PTSEs according to a user-specified timer but also floods the group with PTSEs when it triggers a change of topology. A typical topology change is an addition of an ATM address.
Each PTSE carries an indicator of what type of PTSE it is. This PTSE type appears as both a descriptive string and a number set by the ATM Forum. The section, "Display Contents for dsppnni-ptse" lists the contents of each information group identified by the PTSE type. Five basic types exist, and various subtypes exist. The basic types of PTSEs are:
1.
2.
3.
4.
5.
Granularity of the Output
The optional parameters let you determine the granularity of the target of the command. The granularity ranges from the whole peer group to a specific logical port. Additionally, you can specify a "detailed" display or just the header information for PTSEs.
If you specify:
•
•
•
•
Note
The ptse-id is generated by the node that sends the PTSE.You can use dsppnni-ptse to trouble-shoot a faulty designated transit list (DTL). If a DTL is faulty, you can observe the PTSE of nodes on the designated path to confirm the accuracy of the information used to build the DTL. You can also use dsppnni-ptse to determine if nodes are correctly passing both the topology packets and the Hello packets.
Cards on Which This Command Runs
PXM45
Syntax
dsppnni-ptse[node-index [node-id [ptse-id]]][-detail {true | false}]Syntax Description
Note
Display Contents for dsppnni-ptse
This section describes basic information for each PTSE type. In addition, each variation of the command output contains the following header information.
node-index
This unique, network-wide node identifier is a switch-generated number in the range 1-256. If the network consists of a multi-peer group, the display shows the sequence of node numbers for the lowest level then starts the sequence at the next level.
originating node ID
The identifier of the node that broadcast the PTSE.
PTSE ID
The unique identifier of the PTSE. ptse-id is a 32 bit number index assigned by the PNNI node that created the PTSE.
PTSE type
The type of PTSE is an ASCII designated by the ATM forum PNNI standard. Broad and narrow categories.
internal reachable ATM addresses
A list of reachable ATM addresses that are inside the peer group or network.
exterior reachable ATM addresses
A list of reachable ATM addresses that are outside the network. The current release does not support exterior addresses.
PTSE length
The number of bytes in the PTSE—a 16-bit number.
sequence
The sequence of the PTSE—a 32-bit number.
checksum
The checksum error-checking value. A 16-bit hex number.
remaining lifetime
The length of the remaining lifetime (in seconds). 32-bit number.
details for IG
The flag that determines the level of details for information group (IG) if the detail option is enabled ("true").
Note
type
The type of nodal information group (IG).
length
The length of the nodal IG PTSE. A 16-bit number.
ATM address
The upnode ATM address is a 20-byte, hexadecimal string. The upnode is the node at the other end of the uplink. It is the neighboring peer of the ancestor of the node from which the uplink originates.
priority
The value of the priority parameter, an 8-bit number.
nodal flags
The 8-bit nodal flags.
preferred PGL
A 22-byte hex string. The current release does not support peer group leader (PGL).
next higher level binding information IG type
The next higher level binding information IG type is an ASCII string. The current release does not support higher level binding.
next higher level binding information IG length
A 16-bit number.
The current release does not support higher level binding.parent LGN id
The parent LGN ID is a 22-byte hex string. The current release does not support logical group numbers (LGNs).
parent LGN ATM address
The parent LGN ATM address is a 20-byte, hex string. The current release does not support group numbers (LGNs).
parent PG id
The peer group ID (of length level) assigned to the parent PG. The peer group is the PNNI local group. The peer group consists of all PNNI nodes with matching -pgId values. The current release does not support parent peer groups.
Default: Figure 5-1 shows the factory-set default.
parent peer group PGL
The parent peer group PGL identifier is a 22-byte hexadecimal string.
The current release does not support PGL.type
The ASCII string that indicates the type of the IG nodal state parameters.
length
A 16-bit number.
flags
A string of 8-bit flags.
input port id
The logical identifier on the input interface. For more details, see PNNI Format.
Range: 1-2147483648
output port id
The logical PNNI identifier on the output interface. For more details, see PNNI Format.
Range: 1-2147483648
type
The ASCII string that indicates the type of the internal reachable ATM address IG parameters.
length
A 16-bit number.
flags
A string of 8-bit flags.
port id
The logical PNNI identifier on the interface. For more details, see PNNI Format.
Range: 1-2147483648
scope
The UNI 4.0 address scope.
Note
address info length
The length of the address information—an eight-bit number.
address count
The number of reachable addresses—a 16-bit number.
reachable address prefixes
Display any PNNI summary address reachable by the node. The length of addressprefix is set by prefixlength.
Note
type
The ASCII string that indicates the type of the exterior reachable ATM address IG parameters.
length
A 16-bit number.
flags
A string of 8-bit flags.
port id
The logical port number of the PNNI port. This format is a 32-bit number.
Range: 1-2147483648
scope
An 8-bit number.
address info length
An 8-bit number.
The current release does not support exterior reachable addresses.
address count
A 16-bit number.
reachable address prefixes
Display any exterior PNNI summary address reachable by the node. The length of addressprefix is set by prefixlength.
type
The ASCII string that indicates the type of the horizontal link IG parameters.
length
A 16-bit number.
flags
A string of 8-bit flags.
remote node id
The node ID of the remote node. For a description of the node ID, see the description for addpnni-node or cnfpnni-node.
remote port id
The logical PNNI identifier on the remote interface. For more details, see PNNI Format.
Range: 1-2147483648
local port id
The logical PNNI identifier on the local interface. For more details, see PNNI Format.
Range: 1-2147483648
aggregation token
See the description of the cnfpnni-intf command for a definition of an aggregation token. The current release does not support link aggregation.
Range: 1-32
Note
type
The ASCII string that indicates the type of up link IG parameters.
length
A 16-bit number.
flags
A string of 8-bit flags.
remote higher level node id
The PNNI node identifier assigned to a PNNI node.
common pg id
The peer group ID (of length level) that assigned to the PNNI common PG. This peer group is the local peer group.
Default: Figure 5-1 shows the factory-set default.
local port id
The logical PNNI identifier on the interface. For more details, see PNNI Format.
Range: 1-2147483648
aggregation token
Range: 1-2147483648.
upnode ATM address
The ATM address of the PNNI uplink node. The upnode ATM address is a 20-byte, hexadecimal string. The upnode is the node at the other end of the uplink. It is the neighboring peer of the ancestor of the node from which the uplink originates.
Default: none
type
Indication of bi-directional resource availability information group (RAIG)
length
A 16-bit number.
flags
A 16-bit number.
aw
The bandwidth used by AW metric cells in cells per second.
Range: 1-2147483648.
ctd
The bandwidth used by CTD metric cells in cells per second.
Range: 1-2147483648.
cdv
The bandwidth used by CDV metric cells in cells per second.
Range: 1-2147483648.
mcr
The bandwidth used by MCR metric cells in cells per second.
Range: 1-2147483648.
acr
The bandwidth used by ACR metric cells in cells per second.
Range: 1-2147483648.
clr0
The bandwidth used by CLR0 metric cells in cells per second.
Range: 1-2147483648.
clr0+1
The bandwidth used by CLR0+1 metric cells in cells per second.
Range: 1-2147483648.
type
The ASCII string that indicates the type of GCAC IG parameters.
length
A 16-bit number.
crm
The cell rate margin (CRM) is a measure of the difference between the effective bandwidth allocation and the allocation for sustainable cell rate. It is a safety margin allocated above the aggregate sustainable cell rate for nrt-VBR and rt-VBR. This feature has little impact on traffic management.
The ATM Forum does not require support for CRM, and Cisco Systems currently does not support it on the Cisco MGX 8850 and SES products.
Range: 1-2147483648.
vf
The variance factor (VF) is a relative measure of the square of the cell rate margin (CRM) normalized by the variance of the sum of the cell rates of all existing connections. VF applies to nrt-VBR and rt-VBR, but it has little impact on traffic management.
The ATM Forum does not require support for VF, and Cisco Systems currently does not support it on the Cisco MGX 8850 and SES products.
Range: 1-2147483648.
Related Commands
None
Attributes
Examples
For the first example, enter the command with no parameters, so all information about every node on the switch appears.
Geneva.7.PXM.a > dsppnni-ptse -detail truenode index: 1originating node name: Krishnaoriginating node id: 56:160:47.0091810000000000c0326496.0000c0326496.00Type................ 64 Length.............. 1200Sequence number..... 1 Checksum............ 94dPTSE id............. 1 Remaining lifetime.. 2997PTSE type........... Nodal Info( 97)Type................ 97 Length.............. 65Priority............ 0 Flags............... f8ATM addr..............47.0091810000000000c0326496.0000c0326496.00Pref PGL id...........0:0:00.000000000000000000000000.000000000000.00binding info: Type 192, Length 76next level LGN node id. 48:56:47.009181000000000000000000.0000c0326496.00next level LGN ATM addr 47.0091810000000000c0326496.0000c0326496.30next level LGN PG id... 30:47.00.9181.0000.0000.0000.0000.00next level LGN PGL id.. 30:48:56:47.009181000000000000000000.0000c0326496.00node index: 1originating node name: Lizoriginating node id: 56:160:47.0091810000000000c0326496.0000c0326496.00Type................ 64 Length.............. 1200Sequence number..... 1 Checksum............ 94dPTSE id............. 2 Remaining lifetime.. 2997PTSE type........... Nodal State Parameter( 96)Type................ 96 Length.............. 65Reserved............ 0 Flags............... 0Input port id....... 48 Output port id...... 12For the second example, specify the following parameters:
•
•
•
Display the PTSEs for node index 2. After listing the PTSEs, display details for one particular PTSE—19 in this example.
Note
M8850_NY.7.PXM.a > dsppnni-ptse 2node index: 2originating node name: M8850_NY-02originating node id: 48:56:47.009181000002000000000000.00036b5e30cd.00Type................ 64 Length.............. 96Sequence number..... 155 Checksum............ 689bPTSE id............. 1 Remaining lifetime.. 3224PTSE type........... Nodal Info( 97)node index: 2originating node name: M8850_NY-02originating node id: 48:56:47.009181000002000000000000.00036b5e30cd.00Type................ 64 Length.............. 44Sequence number..... 153 Checksum............ d7fdPTSE id............. 18 Remaining lifetime.. 3224PTSE type........... Int Reach Addr(224)node index: 2originating node name: M8850_NY-02originating node id: 48:56:47.009181000002000000000000.00036b5e30cd.00Type................ 64 Length.............. 52Sequence number..... 152 Checksum............ bbaPTSE id............. 19 Remaining lifetime.. 3224PTSE type........... Int Reach Addr(224)As directed at the beginning of this example, display details for PTSE 19.
M8850_NY.7.PXM.a > dsppnni-ptse 2 48:56:4700918100000200000000000000036b5e30cd00 19 -detail truenode index: 2originating node name: M8850_NY-02originating node id: 48:56:47.009181000002000000000000.00036b5e30cd.00Type................ 64 Length.............. 52Sequence number..... 152 Checksum............ bbaPTSE id............. 19 Remaining lifetime.. 2389PTSE type........... Int Reach Addr(224)Type................ 224 Length................ 32Reserved............ 0 Flags................. 8000Port id............. 1 Scope................. 0Ail................. 14 Aic................... 1prefix..............47.0091.8100.0000.0003.6b5e.30cd./104dsppnni-reachable-addr
Display PNNI Reachable Addresses—displays the reachable PNNI addresses in the peer group.
This command displays all the reachable addresses and address prefixes in the peer group. For a description of the items in the display, refer to the section, "Display Contents for dsppnni-reachable-addr." The display granularity depends on your parameter choice:
•
•
Note
Cards on Which This Command Runs
PXM45
Syntax
dsppnni-reachable-addr <local | network>Syntax Description
Display Contents for dsppnni-reachable-addr
The table contains all reachable addresses within a peer group comes from the internal data base (IDB).
Related Commands
dsppnni-link
Attributes
Examples
Display the reachable addresses that directly connect to this node: the parameter is local.
Geneva.7.PXM.a > dsppnni-reachable-addr localscope............... 0 port id.............4294967295Exterior............ falseATM addr prefix.....47.0091.8100.0000.0030.ff0f.ef38.0000.010b.180b/152scope............... 0 port id.............4294967295Exterior............ falseATM addr prefix.....47.0091.8100.0000.0030.ff0f.ef38.0000.010b.1816/152scope............... 0 port id.............4294967295Exterior............ falseATM addr prefix.....47.0091.8100.0000.0030.ff0f.ef38.0000.010b.1820/152scope............... 0 port id.............4294967295Exterior............ falseATM addr prefix.....47.0091.8100.0000.0030.ff0f.ef38.0000.010b.1821/152scope............... 0 port id.............4294967295Exterior............ falseATM addr prefix.....47.0091.8100.0000.0030.ff0f.ef38.0000.010d.1820/152scope............... 0 port id.............4294967295Exterior............ falseATM addr prefix.....47.0091.8100.0000.0030.ff0f.ef38.0000.010d.1821/152scope............... 0 port id.............4294967295Exterior............ falseATM addr prefix.....47.0091.8100.0000.0030.ff0f.ef38.0000.010d.1822/152Display all the addresses and address prefixes that are reachable from this node, and display the routing parameters for each reachable node in each direction.
Geneva.7.PXM.a > dsppnni-reachable-addr networkscope............... 0 Advertising node number 13Exterior............ falseATM addr prefix.....47.0091.8100.0000.0010.7b65.f27c/104Advertising nodeid..56:160:47.00918100000000309409f13f.00309409f13f.01Node name...........Moscowforward directionCBR RTVBR NRTVBR ABR UBR------ ------ ------ ------ ------AW 5040 5040 5040 5040 5040MaxCR 351500 351500 351500 351500 351500AvCR 290935 290935 290935 290935 290935CTD 41 41 41 n/a n/aCDV 10 10 n/a n/a n/aCLR0 10 8 6 n/a n/aCLR0+1 8 8 8 n/a n/aCRM n/a n/a n/a n/a n/aVF n/a n/a n/a n/a n/abackward directionCBR RTVBR NRTVBR ABR UBR------ ------ ------ ------ ------AW 5040 5040 5040 5040 5040MaxCR 351500 351500 351500 351500 351500AvCR 290935 290935 290935 290935 290935CTD 41 41 41 n/a n/aCDV 10 10 n/a n/a n/aCLR0 10 8 6 n/a n/aCLR0+1 8 8 8 n/a n/aCRM n/a n/a n/a n/a n/aVF n/a n/a n/a n/a n/ascope............... 0 Advertising node number 8Exterior............ falseATM addr prefix.....47.0091.8100.0000.0010.7b65.f27c/104Advertising nodeid..56:160:47.00918100000000107b65f27c.00107b65f27c.01Node name...........Parisscope............... 0 Advertising node number 8Exterior............ trueATM addr prefix.....47.0091.8100.0000.0030.9409.f13f/104Advertising nodeid..56:160:47.00918100000000107b65f27c.00107b65f27c.01Node name...........Parisforward directionCBR RTVBR NRTVBR ABR UBR------ ------ ------ ------ ------AW 5040 5040 5040 5040 5040MaxCR 351500 351500 351500 351500 351500AvCR 290935 290935 290935 290935 290935CTD 41 41 41 n/a n/aCDV 10 10 n/a n/a n/aCLR0 10 8 6 n/a n/aCLR0+1 8 8 8 n/a n/aCRM n/a n/a n/a n/a n/aVF n/a n/a n/a n/a n/abackward directionCBR RTVBR NRTVBR ABR UBR------ ------ ------ ------ ------AW 5040 5040 5040 5040 5040MaxCR 351500 351500 351500 351500 351500AvCR 290935 290935 290935 290935 290935CTD 41 41 41 n/a n/aCDV 10 10 n/a n/a n/aCLR0 10 8 6 n/a n/aCLR0+1 8 8 8 n/a n/aCRM n/a n/a n/a n/a n/aVF n/a n/a n/a n/a n/aGeneva.7.PXM.a >dsppnni-routing-policy
Display PNNI Routing Policy—display the PNNI routing policy parameters.
The dsppnni-routing-policy command displays the parameters associated with the current routing policy for this node. The displayed parameters determine:
•
•
•
•
•
Caution
Cards on Which This Command Runs
PXM45
Syntax
dsppnni-routing-policyDisplay Contents
This section lists the displayed information for each node. The display shows the configuration that results from cnfpnni-routing-policy.
Related Commands
cnfpnni-routing-policy
Attributes
Example
Display the parameters associated with the current routing policy for this node.
Geneva.7.PXM.a > dsppnni-routing-policySPT epsilon......... 0 Load balance........ randomSPT holddown time... 1 On demand routing... best fitSPT path holddown time 2 AW Background Table onCTD Background Table on CDV Background Table onGeneva.7.PXM.a >dsppnni-scope-map
Display Scope Map—display the PNNI scope map table.
The dsppnni-scope-map command displays the table that maps UNI 4.0 scope to PNNI hierarchy level.
Note
Cards on Which This Command Runs
PXM45
Syntax
dsppnni-scope-mapObjects Displayed:
Displays the entire scope map table.
Related Commands
cnfpnni-scope-map
Attributes
Example
This command is not supported by the current release.
dsppnni-spoke
Display PNNI Spoke—display the PNNI complex node default advertisement values.
Note
The dsppnni-spoke command displays how the UNI 4.0 address scope values map to the PNNI hierarchal levels. It displays the PNNI default spoke for a logical group node (LGN) using complex node representation in a given peer group (PG). The spoke is the conceptual "radius" of the peer group. The spoke values are based on averaging the administrate weights (AWs) of all border node paths then dividing that average by 2.
If a logical path is not included in the bypass table, the spoke values can be used to select which peer group a route transits. The PG with the lowest spoke AW is the lowest cost PG and therefore the best path to use (based on AW).
Cards on Which This Command Runs
PXM45
Syntax
dsppnni-spoke <node-id>Syntax Description
node-id
The node identifier of a PNNI logical node can be user-assigned by addpnni-node or cnfpnni-node but also comes as a factory-assigned default.
Default: (the factory-set default)
Display Contents
The following parameters are displayed for each node.
Related Commands
None
Attributes
Example
Display the spoke mapping for LGN 56:160:47.00918100000000309409f1f1.00309409f1f1.0.
SanJose.7.PXM.a > dsppnni-spoke 56:160:47.00918100000000309409f1f1.00309409f1f1.0node index: 1Ptse id ............ 948 Flags................ a3Nodal aggregation method.. spanning treeCBR RTVBR NRTVBR ABR UBR------ ------ ------ ------ ------AW 5040 5040 5040 5040 5040MCR 0 0 0 0 0AvCR 100000 100000 100000 100000 100000CTD 0 0 0 0 0CDV 0 0 0 0 0CLR 0 0 0 0 0 0CLR0+1 0 0 0 0 0CRM 10 10 10 10 10VF 5 5 5 5 5dsppnni-summary-addr
Display PNNI Summary Address—display the PNNI summary addresses.
The dsppnni-summary-addr command displays all summary addresses at the specified degree of granularity.
•
•
Use addpnni-summary-addr to create a new summary addresses or to configure an existing one.
Cards on Which This Command Runs
PXM45
Syntax
dsppnni-summary-addr[node-index]Syntax Description
node-index
Specify the system-generated identifier of a logical node within a hierarchy. In the current release, the only node-index is 1.
Range: 1-10.
Default = 1.
Display Contents
Related Commands
addpnni-summary-addr, delpnni-summary-addr
Attributes
Example
Display the PNNI address prefixes. This command line does not specify node-index, so the output contains all PNNI summary addresses in the peer group rather than a specific node. In this case, only a single peer group exists.
Geneva.7.PXM.a > dsppnni-summary-addrnode index: 1Type.............. internal Suppress.............. falseState............. advertisingSummary address........47.0091.8100.0000.0030.ff0f.ef38/104node index: 1Type.............. internal Suppress.............. falseState............. inactiveSummary address........47.0091.8100.0000.0010.7b65.f260/104Geneva.7.PXM.a >dsppnni-svcc-rcc
Display PNNI Switched Virtual Connection Routing Control Channel (SVCC-RCC)—display the PNNI SVC-based RCC table.
The dsppnni-svcc-rcc command displays the SVCC-RCC connection and packet values.
If you specify:
•
•
•
Cards on Which This Command Runs
PXM45
Syntax
dsppnni-svcc-rcc[node-index [svc-index]]Syntax Description
Display Contents
The dsppnni-svcc-rcc command displays node, Hello packet, and SVC information for each RCC.
Related Commands
None
Attributes
Example
This command is not supported by the current release.
This example shows the dsppnni-svcc-rcc command line that displays SVC-based RCCs.
Geneva.7.PXM.a > dsppnni-svcc-rccnode index: 1 svc index: 33Hello pkt RX........ 34 SVCC VPI............ 34Hello pkt TX........ 34 SVCC VCI............ 128Hello state........... 2wayOutsideRemote node id.........56:160:39.840f80113744000000400202.00107b0efe01.00Remote node ATM addr...39:840f.8011.3744.0000.0040.0102.4000.0c80.8030.00node index: 2 svc index: 33Hello pkt RX........ 34 SVCC VPI............ 34Hello pkt TX........ 34 SVCC VCI............ 128Hello state............2wayOutsideRemote node id.........56:160:39.840f80113744000000400202.00107b0efe01.00Remote node ATM addr...39:840f.8011.3744.0000.0040.0102.4000.0c80.8030.00Geneva.7.PXM.a >mpgses1.2.PXM.a > dsppnni-svcc-rccnode index: 2 svc index: 1Hello pkt RX........ 68 SVCC VPI............ 1Hello pkt TX........ 67 SVCC VCI............ 35Hello state............twoWayInsideRemote node id.........48:56:47.009181000000000000000022.003071f80e56.00Remote node ATM addr...47.009181000000003071f80e56.003071f80e56.02node index: 3 svc index: 2Hello pkt RX........ 57 SVCC VPI............ 1Hello pkt TX........ 54 SVCC VCI............ 36Hello state............twoWayInsideRemote node id.........40:56:47.009181000000000000000033.003071f80e52.00Remote node ATM addr...47.009181000000003071f80e52.003071f80e52.02dsppnni-svcc-rcc-timer
Display PNNI Switched Virtual Connection Routing Control Channel (SVCC-RCC) Timer Values—display the PNNI SVCC-based RCC timer values.
The dsppnni-svcc-rcc-timer command displays the SVCC-RCC timer values that are set by the cnfpnni-svcc-rcc-timer command.
Note
If you specify node-index, the command displays the SVCC-based Routing Control Channel (RCC) timer values of the node-index PNNI node.
Cards on Which This Command Runs
PXM45
Syntax
dsppnni-svcc-rcc-timer[node-index]Syntax Description
node-index
Specify the node identifier in the range 1-10. In the current release, the value of the node-index variable must be `1'.
Range: 1-10
Default: 1
Display Contents
The following parameters are displayed for each node.
Related Commands
dsppnni-svcc-rcc-timer
Attributes
Example
dsppnni-timer
Display PNNI Timer—display the PNNI timer values.
The dsppnni-timer command displays the nodal timer values configured through the cnfpnni-timer command. If you provide a node index with the command, the output contains information for that particular node rather than all logical nodes on the switch.
Cards on Which This Command Runs
PXM45
Syntax
dsppnni-timer[node-index]Syntax Description
Display Contents
The display contains the following information for each node. Except for the node index, you can configure all values through the cnfpnni-timer command.
Related Commands
cnfpnni-timer
Attributes
Example
Display PNNI timer values. Since the value of node-index = 1, the command line displays the PNNI timer values for only node 1.
SanJose.7.PXM.a > dsppnni-timer 1node index: 1Hello holddown(100ms)... 120 PTSE holddown(100ms)... 120Hello int(sec).......... 15 PTSE refresh int(sec).. 1800Hello inactivity factor. 5 PTSE lifetime factor... 200Retransmit int(sec)..... 5AvCR proportional PM.... 3 CDV PM multiplier...... 25AvCR minimum threshold.. 50 CTD PM multiplier...... 50Peer delayed ack int(100ms)................... 10Logical horizontal link inactivity time(sec).. 10Geneva.7.PXM.a >
