-
MGX 8850 (PXM1E/PXM45), MGX 8950, and MGX 8830 Software Configuration Guide, Release 4
-
About This Guide
-
Preparing for Configuration
-
Planning for Card Redundancy, Line Redundancy, and Bulk Distribution
-
Configuring General Switch Features
-
Preparing PXM1E Lines for Communication
-
Preparing AXSM Cards and Lines for Communication
-
Preparing FRSM12 Cards and Lines for Communication
-
Preparing Cell Bus Service Modules for Communication
-
Preparing SRM Cards and Lines for Communications
-
Preparing RPM Cards for Operation
-
Managing Service Class Templates
-
Provisioning PXM1E Communication Links
-
Managing PNNI Nodes and PNNI Routing
-
Switch Operating Procedures
-
Switch Maintenance Procedures
-
Viewing and Responding to Alarms
-
Downloading and Installing Software Upgrades
-
PXM1E Backup Boot Procedures
-
Supporting and Using Additional CLI Access Options
-
Standards Compliance
-
Hardware Survey and Software Configuration Worksheets
-
Table Of Contents
Provisioning PXM1E Communication Links
Quickstart Provisioning Procedures
ATM Trunk Configuration Quickstart
PNNI UNI Port Configuration Quickstart
SPVC and SPVP Configuration Quickstart
PNNI Virtual Trunk Configuration Quickstart
BPX PNNI Trunk Configuration Quickstart
AINI Link Configuration Quickstart
IISP Link Configuration Quickstart
XLMI Link Configuration Quickstart
Cisco IGX Feeder to Cisco MGX 8850 Configuration Quickstart
PNNI UNI Port Configuration Quickstart
General PXM1E Configuration Procedures
Partitioning Port Resources Between Controllers
Selecting the Port Signaling Protocol
Assigning Static ATM Addresses to Destination Ports
Configuring ILMI Traps and Signaling
Configuring ILMI Automatic Configuration
Configuring ILMI Dynamic Addressing
Starting ILMI with the Default or Existing Values
Configuring PXM1E Line Clock Sources
Verifying PNNI Trunk Communications
Verifying End-to-End PNNI Communications
Configuring the Slave Side of SPVCs and SPVPs
Configuring the Master Side of SPVCs and SPVPs
Configuring Point-to-Multipoint SPVCs and SPVPs
Obtaining the NSAP for a Party
Deleting a P2MP Party Configuration
Defining Destination Addresses for Static Links
Configuring Inverse Multiplexing for ATM
Adding an IMA Link to an IMA Group
Configuring a Connection to an IGX Feeder
Connecting a PXM1E Card to a UXM Card on an IGX feeder
Provisioning PXM1E Communication Links
This chapter describes how to add logical ports and virtual connections to physical lines. This chapter explains how to provision the link and connection types listed in Table 11-1.
1 SVC = switched virtual circuits
2 SPVC = soft permanent virtual circuit
3 AINI = ATM Inter-Network Interface
4 IISP = Interim Inter-Switch Protocol
5 ILMI = Extended Link Management Interface
The configuration differences between these types of connections are often as simple as an additional command or a different set of command options. To eliminate redundancy and help experienced users complete configuration procedures quickly, this chapter uses configuration quickstarts and task descriptions to explain how to configure connections.
The first time you configure a connection type, use the quickstart procedure to see the order of tasks to complete, and then read the task descriptions for detailed instructions.
Note
For all commands in this chapter, refer to the Cisco MGX 8850 (PXM1E/PXM45), Cisco MGX 8950, and Cisco MGX 8830 Command Reference for detailed information.
Note
Quickstart Provisioning Procedures
The following sections present abbreviated procedures that you can use to provision connections.
ATM Trunk Configuration Quickstart
ATM trunks connect the switch to other ATM switches in the core ATM network. The quickstart procedure in this section provides a summary of the tasks required to configure ATM trunks on Cisco MGX switches. This procedure is a quick reference for those who have previously configured these types of connections.
Note
Step 1
username
<password>
Start a configuration session.
Note
Step 2
Prepare PXM1E cards and lines as described in Chapter 4, "Preparing PXM1E Lines for Communication."
Remember to select the appropriate card SCT for the controller or controllers you are using.
Step 3
addport <options>
Related commands:
dspports
Add and configure ATM ports. This step establishes ATM communications between two ATM devices.
Specify NNI for interswitch trunks.
See the "Adding ATM Ports" section later in this chapter.
Step 4
addpart <options>
Related commands:
dspparts
dsppart
cnfpart
Assign trunk resources to PNNI controllers. This step can assign all the trunk bandwidth to a single controller, or it can assign portions of the trunk bandwidth to each controller.
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>
Define the signaling protocol used on the trunk. The default signaling protocol is UNI Version 3.1. Specify pnni10 for PNNI trunks.
See the "Selecting the Port Signaling Protocol" section later in this chapter.
Step 6
dsppnni-link
dsppnni-neighbor
When both ends of the link are configured, verify the PNNI communications between the two ends. In the dsppnni-link report, there should be an entry for the port for which you are verifying communications. The Hello state reported should be twoWayInside, and the Remote node ID should display the remote node ATM address after the second colon.
See the "Verifying PNNI Trunk Communications" section later in this chapter.
Step 7
upilmi <ifNum> <partId>
cnfilmi <options>
Related commands:
dspports
dspilmis
This step is optional. Configure and start ILMI on trunks where you want to support Cisco WAN Manager or use ILMI features.
See the "Configuring ILMI on a Port" section later in this chapter.
After you configure an PXM1E trunk, the trunk is ready to support SVCs. You can also create SPVCs and SPVPs between CPE at each end of the trunk as described in "Configuring SPVCs and SPVPs," which appears later in this chapter.
PNNI UNI Port Configuration Quickstart
ATM UNI ports connect the switch to ATM end devices, which serve as the boundary between the ATM network and other communications paths or networks. Typical end devices include ATM routers and multiservice concentrators. UNI signaling is used between the end system (CPE) and the PNNI network for requesting calls.
The quickstart procedure in this section provides a summary of the tasks required to configure UNI ports on Cisco MGX switches. This procedure is provided as an overview and as a quick reference for those who have previously configured UNI ports.
Note
Step 1
username
<password>
Start a configuration session.
Note
Step 2
—
Prepare PXM1E cards and lines as described in Chapter 4, "Preparing PXM1E Lines for Communication."
Remember to select the appropriate card SCT for the controller or controllers you are using.
Step 3
addport <options>
Related commands:
dspports
Add and configure ATM ports. This step establishes ATM layer two communications between two ATM devices.
Specify UNI for ATM lines.
See the "Adding ATM Ports" section later in this chapter.
Step 4
addpart <options>
Related commands:
dspparts
dsppart
cnfpart
Assign line resources to the PNNI controllers. This step can assign all the line bandwidth to a single controller, or it can assign portions of the line bandwidth to each controller.
See the "Partitioning Port Resources Between Controllers" section later in this chapter.
Step 5
dnpnport <portid>
Bring down the port so it can be configured. The next three steps require this step.
Step 6
cnfpnportsig <options>
Related commands:
dsppnports
dsppnport <portid>
dsppnportsig <portid>
Define the signaling protocol used on the line. The default signaling protocol for UNI lines is UNI Version 3.1.
Specify uni30, uni31, or uni40.
See the "Selecting the Port Signaling Protocol" section later in this chapter.
Step 7
cnfaddrreg <portid> no
addaddr <options>
Related commands:
dsppnports
dspatmaddr <portid>
deladdr <options>
Configure static ATM addresses for ports that require them.
See the "Assigning Static ATM Addresses to Destination Ports" section later in this chapter.
Step 8
addprfx <portid> atm-prefix
Related commands:
cnfaddrreg <portid> yes
dspprfx <portid>
If dynamic addressing is to be used on a port, define an ATM address prefix that ILMI can use when assigning addresses.
See the "Configuring ILMI Dynamic Addressing" section later in this chapter.
Step 9
uppnport <portid>
Bring up port after configuration is complete.
Step 10
upilmi <ifNum> <partId>
cnfilmi <options>
Related commands:
dspports
dspilmis
Configure and start ILMI on the port. This step is required for dynamic addressing and the ILMI automatic configuration feature. Otherwise, it is optional.
See the "Configuring ILMI on a Port" section later in this chapter.
SVC Configuration Quickstart
Switched virtual circuits (SVCs) are the solution for on-demand connections. They are set up as needed and torn down when no longer needed. To enable this dynamic activity, SVCs use signaling. End systems request connectivity to other end systems and, provided that the requested services are available, the connection is set up at the time of the request. When idle, an SVC is taken down to save network bandwidth.
Cisco MGX 8850 (PXM1E) and Cisco MGX 8830 switches can use the PNNI protocol to determine how to set up SVCs through the network. Because the switch automatically sets up SVCs, you do not have to configure SVC routes. However, the switch must be configured correctly before it can set up SVCs. The following quickstart procedure summarizes the tasks required to enable SVC communications. With the exception of CPE configuration, all these tasks are described in this chapter.
Note
Step 1
See the "ATM Trunk Configuration Quickstart" section earlier in this chapter.
Configure the trunks that link the switches through which the ATM end stations connect. Be sure to add the PNNI controller on each switch and select that controller when partitioning trunks.
Step 2
dsppnni-reachable-addr network
Verify connectivity between the node pairs that will host SVCs.
See the "Verifying End-to-End PNNI Communications" section later in this chapter.
Step 3
See the "PNNI UNI Port Configuration Quickstart" section earlier in this chapter.
Configure UNI ports for the ATM end stations at each end of the SVC, and assign either static or dynamic addressing to each line. Be sure to add the PNNI controller on each switch and select that controller when partitioning trunks.
Step 4
See the CPE documentation.
Configure CPE devices for communications with the switch through the UNI ports configured in the previous step.
Step 5
dsppncons
This optional step displays the SVC connections that are operating.
See the "Displaying SVCs" section in Chapter 13, "Switch Operating Procedures."
It is beyond the scope of this guide to describe how to configure each model of the CPE to communicate with the switch. To complete this configuration, you will need to learn the capabilities of the CPE and the switch and define a set of communications parameters that are supported by both devices. For example, the Cisco MGX switches support UNI 3.1 communications, but if the CPE does not, you must select a signaling protocol (such as UNI 3.0) that is supported by both devices.
Once all the requirements have been met for SVC connections, CPE devices can establish SVC connections to other CPE devices on the same switched network.
SPVC and SPVP Configuration Quickstart
A soft permanent virtual circuit (SPVC) is a permanent virtual circuit (PVC) that can be rerouted using the Private Network-to-Network Interface (PNNI) Version 1.0 protocol. As with PVCs, SPVCs are full-time connections. A PVC, however, uses a predefined circuit path and will fail if the path is interrupted. Using the PNNI protocol, SPVCs can be rerouted to avoid failed communication links or to use links that offer better bandwidth.
An SPVP is a permanent virtual path that can be rerouted using the PNNI Version 1.0 protocol. The difference between an SPVC and an SPVP is that the SPVP supports multiple virtual circuits, whereas a SPVC is by definition a single virtual circuit. As with SPVCs, when an SPVP fails, PNNI can determine if an alternate route exists and reroute the connection.
The quickstart procedure in this section provides a summary of the tasks required to configure SPVCs and SPVPs on Cisco MGX 8850 (PXM1E) and Cisco MGX 8830 switches. This procedure is provided as an overview and as a quick reference for those who have previously configured these types of connections.
PNNI Virtual Trunk Configuration Quickstart
Virtual trunks are introduced in the "Multiservice Edge Aggregation" section in "Preparing for Configuration." Figure 11-1 shows illustrates how a virtual trunk is configured.
Figure 11-1 Virtual Trunk Topology
Figure 11-1 shows an example of configuration data that you can use when following the quickstart procedure below. Note that the single trunk between Private Switch A and Edge Switch A hosts two virtual trunks, which terminate at Virtual Network-to-Network Interface (VNNI) ports 10:1.2:2 and 10:1.2:7. The switch supports up to 256 VNNI ports on a UNI link and up to 4096 VNNI ports on an NNI link.
To set up a virtual trunk, the following tasks have to be completed:
•
•
The Cisco MGX switches support:
•
•
•
The following quickstart procedure provides a summary of the tasks required to configure virtual trunks on Cisco MGX switches. This procedure is provided as an overview and as a quick reference for those who have previously configured these types of connections.
Step 1
username
<password>
Start a configuration session on a Cisco MGX 8850 (PXM1E) or Cisco MGX 8830 switch. This will be the local routing switch that connects to the feeder.
Note
Step 2
Prepare PXM1E cards and lines as described in Chapter 4, "Preparing PXM1E Lines for Communication."
Remember to select the appropriate card SCT for the controller or controllers you are using.
Step 3
addport <options>
or
addimagrp <options>
addimalink <options>
addimaport <options>
Related commands:
dspports
Configure the virtual trunk end ports at the private switches. Select interface type 3 for VNNI.
For standard port configuration, see the "Adding ATM Ports" section later in this chapter.
If you are configuring IMA on this port, see the "Configuring Inverse Multiplexing for ATM" section later in this chapter.
Step 4
addpart <options>
Related commands:
dspparts
dsppart
cnfpart
Configure the virtual trunk partitions at the private switches. Enter the same VPI number for the minVpi and maxVpi parameters. This number becomes the VPI number for the trunk.
See the "Partitioning Port Resources Between Controllers" section later in this chapter.
Note
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 pnni10See the "Selecting the Port Signaling Protocol" section later in this chapter.
Step 6
addport <ifnum>
Related commands:
dspports
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.
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.
Step 8
dnpnport
cnfpnportsig
uppnport
Related commands:
dsppnports
dsppnport
dsppnportsig
Configure the virtual trunk signaling at each core edge node. Select no trunk signaling by setting the -univer option (UNI ports) to none or the -nniver option (NNI ports) to none.
See the "Selecting the Port Signaling Protocol" section later in this chapter.
Step 9
addcon <options>
Related commands:
dspcon
dspcons
For each virtual trunk, configure an SPVP between the virtual trunk ports at each edge of the core network. See the "Configuring SPVCs and SPVPs" section in this chapter.
Step 10
dsppnni-reachable-addr network
Verify PNNI connectivity between the two nodes that will host the virtual trunk end points.
See the "Verifying End-to-End PNNI Communications"section in this chapter.
BPX PNNI Trunk Configuration Quickstart
When the Cisco SES PNNI controller is attached to a Cisco BPX switch, the BPX switch can participate in a PNNI network with Cisco MGX switches. The connection between an Cisco MGX 8850 (PXM1E) switch and a BPX switch is a trunk between an PXM1E card in the MGX switch and a BXM card in the BPX. For instructions on configuring the BXM end of the trunk, refer to the Cisco SES product documentation. This section describes how to configure the PXM1E end of the trunk.
The procedure for configuring the PXM1E end of the trunk is similar to the general procedure for configuring PXM1E trunks. The following quickstart procedure is customized for setting up BPX PNNI trunks.
Note
Caution
Step 1
username
<password>
Start a configuration session.
Note
Step 2
Prepare PXM1E cards and lines as described in Chapter 4, "Preparing PXM1E Lines for Communication."
Step 3
addport <options>
Related commands:
dspports
Add and configure ATM ports. This step establishes ATM communications between two ATM devices.
Specify NNI for interswitch trunks.
See the "Adding ATM Ports"section later in this chapter.
Step 4
addpart <options>
Related commands:
dspparts
dsppart
cnfpart
Add and configure a PNNI partition for the trunk. This step reserves trunk resources for the PNNI controller.
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>
Define the signaling protocol used on the trunk. The default signaling protocol is UNI Version 3.1, so you must change the signaling protocol to pnni10. For example:
pop20two.7.PXM.a > cnfpnportsig <portid> -nniver pnni10See the "Selecting the Port Signaling Protocol" section later in this chapter.
Step 6
upilmi <ifNum> <partId>
cnfilmi <options>
Related commands:
dspports
dspilmis
Configure and start ILMI on the trunk. ILMI is required on the BXM end of the trunk, so it must be enabled on the PXM1E side too.
See the "Configuring ILMI on a Port" section later in this chapter.
Step 7
dsppnni-link
dsppnni-neighbor
When both ends of the link are configured, verify the PNNI communications between the two ends. In the dsppnni-link report, there should be an entry for the port for which you are verifying communications. The Hello state reported should be twoWayInside and the Remote node ID should display the remote node ATM address after the second colon.
See the "Verifying PNNI Trunk Communications" section later in this chapter.
After you configure a BPX PNNI trunk, the trunk is ready to support SVCs. You can also create SPVCs and SPVPs between CPE at each end of the trunk as described in the "Configuring SPVCs and SPVPs" section later in this chapter.
AINI Link Configuration Quickstart
The quickstart procedure in this section provides a summary of the tasks required to configure ATM Inter-Network Interface (AINI) links on Cisco MGX switches. This procedure is provided as an overview and as a quick reference for those who have previously configured these types of connections.
Step 1
username
<password>
Start a configuration session.
Note
Step 2
Prepare PXM1E cards and lines as described in Chapter 4, "Preparing PXM1E Lines for Communication."
Remember to select the appropriate card SCT for the controller or controllers you are using.
Step 3
addport <options>
Related commands:
dspports
Add and configure ATM ports. This step establishes ATM communications between two ATM devices.
Specify NNI for interswitch trunks.
See the "Adding ATM Ports" section later in this chapter.
Step 4
addpart <options>
Related commands:
dspparts
dsppart
cnfpart
Assign trunk resources to the PNNI controller. This step can assign all the trunk bandwidth to a single controller, or it can assign portions of the trunk bandwidth to each controller.
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>
Define the signaling protocol used at each end of the AINI link. The default signaling protocol is UNI Version 3.1. Specify aini for AINI trunks.
For example:
8850_LA.7.PXM.a > cnfpnportsig 1:1.1:1 -nniver ainiSee the "Selecting the Port Signaling Protocol" section later in this chapter.
Step 6
addaddr <options>
Add destination addresses to each end of the trunk.
See the "Defining Destination Addresses for Static Links" section later in this chapter.
Step 7
addaddr <options>
Add static addresses to destination ports. This step is required when addresses are not dynamically assigned to the CPE at the destination ports.
See the "Assigning Static ATM Addresses to Destination Ports" section later in this chapter.ater in this chapter.
IISP Link Configuration Quickstart
The quickstart procedure in this section provides a summary of the tasks required to configure Interim Inter-Switch Protocol (IISP) links on Cisco MGX switches. This procedure is provided as an overview and as a quick reference for those who have previously configured these types of connections.
Note
Step 1
username
<password>
Start a configuration session.
Note
Step 2
Prepare PXM1E cards and lines as described in Chapter 4, "Preparing PXM1E Lines for Communication."
Remember to select the appropriate card SCT for the controller or controllers you are using.
Step 3
addport <options>
Related commands:
dspports
Add and configure ATM ports. This step establishes ATM communications between two ATM devices.
Specify NNI for interswitch trunks.
See the "Adding ATM Ports," section later in this chapter.
Step 4
addpart <options>
Related commands:
dspparts
dsppart
cnfpart
Assign trunk resources to the PNNI controller. This step can assign all the trunk bandwidth to a single controller, or it can assign portions of the trunk bandwidth to each controller.
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>
Define the signaling protocol used at each end of the IISP link. The default signaling protocol is UNI Version 3.1. Specify either iisp30 or iisp31 for IISP trunks.
For example:
mgx8830a.1.PXM.a > cnfpnportsig 1:1.1:1 -nniver iisp31See the "Selecting the Port Signaling Protocol" section later in this chapter.
Step 6
addaddr <options>
Add destination addresses to each end of the trunk.
See the "Defining Destination Addresses for Static Links" section later in this chapter.
Step 7
addaddr <options>
Add static addresses to destination ports. This step is required when addresses are not dynamically assigned to the CPE at the destination ports.
See the "Assigning Static ATM Addresses to Destination Ports" section later in this chapter.
XLMI Link Configuration Quickstart
An Extended Link Management Interface (XLMI) link joins a PNNI network with an AutoRoute network. After you establish an XLMI link, you can configure connections that link CPE in the PNNI network with CPE in the AutoRoute network. The interconnection of PNNI and AutoRoute networks enables network expansion beyond the limits of AutoRoute and facilitates a gradual migration from an all AutoRoute network to an all PNNI network.
To establish an XLMI link, you need to the following tasks:
1.
2.
3.
The quickstart procedure in this section describes how to configure an PXM1E port to support an XLMI link, and references the instructions for creating a connection between the PNNI and AutoRoute networks. Before you begin configuration, consider the following guidelines and limitations:
•
•
•
•
•
•
•
–
–
–
The following quickstart procedure provides a summary of the tasks required to configure XLMI links on Cisco MGX 8850 (PXM1E) and Cisco MGX 8830 switches.
Step 1
username
<password>
Start a configuration session.
Note
Step 2
—
Prepare PXM1E cards and lines as described in Chapter 4, "Preparing PXM1E Lines for Communication."
Remember to select the appropriate card SCT for the controller or controllers you are using.
Step 3
addport <options>
Related commands:
dspports
Add and configure ATM ports. This step establishes ATM communications between two ATM devices.
The PXM1E cards supports XLMI on UNI or NNI ports.
See the "Adding ATM Ports"section later in this chapter.
Step 4
addpart <options>
Related commands:
dspparts
dsppart
cnfpart
Assign port resources to the PNNI controller. This step can assign all the port bandwidth to a single controller, or it can assign portions of the port bandwidth to each controller.
See the "Partitioning Port Resources Between Controllers" section later in this chapter.
Step 5
addlmi <interface> <type>
Related commands:
dsplmi <interface>
Add LMI to the port. For example:
M8850_NY.6.PXM1E.a > addlmi 2 2Replace the type variable with 2 for XLMI links. (Type 1 selects feeder operation.)
Step 6
dnpnport <portid>
Related commands:
dsppnports
dsppnport <portid>
Bring down the port so it can be configured.
Step 7
cnfpnportsig <options>
Related commands:
dsppnport <portid>
dsppnportsig <portid>
Define the signaling protocol used for the port. The default signaling protocol is UNI Version 3.1. Specify enni for XLMI trunks.
For example:
mgx8830a.1.PXM.a > cnfpnportsig 1:1.1:1 -nniver enniSee the "Selecting the Port Signaling Protocol" section later in this chapter.
Step 8
uppnport <portid>
Related commands:
dsppnports
dsppnport <portid>
Bring up the configured port.
Step 9
—
If you are using CWM to manage your networks, the XLMI link should be ready to use. Use CWM to add a connection from a destination in the AutoRoute network to a destination in the PNNI network.
Step 10
addcon <options>
If you are not using CWM to manage your networks, add a connection from the XLMI link endpoint on the PXM1E to a destination on the PNNI network.
Note
See the "Configuring SPVCs and SPVPs" section later in this chapter.
Note
Step 11
—
If you are not using CWM to manage your networks, add a connection from the XLMI link endpoint on the BXM to a destination on the AutoRoute network.
Note
For more information, refer to the Cisco BPX 8600 Series Installation and Configuration guide.
Cisco IGX Feeder to Cisco MGX 8850 Configuration Quickstart
The quickstart procedure in this section provides a summary of the tasks required to configure a feeder between a Cisco MGX 8850 (PXM1E) or Cisco MGX 8830 switch, and a Cisco IGX 8400 switch. This procedure is provided as an overview and as a quick reference for those who have previously configured these types of connections.
Step 1
username
<password>
Start a configuration session with the active PXM1E card on a Cisco MGX 8850 (PXM1E) or Cisco MGX 8830 switch.
Note
Step 2
upln
addport
or
addimagrp
addimalnk
addimaport <options>
Related commands:
dspports.
Create an interface between the PXM1E card on a Cisco MGX 8850 (PXM1E) or a Cisco MGX 8830, and the UXM card on a Cisco IGX 8400.
For standard port configuration, see the "Adding ATM Ports" section later in this chapter.
If you are configuring IMA on this port, see the "Configuring Inverse Multiplexing for ATM" section later in this chapter.
Step 3
addlmi
Designate the interface as a feeder.
Step 4
dnpnport <portid>
cnfpnportsig <options>
uppnport <portid>
Related commands:
dsppnports
dsppnport <portid>
dsppnportsig <portid>
Define the signaling protocol used at each end of the trunk.
For example:
mgx8830a.1.PXM.a > cnfpnportsig 1:1.1:1 -nniver iisp31See the "Selecting the Port Signaling Protocol" section later in this chapter.
Step 5
username
<password>
Start a configuration session with the UXM card on a Cisco IGX 8400 switch.
Note
Step 6
cnfswfunc
uptrk
cnftrk
Configure the trunk on the IGX switch. The configuration on the UXM end of the trunk must match the configuration on the PXM1E end of the trunk.
PNNI UNI Port Configuration Quickstart
ATM UNI ports connect the switch to ATM end devices, which serve as the boundary between the ATM network and other communications paths or networks. Typical end devices include ATM routers and multiservice concentrators. UNI signaling is used between the end system (CPE) and the PNNI network for requesting calls.
The quickstart procedure in this section provides a summary of the tasks required to configure UNI ports on Cisco MGX 8850 (PXM1E) and Cisco MGX 8830 switches. This procedure is provided as an overview and as a quick reference for those who have previously configured UNI ports.
Note
Step 1
username
<password>
Start a configuration session.
Note
Step 2
—
Prepare PXM1E cards and lines as described in Chapter 4, "Preparing PXM1E Lines for Communication."
Remember to select the appropriate card SCT for the controller or controllers you are using.
Step 3
addport <options>
Related commands:
dspports
Add and configure ATM ports. This step establishes ATM layer two communications between two ATM devices.
Specify UNI for ATM lines.
See the "Adding ATM Ports" section later in this chapter.
Step 4
addpart <options>
Related commands:
dspparts
dsppart
cnfpart
Assign line resources to the PNNI controllers. This step can assign all the line bandwidth to a single controller, or it can assign portions of the line bandwidth to each controller.
See the "Partitioning Port Resources Between Controllers" section later in this chapter.
Step 5
dnpnport <portid>
Bring down the port so it can be configured. The next three steps require this step.
Step 6
cnfpnportsig <options>
Related commands:
dsppnports
dsppnport <portid>
dsppnportsig <portid>
Define the signaling protocol used on the line. The default signaling protocol for UNI lines is UNI Version 3.1.
Specify uni30, uni31, or uni40.
See the "Selecting the Port Signaling Protocol" section later in this chapter.
Step 7
cnfaddrreg <portid> no
addaddr <options>
Related commands:
dsppnports
dspatmaddr <portid>
deladdr <options>
Configure static ATM addresses for ports that require them.
See the "Assigning Static ATM Addresses to Destination Ports" section later in this chapter.
Step 8
addprfx <portid> atm-prefix
Related commands:
cnfaddrreg <portid> yes
dspprfx <portid>
If dynamic addressing is to be used on a port, define an ATM address prefix that ILMI can use when assigning addresses.
See the "Configuring ILMI Dynamic Addressing" section later in this chapter.
Step 9
uppnport <portid>
Bring up port after configuration is complete.
Step 10
upilmi <ifNum> <partId>
cnfilmi <options>
Related commands:
dspports
dspilmis
Configure and start ILMI on the port. This step is required for dynamic addressing and the ILMI automatic configuration feature. Otherwise, it is optional.
See the "Configuring ILMI on a Port" section later in this chapter.
General PXM1E Configuration Procedures
This section describes the following general procedures for configuring PXM1E card communications:
•
•
•
Adding ATM Ports
The previous chapter described how to bring up physical lines by specifying the correct line port number. The line ports correspond to line connectors on the switch back cards. Bringing up a line establishes minimal connectivity between two nodes. When you add an ATM port to a line, you enable ATM communications over the line.
Each line can support UNI or NNI ports. UNI ports are used for lines that connect to PBXs, ATM routers, and other ATM devices that connect to the core ATM network through the switch. NNI ports are used for trunks that connect to other core ATM network devices, such as another Cisco MGX 8850 (PXM1E/PXM45) switch.
You must configure one ATM port for each line or trunk to enable ATM communications over that link. You define the port type when you add the ATM port to the line or trunk. The port type can be one of the following:
•
•
•
•
•
•
To add an ATM port to a line, use the following procedure.
Step 1
Step 2
mgx8830a.1.PXM.a > dsplns
Tip
Step 3
mgx8830a.1.PXM.a > dspportsThis command displays all ports on the PXM1E card in the ifNum (interface number) column. The interfaces listed include UNI, NNI, VUNI, VNNI, EVUNI, and EVNNI ports. Pay attention to the port numbers already in use. When you add a port, you must specify a port number that is unique on the PXM1E card. For example, if port number 2 is assigned to line 2.1 (bay 2, line 1), you cannot use port 2 on any other line on that PXM1E card.
Step 4
mgx8830a.1.PXM.a > addport <ifNum> <bay.line> <guaranteedRate> <maxRate> <sctID> <ifType> [vpi <vpi>] [-minvpi <minvpi>] [-maxvpi <maxvpi>]Table 11-2 lists the parameter descriptions for adding ports. Figure 11-2 shows the relationship between logical interface numbers and physical lines.
