CHAPTER
8-1
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
8
2
Managing PNNI Nodes and PNNI Routing
This chapter provides procedures that you can use to manage Private Network-to-Network Interface
(PNNI) nodes and routes. This chapter includes the following sections:
• Managing PNNI Nodes
• Managing PNNI Routes
• Displaying Node Configuration Information
• Managing CUGs
• Maintaining a Persistent Network Topology for CWM
Note The concepts behind the procedures in this chapter are introduced in the Cisco PNNI Network Planning
Guide for MGX and SES Products.
Managing PNNI Nodes
The following sections describe how to configure upper level peer groups and how to manage the PNNI
node.
Creating Upper Level Peer Groups
Upper level peer groups enable routing from one PNNI peer group to another. If you are managing a
single peer group WAN, you do not need to create upper level peer groups.
Note The “Configuring PNNI Node Parameters” section in Chapter 2, “Configuring General Switch
Features,” describes how to configure the lowest level peer group parameters, which many upper level
peer group parameters are based on. You should configure the basic PNNI node parameters before
creating upper level peer groups.
After you configure the lowest level PNNI nodes, all nodes within the same peer group can communicate
with each other. All you need to do to enable communications between two nodes in a peer group is to
add a PNNI trunk between them as described in the “ATM Trunk Configuration Quickstart” section in
Chapter 3, “Provisioning PXM1E Communication Links.” To enable routing between different peer
groups at the same level, you must create one or more upper level peer groups.
Comments to this Manuals