Specifications

8-52
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 CUGs
Geneva.7.PXM.a > dsppnni-svcc-rcc
node index: 1 svc index: 33
Hello pkt RX........ 34 SVCC VPI............ 34
Hello pkt TX........ 34 SVCC VCI............ 128
Hello state........... 2wayOutside
Remote node id.........56:160:39.840f80113744000000400202.00107b0efe01.00
Remote node ATM addr...39:840f.8011.3744.0000.0040.0102.4000.0c80.8030.00
node index: 2 svc index: 33
Hello pkt RX........ 34 SVCC VPI............ 34
Hello pkt TX........ 34 SVCC VCI............ 128
Hello state............2wayOutside
Remote node id.........56:160:39.840f80113744000000400202.00107b0efe01.00
Remote node ATM addr...39:840f.8011.3744.0000.0040.0102.4000.0c80.8030.00
Managing CUGs
CUG configuration is a two-step process.
1. Define the address or prefix of an interface through the addaddr command as described in the
“Assigning Address Prefixes and AESAs” section later in this chapter.
2. Add a CUG to the interface address or prefix through the addcug command.
The following sections describe processes and procedures that relate to CUG configuration and
management.
• Assigning Address Prefixes and AESAs
• Creating Closed User Groups
• Displaying CUG Configuration Data
• Setting a Default Address for CUG Validation
• Deleting a Default CUG Address
• Managing Access between Users in the Same CUG
• Managing Access between a CUG Member and Non-Members or Members of Other CUGS
• Deleting a CUG Assignment
• Blocking the CUG IE
Assigning Address Prefixes and AESAs
CUGs can be associated with AESAs or address prefixes. When PNNI is establishing a route between
two CUG members, PNNI searches routing tables for the best route to the destination address. When the
best route is located, the call proceeds to the destination switch, which selects the appropriate interface
by searching internal address tables for the longest prefix match. When a switch and its interfaces are
configured with prefixes that enable PNNI to quickly locate the destination interface, PNNI routing and
CUG validation are most efficient. For more information about address prefix and AESA assignment,
refer to the Cisco PNNI Network Planning Guide for MGX and SES Products.
Before you can assign a CUG to an address prefix or AESA, that prefix or AESA must be added to an
interface. The address assignment makes the prefix or AESA known to PNNI, and makes it available for
assignment to a CUG.
Use the following procedure to add an address or prefix to an interface.