MGX 8850 and MGX 8950 Command Reference, Release 2.1
PNNI Commands
Downloads: This chapterpdf (PDF - 863.0KB) The complete bookPDF (PDF - 7.36MB) | Feedback

PNNI Commands

Table Of Contents

PNNI Commands

PNNI Addressing

Position-Dependent and Keyword-Driven Parameters

Command Entry

Identifying the AXSM Models

Identifying Physical and Logical Elements

AXSM Format

PNNI Format

addpnni-node

addpnni-summary-addr

aesa_ping

cnfpnni-election

cnfpnni-intf

cnfpnni-link-selection

cnfpnni-mtu

cnfpnni-node

cnfpnni-pkttrace

cnfpnni-routing-policy

cnfpnni-scope-map

cnfpnni-svcc-rcc-timer

cnfpnni-timer

dbgpnni

delpnni-node

delpnni-summary-addr

dsppnni-bn-path

dsppnni-bypass

dsppnni-dbg

dsppnni-election

dsppnni-idb

dsppnni-inducing-uplink

dsppnni-intf

dsppnni-link

dsppnni-link-selection

dsppnni-mtu

dsppnni-neighbor

dsppnni-node

dsppnni-node-list

dsppnni-path

dsppnni-pkttrace

dsppnni-ptse

dsppnni-reachable-addr

dsppnni-routing-policy

dsppnni-scope-map

dsppnni-spoke

dsppnni-summary-addr

dsppnni-svcc-rcc

dsppnni-svcc-rcc-timer

dsppnni-timer


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 and MGX 8950 switches. (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

Link selection

Node addresses and identifiers

Packet size

PNNI interface

PNNI timers

RCC variables

Routing policies

Scope map table

PNNI summary address

Deleting

A logical node

A PNNI summary address

Displays of:

Debug information

Learned nodes

Link information

Neighbor addresses

Node addresses and identifiers

Packet information

Paths

Reachable addresses

Routing policy

System address tables

Timers

PNNI Addressing

The PNNI addresses and identifiers contain fields that are common to each other and should match each other. If you change a field in one item, Cisco Systems advises you to change the corresponding field in the other item. For example, if you change the ATM address, you should change corresponding fields in the PNNI summary address and node identifier. Note 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:

The Initial Domain Identifier (IDI) identifies the domain.

The Initial Domain Part (IDP) identifies the country.

The Authority and Format Identifier (AFI) identifies the address format and who provided it.

The Data Country Code (DCC) identifies the country.

Figure 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.

An MGX 8850 or MGX 8950 node uses 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 Switch Hardware Installation Guide, Release 2.1 or the Cisco MGX 8950 Switch Hardware Installation Guide, Release 2.1.

Table 5-1 Valid Line Numbers and Number of Bays for AXSM Card Types

Front Card
Speed
Lines
Bays

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

AXSM-2-622-E

OC12

1-2

1-2

AXSM-8-155-E

OC3

1-8

1-2

AXSM-16-T3E3-E

T3, E3

1-8

1-2


Identifying Physical and Logical Elements

The Private Network-to-Network Interface (PNNI) control protocol and the AXSM use different formats to identify the same elements. This section describes the format of these elements in the PNNI and AXSM contexts and how they correspond to each other. When you configure or view items on the CLIs of different cards, you often need to specify it in PNNI as well as the AXSM. For example, when you configure a PNNI port on the CLI of the PXM45, you also need to configure a port on the CLI of the AXSM. Furthermore, when you display a connection on the AXSM, you identify that same connection using a different format on the PXM45 CLI. For specific examples of these parallel actions, see the Cisco MGX 8850 and MGX 8950 Switch Software Configuration Guide, Release 2.1.


Note Apart from the way PNNI and the lower levels of logic identify the same element, the issue of configuration sequence needs explanation. When you configure logical ports—as just one example—you must complete certain tasks on the AXSM CLI before and after related PNNI tasks. This manual describes prerequisites for certain commands, but refer to the Cisco MGX 8850 and MGX 8950 Switch Software Configuration Guide, Release 2.1 for more details of this sequence.


AXSM Format

The AXSM items that you identify for addressing purposes are:

Slot

Bay

Line

Logical port

A logical port on an AXSM (and its CLI) always uses the label ifNum. For a UNI and NNI interface, a one-to-one correspondence exists between a logical port and a physical line. For virtual trunks, you can configure multiple ports for a line.

The maximum number of logical ports on an AXSM is 60 or 32 on an AXSM-E, regardless of the number of AXSM back cards or 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:

The shelf is always 1 for the current product and so is usually omitted.

The slot number of the front card.

Subslot is the number of the bay where the back card resides. This number is 1 or 2.

Port is the physical line.

Subport corresponds to the resource partition on the AXSM. For a UNI or NNI, this resource partition is the same number as the logical port number (ifNum) on the AXSM. For a virtual network-to-network interface (VNNI), these numbers do not directly correspond to each other.

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

PNNI port
AXSM

Shelf

N/A

Slot

Slot

Subslot

Bay (for upper or lower back card)

Port

Line

Subport

Logical interface (or port)


As the table shows, a port from the PNNI side is a line on the AXSM, and a subport from the PNNI side 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:

Slot 1

Bay 2

Line 1

Logical interface 1 (or logical port 1)

addpnni-node

Add PNNI Nodecreates a PNNI logical node.

The addpnni-node command creates an instance of a PNNI logical node on the switch. The maximum number of PNNI logical nodes on a switch is 10. Use addpnni-node to add a node in the following circumstances:

After you have removed a node from the topology by executing delpnni-node

After you clear the entire PNNI configuration from the switch by executing clrallcnf or clrcnf

For each node you add at a level of the hierarchy other than the lowest level

For a single-peer network, you do not initially need to execute addpnni-node

For a multi-peer group, you must execute addpnni-node for each peer group level. For all levels above the lowest level, you need to specify only the level parameter because the ATM address of the lowest level applies to all peer groups in the switch. Use dsppnni-node to view the PNNI node configuration.

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 level is a number in the range 1-104 that shows the relative position of a PNNI logical node within a multi-peer group. The current release supports up to 10 logical nodes.

The ATM address applies to the entire switch—the switch requires only one ATM address.

The PNNI node identifier (ID) defines the logical node on the switch. As the Syntax Description explains, the node ID consists of numerous fields (see Figure 5-1).

A peer group identifier defines the nodes in a peer group within a network. Logical nodes on more than one physical switch can belong to a peer group.

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.

Address Field Descriptions

The addpnni-node parameters include two types of identifiers and an ATM address that have similar formats. Their contents overlap to varying degrees. The sections that follow describe these parameters.

ATM Address of the Node

A switch-level ATM address consists of:

An eight-bit byte that identifies the format of the address. The format is either E.164 or the more common NSAP.

19 8-bit bytes for an ATM address.

The last byte of the ATM address is the selector byte.

The Selector byte identifies the host application on the switch. Host applications like PNNI single and multiple peer groups, IP connectivity, and AESA ping have the same ATM address up to the
19 th. byte. The selector byte differentiates between these applications:

The selector byte for a single-peer group is 01.

The multi-peer group selector bytes are 2-10 and refer to the level of the logical node.

AESA ping is 99.


Note For information on port-level ATM addresses, see the description of addaddr.


Figure 5-2 Switch-Level ATM Address

PNNI Logical Node Identifier

A PNNI logical node identifier (node ID) consists of:

A number that indicates the level for the logical node within a hierarchy. The default level is 56.

The length of the ATM address for the nodeID.

An ATM address (the same ATM address as the physical switch).

In Figure 5-3, the level is the default of 56. The length is 160 bits because the ATM address format is one of the NSAP types—NSAP ICD in this case (the 47 in the ATM format field is the reserved format indicator for NSAP ICD). For an E.164 address format, the length of an ATM address is expressed as decimal digits. For the node-level ATM address, the length is 15. (NSAP address lengths are in bits, whereas E.164 address lengths are in decimal digits.)

Figure 5-3 PNNI Logical Node Identifier

Peer Group Identifier

A peer group identifier (pgID) consists of:

A level that indicates how many bits out of the entire pgID field that are actually used.

A string of hexadecimal bytes copied from the ATM address that uniquely identify the peer group.

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). 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 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 bits

lowest | 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." If the node you are adding is not the lowest, type the word "other."

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.

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 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: The Cisco default appears in Figure 5-1.

-nodeId

The PNNI logical node identifier (node ID). The node-id consists of the following logical elements, starting at the most significant byte:

The level of the PNNI node within the hierarchy. (See the description of the level parameter.)

The number of bits in the ATM address. The number is 160 for an NSAP address because the ATM address of the node is always 20 bytes. For an E.164 address, this field is decimal 15.

The ATM address portion of the peer group ID (20 8-bit, hex bytes).

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.)

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 complexNode parameter specifies whether the PNNI node is a complex node. 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 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:

To disallow branching, type -branchingRestricted on.

To allow branching, type -branchingRestricted off.

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 must specify new addresses. For this purpose, you can either use cnfpnni-node or clear the configuration then use addpnni-node. The Cisco MGX 8850 and MGX 8950 Switch Software Configuration Guide, Release 2.1 explains node-addressing in the section, "Guidelines for Creating an Address Plan."

Related Commands

cnfpnni-node, delpnni-node, dsppnni-node

Attributes

Log: log

State: active

Privilege: SUPER_GP


Example

Add a PNNI node with the following configuration then use dsppnni-node to check the configuration:

The PNNI hierarchy level is 56.

The node is on the lowest level of the PNNI hierarchy.

The node ATM address is 47.00918100000000309409f1f1.00309409f1f1.01.

The node PNNI identifier is 56:160:47.00918100000000309409f1f1.00309409f1f1.01.

The peer group ID is 56:47.009181.0000.00. The number of bytes specified by the level parameter is 7 (level=56). Therefore, with the level itself requiring 1 byte and the pg-id having 7 bytes, the total is 8 bytes. As dsppnni-node shows, the system adds 0s for the remaining 6 bytes.

The node is enabled.

The node permits traffic to cross it on the way to other nodes.

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 off

SanJose.7.PXM.a >

Display the PNNI node configuration.

SanJose.7.PXM.a > dsppnni-node

node index: 1                      node name: SanJose
   Level...............        56     Lowest..............      true 
   Restricted transit..       off Complex node........       off 
   Branching restricted        on 
   Admin status........        up     Operational status..        up 
   Non-transit for PGL election..       off 
   Node id...............56:160:47.00918100000000309409f1f1.00309409f1f1.01 
   ATM address...........47.00918100000000309409f1f1.00309409f1f1.01 
   Peer group id.........56:47.00.9181.0000.0000.0000.0000.00 

SanJose.7.PXM.a > 

addpnni-summary-addr

Add PNNI Summary Addresscreate 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.

Range: 1-10
Default: 1

addressprefix

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.

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 of 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

Log: log

State: active

Privilege: SUPER_GP


Example

This example shows the addpnni-summary-addr command line that adds a PNNI address prefix, configured as follows:

The PNNI summary address is 47.0091.8100.0000.0030.9409.f1f1.

The length of the PNNI summary address is 104 bits.

This PNNI summary address contains only internal addresses.

This PNNI summary address has no advertising suppression (it is advertised).

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 false 
SanJose.7.PXM.a > dsppnni-summary-addr 1

node index: 1
   Type..............    internal     Suppress..............   false
   State............. advertising
   Summary address........47.0091.8100.0000.0030.9409.f1f1/104

SanJose.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 contacts 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

destination address

Set up the destination address in Network Service Access Point (NSAP) format.

Default: null

-setupcall

Set up a switched virtual connection (SVC) as part of a ping. The call is torn down when the interval expires (see -timeout parameter).

yes: Set up a call.
no: Do not set up a call.

Default: no

-qos

The quality of service (QoS) used for switched virtual connection (SVC) ping connection. The QoS can be CBR, ABR, or UBR.

Default: UBR

-trace

Specifies whether a path trace is enabled during the ping. The trace stops when the interval specified by -timeout elapses.

yes: A path trace is enabled.
no: No path trace is enabled.

Default: no

-data

Specify whether data packets are sent with the ping. The data packets cease when the interval specified by -timeout elapses.

yes: The data packets are sent.
no: No data packets are sent.

Default: disable

-timeout

Specify the connection timeout for ping. Any selected ping options also terminate when the interval specified by -timeout elapses.

Range: 5-120 seconds
Default: 5 seconds

-interval

Specify the interval between successive transmissions.

Range: 5-120 seconds
Default: 5 seconds

-pcr

Specify the peak cell rate.

Range: 1-100 cells per second
Default: 10

-scr

Specify the sustained cell rate.

Range: 1-50 cells per second
Default: 5


Related Commands

dsppingatmaddr

Attributes

Log: log

State: active

Privilege: SUPER_GP


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:

No call is set up.

The QoS metric is UBR.

No trace is enabled.

No data is sent with the ping.

The ping waits six seconds for a reply.

The ping re-occurs every 60 seconds unless it finishes.

The peak cell rate of the ping is five cells per second (cps).

The sustained cell rate of the ping is five cps.

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 5

Ping Got CLI message, index=0

PING:from PNNI—SOURCE ROUTE
DTL    1 :Number of (Node/port)elements    2

DTL 1:NODE 1::56:160:71:0:145::238:238:238:238:Port 1:262656

DTL 1:NODE 2::56:160:71:0:145::88:172:35:172:Port 2:0

Port List :no of ports =    1

Port ID    1:262656

SanJose.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.

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:

Number of seconds that the node delays advertising its choice of preferred PGL

Number of seconds that the node waits to be declared the preferred PGL by unanimous agreement among its peer group members

Number of seconds that the node waits before it restarts the election of a new PGL after connectivity to the current PGL is lost

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

node-index

The node-index uniquely identifies of the node within the hierarchy on the local switch.

Range: 1-10
Default: 1

-priority

Specify the leadership priority within a peer group.

Range: 1-20
Default: 0

-initTime

Specify the number of seconds that this node delays advertising its choice of preferred PGL.

Default: 15 seconds

-overrideDelay

Specify the number of seconds that this PNNI node waits to be declared the preferred PGL by unanimous agreement among its peer group members.

Default: 30 seconds

-reelectionTime

After losing connectivity to the current PGL, specify the number of seconds that this PNNI node waits before restarting the process of electing a new peer group leader.

Default: 15 seconds


Related Commands

dsppnni-election

Attributes

Log: log

State: active

Privilege: SUPER_GP


Example

Specify the following PGL election parameters, then use dsppnni-election to check these parameters.

The node index is 1.

The node election priority is 15.

The init time is 15 seconds.

The node waits 20 seconds before proclaiming itself the peer group leader.

If the node looses connection with the peer group leader for 10 secs it starts the election process.

p2spvc4.7.PXM.a > cnfpnni-election 1 -priority 15 -initTime 10 -overrideDelay 20 
-reelectionTime 10 

p2spvc4.7.PXM.a > dsppnni-election

node index: 1
   PGL state......        OperPgl     Init time(sec).......        10
   Priority.......            15      Override delay(sec)..        20
                                      Re-election time(sec)        10
   Pref PGL...............56:160:47.019181004030211100000000.00107be92f13.01
   PGL....................56:160:47.019181004030211100000000.00107be92f13.01
   Active parent node id..36:56:47.019181004030211100000000.000142265c0d.00


node index: 2
   PGL state......        OperPgl     Init time(sec).......        15
   Priority.......            15      Override delay(sec)..        30
                                      Re-election time(sec)        15
   Pref PGL...............36:56:47.019181004030211100000000.000142265c0d.00
   PGL....................36:56:47.019181004030211100000000.000142265c0d.00
   Active parent node id..0:0:00.000000000000000000000000.000000000000.00

p2spvc4.7.PXM.a >

cnfpnni-intf

Configure PNNI Interfacespecify 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.

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

Identifies a PNNI physical port. The format is slot:subslot.port:subport. For a description of each field, see the section, "PNNI Format," at the beginning of the chapter.

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: 0

-awcbr

Specify the administrative weight for constant bit rate (CBR) on this interface.

Range: 0-4,194,304
Default: 5040

-awrtvbr

Specify the administrative weight for real-time variable bit rate (rt-VBR) on this interface.

Range: 0-4,194,304
Default: 5040

-awnrtvbr

Specify the administrative weight for non-real-time variable bit rate (nrt-VBR) on this interface.

Range: 0-4,194,304
Default: 5040

-awabr

Specify the administrative weight for available bit rate (ABR) on this interface.

Range: 0-4,194,304
Default: 5040

-awubr

Specify the administrative weight for unspecified bit rate (UBR) on this interface. UBR connections can include SVC ping connections.

Range: 0-4,194,304
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-4,194,304
Default: 5040


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

Log: log

State: active

Privilege: SUPER_GP


Example

Specify the following AWs on port 4:1.1:11.

The AW for real time variable bit rate is 11040.

The AW for non-real time variable bit rate is 20040.

The AW for unspecified bit rate is 1040.

Use the dsppnni-intf command to display the configuration.

SanJose.7.PXM.a > cnfpnni-intf 4:1.1:11 -awrtvbr 11040 -awnrtvbr 20040 -awubr 1040 

SanJose.7.PXM.a > dsppnni-intf 4:1.1:11

Physical port id: 4: 1.1:11        Logical port id:   17045515
   Aggr token..........         0     AW-NRTVBR...........     20040
   AW-CBR..............      5040     AW-ABR..............     5040
   AW-RTVBR............     11040     AW-UBR..............      1040

SanJose.7.PXM.a > 

cnfpnni-link-selection

Configure PNNI Link Selectionspecify 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

Identifies a PNNI physical port. The format is slot:subslot.port:subport. For a description of each field, see the section, "PNNI Format," at the beginning of the chapter.

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 and so evenly distributes the number of calls across the parallel links. The load balance policy works well with links that have identical or very similar AW or bandwidth characteristics.


Related Commands

dsppnni-link-selection

Attributes

Log: log

State: active

Privilege: SUPER_GP


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 maxavcr 
SanJose.7.PXM.a > dsppnni-link-selection 4:1.1:11

physical port id:        4:1.1:11     link selection: maxavcr
 logical port id:        17045515


SanJose.7.PXM.a > 

cnfpnni-mtu

Configure PNNI Maximum Transfer Unitspecify 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 handle. 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 dsppnni-mtu to display the PNNI packet size configuration.

Cards on Which This Command Runs

PXM45

Syntax

cnfpnni-mtu <mtu>

Syntax Description

mtu

Specify maximum transmit unit in number of bytes.

Range: 2048-8192 bytes
Default: 2048 bytes


Related Commands

dsppnni-mtu

Attributes

Log: log

State: active

Privilege: SUPER_GP


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 3002

SanJose.7.PXM.a > dsppnni-mtu

max packet size : 3002

SanJose.7.PXM.a > 

cnfpnni-node

Configure PNNI Nodemodify parameters for an existing PNNI node.

The node-level cnfpnni-node command lets you:

Modify the parameters of an existing logical node.

Enable or disable a node. This ability applies to:

Parameters that require the node to be disabled before you can modify them (if you do not modify parameters that require a disabled node, you can modify one or more parameters with one execution of cnfpnni-node).

A situation where you created the node in the disabled state with addpnni-node.

The node configuration and state parameters you can modify are as follows:

The ATM address—requires the node to be disabled

The level of the node within the hierarchy—requires the node to be disabled

The node ID—requires the node to be disabled

The peer group ID—requires the node to be disabled

Whether the node is the lowest node in the hierarchy

The state of the node—enabled or disabled

Whether connections can transit this node

Whether or not the node is complex

Whether the node supports point-to-multipoint connections

The preceding parameters appear as optional parameters in the syntax. The only required parameter for this command is the local node index. The local node index is a number in the range 1-10 that indicates the level of the logical node within a multi-peer hierarchy on the switch. If you do not know the value of this system-generated item, use dsppnni-node.


Note When this command runs, existing calls are not affected. Modified parameters apply to new routing after the command finishes.


Disabling the Node for Parameters That Require It

For some of parameters, you must first disable the node. Applicable parameters are the:

Level

ATM address

Node ID

Peer group ID

For these parameters, three executions of cnfpnni-node are necessary:

1. cnfpnni-node -enable false

2. cnfpnni-node (change parameters, including those that do not require a disabled node)

3. cnfpnni-node -enable true

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. 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 the Node for Parameters That Require It." 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). As shown in Figure 5-6, node-id is a 22-byte, formatted hexadecimal string.


Note Before you change the node ID, you must first use the cnfpnni-node command one time with the parameter string -enable false to disable the node.


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

-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



Caution Cisco factory-set defaults for address prefixes and the peer group ID share field values with the ATM address. If you change the peer group ID, you should change the corresponding fields in the ATM address and node identifier. (See Figure 5-6 for the mapping between these addresses.)

Figure 5-6 Cisco Factory-shipped Defaults for PNNI Peer Group Identifier, PNNI Summary Address, ATM Address, and PNNI Node Identifier

Usage Guidelines

All 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 and MGX 8950 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

Log: log

State: active

Privilege: SUPER_GP


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:

The PNNI hierarchy level is 56.

The node ATM address is 47.0091 8100000000309409f1f1.00309409f1f1.01.

The node PNNI identifier is 56:160:47.00918100000000309409f1f1.00309409f1f1.01.

The node PNNI group identifier is 56:47.009181.0000.00. The length specified by the hierarchy level is 56 (8 bytes) the following 12 zeros are fill.

The node is at the lowest level of the network PNNI hierarchy.

The node is enabled.

The node does not permit traffic to cross it on the way to other nodes.

The node is not a complex node.

The node permits branching.

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 off 

SanJose.7.PXM.a > dsppnni-node

node index: 1                      node name: SanJose
   Level...............        56     Lowest..............      true 
   Restricted transit..       on      Complex node........       off 
   Branching restricted        off 
   Admin status........        up     Operational status..        up 
   Non-transit for PGL election..       off 
   Node id...............56:160:47.00918100000000309409f1f1.00309409f1f1.01 
   ATM address...........47.00918100000000309409f1f1.00309409f1f1.01 
   Peer group id.........56:47.00.9181.0000.0000.0000.0000.00 
SanJose.7.PXM.a > 

cnfpnni-pkttrace

Configure PNNI Packet Tracespecify 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 Executing cnfpnni-pkttrace can significantly increase operational overhead, thereby degrading network performance. You should consider executing this command while the node carries little or no live traffic. If you execute cnfpnni-pkttrace while live traffic is present, you may want to consider tracing the packets for one direction at a time (transmit or receive).


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

tx

Specify whether the switch traces transmitted packets.

on: Trace the transmitted packets
off: Do not trace the transmitted packets
Default: (no default)

rx

Specify whether the switch traces received packets.

on: Trace the received packets
off: Do not trace the received packets
Default: (no default)

node-index

The node index indicates the relative level of the logical node within a multi-peer group on the switch. The range is 1-10, and the lowest level is 1.

Range: 1-10
Default: 1

-portId

The port ID in this instance has the format of the logical ID number. The format is a 32-bit encoded number in the range 1-2147483648. If you do not have the port ID in this form, use dsppnport and provide it with the common portID format of slot:subslot.port:subport. The output of dsppnport shows the logical number for the port ID. Use this value is for the -portID parameter.

Range: 1-2147483648

-svcIndex

PNNI uses the SVC index as a reference to the SVC-based, logical, horizontal link. This parameter is meaningful only if you specify node-index.

Default: none


Usage Guidelines

PNNI trace commands have characteristics that standard debug commands lack, namely:

Trace commands debug interactions between different software modules or within a module.

Trace output goes to a system trace buffer, not to the console.

Tracing controls a more granular filtering of unnecessary debug output.

Related Commands

dsppnni-pkttrace, dsppnport, dsppnports

Attributes

Log: log

State: active

Privilege: SERVICE_GP


Example

Configure then display a trace that examines the contents of PNNI Hello packets, as follows:

The transmit packets are traced.

The packet trace occurs at node index of 1 (the default for cnfpnni-pkttrace and therefore omitted).

The packet trace takes place on the port identifier of 17504.

Geneva.7.PXM.a > cnfpnni-pkttrace tx 17504 
PNNI/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  2a00001a

Geneva.7.PXM.a > dsppnni-pkttrace tx -portId 17504

Node Index :1   Port id:        17504   Tx Pkt Trace on

Geneva.7.PXM.a >

cnfpnni-routing-policy

Configure PNNI Routing Policyspecify 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:

Generating background routing tables

Load balancing

On-demand routing—applies to crankback or a situation where the node must route a call to a destination for which no route exists in the pre-computed routing tables

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.

The administrative weight (AW) background routing table stores the AWs for all routes.

The cell transfer delay (CTD) background routing table stores the CTD data for known routes.

The cell delay variation (CDV) background routing table stores the CDV data for known routes.

On-demand routing is used if any of the following occur:

All pre-computed routing tables are disabled.

A route does not appear in the precomputed routing tables.

Crankback is enabled within a designated transit list (DTL).


Caution Poor routing policies can cripple or even crash a network. You should not change routing policies on a deployed network unless you have carefully planned the changes and know how the changes can affect the network.

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

-sptEpsilon

The shortest path (SPT) epsilon you supply specifies a tolerance in the form of a percent that can influence which paths qualify as equal-cost during route calculation. A higher tolerance results in a broader range of path cost-values that can qualify as equal-cost. If two paths have very similar administrative weights (AWs), a large enough tolerance eliminates equal-cost as a routing factor because the routing algorithm regards the costs as equal.

Range: 0-20
Default: 0, which means the cost of two paths must be identical to qualify as equal-cost

The range of 0-20 for this parameter comes from the ATM Forum PNNI specification. However, the percent of tolerance that the numbers dictate is determined by individual vendors. Cisco Systems currently maps the following percentages for a switch:

0: the total AWs along both directions of the route must be identical.
1-2: the total AWs along both directions of the route must be within 1.06%.
3-4: the total AWs along both directions of the route must be within 3.125%.
5-9: the total AWs along both directions of the route must be within 6.25%.
10-15: the total AWs along both directions of the route must be within 12.5%.
16-20: the total AWs along both directions of the route must be within 25.0%.


Note In the event of a crankback, PNNI uses on-demand routing. It starts a new calculation of the path based on the link information in the database. The SPT tables are not used, so sptEpsilon is not a factor in case of a crankback.


-sptHolddown

The interval between two consecutive calculations for generating routing tables. If a network is stable, it may not be necessary to generate routing tables 10 times per second. In such a case, you can increase the value to reclaim CPU time needlessly used to update unchanging routing tables.

Units: 100 millisecond increments
Range: 1-600 (0.1-60 seconds)
Default: 1

-bnPathHolddown

The minimum interval between consecutive calculations of routing tables for border nodes. For a stable network, generating the routing tables 10 times a second may be unnecessary. If this case, you can increase the interval to save the CPU time spent on updating routing tables that are not changing.

Units: 100 milliseconds
Range: 2-600 (0.2-60 seconds)
Default: 2

-loadBalance

The PNNI routing protocol relies on the load balance policy when it determines that the routes to a destination have equal cost. (PNNI determines routes to be identical according to the metrics in the AW, CDV, or CTD routing table.) Note that the SPT epsilon value can be a factor when PNNI calculates cost.

The choice for load balancing is "random" or "maxbw." Type the entire word.

With "random" load balancing, PNNI randomly chooses between the equal cost routes. This rule requires less computational overhead.

With "maxbw" load balancing, PNNI selects the route with more available bandwidth when it chooses between equal cost routes. This rule has more overhead due to ongoing comparison of available bandwidth on the routes.

Default: no default

-onDemand

On-demand routing applies to crankback or a situation where the node must route a call to a destination for which no route exists in the pre-computed routing tables. The on-demand policy is either "firstfit" and "bestfit."

With firstfit (the default), PNNI selects the first route to the destination. This approach minimizes search time but may not result in the best route.

With bestfit, PNNI selects a route based on:

The route with the lowest cost (see AW in the cnfpnni-intf description and maxcost in the addcon description because these parameters are closely related).

Link verification.

Path constraint checks.

Avoidance of blocked nodes and links.

Checking limits in the designated transit list (DTL).

With bestfit, PNNI selects the optimum route but entails greater computing overhead. The search-time depends on the density and complexity of the network.

Default: firstfit

-awBgTable

Enable or disable the background routing table for AW.

on: The background routing table of AW is enabled.
off: The background routing table of AW is disabled.

Default: on

-ctdBgTable

Enable or disable the background routing table of CTD. The CTD parameter is the interval between a cell exiting the source PNNI node and entering the destination PNNI node.

on: The background routing table of CTD is enabled.
off: The background routing table of CTD is disabled.

Default: on

-cdvBgTable

Enable or disable the background routing table of CDV. The CDV parameter is a component of cell transfer delay, and is a quality of service (QoS) delay parameter associated with CBR and VBR service. Cell Delay Variation is the variation of delay between cells, measured peak to peak.

on: The background routing table of CDV is enabled.
off: The background routing table of CDV is disabled.

Default: on


Related Commands

dsppnni-routing-policy

Attributes

Log: log

State: active

Privilege: SUPER_GP


Example

Specify the following routing policy:

Only paths with identical values qualify as equal-cost paths.

The routing tables are generated every 0.1 seconds.

The load balancing is purely random.

On-demand routing selects to the optimal route.

The background routing table for AW is enabled.

The background routing table for cell transfer delay is enabled.

The background routing table for cell delay variation is enabled.

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 on

Geneva.7.PXM.a > dsppnni-routing-policy

SPT epsilon......... 0 Load balance........ random
SPT holddown time... 1 On demand routing... best fit
SPT path holddown time 2 AW Background Table on
CTD Background Table on CDV Background Table on
Geneva.7.PXM.a >

cnfpnni-scope-map

Configure PNNI Scope Map Tablespecify 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.

Cards on Which This Command Runs

PXM45

Syntax

cnfpnni-scope-map <scope> <level>

Syntax Description

scope

Specify the UNI 4.0 address scope.

Range: 1-15, where:

1 = LocalNetwork
2 = LocalNetworkPlusOne
3 = LocalNetworkPlusTwo
4 = SiteMinusOne
5 = IntraSite
6 = SitePlusOne
7 = OrganizationMinusOne
8 = IntraOrganization
9 = OrganizationPlusOne
10 = CommunityMinusOne
11 = IntraCommunity
12 = CommunityPlusOne
13 = Regional
14 = InterRegional
15 = Global
Default = none.

level

Specify the PNNI level to which the UNI 4.0 address scope is mapped.

Range: 1-104
Default = 56


Related Commands

dsppnni-scope-map

Attributes

Log: log

State: active

Privilege: SUPER_GP


Example

Configure the scope map table for the following:

The variable scope is 1.

The variable level is 56.

These values map the UNI 4.0 scope `1' to the PNNI hierarchical level `56'.

Geneva.7.PXM.a > cnfpnni-scope-map 1 56
Geneva.7.PXM.a > dsppnni-scope-map

UNI  Scope                Pnni Routing Level
----------------------    ------------------
LocalNetwork(1)                           56
LocalNetworkPlusOne(2)                    56
LocalNetworkPlusTwo(3)                    56
SiteMinusOne(4)                           40
IntraSite(5)                              40
SitePlusOne(6)                            32
OrganizationMinusOne(7)                   32
IntraOrganization(8)                      24
OrganizationPlusOne(9)                    24
CommunityMinusOne(10)                     24
IntraCommunity(11)                         8
CommunityPlusOne(12)                       8
Regional(13)                               0
InterRegional(14)                          0
Global(15)                                 0

Geneva.7.PXM.a >

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 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

node-index

The node index indicates the relative level of the logical node within a multi-peer group on the switch. The range is 1-10, and the lowest level is 1.

Range: 1-10
Default: 1

-initTime

The number of seconds this node waits before it advertises its choice of preferred SVCC to a neighbor with a numerically lower ATM address. This node does so after determining that such an SVCC should be established.

Range: 1-10 seconds
Default: 10

-retryTime

The number of seconds this node waits before it attempts to re-establish an apparently necessary and viable SVCC-based RCC that was unexpectedly torn down.

Range: 10-60 seconds
Default: 60

-callingIntegrityTime

The number of seconds the node waits while it attempts to set up an SVCC as the calling party. If the SVCC is not fully established within this time period, the node tears down the connection.

Range: 5-300
Default: 300

-calledIntegrityTime

The number of seconds the node waits while it attempts to set up an SVCC as the called party. If the SVCC is not fully established within this time period, the node tears down the connection.

Range: 10-300
Default: 300


Related Commands

dsppnni-svcc-rcc-timer

Attributes

Log: log

State: active

Privilege: SUPER_GP


cnfpnni-timer

Configure PNNI Timers

The cnfpnni-timer command specifies the initial PNNI timer values and significant change thresholds of a network node. You must carefully plan the use of this command because modifying a timer can significantly change network efficiency.

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

node-index

The node index indicates the relative level of the logical node within a multi-peer group on the switch. The range is 1-10. The lowest level is 1.

Range: 1-10
Default: 1

-ptseHolddown

The holddown value is the time the switch waits before it broadcasts PTSEs. The increments are tenths of a second. For example, -ptseHolddown 1 means 0.1 second, and
-ptseHolddown 10 means 1 second, and so on.

Range: 0.1-1000
Default: 10 (1 second)

-helloHolddown

Specify the initial value for the Hello hold down timer that the node uses to limit the rate at which it sends Hellos.

Units: 100 ms. 1 = 0.1 seconds
Range: 0.1-1000
Default: 10 (1 second)

-helloInterval

Specify the initial value for the Hello timer in seconds. The value limits the rate at which the node sends Hellos.

Range: 1-300 seconds
Default: 15 seconds

-helloInactivityFactor

The product of the hello-inactivity-factor and the peer neighbor hello-interval is the maximum time (in sec) that the neighbor is considered alive after the last reception of a Hello packet.

Range: 1-50 seconds
Default: 5 seconds

-ptseRefreshInterval

Specify the initial time allowed for the PTSE to re-originate specified in seconds.

Range: 30-1800 seconds
Default: 1800 seconds

-ptseLifetimeFactor

Specify the value for the lifetime multiplier, expressed as a percentage. The product of it and the ptse-refresh-interval is the initial value of the remaining lifetime of a self-created PTSE.

Range: 101-1000 percent
Default: 200

-retransmitInterval

Specify the period between retransmissions of unacknowledged DS, PTSE request, and PTSP specified in seconds.

Range: 5-60 seconds
Default: 5 seconds

-ptseDelayedAckInterval

Specify the minimum interval between transmissions of delayed PTSE acknowledgment packets.

Units: 100 milliseconds. 1 = 0.1 seconds.
Range: 1-10
Default: 10 (1 second)

-avcrPm

Specify the proportional multiplier used in the algorithms that determine significant change for available cell rate (AvCR) parameters.
avcr-pm is expressed as a percentage.

Range: 1-99 percent
Default: 50 percent

-avcrMt

Specify the minimum threshold used in the algorithms that determine significant change for available cell rate (AvCR) parameters which are expressed as a percentage. You can change this value to minimize the overhead created by advertisements triggered by AVCR changes.
avcr-mt is expressed as a percentage.

Range: 1-99 percent
Default: 3 percent

-cdvPm

Specify the proportional multiplier used in the algorithms that determine significant change for Cell Delay Variation (CDV) parameters which are expressed as a percentage. is the variation of delay between cells, measured peak to peak.You can change this value to minimize the overhead created by advertisements triggered by CDV changes.
cdv-pm is expressed as a percentage.

Range: 1-99 percent
Default: 25 percent

-ctdPm

Specify the proportional multiplier used in the algorithms that determine significant change for cell transfer delay (CTD) parameters which are expressed as a percentage. You can change this value to minimize the overhead created by advertisements triggered by changes to CTD values.
ctd-pm is expressed as a percentage.

Range: 1-99 percent
Default: 50 percent


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

Log: log

State: active

Privilege: SUPER_GP


Example

This example shows the cnfpnni-timer command line that is set with the following parameter values:

The node broadcasts Hello packets every 1.2 seconds.

The node broadcasts Hello packets every 1.2 seconds.

The node Hello timer is 15 seconds.

The node hello-inactivity-factor is 5 seconds.

The node recreates PTSEs every 1800 seconds (30 minutes).

The node evaluates the initial PTSE lifetime by multiplying the ptse-refresh-interval (1800 seconds) by 200.

The node retransmits every 5 seconds.

If the node broadcasts a PTSE and the PTSE is not acknowledged, the node waits 1 second to rebroadcast its PTSE.

The node multiplies an algorithm by 3% to determine the value that qualifies as a significant change for AvCR parameters.

The node multiplies an algorithm by 50% to determine the value that qualifies as the minimum threshold for significant change of AvCR parameters.

The node multiplies an algorithm by 25% to determine the value that qualifies as a significant change for CDV parameters.

The node multiplies an algorithm by 50% to determine the value that qualifies as a significant change for CTD parameters.

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 50

SanJose.7.PXM.a > dsppnni-timer 1
node index: 1
Hello holddown(100ms)... 12 PTSE holddown(100ms)... 12
Hello int(sec).......... 15 PTSE refresh int(sec).. 1800
Hello inactivity factor. 5 PTSE lifetime factor... 200
Retransmit int(sec)..... 5
AvCR proportional PM.... 3 CDV PM multiplier...... 25
AvCR minimum threshold.. 50 CTD PM multiplier...... 50
Peer delayed ack int(100ms)................... 10
Logical horizontal link inactivity time(sec).. 10

Geneva.7.PXM.a > 

dbgpnni

Debug PNNI Messagesspecify 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 The selections you make with this command can significantly affect network performance. The simultaneous dumping of multiple types of debug messages can increase the overhead more than incrementally as each type is added. Consider the options individually rather than simultaneously.


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

-all

Specify whether all types of debug message go to the console.

on: All types of debug message go to the console.
off: Only the debug message-types specified by the other dbgpnni parameters are active.

Default: none

-timer

Specify whether the timer debug messages go to the console.

on: The timer debug messages go to the console.
off: The timer debug messages do not go to the console.

Default: none

-hello

Specify whether the hello debug messages go to the console.

on: The hello debug messages go to the console.
off: The hello debug messages do not go to the console.

Default: none

-nbr

Specify whether the PNNI neighbor FSM debug messages go to the console.

on: The PNNI neighbor FSM messages go to the console.
off: The PNNI neighbor FSM debug messages do not go to the console.

Default: none

-election

Specify whether the PNNI PGL election debug messages go to the console.

on: The PNNI PGL election messages go to the console.
off: The PNNI PGL election debug messages do not go to the console.

Default: none

-nodereachability

Specify whether the debug messages about PNNI node reachability computation go to the console.

on: The PNNI node reachability computation messages go to the console.
off: The PNNI node reachability computation is not active

Default: none

-itf

Specify whether the interface FSM debug messages go to the console.

on: The interface FSM messages go to the console.
off: The interface FSM debug messages do not go to the console.

Default: none

-address

Specify whether the debug messages about the handling on addresses go to the console.

on: The debug handling on addresses is active
off: The debug handling on addresses is not active

Default: none

-lgn

Specify whether the logical group node debug messages go to the console.

on: The PNNI logical group node messages go to the console.
off: The PNNI logical group node debug messages do not go to the console.

Default: none

-itdb

Specify whether the debug messages about the handling on the internal topology database go to the console.

on: The debug messages for the internal topology database go to the console.
off: The debug messages for the internal topology database does not go to the console.

Default: none

-cp

Specify whether the control point debug messages go to the console.

on: The control point debug messages go to the console.
off: The control point debug messages do not go to the console.

Default: none

-spt

Specify whether the shortest path tree debug messages go to the console.

on: The shortest path tree debug messages go to the console.
off: The shortest path tree debug messages do not go to the console.

Default: none

-ra

Specify whether the route agent debug messages go to the console.

on: The route agent debug messages go to the console.
off: The route agent debug messages do not go to the console.

Default: none.

-linkselection

Specify whether the link selection debug messages go to the console.

on: The link selection debug messages go to the console.
off: The link selection debug messages do not go to the console.

Default: none


Related Commands

dsppnni-dbg

Attributes

Log: log

State: active

Privilege: CISCO_GP


Example

Specify the following PNNI debug message-options:

Interface debugging is enabled.

Address handling debugging is enabled.

Use dsppnni-dbg to check which debug messages types appear on the terminal.

SanJose.7.PXM.a > dsppnni-dbg
pnni debugging option:

hello   election   nbr   itf   timer   lgn   spt   node reachability
-----   --------   ---   ---   -----   ---   ---   -----------------
off     off        off   off   off     off   off   off

address   itdb   ra    cp    link selection
-------   ----   ---   ---   --------------
off       off    off   off   off


SanJose.7.PXM.a > dbgpnni -itf on -address on


SanJose.7.PXM.a > dsppnni-dbg
pnni debugging option:

hello   election   nbr   itf   timer   lgn   spt   node reachability
-----   --------   ---   ---   -----   ---   ---   -----------------
off     off        off   on    off     off   off   off

address   itdb   ra    cp    link selection
-------   ----   ---   ---   --------------
on        off    off   off   off

In the second example, the parameters are changed as follows:

Interface debugging is disabled.

Address handling debugging is disabled.

SanJose.7.PXM.a > dbgpnni -itf off -address off


SanJose.7.PXM.a > dsppnni-dbg
pnni debugging option:

hello   election   nbr   itf   timer   lgn   spt   node reachability
-----   --------   ---   ---   -----   ---   ---   -----------------
off     off        off   off    off     off   off   off

address   itdb   ra    cp    link selection
-------   ----   ---   ---   --------------
off       off    off   off   off


SanJose.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

node-index

The node index indicates the relative level of the logical node within a multi-peer group on the switch. The range is 1-10, and the lowest level is 1.

Range: 1-10
Default: 1


Related Commands

addpnni-node, cnfpnni-node, delpnni-node

Attributes

Log: log

State: active

Privilege: SUPER_GP


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 3 
SanJose.7.PXM.a > dsppnni-node 3 

   Unknown Error Code
Syntax: dsppnni-node [node-index]

        nodeIndex -- node-index: 32 bit number starting from 1, Optional parameter

        possible errors are:
node does not exist

SanJose.7.PXM.a > 

delpnni-summary-addr

Delete PNNI Summary Addressdelete 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

node-index

The node index indicates the relative level of the logical node within a multi-peer group on the switch. The range is 1-10, and the lowest level is 1.

Range: 1-10
Default: 1

address-prefix

The PNNI summary address.

Default: none

prefix-length

The length of the address-prefix in bits is less than or equal to 152.

Default: none


Related Commands

addpnni-summary-addr, dsppnni-summary-addr

Attributes

Log: log

State: active

Privilege: SUPER_GP


Example

Delete a summary address, as follows:

The node-index is 1.

The node address prefix is 47.0091.8100.0000.0030.9409.f1f1.

The length of the address prefix is 104 bits.

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 104

SanJose.7.PXM.a > 

dsppnni-bn-path

Display PNNI Border Node Pathsdisplay 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 The command applies to multi-peer groups only.


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

node index

The range is 1-10.

source node IDB index

The node identifier within the internal data base (IDB).

Range: 1-2147483648.

source node ID

The node ID of the source.

destination node IDB index

The node identifier of each destination node.

destination node ID

The node ID of each destination.

metrics for the path

For each class of service (CBR, rt-VBR, nrt-VBR, ABR, UBR), the configuration for each of the following routing metrics:

Administrative weight (AW)

Maximum cell rate (MaxCR)

Available cell rate (AvCR)

Cell transfer delay (CTD)

Cell delay variation (CDV)

Cell loss priority, first leaky bucket (CLP0)

Cell loss priority, second leaky bucket (CLP0+1)


Related Commands

None

Attributes

Log: no

State: active, standby

Privilege: ANYUSER


Example

Enter dsppnni-db-path and specify node index 2.

mpg2.7.PXM.a > dsppnni-bn-path 2 

node index:2 

source node IDB index   source node id 
---------------------   -------------------------------------------------- 
                    1   56:160:47.009181000000003071f80e56.003071f80e56.01 

destination node IDB index   destination node id 
--------------------------   -------------------------------------------------- 
                        12   56:160:47.009181000000003071f80e52.003071f80e52.01 

            CBR    RTVBR   NRTVBR      ABR      UBR 
         ------   ------   ------   ------   ------ 
AW         5040     5040     5040     5040     5040 
MaxCR    250000   250000   250000   250000   250000 
AvCR     248759   248759   248759   248759   248759 
CTD          17       17       17       17       17 
CDV        4167    52954    52954   104912   104912 
CLR0          8        8        8        8        8 
CLR0+1        8        8        8        8        8

dsppnni-bypass

Display PNNI Bypassesdisplay 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 This command applies to multi-peer groups only.


Cards on Which This Command Runs

PXM45

Syntax

dsppnni-bypass <node-index>

Syntax Description

node-index

The node index points to the LGN of this peer group. It indicates the relative level of the node within the hierarchy on the switch. The range is 1-10, and the lowest level is 1.

Range: 1-10
Default: 1


Display Contents

The display contains the following fields for each node.

node-index

The node index indicates the relative level of the logical node within a multi-peer group on the switch. The supported range is 1-10, and the lowest level is 1.

Input port Id

The logical form of port identifier at the input.

Range: 1-2147483648.

Output port Id

The logical form of port identifier at the output.

Range: 1-2147483648.

ptse id

Display the unique identifier assigned to the PNNI topology state elements PTSE. ptse-id is the 32 bit numeric node identifier assigned by the software—it is not user-configurable.

flags

Although a hexadecimal flag appears, it applies to software debugging by Cisco engineers and so is not described here.


Related Commands

None

Attributes

Log: no

State: active, standby

Privilege: ANYUSER


Example

Display the bypass table for an LGN using complex node representation in the peer group.

Geneva.7.PXM.a > dsppnni-bypass
node index: 1
Input portId........ 376 Output portId........ 399
Ptse id............. 12 Flags................ a3

          CBR  RTVBR NRTVBR    ABR    UBR 
-----  ------ ------ ------ ------ ------ 
AW       5040   5040   5040   5040   5040 
MCR         0      0      0      0      0 
AvCR   100000 100000 100000 100000 100000 
CTD         0      0      0      0      0 
CDV         0      0      0      0      0 
CLR0        0      0      0      0      0 
CLR0+1      0      0      0      0      0 
CRM        10     10     10     10     10 
VF          5      5      5      5      5 

Geneva.7.PXM.a > 

dsppnni-dbg

Display PNNI Debug Flagsdisplay 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-dbg

Display 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.

Hello

Display the flag that indicates whether the Hello packet debug is enabled.

on: the Hello packet debug is enabled.
off: the Hello packet debug is disabled.

election

Display the flag that indicates whether the peer group election debug is enabled.

on: the peer group election debug is enabled.
off: the peer group election debug is disabled.

nbr

Display the flag that indicates whether the neighbor debug is enabled.

on: the neighbor debug is enabled.
off: the neighbor debug is disabled.

itf

Display the flag that indicates whether the interface debug is enabled.

on: the interface debug is enabled.
off: the interface debug is disabled.

timer

Display the flag that indicates whether the timer debug is enabled.

on: the timer debug is enabled.
off: the timer debug is disabled.

lgn

Display the flag that indicates whether the logical node (LGN) debug is enabled.

on: the LGN debug is enabled.
off: the LGN debug is disabled.

spt

Display the flag that indicates whether the logical node SPT debug is enabled.

on: the SPT debug is enabled.
off: the SPT debug is disabled.

node reachability

Display the flag that indicates whether the node reachability debug is enabled.

on: the node reachability debug is enabled.
off: the node reachability debug is disabled.

address

Display the flag that indicates whether the addressing debug is enabled.

on: the addressing debug is enabled.
off: the addressing debug is disabled.

itdb

Display the flag that indicates whether the internal data base debug is enabled.

on: the internal data base debug is enabled.
off: the internal data base debug is disabled.

ra

Display the flag that indicates whether the route agent debug is enabled.

on: the route agent debug is enabled.
off: the route agent debug is disabled.

cp

Display the flag that indicates whether the CP debug is enabled.

on: the CP debug is enabled.
off: the CP debug is disabled.

link selection

Display the flag that indicates whether the link selection debug is enabled.

on: the link selection debug is enabled.
off: the link selection debug is disabled.


Related Commands

dbgpnni

Attributes

Log: no

State: active

Privilege: CISCO_GP


Example

Display the active PNNI debug options.

Unknown.1.1.PXM45.a > dsppnni-dbg

pnni debugging option:

hello election nbr itf timer lgn spt   node reachability
----- -------- --- --- ----- --- ---   -----------------
off   off      off off off   off off   off

address   itdb    ra    cp   link selection
-------   ----    ---   ---  --------------
off       off     off   off  off

Geneva.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

node-index

The system-generated node index indicates the relative level of the logical node within a multi-peer group on the switch. The range is 1-10. The lowest node is 1, and the highest is 10.

(Note that node index is inversely related to the node level, which you specify through such commands as cnfpnni-node, for example, and has a range of 1-104. The lowest node level is 104. When you add a logical node to the hierarchy on a switch, the system generates the node index.)

Range: 1-10
Default: 1


Objects Displayed

The following parameters are displayed for each node.

Node-index

The node index has a range of 1-10.

PGL state

OperNotPGL, OprPGL, starting, and so on.

Priority

This node's leadership priority in a peer group.

Initialization time

The number of seconds that this node delays advertising its choice of preferred PGL.

Override delay

The number of seconds that this node waits for itself to be declared the preferred PGL by unanimous agreement among its peers.

Re-election time

After losing connectivity to the current peer group leader, the number of seconds that this node waits before re-starting the process of electing a new peer group leader.

Preferred PGL

The ID of the node that should be the PGL according to the current node. This choice weighs information on leadership priorities and node IDs that it receives from the PTSEs.

PGL

The node in the peer group that has been elected PGL

Active parent
node ID

The node ID of the LGN.


Related Commands

cnfpnni-election, cnfpnni-node, dsppnni-node, dsppnni-node-list, dsppnni-summary-addr

Attributes

Log: nolog

State: active, standby

Privilege: ANYUSER


Example

Display the information about peer group leader election for all nodes in the hierarchy.

8850_NY.7.PXM.a > dsppnni-election

node index: 1
   PGL state......     OperNotPgl     Init time(sec).......        15
   Priority.......            150     Override delay(sec)..        30
                                      Re-election time(sec)        15
   Pref PGL...............56:160:47.0091810000020004c113ba75.0004c113ba75.01
   PGL....................56:160:47.0091810000020004c113ba75.0004c113ba75.01
   Active parent node id..0:0:00.000000000000000000000000.000000000000.00



node index: 2
   PGL state......       Starting     Init time(sec).......        15
   Priority.......              0     Override delay(sec)..        30
                                      Re-election time(sec)        15
   Pref PGL...............0:0:00.000000000000000000000000.000000000000.00
   PGL....................0:0:00.000000000000000000000000.000000000000.00
   Active parent node id..0:0:00.000000000000000000000000.000000000000.00 

dsppnni-idb

Display PNNI Internal Data Basedisplay 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:

If you enter dsppnni-idb with no parameters, the display shows the internal topology database of all nodes in the peer group.

If you specify a node index, the display shows the internal topology database of all nodes that are visible to the local, logical node with the specified index.

If you specify a node number, the display shows the internal topology database for a specific, remote node within the peer group. To see the valid node numbers for nodes in the peer group, first use dsppnni-node-list.

If you specify a port ID after specifying a node number, the display shows the internal topology database of that specific port on that remote node.

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.

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

Log: nolog

State: active, standby

Privilege: ANYUSER


Examples

Display the link-state information for the following:

Node index: 1

Node number: 1

Logical port ID: 16848901

Geneva.7.PXM.a > dsppnni-idb 1 -nodeNumber 1 -portId 16848901 
node index:1
   Local port id.......  16848901     Remote port id.......  16848901
   Local link index....         1     Remote link index....         1
   Local node number...         1     Remote node number...         2
   PGL node index......         0     LGN node index.......         0
   Transit restricted..       off     Complex node.........       off
   Branching restricted        on     PGL..................     false
   Ancestor............     false     Border node..........     false
   VP capable..........      true     Link type............horizontal
   Non-transit for PGL election..       off
   node id...............56:160:47.00918100000000107be92f46.00107be92f46.01
   node name.............pswmgx2-2

Geneva.7.PXM.a > 

dsppnni-inducing-uplink

Display PNNI Inducing Uplinkdisplay 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 This command applies to multi-peer groups only.


The display shows:

Child node index number

Token (if configured)

Uplink node ID—the ID of the node

Uplink ATM address

Uplink peer group ID

Routing metrics of the uplink

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:

If you specify a node index, the display shows the PNNI-inducing uplink database of a specific logical node on the switch.

If you do not specify a node index, the command displays the PNNI-inducing uplink database for each logical node on the switch.

Cards on Which This Command Runs

PXM45

Syntax

dsppnni-inducing-uplink [node-index]

Syntax Description

node-index

The node-index specifies the logical node on the switch.

Range: 1-10
Default: 1


Related Commands

None

Attributes

Log: nolog

State: active, standby

Privilege: ANYUSER


Example

Display the inducing uplink for the level whose node index is 2.

mpgses3.2.PXM.a > dsppnni-inducing-uplink 2

node index:2 
   Token................         0     Child node portId....     66560 
   Child node number....         1 
   Upnode id.............32:56:47.009181001100000000000001.003071f80e56.00 
   Upnode ATM addr.......47.009181000000003071f80e56.003071f80e56.02 
   Upnode PG id..........32:47.00.9181.0000.0000.0000.0000.00 

               CBR      RTVBR    NRTVBR   ABR      UBR 
               ------   ------   ------   ------   ------ 
      AW        10000    10000    10000    10000    10000 
      MaxCR    348207   348207   348207   348207   348207 
      AvCR     347419   347419   347419   347419   347419 
      CTD          17       17       17       17       17 
      CDV        4167    52954    52954   104912   104912 
      CLR0          8        8        8        8        8 
      CLR0+1        8        8        8        8        8

dsppnni-intf

Display PNNI Interfacedisplay the PNNI aggregation token and AW for a port.

This command displays the following information for a PNNI port:

Aggregation token.

Administrative weight (AW).

The logical port identifier assigned to the physical port identifier.

Cards on Which This Command Runs

PXM45

Syntax

dsppnni-intf <portid>

Syntax Description

portid

Identifies a PNNI physical port. The format is slot:subslot.port:subport. For a description of each field, see the section, "PNNI Format," at the beginning of the chapter.

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

Identifies a PNNI physical port. The format is slot:subslot.port:subport. For a description of each field, see the section, "PNNI Format," at the beginning of the chapter.

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-4,194,304

AW-CBR

Display the AW for constant bit rate (CBR) connections on this interface.

Range: 0-4,194,304

AW-ABR

Display the AW for available bit rate (ABR) connections on this interface.

Range: 0-4,194,304

AW-RTVBR

Display the AW for real-time variable bit rate (rt-VBR) connections on this interface.

Range: 0-4,194,304

AW-UBR

Display the AW for unspecified bit rate (UBR) connections. This option also applies to SVC ping connections.

Range: 0-4,194,304


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

Log: yes

State: active, standby

Privilege: ANYUSER


Example

Display the interface configuration for port 4:1.1:11.

SanJose.7.PXM.a > dsppnni-intf 4:1.1:11

Physical port id: 4: 1.1:11        Logical port id:   17045515
   Aggr token..........         0     AW-NRTVBR...........      5040
   AW-CBR..............      5040     AW-ABR..............      5040
   AW-RTVBR............      5040     AW-UBR..............      5040

SanJose.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.

If you specify a node index and a port ID, the command displays information about that specific PNNI link.

If you specify only a node index, the display shows all PNNI links attached to that node.

If you specify nothing, the command displays all links attached to all PNNI nodes in the network.

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.

Range: 1-10

portID

The physical PNNI port identifier.


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

dsppnni-link-selection

Attributes

Log: yes

State: active, standby

Privilege: ANYUSER


Example

Specify node index 1 and port 1:1.2:2.

p2spvc5.7.PXM.a > dsppnni-link 1 1:1.2:2

node index   :1
Local port id:  16848898          Remote port id:  16848898
Local Phy Port Id:1:1.2:2
   Type. lowestLevelHorizontalLink     Hello state....... twoWayInside
   Derive agg...........         0     Intf index...........  16848898
   SVC RCC index........         0     Hello pkt RX.........         2
                                       Hello pkt TX.........         2
   Remote node name.......p2spvc6
   Remote node
id.........56:160:47.00918100000000309409f1ef.00309409f1ef.01
   Upnode
id..............0:0:00.000000000000000000000000.000000000000.00
   Upnode ATM addr........00.000000000000000000000000.000000000000.00
   Common peer group id...00:00.00.0000.0000.0000.0000.0000.00

dsppnni-link-selection

Display PNNI Link Selectiondisplay 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

Identifies a PNNI physical port. The format is slot:subslot.port:subport. For a description of each field, see the section, "PNNI Format," at the beginning of the chapter.


Display Contents

The display shows the following information for each node.

physical port id

Identifies a PNNI physical port. The format is slot:subslot.port:subport. For a description of each field, see the section, "PNNI Format," at the beginning of the chapter.

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

Log: nolog

State: active, standby

Privilege: ANYUSER


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:11

physical port id:        4:1.1:11     link selection: minaw
 logical port id:        17045515


SanJose.7.PXM.a > 

dsppnni-mtu

Display PNNI Maximum Transfer Unitdisplay 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-mtu

Display 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.

max packet size

The value of the max transmit unit mtu in number of bytes.

Range: 1024-8192


Related Commands

dsppnni-idb, cnfpnni-mtu

Attributes

Log: nolog

State: active, standby

Privilege: ANYUSER


Example

Displays the maximum packet size.

SanJose.7.PXM.a > cnfpnni-mtu 3002

SanJose.7.PXM.a > dsppnni-mtu

max packet size : 3002



SanJose.7.PXM.a > 

dsppnni-neighbor

Display PNNI Neighbordisplay 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.

If you specify: both node-index and rmt-node-id, the command displays information about the rmt-node-id neighbors.

If you specify nothing, the command displays all neighbors attached this 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.

node-index

The system-generated node index specifies the relative level of the PNNI logical node within the hierarchy on the switch. the node identifier.

Range: 1-10

rmt-node-id

The node index for a remote node is the index assigned to a neighboring node.


Display Contents

The following parameters are displayed for each node.

node-index

The system-generated node index in the range 1-10.

node name

The name of the neighboring node (assigned through the cnfname command).

Remote node id

The PNNI logical node identifier (node ID). The node-id consists of the following logical elements, starting at the most significant byte:

The level of the PNNI node within the hierarchy. (See the description of the level parameter.)

The number of bits in the ATM address. The number is 160 for an NSAP address because the ATM address of the node is always 20 bytes. For an E.164 address, this field is decimal 15.

The ATM address portion of the peer group ID (20 8-bit, hexadecimal bytes).

Neighbor state

FULL

Port count

The number of ports.

SVC RCC index

The index for the SVC routing control channel.

RX DS pkts

The number of received signal packets in the receive direction.

TX DS pkts

The number of transmitted signal packets in the transmit direction.

RX PTSP pkts

The number of PNNI topology state packets in the receive direction.

TX PTSP pkts

The number of PNNI topology state packets in the transmit direction.

RX PTSE req pkts

The number of PNNI topology state element (PTSE) request packets in the receive direction.

TX PTSE req pkts

The number of transmitted PTSE request packets in the transmit direction.

RX PTSE ack pkts

The number of received PTSE acknowledgment packets in the receive direction.

TX PTSE ack pkts

The number of transmitted PTSE acknowledgment packets in the transmit direction.


Related Commands

None

Attributes

Log: log

State: active, standby

Privilege: ANYUSER


Example

Display information about all neighboring PNNI nodes (with no optional parameters).

Geneva.7.PXM.a > dsppnni-neighbor

node index    : 1

node name     : Paris
Remote node id: 56:160:47.00918100000000107b65f27c.00107b65f27c.01
Neighbor state: FULL
   Port count..........         4     SVC RCC index.......         0
   RX DS pkts..........         3     TX DS pkts..........         3
   RX PTSP pkts........      6032     TX PTSP pkts........      2061
   RX PTSE req pkts....         2     TX PTSE req pkts....         1
   RX PTSE ack pkts....       345     TX PTSE ack pkts....      2282

node index    : 2

node name     : SanJose
Remote node id: 56:160:47.00918100000000309409f1f1.00309409f1f1.01
Neighbor state: FULL
   Port count..........         2     SVC RCC index.......         0
   RX DS pkts..........         4     TX DS pkts..........         3
   RX PTSP pkts........     23107     TX PTSP pkts........     32978
   RX PTSE req pkts....         3     TX PTSE req pkts....         0
   RX PTSE ack pkts....     13673     TX PTSE ack pkts....     12532

Geneva.7.PXM.a >

dsppnni-node

Display PNNI Nodedisplay 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.

Cards on Which This Command Runs

PXM45

Syntax

dsppnni-node [node-index]

Syntax Description

node-index

The node-index identifies a logical node in relation to other nodes in the hierarchy. This node index applies locally within the switch.

Range: 1-10

Default: 1


Related Commands

addpnni-node, cnfpnni-node

Attributes

Log: log

State: active, standby

Privilege: ANYUSER


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

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. The lowest level node cannot be a complex node. Therefore, in a single-peer group, this field 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, disable the nod by executing 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 1

node index: 1                      node name: SanJose
   Level...............        56     Lowest..............      true
   Restricted transit..       off     Complex node........       off
   Branching restricted        on
   Admin status........        up     Operational status..        up
   Non-transit for PGL election..       off
   Node id...............56:160:47.00918100000000309409f1f1.00309409f1f1.01
   ATM address...........47.00918100000000309409f1f1.00309409f1f1.01
   Peer group id.........56:47.00.9181.0000.0000.0000.0000.00

SanJose.7.PXM.a >

dsppnni-node-list

Display PNNI Nodes Listdisplay a list of all learned PNNI nodes in the network.

The dsppnni-node-list command lists the PNNI nodes in the network attached 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:

The node number: all nodes in the network that are visible to the local node at a given level are identified by a unique number and stored in a list.

The node ID is the 22 octet that uniquely identifies the node within the routing domain. See addpnni-node or cnfpnni-node for components of the node ID.

The node level, also configured through either the addpnni-node or the cnfpnni-node command.

Node name (results from cnfname).

In a multi-peer group (MPG), the index number for nodes above the lowest level are added to the node name.


Note This display may not update frequently enough for you if you are configuring the network. You can change timers to update more frequently, but changing timers can have unexpected effects. Before you change any timers, discuss it with the TAC or your Cisco representative. The dsppnni-link command frequently updates a display of the address, link, and Hello packet information of each link.


Cards on Which This Command Runs

PXM45

Syntax

dsppnni-node-list

Syntax Description

This command takes no parameters.

Related Commands

addpnni-node, cnfpnni-node, cnfname, dsppnni-path, dsppnni-reachable-addr

Attributes

Log: log

State: active, standby

Privilege: ANYUSER


Display Contents for the dsppnni-node-list Command

This section describes the contents of a node list. It also describes how the display changes from one level of a hierarchy to a higher level. The description relates to the example of a multi-peer network diagram in Figure 5-8. Further, this diagram reflects the MPG display in the Example section. Linking the description here with the figure and the example clarifies not only the output of the dsppnni-node-list command but also MPGs in general. An example SPG list follows the MPG example.

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.

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 display shows all network nodes that are known to the lowest level. These nodes consist of all nodes in the peer group, all nodes on the level of its parent node, all nodes on the level of its grandparent, and so on. The MPG shown in the Example section illustrates this concept.

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. When the sequence re-starts with node # 1, the display has begun showing the view from the next higher node in the hierarchy. At this next higher level, node # 1 is the current node itself, which has made its own list of nodes. The display continues with peer group members of that level, the members of the parent's group, the grandparent and members of the grandparent's group, and so on. The MPG in the Example section illustrates this progression.

3. For levels above the lowest, the node index is appended to the name of the switch. See the node name column in the display for a multi-peer group in the Example section. For the definition of a node index, see the description of the dsppnni-node command.

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-list

node #  node id                                            node name    level
------- -------------------------------------------------- ---------- -------
    1   56:160:47.009181000000003071f80e4a.003071f80e4a.01 mpglax1        56

node #  node id                                            node name    level
------- -------------------------------------------------- ---------- -------
    3   48:56:47.339181000000000000000000.003071f80833.00  mpglax1-02     48

node #  node id                                            node name    level
------- -------------------------------------------------- ---------- -------
    4   40:56:47.229181000000000000000000.003071f80e52.00  mpglax4-02     40

node #  node id                                            node name    level
------- -------------------------------------------------- ---------- -------
    5   40:48:47.559181000100000000000000.003071f80833.00  mpglax1-03     40

node #  node id                                            node name    level
------- -------------------------------------------------- ---------- -------
    6   48:56:47.119181000000000000000000.003071f80e56.00  mpglax2-02     48

node #  node id                                            node name    level

------- -------------------------------------------------- ---------- -------
    1   48:56:47.339181000000000000000000.003071f80833.00  mpglax1-02     48

node #  node id                                            node name    level
------- -------------------------------------------------- ---------- -------
    2   40:48:47.559181000100000000000000.003071f80833.00  mpglax1-03     40

node #  node id                                            node name    level
------- -------------------------------------------------- ---------- -------
    3   48:56:47.119181000000000000000000.003071f80e56.00  mpglax2-02     48

node #  node id                                            node name    level
------- -------------------------------------------------- ---------- -------
    4   40:56:47.229181000000000000000000.003071f80e52.00  mpglax4-02     40

node #  node id                                            node name    level
------- -------------------------------------------------- ---------- -------
    1   40:48:47.559181000100000000000000.003071f80833.00  mpglax1-03     40

node #  node id                                            node name    level
------- -------------------------------------------------- ---------- -------
    3   40:56:47.229181000000000000000000.003071f80e52.00  mpglax4-02     40

mpglax1.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-list

node #  node id                                            node name    level 
------- -------------------------------------------------- ---------- ------- 
    1   56:160:47.009181000000001029300121.001029300121.01 pswpop6        56 

node #  node id                                            node name    level 
------- -------------------------------------------------- ---------- ------- 
    2   56:160:47.00918100000000c043002de1.00c043002de1.01 pswpop7        56 

node #  node id                                            node name    level 
------- -------------------------------------------------- ---------- ------- 
    3 56:160:47.009181000000000000000000.001029300121.00  pswpop6-02     56 

node #  node id                                            node name    level 
------- -------------------------------------------------- ---------- ------- 
    4   56:160:47.00918100000000500ffde80b.00500ffde80b.01 orses18        56 

Geneva.7.PXM.a >

dsppnni-path

Display PNNI Pathdisplay 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

Routing Metric
Applicable 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 | rtvbr}} [node-index]

Syntax Description


Note The mandatory keywords in this command do not take the usual dash that many keywords require. If you include a dash in front of the keyword, the system rejects the command.



Note The optional node-index lets you select a specific node in the network whose path connectivity you want to see. The local node creates the node indexes (or node numbers) according to the sequence that it discovers its neighbors. You can only provide it as a command parameter or view it in applicable displays. Whether or not you specify node-index, the node indexes appear in the "node#" column. (Note that this node index or node# is not the node index that identifies a node within the hierarchy of a multiple-peer group. See dsppnni-node for details on the local node index.)


aw

Specify administrative weight as the routing metric. The possible service classes associated with AW are CBR, rt-VBR, nrtVBR, and UBR.

ctd

Specify cell transfer delay as the metric. The possible service classes are CBR, rt-VBR, or nrt-VBR.

cdv

Specify cell delay variation as the metric. The possible service classes are CBR and rt-VBR.

node-index

The node index is a number in the range 1-256 that uniquely identifies a switch within a PNNI network. This option lets you specify one destination switch to show connecting paths, otherwise the paths to all switches appear in the display.

Range: 1-256
Default: 1


Display Contents

S or D

The S or D in the first column of the display shows whether the line pertains to the source (S) or begins one or more lines about the destination (D).

node #

The node number (node index) within the network. This node number is a unique identifier of the node within the network and appears as "node-index" in many displays.

Range: 1-256

PortId

The PNNI logical port identifier in the form of a 32-bit number. Certain commands require the port ID in this format. To obtain the logical port ID from the physical port ID, use the dsppnports command.

Range: 1-2147483648

node id

The node identifier (node ID) assigned to a PNNI node. The commands that specify the node ID are addpnni-node and cnfpnni-node. To see the node ID, use dsppnni-node.

node name

The name of the switch assigned by the cnfname command. This name appears in the CLI prompt.


Related Commands

None

Attributes

Log: nolog

State: active, standby

Privilege: ANYUSER


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 5
node #/PortId   node id                                            node name
--------------- -------------------------------------------------- ----------
D  5/         0 56:160:47.00918100000000309409f160.00309409f160.01 Chicago      
S  1/  17045505 56:160:47.00918100000000309409f1f1.00309409f1f1.01 SanJose      

node #/PortId   node id                                            node name
--------------- -------------------------------------------------- ----------
D  5/         0 56:160:47.00918100000000309409f160.00309409f160.01 Chicago      
S  1/  17045506 56:160:47.00918100000000309409f1f1.00309409f1f1.01 SanJose      

node #/PortId   node id                                            node name
--------------- -------------------------------------------------- ----------
D  5/         0 56:160:47.00918100000000309409f160.00309409f160.01 Chicago      
S  1/  17045507 56:160:47.00918100000000309409f1f1.00309409f1f1.01 SanJose      

node #/PortId   node id                                            node name
--------------- -------------------------------------------------- ----------
D  5/         0 56:160:47.00918100000000309409f160.00309409f160.01 Chicago      
S  1/  17045508 56:160:47.00918100000000309409f1f1.00309409f1f1.01 SanJose      

The 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 ubr
node #/PortId   node id                                            node name
--------------- -------------------------------------------------- ----------
D  2/         0 56:160:47.00918100000000309409f2aa.00309409f2aa.01 Toroton      
S  1/  17504257 56:160:47.00918100000000309409f1f1.00309409f1f1.01 SanJose      

node #/PortId   node id                                            node name
--------------- -------------------------------------------------- ----------
D  3/         0 56:160:47.00918100000000301a431c19.00301a431c19.01 Boston       
   2/  17176577 56:160:47.00918100000000309409f2aa.00309409f2aa.01 Toroton      
S  1/  17504257 56:160:47.00918100000000309409f1f1.00309409f1f1.01 SanJose      

node #/PortId   node id                                            node name
--------------- -------------------------------------------------- ----------
D  3/         0 56:160:47.00918100000000301a431c19.00301a431c19.01 Boston       
   2/  17438721 56:160:47.00918100000000309409f2aa.00309409f2aa.01 Toroton      
S  1/  17504257 56:160:47.00918100000000309409f1f1.00309409f1f1.01 SanJose      

node #/PortId   node id                                            node name
--------------- -------------------------------------------------- ----------
D  4/         0 56:160:47.00918100000000309409f23c.00309409f23c.01 London       
   3/  17111041 56:160:47.00918100000000301a431c19.00301a431c19.01 Boston       
   2/  17438721 56:160:47.00918100000000309409f2aa.00309409f2aa.01 Toroton      
S  1/  17504257 56:160:47.00918100000000309409f1f1.00309409f1f1.01 SanJose      

node #/PortId   node id                                            node name
--------------- -------------------------------------------------- ----------
D  4/         0 56:160:47.00918100000000309409f23c.00309409f23c.01 London       
   3/  16848897 56:160:47.00918100000000301a431c19.00301a431c19.01 Boston       
   2/  17176577 56:160:47.00918100000000309409f2aa.00309409f2aa.01 Toroton      
S  1/  17504257 56:160:47.00918100000000309409f1f1.00309409f1f1.01 SanJose      
node #/PortId   node id                                            node name
--------------- -------------------------------------------------- ----------
D  4/         0 56:160:47.00918100000000309409f23c.00309409f23c.01 London       
   3/  16848897 56:160:47.00918100000000301a431c19.00301a431c19.01 Boston       
   2/  17438721 56:160:47.00918100000000309409f2aa.00309409f2aa.01 Toroton 
S  1/  17504257 56:160:47.00918100000000309409f1f1.00309409f1f1.01 SanJose      

node #/PortId   node id                                            node name
--------------- -------------------------------------------------- ----------
D  5/         0 56:160:47.00918100000000309409f160.00309409f160.01 Chicago      
S  1/  17045505 56:160:47.00918100000000309409f1f1.00309409f1f1.01 SanJose      

node #/PortId   node id                                            node name
--------------- -------------------------------------------------- ----------
D  5/         0 56:160:47.00918100000000309409f160.00309409f160.01 Chicago      
S  1/  17045506 56:160:47.00918100000000309409f1f1.00309409f1f1.01 SanJose      

node #/PortId   node id                                            node name
--------------- -------------------------------------------------- ----------
D  5/         0 56:160:47.00918100000000309409f160.00309409f160.01 Chicago      
S  1/  17045507 56:160:47.00918100000000309409f1f1.00309409f1f1.01 SanJose      

node #/PortId   node id                                            node name
--------------- -------------------------------------------------- ----------
D  5/         0 56:160:47.00918100000000309409f160.00309409f160.01 Chicago      
S  1/  17045508 56:160:47.00918100000000309409f1f1.00309409f1f1.01 SanJose      


node #/PortId   node id                                            node name
--------------- -------------------------------------------------- ----------
D  6/         0 56:160:47.00918100000000309409f2a3.00309409f2a3.01 Paris        
   4/  17438721 56:160:47.00918100000000309409f23c.00309409f23c.01 London       
   3/  17111041 56:160:47.00918100000000301a431c19.00301a431c19.01 Boston       
   2/  17176577 56:160:47.00918100000000309409f2aa.00309409f2aa.01 Toroton      
S  1/  17504257 56:160:47.00918100000000309409f1f1.00309409f1f1.01 SanJose      

node #/PortId   node id                                            node name
--------------- -------------------------------------------------- ----------
D  6/         0 56:160:47.00918100000000309409f2a3.00309409f2a3.01 Paris        
   4/  17438721 56:160:47.00918100000000309409f23c.00309409f23c.01 London       
   3/  17111041 56:160:47.00918100000000301a431c19.00301a431c19.01 Boston       
   2/  17438721 56:160:47.00918100000000309409f2aa.00309409f2aa.01 Toroton      
S  1/  17504257 56:160:47.00918100000000309409f1f1.00309409f1f1.01 SanJose      

node #/PortId   node id                                            node name
--------------- -------------------------------------------------- ----------
D  6/         0 56:160:47.00918100000000309409f2a3.00309409f2a3.01 Paris        
   4/  17438721 56:160:47.00918100000000309409f23c.00309409f23c.01 London       
   3/  16848897 56:160:47.00918100000000301a431c19.00301a431c19.01 Boston       
   2/  17176577 56:160:47.00918100000000309409f2aa.00309409f2aa.01 Toroton      
S  1/  17504257 56:160:47.00918100000000309409f1f1.00309409f1f1.01 SanJose      

node #/PortId   node id                                            node name
--------------- -------------------------------------------------- ----------
D  6/         0 56:160:47.00918100000000309409f2a3.00309409f2a3.01 Paris        
   4/  17438721 56:160:47.00918100000000309409f23c.00309409f23c.01 London       
   3/  16848897 56:160:47.00918100000000301a431c19.00301a431c19.01 Boston       
   2/  17438721 56:160:47.00918100000000309409f2aa.00309409f2aa.01 Toroton      
S  1/  17504257 56:160:47.00918100000000309409f1f1.00309409f1f1.01 SanJose      
node #/PortId   node id                                            node name
--------------- -------------------------------------------------- ----------
D  7/         0 56:160:47.00918100000000001a531c01.00001a531c01.01 LA           
  11/  16848918 56:160:47.00918100000000001a531c83.00001a531c83.01 Jup-1        
   3/  16848917 56:160:47.00918100000000301a431c19.00301a431c19.01 Boston       
   2/  17176577 56:160:47.00918100000000309409f2aa.00309409f2aa.01 Toroton      
S  1/  17504257 56:160:47.00918100000000309409f1f1.00309409f1f1.01 SanJose      

node #/PortId   node id                                            node name
--------------- -------------------------------------------------- ----------
D  7/         0 56:160:47.00918100000000001a531c01.00001a531c01.01 LA           
  11/  16848918 56:160:47.00918100000000001a531c83.00001a531c83.01 Jup-1 
   3/  16848917 56:160:47.00918100000000301a431c19.00301a431c19.01 Boston       
   2/  17438721 56:160:47.00918100000000309409f2aa.00309409f2aa.01 Toroton      
S  1/  17504257 56:160:47.00918100000000309409f1f1.00309409f1f1.01 SanJose      

node #/PortId   node id                                            node name
--------------- -------------------------------------------------- ----------
D  8/         0 56:160:47.00918100000000309409f213.00309409f213.01 A4b          
   7/  16848897 56:160:47.00918100000000001a531c01.00001a531c01.01 LA           
  11/  16848918 56:160:47.00918100000000001a531c83.00001a531c83.01 Jup-1        
   3/  16848917 56:160:47.00918100000000301a431c19.00301a431c19.01 Boston       
   2/  17176577 56:160:47.00918100000000309409f2aa.00309409f2aa.01 Toroton      
S  1/  17504257 56:160:47.00918100000000309409f1f1.00309409f1f1.01 SanJose      


SanJose.7.PXM.a >

dsppnni-pkttrace

Display Packet Tracedisplay 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 This command is very intrusive. If you execute it while the node carries live traffic, Cisco recommends that you specify one direction at a time for the trace.


Cards on Which This Command Runs

PXM45

Syntax

dsppnni-pkttrace <rx | tx> [node-index [ -portId port-id | -svcIndex svc-index]]

Syntax Description

tx | rx

Select a direction for the trace to display.

tx: transmit
rx: receive

node-index

The node index indicates the relative level of the logical node within a multi-peer group on the switch. The range is 1-10, and the lowest level is 1.)

Range: 1-10
Default: 1

-portId

The port ID in this instance has the format of the logical ID number. The format is a 32-bit encoded number in the range 1-2147483648. If you do not have the port ID in this form, use dsppnport and provide it with the common portID format of slot:subslot.port:subport. The output of dsppnport shows the logical number for the port ID. Use this value is for the -portID parameter.

Range: 1-2147483648

-svcIndex

An index of the switched virtual connection routing control channel (SVCC-RCC) packet trace. This parameter is meaningful only if you specify node-index.

Default: none


Related Commands

cnfpnni-pkttrace

Attributes

Log: nolog

State: active

Privilege: CISCO_GP


Example

First, configure the following packet trace parameters through cnfpnni-pkttrace:

The direction is transmit.

The node index is 1.

The port identifier is 17373186.

Next, check the packet trace you have configure by executing dsppnni-pkttrace.

Geneva.7.PXM.a > cnfpnni-pkttrace -tx 17373186 
PNNI/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 17373186

Node Index :1   Port id:        17504   Tx Pkt Trace on

Geneva.7.PXM.a >

dsppnni-ptse

Display PNNI topology state elementdisplays 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. Nodal information group

2. Internal reachable addresses

3. External reachable addresses

4. Horizontal links

5. Uplinks (multiple peer groups only)

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:

Nothing, the display contains header information for all PTSEs for all logical nodes in the network.

Only the node-index, the output contains all PTSEs sent from the node indicated by node-index.

Only node-index, node-id, and ptse-id, the display shows the PTSE uniquely identified by these three parameters.

A detailed display, the display contains information about the header and the contents of the PTSE and applies to all combinations of the other parameters.


Note The node-index is automatically generated. See description of dsppnni-node-list.

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 The parameters node-index, node-id, and ptse-id are nested. Therefore, you cannot enter node-id without node-index, nor can you enter ptse-id without node-index and node-id.


node-index

A unique, network-wide node identifier. This system-generated number has a range of 1-256.

Range: 1-256.
Default: (no default)

node-id

The user-specified node ID. See addpnni-node or cnfpnni-node for a description.

Default: (no specific node ID)

ptse-id

An integer that identifies a PTSE generated by a particular node. Regardless of the number of times a node sends a PTSE, this ID remains the same until a change to the topology occurs. For example, adding a ATM address to a node causes that node to generate a new PTSE and associated ID.

The PTSE ID has a theoretical limit of a 32 bit number. However, the PTSE ID is likely to be a relatively small number.

-detail

Selects the amount of detail for the display.

true: Display the contents of the PTSE as well as the header information.
false: Display only the PTSE header.

Default: false


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.

Nodal State Parameter Information

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.

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").

Nodal Information Group Parameters

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.

next higher level binding information IG type

The next higher level binding information IG type is an ASCII string.

next higher level binding information IG length

A 16-bit number.

parent LGN id

The parent LGN ID is a 22-byte hex string.

parent LGN ATM address

The parent LGN ATM address is a 20-byte, hex string.

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.

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.

Nodal State IG Parameters

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 the "PNNI Format" section.

Range: 1-2147483648

output port id

The logical PNNI identifier on the output interface. For more details, see the "PNNI Format" section.

Range: 1-2147483648

Internal Reachable ATM Address IG Parameters

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 the "PNNI Format" section.

Range: 1-2147483648

scope

The UNI 4.0 address scope.

Range: 1-15, where:

1 = LocalNetwork
2 = LocalNetworkPlusOne
3 = LocalNetworkPlusTwo
4 = SiteMinusOne
5 = IntraSite
6 = SitePlusOne
7 = OrganizationMinusOne
8 = IntraOrganization
9 = OrganizationPlusOne
10 = CommunityMinusOne
11 = IntraCommunity
12 = CommunityPlusOne
13 = Regional
14 = InterRegional
15 = Global

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.

External Reachable ATM Address IG Parameters

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.

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.

Horizontal Links IG Parameters

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 the "PNNI Format" section.

Range: 1-2147483648

local port id

The logical PNNI identifier on the local interface. For more details, see the "PNNI Format" section.

Range: 1-2147483648

aggregation token

See the description of the cnfpnni-intf command for a definition of an aggregation token.

Range: 1-32

Uplink IG Parameters

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 the "PNNI Format" section.

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

Resource Availability IG Parameters

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.

Generic Connection Admission Control (GCAC) IG

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 require support for CRM, and Cisco Systems currently does not support it on the Cisco MGX 8850, MGX 8950, 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 require support for VF, and Cisco Systems currently does not support it on the Cisco MGX 8850, MGX 8950, and SES products.

Range: 1-2147483648.


Related Commands

None

Attributes

Log: nolog

State: active, standby

Privilege: ANYUSER


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 true
node index: 1
originating node name: Krishna
originating node id: 56:160:47.0091810000000000c0326496.0000c0326496.00
Type................ 64 Length.............. 1200
Sequence number..... 1 Checksum............ 94d
PTSE id............. 1 Remaining lifetime.. 2997
PTSE type........... Nodal Info( 97)
Type................ 97 Length.............. 65
Priority............ 0 Flags............... f8
ATM addr..............47.0091810000000000c0326496.0000c0326496.00
Pref PGL id...........0:0:00.000000000000000000000000.000000000000.00
binding info: Type 192, Length 76
next level LGN node id. 48:56:47.009181000000000000000000.0000c0326496.00
next level LGN ATM addr 47.0091810000000000c0326496.0000c0326496.30
next level LGN PG id... 30:47.00.9181.0000.0000.0000.0000.00
next level LGN PGL id.. 30:48:56:47.009181000000000000000000.0000c0326496.00
node index: 1
originating node name: Liz
originating node id: 56:160:47.0091810000000000c0326496.0000c0326496.00
Type................ 64 Length.............. 1200
Sequence number..... 1 Checksum............ 94d
PTSE id............. 2 Remaining lifetime.. 2997
PTSE type........... Nodal State Parameter( 96)
Type................ 96 Length.............. 65
Reserved............ 0 Flags............... 0
Input port id....... 48 Output port id...... 12

For the second example, specify the following parameters:

The node-index is 1.

The node-id is 56:160:47.00918100000000107b65f27c.00107b65f27c.01.

The PTSE ID is 28.

Display the PTSEs for node index 2. After listing the PTSEs, display details for one particular PTSE—19 in this example.


Note The presence of the colons in the node ID are required, but the periods are optional.


M8850_NY.7.PXM.a > dsppnni-ptse 2

node index: 2
originating node name: M8850_NY-02 
originating node id: 48:56:47.009181000002000000000000.00036b5e30cd.00
   Type................        64     Length..............        96
   Sequence number.....       155     Checksum............      689b
   PTSE id.............         1     Remaining lifetime..      3224
   PTSE type...........  Nodal Info( 97)

node index: 2
originating node name: M8850_NY-02 
originating node id: 48:56:47.009181000002000000000000.00036b5e30cd.00
   Type................        64     Length..............        44
   Sequence number.....       153     Checksum............      d7fd
   PTSE id.............        18     Remaining lifetime..      3224
   PTSE type...........  Int Reach Addr(224)

node index: 2
originating node name: M8850_NY-02 
originating node id: 48:56:47.009181000002000000000000.00036b5e30cd.00

Type................        64     Length..............        52
   Sequence number.....       152     Checksum............       bba
   PTSE id.............        19     Remaining lifetime..      3224
   PTSE 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 true

node index: 2
originating node name: M8850_NY-02 
originating node id: 48:56:47.009181000002000000000000.00036b5e30cd.00
   Type................        64     Length..............        52
   Sequence number.....       152     Checksum............       bba
   PTSE id.............        19     Remaining lifetime..      2389
   PTSE type...........  Int Reach Addr(224)

   Type................       224     Length................        32
   Reserved............         0     Flags.................      8000
   Port id.............         1     Scope.................         0
   Ail.................        14     Aic...................         1
   prefix..............47.0091.8100.0000.0003.6b5e.30cd./104

dsppnni-reachable-addr

Display PNNI Reachable Addressesdisplays 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:

If you enter local, the display shows the port ID and the addresses directly attached to the local node.

If you enter network, the display shows the advertising node ID, the addresses advertised by other nodes, and the routing parameters for each reachable node.


Note The display may not update frequently enough if you are configuring the network. You can change timers to update more frequently, but changing timers can have unexpected effects. Before you modify a timer, discuss it with the TAC or your Cisco representative.


Cards on Which This Command Runs

PXM45

Syntax

dsppnni-reachable-addr <local | network>

Syntax Description

local | network

Determine whether the display shows the addresses of nodes that directly connect to this switch or all nodes in the peer group.

Local: directly connected switches
Network: all reachable nodes in the peer group

Default: (no default)


Display Contents for dsppnni-reachable-addr

The table contains all reachable addresses within a peer group comes from the internal data base (IDB).

scope


Note The UNI 4.0 address scope. Refer to ATM forum documentation for a description of these scopes.


Range: 1-15, where:

1 = LocalNetwork
2 = LocalNetworkPlusOne
3 = LocalNetworkPlusTwo
4 = SiteMinusOne
5 = IntraSite
6 = SitePlusOne
7 = OrganizationMinusOne
8 = IntraOrganization
9 = OrganizationPlusOne
10 = CommunityMinusOne
11 = IntraCommunity
12 = CommunityPlusOne
13 = Regional
14 = InterRegional
15 = Global

port id

The logical port identifier.

Exterior

The flag that indicates whether the node is an interior or exterior node.

true: the node is an exterior node.
false: the node is an interior node.

ATM addr prefix

The PNNI summary address assigned to the node.

node name

The name of the switch results from the cnfname command and appears in the CLI prompt.

Advertising node
number

The number of the remote node that has advertised information to the current node. This number has a range of 1-256 and appears only if you specified the network argument.

The local node generates the node numbers in the sequence that it discovers its neighbors. You can only provide it as a command parameter or view it in applicable displays. (Note that this node index or node number is not the node index that identifies a node within the hierarchy of a multiple-peer group. See dsppnni-node for details on the local node index.)

Transit Network ID

The transit network ID identifies a network where connections from the current node do not terminate.This number applies to static addresses only. The application of this option depends on the design intent of the user. The ID can have up to four IA5 characters (IA5 is a superset of the ASCII character set).


Related Commands

dsppnni-link

Attributes

Log: nolog

State: active, standby

Privilege: ANYUSER


Examples

Display the reachable addresses that directly connect to this node: the parameter is local.

Geneva.7.PXM.a > dsppnni-reachable-addr local

scope...............         0     port id.............4294967295
Exterior............     false
ATM addr prefix.....47.0091.8100.0000.0030.ff0f.ef38.0000.010b.180b/152

scope...............         0     port id.............4294967295
Exterior............     false
ATM addr prefix.....47.0091.8100.0000.0030.ff0f.ef38.0000.010b.1816/152

scope...............         0     port id.............4294967295
Exterior............     false
ATM addr prefix.....47.0091.8100.0000.0030.ff0f.ef38.0000.010b.1820/152

scope...............         0     port id.............4294967295
Exterior............     false
ATM addr prefix.....47.0091.8100.0000.0030.ff0f.ef38.0000.010b.1821/152

scope...............         0     port id.............4294967295
Exterior............     false
ATM addr prefix.....47.0091.8100.0000.0030.ff0f.ef38.0000.010d.1820/152

scope...............         0     port id.............4294967295
Exterior............     false
ATM addr prefix.....47.0091.8100.0000.0030.ff0f.ef38.0000.010d.1821/152

scope...............         0     port id.............4294967295
Exterior............     false
ATM addr prefix.....47.0091.8100.0000.0030.ff0f.ef38.0000.010d.1822/152

Display 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 network
 
scope...............         0     Advertising node number        13
Exterior............     false
ATM addr prefix.....47.0091.8100.0000.0010.7b65.f27c/104
Advertising nodeid..56:160:47.00918100000000309409f13f.00309409f13f.01
Node name...........Moscow
                        forward direction
            CBR    RTVBR   NRTVBR      ABR      UBR
         ------   ------   ------   ------   ------
AW         5040     5040     5040     5040     5040
MaxCR    351500   351500   351500   351500   351500
AvCR     290935   290935   290935   290935   290935
CTD          41       41       41      n/a      n/a
CDV          10       10      n/a      n/a      n/a
CLR0         10        8        6      n/a      n/a
CLR0+1        8        8        8      n/a      n/a
CRM         n/a      n/a      n/a      n/a      n/a
VF          n/a      n/a      n/a      n/a      n/a
 
                        backward direction
            CBR    RTVBR   NRTVBR      ABR      UBR
         ------   ------   ------   ------   ------
AW         5040     5040     5040     5040     5040
MaxCR    351500   351500   351500   351500   351500
AvCR     290935   290935   290935   290935   290935
CTD          41       41       41      n/a      n/a
CDV          10       10      n/a      n/a      n/a
CLR0         10        8        6      n/a      n/a
CLR0+1        8        8        8      n/a      n/a
CRM         n/a      n/a      n/a      n/a      n/a
VF          n/a      n/a      n/a      n/a      n/a
 
scope...............         0     Advertising node number         8
Exterior............     false
ATM addr prefix.....47.0091.8100.0000.0010.7b65.f27c/104
Advertising nodeid..56:160:47.00918100000000107b65f27c.00107b65f27c.01
Node name...........Paris
 
 
scope...............         0     Advertising node number         8
Exterior............      true
ATM addr prefix.....47.0091.8100.0000.0030.9409.f13f/104
Advertising nodeid..56:160:47.00918100000000107b65f27c.00107b65f27c.01
Node name...........Paris
 
                        forward direction
            CBR    RTVBR   NRTVBR      ABR      UBR
         ------   ------   ------   ------   ------
AW         5040     5040     5040     5040     5040
MaxCR    351500   351500   351500   351500   351500
AvCR     290935   290935   290935   290935   290935
CTD          41       41       41      n/a      n/a
CDV          10       10      n/a      n/a      n/a
CLR0         10        8        6      n/a      n/a
CLR0+1        8        8        8      n/a      n/a
CRM         n/a      n/a      n/a      n/a      n/a
VF          n/a      n/a      n/a      n/a      n/a
 
                        backward direction
            CBR    RTVBR   NRTVBR      ABR      UBR
         ------   ------   ------   ------   ------
AW         5040     5040     5040     5040     5040
MaxCR    351500   351500   351500   351500   351500
AvCR     290935   290935   290935   290935   290935
CTD          41       41       41      n/a      n/a
CDV          10       10      n/a      n/a      n/a
CLR0         10        8        6      n/a      n/a
CLR0+1        8        8        8      n/a      n/a
CRM         n/a      n/a      n/a      n/a      n/a
VF          n/a      n/a      n/a      n/a      n/a

Geneva.7.PXM.a >

dsppnni-routing-policy

Display PNNI Routing Policydisplay 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:

The tolerance of cost-calculations.

The frequency of routing table generation.

The type of load balancing that is specified.

The type of on-demand routing that is specified.

The type of administration weight table that is enabled.


Caution You can change the routing policies to optimize PNNI routing for your network, but incorrect routing policies can cripple or even crash a network. You should not change routing policies on a live network. Use this command only after careful planning.

Cards on Which This Command Runs

PXM45

Syntax

dsppnni-routing-policy

Display Contents

This section lists the displayed information for each node. The display shows the configuration that results from cnfpnni-routing-policy.

SPT epsilon

This parameter is meaningful primarily for crankback. The epsilon you supply specifies a tolerance in the form of a percent that can influence which paths qualify as equal-cost during route calculation. A higher tolerance results in a broader range of path cost-values that can qualify as equal-cost. If two paths have very similar administrative weights (AWs), a large enough tolerance eliminates equal-cost as a routing factor because the routing algorithm regards the costs as equal.

The range of 0-20 for this parameter comes from the ATM Forum PNNI specification. However, the percent of tolerance that the numbers dictate is determined by individual vendors. Cisco Systems currently maps the following percentages on a switch:

0: the total AWs along both directions of the path must be identical.
1-2: the total AWs along both directions of the path must be within 1.06%
3-4: the total AWs along both directions of the path must be within 3.125%
5-9: the total AWs along both directions of the path must be within 6.25%
10-15: the total AWs along both directions of the path must be within 12.5%
16-20: the total AWs along both directions of the path must be within 25.0%

Range: 0-20
Default: 0, so only identical path-cost values qualify as equal-cost

Load balance

A load balancing rule applies when alternative, equal-cost routes exist for a given call request. The characteristics of the possible rules ("random" and "maxbw") are as follows:

random: requires the least overhead due to minimal calculation. The random rule is best when the possible paths have similar available bandwidth.

maxbw: requires the most overhead due to ongoing comparison of available bandwidth on paths. The maxbw rule is best when the possible paths have dissimilar or fluctuating bandwidth.

SPT holddown time

The minimum time between consecutive calculations that generate routing tables.

Units: 100 millisecond increments
Range: 1-600 (0.1-60 seconds)

On demand routing

The current rule for on-demand routing is firstfit or bestfit.

The firstfit routing policy selects the first route found that goes to the destination. The time for finding a route is the least possible, but the optimal route may not be selected.

The bestfit policy selects a route based on:

The least-cost route, where the sum of all administrative weights in both directions of the route must be less than maxCost.

Link verification.

Path constraint checks.

Avoidance of blocked nodes and links.

Checking limits in the designated transit list (DTL).

SPT path holddown
time

The minimum time that can elapse between consecutive calculations that generate routing tables on border nodes.

Units: 100 milliseconds.
Range: 1 (0.1 seconds)-600 (60 seconds).

AW Back-
ground Table

The flag that enables or disables administrative weight (AW) for the background routing table. The AW is the cost to traffic that traverses that path. The metric AW can be specified on the interface and by the service class (or QoS class), and it is associated with each link. 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, such as defining a backup link for use only when there is no available bandwidth on the primary link.

The AW for a path is the sum of all AWs at each port egress for both directions on the path.

CTD Back-
ground Table

The flag that enables or disables cell transfer delay (CTD) for the background routing table. CTD is the time interval between a cell exiting source node and entering the destination node.

CDV Back-
ground Table

The flag that enables or disables cell delay variation (CDV) for the background routing table. CDV is a component of cell transfer delay, and is a quality of service (QoS) delay parameter associated with CBR and VBR service. Cell Delay Variation is the variation of delay between cells, measured peak to peak.


Related Commands

cnfpnni-routing-policy

Attributes

Log: nolog

State: active, standby

Privilege: ANYUSER


Example

Display the parameters associated with the current routing policy for this node.

Geneva.7.PXM.a > dsppnni-routing-policy

   SPT epsilon.........         0     Load balance........    random
   SPT holddown time...         1     On demand routing...  best fit
   SPT path holddown time       2     AW Background Table         on
   CTD Background Table        on     CDV Background Table        on

Geneva.7.PXM.a >

dsppnni-scope-map

Display Scope Mapdisplay the PNNI scope map table.

The dsppnni-scope-map command displays the table that maps UNI 4.0 scope to PNNI hierarchy level.

Cards on Which This Command Runs

PXM45

Syntax

dsppnni-scope-map

Objects Displayed:

Displays the entire scope map table.

1 = LocalNetwork
2 = LocalNetworkPlusOne
3 = LocalNetworkPlusTwo
4 = SiteMinusOne
5 = IntraSite
6 = SitePlusOne
7 = OrganizationMinusOne
8 = IntraOrganization
9 = OrganizationPlusOne
10 = CommunityMinusOne
11 = IntraCommunity
12 = CommunityPlusOne
13 = Regional
14 = InterRegional
15 = Global

Related Commands

cnfpnni-scope-map

Attributes

Log: nolog

State: active

Privilege: ANYUSER


Example

This example shows the dsppnni-scope-map command line that displays the scope map table if UNI 4.0 is supported.

Geneva.7.PXM.a > dsppnni-scope-map

UNI  Scope                Pnni Routing Level
----------------------    ------------------
LocalNetwork(1)                           56
LocalNetworkPlusOne(2)                    56
LocalNetworkPlusTwo(3)                    56
SiteMinusOne(4)                           40
IntraSite(5)                              40
SitePlusOne(6)                            32
OrganizationMinusOne(7)                   32
IntraOrganization(8)                      24
OrganizationPlusOne(9)                    24
CommunityMinusOne(10)                     24
IntraCommunity(11)                         8
CommunityPlusOne(12)                       8
Regional(13)                               0
InterRegional(14)                          0
Global(15)                                 0

Geneva.7.PXM.a >

dsppnni-spoke

Display PNNI Spoke—display the PNNI complex node default advertisement values.


Note This debugging command does not apply to single-peer groups.


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.

nodal aggregation method

The ASCII string of the active aggregation method. The method is full-meshed or spanning tree.

ptse-id

The unique identifier for the PTSE. ptse-id is assigned by the PNNI node that created the PTSE.

node-index

The node-index is the local node index and has a range of 1-10.

Range: 1-10.

AW-NRTVBR

The administrative weight for nrt-VBR connections on this interface.

Range: 0-4,194,304

AW-CBR

The administrative weight for 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-4,194,304

AW-ABR

The administrative weight for available bit rate (ABR) connections on this interface.

Specify the 24 bit number AW for ABR on this interface.

Range: 0-4,194,304

AW-RTVBR

The administrative weight for rt-VBR connections on this interface.

Range: 0-4,194,304

AW-UBR

The administrative weight used for unspecified bit rate (UBR) connections. This category includes switched virtual connection (SVC) ping connections.

Range: 0-4,194,304


Related Commands

None

Attributes

Log: nolog

State: active, standby

Privilege: ANYUSER


Example

Display the spoke mapping for LGN 56:160:47.00918100000000309409f1f1.00309409f1f1.0.

SanJose.7.PXM.a > dsppnni-spoke 56:160:47.00918100000000309409f1f1.00309409f1f1.0
node index: 1
  Ptse id ............      948      Flags................ a3
  Nodal aggregation method.. spanning tree

           CBR    RTVBR   NRTVBR      ABR      UBR
        ------   ------   ------   ------   ------
AW        5040     5040     5040     5040     5040
MCR          0        0        0        0        0
AvCR    100000   100000   100000   100000   100000
CTD          0        0        0        0        0
CDV          0        0        0        0        0
CLR          0        0        0        0        0 0
CLR0+1       0        0        0        0        0
CRM         10       10       10       10       10
VF           5        5        5        5        5

SanJose.7.PXM.a > 

dsppnni-summary-addr

Display PNNI Summary Addressdisplay the PNNI summary addresses.

The dsppnni-summary-addr command displays all summary addresses at the specified degree of granularity.

If you specify node-index, the command displays the PNNI summary addresses of the node-index PNNI node.

If you do not specify node-index, the command displays PNNI summary addresses for all local nodes on network.

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.

Range: 1-10.
Default = 1.


Display Contents

node index

The number of the node within the hierarchy on this switch. The range for a multi-peer group is 1-10. For a single-peer group, the only node index is 1.

Type

Display the value of the argument -type—whether the kind of PNNI summary address is internal or external.

internal: This PNNI summary address includes only addresses that are within the peer group.
exterior: This PNNI summary address includes addresses that are outside of the peer group.

Suppress

Display the value of the argument -suppress—whether the node PNNI summary address is advertised or suppressed.

false: The PNNI summary address is advertised (is not suppressed).
true: The PNNI summary address is not advertised (is suppressed).

State

This system-generated ASCII string indicates the advertisement state.

Possible states: "advertising," "notadvertised," or "inactive"

Summary address

The ATM PNNI summary address assigned to the network. The default is a combination of the peer group id appended with the switch MAC address.

prefixlength

The length of the summary address-prefix in number of bits, equal or less than 152 bits. In the current release, the zero-length PNNI summary address is not supported.


Related Commands

addpnni-summary-addr, delpnni-summary-addr

Attributes

Log: nolog

State: active, standby

Privilege: ANYUSER


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-addr

node index: 1
   Type..............    internal     Suppress..............   false
   State............. advertising
   Summary address........47.0091.8100.0000.0030.ff0f.ef38/104

node index: 1
   Type..............    internal     Suppress..............   false
   State.............    inactive
   Summary address........47.0091.8100.0000.0010.7b65.f260/104

Geneva.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:

Both node-index and svc-index, the display shows information about an SVCC-based RCC.

Only node-index, the display shows all SVC-based RCCs attached to the svc-index node.

Nothing, the display shows all SVC-based RCCs attached to all PNNI nodes in the network.

Cards on Which This Command Runs

PXM45

Syntax

dsppnni-svcc-rcc [node-index [svc-index]]

Syntax Description

node-index

This system-generated indicates the relative position of a logical node within a hierarchy. It has a range of 1-10. For a single-peer group, the only value for node-index is 1

Range: 1-10
Default: 1

svc-index

PNNI uses the SVC index as a reference to the horizontal link (H-link) between the levels in a multi-peer group. An SVC serves as the connection for an H-link.


Display Contents

The dsppnni-svcc-rcc command displays node, Hello packet, and SVC information for each RCC.

Related Commands

None

Attributes

Log: nolog

State: active, standby

Privilege: ANYUSER


Example

This example shows the dsppnni-svcc-rcc command line that displays SVC-based RCCs.

Geneva.7.PXM.a > dsppnni-svcc-rcc 
node index: 1 svc index: 33
Hello pkt RX........ 34 SVCC VPI............ 34
Hello pkt TX........ 34 SVCC VCI............ 128
Hello state........... 2wayOutside
Remote node id.........56:160:39.840f80113744000000400202.00107b0efe01.00
Remote node ATM addr...39:840f.8011.3744.0000.0040.0102.4000.0c80.8030.00
node index: 2 svc index: 33
Hello pkt RX........ 34 SVCC VPI............ 34
Hello pkt TX........ 34 SVCC VCI............ 128
Hello state............2wayOutside
Remote node id.........56:160:39.840f80113744000000400202.00107b0efe01.00
Remote node ATM addr...39:840f.8011.3744.0000.0040.0102.4000.0c80.8030.00

Geneva.7.PXM.a > 

mpgses1.2.PXM.a > dsppnni-svcc-rcc

node index: 2                      svc index: 1         
   Hello pkt RX........        68     SVCC VPI............         1
   Hello pkt TX........        67     SVCC VCI............        35
   Hello state............twoWayInside 
   Remote node id.........48:56:47.009181000000000000000022.003071f80e56.00
   Remote node ATM addr...47.009181000000003071f80e56.003071f80e56.02


node index: 3                      svc index: 2         
   Hello pkt RX........        57     SVCC VPI............         1
   Hello pkt TX........        54     SVCC VCI............        36
   Hello state............twoWayInside 
   Remote node id.........40:56:47.009181000000000000000033.003071f80e52.00
   Remote node ATM addr...47.009181000000003071f80e52.003071f80e52.02

dsppnni-svcc-rcc-timer

Display PNNI Switched Virtual Connection Routing Control Channel (SVCC-RCC) Timer Valuesdisplay 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 This command applies to multi-peer groups only.


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.

Range: 1-10
Default: 1


Display Contents

The following parameters are displayed for each node.

node-index

The local node identifier within the hierarchy. The range is 1-10.

Range: 1-10

Init time

Display the value of -initTime—the interval (in sec) that this node delays advertising its choice of a preferred SVCC to a neighbor with a numerically lower ATM address, The interval begins when the SVCC is established.

Range: 1-10

Retry time

Displays the interval (in sec) this node will delay after an apparently necessary and viable SVCC-based RCC is unexpectedly torn down, before attempting to re-establish it.

Range: 10-60

Calling party

integrity time

Display the value of callingIntegrityTime, which limits wait times for establishing an SVCC as a called party. After the node has decided to accept an SVCC as the called party, the calledIntegrityTime variable specifies the interval (in sec) that this node will wait for an SVCC to become fully established before giving up and tearing down the connection.

Range: 5-300

Called party

integrity time

Display the value of calledIntegrityTime, which limits wait times for establishing an SVCC as a called party. After the node has decided to accept an SVCC as the called party, the calledIntegrityTime variable specifies the interval (in sec) that this node will wait for an SVCC to become fully established before giving up and tearing down the connection.

Range: 10-300


Related Commands

dsppnni-svcc-rcc-timer

Attributes

Log: nolog

State: active, standby

Privilege: ANYUSER


Example

Show any SVCC-based RCC timer values (enter the command without a specific node index).

Geneva.7.PXM.a > dsppnni-svcc-rcc-timer 
node index: 1
Init time.............. 4 Retry time............. 35
Calling party integrity time... 35
Called party integrity time.... 50

Geneva.7.PXM.a > 

dsppnni-timer

Display PNNI Timerdisplay 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

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.

Range: 1-10
Default: 1


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.

node index

The relative position of the local node on the switch.

Hello holddown

The initial value for the Hello hold down timer is the time a node waits to send Hello packets.

Units: 100 milliseconds (1 = 0.1 seconds)

PTSE holddown

The time the node waits to broadcast PNNI topology statement elements (PTSEs).

Hello int

The initial time in millisecond-increments that the node uses to limit the rate of at which it transmits Hello packets.

Units: 100 milliseconds (1 = 0.1 seconds)

PTSE refresh int

The initial number of seconds allowed for the PTSE to re-originate.

Hello inactivity 
factor

The Hello inactivity factor figures in the generation of a time period that a neighbor is considered alive after the local receives the last Hello packet from that neighbor. This period is in seconds and is the product of the hello-inactivity-factor and the peer-neighbor hello-interval.

PTSE lifetime factor

The value for the lifetime multiplier is a percentage. The switch uses it to generate the initial value for the remaining lifetime of a self-created PTSE. This remaining lifetime is the product of the PTSE lifetime factor and the PTSE-refresh-interval.

Retransmit int

The number of seconds between re-transmissions of unacknowledged DS, PTSE request, and PTSP.

AvCR proportional PM

The proportional multiplier is a percent that used in the algorithms that determine significant change for AvCR parameters.

CDV PM multiplier

The proportional multiplier is a percent that is used in the algorithms that determine significant change for peak-to-peak cell delay variation (CDV).

AvCR minimum
threshold

The minimum threshold is a percent that is used in the algorithms that determine significant change for AvCR parameters.

CTD PM multiplier

This proportional multiplier is a percent that is used in the algorithms that determine significant change for cell transfer delay (CTD) parameters.

Peer delayed ack int

The minimum interval between transmissions of delayed PTSE acknowledgment packets appears as 100-millisecond increments.

Units: 100 ms.

Logical horizontal link
inactivity time

The value of -horizontalLinkInactivityTime.


Related Commands

cnfpnni-timer

Attributes

Log: nolog

State: active, standby

Privilege: ANYUSER


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 1
node index: 1
Hello holddown(100ms)... 120 PTSE holddown(100ms)... 120
Hello int(sec).......... 15 PTSE refresh int(sec).. 1800
Hello inactivity factor. 5 PTSE lifetime factor... 200
Retransmit int(sec)..... 5
AvCR proportional PM.... 3 CDV PM multiplier...... 25
AvCR minimum threshold.. 50 CTD PM multiplier...... 50
Peer delayed ack int(100ms)................... 10
Logical horizontal link inactivity time(sec).. 10

Geneva.7.PXM.a >