Specifications

6-21
Cisco MGX 8850 (PXM45) and MGX 8950 Software Configuration Guide
Release 3, Part Number 78-14788-01 Rev. C0, January 2004
Chapter 6 Managing PNNI Nodes and PNNI Routing
Displaying Node Configuration Information
Hello pkt TX......... 19582
Remote node name.......SanJose
Remote node id.........56:160:47.00918100000000309409f1f1.00309409f1f1.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
node index : 1
Local port id: 17504289 Remote port id: 17045537
Local Phy Port Id: 11:2.1:33
Type. lowestLevelHorizontalLink Hello state....... twoWayInside
Derive agg........... 0 Intf index........... 17504289
SVC RCC index........ 0 Hello pkt RX......... 17501
Hello pkt TX......... 18877
Remote node name.......SanJose
Remote node id.........56:160:47.00918100000000309409f1f1.00309409f1f1.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
Displaying the PNNI Routing Policy
Enter the dsppnni-routing-policy command to display the routing policies used for background routing
tables generation:
Geneva.7.PXM.a > dsppnni-routing-policy
The following example shows the report for this command:
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 >
Table 6-10 describes the objects displayed for the dsppnni-routing-policy command.
Table 6-10 Objects Displayed for the dsppnni-routing-policy Command
Parameter Description
sptEpsilon The tolerance used during route calculation to determine which
paths qualify as equal-cost. The range is from 0—20.
sptHolddown The interval between two consecutive calculations for generating
routing tables. The range is from 1 (0.1 sec) to 600 (60 sec).
bnPathHolddown The minimum time that can elapse between consecutive
calculations that generate routing tables for border nodes. The range
is from 2 (0.2 sec) to 600 (60 sec).
-loadBalance Defines the load balancing rule if alternative equal-cost routes exist
for a given call request.