Cisco MGX 8950 Specifications Page 362

  • Download
  • Add to my manuals
  • Print
  • Page
    / 642
  • Table of contents
  • TROUBLESHOOTING
  • BOOKMARKS
  • Rated. / 5. Based on customer reviews
Page view 361
8-72
Cisco MGX 8850 (PXM1E/PXM45), Cisco MGX 8950, Cisco MGX 8830, and Cisco MGX 8880 Configuration Guide
Release 5.0.10, OL-3845-01 Rev. B0, August 16, 2004
Chapter 8 Managing PNNI Nodes and PNNI Routing
Maintaining a Persistent Network Topology for CWM
Note Cisco recommends that you avoid using PXM1E nodes as gateway nodes due to memory limitation.
Note Cisco recommends that you configure two gateway nodes for each SPG network or lowest level peer
groupings of MPG. If one node goes down, CWM can pick the other node and start using it.
Disabling a Gateway Node
To disable a node’s status as a gateway node, use the following procedure:
Step 1 Establish a configuration session on the switch you want to become the gateway node, using a user name
with SUPER_GP privileges or higher.
Step 2 On the active PXM card, enter the cnftopogw off command to disable the nodes status as the gateway
node for the peer group, as shown in the following example.
8830_CH.1.PXM.a > cnftopogw off
Step 3 Enter the dsptopogw command to verify that the current node is functioning as a gateway, as shown in
the following example.
8830_CH.1.PXM.a > dsptopogw
Admin State : DISABLED Operational State DISABLING
The display shows that the gateway node is going through the disabling process. During this period, do
not perform any configuration on the topology database. Enter the dsptopogw command again until the
Operational State shows that the disabling process is DISABLED, as shown in the following example.
8830_CH.1.PXM.a > dsptopogw
Admin State : DISABLED Operational State DISABLED
Once a gateway node has been disabled, that node operates as a regular non-gateway node in the peer
group. If another node in the peer group is not configured as a gateway node, CWM will not maintain a
persistent topology of that peer group.
Deleting a Node from the Topology Database
When a node is removed from the network, it is not automatically removed from the network topology
database. Because information about the removed node is stored in the topology databases of every other
node in the peer group, you need to delete the removed node from each nodes topology database,
regardless of whether the node is a gateway or non-gateway node.
Page view 361
1 ... 361 362 363 ... 642

Comments to this Manuals

No comments