Switch Operating Procedures

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

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

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

2

3

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.

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:

mgx8830a.1.PXM.a > switchapsln 1 1 6
Manual line switch from protection to working succeeded on line 1.1.1

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

Table 13-5 switchapsln Command Parameters

Parameter

Description

bay

Working bay number to switch.

line

Working line number to switch.

switchOption

Method of performing the switchover. The possible methods are as follows:

•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 priority is in effect. This option has the same priority as option 3 (forced working to protection line switchover). Therefor, if a forced working to protection line switchover is in effect, it must be cleared before this option (forced protection to working line switchover) can succeed.

•5 = Manual switchover from working to protection line unless a request of equal or higher priority is in effect.

•6 = Manual switchover from protection to working line. This option is only available in the 1+1 APS architecture.

service switch

This is an optional parameter. When set to 1, this field causes all APS lines to switch to their protected lines.

Enter the dspapslns command to verify that the active line switched over from the protection line to the working line, as shown in the following example:

mgx8830a.1.PXM.a > dspapslns

Working Prot. Conf Oper Active WLine PLine WTR Revt Conf Oper LastUser
Index Index Arch Arch Line State State (min) Dir Dir SwitchReq
------- ----- ---- ----- ------ ----- ----- ----- ---- ---- ---- ----------
1.1.1 2.1.1 1+1 1+1 working OK OK 5 Yes bi bi ManualP->W
Displaying APS Line Information

To display the APS line redundancy configuration for a PXM card, enter the dspapsln command as described below.

Step 1 Establish a configuration session at any access level.

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

mgx8830a.1.PXM.a > dspapsln <working-slot.bay.line>
Replace <working-slot.bay.line> with the slot, bay, and line id of the APS line you want to display. After you enter the command, the switch displays a report similar to the following:

mgx8830a.1.PXM.a > dspapsln 9.1.1

Working Prot. Conf Oper Active SFBer SDBer WTR Revt Dir LastUser
Index Index Arch Arch Line 10^-n 10^-n (min) SwitchReq
------- ----- ---- ----- ------ ----- ----- ----- ---- --- ----------
9.1.1 9.1.2 1+1 1+1 working 3 5 5 No uni No Request
9.2.1 9.2.2 1+1 1+1 working 3 5 5 No uni No Request
Modifying APS Lines

To change the configuration for an APS line, enter the cnfapsln 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 Enter the cnfapsln command as follows:

mgx8830a.1.PXM.a > cnfapsln -w <workingIndex> -sf <SignalFaultBER> -sd <SignalDegradeBER> -wtr <Wait To Restore> -dr <direction> -rv <revertive> -proto <protocol>

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.

Table 13-6 describes the cnfapsln command options.

Table 13-6 Options for cnfapsln Command

Option

Description

-w

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

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.

-proto

The protocol option, which determines whether the switch will use the standard Bellcore protocol, or the ITU protocol.

Switching APS Lines

To switch between two APS lines, enter 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.

Step 2 Enter the switchapsln command as follows:

mgx8830a.1.PXM.a > switchapsln <bay> <line> <switchOption> <serviceSwitch>

Select the working line to switch by replacing <bay> with the bay number of the working line, and replacing <line> with the line number for the working line.

Table 13-7 describes the other options you can use with this command.

Table 13-7 Options for switchapsln Command

Option

Value

Description

switchOption

1

Clear

2

Lockout of protection

3

Forced working->protection

4

Forced protection->working

5

Manual working->protection

6

Manual protection->working; applies only to 1+1 mode

serviceSwitch

0 or 1

0 switches specified line. 1 switches all lines.

Removing APS Redundancy Between Two Lines

To remove the redundant APS line relationship between two lines, enter 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:

mgx8830a.1.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 1, Bay 2, Line 1 and the protection line associated with it.

mgx8830a.1.PXM.a > delapsln 1.2.1
Troubleshooting APS Lines

Port lights on PXM1E, SRM, AXSME, AXSM-XG or FRSM12 front cards indicate the receive status of APS lines. The active front card always displays the status of the active line. The standby card always displays the status of the inactive line. If only one APS line fails, the line failure LED is always displayed on the standby front card.

Caution When the active front card and the active line are in different slots and the inactive line has failed, it is easy to incorrectly identify the failed line as the line in the standby slot. To avoid disrupting traffic through the active line, verify which physical line is at fault before disconnecting the suspect line.

If the active line fails and the standby line is not available, the switch reports a critical alarm.

If the active line fails and the standby line takes over, the former standby line becomes the new active line, and the switch reports a major alarm.

If a PXM1E, SRM, AXSME, AXSM-XG, or FRSM12 front card fails, APS communication between the redundant front cards fails. This can result in one of the following situations:

•If both APS lines were working before the failure, an APS line failure causes a switchover to the protection line

•If either APS line failed prior to a front card failure, a failure on the active line does not cause a switchover to the other line. Because the standby front card failed, it cannot monitor the standby line and report when the line has recovered. This means that the active card cannot use the standby line until the standby front card is replaced and the line problem corrected.

Use the following procedure to troubleshoot APS lines.

Step 1 Enter the dsplns command to determine if the line in alarm is an APS line. The dsplns command shows which lines are enabled for APS.

mgx8830a.1.PXM.a > dsplns

Medium Medium
Sonet Line Line Line Frame Line Line Alarm APS
Line State Type Lpbk Scramble Coding Type State Enabled
----- ----- ------------ ------ -------- ------ ------- ----- --------
1.1 Up sonetSts12c NoLoop Enable Other ShortSMF Clear Enable
1.2 Up sonetSts12c NoLoop Enable Other ShortSMF Clear Disable
2.1 Up sonetSts12c NoLoop Enable Other ShortSMF Clear Disable
2.2 Up sonetSts12c NoLoop Enable Other ShortSMF Clear Disable

If the line in alarm is an APS line, and has always functioned properly as an APS line, proceed to Step 2.

If the line in alarm has never functioned properly as an APS line, verify that the following are true:

•Redundant front and back cards are in the appropriate bays and are installed at both ends of the line.

•Cable is properly connected to both ends of the line.

•Enter the dspapsbkplane command to verify that the APS connector is installed properly at both ends of the line.

Step 2 Enter the dspapslns command at both ends of the communication line to determine whether one or both lines in an APS pair are bad.

Use Table 13-8 to help you determine which APS line is not functioning properly.

Table 13-8 Troubleshooting APS Line Problems Using the dspaps Command

Active Line

Working Line

Protection Line

Working Line LED

Protection Line LED

Description

Working

OK

OK

Green

Green

Active card is receiving signal on working and protection lines. This does not guarantee that transmit lines are functioning properly. You must view the status on remote switch.

Protection

SF

OK

Green

Red

Active card is receiving signal on the protection line. No signal received on the working line.

Working

OK

SF

Green

Red

Active card is receiving signal on the working line. No signal received on the protection line.

Working

SF

SF

Red

Red

Active card is not receiving signal from either line. The working line was the last line to work.

Protection

SF

SF

Red

Red

Active card is not receiving signal from either line. The protection line was the last line to work.

Working

UNAVAIL

UNAVAIL

The card set is not complete. One or more cards have failed or been removed. See Table 13-9 to troubleshoot card errors.

Step 3 If one or both lines appear to be bad, determine whether the working or protection line is in alarm. Troubleshoot and correct the standby line first. Replace the components along the signal path until the problem is resolved.

•If the dspapslns command at either end of the line indicates a front or back card problem, resolve that problem first. (See Table 13-9 to troubleshoot card problems.)

•If the dspapslns command shows a signal failure on the standby line, replace that line.

•If the standby line is still down, replace the cards along the signal path.

Table 13-9 Troubleshooting Card Problems

APS Line Failure

Possible Cause

All lines in upper and lower bays.

Suspect a bad or removed front card. If both front cards are good, both back cards may be bad.

All lines in upper bay only. Lower bay APS lines OK.

Suspect bad upper bay back card.

All lines in lower bay only. Upper bay APS lines OK.

Suspect bad lower bay back card.

Managing Network Clock Sources

The following sections describe how to do the following tasks:

•Synchronize Time of Day clocks

•Manage NCDP

•View the configured clock sources

•Reconfigure network clock sources

•Delete clock sources

•Restore a clock source after failure

Synchronizing TOD Clocks

Clock synchronization is valuable for network clients with applications which need to have a reliable and accurate Time of Day (TOD). SES switches use SNTP to synchronize TOD clocks between a client and a server. An SNTP client can be configured to synchronize with one primary SNTP server and up to three secondary SNTP servers, and an SNTP server can support up to 200 clients.

In an SNTP server/client configuration, the SNTP client periodically requests TOD from the server. If the primary server is not available for some reason, the SNTP client switches over the next available secondary server for TOD information until the primary server comes back up.

An SNTP server can reside on an active PXM in an MGX and in and SES switch. An SES switch an be an SNTP server, but not an SNTP client.

To set synchronized network clocks, you need to perform the following task in order:

1. Set up a primary server for the network client.

2. Set up a secondary server (or several secondary servers), which serves as a backup server if the SNTP client cannot reach the primary server.

3. Configure the network client.

To synchronize the primary and secondary servers, the SNTP client must be enabled on the node or nodes on which the servers are running. Since an SNTP client is not supported on an SES, The supported primary and secondary configurations are as follows:

•An SES is the primary server, and an MGX is the secondary server.

•An SES is the primary server, and another SES is the secondary server.

Use the following procedure to set up TOD synchronization in your network.

Note SNTP clients and servers run only on active PXM cards.

Step 1 Select a primary server that is able to provide reliable TOD information to the network.

Step 2 At the SES PXM1 prompt, enter the cnfsntp -server on -stratum <stratum level > command to enable the server and configure the stratum level. Replace <stratum level > with the stratum level for the server.

espses.1.PXM.a > cnfsntp -server on -stratum 1

Table 13-10 describes the cnfsntp command parameters you must use to set up a server.

Table 13-10 cnfsntp Command Parameters

Parameter

Description

-server

Toggles the primary SNTP server on or off.

-stratum

Stratum of the SNTP client. The default is 0.

Step 3 On an MGX node, set up an SNTP client to point to the SES SNTP server using the addsntprmtsvr as shown in the following example.

mgx.1.PXM.a > addsntprmtsvr <server IP address> on -version <version> -primary yes

Replace <server IP address> with the IP address of the SES server you set up in Step 1 and Step 2. Replace <version> with the SNTP version.

Table 13-11 describes the cnfsntprmtsvr command parameters you must use to set up a remote server.

Table 13-11 cnfsntprmtsvr Command Parameters

Parameter

Description

server IP address

The IP address of the switch you want to be a remote SNTP server.

version

The SNTP version you are using. Possible options are 3 and 4.

Default: 3

-primary

This parameter lets you identify the switch as the primary SNTP server. Type -primary yes to make the primary server. To change the remote switch to a secondary server, type -primary no.

Default: no

Note During power up, the PXM loads the TOD onto all cards in the switch except for the RPM. You must use the SNTP synchronize RPM cards to the MGX TOD.

Deleting an Existing SNTP Server

Enter the delsntprmtsvr <IP_address> command at the active PXM prompt to delete a specific SNTP server. Replace <IP_address> with the IP address of the server you want to delete.

M8850_LA.8.PXM.a > delsntprmtsvr 172.29.52.88

Enter the delsntprmtsvr all command to delete all SNTP servers on the network, as shown in the following example:

M8850_LA.8.PXM.a > delsntprmtsvr all
Displaying an SNTP Server

Enter the dspsntprmtsvr command at the active PXM prompt to display a specific SNTP server.

ses.1.PXM.a > dspsntprmtsvr 172.29.52.88

Enter the dspsntprmtsvr all command at the active PXM prompt to display a list of all existing SNTP servers in the network.

M8850_NY.8.PXM.a > dspsntprmtsvr all

Displaying the Current SNTP Configuration

To display the client requesting the TOD information from the current server, enter the dspsntp command as shown in the following example:

M8850_NY.8.PXM.a > dspsntp

client: yes
server: yes

polling: 64
waiting: 5
rollback: 1024
stratum(default): 3
stratum(current): 3
sync: no

Table 13-12 shows the objects displayed for the dspsntp command.

Table 13-12 Objects Displayed for dspsntp Command

Parameter

Description

client:

Shows whether the SNTP client is turned on or off.

server:

Shows whether the SNTP server is turned on or off.

polling:

Shows the current number of seconds set on the polling timer. When this timer expires, the client requests TOD from the server.

waiting:

Shows the current number of seconds set on the waiting timer. If this timer expires three times, the client switches over to the first available secondary server for TOD.

Default = 5 seconds

rollback:

When a client switches over to the secondary server for TOD requests, the rollback timer takes affect and continues polling the primary server for TOD each time the rollback timer expires. The rollback timer continues polling the primary server until it comes back up.

Default = 1024

stratum (default):

Shows the default stratum level.

stratum (current):

Shows the current settings for the stratum level.

sync:

Shows whether the SNTP client and server are in sync.

Managing NCDP Clock Sources

The following sections provide procedures for managing Network Clock Distribution Protocol (NCDP) clock sources.

Enabling NCDP on a Switch

By default, NCDP is disabled on all nodes and all NNI ports. To enable NCDP on a switch, enter the cnfncdp command as follows:

M8850_LA.8.PXM.a > cnfncdp [-distributionMode 1|2] [-maxNetworkDiameter diameter] [-hello time] [ -holdtime time] [ -topoChangeTimer time]

Note NCDP must be enabled at each switch that will participate in NCDP clock distribution.

The -distributionMode option is the only option required to enable NCDP. Table 13-13 describes the options available for the cnfncdp command.

Table 13-13 cnfncdp Command Parameters

Parameter

Description

-distributionMode

This option selects either NCDP or manual mode clock distribution. To select NCDP mode, enter 1. To select manual clock distribution, enter 2. The default is 1 for NCDP.

-maxNetworkDiameter

This option specifies the maximum network diameter in hops. This is the maximum length of the spanning tree. The range is 3 to 200, and the default is 20.

-hello

This option specifies the NCDP hello packet interval. NCDP hello packets advertise the best network clock source. The range is 75 to 60000 milliseconds, and the default is 500 milliseconds.

-holdtime

This option specifies the hold time interval. The range is 75 to 60000 milliseconds, and the default is 500 milliseconds.

-topoChangeTimer

This option specifies the topology change timer interval. The range is 75 to 60000 milliseconds, and the default is 500 milliseconds.

Configuring an NCDP Clock Source

After you enable NCDP through the cnfncdp command, NCDP automatically selects the root clock source based on the following criteria:

•Priority (should be sufficient to find the root)

•Stratum level (should be sufficient as a tie-breaker)

•Clock source reference

• ATM address of the switch

You can manipulate these criteria and specify a clock source through the cnfncdpclksrc command as follows.

M8850_LA.8.PXM.a > cnfncdpclksrc <portid> <prstid> [-clocktype {e1 | t1}] [-priority <priority>] [-stratumLevel <level>]

Table 13-14 describes the options available for the cnfncdpclksrc command.

Table 13-14 cnfncdpclksrc Command Parameters

Parameter

Description

port-id

Port identifier. For clocking ports on Cisco MGX 8850 (PXM1E/PXM45) and Cisco MGX 8950 switches, the port identifier is 7.35 or 7.36. For clocking ports on Cisco MGX 8830 switches, the port identifier is 1.35 or 1.36.

For an internal oscillator, the port identifier is 255.255.

prs -id

Determines the primary reference source. Enter 0 for an external source, or 255 for an internal source.

-clocktype

Enter e1 or t1 as needed when the port ID is one of the following:

•7.35 or 7.36 in an MGX 8950 or MGX 8850 chassis

•1.35 or 1.36 in an MGX 8830 chassis

Note The default port type for 7.35/1.35 is E1. The default port type for 7.36/1.36 is T1. However, you can configure the BITS clocks portid 7.35/1.35 to be T1, or 7.36/1.36 to be E1, through the -clocktype parameter.

-priority

Prioritizes the clock source. Enter a number in the range from 1 to 255.

Default = 128

-stratumLevel

Determines the stratum level of the clock source. Possible levels are 1, 2E, 2, 3E, 3, 4E, or 4.

Default = 3

In the following example, the user configures an NCDP clock source on port 7.35 with a external source, a priority of 100, and the stratum level 2.

M8850_LA.8.PXM.a > cnfncdpclksrc 7.35 0 -priority 100 -stratumLevel 2

Note Once you enable NCDP, it is automatically enabled on all NNI ports on the switch.

Enter the dspncdpclksrc <portid> command to ensure the NCDP configuration took effect. Replace <portid> with the 7.35 or 7.36 (for T1/E1 ports). The following example displays the NCDP configuration on an E1 port.

M8850_LA.8.PXM.a > dspncdpclksrc 7.35
Best clock source : No
Priority : 100
Stratum level : 2
Primary reference src id : 0(external)
Health : Bad
Configuring an NCDP Port

Once you enable NCDP on your node, NCDP is automatically enabled on all the node's NNI ports. You can alter the default NCDP port configuration through the cnfncdpport <portid> <options> command, as shown in the following example:

M8850_LA.8.PXM.a > cnfncdpport 1:2.2:2 -ncdp enable -vpi 1 -vci 1 -admincost 1 -pcr 200 -scr 100 -mbs 50

Table 13-15 describes the cnfncdpport command options.

Table 13-15 cnfncdpport Command Parameters

Parameter

Description

portid

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

-ncdp

Enables/disables NCDP on the current port.

Default = disable

-vpi

Reserved VPI of the signaling channel, in the range from 0 through 4095. There is no reason to change this number unless a relevant card's partition is intended to support a specific VPI.

Note If you change the VPI, it must be within the valid partition range or it will be disabled.

Note You must disable NCDP before you modify the VPI of the signaling channel.

Default = 0

-vci

Reserved VCI of the signaling channel, in the range from 32 through 65535. Normally, no reason exists to change it.

Note If you change the VCI, it must be within the valid partition range or it will be disabled.

Note You must disable NCDP before you modify the VCI of the signaling channel.

Default = 34

-admincost

Sets the routing cost of the port, in the range from 1 through (2^24-1).

For example, if the equipment were in an area with a large amount of electronic noise, or if the switch carried a particularly large amount of traffic, you might want to raise the cost.)

Default = 10

-pcr

Specifies the PCR^¹ for the port. Default = 250 cells per second

-scr

Specifies the SCR^² for the port.

Default = 150 cells per second

-mbs

Specifies the MBS^³ for the port.

Default = 100 cells

¹PCR = peak cell rate

²SCR = sustained cell rate

³MBS = maximun burst size

Enter the dspncdpport <portid> command to verify that the NCDP parameters were set properly.

M8850_LA.8.PXM.a > dspncdpport 1:2.2:2
Network clock mode : enable
Ncdp Vc status : up
Network clock vpi : 0
Network clock vci : 34
Admin cost : 10
Service Category : sig
PCR : 250
SCR : 150
MBS : 100

M8850_LA.8.PXM.a >
Displaying NCDP Information

The following sections describe how to display information about NCDP configuration in your network.

Display the Current NCDP Root Clock

Enter the dspncdp command to display the current NCDP root clock source on the network.

M8850_LA.8.PXM.a > dspncdp
Distribution Mode : ncdp
Node stratum level : 3
Max network diameter : 20
Hello time interval : 500 ms
Hold Down time interval : 500 ms
Topology change time interval : 500 ms
Root Clock Source : 255.255
Root Clock Source Reason : locked
Root Clock Source Status : ok
Root Stratum Level : unknown
Root Priority : 0
Secondary Clock Source : 0.0
Secondary Clock Source Reason : unknown
Secondary Clock Source Status : unknown
Last Clock Source change time : N/A
Last Clock Source change reason : None

Table 13-16 describes the objects displayed by the dspncdp command.

Table 13-16 dspncdp Command Objects

Parameter

Description

Distribution Mode

Current enabled method of clock distribution. If the method chosen is manual, NCDP is turned off, and vice-versa.

Node stratum level

Stratum level of the clock source. Possible levels are 1, 2E, 2, 3E, 3, 4E, or 4.

Max network diameter

Maximum network diameter measured in hops.

Hello time interval

Time interval between each configuration pdu sent out by a node to advertise the best clock source in the network. This time interval is specified in milliseconds in the display.

Holddown time interval

Number of milliseconds the switch waits before it transmits the next configuration PDU.

Topology change time interval

Time interval for which the topology change detection field in the configuration pdu bit will be set. Having the topology change detection option set informs the recipient node that it needs to transmit configuration pdus out to advertise to its neighbors about recent topology or root clock changes.

Root Clock Source

Clock port from which the node is deriving the clock signal. 255.255 means the node is deriving the clock source from an internal oscillator.

Root Clock Source Reason

The reason for the most recent change of a source of network clock. For a detailed description of the reasons a clock source can change, refer to Table 2-12 in the Cisco MGX 8850 (PXM1E/PXM45), Cisco MGX 8950, and Cisco MGX 8830 Command Reference.

Root Clock Source Status

Status of the network's root clock source.

Root Stratum Level

Stratum level of the network's root clock source. Possible levels are 1, 2E, 2, 3E, 3, 4E, or 4.

Root Priority

Priority of the network's root clock source.

Secondary Clock Source

Secondary clock port from which the node is deriving the clock signal. 255.255 means the node is deriving the clock source from an internal oscillator.

Secondary Clock Source Reason

The reason for the most recent change of the secondary network clock source. For a detailed description of the reasons a clock source can change, refer to Table 2-12 in the Cisco MGX 8850 (PXM1E/PXM45), Cisco MGX 8950, and Cisco MGX 8830 Command Reference.

Secondary Clock Source Status

Status of the network's secondary clock source.

Last clk src change time

Time when the root clock source last changed.

Last clk src change reason

Reason why the root clock source last changed.

Display A Specific NCDP Clock Source

Enter the dspncdpclksrc command to display configuration information about a specific NCDP clock sources on the network.

M8850_LA.8.PXM.a > dspncdpclksrc 7.35
Best clock source : No
Priority : 100
Stratum level : 2
Primary reference src id : 0(external)
Health : Bad

M8850_LA.8.PXM.a >

Table 13-17 describes the objects displayed by the dspncdpclksrc command.

Table 13-17 dspncdpclksrc Command Objects

Parameter

Description

Best clock source

Describes whether the specified clock source is currently the best (or root) clock source in the network.

Priority

Displays the specified clock source's priority.

Stratum Level

Stratum level of the specified clock source. Possible levels are 1, 2E, 2, 3E, 3, 4E, or 4.

Primary reference src id

Displays the specified clock sources ID.

Health

Describes the current health of the specified clock source. The possible health states ar described below.

Good—Specified clock source is the current root clock or the second best clock source, and is in good condition.

Bad—Specified clock source was the root clock at some point, but went bad and is no longer available.

Wideband-Locking—Specified clock source is being qualified by the clock manager and is in wideband-locking mode.

Narrowband-Locking—Specified clock source is being qualified by the clock manager and is in narrowband-locking mode.

Unknown—Specified clock source is not the root clock source.

Display All NCDP Clock Sources

Enter the dspncdpclksrcs command to display all configured NCDP clock sources on the network.

M8850_LA.8.PXM.a > dspncdpclksrcs

PortId Best clk src Priority Stratum level Prs id Health
7.35 (e1) No 100 2 0(external) Bad
7.36 (e1) No 128 3 0(external) Bad
255.255 Yes 128 3 255(internal) Good

M8850_LA.8.PXM.a >

Table 13-18 describes the objects displayed by the dspncdpclksrcs command.

Table 13-18 dspncdpclksrcs Command Objects

Parameter

Description

PortId

Current enabled method of clock distribution. If the method chosen is manual, NCDP is turned off, and vice-versa.

Best clk src

Displays Yes if a clock source is a root clock source or a second best clock source, or displays No if a clock source is not a root or second best clock source.

Priority

Priority of each clock source.

Stratum level

Stratum level of each clock source. Possible levels are 1, 2E, 2, 3E, 3, 4E, or 4.

Prs id

Primary source ID (prs-id) is either 0 for external or 255 for internal.The internal primary source is the free-running oscillator on the PXM back card. (Even though the syntax line and the CLI help indicates a range, the only choice in the current release is 0 or 255.)

Default: 255

Health

Describes the current health of each clock source in the network. The possible health states ar described below.

Good—Specified clock source is the current root clock or the second best clock source, and is in good condition.

Bad—Specified clock source was the root clock at some point, but went bad and is no longer available.

Wideband-Locking—Specified clock source is being qualified by the clock manager and is in wideband-locking mode.

Narrowband-Locking—Specified clock source is being qualified by the clock manager and is in narrowband-locking mode.

Unknown—Specified clock source is not the root clock source.

Display All NCDP Ports on the Switch

Enter the dspncdpports command to display general details about all signaling ports for NCDP.

U1.8.PXM.a > dspncdpports

PortId Clock mode Clock Vpi Clock Vci Admin Cost Ncdp Vc
6:1.1:1 disable 0 34 10 down
6:1.1:2 disable 0 34 10 down
6:1.1:3 disable 0 34 10 down

Table 13-19 describes the objects displayed by the dspncdpports command.

Table 13-19 dspncdpports Command Objects

Parameter

Description

PortId

Port identifier in the format slot:bay.line:ifnum. Table 13-1 describes these parameters.

Clock mode

Displays whether NCDP is enabled or disabled on each port.

Clock VPI

Displays the VPI of the signaling channel for each port.

Clock VCI

Displays the VCI of the signaling channel for each port.

Admin Cost

Displays the routing cost of the port.

NCDP VC

Displays whether the Ncdp VC is up or down.

Display An NCDP Port

Enter the dspncdpport <portid> command to display detailed information for a specified NCDP signaling port. Replace <portid> with the port identifier in the format slot:bay.line:ifnum.

U1.8.PXM.a > dspncdpport 6:1.1:1
Network clock mode : disable
Ncdp Vc status : down
Network clock vpi : 0
Network clock vci : 34
Admin cost : 10
Service Category : sig
PCR : 250
SCR : 150
MBS : 100

Table 13-20 describes the objects displayed by the dspncdpport command.

Table 13-20 dspncdpport Command Objects

Parameter

Description

Network clock mode

Displays whether NCDP is enabled or disabled on each port.

NCDP Vc status

Displays whether the Ncdp VC is up or down.

Network clock VPI

Displays the VPI of the signaling channel for each port.

Network clock VCI

Displays the VCI of the signaling channel for each port.

Admin Cost

Displays the routing cost of the port.

Service Category

Displays the service category for the current NCDP port.

PCR

Displays the PCR^¹ for the port.

SCR

Displays the SCR^² for the port.

MBS

Displays the MBS^³ for the port.

¹PCR = peak cell rate

²SCR = sustained cell rate

³MBS = maximun burst size

Deleting an NCDP Clock Source

Enter the delncdpclksrc <portid> [clocktype <e1 | t1>] command to delete a clock source from the network. describes how to set the <portid> and [clocktype] parameters on all possible switches and cards.

Table 13-21 delncdpclksrc Command Objects

Parameter

Description

portid

The format of the PNNI physical port identifier can vary, as follows:

•On a PXM45: slot:subslot.port:subport

•On a PXM1E for UNI/NNI back card: slot:subslot.port:subport. On the UNI/NNI back card, the subslot is always 2, but the slot depends on the chassis, as follows:

–In an MGX 8850 chassis, slot is always the logical slot 7.

–In an MGX 8830 chassis, slot is always the logical slot 1.

•On a PXM1E for a cell bus service module (CBSM): slot.port.

For BITS clocks only, the default portid is 7.35(for E1 ports) or 7.36 (for T1 ports).In an MGX 8830 chassis, the default portid for BITS is either 1.35 (for E1 ports) or 1.36 (for T1 ports).

Note If the portid was modified, so that the BITS clocks portid 7.35/1.35 has been configured as a T1 (instead of an E1 port), or if 7.36/1.36 has been configured to be an E1 port (instead of a T1 port), then you must specify the clocktype in the delncdpclksrc command.

clocktype

Enter e1 or t1 as needed when the port ID is one of the following:

•7.35 or 7.36 in an MGX 8950 or MGX 8850 chassis

•1.35 or 1.36 in an MGX 8830 chassis

If the clock type is the default E1, this parameter is not necessary for port IDs 7.35 or 7.36 (or 1.35.or 1.36).

Default: e1

In the following example, the user deletes the clock source from the E1 port number 7.35 on a Cisco MGX 8850 (PXM45) switch.

M8850_LA.8.PXM.a > delncdpclksrc 7.35

M8850_LA.8.PXM.a >

Managing Manually Configured Clocks Sources

The following sections provide commands and procedures for managing manually configured clock source.

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.

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

mgx8830a.1.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 1 on the PXM1E card in slot 1. The primary clock source is active. The secondary clock source is coming from port 1 on the CESM card in slot 6.

mgx8830a.1.PXM.a > dspclksrcs
Primary clock type: generic
Primary clock source: 1:2.2:1
Primary clock status: ok
Primary clock reason: okay
Secondary clock type: generic
Secondary clock source: 6:1.1:1
Secondary clock status: ok
Secondary clock reason: okay
Active clock: primary
source switchover mode: non-revertive
Reconfigure Manual 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:

•To reconfigure a clock source for a BITS clock, see the " Configuring the MPLS Controller" section in Chapter 3, "Configuring General Switch Features."

•To reconfigure a clock source to use a PXM1E line, see the " Configuring PXM1E Line Clock Sources" section in Chapter 11, "Provisioning PXM1E Communication Links."

•To reconfigure a clock source to use a AXSM line, see refer to the Cisco ATM Services (AXSM) Software Configuration Guide and Command Reference for MGX Switches.

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, enter the delclksrc command as described in the next section.

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

Step 2 Display the clock source information by entering the dspclksrcs command.

You will need the information in this display to delete the clock source.

Step 3 To delete a clock source, enter the delclksrc command.

mgx8830a.1.PXM.a > delclksrc <priority>

The following example deletes a primary clock source:

mgx8830a.1.PXM.a > delclksrc primary

Step 4 To verify that a clock source has been deleted, enter the dspclksrcs command. When the primary or secondary clock source is deleted, the clock type is set to null.

Restore a Manual Clock Source After Failure

The revertive option for clock sources connected to the PXM allows a primary clock source to resume operation as the primary clock source after a failure and restoration of the clock signal. However, if you have the revertive option disabled, or if your primary clock source is connected to a service module line, you will have to reconfigure the primary clock source after it is restored.

Caution The revertive option is available only for a primary bits clock source. If the primary clock source is not a bits clock, setting the revertive option to enable causes the primary clock source to fail.

To reconfigure the clock source as a BITS clock source, see the " Configuring the MPLS Controller" section in Chapter 3, "Configuring General Switch Features." To reconfigure the clock source as a service module line clock source, see the " Configuring PXM1E Line Clock Sources" section in Chapter 11, "Provisioning PXM1E Communication Links." To reconfigure the clock source as an AXSM line clock source, refer to the Cisco ATM Services (AXSM) Software Configuration Guide and Command Reference for MGX Switches.

Tip Enter 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 PXM 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 source at 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 command to reconfigure the primary clock source for that node.

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:

mgx8830a.1.PXM.a > dsppncons

The following is an example report for the dsppncons command.

mgx8830a.1.PXM.a > dsppncons

Port VPI VCI CallRef:Flag X-Port VPI VCI CallRef:Flag Type OAM-Type Pri
9:1.1:1 0 32 1: 0 9:1.2:2 0 36 5: 0 PTP No 3
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: 0 PTP No 3
Calling-Addr:47.666666666666666666666666.666666666666.00
Called-Addr: 47.111111111111111111111111.111111111111.64

Managing Controllers

Cisco MGX Release 4 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.

mgx8830a.1.PXM.a > addcontroller <cntrlrId> i <cntrlrType> <lslot> [cntrlrName}

Table 13-22 describes the parameters for this command.

Table 13-22 Parameters for the addcontroller Command

Parameter

Description

<cntrlrId>

Number that identifies a network controller. The numbers are reserved as follows:

•2 = PNNI

•3 = Label Switch Controller (LSC), also known as Multiprotocol Label Switch Controller (MPLS). This option is not supported on PXM1E cards.

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

i

Keyword indicating that this controller is internal.

<cntrlrType>

Number that identifies a network controller. The numbers are reserved as follows:

•2 = PNNI

•3 = LSC (Label Switch Controller, also known as MPLS. This option is not supported on PXM1E cards.

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

Controller Bay Number: 0
Controller Line Number: 0
Controller VPI: 0
Controller VCI: 0
Controller In Alarm: NO
Controller Error:
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

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

mgx8830a.1.PXM.a > delcontroller <cntrlrId>

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

Caution Do not enter 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 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.

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 a PXM1E or AXSM card, enter the following command:

mgx8830a.1.PXM.a > dspports

This command displays all configured ports on the PXM1E or 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:

mgx8830a.1.PXM.a > dspport <ifNum>

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

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

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

Note Resource partitions can be managed on AXSM, FRSM12, and PXM1E cards. This section describes how to manage partitions on PXM1E cards. For instructions on managing resource partitions on other types of cards, see the service module documentation listed in Table 1-1.

Displaying a PXM1E 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:

mgx8830a.1.PXM.a > dspparts

The switch displays a report similar to the following:

mgx8830a.1.PXM.a > dspparts

if part Ctlr egr egr ingr ingr min max min max min max
Num ID ID GuarBw MaxBw GuarBw MaxBw vpi vpi vci vci conn conn
(.0001%)(.0001%)(.0001%)(.0001%)
-----------------------------------------------------------------------------
1 1 2 1000000 1000000 1000000 1000000 0 4095 35 65535 10000 10000
2 1 2 1000000 1000000 1000000 1000000 0 255 35 65535 5000 5000

Step 3 To display the configuration of a resource partition, note the interface and partition numbers and enter the following command:

mgx8830a.1.PXM.a > dsppart <ifNum> <partId>

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 report provided by the dsppart command.

mgx8830a.1.PXM.a > dsppart 1 1

Interface Number : 1
Partition Id : 1 Number of SPVC: 0
Controller Id : 2 Number of SPVP: 0
egr Guaranteed bw(.0001percent): 1000000 Number of SVC : 2
egr Maximum bw(.0001percent) : 1000000
ing Guaranteed bw(.0001percent): 1000000
ing Maximum bw(.0001percent) : 1000000
min vpi : 0
max vpi : 4095
min vci : 32
max vci : 65535
guaranteed connections : 10000
maximum connections : 10000

Note Partition ID 1 is reserved for PNNI.

Changing a PXM1E Resource Partition Configuration

To change the configuration of a resource partition, 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 showing the partitions for this card, enter the dspparts command.

Note You can change a resource partition only when the partition is not in use.

Step 3 To create a resource partition on a PXM1E or AXSM card, enter the cnfpart command as shown in the following example:

mgx8830a.1.PXM.a > cnfpart -if <ifNum> -id <partId> -emin <egrminbw> -emax <egrmaxbw> -imin <ingminbw> -imax <ingmaxbw> -vpmin <minVpi> -vpmax <maxVpi> -vcmin <minVci> -vcmax <maxVci> -mincon <minConns> -maxcon <maxConns>

To create a resource partition on a FRSM12 card, enter the cnfpart command as shown in the following example:

mgx8830a.1.PXM.a > cnfpart -if <ifNum> -ctlrnum <controllerNum>] [-lcn <available connections>] [-dlcimin <minDlci>] [-dlcimax <maxDlci> [-ibw <ingPctBw>] [-ebw <egrPctBw>]

Table 13-23 describes the parameters for the cnfpart command. Be sure to configure only the parameters that are appropriate for the card you are configuring.

Table 13-23 Parameters for the cnfpart Command

Parameter

Description

ifNum

Interface number or port number. This number identifies the port this resource partition configures. Enter the interface number that was assigned to the port when it was configured.

controllerNum

Controller number.

1 = PAR (Portable AutoRoute)—Not supported in this release.

2 = PNNI—Only PNNI is supported in this release.

3 = TAG (MPLS)—Not supported in this release.

Note This parameter applies only to FRSM12 cards.

partId

Partition identification number. Enter a number in the range of 1 to 20.
Partition ID 1 is reserved for PNNI.

Note This parameter applies only to PXM1E and AXSM cards.

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 setting for PNNI must be 100% or less, and must be less than the sum of the egrmaxbw settings.

Note This parameter applies only to PXM1E and AXSM cards.

egrmaxbw

Egress maximum bandwidth. Enter the maximum percentage of the outgoing port bandwidth that you want assigned to the controller. One percent is equal to 0.00001 units. For example, an <egrmaxbw> of 1000000 = 100%. The sum of the maximum egress bandwidth settings for PNNI can exceed 100%, and must be more than the sum of the egrminbw settings. Available bandwidth above the minimum bandwidth settings is allocated to the operating controllers on a first-request, first-served basis until the maximum bandwidth setting is met or there is insufficient bandwidth to meet the request.

Note This parameter applies only to PXM1E and AXSM cards.

ingminbw

Ingress minimum bandwidth. Enter the minimum percentage of the incoming port bandwidth that you want assigned to the controller. One percent is equal to 0.00001 units. For example, an <ingminbw> of 500000 = 50%. The sum of the minimum ingress bandwidth settings for PNNI must be 100% or less, and must be less than the sum of the ingmaxbw settings.

Note This parameter applies only to PXM1E and AXSM cards.

ingmaxbw

Ingress maximum bandwidth. Enter the maximum percentage of the incoming port bandwidth that you want assigned to the controller. One percent is equal to 0.00001 units. For example, an <ingmaxbw> of 750000 = 75%. The sum of the maximum ingress bandwidth settings for PNNI can exceed 100%, and must be more than the sum of the ingminbw settings. Available bandwidth above the minimum bandwidth settings is allocated to the operating controllers on a first-request, first-served basis until the maximum bandwidth setting is met or there is insufficient bandwidth to meet the request.

Note This parameter applies only to PXM1E and AXSM cards.

minVpi

Minimum VPI number for this port. For UNI ports, enter a value in the range from 0 to 255. For NNI ports, enter a value in the range from 0 to 4095.

Note This parameter applies only to PXM1E and AXSM cards.

maxVpi

Maximum VPI number for this port. For UNI ports, enter a value in the range from 0 to 255. For NNI ports, enter a value in the range from 0 to 4095. The value for <maxVpi> cannot be less than for <minVpi>.

Note This parameter applies only to PXM1E and AXSM cards.

minVci

Minimum VCI number for this port. 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.

Note This parameter applies only to PXM1E and AXSM cards.

maxVci

Maximum VCI number for this port. Enter a number in the range from 32 to 65535.

Note This parameter applies only to PXM1E and AXSM cards.

minConns

Specifies the guaranteed number of connections.

On the PXM1E UNI/NNI, the ranges vary according to the line types, as follows:

•For OC3, T3, and E3 lines, the range is 10-27000.

•For T1 and E1 lines, the range is 10-13500.

On the AXSM series of cards, the range is 10 through the maximum number of connections in the port group.

Note This parameter applies only to PXM1E and AXSM cards.

maxConns

Maximum number of simultaneous connections allowed on this port. The range is the same as described for the <minConns> parameter. This parameter must be set to number that is greater than the number defined for <minConns>.

Note This parameter applies only to PXM1E and AXSM cards.

available connections

Logical channel number. Range: 0-16000.

Note This parameter applies only to FRSM12 cards.

minDlci

Lowest data-link connection identifier (DLCI). A value that specifies the DLCI in a Frame Relay network:

•Two-byte header—Range: 1-1023

•Four-byte header—Range: 0-8388607

The value specified must be n * 32768, where n is a number from 0 to 255.

Note This parameter applies only to FRSM12 cards.

maxDlci

Highest data-link connection identifier (DLCI). A value that specifies a DLCI in a Frame Relay network:

•2-byte header—Value range: 1 -1023

•4-byte header—Value range: 0 -8388607

The value specified must be (n * 32768)-1, where n is a number from 1 to 256.

Note This parameter applies only to FRSM12 cards.

ingPctBw

Percentage of ingress bandwidth available to the connection. Range: 0-100 percent.

Note This parameter applies only to FRSM12 cards.

egrPctBw

Percentage of egress bandwidth available to the connection. Range: 0-100 percent.

Note This parameter applies only to FRSM12 cards.

Step 4 To display the changed partition configuration, enter 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 Step 5 through Step 8 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:

mgx8830a.1.PXM.a > dspcontrollers

Step 6 Enter 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 "PNNI Controller"

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

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

mgx8830a.1.PXM.a > dspcons

The following is a sample dspcons display.

mgx8830a.1.PXM.a > dspcons

Local Port Vpi.Vci Remote Port Vpi.Vci State Owner Pri Persistency
----------------------+------------------------+---------+-------+---+-----------
3:1.1:1 102 102 Routed 102 102 FAIL MASTER 3 Persistent
Local Addr: 47.00918100000100001a531c2a.000001031801.00
Remote Addr: 47.00918100000200036b5e30cd.000001011802.00
Preferred Route ID:-
Currently on preferred route: N/A

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. You will need these to delete the connections.

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

mgx8830a.1.PXM.a > delcon <ifNum> <VPI> <VCI>

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

mgx8830a.1.PXM.a > dnport <ifNum>

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

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

Step 3 Enter the following command to delete the static address:

mgx8830a.1.PXM.a > deladdr <portid> <atm-address> <length> [-plan {e164|nsap}]

The command parameters are described in Table 13-24.

Table 13-24 ATM Address Configuration Parameters

Parameter

Description

portid

Port identifier in the format slot:bay.line:ifnum. These parameters are described in Table 13-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 is deleted, enter the following command:

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

Replace <portid> with the port address using the format slot:bay.line:ifnum These parameters are described in Table 13-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 Cisco MGX switches allow you to define the minimum and maximum values for the following parameters:

•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 Enter the following command to bring down the PNNI port you want to configure:

mgx8830a.1.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 13-1 describes these parameters.

Step 4 Enter configure the port range, enter the following command:

mgx8830a.1.PXM.a > cnfpnportrange <portid> [-minsvccvpi <min-svcc-vpi>] [-maxsvccvpi <max-svcc-vpi>]] [-minsvccvci <min-svcc-vci>] [-maxsvccvci <max-svcc-vci>]] [-minsvpcvpi <min-svpc-vpi>] [-maxsvpcvpi <max-svpc-vpi>]]

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 13-25 lists and describes the options and parameters for this command.

Table 13-25 Parameters for the cnfpnportrange Command

Parameter

Description

portid

Port identifier in the format slot:bay.line:ifnum. Table 13-1 describes these parameters.

min-svcc-vpi

Minimum VPI value for SVCC.

Range: 0 to 4095.
Default = 0.

max-svcc-vpi

Maximum VPI value for SVCC.

Range: 0 to 4095.
Default = 4095.

min-svcc-vci

Minimum VCI value for SVCC.

Range: 32 to 65535.
Default = 35.

max-svcc-vci

Maximum VCI value for SVCC.

Range: 32 to 65535.
Default = 65535.

min-svpc-vpi

Minimum VPI value for SVPC.

Range: 1 to 4095.
Default = 1.

max-svpc-vpi

Maximum VPI value for SVPC.

Range: 1 to 4095.
Default = 4095.

Step 5 Enter the following command to bring up the PNNI port you just configured:

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

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

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

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

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

mgx8830a.1.PXM.a > dsppnportrange 1:2.1:2

minSvccVpi: 0 maxSvccVpi: 4095
minSvccVci: 35 maxSvccVci: 65535
minSvpcVpi: 1 maxSvpcVpi: 4095

Managing Priority Routing

When an SPVC is created, it can be prioritized so that the user has more control over the sequence in which connections are routed, rerouted, and derouted in the network. Routing priorities are set in a range from 0 through 15, with 0 being the highest priority and 15 being the lowest priority. 0 priority is reserved for networking control connections, while priorities 1 through 15 can be assigned to user connections.

Within the priority categories of 0 through15, connections are further divided into groups based on their bandwidth. Connections requiring more bandwidth are routed before those requiring less bandwidth. The number of bandwidth groups is fixed at 50, but you can specify the following ranges:

•range with the lowest bandwidth requirement

•range of cells per second in each range between the highest and lowest ranges.

Because the bandwidth groups are node-level, they apply to all priorities. The same ranges exist for priority 0, priority 1, priority 2, and so on down to the lowest priority. Connections requiring the least bandwidth are grouped at the low end of the range, and connections requiring the most bandwidth are grouped at the top end of the range. The remaining connections are progressively grouped somewhere between the upper and lower bounds.

Bandwidth for a priority is divided into three parts:

•lowest range—You determine the lowest range by specifying the highest rate within the range. For example, if you type 3000, the lowest range is 0-3000 cps.

•highest range—Highest range is what is left over after you specify the lowest range, the number of bandwidth groups, and the number of cells per second in each bandwidth increment.

•All incremental ranges between the lowest and the highest.

Note The derouting of SVCs uses the same priority routing criteria and the derouting of SPVCs.

Before you can prioritize a specific SPVC, you must set up the priority routing feature on the node itself, as described in the section that follows.

Establishing Priority Routing on a Node

Enter the cnfpri-routing command at the PXM card to establish priority routing on a node.

mgx8830a.1.PXM.a > cnfpri-routing [-bwgrps <grps>] [-bwstart <start>] [-bwincr <incr>][-pribuf <time>] [-nodebuf <delay>]

Table 13-26 describes the options available in the cnfpri-routing command.

Table 13-26 cnfpri-routing Command Parameters

Parameter

Description

-bwgrps

Bandwidth groups.

-bwstart

The value for bwstart is the highest cell rate in the lowest-speed bandwidth group. The number of bandwidth groups is fixed at 50.

Range: 1-500000

Default: 5000

-bwincr

The increment for the cell rate between the upper and lower bounds of each intermediate bandwidth group. For example, an increment of 2000 means that a range starting at 10000 cps ends at
12000 cps. This increment does not apply to the following groups:

•The group with the lowest bandwidth requirements: for this group, the range is determined by the value for bwstart.

•The group with the highest bandwidth requirements: for this group, the range is what remains after computations based on the following values:

–bwstart

–bwincr

Range: 1-500000

Default: 1000

-pribuf

The priority buffer is a time counter. It counts down to the moment when PNNI prioritizes all buffered connections for routing. A connection is buffered due to an event that causes PNNI to re-route the connection.

The routing events are as follows:

•Interface with a master endpoint comes up.

•Routed SPVC or SPVP is released (or failed).

•SPVC or SPVP is created.

•Route optimization begins.

Range: 0-600, in units of 0.1 seconds (0-60 seconds)

Default: 0

-nodebuf

The node buffer is a time counter. It counts down the time to wait before PNNI starts routing connections. Down-counting begins when the first PNNI logical port comes up. The buffer operates once, after node start-up or node reset.

Range: 0-3000, measured in units of 0.1 seconds (0-300 seconds)

Default: 0

Configuring Priority Routing on a Connection

Once priority routing has been set up on a node, you can prioritize the node's SPVCs. A connection's priority is designated during the SPVC master end setup with the addcon command. (See the "Configuring the Master Side of SPVCs and SPVPs" section in Chapter 11, "Provisioning PXM1E Communication Links.")

The following command example defines a port as the master side of an SPVC with a routing priority of 3.

mgx8830a.1.PXM.a > addcon 3 101 101 1 1 -slave -rtngprio 3 4700918100000000001A531C2A00000101180300.101.101
master endpoint added successfully
master endpoint id : 4700918100000000107B65F33C0000010A180300.101.101

Note If you are setting up priority routing on a node that already has established SPVCs, their routing priority is set to 8 by default. You can change the routing priority on an established connection with the cnfcon command. (See the next section " Modifying SPVC Priority Routing Configuration."

Modifying SPVC Priority Routing Configuration

Enter the cnfcon command and use the -rtngprio option to change an SPVC's routing priority, as shown in the following example:

mgx8830a.1.PXM.a > cnfcon 3 101 101 -rtngprio 6

Managing Path and Connection Traces

Cisco MGX switches support the following traces:

•path traces — the trace occurs only during call setup. Therefore, tracing is enabled before call set up then actually occurs while PNNI routes the connection. The applicable connections are SPVCs, SPVPs, SVCs, or SVPs.

•connection traces — the trace occurs for a call that has already been routed. You can trace the route of existing SPVCs and SVCs.

For more information about enabling path and connection traces, refer to the Cisco MGX 8850 (PXM1E/PXM45), Cisco MGX 8950, and Cisco MGX 8830 Command Reference.

Displaying Path and Connection Traces

There are several commands that allow you to display trace information about a connection. By entering these commands at the slave end of the connection, you can determine the path taken by a connection. Table 13-27 describes these commands:

Table 13-27 Path and Connection Trace Commands

Command

Description

dsppathtracenode <enable|disable>

Displays the nodal configuration for the path and connection trace.

dsppathtraceport <portid>

Displays the port configuration for the path and connection trace.

dsppathtraceie <portid>

Displays whether or not TTL 1E is included in the specified port's configuration.

dsppathtracebuffer <portid><vpi><vci>

Displays a specific connection based on the physical port's id, vpi, and vci.

dsppathtracebuffer

Displays all path traces in all the path trace buffers.

conntrace

Displays all path traces in all the path trace buffers.

Clearing a Call at the Destination Node

When a call setup message reaches its destination, you can ensure that the call is cleared by entering the pathtraceport command as follows:

mgx8830a.1.PXM.a > pathtraceport <portid> -X

Replace portid using the format slot:bay.line:ifNum. Table 13-1 describes these parameters. The -X parameter ensures that calls will be cleared once they reach the destination specified in the portid parameter.

Managing Load Sharing

When redundant PXM cards are used, load sharing enables traffic routing through the switch fabric on both PXM 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 PXM 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 PXM 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

Enter the dspxbarmgmt command to display the status of the load sharing options. The following example shows the display for this command.

mgx8830a.1.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 fields show the option status as Enable or Disable. The Plane Alarm Threshold line displays a number from 1 to 32. On PXM 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:

mgx8830a.1.PXM.a > cnfxbarmgmt <loadSharing> <autoShutdown> <planeAlarmThresh>

Note You must enter values for all command parameters, even if you want to change only one of them.

Table 13-28 describes the parameters for this command.

Table 13-28 Command Parameters for cnfxbarmgmt

Parameter

Description

loadSharing

Enables or disables load sharing. Enter -1, 0, or 1. These values control load sharing as follows:

•-1 unconditionally disables load sharing, regardless of switch plane status

•0 disables load sharing only when there are no switch plane alarms

•1 enables load sharing

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

Step 4 To verify your configuration change, enter the dspxbarmgmt command.

Starting and Managing Telnet Sessions to Other Switches

The Cisco MGX 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

• Returning to a Previous Session

• Returning to the Original CLI Session

• Displaying a Telnet Trace

Starting a Telnet Session

To start a Telnet session, enter the telnet command as follows:

mgx8830a.1.PXM.a > telnet [-E<escapeCharacter>] [-R<tracerouteCharacter>] <ipAddress> [[0x|X|x]<tcpPort>]

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

mgx8830a.1.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 with 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 the default escape character, 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 telnet 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 Escape 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 Escape 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:

mgx8830a.1.PXM.a > telnet 172.29.52.88
Trying 172.29.52.88...
Connected to 172.29.52.88

Login: cisco
password:

mgx8830b.1.PXM.a > telnet 172.29.52.56
Trying 172.29.52.56...

Connected to 172.29.52.56

Login:
password:

mgx8830a.1.PXM.a >
-> local IP 172.29.52.56, next hop at 172.29.52.88

-> local IP 172.29.52.88, connected to server at 172.29.52.56

mgx8830b.1.PXM.a >

Verifying PXM Disk Data

When a failure occurs before a write is complete, the data on the active and standby hard disk may not match.

Enter the verifydiskdb check [-l <level>] [-s <slot>] [-p <pass>] command at the active PXM to run the disk verification utility. Table 13-29 describes the possible options for the verifydiskdb check command.

Note Cisco recommends that you run the disk verification utility during a time when there is the least activity on the switch.

Table 13-29 describes the possible options for the verifydiskdb check command.

Table 13-29 verifydiskdb check Command Parameters

Parameter

Description

slot

Slot number of the card on which you want to run the disk verification task.

level

Level on verification for the current task. The levels of verification are as follows:

1 = control information

2 = actual data

Default = 2

application

Number of times the verification utility will pass through the disk if a discrepancy is found. Multiple passes create the opportunity for software to resolve discrepancies. The number of passes rangers from 1 through 10.

Note If no discrepancies are found, the verification utility runs through the disk only once.

Default = 3

If you enter verifydiskdb check without any options, the verification utility verifies that the data on the active hard disk matches the data on the standby hard disk. In the following example, the user runs the verification utility for all cards in the node.

pop20two.7.PXM.a > verifydiskdb check

pop20two.7.PXM.a >

Enter verifydiskdb check with the -sl <slot number> option to run the verification utility only on the specified slot.

In the following example, the user configures the verification utility to check for any discrepancies in the control information on the card in slot 7. If any discrepancy is found, the verification utility will run through the disk up to 3 times before it finishes.

pop20two.7.PXM.a > verifydiskdb check -l 1 -sl 7 -p 3

The disk verification task runs in the background until completion. It can take a few seconds or several hours for the disk verification task to finish. The more connections configured on the switch, the longer it takes the utility to complete disk verification. To view the progress of the disk verification task, enter the verifydiskdb status command while the verification task is running.

pop20two.7.PXM.a > verifydiskdb status
Verification is currently running with the following parameters:
Request: Slot(s): ALL Level: 1 Passes: 3

Current Status
Slot: 7, Databases: 13 Tables 88
DB Index: 12 DB Name: spvcRed
Table Details:
Table Index: 81 Table Name: Disk_spvc_pep_db19
Total Records: 10000 Records Verified: 0

Table 13-30 describes the information displayed by the verifydiskdb status command.

Table 13-30 verifydiskdb status Command Display

Parameter

Description

Slot

Current slot whose databases on active and standby PXM hard drives are being compared.

Databases:

Number of databases detected for the current slot.

Tables

Total number of tables detected for all databases for the slot.

DB Index:

Index number of the current database being compared.

DB Name:

Name of the database currently being compared.

Table Details:

Details about the current table being compared.

Table Index:

Index number of the current table being compared.

Table Name:

Name of the current table being compared.

Total Records:

Total number of records.

Records Verified:

Number of records verified.

Databases Verified:

Number of databases verified.

Tables Verified:

Number of tables verified.

Note To stop the disk verification task while it is in progress, enter the verifydiskdb abort command.

Displaying the Contents of the Disk Verification Utility Log File

When the disk verification task is complete, a log file of the task is stored in the log folder on your hard drive. Each log file contains a header with the slot number and the status of the card.

If more information about the discrepancies is determined, it is stored in the log file. However, there is no comparison between data on the hard disk versus data on the card.

To view the disk verification utility log file, enter the verifydiskdb display command as shown in the following example.

pop20two.7.PXM.a > verifydiskdb display

If you want to view an older log file, enter the verifydiskdb display command with the -l old option, as shown in the following example.

pop20two.7.PXM.a > verifydiskdb display -l old

Note The directory only keeps two log files per slot. If disk verification is executed a third time for a slot that contains two log files, the oldest of the two files is removed.

If no discrepancies are found on a card, the log file contains only the slot number, timestamp of the verification task, and a message stating that no discrepancies were found, as shown in the following example:

------------------ Information for Slot 5 ------------------
Start: 22/05/2002-10:31:19 - End: 22/05/2002-10:31:27

Verify DONE

TotalofDbs= 2, TotalofTbls= 15, #DbVerf=2, #TblVerf= 15
No Discrepancies found for slot 5
--------------------------------------------------------------

If discrepancies were found on a card, the log file contains the names of the databases and tables in which the discrepancies were found, as shown in the following example:

------------------ Information for Slot 1 ------------------
Start: 20/04/2002-17:43:49 - End: 20/04/2002-17:43:57

Verify DONE

TotalofDbs= 4, TotalofTbls= 20, #DbVerf=4, #TblVerf= 20
=============================================================
dbInd: 2 - dbName: EmDiskDb
tblInd: 17 - tblName: LineTable
Record: 8 ActvChkSum: 0 StdbyChkSum: 549
=============================================================
dbInd: 2 - dbName: EmDiskDb
tblInd: 17 - tblName: LineTable
Record: 9 ActvChkSum: 0 StdbyChkSum: 549
===============================================================

Verification Slot Summary
Start: 20/04/2002-17:43:49 - End: 20/04/2002-17:43:57
Total Discrepancies Found: 2, Total Discrepancies Sync: 0
--------------------------------------------------------------

If the verification utility is run on a slot in which no card resides, the display will show that the slot was invalid and has been skipped, and shown in the following example:

--------------------------------------------------------------
------------------ Information for Slot 2 ------------------
Start: 22/05/2002-10:31:10 - End: 22/05/2002-10:31:10

Verify SKIPPED - INV_SLOT

TotalofDbs= 0, TotalofTbls= 0, #DbVerf=0, #TblVerf= 0
No Discrepancies found for slot 2
--------------------------------------------------------------
--------------------------------------------------------------

If the card is in an unstable state, the display indicates that the verification utility has skipped that slot because it is unstable, as shown in the following example.

------------------ Information for Slot 4 ------------------
Start: 20/04/2002-17:44:06 - End: 20/04/2002-17:44:06

Verify SKIPPED - UNSTABLE SLOT

TotalofDbs= 0, TotalofTbls= 0, #DbVerf=0, #TblVerf= 0
No Discrepancies found for slot 4
--------------------------------------------------------------
If a firmware upgrade had not finished (the commitrev command had not yet been used on the slot), the display indicates that the verification utility has skipped that slot because a REV_CHG is in progress, as shown in the following example:

------------------ Information for Slot 6 ------------------
Start: 20/04/2002-17:44:14 - End: 20/04/2002-17:44:14

Verify SKIPPED - REV_CHG

TotalofDbs= 0, TotalofTbls= 0, #DbVerf=0, #TblVerf= 0
No Discrepancies found for slot 6
--------------------------------------------------------------

If more than 20 discrepancies are found in a table or database, the utility is terminated and the display indicates that the slot is unstable, and lists the names of the tables and databases where the discrepancies were found. The following example shows the display for an unstable slot with more that 20 discrepancies:

----------------- Information for Slot 9 ------------------
Start: 20/04/2002-17:44:54 - End: 20/04/2002-17:44:57

Verify SKIPPED - UNSTABLE SLOT

TotalofDbs= 2, TotalofTbls= 6, #DbVerf=0, #TblVerf= 0
=============================================================
dbInd: 1 - dbName: sm_mib_v21
tblInd: 5 - tblName: mib29
Record: 1782 ActvComdID: 0 StdbyComID: 7
=============================================================
dbInd: 1 - dbName: sm_mib_v21
tblInd: 5 - tblName: mib29
Record: 1783 ActvComdID: 0 StdbyComID: 7
=============================================================
dbInd: 1 - dbName: sm_mib_v21
tblInd: 5 - tblName: mib29
Record: 1784 ActvComdID: 0 StdbyComID: 7
=============================================================
dbInd: 1 - dbName: sm_mib_v21
tblInd: 5 - tblName: mib29
Record: 1785 ActvComdID: 0 StdbyComID: 7
=============================================================
dbInd: 1 - dbName: sm_mib_v21
tblInd: 5 - tblName: mib29
Record: 1786 ActvComdID: 0 StdbyComID: 7
=============================================================
dbInd: 1 - dbName: sm_mib_v21
tblInd: 5 - tblName: mib29
Record: 1787 ActvComdID: 0 StdbyComID: 7
=============================================================
dbInd: 1 - dbName: sm_mib_v21
tblInd: 5 - tblName: mib29
Record: 1788 ActvComdID: 0 StdbyComID: 7
=============================================================
dbInd: 1 - dbName: sm_mib_v21
tblInd: 5 - tblName: mib29
Record: 1789 ActvComdID: 0 StdbyComID: 7
=============================================================
dbInd: 1 - dbName: sm_mib_v21
tblInd: 5 - tblName: mib29
Record: 1790 ActvComdID: 0 StdbyComID: 7
=============================================================
dbInd: 1 - dbName: sm_mib_v21
tblInd: 5 - tblName: mib29
Record: 1791 ActvComdID: 0 StdbyComID: 7
=============================================================
dbInd: 1 - dbName: sm_mib_v21
tblInd: 5 - tblName: mib29
Record: 1792 ActvComdID: 0 StdbyComID: 7
=============================================================

Note The disk verification utility only logs discrepancies. It does not synchronize the differences.

Troubleshooting Active and Standby Card Disk Discrepancies

If discrepancies are found by the disk verification utility, follow these steps:

Step 1 Locate the logs that pertain to the affected database(s) for the indicated slot.

Step 2 If possible, perform application specific task to resync that DB record. For example, remove and re-install, and re-provision the card.

Step 3 If you can not perform application specific tasks on the card, enter the resetcd command to reset the standby PXM to re-synchronize the database.

If you provision connections while the verifydiskdb check command is running, discrepancies will be flagged, even if the information between the active PXM and the standby PXM is synchronized. To ensure an accurate log of discrepancies, wait for the verifydiskdb check to finish running before you provision connections.

Configuring a Line Loopback

If a connection fails and you do not know which end of the connection is causing the problem, putting a line into loopback mode can help you determine what the problem is and where it occurs on a connection. In an MGX 8830 and an MGX 8850, loopback lines provide CLI-based line level monitoring capabilities.

When a line is put into loopback, the receiving switch takes all of the data it receives and returns it unchanged back to the sender. The physical line in a loopback configuration is connected between a CPE and a switch; one physical line is connected from the tx (Transmit port) of the CPE to the rx (receive) port of a card on the switch you are testing. Another physical line is connected between the tx port of the same card and the receive port of the CPE.

Configuring Loopback Line Tests on PXM1E and AXSM Cards

Once the physical connection is established, you need to use the CLI to put the connection into loopback mode.

The following types of loopback are supported on PXM1E and AXSM cards:

•Far-end line loopback - Loopback appears at the far-end of the CPE when you send a loopback activation code from the PXM1E. The CPE enters a loop mode in which it returns the received data back to the PXM1E. The CPE continues to return the data back until it receives a no-loopback request.This kind of loopback can be used to run tests, such as BERT.

•Far-end payload loopback- Loopback is similar to FarEnd loopback, except that the payload portion of the data is re-transmitted. Framing is done by the Far end again.

•Remote line loopback - Loopback returns the remote data back to the far end. The received data stream is looped back into the transmit path, overriding the data stream created internally by the framer.

•Local loopback - Loopback allows the transmitted data to be looped back into the receiving path. It can be used to test the internal hardware of the card.

Once your physical line is connected, you can perform a loopback test using the following procedure.

Step 1 Connect a single line to the appropriate transfer and receive ports on the backcard you want to test.

Step 2 Establish a configuration session with the active PXM1E or AXSM card using a user name with SERVICE_GP privileges or higher.

Step 3 Enter the dsplns command to display the configuration for all lines on the current card.

Step 4 Enter the addlnloop <-line type> <bay.line> <-lpb loopback type> command.

addlnloop -ds3 2.1 -lpb 2

Step 5 Enter the dspln -<line type> <line_num> command to verify the that the appropriate line is in the specified loopback state.

dspln -ds3 4.1

Note Before you can change the loopback type for an existing loopback, you must first delete the loopback by executing dellnloop, or you can just enter the addlnloop command with the -lpb 1 (No loopback) option.

Configuring a Line Loopback on a CBSM

Once your physical line is connected, you can perform a loopback test using the following procedure.

Step 1 Connect a single line to the appropriate transfer and receive ports on the backcard you want to test.

Step 2 Establish a configuration session with the active PXM1E or AXSM using a user name with SERVICE_GP privileges or higher.

Step 3 Enter the dsplns command to display the configuration for all lines on the current card.

Step 4 Enter the addlnloop <-line type> <bay.line> <-lpb loopback type> command.

addlnloop -ds3 2.1 -lpb 2

Step 5 Enter the dspln -<line type> <line_num> command to verify the that the appropriate line is in the specified loopback state.

dspln -ds3 4.1
Before you can change the loopback type for an existing loopback, you must first delete the loopback by executing dellnloop, or you can just enter the addlnloop command with the -lpb 1 (No loopback) option.

Managing Bit Error Rate Tests

BERT commands can help you analyze and resolve problems on a physical interface. To conduct a BERT on a line, a user sends a specified pattern over a line that is configured in loopback mode at the far end. The local end receives the loopback pattern, and the user compares the local end pattern to the original pattern sent from the far end. The number of bit errors discovered in the local (or receive) end pattern help the user determine the quality of the physical line.

Note BERT is only available for T1 lines and IMA cards.

Configuring a Bit Error Rate Test

Use the following procedure to configure BERT on an MGX switch.

Step 1 Put the appropriate lines into loopback mode.

Step 2 Establish a configuration session with the active PXM1E or PXM45 using a user name with SERVICE_GP privileges or higher.

Note BERT commands are available only on PXM1E and PXM45 cards. However, you can run BERT on any service modules that support T1 lines or IMA.

Step 3 Enter the dspbertcap command to display the loopback and BERT capabilities of a specific line or port on the current card. The display shows you which test patterns and loopback numbers are available on the current service module.

dspbertcap <SM Interface> <Test Option>

Table 13-31 describes the dspbertcap command parameters.

Table 13-31 dspbertcap Command Parameters

Parameter

Description

SM Interface

The format of Service Module Interface is: SMslot.SMLine[.SMport], as follows:

•SMslot can have a value in one of the following ranges: 1-6, 9-14, 17-22, 25-30.

•SMLine has a range from 1 though the maximum number of lines on the card.

•The optional SMport has a value from 1 though the maximum ports supported by the service module.

Test Option

Type one of the following numbers to select the capability to display:

1: BERT capability

2: Loopback capability

Step 4 Enter the cnfbert command as follows to set up BERT parameters on the looped back connection. You must use the available test patterns and loopback numbers displayed with the dspbertcap command in Step 3.

Unknown.7.PXM.a > cnfbert -cbif <LSMnum> -pat <bertPattern> -lpbk <lpbk> -sbe <singleBitErrInsert> -cir <dropIteration> -en <enable>

Table 13-32 cnfbert Command Parameters

Parameter

Description

LSMnum

Where LSMnum = LSMslot.Line.Port

LSMslot = 1-6,9-14,17-22,25-30

Line = 1 - MAX_LINES

Port = 1 - MAX_PORTS for Port Test,

0 for Line Test

bertPattern

Test pattern to be generated. See the list of patterns supported for a complete listing. for details use dspbertcap command.

lpbk

For details use dspbertcap command.

singleBitErrInsert

Different options of error insertion rates, where singleBitErrInsert is "1" (noError), or "| 2" (insert).

Note Injection of bit error should be done after configuring BERT

dropIteration

where dropIteration is between 1 and 32, used only if loopback is 5:latchDS0Drop.

enable

Enables/disables BERT. Enter "4" to enable BERT or "6" to disable BERT.

In the following example, the user enables a BERT on line 1 in port 0 on the service module in slot 25. The BERT pattern is set to 1 (all zeros), and loopback is set to 14.

Unknown.7.PXM.a > cnfbert -cbif 25.1.0 -pat 1 -lpbk 14 -en 6

Step 5 After the BERT has been running for at least 30 minutes, enter the dspbert <bay> command to display the BERT result. Replace bay with 0 to indicate the upper bay, or 1 to indicate the lower bay.

Note For the PXM1E, the bay will always be 2 because BERT is only run on the lower bay. BERT is supported on both bays for AXSM cards.

Note The dspbert command can be issued even while the BERT is in operation.

Unknown.7.PXM.a > dspbert 2

Replace bay with 1 to indicate the lower bay.

Unknown.7.PXM.a > dspbert 2

Start Date : 08/29/2002
Current Date : 08/29/2002
Start Time : 18:43:07
Current Time : 16:56:23
Physical Slot Number : 22
Logical Slot Number : 22
Line Number : 1 (Line test)
Device To Loop : Local Loopback
BERT Pattern : Double One Zero Pattern
Error Inject Count : 0
Bit Count : 3091031099
Bit Count Received : 3091031099
Bit Error Count : 0
Bit Error Rate (BER) : 0
Bit Counter Overflowed : 6 <times>

BERT is in sync.
Deleting a Configured Bit Error Rate Test

There are two ways to terminate a configured BERT.

1. Enter the delbert <SM Interface> command. Replace <SM Interface> with the service module interface number in the format slot.line.port. In the following example, the user deletes BERT from line 1 on port 2 in the PXM1E in slot 7.

Unknown.7.PXM.a > delbert 7.1.1

2. Enter the cnfbert command with the -en option disabled. (See Table 13-32 for a description of the cnfbert command parameters.)

Unknown.7.PXM.a > cnfbert -cbif 25.1.0 -pat 1 -lpbk 14 -en 6

Diagnostics Support on PXM1E and AXSM Cards

Diagnostics tests run on all the major hardware components that belong to the PXM1E or AXSM front card and its lower back cards, and the connection path between these components. You can configure a hardware-oriented test to check the health of the active and standby PXM1E or AXSM front card. Tests can be run on standby card, the active card, or both cards at the same time.

PXM1E and AXSM cards support both online and offline diagnostics.

•Online diagnostics tests run in the background while a card is in an operational state. These tests are non-intrusive and run with minimal overhead. Online diagnostics can be used to detect hardware errors diagnosis. Its goal is to monitor any potential errors at a card level while a card is in normal operation. You can stop a test at any time by issuing a new diagnostic configuration to disable it. If the online diagnostics test fails on an active AXSM, a switchover is triggered and the active card becomes the standby, and an error message comes on declaring the standby card as failed. If the online diagnostics test fails on an active PXM1E, no switchover is triggered.

Note Online diagnostics do not detect operational errors.

•Off-line diagnostics ensure the standby card is ready to be switched over to. Offline diagnostics tests are performed only on the standby card. Areas for diagnosis include hardware components and cell paths. Off-line diagnostics are destructive. Intensive tests are performed on a card including memory tests and registers read/write tests. It temporarily puts a standby card out of service and makes it unavailable to be switched over to in case of active card failure. When tests are done, the card is reset to its normal state. If the active card fails while the standby card is running off-line diagnostics, off-line diagnostics are immediately aborted

Note Off-line diagnostics will not be performed on AXSM cards with APS configured.

AXSM cards run offline diagnostics in the following areas:

•Processor subsystem: NVRAM and BRAM

•ASIC tests: Atlas (register test, ingress memory, egress memory) and framer (register test)

PXM1E cards run registered offline diagnostics on UI- S3 or UI-S3/B back cards.

Both control path and data path must to be tested in order to have a complete test coverage on the entire connection path within a card. The control path is the path that carries IPC messages between cards. The diagnostic data path is the path for cells travelling between the backplane and the loop back device.

Configuring Offline and Online Diagnostics Tests on PXM1E and AXSM Cards

Enter the cnfdiag command as follows to enable online diagnostics tests on PXM1E or AXSM cards:

MGX.7.PXM.a > cnfdiag <slot> <onEnb> <offEnb> [<offCover> <offStart> <offDow>]

Table 13-33 tells you how to set these parameters to run online diagnostics tests on PXM1E and AXSM cards.

Table 13-33 cnfdiag Command Parameters

Parameter

Description

slot

Enter the slot of the card for which to configure the diagnostics. For the PXM1E, the slot number will be 7 or 8.

onEnb

Enter enable to enable online diagnostic on the card. Enter disable to disable online diagnostics.

offEnb

Enter enable to enable offline diagnostics. Enter disable to disable offline diagnostics.

offCover

Set the offline diagnostics coverage time to light, medium, or full.

light = 5 minutes or less

medium = 30 minutes or less

full = any number of minutes-no limit

Note You do not need to set this parameter if you are not enabling offline diagnostics.

offStart

Set the time for the offline diagnostics to begin using 24 hour time. The format is: hh:mm. For example: 03:45 or 22:30

Note You do not need to set this parameter if you are not enabling offline diagnostics.

offDow

Sets the day of the week for the offline diagnostics to run. The format is SMTWTFS.

Note You do not need to set this parameter if you are not enabling offline diagnostics.

Warning Do not remove the active PXM while the offline diagnostic is running on the redundant PXM. If you remove it, the redundant PXM reboots but will not be able to become active unless its hard disk drive was previously synchronized to the hard disk on the previously active PXM.

Example 13-1 Configuring online diagnostics only

In the following example, the user enables online diagnostics only for the PXM1E in slot 7.

MGX.7.PXM.a > cnfdiag 7 enable disable

Example 13-2 Configuring offline diagnostics only

In the following example, the user enables online diagnostics for the PXM1E in slot 7. A medium online diagnostics coverage test is scheduled to run every Wednesday at 11:30 (11:30 AM).

MGX.7.PXM.a > cnfdiag 7 disable enable medium 11:30 -W-

Example 13-3 Configuring both online and offline diagnostics at the same time

In the following example, the user enables both online and offline diagnostics for the PXM1E in slot 8. A medium offline diagnostics coverage test is scheduled to run every Monday and Friday at 21:30 (8:30 PM).

MGX.7.PXM.a > cnfdiag 7 enable enable medium 21:30 -M-F-

To display your online diagnostics test configuration and ensure all the parameters have been set correctly, enter the dspdiagcnf command.

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

Enter the cnfdiagall command as follows to enable and configures online or offline diagnostics for all card slots:

MGX_a.7.PXM.a > cnfdiagall <slot> <onEnb> <offEnb> [<offCover> <offStart> <offDow>]

Table 13-34 describes the cnfdiagall command parameters.

Table 13-34 cnfdiagall Command Parameters

Parameter

Description

onEnb

Enable or disable online diagnostics. The default is disable.

offEnb

Enable or disable offline diagnostics. The default is disable.

offCover

Set the offline diagnostics coverage time to light, medium, or full.

•light = 5 minutes or less

•medium = 30 minutes or less

•full = any number of minutes-no limit

offStart

Set the time for the offline diagnostics to begin using 24 hour time. The format is: hh:mm. For example: 03:45 or 22:30

offDow

Sets the day of the week for the offline diagnostics to run. The format is SMTWTFS. For example: -M-W--- is Mondays and Wednesdays only.

Example 13-4 Configuring online diagnostics only

In the following example, the user enables online diagnostics only for all cards in the switch.

Unknown.7.PXM.a > cnfdiagall 7 enable disable

Example 13-5 Configuring offline diagnostics only

In the following example, the user enables online diagnostics for all cards in the switch. A medium online diagnostics coverage test is scheduled to run every Wednesday at 11:30 (11:30 AM).

Unknown.7.PXM.a > cnfdiagall 7 disable enable medium 11:30 -W-

Example 13-6 Configuring both online and offline diagnostics at the same time

In the following example, the user enables both online and offline diagnostics for all cards in the switch. A medium offline diagnostics coverage test is scheduled to run every Monday and Friday at 21:30 (8:30 PM).

Unknown.7.PXM.a > cnfdiagall 7 enable enable medium 21:30 -M-F-

To display your online diagnostics test configuration and ensure all the parameters have been set correctly, enter the dspdiagcnf command.

Displaying Online and Offline Diagnostics Test Configuration Information

Enter the dspdiagcnf command to display the current diagnostics configuration on a card. The dspdiagcnf command displays the following information:

•Slot number

•Whether online diagnostics are enabled or disabled

•Whether offline diagnostics are enabled or disabled

•The type of coverage currently running for offline diagnostics

•The Start time for offline diagnostics

•The day(s) of the day on which offline diagnostic tests are scheduled to run.

The following example shows the information displayed by the dspdiagcnf command.

Unknown.7.PXM.a > dspdiagcnf
Online -------------- Offline -------------
Slot Enable Enable Coverage StartTime SMTWTFS
---- ------ ------ -------- --------- -------
1 enable enable light 15:13 ---W---
2 enable enable light 15:13 ---W---
3 enable enable light 15:13 ---W---
4 enable enable light 15:13 ---W---
5 enable enable light 15:13 ---W---
6 enable enable light 15:13 ---W---
7 disable enable light 15:13 ---W---
8 enable enable light 15:13 ---W---
9 enable enable light 15:13 ---W---
10 enable enable light 15:13 ---W---
11 enable enable light 15:13 ---W---
12 enable disable light 15:13 ---W---
13 enable enable light 15:13 ---W---
14 enable enable light 15:13 ---W---
15 disable disable light 15:13 ---W---
16 disable disable light 15:13 ---W---
17 enable enable light 15:13 ---W---
18 enable enable light 15:13 ---W---
19 enable enable light 15:13 ---W---

Type <CR> to continue, Q<CR> to stop:
20 disable disable light 00:00 SMTWTFS
21 disable disable light 00:00 SMTWTFS
22 disable disable light 00:00 SMTWTFS
23 disable disable light 00:00 SMTWTFS
24 disable disable light 00:00 SMTWTFS
25 disable disable light 00:00 SMTWTFS
26 disable disable light 00:00 SMTWTFS
27 disable disable light 00:00 SMTWTFS
28 disable disable light 00:00 SMTWTFS
29 disable disable light 00:00 SMTWTFS
30 disable disable light 00:00 SMTWTFS
31 disable disable light 00:00 SMTWTFS
32 disable disable light 00:00 SMTWTFS

Displaying Online Diagnostic Errors

Enter the dspdiagerr online command to display the current online diagnostics errors for all cards in a switch.

Unknown.7.PXM.a > dspdiagerr online
Slot Date Time Message
---- ---- ---- -------
1 -- --
2 -- --
3 -- --
4 -- --
5 -- --
6 -- --
7 -- --
8 -- --
9 -- --
10 -- --
11 -- --
12 -- --
13 -- --
14 -- --
15 -- --
16 -- --
17 -- --
18 -- --
19 -- --
20 -- --

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

Displaying Offline Diagnostic Errors

Enter the dspdiagerr offline command to display the current online diagnostics errors for all cards in a switch,

Unknown.7.PXM.a > dspdiagerr offline
Slot Date Time Message
---- ---- ---- -------
1 -- --
2 -- --
3 -- --
4 -- --
5 -- --
6 -- --
7 -- --
8 -- --
9 -- --
10 -- --
11 -- --
12 -- --
13 -- --
14 -- --
15 -- --
16 -- --
17 -- --
18 -- --
19 -- --
20 -- --

Type <CR> to continue, Q<CR> to stop: 21 -- --
Enter the dspdiagstat command to display the number of times that the diagnostics has run. The output shows the number of attempts and the number of failures for both offline and online diagnostics.

Unknown.7.PXM.a > dspdiagstat 7

Slot 7 diagnostics statistics:

online diag attempted = 0x00001a26
online diag passed = 0x00001a26
online diag failed = 0x00000000
offline diag attempted = 0x00000000
offline diag passed = 0x00000000
offline diag failed = 0x00000000

Enter the dspdiagstatus command to display the diagnostics status and role (active or standby) for each card on the switch. The diagnostics statuses are:

•Idle—Slot is in an idle state because there is no card in the slot, or due to an error.

•Ready—Card is active and ready for diagnostics test.

•Offline—Card is offline.

•Online—Card is online,

Enter the dspdiagstatus command as shown in the following example:

Unknown.7.PXM.a > dspdiagstatus
Slot State Role
---- ----- ----
1 Idle UNKNOWN CARD ROLE
2 Idle UNKNOWN CARD ROLE
3 Idle UNKNOWN CARD ROLE
4 Idle UNKNOWN CARD ROLE
5 Idle UNKNOWN CARD ROLE
6 Idle UNKNOWN CARD ROLE
7 Ready ACTIVE CARD ROLE
8 Idle UNKNOWN CARD ROLE
9 Idle UNKNOWN CARD ROLE
10 Idle UNKNOWN CARD ROLE
11 Idle UNKNOWN CARD ROLE
12 Idle UNKNOWN CARD ROLE
13 Idle UNKNOWN CARD ROLE
14 Idle UNKNOWN CARD ROLE
15 Ready ACTIVE CARD ROLE
16 Idle UNKNOWN CARD ROLE
17 Idle UNKNOWN CARD ROLE
18 Idle UNKNOWN CARD ROLE
19 Idle UNKNOWN CARD ROLE
20 Idle UNKNOWN CARD ROLE

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

Enabling and Disabling IMA Group ATM Cell Layer Parameters

The cnfatmimagrp allows you to enable and disable the following ATM cell layer parameters on an IMA group:

•payload scrambling

•AIS

To configure ATM cell layer parameters on an IMA group, enter the cnfatmimagrp command as follows:

cnfatmimagrp -grp <bay.group> -sps <PayloadScramble> -ais <aisMode>

In the following example, the user enables payload scrambling and AIS on the ATM IMA group 14 on the PXM1E in the lower bay.

Unknown.7.PXM.a > cnfatmimagrp -grp 2.14 -sps 1 -ais 1

Table 13-35 describes the parameters for the cnfimagrp command.

Table 13-35 cnfatmimagrp Command Parameters

Parameter

Description

-grp <bay.group>

The bay number and the IMA group number.

• bay: Enter 2 for the lower bay.

•grp: 1-16

Note On the PXM1E, the bay number is always 2.

sps <PayloadScramble>

Enable of disable payload scrambling. Default: enabled.

• 1 = enable

• 2 = disable

ais <aisMode>

Enables or disables the alarm indication signal (AIS) mode. The AIS is an all-ones signal that is transmitted instead of the normal signal to maintain transmission continuity and to indicate to the receiving terminal that there is a transmission fault that is located either at the transmitting terminal or upstream from the transmitting terminal.

•1 = Enable AIS transmitting.

•2 = Disable AIS transmitting.

Default = Enable

Enter the dspatmimagrp <bay.group> command to display whether AIS and payload scrambling are enabled or disabled for an IMA group, as shown in the following example:

Satire.2.PXM.a > dspatmimagrp 2.1
GrpNum HCScoset PayloadScramble NullCellHdr NullCellPayload AIS
------- --------- --------------- ----------- --------------- -------
2.1 Enable Disable 0x00000001 6a Enable

Maintaining IMA

The sections that follow describe how to do the following tasks:

•display IMA groups

•display IMA links

•delete IMA groups

•deleting IMA links

•restart an IMA group

Displaying IMA Groups

To display general information about all configured IMA groups on the current PXM1E-16-T1E1, AXSM-32-T1E1-E, or AUSM/B card, enter the dspimagrps command, as shown in the following example:

Unknown.7.PXM.a > dspimagrps

Ima Min Tx Rx Tx Diff NE-IMA FE-IMA IMA
Grp Lnks Frm Frm Clk Delay state state Ver
Len Len Mode (ms)
--------------------------------------------------------------------------------
2.1 1 128 128 CTC 100 StartUp StartUp 1.0
2.2 3 128 128 CTC 100 StartUp StartUp 1.1
2.3 3 128 128 CTC 100 StartUp StartUp 1.1

To display detailed information about a specific IMA group, enter the dspimagrp <bay.group> command. Replace bay with the number 1 to specify the top bay, or 2 to specify the lower bay. Replace group with the IMA group number.

In the following example, the user displays information about the IMA group 2 in the lower bay.

nknown.7.PXM.a > dspimagrp 2.2

Group Number : 2.2
NE IMA Version : Version 1.1
Group Symmetry : Symm Operation
Tx Min Num Links : 3
Rx Min Num Links : 3
NE TX Clk Mode : CTC
FE TX Clk Mode : CTC
Tx Frame Len : 128
Rx Frame Len : 128
Group GTSM : Down
NE Group State : StartUp
FE Group State : StartUp
Group Failure Status : Other Failure
Tx Ima Id : 2
Rx Ima Id : 0
Max Cell Rate (c/s) : 0
Avail Cell Rate (c/s) : 0
Diff Delay Max (msecs) : 100
Diff Delay Max Observed (msecs) : 0
Accumulated Delay (msec) : 0
GTSM Up Integ time(msec) : 10000
GTSM Dn Integ time(msec) : 2500

Type <CR> to continue, Q<CR> to stop:
Num Tx Cfg Links : 0
Num Rx Cfg Links : 0
Num Act Tx Links : 0
Num Act Rx Links : 0
Least Delay Link : Unknown
Tx Timing Ref Link : Unknown
Rx Timing Ref Link : Unknown
Group Running Secs : 0
Alpha Val : 2
Beta Val : 2
Gamma Val : 1
Tx OAM Label : 3
Rx OAM Label : 0
Test Pattern Procedure Status : Disabled
Test Link : Unknown
Test Pattern : 255
Stuff Cell Indication (frames) : 1
Displaying IMA Links

Enter the dspimalnk <bay.link> command to display configuration information for the specified IMA link. Replace bay with the number 1 to specify the top bay, or 2 to specify the lower bay. Replace link with the number of the link you want to display, in the range from 1 through 16.

In the following example, the user displays information about the IMA link 1 in the lower bay.

Satire.2.PXM.a > dspimalnk 2.1
IMA Link Number : 2.1
IMA Link Group Number : 2.1
Link Rel Delay (msecs) : 0
Link NE Tx State : Unusable-Failed
Link NE Rx State : Not In Grp
Link FE Tx State : Not In Grp
Link FE Rx State : Not In Grp
Link NE Rx Failure Status : LIF Fail
Link FE Rx Failure Status : No Failure
IMA Link Tx LID : 0
IMA Link Rx LID : 255
Link Rx Test Pattern : 255
Link Test Procedure Status : Disabled
Link LIF Integ UpTime : 2500
Link LIF Integ DownTime : 10000
Link LODS Integ UpTime : 2500
Link LODS Integ DownTime : 10000
Deleting an IMA Group

To delete an IMA group, enter the delimagrp <bay.group>. Replace bay with the number 1 to specify the top bay, or 2 to specify the lower bay. Replace group with the IMA group number you want to delete.

In the following example, the user deletes the IMA group 3 in the lower bay.

Unknown.7.PXM.a > delimagrp 2.3

Enter the dspimagrps command to ensure that the correct IMA link is deleted.

Deleting an IMA Link

To delete an IMA link, enter the delimalnk <link> command. Replace bay with the 2 to specify the lower bay. Replace link with the IMA link you want to delete, in the range from 1 through 16.

In the following example, the user deletes the IMA link 3 in the lower bay.

Unknown.7.PXM.a > delimalnk 2.3

Enter the dspimalnks command to ensure that the correct IMA link is deleted.

Satire.2.PXM.a > dspimalnks
Link Grp Rel NE NE NE Rx Tx Rx
Num Num Dly Tx Rx Fail LID LID
(ms) State State Status
------------------------------------------------------------------------------
2.1 2.1 0 Unusable-Failed Not In Grp LIF Fail 0 255
2.2 2.1 0 Unusable-Failed Not In Grp LIF Fail 0 255
2.4 2.1 0 Unusable-Failed Not In Grp LIF Fail 0 255

Restarting an IMA Group

To restart an IMA group, enter the restartimagrp <bay.group> command. Replace bay with the number 1 to specify the top bay, or 2 to specify the lower bay. Replace group with the IMA group you want to restart, in the range from 1 through 16.

After you enter the restartimagrp command, the IMA group attempts to re-establish the IMA protocol with far end of a failed connection.

In the following example, the user attempts to restart the IMA group number 6 in the lower bay.

Unknown.7.PXM.a > restartimagrp 2.6

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.

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.

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)

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

Parameter	Description
bay	Working bay number to switch.
line	Working line number to switch.
switchOption	Method of performing the switchover. The possible methods are as follows: •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 priority is in effect. This option has the same priority as option 3 (forced working to protection line switchover). Therefor, if a forced working to protection line switchover is in effect, it must be cleared before this option (forced protection to working line switchover) can succeed. •5 = Manual switchover from working to protection line unless a request of equal or higher priority is in effect. •6 = Manual switchover from protection to working line. This option is only available in the 1+1 APS architecture.
service switch	This is an optional parameter. When set to 1, this field causes all APS lines to switch to their protected lines.

Option	Description
-w	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	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.
-proto	The protocol option, which determines whether the switch will use the standard Bellcore protocol, or the ITU protocol.

Option	Value	Description
switchOption	1	Clear
	2	Lockout of protection
	3	Forced working->protection
	4	Forced protection->working
	5	Manual working->protection
	6	Manual protection->working; applies only to 1+1 mode
serviceSwitch	0 or 1	0 switches specified line. 1 switches all lines.

Active Line	Working Line	Protection Line	Working Line LED	Protection Line LED	Description
Working	OK	OK	Green	Green	Active card is receiving signal on working and protection lines. This does not guarantee that transmit lines are functioning properly. You must view the status on remote switch.
Protection	SF	OK	Green	Red	Active card is receiving signal on the protection line. No signal received on the working line.
Working	OK	SF	Green	Red	Active card is receiving signal on the working line. No signal received on the protection line.
Working	SF	SF	Red	Red	Active card is not receiving signal from either line. The working line was the last line to work.
Protection	SF	SF	Red	Red	Active card is not receiving signal from either line. The protection line was the last line to work.
Working	UNAVAIL	UNAVAIL			The card set is not complete. One or more cards have failed or been removed. See Table 13-9 to troubleshoot card errors.

APS Line Failure	Possible Cause
All lines in upper and lower bays.	Suspect a bad or removed front card. If both front cards are good, both back cards may be bad.
All lines in upper bay only. Lower bay APS lines OK.	Suspect bad upper bay back card.
All lines in lower bay only. Upper bay APS lines OK.	Suspect bad lower bay back card.

Parameter	Description
-server	Toggles the primary SNTP server on or off.
-stratum	Stratum of the SNTP client. The default is 0.

Parameter	Description
server IP address	The IP address of the switch you want to be a remote SNTP server.
version	The SNTP version you are using. Possible options are 3 and 4. Default: 3
-primary	This parameter lets you identify the switch as the primary SNTP server. Type -primary yes to make the primary server. To change the remote switch to a secondary server, type -primary no. Default: no

Parameter	Description
client:	Shows whether the SNTP client is turned on or off.
server:	Shows whether the SNTP server is turned on or off.
polling:	Shows the current number of seconds set on the polling timer. When this timer expires, the client requests TOD from the server.
waiting:	Shows the current number of seconds set on the waiting timer. If this timer expires three times, the client switches over to the first available secondary server for TOD. Default = 5 seconds
rollback:	When a client switches over to the secondary server for TOD requests, the rollback timer takes affect and continues polling the primary server for TOD each time the rollback timer expires. The rollback timer continues polling the primary server until it comes back up. Default = 1024
stratum (default):	Shows the default stratum level.
stratum (current):	Shows the current settings for the stratum level.
sync:	Shows whether the SNTP client and server are in sync.

Parameter	Description
-distributionMode	This option selects either NCDP or manual mode clock distribution. To select NCDP mode, enter 1. To select manual clock distribution, enter 2. The default is 1 for NCDP.
-maxNetworkDiameter	This option specifies the maximum network diameter in hops. This is the maximum length of the spanning tree. The range is 3 to 200, and the default is 20.
-hello	This option specifies the NCDP hello packet interval. NCDP hello packets advertise the best network clock source. The range is 75 to 60000 milliseconds, and the default is 500 milliseconds.
-holdtime	This option specifies the hold time interval. The range is 75 to 60000 milliseconds, and the default is 500 milliseconds.
-topoChangeTimer	This option specifies the topology change timer interval. The range is 75 to 60000 milliseconds, and the default is 500 milliseconds.

Parameter	Description
port-id	Port identifier. For clocking ports on Cisco MGX 8850 (PXM1E/PXM45) and Cisco MGX 8950 switches, the port identifier is 7.35 or 7.36. For clocking ports on Cisco MGX 8830 switches, the port identifier is 1.35 or 1.36. For an internal oscillator, the port identifier is 255.255.
prs -id	Determines the primary reference source. Enter 0 for an external source, or 255 for an internal source.
-clocktype	Enter e1 or t1 as needed when the port ID is one of the following: •7.35 or 7.36 in an MGX 8950 or MGX 8850 chassis •1.35 or 1.36 in an MGX 8830 chassis Note The default port type for 7.35/1.35 is E1. The default port type for 7.36/1.36 is T1. However, you can configure the BITS clocks portid 7.35/1.35 to be T1, or 7.36/1.36 to be E1, through the -clocktype parameter.
-priority	Prioritizes the clock source. Enter a number in the range from 1 to 255. Default = 128
-stratumLevel	Determines the stratum level of the clock source. Possible levels are 1, 2E, 2, 3E, 3, 4E, or 4. Default = 3

Parameter	Description
portid	Port identifier in the format slot:bay.line:ifnum. These parameters are described in Table 13-1.
-ncdp	Enables/disables NCDP on the current port. Default = disable
-vpi	Reserved VPI of the signaling channel, in the range from 0 through 4095. There is no reason to change this number unless a relevant card's partition is intended to support a specific VPI. Note If you change the VPI, it must be within the valid partition range or it will be disabled. Note You must disable NCDP before you modify the VPI of the signaling channel. Default = 0
-vci	Reserved VCI of the signaling channel, in the range from 32 through 65535. Normally, no reason exists to change it. Note If you change the VCI, it must be within the valid partition range or it will be disabled. Note You must disable NCDP before you modify the VCI of the signaling channel. Default = 34
-admincost	Sets the routing cost of the port, in the range from 1 through (2^24-1). For example, if the equipment were in an area with a large amount of electronic noise, or if the switch carried a particularly large amount of traffic, you might want to raise the cost.) Default = 10
-pcr	Specifies the PCR^¹ for the port. Default = 250 cells per second
-scr	Specifies the SCR^² for the port. Default = 150 cells per second
-mbs	Specifies the MBS^³ for the port. Default = 100 cells

Parameter	Description
Distribution Mode	Current enabled method of clock distribution. If the method chosen is manual, NCDP is turned off, and vice-versa.
Node stratum level	Stratum level of the clock source. Possible levels are 1, 2E, 2, 3E, 3, 4E, or 4.
Max network diameter	Maximum network diameter measured in hops.
Hello time interval	Time interval between each configuration pdu sent out by a node to advertise the best clock source in the network. This time interval is specified in milliseconds in the display.
Holddown time interval	Number of milliseconds the switch waits before it transmits the next configuration PDU.
Topology change time interval	Time interval for which the topology change detection field in the configuration pdu bit will be set. Having the topology change detection option set informs the recipient node that it needs to transmit configuration pdus out to advertise to its neighbors about recent topology or root clock changes.
Root Clock Source	Clock port from which the node is deriving the clock signal. 255.255 means the node is deriving the clock source from an internal oscillator.
Root Clock Source Reason	The reason for the most recent change of a source of network clock. For a detailed description of the reasons a clock source can change, refer to Table 2-12 in the Cisco MGX 8850 (PXM1E/PXM45), Cisco MGX 8950, and Cisco MGX 8830 Command Reference.
Root Clock Source Status	Status of the network's root clock source.
Root Stratum Level	Stratum level of the network's root clock source. Possible levels are 1, 2E, 2, 3E, 3, 4E, or 4.
Root Priority	Priority of the network's root clock source.
Secondary Clock Source	Secondary clock port from which the node is deriving the clock signal. 255.255 means the node is deriving the clock source from an internal oscillator.
Secondary Clock Source Reason	The reason for the most recent change of the secondary network clock source. For a detailed description of the reasons a clock source can change, refer to Table 2-12 in the Cisco MGX 8850 (PXM1E/PXM45), Cisco MGX 8950, and Cisco MGX 8830 Command Reference.
Secondary Clock Source Status	Status of the network's secondary clock source.
Last clk src change time	Time when the root clock source last changed.
Last clk src change reason	Reason why the root clock source last changed.

Parameter	Description
Best clock source	Describes whether the specified clock source is currently the best (or root) clock source in the network.
Priority	Displays the specified clock source's priority.
Stratum Level	Stratum level of the specified clock source. Possible levels are 1, 2E, 2, 3E, 3, 4E, or 4.
Primary reference src id	Displays the specified clock sources ID.
Health	Describes the current health of the specified clock source. The possible health states ar described below. Good—Specified clock source is the current root clock or the second best clock source, and is in good condition. Bad—Specified clock source was the root clock at some point, but went bad and is no longer available. Wideband-Locking—Specified clock source is being qualified by the clock manager and is in wideband-locking mode. Narrowband-Locking—Specified clock source is being qualified by the clock manager and is in narrowband-locking mode. Unknown—Specified clock source is not the root clock source.

Parameter	Description
PortId	Current enabled method of clock distribution. If the method chosen is manual, NCDP is turned off, and vice-versa.
Best clk src	Displays Yes if a clock source is a root clock source or a second best clock source, or displays No if a clock source is not a root or second best clock source.
Priority	Priority of each clock source.
Stratum level	Stratum level of each clock source. Possible levels are 1, 2E, 2, 3E, 3, 4E, or 4.
Prs id	Primary source ID (prs-id) is either 0 for external or 255 for internal.The internal primary source is the free-running oscillator on the PXM back card. (Even though the syntax line and the CLI help indicates a range, the only choice in the current release is 0 or 255.) Default: 255
Health	Describes the current health of each clock source in the network. The possible health states ar described below. Good—Specified clock source is the current root clock or the second best clock source, and is in good condition. Bad—Specified clock source was the root clock at some point, but went bad and is no longer available. Wideband-Locking—Specified clock source is being qualified by the clock manager and is in wideband-locking mode. Narrowband-Locking—Specified clock source is being qualified by the clock manager and is in narrowband-locking mode. Unknown—Specified clock source is not the root clock source.

Parameter	Description
PortId	Port identifier in the format slot:bay.line:ifnum. Table 13-1 describes these parameters.
Clock mode	Displays whether NCDP is enabled or disabled on each port.
Clock VPI	Displays the VPI of the signaling channel for each port.
Clock VCI	Displays the VCI of the signaling channel for each port.
Admin Cost	Displays the routing cost of the port.
NCDP VC	Displays whether the Ncdp VC is up or down.

Parameter	Description
Network clock mode	Displays whether NCDP is enabled or disabled on each port.
NCDP Vc status	Displays whether the Ncdp VC is up or down.
Network clock VPI	Displays the VPI of the signaling channel for each port.
Network clock VCI	Displays the VCI of the signaling channel for each port.
Admin Cost	Displays the routing cost of the port.
Service Category	Displays the service category for the current NCDP port.
PCR	Displays the PCR^¹ for the port.
SCR	Displays the SCR^² for the port.
MBS	Displays the MBS^³ for the port.

Parameter	Description
portid	The format of the PNNI physical port identifier can vary, as follows: •On a PXM45: slot:subslot.port:subport •On a PXM1E for UNI/NNI back card: slot:subslot.port:subport. On the UNI/NNI back card, the subslot is always 2, but the slot depends on the chassis, as follows: –In an MGX 8850 chassis, slot is always the logical slot 7. –In an MGX 8830 chassis, slot is always the logical slot 1. •On a PXM1E for a cell bus service module (CBSM): slot.port. For BITS clocks only, the default portid is 7.35(for E1 ports) or 7.36 (for T1 ports).In an MGX 8830 chassis, the default portid for BITS is either 1.35 (for E1 ports) or 1.36 (for T1 ports). Note If the portid was modified, so that the BITS clocks portid 7.35/1.35 has been configured as a T1 (instead of an E1 port), or if 7.36/1.36 has been configured to be an E1 port (instead of a T1 port), then you must specify the clocktype in the delncdpclksrc command.
clocktype	Enter e1 or t1 as needed when the port ID is one of the following: •7.35 or 7.36 in an MGX 8950 or MGX 8850 chassis •1.35 or 1.36 in an MGX 8830 chassis If the clock type is the default E1, this parameter is not necessary for port IDs 7.35 or 7.36 (or 1.35.or 1.36). Default: e1

Parameter	Description
<cntrlrId>	Number that identifies a network controller. The numbers are reserved as follows: •2 = PNNI •3 = Label Switch Controller (LSC), also known as Multiprotocol Label Switch Controller (MPLS). This option is not supported on PXM1E cards. Note The controller ID (cntrlrId) must be the same as the controller type (cntrlrType).
i	Keyword indicating that this controller is internal.
<cntrlrType>	Number that identifies a network controller. The numbers are reserved as follows: •2 = PNNI •3 = LSC (Label Switch Controller, also known as MPLS. This option is not supported on PXM1E cards. 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.

Parameter	Description
ifNum	Interface number or port number. This number identifies the port this resource partition configures. Enter the interface number that was assigned to the port when it was configured.
controllerNum	Controller number. 1 = PAR (Portable AutoRoute)—Not supported in this release. 2 = PNNI—Only PNNI is supported in this release. 3 = TAG (MPLS)—Not supported in this release. Note This parameter applies only to FRSM12 cards.
partId	Partition identification number. Enter a number in the range of 1 to 20. Partition ID 1 is reserved for PNNI. Note This parameter applies only to PXM1E and AXSM cards.
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 setting for PNNI must be 100% or less, and must be less than the sum of the egrmaxbw settings. Note This parameter applies only to PXM1E and AXSM cards.
egrmaxbw	Egress maximum bandwidth. Enter the maximum percentage of the outgoing port bandwidth that you want assigned to the controller. One percent is equal to 0.00001 units. For example, an <egrmaxbw> of 1000000 = 100%. The sum of the maximum egress bandwidth settings for PNNI can exceed 100%, and must be more than the sum of the egrminbw settings. Available bandwidth above the minimum bandwidth settings is allocated to the operating controllers on a first-request, first-served basis until the maximum bandwidth setting is met or there is insufficient bandwidth to meet the request. Note This parameter applies only to PXM1E and AXSM cards.
ingminbw	Ingress minimum bandwidth. Enter the minimum percentage of the incoming port bandwidth that you want assigned to the controller. One percent is equal to 0.00001 units. For example, an <ingminbw> of 500000 = 50%. The sum of the minimum ingress bandwidth settings for PNNI must be 100% or less, and must be less than the sum of the ingmaxbw settings. Note This parameter applies only to PXM1E and AXSM cards.
ingmaxbw	Ingress maximum bandwidth. Enter the maximum percentage of the incoming port bandwidth that you want assigned to the controller. One percent is equal to 0.00001 units. For example, an <ingmaxbw> of 750000 = 75%. The sum of the maximum ingress bandwidth settings for PNNI can exceed 100%, and must be more than the sum of the ingminbw settings. Available bandwidth above the minimum bandwidth settings is allocated to the operating controllers on a first-request, first-served basis until the maximum bandwidth setting is met or there is insufficient bandwidth to meet the request. Note This parameter applies only to PXM1E and AXSM cards.
minVpi	Minimum VPI number for this port. For UNI ports, enter a value in the range from 0 to 255. For NNI ports, enter a value in the range from 0 to 4095. Note This parameter applies only to PXM1E and AXSM cards.
maxVpi	Maximum VPI number for this port. For UNI ports, enter a value in the range from 0 to 255. For NNI ports, enter a value in the range from 0 to 4095. The value for <maxVpi> cannot be less than for <minVpi>. Note This parameter applies only to PXM1E and AXSM cards.
minVci	Minimum VCI number for this port. 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. Note This parameter applies only to PXM1E and AXSM cards.
maxVci	Maximum VCI number for this port. Enter a number in the range from 32 to 65535. Note This parameter applies only to PXM1E and AXSM cards.
minConns	Specifies the guaranteed number of connections. On the PXM1E UNI/NNI, the ranges vary according to the line types, as follows: •For OC3, T3, and E3 lines, the range is 10-27000. •For T1 and E1 lines, the range is 10-13500. On the AXSM series of cards, the range is 10 through the maximum number of connections in the port group. Note This parameter applies only to PXM1E and AXSM cards.
maxConns	Maximum number of simultaneous connections allowed on this port. The range is the same as described for the <minConns> parameter. This parameter must be set to number that is greater than the number defined for <minConns>. Note This parameter applies only to PXM1E and AXSM cards.
available connections	Logical channel number. Range: 0-16000. Note This parameter applies only to FRSM12 cards.
minDlci	Lowest data-link connection identifier (DLCI). A value that specifies the DLCI in a Frame Relay network: •Two-byte header—Range: 1-1023 •Four-byte header—Range: 0-8388607 The value specified must be n * 32768, where n is a number from 0 to 255. Note This parameter applies only to FRSM12 cards.
maxDlci	Highest data-link connection identifier (DLCI). A value that specifies a DLCI in a Frame Relay network: •2-byte header—Value range: 1 -1023 •4-byte header—Value range: 0 -8388607 The value specified must be (n * 32768)-1, where n is a number from 1 to 256. Note This parameter applies only to FRSM12 cards.
ingPctBw	Percentage of ingress bandwidth available to the connection. Range: 0-100 percent. Note This parameter applies only to FRSM12 cards.
egrPctBw	Percentage of egress bandwidth available to the connection. Range: 0-100 percent. Note This parameter applies only to FRSM12 cards.

Parameter	Description
portid	Port identifier in the format slot:bay.line:ifnum. These parameters are described in Table 13-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.

Parameter	Description
portid	Port identifier in the format slot:bay.line:ifnum. Table 13-1 describes these parameters.
min-svcc-vpi	Minimum VPI value for SVCC. Range: 0 to 4095. Default = 0.
max-svcc-vpi	Maximum VPI value for SVCC. Range: 0 to 4095. Default = 4095.
min-svcc-vci	Minimum VCI value for SVCC. Range: 32 to 65535. Default = 35.
max-svcc-vci	Maximum VCI value for SVCC. Range: 32 to 65535. Default = 65535.
min-svpc-vpi	Minimum VPI value for SVPC. Range: 1 to 4095. Default = 1.
max-svpc-vpi	Maximum VPI value for SVPC. Range: 1 to 4095. Default = 4095.

Parameter	Description
-bwgrps	Bandwidth groups.
-bwstart	The value for bwstart is the highest cell rate in the lowest-speed bandwidth group. The number of bandwidth groups is fixed at 50. Range: 1-500000 Default: 5000
-bwincr	The increment for the cell rate between the upper and lower bounds of each intermediate bandwidth group. For example, an increment of 2000 means that a range starting at 10000 cps ends at 12000 cps. This increment does not apply to the following groups: •The group with the lowest bandwidth requirements: for this group, the range is determined by the value for bwstart. •The group with the highest bandwidth requirements: for this group, the range is what remains after computations based on the following values: –bwstart –bwincr Range: 1-500000 Default: 1000
-pribuf	The priority buffer is a time counter. It counts down to the moment when PNNI prioritizes all buffered connections for routing. A connection is buffered due to an event that causes PNNI to re-route the connection. The routing events are as follows: •Interface with a master endpoint comes up. •Routed SPVC or SPVP is released (or failed). •SPVC or SPVP is created. •Route optimization begins. Range: 0-600, in units of 0.1 seconds (0-60 seconds) Default: 0
-nodebuf	The node buffer is a time counter. It counts down the time to wait before PNNI starts routing connections. Down-counting begins when the first PNNI logical port comes up. The buffer operates once, after node start-up or node reset. Range: 0-3000, measured in units of 0.1 seconds (0-300 seconds) Default: 0

Command	Description
dsppathtracenode <enable\|disable>	Displays the nodal configuration for the path and connection trace.
dsppathtraceport <portid>	Displays the port configuration for the path and connection trace.
dsppathtraceie <portid>	Displays whether or not TTL 1E is included in the specified port's configuration.
dsppathtracebuffer <portid><vpi><vci>	Displays a specific connection based on the physical port's id, vpi, and vci.
dsppathtracebuffer	Displays all path traces in all the path trace buffers.
conntrace	Displays all path traces in all the path trace buffers.

Parameter	Description
loadSharing	Enables or disables load sharing. Enter -1, 0, or 1. These values control load sharing as follows: •-1 unconditionally disables load sharing, regardless of switch plane status •0 disables load sharing only when there are no switch plane alarms •1 enables load sharing 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 PXM 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.

Parameter	Description
slot	Slot number of the card on which you want to run the disk verification task.
level	Level on verification for the current task. The levels of verification are as follows: 1 = control information 2 = actual data Default = 2
application	Number of times the verification utility will pass through the disk if a discrepancy is found. Multiple passes create the opportunity for software to resolve discrepancies. The number of passes rangers from 1 through 10. Note If no discrepancies are found, the verification utility runs through the disk only once. Default = 3

Parameter	Description
Slot	Current slot whose databases on active and standby PXM hard drives are being compared.
Databases:	Number of databases detected for the current slot.
Tables	Total number of tables detected for all databases for the slot.
DB Index:	Index number of the current database being compared.
DB Name:	Name of the database currently being compared.
Table Details:	Details about the current table being compared.
Table Index:	Index number of the current table being compared.
Table Name:	Name of the current table being compared.
Total Records:	Total number of records.
Records Verified:	Number of records verified.
Databases Verified:	Number of databases verified.
Tables Verified:	Number of tables verified.