Table Of Contents
Quickstart Provisioning Procedures
MPLS and PNNI Trunk Configuration Quickstart
MPLS and PNNI UNI Port Configuration Quickstart
SPVC and SPVP Configuration Quickstart
PNNI Virtual Trunk Configuration Quickstart
XPVC and XPVP Configuration Quickstart
Cisco IGX Feeder to Cisco MGX 8850 Configuration Quickstart
PXM1 Feeder Configuration Quickstart
Cisco BPX PNNI Trunk Configuration Quickstart
AINI Link Configuration Quickstart
IISP Link Configuration Quickstart
XLMI Link Configuration Quickstart
General AXSM Configuration Procedures
Configuring Inverse Multiplexing over ATM
Adding an IMA Link to an IMA Group
Adding an IMA Port to an IMA Group
Partitioning Port Resources between Controllers
Selecting the Port Signaling Protocol
Assigning Static ATM Addresses to Destination Ports
Configuring ILMI Traps and Signaling
Configuring ILMI Automatic Configuration
Configuring ILMI Dynamic Addressing
Starting ILMI with the Default or Existing Values
Configuring AXSM Line Clock Sources
Defining Destination Addresses for Static Links
Configuring Point-to-Multipoint SPVCs and SPVPs
Obtaining the NSAP for a Party
Provisioning ATM Services
This chapter describes how to configure the AXSM card and provides procedures for adding ATM ports and connections to the physical lines. The types of links and connections presented in this chapter are listed in Table 3-1.
Note
Before you can configure any ATM connections, you must first complete the general switch configuration procedures described in Cisco MGX 8800/8900 Series Configuration Guide, Release 5.2, and you must set up the AXSM cards and lines as described in "Preparing AXSM Lines for Communication."
Table 3-1 AXSM Link and Connection Types
MPLS and PNNI trunks
PNNI trunks connect Cisco MGX switches to other Cisco MGX switches.
MPLS and 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 like a single link.
Extended Permanent Virtual Connections (XPVCs) and Extended Permanent Virtual Paths (XPVPs)
An XPVC/XPVP is basically an SPVC/SPVP that connects a PNNI network to an AutoRoute network. XPVCs and XPVPs span over
AutoRoute-to-PNNI or AutoRoute-to-PNNI-to-AutoRoute hybrid networks.Inverse Multiplexing over ATM (IMA)
Inverse Multiplexing over ATM (IMA) is a protocol that runs on the AXSM-32-T1E1-E. IMA allows you to combine multiple T1 or E1 interfaces into a single, high-speed IMA interface.
Channelized paths
Channelization is possible on AXSM-XG cards. Channelization makes it possible to implement multiple SONET or SDH paths on a single line. It also makes it possible to implement multiple DS3 paths on a single SONET path.
"Channelizing SONET Lines Configuration Quickstart" section
"Channelizing SONET Lines Configuration Quickstart" section
Feeder trunks
Feeder trunks link a feeder switch to a Cisco MGX 8850 (PXM45) switch. The feeder switch concatenates relatively low speed traffic and feeds it over a higher speed interface to the Cisco MGX 8850 switch, which provide the link to the ATM network core. Feeder switches include:
•
•
•
•
"Cisco IGX Feeder to Cisco MGX 8850 Configuration Quickstart" section
Cisco BPX PNNI trunks
Cisco BPX PNNI trunks provide PNNI links between Cisco MGX 8850 (PXM45) and Cisco MGX 8950 and Cisco BPX switches that support PNNI. The Cisco BPX switch supports PNNI when connected to the Cisco SES PNNI Controller.
ATM Inter-Network Interface (AINI) links
AINI links enable connectivity between two independent PNNI networks and block the PNNI database exchange so the two networks remain independent.
Interim Inter-switch Protocol (IISP) links
IISP links enable connectivity between two independent PNNI networks and block the PNNI database exchange so the two networks remain independent. IISP is the predecessor to AINI and should be used only when AINI is not supported on one or both ends of the network link.
Extended Link Management Interface (XLMI) links
XLMI links connect PNNI networks to AutoRoute networks. XLMI links enable the expansion of AutoRoute networks using PNNI, and they facilitate migration from AutoRoute networking to PNNI.
Point-to-Multipoint SPVCs and SPVPs
Point-to-multipoint (P2MP) connections enable a single master endpoint to support several slave endpoints.
Tip
Quickstart Provisioning Procedures
The sections that follow present abbreviated procedures that you can use to configure lines and provision connections. To do the procedures in this section, you must start a CLI session on the appropriate AXSM card by logging in with the appropriate username and password. For detailed information about user names, passwords, and logging into the CLI, refer to the Cisco MGX 8800/8900 Series Configuration Guide, Release 5.2.
Note
MPLS and PNNI Trunk Configuration Quickstart
The following quickstart procedure summarizes how to configure an ATM trunk with MPLS and PNNI partitions. An ATM trunk is a Network-to-Network Interface (NNI) that connects switches in the core of the network.
This procedure must be completed on the switches at both ends of the trunk. After you configure an ATM trunk, the trunk is ready to support SVCs, SPVCs, and SPVPs. (See the "SVC Configuration Quickstart" section or "SPVC and SPVP Configuration Quickstart" section for more details.)
Note
Step 1
username
<password>
Start a configuration session.
To perform all the steps in this quickstart procedure, you must log in as a user with GROUP1 privileges or higher.
Step 2
cc
Change to an AXSM card.
Step 3
Follow the steps in the "Preparing AXSM Lines for Communication" section
Bring up AXSM lines.
Step 4
addport
or
addimagrp
addimalnk
addimaport
Related commands:
dspports
or
dspimagrp
dspimagrps
dspimalnk
dspimalnks
dspimaport
dspimaports
Add and configure ATM ports. This step establishes ATM communications between two ATM devices.
Specify NNI for interswitch trunks.
For standard port configuration, see the "Adding ATM Ports" section.
To configure ATM communications over an IMA group, see the "Configuring Inverse Multiplexing over ATM" section.
Step 5
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.
Step 6
cnfpart
Related commands:
dspparts
dsppart
Configure trunk resources to PNNI and MPLS controllers. This step can assign all the trunk bandwidth to one controller, or it can assign portions of the trunk bandwidth to each controller.
Note
See the "Partitioning Port Resources between Controllers" section.
Step 7
cc
Change to the PXM card.
Step 8
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.
Note
Step 9
Configure the other end of the link. If the other end of the link is connected to another AXSM 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 10
cc
dsppnni-link
dsppnni-neighbor
When both ends of the link are configured, change to the active PXM card and verify the PNNI communications 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 communications. The Hello state reported should be twoWayInside, and the Remote node ID should display the remote node ATM address after the second colon.
See the "Verifying PNNI Communications" section on page 4-52.
Step 11
cc
Change back to the AXSM card.
Step 12
upilmi
cnfilmi
Related commands:
dspports
dspilmis
This step is optional. Configure and start ILMI on trunks where you want to support Cisco WAN Manager (CWM) or use ILMI features.
See the "Configuring ILMI on a Port" section.
MPLS and PNNI UNI Port Configuration Quickstart
ATM User-to-Network Interface (UNI) ports connect the switch to ATM end devices, which serve as the boundary between the ATM network and other communications paths or networks. Typical end devices include ATM routers and multiservice concentrators. UNI signaling is used between the end system (CPE) and the PNNI network for requesting calls.
The quickstart procedure in this section provides a summary of the tasks required to configure UNI ports on AXSM cards. 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 the steps in this quickstart procedure, you must log in as a user with GROUP1 privileges or higher.
Step 2
cc
Change to the AXSM card.
Step 3
Bring up AXSM lines as described in the "Preparing AXSM Lines for Communication" section
Step 4
addport
or
addimagrp
addimalnk
addimaport
Related commands:
dspports
or
dspimagrp
dspimagrps
dspimalnk
dspimalnks
dspimaport
dspimaports
Add and configure ATM ports. This step establishes ATM communications between two ATM devices.
Specify UNI for ATM lines.
For standard port configuration, see the "Adding ATM Ports" section.
To configure ATM communications over an IMA group, see the "Configuring Inverse Multiplexing over ATM" section.
Step 5
cnfport
Related commands:
dspport
dspports
Use this optional step if you need to make changes to the port created in the previous step.
For more details on modifying ports, see the "Adding ATM Ports" section.
Step 6
cnfpart
Related commands:
dsppart
dspparts
Configure the trunk resources that are assigned to the PNNI and MPLS controllers. This step can assign all the line bandwidth to one controller, or it can assign portions of the line bandwidth to each controller.
Note
See the "Partitioning Port Resources between Controllers" section.
Step 7
cc
Change to the PXM card.
Step 8
dnpnport <portid>
Bring down the port so it can be configured.
Note
Step 9
cnfpnportsig
Related commands:
dsppnports
dsppnport
dsppnportsig
Define the signaling protocol used on the line.
Specify uni30, uni31, or uni40.
Step 10
cnfaddrreg
addaddr
Related commands:
dsppnports
dspatmaddr
deladdr
Configure static ATM addresses for ports that require them.
See the "Assigning Static ATM Addresses to Destination Ports" section.
Step 11
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 12
uppnport
Bring up the port after configuration is complete.
Step 13
cc
Change back to the AXSM card.
Step 14
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 (PXM45) and Cisco MGX 8950 can use the PNNI protocol to determine how to set up SVCs through the network. Because the switch automatically sets up SVCs, you do not have to configure SVC routes. However, the switch must be configured correctly before it can set up SVCs.
The following quickstart procedure summarizes the tasks required to enable SVC communications. With the exception of CPE configuration, all these tasks are described in this chapter.
Note
Step 1
Follow the steps in the "MPLS and PNNI Trunk Configuration Quickstart" section.
Configure the trunks that link the switches through which the ATM end stations connect. Be sure to add the appropriate controller (either PNNI or MPLS) on each switch and select that controller when partitioning trunks.
Step 2
dsppnni-reachable-addr network
On the PXM, verify connectivity between the node pairs that will host SVCs.
See the "Verifying PNNI Communications" section on page 4-52.
Step 3
Follow the steps in the "MPLS and PNNI UNI Port Configuration Quickstart" section.
Configure UNI ports for the ATM end stations at each end of the SVC, and assign either static or dynamic addressing to each line. Be sure to add the appropriate controller (either PNNI or MPLS) on each switch and select that controller when partitioning trunks.
Step 4
See the CPE documentation.
Configure CPE devices for communications with the switch through the UNI ports configured in the previous step.
Step 5
dsppncons
This optional step displays the SVC connections that are operating. Enter the dsppncons command on the active 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 will need to learn the capabilities of the CPE and the switch and define a set of communications parameters that are supported by both devices. For example, the Cisco MGX 8850 (PXM45) switches support UNI 3.1 communications, but if the CPE does not, you must select a signaling protocol (such as UNI 3.0) that is supported by both devices.
After all requirements have been met for SVC connections, CPE devices can establish SVC connections to other CPE devices on the same switched network.
SPVC and SPVP Configuration Quickstart
A soft permanent virtual circuit (SPVC) is a permanent virtual circuit (PVC) that can be rerouted using the Private Network-to-Network Interface (PNNI) Version 1.0 protocol. 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.
The difference between an SPVC and a soft permanent virtual path (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 following quickstart procedure provides a summary of the tasks required to configure SPVCs and/or SPVPs on AXSM cards. This procedure is provided as an overview and as a quick reference for those who have previously configured these types of connections.
Step 1
Follow the steps in the "MPLS and PNNI Trunk Configuration Quickstart" section.
Configure the trunks that link the switches through which the ATM end stations connect. Be sure to add the appropriate controller (either PNNI or MPLS) on each switch and select that controller when partitioning trunks.
Step 2
dsppnni-reachable-addr network
On the PXM, verify connectivity between the node pairs that will host SVCs.
See the "Verifying PNNI Communications" section on page 4-52.
Step 3
Follow the steps in the "MPLS and PNNI UNI Port Configuration Quickstart" section.
Configure UNI ports for the ATM end stations at each end of the SVC, and assign either static or dynamic addressing to each line. Be sure to add the appropriate controller (either PNNI or MPLS) on each switch and select that controller when partitioning trunks.
Step 4
cc
Change to the AXSM card.
Step 5
addcon
Related commands:
dspchans
dspchan
If you are configuring a double-ended SPVC, configure the slave side of the SPVC or SPVP.
If the slave side of the connection is on the AXSM card, see the "Configuring the Slave Side of SPVCs and SPVPs" section.
If the slave side of the connection is on a non- AXSM card, refer to the documentation for that card.
Note
Step 6
dspcon
Verify the configuration for the connection you added in Step 5.
Step 7
username
<password>
or
cc
If you are configuring an SPVC or SPVP between:
•
•
Step 8
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 9
dsppncons
This optional step displays the SVC connections that are operating. Enter this command on the active PXM.
PNNI Virtual Trunk Configuration Quickstart
Virtual trunks are introduced and explained in the Cisco MGX 8800/8900 Series Configuration Guide, Release 5.2.
To set up a virtual trunk, as shown in Figure 3-1, the following tasks have to be completed:
•
•
The Cisco MGX 8850 (PXM45) and Cisco MGX 8950 support:
•
•
Note
Figure 3-1 Virtual Trunk Configuration
The following procedure summarizes the tasks required to configure virtual trunks on AXSM cards.
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 AXSM card.
Step 3
Add a channelized path:
upln
cnfpath
uppath
Related commands:
dsppath
dsppaths
This step is for for AXSM-XG cards only. Otherwise, skip to Step 4.
Add, configure, and bring up a channelized path. Do this step only if you are configuring a virtual trunk on an AXSM-XG card. See the "Channelizing SONET, SDH, and DS3 (T3) Lines into Paths" section.
Step 4
addport
or
addimagrp
addimalnk
addimaport
Related commands:
dspports
or
dspimagrp
dspimagrps
dspimalnk
dspimalnks
dspimaport
dspimaports
Add and configure the virtual trunk end ports at the private switches. This step establishes ATM communications between two ATM devices.
Select interface type 3 for VNNI.
For standard port configuration, see the "Adding ATM Ports" section.
To configure ATM communications over an IMA group, see the "Configuring Inverse Multiplexing over ATM" section.
Step 5
cnfpart
Related commands:
dspparts
dsppart
Configure trunk resources to PNNI and MPLS controllers. This step can assign all the trunk bandwidth to one controller, or it can assign portions of the trunk bandwidth to each controller.
Note
See the "Partitioning Port Resources between Controllers" section.
Step 6
cc
Change to the PXM card.
Step 7
dnpnport <portid>
Bring down the port so it can be configured.
Note
Step 8
cnfpnportsig
uppnport
Related commands:
dsppnports
dsppnport
dsppnportsig
Define the virtual trunk signaling at the private switches. Select PNNI signaling by setting the -nniver option to pnni100.
Step 9
cc
Change back to the AXSM card.
Step 10
addport
or
addimagrp
addimalnk
addimaport
Related commands:
dspports
or
dspimagrp
dspimagrps
dspimalnk
dspimalnks
dspimaport
dspimaports
Add and configure the virtual trunk end ports at each core edge node. Specify interface type 1 for UNI or 2 for NNI.
For standard port configuration, see the "Adding ATM Ports" section.
To configure ATM communications over an IMA group, see the "Configuring Inverse Multiplexing over ATM" section.
Step 11
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 between Controllers" section.
Step 12
cc
Change to the PXM card.
Step 13
dnpnport <portid>
Bring down the port so it can be configured.
Note
Step 14
cnfpnportsig
uppnport
Related commands:
dsppnports
dsppnport
dsppnportsig
Define 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.
Step 15
Follow the steps in the "Configuring SPVCs and SPVPs" section.
For each virtual trunk, configure an SPVP between the virtual trunk ports at each edge of the core network.
Step 16
cc
Change to the PXM card.
Step 17
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 on page 4-54.
XPVC and XPVP Configuration Quickstart
AXSM/A, AXSM/B, and AXSM-XG cards support both an Extended Permanent Virtual Connection (XPVCs) and an Extended Permanent Virtual Paths (XPVPs). An XPVC/XPVP is basically an SPVC/SPVP that connects a PNNI network to an AutoRoute network.
XPVCs and XPVPs span over AutoRoute-PNNI or AutoRoute-PNNI-AutoRoute hybrid networks. Each XPVC/XPVP can contain up to five segments that support various combination pairs of Frame Relay, ATM, and RPM endpoints. Each XPVC/XPVP may contain feeder nodes such as the Cisco MGX 8220, Cisco MGX 8230, Cisco MGX 8250, and Cisco MGX 8850 (PXM1).
The UNI or NNI interface on each XPVC segment is enhanced and called either an Enhanced User-to-Network Interface (EUNI) or an Enhanced Network-to-Network Interface (ENNI). The EUNI/ENNI allows segment OAM loopback cells to start from an edge of the hybrid AutoRoute-PNNI network and traverse through the multiple XPVC segments.
Note
Step 1
Follow the steps in the "MPLS and PNNI Trunk Configuration Quickstart" section.
Configure the trunks that link the switches to which the ATM end stations connect.
Step 2
dsppnni-reachable-addr network
Verify PNNI connectivity between the two nodes that will host the XPVC or XPVP end points.
See the "Verifying End-to-End PNNI Communications" section on page 4-54.
Step 3
Follow the steps in the "MPLS and PNNI UNI Port Configuration Quickstart" section.
Configure lines for the ATM end stations at each end of the XPVC or XPVP, and assign either static or dynamic addressing to each line.
Step 4
addport
or
addimagrp
addimalnk
addimaport
Related commands:
dspports
or
dspimagrp
dspimagrps
dspimalnk
dspimalnks
dspimaport
dspimaports
Add and configure ATM ports. This step establishes ATM layer two communications between two ATM devices.
Assign a service type of evuni or evnni to the port, and provide the -minvpi and -maxvpi for the XPVC/XPVP in one of the following ranges:
•
•
For standard port configuration, see the "Adding ATM Ports" section.
To configure ATM communications over an IMA group, see the "Configuring Inverse Multiplexing over ATM" section.
Step 5
addcon
Related commands:
dspchans
dspchan
If you are configuring a double-ended XPVC/XPVP, configure the slave side of the XPVC/XPVP as you would an SPVC/SPVP.
See the "Configuring SPVCs and SPVPs" section.
Note
Step 6
addcon
Related commands:
dspchans
dspchan
Configure the master side of an XPVC/XPVP as you would an SPVC/SPVP.
Cisco IGX Feeder to Cisco MGX 8850 Configuration Quickstart
A Cisco IGX node with a UXM card can be configured as a feeder to a Cisco MGX8850 switch, which can be configured as a routing node for the IGX feeder. The Cisco IGX feeder trunk interface on the UXM can connect to the AXSM, AXSM-E, or PXM1E of a Cisco MGX8850.
Note
Figure 3-2 shows the IGX feeder topology.
Figure 3-2 IGX Feeder Topology
The following procedure summarizes how to configure a connection from an AXSM or AXSM-E card to an IGX feeder.
Step 1
Follow the steps in the "MPLS and PNNI Trunk Configuration Quickstart" section.
Create an interface between the IGX/UXM and MGX/AXSM.
Step 2
addlmi
On the AXSM, designate the interface as a feeder.
Step 3
cc
Change to the PXM card.
Step 4
dnpnport <portid>
Bring down the port so it can be configured.
Note
Step 5
cnfpnportsig
uppnport
Related commands:
dsppnports
dsppnport
dsppnportsig
Set up the IP connectivity on the PXM controller card.
Step 6
IGX commands:
cnfswfunc
uptrk
cnftrk
Configure the IGX switch as described in the appropriate IGX documentation. Relevant IGX commands are as follows:
•
•
•
Note
PXM1 Feeder Configuration Quickstart
This procedure provides a summary of the tasks requiredto add a Cisco MGX 8850 (PXM1), Cisco MGX 8230 or Cisco MGX 8250 as a feeder to an AXSM card on a Cisco MGX 8850 (PXM45). Also, it provides an outline to add a connection.
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 AXSM card.
Step 3
addport
or
addimagrp
addimalnk
addimaport
Related commands:
dspports
or
dspimagrp
dspimagrps
dspimalnk
dspimalnks
dspimaport
dspimaports
Configure the local routing switch port that leads to the feeder. When configuring the line, select either interface type 1 (UNI) or 2 (NNI). Use the same interface type when defining the port on the feeder.
For standard port configuration, see the "Adding ATM Ports" section.
To configure ATM communications over an IMA group, see the "Configuring Inverse Multiplexing over ATM" section.
Step 4
cnfpart
Related commands: dspparts,
dsppart
Assign trunk resources to the PNNI controller ID, which is 2.
Note
See the "Partitioning Port Resources between Controllers" section.
Step 5
cc
Change to the PXM card.
Step 6
dnpnport <portid>
Bring down the port so it can be configured.
Note
Step 7
cnfpnportsig
cnfoamsegep no
uppnport
Related commands: dsppnports
dsppnport
dsppnportsig
Define the signaling protocol used on the trunk. If CWM will be used to manage the feeder, enter the cnfpnportsig command to enable IP communications between the switch and the feeder.
MGX8850.7.PXM.a > cnfpnportsig <portid> -cntlvc ipUse the cnfoamsegep command to define the local routing switch feeder port as a non-OAM segment endpoint. This is required to enable testing with the tstdelay command.
Step 8
cc
Change back to the AXSM card.
Step 9
addfdr
Related commands:
dspfdr
Define the local routing switch port as a feeder port.
See the "Defining a Feeder Port" section.
Step 10
Refer to the Cisco MGX 8850 PXM1-based documentation.
At the Cisco MGX 8850 PXM1-based feeder, enter the addcon command to add a connection on the link to the Cisco MGX 8850 (PXM45) switch.
Step 11
—
Configure the port on the remote routing switch that terminates calls in the core network. If the remote routing switch port connects to a feeder, repeat Steps 2 and 3 to configure the remote feeder trunk. If the remote routing switch port connects to CPE, configure the port for UNI communications.
Step 12
cc
Change to the PXM card.
Step 13
cnfoamsegep
Define the local routing switch feeder port as a non-OAM segment endpoint. This is required to enable testing with the tstdelay command.
Step 14
cc
Change back to the AXSM card.
Step 15
addcon
Related commands:
dspcons
Create an SPVC from the local routing switch feeder port to the remote routing switch termination port.
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 (PXM45) and Cisco MGX 8950 switches. The connection between a Cisco MGX 8850 (PXM45) and Cisco MGX 8950 and a Cisco BPX switch is a trunk between an AXSM 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 AXSM end of the trunk.
The procedure for configuring the AXSM end of the trunk is similar to the general procedure for configuring AXSM trunks. The following procedure is customized for setting up Cisco BPX PNNI trunks.
Note
Caution
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 AXSM card.
Step 3
Add a channelized path:
upln
cnfpath
uppath
Related commands:
dsppath
dsppaths
This step is for AXSM-XG cards only. Otherwise, skip to Step 4.
Add, configure, and bring up a channelized path. Do this step only if you are configuring a virtual trunk on an AXSM-XG card. See the "Channelizing SONET, SDH, and DS3 (T3) Lines into Paths" section.
Step 4
addport
or
addimagrp
addimalnk
addimaport
Related commands:
dspports
or
dspimagrp
dspimagrps
dspimalnk
dspimalnks
dspimaport
dspimaports
Add and configure ATM ports. This step establishes ATM communications between two ATM devices.
Specify NNI for interswitch trunks and VNNI for virtual trunks.
For standard port configuration, see the "Adding ATM Ports" section.
To configure ATM communications over an IMA group, see the "Configuring Inverse Multiplexing over ATM" section.
Step 5
cnfpart
Related commands:
dspparts
dsppart
Add and configure a PNNI partition for the trunk. This step reserves trunk resources for the PNNI controller.
Note
See the "Partitioning Port Resources between Controllers" section.
Step 6
cc
Change to the PXM card.
Step 7
dnpnport <portid>
Bring down the port so it can be configured.
Note
Step 8
cnfpnportsig
uppnport
Related commands:
dsppnports
dsppnport
dsppnportsig
Configure the signaling protocol used on the trunk by setting the -nniver option to pnni10.
Step 9
cc
Change back to the AXSM 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 AXSM side too.
See the "Configuring ILMI on a Port" section.
Step 11
cc
Change to the PXM card.
Step 12
dsppnni-link
dsppnni-neighbor
When both ends of the link are configured, verify the PNNI communications between the two ends. In the dsppnni-link report, there should be an entry for the port for which you are verifying communications.
The 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 on page 4-52.
AINI Link Configuration Quickstart
The following procedure provides a summary of the tasks required to configure ATM Inter-Network Interface (AINI) links on an AXSM card. 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
cc
Change to the AXSM card.
Step 3
Add a channelized path:
upln
cnfpath
uppath
Related commands:
dsppath
dsppaths
This step is for for AXSM-XG cards only. Otherwise, skip to Step 4.
Add, configure, and bring up a channelized path. Do this step only if you are configuring a virtual trunk on an AXSM-XG card. See the "Channelizing SONET, SDH, and DS3 (T3) Lines into Paths" section.
Step 4
addport
or
addimagrp
addimalnk
addimaport
Related commands:
dspports
or
dspimagrp
dspimagrps
dspimalnk
dspimalnks
dspimaport
dspimaports
Add and configure ATM ports. This step establishes ATM communications between two ATM devices.
Specify NNI for interswitch trunks.
For standard port configuration, see the "Adding ATM Ports" section.
To configure ATM communications over an IMA group, see the "Configuring Inverse Multiplexing over ATM" section.
Step 5
cnfpart
Related commands:
dspparts
dsppart
Assign trunk resources to the PNNI controller. This step can assign all the trunk bandwidth to a single controller, or it can assign portions of the trunk bandwidth to each controller.
Note
See the "Partitioning Port Resources between Controllers" section.
Step 6
cc
Change to the PXM card.
Step 7
dnpnport <portid>
Bring down the port so it can be configured.
Note
Step 8
cnfpnportsig
uppnport
Related commands:
dsppnports
dsppnport
dsppnportsig
Configure the signaling protocol used at each end of the AINI link by setting the -nniver option to aini.
Step 9
addaddr
Add destination addresses to each end of the trunk.
See the "Defining Destination Addresses for Static Links" section.
Step 10
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 "Assigning Static ATM Addresses to Destination Ports" section.
