Provisioning ATM Services on MPSM-T3E3-155 and MPSM-16-T1E1 · Part Number OL-6487-01 Rev. B0, March 15, 2005 Chapter 3 Provisioning ATM Services on MPSM-T3E3-155 and MPSM-16-T1E1

C H A P T E R

3-1Cisco ATM and Frame Relay Services (MPSM-T3E3-155 and MPSM-16-T1E1) Configuration Guide and Command Reference, Release 5.1

Part Number OL-6487-01 Rev. B0, March 15, 2005

3Provisioning ATM Services on MPSM-T3E3-155 and MPSM-16-T1E1

This chapter describes how to provision ATM services on the MPSM-T3E3-155 and MPSM-16-T1E1 cards, and provides procedures for adding ATM ports and connections to the physical lines and paths. The types of links and connections presented in this chapter are listed in Table 3-1.

Note Before you perform the procedures in this section, you must set up the MPSM-T3E3-155 and MPSM-16-T1E1 cards and lines from the PXM controller as described in Chapter 2, “Preparing MPSM-T3E3-155 and MPSM-16-T1E1 Cards and Lines for Communication.” Make sure that you select the appropriate card SCT for the controller that you are using.

Table 3-1 MPSM-T3E3-155 and MPSM-16-T1E1 ATM Link and Connection Types

ATM Link or Connection Type Description

PNNI trunks NNI trunks connect Cisco MGX switches to other Cisco MGX switches.

PNNI UNI ports PNNI UNI ports connect Cisco 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 as one link.

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



Chapter 3 Provisioning ATM Services on MPSM-T3E3-155 and MPSM-16-T1E1Quickstart Provisioning Procedures

The MPSM-T3E3-155 and MPSM-16-T1E1supports ATM SPVCs, SPVPs, and SVCs to the following cards:

• another MPSM-T3E3-155

• another MPSM-16-T1E1

• MPSM-8

• FRSM12, FRSM-8, FRSM-2CT3, FRSM-2T3E3, FRSM-HS2/B

• RPM

• AUSM

• AXSM/B, AXSM-E, AXSM-XG

• PXM1E

• VISM

• CESM-8

• BXM (on a BPX 8600 switch)

To perform the procedures in this section, you must start a CLI session on the appropriate MPSM-T3E3-155 and MPSM-16-T1E1 cards by logging in with the appropriate username and password. For detailed information about usernames, passwords, and logging into the CLI, refer to the Cisco MGX 8850 (PXM1E/PXM45), Cisco MGX 8950, and Cisco MGX 8830 Configuration Guide, Release 5.

Note To perform the procedures in this section, you must log in as a user with Group1 privileges or higher.

Quickstart Provisioning ProceduresThis section presents abbreviated procedures that you can use to configure lines and provision connections. These procedures are for experienced users who already have experience configuring the MPSM-T3E3-155 and MPSM-16-T1E1 cards.

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.

Table 3-1 MPSM-T3E3-155 and MPSM-16-T1E1 ATM Link and Connection Types (continued)

ATM Link or Connection Type Description




ATM Trunk Configuration QuickstartATM 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 Comments

Step 1 username

<password>

Start a configuration session.

To perform all of the steps in this quickstart procedure, you must log in as a user with Group1 privileges or higher.

Step 2 cc Change to the MPSM-T3E3-155 or MPSM-16-T1E1 card.

Step 3 setctx atm If the current CLI context is Frame Relay, use the setctx atm command to ensure you are using the ATM CLI.

Step 4 upln Bring up lines as described in the Chapter 2, “Preparing MPSM-T3E3-155 and MPSM-16-T1E1 Cards and Lines for Communication.”

Step 5 addport

or

addimagrp

addimalnk

addimaport

Related command:

dspports

Add and configure ATM ports. This step establishes ATM communication between two ATM devices.

Specify NNI for interswitch trunks.

For standard port configuration, see the “Adding ATM Ports” section on page 3-18.

To configure ATM communication over an IMA group, see the “Configuring Inverse Multiplexing over ATM” section later in this chapter.

Note The MPSM-T3E3-155 and MPSM-16-T1E1 require a multilink license for IMA configuration. Without a multilink license, you cannot configure IMA on the MPSM-T3E3-155 and MPSM-16-T1E1 cards. To view the feature licenses that are assigned to or are needed by the cards, enter the dspliccd command

Step 6 cnfport

Related commands:

dspports

dspports

Use this optional step to make changes to the port created in the previous step.

For more information on modifying ports, see the “Adding ATM Ports” section later in this chapter.




Step 7 cnfpart

Related commands:

dspparts

dsppart

Configure trunk resources that are assigned to the PNNI controller. This step can assign all trunk bandwidth to one controller, or it can assign portions of the trunk bandwidth to each controller.

See the “Partitioning Port Resources on the PNNI Controller” section on page 3-30.

Note On the MPSM-T3E3-155 and MPSM-16-T1E1, a partition is automatically added when you add a port. To change the configuration of a resource partition, use the cnfpart command.

Step 8 cc Change to the PXM card.

Step 9 dnpnport

cnfpnportsig

uppnport

Related commands:

dsppnports

dsppnport

dsppnportsig

Define the signaling protocol used on the trunk. Specify pnni10 for PNNI trunks.

See the “Selecting the Port Signaling Protocol” section on page 3-34.

Step 10 Configure the other end of the link. If the other end of the link is connected to another MPSM-T3E3-155 or MPSM-16-T1E1 card, repeat Step 1 through Step 8.

If the other end of the link is on a different card type, refer the documentation for that card.

Step 11 cc

dsppnni-link

dsppnni-neighbor

When both ends of the link are configured, change to the active PXM card and verify the PNNI communication between the two ends of the connection. In the dsppnni-link report, there should be an entry for the port for which you are verifying communication. 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 Communication” section in Chapter 6, “MPSM-T3E3-155 and MPSM-16-T1E1 Card Management.”

Step 12 cc Change back to the appropriate card.


Step 14 upilmi

cnfilmi

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 on page 3-36.

Command Comments




After you configure an MPSM-T3E3-155 or MPSM-16-T1E1 trunk, the trunk is ready to support SVCs. You can also create SPVCs and SPVPs between the CPE at each end of the trunk.

PNNI UNI Port Configuration QuickstartATM UNI ports connect the switch to ATM end devices, which serve as the boundary between the ATM network and other communication 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/PXM45) 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.

Command Comments

Step 1 username

<password>




Step 3 upln Bring up MPSM-T3E3-155 lines as described in the Chapter 2, “Preparing MPSM-T3E3-155 and MPSM-16-T1E1 Cards and Lines for Communication.”


Step 5 addport

or

addimagrp

addimalnk

addimaport

Related command:

dspports


Specify UNI for interswitch trunks.

For standard port configuration, see the “Adding ATM Ports” section on page 3-18.

To configure ATM communication over an IMA group, see the “Configuring Inverse Multiplexing over ATM” section later in this chapter.

Note The MPSM-T3E3-155 and MPSM-16-T1E1 require a multilink license for IMA configuration. Without a multilink license, you cannot configure IMA on the cards. To view the feature licenses that are assigned to or are needed by the cards, enter the dspliccd command.

Step 6 cnfport

Related commands:

dspports

dspports

Use this optional step if you need to make changes to the port created in the previous step.

For more information on modifying ports, see the “Adding ATM Ports” section later in this chapter.




Step 7 cnfpart

Related commands:

dspparts

dsppart

Configure the trunk resources that are assigned to the PNNI controller. This step can assign all of the trunk bandwidth to one controller, or it can assign portions of the trunk bandwidth to each controller.


Note On the MPSM-T3E3-155 and MPSM-16-T1E1, a partition is automatically added when you add a port. Use the cnfpart command to change the configuration of a resource partition.


Step 9 dnpnport <portid> Bring down the port so it can be configured. The next three steps require this step.

Step 10 cnfpnportsig

Related commands:

dsppnports

dsppnport

dsppnportsig

Define the signaling protocol used on the line.

Specify uni30, uni31, or uni40.


Step 11 cnfaddrreg

addaddr

Related commands:

dsppnports

dspatmaddr

deladdr

Configure static ATM addresses for ports that require them.


Step 12 addprfx

Related commands:

cnfaddrreg

dspprfx

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 on page 3-39.

Step 13 uppnport Bring up port after configuration is complete.

Step 14 cc Change back to the appropriate card.


Step 16 upilmi

cnfilmi

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.


Command Comments




SVC Configuration QuickstartSwitched 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/PXM45) 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 communication. 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.

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 must learn the capabilities of the CPE and the switch and define a set of communication parameters that are supported by both devices. For example, the Cisco MGX 8850 (PXM1E/PXM45) and Cisco MGX 8830 switches support UNI 3.1 communication, but if the CPE does not, you must select a signaling protocol (such as UNI 3.0) that is supported by both devices.

After all of the requirements are met for SVC connections, CPE devices can establish SVC connections to other CPE devices on the same switched network.

Command Comments

Step 1 See the “ATM Trunk Configuration Quickstart” section on page 3-3.

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

At the PXM, verify connectivity between the node pairs that will host SVCs.

See the “Verifying End-to-End PNNI Communications” section in Chapter 6, “MPSM-T3E3-155 and MPSM-16-T1E1 Card Management.”

Step 3 See the “PNNI UNI Port Configuration Quickstart” section on page 3-5.

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 communication 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. Enter this command on the active the PXM.




SPVC and SPVP Configuration QuickstartA 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. 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 Cisco MGX 8850 (PXM1E/PXM45) and Cisco MGX 8830 switches. This procedure is provided as an overview and as a quick reference for those who have previously configured these types of connections.

Command Comments

Step 1 See the ““ATM Trunk Configuration Quickstart” section on page 3-3.

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.


At the PXM, verify connectivity between the node pairs that will host SVCs.


Step 3 See the ““PNNI UNI Port Configuration Quickstart” section on page 3-5.

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 you partition trunks.



Step 6 addcon

Related commands:

dspchans

dspchan

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

If the slave side of the connection is on:

• An MPSM card, see the “Configuring the Slave Side of SPVCs and SPVPs” section on page 43.

• A non-MPSM card, refer to the documentation for that card.

Note If you are configuring a single-ended SPVC, you do not need to configure the slave end of an SPVC.

Step 7 dspcon Verify the configuration for the connection you added in Step 4.




PNNI Virtual Trunk Configuration QuickstartVirtual trunks are introduced and explained in the Cisco MGX 8850 (PXM1E/PXM45), Cisco MGX 8950, and Cisco MGX 8830 Configuration Guide, Release 5. Figure 3-1 illustrates how to configure a virtual trunk.

Figure 3-1 Virtual Trunk Configuration

Step 8 username

<password>

or

cc

If you are configuring an SPVC between:

• The MPSM and a remote card—Log onto the remote card.

• Two ports on the current MPSM card—Change to the desired card using the cc command.

Step 9 addcon

Related commands:

dspcon

dspcons

Add and configure the master side of an SPVC or SPVP on the remote card.

If the master side of the connection is on:

• The MPSM card, see the “Configuring the Master Side of SPVCs and SPVPs” section on page 51.

• A non-MPSM card, refer to the documentation for that card.

Step 10 dsppncons This optional step displays the SVC connections that are operating. Enter this command on the active the PXM.

Command Comments

VNNIport 10:1.2:2

VNNIport 10:1.2:7

Core ATMnetwork

SPVP

SPVPEdge

switch 1

VPI 12

Legend

Physical line

VPI 10Private

switch A

Edgeswitch 2

Edgeswitch 3

port 6:2.1:12

port 6:2.1:43

Privateswitch B

port 59

VNNIport50

Privateswitch C

VNNIport 36

port 3

VPI 10

VPI 12

Virtual trunk 4650

7




Figure 3-1 shows an example of configuration data that you can use when following the 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, depending on the card type.

To set up a virtual trunk, the following tasks must 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.

Cisco MGX 8850 (PXM1E/PXM45) and Cisco MGX 8830 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 MPSM-T3E3-155 card and 100 ports per switch.

The following is a summary of the tasks required to configure virtual trunks on Cisco MGX 8850 (PXM1E/PXM45) and Cisco MGX 8830 switches.

Command Comments

Step 1 username

<password>






Step 5 Add a channelized path:

cnfpath

uppath

Related commands:

dsppath

dsppaths

Add and configure a channelized path. Perform this step only if you are configuring a virtual trunk on an MPSM-T3E3-155 port. See the “Channelizing MPSM-T3E3-155 SONET, SDH, and DS3 (T3) Lines” section in Chapter 2, “Preparing MPSM-T3E3-155 and MPSM-16-T1E1 Cards and Lines for Communication,” for details.

Step 6 addport

or

addimagrp

addimalnk

addimaport

Related commands:

dspports

dspimagrps

dspimalnks

Configure the virtual trunk end ports at the private switches. Select interface type 3 for VNNI. See the “Adding ATM Ports” section on page 3-18.

Or if you are configuring IMA, add and configure IMA groups, then IMA links, then IMA ports. See the “Configuring Inverse Multiplexing over ATM” section on page 3-22.

Note The MPSM-T3E3-155 and MPSM-16-T1E1 card require a multilink license for IMA configuration. Without a multilink license, you cannot configure IMA on the cards. To view the feature licenses that are assigned to or are needed by the cards, enter the dspliccd command.




Step 7 cnfpart

Related commands:

dspparts

dsppart

cnfpart

Optional: Configure the trunk resources that are assigned to the PNNI controller. This step can assign all trunk bandwidth to one controller, or it can assign portions of the trunk bandwidth to each controller.

Note A partition is automatically added when you add a port. Use the cnfpart command to change the configuration of a resource partition.

Note Enter the same VPI number for the minVpi and maxVpi parameters. This number becomes the VPI number for the trunk.



Step 9 dnpnport

cnfpnportsig

uppnport

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 on page 3-34.

Related commands:

dsppnports

dsppnport

dsppnportsig

Step 10 cc Change back to the card.

Step 11 setctx atm If the current CLI context is Frame Relay, use the setctx atm command to ensure that you are using the ATM CLI.

Step 12 addport

Related command:

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 on page 3-18.

Step 13 cnfpart

Related commands:

dspparts

dsppart

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.

Note When you add a port, a partition is automatically added. To change the configuration of a resource partition, use the cnfpart command.



Command Comments




Cisco BPX PNNI Trunk Configuration QuickstartWhen the Cisco SES PNNI controller is attached to a Cisco BPX switch, the Cisco BPX switch can participate in a PNNI network with Cisco MGX 8850 (PXM1E/PXM45) or Cisco MGX 8830 switches. The connection between a Cisco MGX 8850 (PXM1E/PXM45) or Cisco MGX 8830 switch and a Cisco BPX switch is a trunk between an MPSM card in the Cisco MGX switch and a Cisco BXM card in the Cisco BPX switch. For instructions on configuring the BXM end of the trunk, refer to the Cisco SES product documentation. This section describes how to configure the MPSM end of the trunk.

The procedure for configuring the MPSM end of the trunk is similar to the general procedure for configuring MPSM trunks. The following procedure is customized for setting up Cisco BPX PNNI trunks.

Note The trunk configuration is not complete until the BXM end of the trunk is configured.

Caution Before you can configure a BPX PNNI trunk, you must allocate PNNI resources. To verify that a PNNI resource is allocated on the trunk, enter the dsprsrc <slot.port> command on the active PXM.

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



Step 18 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.



Verify PNNI connectivity between the two nodes that will host the virtual trunk end points.


Command Comments




Command Comments

Step 1 username

<password>




Step 3 cnfpath

Related commands:

dsppath

dsppaths

Add and configure a channelized path. Do this step only if you are configuring a virtual trunk on an MPSM-T3E3-155. See “Channelizing MPSM-T3E3-155 SONET, SDH, and DS3 (T3) Lines” in Chapter 2, “Preparing MPSM-T3E3-155 and MPSM-16-T1E1 Cards and Lines for Communication.”.

Step 4 uppath

Related commands:

dsppath

dsppaths

Bring up the path you configured in Step 3.

Step 5 addport

Related command:

dspports


Specify NNI for interswitch trunks and VNNI for virtual trunks.


Step 6 cnfpart

Related commands:

dspparts

dsppart





Step 8 dnpnport

cnfpnportsig

uppnport

Related commands:

dsppnports

dsppnport

dsppnportsig

Configure the signaling protocol used on the trunk to be pnni10. For example:

MGX8850.7.PXM.a > cnfpnportsig <portid> -nniver pnni10


Step 9 cc Change back to the MPSM-T3E3-155 or MPSM-16-T1E1 card.




After you configure a Cisco 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 the Master Side of SPVCs and SPVPs” section on page 3-51.

AINI Link Configuration QuickstartThe 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 an overview and acts as a quick reference for those who have previously configured these types of connections.

Note AINI is a new 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 V4.0 connections.

Step 10 upilmi

cnfilmi

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 MPSM side too.



Step 12 dsppnni-link

dsppnni-neighbor

After you have configured both ends of the link, verify the PNNI communication. In the dsppnni-link report, an entry for the port for which you are verifying communication should appear. The reported Hello state should be twoWayInside and the Remote node ID should display the remote node ATM address after the second colon.

See the “Verifying PNNI Trunk Communication” section in Chapter 6, “MPSM-T3E3-155 and MPSM-16-T1E1 Card Management.”

Command Comments

Command Comments

Step 1 username

<password>







Step 3 cnfpath

Related commands:

dsppath

dsppaths

Add and configure a channelized path. Do this step only if you are configuring a virtual trunk on an MPSM-T3E3-155. See the “Channelizing MPSM-T3E3-155 SONET, SDH, and DS3 (T3) Lines” section in Chapter 2, “Preparing MPSM-T3E3-155 and MPSM-16-T1E1 Cards and Lines for Communication,” for details.

Step 4 uppath

Related commands:

dsppath

dsppaths


Step 5 addport

Related command:

dspports




Step 6 cnfpart

Related commands:

dspparts

dsppart





Step 8 dnpnport

cnfpnportsig

uppnport

Related commands:

dsppnports

dsppnport

dsppnportsig

Configure the signaling protocol used on the trunk to be aini. For example:

MGX8850.7.PXM.a > cnfpnportsig <portid> -nniver aini



Step 10 addaddr Add destination addresses to each end of the trunk.

See the “Defining Destination Addresses for Static Links” section on page 3-53.

Step 11 addaddr 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 “Defining Destination Addresses for Static Links” section on page 3-53.

Command Comments




IISP Link Configuration QuickstartThe 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 new 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 V4.0 connections.

Command Comments

Step 1 username

<password>



Step 2 Bring up MPSM-T3E3-155 lines as described in the Chapter 2, “Preparing MPSM-T3E3-155 and MPSM-16-T1E1 Cards and Lines for Communication.”

Step 3 cnfpath

Related commands:

dsppath

dsppaths

Add and configure a channelized path. Do this step only if you are configuring a virtual trunk on an MPSM-T3E3-155. See the “Channelizing MPSM-T3E3-155 SONET, SDH, and DS3 (T3) Lines” section in Chapter 2, “Preparing MPSM-T3E3-155 and MPSM-16-T1E1 Cards and Lines for Communication,” for details.

Step 4 uppath

Related commands:

dsppath

dsppaths


Step 5 addport

Related command:

dspports




Step 6 cnfpart

Related commands:

dspparts

dsppart







Chapter 3 Provisioning ATM Services on MPSM-T3E3-155 and MPSM-16-T1E1ATM Configuration Concepts

ATM Configuration ConceptsThis section describes the following MPSM-T3E3-155 and MPSM-16-T1E1 ATM configuration concepts and general procedures:

• Adding ATM Ports

• Configuring Inverse Multiplexing over ATM

• Partitioning Port Resources on the PNNI Controller

• Selecting the Port Signaling Protocol

• Configuring ILMI on a Port

• Provisioning and Managing SPVCs and SPVPs

• Defining Destination Addresses for Static Links

Most of the descriptions and procedures in this section use ATM service context commands. See Chapter 7, “MPSM-T3E3-155 and MPSM-16-T1E1 Command Reference” for detailed descriptions of the MPSM-T3E3-155 and MPSM-16-T1E1 ATM service commands and parameters. Some of the procedures in this section use PXM commands and PNNI commands. Refer to the Cisco MGX 8830, Cisco MGX 8850 (PXM45 and PXM1E), and Cisco MGX 8950 Command Reference, Release 5 for descriptions of the PXM and PNNI commands and parameters.

Refer to the following documentation for additional information regarding ATM provisioning:

• For a list of the MPSM-T3E3-155 and MPSM-16-T1E1 model numbers, back cards, and the number of possible connections, see Table 1-2 in Chapter 1, “Introduction”.

• For more information on port signaling, refer to the Cisco MGX 8850 (PXM1E/PXM45), Cisco MGX 8950, and Cisco MGX 8830 Configuration Guide, Release 5.

Step 8 dnpnport

cnfpnportsig

uppnport

Related commands:

dsppnports

dsppnport

dsppnportsig

Configure the signaling protocol used on the trunk.to be either iisp30 or iisp31 for IISP trunks. For example:

MGX8850.7.PXM.a > cnfpnportsig <portid> -nniver iisp31



Step 10 addaddr Add destination addresses to each end of the trunk.

See the “Defining Destination Addresses for Static Links” section later in this chapter.

Step 11 addaddr 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 “Defining Destination Addresses for Static Links” section later in this chapter.

Command Comments




• For more information on ATM address planning, refer to the Cisco MGX and SES PNNI Network Planning Guide.

• For information on additional ILMI management procedures, refer to the Cisco MGX 8850 (PXM1E/PXM45), Cisco MGX 8950, and Cisco MGX 8830 Configuration Guide, Release 5. See the Chapter 7, “MPSM-T3E3-155 and MPSM-16-T1E1 Command Reference” for descriptions of ILMI commands and parameters.

Adding ATM PortsOn an MPSM-T3E3-155 or MPSM-16-T1E1 card, a logical port is also called a virtual interface and is represented by the ifNum variable. The MPSM cards can have the following types of interfaces:

• UNI (User-to-Network Interface)—You can configure only one logical port per line.

• NNI (Network-to-Network Interface)—You can configure only one logical port per line.

• VNNI (Virtual Network-to-Network Interface)—You can configure multiple ports per line.

• VUNI (Virtual User-to-Network Interface)—You can configure multiple ports per line.

• EVUNI (Enhanced Virtual User-to-Network Interface)—You can specify a range of VPIs for one interface, and this range of VPIs represents the virtual UNI trunk.

• EVNNI (Enhanced Virtual Network-to-Network Interface)—You can specify a range of VPIs for one interface, and this range of VPIs represents the virtual NNI trunk.

Note Multiple VNNIs and EVNNIs can coexist on the same line.

Bringing up a line establishes minimal connectivity between two nodes. When you add an ATM port to a line or path, you enable ATM communication over the line.

Each line can support UNI, NNI, VNNI, EVNNI, or EVUNI 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 switch. VNNI ports support virtual trunk connections between two ATM end stations. EVNNI and EVUNI are enhanced virtual trunks for network and user connections.

You must configure one ATM port for each line or path to enable ATM communication over that link.

When you add the ATM port to the line or path, you define the port type (UNI, NNI, VNNI, EVNNI, or EVUNI).

Note You cannot add a port directly on a SONET line. If you are configuring lines on an OC-3 back card (the SFP-2-155 or SMB-2-155-EL), you must first configure paths on the SONET line, as described in the “Channelizing MPSM-T3E3-155 SONET, SDH, and DS3 (T3) Lines” section in Chapter 2, “Preparing MPSM-T3E3-155 and MPSM-16-T1E1 Cards and Lines for Communication.”

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

Step 1 Establish a configuration session using a username with Group1 privileges or higher.

Step 2 Obtain the line or path number on which you will add the port, and verify that the line/path and port number you want to use is not already configured.




To display a list of the lines and their numbers, enter the dsplns command:

MGX8850.10.MPSM-155[ATM].a > dsplns .

If you adding a port to a path, enter the dsppaths -all command to display a list of all paths:

MGX8850.10.MPSM-155[ATM].a > dsppaths -all

Step 3 To display a list of the ports already configured on the card, enter the dspports command as shown in the following example:

M8850_NY.13.MPSM155[ATM].a > dspportsifNum Line/ Admin Oper Guaranteed Maximum sctID ifType VPI MINVPI MAXVPI IMA Path State State Rate Rate Cnf/InUse (VNNI, (EVUNI, (EVUNI, GRP VUNI) EVNNI) EVNNI)----- ----------- ----- ---------- ---------- -------- ----------- ------ ------ ------- ------- --- 4 1.1.1 Up LowLayerDn 100 100 0/ 0 =Def NNI 0 0 0 N/A

This command displays the existing port numbers on the card in the ifNum (interface number) column. The interfaces listed can include UNI, NNI, VNNI, EVNNI, and EVUNI ports. When you add a port, you must specify a port number that is unique on the card. For example, if port number 2 is assigned to line 1.1 (bay 1, line 1), you cannot use port 2 on any other line on that MPSM-T3E3-155 card.

Step 4 To add an ATM port to a line or path, enter the addport command as follows:

M8850_NY.13.MPSM155[ATM].a > addport <ifNum> <path_num> <guaranteedRate> <maxRate> <sctID> <ifType> [-vpi <vpi>] [-minvpi <minvpi>] [-maxvpi <maxvpi>]

Table 3-2 lists the parameters for configuring ATM ports.

Table 3-2 Parameters for Configuring ATM Ports Using the addport Command

Parameter Description

ifNum Specifies the interface number (port number) of the port you are adding.

• MPSM-16-T1E1 range: 4–499

• MPSM-T3E3-155 range: 4–1003

Note Port numbers 1 through 3 are reserved for broadband Frame Relay ports.

path_num Identifies the line or path on which to add the port:

• T1/E1 or T3/E3 line: bay.line

• DS3 payload: bay.line[.sts]:[ds1]

• VT payload: bay.line[.sts]:[vtg.vt]

• VT structured: bay.line[.sts]:[tug3.vtg.vt]

where: bay=1, line=1-3, sts=0-3, ds1=1-28, tug3=1-3, vtg=1-7, vt=1-4 (VT15) or 1-3 (VT2)

Note To see the path numbers for all available paths, use the dsppaths command. To see line numbers for all available lines, use the dsplns command.

Note On a BNC-3-T3 or BNC-3-E3 back card, you can add a port on a physical line or on a path. On an SFP-2-155 and the SMB-2-155-EL OC-3 back card, you can add a port on a path only.




guaranteedRate Specifies the guaranteed rate on a port in cells per second. The guaranteed rate can be either max cell rate of the interface, or a multiple of 50.

The total guaranteed rates cannot exceed the highest value in the following ranges:

• MPSM-T3E3-155 ranges:

– OC-3—50 through 353207 cps

– STS1—50 through 114113 cps

– DS3—Between 50 and 96000(PLCP) or 104268(ADM)

– E3—50 and 80000

– E1—Between 50 and 4528 cps

– DS1—Between 50 and 3622 cps

• MPSM-T3E3-155 and MPSM-16-T1E1 ranges:

– E1—Between 50 and 4528 cps

– DS1—Between 50 and 3622 cps

Note For all interface types (UNI, NNI, VNNI, EVNNI, and EVUNI), the guaranteedRate must be the same as maxrate.

maxRate Specifies the maximum rate on a logical port in cells/second. For all interface types (UNI, NNI, VNNI, EVNNI, and EVUNI), maxrate must be the same as guaranteedRate. See guaranteedRate.

sctID The ID of a service class template (SCT) for the port. The range is 0–255. The SCT file must exist on the PXM disk. See cnfcdsct.

Note Currently, the system does not support certain parameters in the service class templates (SCTs). When applicable, these parameters are PCR, SCR, and ICR. To specify the parameters, use the addcon command, the cnfcon command, or Cisco WAN Manager.

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 permit a range of VPIs for one interface, and this range of VPIs represents the virtual NNI or virtual UNI trunk. VNNI and VUNI allow only one VPI for one interface, and that VPI represents the virtual NNI or virtual UNI trunk. Multiple VNNIs and EVNNIs can coexist on the same line.

-vpi Virtual Path Identifier for a VNNI or VUNI interface:

• VNNI range: 1–4095

• VUNI range: 1–255

Table 3-2 Parameters for Configuring ATM Ports Using the addport Command (continued)





The following sample command adds an UNI port to a line:

M8850_NY.13.MPSM155[ATM].a > addport 20 1.2:1 1000 1000 0 1

Step 5 To display a list of the ports configured on the card, enter the dspports command as follows:

M8850_NY.13.MPSM155[ATM].a > dspports

This command displays all configured ports on the 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.

M8850_NY.13.MPSM155[ATM].a > dspportsifNum Line/ Admin Oper Guaranteed Maximum sctID ifType VPI MINVPI MAXVPI IMA Path State State Rate Rate Cnf/InUse (VNNI, (EVUNI, (EVUNI, GRP VUNI) EVNNI) EVNNI)----- ----------- ----- ---------- ---------- -------- ----------- ------ ------ ------- ------- --- 10 N/A Up LowLayerDn 1000 1000 0/ 0 =Def NNI 0 0 0 1 11 N/A Up LowLayerDn 1000 1000 0/ 0 =Def NNI 0 0 0 2 20 1.2:1 Up LowLayerDn 1000 1000 0/ 0 =Def UNI 0 0 0 N/A 21 1.2:2 Up LowLayerDn 3622 3622 0/ 0 =Def UNI 0 0 0 N/A

Step 6 To display the port configuration, enter the dspport command as follows:

MGX8850.10.MPSM-155[ATM].a > dspport <ifNum>

Replace <ifNum> with the number assigned to the port during configuration. The following example shows information for port 4.

M8850_NY.13.MPSM155[ATM].a > dspport 4 Interface Number : 4 Line/Path Number : 1.1.1 IMA Group Number : N/A Admin State : Up Operational State : LowLayern Guaranteed bandwidth(cells/sec): 1000 Number of partitions : 1 Maximum bandwidth(cells/sec) : 1000 Number of SPVC : 0 ifType : NNI Number of SPVP : 0 VPI number (VNNI, VUNI) : 0 Number of SVC : 0 Number of Sig VC : 0 MIN VPI (EVNNI, EVUNI) : 0 MAX VPI (EVNNI, EVUNI): 0 SCT Id : 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 using the upport and dnport commands.

-minvpi The minimum VPI for an EVUNI or EVNNI interface:

• EVUNI range: 0–255

• EVNNI range: 0–4095

-maxvpi The maximum VPI for an EVUNI or EVNNI interface:



Table 3-2 Parameters for Configuring ATM Ports Using the addport Command (continued)





Configuring Inverse Multiplexing over ATMInverse Multiplexing over ATM (IMA) is a protocol that combines multiple T1 or E1 interfaces into one high-speed IMA interface, called an IMA group.

Note The MPSM-T3E3-155 and MPSM-16-T1E1 cards require a multilink license for IMA configuration. To view the feature licenses that are assigned to or are needed by the cards, enter the dspliccd command.

The IMA feature has the following capabilities and restrictions:

• The MPSM-T3E3-155 supports a maximum of 42 IMA groups with up to 16 links per group. IMA links on the MPSM-T3E3-155 are paths on a channelized line.

• The MPSM-16-T1E1 supports a maximum of 16 IMA groups with up to 8 links per group. IMA channels on the MPSM-16-T1E1 are individual lines, rather than paths. Therefore, the Line Interface Index is the IMA Link Interface Index for SNMP access.

• The MPSM-16-T1E1 requires that all links in an IMA group be within lines 1-8 or 9-16. For example, an IMA group with lines 7, 8, and 9 is not supported.

• The MPSM-16-T1E1 implements the IMA protocol using the network processor. The MPSM-T3E3-155 implements the IMA protocol using the IMA-84 device.

• The MPSM-T3E3-155 and MPSM-16-T1E1 cards support IMA Versions 1.0 and 1.1.

• SCTs number 54 and 55 provide support for IMA groups with up to 4 lines. You must create your own SCTs for IMA groups with more than 4 lines.

IMA is also supported on the following Cisco MGX 8850 and Cisco MGX 8830 cards:

• PXM1E-16-T1E1 (supports a maximum of 16 IMA groups in the bottom bay only)

• AUSM-8-T1/B (supports a maximum of 8 IMA groups)

• AUSM-8-E1/B (supports a maximum of 8 IMA groups)

• AXSM-32-T1E1-E (supports a maximum of 16 IMA groups in the top bay, and 16 groups in the bottom bay)

Note For information on PXM1E IMA, refer to the Cisco MGX 8850 (PXM1E/PXM45), Cisco MGX 8950, and Cisco MGX 8830 Configuration Guide, Release 5.

Note For information on AUSM IMA, refer to the Cisco AUSM Software Configuration Guide and Command Reference for MGX 8850 (PXM1E) and MGX 8830, Release 5.

Note For information on AXSM IMA, refer to the Cisco ATM Services (AXSM) Software Configuration Guide, Release 5.

Configuring IMA is a 3-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




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

Creating an IMA Group

To create an IMA group, use the following procedure:

Step 1 Establish a configuration session with the active MPSM-T3E3-155 or MPSM-16-T1E1.

Step 2 Enter the addimagrp command as follows to create a new IMA group:

M8830_CH.12.MPSM155[ATM].a > addimagrp <group> <version> <minLinks> <txImaId> <txFrameLen> <txclkMode> <diffDelayMax>

Table 3-3 describes the parameters for the addimagrp command.

Table 3-3 addimagrp Command Parameters


group The IMA group number.

• MPSM-T3E3-155 range: 1–42


version The version number of ATM Forum IMA specification.

• 1 = Version 1.0

• 2 = Version 1.1

minLinks The minimum number of links that must be operational before the IMA group is operational.



For example, if you create an IMA group of 4 links and specify a minimum number of 3 links, then three of the four specified links must be operational before the IMA group can be used.

txImaId The IMA ID number transmitted in the IMA ID field of the ICP cell, in the range 0–255.

txFrameLen The length of transmitted IMA frame in bytes. For IMA version 1.0, the txImaFrameLength value is 128. For Version 1.1, the txImaFrameLength value can be 32, 64, 128, or 256.




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

M8830_CH.12.MPSM155[ATM].a > addimagrp 1 1 3 255 128 1 100

Step 3 To configure additional IMA group parameters, enter the cnfimagrp command as follows:

M8830_CH.12.MPSM155[ATM].a > cnfimagrp <-grp group> [-ver <version>] [-txm <minLinks>] [-txid <txImaId>] [-txfl <txFrameLen>] [-dd <diffDelayMax>] [-uptim groupUpTime] [-dntim <groupDownTime>] [-vfb <verFallback> [-mode <autoRestart>] [-rxid <rxImaIdExpected>] [-cm <txclkMode>]

Table 3-4 describes the parameters for the addimagrp command.

txclkMode Specifies the near-end transmit clock mode. Enter a number to indicate the transmit clock mode as follows:

• 1 = CTC

• 2 = ITC

Note Option 2 (ITC) is not supported in MPSM-T3E3-155 Release 5.

diffDelayMax The maximum differential delay in milliseconds.

• T1 range: 1–275 ms

• E1 range: 1–220 ms

Table 3-3 addimagrp Command Parameters


Table 3-4 cnfimagrp Command Parameters


-grp Specifies the IMA group.



Note Enter the dspimagrps command to see a list of all IMA groups on the current card.

-ver Version number of ATM Forum IMA specification.

• 1 = Version 1.0

• 2 = Version 1.1

-txm Minimum number of links that must be operational before the IMA group is operational.



For example, if you create an IMA group of 4 links and specify a minimum number of 3 links, then three of the four specified links must be operational before the IMA group can be used.

-txid IMA ID number transmitted in the IMA ID field of the ICP cell, in the range 0–255.




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

M8830_CH.12.MPSM155[ATM].a > dspimagrpsIma Min Tx Rx Tx Diff NE-IMA FE-IMA IMAGrp Lnks Frm Frm Clk Delay State State Ver Len Len Mode (ms)-------------------------------------------------------------------------------- 1 3 128 128 CTC 100 StartUp StartUp 1.0

Adding an IMA Link to an IMA Group

After you have created and configured an IMA group, you can begin adding IMA links to the group.

To add an IMA link to an IMA group, perform the following steps:

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

M8850_NY.13.MPSM155[ATM].a > dspimagrpsIma Min Tx Rx Tx Diff NE-IMA FE-IMA IMA

-txfl Length of transmitted IMA frame in bytes. For IMA version 1.0, the txImaFrameLength value is 128. For version 1.1, the txImaFrameLength value can be 32, 64, 128, or 256.

-dd Maximum differential delay in milliseconds.

• T1 range: 1–275 ms

• E1 range: 1–220 ms

-uptim Group uptime, in the range 0–400000 milliseconds. Default: 10000.

-dntim Group downtime, in the range 0–100000 milliseconds. Default: 2500.

-vfb Enables or disables version fallback on the IMA group.

• 1 = Enable version fallback

• 2 = Disable version fallback

Note You must enable version fallback on the card level before you enable it for individual IMA groups. See cnfimaparms -fallback.

-mode Configures IMA autorestart functionality for the current group.

• 1 = Disable IMA auto-restart

• 2 = Relearn IMA auto-restart

• 3 = Resume a previous IMA auto-restart

Note You must enable auto-restart on the card level before you enable it for individual IMA groups. See cnfimaparms -restart.

-rxid Identifies the expected received IMA ID, either -1 or in the range 1–255.

-cm Sets the transmit clock mode.

Note Applies to MPSM-16-T1E1 only.

Table 3-4 cnfimagrp Command Parameters





Grp Lnks Frm Frm Clk Delay State State Ver Len Len Mode (ms)-------------------------------------------------------------------------------- 1 1 128 128 CTC 150 StartUp StartUp 1.1 2 1 128 128 CTC 150 StartUp StartUp 1.1

Step 2 Bring up the MPSM-16-T1E1 line, or MPSM-T3E3-155 path that you want to add to the IMA group.

• MPSM-T3E3-155—Enter the uppath [-path_filter] <path_num> command, replacing [-path_filter] with the type of path you want to bring up (for example, -ds1). Replace <path_num> with the number of the path you want to bring up.

• MPSM-16-T1E1—Enter the upln <bay.line> command, replacing <bay.line> with the line number.

Note To view all lines or paths, enter the dsplns or dsppaths -all command, respectively.

Step 3 Enter the addimalnk command as follows to add an link to an IMA group.

M8830_CH.12.MPSM155[ATM].a > addimalnk <link> <group>

Table 3-5 describes the parameters for the addimalnk command.

In the following example, the user adds the DS1 path 1.1.3:1.1 to IMA group 1.

M8850_NY.13.MPSM155[ATM].a > addimalnk 1.1.3:1.1 1

Table 3-5 addimalnk Command Parameters


link Identifies the line or path to add to the IMA group:

• DS1/E1 or DS3/E3 line: bay.line[:ds1/e1]

• DS3 payload: bay.line.sts:ds1

• VT payload: bay.line.sts:vtg.vt

• VT structured: bay.line.sts:tug3.vtg.vt

where: bay = 1, line = 1–3, sts = 0-3, ds1 = 1–28, tug3 = 1–3, vtg = 1-7, vt = 1–4 (VT15) or 1–3 (VT2)

Note The MPSM-16-T1E1 requires all links in an IMA Group be within lines 1-8 or 9-16. For example, an IMA Group with lines 7, 8, and 9 is not valid.

group Specifies the IMA group number.



Note Enter the dspimagrps command to see the all active IMA groups on the current card. You must be in the ATM service context to view or configure IMA groups.




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

M8850_NY.13.MPSM155[ATM].a > cnfimalnk -lnk <link> [-uplif <lifUpTime>] [-dnlif <lifDnTime>] [-uplods <lodsUpTime>] [-dnlods <lodsDnTime>]

Table 3-6 describes the parameters for the cnfimalnk command.

In the following example, the user configures link 1.1.3:1.1 so that it has an LIF uptime of 25,000 milliseconds, an LIF downtime of 1000 milliseconds, an LODS integration uptime of 25,000 milliseconds, and an LODS integration downtime of 1000 milliseconds.

M8850_NY.13.MPSM155[ATM].a > cnfimalnk -lnk 1.1.3:1.1 -uplif 25000 -dnlif 1000 -uplods 25000 -dnlods 1000

Table 3-6 cnfimalnk Command Parameters


-lnk The link (line or path) in the IMA group to configure:

• DS1/E1 or DS3/E3 line: bay.line[:ds1/e1]

• DS3 payload: bay.line.sts:ds1

• VT payload: bay.line.sts:vtg.vt

• VT structured: bay.line.sts:tug3.vtg.vt

where: bay = 1, line = 1–3, sts = 0–3, ds1 = 1–28,tug3 = 1–3, vtg = 1–7, vt = 1–4 (VT15) or 1–3 (VT2)

Note The MPSM-16-T1E1 requires all links in an IMA group to be within the range 1–8 or 9–16. For example, an IMA group with lines 7, 8, and 9 is not valid.

Note Enter the dsplns or dsppaths command to see a list of all line or path numbers on the current card.

-uplif LIF integration uptime, in the 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 LIF integration downtime, in the 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 LODS integration uptime, in the 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 LODS integration downtime, in the 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.




Step 5 Enter the dspimalnk <link/pathid> command to verify the configuration of the new IMA link. Replace <link/pathid> with the number of the line or path to display.

In the following example, the user displays the IMA link 1.1.3:1.1.

M8850_NY.13.MPSM155[ATM].a > dspimalnk 1.1.3:1.1 IMA Link Number : 1.1.3:1.1 IMA Link Group Number : 1 Link Rel Delay (msecs) : 0 Link NE Tx State : Unusable-Failed Link NE Rx State : Not In Grp Link FE Tx State : Not In Grp Link FE Rx State : Not In Grp Link NE Rx Failure Status : Link Fail Link FE Rx Failure Status : No Failure IMA Link Tx LID : 0 IMA Link Rx LID : 255 Link Rx Test Pattern : 255 Link Test Procedure Status : Disabled Link LIF Integ UpTime : 25000 Link LIF Integ DownTime : 1000 Link LODS Integ UpTime : 25000 Link LODS Integ DownTime : 1000

Adding an IMA Port

After you configure an IMA group, you must add a port to the group.

To add an IMA port to a group, perform the following steps:


Step 2 Obtain 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 IMA port number you want to use is not already configured. To display a list of the ports configured, enter the dspports command as follows:

M8850_NY.13.MPSM155[ATM].a > dspportsifNum Line/ Admin Oper Guaranteed Maximum sctID ifType VPI MINVPI MAXVPI IMA Path State State Rate Rate Cnf/InUse (VNNI, (EVUNI, (EVUNI, GRP VUNI) EVNNI) EVNNI)----- ----------- ----- ---------- ---------- -------- ----------- ------ ------ ------- ------- --- 5 1.1.3:1.2 Up LowLayerDn 100 100 0/ 0 =Def NNI 0 0 0 N/A 6 1.1.3:1.3 Up LowLayerDn 100 100 0/ 0 =Def NNI 0 0 0 N/A 7 1.1.3:1.4 Up LowLayerDn 100 100 0/ 0 =Def NNI 0 0 0 N/A

This command displays all ports on the card in the ifNum (interface number) column. When you add a port, you must specify a port number that is unique on the card. For example, if port number 5 is assigned to path 1.1.3:1.2, you cannot use port 5 on any other line on that card.

Note Cisco MGX switches support one port per IMA group only.

Step 4 To add an ATM port to a group, enter the addimaport command as follows:

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




Table 3-7 lists parameters for adding IMA ports.

Table 3-7 addmaport Command Parameters


ifNum Specifies an interface number (port number) for the port you are adding.


• MPSM-T3E3-155 range: 4–1003

Note Port numbers 1 through 3 are reserved for broadband Frame Relay ports.

group Number of the IMA group to which you want to add an IMA port.

Note Enter the dspimagrps command to see the all active IMA groups on the current card.

guaranteedRate Guaranteed minimum bandwidth rate in cells per second.

Range for T1: 50 to N * (3622 * (M-1)/M * 2048/2049)

Range for E1: 50 to N * (4528 * (M-1)/M * 2048/2049)

N = Number of IMA links in the IMA groupM = IMA group frame length

Note The guaranteed rate and max rate settings must be the same.

maxRate Maximum bandwidth rate for the IMA port in cells per second. See guaranteedRate.

Note The guaranteed rate and max rate settings must be the same.

sctID ID number of the port SCT file on the PXM disk, in the range from 0–255.

For IMA, use SCT 54 (policing) or SCT 55 (non-policing).

Defaul:0.

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 permit a range of VPIs for one interface, and this range of VPIs represents the virtual NNI or virtual UNI trunk. VNNI and VUNI allow 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 Virtual Path Identifier for a VNNI or VUNI interface:

• VNNI range: 1–4095

• VUNI range: 1–255




In the following example, the user adds IMA port 8 to IMA group 1. The port operates as an NNI and uses the default SCT, with a guaranteed minimum and maximum bandwidth rate of 100 cps.

M8850_NY.13.MPSM155[ATM].a > addimaport 8 1 100 100 0 2

Step 5 To display a list of all ports configured on the 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, enter the dspport <ifNum> command, replacing ifNum with the desired port number.

M8850_NY.13.MPSM155[ATM].a > dspportsifNum Line/ Admin Oper Guaranteed Maximum sctID ifType VPI MINVPI MAXVPI IMA Path State State Rate Rate Cnf/InUse (VNNI, (EVUNI, (EVUNI, GRP VUNI) EVNNI) EVNNI)----- ----------- ----- ---------- ---------- -------- ----------- ------ ------ ------- ------- --- 5 1.1.3:1.2 Up LowLayerDn 100 100 0/ 0 =Def NNI 0 0 0 N/A 6 1.1.3:1.3 Up LowLayerDn 100 100 0/ 0 =Def NNI 0 0 0 N/A 7 1.1.3:1.4 Up LowLayerDn 100 100 0/ 0 =Def NNI 0 0 0 N/A 8 N/A Up LowLayerDn 100 100 0/ 0 =Def NNI 0 0 0 1

Partitioning Port Resources on the PNNI ControllerAfter you add a line or trunk port, you must define how the port resources are used by the PNNI controller. You can assign all resources to the PNNI controller, or you can assign some of the port resources to the PNNI controller, including:

• Range of VPI values

• Range of VCI values

• Guaranteed percent of bandwidth for ingress and egress directions

• Minimum and maximum number of connections

Note 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, 2 or 3 very busy ports could use all available connections and disable communication on all other ports.

-minvpi The minimum VPI for an EVUNI or EVNNI interface:



-maxvpi The maximum VPI for an EVUNI or EVNNI interface:



Table 3-7 addmaport Command Parameters (continued)





The port resources are defined as a group in a controller partition, which is dedicated to one 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 3-2 presents a simplified view of the relationship between the port controller, controller partition, and resource partitions.

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

Figure 3-2 shows that one controller partition connects to the port controller and to the resource partitions. When you add a port, a partition is automatically added. You can change the resource partition configuration using the cnfpart command.

To create additional resource partitions for a port, use the addpart command. 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 MPSM-T3E3-155 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).

Important VPI/VCI Range Issues

When you configure a partition, be sure to configure the VPI/VCI ranges to meet your usage requirements. It is important that you do not configure the entire VPI/VCI range for one partition. The ability to seamlessly add new partitions in the future depends on configuring only the necessary ranges for each partition.

We recommend the following ranges for one partition:

• For a VPI on a UNI port where the available range is 0 to 255, the recommended configured range is 0 to 140.

• For a VPI on a PNNI port where the range is 0 to 4096, the recommended configured range is 0 to 2500 or about 60 percent.

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

4293

9

Controller partition(partition ID)

Resource partition port 1(interface numberand partition ID)

MPSM-T3E3-155 card

PXM card

Resource partition port 2(interface numberand partition ID)

Resource partitions foradditional ports

Port controller(controller ID)





Note Before you create a resource partition for a port, you must add the PNNI controller and add a port. For instructions on adding the controller, refer to the Cisco MGX 8850 (PXM1E/PXM45), Cisco MGX 8950, and Cisco MGX 8830 Configuration Guide, Release 5. For instructions on adding ports, see the “Adding ATM Ports” section on page 3-18.

Step 2 Determine the port number whose resource partition you want to configure. To display a list of the ports, enter the dspports command:

M8850_NY.13.MPSM155[ATM].a > dspportsifNum Line/ Admin Oper Guaranteed Maximum sctID ifType VPI MINVPI MAXVPI IMA Path State State Rate Rate Cnf/InUse (VNNI, (EVUNI, (EVUNI, GRP VUNI) EVNNI) EVNNI)----- ----------- ----- ---------- ---------- -------- ----------- ------ ------ ------- ------- --- 10 N/A Up LowLayerDn 1000 1000 0/ 0 =Def NNI 0 0 0 1 11 N/A Up LowLayerDn 1000 1000 0/ 0 =Def NNI 0 0 0 2 20 1.2:1 Up LowLayerDn 1000 1000 0/ 0 =Def UNI 0 0 0 N/A 21 1.2:2 Up LowLayerDn 3622 3622 0/ 0 =Def UNI 0 0 0 N/A

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

Step 3 To configure a resource partition, enter the cnfpart command as shown in the following example:

M8850_NY.13.MPSM155[ATM].a > cnfpart -if <if> -id <partionID> -emin <egrMinBw> -emax <egrMaxBw> -imin <ingMinBw> -imax <ingMaxBw> -vpmin <minVpi> -vpmax <maxVpi> -vcmin <minVci> -vcmax <maxVci> -mincon <min connections> -maxcon <max connections>

Table 3-8 lists the parameters for configuring resource partitions.

Table 3-8 Parameters for Configuring Resource Partitions with the cnfpart Command


-if Interface number (partition number) of the partition to configure.


• MPSM-T3E3-155 range: 4–1003

Note Use the dspparts command in the ATM CLI context to see all active ATM partitions.

-id Number that identifies the partition, in the range 1–20.

-emin Guaranteed percentage of egress bandwidth. Each unit of egrminbw is 0.0001 percent of the total bandwidth on the port. (An egrMinBw of 1000000 = 100%.) These small increments provide a high level of granularity.

-emax Maximum percentage of egress bandwidth. Each unit of egrmaxbw is 0.0001 percent of the total bandwidth available to the port. (An egrMaxBw of 1000000 = 100%.) The minimum bandwidth must be at least 50 cps.

-imin Guaranteed percentage of the ingress bandwidth. Each unit of ingminbw is 0.0001 percent of the total bandwidth available to a port. (An ingMinBw of 1000000 = 100%.)

-imax Maximum percentage of the ingress bandwidth. Each increment of ingmaxbw is 0.0001 percent of the total bandwidth on the port. (An ingMaxBw of 100000000 = 100%.) The maximum ingress bandwidth must be at least 50 cps.




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

M8850_NY.13.MPSM155[ATM].a > dsppartsif part Ctlr egr egr ingr ingr min max min max min maxNum ID ID GuarBw MaxBw GuarBw MaxBw vpi vpi vci vci conn conn (.0001%)(.0001%)(.0001%)(.0001%)----------------------------------------------------------------------------- 4 4 2 100000 100000 100000 100000 10 110 100 2000 100 500

Step 5 To display the configuration of a specific resource partition, enter the dsppart <ifNum> <partId> command. Replace <ifNum> with the number of interface (or port) whose resource partition you want to display, and replace <partId> with the partition ID number. (See Table 3-8 for a description of the <ifNum> and <partId> parameters.)

M8850_NY.13.MPSM155[ATM].a > dsppart <ifNum> <partId>

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

MGX8850.3.MPSM155[ATM].a > dsppart 4 4 Interface Number : 4 Partition Id : 4 Number of SPVC: 0 Controller Id : 2 Number of SPVP: 0 egr Guaranteed bw(.0001percent): 100000 Number of SVC : 0 egr Maximum bw(.0001percent) : 100000 ing Guaranteed bw(.0001percent): 100000 ing Maximum bw(.0001percent) : 100000 min vpi : 10 max vpi : 110 min vci : 100 max vci : 2000 guaranteed connections : 100

maximum connections : 500

-vpmin Minimum VPI for the partition:

• UNI range 0–255

• NNI or VNNI range: 0–4095

-vpmax Maximum VPI for the partition

• UNI range 0–255

• NNI or VNNI range: 0–4095

The max_vpi cannot be less than the min_vpi.

-vcmin Minimum VCI, in the range from 1–65535

-vcmax Maximum VCI, in the range from 1–65535

The max_vci cannot be less than the min_vci.

-mincon Guaranteed number of connections. Value: 0 only

-maxcon Maximum number of connections, in the range 10–2000.

Table 3-8 Parameters for Configuring Resource Partitions with the cnfpart Command





Selecting the Port Signaling ProtocolAfter you bring up a port, you need to set the signaling protocol to UNI or NNI. Use the following procedure to configure the port signaling protocol for a port.

Step 1 Establish a configuration session with the active PXM using a username with Group1 privileges or higher.

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

MGX8850.7.PXM.a > dsppnports

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

MGX8850.7.PXM.a > dnpnport <portid>

A port is automatically brought up when you add it. Before you can change the port signaling protocol, you must bring down the port. Replace <portid> using the format slot[:bay].line[:ifNum].

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

MGX8850.7.PXM.a > dsppnportsSummary of total connections(p2p=point to point,p2mp=point to multipoint,SpvcD=DAX spvc,SpvcR=Routed spvc)Type #Svcc: #Svpc: #SpvcD: #SpvpD: #SpvcR: #SpvpR: #Total:p2p: 0 0 0 0 0 0 0 p2mp: 0 0 0 0 0 0 0 Total=0 Summary of total configured SPVC endpointsType #SpvcCfg: #SpvpCfg:p2p: 1 0 p2mp: 0 0

Per-port status summary

PortId IF status Admin status ILMI state #Conns

7.35 up up Undefined 0




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

1:1.1:1 down down Disable 0

2:2.2:1 up up Disable 0

Step 5 To select the port signaling protocol, enter the cnfpnportsig command as follows:

M8850_NY.7.PXM.a > cnfpnportsig <portid> [-univer {uni30|uni31|uni40|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.

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 commands at the PXM switch prompt, you must always specify the complete port identification number. When entering commands at the switch prompt, you can enter only the interface number, because the interface number is unique on the card and identifies the slot, bay, and line for the port.

Note When the port is added using the addport command, the selection of UNI or NNI occurs. 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.

M8850_NY.7.PXM.a > cnfpnportsig 1:1.1:1 -nniver pnni10

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

M8850_NY.7.PXM.a > cnfoamsegep <portid>

Replace <portid> using the format slot:bay.line:ifNum.

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

Step 7 To bring up the port you just configured, enter the uppnport command:

M8850_NY.7.PXM.a > uppnport <portid>

Replace <portid> using the format slot:bay.line:ifNum.

Note The bay is always 1.

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 dsppnport command as follows:

M8850_NY.7.PXM.a > dsppnport <portid>

Replace <portid> using the format slot:bay.line:ifNum. The following example shows the report for this command.

M8850_NY.7.PXM.a > dsppnport 1:1.1:1Port: 1:1.1:1 Logical Id: 16848897IF status: up Admin Status: up UCSM: enable Auto-config: enable Addrs-reg: enable IF-side: network IF-type: nni UniType: private version: pnni10 Input filter: 0 Output filter: 0minSvccVpi: 0 maxSvccVpi: 4095minSvccVci: 35 maxSvccVci: 65535




minSvpcVpi: 1 maxSvpcVpi: 4095 #SpvcCfg: #SpvcActive: #SpvpCfg: #SpvpActive:p2p : 0 0 0 0p2mp: 0 0 0 0 #Svcc: #Svpc: Total:p2p : 0 0 0p2mp: 0 0 0 Total : 0

Configuring ILMI on a PortInterim Local Management Interface (ILMI) is a feature you can activate on any ATM port. Activate ILMI on a port to perform 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 a port

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

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

ILMI is enabled by default on all ports, but remains in a down state until ILMI is started.

To start ILMI on a port, you can either:

• Configure and start ILMI using one command—Enter the cnfilmi command, or

• Start ILMI using the default values—Use the upilmi command

The sections that follow describe how to perform the following tasks:

• Configuring ILMI Traps and Signaling, page 3-36

• Configuring ILMI Automatic Configuration, page 3-38

• Configuring ILMI Dynamic Addressing, page 3-39

• Starting ILMI Using Default or Existing Values, page 3-41

Configuring ILMI Traps and Signaling

The default ILMI configuration uses 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 using 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 2 To preview the current ILMI configuration for a port, enter the dspilmis command. The following example shows the dspilmis command report.

M8850_NY.13.MPSM155[ATM].a > dspilmis Sig. rsrc Ilmi Sig Sig Ilmi S:Keepalive T:conPoll K:conPoll




Port Part State Vpi Vci Trap Interval Interval InactiveFactor ---- ---- ---- ---- ---- --- ------------ ---------- ---------- 11 1 On 0 16 On 1 5 4 12 1 Off 0 16 On 1 5 4 13 1 Off 0 16 On 1 5 4

The example above shows that ILMI is enabled on port 11 (ILMI State = On) and is disabled on ports 12 and 13 (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. To view the operational state, enter the dsppnports or dsppnilmi commands.

Step 3 Enter the cnfilmi command as follows to configure ILMI on a specific port.

MGX8850.10.MPSM-155[ATM].a > cnfilmi -if <ifNum> -id <partitionID> -ilmi <ilmiEnable> -vpi <vpi> -vci <vci> -trap <ilmiTrapEnable> -s <keepAliveInt> -t <pollingIntervalT491> -k <pollInctFact>

Table 3-9 lists the parameters for configuring resource partitions.

In the following example, the user enables ILMI on port 12.

M8830_CH.12.MPSM155[ATM].a > cnfilmi -if 12 -id 1 -ilmi 1

Table 3-9 Parameters for Configuring ILMI with the cnfilmi Command


-if Specifies the interface number (port number) for which you want to configure ILMI.


• MPSM-T3E3-155 range: 4–1003

Note To see the interface number and partition id for all active ATM ports, use the dspparts command in the ATM CLI context.

-id Specifies the partition ID, in the range 1–20. (See description of addpart or addrscprtn for information regarding resource partition ID.)

-ilmi Enable or disable ILMI.

• 1 = enable

• 2 = disable

-vpi VPI for the ILMI signaling connection, in the range 0–255.

-vci VPI for the ILMI signaling connection, in the range 0–65535.

-trap Enable or disable ILMI trap.

• 1 = enable

• 2 = disable

-s Keepalive interval, in the range 1–16 seconds.

-t Polling interval timer value for T491, in the range 0–255 seconds.

Note To disable polling on the specified interface, enter 0.

-k Polling inactive factor K, in the range 0–255.




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

Configuring ILMI Automatic Configuration

Using the automatic configuration feature of ILMI Version 4.0, two devices that share a link can 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 VCI supported by both nodes. To use ILMI automatic configuration, the devices at each end of the link must support the ILMI 4.0 feature.

Note If the ILMI automatic configuration feature is enabled at one end and disabled at the other end, a link between two nodes does not operate correctly.

To enable or disable automatic configuration on a port, use the following procedure.


Step 2 To display the automatic configuration status of a port, enter the dsppnport <portid> command at the PXM card. Replace <portid> with the number that identifies the port whose automatic configuration status you want to display, in the format slot.port.

In the following example, the user displays the automatic configuration status of port 1 on the card in slot 12:

M8830_CH.1.PXM.a > dsppnport 12.5

Port: 12.5 Logical ID: 17569797 IF status: down Admin Status: up VSVD Internal Loop: unspecified VSVD External Loop: unspecified 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: 255 minSvccVci: 35 maxSvccVci: 65535 minSvpcVpi: 1 maxSvpcVpi: 4095

P2P Details: (P=Configured Persistent Pep, NP=Non-Persistent Pep, Act=Active) #Spvc-P: #Spvc-NP: #SpvcAct: #Spvp-P: #Spvp-NP: #SpvpAct: 1 0 0 0 0 0 #Svcc: #Svpc: #Ctrl: Total: 0 0 0 0 P2MP Details:

Type <CR> to continue, Q<CR> to stop: DSPPNPORT (P=Persistent, NP=Non-Persistent, Pa = Party, Act=Active)Type #Root: #Leaf: #Party: svcc: 0 0 0 svpc: 0 0 0 #Spvc-P: #Spvc-NP: #SpvcAct: #Spvp-P: #Spvp-NP: #SpvpAct: 0 0 0 0 0 0




#SpvcPa-P:#SpvcPaAct:#SpvpPa-P: #SpvpPaAct: 0 0 0 0

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

Step 3 To enable or disable automatic configuration, bring down the port to be configured with the dnpnport <portid> command, as shown in the following example. Replace <portid> with the ID of the port on which you will enable or disable ILMI, in the format slot.ifnum.

MGX8850.7.PXM.a > dnpnport 12.5

Step 4 Enter the cnfautocnf command as follows to enable or disable the automatic configuration feature on a port:

MGX8850.7.PXM.a > cnfautocnf <portid> <yes | no>

Replace portid with the port address using the format slot.ifnum.

Enter yes to enable automatic configuration or enter no to disable automatic configuration.

Note The default is yes.

In the following example, the user disables the autoconfig feature on port 5 on the card in slot 12:

MGX8850.7.PXM.a > cnfautocnf 12.5 no

Step 5 To bring up the port you configured in Step 4, enter the uppnport <portid> command as shown in the following example. Replace <portid> with the ID of the port you want to activate.

MGX8850.7.PXM.a > uppnport 12.5

Step 6 To verify that the automatic configuration feature is enabled or disabled as specified, enter the dsppnport <portid> command. Replace <portid> with the ID of the port you want to verify.

Configuring ILMI Dynamic Addressing

Dynamic ATM addressing is enabled by default on all ports. After 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 Cisco MGX and SES PNNI Network Planning Guide. If you change the:

• PNNI node prefix—The SPVC prefix and the ILMI prefix remain unchanged.

• SPVC prefix—The ILMI prefix changes 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.




Note The Cisco MGX 8850 and Cisco MGX 8830 switches support up to 255 ILMI prefixes per MPSM-T3E3-155 card, and these prefixes can be assigned to one port or distributed among the ports.

To enable or disable dynamic addressing or assign an ILMI address prefix to a port, perform the following steps.


Step 2 To display the dynamic addressing status of a port, enter the dsppnport <portid> command as shown in the following example. Replace <portid> with the ID of the port you want to display.

M8830_CH.1.PXM.a > dsppnport 12.5Port: 12.5 Logical ID: 17569797 IF status: down Admin Status: up VSVD Internal Loop: unspecified VSVD External Loop: unspecified 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: 255 minSvccVci: 35 maxSvccVci: 65535 minSvpcVpi: 1 maxSvpcVpi: 4095

P2P Details: (P=Configured Persistent Pep, NP=Non-Persistent Pep, Act=Active) #Spvc-P: #Spvc-NP: #SpvcAct: #Spvp-P: #Spvp-NP: #SpvpAct: 1 0 0 0 0 0 #Svcc: #Svpc: #Ctrl: Total: 0 0 0 0 P2MP Details: DSPPNPORT (P=Persistent, NP=Non-Persistent, Pa = Party, Act=Active)Type #Root: #Leaf: #Party: svcc: 0 0 0 svpc: 0 0 0 #Spvc-P: #Spvc-NP: #SpvcAct: #Spvp-P: #Spvp-NP: #SpvpAct: 0 0 0 0 0 0 #SpvcPa-P:#SpvcPaAct:#SpvpPa-P: #SpvpPaAct: 0 0 0 0

The Addrs-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:

MGX8850.7.PXM.a > dspprfx <portid>

Replace <portid> with the port address using the format slot.ifnum. For example:

MGX8850.7.PXM.a > dspprfx 12.5

INFO: No Prefix registered

In the example above, no ILMI prefixes are assigned to the port, so the port uses the prefix configured for the SPVC prefix.




Step 4 To change the dynamic addressing configuration, bring down the port to be configured using the dnpnport <portid> command. Replace <portid> with the ID of the port you want to bring down, in the format slot.ifNum. For example:

MGX8850.7.PXM.a > dnpnport 12.5

Step 5 To enable or disable dynamic address registration, enter the cnfaddrreg command as follows:

MGX8850.7.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 To define an ATM prefix for a port, enter the addprfx command as follows:

MGX8850.7.PXM.a > addprfx <portid> <atm-prefix>

Replace <portid> with the ID of the port on which you are defining an ATM prefix, using the format slot.ifNum.

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 Cisco MGX and SES PNNI Network Planning Guide.

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 To bring up the port you configured, enter the uppnport <portid> command as shown in the following example. Replace <portid> with the ID of the port you want to bring up.

MGX8850.7.PXM.a > uppnport 12.5

Step 8 To verify the proper ATM prefix configuration for a port, enter the dspprfx <portid> command. Replace <portid> with the ID of the port you want to verify, in the format slot.ifNum.

Step 9 To see a dynamically assigned address, enter the dspilmiaddr <port> command. Replace <portid> with the ID of the port whose ILMI address you want to display, in the format slot.ifNum.

Starting ILMI Using Default or Existing Values

The upilmi command starts ILMI on a port with the existing ILMI configuration, which is the default configuration if ILMI was not previously configured for 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 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.




MM8850_NY.13.MPSM155[ATM].a > dsppartsif part Ctlr egr egr ingr ingr min max min max min maxNum ID ID GuarBw MaxBw GuarBw MaxBw vpi vpi vci vci conn conn (.0001%)(.0001%)(.0001%)(.0001%)----------------------------------------------------------------------------- 4 4 2 100000 100000 100000 100000 10 110 100 2000 100 500

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

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

MGX8850.10.MPSM-155[ATM].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:

MGX8850.10.MPSM-155[ATM].a > upilmi 4 1

Step 4 Enter the dspilmis command to display the ILMI status of all of the ports. For example:

MGX8850.1.MPSM-155[ATM].a > dspilmis

Sig. rsrc Ilmi Sig Sig Ilmi S:Keepalive T:conPoll K:conPoll Port Part State Vpi Vci Trap Interval Interval InactiveFactor ---- ---- ---- ---- ---- --- ------------ ---------- ---------- 4 1 On 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 command on the PXM to see the operational state).

Provisioning and Managing SPVCs and SPVPsBefore you can add an SPVC, the following tasks must have been completed:

1. The switch must have a network controller (see the addcontroller command in Cisco MGX 8830, Cisco MGX 8850 (PXM45 and PXM1E), and Cisco MGX 8950 Command Reference, Release 5.

2. A physical line must be active. Use the upln command or the Cisco WAN Manager application.

3. At least one logical port must exist on the active physical line. To create the port, use the addport command or the Cisco WAN Manager application. If necessary, modify the port through cnfport.

4. At least one resource partition must exist on the logical port. A partition is automatically added when you add a port. The resource partition should be associated with the controller added in Step 1. The sections that follows describe the following tasks:

– Configuring Point-to-Point Connections

– Defining Destination Addresses for Static Links




Configuring Point-to-Point Connections

Point-to-point SPVCs and SPVPs are created between two ATM CPE, so you must configure them 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 that 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—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. For this feature to work correctly, the destination endpoint must support single-ended SPVCs.

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

Note SPVC/SPVP termination is not supported on feeder ports and legacy service modules; they terminate on the feeder trunk only.

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 2 Define the slave side of the SPVC or SPVP by entering the addcon command as follows:

M8850_SF.27.MPSM16T1E1[ATM].a > addcon <ifNum> <vpi> <vci> <service type> <mastership>[-casttype <value>] [-slave <NSAP.vpi.vci>] [-lpcr <local PCR>] [-rpcr <remote PCR>] [-lscr <local SCR>] [-rscr <remote SCR>] [-lmbs <local MBS>] [-rmbs <remote MBS>][-lcdv <local maxCDV>] [-rcdv <remote maxCDV>] [-lctd <local maxCTD>] [-rctd <remote maxCTD>] [-lmcr <local MCR>][-rmcr <remote MCR>][-cdvt <local CDVT>] [-cc <OAM CC Cnfg>] [-stat <Stats Cnfg>][-frame <frame discard>] [-mc <maximum cost>][-lputil <local util>] [-rputil <remote util>] [-slavepersflag <slavepers>] [-rtngprio <routingPriority>] [-prefrte <preferredRouteId>] [-intvsvd <internal VSVD config>] [-extvsvd <external VSVD config>][-directrte <directRoute>]




Table 3-10 lists the parameters for adding connections.

Table 3-10 Parameters for Configuring Connections with the addcon Command


ifNum Interface number (port number) of the port to connect.


• MPSM-T3E3-155 range: 1–1003

Note To see the port numbers for all active ATM ports, use the dspports command in the ATM CLI context.

Note When you add an endpoint on an NNI, make sure that PNNI signaling is disabled on the PXM (cnfpnportsig <portid> -nniver none).

vpi Specifies the Virtual Path Identifier.

• VCC UNI range 0–255

• VCC NNI or VNNI range: 0–4095

For a VNNI, specify 1 VPI per port.

vci Specifies the Virtual Connection Identifier (VCI).

• VCC UNI range: 1–4095

• VCC NNI or VNNI range: 1–65535

• VPC: 0 only




service type Specifies the ATM service type:

• 1 = CBR1 (Constant Bit Rate 1)

• 2 = VBR1RT (Variable Bit Rate 1, Real Time)



• 5 = VBR1NRT (Variable Bit Rate 1, Non-Real Time)



• 8 = UBR1 (Unspecified Bit Rate 1)

• 9 = UBR2 (Unspecified Bit Rate 2)

• 10 = ABRSTD (Standard ABR—See cnfabr for VS/VD-specific parameters)



Note CBR2 and CBR3 will be obsoleted in the future. Use CBR1 instead.

Note For ATM-FR interworking, the service mapping is.

FR ATM

highpriority cbr1

rtVBR vbr3rt

rtVBR vbr3nrt

uBR ubr

stdABR stdabr

mastership Defines the endpoint as master or slave:

• 1 = master

• 2 = slave

-casttype The broadcast type is either point-to-point or point-to-multipoint, as follows:

• 0 for point-to-point (P2P)

• 1 for point-to-multipoint. P2MP connections are single-ended, so you add only the master endpoint. Thereafter, you can add parties using the addparty command.

Note Option 1 (P2MP) is not supported on Release 5 of the MPSM-T3E3-155.

Default: point-to-point (0)

Table 3-10 Parameters for Configuring Connections with the addcon Command (continued)





-slave Specifies the slave-end connection identifier for the master endpoint. You get the slave-end connection ID at the slave-end node when you add that endpoint. Specify the slave in the following format:

slave_nsap_address.vpi.vci

Note This parameter is required when you configure a master endpoint (mastership=1).

-lpcr Specifies the Peak Cell Rate for this connection in the local to remote direction. The PCR of the local and remote endpoints must match to successfully create a connection.

• MPSM-T3E3-155 range: 10–104268 cps

• MPSM-16-T1E1 range: 10–36064 cps

-rpcr Specifies the Peak Cell Rate for this connection in the remote to local direction. The PCR of the local and remote endpoints must match to successfully create a connection.

• MPSM-T3E3-155 range: 10–104268 cps


-lscr Specifies the Sustainable Cell Rate for this connection in the local to remote direction. The SCR of the local and remote endpoints must match for variable bit rate connections.

• MPSM-T3E3-155 range: 10–104268 cps


-rscr Specifies the Sustainable Cell Rate for this connection in the remote to local direction. The SCR of the local and remote endpoints must match for variable bit rate connections.

• MPSM-T3E3-155 range: 10–104268 cps


-lmbs Specifies the Maximum Burst Size for variable bit rate connections in the local to remote direction. MBS is the maximum number of cells that can burst at the PCR and still be compliant. Range: 0–5000000 cells

-rmbs Specifies the Maximum Burst Size for variable bit rate connections in the remote to local direction. MBS is the maximum number of cells that can burst at the PCR and still be compliant. Range: 0–5000000 cells

-lcdv Specifies the Local Cell Delay Variation, which limits the peak to peak cell delay variation from the local endpoint to the remote endpoint, in the range 1–16777215 microseconds.

-rcdv Specifies the Remote Cell Delay Variation, which limits the peak to peak cell delay variation from the remote endpoint to the local endpoint, in the range 1–16777215 microseconds.

Default: –1

-lctd Specifies the Local Cell Transfer Delay (CTD), which limits the CTD from a local endpoint to a remote endpoint, in the ranges 0–65535 microseconds.






-rctd Specifies the Remote Cell Transfer Delay (CTD), which limits the CTD from the remote endpoint to the local endpoint, in the range 0–65535 microseconds.

Default: –1

-lmcr Specifies the Minimum Cell Rate for available bit rate connections in the local to remote direction.

• MPSM-T3E3-155 range: 10–104268 cps


-rmcr Specifies the Minimum Cell Rate for available bit rate connections in the remote to local direction.

• MPSM-T3E3-155 range: 10–104268 cps


-cdvt Specifies the Local Cell Delay Variation Tolerance (CDVT) from a local endpoint to a remote endpoint, in the range 1–5000000 microseconds. Cell Delay Variation Tolerance controls the time scale over which the PCR is policed.

Note No remote CDVT is necessary.

-cc Enables or disables the Operations, Administration, and Maintenance continuity check (OAM CC):

• 1 = enable

• 0 = disable (default)

Continuity checking invokes a round trip of an OAM cell simply to confirm that both directions of the connection are intact.

To provision continuity checking, enable this function at both ends of the connection; otherwise, a connection alarm results. When you add a connection and include this parameter, the connection goes into alarm until both ends of the connection are added.

Note A nonzero AIS delay timer affects CC functionality (if enabled) during the intentional rerouting of a connection following the optrte or cnfrteopt command at the PXM card. The cnfaisdelaytimer command at the PXM card controls the AIS-delay feature. If the delay timer is configured and the connection is groomed, the switch turns off CC until the connection is rerouted.






-stat Enables or disables connection statistics collection for the Cisco WAN Manager tool:

• 1 = enable


Note Statistics collection has an impact, which may not be significant, on the real-time response, especially for SVCs (which can be affected even though you do not add SVCs). Therefore, you should enable statistics collection for only the subset of connections that really warrant such a feature.

-frame Enables or disables frame discard for this connection. You can use this option only at the master endpoint of a connection.

• 1 = enable


-mc<maxCost>

The maximum cost (maxcost) creates a routing priority. (PNNI does not use a route if the cost for the route exceeds the maxcost.) If you do not specify this optional parameter, the connection defaults to having the highest routing priority. Therefore, the maxcost parameter lets you lower the priority of a connection—but only in regards to finding a route for it. The range for maxcost is 0–4294967295, and the default is 4294967295.

The cost of a route (not the maxcost of the connection) depends on a cost-per-link specified through the cnfpnni-intf command. The cost-per-link applies at the egress of a port for all connections of a particular service type. For example, the cost-per-link is the same for all VBR.1 connections that PNNI controls on a given port, but this cost can differ from all UBR.1 connections on the same port.

For a route under consideration, the cost is the sum of all of the costs-per-link at each egress in the forward and backward directions along the entire route. In a 1-link route, for example, the cost is the sum of the cost-per-links at two ports.

To illustrate further, with a 4-link route:

1. Specify a maxcost of 100000.

2. A route under consideration by PNNI has 4 links for a total of 8 egress points.

3. The cost-per-link at 6 of the ports is 5040 (the default in cnfpnni-intf), and the cost per link at two ports is 10000.

The node would use the route because the resulting cost of 50240 is less than the maxcost of 100000.

Default: 4294967295

Note To return maxcost to the default, type -mc 4294967295. Setting maxcost to this value makes maxcost meaningless and causes PNNI to ignore this metric when making routing decisions.






-lputil Specifies the Local Percentage Utilization, in the range 1–100 percent.

Default: 100 percent

-rputil Specifies the Remote Percentage Utilization, in the range 1–100 percent. Default: 100 percent.

-slavepersflag<slavepers>

The slave endpoint persistency flag is necessary for setting up a single-ended connection.

• 0 = persistent.

• 1 = for nonpersistent.

Default: 0 (persistent)

-rtngprio The routing priority for the connection, in the range 1–15. 0 is reserved for control connections, and 1 is reserved for IP to CWM.

Default: 8

-prefrte This option associates a preferred route to the connection. Use this parameter at the master endpoint only. Before you associate it with the connection, be sure the route exists because the system does not check it. To display preferred routes, use the dspprefs command at the PXM card.

The following values are valid:

• 0: Disassociate a connection from a route (default)

• 1-65535: The preferred route id

Note Before you delete the route, disassociate all connections from the route; otherwise, a dangling preferred route path remains. To display all connections associated with a route, use the dspcons [-rteid <pref rte id> ] command at the PXM card.

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.

-intvsvd Enables or disables VS/VD on the internal loop:

• 1 = Off (default)

• 2 = On

• 3 = Unspecified: Use the VS/VD specification in the SCT file.

The cnfintfvsvd command enables VS/VD at the PNNI port level.






Caution After you create an SPVC connection, you cannot change the SPVC prefix until all SPVC connections are deleted. The procedure for changing the SPVC prefix is described in the Cisco MGX 8850 (PXM1E/PXM45), Cisco MGX 8950, and Cisco MGX 8830 Configuration Guide, Release 5.

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

M8850_SF.27.MPSM16T1E1[ATM].a > addcon 15 10 40 1 2slave endpoint added successfully

Step 3 To verify that the SPVC or SPVP was associated with the preferred route, enter the dspcon <portid> <vpi> <vci> command. Replace <portid> with the port ID associated with the connection. Replace <vpi> and <vci> with the VPI and VCI of the connection.

Tip The PCR, MBS, CDVT, CDV, MCR, and CTD configuration options are optional. To override the default values for any option, enter the option with a new value.

Note You can configure additional ABR parameters using the cnfabr command. For more information, refer to the Cisco MGX 8830, Cisco MGX 8850 (PXM45 and PXM1E), and Cisco MGX 8950 Command Reference, Release 5.

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

-extvsvd Enables or disables VS/VD on the external loop:

• 1 = Off (default)

• 2 = On

• 3 = Unspecified: Use the VS/VD specification in the SCT file.

The cnfintfvsvd command enables VS/VD at the PNNI port level.

-directrte Enables or disables a direct route for this connection. When enabled (yes), the preferred route is the only permissible route for this connection. Should the directed preferred route be unavailable, the connection fails. When disabled (no), the connection tries another alternate route if the preferred route is unavailable.

The values are as follows:

• 1 = yes (make the preferred route required)

• 0 = no (do not require the connection to take the preferred route)

Default: 0






Tip When you set up the master side of the connection, you must 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 5 Verify the slave-side SPVC addition by entering the dspcons command as follows:

M8850_SF.27.MPSM16T1E1[ATM].a > dspcons

The switch displays the slave connection just added:

M8850_SF.27.MPSM16T1E1[ATM].a > dspconsrecord Identifier Type SrvcType M/S Upld Admn Alarm------ ---------- ---- -------- --- ---- ---- ----- 0 15 0010 00040 VCC cbr1 S 00000032 UP Condn

Configuring the Master Side of SPVCs and SPVPs

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


Tip During this procedure, you must 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 cc command to select the card that hosts the master side of the SPVC:

MGX8850.7.PXM.a > cc <slotnumber>

Replace <slotnumber> with the slot number of card that hosts the master side of the SPVC.

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

M8850_SF.27.MPSM16T1E1[ATM].a > addcon <ifNum> <vpi> <vci> <service type> <mastership>[-casttype <value>] [-slave <NSAP.vpi.vci>] [-lpcr <local PCR>] [-rpcr <remote PCR>] [-lscr <local SCR>] [-rscr <remote SCR>] [-lmbs <local MBS>] [-rmbs <remote MBS>][-lcdv <local maxCDV>] [-rcdv <remote maxCDV>] [-lctd <local maxCTD>] [-rctd <remote maxCTD>] [-lmcr <local MCR>][-rmcr <remote MCR>][-cdvt <local CDVT>] [-cc <OAM CC Cnfg>] [-stat <Stats Cnfg>][-frame <frame discard>] [-mc <maximum cost>][-lputil <local util>] [-rputil <remote util>] [-slavepersflag <slavepers>] [-rtngprio <routingPriority>] [-prefrte <preferredRouteId>] [-intvsvd <internal VSVD config>] [-extvsvd <external VSVD config>][-directrte <directRoute>]

Note Table 3-10 in the previous section lists the parameters for configuring connections.




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

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. To override the default values for any option, enter the option with a new value.

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

M8850_SF.27.MPSM16T1E1[ATM].a > addcon 113 101 201 1 1 -slave 47009181000000000164444B610000011B180F00.10.40 master endpoint added successfullymaster endpoint id : 47009181000000000164444B610000011B187100.101.201

Step 4 Verify the master-side SPVC addition by entering the dspcons command as follows:

M8850_NY.13.MPSM155[ATM].a > dspcons

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

M8850_SF.27.MPSM16T1E1[ATM].a > dspconsrecord Identifier Type SrvcType M/S Upld Admn Alarm------ ---------- ---- -------- --- ---- ---- ----- 0 15 0010 00040 VCC cbr1 S 00000032 UP none 1 113 0101 00201 VCC cbr1 M 00000033 UP none

Step 5 To display the configuration for one connection, enter the dspcon command as follows:

M8850_NY.13.MPSM155[ATM].a > dspcon <ifNum> <vpi> <vci>

Replace the <ifNum> parameter with the interface or port number. Replace <vpi> and <vci> with the VPI and VCI for the connection.

The following example shows a dspcon command report.

M8850_SF.27.MPSM16T1E1[ATM].a > dspcon 113 101 201--------------------------------------------------------------------------Local : NSAP Address vpi vci (M) 47009181000000000164444B610000011B187100 101 201 Remote : NSAP Address vpi vci (S) 47009181000000000164444B610000011B180F00 10 40 --------------------------------------------------------------------------Conn. Type : VCC Admn Status : ADMN-UPService Type : cbr1 Oper Status : OKController : 2 Record # : 1SlavePersist : YES Cast-type : P2P--------------------------------------------------------------------------Local PCR : 50 Remote PCR : 50 Local SCR : N/A Remote SCR : N/A Local CDV : -1 Remote CDV : -1 Local CTD : -1 Remote CTD : -1 Local MBS : N/A Remote MBS : N/A Max Cost : -1 Frame discard: DISABLED Local CDVT : 250000 OAM segment : ENABLEDLocal PctUtil : 100 Rmt PctUtil : 100 Priority : 8 Pref Rte Id : 0 Directed route: NO--------------------------------------------------------------------------

Type <CR> to continue, Q<CR> to stop: OAM CC Config : DISABLED Statistics : ENABLED--------------------------------------------------------------------------




Loopback Type : No Lpbk | Dir: N/A | Status: No Lpbk | RTD: 0us --------------------------------------------------------------------------

--------------------------------------------------------------------------Port side Tx : normal Swth side Tx : normalPort side Rx : normal Swth side Rx : normal--------------------------------------------------------------------------I-AIS/RDI E-AIS/RDI CONDITIONED CCFAIL IfFail Mismatch LMI-ABIT NO NO NO NO NO NO NO --------------------------------------------------------------------------

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.

Step 6 To display connections from the PXM card, enter the cc command to select the active PXM, then enter the dspcons command.

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

M8850_NY.7.PXM.a > dspconsLocal Port Vpi.Vci Remote Port Vpi.Vci State Owner Pri Persistency----------------------+------------------------+---------+-------+---+-----------27.15 10 40 27.113 101 201 OK SLAVE - PersistentLocal Addr: 47.009181000000000164444b61.0000011b180f.00Remote Addr: 47.009181000000000164444b61.0000011b1871.00Preferred Route ID:- Cast Type: P2P27.113 101 201 27.15 10 40 OK MASTER 8 PersistentLocal Addr: 47.009181000000000164444b61.0000011b1871.00Remote Addr: 47.009181000000000164444b61.0000011b180f.00Preferred Route ID:- Cast Type: P2P

Defining Destination Addresses for Static LinksTypically, you use AINI or IISP static links to join two independent networks, rather than PNNI, so that the topologies of the two networks can 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.

Use the following procedure to add destination addresses to a static link.


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

Step 3 Enter the addaddr command as follows to specify an ATM address:

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

Step 4 Enter the dspatmaddr command as follows to verify that the new address is assigned:

MGX8850.7.PXM.a > dspatmaddr <portid>

Replace <portid> with the port address using the format slot:bay.line:ifnum. For example:

MGX8850.7.PXM.a > dspaddr 2:1.2:247.0091.8100.0000.0003.6b5e.30cd.0003.6b5e.30cd.01length: 160 type: exterior proto: staticscope: 0 plan: nsap_icd redistribute: false

Documents

Provisioning ATM Services on MPSM-T3E3-155 and MPSM-16-T1E1 · Part Number OL-6487-01 Rev. B0, March 15, 2005 Chapter 3 Provisioning ATM Services on MPSM-T3E3-155 and MPSM-16-T1E1