Specifications

8-4
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
Managing PNNI Nodes
Pref PGL node name .....PXM1E_SJ
PGL.....................56:160:47.00918100000000036b5e31b3.00036b5e31b3.01
PGL node name ..........M8850_NY
Active parent node id...0:0:00.000000000000000000000000.000000000000.00
Active parent node name
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
Pref PGL node name .....
PGL.....................0:0:00.000000000000000000000000.000000000000.00
PGL node name ..........
Active parent node id...0:0:00.000000000000000000000000.000000000000.00
Active parent node name
The first time the dsppnni-election command was entered, the PGL state was OperNotPgl, which means
that the node is operating, but is not operating as a PGL. After the priority is changed, the PGL state
changes to AwaitUnanimity, which means the node is communicating with the other nodes in its peer
group to see if it has the highest priority and should be PGL. If you enter the dsppnni-election command
again after about 15 seconds, the PGL state changes as shown in the following example:
PXM1E_SJ.7.PXM.a > dsppnni-election
node index: 1
PGL state...... OperPgl Init time(sec)....... 15
Priority....... 250 Override delay(sec).. 30
Re-election time(sec) 15
Pref PGL................56:160:47.00918100000000001a533377.00001a533377.01
Pref PGL node name .....PXM1E_SJ
PGL.....................56:160:47.00918100000000001a533377.00001a533377.01
PGL node name ..........PXM1E_SJ
Active parent node id...40:56:47.009181000000000000000000.0007856e15e1.00
Active parent node name PXM1E_SJ-02
node index: 2
PGL state...... OperNotPgl Init time(sec)....... 15
Priority....... 0 Override delay(sec).. 30
Re-election time(sec) 15
Pref PGL................0:0:00.000000000000000000000000.000000000000.00
Pref PGL node name .....
PGL.....................0:0:00.000000000000000000000000.000000000000.00
PGL node name ..........
Active parent node id...0:0:00.000000000000000000000000.000000000000.00
Active parent node name
In the example above, the PGL state changes to show that logical node 1 is now the PGL. Notice that the
priority value is 250. An earlier example in this procedure set the priority to 200. When a node is elected
PGL, the node adds 50 to its priority value to prevent instability that might be caused by other peer group
nodes with a marginally higher priority value.
Step 4 Repeat this procedure for backup peer group leaders and be sure to set their priority value to a lower
value so that they operate as backup PGLs.