Table Of Contents

Switch Operating Procedures

Managing the Configuration Files

Saving a Configuration

Clearing a Switch Configuration

Clearing a Slot Configuration

Restoring a Saved Configuration

Managing ILMI

Enabling and Disabling ILMI on a Port

Displaying the ILMI Port Configuration

Displaying and Clearing ILMI Management Statistics

Deleting ILMI Prefixes

Determining the Software Version Number from Filenames

Displaying Software Revisions for Cards

Displaying Software Revisions in Use

Displaying Software Revisions for a Single Card

Managing Redundant Cards

Displaying Redundancy Status

Switching Between Redundant PXM Cards

Switching Between Redundant Service Modules

Removing Redundancy Between Two Cards

Switching Between Redundant RPM Cards

Managing Redundant APS Lines

Preparing for Intercard APS

Configuring Intercard APS Lines

Displaying APS Line Information

Modifying APS Lines

Switching APS Lines

Removing APS Redundancy Between Two Lines

Troubleshooting APS Lines

Managing Network Clock Sources

Synchronizing TOD Clocks

Deleting an Existing SNTP Server

Displaying an SNTP Server

Displaying the Current SNTP Configuration

Managing NCDP Clock Sources

Enabling NCDP on a Switch

Configuring an NCDP Clock Source

Configuring an NCDP Port

Displaying NCDP Information

Display the Current NCDP Root Clock

Display A Specific NCDP Clock Source

Display All NCDP Clock Sources

Display All NCDP Ports on the Switch

Display An NCDP Port

Deleting an NCDP Clock Source

Managing Manually Configured Clocks Sources

View the Configured Clock Sources

Reconfigure Manual Clock Sources

Delete Manual Clock Sources

Restore a Manual Clock Source After Failure

Displaying SVCs

Managing Controllers

Adding Controllers

Deleting a Controller

Viewing an ATM Port Configuration

Managing PXM1E Partitions

Displaying a PXM1E Resource Partition Configuration

Changing a PXM1E Resource Partition Configuration

Deleting a PXM1E Resource Partition

Removing Static ATM Addresses

Configuring VPI and VCI Ranges for SVCs and SPVCs

Managing Priority Routing

Establishing Priority Routing on a Node

Configuring Priority Routing on a Connection

Modifying SPVC Priority Routing Configuration

Managing Path and Connection Traces

Displaying Path and Connection Traces

Clearing a Call at the Destination Node

Managing Load Sharing

Displaying Load Sharing Status

Changing Load Sharing Options

Starting and Managing Telnet Sessions to Other Switches

Starting a Telnet Session

Returning to a Previous Session

Returning to the Original CLI Session

Displaying a Telnet Trace

Verifying PXM Disk Data

Displaying the Contents of the Disk Verification Utility Log File

Troubleshooting Active and Standby Card Disk Discrepancies

Configuring a Line Loopback

Configuring Loopback Line Tests on PXM1E and AXSM Cards

Configuring a Line Loopback on a CBSM

Managing Bit Error Rate Tests

Configuring a Bit Error Rate Test

Deleting a Configured Bit Error Rate Test

Diagnostics Support on PXM1E and AXSM Cards

Configuring Offline and Online Diagnostics Tests on PXM1E and AXSM Cards

Enabling Online and Offline Diagnostics Tests on All Cards in a Switch

Displaying Online and Offline Diagnostics Test Configuration Information

Displaying Online Diagnostic Errors

Displaying Offline Diagnostic Errors

Enabling and Disabling IMA Group ATM Cell Layer Parameters

Maintaining IMA

Displaying IMA Groups

Displaying IMA Links

Deleting an IMA Group

Deleting an IMA Link

Restarting an IMA Group

Switch Operating Procedures

---

This chapter describes procedures you can use to manage the Cisco MGX 8850 (PXM1E/PXM45), Cisco MGX 8950, and Cisco MGX 8830 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, enter 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 Cisco MGX 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 To save the configuration, enter the saveallcnf command:

mgx8830a.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 3 Read the prompt that appears. Press Y if you want to continue, and then 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:

mgx8830a.1.PXM.a > saveallcnf

The 'saveallcnf' command can be time-consuming. The shelf

must not provision new circuits while this command is running.

Do not run this command unless the shelf configuration is stable

or you risk corrupting the saved configuration file.

ATTENTION PLEASE NOTE: 

        -> If you want to abort the save, please use abortallsaves CLI.

        If you use cntrl-C, you will risk hanging the whole telnet

        session and may lose capability of being able to perform

        subsequent saves

        -> The save command will only store the

        2 most recent saved files in C:/CNF directory. 

        If you have 2 or more files already saved in C:/CNF,

        the older ones will be deleted by the current save,

        keeping the 2 most recent.

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

saveallcnf: shelf configuration saved in C:/CNF/pop20one_01_200006151550.zip.

---

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 PXM Hard Drive card fails.

---

---

Clearing a Switch 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 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.

Clearing a Slot Configuration

To clear the entire configuration on both the RAM and the disk for a specified service module slot, enter the clrsmcnf command. If you enter clrsmcnf <slot> without any options, only the RAM and disk will be cleared. If you enter clrsmcnf <slot> -all, card specific information will be cleared along with the RAM and disk.

The service module will go into reboot, and then it will come back up in the previous revision.

Enter the dspcd command to verify whether the clrsmcnf command was successful or not.

---

Note The clrsmcnf command does not work on redundant cards. Enter the delred command to delete redundancy on a pair prior to running the clrsmcnf command.

---

---

Caution When replacing T1 or T3 cards are replaced with E1 or E3 cards, or vice versa, you must enter the clrsmcnf command on the appropriate slot before you install the replacement card.

---

Restoring a Saved Configuration

You can restore a configuration if all of the following statements 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 Cisco MGX 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.

---

---

Tip Enter the cd command to navigate the C:/CNF directory, and enter the ll command to display the directory contents. For information on transferring files to and from the switch, see Appendix A, "Downloading and Installing Software Upgrades."

---

Step 3 To restore a saved configuration file, enter the restoreallcnf command.

mgx8830a.1.PXM.a > restoreallcnf -f filename

---

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 Cisco MGX switches provide several commands that you can use to enable or disable ILMI on a port. For instructions on enabling or disabling ILMI from a PXM1E card, see the "Configuring ILMI on a Port" section in Chapter 11, "Provisioning PXM1E Communication Links." For instructions on enabling or disabling ILMI from a AXSM card, see refer to the Cisco ATM Services (AXSM) Software Configuration Guide and Command Reference for MGX Switches.

To enable or disable ILMI from the PXM 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:

mgx8830a.1.PXM.a >cnfilmienable <portid> <no | yes>

Replace portid using the format slot:bay.line:ifNum. Table 13-1 describes these parameters.

Enter yes to enable ILMI on the port, or enter no to disable ILMI.

Table 13-1 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 2 for a PXM1E, and 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 31 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.

Step 3 To verify the ILMI status change, re-enter the dsppnports 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 a PXM1E or AXSM card, enter the dspilmis command. The following example shows the dspilmis command report:

mgx8830a.1.PXM.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 

    3    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 13-2 describes each of the report columns.

Table 13-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	VPI for the ILMI signaling VCC.
Sig Vci	VCI for the ILMI signaling VCC.
Ilmi Trap	Indicates whether ILMI traps are enabled (On) or disabled (Off) for this port.
S:Keepalive Interval	Keep alive interval. The range is 1-65535 seconds.
T:conPoll Interval	Polling interval for T491 in the range 0-65535 seconds.
K:conPoll InactiveFactor	Polling interval K in the range 0-65535 seconds.

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

mgx8830a.1.PXM.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 13-2 describes each of the columns that appear in the command report.

mgx8830a.1.PXM.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, enter the dsppnports command at the PXM prompt as shown in the following example:

mgx8830a.1.PXM.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:  #Total:

p2p:   0        0        0        0        0        0        0      

p2mp:  0        0        0        0        0        0        0      

                                                       Total=0      

Summary of total configured SPVC endpoints

Type   #SpvcCfg: #SpvpCfg:

p2p:   0         0      

p2mp:  0         0      

Per-port status summary

PortId         IF status         Admin status       ILMI state       #Conns

7.35           up                up                 Undefined        0       

7.36           up                up                 Undefined        0       

7.37           up                up                 Undefined        0       

7.38           up                up                 Undefined        0       

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

10:1.1:1       up                up                 UpAndNormal      0       

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. In other words, the EnableNotUp status 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, enter the dsppnilmi command at the PXM prompt as follows:

mgx8830a.1.PXM.a > dsppnilmi <portid>

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

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

---

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:

mgx8830a.1.PXM.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.

mgx8830a.1.PXM.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:

mgx8830a.1.PXM.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.

mgx8830a.1.PXM.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.

---

Deleting ILMI Prefixes

The following procedure describes how to delete an ILMI address prefix from a port.

---

Note The procedure for adding ILMI prefixes is described in "Configuring ILMI Dynamic Addressing" in Chapter 11, "Provisioning PXM1E Communication Links."

---

---

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

Step 2 To view the ILMI prefixes assigned to a port, enter the dspprfx command as follows:

mgx8830a.1.PXM.a > dspprfx <portid>

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

mgx8830a.1.PXM.a > dspprfx 10:2.2:4

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 3 To prepare for deleting an ILMI prefix, down the port to be configured with the dnpnport command. For example:

mgx8830a.1.PXM.a > dnpnport 10:2.2:4

Step 4 Enter the following command to delete an ATM prefix for a port:

mgx8830a.1.PXM.a > delprfx <portid> <atm-prefix>

Replace portid using the format slot:bay.line:ifNum. Table 13-1 describes these parameters.

Replace atm-prefix with the 13-byte ATM address prefix in use.

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

mgx8830a.1.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:

•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 (PXM1E/PXM45), Cisco MGX 8950, and Cisco MGX 8830, Software Version 4.0.00. 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:

mgx8830a.1.PXM.a > cd C:/FW

---

Note Remember that UNIX directory and filenames are case sensitive.

---

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

mgx8830a.1.PXM.a > ll

The following example shows the ll command display:

mgx8830a.1.PXM.a > ll

-rwxrwxrwx  1 0       0          1367596 Mar 12 18:27 ausm_8t1e1_020.000.000.106-D.fw 

-rwxrwxrwx  1 0       0           967736 Apr 11 18:43 pxm1e_002.001.050.000-D_diag.fw 

-rwxrwxrwx  1 0       0          6476612 Mar 29 23:51 pxm1e_003.000.000.000-D_mgx.fw 

-rwxrwxrwx  1 0       0          1123104 Mar  6 18:26 pxm1e_003.000.000.000-D_diag.fw 

-rwxrwxrwx  1 0       0          6412036 Feb 27 19:39 pxm1e_003.000.000.206-P1_m30.fw 

-rwxrwxrwx  1 0       0          3810744 Feb 26 23:54 vism_8t1e1_003.000.000.051-I.fw 

-rwxrwxrwx  1 0       0          3811160 Feb 26 19:21 vism_8t1e1_003.000.000.050-I.fw 

-rwxrwxrwx  1 0       0          1085856 Jan  5  2000 pxm1e_001.001.050.005-A_diag.fw 

-rwxrwxrwx  1 0       0          6327220 Feb  1 00:02 pxm1e_003.000.000.185-P2_m30.fw 

-rwxrwxrwx  1 0       0          1015768 Feb  1 00:02 pxm1e_003.000.000.185-P2_bt.fw 

-rwxrwxrwx  1 0       0          6331172 Jan 29 00:24 pxm1e_003.000.000.185-A_mgx.fw 

-rwxrwxrwx  1 0       0           878976 Jan  1  2098 pxm1e_002.001.050.007-A_bt.fw 

-rwxrwxrwx  1 0       0           725744 Mar 12 18:27 cesm_8t1e1_020.000.000.106-D.fw 

-rwxrwxrwx  1 0       0           867564 Mar 12 18:27 frsm_8t1e1_020.000.000.106-D.fw 

-rwxrwxrwx  1 0       0          1004548 Mar 12 18:28 frsm_vhs_020.000.000.106-D.fw 

-rwxrwxrwx  1 0       0          6524548 May  3 00:38 pxm1e_003.000.000.000-D_m30.fw 

-rwxrwxrwx  1 0       0          6505668 Apr 29 23:24 pxm1e_003.000.000.026-P4_m30.fw 

In the file system : 

    total space :  819200 K bytes

    free  space :  786279 K bytes

---

Note The above example was created during product development. The filenames may be different from those in use on your switch. For the latest list of filenames, refer to the Release Notes for Cisco MGX 8850 (PXM1E/PXM45), Cisco MGX 8950, and Cisco MGX 8830, Software Version 4.0.00.

---

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

Figure 13-1 Filename Format for Released Software

Filenames that include "_mgx" are for runtime PXM firmware, and filenames that include "_bt" are for boot firmware. Service module 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 13-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 13-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 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.

mgx8830a.1.PXM.a > runrev

ERR: Syntax: runrev <slot> <revision> 

        slot -- optional; value: 15,16,31,32

           revision - revision number. E.g.,

                      2.0(1)

                      2.0(1.255)

                      2.0(0)I  or 2.0(0)A

                      2.0(0)P1 or 2.0(0)P2

                      2.0(0)P3 or 2.0(0)P4

                      2.0(0)D

                      2.0(1.166)I  or 2.0(1.166)A

                      2.0(1.166)P1 or 2.0(1.166)P2

                      2.0(1.166)P3 or 2.0(1.166)P4

The first example above, 2.0(1), is for released firmware version 2.0, maintenance release 1. The second example, 2.0(1.255), is for patch 255 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 13-3 shows some example filenames and the correct version numbers to use with the revision management commands.

Table 13-3 Determining Firmware Version Numbers from Filenames 

Filename	Version Number for Revision Management Commands
ausm_8t1e1_020.000.001.047.fw	20.0(1.47)
axsm_002.000.001.001.fw	2.0(1.1)
axsm_002.000.016-D.fw	2.0(16)D
cesm_8t1e1_020.000.001.047.fw	20.0(1.47)
frsm_8t1e1_020.000.001.047.fw	20.0(1.47)
frsm_vhs_020.000.001.047.fw	20.0(1.47)
pxm1e_003.000.000.000_bt.fw	3.0(0.0)
pxm1e_003.000.001.000_bt.fw	3.0(1.0)
pxm1e_003.000.001-D_mgx.fw	3.0(1)D
pxm1e_003.000.014-A1_bt.fw	3.0(14)A1
pxm45_002.000.000.000_bt.fw	2.0(0.0)
pxm45_002.000.001.000_bt.fw	2.0(1.0)
pxm45_002.000.001-D_mgx.fw	2.0(1)D
pxm45_002.000.014-A1_bt.fw	2.0(14)A1
vism_8t1e1_003.000.000.103-I.fw	3.0(0.103)

---

Displaying Software Revisions for Cards

This section describes how to display software revision information for the cards in your switch.

Displaying Software Revisions in Use

To display the boot and runtime software version in use on every card in the switch, enter the dsprevs command as shown in the following example:

mgx8830a.1.PXM.a > dsprevs

Unknown                          System Rev: 03.00   May. 04, 2002 20:24:57 GMT

MGX8830                                              Node Alarm: MINOR

Phy. Log. Inserted       Cur Sw              Boot FW             

Slot Slot Card           Revision            Revision            

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

01   01   PXM1E-4-155    3.0(0.26)P4         3.0(0.26)A          

02   01   PXM1E-4-155    3.0(0.26)P4         3.0(0.26)A          

03   03   ---            ---                 ---                 

04   04   FRSM_2CT3      ---                 ---                 

05   05   FRSM_2CT3      ---                 ---                 

06   06   CESM_8T1       ---                 ---                 

07   07   SRM_3T3        ---                 ---                 

08   08   ---            ---                 ---                 

09   09   ---            ---                 ---                 

10   10   ---            ---                 ---                 

11   11   FRSM_8T1       ---                 ---                 

12   12   ---            ---                 ---                 

13   13   FRSM_8T1       ---                 ---                 

14   07   SRM_3T3        ---                 ---              

To display the upgrades status of the runtime software on all switch cards, enter the dsprevs -status command as shown in the following example:

mgx8830a.1.PXM.a > dsprevs -status

Corvette                         System Rev: 03.00   Jun. 07, 2002 19:12:23 GMT

MGX8830                                              Node Alarm: MINOR

Phy. Log. Cur Sw           Prim Sw          Sec Sw           Rev Chg           

Slot Slot Revision         Revision         Revision         Status            

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

01   01   3.0(0.83)D       3.0(0.83)D       3.0(0.83)D       ---               

02   01   3.0(0.83)D       3.0(0.83)D       3.0(0.83)D       ---               

03   03   ---              ---              ---              ---               

04   04   20.0(1.44)A      20.0(1.44)A      20.0(1.44)A      ---               

05   04   20.0(1.44)A      20.0(1.44)A      20.0(1.44)A      ---               

06   06   20.0(1.44)A      20.0(1.44)A      20.0(1.44)A      ---               

07   07   ---              ---              ---              ---               

08   08   ---              ---              ---              ---               

09   09   ---              ---              ---              ---               

10   10   ---              ---              ---              ---               

11   11   20.0(1.44)A      20.0(1.44)A      20.0(1.44)A      ---               

12   12   ---              ---              ---              ---              

13   13   ---              ---              ---              ---               

14   07   ---              ---              ---              ---      

Displaying Software Revisions for a Single Card

To display the boot and runtime software revisions in use on a single card, enter the dspcd <slot> command as shown in the following example:

mgx8830a.1.PXM.a > dspcd 2

Unknown                          System Rev: 03.00   May. 04, 2002 20:29:14 GMT

MGX8830                                              Node Alarm: MINOR

Slot Number    2    Redundant Slot:  1

                    Front Card          Upper Card          Lower Card

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

Inserted Card:      PXM1E-4-155         UI Stratum3         SMFIR_4_OC3        

Reserved Card:      PXM1E-4-155         UI Stratum3         UnReserved         

State:              Active              Active              Active         

Serial Number:      S1234567890         SAK0325008J         SAG05415SW9 

Prim SW Rev:        3.0(0.26)P4         ---                 ---

Sec SW Rev:         3.0(0.26)P4         ---                 ---

Cur SW Rev:         3.0(0.26)P4         ---                 ---

Boot FW Rev:        3.0(0.26)A          ---                 ---

800-level Rev:      E2                  03                  4P   

800-level Part#:    800-12345-01        800-05787-01        800-18663-01

CLEI Code:          à0                                      0          

Reset Reason:       On Power up

Card Alarm:         NONE                

Failed Reason:      None                

Miscellaneous Information:

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

Managing Redundant Cards

The MGX switches support redundancy between two cards of the same type. For PXM1E, PXM45, and SRM cards, this redundancy is preconfigured on the switch. To establish redundancy between two CBSMs (for example, CESM, AUSM, FRSM, and VISM), two AXSMs, or two FRSM12s, you can enter the addred command as described in the "Establishing Redundancy Between CBSM Cards" section in "Preparing Cell Bus Service Modules for Communication."

The following sections describe how to

•Display the redundancy configuration

•Switch operation from one card to the other

•Remove the redundancy between two service modules

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:

mgx8830a.1.PXM.a > dspred

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

mgx8830a.1.PXM.a > dspred

Unknown                          System Rev: 03.00   May. 04, 2002 20:31:39 GMT

MGX8830                                              Node Alarm: MINOR

Logical   Primary          Secondary            Card     Redundancy  

Slot   Slot     Card     Slot       Red         Type        Type      

                State              State                                    

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

  1     1    Standby      2     Active       PXM1E            1:1      

  7     7    Standby      14    Active       SRM-3T3          1:1 

---

Switching Between Redundant PXM Cards

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

---

Note The switchcc command is entered only when all cards are operating in active or standby roles. For example, if a non-active PXM is not in standby state, or if a service module is being upgraded, the switchcc command is not entered.

---

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:

mgx8830a.1.PXM.a > switchcc

---

Switching Between Redundant Service Modules

To switch operation from an active redundant service module 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:

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

---

Removing Redundancy Between Two Cards

To remove the redundant relationship between two service modules, 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:

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

---

Switching Between Redundant RPM Cards

To switch operation from an active RPM-PR or RPM-XF 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.

---

Managing Redundant APS Lines

APS line redundancy is supported on PXM1E, AXSM, and SRME cards. To establish redundancy between two lines, you can enter the addapsln command as described in the "Establishing Redundancy Between Two Lines with APS" section in Chapter 4, "Preparing PXM1E Lines for Communication."

The following sections describe how to:

•Prepare for Intercard APS

•Display APS line information

•Modify APS lines

•Switch APS lines

•Remove the redundancy between two lines

---

Note APS is required for line redundancy on SRME cards that are installed in Cisco MGX 8850 (PXM1E) switches, and for line redundancy on PXM1E-8-155 cards in Cisco MGX 8850 (PXM1E) and Cisco MGX 8830 switches. APS is not required for SRME cards that are installed in Cisco MGX 8830 switches.

---

---

Note You must install and configure APS on your PXM1E-4-155 cards in order to facilitate a future upgrade to the PXM1E-8-155 card.

---

Preparing for Intercard APS

The following components are required for intercard APS:

•two front cards.

•two back cards for every bay hosting APS lines. All lines on cards used for intercard APS must operate in APS pairs or use Y cables.

•an APS connector installed between the two back cards for every bay hosting APS lines.

Enter the dspapsbkplane command on both the standby and active card to verify that the APS connector is plugged in properly. The following example shows the results displayed by the dspapsbkplane command when the APS connector is in place:

mgx8830a.1.PXM.a > dspapsbkplane

Line-ID   Primary Card Signal Status       Secondary Card Signal Status

                    Slot #1                             Slot #2        

  1.1               PRESENT                             PRESENT

  1.2               PRESENT                             ABSENT 

  2.1               PRESENT                             ABSENT 

  2.2               PRESENT                             ABSENT 

Remote Front Card : PRESENT 

Top Back Card     : ENGAGED 

Bottom Back Card  : ENGAGED 

The following example shows the results displayed by the dspapsbkplane command when the APS connector is not place:

mgx8830a.1.PXM.a > dspapsbkplane

Line-ID   Primary Card Signal Status       Secondary Card Signal Status

                    Slot #1                             Slot #2        

  1.1               PRESENT                             ABSENT

  1.2               ABSENT                              ABSENT 

  2.1               PRESENT                             ABSENT 

  2.2               ABSENT                              ABSENT 

Remote Front Card : ABSENT 

Top Back Card     : ENGAGED 

Bottom Back Card  : NOT-ENGAGED 

---

Note The dspapsbkplane command should be used only when the standby card is in the Ready state. When the standby card is booting or fails, intercard APS cannot work properly and this command displays "NOT ENGAGED."

---

If the dspapsbkplane command displays the message "APS Line Pair does not exist," suspect that the APS is not configured on a line.

If the dspapsbkplane command shows different values for each card in a pair of PXM1E, SRM, AXSME, or AXSM-XF cards, suspect that the APS connector is seated properly on one card but not on the other.

The APS connector status is the same for all lines in a single bay because the APS connector interconnects two back cards within the same bay. You need to enter the dspapsbkplane command only once to display the APS connector status for both upper and lower bays.

Enter the dspapslns command to verify APS configuration. If the working and protection lines show OK, both lines are receiving signals from the remote node.

Configuring Intercard APS Lines

In PXM1E, SRM, AXSME, or AXSM-XG intercard APS, either front card can be active, and can be connected to either APS line through the APS connector joining the two back cards. The following process describes how intercard APS communication works:

1. The signal leaves the front card at the remote end of the line.

2. The signal passes through the APS connector and both back card transmit ports at the remote end of the line.

3. The signal travels through both communication lines to the receive ports on both back cards at the local end.

4. The active front card processes the signal that is received on the active line.

5. The standby card monitors only the status of the standby line.

6. If necessary, the signal passes through the APS connector to the front card.

---

Note The front card monitors only one of the receive lines.

---

Line failures are always detected at the receive end of the line. This is where a switchover occurs when a failure is detected. Two different types of switchovers can occur, depending on whether the APS was configured as unidirectional or bidirectional in the cnfapsln command:

•When a failure occurs on a line configured for unidirectional switching, the switch changes lines at the receive end only. A switchover is not necessary at the transmit end because the transmitting back cards send signals on both lines in the 1 +1 APS configuration.

•When a failure occurs on a line configured for bidirectional switching, a switchover occurs at both ends of the line.

If the status of the standby line is good, a switchover from the failed active line to the standby is automatic.

Enter the cnfapsln command to enable an automatic switchover back to the working line after it recovers from a failure, as shown in the following example:

mgx8830a.1.PXM.a > cnfapsln -w 1.1.1 -rv 2

Table 13-4 describes the configurable parameters for the cnfapsln command.

Table 13-4 cnfapsln Command Parameters 

Parameter	Description
-w <working line>	Slot number, bay number, and line number of the active line to configure, in the following format: slot.bay.line Example: -w 1.1.1
-sf <signal fault ber>	A number between 3 and 5 indicating the Signal Fault Bit Error Rate (BER), in powers of ten. •3 = 10-3 •4 = 10-4 •5 = 10-5 Example: -sf 3
-sd <SignalDegradeBER>	A power if 10 in the range 5-9 that indicates the Signal Degrade Bit Error Rate (BER): •5 = 10-5 •6 = 10-6 •7 = 10-7 •8 = 10-8 •9 = 10-9 Example: -sd 5
-wtr <Wait To Restore>	The number of minutes to wait after the failed working line has recovered, before switching back to the working line. The range is 5-12.