Specifications

3-11
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 3 Provisioning PXM1E Communication Links
Quickstart Provisioning Procedures
Step 4
addpart <options>
Related commands:
dspparts
dsppart
cnfpart
Configure the virtual trunk partitions at the private switches.
For a VNNI port, enter the same VPI number for the minVpi and maxVpi
parameters. This number becomes the VPI number for the virtual trunk.
For an EVNNI port, enter the same minimum and maximum VPI numbers
you entered when creating the port. This range becomes the VPI number
range for the virtual trunk.
See the “Partitioning Port Resources Between Controllers” section later in
this chapter.
Step 5
dnpnport <portid>
cnfpnportsig <options>
uppnport <portid>
Related commands:
dsppnports
dsppnport <portid>
dsppnportsig <portid>
Configure the virtual trunk signaling at the private switches. Select PNNI
signaling by setting the -nniver option to pnni10.
pop20two.7.PXM.a > cnfpnportsig <portid> -nniver pnni10
See the “Selecting the Port Signaling Protocol” section later in this
chapter.
Step 6
addport <options>
or
addimagrp <options>
addimalnk <options>
addimaport <options>
Related commands:
dspports
dspimalnk
dspimalnks
dspimagrp
dspimagrps
Add and configure the virtual trunk end ports at each core edge node.
Specify interface type 1 for UNI or 2 for NNI.
See the “Adding ATM Ports” section later in this chapter.
If you want to configure ATM communications over an IMA group, see the
“Configuring Inverse Multiplexing for ATM” section later in this chapter.
Step 7
addpart
Related commands:
dspparts
dspparts
cnfpart
Configure the virtual trunk partitions at each core edge node. Use a VPI
range that includes all VPI numbers set for virtual trunks on this line at the
private switch.
See the “Partitioning Port Resources Between Controllers“section in this
chapter.
Note If you plan to migrate to MPLS, do not configure the whole range
of VPI/VCI. Instead, only configure as much as you need for PNNI
to operate. You cannot shrink the VPI/VCI range without affecting
the service of your network.
Command Purpose