-
Cisco ATM and Frame Relay Services (MPSM-T3E3-155 and MPSM-16T1E1) Configuration Guide and Command Reference, Release 5.1
-
About This Guide
-
Introduction
-
Preparing Cards and Lines for Communication
-
Provisioning ATM Services
-
Provisioning Frame Relay Services
-
Provisioning Multilink PPP Services
-
MPSM Card Management
-
MPSM Command Reference (addapsln through cnfimaparms)
-
MPSM Command Reference (cnfln through dspilmis)
-
MPSM Command Reference (dspimagrp through whoami)
-
Table Of Contents
Provisioning ATM Services on MPSM-T3E3-155 and MPSM-16-T1E1
Quickstart Provisioning Procedures
ATM Trunk Configuration Quickstart
PNNI UNI Port Configuration Quickstart
SPVC and SPVP Configuration Quickstart
PNNI Virtual Trunk Configuration Quickstart
Cisco BPX PNNI Trunk Configuration Quickstart
AINI Link Configuration Quickstart
IISP Link Configuration Quickstart
Configuring Inverse Multiplexing over ATM
Adding an IMA Link to an IMA Group
Partitioning Port Resources on the PNNI Controller
Selecting the Port Signaling Protocol
Configuring ILMI Traps and Signaling
Configuring ILMI Automatic Configuration
Configuring ILMI Dynamic Addressing
Starting ILMI Using Default or Existing Values
Provisioning and Managing SPVCs and SPVPs
Configuring Point-to-Point Connections
Defining Destination Addresses for Static Links
Provisioning 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 "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.
The MPSM-T3E3-155 and MPSM-16-T1E1supports ATM SPVCs, SPVPs, and SVCs to the following cards:
•
•
•
•
•
•
•
•
•
•
•
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
Quickstart Provisioning Procedures
This 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 Trunk Configuration Quickstart
ATM trunks connect the switch to other ATM switches in the core ATM network. The quickstart procedure in this section provides a summary of the tasks required to configure ATM trunks on Cisco MGX switches. This procedure is a quick reference for those who have previously configured these types of connections.
Note
Step 1
username
<password>
Start a configuration session.
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 "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.
To configure ATM communication over an IMA group, see the "Configuring Inverse Multiplexing over ATM" section later in this chapter.
Note
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.
Note
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.
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 13
setctx atm
If the current CLI context is Frame Relay, use the setctx atm command to ensure you are using the ATM CLI.
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.
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 Quickstart
ATM 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.
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
upln
Bring up MPSM-T3E3-155 lines as described in the "Preparing MPSM-T3E3-155 and MPSM-16-T1E1 Cards and Lines for Communication."
Step 4
setctx atm
If the current CLI context is Frame Relay, use the setctx atm command to ensure you are using the ATM CLI.
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 UNI for interswitch trunks.
For standard port configuration, see the "Adding ATM Ports" section.
To configure ATM communication over an IMA group, see the "Configuring Inverse Multiplexing over ATM" section later in this chapter.
Note
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.
See the "Partitioning Port Resources on the PNNI Controller" section.
Note
Step 8
cc
Change to the PXM card.
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.
See the "Configuring ILMI on a Port" section.
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.
Step 13
uppnport
Bring up port after configuration is complete.
Step 14
cc
Change back to the appropriate card.
Step 15
setctx atm
If the current CLI context is Frame Relay, use the setctx atm command to ensure you are using the ATM CLI.
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.
See the "Configuring ILMI on a Port" section.
SVC Configuration Quickstart
Switched virtual circuits (SVCs) are the solution for on-demand connections. They are set up as needed and torn down when no longer needed. To enable this dynamic activity, SVCs use signaling. End systems request connectivity to other end systems and, provided that the requested services are available, the connection is set up at the time of the request. When idle, an SVC is taken down to save network bandwidth.
Cisco MGX 8850 (PXM1E/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
Step 1
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
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.
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.
SPVC and SPVP Configuration Quickstart
A soft permanent virtual circuit (SPVC) is a permanent virtual circuit (PVC) that can be rerouted using the Private Network-to-Network Interface (PNNI) Version 1.0 protocol. As with PVCs, SPVCs are full-time connections. 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.
Step 1
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
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 4
cc
Change to the MPSM-T3E3-155 or MPSM-16-T1E1 card.
Step 5
setctx atm
If the current CLI context is Frame Relay, use the setctx atm command to ensure you are using the ATM CLI.
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:
•
•
Note
Step 7
dspcon
Verify the configuration for the connection you added in Step 4.
Step 8
username
<password>
or
cc
If you are configuring an SPVC between:
•
•
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:
•
•
Step 10
dsppncons
This optional step displays the SVC connections that are operating. Enter this command on the active the PXM.
PNNI Virtual Trunk Configuration Quickstart
Virtual 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
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:
•
•
Cisco MGX 8850 (PXM1E/PXM45) and Cisco MGX 8830 switches support:
•
•
The following is a summary of the tasks required to configure virtual trunks on Cisco MGX 8850 (PXM1E/PXM45) and Cisco MGX 8830 switches.
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
upln
Bring up lines as described in the "Preparing MPSM-T3E3-155 and MPSM-16-T1E1 Cards and Lines for Communication."
Step 4
setctx atm
If the current CLI context is Frame Relay, use the setctx atm command to ensure you are using the ATM CLI.
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 "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.
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.
Note
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
Note
See the "Partitioning Port Resources on the PNNI Controller" section.
Step 8
cc
Change to the PXM card.
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.
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.
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
See the "Partitioning Port Resources on the PNNI Controller" section.
Step 14
cc
Change to the PXM card.
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 16
cc
Change to the MPSM-T3E3-155 or MPSM-16-T1E1 card.
Step 17
setctx atm
If the current CLI context is Frame Relay, use the setctx atm command to ensure you are using the ATM CLI.
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.
Step 19
cc
Change to the PXM card.
Step 20
dsppnni-reachable-addr network
Verify PNNI connectivity between the two nodes that will host the virtual trunk end points.
See the "Verifying End-to-End PNNI Communications" section in Chapter 6, "MPSM-T3E3-155 and MPSM-16-T1E1 Card Management."
Cisco BPX PNNI Trunk Configuration Quickstart
When 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
Caution
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
upln
Bring up lines as described in the "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 "Channelizing MPSM-T3E3-155 SONET, SDH, and DS3 (T3) Lines" in "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
Add and configure ATM ports. This step establishes ATM communication between two ATM devices.
Specify NNI for interswitch trunks and VNNI for virtual trunks.
See the "Adding ATM Ports" section.
Step 6
cnfpart
Related commands:
dspparts
dsppart
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
See the "Partitioning Port Resources on the PNNI Controller" section.
Step 7
cc
Change to the PXM card.
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 pnni10Step 9
cc
Change back to the MPSM-T3E3-155 or MPSM-16-T1E1 card.
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.
See the "Configuring ILMI on a Port" section.
Step 11
cc
Change to the PXM card.
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."
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.
AINI Link Configuration Quickstart
The quickstart procedure in this section provides a summary of the tasks required to configure ATM Inter-Network Interface (AINI) links on Cisco MGX switches. This procedure is an overview and acts as a quick reference for those who have previously configured these types of connections.
Note
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
upln
Bring up lines as described in the "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 "Preparing MPSM-T3E3-155 and MPSM-16-T1E1 Cards and Lines for Communication," for details.
Step 4
uppath
Related commands:
dsppath
dsppaths
Bring up the path you configured in Step 3.
Step 5
addport
Related command:
dspports
Add and configure ATM ports. This step establishes ATM communication between two ATM devices.
Specify NNI for interswitch trunks and VNNI for virtual trunks.
See the "Adding ATM Ports" section.
Step 6
cnfpart
Related commands:
dspparts
dsppart
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.
See the "Partitioning Port Resources on the PNNI Controller" section.
Note
Step 7
cc
Change to the PXM card.
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 ainiStep 9
cc
Change back to the MPSM-T3E3-155 or MPSM-16-T1E1 card.
Step 10
addaddr
Add destination addresses to each end of the trunk.
See the "Defining Destination Addresses for Static Links" section.
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.
IISP Link Configuration Quickstart
The quickstart procedure in this section provides a summary of the tasks required to configure Interim Inter-Switch Protocol (IISP) links on Cisco MGX switches. This procedure is provided as an overview and as a quick reference for those who have previously configured these types of connections.
Note
Step 1
username
<password>
Start a configuration session.
To perform all of the steps in this quickstart procedure, you must log in as a user with Group1 privileges or higher.
Step 2
Bring up MPSM-T3E3-155 lines as described in the "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 "Preparing MPSM-T3E3-155 and MPSM-16-T1E1 Cards and Lines for Communication," for details.
Step 4
uppath
Related commands:
dsppath
dsppaths
Bring up the path you configured in Step 3.
Step 5
addport
Related command:
dspports
Add and configure ATM ports. This step establishes ATM communication between two ATM devices.
Specify NNI for interswitch trunks and VNNI for virtual trunks.
See the "Adding ATM Ports" section.
Step 6
cnfpart
Related commands:
dspparts
dsppart
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.
See the "Partitioning Port Resources on the PNNI Controller" section.
Note
Step 7
cc
Change to the PXM card.
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 iisp31Step 9
cc
Change back to the MPSM-T3E3-155 or MPSM-16-T1E1 card.
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.
ATM Configuration Concepts
This section describes the following MPSM-T3E3-155 and MPSM-16-T1E1 ATM configuration concepts and general procedures:
•
•
•
•
•
Most of the descriptions and procedures in this section use ATM service context commands. See "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:
•
•
•
•
Adding ATM Ports
On 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:
•
•
•
•
•
•
Note
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
To add an ATM port to a path or line, use the following procedure.
Step 1
Step 2
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 -allStep 3
M8850_NY.13.MPSM155[ATM].a > dspportsifNum Line/ Admin Oper Guaranteed Maximum sctID ifType VPI MINVPI MAXVPI IMAPath State State Rate Rate Cnf/InUse (VNNI, (EVUNI, (EVUNI, GRPVUNI) EVNNI) EVNNI)----- ----------- ----- ---------- ---------- -------- ----------- ------ ------ ------- ------- ---4 1.1.1 Up LowLayerDn 100 100 0/ 0 =Def NNI 0 0 0 N/AThis 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
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.
