Creating Closed User Groups - Cisco MGX 8850 (PXM1E/PXM45) Configuration Manual

Chapter 8 Managing PNNI Nodes and PNNI Routing
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
scope: 0
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
Between a CUG Member and Non-Members or Members of other
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:
•
•
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.
If a prefix or address is not assigned to any CUG, it can still communicate with a CUG member only
when that member is configured to communicate with non-CUG members. This is described in
"Managing Access Between a CUG Member and Non-Members or Members of other
appears later in this chapter.
To create a CUG or assign a new user to a CUG, use the following procedure.
Establish a configuration session using a user name with SUPER_GP privileges or higher.
Step 1
Step 2 To create a CUG or to add a prefix or address to an existing CUG, enter the addcug command using the
following format:
mgx8830a.1.PXM1.a > addcug <atm-address> <length> <plan> <cug-index> <aesa-ic>
[-callsbarred {none|incoming|outgoing}]
Table 8-20
Release 5.0.10, OL-3845-01 Rev. B0, August 16, 2004
type: internal
plan: nsap_icd
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.
defines the addcug command parameters and options.
Cisco MGX 8850 (PXM1E/PXM45), Cisco MGX 8950, Cisco MGX 8830, and Cisco MGX 8880 Configuration Guide
proto: local
redistribute: false
Managing CUGs
"Managing Access
CUGS," which appears later in this
CUGS," which
8-57