This chapter describes how to add logical ports and virtual connections to physical lines. This chapter explains how to provision the link and connection types listed in Table 7-1.
Table 7-1 PXM1E Link and Connection Types
PXM1E Link or Connection Type
Description
PNNI trunks
PNNI trunks connect MGX switches to other MGX switches.
PNNI UNI ports
PNNI UNI ports connect MGX switches to CPE.
SVCs1
SVCs are temporary connections that are brought up and torn down upon request from CPE.
SPVCs2
SPVCs are permanent connections that can be rerouted if a link fails.
PNNI virtual trunks
PNNI virtual trunks are used to traverse public networks. The virtual trunk endpoints are on separate networks, but the path between the networks is treated like a single link.
Cisco MGX 8850 Release 1 feeder PNNI trunks
Feeder trunks link a feeder switch, such as a Cisco MGX 8230 or Cisco MGX 8250 switch, to a Cisco MGX 8850 Release 3 switch. The feeder switch concatenates relatively low speed traffic and feeds it over a higher speed interface to the Cisco MGX 8850 switch, which provide the link to the ATM network core.
BPX PNNI trunks
BPX PNNI trunks provide PNNI links between MGX 8850 and 8950switches and BPX switches that support PNNI. The BPX switch supports PNNI when connected to the Cisco SES PNNI Controller.
AINI3 links
AINI links enable connectivity between two independent PNNI networks and block the PNNI database exchange so the two networks remain independent.
IISP4 links
IISP links enable connectivity between two independent PNNI networks and block the PNNI database exchange so the two networks remain independent. IISP is the predecessor to AINI and should be used only when AINI is not supported on either end of the link.
XLMI5 links
XLMI links connect PNNI networks to AutoRoute networks. XLMI links enable the expansion of AutoRoute networks using PNNI, and they facilitate migration from AutoRoute networking to PNNI.
1 SVC = switched virtual circuits
2 SPVC = soft permanent virtual circuit
3 AINI = ATM Inter-Network Interface
4 IISP = Interim Inter-Switch Protocol
5 ILMI = Extended Link Management Interface
The configuration differences between these types of connections are often as simple as an additional command or a different set of command options. To eliminate redundancy and help experienced users complete configuration procedures quickly, this chapter uses configuration quickstarts and task descriptions to explain how to configure connections.
The first time you configure a connection type, use the quickstart procedure to see the order of tasks to complete, and then read the task descriptions for detailed instructions.
Note For all commands in this chapter, refer to the Cisco MGX 8850, MGX 8950, and MGX 8830 Command
Reference (PXM45/B and PXM1E), Release 3 for detailed information.
Note Before you start configuring ATM connections, complete the general switch configuration as described
in "Configuring General Switch
Features." Some of the procedures described in this chapter will not work if the switch has not been
set up properly.
Quickstart Provisioning Procedures
The following sections present abbreviated procedures that you can use to provision connections.
ATM Trunk Configuration Quickstart
ATM trunks connect the switch to other ATM switches in the core ATM network. The quickstart procedure in this section provides a summary of the tasks required to configure ATM trunks on Cisco MGX 8850 switches. This procedure is a quick reference for those who have previously configured these types of connections.
Note The trunk configuration is not complete until the following procedure has been completed on the
switches at both ends of the trunk.
Command
Purpose
Step 1
username
<password>
Start a configuration session.
Note To perform all the steps in this quickstart procedure, you must log in as a user with GROUP1 privileges or higher.
Assign trunk resources to PNNI controllers. This step can assign all the trunk bandwidth to a single controller, or it can assign portions of the trunk bandwidth to each controller.
When both ends of the link are configured, verify the PNNI communications between the two ends. In the dsppnni-link report, there should be an entry for the port for which you are verifying communications. The Hello state reported should be twoWayInside, and the Remote node ID should display the remote node ATM address after the second colon.
After you configure an PXM1E trunk, the trunk is ready to support SVCs. You can also create SPVCs and SPVPs between CPE at each end of the trunk as described in "Configuring SPVCs and SPVPs," which appears later in this chapter.
PNNI UNI Port Configuration Quickstart
ATM UNI ports connect the switch to ATM end devices, which serve as the boundary between the ATM network and other communications paths or networks. Typical end devices include ATM routers and multiservice concentrators. UNI signaling is used between the end system (CPE) and the PNNI network for requesting calls.
The quickstart procedure in this section provides a summary of the tasks required to configure UNI ports on Cisco MGX 8850 and Cisco MGX 8830 switches. This procedure is provided as an overview and as a quick reference for those who have previously configured UNI ports.
Note The link configuration is not complete until the equipment at both ends of the line has been configured
with compatible configuration settings.
Command
Purpose
Step 1
username
<password>
Start a configuration session.
Note To perform all the steps in this quickstart procedure, you must log in as a user with GROUP1 privileges or higher.
Assign line resources to the PNNI controllers. This step can assign all the line bandwidth to a single controller, or it can assign portions of the line bandwidth to each controller.
Configure and start ILMI on the port. This step is required for dynamic addressing and the ILMI automatic configuration feature. Otherwise, it is optional.
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 and Cisco MGX 8830 switches can use the PNNI protocol to determine how to set up SVCs through the network. Because the switch automatically sets up SVCs, you do not have to configure SVC routes. However, the switch must be configured correctly before it can set up SVCs. The following quickstart procedure summarizes the tasks required to enable SVC communications. With the exception of CPE configuration, all these tasks are described in this chapter.
Note The tasks in the following procedure do not have to be completed in the order presented. However, all
tasks must be completed before SVCs will operate.
Configure the trunks that link the switches through which the ATM end stations connect. Be sure to add the PNNI controller on each switch and select that controller when partitioning trunks.
Step 2
dsppnni-reachable-addr network
Verify connectivity between the node pairs that will host SVCs.
Configure UNI ports for the ATM end stations at each end of the SVC, and assign either static or dynamic addressing to each line. Be sure to add the PNNI controller on each switch and select that controller when partitioning trunks.
Step 4
See the CPE documentation.
Configure CPE devices for communications with the switch through the UNI ports configured in the previous step.
Step 5
dsppncons
This optional step displays the SVC connections that are operating.
It is beyond the scope of this guide to describe how to configure each model of the CPE to communicate with the switch. To complete this configuration, you will need to learn the capabilities of the CPE and the switch and define a set of communications parameters that are supported by both devices. For example, the Cisco MGX 8850 switches support UNI 3.1 communications, but if the CPE does not, you must select a signaling protocol (such as UNI 3.0) that is supported by both devices.
Once all the requirements have been met for SVC connections, CPE devices can establish SVC connections to other CPE devices on the same switched network.
SPVC and SPVP Configuration Quickstart
A soft permanent virtual circuit (SPVC) is a permanent virtual circuit (PVC) that can be rerouted using the Private Network-to-Network Interface (PNNI) Version 1.0 protocol. As with PVCs, SPVCs are full-time connections. A PVC, however, uses a predefined circuit path and will fail if the path is interrupted. Using the PNNI protocol, SPVCs can be rerouted to avoid failed communication links or to use links that offer better bandwidth.
An SPVP is a permanent virtual path that can be rerouted using the PNNI Version 1.0 protocol. The difference between an SPVC and an SPVP is that the SPVP supports multiple virtual circuits, whereas a SPVC is by definition a single virtual circuit. As with SPVCs, when an SPVP fails, PNNI can determine if an alternate route exists and reroute the connection.
The quickstart procedure in this section provides a summary of the tasks required to configure SPVCs and SPVPs on Cisco MGX 8850 and Cisco MGX 8830 switches. This procedure is provided as an overview and as a quick reference for those who have previously configured these types of connections.
PNNI Feeder Configuration Quickstart
The quickstart procedure in this section provides a summary of the tasks required to configure a connection from a Cisco MGX 8850 Release 1 feeder through one or more Cisco MGX 8850 Release 3 switches and to a remote feeder or CPE. This procedure is provided as an overview and as a quick reference for those who have previously configured these types of connections.
Note Feeder connections from Cisco MGX 8850 Release 1 feeders are not supported on PXM1E-E ports. The
feeder trunk configuration is not complete until the Cisco MGX 8850 Release 1 feeder is also
configured.
Command
Purpose
Step 1
username
<password>
Start a configuration session on the Cisco MGX 8850 Release 3 switch. This will be the local routing switch that connects to the feeder.
Note To perform all the steps in this quickstart procedure, you must log in as a user with GROUP1 privileges or higher.
Remember to select the appropriate card SCT for the controller or controllers you are using.
Step 3
addport <options>
Related commands:
dspports
Configure the local routing switch port that leads to the feeder. When configuring the line, select either interface type 1 (UNI) or 2 (NNI). Use the same interface type when defining the port on the feeder.
Note If you plan to migrate to MPLS, do not configure the whole range of VPI/VCI. Instead, only configure as much as you need for PNNI to operate. You cannot shrink the VPI/VCI range without affecting the service of your network.
Step 5
dnpnport <portid>
cnfpnportsig <options>
cnfoamsegep <portid> no
uppnport <portid>
Related commands:
dsppnports
dsppnport <portid>
dsppnportsig <portid>
Define the signaling protocol used on the trunk. If CWM will be used to manage the feeder, enter the cnfpnportsig command to enable IP communications between the switch and the feeder.
pop20two.7.PXM.a > cnfpnportsig <portid> -cntlvc ip
Enter the cnfoamsegep command to define the local routing switch feeder port as a non-OAM segment endpoint. This command is required to enable testing with the tstdelay command.
At the Cisco MGX 8850 Release 1 feeder, enter the addcon command to add a connection on the link to the Cisco MGX 8850 Release 3 switch.
Step 8
Configure the port on the remote routing switch that terminates calls in the core network. If the remote routing switch port connects to a feeder, repeat Steps 2 and 3 to configure the remote feeder trunk. If the remote routing switch port connects to CPE, configure the port for UNI communications.
Step 9
cnfoamsegep <portid> no
Define the local routing switch feeder port as a non-OAM segment endpoint. This command is required to enable testing with the tstdelay command.
Step 10
addcon <options>
Related commands:
dspcons
Create an SPVC from the local routing switch feeder port to the remote routing switch termination port.
When the Cisco SES PNNI controller is attached to a Cisco BPX switch, the BPX switch can participate in a PNNI network with Cisco MGX 8850 switches. The connection between an Cisco MGX 8850 switch and a BPX switch is a trunk between an PXM1E card in the MGX switch and a BXM card in the BPX. For instructions on configuring the BXM end of the trunk, refer to the Cisco SES product documentation. This section describes how to configure the PXM1E end of the trunk.
The procedure for configuring the PXM1E end of the trunk is similar to the general procedure for configuring PXM1E trunks. The following quickstart procedure is customized for setting up BPX PNNI trunks.
Note The trunk configuration is not complete until the BXM end of the trunk is configured.
Caution You need to allocate PNNI resources before you can configure a BPX PNNI trunk. To verify that the PNNI resource has been allocated on the trunk, enter the dsprsrc <slot.port> command.
Command
Purpose
Step 1
username
<password>
Start a configuration session.
Note To perform all the procedures in this quickstart procedure, you must log in as a user with GROUP1 privileges or higher.
Define the signaling protocol used on the trunk. The default signaling protocol is UNI Version 3.1, so you must change the signaling protocol to pnni10. For example:
When both ends of the link are configured, verify the PNNI communications between the two ends. In the dsppnni-link report, there should be an entry for the port for which you are verifying communications. The Hello state reported should be twoWayInside and the Remote node ID should display the remote node ATM address after the second colon.
After you configure a BPX PNNI trunk, the trunk is ready to support SVCs. You can also create SPVCs and SPVPs between CPE at each end of the trunk as described in the "Configuring SPVCs and SPVPs" section later in this chapter.
AINI Link Configuration Quickstart
The quickstart procedure in this section provides a summary of the tasks required to configure ATM Inter-Network Interface (AINI) links on Cisco MGX 8850 switches. This procedure is provided as an overview and as a quick reference for those who have previously configured these types of connections.
Command
Purpose
Step 1
username
<password>
Start a configuration session.
Note To perform all the steps in this quickstart procedure, you must log in as a user with SUPER_GP privileges or higher.
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.
The quickstart procedure in this section provides a summary of the tasks required to configure Interim Inter-Switch Protocol (IISP) links on Cisco MGX 8850 switches. This procedure is provided as an overview and as a quick reference for those who have previously configured these types of connections.
Note AINI is a newer protocol that is designed to replace the function of IISP. Unless you are configuring a
link with another switch that does not support AINI, you should configure an AINI link instead of an
IISP link. IISP links provide fewer capabilities than AINI links. For example, IISP links cannot support
UNI 4.0 connections.
Command
Purpose
Step 1
username
<password>
Start a configuration session.
Note To perform all the steps in this quickstart procedure, you must log in as a user with SUPER_GP privileges or higher.
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.
Define the signaling protocol used at each end of the IISP link. The default signaling protocol is UNI Version 3.1. Specify either iisp30 or iisp31 for IISP trunks.
An Extended Link Management Interface (XLMI) link joins a PNNI network with an AutoRoute network. After you establish an XLMI link, you can configure connections that link CPE in the PNNI network with CPE in the AutoRoute network. The interconnection of PNNI and AutoRoute networks enables network expansion beyond the limits of AutoRoute and facilitates a gradual migration from an all AutoRoute network to an all PNNI network.
To establish an XLMI link, you need to the following tasks:
1. Configure a PXM1E port for the XLMI link.
2. Configure a BXM port for the XLMI link.
3. Create a connection between a destination on the PNNI network and a destination on the AutoRoute network.
The quickstart procedure in this section describes how to configure an PXM1E port to support an XLMI link, and references the instructions for creating a connection between the PNNI and AutoRoute networks. Before you begin configuration, consider the following guidelines and limitations:
XLMI cannot be provisioned on a port which already has connections provisioned. To change the port to XLMI, you must first delete all existing connections.
The control VC for LMI uses VPI = 3 and VCI = 31. These numbers are not allowed on other types of connections.
Each PXM1E card supports a maximum of 16 links to AutoRoute networks and feeder nodes.
Each PXM1E port can support one link to an AutoRoute network, so the maximum number of links to AutoRoute networks is equal to the maximum number of physical PXM1E ports.
XLMI links support SPVCs and SPVPs. SVCs and LVCs are not supported.
XLMI is not supported on virtual trunks.
The various XLMI timers are not configurable on the PXM1E. Timer configuration is done on the BPX. The values for the LMI timers on PXM1E are
LMI SPVC Status Enquiry Timer (T393): 10 sec
LMI SPVC Update Status Timer (T394): 10 sec
LMI Retry Timers (N394 and N395): 5 sec
The following quickstart procedure provides a summary of the tasks required to configure XLMI links on Cisco MGX 8850 switches.
Command
Purpose
Step 1
username
<password>
Start a configuration session.
Note To perform all the steps in this quickstart procedure, you must log in as a user with SUPER_GP privileges or higher.
Assign port resources to the PNNI controller. This step can assign all the port bandwidth to a single controller, or it can assign portions of the port bandwidth to each controller.
If you are using CWM to manage your networks, the XLMI link should be ready to use. Use CWM to add a connection from a destination in the AutoRoute network to a destination in the PNNI network.
Step 10
addcon <options>
If you are not using CWM to manage your networks, add a connection from the XLMI link endpoint on the PXM1E to a destination on the PNNI network.
Note The PNNI connection you create must use the same VPI and VCI as the connection defined in the AutoRoute network.
Note Connections added with the CLI (addcon) command cannot be managed by CWM. If you are using CWM, create the connection with CWM. Afterwards, you can modify the connection with CWM or the CLI.
Step 11
—
If you are not using CWM to manage your networks, add a connection from the XLMI link endpoint on the BXM to a destination on the AutoRoute network.
Note The AutoRoute connection you create must use the same VPI and VCI as the connection defined in the PNNI network.
For more information, refer to Cisco BPX 8600 Series Installation and Configuration, Release 9.3.30.
IMA Link Configuration Quickstart
The quickstart procedure in this section provides a summary of the tasks required to configure Inverse Multiplexing for ATM (IMA) links on Cisco MGX 8850 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
Purpose
Step 1
username
<password>
Start a configuration session.
Note To perform all the steps in this quickstart procedure, you must log in as a user with SUPER_GP privileges or higher.
Define the signaling protocol used at each end of the IMA link. The default signaling protocol is UNI Version 3.1. Specify either iisp30 or iisp31 for IISP trunks.
The previous chapter described how to bring up physical lines by specifying the correct line port number. The line ports correspond to line connectors on the switch back cards. Bringing up a line establishes minimal connectivity between two nodes. When you add an ATM port to a line, you enable ATM communications over the line.
Each line can support UNI or NNI ports. UNI ports are used for lines that connect to PBXs, ATM routers, and other ATM devices that connect to the core ATM network through the switch. NNI ports are used for trunks that connect to other core ATM network devices, such as another Cisco MGX 8850 switch.
You must configure one ATM port for each line or trunk to enable ATM communications over that link. You define the port type (UNI or NNI) when you add the ATM port to the line or trunk.
To add an ATM port to a line, use the following procedure.
Step 1 Establish a configuration session using a user name with GROUP1 privileges or higher.
Step 2 Get the line number on which you will add the port. To display a list of the lines and line numbers, enter the following command:
Step 3 Verify that the line and port number you want to use is not configured. To display a list of the ports configured on the PXM1E card, enter the following command:
mgx8830a.1.PXM.a > dspports
This command displays all ports on the PXM1E card in the ifNum (interface number) column. The interfaces listed include UNI and NNI ports. Pay attention to the port numbers already in use. When you add a port, you must specify a port number that is unique on the PXM1E card. For example, if port number 2 is assigned to line 2.1 (bay 2, line 1), you cannot use port 2 on any other line on that PXM1E card.
Note The Cisco Cisco MGX 8850 switches support one port per line.
Step 4 To add an ATM port to a line, enter the following command:
Table 7-2 lists the parameter descriptions for adding ports. Figure 7-1 shows the relationship between logical interface numbers and physical lines.
Table 7-2 Parameters for addport Command
Parameter
Description
ifNum
An ATM port is also called an interface. An ATM port is defined by its slot, bay, line, and interface numbers. You do not have to enter a slot number during port configuration because you identify the slot number when you select the card.
Enter a number from 1 to 60 to identify this interface. The interface number must be unique on the card to which it is assigned. For UNI and NNI ports, you can assign one logical interface per line.
bay
Replace <bay> with 1 if the line is connected to a back card in the upper bay, or replace it with 2 if the line is connected to a back card in the lower bay. Remember that the bay number is always 1 for an PXM1E-1-2488.
line
Replace <line> with the number that corresponds to the back card port to which the line is connected. Table 7-1 lists the valid line numbers for each PXM1E card.
guaranteedRate
Enter the minimum rate for the port in cells per second (cps).
Note In this release, the <guaranteedRate> value should equal the <maxRate> value.
The rate ranges are as follows:
OC48: 50 - 5651320.
OC12: 50 - 1412830.
OC3: 50 - 353207.
T3: 50 - 96000 (PLCP) or 104268 (ADM).
E3: 50 - 80000.
maxRate
Enter the maximum rate for the port in cps.
Note In this release, the <maxRate> value should equal the <guaranteedRate> value.
The rate ranges are as follows:
OC48: 50 - 5651320.
OC12: 50 - 1412830.
OC3: 50 - 353207.
T3: 50 - 96000 (PLCP) or 104268 (ADM).
E3: 50 - 80000.
sctID
Enter the port SCT number (0 to 255). For PNNI communications, use SCT ID 2 or 4 for policing applications and use SCT ID 3 or 5 for non-policing applications.
Note Cisco Systems recommends that you use non-policing SCT IDs for all ports configured with the NNI interface type.
ifType
Enter a number that indicates the interface type. Enter 1 for UNI, or 2 for NNI.
Note Option 3 (for VNNI) is not supported on the PXM1E.
vpi
This parameter is not required for PXM1E cards (UNI and NNI ports).
minvpi
Minimum VPI between 0 and 255 for EVUNI, 0 and 4095 for EVNNI.
Note This parameter is not available for PXM1E cards (UNI and NNI ports).
maxvpi
Maximum VPI between 0 and 255 for EVUNI, 0 and 4095 for EVNNI.
Note This parameter is not available for PXM1E cards (UNI and NNI ports).
Figure 7-1 Relationship Between Cards, Bays, Lines, and Logical Interface Numbers
The following example command defines a line port as a UNI T3 line:
mgx8830a.1.PXM1.a > addport 1 1.1 96000 96000 1 1
The following example command defines a line port as an OC48 NNI trunk:
Step 5 To display a list of the ports configured on the PXM1E card, enter the following command:
mgx8830a.1.PXM1.a > dspports
This command displays all configured ports on the PXM1E card. Port numbers are listed in the ifNum (interface number) column. If you want to view information on a particular port, note the number of that port.
Step 6 To display the port configuration, enter the following command:
mgx8830a.1.PXM1.a > dspport <ifNum>
Replace <ifNum> with the number assigned to the port during configuration. The following example shows the report for this command:
mgx8830a.1.PXM1.a > dspport 1
Interface Number : 1
Line Number : 2.3 IMA Grp Number : N/A
Admin State : Up Operational State : Up
Guaranteed bandwidth(cells/sec): 353207 Number of partitions : 1
Maximum bandwidth(cells/sec) : 353207 Number of SPVC : 0
ifType : NNI Number of SPVP : 0
VPI number (VNNI, VUNI) : 0 Number of SVC : 3
MIN VPI (EVNNI, EVUNI) : 0 MAX VPI (EVNNI, EVUNI): 0
SCT Id (Conf./InUse) : 0/0=Def
, F4 to F5 Conversion : Disabled
Tip To change the port configuration, enter the cnfport command, or enter the delport command to delete a port configuration. You can also activate and deactivate ports entering the upport and dnport commands. For more information on these commands, refer to the Cisco MGX 8850, MGX 8950, and MGX 8830 Command Reference (PXM45/B and PXM1E).
Partitioning Port Resources Between Controllers
After you add a line or trunk port, you need to define how the port resources are used by the PNNI controller. You can assign all resources to one controller, or you can divide the port resources between both controllers. You can assign the following resources to controllers:
Range of VPI values
Range of VCI values
Guaranteed percent of bandwidth for ingress and egress directions
Minimum and maximum number of connections
Note You can and should use the partition definition to control how available connections are distributed
within the switch. Each switch, card, and port supports a maximum number of connections. Although
you can enable the maximum number of connections on all ports, two or three very busy ports could use
all available connections and disable communications on all other ports.
The port resources are defined as a group in a controller partition, which is dedicated to a single port controller. You must define one controller partition for each controller type you want to support, and you must configure one resource partition for each port that uses a controller. Figure 7-2 presents a simplified view of the relationship between the port controller, controller partition, and resource partitions.
Figure 7-2 Relationship of Port Controller, Controller Partition, and Resource Partitions
Figure 7-2 shows that the single controller partition connects to the port controller and to the resource partitions. After you create a port, you must create a resource partition for that port, select the PNNI controller, and define which ATM resources the port will use. You do not have to create the controller partition, as it is automatically created when you create the first resource partition. It is important that the same controller partition, and therefore the same partition ID, be used for all resource partitions of the same type on the same PXM1E card. For example, the controller is identified by the controller ID and the controller partition is identified by the partition ID. The resource partitions are identified by specifying the partition ID in combination with the port ID (interface number).
Note Partition ID 1 is reserved for PNNI.
To create a resource partition for a port, use the following procedure.
Step 1 Establish a configuration session using a user name with GROUP1 privileges or higher.
Note You must add the PNNI controller and add a port before you create a resource partition for a
port. For instructions on adding the controller, see the
"Adding the PNNI Controller"
section in "Configuring
General Switch Features." For instructions on adding ports, see the
"Adding ATM Ports" section
earlier in this chapter.
Step 2 Determine the port number to which you want to assign the resource partition. To display a list of the ports, enter the following command:
mgx8830a.1.PXM1.a > dspports
This command displays all ports on the PXM1E card in the ifNum (interface number) column.
Step 3 To create a resource partition, enter the following command:
Table 7-3 describes the parameters for this command.
Table 7-3 Parameters for the addpart Command
Parameter
Description
ifNum
Interface number or port number. This number identifies the port this resource partition configures. Enter the interface number that was assigned to the port when it was configured (see the "Adding ATM Ports" section earlier in this chapter).
partId
Partition identification number. Enter a number in the range of 1 to 5. On an PXM1E card, this number must be the same for all ports that use the same controller type. For example, if you assign the number 2 to the PNNI controller on any port, the partition ID for the PNNI controller on all other ports must be set to 2.
ctrlrId
Controller identification number. Enter the number 2 to specify the PNNI controller.
Egress minimum bandwidth. Enter the minimum percentage of the outgoing port bandwidth that you want assigned to the specified controller. One percent is equal to 0.00001 units. For example, an <egrminbw> of 250000 = 25%. The sum of the minimum egress bandwidth settings for PNNI must be 100% or less, and must be less than the sum of the egrmaxbw settings.
egrmaxbw
Egress maximum bandwidth. Enter the maximum percentage of the outgoing port bandwidth that you want assigned to the controller. One percent is equal to 0.00001 units. For example, an <egrmaxbw> of 1000000 = 100%. The sum of the maximum egress bandwidth settings for PNNI can exceed 100%, and must be more than the sum of the egrminbw settings. Available bandwidth above the minimum bandwidth settings is allocated to the operating controllers on a first-requested, first-served basis until the maximum bandwidth setting is met or there is insufficient bandwidth to meet the request.
ingminbw
Ingress minimum bandwidth. Enter the minimum percentage of the incoming port bandwidth that you want assigned to the controller. One percent is equal to 0.00001 units. For example, an <ingminbw> of 500000 = 50%. The sum of the minimum ingress bandwidth settings for PNNI must be 100% or less, and must be less than the sum of the ingmaxbw settings.
ingmaxbw
Ingress maximum bandwidth. Enter the maximum percentage of the incoming port bandwidth that you want assigned to the controller. One percent is equal to 0.00001 units. For example, an <ingmaxbw> of 750000 = 75%. The sum of the maximum ingress bandwidth settings for PNNI can exceed 100%, and must be more than the sum of the ingminbw settings. Available bandwidth above the minimum bandwidth settings is allocated to the operating controllers on a first-request, first-served basis until the maximum bandwidth setting is met or there is insufficient bandwidth to meet the request.
minVpi
Minimum VPI number for this port. For UNI ports, enter a value in the range from 0 to 255. For NNI ports, enter a value in the range from 0 to 4095.
Note If you plan to migrate to MPLS in the future, do not use the full range of VPI. You cannot shrink a partition's VPI range without bringing the port down, and this will affect the service of your network. Cisco recommends setting the VPI in the range from 0 to 140.
maxVpi
Maximum VPI number for this port. For UNI ports, enter a value in the range from 0 to 255. For NNI ports, enter a value in the range from 0 to 4095. The value for <maxVpi> cannot be less than for <minVpi>.
Note If you plan to migrate to MPLS in the future, do not use the full range of VPI. You cannot shrink a partition's VPI range without bringing the port down, and this will affect the service of your network. Cisco recommends setting the VPI in the range from 0 to 140.
minVci
Minimum VCI number for this port. For OC-48 PXM1E cards, enter a number in the range from 32 to 131072. For all other cards, enter a number in the range from 32 to 65535. To support features planned for the future, Cisco recommends setting the minimum VCI to 35 or higher.
For PNNI controllers, the minimum VCI is 35. This reserves VCI values 32 through 34 for other control purposes.
Note If you plan to migrate to MPLS in the future, do not use the full range of VCI. You cannot shrink a partition's VCI range without bringing the port down, and this will affect the service of your network. Cisco recommends setting the VCI range from 0 to 140.
maxVci
Maximum VCI number for this port. For OC-48 PXM1E cards, enter a number in the range from 32 to 131072. For all other cards, enter a number in the range from 32 to 65535.
Note If you plan to migrate to MPLS in the future, do not use the full range of VCI. You cannot shrink a partition's VCI range without bringing the port down, and this will affect the service of your network. Cisco recommends setting the VCI in the range from 0 to 140.
minConns
Minimum number of simultaneous connections allowed on this port. The minimum number of connections is 0. The type of back card and line determine the maximum number of connections as follows:
T3/E3 lines: 0 per back card.
OC3 lines: 0 per back card.
maxConns
Maximum number of simultaneous connections allowed on this port. The range is the same as described for the <minConns> parameter, and this parameter must be set to number that is greater than the number defined for <minConns>.
Note The maximum number of connections allowed is 2,700.
Step 4 To display a list showing the resource partition you have created, enter the following command:
mgx8830a.1.PXM1.a > dspparts
Step 5 To display the configuration of a specific resource partition, note the interface and partition numbers and enter the following command:
mgx8830a.1.PXM1.a > dsppart <ifNum> <partId>
Table 7-3 describes the parameters for this command.
The following example shows the report provided by the dsppart command.
mgx8830a.1.PXM1.a > dsppart 1 1
Interface Number : 1
Partition Id : 1 Number of SPVC: 0
Controller Id : 2 Number of SPVP: 0
egr Guaranteed bw(.0001percent): 1000000 Number of SVC : 0
The default signaling protocol for all new ports is UNI Version 3.1. If you plan to use this protocol on a line, you can accept this default and skip this section. However, if you plan to use a different protocol on the line, such as NNI or PNNI, you must select the correct protocol using the following procedure.
Step 1 Establish a configuration session using a user name with GROUP1 privileges or higher.
Step 2 Enter the dsppnports command to display a list of the ports you can configure.
mgx8830a.1.PXM1.a > dsppnports
Step 3 Enter the dsppnport command to bring down the port you want to configure.
mgx8830a.1.PXM1.a >dnpnport <portid>
A port is automatically brought up when you add it. You must bring down the port before you can change the port signaling protocol. Replace <portid> using the format slot[:bay].line[:ifNum]. Table 7-4 describes these parameters.
Step 4 To confirm the port is down, enter the dsppnports command. The following example shows the report that appears.
mgx8830a.1.PXM1.a > dsppnports
Summary of total connections
(p2p=point to point,p2mp=point to multipoint,SpvcD=DAX spvc,SpvcR=Routed spvc)
Type #Svcc: #Svpc: #SpvcD: #SpvpD: #SpvcR: #SpvpR: #Ctrl #Total:
p2p: 0 0 0 0 1 0 0 1
p2mp: 0 0 0 0 0 0 0 0
Total(User cons) = 1/27000, Total(Ctrl cons) = 0
Total=1
Summary of total SPVC endpoints
(P=Persistent, NP=Non-Persistent)
Type #SpvcR-P #SpvcR-NP #SpvpR-P #SpvpR-NP #SpvcD #SpvpD Total
p2p: 2 0 0 0 0 0 2
p2mp: 0 0 0 0 0 0 0
Total=2
Summary of total active SVC/SPVC intermediate endpoints
Type #Svcc #Svpc #SpvcR #SpvpR Total
p2p: 0 0 1 0 1
p2mp: 0 0 0 0 0
Total=1
Type <CR> to continue, Q<CR> to stop:
DSPPNPORTS EndPoint Grand Total = 3/54000
Per-port status summary
PortId LogicalId IF status Admin status ILMI state #Conns
1.35 16845603 up up NotApplicable 0
1.36 16845604 up up NotApplicable 0
1.37 16845605 up up NotApplicable 0
1.38 16845606 up up NotApplicable 0
4.1 16851713 up up NotApplicable 1
1:2.1:3 16845571 up up NotApplicable 0
1:2.3:1 16845569 up up Disable 1
Step 5 To select the port signaling protocol, enter the following command:
The only required parameter for this command is the <portid> parameter, but the command serves no purpose if you do not enter at least one option with it. If you include some options with the command and omit others, the omitted option remains set to the last configured value.
Table 7-4 shows the components required in the <portid> parameter, which is used with many commands. Table 7-5 lists and describes the options and parameters for the cnfpnportsig command.
Tip With some commands, you can refer to a port using only the interface number, while other commands require you to enter a complete port identification number, which includes the slot, bay, line, and interface numbers. When entering commands at the PXM45 switch prompt, you always need to specify the complete port identification number. When entering commands at the PXM1E switch prompt, you can enter only the interface number, because the interface number is unique on the PXM1E card and identifies the slot, bay, and line for the port.
Table 7-4 Port Identification Parameters
Parameter
Description
slot
Enter the slot number for the card that hosts the port you are configuring.
bay
Replace <bay> with 1 if the line is connected to a back card in the upper bay, or replace it with 2 if the line is connected to a back card in the lower bay. Remember that the bay number is always 1 for an PXM1E-1-2488.
line
Replace <line> with the number that corresponds to the back card port to which the line is connected.
ifNum
An ATM port is also called an interface. Enter a number from 1 to 60 to identify this interface. The interface number must be unique on the card to which it is assigned. An ATM port is defined by its slot, bay, line, and interface numbers. You do not have to enter a slot number during port configuration because you identify the slot number when you select the card.
Table 7-5 Port Signaling Configuration Parameters
Parameter
Description
<portid>
Port identifier in the format slot:bay.line:ifnum. These parameters are described in Table 7-4.
-univer
When configuring PNNI signaling for a UNI port, you can use this option to specify which version of UNI signaling you want the port to use. You can select UNI version 3.0 (uni30), UNI version 3.1 (uni31), UNI version 4.0 (uni40), ENNI (enni), or no UNI signaling (none). The default value is uni31. For lines that will support ABR SVCs, select uni40. The UNI ports at each end of a virtual trunk SPVP must be set to none. SPVCs and SPVPs can use UNI 3.x or 4.0 signaling.
-nniver
When configuring PNNI signaling for an NNI port, you can use this option to specify which signaling protocol you want the port to use. You can select IISP version 3.0 (iisp30), IISP version 3.1 (iisp31), PNNI version 1.0 (pnni10), ENNI (enni), or AINI (aini). The NNI ports at each end of a virtual trunk SPVP must be set to none.
-unitype
When configuring PNNI signaling for a UNI port, you can use this option to specify the UNI type. You can define the port as a private UNI port (private) or as a public UNI port (public). The default value is private.
-addrplan
When configuring PNNI signaling for a UNI port, this parameter specifies the ATM address plan used on this port. You can select AESA (aesa), E.164 (e164), or both (both). The default value is aesa.
-side
Defines the role of the signaling service used on the port. This parameter applies to IISP ports when static addressing is used (address registration is disabled). If this is a UNI connection or an NNI connection within the network, select network. For connections to other networks, you might need to select user (this is negotiated with the administrators of the other network). The default value is network.
-vpi
Defines the VPI for signaling services on this port. Enter a value in the range from 0 to 4095. The default value is 0.
-sigvci
Defines the VCI for signaling services on this port. The default value is 5, which is the well-known, reserved VCI for signaling services on VPI 0. If you choose another VCI for signaling, choose a VCI value in the range from 32 to 65535. Otherwise, the VCI can conflict with other VCIs in the reserved range from 0 to 31 on VPI 0.
-rccvci
Defines the VCI for the PNNI Routing Control Connection (RCC1) on this port. The default value is 18, which is the well-known, reserved VCI for this services on VPI 0. If you choose another VCI for signaling, choose a VCI value in the range of 32 to 65535. Otherwise, the VCI can conflict with other VCIs in the reserved range from 0 to 31 on VPI 0.
-cntlvc
This option defines a feeder trunk. The syntax for the feeder trunk definition is:
pop20two.7.PXM.a > cnfpnportsig <portid> -cntlvc ip
-passalongcap
Pass-along capability: type enable or disable. With this capability, the port has the ability to pass along unrecognized information elements (IEs) or messages. Enabling or disabling the pass-along capability applies to AINI, IISP, and public UNI. For all other types, the port behaves as if pass-along is enabled—you cannot disable pass-along on the other port types.
Default: enable
-hopcntgen
This parameter applies to AINI only. Type the entire word enable or disable. If you enable hop counting for AINI, the controller generates the hop counter information IE for all setup messages that pass through the interface if this IE does not already exist in the setup message. You must also enable AINI hop count IE for the switch by entering the cnfainihopcount command.
-vpivcialloc
This parameter applies to AINI: type enable or disable. If you enable it, the interface becomes responsible for assigning the VPI and VCI for all connections. if you enable VPI/VCI allocation on one side of the AINI link, allocation must be disabled on the other side of the link,
-svcroutingpri
Assign a routing priority at the port level for SVC, an SPVC, or an SPVP that has no priority. The Routing Priority feature does not support SVCs. However, port-level priority helps with the de-routing of SVCs in a way that supports the Priority Routing feature to re-route SPVCs and SPVPs.
1 Routing Control Connection
Note The selection of UNI or NNI is made when the port is added with the addport command. You cannot
use the -univer and -nniver options to change the port type.
The following example illustrates how to configure an NNI port to use PNNI Version 1.0 signaling.
Replace <portid> using the format slot:bay.line:ifNum. Replace <oam diagnostics> with no to disable OAM diagnostics support. Table 7-4 describes these parameters.
Note This step is required to enable testing with the tstdelay command.
Step 7 Enter the following command to bring up the port you just configured:
mgx8830a.1.PXM1.a >uppnport <portid>
Replace <portid> using the format slot:bay.line:ifNum. Table 7-4 describes these parameters.
Step 8 To verify the status of the port, enter the dsppnports command.
Step 9 To display the configuration of the PNNI port, enter the following command:
mgx8830a.1.PXM1.a >dsppnport <portid>
Replace <portid> using the format slot:bay.line:ifNum. Table 7-4 describes these parameters. The following example shows the report for this command.
Assigning Static ATM Addresses to Destination Ports
When a CPE does not support ILMI, the switch cannot automatically determine the CPE address. To enable communications with the CPE, you must assign a static ATM address to the port leading to the CPE. The static address must match the address used by the CPE. When assigning the static address, you can use command options to define how widely the static address is advertised within the switch network. Use the following procedure to define a static address for a UNI port.
Step 1 Establish a configuration session using a user name with GROUP1 privileges or higher.
Step 2 To locate the port to which you want to add an address, enter the dsppnports command.
Step 3 Enter the following command to turn off automatic address registration (it is enabled by default) on the port that will use the static address:
mgx8830a.1.PXM1.a >cnfaddrreg <portid> no
Replace portid using the format slot:bay.line:ifNum. Table 7-4 describes these parameters.
Step 4 Specify an ATM address for the port using the following command:
Note The addaddr command is used to specify static addresses for UNI links to CPE and to define
destination addresses for AINI and IISP static links. The command format above shows the
options that apply when defining static addresses for CPE.
Replace <portid> with the ID you used with the cnfaddreg command described earlier. Table 7-6 describes the other parameters used with the addaddr command.
Note The static ATM address you choose should conform to the address plan for your network. For more
information on address planning, refer to the Cisco MGX and SES PNNI Network Planning Guide.
Table 7-6 ATM Address Configuration Parameters
Parameter
Description
portid
Port identifier in the format slot:bay.line:ifnum. These parameters are described in Table 7-4.
atm-address
Enter the ATM address using up to 40 nibbles. The ATM address can include up to 20 bytes, which is 40 nibbles or 160 bits.
length
Enter the length, in bits, of the address you specified with the <atm-address> parameter. Each nibble is equal to 4 bits. The acceptable range for the parameter is from 0 to 160 bits.
-type
Enter the address type, which is int (internal) for CPE static addresses. The ext (external) value is used when creating destination addresses for AINI and IISP static links.
Note that because the default value is int, you do not have to specify this option when defining static CPE addresses.
Default = int.
-proto
For CPE static addresses, specify the -proto option with the local value. The static value applies to AINI and IISP static links.
Note that because the default value is local, you do not have to specify this option when defining static CPE addresses.
Default = local.
-plan
Enter the address plan, which is either e164 (E.164) or nsap (NSAP). For an NSAP address, the first byte of the address automatically implies one of the three NSAP address plans: NSAP E.164, NSAP DCC, or NSAP ICD.
Default = nsap.
-scope
PNNI scope of advertisement. The scope defines the level of the PNNI hierarchy at which this address is advertised. Enter 0 to advertise the destination address to all nodes in the node's peer group.
Range: 0 to 104. Default = 0.
-redistribute
Specifies whether or not the ATM address should be distributed or advertised to PNNI neighbor nodes. Enter yes to enable distribution and enter no to disable. When this option is set to yes, the node distributes the address to the PNNI neighbors defined with the scope option. When set to no, the address is not advertised to any other nodes.
Default = no.
-tnid
The transit network ID identifies a network where connections from the current node do not terminate.This number applies to static addresses only. The application of this option depends on the design intent of the user. The ID can have up to four IA5 characters (IA5 is a superset of the ASCII character set).
The following example assigns an ATM address to port 9:1.2:2:
ILMI is optional on most ports. Use ILMI on a port when you want to do any of the following tasks:
Use ILMI automatic configuration, which negotiates ATM communication parameters
Use ILMI address registration, which negotiates an ATM address for an attached CPE using an ILMI prefix assigned to the port
Enable CWM auto-discovery on a link, which allows CWM to search for and discover Cisco Systems switches that it can manage
Create a PNNI link to a BXM card on a BPX
ILMI is enabled by default on all ports and remains in a down state until ILMI is started. There are two ways to start ILMI on a port. To configure and start ILMI with a single command, use the cnfilmi command. To start ILMI using the default values, enter the upilmi command. The following sections describe how to
Configure ILMI traps and signaling and start ILMI
Configure ILMI automatic configuration
Configure ILMI dynamic addressing
Start ILMI with the default trap and signaling parameters
The default ILMI configuration uses the standard ILMI signaling VPI and VCI, sets three ILMI signaling timers, and enables the distribution of ILMI management messages (traps) to SNMP managers such as CWM. If the defaults are acceptable, you can start ILMI on the port entering the upilmi command. To change the defaults and start ILMI, use the following procedure.
Note When ILMI is configured and started at one end of a link, it must be configured and started at the other
end of the link before the link will operate properly.
Step 1 Establish a configuration session using a user name with GROUP1 privileges or higher.
Step 2 If you want to preview the current ILMI configuration for a port, enter the dspilmis command. The following example shows the dspilmis command report:
mgx8830a.1.PXM1.a > dspilmis
Sig. rsrc Ilmi Sig Sig Ilmi S:Keepalive T:conPoll K:conPoll
Port Part State Vpi Vci Trap Interval Interval InactiveFactor
The example above shows that ILMI is enabled on port 1 (ILMI State = On) and is disabled on ports 2 and 3 (ILMI State = Off). All other ILMI parameters are set to the default values.
Note The ILMI state displayed by the dspilmis command is the configuration state, not the operational state,
which appears when you enter the dsppnports or dsppnilmi commands.
Interface number or port number. This number identifies the port on which you are configuring ILMI. Enter the interface number that was assigned with the addport command (see "Adding ATM Ports").
partitionID
Partition ID number. This number identifies the PNNI partition assigned to the port. Enter the partition number that was assigned to the port with the addpart command (see "Partitioning Port Resources Between Controllers").
Note Partition ID 1 is reserved for PNNI.
ilmiEnable
ILMI enable parameter. To change the current state of ILMI, enter 1 to enable or start ILMI or 2 to disable ILMI. Note that the default value is 1, which causes ILMI to start whenever the cnfilmi command is entered, unless you enter this parameter with value 2.
Default = 1 (enable).
vpi
ILMI signaling VPI. If you need to change the default, enter a VPI number in the range of 0 to 255. Note that changing this value disables ILMI communications until the device at the remote end of the line has been configured for the same ILMI VPI.
Default = 0.
vci
ILMI signaling VCI. If you need to change the default, enter a VCI number in the range of 0 to 65535. Note that changing this value disables ILMI communications until the device at the remote end of the line has been configured for the same ILMI VCI.
Default = 16.
ilmiTrapEnable
ILMI trap distribution. When ILMI is started on a port, ILMI traps are sent to SNMP managers such as CWM.
To enable or disable the distribution of ILMI traps, enter 1 to enable ILMI traps or 2 to disable ILMI traps.
Default = 1 (enable).
keepAliveInt
ILMI keep alive timer.
Range: 1 to 65535. Default = 1.
pollingIntervalT491
ILMI polling interval T491 timer.
Range: 0 to 65535. Default = 5.
pollInctFact
ILMI polling factor K timer.
Range: 0 to 65535. Default = 4.
Step 4 To confirm your configuration changes, enter the dspilmis command.
Configuring ILMI Automatic Configuration
The Cisco MGX 8850 and Cisco MGX 8830 switches support the automatic configuration feature of ILMI 4.0, which allows two devices that share a link to share their configurations and negotiate a common set of communication parameters. For example, if two network devices share a link and are configured for different maximum VCIs on a partition, the automatic configuration feature can determine and select the highest VCI supported by both nodes. To use ILMI automatic configuration, the devices at each end of the link must support this ILMI 4.0 feature.
To enable or disable automatic configuration on a port, enter the cnfautocnf command as described in the following procedure.
Note A link between two nodes will not operate correctly if the ILMI automatic configuration feature is
enabled at one end and disabled at the other.
Step 1 Establish a configuration session using a user name with GROUP1 privileges or higher.
Step 2 To display the automatic configuration status of a port, use the dsppnport command. For example:
Replace portid with the port address using the format slot:bay.line:ifnum. These parameters are described in Table 7-4.
Enter yes to enable automatic configuration or enter no to disable automatic configuration. The default is yes.
Step 5 Up the port you configured with the uppnport command. For example:
mgx8830a.1.PXM1.a > uppnport 1:1.1:1
Step 6 To verify the change, re-enter the dsppnport command.
Configuring ILMI Dynamic Addressing
Dynamic ATM addressing is enabled by default on all Cisco MGX 8850 ports. Once ILMI is started, ILMI can negotiate ATM addresses for CPE connected to the port. To determine the ATM address for the CPE, the switch uses a 13-byte ILMI prefix that is assigned to the port, a 6-byte end system ID, and a 1-byte selector byte. The end system ID and selector byte are defined on the end system. Depending on the end system configuration, the end system ID may correspond with the interface MAC address. For dynamic addressing to work, the remote device must support it. ILMI versions 3.x and 4.0 support dynamic address registration.
The default ILMI prefix matches the PNNI node prefix and the SPVC prefix, both of which are described in the Cisco MGX and SES PNNI Network Planning Guide. If you change the PNNI node prefix, the SPVC prefix and the ILMI prefix remain unchanged. If you change the SPVC prefix, the ILMI prefix will change with it, as long as no ILMI prefix is assigned directly to the port. To eliminate the possibility of having a future SPVC prefix change affect dynamic addressing on a port, assign one or more ILMI prefixes to the port.
The following procedure describes how to enable or disable dynamic addressing and how to assign an ILMI address prefix to a port.
Note The Cisco MGX 8850 switches support up to 255 ILMI prefixes per PXM1E card, and these prefixes can
be assigned to one port or distributed among the ports.
Step 1 Establish a configuration session using a user name with GROUP1 privileges or higher.
Step 2 To display the dynamic addressing status of a port, use the dsppnport command. For example:
The Auto-reg field shows whether the dynamic addressing feature is enabled or disabled.
Step 3 To view the ILMI prefixes assigned to a port, enter the dspprfx command as follows:
mgx8830a.1.PXM1.a > dspprfx <portid>
Replace portid with the port address using the format slot:bay.line:ifnum. These parameters are described in Table 7-4. For example:
mgx8830a.1.PXM1.a > dspprfx 1:2.3:1
INFO: No Prefix registered
In the example above, no ILMI prefixes have been assigned to the port, so the port will use the prefix configured for the SPVC prefix.
Step 4 If you want to change the dynamic addressing configuration, bring down the port to be configured with the dnpnport command. For example:
mgx8830a.1.PXM1.a > dnpnport 1:2.3:1
Step 5 To enable or disable dynamic address registration, enter the following command:
mgx8830a.1.PXM1.a >cnfaddrreg <portid> <yes | no>
Enter yes to enable dynamic address configuration or enter no to disable it. The default is yes.
Step 6 Enter the following command to define an ATM prefix for a port:
mgx8830a.1.PXM1.a >addprfx <portid> <atm-prefix>
Replace portid using the format slot:bay.line:ifNum. Table 7-4 describes these parameters.
Replace atm-prefix with the 13-byte ATM address prefix that you want the dynamically assigned address to use. Specify the address prefix using 26 hexadecimal digits. The range for each digit is 0 through F (0 through 9, A, B, C, D, E, and F).
Note The address prefix you choose should conform to the address plan for your network. For more
information on address planning, refer to the 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 Up the port you configured with the uppnport command. For example:
mgx8830a.1.PXM1.a > uppnport 1:2.3:1
Step 8 To verify the proper ATM prefix configuration for a port, re-enter the dspprfx command.
Step 9 To see a dynamically assigned address that uses the prefix, enter the dspilmiaddr <port> command.
Starting ILMI with the Default or Existing Values
The upilmi command starts ILMI on a port with the existing ILMI configuration, which is the default configuration when ILMI has never been configured on that port. Although ILMI starts automatically when you configure it with the cnfilmi command, you might have to bring down ILMI with the dnilmi command to make a configuration change such as adding an ILMI prefix. To start or restart ILMI with the upilmi command, use the following procedure.
Step 1 Establish a configuration session using a user name with GROUP1 privileges or higher.
Step 2 If you do not know the interface number and partition ID for the port on which you are starting ILMI, enter the dspparts command as shown in the following example.
mgx8830a.1.PXM1.a > dspparts
if part Ctlr egr egr ingr ingr min max min max min max
Num ID ID GuarBw MaxBw GuarBw MaxBw vpi vpi vci vci conn conn
The ILMI State column displays the configured state for ILMI, which is On if ILMI is enabled and Off if ILMI is disabled (use dsppnports or dsppnilmi to see the operational state). The other columns display ILMI configuration parameters described in Table 7-7.
Configuring PXM1E Line Clock Sources
To configure the switch to receive a clock source on an PXM1E line, you must do the following:
Connect a line between the PXM1E and the node with the clock source.
Activate the line.
Create a logical port (subport) for the clock signal.
Create a resource partition.
Note If you are using NCDP to select the clock path for an MGX switch, you do not need to configure an
PXM1E line clock source.
"Preparing PXM1E Lines for Communication," describes how to activate a line. The procedures for creating ports and resource partitions appear earlier in this chapter. The following procedure describes how to configure an PXM1E clock source after the line and port have been configured.
Step 1 Establish a configuration session using a user name with GROUP1 privileges or higher.
Step 2 To set a primary or secondary PXM1E clock source, enter the following command:
Table 7-8 describes the parameters for this command.
Tip To get the correct slot:bay.line:ifnum specification, use the port ID displayed by the dsppnports command.
Table 7-8 Parameter Descriptions for cnfclksrc Command when Used for PXM1E
Parameter
Values
Descriptions
priority
primary or secondary
Replace priority with the type of clock source, which is either primary or secondary. The default is primary.
shelf
1
The shelf value is always 1, and it is optional.
slot
1 to 6, 9 to 14
The slot identifies the slot number of the PXM1E card that is receiving the clock signal.
bay
1 or 2
The bay identifies the bay in which the back card is installed. If the clock source line is connected to upper card, enter 1. If it is connected to the lower card, enter 2. The default is 1.
line
1 to 8
The line number corresponds to the line number on the back card. The line must already be active (using upln).
ifnum
1 to 60
The ifnum number corresponds to the interface number or logical port number, which is from 1 to 60. The interface number must have been previously defined using the addport command.
Step 3 To configure an additional clock source, repeat Step 2 using the correct parameters for the additional source.
The following command example shows how to configure a secondary clock source for subport (logical port) 10 on line 1 of the PXM1E card in the upper bay of slot 3. Note the placement of the periods and colons.
mgx8830a.1.PXM.a > cnfclksrc secondary 3:1.1:10
Procedures for PNNI Links
This section describes PXM1E configuration procedures that apply only to PNNI links. The following subsections explain the following:
After setting up trunks or when problems occur, use the procedures in this section to determine if PNNI is operating. The next section describes how to verify PNNI communications on a single trunk. The following section describes how to verify PNNI communications between two nodes, which can be separated by multiple PNNI links.
Verifying PNNI Trunk Communications
After you configure both ends of a PNNI trunk, it should be ready to support SVCs and any SPVCs or SPVPs that are configured. To verify that the trunk is functioning, use the following procedure.
Step 1 Establish a CLI session using a user name at any access level. When both ends of the trunk are connected to Cisco MGX 8850 switches, you can start the CLI session at either end.
Step 2 If you do not know the line number you are validating, you can view the port and line numbers by entering the dsppnports command. The first three numbers identify the slot, bay, and line. For example, port 10:2.1:3 represents slot 10, bay 2, line 1. The remaining number is the interface number assigned with the addport command.
Step 3 Enter the dsppnni-link command as follows:
mgx8830a.1.PXM1.a > dsppnni-link
The dsppnni-link command displays a report for every PNNI link on the switch. The following example shows the report for a switch with a single PNNI link.
Common peer group id...00:00.00.0000.0000.0000.0000.0000.00
In the dsppnni-link command report, there should be an entry for the port for which you are verifying communications. The Local Phy Port Id field in this entry displays the port id in the same format shown in the dsppnports command report. The Hello state reported for the port should be twoWayInside and the Remote note ID should display the remote node ATM address after the second colon.
In the example above, the report shown is for port 1:1.1:1. The Hello state is twoWayInside, and the ATM address of the node at the other end of the link is 47.00918100000000107b65f33c.00107b65f33c.01. This link is ready to support connections between the two switches.
Tip If the Hello state for the link is oneWayInside, that side is trying to communicate. Check the status at the other end. Remember that the configuration at each end of the trunk must be compatible with that on the other end. For example, if ILMI auto configuration is configured at one end and not at the other, the Hello state cannot change to twoWayInside or twoWayOutside.
Verifying End-to-End PNNI Communications
When connections between two nodes travel over multiple trunks, use the following steps to verify that the PNNI communications path is operational.
Step 1 Establish a CLI session using a user name at any access level. When both ends of the communications path are connected to Cisco MGX 8850 switches, you can start the CLI session at either end.
Step 2 To display information on all accessible nodes, enter the dsppnni-node-list command as shown in the following example:
The remote node ATM address appears in the Advertising nodeid row. The information before the first colon (56) is the PNNI level, the information between the first and second colons (160) is the ATM address length, and the remainder of the node ID is the ATM address for the remote node.
Tip If you cannot verify communications with a remote node, try verifying communications across each of the links between the nodes as described in the previous section, "Verifying PNNI Trunk Communications."
Configuring SPVCs and SPVPs
SPVCs and SPVPs are created between two ATM CPE and must be configured at each endpoint. The master endpoint is responsible for routing and rerouting. The slave endpoint is responsible for responding to requests from the master during connection setup and rerouting. Both endpoints are configured on the switch to which the ATM CPE connects. These endpoints can be on the same switch or on different switches.
The master and slave relationships exist for each SPVC or SPVP and apply only to the SPVC or SPVP connection. For example, you can have one SPVC with a master on Node A and a slave on Node B, and then create another with the Master on Node B and the slave on Node A. It is good practice to distribute the master side of SPVCs and SPVPs among the network nodes so that route processing is distributed.
The following sections describe how to configure slave and master SPVC and SPVP connections.
Tip The configuration of SPVCs and SPVPs is very similar. The difference is that SPVPs are assigned VCI 0 and do not use nonzero VCI numbers. An SPVC requires a nonzero VCI.
Configuring the Slave Side of SPVCs and SPVPs
To configure the slave side of an SPVC or SPVP, use the following procedure.
Step 1 Establish a configuration session using a user name with GROUP1 privileges or higher.
Step 2 Define the slave side of the SPVC by entering the following command:
Table 7-9 lists and defines the parameters and options for the addcon command. The local and remote terms used in Table 7-9 refer to settings for the local port you are configuring and the remote port at the other end of the connection. If you omit an option, the SPVC uses the default value.
Table 7-9 Parameters for the addcon Command
Parameter
Description
ifNum
Enter the interface number (which is defined with the addport command) for the port to which this SPVC will connect. The range is from 1 to 60.
vpi
Enter the VPI for the slave side of the SPVC.
UNI Range: 0 to 255. NNI Range: 0 to 4095.
vci
Enter the VCI for the slave side of the SPVC or SPVP.
SPVC Range: 32 to 65535.
SPVP Range: 0.
Note Cisco recommends setting the minimum VCI to 35 or higher. Future products will use VCI 32 through 34 for other services.
serviceType
Replace <serviceType> with the number that corresponds to the requested service type for this SPVC (this value must be identical on master and slave sides). Possible service types and their corresponding numbers are as follows:
cbr1 = 1
cbr2 = 11
cbr3 = 12
vbr1rt = 2
vbr2rt = 3
vbr3rt = 4
vbr1nrt = 5
vbr2nrt = 6
vbr3nrt = 7
ubr1 = 8
ubr2 = 9
abrstd = 10
mastership
Enter 2 or s if this port will serve as the slave side of the connection. Enter 1 or m if the port serves as the master side of the connection.
atmAddr.vpi.vci
This parameter is used only when defining the master side of a connection. The value entered should match the NSAP displayed after the slave side of the connection is defined. The atmAddr portion of the address corresponds to the remote ATM address; the vpi and vci parameters correspond to the VPI and VCI settings for the slave. The periods between atmAddrp and vpi and between vpi and vci are required.
-lpcr -rpcr
These options specify the local-to-remote (-lpcr) and remote-to-local (-rpcr) peak cell rate (PCR) for the connection. The values defined at each connection end must correspond to the values set at the other end. For example, the PCR defined for the local-to-remote direction at one end must match the value set for the remote-to-local direction at the other end.
Range cells per second:
OC12: 7 to 1412830.
OC3: 7 to 353207.
T3: 7 to 96000 (PLCP) or 104268 (ADM).
E3: 7 to 80000.
T1: 7 to 3622
E1: 7 to 4528
Default: 50 cells per second.
-lscr -rscr
These options specify the local-to-remote (-lscr) and remote-to-local (-rscr) sustained cell rate (SCR) for the connection. The values defined at each connection end must correspond to the values set at the other end. For example, the SCR defined for the local-to-remote direction at one end must match the value set for the remote-to-local direction at the other end.
Range cells per second:
OC12: 7 to 1412830.
OC3: 7 to 353207.
T3: 7 to 96000 (PLCP) or 104268 (ADM).
E3: 7 to 80000.
Default: Uses -lpcr and -rpcr values.
-lmbs -rmbs
These options specify the local-to-remote (-lmbs) and remote-to-local (-rmbs) Maximum Burst Size (MBS) for the connection. The values defined at each connection end must correspond to the values set at the other end. For example, the MBS defined for the local-to-remote direction at one end must match the value set for the remote-to-local direction at the other end.
Range: 1 to 5000000 cells.
Default: 1024 cells.
Note that you can change the default MBS with the cnfmbsdft command.
-lcdv -rcdv
These options specify the maximum cell delay variation (CDV) desired for the connection. The -lcdv option defines the CDV setting for the local-to-remote direction, and the -rcdv option specifies the CDV for the remote-to-local direction.
Range: 1 to 16777215 microseconds.
Default: -1, parameter not used in route selection.
-lctd -rctd
These options specify the maximum cell transfer delay (CTD) desired for the connection. The -lctd option defines the CTD setting for the local-to-remote direction, and the -rctd option specifies the CTD for the remote-to-local direction.
Range: 1 to 65535 milliseconds.
Default: -1, parameter not used in route selection.
-lmcr> -rmcr
These options specify the local-to-remote (-lmcr) and remote-to-local (-rmcr) Minimum Cell Rate (MCR) for the connection. The values defined at each connection end must correspond to the values set at the other end. For example, the MCR defined for the local-to-remote direction at one end must match the value set for the remote-to-local direction at the other end.
Range cells per second: OC12: 7 to 1412830. OC3: 7 to 353207. T3: 7 to 96000(PLCP) or 104268(ADM). E3: 7 to 80000. T1: 7 to 3622. E1: 7 to 4528.
Default: Uses -lpcr and -rpcr values.
-cdvt
This option specifies the local Cell Delay Variation Tolerance (CDVT) for the SPVC.
Range: 1 to 5000000 microseconds.
Default: 250,000 microseconds.
Note You can change the default CDVT with the cnfcdvtdft command.
-cc
This option enables or disables the flow of Operation, Administration, and Maintenance Continuity Check (OAMCC) traffic on the connection. Enter 1 to enable OAM traffic flow, or enter 0 to disable traffic flow.
Note that when this option is enabled on only one side of a connection, a transient alarm is reported until this option is set to the same value at both ends.
Default: 0, disabled.
-stat
This option enables or disables statistics collection for the SPVC. Enter 1 to enable OAM statistics collection, or enter 0 to disable it.
Default: 0,disabled.
-frame
This option enables or disables frame discard. Enter 1 to enable frame discard, or enter 0 to disable it.
Default: 0, disabled.
-mc
The maximum cost option assigns a maximum acceptable cost value to the connection. When a connection is being established, there can be multiple routes available. The cost of the connection over each route is the sum of the Administrative Weight (AW) values assigned to the links along that route. The connection will not be attempted across any route for which the total cost exceeds the value set for this option.
Range: 0 to 16777215 microseconds
Default: -1, no maximum cost required for route.
Note The AW for each link is set with the cnfpnni-intf command. For more information, refer to the Cisco MGX 8850, MGX 8950, and MGX 8830 Command Reference (PXM45/B and PXM1E).
-lputil
This option assigns the percent utilization for the local end of the connection.
-rputil
This option assigns the percent utilization for the remote end of the connection.
-slavepersflag
This option determines the persistency of the endpoint.
-rtngprio
This option determines the routing priority for the specified connection, in the range from 1 through 15, where 1 is the highest priority and 15 is the lowest priority.
Default: 8
Tip The PCR, MBS, CDVT, CDV, MCR, and CTD configuration options are optional. If you omit one of these options when entering the addcon command, the connection uses the default value listed in Table 7-9. To override the default values for any option, enter the option with a new value.
Note You can configure additional ABR parameters with the cnfabr and
cnfabrtparmdft commands. For more information, refer to the
Cisco MGX 8850, MGX 8950, and MGX 8830 Command Reference (PXM45/B and PXM1E).
The following command example defines a port as the slave side of an SPVC. Note the slave id shown in the command response.
mgx8830a.1.PXM1.a > addcon 3 101 101 1 2
slave endpoint added successfully
slave endpoint id : 4700918100000000001A531C2A00000101180300.101.101
Step 3 Write down the NSAP address the switch displays when the addcon command is complete. You will need this to configure the master side of the SPVC.
Tip When you set up the master side of the connection, enter the slave ATM address reported by the addcon command. If you maintain the current session or use the session Copy command to copy the ATM address now, you can use the session Paste command to complete the addcon command on the switch that hosts the master side of the connection.
Step 4 Verify the slave-side SPVC addition by entering the following command:
mgx8830a.1.PXM1.a > dspcons
The switch displays a report similar to the following:
mgx8830a.1.PXM1.a > dspcons
rLocal Port Vpi.Vci Remote Port Vpi.Vci State Owner Pri Persisteny
To configure the master side of an SPVC, use the following procedure.
Step 1 Establish a configuration session using a user name with GROUP1 privileges or higher.
Tip During this procedure, you will have to enter the ATM address for the slave end of the connection. If you establish this session from the same workstation you used to create the slave connection, you can use the Copy and Paste commands to avoid data entry errors.
Step 2 Enter the following command to select the PXM1E card that hosts the master side of the SPVC:
mgx8830a.1.PXM1.a > cc <slotnumber>
Step 3 Define the master side of the SPVC by entering the addcon command:
Table 7-9 lists and defines the parameters and options for this command. If you omit an option, the SPVC uses the default value.
Tip The PCR, MBS, CDVT, CDV, MCR, and CTD configuration options are optional. If you omit one of these options when entering the addcon command, the connection uses the default value listed in Table 7-9. To override the default values for any option, enter the option with a new value.
The following command example defines a port as the master side of an SPVC. Note the master id shown in the command response.
Step 5 To display the configuration for a single connection, enter the following command:
pop20two.9.PXM1E.a > dspcon ifNumvpivci
Replace the ifNum parameter with the interface or port number. The vpi and vci parameters are described in Table 7-9. The following example shows a dspcon command report.
The -1 entries in the example above indicate that a value was not specified with the addcon command. The N/A entries indicate that a value is not applicable to connections with this service type.
The following example shows the report for the connection shown in the preceding examples.
mgx8830a.1.PXM1.a > dspcons
Local Port Vpi.Vci Remote Port Vpi.Vci State Owner Pri Persisteny
To delete an SPVC or SPVP that terminates on an PXM1E card, enter the delcon command using the following format:
mgx8830a.1.PXM1.a > delcon <ifNum> <vpi> <vci>
Replace the ifNum parameter with the interface or port number. The vpi and vci parameters are described in Table 7-9. This command deletes the connection end on the local switch. It does not delete the remote end of the connection, which must be deleted on the remote switch.
Defining a PNNI Feeder Port
An ATM feeder node provides a connection between multiple relatively slow lines (such as T1 lines) and a relatively faster uplink (such as an OC-3 line) to an ATM core network. Feeders such as the Cisco MGX 8850 Release 1 switch can concatenate traffic from Frame Relay, ATM, circuit emulation, and voice circuits for transmission over the core to other feeders or to Customer Premise Equipment (CPE).
Note Feeder ports are not supported on PXM1E cards.
Note In this guide, the term Cisco MGX 8850 switch refers to an Cisco MGX 8850, Release 3 switch.
Whenever the discussion applies to an MGX 8850 Release 1 switch, the release number is included.
Figure 7-3 shows a topology that includes an Cisco MGX 8850 Release 1 feeder node.
Figure 7-3 Feeder Node Topology
In the configuration shown in Figure 7-3, the Cisco MGX 8850 switch supports up to 16 feeders. When using the Cisco MGX 8850 Release 1 switch as a feeder, you can route traffic to the core from the following Cisco MGX 8850 Release 1 service modules:
AUSM
CESM
FRSM
RPM
VISM
The lower speed communication lines that connect to the feeder must exit the core network on lines that lead to another feeder or CPE. To enable communications between a feeder and a remote feeder or CPE, you need to configure an SPVC as described in "Configuring SPVCs and SPVPs," which appears earlier in this chapter. Table 7-10 identifies the supported interoperability between Cisco MGX 8850 Release 1 service modules over these PXM1E SPVCs.
Table 7-10 Service Module Compatibility Between Feeders
Feeder A Service Module Type
Cisco MGX 8850 Service Module Type
Feeder B Service Module Type
FRSM
AXSM-E
AXSM/B
FRSM
FRSM
AUSM
FRSM
RPM
AUSM
AUSM
AUSM
CESM
AUSM
VISM
AUSM
RPM
CESM
CESM
VISM
VISM
RPM
RPM
Note To operate properly, the Cisco MGX 8850 Release 1 feeder must be running compatible software. For
information on the compatible feeder software for this release, refer to the Release Notes for
Cisco MGX 8850 and MGX 8830 Software Version 3 (PXM45/B and PXM1E).
The Cisco MGX 8850 switch uses the LMI Annex G protocol to communicate with the Cisco MGX 8850 Release 1 feeder node. When you define a feeder port, you instruct the switch to use this protocol to communicate with a feeder. The following procedure describes how to define a feeder port on the Cisco MGX 8850 switch.
Step 1 Establish a configuration session using a user name at any user level.
Step 2 To identify a port as a feeder port, enter the addfdr command as follows:
mgx8830a.1.PXM1.a > addfdr <ifNum>
Replace ifNum with the interface number for the port. For example:
mgx8830a.1.PXM1.a > addfdr 1
Tip The interface number is displayed in the dspports command report.
Note The addfdr command is blocked if other connections have been defined on the interface.
Step 3 To display the feeder ports configured on the PXM1E card, enter the dspfdrs command.
Step 4 To display information on a specific feeder port, enter the dspfdr <ifnum> command and replace ifnum with the interface number.
After you configure a feeder connection, you can enter the dspcons command to check for alarms on the feeder line. In the example below, the Abitfail alarm on connections 3 and 4 indicate a communication problem between the routing switch and the feeder node.
rtnode3.13.PXM1E.a > dspcons
record Identifier Type SrvcType M/S Upld Admn Alarm
Possible causes for the alarms shown above include:
Disconnected or damaged line
Feeder port not configured to communicate with routing switch
Service module failure in feeder
Defining Destination Addresses for Static Links
Typically, an AINI or IISP static link joins two independent networks. AINI or IISP links are used instead of PNNI so that the topologies of the two networks remain unknown to the each other.
When you create a static link, you must identify destination addresses for each side of the link. These addresses identify which ATM nodes are accessible on the other side of the link. After you define these addresses, all requests for these addresses are routed over the static link to the other network.
Note To enable bidirectional call initiation, the appropriate destination address must be configured at each end
of the link. For example, if nodes A and B have PNNI connections to a static link, the ATM address for
Node B must be added to the Node A side of the static link, and the Node A address must be added to
the Node B side of the static link.
To add destination addresses to a static link, use the following procedures.
Step 1 Establish a configuration session using a user name with GROUP1 privileges or higher.
Step 2 To locate the port to which you want to add an address, enter the dsppnports command.
Step 3 Specify an ATM address using the following command:
Note The addaddr command is used to define destination addresses for static links and to specify static
addresses for links to CPE. The command format above shows the options as they apply when defining
destination addresses for static links.
Table 7-11 describes the parameters used with the addaddr command.
Table 7-11 ATM Address Configuration Parameters
Parameter
Description
portid
Enter the port identifier in the format slot:bay.line:ifnum. These parameters are described in Table 7-4.
atm-address
Enter the ATM address using up to 40 nibbles. The ATM address can include up to 20 bytes, which is 40 nibbles or 160 bits. To summarize a group of destination addresses, enter an ATM address that is less than 20 bytes and includes the common bytes in the group of destination addresses.
length
Enter the length, in bits, of the address you specified with the <atm-address> parameter. Each nibble is equal to 4 bits. The acceptable range for the parameter is from 0 to 160 bits. When you enter a complete 20-byte ATM address, the length is 160. When you summarize a group of destination addresses, the length is equal to the number of bytes entered multiplied by 8.
-type
Enter the address type, which is ext (external) for destination addresses on the other side of a static link. The int (internal) value is used when creating static addresses for links to CPE.
Default = int.
-proto
For static link destination addresses, specify the -proto option with the static value. The local value applies to CPE links.
Default = local.
-plan
Enter the address plan, which is either e164 (E.164) or nsap (NSAP). For an NSAP address, the first byte of the address automatically implies one of the three NSAP address plans: NSAP E.164, NSAP DCC, or NSAP ICD.
Default = nsap.
-scope
PNNI scope of advertisement. The scope defines the level of the PNNI hierarchy at which this address is advertised. Enter 0 to advertise the destination address to all nodes in the node's peer group.
Range: 0 through 104. Default = 0.
-redistribute
Specifies whether or not the ATM address should be distributed or advertised to PNNI neighbor nodes. Enter yes to enable distribution and enter no to disable. When this option is set to yes, the node distributes the address to the PNNI neighbors defined with the scope option. When set to no, the address is not advertised to any other nodes.
Default = no.
Step 4 To verify that the new address is assigned, enter the following command:
mgx8830a.1.PXM1.a >dspatmaddr <portid>
Replace <portid> with the port address using the format slot:bay.line:ifnum. These parameters are described in Table 7-4. For example:
Table 7-12 describes the parameters for the addimagrp command.
Table 7-12 addimagrp command parameters
group_num
Number for the IMA group. The range is 1-8.
version
IMA version; 1: 1.0, 2: 1.1
minLinks
Minimum number of links required for group operation. For example, if you create an IMA group of 4 lines and specify a minimum number of 3 lines, then three of the four specified lines must be operational before the IMA group can be used. The range for this value is from 1 to n, where n represents the number of lines that are dedicated to the group.
txImaId
Transmit IMA Id; 0..255
txFrameLen
Transmit Frame Length;
32, 64, 128, 256 for IMA V1.1, 128 for IMA V1.0
txclkMode
Transmit Clock Mode; 1: CTC, 2: ITC
Note Option 2: ITC is not supported in Release 3 of the MGX 8850 (PXM45) and MGX 8830 switches.
diffDelayMax
Maximum Differential Delay;
Enter a umber between 1 and 275 msec for T1
Enter a number between 1 and 220 msec for E1
In the following example, the user creates a UNI IMA group 1 with lines 3, 4, and 5. The minimum number of lines is 3.
Unknown.7.PXM.a > addimagrp 2.1 1 1 1 128 1 100
Step 4 To verify that the IMA group has been created, enter the dspimagrps command:
Once you have added an IMA group on your PXM1E, you can configure that IMA group's parameters. To configure IMA group parameters, use the following procedure
Step 1 Establish a configuration session with the active PXM1E.
Step 2 Enter the dspimagrps command to list the IMA groups configured on the current card.
Step 3 To display the configuration information for the particular IMA group that you want to configure, enter a dspimagrp <bay.grp> command with the group number. Replace bay with the 2 to specify the lower bay. Replace grp with the IMA group number you want to display, in the range from1 through 16.
Note On the PXM1E, the bay number is always 2.
In the following example, the user displays the IMA group 14 in the lower bay.
Unknown.7.PXM.a > dspimagrp 2.2
Group Number : 2.2
NE IMA Version : Version 1.1
Group Symmetry : Symm Operation
Tx Min Num Links : 3
Rx Min Num Links : 3
NE TX Clk Mode : CTC
FE TX Clk Mode : CTC
Tx Frame Len : 128
Rx Frame Len : 128
Group GTSM : Down
NE Group State : StartUp
FE Group State : StartUp
Group Failure Status : Other Failure
Tx Ima Id : 2
Rx Ima Id : 0
Max Cell Rate (c/s) : 0
Avail Cell Rate (c/s) : 0
Diff Delay Max (msecs) : 100
Diff Delay Max Observed (msecs) : 0
Accumulated Delay (msec) : 0
GTSM Up Integ time(msec) : 10000
GTSM Dn Integ time(msec) : 2500
Type <CR> to continue, Q<CR> to stop:
Num Tx Cfg Links : 0
Num Rx Cfg Links : 0
Num Act Tx Links : 0
Num Act Rx Links : 0
Least Delay Link : Unknown
Tx Timing Ref Link : Unknown
Rx Timing Ref Link : Unknown
Group Running Secs : 0
Alpha Val : 2
Beta Val : 2
Gamma Val : 1
Tx OAM Label : 3
Rx OAM Label : 0
Test Pattern Procedure Status : Disabled
Test Link : Unknown
Test Pattern : 255
Step 4 To configure an IMA group, enter a cnfimagrp command, as shown in the following example:
Table 7-13 describes the parameters for the cnfimagrp command.
Table 7-13 cnfimagroup Command Parameters
-grp <group>
The bay number and the IMA group number.
bay: 1-2
grp: 1-16
Note On the PXM1E, the bay number is always 2.
-ver <version>
The protocol version of the IMA group.
2 = IMA version 1.0
3 = IMA version 1.1
-txm <minLinks>
The minimum number of links that will allow the IMA group to be operational (Range: 1-16). The minLinks value is configurable ONLY for IMA version 1.1. For IMA version 1.0, the minLinks value is always 128.
--txid <txImaId>
The IMA ID number transmitted in the IMA ID field
This field cannot be change while the IMA group is up.
txFrameLen
The length of transmitted IMA frame in megabytes. For IMA version 1.0, the txImaFrameLength value is always 128. For version 1.1, the txImaFrameLength value ca
diffDelayMax
The maximum differential delay in milliseconds (Range: 25-279).
Defaults: T1 = 276, E1 = 226
groupUpTime
0-400000 milliseconds
groupDownTime
0 and 100000 milliseconds
Note Modifying any of the attributes causes the IMA group to restart.
In the following example, the user modifies the transmit frame length, the IMA group uptime, and the IMA group downtime:
Step 3 Verify that the line and port number you want to use is not configured. To display a list of the ports configured on the PXM1E card, enter the following command:
mgx8830a.1.PXM.a > dspimaports
This command displays all ports on the PXM1E card in the ifNum (interface number) column. The interfaces listed include UNI and NNI ports. Pay attention to the port numbers already in use. When you add a port, you must specify a port number that is unique on the PXM1E card. For example, if port number 2 is assigned to line 2.1 (bay 2, line 1), you cannot use port 2 on any other line on that PXM1E card.
Note The Cisco MGX 8850 switches support one port per line.
Step 4 To add an ATM port to a line, enter the following command:
Table 7-2 lists the parameter descriptions for adding ports. Figure 7-1 shows the relationship between logical interface numbers and physical lines.
Table 7-14 Parameters for addport Command
Parameter
Description
ifNum
An ATM port is also called an interface. An ATM port is defined by its slot, bay, line, and interface numbers. You do not have to enter a slot number during port configuration because you identify the slot number when you select the card.
Enter a number from 1 to 60 to identify this interface. The interface number must be unique on the card to which it is assigned. For UNI and NNI ports, you can assign one logical interface per line.
group
ATM IMA group number in the format bay.line. Replace bay with 1 if the line is connected to a back card in the upper bay, or replace it with 2 if the line is connected to a back card in the lower bay. Remember that the bay number is always 1 for an PXM1E-16-T1E1. Replace group with the IMA group number, in the range from 1 through 16.
guaranteedRate
Enter the minimum rate for the port in cells per second (cps).
Note In this release, the <guaranteedRate> value should equal the <maxRate> value.
The rate ranges are as follows:
OC48: 50 to 5651320.
OC12: 50 to 1412830.
OC3: 50 to 353207.
T3: 50 to 96000 (PLCP) or 104268 (ADM).
E3: 50 to 80000.
maxRate
Enter the maximum rate for the port in cps.
Note In this release, the <maxRate> value should equal the <guaranteedRate> value.
The rate ranges are as follows:
OC48: 50 to 5651320.
OC12: 50 to 1412830.
OC3: 50 to 353207.
T3: 50 to 96000 (PLCP) or 104268 (ADM).
E3: 50 to 80000.
sctID
Enter the port SCT number (0 to 255). For PNNI communications, use SCT ID 2 or 4 for policing applications and use SCT ID 3 or 5 for non-policing applications.
Note Cisco Systems recommends that you use non-policing SCT IDs for all ports configured with the NNI interface type.
ifType
Enter a number that indicates the interface type. Enter 1 for UNI, or 2 for NNI.
Note Option 3 (for VNNI) is not supported on the PXM1E.
vpi
This parameter is not required for PXM1E cards (UNI and NNI ports).
minvpi
Minimum VPI between 0 and 255 for EVUNI, 0 and 4095 for EVNNI.
Note This parameter is not available for PXM1E cards (UNI and NNI ports).
maxvpi
Maximum VPI between 0 and 255 for EVUNI, 0 and 4095 for EVNNI.
Note This parameter is not available for PXM1E cards (UNI and NNI ports).
Step 5 To display a list of the ports configured on the PXM1E card, enter the following command:
mgx8830a.1.PXM1.a > dspports
This command displays all configured ports on the PXM1E card. Port numbers are listed in the ifNum (interface number) column. If you want to view information on a particular port, note the number of that port.
