Switch Operating Procedures

This chapter describes procedures you can use to manage the MGX 8850 and MGX 8950 switches.

Managing the Configuration Files

The following sections describe how to save a switch configuration in a single zipped file, clear or erase a configuration, and restore a configuration from a file.

Saving a Configuration

After configuring your switch or after making configuration updates, it is wise to save the configuration. Restoring a saved configuration is much easier than re-entering all the commands used to configure the switch.

To save a configuration, you use the saveallcnf command, which saves the configuration to a file in the C:/CNF directory. The file is named using the switch name and the current date as follows:

Name_01_DateTime.zip.

The date appears in YYYYMMDD (year, month, day) format, and the time appears in HHMM (hour, minute) format. For example, if the configuration for a switch named mgx8850a were saved on February 29th, 2000 at 2:31pm, the file would be named C:/CNF/mgx8850a_01_200002291431.zip.

When you save a configuration, the switch saves all configuration data, including the software revision levels used by the cards in the switch. The saved configuration file does not include the boot and runtime software files. Should you need to restore a configuration, the restoreallcnf command restores the configuration exactly as it was when the configuration file was saved. If the boot and runtime files have been removed from the switch, they must be transferred to the switch before the restored configuration can start.

Note If you have upgraded software on the switch since the last time the configuration was saved, a configuration restore will restore the non-upgraded software versions and configuration data. The software does not allow you to save a configuration and restore it on a different revision level of the software.

You can save a configuration if both of the following are true:

•No save or restore process is currently running.

•No configuration changes are in progress.

Caution Make sure that no other users are making configuration changes when you save the configuration. The MGX 8850 and MGX 8950 switches do not check for other CLI or CWM users before saving a configuration. If other users make changes while the file is being saved, the configuration can become corrupt. If you try to restore the configuration from a corrupt file, the switch can fail and you might have to send switch cards back to the factory for reprogramming.

To save a switch configuration, use the following procedure.

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

Step 2 If RPM-PR cards are used in the switch, execute the copy run start command on each RPM-PR card to save the current configuration. For example:

M8850_LA.7.PXM.a > cc 9

(session redirected)

RPM-PR_LA_9>enable

Password:

RPM-PR_LA_9#copy run start

Destination filename [startup-config]?

Building configuration...

[OK]

RPM-PR_LA_9#cc 7

(session redirected)

M8850_LA.7.PXM.a >

This step updates the configuration files, which will be saved in Step 3.

Step 3 To save the configuration, enter the saveallcnf command:

mgx8850a.7.PXM.a > saveallcnf [-v]

The verbose option, -v, displays messages that show what the switch is doing during the save process. You do not need to see these messages, but they do give you an indication on how the save process is proceeding. If you do not enter the -v option, the switch does not display any status messages until the save is complete.

Step 4 Read the prompt that appears. Press Y if you want to continue, and press Enter.

When the save is complete, the switch prompt reappears, and the new file is stored in the C:/CNF directory.

Note The switch stores only the last two files saved with the saveallcnf command. This prevents the hard disk from getting full due to repetitive use of this command. If you need to save files that will be erased the next time the saveallcnf command is run, use an FTP client to copy them to a file server or workstation before saving the next configuration.

The following example shows what appears on the switch when the saveallcnf command is used without the -v option:

Note Cisco Systems recommends that you use an FTP client to copy the saved configuration file to a workstation. This ensures that you have a backup copy if the PXM45 Hard Drive card fails. Please note that subsequent usage of the saveallcnf command will overwrite an existing older configuration file, if more than one file exists in the CNF directory.

Clearing a Configuration

There are two commands that allow you to clear the switch configuration: clrcnf and clrallcnf.

To clear switch provisioning data such as the PNNI controller, AXSM ports, and SPVC connections, enter the clrcnf command. This command clears all configuration data except the following:

•IP address configuration

•Node name

•Software version data for each card

•SNMP community string, contact, and location

•Date, time, time zone, and GMT offset

To clear the entire configuration, use the clrallcnf command. This command clears all the provisioning data and most of the general switch configuration parameters, such as the switch name and SNMP configuration. The clrallcnf command clears all IP addresses except the boot IP address.

Note When 4 or more RPM-PR cards are installed in the switch, a standby PXM45 can take approximately 45 minutes to reach standby state after the clrallcnf is entered.

Restoring a Saved Configuration

You can restore a configuration if all of the following are true:

•No save or restore process is currently running.

•No configuration changes are in progress.

•The switch is not hosting any critical calls.

Caution Make sure that no other users are making configuration changes when you restore the configuration. The MGX 8850 and MGX 8950 switches do not check for other CLI or CWM users before restoring a configuration. If other users make changes while the file is being restored, the configuration can become corrupt, the switch can fail, and you might have to send switch cards back to the factory for reprogramming.

To restore a saved switch configuration, use the following procedure.

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

Step 2 Verify that the file from which you want to restore configuration data is located in the C:/CNF directory.

Note The C:/CNF directory is the only location from which you can restore a configuration file. If the file has been moved to another directory or stored on another system, the file must be returned to this directory before the data can be restored.

Caution The
restoreallcnf command resets all cards in the switch and terminates all calls passing through the switch.

Note The configuration file saved with the saveallcnf command does not include the boot and runtime software files in use at the time of the save. If you have removed any of these files, you need to transfer them to the switch before the switch can start the restored configuration.

Replace filename with the name of the saved configuration file.You do not have to enter the path to the file or the extension. For information on the location and name of the file, see "Saving a Configuration."

Managing ILMI

The following sections describe how to:

•Enable and disable ILMI on a port

•Display ILMI port configuration data

•Display and clear ILMI management statistics

•Delete ILMI prefixes

Enabling and Disabling ILMI on a Port

The MGX 8850 and MGX 8950 switches provide several commands that you can use to enable or disable ILMI on a port. For instructions on enabling or disabling ILMI from an AXSM card prompt, refer to "Configuring ILMI on a Port," in "Provisioning AXSM Communication Links." To enable or disable ILMI from the PXM45 prompt, use the following procedure.

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

Step 2 To display a list of ports and view the current ILMI status of each, enter the dsppnports command.

To enable or disable ILMI on a port, enter the cnfilmienable command as follows:

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 AXSM-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. Interface numbers are assigned with the addport command.

Displaying the ILMI Port Configuration

The following procedure describes some commands you can use to view the ILMI port configuration.

Step 1 Establish a configuration session using a user name with access privileges at any level.

Step 2 To display the ILMI configuration for all ports on an AXSM card, enter the dspilmis command. The following example shows the dspilmis command report:

pop20two.1.AXSM.a > dspilmis

Sig. rsrc Ilmi Sig Sig Ilmi S:Keepalive T:conPoll K:conPoll

Port Part State Vpi Vci Trap Interval Interval InactiveFactor

---- ---- ---- ---- ---- --- ------------ ---------- ----------

1 1 Off 0 16 On 1 5 4

2 1 Off 0 16 On 1 5 4

3 1 Off 0 16 On 1 5 4

4 1 Off 0 16 On 1 5 4

The example above shows that all ports are configured for the default ILMI values and that ILMI has not been started on any port. Table 7-2 describes each of the report columns.

Table 7-2 Column Descriptions for dspilmis and dspilmi commands

Column

Description

Sig. Port

Port or logical interface for which ILMI status appears.

rsrc Part

Resource partition assigned to the port.

ILMI State

Configured ILMI state, which appears as either On or Off. The default ILMI state is Off, which indicates that ILMI is disabled on the port. You can enable ILMI signaling on the port by entering the upilmi command, which changes the state to On. Note that this column indicates whether ILMI is enabled or disabled. To see the operational state of ILMI, use the dsppnport, dsppnports, or dsppnilmi commands.

Sig Vpi

The VPI for the ILMI signaling VCC.

Sig Vci

The VCI for the ILMI signaling VCC.

Ilmi Trap

Indicates whether ILMI traps are enabled (On) or disabled (Off) for this port.

S:Keepalive Interval

T:conPoll Interval

K:conPoll InactiveFactor

Step 3 To display the ILMI configuration for a single port, enter the dspilmi command as follows:

pop20one.10.AXSM.a > dspilmi <ifnum> <partitionId>

Replace ifnum with the interface number of the port, and replace partitionID with the partition number assigned to the port. You can view both of these numbers in the dspilmis command report. The following is an example report for the dspilmi command. Table 7-2 describes each of the columns that appear in the command report.

pop20one.10.AXSM.a > dspilmi 1 1

Sig. rsrc Ilmi Sig Sig Ilmi S:Keepalive T:conPoll K:conPoll

Port Part State Vpi Vci Trap Interval Interval InactiveFactor

---- ---- ---- ---- ---- --- ------------ ---------- ----------

1 1 On 0 16 On 1 5 4

Step 4 To display the operational state of ILMI on all ports, use the dsppnports command at the PXM45 prompt as shown in the following example:

The ILMI operational state is displayed as one of the following: Disable, EnableNotUp, or UpAndNormal. When ILMI is disabled on the port, the operational status is Disable. When ILMI is enabled on the local port but cannot communicate with ILMI on the remote port, the status is EnableNotUp (This happens when ILMI is disabled on the remote end.). When ILMI is enabled and communicating with ILMI on the remote port, the ILMI state is UpAndNormal.

Step 5 To display ILMI configuration data for a specific port, use the dsppnilmi command at the PXM45 prompt as follows:

pop20one.7.PXM.a > dsppnilmi <portid>

Replace portid using the format slot:bay.line:ifNum. Table 7-1 describes these parameters. The following example shows the format of the dsppnilmi command report.

pop20one.7.PXM.a > dsppnilmi 10:1.1:1

Port: 10:1.1:1 Port Type: PNNI Side: network

Autoconfig: disable UCSM: disable

Secure Link Protocol: enable

Change of Attachment Point Procedures: enable

Modification of Local Attributes Standard Procedure: enable

Addressreg: Permit All

VPI: 0 VCI: 16

Max Prefix: 16 Total Prefix: 0

Max Address: 64 Total Address: 0

Resync State: 0 Node Prefix: yes

Peer Port Id: 16848897 System_Id : 0.80.84.171.226.192

Peer Addressreg: enable

Peer Ip Address : 0.0.0.0

Peer Interface Name : atmVirtual.01.1.1.01

ILMI Link State : UpAndNormal

ILMI Version : ilmi40

INFO: No Prefix registered

Table 7-3 Descriptions for dsppnilmi Command Display Components

Component

Description

Port

Port or logical interface for which ILMI status appears.

Port Type

Controller type to which this port is assigned.

Side

Side of ATM link, which is either network or user.

Autoconfig

Status of Autoconfig option, which is either enable or disable.

UCSM

Status of UCSM option, which is either enable or disable.

Secure Link Protocol

Status of secure link protocol option, which is either enable or disable. You can change this option with the cnfilmiproto command.

Change of Attachment Point Procedures

Status of change-of-attachment-point-procedures option, which is either enable or disable. You can change this option with the cnfilmiproto command.

Modification of Local Attributes Standard Procedure

Status of modification-of-local-attributes-standard-procedure option, which is either enable or disable. You can change this option with the cnfilmiproto command.

Addressreg

VPI

ILMI signaling VPI. You can change this option with the cnfilmi command.

VCI

ILMI signaling VCI. You can change this option with the cnfilmi command.

Max Prefix

Total Prefix

Max Address

Total Address

Resync State

Node Prefix

Peer Port ID

System ID

Peer Address Reg

Peer IP Address

Peer Interface Name

ILMI Link State

The ILMI operational state is displayed as one of the following: Disable, Undefined, or UpAndNormal. When ILMI is disabled on the port, the operational status is Disable. When ILMI is enabled on the local port but cannot communicate with ILMI on the remote port, the status is Undefined (This happens when ILMI is disabled on the remote end.). When ILMI is enabled and communicating with ILMI on the remote port, the ILMI state is UpAndNormal.

ILMI Version

ilmi40

Info

Displaying and Clearing ILMI Management Statistics

The following procedure describes some commands you can use to view ILMI management statistics.

Step 1 To display ILMI management statistics for a port, enter the dspilmicnt command as follows:

pop20one.10.AXSM.a > dspilmicnt <ifnum> <partitionId>

Replace ifnum with the interface number of the port, and replace partitionID with the partition number assigned to the port. You can view both of these numbers in the dspilmis command report. The following is an example report for the dspilmicnt command.

pop20one.10.AXSM.a > dspilmicnt 1 1

If Number : 1

Partition Id : 1

SNMP Pdu Received : 36914

GetRequest Received : 18467

GetNext Request Received : 0

SetRequest Received : 0

Trap Received : 1

GetResponse Received : 18446

GetResponse Transmitted : 18467

GetRequest Transmitted : 18446

Trap Transmitted : 4

Unknown Type Received : 0

ASN1 Pdu Parse Error : 0

No Such Name Error : 0

Pdu Too Big Error : 0

Note Partition ID 1 is reserved for PNNI.

Step 2 To clear the ILMI management statistics for a port, enter the clrilmicnt command as follows:

pop20one.10.AXSM.a > clrilmicnt <ifnum> <partitionId>

Replace ifnum with the interface number of the port, and replace partitionID with the partition number assigned to the port. The following example shows the switch response to this command.

pop20one.10.AXSM.a > clrilmicnt 1 1

ilmi stats for ifNum 1, partId 1 cleared

Step 3 To verify that the statistics have been cleared, re-enter the dspilmicnt command.

Step 5 Up the port you configured with the uppnport command. For example:

pop20one.7.PXM.a > uppnport 10:2.2:4

Step 6 To verify the proper ATM prefix configuration for a port, re-enter the dspprfx command.

Determining the Software Version Number from Filenames

The following version management commands require a version number to be entered in a specific format as follows:

•abortrev

•burnboot

•commitrev

•loadrev

•runrev

•setrev

In most cases, you will find the correct firmware version numbers in the Release Notes for Cisco MGX 8850 Software Version 2.1.60 or the Release Notes for Cisco MGX 8950 Software Version 2.1.60. If the release notes are not available, you can use the firmware filename to determine the version number as described below.

Step 1 Establish a configuration session at any access level.

Step 2 To view the files on the switch hard drive, you can enter UNIX-like commands at the switch prompt. To change directories to the firmware directory (FW), enter the cd command as follows:

mgx8850a.7.PXM.a > cdC:/FW

Note Remember that UNIX directory and filenames are case sensitive.

Step 3 To list the contents of the directory, enter the ll command:

mgx8850a.7.PXM.a > ll

The display shows:

pop20one.7.PXM.a > ll

size date time name

-------- ------ ------ --------

512 APR-19-2000 01:24:16 . <DIR>

512 APR-19-2000 01:24:16 .. <DIR>

2248536 MAY-17-2000 15:12:16 axsm_002.000.000.000.fw

591008 MAY-15-2000 21:37:28 axsm_002.000.000.000_bt.fw

839392 MAY-15-2000 21:37:36 pxm45_002.000.000.000_bt.fw

3450888 MAY-15-2000 21:37:48 pxm45_002.000.000.000_mgx.fw

2260984 JUN-06-2000 07:18:40 axsm_002.000.001.000.fw

592288 JUN-06-2000 07:09:02 axsm_002.000.001.000_bt.fw

844720 JUN-06-2000 07:09:26 pxm45_002.000.001.000_bt.fw

3481816 JUN-06-2000 07:11:00 pxm45_002.000.001.000_mgx.fw

In the file system :

total space : 819200 K bytes

free space : 786279 K bytes

Figure 7-1 shows the information contained in filenames for released software.

Figure 7-1 Filename Format for Released Software

Filenames that include "_mgx" are for runtime PXM45 firmware, and filenames that include "_bt" are for boot firmware. AXSM runtime firmware images do not have an image description after the version number. When you first receive the switch from Cisco, there will be single versions of each file. If you download updates to any files, there will be multiple versions of those files.

Figure 7-2 shows the information contained in filenames for prereleased firmware. If you are evaluating nonreleased firmware, the filename format shows that the firmware is prereleased and indicates the development level of the prerelease firmware.

Figure 7-2 Filename Format for Prereleased Firmware

Step 4 Translate the filenames to version numbers, and write the numbers down so you can set the revision levels for the software.

Write the version number down in the format required by the revision management commands. The following example shows the required format. If you are logged in as a user with SERVICE_GP access privileges, you can display this example by entering any of the revision management commands without parameters.

pop20one.7.PXM.a > runrev

ERR: Syntax: runrev <slot> <revision>

revision - revision number. E.g.,

2.0(1)

2.0(1.248)

2.0(0)B1 or 2.0(0)B2

2.0(0)A1 or 2.0(0)A2

2.0(0)I1 or 2.0(0)I2

2.0(0)D

The first example above, 2.0(1), is for released firmware version 2.0, maintenance release 1. The second example, 2.0(1.248), is for patch 248 to version 2.0, maintenance release 1. The other examples are for prerelease firmware. Prerelease firmware does not include patches; the maintenance release number is increased for each software change.

Table 7-4 shows some example filenames and the correct version numbers to use with the revision management commands.

Displaying Redundancy Status

To display the redundancy configuration for the switch, use the following procedure.

Step 1 Establish a configuration session at any access level.

Step 2 To view the redundancy status, enter the following command:

mgx8850a.7.PXM.a > dspred

After you enter the command, the switch displays a report similar to the following:

pop2one.7.PXM.a > dspred

pop2one System Rev: 02.00 Feb. 23, 2000 10:59:10 PST

MGX8850 Shelf Alarm: NONE

Primary Primary Primary Secondary Secondary Secondary Redundancy

SlotNum Type State SlotNum Type State Type

------- ------- ------- --------- --------- --------- ----------

7 PXM45 Active 8 PXM45 Empty Resvd 1-1

Switching Between Redundant PXM Cards

When the switch has two PXM45 cards running in active and standby mode, you can use the swtichcc command to swap the roles of the two cards. Typically, you use this command to switch roles so you can upgrade the hardware or software on one of the cards.

Note The switchcc command is executed only when all cards are operating in active or standby roles. For example, if the non-active PXM45 is not in standby state, or if an AXSM card is being upgraded, the swtichcc command is not executed.

To switch operation from one redundant PXM card to another, use the following procedure.

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

Step 2 Check the status of the active and standby cards by entering the dspcds command.

The dspcds command should list one card as active and one card as standby. If the cards are not in their proper states, the switchover cannot take place.

Step 3 To switch cards, enter the following command after the switch prompt:

mgx8850a.7.PXM.a > switchcc

Switching Between Redundant AXSM Cards

To switch operation from an active redundant AXSM card to the standby card, use the following procedure.

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

Step 2 Check the status of the active and standby cards by entering the dspcds command.

The dspcds command should list one card as active and one card as standby. If the cards are not in their proper states, the switchover cannot take place.

Step 3 To switch cards, enter the following command after the switch prompt:

mgx8850a.7.PXM.a > switchredcd <fromSlot> <toSlot>

Replace <fromSlot> with the card number of the active card, and replace <toSlot> with the card number to which you want to switch control.

Switching Between Redundant RPM-PR Cards

To switch operation from an active RPM-PR card to the standby card, use the following procedure.

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

Step 2 Check the status of the active and standby cards by entering the dspcds command.

The dspcds command should list one card as active and one card as standby. If the cards are not in their proper states, the switchover cannot take place.

Step 3 To switch cards, enter the following command after the switch prompt:

mgx8850a.7.PXM.a > softswitch <fromSlot> <toSlot>

Replace <fromSlot> with the card number of the active card, and replace <toSlot> with the card number to which you want to switch control.

Removing Redundancy Between Two Cards

To remove the redundant relationship between two AXSM cards, use the following procedure.

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

Step 2 To remove card redundancy, enter the following command after the switch prompt:

mgx8850a.7.PXM.a > delred <primarySlot>

Replace primarySlot with the number of the primary card. You can view the primary and secondary status of cards by entering the dspred command.

Select the working line to configure by replacing <workingIndex> with the with the location of the working line using the format slot.bay.line. For example, to specify the line on card 9, bay 1, line 2, enter 9.1.2.

The signal failure Bit Error Rate (BER) threshold. Replace <SignalFaultBER> with a number in the range of 3 to 5.

5 = signal failure BER threshold = 10 ^^ -5.

-sd

The Signal degrade BER threshold. Replace <SignalDegradeBER> with a number in the range of 5 to 9.

5 = signal degrade BER threshold = 10 ^^ -5.

-wtr

The number of minutes to wait before attempting to switch back to the working line. Replace <Wait To Restore> with a number in the range of 1 to 12 (minutes).

Note that this option is applicable only when the -rv option is set to 2, enabling revertive operation.

-dr

The direction option, which specifies the communication paths to be switched when a failure occurs. The options are unidirectional or bidirectional. When the unidirectional option is selected, only the affected path, either transmit or receive, is switched. When the bidirectional option is selected, both paths are switched.

To set this option, replace the <direction> variable with 1 for unidirectional operation or 2 for bidirectional operation.

-rv

The revertive option, which defines how the switch should operate when a failed line recovers. The options are revertive and nonrevertive. When the -rv option is configured for revertive operation and the working line recovers, the switch will switch back to the working line after the period specified by the -wtr option. If the line is configured for nonrevertive operation, a failure on the working line will cause the switch to use the protect line until a manual switchover is initiated as described in "Switching APS Lines."

To set this option, replace the <revertive> variable with 1 for non-revertive operation or 2 for revertive operation.

Switching APS Lines

To switch between two APS lines, use the switchapsln command as described in the following procedure.

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

Removing APS Redundancy Between Two Lines

To remove the redundant APS line relationship between two lines, use the delapsln command as described in the following procedure.

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

Step 2 To remove redundancy between the two lines, enter the following command after the switch prompt:

mgx8850a.7.PXM.a > delapsln <workingIndex>

Select the working line to delete by replacing <workingIndex> with the location of the working line using the format slot.bay.line. In the following example, the delapsln command removes the APS redundancy between the working line at Card 9, Bay 2, Line 1 and the protection line associated with it.

pop20one.9.AXSM.a > delapsln 9.2.1

Managing Network Clock Sources

The following sections describe how to do the following:

•View the configured clock sources

•Reconfigure network clock sources

•Delete clock sources

•Restore clock the clock source after failure

View the Configured Clock Sources

One command allows you to view the configured clock sources and determine which clock source is active. To view the configured clock sources, use the following procedure.

Step 1 Establish a configuration session at any access level.

Step 2 Enter the dspclksrcs command:

mgx8850a.7.PXM.a > dspclksrcs

The following example shows a display with neither primary nor secondary clocks configured. This is the default configuration of a switch, which uses the internal clock as the network clock source. Whenever the active clock is listed as null, the switch is using the internal clock.

pop20two.7.PXM.a > dspclksrcs

Primary clock type: null

Primary clock source: 0.0

Primary clock status: not configured

Primary clock reason: okay

Secondary clock type: null

Secondary clock source: 0.0

Secondary clock status: not configured

Secondary clock reason: okay

Active clock: internal clock

source switchover mode: non-revertive

In the following example, the display shows that both the primary and secondary clocks are configured for network clock sources. The primary clock source is coming from port 4 on the AXSM card in slot 10. The primary clock source is active. The secondary clock source is coming from port 1 on the AXSM card in slot 9.

pop20one.7.PXM.a > dspclksrcs

Primary clock type: generic

Primary clock source: 10:2.2:4

Primary clock status: ok

Primary clock reason: okay

Secondary clock type: generic

Secondary clock source: 9:1.1:1

Secondary clock status: ok

Secondary clock reason: okay

Active clock: primary

source switchover mode: non-revertive

Reconfigure Clock Sources

The procedure you use to reconfigure a clock source depends on whether or not you need to change the role of the clock source. If the clock source keeps its role as either primary or secondary, just enter a new cnfclksrc command as described in the following locations:

When reconfiguring a clock source from primary to secondary or from secondary to primary, you must delete both existing clock sources and define new clock sources. The switch will not allow you to create two primary or two secondary clock sources, and the switch will not allow you to configure the same line as both primary and secondary clock sources. After you have deleted the old clock source, you can use the appropriate procedure (referenced above) to define a new clock source.

To delete a clock source, use the delclksrc command as described in the next section.

Delete Clock Sources

Deleting a clock source deletes the definition of the clock source, not the clock source itself. You might want to delete a primary or secondary clock source definition so that you can reassign the clock source to another line.

To delete a clock source, use the following procedure.

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

Tips Use the dspclksrcs command to display the current configuration settings for the primary clock source. Having this information available makes it easier to re-enter the cnfclksrc command.

Note To change a clock source on the PXM45 from nonrevertive to revertive, enter the cnfclksrc with the option -revertive enable.

When the primary clock source is restored on the master clock node, you may have to reconfigure the primary clock sourceat each remote node where the node has switched from the primary source to the secondary source. This reconfiguration is necessary only if the local node has detected a change in the master clock source.

To determine if you need to reconfigure the primary clock at a nonmaster node, enter the dspclksrcs command. If the active clock has changed to either secondary or internal clock, you must use the cnfclksrc commandto reconfigure the primary clock source for that node.

Display the feeder configuration for a specific interface. Replace <ifnum> with the interface number.

dspfdrstat <ifnum>

Display statistics on a feeder interface. Replace <ifnum> with the interface number.

clrfdrstat <ifnum>

Clear statistics counters for a feeder interface. Replace <ifnum> with the interface number.

delfdr <ifnum>

Remove the feeder configuration from an interface. Replace <ifnum> with the interface number.

Displaying SVCs

To display active SVCs, use the following procedure.

Step 1 Establish a CLI management session at any user access level.

Step 2 Enter the following command:

popeye2.7.PXM.a > dsppncons

The following is an example report for the dsppncons command.

popeye2.7.PXM.a > dsppncons

Port VPI VCI CallRef X-Port VPI VCI CallRef Type OAM-Type

9:1.1:1 0 32 1 9:1.2:2 0 36 5 PTP No

Calling-Addr:47.666666666666666666666666.666666666666.00

Called-Addr: 47.111111111111111111111111.111111111111.64

9:1.2:2 0 36 5 9:1.1:1 0 32 1 PTP No

Calling-Addr:47.666666666666666666666666.666666666666.00

Called-Addr: 47.111111111111111111111111.111111111111.64

Managing Controllers

MGX 8850 and MGX 8950 Release 2 switches support one PNNI controller and up to two Label Switch Controllers. The controller identifies a network control protocol to the Virtual Switch Interface (VSI) that runs on the node.

Adding Controllers

To add a controller, use the following procedure.

Step 1 Establish a configuration session at any user access level.

Step 2 Enter the addcontroller command to add a controller to the node.

Note The controller type (cntrlrType) must be the same as the controller ID (cntrlrId).

<lslot>

The logical slot number on which the controller resides. For the PXM-45, lslot is 7 regardless of which card is active.

[cntrlrName}

(Optional) A string to serve as a name for the controller.

Step 3 To display all controllers on the switch and verify the added controller, enter the dspcontrollers command.

MGX8850.7.PXM.a > dspcontrollers

MGX8850 System Rev: 02.00 Jul. 30, 2000 09:39:36 GMT

MGX8850 Shelf Alarm: NONE

Number of Controllers: 1

Controller Name: PNNITWO

Controller Id: 2

Controller Location: Internal

Controller Type: PNNI

Controller Logical Slot: 7

Controller Bay Number: 0

Controller Line Number: 0

Controller VPI: 0

Controller VCI: 0

Controller In Alarm: NO

Controller Error:

Deleting Controller

To delete a controller, use the following procedure.

Step 1 Establish a configuration session at any user access level.

Step 2 Enter the delcontroller command to prevent the switch from using a specified controller.

pop20two.9.PXM45.a > addcontroller <cntrlrId>

Replace <cntrlrId> with 2 to identify PNNI controller, or 3 to identify an LSC controller.

Caution Do not execute the
delcontroller command on a card with existing connections. If you do, those connections cannot be recovered until the controller is re-added using the
addcontroller command, and the AXSM cards or the entire node is reset. Otherwise, ports remain in the provisioning state.

Step 3 To verify that the switch is no longer using the specified controller, enter the dspcontrollers command.

Note The delcontroller command does not delete the controller software, but directs the switch not to use it.

Displaying the SCT Assigned to a Card

The dspcd report displays a row labeled "Card SCT Id," which identifies the SCT assigned to the card.

pop20two.1.AXSM.a > dspcd

Front Card Upper Card Lower Card

---------- ---------- ------------

Card Type: AXSM-4-622 SMFIR-2-622 SMFIR-2-622

State: Active Present Present

Serial Number: SAK03500088 SBK0406002V SAK0346003F

Boot FW Rev: 2.0(252)A1 --- ---

SW Rev: 2.0(252)A1 --- ---

800-level Rev: M6 14 13

Orderable Part#: 800-5774-5 800-5383-1 800-5383-1

PCA Part#: 73-4504-2 73-4125-1 73-4125-1

Reset Reason:On Power up

Card SCT Id: 2

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

Displaying Port SCT Settings

To view the port SCT settings, use the following procedure.

Step 1 Establish a CLI management session at any user access level.

Step 2 Enter the following command:

pop20two.9.AXSM.a > dspportsct <bw|gen|cosb|vcThr|cosThr> <ifNum>

Select one of the options to display one of the five SCT configuration reports, and replace <ifNum> with the number of the port you want to view. Table 7-9 describes the reports for each of these options.

Note The option names are case sensitive. The switch does not recognize the vcthr option. You must enter vcThr.

Table 7-9 Options for dspcdsct Command

Option

Description

bw

Displays bandwidth and policing parameters

gen

Displays general SCT parameters

cosb

Displays COSB parameters

vcThr

Displays virtual circuit threshold parameters

cosThr

Displays COSB threshold parameters

The following sections display the reports for each of the dspportsct command options.

Table 7-10 describes the service types shown in the example, and Table 7-11 explains the SCT bandwidth and policing parameters.

Table 7-10 Service Class Template: ATM Service Types

Label

Description

CBR.1, CBR.2, & CBR.3

Constant Bit Rate. Used for connections that require a high QoS and strict CDV. The numbers 1, 2, and 3 indicate the type of ATM traffic management parameters used in policing for this service type.

VBR-RT.1, VBR-RT.2, & VBR-RT.3

Variable Bit Rate - Real Time. Used for connections that have bursty traffic and that require a strict CDV. The numbers 1, 2, and 3 indicate the type of ATM traffic management parameters used in policing for this service type.

VBR-nRT.1, VBR-nRT.2, & VBR-nRT.3

Variable Bit Rate - non-Real Time. Used for connections that do not require end to end timing. The numbers 1, 2, and 3 indicate the type of ATM traffic management parameters used in policing for this service type.

UBR.1& UBR.2

Unspecified Bit Rate. Used for connections that can allow any amount of data, up to a specified maximum, to be transmitted, but with no guarantees in terms of cell loss rate and delay. The numbers 1 and 2 indicate the type of ATM traffic management parameters used in policing for this service type.

ABR

Available Bit Rate. Used for connections that do not require timing relationships between source and destination endpoints. ABR provides no guarantees in terms of cell loss or delay, and provides only a best-effort service. Cell rates are adjusted in response to the state or condition of the network and its ability to successfully deliver data.

Table 7-11 Service Class Template: SCT Bw and Policing Parameters

Parameter

Range and Units

Description

SERV-TYPE

N.A.

The service type (i.e., CBR, VBR, ABR) to which the parameters (i.e., PCR, SCR, MCR) in this table apply.

PCR

0 to 1000000

Peak Cell Rate. The peak (maximum) cell rate for a connection using the service type. This value is a percentage of the maximum cell rate for the logical interface. 1000000 is equal to 100%.

SCR

0 to 1000000

Sustained Cell Rate. The sustained cell rate for a connection using this service type. This value is a percentage of the maximum cell rate for the logical interface. 1000000 is equal to 100%.

MCR

0 to 1000000

Minimum Cell Rate. The minimum cell rate for a connection using the service type. This value is a percentage of the maximum cell rate for the logical interface. 1000000 is equal to 100%.

MBS

1 to 5000000

Maximum Burst Size. Used for policing.

CDVT

0 to 5 microseconds

Cell Delay Variation Tolerance. Used for policing. For PNNI, the CDVT default value from the SCT is not used. Use dspcdvtdft.

ICR

0 to 1000000

Initial Cell Rate. The cell rate used to begin a transmission on a connection that has been idle for a configured period of time. This value is a percentage of the PCR for the logical interface. 1000000 is equal to 100%. (This parameter is used only on ABR service type connections.)

Port SCT General Parameters (dspportsctgen)

The following report appears when you enter the dspportsct gen command:

Generic Cell Rate Algorithm - Bucket 1. In ATM, an algorithm that defines conformance with respect to the traffic contract of the connection. For each cell arrival, the GCRA determines whether the cell conforms to the traffic contract.

Note If UPC-Enable is set to disable, this object is not used.

Choose one of the following options to indicate how cells that fail the first bucket of the policer should be handled:

1 - Discard

2 - Set CLP bit

3 - Set CLP of untagged cells, discard tagged cells.

GCRA-2

1 to 3

Generic Cell Rate Algorithm - Bucket 2. In ATM, an algorithm that defines conformance with respect to the traffic contract of the connection. For each cell arrival, the GCRA determines whether the cell conforms to the traffic contract.

Note If UPC-Enable is set to disable, this object is not used.

Choose one of the following options to indicate how cells that fail the second bucket of the policer should be handled:

The service type (i.e., CBR, VBR, ABR) to which the parameters (i.e., EFCI, CLP_HI, EPD0) in this table apply.

VC THRESH TBL IDX

—

An index number into the queue engine VC threshold table.

PACKET MODE

1 - Enabled2 - Disabled

Enables or disables Packet Discard Mode on the connection.

MAX_CELL THRESH

0 to 5000000 microseconds

The VcMax threshold for CLP (0+1) cells in microseconds.

EFCI

0 to 1000000

Explicit Forward Congestion Indication. The VC EFCI discard threshold. This value is a percentage of MAX_CELL THRESH. 1000000 is equal to 100%.

CLP_HI

0 to 1000000

Cells Loss Priority - High. The high hysteresis threshold at which CLP (1) cells will be discarded. The cells will continue to be discarded until the CLP_LO threshold is reached. This value is a percentage of MAX_CELL THRESH. 1000000 is equal to 100%.

EPD0

0 to 1000000

Early Packet Discard 0. The maximum threshold for CLP(0+1) cells. This value is a percentage of the MAX_CELL THRESH for the connection. 1000000 is equal to 100%.

Class of Service Scaling Class. Indicates which of the four Scaling Class Tables (1 to 4, see Table 7-15) to use for a connection. Each table is for a specific service category and has an index of 16 entries. Each index entry contains a percentage by which to scale traffic on a connection to reduce CoS buffer congestion. The hardware generates the index and selects the entries as needed. Each entry is the ratio of the COSB cell count to the COSB maximum threshold. CoS scaling occurs when the CoSB cell count is approximately 50% of the CoSB max threshold.

SCALING Log-If

1 to 4

Logical Port Scaling Class. Indicates which of the four Scaling Class Tables (1 to 4, see Table 7-16) to use on a logical port. Each table is for a specific service category and has an index of 16 entries. Each index entry contains a percentage by which to scale traffic on a connection on a logical port to reduce congestion. The hardware generates the index and selects the entries as needed. Each entry is the ratio of the interface cell count to the interface maximum threshold. Interface scaling occurs when the interface cell count is approximately 50% of the interface max threshold.

Table 7-15 Class of Service (CoS) Scaling Table

Index

Scaling Class Table #1 (CBR)

Scaling Class Table #2 (VBR)

Scaling Class Table #3 (ABR)

Scaling Class Table #4 (UBR)

0

100.00%

100.00%

100.00%

100.00%

1

100.00%

100.00%

100.00%

100.00%

2

100.00%

100.00%

100.00%

100.00%

3

100.00%

100.00%

100.00%

100.00%

4

100.00%

100.00%

100.00%

100.00%

5

100.00%

100.00%

100.00%

100.00%

6

100.00%

100.00%

100.00%

67.00%

7

100.00%

100.00%

100.00%

34.00%

8

100.00%

100.00%

50.00%

20.00%

9

100.00%

50.00%

25.00%

12.00%

10

100.00%

25.00%

12.00%

8.00%

11

100.00%

12.00%

6.00%

4.00%

12

100.00%

6.00%

3.00%

2.50%

13

100.00%

3.00%

1.30%

1.40%

14

100.00%

1.30%

0.75%

1.00%

15

100.00%

0.50%

0.50%

0.50%

Table 7-16 Logical Interface Scaling Table

Index

Scaling Class Table #1 (CBR)

Scaling Class Table #2 (VBR)

Scaling Class Table #3 (ABR)

Scaling Class Table #4 (UBR)

0

100.00%

100.00%

100.00%

100.00%

1

100.00%

100.00%

100.00%

100.00%

2

100.00%

100.00%

100.00%

100.00%

3

100.00%

100.00%

100.00%

100.00%

4

100.00%

100.00%

100.00%

100.00%

5

100.00%

100.00%

100.00%

100.00%

6

100.00%

100.00%

100.00%

67.00%

7

100.00%

100.00%

100.00%

34.00%

8

100.00%

100.00%

50.00%

20.00%

9

100.00%

50.00%

25.00%

12.00%

10

100.00%

25.00%

12.00%

8.00%

11

100.00%

12.00%

6.00%

4.00%

12

50.00%

6.00%

3.00%

2.50%

13

25.00%

3.00%

1.30%

1.40%

14

6.00%

1.30%

0.75%

1.00%

15

0.50%

0.50%

0.50%

0.50%

Port SCT COSB Threshold Parameters (cosThr)

The following report appears when you enter the dspportsct cosThr command:

The service type (i.e., CBR, VBR, ABR) to which the parameters (i.e., EFCI, CLP_HI, EPD0) in this table apply.

COSB THRESH TBL IDX

—

An index number into Queue Engine COSB threshold table.

MAX_CELL THRESH

0 to 5000000 microseconds

The maximum threshold, in microseconds, beyond which all CLP (0+1) cells must be dropped.

EFCI

0 to 1000000

Explicit Forward Congestion Indication. The threshold level for congestion indication for ABR traffic using CI control. This threshold is a percentage of the MAX_CELL THRESH for the connection. 1000000 is equal to 100%.

CLP_HI

0 to 1000000

Cells Loss Priority High. The maximum number of cells that can be queued in the buffer. CLP(1) cells that exceed this threshold are discarded. This threshold is a percentage of the MAX_CELL THRESH for the connection. 1000000 is equal to 100%.

EPD0

0 to 1000000

Early Packet Discard 0. The maximum number of cells that can be queued in the buffer in packet mode. Any CLP(0+1) cells that exceed this threshold, will be discarded. This threshold is a percentage of the MAX_CELL THRESH for the connection. 1000000 is equal to 100%.

CLP_LO /EPD1

0 to 1000000

Cell Loss Priority Low/ Early Packet Discard 1. The threshold at which CLP (0+1) cells that exceed this threshold are discarded. This threshold is a percentage of the MAX_CELL THRESH for the connection. 1000000 is equal to 100%.

RED

0 to 1000000

Random Early Discard. The threshold at which the COSB Random Early Discard is activated. This threshold is a percentage of the MAX_CELL THRESH for the connection. 1000000 is equal to 100%.

RED PROB FACTOR

0 to 15

RED Probability Factor. The mantissa value of probability for maximum discard when RED is activated. Determined as 1/2^<value>.

Displaying Card SCT Settings

To view the card SCT settings, use the following procedure.

Step 1 Establish a CLI management session at any user access level.

Step 2 Enter the following command:

pop20two.9.AXSM.a > dspcdsct <bw|gen|cosb|vcThr|cosThr>

Select one of the options to display one of the five SCT configuration reports. Table 7-18 describes the reports for each of these options. The following section lists sample reports for each of these options.

Note The option names are case sensitive. For example, the switch does not recognize the vcthr option. You must enter vcThr.

Table 7-18 Options for dspcdsct Command

Option

Description

bw

Displays bandwidth and policing parameters.

gen

Displays general SCT parameters.

cosb

Displays COSB parameters.

vcThr

Displays virtual circuit threshold parameters.

cosThr

Displays COSB threshold parameters.

The following sections display the reports for each of the dspcdsct command options.

Note For descriptions of the Card SCT parameters refer to Service Class Template Tables 7-6 through 7-11 in the Displaying Port SCT Settings earlier in this chapter.

Viewing an ATM Port Configuration

To view the configuration of an ATM line or trunk port, use the following procedure.

Step 1 Establish a CLI management session at any user access level.

Step 2 To display a list of the ports already configured on the AXSM card, enter the following command:

mgx8850a.10.AXSM.a > dspports

This command displays all configured ports on the AXSM card. Port numbers are listed in the ifNum (interface number) column. The interfaces listed include UNI and NNI ports. Note the number of the port for which you want to view the configuration.

Step 3 To display the port configuration, enter the following command:

mgx8850a.10.AXSM.a > dspport <ifNum>

Replace ifNum with the number assigned to the port during configuration. The following example shows the report for this command:

pop20two.9.AXSM.a > dspport 2

Interface Number : 2

Line Number : 2.1

Admin State : Up Operational State : Down

Guaranteed bandwidth(cells/sec): 100000 Number of partitions: 1

Maximum bandwidth(cells/sec) : 100000 Number of SPVC : 0

ifType : NNI Number of SVC : 0

SCT Id : 6

VPI number(VNNI only) : 0

Managing Partitions

The following sections describe how to display, change, and delete a resource partition.

Displaying a Resource Partition Configuration

To display a list of resource partitions or a resource partition configuration, use the following procedure.

Step 1 Establish a CLI management session at any user access level.

Step 2 To display a list showing the resource partitions on this card, enter the following command:

Partition identification number. Enter a number in the range of 1 to 20. Partition ID 1 is reserved for PNNI. On an AXSM card, this number must be the same for all ports that use the PNNI controller.

egrminbw

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 and MPLS 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 and MPLS 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-request, 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 and MPLS 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 and MPLS 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.

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

minVci

Minimum VCI number for this port. For OC-48 AXSM 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.

maxVci

Maximum VCI number for this port. For OC-48 AXSM 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.

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: 65535 per line to a total of 65535 per back card

OC3 lines: 32767 per line to a total of 65535 per back card

OC12 lines: 32767 per line to a total of 65535 per back card

OC48 lines: 131071 per line to a total of 131071 per back card

Note that the maximum number of connections is 128K (131,071) for the AXSM front card and the OC48 back card. For the other AXSM back cards, which are used in pairs (upper and lower bays), the maximum number of connections is 64K (65535), which totals 128K for the front 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>.

Step 4 To display the changed partition configuration, use the dsppart command as described in the previous section.

Note The current software release does not support dynamic changes to partitions. To begin using changes to a resource partition, you need to delete the controller and then add the controller as described in the rest of this procedure.

Step 5 Display the available controllers with the dspcontrollers command, and write down the controller settings for the controller you are about to delete. For example:

pop20two.7.PXM.a > dspcontrollers

pop20two System Rev: 02.01 Feb. 08, 2001 19:10:33 PST

MGX8850 Node Alarm: NONE

Number of Controllers: 2

Controller Name: PNNI Controller

Controller Id: 2

Controller Location: Internal

Controller Type: PNNI

Controller Logical Slot: 7

Controller Bay Number: 0

Controller Line Number: 0

Controller VPI: 0

Controller VCI: 0

Controller In Alarm: NO

Controller Error:

Controller Name: MPLS Controller

Controller Id: 3

Controller Location: Internal

Controller Type: LSC

Controller Logical Slot: 7

Controller Bay Number: 0

Controller Line Number: 0

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

pop20two System Rev: 02.01 Feb. 08, 2001 19:10:33 PST

MGX8850 Node Alarm: NONE

Controller VPI: 0

Controller VCI: 0

Controller In Alarm: NO

Controller Error:

Step 6 Use the delcontroller command to delete the controller that corresponds to the resource partition you modified. For example:

pop20two.7.PXM.a > delcontroller 3

All Ports and Connections

on this controller will be deleted.

delcontroller: Do you want to proceed (Yes/No)? y

Step 7 To register the resource partition changes, add the deleted controller with the addcontroller command. For example:

pop20two.7.PXM.a > addcontroller 3 i 3 7 "MPLS Controller"

Step 8 To verify that the controller was added correctly, enter the dspcontrollers command.

To add an MPLS partition on port which has a minimum VCI value of 32, perform one of the following options:

•Add the MPLS controller, and then add the TDP sig vc using a VPI/VCI pair within its partition's range.

•Enter the dnport and cnfpart commands to change the minimum VCI to 35 for all partitions on the port.

Deleting a Resource Partition

To delete a resource partition, you must do the following:

•Delete any connections that are using the affected port

•Bring down the affected port

The following procedure explains how to delete a resource partition.

Step 1 Establish a configuration session using a user name with CISCO_GP privileges.

Step 2 To display a list showing the partitions for this card, enter the dspparts command.

Step 3 Note the interface number and partition number for the resource partition you want to delete.

Step 4 To display the active connections, enter the following command:

Step 5 Review the dspcons command display to see if the interface to which the partition is assigned is being used by a connection. The Identifier column identifies the interface, VPI, and VCI for the connection in the format: if.VPI.VCI. If the interface is in use, note the VPI and VCI values of all connections that use the interface, as you will need these to delete the connections.

Step 6 Delete each connection that uses the interface by entering the following command:

mgx8850a.10.AXSM.a > delcon <ifNum> <VPI> <VCI>

Step 7 Bring down the interface by entering the following command:

mgx8850a.10.AXSM.a > dnport <ifNum>

Step 8 Delete the resource partition by entering the following command:

mgx8850a.10.AXSM.a > delpart <ifNum> <partId>

Replace ifnum with the interface number of the port, and replace partitionID with the partition number assigned to the port.

Step 9 To verify that the partition has been deleted, enter the dspparts command to display a list of partitions for the card.

Removing Static ATM Addresses

If you create a static ATM address and later want to remove that address, use the following procedure to delete it.

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

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

Port identifier in the format slot:bay.line:ifnum. These parameters are described in Table 7-1.

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.

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

Step 4 To verify that the static address has been deleted, enter the following command:

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

Replace <portid> with the port address using the format slot:bay.line:ifnum These parameters are described in Table 7-1.

Configuring VPI and VCI Ranges for SVCs and SPVCs

When you add a partition to a port, you define the minimum and maximum VPIs and VCIs for that port. These VPIs and VCIs become available for all services unless you make additional configuration changes. If this configuration is acceptable for your installation, you can skip this section. You are not required to configure VPI and VCI ranges for SVCs and SPVCs.

The MGX 8850 and MGX 8950 switches allow you to define the minimum and maximum values for the following:

•SVCC VPIs

•SVCC VCIs

•SPVC VPIs

To configure VPI and VCI usage for connections on a specific port, use the following procedure.

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

Step 2 To display a list of PNNI ports, enter the dsppnports command.

Step 3 Use the following command to bring down the PNNI port you want to configure:

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

A PNNI port is automatically brought up when you add it. You must bring down the port before you can change the port range. Replace <portid> using the format slot:bay.line:ifNum. Table 7-1 describes these parameters.

The only required parameter for this command is the <portid> parameter, but the command serves no purpose if you enter it without options. If you include some options with the command and omit others, the omitted options remain set to the last configured values. Table 7-21 lists and describes the options and parameters for this command.

Step 6 To display the PNNI port range for a port, enter the following command:

popeye2.7.PXM.a > dsppnportrange <portid>

After you enter this command, the switch displays a report similar to the following:

pop20two.7.PXM.a > dsppnportrange 1:2.1:2

minSvccVpi: 0 maxSvccVpi: 4095

minSvccVci: 35 maxSvccVci: 65535

minSvpcVpi: 1 maxSvpcVpi: 4095

Managing Load Sharing

When redundant PXM45 cards are used, load sharing enables traffic routing through the switch fabric on both PXM45 cards, doubling the capacity of the switch. Load sharing is enabled by default and should only be disabled for testing or debugging purposes.

The switch provides two options for load sharing management: Auto Shutdown and Plane Alarm Threshold. The switch fabric on each PXM45 is made up of 3 switch planes that each contain links to 14 slots within the switch chassis. When the Auto Shutdown feature is enabled and one of these internal links fails, that link is automatically shut down, and the card in the affected slot must use a link to another switch plane. If Auto Shutdown is not enabled and a link goes bad, the affected card slot can still attempt to use that link.

The Plane Alarm Threshold option defines the threshold at which a switch plane is declared bad and reported as such. When a switch plane is reported bad, the PXM45 on which the switch plan resides should be replaced.

The following procedures describe how to view the load sharing option settings and how to change them.

Displaying Load Sharing Status

To display whether the status of the load sharing options, enter the dspxbarmgmt command. The following example shows the display for this command.

pop20two.7.PXM.a > dspxbarmgmt

pop20two System Rev: 02.01 Dec. 07, 2000 18:36:47 GMT

MGX8850 Node Alarm: MAJOR

Load Sharing: Enable

Auto Shutdown: Disable

Plane Alarm Threshold: 3

The Load Sharing and Auto Shutdown lines shows the option status as Enable or Disable. The Plane Alarm Threshold line displays a number from 1 to 32. On PXM45 cards, the maximum number of slots to which each plane can connect is 14.

Changing Load Sharing Options

To change the load sharing options, enter the cnfxbarmgmt command as described in the following procedure.

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

Step 2 Display the current configuration setting by entering the dspxbarmgmt command.

Step 3 Set the load sharing options by entering the cnfxbarmgmt command as follows:

If you do not want to change the setting, enter the value that corresponds to the current setting displayed with the dspxbarmgmt command.

autoShutdown

Enables or disables the Auto Shutdown feature. Enter 0 to disable this feature, or enter 1 to automatically shut down a failed link between a switch plane and a card slot.

If you do not want to change the setting, enter the value that corresponds to the current setting displayed with the dspxbarmgmt command.

planeAlarmThresh

Defines when a switch plane should be reported as bad. Set the threshold to the number of failed links (between a switch plane and the card slots it services) that exceeds your acceptable limit. The default threshold is 3. The PXM45 card supports up to 14 links.

If you do not want to change the setting, enter the value that appears when you enter the dspxbarmgmt command.

Starting and Managing Telnet Sessions to Other Switches

The MGX 8850 and MGX 8950 switches support Telnet sessions between switches. For example, you can start a CLI session with one switch, Telnet to a second switch to view configuration information, then switch back to the first switch and continue that CLI session. Each switch supports up to 15 simultaneous Telnet sessions, and you can Telnet across multiple switches. For example, you can establish a CLI session on switch A, Telnet to switch B, and then Telnet from switch B to switch C. The following sections describe:

Starting a Telnet Session

You must enter an IP address with the telnet command as shown in the following example:

pop20one.7.PXM.a > telnet 172.29.52.88

Trying 172.29.52.88...

Connected to 172.29.52.88

Login: cisco

password:

The -E option allows you to specify an escape character that takes you back to the previous session. For example, if you have Telnetted from Switch A to Switch B to Switch C, you can use this escape character to return to Switch B. The default escape character is Q. To change this, specify an alternate escape character withe the -E option when you start a Telnet session. There should be no space character between the -E and the escape character.

The -R option allows you to specify an escape character that displays a trace of your Telnet activity. For example, if you have Telnetted from Switch A to Switch B to Switch C, you can use this escape character to display the Telnet routes from A to B and from B to C. The default escape character is g. To change this, specify an alternate escape character withe the -R option when you start a Telnet session. There should be no space character between the -R and the escape character.

The tcpPort option allows you to specify a destination port for the Telnet session. If you omit this option, the Telnet session uses the default Telnet port.

Returning to a Previous Session

After you Telnet from one switch to another, enter the bye command or the exit command to close the current session and return to the previous session. For example, if you have Telnetted from Switch A to Switch B to Switch C, the bye command will terminate the session on Switch C and display the session on Switch B.

Returning to the Original CLI Session

After you Telnet from switch to switch, enter the escape character to close all Telnet sessions and return to the original CLI session. The default escape sequence is Escape, Q (uppercase Q). Press the Escape key first, then press Shift-Q. If you specified an alternate escape character when opening Telnet sessions, enter that character in place of Q.

For example, if you Telnet from Switch A to Switch B to Switch C, the escape character sequence closes the Telnet sessions on Switches B and C, and displays the CLI session on Switch A.

Displaying a Telnet Trace

After you Telnet from switch to switch, enter the trace escape character to display a list of connections you have established between switches. The default escape sequence is Escape, g (lowercase g). Press the Escape key first, then press g. If you specified an alternate escape character when opening Telnet sessions, enter that character in place of g.

The following example shows a sequence of Telnet sessions and the trace that documents the sequence: