8-64
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
Managing CUGs
Deleting a CUG Assignment
A CUG assignment is made when the addcug command is used to assign a user to a CUG. To delete a
single CUG assignment, use the following procedure.
Note
When you delete a CUG assignment, all active connections that have been validated with that CUG are
unaffected by the change. To completely delete a CUG from a network, you must delete all CUG
assignments on all switches.
Step 1
Establish a configuration session using a user name with SUPER_GP privileges or higher.
Step 2
To display the current CUG access configuration for a user, enter the dspcug command as described in
the “
Displaying CUG Configuration Data
” section, which appears earlier in this document.
Step 3
Enter the delcug command as follows to delete the CUG assignment:
mgx8830a.1.PXM1.a >
delcug
<
atm-address
> <
length
> <
plan
> <
cug-index
>
The delcug command parameters are described in
. You must enter the CUG parameters that
were defined when the CUG was assigned with the addcug command.
Blocking the CUG IE
When a CUG call is set up, the CPE may generate a CUG information element (IE) during the call setup.
If the CPE generates the IE, it contains the CUG index assigned when the CUG was added. When the
call setup proceeds to the source switch, the switch can block or forward the CUG information element.
The default configuration blocks IE forwarding on UNI interfaces and forwards the CUG on NNI
interfaces. This is the auto configuration selection.
When the CUG IE is signaled between switches, it contains the CUG interlock code. If CUG IE
forwarding is enabled at the destination switch, the interlock code is translated back to a CUG index and
forwarded to the CPE by default.
If any switch along the call route cannot accept the CUG IE, or if the destination CPE cannot accept the
CUG IE, you can block forwarding of the CUG IE on the appropriate interface. From the point at which
the CUG IE is blocked to the destination CPE, the call behaves like a normal call. This feature can be
used to allow devices that do not support CUG to participate in CUGs. In this sort of topology, the
outgoing interface where the CUG IE is blocked serves as the CUG destination.
Use the following procedure to block forwarding of the CUG IE.
Step 1
Establish a configuration session using a user name with GROUP1 privileges or higher.
Step 2
Enter the dsppnportie <portid> command as follows to display the current configuration for the CUG
IE feature. Replace <portid
>
with the appropriate port identifier in the format slot:bay.line:ifnum.
mgx8830a.1.PXM1.a >
dsppnportie
3:1.2:2
IE Options for port : 3:1.2:2
PS IE Option : auto
CUG IE Option : auto
