Table of Contents

Preparing for Provisioning
Quickstart Provisioning Procedures

Line Configuration Quickstart
ATM Port Configuration Quickstart
IMA Group Configuration Quickstart
AUSM-to-AUSM SPVC Configuration Quickstart
AUSM-to-Non-AUSM SPVC Configuration Quickstart

General AUSM Provisioning Procedures

Bringing Up Lines
Configuring Lines
Adding ATM Ports
Adding IMA Groups
Configuring IMA Groups
Configuring SPVCs on AUSM Cards

Configuring the Slave Side of SPVCs
Configuring the Master Side of SPVCs

Provisioning Communications Links

This chapter describes how to bring up ATM communications on the physical ports of the AUSM cards using the command-line interface (CLI).

Note   AUSM cards, lines, and ports can also be configured using the CiscoView application. Refer to the CiscoView documentation for the directions.

Note   The easiest way to add connections is by using the Cisco WAN Manager application. For full details on how to set up a connection through the Cisco WAN Manager GUI, refer to the Cisco WAN Manager User's Guide.

This chapter explains how to provision the link and connection types described in Table 2-1.

To eliminate redundancy and help experienced users complete configuration tasks quickly and efficiently, this chapter provides configuration quickstart procedures.

The first time you configure a connection type, use the applicable quickstart procedure to get an overview of the tasks to be performed. Then, for more detailed instructions, consult the appropriate section(s) elsewhere in the document that are called out in the quickstart procedure. As you gain experience in configuring AUSM card connections, referring to a quickstart procedure may suffice for performing a particular configuration task.

---

Tip You can get information about most CLI commands by entering the command without parameters. Ordinarily, experienced users can configure AUSM card connections using just the quickstart procedures and the online help facilities.

---

---

Note   For a detailed description of the commands used in this chapter, refer to "AUSM Command Reference."

---

Preparing for Provisioning

When an AUSM card is first installed, it must be initialized before you can start configuration. The AUSM cards support card redundancy, and they support line redundancy and bulk distribution through SRM cards. Before you begin provisioning connections, you need to initialize the cards you plan to provision, and then you should configure the card and line redundancy options. Otherwise, you may have to change your configuration later to support these options.

For instructions on initializing cards and configuring card and line redundancy, refer to the Cisco MGX 8850 (PXM1E) and MGX 883Cisco MGX 8850 (PXM1E) and MGX 8830 Software Configuration Guide, Release 3.

Quickstart Provisioning Procedures

The following sections contain abbreviated procedures for provisioning the communications capabilities of AUSM cards installed in MGX 8850 (PXM1E) and 8830 Release 3 switches. These procedures provide a high level overview and serve as a procedural reminder for users already experienced in configuring MGX switches.

Line Configuration Quickstart

To prepare AUSM lines for communications with customer premises equipment (CPE), perform the following steps:

ATM Port Configuration Quickstart

An ATM port is a logical entity that adds ATM layer communications to a physical line that connects an MGX 8850 switch to a CPE ATM device (which, in most cases, is a router).

Note   The equipment at both ends of an ATM line must be configured with compatible settings in order for the link to be logically completed.

To configure an ATM port on an AUSM card, perform the following steps:

IMA Group Configuration Quickstart

An Inverse Multiplexing for ATM (IMA) group is a logical entity (which is similar to an ATM port) that adds ATM layer communications to a group of physical lines that connect an MGX 8850 switch to a CPE ATM device (which, in most cases, is a router). The physical lines in an IMA group collectively support a throughput roughly equal to the sum of the throughputs for the individual lines. For example, a single T1 line can support about 3,591 cells per second (cps). If you create an IMA group of 4 T1 lines, the group can support up to 14,364 cps. You can define an IMA group to include up to 8 lines for a maximum T1 throughput of 28,728 cps.

To create an IMA group, perform the following steps:

AUSM-to-AUSM SPVC Configuration Quickstart

A soft permanent virtual circuit (SPVC), a variant of a permanent virtual circuit (PVC), can be rerouted using the Private Network-to-Network Interface (PNNI) Version 1.0 protocol.

AUSM-to-Non-AUSM SPVC Configuration Quickstart

When creating an SPVC between a AUSM card and a non-AUSM card (such as a FRSM, RPM, or AXSM card), you must define both ends of the connection, just as you would for an AUSM-to-AUSM connection. The difference is that you will have to refer to the documentation for the non-AUSM product for information on configuring the connection endpoint.

To configure an SPVC between an AUSM card and a non-AUSM card, perform the following steps:

General AUSM Provisioning Procedures

This section describes the following procedures for configuring AUSM card communications:

• Bringing Up Lines
  
  
• Configuring Lines
  
  
• Adding ATM Ports
  
  
• Adding IMA Groups
  
  
• Configuring SPVCs on AUSM Cards
  
  

Bringing Up Lines

Installing an AUSM card can add up to 8 physical lines to your switch. You must bring up a line before you can configure it or provision ATM services on the line.

Before a line is brought up, or after it is brought down, the switch does not monitor the line. Prior to bringing up a line, the AUSM port status light for the line is unlit, and all line alarms are cleared.

When you bring up a line on an AUSM card, the switch starts monitoring the line. The AUSM card port status light turns green when physical layer connectivity is established with a remote device. If a physical layer communications problem occurs, the port status light turns red, and an alarm is reported.

Tip To minimize the number of alarms reported and to reduce the frequency of failed port status lamps (which display red), keep lines down until they are actually needed for communication.

To bring up an AUSM line on an MGX switch, perform the following steps:

Step 1   Establish a configuration session using a user name with GROUP 1 privileges or higher.

Step 2   Select the AUSM card on which you want to bring up a line by issuing the cc command, as shown below:

Replace the <slotnumber> parameter with the number of the slot in which the AUSM card is installed.

Step 3   To activate a line on the AUSM card, enter the addln command as shown below:

Replace the <line> parameter with the number corresponding to the back card port to which the line is connected. Table 2-2 lists the valid line numbers for the AUSM cards.

When a line has been successfully brought up, the status column reports the line status as Ena, which is an abbreviation for enabled.

Configuring Lines

All line types are brought up with a default configuration, which may or may not be compatible with the ATM device to which you are connecting. When configuring an AUSM card line, you must ensure that the devices at both ends of the connection are using the same configuration parameters on the shared line.

To configure lines on an AUSM card, perform the following steps:

Step 1   Establish a configuration session using a user name with GROUP 1 privileges or higher.

Step 2   If you do not know the line number you want to configure on the AUSM card, enter the dsplns command to display the current configuration of all lines on the card:

Remember that you cannot configure a line until you have brought it up, as described earlier in the "Bringing Up Lines" section.

Step 3   To display the configuration information for the particular line that you want to configure, enter a dspln command in the format shown below:

This sample dspln command shows the configuration parameters of a T1 line for an AUSM card that is installed in slot 1.

Step 4   To configure a line on an AUSM card, enter a cnfln command in the format shown below:

Table 2-3 lists and describes the parameters that you use in configuring T1 and E1 lines on an AUSM card.

Adding ATM Ports

The "Bringing Up Lines" section that appears earlier in this chapter describes how to bring up physical lines by specifying the correct line port number. Line ports correspond to the line connectors on the back cards of an MGX 8850 switch.

Bringing up a line establishes physical layer connectivity between two network devices. When you add an ATM port to a line, you enable ATM communications over that line.

To add a ATM port to a line, perform the following steps:

Step 1   Establish a configuration session using a user name with GROUP1 privileges or higher.

Step 2   Determine the line number on which you intend to add the Frame Relay port. To do so, enter the dsplns command.

Step 3   Verify that the port number you want to use is not already in use. To display a list of the configured ports on the AUSM card, enter the following command:

In the list of ports shown above, the port numbers configured on the AUSM card are shown in the Port column. The port numbers in the Port column appear in the format slot.port, so the port number is the number that appears after the period. When you add a port, you must specify a unique port number. For example, if port number 2 is assigned to line 2, you cannot use port 2 on any other line on that AUSM card.

Notice the list of IMA groups shown in the previous example. An IMA group serves as a single ATM port operating over multiple physical lines. When you assign a group number to an IMA group, that number serves as the ATM port number. Therefore, you cannot use the same number for both an ATM port and an IMA group.

Step 4   To add a Frame Relay port to an AUSM card, enter the following command:

Table 2-4 lists and describes the addport command parameters.

Step 5   To display the configuration information for a specific port, enter the following command:

Replace the <port> parameter with the number assigned to the port during configuration.

The following example shows the output of a dspport command for port number 7:

PXM1E_SJ.1.1.AUSMB8.a > dspport 7 LogicalPortNumber: 7 Port Enable: UP Port State: Line alarm PortType: UNI PhysicalPortNumber: 7 CellFraming: ATM CellScramble: No Scramble Plpp Loopback: No Loopback Single-bit error correction: Disabled PXM1E_SJ.1.1.AUSMB8.a >

---

---

Tip To change the port configuration, enter the cnfport command. To delete the port configuration, enter the delport command. For more information about these commands, refer to "AUSM Command Reference".

---

Adding IMA Groups

An IMA group is an ATM logical port that spans multiple physical lines. To add an IMA group, use the following procedure:

Step 1   Establish a configuration session using a user name with GROUP 1 privileges or higher.

Step 2   If you do not know the line numbers that you want to group, enter the dsplns command to display the status of all lines on the card:

Note   You cannot add a line to an IMA group until you have brought it up, as described earlier in the "Bringing Up Lines" section. To configure a line, refer to the "Configuring Lines" section.

Step 3   Enter the addimagrp (or addaimgrp) command to create the IMA group by using the following syntax:

Tip Many of the commands used to manage IMA groups are presented in two forms. For example, the addimagrp command has the same parameters and serves the same function as the addaimgrp command. ATM Inverse Multiplexing (AIM) is an older term that refers to the same features supported by Inverse Multiplexing for ATM (IMA). If this feature is new to you, use the commands with ima in the command name. If you are accustomed to using the commands with aim in the command name, you can continue to use these commands.

---

Table 2-5: Parameters for addimagrp Command

Parameter	Description
group_num	Enter a number for the IMA group. Range: 1-8 Note   The AUSM card uses the IMA group number to identify the near and far ends of the group connection. Use different IMA group IDs at each end of an IMA connection so that the switch can distinguish between loopbacked lines (near end IMA group ID) and remote switch connections.
port_type	Specify the port type—1 = UNI, 2 = NN1.
list_of_links	List the links to be included in the group. Separate each link number by a period. For example, 1.2.3.4 adds links 1 through 4 to the IMA group.
minNumLink	Enter the 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.

The following example creates an NNI IMA group 1 with lines 1, 2, 3 and 4. The minimum number of lines is 3.

PXM1E_SJ.1.1.AUSMB8.a > addimagrp 1 2 1.2.3.4 3

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

PXM1E_SJ.1.1.AUSMB8.a >

Configuring IMA Groups

To configure an IMA group, perform the following steps:

Step 1   Establish a configuration session using a user name with GROUP 1 privileges or higher.

Step 2   If you do not know the number of the IMA group you want to configure, 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 command with the group number in the format shown below:

This sample dspimagrp command shows the configuration parameters for a four-line IMA group on the AUSM card that is installed in slot 1.

Step 4   To configure an IMA group, enter a cnfimagrp command in the format shown below:

Table 2-3 lists and describes the parameters that you use in configuring T1 and E1 lines on an AUSM card.

Step 5   To verify IMA group configuration changes, enter a dspimagrp command for the appropriate IMA group.

Configuring SPVCs on AUSM Cards

SPVCs can be added and modified through the Cisco WAN Manager or the CLI. Refer to applicable documentation if you use the Cisco WAN Manager application.

AUSM SPVCs are created between one ATM port and another ATM port. Each SPVC has two endpoints. The master endpoint is responsible for routing and rerouting functions. The slave endpoint is responsible for responding to requests from the master during connection setup and rerouting. Both endpoints are configured on the switch or switches to which the ATM CPE connects. Such endpoints can be on the same switch or on different switches.

The master/slave relationship exists for each SPVC and applies only to that SPVC connection. For example, you can have one SPVC with a master on Node A and a slave on Node B, and then create another SPVC with the master on Node B and the slave on Node A. It is good practice to distribute the master side of SPVCs among network nodes so that route processing functions can be distributed.

You can create two types of SPVCs on a AUSM cards:

• Single-ended SPVCs
  
  
• Double-ended SPVCs
  
  

Single-ended SPVCs are defined at the master endpoint and do not require configuration of a slave endpoint. The primary benefit of single-ended SPVCs is that they are easier to configure. After configuration, the master endpoint configures and brings up the slave endpoint. In order for this feature to work correctly, the destination endpoint must support single-ended SPVCs.

Note   In this software release, the AUSM cards support only the slave side of single-ended SPVCs. This means that you can configure master endpoints for single-ended SPVCs on other devices that support this feature, but you cannot create a single-ended SPVC by defining a master endpoint on an AUSM card. If both SPVC endpoints must terminate on AUSM cards, you must create a double-ended SPVC.

Double-ended SPVCs require separate configuration of the master and slave endpoints. The slave endpoint must be configured first because this step generates a slave address that must be entered during master endpoint configuration.

The following sections describe how to configure slave and master SPVC connections.

Configuring the Slave Side of SPVCs

If you wish to configure a double-ended SPVC connection, you must first configure the slave endpoint for the connection. If you are configuring a single-ended SPVC, you need not configure a slave endpoint.

To configure the slave side of a double-ended SPVC, perform the following steps:

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 addcon command:

Note   If the addcon command fails and displays the "Failed to update disk" message, it could be that the PNNI controller has not been added on the PXM1E card. For information on adding the PNNI controller, refer to the Cisco MGX 8850 (PXM1E) and MGX 883Cisco MGX 8850 (PXM1E) and MGX 8830 Software Configuration Guide, Release 3.

---

Table 2-7 lists and describes the parameters for the addcon command. The local and remote terms used in this table 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, a default value for that option is used for SPVC configuration.

Caution   Once you create an SPVC connection, you cannot change the SPVC prefix until all SPVC connections have been deleted. The procedure for changing the SPVC prefix is described in the Cisco MGX 8850 (PXM1E) and MGX 883Cisco MGX 8850 (PXM1E) and MGX 8830 Software Configuration Guide, Release 3.

---

Tip If you omit one or more of the configuration options when entering the addcon command, the SPVC connection uses the default values listed in Table 2-7, as appropriate. To override the default value for a given option, enter the option with a desired value.

---

The following addcon command defines a port as the slave side of an SPVC connection. Note the slave Local Connection ID shown at the end of the display.

PXM1E_SJ.1.4.AUSMB8.a > addcon 1 100 100 Local Connection Id is : 4700918100000000016444445c00000101230100.100.100 PXM1E_SJ.1.4.AUSMB8.a >

Step 3   Write down the NSAP address displayed when the addcon command output is completed. You will need the NSAP address to configure the master side of the SPVC connection.

---

Tip When you set up the master side of the SPVC, you will need to 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 SPVC.

---

Step 4   Verify the addition of the slave side of the SPVC connection by entering the following command, which causes all information for the SPVCs to be displayed:

PXM1E_SJ.1.4.AUSMB8.a > dspcons LCN Port VPI VCI Class Type M/S EgrQ Admin Alarm ---- ---- --- ----- ------- ----- --- ---- ----- ----- 0016 001 100 00100 CBR1 VCC S 1 Up PORT-ALARM Number of channels: 1 ChanNumNextAvailable : 17 Local VpId NextAvailable : 1 PXM1E_SJ.1.4.AUSMB8.a >

Step 5   If you add the master side of the SPVC at a later date, you can display the slave connection ID with the dspcon command as follows:

PXM1E_SJ.1.4.AUSMB8.a > dspcon <port_num> <vpi> <vci>

The complete slave ID must be entered at the master endpoint in the format LocalNSAP.VPI.VCI. These values correspond to dspcon parameters shown in this example:

PXM1E_SJ.1.4.AUSMB8.a > dspcon 1 100 100 ------------------------------------------- ChanNum: 16 RowStatus: Add AdmnState: Up ChanState: Failed ---------- ---------- ---------- ---------- PORT-ALARM CTRLR-ABIT E-AIS/RDI I-AIS/RDI ---------- ---------- ---------- ---------- YES YES NO NO ------------------------------------------- ChanNum: 16 RowStatus: Add ConnAdminStatus: Up ConnectionType: VCC ServiceType: CBR1 ChanSvcFlag: PNNI PortNum: 1 VPI: 100 VCI (For VCC): 100 Local VPId(for VPC): 0 EgressQNum: 1 IngressQDepth(cells): 1000 IngressDiscardOption: CLP hysterisis IngressFrameDiscardThreshold 1000 IngressQCLPHigh(cells): 900 IngressQCLPLow(cells): 800 QCLPState: LOW IngressEfciThreshold(cells): 1000 UPCEnable: Enabled PeakCellRate[0+1](cells/sec): 3591 CellDelayVariation[0+1]: 10000 (micro secs) PeakCellRate[0](cells/sec): 3591 CellDelayVariation[0]: 250000 (micro secs) SustainedCellRate(cells/sec): 10 MaximumBurstSize(cells): 1024 SCRPolicing: CLP[0] CLPTagEnable: Enabled FrameGCRAEnable: Disable InitialBurstSize(cells): 0 LocalRemoteLpbkState: Disable ChanTestType: No Test ChanTestState: Not In Progress ChanRTDresult: 65535 ms Ingress percentage util: 100 Egress percentage util : 100 Egress Service Rate: 3591 LocalVpi: 100 LocalVci: 100 LocalNSAP: 4700918100000000016444445c00000101230100 RemoteVpi: 0 RemoteVci: 0 RemoteNSAP: 0000000000000000000000000000000000000000 Mastership: Slave VpcFlag: Vcc RoutingPriority: 8 MaxCost: 2147483647 RestrictTrunkType: No Restriction LocalConnPCR: 3591 LocalConnSCR: 10 LocalConnMCR: 10 RemoteConnPCR: 3591 RemoteConnSCR: 10 RemoteConnMCR: 10 LocalConnMBS: 1024 RemoteConnMBS: 1024 Chan Reroute: False ConnPercentUtil: 100 ChanOvrSubOvrRide: Enabled Stdabr Parameters: Minimum Cell Rate: 10 Cells per second Peak Cell Rate: 10 Cells per second Initial Cell rate: 10 Cells per second Rate Increase Factor: 64 Rate Decrease Factor: 16 Nrm -- Inrate Cell Count: 64 Trm -- Time limit for Frm: 255 milliseconds Transient Buffer Exposure: 16777215 Cells Fixed Round Trip Time: 0 milliseconds ACR Decrease Time Factor: 500 milliseconds Cutoff Decrease Factor: 16 AbrType: Switch behavior without VS/VD ChanNumNextAvailable : 17 Local VpId NextAvailable : 1 PXM1E_SJ.1.4.AUSMB8.a >

---

Configuring the Master Side of SPVCs

To configure the master side of an SPVC, perform the following steps:

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 do a copy and paste sequence to avoid data entry errors.

Step 2   To define the master side of the SPVC connection, enter the following command:

Note   If the addcon command fails and displays the "Failed to update disk" message, it could be that the PNNI controller has not been added on the PXM1E card. For information on adding the PNNI controller, refer to the Cisco MGX 8850 (PXM1E) and MGX 883Cisco MGX 8850 (PXM1E) and MGX 8830 Software Configuration Guide, Release 3.

---

Table 2-7 lists and describes the parameters for the addcon command.

Tip If you omit one or more of the options when entering the addcon command, the connection uses the default values listed in Table 2-7. To override the default value for a given option, enter the option with the desired value. Any parameters you enter must match the corresponding parameters defined for the slave end of the connection.

The following addcon command defines a port as the master side of a double-ended SPVC.

Step 3   To view the master-side of the new SPVC connection in the connection list, enter the dspcons command:

This command displays all the connections for the AUSM card.

Step 4   To display the configuration information for a specific SPVC endpoint, enter the following command:

The port, VPI, and VCI numbers are listed in the dspcons command display.

The following is sample output from the dspcon command for the connection created in the previous example. Notice that this report shows the NSAP IDs for both ends of the connection.

Posted: Fri Oct 18 11:16:19 PDT 2002
All contents are Copyright © 1992--2002 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.