Table Of Contents

Provisioning PXM1E Communication Links

Quickstart Provisioning Procedures

Line Configuration Quickstart

ATM Trunk Configuration Quickstart

PNNI UNI Port Configuration Quickstart

SVC 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 MGX 8830 or MGX 8850 (PXM1E) Configuration Quickstart

General PXM1E Configuration Procedures

Configuring the Card Mode

Setting Up Lines

Bringing Up Lines

Configuring Lines

Verifying Line Configuration

Configuring Inverse Multiplexing for ATM

Creating an IMA Group

Configuring an IMA Group

Adding an IMA Link to an IMA Group

Configuring IMA Links

Adding an IMA Port

Establishing Redundancy Between Two Lines with APS

Configuring Intracard APS Lines

Configuring Intercard APS Lines

Adding ATM Ports

Modifying ATM Ports

Partitioning Port Resources Between Controllers

Selecting the Port Signaling Protocol

Defining Destination Addresses for Static Links

Assigning Static ATM Addresses to Destination Ports

Configuring ILMI on a Port

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 Communications

Verifying PNNI Trunk Communications

Verifying End-to-End PNNI Communications

Provisioning and Managing SPVCs and SPVPs

Configuring Point-to-Point Connections

Configuring Point-to-Multipoint Connections

Adding Parties to a P2MP Root Connection

Obtaining the NSAP for a Party

Displaying a List of Connections

Displaying the Status of a Single Connection

Modifying P2P and P2MP Connections

Bringing Down a Connection

Bringing Up a Connection

Bringing Down a Party

Bringing Up a Party

Rerouting Connections

Rerouting a P2MP Party

Deleting Connections

Deleting a P2MP Party

Configuring and Managing a Connection to an IGX Feeder

Connecting a PXM1E Card to a UXM Card on an IGX feeder

Deleting an IGX Feeder

Provisioning PXM1E Communication Links

---

This chapter describes how to prepare PXM1E lines for physical connectivity to other switches. It describes how to add ports and connections that support ATM communications over the PXM1E lines to other devices.

This chapter provides a quickstart procedure for configuring PXM1E cards and lines and describes how to provision the link and connection types listed in Table 3-1.

---

Note The procedures in this chapter do not apply to the Cisco MGX 8850 (PXM45) or to the Cisco MGX 8950. PXM45 cards do not provide ATM lines. Cisco MGX 8850 (PXM45) and Cisco MGX 8950 switches support ATM communication on the AXSM card.

---

Table 3-1 PXM1E Link and Connection Types 

PXM1E Link or Connection Type	Description
PNNI trunks	PNNI trunks connect MGX switches to other MGX switches.
PNNI UNI ports	PNNI user-network interface (UNI) ports connect MGX switches to CPE.
SVCs1	SVCs are temporary connections that are brought up and torn down upon request from CPE.
SPVCs2	SPVCs are permanent connections that can be rerouted if a link fails.
PNNI virtual trunks	PNNI virtual trunks are used to traverse public networks. The virtual trunk endpoints are on separate networks, but the path between the networks is treated like a single link.
Cisco MGX 8850 (PXM1) feeder PNNI trunks	Feeder trunks link a feeder switch, such as a Cisco MGX 8230 or Cisco MGX 8250 switch, to a Cisco MGX 8850 Release 5 switch. The feeder switch concatenates relatively low speed traffic and feeds it over a higher speed interface to the Cisco MGX 8850 switch, which provide the link to the ATM network core.
BPX PNNI trunks	BPX PNNI trunks provide PNNI links between MGX 8850 switches and BPX switches that support PNNI. The BPX switch supports PNNI when connected to the Cisco SES PNNI Controller.
AINI3 links	AINI links enable connectivity between two independent PNNI networks and block the PNNI database exchange so the two networks remain independent.
IISP4 links	IISP links enable connectivity between two independent PNNI networks and block the PNNI database exchange so the two networks remain independent. IISP is the predecessor to AINI and should be used only when AINI is not supported on one or both ends of the link.
XLMI5 links	XLMI links connect PNNI networks to AutoRoute networks. XLMI links enable the expansion of AutoRoute networks using PNNI, and they facilitate migration from AutoRoute networking to PNNI.

1 SVC = switched virtual circuits

2 SPVC = soft permanent virtual circuit

3 AINI = ATM Inter-Network Interface

4 IISP = Interim Inter-Switch Protocol

5 XLMI = 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 (PXM45/PXM1E), Cisco MGX 8950, Cisco MGX 8830, and Cisco MGX 8880 Command Reference, Release 5 for detailed information.

---

---

Note Before you start configuring ATM connections, complete the general switch configuration as described in Chapter 2, "Configuring General Switch Features." Some of the procedures described in this chapter will not work if the switch has not been set up properly.

---

Quickstart Provisioning Procedures

The following sections present abbreviated procedures that you can use to configure lines and provision connections.

Line Configuration Quickstart

The quickstart procedure in this section provides a summary of the tasks required to prepare PXM1E cards and lines for configuration as ATM trunks and lines. This procedure is provided as an overview and as a quick reference for those who already have configured Cisco MGX 8850 (PXM1E) and Cisco MGX 8830 switches.

	Command	Purpose
Step 1	username <password>	Start a configuration session. Note To perform all the steps in this quickstart procedure, you must log in as a user with GROUP1 privileges or higher.
Step 1	cnfcdmode <mode>	Configure the operational mode of all lines on PXM1E cards that support T1, E1, T3 or E3 lines. This step selects either T1 or E1, or either T3 or E3, depending on the card type. Note You need to configure the card mode before you provision connections on the PXM1E card.
Step 2	upln <bay.line> Related commands: dsplns dspln -type <bay.line>	Bring up and configure lines. This step establishes physical layer connectivity between two switches. See the "Setting Up Lines" section later in this chapter.
Step 3	cnfln <options> Related commands: dsplns dspln -type <bay.line>	Configure lines if the default configuration parameters must be changed. See the "Configuring Lines" section later in this chapter.
Step 4	addapsln <workingIndex> <protectIndex> <archmode> dspapslns dspapsln working-slot.bay.line>	Configure a redundant relationship between two PXM1E lines. See the "Establishing Redundancy Between Two Lines with APS" section later in this chapter.

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 The trunk configuration is not complete until the following procedure has been completed on the switches at both ends of the trunk.

---

	Command	Purpose
Step 1	username <password>	Start a configuration session. Note To perform all the steps in this quickstart procedure, you must log in as a user with GROUP1 privileges or higher.
Step 2		Bring up PXM1E lines as described in the "Line Configuration Quickstart," which appears earlier in this chapter.
Step 3	addport <options> or addimagrp <options> addimalnk <options> addimaport <options> Related commands: dspports dspimalnk dspimalnks dspimagrp dspimagrps	Add and configure ATM ports. This step establishes ATM layer two communications between two ATM devices. Note The PNNI or MPLS controller must be added before adding ports for ATM trunks. Procedures for adding controllers can be found in Chapter 2, "Configuring General Switch Features." Specify NNI for interswitch trunks. For standard port configuration, 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 4	cnfport <options> Related commands: dspport dspports	Use this optional step if you need to make changes to the port created in the previous step. For more information on modifying ports, see the "Modifying ATM Ports" section later in this chapter.
Step 5	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 6	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 none. Specify pnni10 for PNNI trunks. See the "Selecting the Port Signaling Protocol" 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.
Step 8	upilmi <ifNum> <partId> cnfilmi <options> Related commands: dspports dspilmis	This optional step configures and starts the integrated local management interface (ILMI) protocol 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 "Provisioning and Managing 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 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 The link configuration is not complete until the equipment at both ends of the line has been configured with compatible configuration settings.

---

	Command	Purpose
Step 1	username <password>	Start a configuration session. Note To perform all the steps in this quickstart procedure, you must log in as a user with GROUP1 privileges or higher.
Step 2		Bring up a PXM1E line for connection to an ATM end device as described in the "Line Configuration Quickstart," which appears earlier in this chapter.
Step 3	addport <options> or addimagrp <options> addimalnk <options> addimaport <options> Related commands: dspports dspimalnk dspimalnks dspimagrp dspimagrps	Add and configure ATM ports. This step establishes ATM layer two communications between two ATM devices. Note The PNNI or MPLS controller must be added before adding UNI ports. Procedures for adding controllers can be found in Chapter 2, "Configuring General Switch Features." Specify UNI for ATM lines. For standard port configuration, 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 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 none. 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>	If required, configure static ATM addresses for the PXM1E UNI port. 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 the 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 The tasks in the following procedure do not have to be completed in the order presented. However, all tasks must be completed before SVCs will operate.

---

	Command	Purpose
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 9, "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 VCIs, whereas an 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.

	Command	Purpose
Step 1	username <password>	Start a configuration session. Note To perform all the steps in this quickstart procedure, you must log in as a user with GROUP1 privileges or higher.
Step 2	See "ATM Trunk Configuration Quickstart," which appears earlier in this chapter.	Configure the trunks that link the switches to which the ATM end stations connect.
Step 3	dsppnni-reachable-addr network	Verify PNNI connectivity between the two nodes that will host the SPVC or SPVP end points. See "Verifying End-to-End PNNI Communications," which appears later in this chapter.
Step 4	See "PNNI UNI Port Configuration Quickstart," which appears earlier in this chapter.	Configure lines for the ATM end stations at each end of the SPVC or SPVP, and assign either static or dynamic addressing to each line.
Step 5	addcon <options> Related commands: dspcons dspcon <ifNum> <vpi> <vci>	Configure the slave side of the connection. See "Configuring the Slave Side of SPVCs and SPVPs," which appears later in this chapter.
Step 6	addcon <options> Related commands: dspcons dspcon <ifNum> <vpi> <vci>	Configure the master side of the connection. See "Configuring the Master Side of SPVCs and SPVPs," which appears later in this chapter.

PNNI Virtual Trunk Configuration Quickstart

Virtual trunks are introduced in the "Multiservice Edge Aggregation" section in "Preparing for Configuration." Figure 3-1 shows illustrates how a virtual trunk is configured.

Figure 3-1 Virtual Trunk Topology

Figure 3-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 1 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 32 VNNI ports on the node.

To set up a virtual trunk, the following tasks have to be completed:

•Virtual trunks must be defined between the private network nodes and the core edge nodes.

•The core network operators must define an SPVP for each virtual trunk that connects the core edge nodes on the virtual trunk path.

The Cisco MGX switches support:

•Up to 256 SPVPs across an ATM core network (or ATM cloud). The range is from 0 to 255.

•Up to 60 virtual trunks on a physical interface with a total of 60 per PXM1E card and 100 ports per switch.

•Multiple SPVPs on a virtual trunk when the EVNNI port type is selected and a range of VPIs is configured.

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.

	Command	Purpose
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 To perform all the steps in this quickstart procedure, you must log in as a user with GROUP1 privileges or higher.
Step 2		Bring up PXM1E lines as described in the "Line Configuration Quickstart," which appears earlier in this chapter.
Step 3	addport <options> or addimagrp <options> addimalnk <options> addimaport <options> Related commands: dspports dspimalnk dspimalnks dspimagrp dspimagrps	Configure the virtual trunk end ports at the private switches. Valid virtual trunk port types are VNNI and EVNNI. For standard port configuration, 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 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.
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 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 "Provisioning and Managing 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 endpoints. 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 a 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 The trunk configuration is not complete until the BXM end of the trunk is configured.

---

---

Caution You need to allocate PNNI resources before you can configure a BPX PNNI trunk. To verify that the PNNI resource has been allocated on the trunk, enter the dsprsrc <slot.port> command.

---

	Command	Purpose
Step 1	username <password>	Start a configuration session. Note To perform all the procedures in this quickstart procedure, you must log in as a user with GROUP1 privileges or higher.
Step 2		Bring up PXM1E lines as described in the "Line Configuration Quickstart," which appears earlier in this chapter.
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 pnni10 See 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 "Provisioning and Managing 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.

	Command	Purpose
Step 1	username <password>	Start a configuration session. Note To perform all the steps in this quickstart procedure, you must log in as a user with SUPER_GP privileges or higher.
Step 2		Bring up the PXM1E line that will become the AINI trunk as described in the "Line Configuration Quickstart," which appears earlier in this chapter.
Step 3	addport <options> or addimagrp <options> addimalnk <options> addimaport <options> Related commands: dspports dspimalnk dspimalnks dspimagrp dspimagrps	Add and configure an ATM port for the AINI trunk. This step establishes ATM communications between two ATM devices. Specify NNI for interswitch trunks. For standard port configuration, 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 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> Related commands: dsppnports dsppnport <portid> dsppnportsig <portid>	Define the signaling protocol used at the local end of the AINI trunk. The default signaling protocol is none. Specify aini for AINI trunks. For example: 8850_LA.7.PXM.a > cnfpnportsig 1:1.1:1 -nniver aini See the "Selecting the Port Signaling Protocol" section later in this chapter.
Step 6	cnfpnportsig <options>	At one end of the AINI trunk, VPI and VCI allocation must be disabled. VPI and VCI allocation is enabled by default on a PXM1E trunks. To disable this feature, enter the command: 8850_LA.7.PXM.a > cnfpnportsig 1:1.1:1 -vpivcialloc disable
Step 7	uppnport <portid>	When signaling configuration is complete, bring up the port.
Step 8	addaddr <options>	Add destination addresses to local end of the trunk. See the "Defining Destination Addresses for Static Links" section later in this chapter.
Step 9	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 AINI is a newer protocol that is designed to replace the function of IISP. Unless you are configuring a link with another switch that does not support AINI, you should configure an AINI link instead of an IISP link. IISP links provide fewer capabilities than AINI links. For example, IISP links cannot support UNI 4.0 connections.

---

	Command	Purpose
Step 1	username <password>	Start a configuration session. Note To perform all the steps in this quickstart procedure, you must log in as a user with SUPER_GP privileges or higher.
Step 2		Bring up the PXM1E line that will serve as the IISP trunk as described in the "Line Configuration Quickstart," which appears earlier in this chapter.
Step 3	addport <options> or addimagrp <options> addimalnk <options> addimaport <options> Related commands: dspports dspimalnk dspimalnks dspimagrp dspimagrps	Add a port to the IISP trunk. This step establishes ATM communications between two ATM devices. Specify NNI for interswitch trunks. For standard port configuration, 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 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 the local end of the IISP trunk. The default signaling protocol is none. Specify either iisp30 or iisp31 for IISP trunks. For example: mgx8830a.1.PXM.a > cnfpnportsig 1:1.1:1 -nniver iisp31 -side [network|user] One side of the IISP trunk must be defined as the network side and one side must be defined as the user side. The side that issues VPIs and VCIs is the network side. See 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 do the following tasks:

1. Configure a PXM1E port for the XLMI link.

2. Configure a BXM port for the XLMI link.

3. Create a connection between a destination on the PNNI network and a destination on the AutoRoute network.

The quickstart procedure in this section describes how to configure a 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:

•XLMI cannot be provisioned on a port which already has connections provisioned. To change the port to XLMI, you must first delete all existing connections.

•The control VC for LMI uses VPI = 3 and VCI = 31. These numbers are not allowed on other types of connections.

•Each PXM1E card supports a maximum of 16 links to AutoRoute networks and feeder nodes.

•Each PXM1E port can support one link to an AutoRoute network, so the maximum number of links to AutoRoute networks is equal to the maximum number of physical PXM1E ports.

•XLMI links support SPVCs and SPVPs. SVCs and LVCs are not supported.

•XLMI is not supported on virtual trunks.

•The various XLMI timers are not configurable on the PXM1E. Timer configuration is done on the BPX. The values for the LMI timers on PXM1E are

–LMI SPVC Status Enquiry Timer (T393): 10 sec

–LMI SPVC Update Status Timer (T394): 10 sec

–LMI Retry Timers (N394 and N395): 5 sec

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.

	Command	Purpose
Step 1	username <password>	Start a configuration session. Note To perform all the steps in this quickstart procedure, you must log in as a user with SUPER_GP privileges or higher.
Step 2		Bring up PXM1E lines as described in the "Line Configuration Quickstart," which appears earlier in this chapter.
Step 3	addport <options> or addimagrp <options> addimalnk <options> addimaport <options> Related commands: dspports dspimalnk dspimalnks dspimagrp dspimagrps	Add and configure ATM ports. This step establishes ATM communications between two ATM devices. The PXM1E cards supports XLMI on UNI or NNI ports. For standard port configuration, 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 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 2 Replace 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 enni See 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 The PNNI connection you create must use the same VPI and VCI as the connection defined in the AutoRoute network. See the "Provisioning and Managing SPVCs and SPVPs" section later in this chapter. Note Connections added with the CLI (addcon) command cannot be managed by CWM. If you are using CWM, create the connection with CWM. Afterwards, you can modify the connection with CWM or the CLI.
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 The AutoRoute connection you create must use the same VPI and VCI as the connection defined in the PNNI network. For more information, refer to the Cisco BPX 8600 Series Installation and Configuration guide.

Cisco IGX Feeder to MGX 8830 or MGX 8850 (PXM1E) 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.

	Command	Purpose
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 To perform all the steps in this quickstart procedure, you must log in as a user with SUPER_GP privileges or higher.