Table Of Contents

Provisioning PXM1E Communication Links

Quickstart Provisioning Procedures

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 Cisco MGX 8850 Configuration Quickstart

PNNI UNI Port Configuration Quickstart

General PXM1E Configuration Procedures

Adding ATM Ports

Partitioning Port Resources Between Controllers

Selecting the Port Signaling Protocol

Assigning Static ATM Addresses to Destination Ports

Configuring ILMI on a Port

Configuring PXM1E Line Clock Sources

Procedures for PNNI Links

Verifying PNNI Communications

Configuring SPVCs and SPVPs

Configuring Point-to-Multipoint SPVCs and SPVPs

Deleting SPVCs and SPVPs

Defining Destination Addresses for Static Links

Configuring Inverse Multiplexing for ATM

Creating an IMA Group

Configuring an IMA Group

Adding an IMA Link to an IMA Group

Adding an IMA Port

Configuring 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 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.

Table 11-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 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 4 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 witches 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 either end 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 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 Before you start configuring ATM connections, complete the general switch configuration as described in Chapter 3, "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 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 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		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 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	—	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 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 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:

•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.

•Virtual trunks can support SPVPs, provided a range of VPIs is configured in the virtual trunk's partition.

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		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 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 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 <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 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		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 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 " 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.

	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		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 aini 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.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		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 iisp31 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 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 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:

•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	—	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 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 " Configuring 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 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.

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

• Partitioning Port Resources Between Controllers

• Selecting the Port Signaling Protocol

• Assigning Static ATM Addresses to Destination Ports

• Configuring ILMI on a Port

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:

•UNI

•NNI

•VUNI

•VNNI

•EVUNI

•EVNNI

To add an ATM port to a line, use the following procedure.

---

Step 1 Establish a configuration session using a user name with GROUP1 privileges or higher.

Step 2 Get the line number on which you will add the port. To display a list of the lines and line numbers, enter the following command:

mgx8830a.1.PXM.a > dsplns

---

Tip Remember that you cannot configure a line until you have brought it up as described in " Bringing Up Lines," in Chapter 4, "Preparing PXM1E Lines for Communication."

---

Step 3 Verify that the line and port number you want to use is not configured. To display a list of the ports configured on the PXM1E card, enter the following command:

mgx8830a.1.PXM.a > dspports




This 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 To add an ATM port to a line, enter the following command:

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.

Table 11-2 Parameters for addport Command 

Parameter	Description
ifNum	An ATM port is also called an interface. An ATM port is defined by its slot, bay, line, and interface numbers. You do not have to enter a slot number during port configuration because you identify the slot number when you select the card. Enter a number from 1 to 31 to identify this interface. For UNI and NNI ports, you can assign one logical interface per line.
bay	Replace <bay> with 2 to indicate the lower bay.
line	Replace <line> with the number that corresponds to the back card port to which the line is connected.
guaranteedRate	Enter the minimum rate for the port in cells per second (cps). Note The <guaranteedRate> value should equal the <maxRate> value. The rate ranges for PXM1E are as follows: OC3: 50 - 353207. T3: 50 - 96000 (PLCP) or 104268 (ADM). E3: 50 - 80000. T1: 50-3622 cps E1: 50-4528 cps
maxRate	Enter the maximum rate for the port in cps. Note The <maxRate> value should equal the <guaranteedRate> value. The rate ranges are as follows: OC3: 50 - 353207. T3: 50 - 96000 (PLCP) or 104268 (ADM). E3: 50 - 80000. T1: 50-3622 cps E1: 50-4528 cps
sctID	Enter the port SCT number (0 to 255). For PNNI communications, use SCT ID 2 or 4 for policing applications and use SCT ID 3 or 5 for non-policing applications. Note If the PXM1E back card is T1/E1, use the provided SCTs 52 and 53. If you plan to use IMA with 1-4 IMA links, use provided SCT 54 or 55. Note Cisco Systems recommends that you use non-policing SCT IDs for all ports configured with the NNI interface type.
ifType	Enter a number that indicates the interface type as follows: 1—UNI 2—NNI, 3—VNNI 4—VUNI 5—EVUNI 6—EVNNI
vpi	Virtual Path Identifier: •UNI, Range 1-4095 •NNI, Range 1-4095 •VNNI, Range: 1-4095 •VUNI, Range: 1-255 •EVUNI, Range: 0-255 •EVNNI, Range: 0-4095
minvpi	Minimum VPI between 0 and 255 for EVUNI, 0 and 4095 for EVNNI.
maxvpi	Maximum VPI between 0 and 255 for EVUNI, 0 and 4095 for EVNNI.

Figure 11-2 Relationship Between Cards, Bays, Lines, and Logical Interface Numbers

The following example command defines a line port as a UNI line:

mgx8830a.1.PXM.a > addport 1 2.1 96000 96000 1 1




The following example command defines a line port as an NNI trunk:

mgx8830a.1.PXM.a > addport 2 2.1 3622 3622 52 2




Step 5 To display a list of the ports configured on the PXM1E card, enter the following command:

mgx8830a.1.PXM.a > dspports




This command displays all configured ports on the PXM1E card. Port numbers are listed in the ifNum (interface number) column. If you want to view information on a particular port, note the number of that port.

Step 6 To display the port configuration, enter the following command:

mgx8830a.1.PXM.a > dspport <ifNum>




Replace <ifNum> with the number assigned to the port during configuration. The following example shows the report for this command:

mgx8830a.1.PXM.a > dspport 1

Interface Number : 1

Line Number : 2.3 IMA Grp Number : N/A

Admin State : Up Operational State : Up

Guaranteed bandwidth(cells/sec): 353207 Number of partitions : 1

Maximum bandwidth(cells/sec) : 353207 Number of SPVC : 0

ifType : NNI Number of SPVP : 0

VPI number (VNNI, VUNI) : 0 Number of SVC : 3

MIN VPI (EVNNI, EVUNI) : 0 MAX VPI (EVNNI, EVUNI): 0

SCT Id (Conf./InUse) : 0/0=Def

, F4 to F5 Conversion : Disabled




---

---

Tip To change the port configuration, enter the cnfport command, or enter the delport command to delete a port configuration. You can also activate and deactivate ports entering the upport and dnport commands. For more information on these commands, refer to the Cisco MGX 8850 (PXM1E/PXM45), Cisco MGX 8950, and Cisco MGX 8830 Command Reference.

---

Partitioning Port Resources Between Controllers

After you add a line or trunk port, you need to define how the port resources are used by the PNNI controller. You can assign the following resources to controllers:

•Range of VPI values

•Range of VCI values

•Guaranteed percent of bandwidth for ingress and egress directions

•Minimum and maximum number of connections

---

Note You can and should use the partition definition to control how available connections are distributed within the switch. Each switch, card, and port supports a maximum number of connections. Although you can enable the maximum number of connections on all ports, two or three very busy ports could use all available connections and disable communications on all other ports.

---

The port resources are defined as a group in a controller partition, which is dedicated to a single port controller. You must define one controller partition for each controller type you want to support, and you must configure one resource partition for each port that uses a controller.

Figure 11-3 presents a simplified view of the relationship between the port controller, controller partition, and resource partitions on MGX switches with PXM1E controllers. Because a PXM1E controller supports ATM connections on Cisco MGX 8850 (PXM1E) and Cisco MGX 8830 switches, you can configure resource partitions directly on the PXM1E card.

Figure 11-3 Relationship of Port Controller, Controller Partition, and Resource Partitions

Figure 11-3 shows that the single controller partition connects to the port controller and to the resource partitions. Note that the port controller and the controller partition both reside on the PXM1E card.

After you create a port, you must create a resource partition for that port, select the PNNI controller, and define which ATM resources the port will use. You do not have to create the controller partition, as it is automatically created when you create the first resource partition. It is important that the same controller partition, and therefore the same partition ID, be used for all resource partitions of the same type on the same PXM1E card. For example, the controller is identified by the controller ID and the controller partition is identified by the partition ID. The resource partitions are identified by specifying the partition ID in combination with the port ID (interface number).

---

Note Partition ID 1 is reserved for PNNI.

---

To create a resource partition for a port, use the following procedure.

---

Step 1 Establish a configuration session using a user name with GROUP1 privileges or higher.

---

Note You must add the PNNI controller and add a port before you create a resource partition for a port. For instructions on adding the controller, see the " Adding the PNNI Controller" section in Chapter 3, "Configuring General Switch Features." For instructions on adding ports, see the " Adding ATM Ports" section earlier in this chapter.

---

Step 2 Determine the port number to which you want to assign the resource partition. To display a list of the ports, enter the following command:

mgx8830a.1.PXM.a > dspports




This command displays all ports on the PXM1E card in the ifNum (interface number) column.

Step 3 To create a resource partition, enter the following command:

mgx8830a.1.PXM.a > addpart <ifNum> <partId> <ctrlrId> <egrminbw> <egrmaxbw> <ingminbw> <ingmaxbw> <minVpi> <maxVpi> <minVci> <maxVci> <minConns> <maxConns>




Table 11-3 describes the parameters for this command.

Table 11-3 Parameters for the addpart Command 

Parameter	Description
ifNum	Interface number or port number. This number identifies the port this resource partition configures. Enter the interface number that was assigned to the port when it was configured (see the " Adding ATM Ports" section earlier in this chapter).
partId	Partition identification number. Enter a number in the range of 1 to 20. On an PXM1E card, this number must be the same for all ports that use the same controller type. For example, if you assign the number 2 to the PNNI controller on any port, the partition ID for the PNNI controller on all other ports must be set to 2.
ctrlrId	Controller identification number. Enter the number 2 to specify the PNNI controller. For more information, refer to " Adding the PNNI Controller" in Chapter 3, "Configuring General Switch Features."
egrminbw	Egress minimum bandwidth. Enter the minimum percentage of the outgoing port bandwidth that you want assigned to the specified controller. One percent is equal to .0001 units. For example, an <egrminbw> of 250000 = 25%. The sum of the minimum egress bandwidth settings for PNNI must be 100% or less, and must be less than the sum of the egrmaxbw settings.
egrmaxbw	Egress maximum bandwidth. Enter the maximum percentage of the outgoing port bandwidth that you want assigned to the controller. One percent is equal to .0001 units. For example, an <egrmaxbw> of 1000000 = 100%. The sum of the maximum egress bandwidth settings for PNNI can exceed 100%, and must be more than the sum of the egrminbw settings. Available bandwidth above the minimum bandwidth settings is allocated to the operating controllers on a first-requested, first-served basis until the maximum bandwidth setting is met or there is insufficient bandwidth to meet the request.
ingminbw	Ingress minimum bandwidth. Enter the minimum percentage of the incoming port bandwidth that you want assigned to the controller. One percent is equal to .0001 units. For example, an <ingminbw> of 500000 = 50%. The sum of the minimum ingress bandwidth settings for PNNI must be 100% or less, and must be less than the sum of the ingmaxbw settings.
ingmaxbw	Ingress maximum bandwidth. Enter the maximum percentage of the incoming port bandwidth that you want assigned to the controller. One percent is equal to .0001 units. For example, an <ingmaxbw> of 750000 = 75%. The sum of the maximum ingress bandwidth settings for PNNI can exceed 100%, and must be more than the sum of the ingminbw settings. Available bandwidth above the minimum bandwidth settings is allocated to the operating controllers on a first-request, first-served basis until the maximum bandwidth setting is met or there is insufficient bandwidth to meet the request.
minVpi	Minimum VPI. For NNI, the range is 0-4095. For UNI, the range is 0-255.
maxVpi	Maximum VPI in the range 0-4095 for an NNI. For a UNI, the range is 0-255. The maxvpi cannot be less than the minvpi.
minVci	The minimum VCI has a range of 1-65535.
maxVci	Maximum VPI in the range 0-4095 for an NNI. For a UNI, the range is 0-255. The maxvpi cannot be less than the minvpi.
minConns	Specifies the guaranteed number of connections. On the PXM1E UNI/NNI, the ranges vary according to the line types, as follows: •For OC3, T3, and E3 lines, the range is 10-27000. •For T1 and E1 lines, the range is 10-13500.
maxConns	Specifies the guaranteed number of connections. On the PXM1E UNI/NNI, the ranges vary according to the line types, as follows: •For OC3, T3, and E3 lines, the range is 10-27000. •For T1 and E1 lines, the range is 10-13500.

Step 4 To display a list showing the resource partition you have created, enter the following command:

mgx8830a.1.PXM.a > dspparts




Step 5 To display the configuration of a specific resource partition, note the interface and partition numbers and enter the following command:

mgx8830a.1.PXM.a > dsppart <ifNum> <partId>




Table 11-3 describes the parameters for this command.

The following example shows the report provided by the dsppart command.

mgx8830a.1.PXM.a > dsppart 1 1

Interface Number : 1

Partition Id : 1 Number of SPVC: 0

Controller Id : 2 Number of SPVP: 0

egr Guaranteed bw(.0001percent): 1000000 Number of SVC : 0

egr Maximum bw(.0001percent) : 1000000

ing Guaranteed bw(.0001percent): 1000000

egr Maximum bw(.0001percent) : 1000000

min vpi : 0

max vpi : 4095

min vci : 1

max vci : 65535

guaranteed connections : 10000

maximum connections : 10000




---

Note Partition ID 1 is reserved for PNNI.

---

---

---

Note For more information on working with partitions, see the " Managing PXM1E Partitions" section in Chapter 13, "Switch Operating Procedures."

---

Selecting the Port Signaling Protocol

The default signaling protocol for all new ports is UNI Version none. If you plan to use this protocol on a line, you can accept this default and skip this section. However, if you plan to use a different protocol on the line, such as NNI or PNNI, you must select the correct protocol using the following procedure.

---

Step 1 Establish a configuration session using a user name with GROUP1 privileges or higher.

Step 2 Enter the dsppnports command to display a list of the ports you can configure.

mgx8830a.1.PXM.a > dsppnports




Step 3 Enter the dnpnport command to bring down the port you want to configure.

mgx8830a.1.PXM.a > dnpnport <portid>




A port is automatically brought up when you add it. You must bring down the port before you can change the port signaling protocol. Replace <portid> using the format slot[:bay].line[:ifNum]. Table 11-4 describes these parameters.

Step 4 To confirm the port is down, enter the dsppnports command. The following example shows the report that appears.

mgx8830a.1.PXM.a > dsppnports

Summary of total connections

(p2p=point to point,p2mp=point to multipoint,SpvcD=DAX spvc,SpvcR=Routed spvc)

Type #Svcc: #Svpc: #SpvcD: #SpvpD: #SpvcR: #SpvpR: #Ctrl #Total:

p2p: 0 0 0 0 1 0 0 1

p2mp: 0 0 0 0 0 0 0 0




Total(User cons) = 1/27000, Total(Ctrl cons) = 0

Total=1




Summary of total SPVC endpoints

(P=Persistent, NP=Non-Persistent)

Type #SpvcR-P #SpvcR-NP #SpvpR-P #SpvpR-NP #SpvcD #SpvpD Total

p2p: 2 0 0 0 0 0 2

p2mp: 0 0 0 0 0 0 0

Total=2




Summary of total active SVC/SPVC intermediate endpoints

Type #Svcc #Svpc #SpvcR #SpvpR Total

p2p: 0 0 1 0 1

p2mp: 0 0 0 0 0

Total=1





Type <CR> to continue, Q<CR> to stop:

DSPPNPORTS EndPoint Grand Total = 3/54000

Per-port status summary




PortId LogicalId IF status Admin status ILMI state #Conns




1.35 16845603 up up NotApplicable 0




1.36 16845604 up up NotApplicable 0




1.37 16845605 up up NotApplicable 0




1.38 16845606 up up NotApplicable 0




4.1 16851713 up up NotApplicable 1




1:2.1:3 16845571 up up NotApplicable 0




1:2.3:1 16845569 up up Disable 1




Step 5 To select the port signaling protocol, enter the following command:

mgx8830a.1.PXM.a > cnfpnportsig <portid> [-univer {uni30|uni31|uni40|q2931|none|self}] [-nniver {iisp30|iisp31|pnni10|enni|aini}] [-unitype {public|private}] [-addrplan {both|aesa|e164}] [-side {user|network}] [-vpi <vpi>] [-sigvci <signalling-vci>] [-rccvci <routing-vci>] [-cntlvc <ip>][-passalongcap {enable|disable}] [-hopcntgen {enable|disable}] [-vpivcialloc {enable|disable}] [-svcroutingpri <svcroutingPriority>]




The only required parameter for this command is the <portid> parameter, but the command serves no purpose if you do not enter at least one option with it. If you include some options with the command and omit others, the omitted option remains set to the last configured value.

Table 11-4 shows the components required in the <portid> parameter, which is used with many commands. Table 11-5 lists and describes the options and parameters for the cnfpnportsig command.

---

Tip With some commands, you can refer to a port using only the interface number, while other commands require you to enter a complete port identification number, which includes the slot, bay, line, and interface numbers. When entering controller related commands at the PXM1E switch prompt (such as PNNI signaling commands), you always need to specify the complete port identification number. When entering interface related commands at the PXM1E switch prompt, you can enter only the interface number, because the interface number is unique on the PXM1E card and identifies the bay and line for the port.

---

Table 11-4 Port Identification Parameters 

Parameter	Description
slot	Enter the logical slot number for the card that hosts the port you are configuring.
bay	Replace <bay> with 2 to indicate that the line is connected to a back card in the lower bay. Remember that the bay number is always 2 for a PXM1E.
line	Replace <line> with the number that corresponds to the back card port to which the line is connected.
ifNum	An ATM port is also called an interface. Enter a number from 1 to 31 to identify this interface. The interface number must be unique on the card to which it is assigned. An ATM port is defined by its slot, bay, line, and interface numbers. You do not have to enter a slot number during port configuration because you identify the slot number when you select the card.

Table 11-5 Port Signaling Configuration Parameters 

Parameter	Description
<portid>	Port identifier in the format slot:bay.line:ifnum. These parameters are described in Table 11-4.
-univer	When configuring PNNI signaling for a UNI port, you can use this option to specify which version of UNI signaling you want the port to use. You can select UNI version 3.0 (uni30), UNI version 3.1 (uni31), UNI version 4.0 (uni40), ENNI (enni), or no UNI signaling (none). The default value is none. For lines that will support ABR SVCs, select uni40. The UNI ports at each end of a virtual trunk SPVP must be set to none. SPVCs and SPVPs can use UNI 3.x or 4.0 signaling.
-nniver	When configuring PNNI signaling for an NNI port, you can use this option to specify which signaling protocol you want the port to use. You can select IISP version 3.0 (iisp30), IISP version 3.1 (iisp31), PNNI version 1.0 (pnni10), ENNI (enni), or AINI (aini). The NNI ports at each end of a virtual trunk SPVP must be set to none.
-unitype	When configuring PNNI signaling for a UNI port, you can use this option to specify the UNI type. You can define the port as a private UNI port (private) or as a public UNI port (public). The default value is private.
-addrplan	When configuring PNNI signaling for a UNI port, this parameter specifies the ATM address plan used on this port. You can select AESA (aesa), E.164 (e164), or both (both). The default value is aesa.
-side	Defines the role of the signaling service used on the port. This parameter applies to IISP ports when static addressing is used (address registration is disabled). If this is a UNI connection or an NNI connection within the network, select network. For connections to other networks, you might need to select user (this is negotiated with the administrators of the other network). The default value is network.
-vpi	Defines the VPI for signaling services on this port. Enter a value in the range from 0 to 4095. The default value is 0.
-sigvci	Defines the VCI for signaling services on this port. The default value is 5, which is the well-known, reserved VCI for signaling services on VPI 0. If you choose another VCI for signaling, choose a VCI value in the range from 32 to 65535. Otherwise, the VCI can conflict with other VCIs in the reserved range from 0 to 31 on VPI 0.
-rccvci	Defines the VCI for the PNNI Routing Control Connection (RCC1) on this port. The default value is 18, which is the well-known, reserved VCI for this services on VPI 0. If you choose another VCI for signaling, choose a VCI value in the range of 32 to 65535. Otherwise, the VCI can conflict with other VCIs in the reserved range from 0 to 31 on VPI 0.
-cntlvc	This option defines a feeder trunk. The syntax for the feeder trunk definition is: pop20two.7.PXM.a > cnfpnportsig <portid> -cntlvc ip
-passalongcap	Pass-along capability: type enable or disable. With this capability, the port has the ability to pass along unrecognized information elements (IEs) or messages. Enabling or disabling the pass-along capability applies to AINI, IISP, and public UNI. For all other types, the port behaves as if pass-along is enabled—you cannot disable pass-along on the other port types. Default: enable
-hopcntgen	This parameter applies to AINI only. Type the entire word enable or disable. If you enable hop counting for AINI, the controller generates the hop counter information IE for all setup messages that pass through the interface if this IE does not already exist in the setup message. You must also enable AINI hop count IE for the switch by entering the cnfainihopcount command.
-vpivcialloc	This parameter applies to AINI: type enable or disable. If you enable it, the interface becomes responsible for assigning the VPI and VCI for all connections. if you enable VPI/VCI allocation on one side of the AINI link, allocation must be disabled on the other side of the link,
-svcroutingpri	Assign a routing priority at the port level for SVC, an SPVC, or an SPVP that has no priority. The Routing Priority feature does not support SVCs. However, port-level priority helps with the de-routing of SVCs in a way that supports the Priority Routing feature to re-route SPVCs and SPVPs.

1 Routing Control Connection

---

Note The selection of UNI or NNI is made when the port is added with the addport command. You cannot use the -univer and -nniver options to change the port type.

---

The following example illustrates how to configure an NNI port to use PNNI Version 1.0 signaling.

mgx8830a.1.PXM.a > cnfpnportsig 1:2.1:1 -nniver pnni10




Step 6 Enter the following command to define the local routing switch feeder port as a non-OAM segment endpoint:

mgx8830a.1.PXM.a > cnfoamsegep <portid> <enable_oam_diagnostics>




Replace <portid> using the format slot:bay.line:ifNum. Replace <oam diagnostics> with no to disable OAM diagnostics support. Table 11-4 describes these parameters.

---

Note This step is required to enable testing with the tstdelay command.

---




Step 7 Enter the following command to bring up the port you just configured:

mgx8830a.1.PXM.a > uppnport <portid>




Replace <portid> using the format slot:bay.line:ifNum. Table 11-4 describes these parameters.

Step 8 To verify the status of the port, enter the dsppnports command.

Step 9 To display the configuration of the PNNI port, enter the following command:

mgx8830a.1.PXM.a > dsppnport <portid>




Replace <portid> using the format slot:bay.line:ifNum. Table 11-4 describes these parameters. The following example shows the report for this command.

mgx8830a.1.PXM.a > dsppnport 1.35




Port: 1.35 Logical ID: 16845603

IF status: up Admin Status: up

UCSM: enable SVC Routing Pri: 8

Auto-config: enable Addrs-reg: enable

IF-side: network IF-type: uni

UniType: private Version: none

PassAlongCapab: n/a

Input filter: 0 Output filter: 0

minSvccVpi: 0 maxSvccVpi: 0

minSvccVci: 35 maxSvccVci: 0

minSvpcVpi: 1 maxSvpcVpi: 0




(P=Configured Persistent Pep, NP=Non-Persistent Pep, Act=Active)

#Spvc-P: #Spvc-NP: #SpvcAct: #Spvp-P: #Spvp-NP: #SpvpAct:

p2p : 0 0 0 0 0 0

p2mp: 0 0 0 0 0 0

#Svcc: #Svpc: #Ctrl: Total:

p2p : 0 0 0 0

p2mp: 0 0 0 0

Total: 0




---

Assigning Static ATM Addresses to Destination Ports

When a CPE does not support ILMI, the switch cannot automatically determine the CPE address. To enable communications with the CPE, you must assign a static ATM address to the port leading to the CPE. The static address must match the address used by the CPE. When assigning the static address, you can use command options to define how widely the static address is advertised within the switch network. Use the following procedure to define a static address for a UNI port.

---

Step 1 Establish a configuration session using a user name with GROUP1 privileges or higher.

Step 2 To locate the port to which you want to add an address, enter the dsppnports command.

Step 3 Enter the following command to turn off automatic address registration (it is enabled by default) on the port that will use the static address:

mgx8830a.1.PXM.a > cnfaddrreg <portid> no




Replace portid using the format slot:bay.line:ifNum. Table 11-4 describes these parameters.

Step 4 Specify an ATM address for the port using the following command:

mgx8830a.1.PXM.a > addaddr <portid> <atm-address> <length> [-type int] [-proto local] [-plan {e164 | nsap}] [-scope scope] [-redistribute {yes | no}] [-tnid tnid]




---

Note The addaddr command is used to specify static addresses for UNI links to CPE and to define destination addresses for AINI and IISP static links. The command format above shows the options that apply when defining static addresses for CPE.

---

Replace <portid> with the ID you used with the cnfaddreg command described earlier. Table 11-6 describes the other parameters used with the addaddr command.

---

Note The static ATM address you choose should conform to the address plan for your network. For more information on address planning, refer to the PNNI Network Planning Guide for MGX and SES Products.

---

Table 11-6 ATM Address Configuration Parameters 

Parameter	Description
portid	Port identifier in the format slot:bay.line:ifnum. These parameters are described in Table 11-4.
atm-address	Enter the ATM address using up to 40 nibbles. The ATM address can include up to 20 bytes, which is 40 nibbles or 160 bits.
length	Enter the length, in bits, of the address you specified with the <atm-address> parameter. Each nibble is equal to 4 bits. The acceptable range for the parameter is from 0 to 160 bits.
-type	Enter the address type, which is int (internal) for CPE static addresses. The ext (external) value is used when creating destination addresses for AINI and IISP static links. Note that because the default value is int, you do not have to specify this option when defining static CPE addresses. Default = int.
-proto	For CPE static addresses, specify the -proto option with the local value. The static value applies to AINI and IISP static links. Note that because the default value is local, you do not have to specify this option when defining static CPE addresses. Default = local.
-plan	Enter the address plan, which is either e164 (E.164) or nsap (NSAP). For an NSAP address, the first byte of the address automatically implies one of the three NSAP address plans: NSAP E.164, NSAP DCC, or NSAP ICD. Default = nsap.
-scope	PNNI scope of advertisement. The scope defines the level of the PNNI hierarchy at which this address is advertised. Enter 0 to advertise the destination address to all nodes in the node's peer group. Range: 0 to 104. Default = 0.
-redistribute	Specifies whether or not the ATM address should be distributed or advertised to PNNI neighbor nodes. Enter yes to enable distribution and enter no to disable. When this option is set to yes, the node distributes the address to the PNNI neighbors defined with the scope option. When set to no, the address is not advertised to any other nodes. Default = no.
-tnid	The transit network ID identifies a network where connections from the current node do not terminate.This number applies to static addresses only. The application of this option depends on the design intent of the user. The ID can have up to four IA5 characters (IA5 is a superset of the ASCII character set).

The following example assigns an ATM address to port 2:2.2:1:

mgx8830a.1.PXM.a > addaddr 1:2.1:3 47.1111.1111.1111.1111.1111.1111.1111.1111.1111.11 160




Step 5 To verify that the new address has been assigned, enter the dspatmaddr command as shown in the following example:

mgx8830a.1.PXM.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 type: internal proto: local

scope: 0 plan: nsap_icd redistribute: false

---

Configuring ILMI on a Port

ILMI is optional on most ports. Use ILMI on a port when you want to do any of the following tasks:

•Use ILMI automatic configuration, which negotiates ATM communication parameters

•Use ILMI address registration, which negotiates an ATM address for an attached CPE using an ILMI prefix assigned to the port

•Enable CWM auto-discovery on a link, which allows CWM to search for and discover Cisco Systems switches that it can manage

•Create a PNNI link to a BXM card on a BPX

ILMI is enabled by default on all signaling ports and remains in a down state until ILMI is started. There are two ways to start ILMI on a port. To configure and start ILMI with a single command, use the cnfilmi command. To start ILMI using the default values, enter the upilmi command. The following sections describe how to

•Configure ILMI traps and signaling and start ILMI

•Configure ILMI automatic configuration

•Configure ILMI dynamic addressing

•Start ILMI with the default trap and signaling parameters

---

Note For information on additional ILMI management procedures, see the " Managing ILMI"section in Chapter 13, "Switch Operating Procedures."

---

Configuring ILMI Traps and Signaling

The default ILMI configuration uses the standard ILMI signaling VPI and VCI, sets three ILMI signaling timers, and enables the distribution of ILMI management messages (traps) to SNMP managers such as CWM. If the defaults are acceptable, you can start ILMI on the port entering the upilmi command. To change the defaults and start ILMI, use the following procedure.

---

Note When ILMI is configured and started at one end of a link, it must be configured and started at the other end of the link before the link will operate properly.

---

---

Step 1 Establish a configuration session using a user name with GROUP1 privileges or higher.

Step 2 If you want to preview the current ILMI configuration for a port, enter the dspilmis command. The following example shows the dspilmis command report:

mgx8830a.1.PXM.a > dspilmis




Sig. rsrc Ilmi Sig Sig Ilmi S:Keepalive T:conPoll K:conPoll

Port Part State Vpi Vci Trap Interval Interval InactiveFactor

---- ---- ---- ---- ---- --- ------------ ---------- ----------

1 1 On      0 16 On 1 5 4

2    1   Off     0 16 On 1 5 4

    3 1 Off 0 16 On 1 5 4




The example above shows that ILMI is enabled on port 1 (ILMI State = On) and is disabled on ports 2 and 3 (ILMI State = Off). All other ILMI parameters are set to the default values.

---

Note The ILMI state displayed by the dspilmis command is the configuration state, not the operational state, which appears when you enter the dsppnports or dsppnilmi commands.

---

Step 3 Enter the cnfilmi command as follows:

mgx8830a.1.PXM.a > cnfilmi -if <ifNum> -id <partitionID> [-ilmi <ilmiEnable>] [-vpi <vpi>] [-vci <vci>] [-trap <ilmiTrapEnable>] [-s <keepAliveInt>] [-t <pollingIntervalT491>] [-k <pollInctFact>]




Table 11-7 describes the parameters for the cnfilmi command.

Table 11-7 cnfilmi Command Configuration Parameters 

Parameter	Description
ifNum	Interface number or port number. This number identifies the port on which you are configuring ILMI. Enter the interface number that was assigned with the addport command (see " Adding ATM Ports").
partitionID	Partition ID number. This number identifies the PNNI partition assigned to the port. Enter the partition number that was assigned to the port with the addpart command (see " Partitioning Port Resources Between Controllers"). Note Partition ID 1 is reserved for PNNI.
ilmiEnable	ILMI enable parameter. To change the current state of ILMI, enter 1 to enable or start ILMI or 2 to disable ILMI. Note that the default value is 1, which causes ILMI to start whenever the cnfilmi command is entered, unless you enter this parameter with value 2. Default =  1 (enable).
vpi	ILMI signaling VPI. If you need to change the default, enter a VPI number in the range of 0 to 255. Note that changing this value disables ILMI communications until the device at the remote end of the line has been configured for the same ILMI VPI. Default = 0.
vci	ILMI signaling VCI. If you need to change the default, enter a VCI number in the range of 0 to 65535. Note that changing this value disables ILMI communications until the device at the remote end of the line has been configured for the same ILMI VCI. Default = 16.
ilmiTrapEnable	ILMI trap distribution. When ILMI is started on a port, ILMI traps are sent to SNMP managers such as CWM. To enable or disable the distribution of ILMI traps, enter 1 to enable ILMI traps or 2 to disable ILMI traps. Default =  1 (enable).
keepAliveInt	ILMI keep alive timer. Range: 1 to 255. Default = 1.
pollingIntervalT491	ILMI polling interval T491 timer. Range: 0 to 255. Default = 5. Note 0 = no polling
pollInctFact	ILMI polling factor K. Range: 0 to 65535. Default = 4.

Step 4 To confirm your configuration changes, enter the dspilmis command.

---

Configuring ILMI Automatic Configuration

The Cisco MGX 8850 (PXM1E) and Cisco MGX 8830 switches support the automatic configuration feature of ILMI 4.0, which allows two devices that share a link to share their configurations and negotiate a common set of communication parameters. For example, if two network devices share a link and are configured for different maximum VCIs on a partition, the automatic configuration feature can determine and select the highest common VCI supported by both nodes. To use ILMI automatic configuration, the devices at each end of the link must support this ILMI 4.0 feature.

To enable or disable automatic configuration on a port, enter the cnfautocnf command as described in the following procedure.

---

Note A link between two nodes will not operate correctly if the ILMI automatic configuration feature is enabled at one end and disabled at the other.

---

---

Step 1 Establish a configuration session using a user name with GROUP1 privileges or higher.

Step 2 To display the automatic configuration status of a port, use the dsppnport command. For example:

mgx8830a.1.PXM.a > dsppnport 1:2.3:1

Port: 1:2.3:1 Logical ID: 16845569

IF status: up Admin Status: up

UCSM: enable SVC Routing Pri: 8

Auto-config: enable Addrs-reg: enable

IF-side: network IF-type: nni

UniType: private Version: pnni10

PassAlongCapab: n/a

Input filter: 0 Output filter: 0

minSvccVpi: 0 maxSvccVpi: 4095

minSvccVci: 35 maxSvccVci: 65535

minSvpcVpi: 1 maxSvpcVpi: 4095




(P=Configured Persistent Pep, NP=Non-Persistent Pep, Act=Active)

#Spvc-P: #Spvc-NP: #SpvcAct: #Spvp-P: #Spvp-NP: #SpvpAct:

p2p : 0 0 0 0 0 0

p2mp: 0 0 0 0 0 0

#Svcc: #Svpc: #Ctrl: Total:

p2p : 1 0 0 1

p2mp: 0 0 0 0

Total: 1




The Auto-config field shows whether the automatic configuration feature is enabled or disabled.

Step 3 If you want to enable or disable automatic configuration, bring down the port to be configured with the dnpnport command. For example:

mgx8830a.1.PXM.a > dnpnport 1:2.3:1




Step 4 To enable or disable the automatic configuration feature, enter the cnfautocnf command as follows:

mgx8830a.1.PXM.a > cnfautocnf <portid> <yes | no>




Replace portid with the port address using the format slot:bay.line:ifnum. These parameters are described in Table 11-4.

Enter yes to enable automatic configuration or enter no to disable automatic configuration. The default is yes.

Step 5 Up the port you configured with the uppnport command. For example:

mgx8830a.1.PXM.a > uppnport 1:2.3:1




Step 6 To verify the change, re-enter the dsppnport command.

---

Configuring ILMI Dynamic Addressing

Dynamic ATM addressing is enabled by default on all PXM1E ports. Once ILMI is started, ILMI can negotiate ATM addresses for CPE connected to the port. To determine the ATM address for the CPE, the switch uses a 13-byte ILMI prefix that is assigned to the port, a 6-byte end system ID, and a 1-byte selector byte. The end system ID and selector byte are defined on the end system. Depending on the end system configuration, the end system ID may correspond with the interface MAC address. For dynamic addressing to work, the remote device must support it. ILMI versions 3.x and 4.0 support dynamic address registration.

The default ILMI prefix matches the PNNI node prefix and the SPVC prefix, both of which are described in the PNNI Network Planning Guide for MGX and SES Products. If you change the PNNI node prefix, the SPVC prefix and the ILMI prefix remain unchanged. If you change the SPVC prefix, the ILMI prefix will change with it, as long as no ILMI prefix is assigned directly to the port. To eliminate the possibility of having a future SPVC prefix change affect dynamic addressing on a port, assign one or more ILMI prefixes to the port.

The following procedure describes how to enable or disable dynamic addressing and how to assign an ILMI address prefix to a port.

---

Note The Cisco MGX switches support up to 255 ILMI prefixes per PXM1E card, and these prefixes can be assigned to one port or distributed among the ports.

---

---

Step 1 Establish a configuration session using a user name with GROUP1 privileges or higher.

Step 2 To display the dynamic addressing status of a port, use the dsppnport command. For example:

mgx8830a.1.PXM.a > dsppnport 1:2.3:1




Port: 1:2.3:1 Logical ID: 16845569

IF status: up Admin Status: up

UCSM: enable SVC Routing Pri: 8

Auto-config: enable Addrs-reg: enable

IF-side: network IF-type: nni

UniType: private Version: pnni10

PassAlongCapab: n/a

Input filter: 0 Output filter: 0

minSvccVpi: 0 maxSvccVpi: 4095

minSvccVci: 35 maxSvccVci: 65535

minSvpcVpi: 1 maxSvpcVpi: 4095




(P=Configured Persistent Pep, NP=Non-Persistent Pep, Act=Active)

#Spvc-P: #Spvc-NP: #SpvcAct: #Spvp-P: #Spvp-NP: #SpvpAct:

p2p : 0 0 0 0 0 0

p2mp: 0 0 0 0 0 0

#Svcc: #Svpc: #Ctrl: Total:

p2p : 1 0 0 1

p2mp: 0 0 0 0

Total: 1

The Addr-reg field shows whether the dynamic addressing feature is enabled or disabled.

Step 3 To view the ILMI prefixes assigned to a port, enter the dspprfx command as follows:

mgx8830a.1.PXM.a > dspprfx <portid>




Replace portid with the port address using the format slot:bay.line:ifnum. These parameters are described in Table 11-4. For example:

mgx8830a.1.PXM.a > dspprfx 1:2.3:1




INFO: No Prefix registered




In the example above, no ILMI prefixes have been assigned to the port, so the port will use the prefix configured for the SPVC prefix.

Step 4 If you want to change the dynamic addressing configuration, bring down the port to be configured with the dnpnport command. For example:

mgx8830a.1.PXM.a > dnpnport 1:2.3:1




Step 5 To enable or disable dynamic address registration, enter the following command:

mgx8830a.1.PXM.a > cnfaddrreg <portid> <yes | no>




Enter yes to enable dynamic address configuration or enter no to disable it. The default is yes.

Step 6 Enter the following command to define an ATM prefix for a port:

mgx8830a.1.PXM.a > addprfx <portid> <atm-prefix>




Replace portid using the format slot:bay.line:ifNum. Table 11-4 describes these parameters.

Replace atm-prefix with the 13-byte ATM address prefix that you want the dynamically assigned address to use. Specify the address prefix using 26 hexadecimal digits. The range for each digit is 0 through F (0 through 9, A, B, C, D, E, and F).

---

Note The address prefix you choose should conform to the address plan for your network. For more information on address planning, refer to the PNNI Network Planning Guide for MGX and SES Products.

---

---

Tip Each hexadecimal digit represents 1 nibble (four bits), and each pair of hexadecimal digits represents a byte. There are 13 pairs of hexadecimal digits in the prefix, or 26 total digits.

---

Step 7 Up the port you configured with the uppnport command. For example:

mgx8830a.1.PXM.a > uppnport 1:2.3:1




Step 8 To verify the proper ATM prefix configuration for a port, re-enter the dspprfx command.

Step 9 To see a dynamically assigned address that uses the prefix, enter the dspilmiaddr <port> command.

---

Starting ILMI with the Default or Existing Values

The upilmi command starts ILMI on a port with the existing ILMI configuration, which is the default configuration when ILMI has never been configured on that port. Although ILMI starts automatically when you configure it with the cnfilmi command, you might have to bring down ILMI with the dnilmi command to make a configuration change such as adding an ILMI prefix. To start or restart ILMI with the upilmi command, use the following procedure.

---

Step 1 Establish a configuration session using a user name with GROUP1 privileges or higher.

Step 2 If you do not know the interface number and partition ID for the port on which you are starting ILMI, enter the dspparts command as shown in the following example.

mgx8830a.1.PXM.a > dspparts

if part Ctlr egr egr ingr ingr min max min max min max

Num ID ID GuarBw MaxBw GuarBw MaxBw vpi vpi vci vci conn conn

(.0001%)(.0001%)(.0001%)(.0001%)

-----------------------------------------------------------------------------

1 1 2 1000000 1000000 1000000 1000000 0 4095 1 65535 10000 10000

3 1 2 1000000 1000000 1000000 1000000 0 255 1 65535 2000 2000




---

Tip To see the relationship between interface numbers and lines, enter the dspports command.

---

---

Note Partition ID 1 is reserved for PNNI.

---

Step 3 To start ILMI on a port, enter the upilmi command as follows:

mgx8830a.1.PXM.a > upilmi <ifNum> <partId>




Replace ifNum with the interface number for the port, and replace partId with the partition number assigned to the port. For example:

mgx8830a.1.PXM.a > upilmi 2 1




Step 4 To display the ILMI status of all the ports on an PXM1E card, enter the dspilmis command. For example:

mgx8830a.1.PXM.a > dspilmis




mgx8830a.1.PXM.a > dspilmis




Sig. rsrc Ilmi Sig Sig Ilmi S:Keepalive T:conPoll K:conPoll

Port Part State Vpi Vci Trap Interval Interval InactiveFactor

---- ---- ---- ---- ---- --- ------------ ---------- ----------

1 1 On 0 16 On 1 5 4

3 1 Off 0 16 On 1 5 4




The ILMI State column displays the configured state for ILMI, which is On if ILMI is enabled and Off if ILMI is disabled (use dsppnports or dsppnilmi to see the operational state). The other columns display ILMI configuration parameters described in Table 11-7.

---

Configuring PXM1E Line Clock Sources

To configure the switch to receive a clock source on an PXM1E line, you must do the following:

•Connect a line between the PXM1E and the node with the clock source.

•Activate the line.

•Create a logical port (subport) for the clock signal.

•Create a resource partition.

---

Note If you are using NCDP to select the clock path for an MGX switch, you do not need to configure an PXM1E line clock source.

---

Chapter 4, "Preparing PXM1E Lines for Communication," describes how to activate a line. The procedures for creating ports and resource partitions appear earlier in this chapter. The following procedure describes how to configure an PXM1E clock source after the line and port have been configured.

---

Step 1 Establish a configuration session using a user name with GROUP1 privileges or higher.

Step 2 To set a primary or secondary PXM1E clock source, enter the following command:

mgx8830a.1.PXM.a > cnfclksrc <priority> [shelf.]<slot:bay.line:ifnum>




Table 11-8 describes the parameters for this command.

---

Tip To get the correct slot:bay.line:ifnum specification, use the port ID displayed by the dsppnports command.

---

Table 11-8 Parameter Descriptions for cnfclksrc Command when Used for PXM1E 

Parameter	Values	Descriptions
priority	primary or secondary	Replace priority with the type of clock source, which is either primary or secondary. The default is primary.
shelf	1	The shelf value is always 1, and it is optional.
slot	1 or 2 on a Cisco MGX 8830 7 or 8 on a Cisco MGX 8850 (PXM1E)	The slot identifies the slot number of the PXM1E card that is receiving the clock signal.
bay	1 or 2 on a Cisco MGX 8830 7 or 8 on a Cisco MGX 8850 (PXM1E)	The bay identifies the bay in which the back card is installed. If the clock source line is connected to upper card, enter 1. If it is connected to the lower card, enter 2. The default is 1 In a PXM1E card, the clock source line is always connection to the back card in the lower bay (2).
line	1 to 16	The line number corresponds to the line number on the back card. The line must already be active (using upln).
ifnum	1 to 31	The ifnum number corresponds to the interface number or logical port number, which is from 1 to 31. The interface number must have been previously defined using the addport command.

Step 3 To configure an additional clock source, repeat Step 2 using the correct parameters for the additional source.

---

The following command example shows how to configure a secondary clock source for subport (logical port) 10 on line 1 of the PXM1E card in the upper bay of slot 3. Note the placement of the periods and colons.

mgx8830a.1.PXM.a > cnfclksrc secondary 3:1.1:10




Procedures for PNNI Links

This section describes PXM1E configuration procedures that apply only to PNNI links. The following subsections explain the following:

• Verifying PNNI Communications

• Configuring SPVCs and SPVPs

• Deleting SPVCs and SPVPs

Verifying PNNI Communications

After setting up trunks or when problems occur, use the procedures in this section to determine if PNNI is operating. The next section describes how to verify PNNI communications on a single trunk. The following section describes how to verify PNNI communications between two nodes, which can be separated by multiple PNNI links.

Verifying PNNI Trunk Communications

After you configure both ends of a PNNI trunk, it should be ready to support SVCs and any SPVCs or SPVPs that are configured. To verify that the trunk is functioning, use the following procedure.

---

Step 1 Establish a CLI session using a user name at any access level. When both ends of the trunk are connected to Cisco MGX 8850 (PXM1E/PXM45) switches, you can start the CLI session at either end.

Step 2 If you do not know the line number you are validating, you can view the port and line numbers by entering the dsppnports command. The first three numbers identify the slot, bay, and line. For example, port 10:2.1:3 represents slot 10, bay 2, line 1. The remaining number is the interface number assigned with the addport command.

Step 3 Enter the dsppnni-link command as follows:

mgx8830a.1.PXM.a > dsppnni-link




The dsppnni-link command displays a report for every PNNI link on the switch. The following example shows the report for a switch with a single PNNI link.

mgx8830a.1.PXM.a > dsppnni-link

node index : 1

Local port id: 16845569 Remote port id: 17176579

Local Phy Port Id: 1:2.3:1

Type. lowestLevelHorizontalLink Hello state....... twoWayInside

Derive agg........... 0 Intf index........... 16845569

SVC RCC index........ 0 Hello pkt RX......... 1505

Hello pkt TX......... 1498

Remote node name.......porche

Remote node id.........56:160:47.00918100000000036b5e2b1f.00036b5e2b1f.01

Upnode id..............0:0:00.000000000000000000000000.000000000000.00

Upnode ATM addr........00.000000000000000000000000.000000000000.00

Common peer group id...00:00.00.0000.0000.0000.0000.0000.00




In the dsppnni-link command report, there should be an entry for the port for which you are verifying communications. The Local Phy Port Id field in this entry displays the port id in the same format shown in the dsppnports command report. The Hello state reported for the port should be twoWayInside and the Remote note ID should display the remote node ATM address after the second colon.

In the example above, the report shown is for port 1:1.1:1. The Hello state is twoWayInside, and the ATM address of the node at the other end of the link is 47.00918100000000107b65f33c.00107b65f33c.01. This link is ready to support connections between the two switches.

---

---

Tip If the Hello state for the link is oneWayInside, that side is trying to communicate. Check the status at the other end. Remember that the configuration at each end of the trunk must be compatible with that on the other end. For example, if ILMI auto configuration is configured at one end and not at the other, the Hello state cannot change to twoWayInside or twoWayOutside.

---

Verifying End-to-End PNNI Communications

When connections between two nodes travel over multiple trunks, use the following steps to verify that the PNNI communications path is operational.

---

Step 1 Establish a CLI session using a user name at any access level. When both ends of the communications path are connected to Cisco MGX 8850 (PXM1E/PXM45) switches, you can start the CLI session at either end.

Step 2 To display information on all accessible nodes, enter the dsppnni-node-list command as shown in the following example:

mgx8830a.1.PXM.a > dsppnni-node-list




node # node id node name level

------- -------------------------------------------------- ---------- -------

1 56:160:47.009181000000000164444494.000164444494.01 ferrari 56




node # node id node name level

------- -------------------------------------------------- ---------- -------

2 56:160:47.00918100000000036b5e2b1f.00036b5e2b1f.01 porche 56




If a switch appears in this list, you have verified communications with it.

Step 3 To display additional information on the local switch, use the dsppnni-node command. For example.

mgx8830a.1.PXM.a > dsppnni-node




node index: 1 node name: mgx8830a

Level............... 56 Lowest.............. true

Restricted transit.. off Complex node........ off

Branching restricted on

Admin status........ up Operational status.. up

Non-transit for PGL election.. off

Node id...............56:160:47.009181000000000164444494.000164444494.01

ATM address...........47.009181000000000164444494.000164444494.01

Peer group id.........56:47.00.9181.0000.0000.0000.0000.00




Step 4 To display additional information on remote switches, enter the dsppnni-reachable-addr command as follows:

mgx8830a.1.PXM.a > dsppnni-reachable-addr network




scope............... 0 Advertising node number 2

Exterior............ false

ATM addr prefix.....47.0091.8100.0000.0003.6b5e.2b1f/104

Transit network id..

Advertising nodeid..56:160:47.00918100000000036b5e2b1f.00036b5e2b1f.01

Node name...........porche




The remote node ATM address appears in the Advertising nodeid row. The information before the first colon (56) is the PNNI level, the information between the first and second colons (160) is the ATM address length, and the remainder of the node ID is the ATM address for the remote node.

---

---

Tip If you cannot verify communications with a remote node, try verifying communications across each of the links between the nodes as described in the previous section, " Verifying PNNI Trunk Communications."

---

Configuring SPVCs and SPVPs

SPVCs and SPVPs are created between two ATM CPE and must be configured at each endpoint. The master endpoint is responsible for routing and rerouting. The slave endpoint is responsible for responding to requests from the master during connection setup and rerouting. Both endpoints are configured on the switch to which the ATM CPE connects. These endpoints can be on the same switch or on different switches.

The master and slave relationships exist for each SPVC or SPVP and apply only to the SPVC or SPVP connection. For example, you can have one SPVC with a master on Node A and a slave on Node B, and then create another with the Master on Node B and the slave on Node A. It is good practice to distribute the master side of SPVCs and SPVPs among the network nodes so that route processing is distributed.

Cisco MGX switches support two types of SPVCs/SPVPs:

•Single-ended SPVCs

•Double-ended SPVCs

Single-ended SPVCs are defined at the master endpoint and do not require configuration of a slave endpoint. The primary benefit of single-ended SPVCs is that they are easier to configure. After configuration, the master endpoint configures and brings up the slave endpoint. In order for this feature to work correctly, the destination endpoint must support single-ended SPVCs.

Single-ended SPVCs are non-persistent. Non-persistent SPVCs will attempt to route on the specified path first. If the configured path is unavailable, the non-persistent SPVC will attempt to route over another available path.

---

Note In this software release, the PXM1E card supports only the origination of single-ended SPVCs. This means that you can configure master endpoints for single-ended SPVCs that terminate on other card types. If both SPVC endpoints must terminate on PXM1E cards, you must create a double-ended SPVC.

---

Double-ended SPVCs and SPVPs require separate configuration of the master and slave endpoints. The slave endpoint must be configured first because this step generates a slave address that must be entered during master endpoint configuration. Double-ended SPVCs are persistent, because they will follow only the specified path. If that path is unavailable, the persistent SPVC/SPVP will not route.

---

Note SPVC/SPVP termination is not supported on feeder ports and legacy service modules.

---

The following sections describe how to configure slave and master SPVC and SPVP connections.

---

Tip The configuration of SPVCs and SPVPs is very similar. The difference is that SPVPs are assigned VCI 0 and do not use nonzero VCI numbers. An SPVC requires a nonzero VCI.

---

Configuring the Slave Side of SPVCs and SPVPs

To configure the slave side of an SPVC or SPVP, use the following procedure.

---

Step 1 Establish a configuration session using a user name with GROUP1 privileges or higher.

Step 2 Define the slave side of the SPVC by entering the following command:

mgx8830a.1.PXM.a > addcon <ifNum> <vpi> <vci> <serviceType> <mastership> [-casttype <casttype>] [-slave atmAddr.vpi.vci] [-lpcr <cellrate>] [-rpcr <cellrate>] [-lscr <cellrate>] [-rscr <cellrate>] [-lmbs <cells>] [-rmbs <cells>] [-lcdv <time>] [-rcdv <time>] [-lctd <time>] [-rctd <time>] [-lmcr <cellrate>] [-rmcr <time>] [-cdvt <time>] [-cc <1|0>] [-stat <1|0>] [-frame <1|0>] [-mc <maxCost>] [-lputil <percentage>] [-rputil <percentage>] [-slavepersflag <persistent|nonpersistent>] [-rtngprio <routingpriority>] [-prefrte <preferredRouteId>] [-directrte <directRoute>]




---

Caution Once you create an SPVC connection, you cannot change the SPVC prefix until all SPVC connections have been deleted. The procedure for changing the SPVC prefix is described in the " Setting and Viewing the SPVC Prefix" section in Chapter 3, "Configuring General Switch Features."

---

Table 11-9 lists and defines the parameters and options for the addcon command. The local and remote terms used in Table 11-9 refer to settings for the local port you are configuring and the remote port at the other end of the connection. If you omit an option, the SPVC uses the default value.

Table 11-9 Parameters for the addcon Command 

Parameter	Description
ifNum	Enter the interface number (which is defined with the addport command) for the port to which this SPVC will connect. The range is from 1 to 31.
vpi	Enter the VPI for the slave side of the SPVC. UNI Range: 0 to 255. NNI Range: 0 to 4095.
vci	Enter the VCI for the slave side of the SPVC or SPVP. SPVC Range: 32 to 65535. SPVP Range: 0. Note Cisco recommends setting the minimum VCI to 35 or higher. Future products will use VCI 32 through 34 for other services.
serviceType	Replace <serviceType> with the number that corresponds to the requested service type for this SPVC (this value must be identical on master and slave sides). Possible service types and their corresponding numbers are as follows: •cbr1 = 1 •vbr1rt = 2 •vbr2rt = 3 •vbr3rt = 4 •vbr1nrt = 5 •vbr2nrt = 6 •vbr3nrt = 7 •ubr1 = 8 •ubr2 = 9 •abrstd = 10 •cbr2 = 11 •cbr3 = 12
mastership	Enter 2 or s if this port will serve as the slave side of the connection. Enter 1 or m if the port serves as the master side of the connection.
-casttype	The broadcast type is either point-to-point or point-to-multipoint, as follows: •0 for point-to-point •1 for point-to-multipoint Default: point-to-point (0)
-slave	Keyword for the slave-end identifier, an item you enter at the master end. This keyword is mandatory when you are adding a master endpoint (mastership=m or 1).
-lpcr	Local peak cell rate (PCR). Specifies the PCR from a local endpoint to a remote endpoint (3-5651328 cells per second). PCR is the maximum cell rate for the connection at any time.
-rpcr	Remote peak cell rate (PCR). Specifies the PCR from a remote endpoint to a local endpoint (3-5651328 cells per second). PCR is the maximum cell rate for the connection at any time.
-lscr	Local sustained cell rate (SCR). Specifies the SCR from a local endpoint to a remote endpoint (3-5651328 cells per second). SCR is the maximum cell rate that a connection can sustain for long periods.
-rscr	Remote sustained cell rate (SCR). Specifies the SCR from a remote endpoint to a local endpoint (3-5651328 cells per second). SCR is the maximum cell rate that a connection can sustain for long periods.
-lmbs	Specifies the MBS from a local endpoint to a remote endpoint, in the range from 1-5000000 cells. MBS is the maximum number of cells that can burst at the PCR and still be compliant. In the operation of the GCRA (Generic Cell Rate Algorithm), the MBS and SCR are closely related in the generation of the burst tolerance. According to buffering and the correct operation of the ATM chipset, the maximum MBS is derived from the configured SCR, and the relative values of SCR and PCR. The maximum obtained MBS will reduce as the SCR becomes lower, and as the gap between PCR and SCR gets larger.
-rmbs	Specifies the MBS from a remote endpoint to a local endpoint, in the range from 1-5000000 cells. MBS is the maximum number of cells that can burst at the PCR and still be compliant. In the operation of the GCRA (Generic Cell Rate Algorithm), the MBS and SCR are closely related in the generation of the burst tolerance. According to buffering and the correct operation of the ATM chipset, the maximum MBS is derived from the configured SCR, and the relative values of SCR and PCR. The maximum obtained MBS will reduce as the SCR becomes lower, and as the gap between PCR and SCR gets larger.
-lcdv	The local cell delay variation (CDV) parameter specifies the peak to peak cell delay variation from the local endpoint to the remote endpoint. The range is 1-16777215 microseconds.
-rcdv	The remote cell delay variation (CDV) parameter specifies the peak to peak cell delay variation from the remote endpoint to the local endpoint. The range is 1-16777215 microseconds. Default: -1
-lctd	Local cell transfer delay (CTD). This parameter specifies the CTD from a local endpoint to a remote endpoint. The range is 0-65535 milliseconds.
-rctd	Remote cell transfer delay (CTD). This parameter specifies the CTD from the remote endpoint to the local endpoint. The range is 0-65535 milliseconds. Default: -1
-lmcr	Local maximum cell rate OC3: 50 - 353207 cps T3: 50 - 96000 (PLCP) cps or 104268 (ADM) cps E3: 50 - 80000 cps T1: 50-3622 cps E1: 50-4528 cps
-rmcr	Remote maximum cell rate. OC3: 50 - 353207 cps T3: 50 - 96000 (PLCP) cps or 104268 (ADM) cps E3: 50 - 80000 cps T1: 50-3622 cps E1: 50-4528 cps
-cdvt	Local cell delay variation tolerance (CDVT). Specifies the CDVT from a local endpoint to a remote endpoint (1-5000000 microseconds). Cell Delay Variation Tolerance controls the time scale over which the PCR is policed. No remote CDVT is necessary.
-cc	This option enables or disables the flow of Operation, Administration, and Maintenance Continuity Check (OAMCC) traffic on the connection. Enter 1 to enable OAM traffic flow, or enter 0 to disable traffic flow. Note that when this option is enabled on only one side of a connection, a transient alarm is reported until this option is set to the same value at both ends. Default: 0, disabled.
-stat	This option enables or disables statistics collection for the SPVC. Enter 1 to enable OAM statistics collection, or enter 0 to disable it. Default: 0, disabled.
-frame	This option enables or disables frame discard. Enter 1 to enable frame discard, or enter 0 to disable it. Default: 0, disabled.
-mc	The maximum cost option assigns a maximum acceptable cost value to the connection. When a connection is being established, there can be multiple routes available. The cost of the connection over each route is the sum of the Administrative Weight (AW) values assigned to the links along that route. The connection will not be attempted across any route for which the total cost exceeds the value set for this option. Range: 0 to 16777215 microseconds Default: -1, no maximum cost required for route. Note The AW for each link is set with the cnfpnni-intf command. For more information, refer to the Cisco MGX 8850 (PXM1E/PXM45), Cisco MGX 8950, and Cisco MGX 8830 Command Reference.
-lputil	This option assigns the percent utilization for the local end of the connection.
-rputil	This option assigns the percent utilization for the remote end of the connection.
-slavepersflag	This option determines the persistency of the endpoint.
-rtngprio	This option determines the routing priority for the specified connection, in the range from 1 through 15, where 1 is the highest priority and 15 is the lowest priority. Default: 8
-prefrte	You can modify the priority of this connection. The range is 1-15. Default: 8 To disassociate a connection from a route, assign a value of 0 for the -prefrte parameter through the cnfcon command. Note An SPVC can be associated with one preferred route. For an XPVC, you can associate the preferred route with only the SPVC portion of the XPVC. Range: 0-65535 Default: 0
-directrte	This parameter specifies that the connection can take only the preferred route associated through the -prefrte parameter. Use this optional parameter at the master endpoint only. To remove this requirement from the connection, use the cnfcon command and specify a 0 for the parameter. The possible values are as follows: 1: yes (make the preferred route required) 0: no (do not require the connection to take the preferred route) Default: no (0)

---

Tip The PCR, MBS, CDVT, CDV, MCR, and CTD configuration options are optional. If you omit one of these options when entering the addcon command, the connection uses the default value listed in Table 11-9. To override the default values for any option, enter the option with a new value.

---

---

Note You can configure additional ABR parameters with the cnfabr and cnfabrtparmdft commands. For more information, refer to the Cisco MGX 8850 (PXM1E/PXM45), Cisco MGX 8950, and Cisco MGX 8830 Command Reference.

---

The following command example defines a port as the slave side of an SPVC. Note the slave id shown in the command response.

mgx8830a.1.PXM.a > addcon 3 101 101 1 2

slave endpoint added successfully

slave endpoint id : 4700918100000000001A531C2A00000101180300.101.101




Step 3 Write down the NSAP address the switch displays when the addcon command is complete. You will need this to configure the master side of the SPVC.

---

Tip When you set up the master side of the connection, enter the slave ATM address reported by the addcon command. If you maintain the current session or use the session Copy command to copy the ATM address now, you can use the session Paste command to complete the addcon command on the switch that hosts the master side of the connection.

---

Step 4 Verify the slave-side SPVC addition by entering the following command:

mgx8830a.1.PXM.a > dspcons




The switch displays a report similar to the following:

mgx8830a.1.PXM.a > dspcons

rLocal Port Vpi.Vci Remote Port Vpi.Vci State Owner Pri Persisteny

----------------------+------------------------+---------+-------+---+----------

4.1 4 120 Routed 12 120 OK MASTER 8 Persistent

Local Addr: 47.009181000000000164444494.000001012301.00

Remote Addr: 47.00918100000000036b5e2b1f.000001076301.00

Preferred Route ID:-

1:2.1:3 11 100 No Slave 11 119 FAIL MASTER 8 Persistent

Local Addr: 47.009181000000000164444494.000001010b03.00

Remote Addr: 47.009181000000000164444494.000001015b01.00

Preferred Route ID:-




---

Configuring the Master Side of SPVCs and SPVPs

To configure the master side of an SPVC, use the following procedure.

---

Step 1 Establish a configuration session using a user name with GROUP1 privileges or higher.

---

Tip During this procedure, you will have to enter the ATM address for the slave end of the connection. If you establish this session from the same workstation you used to create the slave connection, you can use the Copy and Paste commands to avoid data entry errors.

---

Step 2 Enter the following command to select the PXM1E card that hosts the master side of the SPVC:

mgx8830a.1.PXM.a > cc <slotnumber>




Step 3 Define the master side of the SPVC by entering the addcon command:

mgx8830a.1.PXM.a > addcon <ifNum> <vpi> <vci> <serviceType> <mastership> [-lpcr <cellrate>] [-rpcr <cellrate>] [-lscr <cellrate>] [-rscr <cellrate>] [-lmbs <cells>] [-rmbs <cells>] [-cdvt <time>] [-lcdv <time>] [-rcdv <time>] [-lctd <time>] [-rctd <time>] [-cc <1|0>] [-stat <1|0>] [-frame <1|0>] [-mc <maxCost>] [-lputil <percentage>] [-rputil <percentage>] [-slavepersflag <persistent|nonpersistent>] [-routingprio <routingpriority>]

---

Note If you omit an optional parameter, the SPVC/SPVP uses the default value.

---

---

Note In P2MP connections, do not include the -slave option with the addcon command.

---

Table 11-9 lists and defines the parameters and options for this command. If you omit an option, the SPVC uses the default value.

---

Tip The PCR, MBS, CDVT, CDV, MCR, and CTD options are optional. If you omit one of these options when entering the addcon command, the connection uses the default value listed in Table 11-9. To override the default values for any option, enter the option with a new value.

---

The following command example defines a port as the master side of an SPVC. Note the master id shown in the command response.

mgx8830a.1.PXM.a > addcon 3 101 101 1 1 -slave 4700918100000000001A531C2A00000101180300.101.101

master endpoint added successfully

master endpoint id : 4700918100000000107B65F33C0000010A180300.101.101




---

Note To designate priority routing for this SPVC, you need to include the -routingprio <routingpriority> option with the addcon command in this step.

---

Step 4 Verify the master-side SPVC addition by entering the following command:

mgx8830a.1.PXM.a > dspcons




The switch displays a report showing all connections. The following example show a report for a switch with one connection:

mgx8830a.1.PXM.a > dspcons

rLocal Port Vpi.Vci Remote Port Vpi.Vci State Owner Pri Persisteny

----------------------+------------------------+---------+-------+---+----------

4.1 4 120 Routed 12 120 OK MASTER 8 Persistent

Local Addr: 47.009181000000000164444494.000001012301.00

Remote Addr: 47.00918100000000036b5e2b1f.000001076301.00

Preferred Route ID:-

1:2.1:3 11 100 No Slave 11 119 FAIL MASTER 8 Persistent

Local Addr: 47.009181000000000164444494.000001010b03.00

Remote Addr: 47.009181000000000164444494.000001015b01.00

Preferred Route ID:-




Step 5 To display the configuration for a single connection, enter the following command:

pop20two.9.PXM1E.a > dspcon ifNum vpi vci




Replace the ifNum parameter with the interface or port number. The vpi and vci parameters are described in Table 11-9. The following example shows a dspcon command report.

mgx8830a.1.PXM.a > dspcon 1:2.1:3 11 100




Port Vpi Vci Owner State Persistency

----------------------------------------------------------------------------

Local 1:2.1:3 11.100 MASTER FAIL Persistent

Address: 47.009181000000000164444494.000001010b03.00

Node name: Ferrari

Remote No Slave 11.119 SLAVE FAIL Persistent

Address: 47.009181000000000164444494.000001015b01.00

Node name:




-------------------- Provisioning Parameters --------------------

Connection Type: VCC Cast Type: Point-to-Point

Service Category: CBR Conformance: CBR.1

Bearer Class: BCOB-X

Last Fail Cause: N/A Attempts: 0

Continuity Check: Disabled Frame Discard: Disabled

L-Utils: 100 R-Utils: 100 Max Cost: -1 Routing Cost: 0

OAM Segment Ep: Enabled

Priority: 8




---------- Traffic Parameters ----------

Values: Configured (Signalled)

Tx PCR: 240 (-) Rx PCR: 240 (-)




Type <CR> to continue, Q<CR> to stop:

Tx CDVT: 250000 (-)

Tx CDV: -1 (-) Rx CDV: -1 (-)

Tx CTD: -1 (-) Rx CTD: -1 (-)




-------------------- Preferred Route Parameters------------------

Preferred Route ID: -

Currently on preferred route: N/A




The -1 entries in the example above indicate that a value was not specified with the addcon command. The N/A entries indicate that a value is not applicable to connections with this service type.

The following example shows the report for the connection shown in the preceding examples.

mgx8830a.1.PXM.a > dspcons




Local Port Vpi.Vci Remote Port Vpi.Vci State Owner Pri Persisteny

----------------------+------------------------+---------+-------+---+----------

4.1 4 120 Routed 12 120 OK MASTER 8 Persistent

Local Addr: 47.009181000000000164444494.000001012301.00

Remote Addr: 47.00918100000000036b5e2b1f.000001076301.00

Preferred Route ID:-

1:2.1:3 11 100 No Slave 11 119 FAIL MASTER 8 Persistent

Local Addr: 47.009181000000000164444494.000001010b03.00

Remote Addr: 47.009181000000000164444494.000001015b01.00

Preferred Route ID:-




---

Configuring Point-to-Multipoint SPVCs and SPVPs

In point-to-multipoint (P2MP) connections, one master endpoint, or root, can be configured to support several slave endpoints, or parties.

P2MP SPVCs and SPVPs are created between several ATM CPE. During P2MP connection setup and rerouting, the root is responsible for routing and rerouting, and the parties are responsible for responding to requests from the master. The root and its parties are configured on the switch to which the ATM CPE connects. These endpoints can be on the same switch or on different switches.

P2MP functionality is necessary for the following applications:

•data and video broadcast

•LAN emulation

The procedures in this section describe how to configure P2MP connections on a PXM1E. For more detailed information on planning and establishing P2MP connections in a PNNI network, refer to the PNNI Network Planning Guide for MGX and SES Products.

Keep the following in mind when configuring P2MP connections on Cisco MGX 8850 (PXM1E) and Cisco MGX 8830 switches:

•PXM1E cards do not support egress multicasting and, therefore, do not support branching.

•A root can originate on a CBSM, but it cannot terminate on a CBSM. In other words, parties are not supported on the CBSMs. This is because P2MP parties are non-persistent, and CBSMs do not support non-persistent connections.

•ABR P2MP connections are not supported.

•P2MPs support uni-directional traffic.

•Unicast (P2P) traffic has a higher priority than multi-cast (P2MP) traffic. P2MPs have a default routing priority of 8.

•P2MPs do not support CUGs.

•In a P2MP connection, the root can be on any port that supports ingress multicasting. The port that is the root of the connection does not need to support egress multicasting. The port on which the parties are configured must support both egress and ingress multicasting. For example, if you add a party on a port that does not support egress multicasting, the connection will not route.

•All configuration for P2MP connections is done at the root.You can not do any configuration on the remote (slave) end of the connection. Any attempt to specify parameters for the remote end will be blocked.

Table 11-10 summarizes the connection limit on Cisco MGX 8850 (PXM1E) and Cisco MGX 8830 switches.

Table 11-10 Connection/Party Limits

Connection Type	Limit
Total number of connections (P2P and P2MP)	27,000
Total number of P2MP Connections	500
Number of parties per P2MP connection	100
Number of branches at originating node	1
Total Number of parties per node	1,000

The establishment of a P2MP connection is a two-step process:

1. Set up the master end point, or root, of the connection.

2. Add parties to the root of the connection.

---

Tip The configuration of SPVCs and SPVPs is very similar. The difference is that SPVPs are assigned VCI 0 and do not use nonzero VCI numbers. An SPVC requires a nonzero VCI.

---

To configure a P2MP connection, use the following procedure.

---

Step 1 Establish a configuration session using a user name with GROUP1 privileges or higher.

Step 2 At the active PXM1E prompt, enter the addcon command to establish the master end-point, or root, of a P2MP connection, as shown in the following example. Be sure to include the -casttype 1 option to specify that this connection is a P2MP connection.

mgx8830a.1.PXM.a > addcon <ifNum> <vpi> <vci> <serviceType> <mastership> -casttype 1




In the following example, the root of a P2MP connection is set up on interface 3, on VPI 101 and VCI 101.

mgx8830a.1.PXM.a > addcon 3 101 101 1 1 -casttype 1

Step 3 Enter the dspcon <portid> <vpi> <vci> command to verify that the root was established properly. Replace the <portid> parameter with the interface or port number. The <vpi> and <vci> parameters are described earlier in this chapter in Table 11-9.

Step 4 Enter the addparty command to add a party to a P2MP connection, as shown in the following example.

mgx8830a.1.PXM.a > addparty <port> <vpi> <vci> <epref> [-party <party_nsap.vpi.vci>




The addparty command parameters are described in Table 11-11.

Table 11-11 addparty Command Parameters

Parameter	Description
port	Port identifier, in the format [shelf.]slot[:subslot].port[:subport]
vpi	VPI range (UNI: 0 to 255 | NNI: 0 to 4095)
vci	VCI range 35 to 65535
epref	Endpoint reference range 1 to 32767.
party	PartyNSAP.vpi.vci To obtain a slave/party's NSAP, see the "Obtaining the NSAP for a Party" section that follows.

Step 5 To verify that the party was added properly, enter the dspparty command as follows:

mgx8830a.1.PXM.a > dspparty <port> <vpi> <vci> <epref>




The dspparty command parameters are the same parameters you set with the addparty command ( Table 11-11). The following example shows the dspparty command display:

pswpop6.1.PXM.a > dspparty 5.3 100 100 -epref 10

----------------------------------------------------------------------------

Local 5:-1.3:-1 100.100 MASTER OK Persistent

Address: 47.009181000000001029300121.000000050300.00

Node name: pswpop6

Remote 5:-1.3:-1 100.101 PARTY OK Persistent

Address: 47.00918100000000c043002de1.000000050300.00

Node name: pswpop7

Endpoint Reference: 10




Step 6 Repeat Steps 4 and 5 to add more parties, one at a time, to the root you created in Step 2.

---

To display all configured parties for a specific connection, enter the dsppartiespercon <portid> <vpi> <vci> command. Replace <portid> with the Port identifier whose parties you want to view, in the format. Replace <vpi> with the appropriate VPI of the connection, and <vci> with the appropriate VCI of the connection.

pswpop6.1.PXM.a > dsppartiespercon 5.3 100 100

Port Vpi Vci Owner State Persistency

----------------------------------------------------------------------------

5.3 100 100 OK MASTER Persistent

Local Addr: 47.009181000000001029300121.000000050300.00

Remote Party 100 101 OK PARTY Persistent

Remote Addr: 47.00918100000000c043002de1.000000050300.00

Endpoint Reference: 101

Remote Party 100 102 OK PARTY Persistent

Remote Addr: 47.00918100000000c043002de1.000000050300.00

Endpoint Reference: 102

Port Vpi Vci Owner State Persistency

----------------------------------------------------------------------------

5.3 100 100 OK MASTER Persistent

Local Addr: 47.009181000000001029300121.000000050300.00

Remote Party 100 103 OK PARTY Persistent

Remote Addr: 47.00918100000000c043002de1.000000050300.00

Endpoint Reference: 103

Remote Party 100 104 OK PARTY Persistent




Obtaining the NSAP for a Party

To obtain the NSAP for a party, you need to add a slave endpoint at the port on which the desired party will reside, and then delete it. Use the following procedure to obtain the NSAP for a party/slave endpoint.

---

Step 1 Establish a configuration session with the switch that will host the party, using a user name with GROUP1 privileges or higher.

Step 2 At the active PXM1E prompt, enter the addcon command to establish a slave end-point for the root you created in the previous section, as if you are configuring a regular P2P connection.

mgx8830a.1.PXM.a > addcon <ifNum> <vpi> <vci> <serviceType> <mastership>




In the following example, the user creates a slave on logical port 1 with a VPI of 10, a VCI of 10, and the service type CBR.

PXM1E_SJ.7.PXM.a >addcon 1 10 10 1 s

slave endpoint added successfully

slave endpoint id: 00000E1000001C008051B730FFFFFF010B180100.10.40




Step 3 Write down the NSAP address the switch displays when the addcon command is complete. You will need this address when you add the party to the root of the P2MP connection.

Step 4 Enter the delcon command to delete the connection you added in Step 2.

Step 5 Enter the dspcon command to verify that the slave was deleted properly.

---

Once you have the NSAP for a party, you can add that party to a root.

Rerouting a P2MP Party

Before you can reroute a configured party on a P2MP connection, you must bring the party down with the dnparty command. Once a party's new route is configured, you can bring that party back up with the upparty command.

The following procedure provides detailed steps for rerouting a party.

---

Step 1 Establish a configuration session using a user name with GROUP1 privileges or higher.

Step 2 At the active PXM1E prompt, enter the dspparties command to display all parties on the node.

pswpop6.1.PXM.a > dspparties 5.3 100 100

Port Vpi Vci Owner State Persistency

----------------------------------------------------------------------------

5.3 100 100 OK MASTER Persistent

Local Addr: 47.009181000000001029300121.000000050300.00

Remote Party 100 101 OK PARTY Persistent

Remote Addr: 47.00918100000000c043002de1.000000050300.00

Endpoint Reference: 10

Remote Party 100 110 OK PARTY Persistent

Remote Addr: 47.00918100000000c043002de1.000000050300.00

Endpoint Reference: 11




To display information about the specific party you want to modify, enter the dspparty command as shown in the following example.

pswpop6.1.PXM.a > dspparty <portid> <vpi> <vci< -epref <epref>




---

Note The dspparty command parameters are the same parameters you set with the addparty command ( Table 11-11).

---




Step 3 Enter the dnparty command to bring down the party you want to reroute, as shown in the following example.

mgx8830a.1.PXM.a > dnparty <port> <vpi> <vci> <epref>




---

Note The dnparty command parameters are the same parameters you set with the addparty command ( Table 11-11).

---

Step 4 Enter the rrtparty command to reroute the appropriate party, as shown in the following example.

mgx8830a.1.PXM.a > rrtparty <port> <vpi> <vci> <epref>




---

Note The rrtparty command parameters are the same parameters you set with the addparty command ( Table 11-11).

---




Step 5 Enter the upparty command to bring the rerouted party back up, as shown in the following example.

mgx8830a.1.PXM.a > upparty <port> <vpi> <vci> <epref>

---

Note The upparty command parameters are the same parameters you set with the addparty command ( Table 11-11).

---

Step 6 Enter the dspparty command as shown in the following example to verify that the party was rerouted correctly.

pswpop6.1.PXM.a > dspparty <portid> <vpi> <vci< -epref <epref>

---

Note The dspparty command parameters are the same parameters you set with the addparty command ( Table 11-11).

---

---

Deleting a P2MP Party Configuration

Before you can delete a P2MP connection, you must first delete all parties associated with that connection. A P2MP connection will remain in service as long as there are parties configured on that connection. For example, a P2MP connection that has 100 parties will remain in service, even if 99 of those parties are down.

To delete a party from a P2MP connection, enter the delparty command, as shown in the following example.

mgx8830a.1.PXM.a > delparty <port> <vpi> <vci> <epref>

---

Note The delparty command parameters are the same parameters you set with the addparty command ( Table 11-11).

---

One you have deleted all parties on a P2MP connection, you can delete the connection itself by entering the delcon command, as shown in the following example.

mgx8830a.1.PXM.a > delcon <ifNum> <vpi> <vci>




Replace the ifNum parameter with the interface or port number. The vpi and vci parameters are described earlier in Table 11-9.

Deleting SPVCs and SPVPs

To delete an SPVC or SPVP that terminates on an PXM1E card, enter the delcon command using the following format:

mgx8830a.1.PXM.a > delcon <ifNum> <vpi> <vci>




Replace the ifNum parameter with the interface or port number. The vpi and vci parameters are described in Table 11-9. This command deletes the connection end on the local switch. It does not delete the remote end of the connection, which must be deleted on the remote switch.

Defining Destination Addresses for Static Links

Typically, an AINI or IISP static link joins two independent networks. AINI or IISP links are used instead of PNNI so that the topologies of the two networks remain unknown to the each other.

When you create a static link, you must identify destination addresses for each side of the link. These addresses identify which ATM nodes are accessible on the other side of the link. After you define these addresses, all requests for these addresses are routed over the static link to the other network.

---

Note To enable bidirectional call initiation, the appropriate destination address must be configured at each end of the link. For example, if nodes A and B have PNNI connections to a static link, the ATM address for Node B must be added to the Node A side of the static link, and the Node A address must be added to the Node B side of the static link.

---

To add destination addresses to a static link, use the following procedures.

---

Step 1 Establish a configuration session using a user name with GROUP1 privileges or higher.

Step 2 To locate the port to which you want to add an address, enter the dsppnports command.

Step 3 Specify an ATM address using the following command:

mgx8830a.1.PXM.a > addaddr <portid> <atm-address> <length> -type ext -proto static [-plan {e164 | nsap}] [-scope scope] [-redistribute {yes | no}]




---

Note The addaddr command is used to define destination addresses for static links and to specify static addresses for links to CPE. The command format above shows the options as they apply when defining destination addresses for static links.

---

Table 11-12 describes the parameters used with the addaddr command.

Table 11-12 ATM Address Configuration Parameters 

Parameter	Description
portid	Enter the port identifier in the format slot:bay.line:ifnum. These parameters are described in Table 11-4.
atm-address	Enter the ATM address using up to 40 nibbles. The ATM address can include up to 20 bytes, which is 40 nibbles or 160 bits. To summarize a group of destination addresses, enter an ATM address that is less than 20 bytes and includes the common bytes in the group of destination addresses.
length	Enter the length, in bits, of the address you specified with the <atm-address> parameter. Each nibble is equal to 4 bits. The acceptable range for the parameter is from 0 to 160 bits. When you enter a complete 20-byte ATM address, the length is 160. When you summarize a group of destination addresses, the length is equal to the number of bytes entered multiplied by 8.
-type	Enter the address type, which is ext (external) for destination addresses on the other side of a static link. The int (internal) value is used when creating static addresses for links to CPE. Default = int.
-proto	For static link destination addresses, specify the -proto option with the static value. The local value applies to CPE links. Default = local.
-plan	Enter the address plan, which is either e164 (E.164) or nsap (NSAP). For an NSAP address, the first byte of the address automatically implies one of the three NSAP address plans: NSAP E.164, NSAP DCC, or NSAP ICD. Default = nsap.
-scope	PNNI scope of advertisement. The scope defines the level of the PNNI hierarchy at which this address is advertised. Enter 0 to advertise the destination address to all nodes in the node's peer group. Range: 0 through 104. Default = 0.
-redistribute	Specifies whether or not the ATM address should be distributed or advertised to PNNI neighbor nodes. Enter yes to enable distribution and enter no to disable. When this option is set to yes, the node distributes the address to the PNNI neighbors defined with the scope option. When set to no, the address is not advertised to any other nodes. Default = no.

Step 4 To verify that the new address is assigned, enter the following command:

mgx8830a.1.PXM.a > dspatmaddr <portid>




Replace <portid> with the port address using the format slot:bay.line:ifnum. These parameters are described in Table 11-4. For example:

mgx8830a.1.PXM.a > dspaddr 2:1.2:2

47.0091.8100.0000.0003.6b5e.30cd.0003.6b5e.30cd.01

length: 160 type: exterior proto: static

scope: 0 plan: nsap_icd redistribute: false

---

Configuring Inverse Multiplexing for ATM

The Inverse Multiplexing for ATM (IMA) feature enables multiple T1 or E1 lines to be grouped into a single high-speed ATM port. The advantage of the IMA feature is that you do not need T3/E3 circuits to support high bandwidth on your switch. On Cisco MGX 8850 (PXM1E) and Cisco MGX 8830 switches, IMA is supported on the PXM1E-16-T1E1 and AUSM-8-T1E1/B cards. On Cisco MGX 8850 (PXM45) switches, IMA is supported on AXSM cards. IMA is not supported on Cisco MGX 8950 switches.

---

Note The procedures in this chapter apply only to the PXM1E card. To configure IMA on AUSM/B cards, refer to the Cisco AUSM Software Configuration Guide and Command Reference for Cisco MGX 8850 (PXM1E) and Cisco MGX 8830, Release 3. To configure IMA on AXSM-32-T1E1-E cards, refer to the Cisco ATM Services (AXSM) Software Configuration Guide and Command Reference for MGX Switches.

---

The PXM1E-16-T1E1 card supports IMA version 1.0 and version 1.1. A single IMA group can support up to 16 T1 or E1 links. Each T1 IMA link supports up to 1.5 Mbps, for a total of 27 Mbps per back card. Each E1 IMA link supports up to 2 Mbps, for a total of 32 Mbps per back card. If IMA is disabled on the PXM1E-16-T1E1, each T1 or E1 interface can be configured as a single port running at full line rate.

Each combination of multiple links is called an IMA group. IMA groups are comprised of IMA links.

---

Note During PXM1E-16-T1E1 switchovers, traffic loss on an IMA group can be around 3 seconds, and connections on the IMA group may be re-routed.

---

Configuring IMA on PXM1E ports is a three-step process.

1. Create and configure an IMA group

2. Add IMA links to the IMA group

3. Add and configure an IMA port for the IMA group

The sections that follow provide detailed procedures for configuring IMA on PXM1E ports.

Creating an IMA Group

---

Note Both ends of an IMA connection must support IMA, and the IMA configuration must match on both ends.

---

To create an IMA group and add it to an ATM port, use the following procedure:

---

Step 1 Establish a configuration session with the active PXM1E.

Step 2 Enter the dsplns command to display all configured lines on the current card.

MGXswitch.7.PXM.a > dsplns

Line Line Line Line Length Valid Alarm

Num State Type Lpbk (meters) Intvls State

---- ----- --------- ----------- -------- ---------- -------

2.1 Up dsx1ESF NoLoop 40 89 Critical

2.2 Down dsx1ESF NoLoop 40 0 Clear

2.3 Down dsx1ESF NoLoop 40 0 Clear

2.4 Down dsx1ESF NoLoop 40 0 Clear

2.5 Down dsx1ESF NoLoop 40 0 Clear

2.6 Down dsx1ESF NoLoop 40 0 Clear

2.7 Down dsx1ESF NoLoop 40 0 Clear

2.8 Down dsx1ESF NoLoop 40 0 Clear

2.9 Down dsx1ESF NoLoop 40 0 Clear

2.10 Down dsx1ESF NoLoop 40 0 Clear

2.11 Down dsx1ESF NoLoop 40 0 Clear

2.12 Down dsx1ESF NoLoop 40 0 Clear

2.13 Down dsx1ESF NoLoop 40 0 Clear

2.14 Down dsx1ESF NoLoop 40 0 Clear

2.15 Down dsx1ESF NoLoop 40 0 Clear

2.16 Down dsx1ESF NoLoop 40 0 Clear




---

Note If a line you want to add to the IMA group is up, enter the dnln <x.line> command bring that line down. A line must be down before you add it to an IMA group.

---

Step 3 Enter the addimagrp command to create the IMA group, as shown in the following example:

MGXswitch.7.PXM.a > addimagrp <group> <version> <minLinks> <txImaId> <txFrameLen> <txclkMode> <diffDelayMax>




Table 11-13 describes the parameters for the addimagrp command.

Table 11-13 addimagrp Command Parameters 

group_num	Number for the IMA group. On a PXM1E, the range is 1-16.
version	IMA version; 1: 1.0, 2: 1.1
minLinks	Minimum number of links required for group operation. For example, if you create an IMA group of 4 lines and specify a minimum number of 3 lines, then three of the four specified lines must be operational before the IMA group can be used. The range for this value is from 1 to n, where n represents the number of lines that are dedicated to the group.
txImaId	Transmit IMA Id; 0 to 255
txFrameLen	Transmit Frame Length; 32, 64, 128, 256 for IMA V1.1, 128 for IMA V1.0
txclkMode	Transmit Clock Mode; 1: CTC, 2: ITC Note Option 2: ITC is not supported in Release 4 of the Cisco MGX 8850 (PXM1E) and Cisco MGX 8830 switches.
diffDelayMax	Maximum Differential Delay; •Enter a umber between 1 and 275 msec for T1 •Enter a number between 1 and 220 msec for E1

In the following example, the user creates group 1 running IMA version 1.0. The minimum number of lines required for this group to operate is 3. The transmit IMA ID for IMA group 1 is 255, the transmit frame length is 128, the transmit clock mode is CTC, and the maximum differential delay is 100.

MGXswitch.7.PXM.a > addimagrp 2.1 1 3 255 128 1 100




Step 4 To verify that the IMA group has been created, enter the dspimagrps command:

MGXswitch.7.PXM.a > dspimagrps




Ima Min Tx Rx Tx Diff NE-IMA FE-IMA IMA

Grp Lnks Frm Frm Clk Delay state state Ver

Len Len Mode (ms)

--------------------------------------------------------------------------------

2.1 1 128 128 CTC 100 StartUp StartUp 1.0

2.2 3 128 128 CTC 100 StartUp StartUp 1.1

2.3 3 128 128 CTC 100 StartUp StartUp 1.1




---

Configuring an IMA Group

Once you have added an IMA group on your PXM1E, you can configure that IMA group's parameters. Use the following procedure to configure IMA group parameters.

---

Step 1 Establish a configuration session with the active PXM1E.

Step 2 Enter the dspimagrps command to list the IMA groups configured on the current card.

MGXswitch.7.PXM.a > dspimagrps




Ima Min Tx Rx Tx Diff NE-IMA FE-IMA IMA

Grp Lnks Frm Frm Clk Delay state state Ver

Len Len Mode (ms)

--------------------------------------------------------------------------------

2.1 1 128 128 CTC 100 StartUp StartUp 1.0

2.2 3 128 128 CTC 100 StartUp StartUp 1.1

2.3 3 128 128 CTC 100 StartUp StartUp 1.1




Step 3 To display the configuration information for the particular IMA group that you want to configure, enter a dspimagrp <bay.group> command with the group number. Replace bay with the 2 to specify the lower bay. Replace group with the IMA group number you want to display, in the range from1 through 16.

---

Note On the PXM1E, the bay number is always 2.

---

In the following example, the user displays the IMA group 2 in the lower bay.

MGXswitch.7.PXM.a > dspimagrp 2.2

Group Number : 2.2

NE IMA Version : Version 1.1

Group Symmetry : Symm Operation

Tx Min Num Links : 3

Rx Min Num Links : 3

NE TX Clk Mode : CTC

FE TX Clk Mode : CTC

Tx Frame Len : 128

Rx Frame Len : 128

Group GTSM : Down

NE Group State : StartUp

FE Group State : StartUp

Group Failure Status : Other Failure

Tx Ima Id : 2

Rx Ima Id : 0

Max Cell Rate (c/s) : 0

Avail Cell Rate (c/s) : 0

Diff Delay Max (msecs) : 100

Diff Delay Max Observed (msecs) : 0

Accumulated Delay (msec) : 0

GTSM Up Integ time(msec) : 10000

GTSM Dn Integ time(msec) : 2500




Type <CR> to continue, Q<CR> to stop:

Num Tx Cfg Links : 0

Num Rx Cfg Links : 0

Num Act Tx Links : 0

Num Act Rx Links : 0

Least Delay Link : Unknown

Tx Timing Ref Link : Unknown

Rx Timing Ref Link : Unknown

Group Running Secs : 0

Alpha Val : 2

Beta Val : 2

Gamma Val : 1

Tx OAM Label : 3

Rx OAM Label : 0

Test Pattern Procedure Status : Disabled

Test Link : Unknown

Test Pattern : 255

Step 4 To configure an IMA group, enter the cnfimagrp command, as shown in the following example:

MGXswitch.7.PXM.a > cnfimagrp <-grp <group> [-ver <version>] [-txm <minLinks>] [-txid <txImaId>] [-txfl <txFrameLen>] [-dd <diffDelayMax>] [-uptim<groupUpTime>] [-dntim <groupDownTime>]




Table 11-14 describes the parameters for the cnfimagrp command.

Table 11-14 cnfimagrp Command Parameters 

-grp <bay.group>	The bay number and the IMA group number. • bay: 1-2 •grp: 1-16 Note On the PXM1E, the bay number is always 2.
-ver <version>	The protocol version of the IMA group. •1 = IMA version 1.0 •2 = IMA version 1.1
-txm <minLinks>	The minimum number of links that will allow the IMA group to be operational (Range: 1-16).
--txid <txImaId>	The IMA ID number transmitted in the IMA ID field (Range: 0-255). This field cannot be change while the IMA group is up.
txFrameLen	The length of transmitted IMA frame in cells. This frame length is described as M consecutive cells for each Tx frame. The txFrameLen value is configurable ONLY for IMA version 1.1. For IMA version 1.0, the txImaFrameLength value is always 128. For IMA version 1.1, the txImaFrameLength value can be 32, 64, 128, or 256 bytes.
diffDelayMax	The maximum differential delay in milliseconds, in the following range: T1 = from 1 through 275 msec E1 = from 1 through 220 msec Defaults: T1 = 275, E1 = 220
groupUpTime	0-400000 milliseconds
groupDownTime	0 and 100000 milliseconds

---

Note Modifying any of the attributes causes the IMA group to restart.

---

In the following example, the user modifies the transmit frame length, the IMA group uptime, and the IMA group downtime:

MGXswitch.7.PXM.a > cnfimagrp -grp 2.1 -txfl 256 -uptim 100 -dntim 100




Step 5 To verify IMA group configuration changes, enter a dspimagrp command for the appropriate IMA group.

MGXswitch.7.PXM.a > dspimagrp 2.2

Group Number : 2.2

NE IMA Version : Version 1.1

Group Symmetry : Symm Operation

Tx Min Num Links : 4

Rx Min Num Links : 4

NE TX Clk Mode : CTC

FE TX Clk Mode : CTC

Tx Frame Len : 256

Rx Frame Len : 128

Group GTSM : Down

NE Group State : StartUp

FE Group State : StartUp

Group Failure Status : Other Failure

Tx Ima Id : 1

Rx Ima Id : 0

Max Cell Rate (c/s) : 0

Avail Cell Rate (c/s) : 0

Diff Delay Max (msecs) : 100

Diff Delay Max Observed (msecs) : 0

Accumulated Delay (msec) : 0

GTSM Up Integ time(msec) : 100

GTSM Dn Integ time(msec) : 100




Type <CR> to continue, Q<CR> to stop:

Num Tx Cfg Links : 0

Num Rx Cfg Links : 0

Num Act Tx Links : 0

Num Act Rx Links : 0

Least Delay Link : Unknown

Tx Timing Ref Link : Unknown

Rx Timing Ref Link : Unknown

Group Running Secs : 0

Alpha Val : 2

Beta Val : 2

Gamma Val : 1

Tx OAM Label : 3

Rx OAM Label : 0

Test Pattern Procedure Status : Disabled

Test Link : Unknown

Test Pattern : 255




---

Adding an IMA Link to an IMA Group

Once you have established and configured an IMA group, you can begin adding IMA links to the group. Use the following procedure to add an IMA link to an IMA group.

---

Step 1 Enter the dspimagrps command to see the available IMA groups, as shown in the following example:

MGXswitch.7.PXM.a > dspimagrps




Ima Min Tx Rx Tx Diff NE-IMA FE-IMA IMA

Grp Lnks Frm Frm Clk Delay state state Ver

Len Len Mode (ms)

--------------------------------------------------------------------------------

2.1 1 128 128 CTC 100 StartUp StartUp 1.0

2.2 3 128 128 CTC 100 StartUp StartUp 1.1

2.3 3 128 128 CTC 100 StartUp StartUp 1.1




Step 2 Enter the addimalnk <link> <group> command to add an IMA link to an IMA group. Replace <link> with the link number you want to add to the group, in the format bay.line. Replace <group> with the number of the group to which the link will be added, in the format bay.group.

In the following example, the user adds link 1 to the IMA group 1 in the lower bay.

MGXswitch.7.PXM.a > addimalnk 2.1 2.1




Step 3 Enter the cnfimalnk command as follows to configure the IMA link you just added:

cnfimalnk -lnk <link> [-uplif <lifUpTime>] [-dnlif <lifDnTime>] [-uplods <lodsUpTime>] [-dnlods <lodsDnTime>]

Table 11-15 describes the parameters for the cnfimagrp command.

Table 11-15 cnfimalnk Command Parameters 

-lnk <link>	The bay number (2) and the IMA link number (1-16) in the format bay.link. For example: 2.16 Note On the PXM1E, the bay number is always 2.
-uplif <lifUpTime>	LIF integration up time. Range: 0-25000 milliseconds. The LIF (Loss of IMA Frame) defect is the occurrence of persistent OIF (Out of IMA Frame) anomalies for at least 2 IMA frames.
-dnlif <lifDnTime>	LIF integration down time. Range 0-25000 milliseconds. The LIF (Loss of IMA Frame) defect is the occurrence of persistent OIF (Out of IMA Frame) anomalies for at least 2 IMA frames.
-uplods <lodsUpTime>	LODS integration up time. Range 0-25000 milliseconds. The LODS (Link Out of Delay Synchronization) is a link event indicating that the link is not synchronized with the other links within the IMA group.
-dnlods <lodsDnTime>	LODS integration down time. Range 0-25000 milliseconds. The LODS (Link Out of Delay Synchronization) is a link event indicating that the link is not synchronized with the other links within the IMA group.

In the following example, the user configures link 2.5 so that it has an LIF up time of 25000 milliseconds, an LIF downtime of 1000 milliseconds, an LODS integration up time of 25000 milliseconds, and an LODS integration down time of 1000 milliseconds.

MGXswitch.7.PXM.a > cnfimalnk -lnk 2.5 -uplif 25000 -dnlif 1000 -uplods 25000 -dnlods 1000




Step 4 Enter the dspimalink <link> command to verify the configuration of the new IMA link. Replace <link> with the number of the link you wish to display in the format bay.link. For PXM1E cards, the bay is always 2 (the lower bay).

In the following example, the user displays the IMA link number 5 in the lower bay.

MGXswitch.7.PXM.a > dspimalnk 2.5

IMA Link Number : 2.5

IMA Link Group Number : 2.1

LinkRelDelay (msec) : 0

LinkNeTxState : Unusable-Failed

LinkNeRxState : Not In Grp

LinkFeTxState : Not In Grp

LinkFeRxState : Active

LinkNeRxFailureStatus : Lif Fail

LinkFeRxFailureStatus : Lods Fail

ImaLink TxLid : 4

ImaLink RxLid : 255

LinkRxTestPattern : 255

LinkTestProcStatus : Disabled




---

Adding an IMA Port

Once you have configured an IMA group, you need to add a port to group to make it fully operational. Use the following procedure to add an IMA port to a group.

---

Step 1 Establish a configuration session using a user name with GROUP1 privileges or higher.

Step 2 Get the group number on which you will add the port. To display a list of the IMA group numbers, enter the dspimagrps command.

Step 3 Verify that the line and port number you want to use is not configured. To display a list of the ports configured on the PXM1E card, enter the following command:

mgx8830a.1.PXM.a > dspports




This command displays all ports on the PXM1E card in the ifNum (interface number) column. The interfaces listed include UNI and NNI 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.

---

Note The Cisco MGX switches support one port per line.

---

Step 4 To add an ATM port to a group, enter the following command:

mgx8830a.1.PXM.a > addimaport <ifNum> <group> <guaranteedRate> <maxRate> <sctID> <ifType> [vpi <vpi>] [-minvpi <minvpi>] [-maxvpi <maxvpi>]




Table 11-16 lists the parameter descriptions for adding IMA ports.

---

Note Refer to Figure 11-2 earlier in this chapter to see the relationship between logical interface numbers and physical lines.

---

Table 11-16 Parameters for addimaport Command 

Parameter	Description
ifNum	An ATM port is also called an interface. An ATM port is defined by its slot, bay, line, and interface numbers. You do not have to enter a slot number during port configuration because you identify the slot number when you select the card. Enter a number from 1 to 31 to identify this interface. The interface number must be unique on the card to which it is assigned. For UNI and NNI ports, you can assign one logical interface per line.
group	ATM IMA group number in the format bay.line. Replace bay with 1 if the line is connected to a back card in the upper bay, or replace it with 2 if the line is connected to a back card in the lower bay. Remember that the bay number is always 1 for an PXM1E-16-T1E1. Replace group with the IMA group number, in the range from 1 through 16.
guaranteedRate	Use one of the following formulas to compute the guaranteed minimum rate: •For a T1-based IMA group, the rate is as follows: from 50 through N * (3622 * (M-1)/M * 2048/2049) •For an E1-based IMA group, the rate is as follows: from 50 through N * (4528 * (M-1)/M * 2048/2049) where N is the number of IMA links in the IMA group, and M is the IMA group frame length Note On the PXM1E, the guaranteed minimum bandwidth rate does not have to be the same as maxRate.
maxRate	Use one of the following formulas to compute the maximum rate: •For a T1-based IMA group the rate is as follows: from 50 through N * (3622 * (M-1)/M * 2048/2049) •For an E1-based IMA group, the rate is: from 50 through N * (4528 * (M-1)/M * 2048/2049) where N is the number of IMA links in the IMA group, and M is the frame length for the IMA group. Note On the PXM1E, the maxRate does not have to be the same as guaranteed minimum bandwidth rate.
sctID	The port SCT number (0 to 255). For common IMA applications where the IMA group has 1-4 links, use SCT 54 (policing) or SCT 55 (non-policing). For IMA applications where the IMA group has 5-16 links, use the Cisco WAN Manager (CWM) to create a new SCT and change the maximum VC/CoSB cell threshold (in microseconds). See the Cisco WAN Manager User's Guide, Release 12, for information how to create a new SCT.
ifType	Specifies the port as one of the following types of interfaces: •1 = UNI (User-to-Network Interface) •2 = NNI (Network-to-Network Interface) •3 = VNNI (Virtual Network-to-Network Interface) •4 = VUNI (Virtual User-to-Network Interface) •5 = EVUNI (Enhanced Virtual User-to-Network Interface) •6 = EVNNI (Enhanced Virtual Network-to-Network Interface) EVNNI and EVUNI allow you to specify a range of VPIs for a single interface, and this range of VPIs represents the virtual NNI or virtual UNI trunk. VNNI and VUNI allow you to specify only one VPI for a single interface, and that VPI represents the virtual NNI or virtual UNI trunk. Multiple VNNIs and EVNNIs can coexist on the same line.
vpi	The virtual path identifier (VPI), which is used in this case to configure the interface as a virtual trunk. Ranges: •1-255 VUNI •1- 4095 VNNI
minvpi	The minimum VPI has a range that depends on the interface, as follows: •0-255 EVUNI •0-4095 for EVNNI
maxvpi	The maximum VPI has a range that depends on the interface, as follows: •0-255 EVUNI •0-4095 for EVNNI

Step 5 To display a list of all ports configured on the PXM1E card, enter the dspports command. Port numbers are listed in the ifNum (interface number) column. If you want to view information on a particular port, note the number of that port.

---

Configuring a Connection to an IGX Feeder

A Cisco IGX node with a UXM card can be configured as a feeder to a Cisco MGX8850 switch, which can be configured as a routing node for the IGX feeder. The Cisco IGX feeder trunk interface on the UXM can connect to the AXSM, AXSM-E, or PXM1E of a Cisco MGX8850.

---

Note The procedure that follows applies only to the PXM1E. To configure an IGX feeder connection on an AXSM card, refer to the Cisco ATM Services (AXSM) Software Configuration Guide and Command Reference for MGX Switches.

---

Figure 11-4 shows the IGX feeder topology.

Figure 11-4 IGX Feeder Topology

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

This procedure describes how to configure a connection from an MGX 8850 PXM1-E card to an IGX feeder.

---

Step 1 Establish a configuration session with the Cisco MGX 8850 (PXM1E) or the Cisco MGX 8830 using a user name with GROUP1 privileges or higher.

Step 2 Enter the upln command to create an interface between the PXM1E card on the Cisco MGX 8850 or Cisco MGX 8830 8830 switch, and the UXM card on the IGX switch.

Step 3 If you are creating a non-IMA interface, enter the addport command. If you are creating an IMA interface, enter the addimagroup, addimalink and addimaport commands, as described in the "Configuring Inverse Multiplexing for ATM" section earlier in this chapter.

---

Tip Remember that you cannot configure a line until you have brought it up as described in " Bringing Up Lines," in Chapter 4, "Preparing PXM1E Lines for Communication."

---

Step 4 At the active PXM1E, enter the addlmi <ifNum> <type> command to designate the interface as a feeder. Replace <ifNum> with the logical interface number, in the range from 1 through 60. Replace <type> with 1 to specify that the interface you are configuring is a feeder.

Step 5 Enter the dsppnport to ensure that the port you are configuring is down. It the port is up, enter the dnpnport command to bring it down.

---

Note The port you are configuring must be down before you specify port signaling.

---

Step 6 Enter the cnfpnportsig <portid> -cntlvc ip command to define the signaling protocol used on the trunk. Replace <portid> using the format slot[:bay].line[:ifNum].

Step 7 Enter the uppnport <portid> command to bring the port up. Replace <portid> using the format slot:bay.line:ifNum. Table 11-4 describes these parameters.

Step 8 Establish a configuration session with the Cisco MGX 8850 (PXM1E) or the Cisco MGX 8830 using a user name with GROUP1 privileges or higher.

Step 9 At the UXM switch prompt, enter the cnfswfunc command to make the IGX node a feeder.

Step 10 Enter the uptrk create a standard trunk or an IMA trunk between the UXM on the IGX and the PXM1E on the Cisco MGX switch.

Step 11 Enter the cnftrk configure the trunk.

---

Note The configuration on the UXM end of the trunk must be identical to the configuration on the PXM1E end of the trunk.

---

Step 12 Enter the dsptrk command to ensure that the trunk you just configured is functioning properly.

---

Note For more information on the IGX switch and the IGX CLI, refer to the Cisco IGX 8400 Series Provisioning Guide, Release 9.3.30.

---

---

Deleting an IGX Feeder

This procedure describes how to remove an IGX feeder connection from a PXM1E card on a Cisco MGX 8850 (PXM1E) or a Cisco MGX 8830 switch.

---

Step 1 Establish a configuration session with the Cisco MGX 8850 (PXM1E) or the Cisco MGX 8830 using a user name with GROUP1 privileges or higher.

Step 2 At the active PXM1E, enter the delcon or delcons command to delete all connections to the IGX feeder.

---

Note If you use the delcon command, you must enter the command once for each connection to the IGX feeder.

---

Step 3 Enter the dellmi <ifNum> command to delete the LMI from the feeder interface. Replace <ifNum> with the number assigned to the port.

---

Note Remove all connections before you delete LMI on an interface.

---

Step 4 Establish a configuration session with the Cisco IGX 8400 switch using a user name with GROUP1 privileges or higher.

Step 5 At the UXM card, enter the cnftrk command to set the UXM trunk configuration so that it does to not listen for LMI/AAL5 messages.

Step 6 Enter the dntrk command to down the UXM interface.

Step 7 Enter the cnfswfunc to turn off the feeder functionality on the IGX switch. For more information on the IGX switch and the IGX CLI, refer to the Cisco IGX 8400 Series Provisioning Guide, Release 9.3.30.

---

Note For more information on the IGX switch and the IGX CLI, refer to the Cisco IGX 8400 Series Provisioning Guide, Release 9.3.30.

---

---