Table Of Contents

Switch Operating Procedures

Managing the Configuration Files

Saving a Configuration

Clearing a 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 in Use

Displaying Software Revisions for All Cards

Displaying Software Revisions for a Single Card

Managing Redundant Cards

Displaying Redundancy Status

Switching Between Redundant PXM Cards

Switching Between Redundant AXSM Cards

Switching Between Redundant RPM-PR Cards

Removing Redundancy Between Two Cards

Managing Redundant APS Lines

Prepare 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 Time of Day Clocks

Modifying SNTP Servers

Modifying SNTP Clients

Deleting an Existing SNTP Server

Displaying an SNTP Server

Displaying the Current SNTP Configuration

Managing NCDP Clock Sources

Configuring an NCDP Clock Source

Configuring an NCDP Port

Displaying NCDP Clock Source Information

Display the Current NCDP Root Clock

Display A Specific NCDP Clock Sources

Display All NCDP Clock Sources

Display All NCDP Ports in the Network

Display An NCDP Port

Deleting an NCDP Clock Source

Managing Manually Configured Clocks Sources

View the Configured Clock Sources

Reconfigure Clock Sources

Delete Clock Sources

Restore a Clock Source After Failure

Managing Feeder Connections

Displaying SVCs

Managing Controllers

Adding Controllers

Deleting Controllers

Managing Service Class Templates

Displaying all Registered SCTs on a Switch

Displaying the SCT Assigned to a Port

Displaying the SCT Assigned to a Card

Displaying Port SCT Settings

Port SCT General Parameters (dspportsctgen)

Port SCT COSB Parameters (cosb)

Port SCT Virtual Circuit Threshold Parameters (vcThr)

Port SCT COSB Threshold Parameters (cosThr)

Displaying Card SCT Settings

Card SCT Bandwidth and Policing Parameters (dspcdsct bw)

Card SCT General SCT Parameters (dspcdsct gen)

Card SCT COSB Parameters (dspcdsct cosb)

Card SCT Virtual Circuit Threshold Parameters (dspcdsct vcThr)

Card SCT COSB Threshold Parameters (dspcdsct cosThr)

Applying a New Version of an SCT to a Card or Port

Displaying the SCT Checksum

Deleting an SCTs your Network

Viewing an ATM Port Configuration

Managing Partitions

Displaying a Resource Partition Configuration

Changing a Resource Partition Configuration

Deleting a 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

Tracing Established Connections

Setting and Viewing the Path Trace Feature on the Node

Setting and Viewing the Path Trace Feature on a Port

Displaying Path Trace Information

Clearing Path and ConnectionTraces

Clear the Connection Trace Buffer

Clear the Path Trace Buffer

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 PXM45 Disk Data

Displaying the Contents of the Disk Verification Utility Log File

Troubleshooting Discrepancies Between the Active and Standby Disk

Managing Line Loopbacks

Deleting a Loopack State

Configuring a line loopback

Configuring Loopback Line Tests on AXSME Cards

Configuring a loopback line on Connection

Configuring a Bit Error Rate Test on an AXSM

Deleting a Configured Bit Error Rate Test

Diagnostics Support MGX 8850 and MGX 8950 Switches

Configuring Offline and Online Diagnostics Tests on the AXSME Card

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

Displaying Online and Offline Diagnostics Test configuration information

Displaying online diagnostic errors

Displaying offline diagnostic errors

Switch Operating Procedures

---

This chapter describes procedures you can use to manage the Cisco MGX 8850 and Cisco 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, 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 8850 and Cisco 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, enter 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, andthen 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:

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

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 PXM45 Hard Drive card fails. 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 except the following data:

•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, enter 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 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 8850 and Cisco 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.

---

---

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

---

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

mgx8850a.7.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 the "Saving a Configuration" section.

---

Managing ILMI

The following sections describe how to perform the following tasks:

•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 8850 and Cisco 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, see the "Configuring ILMI on a Port" section 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:

popeye2.1.7pxm.a>cnfilmienable <portid> <no | yes>

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

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

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

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

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

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

---

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 are cleared, re-enter the dspilmicnt command.

---

Deleting ILMI Prefixes

The procedure for adding ILMI prefixes is described in the "Configuring ILMI Dynamic Addressing" section in "Provisioning AXSM Communication Links." The following procedure describes how to delete an ILMI address prefix from a port.

---

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:

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

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

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

INFO:  No Prefix registered

In the example above, no ILMI prefixes were 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:

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

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

popeye2.7.PXM.a > delprfx <portid> atm-prefix

Replace portid using the format slot:bay.line:ifNum. Table 7-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,

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 and MGX 8830 Software Version 3 (PXM45/B and PXM1E) or the Release Notes for Cisco MGX 8950 Software Version 3. 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 > 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:

mgx8850a.7.PXM.a > ll

The following example shows an ll command display:

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-3 shows some example filenames and the correct version numbers to use with the revision management commands.

Table 7-3 Determining Firmware Version Numbers from Filenames

Filename	Version Number for Revision Management Commands
pxm45_002.000.000.000_bt.fw	2.0(0)
pxm45_002.000.001.000_bt.fw	2.0(1)
axsm_002.000.001.001.fw	2.0(1.1)
pxm45_002.000.001-D_mgx.fw	2.0(1)D
pxm45_002.000.014-A1_bt.fw	2.0(14)A1
axsm_002.000.016-D.fw	2.0(16)D

---

Displaying Software Revisions in Use

The following sections describe:

•Displaying Software Revisions for All Cards

•Displaying Software Revisions for a Single Card

Displaying Software Revisions for All Cards

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:

pop20one.7.PXM.a > dsprevs

pop20one                         System Rev: 02.00   Jan. 24, 2001 18:32:57 PST

MGX8850                                              Node Alarm: NONE

Physical  Logical   Inserted       Cur Sw              Boot FW             

Slot      Slot      Card           Revision            Revision            

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

01        01        AXSM_4OC12     2.0(12)             2.0(12)             

02        02        AXSM_4OC12     2.0(12)             2.0(12)             

03        03        ---            ---                 ---                 

04        04        ---            ---                 ---                 

05        05        ---            ---                 ---                 

06        06        ---            ---                 ---                 

07        07        PXM45          2.0(12)             2.0(12)             

08        07        PXM45          2.0(12)             2.0(12)             

09        09        ---            ---                 ---                 

10        10        ---            ---                 ---                 

11        11        ---            ---                 ---                 

12        12        ---            ---                 ---                 

13        13        ---            ---                 ---                 

14        14        ---            ---                 ---                 

15        15        ---            ---                 ---                 

16        16        ---            ---                 --- 

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

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

pop20one.7.PXM.a > dsprevs -status

pop20one                         System Rev: 02.00   Jan. 24, 2001 18:37:16 PST

MGX8850                                              Node Alarm: NONE

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

Slot Slot Revision         Revision         Revision         Status            

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

01   01   2.0(12)          2.0(12)          2.0(12)          ---               

02   02   2.0(12)          2.0(12)          2.0(12)          ---               

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

04   04   ---              ---              ---              ---               

05   05   ---              ---              ---              ---               

06   06   ---              ---              ---              ---               

07   07   2.0(12)          2.0(12)          2.0(12)          ---               

08   07   2.0(12)          2.0(12)          2.0(12)          ---               

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

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

11   11   ---              ---              ---              ---               

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

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

14   14   ---              ---              ---              ---               

15   15   ---              ---              ---              ---               

16   16   ---              ---              ---              ---               

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

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:

pop20one.7.PXM.a > dspcd 7

pop20one                         System Rev: 02.00   Jan. 24, 2001 18:39:00 PST

MGX8850                                              Node Alarm: NONE

Slot Number    7    Redundant Slot:  8

                    Front Card          Upper Card          Lower Card

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

Inserted Card:      PXM45               UI Stratum3         PXM HardDiskDrive  

Reserved Card:      PXM45               UI Stratum3         PXM HardDiskDrive  

State:              Active              Active              Active         

Serial Number:      SAK03260058         SAK0332009P         SAK0325007Q 

Prim SW Rev:        2.0(12)             ---                 ---

Sec SW Rev:         2.0(12)             ---                 ---

Cur SW Rev:         2.0(12)             ---                 ---

Boot FW Rev:        2.0(12)             ---                 ---

800-level Rev:      06                  04                  03   

Orderable Part#:    800-05306-01        800-05787-01        800-05052-02

CLEI Code:                        h                              

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 Cisco MGX 8850 and Cisco MGX 8950 switches support redundancy between two cards of the same type. For PXM45 cards, this redundancy is preconfigured on the switch. To establish redundancy between two AXSM cards, enter the addred command as described in the "Establishing Redundancy Between Two AXSM Cards" section in "Preparing AXSM Cards and Lines 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 AXSM cards

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, enter 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 switchcc 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 switchcc 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 switchredcd 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.

---

Managing Redundant APS Lines

The Cisco MGX 8850 and Cisco MGX 8950 switches support APS line redundancy. To establish redundancy between two lines, enter the addapsln command as described in the "Establishing Redundancy Between Two Lines with APS" section in "Preparing AXSM Cards and Lines for Communication."

The following sections describe how to

•Prepare for Intercard APS

•Display APS line information

•Configure APS lines

•Switch APS lines

•Remove the redundancy between two lines

Prepare 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:

M8850_NY.1.AXSM.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:

M8850_LA.1.AXSM.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 the dspapsbkplane 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 of the two 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 note.

Configuring Intercard APS Lines

In AXSM and AXSM/B 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.

---

Figure 7-3 shows an example of how this process operates in a standard APS configuration, where the primary card monitors the working line and the secondary card monitors the protection line.

Figure 7-4 shows an example of how the APS communication process operates in a crossed APS configuration, where the secondary card monitors the working line that is attached to the primary card, and the primary card monitors the protection line that is connected to the secondary card.

Figure 7-3

Standard APS Configuration

Figure 7-4

Crossed APS Configuration

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:

M8850_LA.1.AXSM.a > cnfapsln -w 1.1.1 -rv 2

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

Table 7-4 cnfapsln Command Parameters 

Parameter	Description
-w <working line>	Slot number, bay number, and line number of the active line to configure, in the 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. Example: -wtr 5
-dr <direction>	Determines whether the line is unidirectional or bidirectional. •1 = Unidirectional. The line switch occurs at the receive end of the line. •2 = Bidirectional. The line switch occurs at both ends of the line. Note This optional parameter is not shown in the above example because you do not need to set it for a revertive line. Example: -dr 2
-rv <revertive>	Determines whether the line is revertive or non-revertive. •1 = Non-revertive. You must manually switch back to a recovered working line. •2 = Revertive. APS automatically switches back to a recovered working line after the number of minutes set in the -wtr parameter. Example: -rv 1

If you want to manually switch from one line to another, enter the switchapsln <bay> <line> <switchOption> command, as shown in the following example:

M8850_LA.1.AXSM.a > switchapsln 1 1 6

Manual line switch from protection to working succeeded on line 1.1.1

Table 7-5 describes the configurable parameters for the switchapsln command.

Table 7-5 switchapsln Command Parameters 

Parameter	Description
bay	The working bay number to switch.
line	The working line number to switch.
switchOption	The method of performing the switchover. •1 = Clear previous user switchover requests. Return to working line only if the mode is revertive. •2 = Lockout of protection. Prevents specified APS pair from being switched over to the protection line. If the protection line is already active, the switchover is made back to the working line. •3 = Forced working to protection line switchover. If the working line is active, the switchover is made to the protection line unless the protection line is locked out or in the SF condition, or if a forced switchover is already in effect. •4 = Forced protection to working line switchover. If the protection line is active, the switch is made to the working line unless a request of equal or higher prior