Cisco MGX 8950 Specifications Page 355

  • Download
  • Add to my manuals
  • Print
  • Page
    / 642
  • Table of contents
  • TROUBLESHOOTING
  • BOOKMARKS
  • Rated. / 5. Based on customer reviews
Page view 354
8-65
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
Step 3 Enter the cnfpnportie command as follows to block the CUG IE.
mgx8830a.1.PXM1.a > cnfpnportie <portid> -cugie disallowed
Replace <portid> with the port identifier in the format slot:bay.port:interface. The disallowed option
always blocks the CUG IE.
Step 4 To verify your change, enter the dsppnportie command as described in Step 2 of this procedure.
Note Refer to Q.2955.1 for more information about when calls are rejected for different IA/OC combinations.
If you want to re-enable CUG IE forwarding on an interface, enter the cnfpnportie <portid> -cugie
allowed command. Replace <portid> with the port identifier in the format slot:bay.port:interface.
Enter the cnfpnportie <portid> -cugie auto command to block the CUG IE on UNI interfaces, and
forward it on NNI and AINI interfaces. Replace <portid> with the port identifier in the format
slot:bay.port:interface.
Maintaining a Persistent Network Topology for CWM
If you are using CWM to configure and monitor your network, you can set up and maintain a persistent
topology of the routing nodes, feeder nodes, and PNNI links in your network. The persistent topology is
maintained in topology databases on each node in a specified peer group. CWM receives network
topology information through gateway nodes that are set up by the network administrator. You can setup
a gateway node through the CLI or through CWM. This document describes the CLI procedures for
configuring gateway nodes and maintaining topology databases on each node in your network. To
configure a gateway node through CWM, refer to the current CWM documentation.
Non-gateway nodes maintain a persistent topology of the network in the same way as a gateway node.
However, CWM only interacts with gateway nodes. Whenever a node is added, deleted, or a modified in
a peer group, that peer groups gateway node sends a trap to CWM so that CWM can update its topology
databases.
Once you have set up a gateway node for a peer group, a persistent topology comprised of node, link,
and feeder database is automatically created, and you can use CWM to monitor your entire network.
Note All node and connection information is passed only through PNNI links.
Configuring a Gateway Node
Use the following procedure to enable a switch as a gateway node for its peer group.
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 on command to enable the switch as the gateway node for
its peer group, as shown in the following example.
8830_CH.1.PXM.a > cnftopogw on
Page view 354
1 ... 354 355 356 ... 642

Comments to this Manuals

No comments