Specifications

8-51
Cisco MGX 8800/8900 Series Software Configuration Guide
Release 5.1, Part Number OL-6482-01, Rev. A0, January 25, 2005
Chapter 8 Managing PNNI Nodes and PNNI Routing
Displaying Node Configuration Information
Displaying Routing Policy Parameters
Enter the dsppnni-timer command to display the routing policy parameters.
mgx8830a.1.PXM.a > dsppnni-timer
The following example shows the report for this command:
mgx8830a.1.PXM.a > dsppnni-timer
node index: 1
Hello holddown(100ms)... 10 PTSE holddown(100ms)... 10
Hello int(sec).......... 15 PTSE refresh int(sec).. 1800
Hello inactivity factor. 5 PTSE lifetime factor... 200
Retransmit int(sec)..... 5
AvCR proportional PM.... 50 CDV PM multiplier...... 25
AvCR minimum threshold.. 3 CTD PM multiplier...... 50
Peer delayed ack int(100ms)................... 10
Logical horizontal link inactivity time(sec).. 120
Displaying the SVCC RCC Table
Enter the dsppnni-svcc-rcc command to display the PNNI SVCC RCC Table.
mgx8830a.1.PXM.a > dsppnni-svcc-rcc [node-index] [svc-index]
If you specify both the node-index and the svc-index, the command displays information about an
SVCC-based RCC. If you specify only node-index, the command displays all SVC-based RCCs attached
to the svc-index node. If you specify no options, the command displays all SVC-based RCCs attached
to all PNNI nodes on this WAN as shown in the following example.
Table 8-19 Objects Displayed for the dsppnni-svcc-rcc-timer Command
Parameter Description
node-index The node index assigned to a PNNI logical node on a network. The range
is from 1 to 65535.
Init time The amount of time (in seconds) this node will delay advertising its
choice of preferred an SVCC to a neighbor with a numerically lower
ATM address, after determining that such an SVCC should be
established. The range is from 1 to 10.
Retry time The amount of time (in seconds) this node will delay after an apparently
still necessary and viable SVCC-based RCC is unexpectedly torn down,
before attempting to re-establish it. The range is from 10 to 60.
Calling party integrity time When the node initiates an SVCC as a calling party, this parameter
establishes the amount of time this node will wait for an SVCC to become
fully established. If the SVCC is not fully established at the end of the
configured time, it is torn down. The range is 5 to 300 seconds.
Called party integrity time When the node receives an SVCC setup as the called party, this parameter
establishes the amount of time this node will wait for the SVCC to
become fully established. If the SVCC is not fully established at the end
of the configured time, it is torn down. The range is 10 to 300 seconds.