Specifications

8-53
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
Step 1 Establish a configuration session using a user name with GROUP1 privileges or higher.
Step 2 Enter the dsppnports command to locate the port to which you want to add the address,.
Step 3 Specify an ATM address for the port using the addaddr command as follows:
addaddr <portid> <atm-address> <length> [-type int] [-proto local] [-plan {e164 | nsap}]
[-scope scope] [-redistribute {yes | no}] [-tnid tnid]
Table 3-14 in Chapter 3, “Provisioning PXM1E Communication Links.” describes the addaddr
command parameters.
The following example assigns an ATM address to port 9:1.2:2:
mgx8830a.1.PXM1.a > addaddr 1:2.1:3 47.1111.1111.1111.1111.1111.1111.1111.1111.1111.11 160
Step 4 To verify that the new address has been assigned, enter the dspatmaddr <portid> command. Replace
<portid> with the appropriate port identifier in the format slot:bay.line:ifnum.
In the following example, the user displays the ATM address for port 2:2.2:1:
mgx8830a.1.PXM1.a > dspatmaddr 2:2.2:1
Port Id: 2:2.2:1
Configured Port Address(es) :
47.1111.1111.1111.1111.1111.1111.1111.1111.1111.11
length: 160 type: internal proto: local
scope: 0 plan: nsap_icd redistribute: false
For more information about address assignment and address assignment issues that apply to CUGs, refer
to the “Cisco PNNI Network Planning Guide for MGX and SES Products.”
Creating Closed User Groups
A CUG is established by assigning the same 24-byte interlock code to two or more prefixes or AESAs
on a PNNI network. All prefixes and addresses that share the same interlock code are considered part of
the same CUG and can establish connections amongst themselves, unless these connections are blocked
by configuration options.
The interlock code is defined within the PNNI node and is not shared with CPE. If a CPE AESA is a
member of only one CUG and that CUG is defined as the preferential CUG (see “Managing Access
between a CUG Member and Non-Members or Members of Other CUGS,” which appears later in this
chapter), the CPE does not need to be configured to use a particular CUG. The preferential CUG serves
as the implicit CUG, and is used whenever a CUG is not specified by the CPE.
A CPE must be configured to specify a particular CUG during call setup when any of the following
conditions exist:
• One or more CUGs are defined for the CPE prefix or address and no preferential CUG is defined.
• Multiple CUGs are defined for the prefix or address and the CPE intends to use a CUG other than
the preferential CUG.
To select a CUG, the CPE is configured with a CUG index, which is a number that you assign when you
assign a prefix or address to a CUG with the addcug command. When a CPE requests a specific CUG
during call setup, this is called an explicit CUG request.