Cisco MGX 8850 (PXM45) and MGX 8950 Software Configuration Guide, Release 3 - Provisioning AXSM Communication Links [Cisco MGX 8800 Series Switches]

Table Of Contents

Provisioning AXSM Communication Links

Quickstart Provisioning Procedures

MPLS and PNNI Trunk Configuration Quickstart

MPLS and PNNI UNI Port Configuration Quickstart

SVC Configuration Quickstart

SPVC and SPVP Configuration Quickstart

PNNI Virtual Trunk Configuration Quickstart

PNNI Feeder Configuration Quickstart

BPX PNNI Trunk Configuration Quickstart

AINI Link Configuration Quickstart

IISP Link Configuration Quickstart

XLMI Link Configuration Quickstart

General AXSM 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 ILMI Traps and Signaling

Configuring ILMI Automatic Configuration

Configuring ILMI Dynamic Addressing

Starting ILMI with the Default or Existing Values

Configuring AXSM Line Clock Sources

Procedures for PNNI Links

Verifying PNNI Communications

Verifying PNNI Trunk Communications

Verifying End-to-End PNNI Communications

Configuring SPVCs and SPVPs

Configuring the Slave Side of SPVCs and SPVPs

Configuring the Master Side of SPVCs and SPVPs

Configuring SPVC/SPVP Overrides on Single-Ended Connections

Deleting SPVCs and SPVPs

Defining a PNNI Feeder Port

Defining Destination Addresses for Static Links

Provisioning AXSM Communication Links

This chapter describes how to add ATM ports and connections to the physical lines defined in "Preparing AXSM Cards and Lines for Communication." This chapter explains how to provision the link and connection types listed in Table 6-1.

Table 6-1 AXSM Link and Connection Types

AXSM Link or Connection Type

Description

MPLS and PNNI trunks

MPLS and PNNI trunks connect MGX switches to other MGX switches.

MPLS and PNNI UNI ports

MPLS and PNNI UNI ports connect MGX switches to CPE.

Switched Virtual Circuits (SVCs)

SVCs are temporary connections that are brought up and torn down upon request from CPE.

Soft Permanent Virtual Circuits (SPVCs)

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.

MGX 8850 Release 1 feeder PNNI trunks

Feeder trunks link a feeder switch, such as an MGX 8230 or
MGX 8250 switch, to an MGX 8850 Release 2 switch. The feeder switch concatenates relatively low speed traffic and feeds it over a higher speed interface to the MGX 8850 switch, which provide the link to the ATM network core.

BPX PNNI trunks

BPX PNNI trunks provide PNNI links between MGX 8850 and the MGX 8950 switches and BPX switches that support PNNI. The BPX switch supports PNNI when connected to the Cisco SES PNNI Controller.

ATM Inter-Network Interface (AINI) links

AINI links enable connectivity between two independent PNNI networks and block the PNNI database exchange so the two networks remain independent.

Interim Inter-switch Protocol (IISP) links

IISP links enable connectivity between two independent PNNI networks and block the PNNI database exchange so the two networks remain independent. IISP is the predecessor to AINI and should be used only when AINI is not supported on one or both ends of the network link.

Extended Link Management Interface (XLMI) 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.

a

The configuration differences between these different 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. As you get more experience configuring connections, you can look up fewer tasks.

Tips Remember that you can get information on most commands by entering the command without parameters. Experienced users can usually configure connections using just the quickstarts and the online help.

Note For all commands in this chapter, refer to the Cisco MGX 8850, MGX 8950, and MGX 8830 Command Reference (PXM45/B) for detailed information.

Note Before you start configuring ATM connections, complete the general switch configuration as described in "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 the switch.

MPLS and PNNI 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 MGX 8850 and MGX 8950 switches. This procedure is provided as an overview and as 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 procedures in this quickstart procedure, you must log in as a user with GROUP1 privileges or higher.

Step 2

Prepare AXSM cards and lines as described in "Preparing AXSM Cards and 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, which appears later in this chapter.

Step 4

addpart <options>

Related commands:

dspparts

dsppart

cnfpart

Assign trunk resources to PNNI and MPLS 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, which appears 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, which appears 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, which appears 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, which appears later in this chapter.

After you configure an AXSM 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.

MPLS and 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 MGX 8850 and MGX 8950 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 procedures in this quickstart procedure, you must log in as a user with GROUP1 privileges or higher.

Step 2

—

Prepare AXSM cards and lines as described in "Preparing AXSM Cards and 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, which appears later in this chapter.

Step 4

addpart <options>

Related commands:

dspparts

dsppart

cnfpart

Assign line resources to the PNNI and MPLS 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, which appears later in this chapter.

Step 5

dnpnport <portid>

At the PXM, 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, which appears 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, which appears 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, which appears 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, which appears 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.

MGX 8850 and MGX 8950 switches can use the PNNI and MPLS protocols 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 "MPLS and PNNI Trunk Configuration Quickstart" section, which appears earlier in this chapter.

Configure the trunks that link the switches through which the ATM end stations connect. Be sure to add the appropriate controller (which is either PNNI or MPLS) 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, which appears later in this chapter.

Step 3

See the "MPLS and PNNI UNI Port Configuration Quickstart" section, which appears 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 appropriate controller (which is either PNNI or MPLS) 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 8, "Switch Operating Procedures."

It is beyond the scope of this guide to describe how to configure each model of 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 MGX 8850 and MGX 8950 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.

A soft permanent virtual path (SPVP) is a permanent virtual path that can be rerouted using the Private Network-to-Network Interface (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 MGX 8850 and MGX 8950 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 procedures in this quickstart procedure, you must log in as a user with SUPER_GP privileges or higher.

Step 2

See "MPLS and PNNI Trunk Configuration Quickstart," which appears earlier in this chapter.

Configure the trunks that link the switches to which the ATM end stations connect.

Step 3

dsppnni-reachable-addr network

Verify PNNI connectivity between the two nodes that will host the SPVC or SPVP end points.

See the "Verifying End-to-End PNNI Communications" section, which appears later in this chapter.

Step 4

See "MPLS and PNNI UNI Port Configuration Quickstart," which appears earlier in this chapter.

Configure lines for the ATM end stations at each end of the SPVC or SPVP, and assign either static or dynamic addressing to each line.

Step 5

addcon <options>

Related commands:

dspchans

dspchan <ifNum> <vpi> <vci>

If you are configuring a double-ended SPVC, configure the slave side of the SPVC.

See the "Configuring SPVCs and SPVPs" section, which appears later in this chapter.

Note Release 3 MGX switches support single-ended SPVCs, so you do not need to configure that slave end of an SPVC

Step 6

addcon <options>

Related commands:

dspchans

dspchan <ifNum> <vpi> <vci>

Configure the master side of an SPVC.

See the "Configuring SPVCs and SPVPs" section, which appears later in this chapter.

PNNI Virtual Trunk Configuration Quickstart

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

Figure 6-1 Virtual Trunk Configuration

Figure 6-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 MGX 8850 and MGX 8950 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 AXSM card and 100 ports per switch.

Note SPVPs are not allowed on virtual trunks.

The following quickstart procedure provides a summary of the tasks required to configure virtual trunks on the MGX 8850 and MGX 8950 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 procedures in this quickstart procedure, you must log in as a user with SUPER_GP privileges or higher.

Step 2

—

Prepare AXSM cards and lines as described in "Preparing AXSM Cards and 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

Configure the virtual trunk end ports at the private switches. Select interface type 3 for VNNI.

See the "Adding ATM Ports" section, which appears 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, which appears later in this chapter.

Step 5

dnpnport <portid>

cnfpnportsig <options>

uppnport <portid>

Related commands:

dsppnports

dsppnport <portid>

dsppnportsig <portid>

Configure the virtual trunk signaling at the private switches. Select PNNI signaling by setting the -nniver option to pnni10.

See the "Selecting the Port Signaling Protocol" section, which appears later in this chapter.

Step 6

addport <options>

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, which appears later in this chapter.

Step 7

addpart <options>

Related commands:

dspparts

dsppart

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, which appears later in this chapter.

Step 8

dnpnport <portid>

cnfpnportsig <options>

uppnport <portid>

Related commands:

dsppnports

dsppnport <portid>

dsppnportsig <portid>

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, which appear later in this chapter.

Step 9

See the "Configuring SPVCs and SPVPs" section, which appears later in this chapter.

Fore each virtual trunk, configure an SPVP between the virtual trunk ports at each edge of the core network.

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, which appears later in this chapter.

PNNI Feeder Configuration Quickstart

The quickstart procedure in this section provides a summary of the tasks required to configure a connection from an MGX 8850 Release 1 feeder through one or more MGX 8850 Release 2 switches, and to a remote feeder or CPE. This procedure is provided as an overview and as a quick reference for those who have previously configured these types of connections.

Note Feeder connections from MGX 8850 Release 1 feeders are not supported on MGX 8950 switches and AXSM-E ports. The feeder trunk configuration is not complete until the MGX 8850 Release 1 feeder is also configured.
Command

Purpose

Step 1

username

<password>

Start a configuration session on the MGX 8850 Release 2 switch. This will be the local routing switch that connects to the feeder.

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 AXSM cards and lines as described in "Preparing AXSM Cards and 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

Configure the local routing switch port that leads to the feeder. When configuring the line, select either interface type 1 (UNI) or 2 (NNI). Use the same interface type when defining the port on the feeder.

See the "Adding ATM Ports" section, which appears later in this chapter.

Step 4

addpart <options>

Related commands:

dspparts

dsppart

cnfpart

Assign trunk resources to the PNNI controller ID, which is 2.

See the "Partitioning Port Resources Between Controllers" section, which appears later in this chapter.
Step 5

dnpnport <portid>

cnfpnportsig <options>

cnfoamsegep <portid> no

uppnport <portid>

Related commands:

dsppnports

dsppnport <portid>

dsppnportsig <portid>
Define the signaling protocol used on the trunk. If CWM will be used to manage the feeder, enter the cnfpnportsig command to enable IP communications between the switch and the feeder.
pop20two.7.PXM.a > cnfpnportsig <portid> -cntlvc ip
Use the cnfoamsegep command to define the local routing switch feeder port as a non-OAM segment endpoint. This is required to enable testing with the tstdelay command.

See the "Selecting the Port Signaling Protocol" section, which appears later in this chapter.
Step 6

addfdr <ifnum>

Related commands:

dspfdr <ifnum>

Define the local routing switch port as a feeder port.

See the "Defining a PNNI Feeder Port" section, which appears later in this chapter.

Step 7

Refer to the MGX 8850 Release 1 documentation.

At the MGX 8850 Release 1 feeder, enter the addcon command to add a connection on the link to the MGX 8850 Release 2 switch.

Step 8

—

Configure the port on the remote routing switch that terminates calls in the core network. If the remote routing switch port connects to a feeder, repeat Steps 2 and 3 to configure the remote feeder trunk. If the remote routing switch port connects to CPE, configure the port for UNI communications.

Step 9

cnfoamsegep <portid> no

Define the local routing switch feeder port as a non-OAM segment endpoint. This is required to enable testing with the tstdelay command.

Step 10

addcon <options>

Related commands:

dspcons

Create an SPVC from the local routing switch feeder port to the remote routing switch termination port.

See the "Configuring SPVCs and SPVPs" section.
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 MGX 8850 and MGX 8950 switches. The connection between an MGX 8850 or MGX 8950 switch and a BPX switch is a trunk between an AXSM 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 AXSM end of the trunk.

The procedure for configuring the AXSM end of the trunk is similar to the general procedure for configuring AXSM 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.
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 AXSM cards and lines as described in "Preparing AXSM Cards and 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 and VNNI for virtual trunks.

See the "Adding ATM Ports" section, which appears 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, which appears 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 this to pnni10. For example:
pop20two.7.PXM.a > cnfpnportsig <portid> -nniver pnni10
See the "Selecting the Port Signaling Protocol" section, which appears 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 AXSM side too.

See the "Configuring ILMI on a Port" section, which appears 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, which appears 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 "Configuring SPVCs and SPVPs," which appears 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 MGX 8850 and MGX 8950 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 procedures in this quickstart procedure, you must log in as a user with SUPER_GP privileges or higher.

Step 2

Prepare AXSM cards and lines as described in "Preparing AXSM Cards and 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, which appears 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, which appears 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:
M8850_LA.7.PXM.a > cnfpnportsig 1:1.1:1 -nniver aini
See the "Selecting the Port Signaling Protocol" section, which appears 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, which appears 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, which appears later 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 MGX 8850 and MGX 8950 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 procedures in this quickstart procedure, you must log in as a user with SUPER_GP privileges or higher.

Step 2

—

Prepare AXSM cards and lines as described in "Preparing AXSM Cards and 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, which appears 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, which appears 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:
M8850_LA.7.PXM.a > cnfpnportsig 1:1.1:1 -nniver iisp31
See the "Selecting the Port Signaling Protocol" section, which appears 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, which appears 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, which appears 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.

Note XLMI links are not supported on MGX 8950 switches, AXSM-E, or AXSM-32-E cards.

To establish an XLMI link, you need to perform the following tasks:

1. Configure an AXSM 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 AXSM 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 AXSM or AXSM/B card supports a maximum of 16 links to AutoRoute networks and feeder nodes.

•Each AXSM or AXSM/B 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 AXSM 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 AXSM. Timer configuration is done on the BPX. The values for the LMI timers on AXSM 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 MGX 8850 switches.
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 SUPER_GP privileges or higher.

Step 2

—

Prepare AXSM cards and lines as described in "Preparing AXSM Cards and 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 AXSM cards supports XLMI on UNI or NNI ports.

See the "Adding ATM Ports" section, which appears 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, which appears later in this chapter.
Step 5

addlmi <interface> <type>

Related commands:

dsplmi <interface>
Add LMI to the port. For example:
M8850_NY.6.AXSM.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:
M8850_LA.7.PXM.a > cnfpnportsig 1:1.1:1 -nniver enni
See the "Selecting the Port Signaling Protocol" section, which appears 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 AXSM 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, which appears 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, Release 9.3.30.
General AXSM Configuration Procedures

This section describes the following general procedures for configuring AXSM 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, NNI, or VNNI 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 MGX 8850 or MGX 8950 switch. VNNI ports support virtual trunk connections between two ATM end stations.

You must configure one ATM port for each line or trunk to enable ATM communications over that link. You define the port type (UNI, NNI, or VNNI) when you add the ATM port to the line or trunk.

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:
mgx8850a.10.AXSM.a > dsplns 
Tips Remember that you cannot configure a line until you have brought it up as described in the "Bringing Up Lines" section in "Preparing AXSM Cards and 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 AXSM card, enter the following command:
mgx8850a.10.AXSM.a > dspports 
This command displays all ports on the AXSM card in the ifNum (interface number) column. The interfaces listed include UNI, NNI, and VNNI 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 AXSM 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 AXSM card.

Note The Cisco MGX 8850 and MGX 8950 switches support one port per line.

Step 4 To add an ATM port to a line, enter the following command:
mgx8850a.10.AXSM.a > addport <ifNum> <bay.line> <guaranteedRate> <maxRate> <sctID> 
<ifType> [vpi]
Table 6-2 lists the parameter descriptions for adding ports. Figure 6-2 shows the relationship between logical interface numbers and physical lines.

Table 6-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 60 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. For VNNI ports (for virtual trunks), you can assign multiple logical interfaces per line.

bay

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 AXSM-1-2488.

line

Replace <line> with the number that corresponds to the back card port to which the line is connected. Table 6-3 lists the valid line numbers for each AXSM card.

guaranteedRate

Enter the minimum rate for the port in cells per second (cps).

Note In this release, the <guaranteedRate> value should equal the <maxRate> value.

The rate ranges are as follows:

OC48: 50 to 5651320.

OC12: 50 to 1412830.

OC3: 50 to 353207.

T3: 50 to 96000 (PLCP) or 104268 (ADM).

E3: 50 to 80000.

maxRate

Enter the maximum rate for the port in cps.

Note In this release, the <maxRate> value should equal the <guaranteedRate> value.

The rate ranges are as follows:

OC48: 50 to 5651320.

OC12: 50 to 1412830.

OC3: 50 to 353207.

T3: 50 to 96000 (PLCP) or 104268 (ADM).

E3: 50 to 80000.

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. If MPLS will be used on the port, use SCT ID 4 for policing applications and use SCT ID 5 for non-policing applications.

Note Cisco Systems recommends that you use non-policing SCT IDs for all ports configured with the NNI and VNNI interface types.

ifType

Enter a number that indicates the interface type. Enter 1 for UNI, 2 for NNI, and 3 for VNNI, which defines a virtual trunk port.

vpi

When the <ifType> parameter is set to 3 for VNNI, enter a VPI number for the virtual trunk in the range of 1 to 4095. This parameter is not required for UNI and NNI ports.