MGX 8850 (PXM1E/PXM45), MGX 8950, and MGX 8830 Command Reference, Release 4
exit-
Downloads: This chapterpdf (PDF - 651.0KB) The complete bookPDF (PDF - 8.16MB) | Feedback

enableaxsmbaps

Table Of Contents

enableaxsmbaps

exit

forcecdnative

help

history

insbiterror

ipifconfig

loadrev

logout

ls

optrte

pathtraceie

pathtracenode

pathtraceport

Crankback Option

Tracing All Calls or Specific AESAs

Path Trace Limits

ping

pvcifconfig

pwd

resetcd

resetevtlogsem

resetsys

restoreallcnf

routeShow

routestatShow

rrtparty

rstrtimagrp

rrtcon

runrev

saveallcnf

setcugdefaddr

setipconndebug

setrev

smclrscrn

stackdump

startimalnktst

startuplinkbert

stopimalnktst

stopuplinkbert

svcifconfig

switchapsln

switchcc

switchredcd

telnet

timeout

tstconseg

tstdelay

tstpndelay

upcon

upilmi

upimagrp

upln

upparty

uppnport

upport

users

verifydiskdb

who

whoami

zip


enableaxsmbaps

Enable AXSM/B for APS—PXM45

The enableaxsmbaps command lets you specify that an AXSM/B runs in AXSM/B mode. This command addresses a carry-over from releases prior to Release 3.0. The enableaxsmbaps command is necessary only if you intend the AXSM/B to support APS.

The enableaxsmbaps command runs in the context of a graceful upgrade of AXSM/B firmware from a version of 2.x to 3.0 or higher. If you have an AXSM/B that ran with any version of 2.x firmware and you upgrade to 3.0 or higher and intend to configure APS, you must run the sequence of commands for a graceful upgrade and follow the upgrade by using the enableaxsmbaps command. The sequence of commands is as follows:

1. loadrev

2. runrev

3. commitrev

4. enableaxsmbaps


Note In any version of Release 2.x, you could pair an AXSM/A and AXSM/B to support APS. Beginning with Release 3.0, the AXSM/B must connect to another AXSM/B to support APS.


Syntax

enableaxsmbaps <primary/secondary slot>

Syntax Description

primary slot

The number of the primary slot. The ranges are as follows:

MGX 8850 node: 1-6 and 9-14

MGX 8950 node: 1-6 and 9-16

secondary slot

The number of the secondary slot. The ranges are as follows:

MGX 8850 node: 1-6 and 9-14

MGX 8950 node: 1-6 and 9-16


Related Commands

loadrev, runrev, commitrev

Attributes

Log yes

State: active, standby

Privilege: SUPER_GP


Example

Set the card pair in slot 1 and slot 2 to run in AXSM/B mode.

M8850_LA.8.PXM.a > enableaxsmbaps 1/2
This command will enable the software to use Model B hardware
for APS. Make Sure that Hardware is AXSM Model B and the card
is running the correct software revision.
enableaxsmbaps: Do you want to proceed (Yes/No)? y
ERR: The card present in this slot does not have this feature
ERR: Syntax: enableaxsmbaps <primary/secondary slot>

exit

Exit from User Session—PXM45, PXM1E

Use exit to exit the current user session and log out. To start another session, you must log in by using telnet (for example).

Syntax

exit

Related Commands

bye, logout

Attributes

Log: yes

State: active, standby, init

Privilege: ANYUSER


Example

Exit from the current user session.

MGX8850.8.PXM.a > exit

(session ended)

forcecdnative

Force Card Native—PXM45, PXM1E

The forcecdnative command is used to recover from a PXM failure because of non-nativity issues. This command forces the PXM to ignore nativity and rebuild from the configuration on the disk Running the forcecdnative command causes the PXM to reset, so you are prompted to confirm the operation before it actually runs.


Note This command is available only on a card that is in the failed state.


Syntax

forcecdnative

Syntax Description

This command takes no parameters.

Related Commands

none

Attributes

Log: no

State: active, standby, init

Privilege: SERVICE_GP


Example

Force the card to recover its native configuration from the hard drive. (If the PXM were not in the failed state, the following error message would appear: "ERR: This command is applicable only in FAILED state.")

London21.7.PXM.a > forcecdnative
This command will cause the system to reset and bring up the shelf
with the configuration on the hard disk.
Please confirm now!

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

help

Help—PXM45, PXM1E

Use help to view commands associated with the current card. The help command is case-sensitive. Its behavior with or without parameters is:

With no parameter string, it lists all commands on the card.

With part of a command name, it lists all commands that contain that string.

With the entire command name, the output shows only whether the command is available.

Syntax

Help [string]

Related Commands

?

Attributes

Log: no

State: active, standby, init

Privilege: ANYUSER


history

History—PXM45, PXM1E

Use history to display the recent commands that have run on the current card. The default number of commands in the display is 10, but you can specify a much larger number of commands (see Syntax Description).

To repeat a previous command and its parameters, type an exclamation mark followed by the associated number and no spaces, then press Return.

Syntax

history [history]

Syntax Description

history

The number of the commands to display in the history output has a range of 0-256.


Related Commands

None

Attributes

Log no

State: active, standby, init

Privilege: ANYUSER


Example

Display the last 10 commands executed on the PXM. Repeat the previous execution of dspdate.

MGX8850.7.PXM.a > dspdate
    Sep 09 2000 16:37:37 GMT

MGX8850.7.PXM.a > history
Size of cmdHistory is currently 10 line(s)
  1 q
  2 help dsp
  3 help dspdate
  4 q
  5 help dspdate
  6 history
  7 6
  8 help dspdate
  9 dspdate
 10 history

MGX8850.7.PXM.a > !9
dspdate
    Sep 09 2000 16:38:06 GMT

insbiterror

Insert Bit Error—PXM1E

Inserts single bit errors into the transmitted BERT pattern.

Syntax

insbiterror -ln <bay.line>

Syntax Description

bay

Bay number: always 2

line

Line has a range of 1-12 and depends on whether the card is the combo card or the standard card.

For T3 or E3:

5-12 on the combo card

1-8 on standard card

For OC3c: 1-8


Related Commands

cnfbert, startbert, stopbert

Attributes

Log: yes

State: active

Privilege: GROUP1


ipifconfig

IP Interface Configuration—PXM45, PXM1E

The ipifconfig command lets you configure an IP address and other user-interface parameters to provide runtime IP connectivity for control of the switch. The name of the IP address for runtime user-control is the disk IP address. (When the PXM is either in boot mode or in the standby state, its IP address is called the boot IP address.) The interface type can be ATM, Ethernet, or SLIP. Typically, the Cisco WAN Manager application on a local or remote work station controls a switch through this interface.

(Note that ipifconfig and related commands have no bearing on the Console Port for an ASCII terminal that is co-located with the node. For details on the hardware connections and initial start-up through the console port, see the Cisco MGX 8850 (PXM1E/PXM45), Cisco MGX 8950, and Cisco MGX 8830 Software Configuration Guide, Release 4.)

The ipifconfig command lets you specify:

A type of interface—ATM, Ethernet, or SLIP

A disk IP address for the Ethernet interface

A broadcast address for Ethernet

Restriction of connections for IP connectivity to be either SVCs or PVCs

Support at the interface level for ARP

An interface type that serves as the default when the switch powers up

The operational state of the interface—up or down

Behavioral Characteristics

Note the following characteristics of IP connectivity in general and the disk IP address in particular:

The disk IP address is used during normal PXM operation and is configured through the ipifconfig command.

The boot IP address is utilized only when the PXM is booting up. Also, the standby PXM's effective IP address is the same as the boot IP address.

On the active PXM, the boot IP address is configured through the bootchange command.

At the boot mode prompt of a PXM, the boot IP address is configured through the sysBootChange command.

The disk IP configuration should match the boot IP configuration. The netmask (subnet) of the disk and boot IP configurations must be the same. However, the disk IP address can differ from the disk IP address but must be in the same subnet as the boot IP address.

Information is written to disk and is synchronized to the standby PXM.

During PXM switchover, the new active PXM changes its IP address to the disk IP address.

Usage Guidelines

Except for the first-time, mandatory configuration of an IP address for the interface, the ipifconfig parameters are optional details you can use to modify the interface. The parameters include default states that apply to a broad range of network designs. The purpose of these defaults is to minimize the need to change the optional parameters.

The IP interface configuration requires knowledge of the capabilities of the devices or interfaces that exist between the PXM and workstation. Particularly, any attached routers should be feature-rich. For example, the most likely configuration consists of:

Cisco 7000-family or Cisco 4500-series routers connected to an AXSM port. An MGX 8850 switch can communicate with a maximum of 42 routers. If one router does not, for example, support ATMARP, you must configure the interface not to use ATMARP when communicating with any router in the IP connectivity path.

An ATM router interface with LLC encapsulation and ATMARP protocol service, RIP protocol, and ILMI protocol.

A Sun workstation running Cisco WAN Manager with support for RIP and SNMP protocols.


Note The ipifconfig command on the PXM45 or PXM1E corresponds to cnfifip on the PXM1.


Syntax

ipifconfig <interface>  [ip_address] [netmask <mask>] [broadcast <broad_addr>]
[dest <peer_ip_address>] [up | down ] [arp | noarp] [svc | nosvc] [pvc | nopvc] [default | nodefault] [clrstats]

Syntax Description

interface

A name that identifies the type of interface. The type of interface affects the applicability of other ipifconfig parameters.

The choices for interface are:

lnPci0 for Ethernet (the default on power-up)

atm0 for the ATM

sl0 for SLIP

ip_address

(Optional if already configured, mandatory if not) ip_address is a 32-bit IP address in dotted decimal format. This parameter is mandatory when you first configure a particular interface type (lnPci0, and so on). If you subsequently modify one or more optional interface parameters, you can omit this IP address because the interface name (interface, above) is sufficient to get the address.

netmask

32-bit net mask in dotted decimal format. Ideally, the PXM and any routers associated with connected workstations exist in the same subnet. Specifically, having the same subnet mask simplifies router configuration.

broadcast

Broadcast address—applies to Ethernet only.

dest

The dest option lets you specify a destination IP address for a situation where a point to point connection is required and one or more endpoints do not support negotiation. Typically, this option applies to a SLIP interface.

up | down

This option specifies that the interface is either up or down. The default is up. Setting it to down turns off all IP packet communication. You should have a specific purpose for downing the interface.

arp | noarp

This option enables or disables ARP for all connections on the interface. Enter the keyword arp or noarp in its entirety. The default is enabled (arp). Note that disabling ARP for Ethernet is a very unlikely choice.

If you disable ARP, the system subsequently prevents you from specifying ARP for an individual SVC or PVC. If you need to disable ARP for a connection because a particular interface or device does not support ARP, disable it though svcifconfig or pvcifconfig.

svc | nosvc

This option specifies whether SVC support is enabled on the interface. The choice applies to all connections on the interface. The default is enabled (svc) and is the most common application. Specific contexts may provide a reason to disable SVCs on the interface.

pvc | nopvc

This option specifies whether PVC support is enabled. The default for this parameter is enabled (pvc). The application of PVC support is for a device in the network management path that provides IP connectivity but does not support SVCs. With PVC support enabled, you subsequently set up a PVC to that device by executing pvcifconfig. If PVC support is not enabled, pvcifconfig fails.

If you change this value, type the word pvc or nopvc in its entirety.

default | nodefault

This option specifies whether this interface is the default interface. As stated in the description of the interface parameter, the default interface is Ethernet the first time the switch powers up. You can change the default by entering the default or nodefault keyword. For example, if you currently are specifying an ATM interface (atm0) on the control port, you can make it the default (upon subsequent node reset) by typing the keyword default.

clrstats

This option clears all interface and connection statistics for the specified interface type. The statistics pertain to incoming and outgoing packets, errored packets, and so on.


Related Commands

bootchange, dspipif, pvcifconfig, dsppvcif, svcifconfig, dspsvcif, dspipifcache

Attributes

Log: no

State: active

Privilege: SUPER_GP


Example

Specify an IP interface of type ATM, address of 163.72.29.177, and a net mask of 255.255.255.000, and use the defaults for all other parameters.

wilco.7.PXM.a > ipifconfig atm0 163.72.29.177 mask 255.255.255.000

loadrev

Load Revision—PXM45, PXM1E

Use the loadrev command to download a firmware image from the FW directory on the disk to flash memory on the targeted card. Running loadrev is the first step in a graceful firmware upgrade. A graceful revision change preserves the configuration of the card and minimizes any data loss that could result from the brief disruption in service.

Syntax

loadrev <slot> <revision>

Syntax Description

slot

The number of the targeted card slot. You cannot use loadrev for the following slots:

In an MGX 8950 switch: 9, 10, 25, or 26

In an MGX 8850 switch: 15, 16, 31, or 32

In an MGX 8830 switch: 7, 14

revision

Revision number derived from the firmware file. See "Version Numbering Conventions."


Usage Guidelines

Although loadrev runs on a PXM, the target can be either a service module or the PXM45 itself. The system automatically determines which card in a redundant setup is active and which is standby. Specifying the active card slot is sufficient. For example, if a PXM is the target, you can specify either slot 7 or slot 8 regardless of the active slot number.

The sequence of commands for a graceful revision change appear in the following list. See Table 2-18 and Table 2-19 for a clarification of the various states within this sequence.

1. loadrev loads a firmware version from the hard disk to a card's memory. In a non-redundant card setup, loadrev does not cause the system to reset the card.

2. runrev causes the primary card to start running the new version. For a redundant pair of cards, the standby becomes the active card then starts running the new version.

3. If an unacceptable problem occurs, the optional abortrev command restores the previous version of firmware as well as the previous database contents.

4. commitrev declares the new primary version to be acceptable and removes the old primary from main memory (but not the hard disk).


Note You must terminate a current graceful upgrade by using commitrev or abortrev before starting another upgrade. For example, if you attempt to run loadrev on a card before using commitrev to complete an upgrade, the system blocks the attempt and returns an error message.


A graceful upgrade takes a single card or a redundant card pair through different stages. If you must execute abortrev on a redundant pair, the card (or possibly both cards in the case of a redundant pair) is reset. The stages of a graceful upgrade and the reset actions appear in Table 2-18 for a single-card upgrade and Table 2-19 for a redundant-pair upgrade.

The tables start by showing that, initially, the primary and secondary versions of firmware are 2.x, so the only possible operational version is 2.x. The loadrev command loads a generic version called 2.y, and the upgrade sequence progressively changes the primary and secondary firmware versions.

Table 2-18 Single-Card Upgrade From 2.x to 2.y 

Firmware Status
Initial Version
After loadrev
After runrev
After commitrev

Primary

2.x

2.x

2.y

2.y

Secondary

2.x

2.y

2.x

2.y

Operational

2.x

2.x

2.y

2.y

     

After runrev, the card resets.

 


Note Of special note in Table 2-19, runrev causes the standby card to become the active card. The reversed location of the "Active" and "Standby" columns shows the changed states.


Table 2-19 Redundant Pair Upgrade From 2.x to 2.y 

Firmware status
Before upgrade
After loadrev
After runrev
After commitrev
 
Active
Standby
Active
Standby
Standby
Active
Standby
Active

Primary

2.x

2.x

2.x

2.x

2.y

2.y

2.y

2.y

Secondary

2.x

2.x

2.y

2.y

2.x

2.x

2.y

2.y

Current

2.x

2.x

2.x

2.y

2.y

2.y

2.y

2.y

     

abortrev resets only standby card.

abortrev resets both cards.

   

After you execute runrev, the PXM updates the database records on disk if changes occur (such as changes to the configuration or network topology). If you revert to the previous version by executing abortrev, the post-runrev changes are lost. For example, if a switch was added to the network between runrev and abortrev, the restored database has no record of the topology change.

Version Numbering Conventions

This section describes how to interpret the version number of a firmware image. Commands such as loadrev and setrev require a version number rather than a filename. Similarly, dspversion shows the firmware version number rather than the firmware filename. Although the version number derives from the firmware filename, they are distinctly different.

Firmware Filenames

The FW directory on the hard drive contains firmware files of possibly many revisions. (Each firmware file has the fw file extension.) The format of a firmware filename is:

cardtype_version-element[_platform].fw

Note that platform is an optional field because it applies to only the PXM. For example, a firmware file may have the name "axsm_002.000.001.001.fw." Within this filename, the version-portion is 002.000.001.001. (Note the absence of "mgx.") This version-portion has the following format:

major-release.minor-release.maintenance.patch-phase

The range for major release numbers is 0-31. The range for all other release numbers—minor, maintenance, and patch—is 0-255. Note that, as you read left-to-right, each element is a superset of the element on the right, and the number on the right resets to 0 or 1 when the element on its left is incremented. For example, if the minor-release number 010 rolls to 011, the maintenance on its right is reset to 1, so the new version in the example is 002.011.001.000. (Note the anomaly here is that the maintenance number resets to 1 rather than 0 because of the IOS convention of starting maintenance numbers at 1.)

Version Numbers

To derive the firmware version number, the firmware filename is altered by removing insignificant zeroes and being reformatted to include parentheses. The format of a version number is:

major-release.minor-release(maintenance.patch)phase

For example, the significance of 2.1(60.8)P1 is shown below:

major-release

minor-release

(maintenance.patch)

phase

2.

1.

(6.8)

P1


The first two revision numbers in the following list represent released product. These two bullets show major release 2, minor release 1, and the maintenance number 70. The last three bullets show developmental revision numbers. Pre-release, developmental versions have alphanumeric characters at the end of the revision number. Having a pre-release version is not typical, but it may appear in various contexts. An easy way of seeing a pre-release number is the on-line help for either the loadrev or setrev command. The following are examples:

2.1(70) (note the absence of a patch number)

2.1(70.248) (note the patch number is 248)

2.1(70.248)P1, 2.1(0.1)P2, 2.1(0.113)P3, 2.1(0.10)P4


Note The possible phases are I, A, P1, P2, P3, P4, and D


Related Commands

abortrev, commitrev, runrev, setrev, dspversion, dspcd

Attributes

Log: yes

State: active

Privilege: SERVICE_GP


Example

Load version 2.1(70.4) to the AXSM in slot 5.

pinnacle.7.PXM.a > loadrev 5 2.1(70.4)

logout

Log Out—PXM45, PXM1E

Use logout to end the current user session.

Syntax

logout

Syntax Description

This command takes no parameters.

Related Commands

bye, exit

Attributes

Log: yes

State: active, standby, init

Privilege: ANYUSER


Example

Log out of the current CLI shell.

MGX8850.8.PXM.a > logout

(session ended)

ls

List—PXM45, PXM1E

Use ls to list the contents of the working directory. The filename is listed for each entry. The total space of the file system and free space is also summarized at the end of the output.

Syntax

ls [dir]

Syntax Description

You can specify an optional directory or path to list.

Related Commands

cd, pwd, rename, copy

Attributes

Log: no

State: active, standby, init

Privilege: ANYUSER


Examples

For the first example, list all the files at the highest level of the disk.

MGX8850.7.PXM.a > ls
SM
FW
DIAG
STATS
TMP
CNF
RPM
LOG
clrDB
upgrade.state
config.sys
DB

In the file system:
    total space: 819200 K bytes
    free space: 700583 K bytes

Change to the SCT directory. List all files in the SCT directory, then list the files in the AXSM directory.

MGX8850.7.PXM.a > cd /SCT

MGX8850.7.PXM.a > ls
.
..
AXSM

In the file system :
    total space :  819200 K bytes
    free  space :  660582 K bytes

MGX8850.7.PXM.a > ls AXSM
.
..
AXSM_SCT.CARD.2
AXSM_SCT.CARD.3
AXSM_SCT.PORT.2
AXSM_SCT.PORT.3

In the file system :
    total space :  819200 K bytes
    free  space :  660582 K bytes 
MGX8850.7.PXM.a >

optrte

Optimize Routes—PXM45, PXM1E

The optrte command lets you force immediate optimization of all SPVCs and SPVPs on a PNNI logical port. Optionally, you optimize a single connection or a range of connections. (Connection grooming is a common word for optimization.)

Re-routing depends on a reduction in the cost of the route. If the PXM can find a route with sufficiently lower cost, the connection is de-routed then re-routed. Route cost-reduction depends on the percent of cost reduction and an absolute grooming threshold. These grooming are configurable through the cnfrteoptthld command. For a detailed explanation of route optimization, see the cnfrteopt description.


Note Grooming a point-to-multipoint (P2MP) connection depends on branching concerns rather than routing costs. Therefore, the optrte, cnfrteopt, and cnfrteoptthld commands are not appropriate for P2MP connections. To re-route a P2MP connection, use rrtcon.



Note If a connection with a preferred route has been taken off its preferred route, it can regain its preferred route through grooming. Re-routing can occur by scheduled grooming or through forced optimization.


Syntax

optrte <portid> [-vpi <vpi>] [-vci <vci>] [-range <starting-vpi/vci..ending-vpi/vci>]

Syntax 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 narrowband service module (NBSM): slot.port.

For more details, see the section, "PNNI Format," in "Introduction."

-vpi

Keyword that specifies the vpi. The range is 0-4095.

-vci

Keyword that specifies the vci. The range is 1-65535.

-range

The range of connections for grooming. The VPI of the starting SPVC must be less than the ending VPI, and the starting VCI must be less than the ending VCI.

Use the notation as it appears on the syntax line: type a slash between the VPI and VCI and two dots with no spaces between the starting and ending values. For example, 100/1000..200/10000 is a valid entry. The ranges are as follows:

VPI: 0-4095

VCI: 1-65535

In the variable parameter starting-vpi/vci..ending-vpi/vci, the starting and ending VPIs are independent of the starting and ending VCIs. For example, -range 3/40..5/50 means the following:

Optimize all SPVCs that have a VPI in the range 3-5 and a VCI in the range 40-50.

This example range could include 3/40, 3/45, 4/45, 5/45 and 5/50 but not 4/60.

Note that the default for -range is all connections on the PNNI port specified by portid. Therefore, to groom all connections on the port, leave out the -range parameter.


Related Commands

cnfrteopt, cnfrteoptthld, dsprteoptcnf, dsprteoptstat

Attributes

Log: yes

State: active

Privilege: GROUP1


Example

Immediately find a better route for the SPVC with VPI.VCI 1000.50000 on port 1:2.1:1.

pop20two.7.PXM.a > optrte 1:2.1:1 -vpi 1000 -vci 50000

pathtraceie

Path Trace IE—PXM45, PXM1E

This command determines whether the PNNI trace feature removes or inserts the path trace information element (IE) at the port level. If the choice is remove, PNNI removes the path trace IE before the SETUP message goes to the next node. If the choice is insert, the IE continues in the SETUP message tot the next node.

In most cases, the default is insert. In contrast, for AINI/IISP links, PNNI automatically removes the IE. See also the descriptions of the pathtraceie and pathtraceport commands.

Syntax

pathtraceie <portid> {rmv | ins}

Syntax 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 narrowband service module (NBSM): slot.port.

For more details, see the section, "PNNI Format," in "Introduction."

rmv

Allow the deletion of the Trace Transit List IE at the port.

ins

Allow the insertion of the Trace Transit List IE at the port.


Related Commands

conntrace, pathtraceport, pathracenode, dsppathtraceie

Attributes

Log: yes

State: active

Privilege: SUPER_GP


pathtracenode

Path Trace Node—PXM45, PXM1E

Enables or disables the path trace feature at the node level. The default at the node-level is for path tracing to be enabled. (The default capability for path traces at the port level is disabled. Therefore, you need to enable path tracing on a per-port basis.)

Syntax

pathtracenode {enable | disable}

Syntax Description

enable or disable

Enter the word "enable" or "disable" for the path trace at the node level.

Default: enable


Related Commands

dsppathtracenode, pathtraceport

Attributes

Log: yes

State: active

Privilege: SUPER_GP


pathtraceport

Path Trace Port—PXM45, PXM1E

The pathtraceport command lets you enable (or disable) the path trace feature at the port level. Path tracing means that 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.

(Tracing a route for a call that has already been routed is a connection trace. See the conntrace description. However, if the connection fails to route, conntrace cannot show the route. You can use a path trace to find where the routing breaks down.)

With path tracing, you can observe routing behavior to improve load sharing or for isolating points of routing failure. Examples of events that trigger a path trace are as follows:

The first-time routing of a connection.

The activation of a port that had connections before it was de-activated. In this case, a very substantial amount of routing may occur, but you can specify the ATM addresses you want to trace (see the section, "Tracing All Calls or Specific AESAs").

The triggering of a re-route by using the rrtcon command.

You can use these triggers as often as necessary for researching the path that a call setup takes.

By default, path tracing is disabled at the port level but enabled at the node level. With path trace enabled, you can view either a trace for an individual connection or a list of all traces by using the dsppathtracebuffer or dsppathtracebuffers command, respectively. You can clear one or all trace buffers by using the clrpathtracebuffer or clrpathtracebuffers command.

Crankback Option

By enabling the crankback option, you can see in the trace buffer where the call was cranked back and therefore isolate the point of failure. If the crankback option is disabled, the system does not keep a record of the route if the call is cranked back.

Tracing All Calls or Specific AESAs

When you enable path tracing, the feature stores the routes for all calls on the port in the trace buffers. The capacity for this feature is ten trace buffers with 100 trace records in each buffer. When a buffer is full, the system deletes the oldest entry as it performs each new trace. For a port with many calls, the traces can fill up the buffers and be flushed before you check them. Therefore, this command has filter options to let you narrow the scope of the trace.

Two pairs of options let you create filters based on ATM addresses. You can specify up to five calling party ATM addresses and five called party ATM addresses on each list. With these options, the feature traces only the connections for these addresses when they go through a particular port. As soon as you add one address to either list, the feature stops the default of tracing all calls on the port. Thereafter, only the calls on the list are traced during call setup.

Typically, you would specify the option of one called AESA or one calling AESA per iteration of the command. You can specific both a called address and a calling address in one command iteration, but then the trace occurs only if both the called address and calling address match what you specified. Put another way: the calling and called AESAs are ANDed instead of ORed before the system traces the call.

Path Trace Limits

Note the following limits for path trace:

The limit for concurrent traces is five. If you a trigger many traces at once—by upping a port, for example—the feature can trace the routing of five different calls at once. With a sudden and extensive re-routing, only five to eight traces end up in the buffer.

The buffer holds a maximum of 100 trace results. If you were to re-route one connection at a time by using the rrtcon command, the buffer eventually would reach its limit of 100 trace records.

The lists of specific addresses hold five calling AESAs and five called AESAs.

A maximum of 1000 calls per port can be traced.

The switch stores the port-level, path trace configuration on the disk of the active and standby PXM. Exceptions are the calling party and called party filters: only the standby PXM retains these values.

Syntax

pathtraceport <portid> {enable | disable} [-X {on | off}] [-CB {on | off}] [-V {on | off}]
[-CR {on | off}] [-cldnum called-AESA -cldopt {add | del}]
[-clgnum calling-AESA -clgopt {add | del}]

Syntax 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 narrowband service module (NBSM): slot.port.

For more details, see the section, "PNNI Format," in "Introduction."

enable or
disable

Enables or disables path trace on the port. If path tracing is enabled on a port and you specify that the switch disable it, the other parameters for this command are meaningless.

For SPVCs and SPVPs, enable path tracing at the master and slave UNIs.

Default: disabled

-X

Specifies the clear call option. If this option is specified, the call's route is traced, but the call is released after the trace—and therefore never routed as long as this option is on. This option has limited application. Type either "on" or "off."

Default: off

-CB

Specifies the crankback option as on or off. With the crankback option on, you can see in the trace buffer where the call was cranked back. Also, the failure cause for crankback is included in the TTL IE. Type either "on" or "off."

Note Cisco Systems recommends that you enable the crankback option when enabling path tracing. If the crankback option is off, PNNI completes the trace only if it successfully routes the connection.

Default: off

-V

Specifies the VPI/VCI option. If enabled, VPI/VCI values of the egress port are added in the TTL IE at every node.

Default: on

-CR

Specifies the call reference option. If enabled, call reference values of all egress ports are added in the TTL IE.

Default: on

-cldnum

Specifies a called party AESA. This address is either added to or deleted from the list of called party addresses on this port for tracing purposes. This option works in conjunction with -cldopt. The -cldopt option specifies whether to add or delete the address from the list. The port can retain up to five such addresses.

-cldopt

This option either adds or deletes the called party AESA you specified with the -cldnum option for the purpose of tracing calls.

-clgnum

Specifies a calling party AESA. This address is either added to or deleted from the list of calling party addresses on this port for tracing purposes. This option works in conjunction with -clgopt. The -clgopt option specifies whether to add or delete the address from the list. The port can retain up to five such addresses.

-clgopt

This option either adds or deletes the calling party AESA you specified with the -clgnum option for the purpose of tracing calls.


Related Commands

conntrace, pathracenode, pathraceie, dsppathtracebuffer, dsppathtracebuffers

Attributes

Log: yes

State: active

Privilege: SUPER_GP


Examples

Enable path tracing on port 5:1.1:1 with crankback also enabled, then display the path trace configuration for the same port.

r18pop157.7.PXM.a > pathtraceport 5:1.1:1 enable -CB on
 
r18pop157.7.PXM.a > dsppathtraceport 5:1.1:1
 
Port option    :on 
Clear          :off 
Crankback      :on 
VPI/VCI        :on 
Call Reference :on 
Calling address:none
Called address:none

Enable path trace on port 9:1.1:1 with crankback on and a called address filter of 4755500000000000000000000000000000000000.

p2spvc8.7.PXM.a > pathtraceport 9:1.1:1 enable -CB on  
-cldnum 4755500000000000000000000000000000000000 -cldopt add

The following example illustrates how the configuration would appear if you specified five calling party AESAs and five called party AESAs.

p2spvc8.7.PXM.a > dsppathtraceport 9:1.1:1

Port option    :on
Clear          :off
Crankback      :on
VPI/VCI        :on
Call Reference :on
Calling address(es):47aaa00000000000000000000000000000000000
                   :4799900000000000000000000000000000000000
                   :4788800000000000000000000000000000000000
                   :4777700000000000000000000000000000000000
                   :4766600000000000000000000000000000000000
Called address(es) :4755500000000000000000000000000000000000
                   :4744400000000000000000000000000000000000
                   :4733300000000000000000000000000000000000
                   :4722200000000000000000000000000000000000
                   :4711100000000000000000000000000000000000

ping

Ping—PXM45, PXM1E

Use ping to determine whether a host is operational. The command causes the switch to send an ICMP packet to a destination address.

Syntax

ping <IP_Addr> [<Num_Packets>]

Syntax Description

IP_Addr

IP address of the destination host in dotted decimal format.

Num_Packets

Number of packets, in the range 0-65535.

0 specifies an infinite number of packets

3 is the default


Related Commands

None

Attributes

Log: no

State: active, standby

Privilege: ANYUSER


Example

Ping IP address 172.29.23.148.

MGX8850.7.PXM.a > ping 172.29.23.148
PING 172.29.23.148: 56 data bytes
64 bytes from 172.29.23.148: icmp_seq=0. time=0. ms
64 bytes from 172.29.23.148: icmp_seq=1. time=0. ms
64 bytes from 172.29.23.148: icmp_seq=2. time=0. ms
----172.29.23.148 PING Statistics----
3 packets transmitted, 3 packets received, 0% packet loss
round-trip (ms) min/avg/max = 0/0/0

pvcifconfig

PVC Interface Configuration—PXM45, PXM1E

Modifies an existing PVC to support IP connectivity to a feeder such as a BPX switch or an MGX Release 1 switch.

Syntax

pvcifconfig <interface> <router | local> <pvc_address> [atmarp | noatmarp] [llcencap | vcmux]
[default | nodefault] [reset] [delete] [up] [clrstats]

Syntax Description

interface

An alphanumeric string that identifies the interface type. The choices are:

lnPci0 for Ethernet (the default on power-up)

atm0 for the ATM.

sl0 for SLIP

Enter the entire keyword.Where appropriate, each subsequent parameter description identifies characteristics that depend on the type of interface.

router | local

Specifies whether the AESA corresponds to a router or the local PXM45. Both router and local ends should be configured. Configure the local end first, then execute pvcifconfig to specify the router end.

You must enter the entirety of one of these keywords. The AESA is an NSAP address used by the router or the local PXM45.

pvc_address

The VPI and VCI of the PVC. The format is vpi.vci.

[atmarp | noatmarp]

(Optional) Enables or disables ATMARP on a PVC—if the connected router supports ATMARP. Furthermore, it applies to only the ATM End Station Address (AESA) configuration at the router's interface. (See ipifconfig description.)

llcencap | vcmux

Applies to the router link only. This parameter specifies encapsulation. The choice primarily depends on whether the router supports LLC Snap encapsulation (llcsnap). The alternative is VC-based multiplexing (vcmux).

default | nodefault

(Optional) Specifies whether this PVC is the default route on the interface.

reset

(Optional) Resets the PVC.

delete

(Optional) Delete the specified AESA configuration.

clrstats

(Optional) Clear all SVC statistics on this interface.

up

(Optional) Put the PVC in the UP state and try to bind the associated lcns.

default | nodefault

(Optional) Specifies whether this PVC is the default route on the interface.

clrstats

(Optional) Clear any statistics for this PVC (dropped packets, for example).


Related Commands

dsppvcif, ipifconfig, setipconndebug

Attributes

Log: no

State: active

Privilege: SUPER_GP


pwd

Present Working Directory—PXM45, PXM1E

Use pwd to identify the current working directory on the PXM.

Syntax

pwd

Syntax Description

This command takes no parameters.

Related Commands

cd, rmdir, rm, ls, copy

Attributes

Log: no

State: active, standby, init

Privilege: ANYUSER


Example

Identify the present working directory.

MGX8850.7.PXM.a > pwd
C:
MGX8850.7.PXM.a >

resetcd

Reset Card—PXM45, PXM1E

The resetcd command lets you reset one of the following:

A PXM

A service module

Only the failure history of a card


Note You cannot specify an SRM to this command. A reset of a PXM also resets any associated SRMs.


Using the resetcd command without defining a slot number results in an ungraceful (disruptive) upgrade. This is the fastest method to upgrade a card, but it disrupts service.

A graceful (non-disruptive) upgrade requires that the loadrev, runrev, and commitrev commands have already been executed and that the card is identified in the command string.

Syntax

resetcd [slot] [-f]

Syntax Description

slot

The optional slot parameter identifies a card to reset. If you do not specify a slot, the command targets the current PXM.

-f

Specifies that the command resets only the failure history of a card.


Related Commands

resetsys

Attributes

Log: no

State: active, init

Privilege: SUPER_GP


Example

Reset the current PXM45.

pinnacle.7.PXM.a > resetcd
The card in slot number 7, will be reset. Please confirm action
Do you want to proceed (Yes/No)? n
(command not executed) 

Reset the failure history of the card in slot 1.

8850_NY.7.PXM.a > resetcd 1 -f
Clearing (-F) Failed state on slot 1. Please confirm action
resetcd: Do you want to proceed (Yes/No)?

resetevtlogsem

Reset Event Log Semaphore—PXM45, PXM1E

This special troubleshooting command applies to a situation where the dsplog or dsplogs function hangs because it was previously interrupted by Ctrl-C.

Syntax

resetevtlogsem

Syntax Description

This command takes no parameters.

Related Commands

dsplog, dsplogs

Attributes

Log: yes

State: active, standby

Privilege: CISCO_GP


Example

Reset the event log.

PXM1E_SJ.7.PXM.a > resetevtlogsem

WARNING:
This command should be executed only if the dsplog/dsplogs
was previously interrupted by Ctrl-C. And now, dsplog hangs
*** Ensure that NO other user is executing dsplogs
*** or dsplog on this switch before proceeding.
*** Otherwise, this command may corrupt the log file.

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

resetsys

Reset System—PXM45, PXM1E

Reset the entire node.

Syntax

resetsys

Syntax Description

This command takes no parameters but displays a warning and prompts you to continue the execution.

Related Commands

resetcd

Attributes

Log: no

State: active, init

Privilege: SUPER_GP


Example

Reset the system.

pinnacle.7.PXM.a > resetsys
This command resets the entire shelf, a destructive command.
Please confirm now!
Do you want to proceed (Yes/No)? n
(command not executed)

restoreallcnf

Restore All Configurations—PXM45, PXM1E

Restores all configuration files saved to the CNF directory on the hard drive. The saved configuration is the result of a prior execution of the saveallcnf command. To see a list of existing configurations that have been zipped by saveallcnf, cd to the C drive and list the contents of the CNF directory.

Syntax

restoreallcnf -f filename [-v]

Syntax Description

-f

Specifies the filename of the zipped version of the configuration.

-v

(Optional) Specifies that a list of the restored configuration files goes to the default printer. The default is no printout.


Related Commands

saveallcnf, abortallsaves

Attributes

Log: no

State: active, init

Privilege: SERVICE_GP


Example

Restore the system configuration created on February 5, 2001. The system responds with a statement of what the command would do and prompts you to accept the action before it proceeds with command execution.

pinnacle.7.PXM.a > restoreallcnf -f pop20two_01_200102051156.zip
The current configuration will be replaced with the contents
of the specified file and the shelf will be rebooted.

restoreallcnf: Do you want to proceed (Yes/No)? n
(command not executed

routeShow

Route Show—PXM45, PXM1E

Show the current IP routing of the network layer of the operating system.

Syntax

routeShow

Related Commands

routestatShow

Attributes

Log: no

State: active, standby, init

Privilege: ANYUSER


Example

Display the current IP routing of the network layer of the operating system.

pinnacle.8.PXM.a > routeShow
 
ROUTE NET TABLE
destination      gateway          flags  Refcnt  Use           Interface
------------------------------------------------------------------------
0.0.0.0          172.29.23.149    1      1       21778         lnPci0
0.0.0.0          172.29.23.1      3      0       2755          lnPci0
172.1.1.0        172.1.1.149      1      0       0             atm0
172.29.23.0      172.29.23.149    1      2       5275          lnPci0
------------------------------------------------------------------------
 
ROUTE HOST TABLE
destination      gateway          flags  Refcnt  Use           Interface
------------------------------------------------------------------------
0.0.0.0          0.0.0.0          5      0       0             sl0
127.0.0.1        127.0.0.1        5      1       0             lo0
172.29.23.3      172.1.1.149      5      0       3555          atm0
172.29.23.5      172.1.1.149      5      0       3304          atm0
172.29.23.7      172.1.1.149      5      0       3335          atm0
171.71.29.18     172.1.1.149      5      0       3304          atm0
172.29.23.18     172.1.1.149      5      0       3304          atm0
172.29.23.28     172.1.1.149      5      0       6127          atm0
172.29.23.29     172.1.1.149      5      1       6065          atm0
171.71.29.32     172.1.1.149      5      0       5842          atm0
171.71.29.44     172.1.1.149      5      0       3304          atm0
172.29.23.53     172.1.1.149      5      0       3304          atm0
171.71.29.59     172.1.1.149      5      0       3304          atm0
171.71.28.126    172.1.1.149      5      0       3309          atm0
------------------------------------------------------------------------
 
pinnacle.8.PXM.a >

routestatShow

Show Routing Statistics—PXM45, PXM1E

Use the routestatShow command to view the current IP routing statistics for the network layer of the operating system.

Syntax

routestatShow

Related Commands

routeShow

Attributes

Log: no

State: active, standby, init

Privilege: ANYUSER


Example

Display the current IP routing statistics for the network layer of the operating system

pinnacle.8.PXM.a > routestatShow
 
routing:
        0 bad routing redirect
        0 dynamically created route
        0 new gateway due to redirects
        0 destination found unreachable
        11095 uses of a wildcard route
 
pinnacle.8.PXM.a >

rrtparty

Re-route Party—PXM45, PXM1E

The rrtparty command forces PNNI to search for a better route between the root and party on a point-to-multipoint (P2MP) connection.

Syntax

rrtparty portid vpi vci endpointRef

Syntax 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 narrowband service module (NBSM): slot.port.

For more details, see the section, "PNNI Format," in "Introduction."

vpi

The local VPI of the connection is in one of the following ranges:

UNI: 0-255

NNI: 0-4095

vci

The local VCI of the connection has a range of 35-65535.

endpointRef

The endpoint reference has a range of 1-32767


Related Commands

addcon, delparty, dnparty, upparty, addparty, dspparty, dspparties, dsppartiespercon, dspcon, dspcons, dsppnport, dsppnports, clrspvcnonpers

Attributes

Log: yes

State: active

Privilege: GROUP1


Example

rstrtimagrp

Restart IMA Group—PXM1E

The rstrtimagrp command restarts the IMA group at the near end, restarts all the internal IMA state machines, and causes the IMA group to attempt to re-establish the IMA protocol with far end.

The order of commands for downing and upping an IMA group is as follows:

1. dnimagrp

2. upimagrp

3. rstrtimagrp

Syntax

rstrtimagrp <group>

Syntax Description

group

The group identifier consists of a bay number as well as a group number in the format bay.group. The possible values are as follows:

bay: always 2 on the PXM1E

link: 1-16


Related Commands

dspimagrp, dspimalnk

Attributes

Log: yes

State: active

Privilege: GROUP1


Example

Restart IMA group 1.

MGX8850.7.PXM1E.a> rstrtimagrp 2.1

rrtcon

Re-route Connection—PXM1E

The rrtcon command lets you trigger the immediate re-routing of a connection.

If the connection is a point-to-multipoint connection, all parties on the connection also are re-routed. To re-route an individual party, use the rrtparty command.

Grooming a point-to-multipoint (P2MP) connection depends on branching concerns rather than routing costs. The optrte, cnfrteopt, and cnfrteoptthld commands are not appropriate for P2MP connections because these commands depend on routing costs. The rrtcon command merely triggers the re-route, then PNNI determines route improvements based on branching.


Note If a connection with a preferred route has been taken off its preferred route, it can regain its preferred route through grooming. Re-routing can occur by scheduled grooming or through forced re-routing.


Syntax

rrtcon <ifNum> <vpi> <vci>

Syntax Description

ifNum

The range for logical port number is 1-31.

vpi

The VPI of the connection. For UNI, the range is 0-255. For NNI, the range is 0-4095.

vci

The VCI of the connection.

For a VCC, the VCI range is 1-65535.

For a VPC, the VCI is always 0.


Related Commands

dspcons, dspcon, dspparty, dspparties, dsppartiespercon

Attributes

Log: yes

State: active

Privilege: GROUP1


runrev

Run Revision—PXM45, PXM1E

The runrev command causes a new firmware version to start running. The runrev command is the second of the required commands in a graceful upgrade. It runs on a PXM but can target either a service module or the PXM.

The order of commands in a graceful upgrade, including the option of aborting the upgrade, appears in the following list. For clarification of the states in a graceful upgrade, see Table 2-20 and Table 2-21.

1. The loadrev command loads a firmware version from the hard disk to a card's memory. In a non-redundant card setup, loadrev does not cause the system to reset the card.

2. The runrev command causes the primary card to start running the new version. For a redundant pair of cards, the standby becomes the active card then starts running the new version.

3. If an unacceptable problem occurs, the optional abortrev command restores the previous version of firmware as well as the previous database contents.

4. The commitrev command declares the new primary version to be acceptable and removes the old primary from main memory (but not the hard disk).

The tables start by showing that, initially, the primary and secondary versions of firmware are 2.x, so the only possible operational version is 2.x. The loadrev command loads a generic version called 2.y, and the upgrade sequence progressively changes the primary and secondary firmware versions.

Table 2-20 Single-Card Upgrade From 2.x to 2.y 

Firmware Status
Initial Version
After loadrev
After runrev
After commitrev

Primary

2.x

2.x

2.y

2.y

Secondary

2.x

2.y

2.x

2.y

Operational

2.x

2.x

2.y

2.y

     

After runrev, the card resets.

 


Note Of special note in Table 2-21, runrev causes the standby card to become the active card. The reversed location of the "Active" and "Standby" columns shows the changed states.


Table 2-21 Redundant Pair Upgrade From 2.x to 2.y 

Firmware status
Before upgrade
After loadrev
After runrev
After commitrev
 
Active
Standby
Active
Standby
Standby
Active
Standby
Active

Primary

2.x

2.x

2.x

2.x

2.y

2.y

2.y

2.y

Secondary

2.x

2.x

2.y

2.y

2.x

2.x

2.y

2.y

Current

2.x

2.x

2.x

2.y

2.y

2.y

2.y

2.y

     

abortrev resets only standby card.

abortrev resets both cards.

   

After you use the runrev command, the PXM updates the database records on disk if changes occur (such as changes to the configuration or network topology). If you revert to the previous version by running abortrev, the post-runrev changes are lost. For example, if a switch was added to the network between runrev and abortrev, the restored database has no record of the topology change.

Syntax

runrev <slot> <revision>

Syntax Description

slot

Number of the targeted card slot.You cannot use runrev for the following slots:

In an MGX 8950 switch: 9, 10, 25, or 26

In an MGX 8850 switch: 15, 16, 31, or 32

In an MGX 8830 switch: 7, 14

revision

The revision number comes from the name of the firmware file. If the standby card does not have the specified image, runrev has no effect, and the system displays an error message. For an explanation, see the section, "Version Numbering Conventions," in the loadrev description.


Related Commands

abortrev, commitrev, loadrev, setrev, dspcd, dspversion

Attributes

Log: yes

State: active

Privilege: SERVICE_GP


Example

Run version 2.1(0.4) in logical slot 7. A previous check of the cards (by using dspcds) and firmware images (by using dspcd) would show whether a redundant card and version 2.1(0.4) are present.

excel.8.PXM.a > runrev 7 2.1(0.4)

saveallcnf

Save All Configurations—PXM45, PXM1E

The saveallcnf command saves all configurations to a zipped file in the CNF directory on the hard drive. Use the saveallcnf configuration only if no connection provisioning is occurring.

This command takes significant time, so a warning message prompts you for confirmation before the system performs the task. Upon completion, the system displays the name of the saved configuration file. The system stores up to two zipped configuration files. If you want to save more than two configurations, use FTP to transfer the files to another device.

To restore the system configuration, use restoreallcnf. To abort a configuration save, use abortallsaves.


Note Saving the configuration does not save the image. The number of the image version that was running when the configuration was saved is in the file C:version. When the system is restored, C:version is also restored. Restoring the version file leads to the old image being loaded. The configuration is tied to the runtime image to prevent conflict of database records when the system is restored.


Syntax

saveallcnf

Related Commands

restoreallcnf, abortallsaves

Attributes

Log: yes

State: active, init

Privilege: SERVICE_GP


Example

Save the system configuration. Note that the system displays the name of the saved configuration file.

MGX8850.7.PXM.a > saveallcnf
The 'saveallcnf' command can be time-consuming. The shelf
must not provision new circuits while this command is running.

Do not run this command unless the shelf configuration is stable
or you risk corrupting the saved configuration file.


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.
saveallcnf: Do you want to proceed (Yes/No)? n
(command not executed)

setcugdefaddr

Set Closed User Group Default Address—PXM45, PXM1E

The port-level setcugdefaddr command lets you specify an ATM address prefix as the default address for CUG validation. See the addcug description for details on the CUG feature.

The default address has the following uses:

PNNI uses it for CUG validation at the source node when the user does not signal a calling address.

At the source and destination nodes, PNNI uses it to validate CUG for ILMI-discovered addresses that have not been re-added through the addaddr command and configured with CUG membership. (CUG addresses cannot be learned through ILMI, so addresses for CUG must be added manually.)

Syntax

setcugdefaddr <portid> <atm-address> <length> [-plan {e164 | nsap}]

Syntax 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 narrowband service module (NBSM): slot.port.

For more details, see the section, "PNNI Format," in "Introduction."

atm-address

The NSAP or E.164 address on the local UNI interface is 20 bytes.

length

Address length. The units of measure differ for each address plan. The -plan option lets you specify E.164 or NSAP.

For an NSAP address plan, the units of measure are bits. The range is 0-160. Using the maximum of a 20-byte ATM address:

20 bytes x 8 bits per byte = 160 bits

For an E.164 address plan, the value is the number of decimal digits. If the ATM address consists of 15 digits, the value for this parameter is also 15.

-plan

The plan is either NSAP or E.164 and is set when you add the ATM address by using the addaddr command. Type either e164 or nsap in its entirety.

Default: nsap


Related Commands

addcug, cnfcug, clrcugdefaddr, cnfaddrcug, cnfnodecug, delcug, dspaddrcug, dspcug, dspcugdefaddr, dspnodecug

Attributes

log: yes

State: active

Privilege: GROUP1


Example

At port 12:12.1:1, specify the following default address for CUGs:

ATM address: 47.0091.8100.0000.0001.4444.7777

Length: 104

Plan: NSAP

pswpop3-1.7.PXM.a > setcugdefaddr 12:12.1:1 47.0091.8100.0000.0001.4444.7777 104 nsap

setipconndebug

Set IP Connection Debug—PXM45, PXM1E

Specify a debug mode and whether to use a console for debugging IP connectivity. This command requires SUPER_GP privilege. After you set the debug level, a status message states the current level.

Syntax

setipconndebug [-console | -noconsole] [debuglevel]

Syntax Description

-console | -no console

Configure where to run setipconndebig: console (ASCII) terminal or elsewhere.

debuglevel

Specifies a debug level. To select one or all of the following levels, enter the associated hexadecimal number and include the leading "0x" (see example):

No Logging (0x0)

Task Errors (0x1)

Task Debug (0x2)

ATM Protocol (0x4)

Task Startup (0x8)

Task Events (0x10)

SVC Call Events (0x20)

ATMARP Protocol (0x40)

Task Timers (0x80)

Interface Cache (0x100)

Subtask Events (0x200)

DISKDB Events (0x400)

RAMDB Events (0x800)

TRAP Events (0x1000)

All Logging (0xffffffff)


Attributes

Log: no

State: active, standby, init

Privilege: SERVICE_GP


Example

Set IP connection debug to console and specify a debug level of 20 for SVC call events.

node19.8.PXM.a > setipconndebug -console 20

setrev

Set Revision—PXM45, PXM1E

Force-load and run a firmware version for a card. You must execute setrev from the CLI of the active PXM whether the target is a service module or the PXM.


Note For the first-time power-up of the node, you should execute the burnboot command to burn in the bootcode. For details, refer to the Cisco MGX 8850 and MGX 8950 Switch Software Configuration Guide, Release 4.



Note The setrev command resets the active PXM only if the revision changes on the active card are a result of the setrev command.


Syntax

setrev <slot> <version>


Note With the current release, the primary and secondary images are the same. For this reason, you do not specify the secondary revision, so the syntax line indicates only "version."


Syntax Description

slot

Number of the targeted card slot.

You cannot use the setrev command for the following slots:

In an MGX 8950 switch: 9, 10, 25, or 26.

In an MGX 8850 switch: 15, 16, 31, or 32.

In an MGX 8830 switch: 7, 14

version

An alphanumeric string derived from the name of the firmware file. For an explanation of the numbering scheme, see the section, "Version Numbering Conventions," earlier in the setrev description. Note that primary and secondary firmware images have the same version for the current release.


Usage Guidelines

From a high-level perspective, the setrev command has two effects. It causes the PXM to load a firmware image from the hard drive to a card, then it causes the receiving card to run that image. The impact is a forced revision change. (A graceful revision path is available through the sequence of loadrev, runrev, and commitrev. A revision is an upgrade if the new firmware version has a higher numerical value or a downgrade if the new version has a lower value.)

At the time you initially bring up a node or after executing clrallcnf, the service modules have no runtime firmware image, so you must execute setrev for each service module in the switch. For the PXM, Cisco ships the product with firmware installed, so executing setrev is not necessary until you need to change firmware version or after you execute clrallcnf.

Version Numbering Conventions

This section describes how to interpret the version number of a firmware image. Commands such as loadrev and setrev require a version number rather than a filename. Similarly, dspversion shows the firmware version number rather than the firmware filename. Although the version number derives from the firmware filename, they are distinctly different.

Firmware Filenames

The FW directory on the hard drive contains firmware files of possibly many revisions. (Each firmware file has the fw file extension.) The format of a firmware filename is:

cardtype_version-element[_platform].fw

Note that platform is an optional field because it applies to only the PXM. For example, a firmware file may have the name "axsm_002.000.001.001.fw." Within this filename, the version-portion is 002.000.001.001. (Note the absence of "mgx.") This version-portion has the following format:

major-release.minor-release.maintenance.patch

The range for each release, maintenance, and patch is 0-255. Note that, as you read left-to-right, each element is a superset of the element on the right, and the number on the right resets to 0 or 1 when the element on its left is incremented. For example, if the minor-release number 010 rolls to 011, the maintenance on its right is reset to 1, so the new version in the example is 002.011.001.000. (Note the anomaly here is that the maintenance number resets to 1 rather than 0 because of the IOS convention of starting maintenance numbers at 1.)

Version Numbers

To derive the firmware version number, the firmware filename is altered by removing insignificant zeroes and being reformatted to include parentheses. The format of a version number is:

major-release.minor-release(maintenance.patch)

Using the example of axsm_002.001.001.001.fw, the version is 2.1(1.1). Similarly, if no patch were present, the version number would be 2.1(1).

Pre-release, developmental versions have one or two alphanumeric characters at the end of the version number, and these versions may appear in various contexts. For example, the help display for setrev gives examples of revision, but only the first two in the following list could be in released product. These two bullets show major release 2, minor release 1, and the minimal maintenance number of 1 (per the IOS precedent). The last three bullets show developmental revision numbers:

2.1(1) (note the absence of a patch number)

2.1(1.248) (note the patch number is 248)

2.1(0.248)P1, 2.1(0.1)P2, 2.1(0.113)P3, 2.1(0.10)P4


Note The possible phases are I, A, P1, P2, P3, P4, and D


Related Commands

loadrev, runrev, commitrev, abortrev, dspversion, dspcd

Attributes

Log: yes

State: active

Privilege: SERICE_GP


Example

Specify version 2.0(2) for the card in slot 9. In addition to setrev, this example shows other commands you could use before and after setrev. The sequence begins with a display of all the cards. While the firmware is going into the RAM on the card, periodically execute dspcds on the PXM to see the changing status of the target card. After setrev finishes, run dspcd on the targeted service module to see the version and other details of the card or dspversion to see just the version.


Step 1 On the PXM, use dspcds. The display shows slot 9 has a card with no firmware.

pinnacle.7.PXM.a > dspcds
pxm45tl                          System Rev: 00.00   Jan. 05, 2000 15:18:40 GMT
Boot F/W Rev: 0.0(0)             H/W Rev:    00.00   GMT Offset 0
Backplane Serial No: _UNKNOWN___ Backplane HW Rev: 00.00 
Statistics Master IP Address: 0.0.0.0                   Shelf Alarm: NONE
Card  Front/Back       Card           Alarm      Redundant  Redundancy     
Slot  Card State       Type           Status     Slot       Type   
---   ----------       --------       --------   -------    -----  

01    Empty            ---            ---        ---         ---    
02    Empty            ---            ---        ---         ---    
03    Empty            ---            ---        ---         ---    
04    Empty            ---            ---        ---         ---    
05    Empty            ---            ---        ---         ---    
06    Empty            ---            ---        ---         ---    
07    Active/Empty    UNKNOWN_FC      NONE       08         PRIMARY SLOT
08    Empty Resvd/Emp UNKNOWN_FC      MAJOR      07         SECONDARY SLOT
09    Failed/Empty    UNKNOWN_FC      NONE       NA         NO REDUNDANCY
10    Empty            ---            ---        ---         ---    
11    Empty            ---            ---        ---         ---    
12    Empty            ---            ---        ---         ---    
13    Empty            ---            ---        ---         ---    
14    Empty            ---            ---        ---         --- 

Step 2 Change directories to the "FW" (firmware) directory.

pinnacle.7.PXM.a > cd /FW

Step 3 List the contents of the directory:

pinnacle.7.PXM.a > ls

The display shows the names of the firmware files. Extract the AXSM version number—2.0(2):

pxm45_002.000.001-D.fw
pxm45_002.000.014-A1_bt.fw
axsm_002.000.002.fw

Step 4 Type setrev and specify version 2.0(2) as the primary firmware version for slot 9.


Note For the current release only, you do not need to enter the secondary revision number because the primary and secondary are the same.


pinnacle.7.PXM.a > setrev 9 2.0(2)

Step 5 Check the progress by executing dspcds. The following display shows that the PXM has detected the card type in slot 9. The status is "init"—initialization in progress:

pxm45tl                          System Rev: 00.00   Jan. 05, 2000 15:21:01 GMT
Boot F/W Rev: 0.0(0)             H/W Rev:    00.00   GMT Offset  0
Backplane Serial No: _UNKNOWN___ Backplane HW Rev: 00.00 
Statistics Master IP Address: 0.0.0.0                   Shelf Alarm: NONE
Card  Front/Back       Card           Alarm      Redundant  Redundancy     
Slot  Card State       Type           Status     Slot       Type   
---   ----------       --------       --------   -------    -----  

01    Empty            ---            ---        ---         ---    
02    Empty            ---            ---        ---         ---    
03    Empty            ---            ---        ---         ---    
04    Empty            ---            ---        ---         ---    
05    Empty            ---            ---        ---         ---    
06    Empty            ---            ---        ---         ---    
07    Active/Empty    UNKNOWN_FC      NONE       08         PRIMARY SLOT
08    Empty Resvd/Emp UNKNOWN_FC      MAJOR      07         SECONDARY SLOT
09    Init/Empty      AXSM_16OC3      NONE       NA         NO REDUNDANCY
10    Empty            ---            ---        ---         ---    
11    Empty            ---            ---        ---         ---    
12    Empty            ---            ---        ---         ---    
13    Empty            ---            ---        ---         ---    
14    Empty            ---            ---        ---         ---    

Step 6 The next use of dspcds indicates the card is active. Therefore, the firmware is running.

pxm45tl                          System Rev: 00.00   Jan. 05, 2000 15:21:11 GMT
Boot F/W Rev: 0.0(0)             H/W Rev:    00.00   GMT Offset  0
Backplane Serial No: _UNKNOWN___ Backplane HW Rev: 00.00 
Statistics Master IP Address: 0.0.0.0                   Shelf Alarm: NONE
Card  Front/Back       Card           Alarm      Redundant  Redundancy     
Slot  Card State       Type           Status     Slot       Type   
---   ----------       --------       --------   -------    -----  

01    Empty            ---            ---        ---         ---    
02    Empty            ---            ---        ---         ---    
03    Empty            ---            ---        ---         ---    
04    Empty            ---            ---        ---         ---    
05    Empty            ---            ---        ---         ---    
06    Empty            ---            ---        ---         ---    
07    Active/Empty    UNKNOWN_FC      NONE       08         PRIMARY SLOT
08    Empty Resvd/Emp UNKNOWN_FC      MAJOR      07         SECONDARY SLOT
09    Active/Active   AXSM_16OC3      NONE       NA         NO REDUNDANCY
10    Empty            ---            ---        ---         ---    
11    Empty            ---            ---        ---         ---    
12    Empty            ---            ---        ---         ---    

Step 7 Run dspversion to see the version of the runtime image.

pinnacle.7.PXM.a > dspversion
 
  Image Type   Shelf Type    Card Type         Version   Built On 
  ----------   ----------   ----------    ------------   ------------ 
     Runtime          MGX         AXSM         2.0(2)   Jan 03 2000, 16:36:39 
        Boot          MGX         AXSM      2.0(128)A1   - 


smclrscrn

Service Module Clear Screen—PXM45, PXM1E

The smclrscrn command lets you enable or disable at the node level certain clear-screen commands for narrowband service modules (NBSMs). The two commands on the NBSMs are clear and cls. If these commands are not enabled by the smclrscrn command on the PXM, they do nothing. The applicable NBSMs are AUSM, FRSM, and CESM, and so on.

To see the current enable state, enter smclrscrn with no parameters.


Note On the NBSMs, the clrscrn command works independently of the smclrscrn state.


Syntax

smclrscrn [enable | disable]

Syntax Description

enable

disable

Type enable or disable to enable or disable the cls and clear commands on the NBSMs.

Default: disabled


Related Commands

clrscrn, cls, clear (on the NBSMs)

Attributes

Log: yes

State: active

Privilege: GROUP1


stackdump

Stack Dump—PXM45, PXM1E

The stackdump command writes stack data to an error file. You can view the file by using dsplog.

Syntax

stackdump

Syntax Description

This command takes no parameters.

Related Commands

dsplog

Attributes

Log: no

State: active, standby

Privilege: SERVICE_GP


Example

Run the stackdump command then view the resulting log file by using the dsplog command.

M8850_NY.7.PXM.a > stackdump
The trace is saved in file error01.log

M8850_NY.7.PXM.a > dsplog -log error01.log
07A09583 08/25/2001-11:56:31  SSI-4-STKCHK         
         tChunkMon  ssiCheckAllTaskStack
 Stack usage exceeds threshold (70 percent): Task=pnCliTask (0x82ea2060), 
Size=8176, Usage=7032
05A03052 08/25/2001-11:45:40 STAT-4-ERROR          
 E:01588 StatFileMg sfm_fileCreateMsgH
 Func-sfm_fileCreateMsgH, Line-911, Errno-0x20643: sfm_sumEpidResolveDBSync 
returned error
05A03051 08/25/2001-11:45:40 STAT-5-WARNING        
         StatFileMg sfm_sumEpidResolveDBSyn
 Func-sfm_sumEpidResolveDBSync, Line-768, Errno-0x20643: ipcSend failed to send 
listResMsg, 1508-times failed so far
06A01484 08/25/2001-11:45:20 STAT-4-ERROR          
 E:00777 StatFileMg sfm_fileCreateMsgH
 Func-sfm_fileCreateMsgH, Line-911, Errno-0x20643: sfm_sumEpidResolveDBSync 
returned error
06A01483 08/25/2001-11:45:20 STAT-5-WARNING        
         StatFileMg sfm_sumEpidResolveDBSyn
 Func-sfm_sumEpidResolveDBSync, Line-768, Errno-0x20643: ipcSend failed to send 
listResMsg, 734-times failed so far
01A01963 08/25/2001-11:45:20 STAT-4-ERROR          
 E:01707 StatFileMg sfm_fileCreateMsgH

startimalnktst

Start IMA Link Test—PXM1E

The startimalnktst command starts an IMA link connectivity test on an IMA link. This test can confirm that an IMA link connection is valid by sending a test pattern to the link. The test pattern is a number in the range 0-254. A 0 causes the system to select a number for the pattern. If the transmitted number is the same as the number that arrives at the receiving end of the link, the link is valid. If the test pattern is different or does not arrive at all, the link is invalid.

The order of commands for configuring and using an IMA link is as follows:

1. cnfimalnktst

2. startimalnktst

3. stopimalnktst

Syntax

startimalnktst <group> <link> -pat <testPat>

Syntax Description

group

The group identifier consists of a bay number as well as a group number in the format bay.group. The possible values are as follows:

bay: always 2 on the PXM1E

group: 1-16

link

The link identifier consists of a bay number as well as a link number in the format bay.link, as follows:

bay: always 2 on the PXM1E

link: 1-16

-pat

The testPat is a number in the range 0-254. A 0 causes the system to select a number for the test pattern.

Default: 0


Related Commands

stopimalnktst, cnfimalnktst

Attributes

Log: yes

State: active

Privilege: GROUP1


Example

Start an IMA link test with the following values:

Group 1.

Link 1.

Test pattern is the number 77.

For group 1 and link 1, specify a test pattern of 77.

MGX8850.7.PXM1E.a> startimalnktst 2.1 2.1 -pat 77

startuplinkbert

Start Uplink Bit Error Rate Testing—PXM1E

The startuplinkbert command starts BERT on one of the lines on the PXM1E UNI/NNI back card. Before you start the test, it must have been configured through the cnfuplinkbert command. To stop the test, use the stopuplinkbert command. To display BERT-related information, use the dspuplinkbert or dspuplinkbertstats command.

Syntax

startuplinkbert <bay.line>

Syntax Description

bay.line

The required parameter identifies the bay and line for the test. The possible values are as follows:

bay: always 2 on the PXM1E

line: 1-16


Related Commands

cnfuplinkbert, dspuplinkbert, dspuplinkbertstats, stopuplinkbert

Attributes

Log: yes

State: active

Privilege: GROUP1


stopimalnktst

Stop IMA Link Test—PXM1E

This command stops the IMA link test that you started by using the startimalnktst command.

Syntax

stopimalnktst group

Syntax Description

group

The group identifier consists of a bay number as well as a group number in the format bay.group. The possible values are as follows:

bay: always 2 on the PXM1E

link: 1-16


Related Commands

startimalnktst, cnfimalnktst

Attributes

Log: yes

State: active

Privilege: GROUP1


Example

Stop the IMA link test for group 1.

MGX8850.7.PXM1E.a> stopimalnktst 2.1

stopuplinkbert

Stop Uplink Bit Error Rate Testing—PXM1E

The stopuplinkbert command stops the BERT that is running on one of the lines on the PXM1E UNI/NNI back card.

Syntax

stopuplinkbert <bay.line>

Syntax Description

bay.line

The required parameter identifies the bay and line that is under test. The possible values are as follows:

bay: always 2 on the PXM1E

line: 1-16


Related Commands

cnfuplinkbert, dspuplinkbert, dspuplinkbertstats, startuplinkbert

Attributes

Log: yes

State: active

Privilege: GROUP1


svcifconfig

SVC Interface Configure—PXM45, PXM1E

Configure IP-related parameters for the SVCs that support network control at a workstation.The configuration applies to all the SVCs on one of the three physical port types. Note that a complete configuration requires you to use svcifconfig twice. The first instance identifies the ATM end-station address (AESA) and encapsulation type at the router end. The second instance identifies the AESA—but no encapsulation type—for the switch.

Syntax

svcifconfig <interface> <router | local> <svc_address> [atmarp | noatmarp] [llcencap | vcmux] [default | nodefault] [reset] [delete] [force] [clrstats]

Syntax Description

Enter all keywords in their entirety.

interface

Alphanumeric string identify the interface type for the current SVC configuration. The choices are:

lnPci0 for Ethernet (the default on power-up)

atm0 for the ATM.

sl0 for SLIP

Enter the entire keyword.Where appropriate, each subsequent parameter description identifies characteristics that depend on the type of interface.

router | local

Specifies whether the AESA corresponds to a router or the local PXM. Both router and local ends should be configured. Configure the local end first, then execute svcifconfig to specify the router end.

You must enter the entirety of one of these keywords. The AESA is an NSAP address used by the router or the local PXM.

svc_address

The NSAP portion of SVCs that the node sets up on the specified interface type.

atmarp | noatmarp

(Optional) This parameter is valid for router AESA configuration only. Enables or disables ATMARP. For ATMARP to be available, the interface must support ARP (see ipifconfig description).

llcencap | vcmux

Applies to the router link only. This parameter specifies encapsulation. The choice primarily depends on whether the router supports LLC Snap encapsulation (llcsnap). The alternative is VC-based multiplexing (vcmux).

default | nodefault

(Optional) Specifies whether this SVC is the default route on the interface.

reset

(Optional) Reset of the SVC. The SVC is freed, then the call is attempted again.

delete

(Optional) Delete the specified AESA configuration.

force

(Optional) Force the SVC to be reset or deleted.
Use the force option with reset or delete if reset or delete appears to be hung.

clrstats

(Optional) Clear all SVC statistics on this interface.


Related Commands

ipifconfig, dspipif, dspsvcif, dspipifcache

Attributes

Log: no

State: active

Privilege: SUPER_GP


Example

First configure the AESA for the local (PXM) side, then configure the AESA for the router. This case uses the defaults for encapsulation (llcencap) and ARP (enabled).

sfo.7.PXM.a > svcifconfig arm0 local 47.0091.8100.0000.1010.1010.1010.1010.1010.1010.10

sfo.7.PXM.a > svcifconfig arm0 router 47.0091.8100.0000.0101.0101.0101.0101.0101.0101.01

switchapsln

Switch APS Line—PXM45, PXM1E

The switchapsln command switches traffic from the working line to the protection line. See the addapsln description for details on Automatic Protection Switching (APS) on the current product. When entered on a PXM, this command applies to the following hardware:

On a PXM45, this command applies to the SRME in an MGX 8850 chassis (the MGX 8950 switch does not support SRME).

On a PXM1E, the command applies to one of the following:

An SRME pair with inter-card APS

A pair of lines with intra-card or inter-card APS on the PXM1E UNI/NNI back card (or cards).

Syntax

switchapsln <slot> <bay> <line> <switchOption> [serviceSwitch]

Syntax Description

slot

The slot number depends on the chassis as well as the type of card, as follows:

For PXM45 in an MGX 8850 chassis, slot is 15 or 31.

For PXM1E in an MGX 8850 chassis:

For the UNI/NNI back card, slot is 7.

For the SRME, slot is 15 or 31.

For PXM1E in an MGX 8830 chassis:

For the UNI/NNI back card, slot is 1.

For the SRME, slot is 7.

bay

The bay number is present only for consistency with legacy purposes (the slot number uniquely identifies the location of the card) The bay is a fixed logical number that depends on the card, as follows:

For SRME, bay always is 1.

For the PXM1E interface, bay always is 2.

line

On the PXM1E OC3c/STM1 back card, the line depends on the back card type, as follows:

9-12 on the combo card

1-4 on the regular, 4-line card

1-8 on the regular, 8-line card

On an SRME, the line number always is 1.

switchOption

The method of performing the switch.

1 = clear (return to working line)

2 = lockout of protection (the system locks out the specified APS pair from being switched to protection line)

3 = forced working --> protection (the system forces a working line to protection line switch unless the protection line is locked out)

4 = forced protection --> working (the system forces a protection line to working line switch; 1+1 architecture mode only)

5 = manual working --> protection (manual switch)

6 = manual protection --> working (manual switch; 1+1 architecture mode only)

service switch

When set to 1, this field causes all APS lines to switch to their protected lines.

Default: 0


Related Commands

addapsln, cnfapsln, delapsln, dspapsln, dspapslns, dspapsbkplane, clrbecnt, dspbecnt

Attributes

Log: yes

State: active

Privilege: GROUP1


Example

On line number 8 of the active PXM1E, force a switch to the protection line.

Goa.2.PXM.a > switchapsln 7 1 8 3
Forced line switch from working to protection succeeded on line 7.2.8

Goa.2.PXM.a >

switchcc

Switch Core Cards—PXM45, PXM1E

The switchcc command lets you activate a standby controller card and make the active card in the redundant pair go to standby. (To switch the state of redundant service modules, use the switchredcd command.) If a standby PXM is not available, the switchcc command fails.

You cannot run switchcc during a configuration-copy. If you attempt it, the system blocks the operation. Also, the operation fails if the switch is unstable or if the standby PXM is not in the standby state (for example, if the card is in the init state).


Note If more than one node level exists in a multiple peer group (MPG) network, a significant addition to bringup time can occur when the controller cards switch over. For example, upon switchover to the standby on a peer group leader (PGL) node in a switch with three levels, five minutes may be required for the standby PXM to come up for the PGL and for the SVC-based RCC to be set up. This delay is typical because PNNI does not support hot redundancy, so the entire PNNI database has to be re-built. The process resembles a reboot for PNNI even though the active calls are not affected. While the standby PXM is coming up, the PNNI display commands may show discrepancies between the active and standby card information.


Syntax

switchcc

Related Commands

switchredcd, dspred

Attributes

Log: no

State: active

Privilege: SERVICE_GP


Example

Attempt a switchcc without a standby PXM in the backplane.

raviraj.7.PXM.a > switchcc
Do you want to proceed (Yes/No)? y

 Core card redundancy unavailable 

raviraj.7.PXM.a >

switchredcd

Switch Redundant Card—PXM45, PXM1E

The switchredcd command lets you activate a standby service module and make the active card in the redundant pair go to standby. (To switch the state of redundant PXMs, use the switchcc command.)

Syntax

switchredcd <fromSlot> <toSlot>

Syntax Description

fromSlot

The active card in the redundant pair.

toSlot

The standby card in the redundant pair—which you are switching to active.


Related Command

dspred, delred, switchcc

Attributes

Log: no

State: active

Privilege: SERVICE_GP


Example

mgx8850a.7.PXM.a > switchredcd 8 7 

telnet

Telnet—PXM45, PXM1E

The telnet command lets you directly telnet to another switch from the current CLI session. Therefore, you do not have to exit the current CLI session and start a new telnet session to reach another switch. The limit of nodes to which you can telnet is one. This command requires 2.1 or higher software.

To return to the CLI from which you telnetted—to break the connection and end the telnet session—enter the exit or bye command.

Syntax

telnet [-E <escape character>] [-R <traceroute character>] <ip addr> [[0x|X|x] <tcp port>]

Syntax Description

-E

(Optional.) The escape character for terminating the next telnet session in the chain. The purpose of the escape sequence (Esc key then escape character) is to terminate the telnet attempt if the destination node is unable to accept the telnet session for reasons such as: the destination switch is down or unreachable; its in backup boot mode; or it detects that TCP communication is down. If you use the escape sequence, the session falls back to the first switch in the telnet chain. The default value for escape character is "Q."

-R

(Optional.) The character for triggering a printout of details for all successive hops in the telnet session. The default value for the traceroute character is "g."

ip addr

The IP address of the other switch.

tcp port

(Optional.) The destination tcp port. The default TCP port is identical to the destination telnet port. Most applications call for the default.

In addition, by default you can enter the number in decimal format, but you can also enter the optional TCP port address in hexadecimal format by preceding the TCP destination with any one of the strings "0x," "X," or "x."


Related Commands

exit, bye

Attributes

Log: no

State: active, standby, init

Privilege: ANYUSER


Example

First telnet to IP address 172.29.65.40, then try to telnet to a second switch.

jeffrey-u10\> telnet 172.29.65.40
telnet 172.29.65.40
Trying 172.29.65.40...
Connected to 172.29.65.40.
Escape character is '^]'.

Login: cisco
password: 

jeff.7.PXM.a > telnet 172.29.65.40
Trying 172.29.65.40...
Connected to 172.29.65.40.
Escape character is ^]
Login: cisco
password: 

jeff.7.PXM.a > telnet 172.29.65.49
Err: telnet node-to-node is limited to one hop

timeout

Timeout—PXM45, PXM1E

The timeout command lets you extend the amount of idle time in a user-session from the default of
10 minutes. If you do not specify a timeout period, the system displays the current timeout. At the end of the session, the system logs you out.


Note The timeout command is the same as the sesntimeout command.


Syntax

timeout [time_out]

Syntax Description

time_out

Number of idle seconds allowed for the session.

Range: 0-43200 seconds. Note that entering a 0 actually specifies the maximum of 43200 seconds (12 hours).


Related Commands

sesntimeout

Attributes

Log: no

State: active, standby, init

Privilege: ANYUSER


Examples

Display the current timeout.

pinnacle.7.PXM.a > timeout
The timeout period for this session is currently 600 second(s)
pinnacle.7.PXM.a > 

Set the session timeout threshold to 100 minutes (6000 seconds).

pinnacle.7.PXM.a > timeout 6000
The timeout period for this session is now set to 5000 second(s)
 pinnacle.7.PXM.a >

tstconseg

Test Connection Segment—PXM1E

Test the integrity of an SVC or SPVC. With tstconseg, a single collection of supervisory cells is sent in the egress direction between the card and service equipment (CPE). (See tstdelay for ingress direction.)

When the test successfully starts, the system displays a message stating that the test has begun and directs you to use either dspcon or dspchantests to see the results. The dspcon command shows detailed information about the connection and has a field for the results of this test. The dspchantests command display only the results of the test.


Note The dspcon fields for round trip delay—including the status of OAM loopback—always show the results of the latest test and are not changed until a new tstconseg or tstdelay operation occurs. Therefore, dspcon does not clear the value for RTD or the indication that an OAM loopback is present. Also, the only way to change these fields to null is to down the port (through dnport).


Syntax

tstconseg <ifNum> <vpi> <vci> [-num <iterations>]

Syntax Description

ifNum

The logical port number has a range of 1-31.

vpi

The VPI range for the SVC or SPVC is 1-255.

vci

The VCI range for the SVC is 1-65535.

-num

(Optional) Specifies the number of times a collection of supervisory cells should traverse the SVC for the current execution of tstconseg.


Related Commands

dspcon, tstdelay, dspchantests

Attributes

Log: yes

State: active

Privilege: GROUP1


Example

Test the integrity of 1 10 1000 in the egress direction.

node19.7.PXM1E.a > tstconseg 1 10 100
Test started; Use dspcon/dspchantests to see test results

tstdelay

Test Delay—PXM1E

Test the integrity of the connection in the ingress direction by sending a collection of supervisory cells to the remote end of the network and back. (See tstconseg for the egress direction.) The tstdelay command applies to only SPVCs. It does not apply to point-to-multipoint connections.

If the test successfully begins, the display states the fact and directs you to use the dspcon or dspchantests command to view the round trip time in microseconds. The dspcon display shows detailed information on the connection and has a field for the test results. The dspchantests display shows the results of only the round trip delay test.


Note The dspcon fields 1-31for round trip delay—including the status of OAM loopback—always show the results of the latest test and are not changed until a new execution of tstconseg or tstdelay. Therefore, re-executing dspcon does not clear the value for RTD or the indication that an OAM loopback is present. The only way to reset these fields to null is to down the port (through dnport).



Note The primary purpose of tstdelay is to test the integrity of the connection. The round trip time is not accurate enough for any use that requires an accurate measurement of delay.


Syntax

tstdelay <ifNum> <vpi> <vci> [-num <iterations>]

Syntax Description

ifNum

The logical port number has a range of 1-31.

vpi

Virtual path identifier. The range is 1-255.

vci

Virtual connection identifier. The possible VCIs are as follows:

For a VCC: 1-65535

For a VPC: 0

-num

(Optional) Specifies the number of times a collection of supervisory cells should traverse the SVC for the current execution of tstdelay.


Related Commands

dspcons, tstconseg, dspcon

Attributes

Log: yes

State: active

Privilege: GROUP1


Example

Get the round-trip delay for connection 1 10 100. This example contains four tasks to illustrate how to obtain a list of logical ports; obtain a connection number; start the test; and view the results. The commands are dspports, dspcons, tstdelay, and dspcon.


Step 1 Identify the logical ports on the card by executing dspports. For this example, the logical port (ifNum in the display) is 1.

node19.7.PXM1E.a > dspports
ifNum Line Admin Oper. Guaranteed Maximum     Port SCT Id     ifType  VPI
           State State Rate       Rate                               (VNNI only)
----- ---- ----- ----- ---------- --------- ----------------- ------ ----------
    1  2.1    Up    Up    1412831   1412831   6                   UNI    0

Step 2 Use dspcons to get the connection ID for tstdelay. The connection identifier appears in NSAP format. In this example, assume tstdelay occurs at the slave end of the SPVC. Take the significant digits from the Identifier (01.0010.00100) to get the logical port, VPI, and VCI for tstdelay. These values are 1, 10, and 100.

node19.7.PXM1E.a > dspcons
record    Identifier   Type   SrvcType   M/S    Upld    Alarm
------    ----------   ----   --------   ---    ----    -----
    0  01.0010.00100   VCC        ubr1   S    0000ebfb      none
    1  01.0011.00101   VCC        ubr1   M    0000ec27      none

Step 3 Run tstdelay for logical port 1, vpi 10, vci 100. The system response shows that the command started correctly and directs you to use dspcon or dspchantests to see the results.

node19.7.PXM1E.a > tstdelay 1 10 100
Test started; Use dspcon/dspchantests to see test results

Step 4 Run dspchantests to see the results as displayed by this command. The units of measure for the round trip delay is microseconds—30000 microseconds in this case.

node19.7.PXM1E.a > dspchantests 1 10 100
Connection Id    Test Type    Direction    Result     Round Trip Delay
=============    =========    =========    =======    ================
01.0010.00100:    OAM Lpbk     ingress     Success          30000

Step 5 Use dspcon to see the results as displayed by this command. The line with test results appears towards the end of the display and begins with Loopback Type. The Direction field shows ingress, indicating the tstdelay command produced these results. (If tstconseg had been the last test command, this field would say egress.) The RTD (round trip delay) field shows 30000 microseconds.

node19.7.PXM1E.a > dspcon 1 10 100
--------------------------------------------------------------------------
Local   :                NSAP  Address               port     vpi    vci
(S)       4700918100000000001A53C82D00000101180100  1.01.01     10     100
Remote  :                NSAP  Address               port     vpi    vci
(M)       4700918100000000001A53C82D00000101180100  1.01.01     11     101
--------------------------------------------------------------------------
Conn. Type    :     VCC                           Admn Status  : ADMN-UP
Service Type  :    ubr1                           Rtng Status  : -67372037
Controller    :       2
--------------------------------------------------------------------------
Local PCR     :      14                           Remote PCR   :      14
Local SCR     :       3                           Remote SCR   :       3
Local CDV     :      -1                           Remote CDV   :      -1
Local CTD     :      -1                           Remote CTD   :      -1
Local MBS     :       1                           Remote MBS   :       1
Local CDVT    :      -1                           Remote CDVT  :      -1
Admin weight  :      -1                           Frame discard:       N
--------------------------------------------------------------------------
OAM CC Config : DISABLED                          Statistics   : DISABLED
--------------------------------------------------------------------------
Loopback Type : OAM Lpbk | Dir: ingress | Status: Success | RTD:   30000 us
--------------------------------------------------------------------------

--------------------------------------------------------------------------
Port side Tx  :  normal                           Swth side Tx :  normal
Port side Rx  :  normal                           Swth side Rx :  normal
--------------------------------------------------------------------------
I-AIS/RDI   E-AIS/RDI   CONDITIONED    CCFAIL       IfFail      Mismatch
   NO           NO           NO           NO           NO          NO
-------------------------------------------------------------------------- 

tstpndelay

Test PNNI Port Delay—PXM45, PXM1E

Initiates loopback test for a connection. If you provide both a VPI and VCI, the segment endpoint is an F5 flow endpoint (for VCCs). If you provide only a VPI, the segment endpoint is a F4 flow endpoint (for VPCs). This command displays the round trip delay in microseconds.

Use cnfconsegep to specify the segment endpoint if one does not already exist.

Syntax

tstpndelay <portid> <vpi> [vci] [-direction {inbound | outbound}]

Syntax 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 narrowband service module (NBSM): slot.port.

For more details, see the section, "PNNI Format," in "Introduction."

vpi

VPI of the connection.

vci

VCI of the connection.

Default: 0

-direction

Specifies the direction of loopback.

inbound: endpoint towards the backplane

outbound: endpoint departing the port

Default: inbound


Related Commands

cnfconsegep

Attributes

Log: yes

State: active

Privilege: SUPER_GP


Example

After confirming that the endpoints are configured to be OAM segment endpoints, run tstpndelay on connection 0 2929 on port 9:1.1:11. Make the direction outbound.

cokemt20.8.PXM.a > tstpndelay 9:1.1:11 0 2929 -direction outbound
cokemt20.8.PXM.a > Response for the cli Command -- tstpndelay:In Progress
It is Primary OAM Endpoint vpi:0, vci:2929

Successful, Cell round trip delay time = 117 uSec

upcon

Up Connection—PXM1E

Activate a connection that was previously brought down by the dncon command. (The typical purpose of dncon is some form of operational modification or troubleshooting.)

Syntax

upcon <ifNum > <vpi> <vci>

Syntax Description

ifNum

The range for logical interface (or port) numbers is 1-31.

vpi

Virtual path identifier. The range is 0-255.

vci

Virtual connection identifier. The possible entries depend on whether the connection is a VCC or VPC, as follows:

VCC: 1-65535

VPC: 0


Related Commands

dncon

Attributes

Log: yes

State: active

Privilege: GROUP1


upilmi

Up Integrated Local Management Interface—PXM1E

Use upilmi to activate integrated local management interface (ILMI) for a particular resource partition on a logical port. Before using the upilmi command, you must:

1. Activate a line through the upln command and configure the line through cnfln

2. Create a logical port through the addport command

3. Add resource partitions through addrscprtn

After activating ILMI, you can configure it by using the cnfilmi command.

Syntax

upilmi <ifNum> <partId>

Syntax Description

ifNum

The range for logical interface (or port) numbers is 1-31.

partId

The range for partition identifier is 1-20.


Related Commands

cnfilmi, dspilmi

Attributes

Log: yes

State: active, standby

Privilege: GROUP1


Example

Determine whether ILMI is up on logical port 1, resource partition 1. If ILMI is down (or off), activate it by using the upilmi command. Note the second time you run the dspilmi command, the ILMI state now appears as "on."

M8850_NY.7.PXM1E.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   Off     0    16   Off          1          5          4 

M8850_NY.7.PXM1E.a > upilmi 1 1
Warning: connections (if any) on port could get rerouted.
Do you want to proceed (Yes/No) ? y

M8850_NY.7.PXM1E.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   Off          1          5          4

upimagrp

Up IMA Group—PXM1E

The upimagrp command administratively activates an IMA group and is necessary only after the group has been deactivated through the dnimagrp command.

The order of commands for downing and upping an IMA group is as follows:

1. dnimagrp

2. upimagrp

3. rstrtimagrp

Syntax

upimagrp <group>

Syntax Description

group

The group identifier consists of a bay number as well as a group number in the format bay.group. The possible values are as follows:

bay: always 2 on the PXM1E

link: 1-16


Related Commands

addimagrp, delimagrp, dspimagrp, dnimagrp

Attributes

Log: yes

State: active

Privilege: GROUP1


Example

Activate IMA group 1.

MGX8850.7.PXM1E.a> upimagrp 2.1

upln

Up Line—PXM45, PXM1E

On a PXM1E, the upln command activates a line on one of two different card types. The line can be on the PXM1E UNI/NNI back card or on a service resource module (SRME or SRM-3T3). An upln command also runs on the AXSMs in a switch with a PXM45. See the other upln description for details.

If the line is on the PXM1E back card, consider the resource partitioning issues for the lines. See the description of cnfcdsct for important information.

After you have activated the line, use the cnfln command to configure the line characteristics, such as the type of line (SONET, T3, or E3), line signaling, and so on.

Until you take certain configuration steps, the following is true for the SRMs and the PXM1E back card:

Neither of these card types is reserved (in the system database)

Neither of these card types is part of the PXM1E card set.

Note that the PXM1E can operate without SRMs and without a UNI/NNI back card. For the back card, you must up at least one line. For an SRM, you can either up a line or configure non-bulk mode redundancy by adding a link (see addlink description).

Syntax

upln <X>.<line>

Syntax Description

X

X identifies the card. For SRMs, X differs in an MGX 8850 and MGX 8830 chassis:

X = 2 identifies the UNI/NNI back card on the PXM1E

X = 15 or 31 identifies an SRM in an MGX 8850 chassis (includes redundant cards in 16 or 32)

X = 7 identifies an SRM in an MGX 8830 chassis (includes redundant card in slot 14)

line

The range for line numbers depends on the card type and is from 1 to the highest numbered line on the back card, as follows:

PXM1E back card: 1-16

SRM-3T3: 1-3

SRME: 1


Related Commands

dspln, dsplns, cnfln, dnln

Attributes

Log: yes

State: active

Privilege: GROUP1


upparty

Up Party—PXM45, PXM1E

This command lets you administratively up a party on a point-to-multipoint (P2MP) connection. The down state results from the use of the dnparty command. See the addparty description for details about parties on a P2MP.

Syntax

upparty portid vpi vci endpointRef

Syntax 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 narrowband service module (NBSM): slot.port.

For more details, see the section, "PNNI Format," in "Introduction."

vpi

The local VPI of the connection is in one of the following ranges:

UNI: 0-255

NNI: 0-4095

vci

The local VCI of the connection has a range of 35-65535.

endpointRef

The endpoint reference has a range of 1-32767


Related Commands

addcon, delparty, rrtparty, dnparty, addparty, dspparty, dspparties, dsppartiespercon, dspcon, dspcons, dsppnport, dsppnports, clrspvcnonpers

Attributes

Log: yes

State: active

Privilege: GROUP1


Example

uppnport

Up PNNI Port:—PXM45, PXM1E

The uppnport command lets you put a UNI or NNI port into service (administratively "up" the port). The circumstances in which you would use the uppnport command are as follows:

After you have downed the port for any reason by using the dnpnport command

After you have pre-configured a port by using the addpnport command (see taddpnport description)

Syntax

uppnport <portid>

Syntax 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 narrowband service module (NBSM): slot.port.

For more details, see the section, "PNNI Format," in "Introduction."


Related Commands

addpnport, delpnport, dnpnport, dsppnport, dsppnports

Attributes

Log: yes

State: active

Privilege: GROUP1


Example

Check for any downed ports by executing dsppnports. Use uppnport to up any ports that are down. The output of dsppnports shows that only one user port exists (not the 7.3x ports, the first two of which are the BITS clock ports).

8850_NY.8.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/50000 

Summary of total configured SPVC endpoints
Type   #SpvcR   #SpvpR   #SpvcD   #SpvpD   Total
p2p:   0         0         0         0         0      
p2mp:  0         0         0         0         0      
                         Total=0      

Summary of total active SVC/SPVC intermediate endpoints
Type   #Svcc    #Svpc     #SpvcR   #SpvpR   Total
p2p:   0         0         0         0         0      
p2mp:  0         0         0         0         0      
                         Total=0      

          EndPoint Grand Total =      0/100000 
Per-port status summary

PortId      LogicalId    IF status      Admin status  ILMI state        #Conns

7.35         17251107    up             up            Undefined         0       

7.36         17251108    up             up            Undefined         0       

7.37         17251109    up             up            Undefined         0       

7.38         17251110    up             up            Undefined         0       

3:1.1:1      16979969    down           down          Disable           0       

8850_NY.8.PXM.a > 

SanJose.7.PXM.a > uppnport 3:1.1:1

Check the administrative status of 3:1.1:1.

8850_NY.8.PXM.a > dsppnport 3:1.1:1

Port:               3:1.1:1           Logical ID:       16979969          
IF status:          up                Admin Status:     up                
UCSM:               enable            
Auto-config:        enable            Addrs-reg:        enable            
IF-side:            network           IF-type:          uni               
UniType:            private           Version:          uni3.1            
PassAlongCapab:     n/a               
Input filter:       0                 Output filter:    0                 
minSvccVpi:         0                 maxSvccVpi:       4095              
minSvccVci:         35                maxSvccVci:       65535             
minSvpcVpi:         1                 maxSvpcVpi:       4095 

upport

Up Port—PXM1E

The upport command returns a logical port to the up state ("ups" the port) so the port can again carry traffic. The upport command concludes possible re-configuration or troubleshooting steps. Before you use upport, you must have downed the port by using dnport. Throughout the sequence of downing and upping a port, the configuration for the port remains intact whether the logical port is a UNI or an NNI.

The routes for connections vary by interface type:

After you re-enable an NNI port through upport, you cannot return the re-routed connections to the upped port. The PXM routes connections over the trunk as needed.

On a UNI, the connections continue to exist but remain in the failed state until you enable the port by executing upport.

Syntax

upport <ifNum>

Syntax Description

ifNum

The range for is ifNum is 1-31.

Use dspports or dspport as needed to determine which port to bring up.


Related Commands

dspport, dspports, dnport

Attributes

Log: yes

State: active

Privilege: GROUP1


Example

Restore port 1 on the current card to operation.

MGX8850.1.PXM1E.a > upport 1

users

Users—PXM45, PXM1E

The users command displays the following information about user sessions that are currently running:

Access method and port (telnet session to the PXM45, for example)

Current card slot

Idle time for the user session (can depend on the sesntimeout command)

User-name (the login name)

Point from which the user gained access (for example, an IP address in the case of a telnet session or the word "console" if the user logged in through a local terminal at the console port)

Note that users shows the current user sessions, whereas the dspusers command shows the names of all the user accounts on the switch.

Syntax

users

Syntax Description

This command takes no parameters.

Related Commands

dspusers, adduser, cnfuser, timeout

Attributes

Log: no

State: active, standby

Privilege: ANYUSER


Example

Display the current users on the switch. Only one user-session is currently running. The user telnetted to the switch from IP address 10.18.247.21. The idle time is 0 because the current user has just executed the users command. If other user-sessions were running and one or more were idle, the idle time for each user would be a non-zero number. Change to the AXSM CLI and execute users.

pop20one.7.PXM.a > users

    Port        Slot      Idle       UserId       From
    -------------------------------------------------------------
    telnet.01 *    7     0:00:00     davids4      10.18.247.21 

pop20one.10.AXSM.a > users

    Port        Slot      Idle       UserId       From
    -------------------------------------------------------------
    telnet.01     10     0:00:00     cisco        0.0.0.0

smterm.03 * 10 0:00:00 davids4 slot 7

verifydiskdb

Verify Disk Database—PXM45, PXM1E

The verifydiskdb command activates a utility that validates the database synchronization between the active and standby PXMs. This database includes information about all slots. The compared information resides in the D:/DB directory (see the section, "Structure of the D:\DB2 Directory," for its contents). You can configure the scope of the comparison and the output displays.

The most common use of the verifydiskdb command is in connection with a switchover. If you suspect the active card is bad, you can first run verifydiskdb to check databases before switchover. If discrepancies appear, you can reset the standby then switch over after the standby comes up. You can verify database synchronization before and after running the switchcc or switchredcd command. Similarly, after doing substantial provisioning or configuration changes or after you insert a card, you can verify that the databases have synchronized on the active and standby PXMs.


Note This utility does not correct discrepancies between databases. It can show past discrepancies and show whether the information is now synchronized. Discrepancies are corrected by the database synchronization task or other internal tasks. If discrepancies persist, you can force synchronization by resetting the standby PXM. Replacing a card may become necessary.


This utility does the following:

Checks the data for all slots or a single slot

Lets you display status while the utility is running

Verifies either just the control information or complete records, as follows:

For the control information, it can discover any discrepancy between the primary version databases and their associated tables. It also verifies flags, commit IDs, and the checksum value of the records in these tables.

For the complete records, it performs a byte-for-byte verification of data records in addition to the control information.

Runs a number of passes, logs discrepancies, and shows if discrepancies have been synchronized

Lets you abort the utility

When the utility either completes, fails, or aborts, the status is communicated to the network management station (such as a CWM workstation) through an SNMP trap. If the utility aborts, the status is also communicated to the CLI.

The options for the verifydiskdb command let you specify the following:

Choice of a specific slot or all slots

The level of verification (control information or complete records)

A display of the utility's status

A display of the synchronization log file

Two levels of verification are available. Level 1 is control records only. Level 2 is control information plus data records (complete records). For level 2, the utility sequentially compares the flags, commit IDs, checksums, and data records. See Figure 2-18 for an illustration of these levels of comparison.

Figure 2-18

Hierarchy of Level 1 and Level 2 Comparisons

Control Records

The control records consist of the items in the following hierarchy:

1. The flags are internal flags for the purpose of comparing databases. A flag has information about the records. For example, if the flag for record 20 on an active card indicates the record is valid, but the flag for record 20 on the standby card shows that record 20 is invalid, a flag discrepancy exists. In this case, the utility quits instead of actually comparing record 20 on the active and standby cards.

2. The commit IDs are values the utility uses to determine if it has the latest records to compare.

3. The checksums apply to the flags and commit IDs.

Structure of the D:\DB2 Directory

Figure 2-19 Contents of the DB2 Directory

For each logical slot, two versions (at most) exist: a primary version and a secondary version.

For each version, one or more items with the format "dbName" exist. For each "dbName," one MAP file and one or more DAT files exist.

In regard to actions performed by the utility on the items in the DB2 directory, note the following:

One or more logical slots are verified. This choice is one of the verifydiskdb parameters.

Only the primary database version is verified.

A MAP file contains control information for the DAT files under its parent directory. The control information consists of DAT file sizes, file names, and the number of files. The information in the MAP file is compared to the output of an ll command from the node to verify the file structure.

A DAT file contains two copies of each record, a copy-A and a copy-B. A record contains record control information and application data. The utility compares only the information in the latest copy. An example of a DAT filename is sm_hdr_v83.MAP.

Operational Characteristics of verifydiskdb

The Disk Sync Verify feature has the following operational characteristics:

If the discrepancy-count for a slot reaches the configured amount, the utility stops verification of that slot. The captured information up to the moment of termination goes to the log. If you chose "all" for the check -sl slot parameter, the utility would proceed to the next logical slot.

If the verification utility terminates its check of control records on one part of the hierarchy, it skips the remaining records for that part. For example, if a flag indicates the records are invalid, no reason exists to compare the records themselves between the databases. If the flags indicate that valid records exist, the utility proceeds.

If it detects 20 discrepancies for a slot (the maximum), the utility skips all remaining records for the slot and goes to the next slot.

If repetitive passes are running and the utility detects that discrepancies have been synchronized, the utility stops.

An active verification stops if you run the switchcc command.

Upgrading a service module causes the utility to skip over that slot. If a verification is running on a slot and an upgrade begins for that slot, the utility skips over that slot.

If you run the addred command during a database verification, the verification does not occur for the card slot that is about to become the standby.

If verification is running when you use the delred command, it may not verify the information for the card slot that is becoming the active slot as a result of delred. The status of the card in transition must become active/ready before the utility attempts database verification for the slot.

If a failure occurs on the active or standby PXM during verification, the reported discrepancies between databases are not necessarily valid.

If provisioning occurs during verification, the utility may show discrepancies even though the information on the active and standby PXMs actually is valid.

If you plug in a service module (with paired PXMs up) then run this utility, discrepancies may appear for the card slot. The slot is likely to be shown as "unstable." To ensure that the databases are synced, reset the standby PXM.

If the card in a targeted slot fails during verification, the utility proceeds to the next card slot.

While the verification is in progress, you are not able to enter verifydiskdb display combination and see the log.

While the verification is in progress, you can the status of the verification by entering the verifydiskdb status combination.

The log files for the previous run and the latest run are persistent. However, the log files are not synchronized upon switchover and are not synchronized to the active PXM during a verification run.

Usage Guidelines

The maximum of discrepancies is 20. If you see 20 discrepancies, you may want to consider further actions. You can synchronize the databases by resetting the standby PXM. After the standby comes up, run the verifydiskdb command again.

If discrepancies appear for a slot, you should focus subsequent iterations of the utility on that slot.

For persistent discrepancies, consider the following:

If the same discrepancy repeatedly appears after synchronization, the database may be defective.

If discrepancies persist in diverse categories and for varying slots, the standby PXM or the link through which database updates pass may have a problem.

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

Troubleshooting Discrepancies Between the Active and Standby Disk

If the disk verification utility finds discrepancies, you can take one of the following approaches:

If the utility presents you with a list of discrepancies, try to gather any log files associated with the slot that shows discrepancies. If possible, attempt application-specific tasks to resync the records (for example, remove and re-provision, add a user, and so on). You can use the following commands for this approach:

1. dsplogs

2. dsplog

3. dsperr

The other approach is to enter the resetcd command to reset the standby PXM to re-synchronize it with the active disk.

Syntax

The verifydiskdb command runs with any of the following syntax forms:

verifydiskdb check [-l <level>] [-sl <slot>] [-p <iterations>]

verifydiskdb abort

verifydiskdb status

verifydiskdb display -l <log>

Syntax Description

check

After typing the subcommand check, you can specify each optional parameter or rely on one or more defaults.

-l <level> The level is either "1" or "2," as follows:

1: control information

2: actual data

Default: control information (1)

-sl <slot> For the slot, enter a number, otherwise the default is "all."

-p <iterations> Multiple passes creates the opportunity for software to resync that databases. The number of passes is as follows:

Range: 1-10

Default: 3

abort

If the utility is running, you can enter the sequence verifydiskdb abort to stop it. All information from the utility is lost.

status

If the utility is running, enter the sequence verifydiskdb status to see its progress. The displayed status is one of the following:

IDLE: the verification utility has never been executed.

IN PROGRESS: the verification utility is running.

DONE: the verification utility has finished.

FAIL: the verification utility has failed. Examine the log for more information.

display

This subcommand displays a log. After typing the subcommand display, type the keyword -l followed by the word new or old. If you start another verification, the switch saves the "new" log as "old" before it starts the verification.

Default: new


Related Commands

dsplogs, dsplog, dsperr

Attributes

Log: yes

State: active

Privilege: SUPER_GP


Display Contents for verifydiskdb

This section introduces the contents of the display when you include the status or display parameter. Details for these contents are explained in the Example section.

In addition to the types of records that the utility compares (control records and data records), the status display shows the three layers of hierarchy that are a part of the database:

An individual database, identified by a number and name

Tables within a database, identified by a number and a name

Records within a table

These layers are illustrated out in the forthcoming section.

If you enter verifydiskdb status, the display states whether or not a verification is running. If the utility is running, it displays the following snapshot of information (see the example that accompanies this list):

The configuration for the comparison (level, number of passes, and so on)

The Current Status shows the following:

The slot whose databases on active and standby PXM hard drives are being compared (slot 7)

The number of databases detected for the current slot (13 in the example below)

The total number of tables detected for all databases for the slot (88)

The index number of the current database being compared (12)

The name of the database currently being compared (spvcRed)

The index number of the current table being compared (81)

The name of the current table being compared (Disk_spvc_pep_db19)

The total number of records (0)

The number of records verified (0)

Databases verified (0)

Tables verified (6)

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

Databases Verified: 0, Tables Verified 6

The range of index numbers for the tables and databases includes 0, so the range for tables in the preceding example is 0-87. In the snapshot shown here, the current table index number is 81, and number of tables verified so far is 6.

Examples

Use the following series of commands:

1. Use the status parameter to see whether a verification is running. In this case, none is running.

2. Start verification with the default parameters, so you need to enter the check parameter but none of the optional parameters associated with check. Therefore, the slots are "all." The number of passes is 3. The level is 1 (just the control information).

3. With the utility now running, check the process with the status parameter.

4. Check the process with the display parameter. It shows the utility is running.

5. Again check the process by using the status parameter alone.

6. Again check the process by using the display parameter with no optional parameter. By not entering a parameter, the default of "new" applies The display is extensive.

M8850_LA.8.PXM.a > verifydiskdb status
Disk Sync Verification is currently not running.

M8850_LA.8.PXM.a > 

M8850_LA.8.PXM.a > verifydiskdb check

M8850_LA.8.PXM.a > verifydiskdb display
Disk Sync Verification is currently running.

M8850_LA.8.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
Databases Verified: 0, Tables Verified 6

M8850_LA.8.PXM.a > 

M8850_LA.8.PXM.a > verifydiskdb display
Disk Sync Verification is currently running.

In the preceding use of verifydiskdb display, the utility was still running. In the next use, the utility has finished, so it displays the results. A description for each slot in the display precedes the screen capture.

The display begins with the configuration for this comparison—the defaults in this case. The start and stop timestamps appear at the beginning of each of the per-slot results.

For slot 1, 2 discrepancies remained after 3 passes. The discrepancies were in the checksums for records 8 and 9. During the 3 passes, no discrepancies were synchronized.

For slot 2, the utility skipped to the next slot because of invalid slot: no card resides in slot 2.

For slot 3, verification finished with no discrepancies re-synced and no discrepancies found.

For slot 4, the utility skipped to the next slot because the card was in an unstable state. This state can refer to a variety of conditions but usually means the card is in transition, as during reboot. The card might be stuck in transition.

For slot 5, verification finished with no discrepancies re-synced and no discrepancies found.

For slot 6, the utility skipped to the next slot because a firmware upgrade had not finished (the commitrev command had not yet been used on the slot).

For slot 7, verification finished with no discrepancies re-synced and no discrepancies found.

For slot 8, the utility skipped to the next slot because of invalid slot.

For slot 9, the utility was terminated (and the display was truncated in the example) because more than 20 discrepancies were found in the table named mib29.

M8850_LA.8.PXM.a > verifydiskdb display
        Verify Req Level: 1   All Slots   Req Iter: 3
--------------------------------------------------------------
------------------  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 Synced: 0
--------------------------------------------------------------
--------------------------------------------------------------
------------------  Information for Slot  2 ------------------
Start: 20/04/2002-17:43:58    -    End: 20/04/2002-17:43:58 
 
           Verify SKIPPED - INV_SLOT
 
 TotalofDbs= 0, TotalofTbls= 0, #DbVerf=0, #TblVerf= 0 
             No Discrepancies found for slot 2
--------------------------------------------------------------
--------------------------------------------------------------
------------------  Information for Slot  3 ------------------
Start: 20/04/2002-17:43:58    -    End: 20/04/2002-17:44:06 
 
             Verify DONE
 
 TotalofDbs= 4, TotalofTbls= 20, #DbVerf=4, #TblVerf= 20 
             No Discrepancies found for slot 3
--------------------------------------------------------------
--------------------------------------------------------------
------------------  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
--------------------------------------------------------------
--------------------------------------------------------------
------------------  Information for Slot  5 ------------------
Start: 20/04/2002-17:44:06    -    End: 20/04/2002-17:44:14 
 
             Verify DONE
 
 TotalofDbs= 2, TotalofTbls= 15, #DbVerf=2, #TblVerf= 15 
             No Discrepancies found for slot 5
--------------------------------------------------------------
--------------------------------------------------------------
------------------  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
--------------------------------------------------------------
--------------------------------------------------------------
------------------  Information for Slot  7 ------------------
Start: 20/04/2002-17:44:14    -    End: 20/04/2002-17:44:54 
 
             Verify DONE
 
 TotalofDbs= 13, TotalofTbls= 88, #DbVerf=13, #TblVerf= 88 
=============================================================
dbInd: 3 - dbName: provRed 
tblInd: 28 - tblName: Disk_prov_Ncdp_port
Record: 7  ActvChkSum: 0 StdbyChkSum: 905
===============================================================
 
                 Verification Slot Summary 
Start: 20/04/2002-17:44:14    -    End: 20/04/2002-17:44:54 
Total Discrepancies Found: 1, Total Discrepancies Synced: 0
--------------------------------------------------------------
--------------------------------------------------------------
------------------  Information for Slot  8 ------------------
Start: 20/04/2002-17:44:54    -    End: 20/04/2002-17:44:54 
 
           Verify SKIPPED - INV_SLOT
 
 TotalofDbs= 0, TotalofTbls= 0, #DbVerf=0, #TblVerf= 0 
             No Discrepancies found for slot 8
--------------------------------------------------------------
--------------------------------------------------------------
------------------  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
=============================================================

who

Who—PXM45, PXM1E

Use who to see details about the user currently logged into a card. The information consists of the:

Type of port where you logged into the card

Slot number of the current card

Idle time in hours, minutes, and seconds

Current username

IP address of the device that accessed the card (not the IP address of the card or node)

Syntax

who

Syntax Description

This command takes no parameters.

Related Commands

adduser, deluser, whoami

Attributes

Log: no

State: active, standby

Privilege: ANYUSER


Example

Display information about the user currently logged into the card.

MGX8850.7.PXM.a > who

Port        Slot      Idle       UserId       From
-------------------------------------------------------------
telnet.01 *    7     0:00:00     admin 171.71.25.240

whoami

Who Am I—PXM45, PXM1E

View the current login Cards on Which This Command Runs

Syntax

whoami

Syntax Description

This command takes no parameters.

Related Commands

adduser, deluser, who

Attributes

Log: no

State: active, standby

Privilege: ANYUSER


Example

Display information about the user of the current terminal session.

MGX8850.7.PXM.a > whoami

User ID:        cisco
Access Level:   CISCO_GP
Terminal Port: telnet.01

MGX8850.7.PXM.a >

zip

Zip-PXM45, PXM1E

The zip utility lets you zip a file or directory. A common application is for quickly copying an event or error log (and, if necessary, transferring to a workstation). Note the following characteristics:

If you zip a directory, this utility zips the directory recursively.

You can specify the entire path (see Example).

Execution of the zip utility is not logged.

If the destination zip file already exists, the system prompts you before continuing.

Syntax

zip <dir | file> <destination zip file>

Syntax Description

dir or

file

Specify either a file name or a directory name.


Related Commands

ls, ll, dir

Attributes

Log: no

State: active, standby

Privilege: CISCO_GP


Example

Zip the file named "foo."

M8830_SF.2.PXM.a > zip C:/FW/foo C:/TEMP/foo.zip