5-89
Cisco MGX 8850 Routing Switch Command Reference
Release 2.0, Part Number 78-10467-04 Rev C0, October 2001
Chapter 5
PNNI Commands
dsppnni-path
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