cc/td/doc/product/wanbu/mgx8850/20x
hometocprevnextglossaryfeedbacksearchhelp
PDF

Table of Contents

Shelf Management Commands

Shelf Management Commands

This chapter describes the shelf management commands. These commands allow you to add, delete, configure, display status for, and create statistics for node-level features.

The functional areas under shelf management are:

Position-Dependent and Keyword-Driven Parameters

A command can include parameters that are keyword-driven or position-dependent.

For position-dependent parameters, you must type parameters in the order they appear in the syntax description or on-line help. To create a logical port, for example, the position-dependent syntax is:

addport <ifNum> <bay.line> <guaranteedRate> <maxrate> <sctID> <ifType> [vpi]

For a keyword-driven parameter, a keyword must precede the value. The keyword is preceded by a dash and followed by the parameter (-timeout <secs>, for example). The order you enter keyword-driven parameters does not matter—although any preceding or succeeding, position-dependent parameters must appear as they do in the command syntax description.

In the following syntax example, the command is to delete more than one connection at a time. The mandatory, position-dependent connection identifier consist of a logical port (ifNum) and the VPI and VCI of the first connection to delete. After the connection identifier, the line shows two optional, keyword-driven parameters. These keyword-driven parameters let you enter the number of connections to delete and specify verbose mode:

delcons <ifNum> <vpi> <vci> [-num <num. conns to del>] [-verbose < 1 | 0 >]

Command Entry

When you enter a command with the current version of the product, you must type all intended arguments before you press the Return key or Enter key.

If you press the Return key or Enter key with incorrect parameters or no parameters (if the command requires parameters), a message displays the syntax and parameter ranges. The returned message may also suggest what the problem is. For example, the message may warn of too few parameters. No error messages or warnings appear until you complete the command.

Identifying the AXSM Models

The model number of an AXSM identifies the line speed, line count, and number of bays (see Table 2-1.) Note that the number of lines applies to an individual back card, so the total number of lines supported by the front card equals the highest line number times the number of bays. The OC-48 card AXSM-1-2488 has the lowest number of lines—one. The highest number of lines exist on the AXSM-16-155 and AXSM-16-T3E3—16, as the name indicates.

The MGX 8850 and MGX 8950 nodes use the concept of a bay. The bay refers to the upper or lower location of a single-height card. (The switch has a double-height card cage, so a single-height back card necessarily occupies either an upper or lower position.)

The T3/E3, OC-3, and OC-12 versions of the AXSM can have two back cards, one in bay 1 (upper location of the back slot) and the second in bay 2 (lower slot). The MGX-AXSM-1-2488 (OC-48 AXSM) can have a back card in bay 1 only. For further descriptions and illustrations of the card sets, refer to Cisco MGX 8850 Hardware Installation, Rel 2.0Cisco MGX 8950 Hardware Installation, Rel 1.0.


Table 2-1: Valid Line Numbers and Number of Bays for AXSM Card Types
Front Card Speed Lines Bays

AXSM-1-2488

OC-48

1

1

AXSM-4-622

OC-12

1-4

1-2

AXSM-16-155

OC-3

1-8

1-2

AXSM-16-T3E3

T3 or E3

1-8

1-2

Connection Capacities of the AXSM

The SVC and SPVC connection capacities for the front card, back card, and physical lines appear in Table 2-2 and Table 2-3. The capacity of a single AXSM card is greater than that of the node itself. Nevertheless, the tables provide these maximums when you plan the use of commands such as addrscprtn, addcon, and any other command where you may want to know the capacity of the configured item to support connections.


Table 2-2: Maximum Connections by Connection Type and Front Card
Front Card SVC SPVC

AXSM-1-2488

128 K

64 K

AXSM-4-622

128 K

64 K

AXSM-16-155

128 K

64 K

AXSM-16-T3E3

128 K

64 K


Table 2-3: Maximum Connections on Back Cards and Lines
Card Type Back Card Maximum Physical Line Maximum

OC-48c

128 K

64 K

OC-12c

64 K

32 K

OC-3c

64 K

32 K

T3

64 K

64 K

E3

64 K

64 K

Identifying Physical and Logical Elements

The Private Network-to-Network Interface (PNNI) control protocol and the AXSM use different formats to identify the same elements. This section describes the format of these elements in the PNNI and AXSM contexts and how they correspond to each other. When you configure or view items on the CLIs of different cards, you often need to specify it in PNNI as well as the AXSM. For example, when you configure a PNNI port on the CLI of the PXM45, you also need to configure a port on the CLI of the AXSM. Furthermore, when you display a connection on the AXSM, you identify that same connection using a different format on the PXM45 CLI. For specific examples of these parallel actions, see the Cisco MGX 8850 Software Configuration Guide, 2.0Cisco MGX 8950 Software Configuration Guide, 1.0.

Note   Apart from the way PNNI and the lower levels of logic identify the same element, the issue of configuration sequence needs explanation. When you configure logical ports—as just one example—you must complete certain tasks on the AXSM CLI before and after related PNNI tasks. This manual describes prerequisites for certain commands, but refer to the Cisco MGX 8850 Software Configuration Guide, 2.0Cisco MGX 8950 Software Configuration Guide, 1.0 for more details of this sequence.

AXSM Format

The AXSM items that you identify for addressing purposes are:

A logical port on an AXSM (and its CLI) always uses the label ifNum. For a UNI and NNI interface, a one-to-one correspondence exists between a logical port and a physical line. For virtual trunks, you can configure multiple ports for a line.

The maximum number of logical ports on an AXSM is 60 regardless of the AXSM model or the number of AXSM back cards. The range for ifNum is 1-60, also regardless of the whether the interface type is UNI. NNI, or VNNI.

PNNI Format

The elements of a port in the PNNI protocol are as follows:

The PNNI port identifier (portid) appears on only the PXM45 CLI. Throughout this manual, portid refers the following format:

[shelf.]slot[:subslot].port[:subport]

The portid consists of a series of mandatory and optional elements. Note the period or colon associated with each optional element inside the square brackets. For the correspondence between a PNNI port and the AXSM elements, see Table 2-4.


Table 2-4: Mapping PNNI Port ID to AXSM Elements
PNNI port AXSM

Shelf

N/A

Slot

Slot

Subslot

Bay (for back cards

Port

Line

Subport

Logical port (ifNum)

An example of a PNNI port identifier is 1:2.1:3. This portid corresponds to slot 1, bay 2, line 1, and logical port 3 on an AXSM.

abortrev

Abort Revision

The abortrev command causes the target card to use the previous operational firmware image. It provides a way out of a graceful upgrade that has shown signs of unacceptable performance. (For example, a new feature may not perform as expected.) The commands for changing firmware versions commands run on the PXM45, but they can target either a service module or the PXM45 itself.

You can execute the abortrev command after you have executed either loadrev or runrev but before commitrev. (After commitrev, the only way to restore the previous version is to force-load it by executing setrev.) The following list outlines the sequence for a graceful upgrade. For a state-by-state view that elaborates on this subject, see Table 2-5 and Table 2-6.

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

A graceful upgrade takes a single card or a redundant card pair through different states. In addition, the stage at which you execute abortrev on a redundant pair determines whether the system resets one or both cards in the pair. The reset depends on whether you execute abortrev before or after runrev. The stages of a graceful upgrade and the reset actions appear in Table 2-5 and Table 2-6. For a single-card upgrade, see Table 2-5. For a redundant-pair upgrade, see Table 2-6.

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-5: 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 abortrev, the card is reset.
Note   Of special note in Table 2-6, 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-6: 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.
Note   After you execute runrev, the PXM45 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.
Card(s) on Which Command Executes

PXM45

Syntax
abortrev 

<slot> 

<revision>
Syntax Description

slot

Number of the slot where firmware must revert to previous version.

revision

Revision number derived from the name of the firmware file. For an explanation, see the section, "Version Numbering Conventions," in the loadrev description.

A system response does not occur unless an error is detected.

Related Commands

loadrev, commitrev, runrev, setrev

Attributes

Log: log

State: active

Privilege: SERVICE_GP

Example

Abort loading firmware file pxm45_002.000.000.000_mgx.fw (therefore, 2.0(0) is the version parameter.)

pinnacle.8.PXM.a > abortrev 8 2.0(0)

addserialif

Add Serial Interface

The addserialif command activates a serial port on the PXM45-UI-S3 back card. The two types of serial ports are the console port and the maintenance port. These ports provide user-access for controlling the switch. The default rate on a serial interface is 9600 bits per second, and you can select a different rate for the terminal by executing cnfserialif.

Each port connects to a different type of terminal implementation. Refer to the Cisco MGX 8850 Software Configuration Guide for a description of how to use these physical ports for switch control.

Cards on Which This Command Executes

PXM45

Syntax

addserialif <port#>

port#

Specifies the physical port:

  • 1=maintenance port.

  • 2=console port.

Related Commands

cnfserialif, delserialif, dspserialif

Attributes

Log: log

State: active

Privilege: SUPER_GP

Example

Activate a console port.

node19.8.PXM.a > addserialif 2

addtrapmgr

Add Trap Manager

Set up an SNMP manager that you intend to receive SNMP traps.

Trap managers you add through addtrapmgr and trap managers that are added by the SNMP manager (Cisco WAN Manager or other application) do not age and are not deleted. To delete a trap manager, use either the deltrapmgr command or an SNMP Set on the intended object.

Card(s) on Which Command Executes

PXM45

Syntax
addtrapmgr 

<ip_addr> 

<portnum>
Syntax Description

ip_addr

IP address in dotted decimal format:

nnn.nnn.nnn.nnn, n=0-9 and nnn < 256

portnum

Port number on the workstation that receives traps. The range is 0-65535. If you add a trap manager through SNMP, the default portnum is 162

Related Commands

deltrapmgr, dsptrapmgr

Attributes

Log: log

State: active

Privilege: SUPER_GP

Example

Add a trap manager with IP address 161.10.144.56 to port 50.

node501.7.PXM.a > addtrapmgr 161.10.144.56 50

adduser

Add User

Adds a user account with associated name, privilege level, and password. The privilege level of the user you are adding must be lower than the user-level at which you execute adduser. For example, to create a user with a privilege 1, you must log in as a superuser or above.

You can execute commands that require either the same or lower level privilege. With superuser access, for example, you can execute commands that require "superuser," "group 1," or "anyuser" privilege. The minimum access level for a command appears in the Attributes section of each description.

In descending order of access privilege:

Card(s) on Which Command Executes

PXM45

Syntax
adduser 

<user ID> 

<accessLevel>
Syntax Description

After you enter a user ID and access level, the system prompts for a password, as the example shows.

user ID

String that you enter to log into the CLI of a PXM45 or a service module. Note that:

  • The name can consist of up to 12 characters composed of alpha and numeric characters and can include the special characters "_" and "-" but no spaces.

  • The name must begin with an alpha character.

  • The name is case sensitive.

  • The maximum number of user-names on a switch is 50.

accessLevel

System privilege level to be allocated for the user ID. Note that the accessLevel is case-sensitive and must be entered as it appears below:

  • SERVICE_GP

  • SUPER_GP

  • GROUP1

  • ANYUSER

The new user that you configure must have a lower accessLevel than that of the current user.

Related Commands

cnfuser, dspusers, deluser, cnfpasswd, whoami

Attributes

Log: log

State: active

Privilege: GROUP1

Example

Add a user named "fin" with privilege level GROUP1. To add a GROUP1 user, the current user-prefilter level must be SUPER_GP or higher. To determine the current username, execute the whoami command. To see all current privilege levels, execute the dspusers command.

If the privilege level of the current user in this example is GROUP1 or lower, the command fails after you enter the password for the second time, and the system returns a message stating that you entered an incoherent value for "-l " (the level).

pinnacle.7.PXM.a > adduser fin GROUP1
 
Enter password:
Re-enter password:

Add the user "leroy" but without establishing a password for "leroy." The system displays the default password "newuser." Subsequently, either a network administrator or the user "leroy" can execute the cnfpasswd command to create a password.

pop20two.7.PXM.a > adduser leroy ANYUSER
Enter password:
(default password "newuser" will be used)

bootChange

Boot Change

For boot-mode only, specify the boot IP address and gateway address of a PXM45 card. The IP address you define with bootChange is used only when the PXM45 is in the boot state.

In the current release, the only parameters you should enter are "inet on ethernet (e)" and "gateway inet (g)." The bootChange command presents one parameter at a time. Therefore, press the Return (or Enter) key at each prompt except for these two. The example in this description shows the two fields where you need to enter an IP address and the fields you skip.

Note   Use the ipifconfig command to assign IP addresses for the PXM45 and the shelf.
Card(s) on Which Command Executes

PXM45

Syntax
bootChange
Related Commands

none

Attributes

Log: log

State: active, standby

Privilege: SERVICE_GP

Example

Specify an IP address of 170.11.52.61 for the Ethernet port and 170.11.52.2 for the gateway IP address. The display shows all the fields that the node presents. For all fields except the ethernet and gateway prompts, press Return or Enter.

pinnacle.7.PXM.a > bootChange

 
'.' = clear field;  '-' = go to previous field;  ^D = quit
 
boot device          : lnPci
processor number     : 0
host name            : winter
file name            : /users/joloughl/pxm45_002.000.014-A1.fw
inet on ethernet (e) : 170.11.52.61
inet on backplane (b):
host inet (h)        : 170.11.25.42
gateway inet (g)     : 170.11.52.2
user (u)             : rli
ftp password (pw) (blank = use rsh):
flags (f)            : 0x0
target name (tn)     : pxm45-71
startup script (s)   :
other (o)            :

clrallcnf

Clear All Configurations

Deletes the configuration of all the cards in the switch. After clrallcnf, you need to reconfigure the switch. (See setrev description.)

Caution Be absolutely sure you need to execute this command because it clears all configuration files on the PXM45. After you first enter the command, the system prompts you to confirm the action.
Card(s) on Which Command Executes

PXM45

Syntax
clrallcnf
Related Commands

None

Attributes

Log: log

State: active

Privilege: SERVICE_GP

Example

Clear all the configuration elements for all the cards in the node. The system prompts for confirmation.

node1.7.PXM.a > clrallcnf

All SM's config will be deleted, and
        the shelf will be reset.
Do you want to proceed (Yes/No)?

cnfclksrc

Configure Clock Source

Configures a primary or secondary clock source for the node. A clock source can be:

Clock Operation

When the switch first powers up, the internal oscillator on the PXM45 provides the clock to the node. Thereafter, you configure the clock sources at each node according to a well-designed plan for network synchronization. A typical configuration for an MGX 8850 network starts with a Building Integrated Timing System (BITS) clock source of stratum 3 or higher on one node. Therefore, the node with the BITS clock becomes the master clock source for the network. The active clock drives the clock line on the backplane, and each service module takes its clock from this line. Thereafter, the clock goes out through every line and is available as a configurable clock source on the other nodes.

Currently, automatic propagation of a master clock through the network is not available. To propagate the BITS-sourced clock to the other nodes, you execute cnfclksrc on the PXM45 at each node to specify primary and secondary clocks derived from the AXSMs.

(For a description of line-level looped timing, refer to the cnfln description the chapter, "Equipment and Resource Provisioning." With looped timing, a clock arrives on a line and is redirected to become the transmit clock for only that line.)

Prerequisites to Clock Configuration

Whether it uses BITS or an AXSM line for a clock source, the node first must have a network controller. See the addcontroller description. For an AXSM-sourced clock, the additional prerequisites are:

Database Updates and Clock Configuration

If the node has a redundant PXM45, it automatically receives changes you make to the clock configuration as well as automated clock changes that occur under node management. For example, if you delete a clock source (delclksrc), the standby card automatically implements this configuration change. Also, any switch from primary to secondary source is recorded by the standby PXM45.

Card(s) on Which Command Executes

PXM45

Syntax

The syntax for cnfclksrc depends on the clock source:

For BITS clock:

cnfclksrc 
<priority> 
<portid>

portid has the format [shelf.]slot.port -bits e1 | t1 [-revertive <enable | disable>]

For AXSM-sourced clock (note the positions of the periods and colons):

cnfclksrc 
<priority> 
<portid>

portid has the format [shelf.]slot[:subslot].port[:subport]

Syntax Description

priority

The priority of the clock source is either primary or secondary. The default is primary.

portid for BITS

  • shelf is always 1 and is purely optional.

  • slot is the logical slot number 7 for a BITS circuit on the PXM45-UI S3 (regardless of where the active PXM45 resides).

  • port is a logical number that indicates the upper or lower external clock connector on the PXM45-UI S3. The logical port number for the upper connector is 35. The lower connector is 36.

  • bits—a required keyword once you specify slot number 7 and a port number of 35 or 36 because you have identified a BITS clock source. Type the string "-bits" followed by a space then either "e1" or "t1." See "Usage Guidelines" for details.

  • revertive—an option that applies to only the BITS clock. Type the string "-revertive" followed by the complete word "enable" or "disable." The default is disable. See "Usage Guidelines for cnfclksrc" for important details.

portid for AXSM

  • shelf is always 1 and is purely optional.

  • slot is the slot number of the AXSM.

  • subslot identifies the upper or lower bay of the back card—either a 1 for the upper bay or 2 for the lower bay (default is 1).

  • port is the line number on the AXSM. (The specified line must already be active (see upln).

  • subport is the logical port number in the range 1-60. This value is the logical port (or ifNum) that you must have assigned through addport. Also, the logical port must be known to PNNI (see dsppnports).

Usage Guidelines for cnfclksrc

This section contains guidance for using cnfclksrc and important details about its parameters.

Specifying Primary and Secondary Clock Sources

Before using cnfclksrc, note the following:

Changing the Priority of a Clock Source

To change the priority of a clock source, the command sequence depends on the priority of the sources:

Configuring a BITS Clock

You can configure a node to get its primary and secondary clocks through the BITS circuitry on the PXM-UI S3. (The PXM-UI S3 has two connectors to receive highly stable clocks from an external device. The PXM-UI S3 can support stratum levels 1-3.) If primary and secondary clocks are both externally-sourced, they must be the same rate. For example, you cannot specify a T1 primary source and an E1 secondary source.

Note   Whenever the internal oscillator becomes the primary or secondary source due to a failure, a minor alarm is triggered on the local node.

With the current BITS scheme on the MGX 8850 node, you can enable a revertive mode for the primary clock source. The revertive mode pertains to the restoration of a failed primary BITS clock (where the failure is due to a loss of the signal.) If a primary clock returns after a failure and revertive mode is enabled, the node automatically reverts to the primary source. Note that the restored primary clock must be available for 12 seconds before it again becomes the active clock source.

If the primary clock source fails and revertive mode is disabled, you must re-configure the primary source after the failure has been corrected.

To change the mode from revertive to non-revertive, execute cnfclksrc. Follow the portID and priority with "-revertive disable."

Note   For an E1 BITS clock, the current product is automatically limited to two parameters of an E1 line that is used as a BITS source: twisted pair cabling and date-type signaling.
Related Commands

dspclksrcs, delclksrc, dspclkalms

Attributes

Log: log

State: active

Privilege: GROUP1

Examples

Configure the E1 clock at the upper connector of the PXM-UI S3 as the primary source. Configure subport (logical port) 10 on the line of the AXSM-1-2488 in slot 3 as the secondary. For the secondary source on the AXSM, note the locations of the periods and colons. Upon successful execution, the system displays a confirmation message.

pinnacle.7.PXM.a> cnfclksrc primary 7.35 -bits e1
Clock Manager has been sucessfully executed.
 
pinnacle.7.PXM.a> cnfclksrc secondary 3:1.1:10
Clock Manager has been sucessfully executed.

Configure a primary network clock to revert to the highest priority E1 clock source after recuperation from a failure. Upon successful execution, the system displays a confirmation message.

pinnacle.7.PXM.a> cnfclksrc primary 7.36 -bits e1 -revertive enable
Clock Manager has been sucessfully executed.

cnfdate

Configure Date

Configure the system date. The system does not return a message unless an error occurred. To see the date, execute dspdate.

Card(s) on Which Command Executes

PXM45

Syntax
cnfdate 

<mm/dd/yyyy>
Syntax Description

mm/dd/yyyy

  • mm is the month in the range 01-12.

  • dd is the day in the range 01-31.

  • yyyy is the year in the range 0000-9999.

Related Commands

dspdate

Attributes

Log: log

State: active

Privilege: SUPER_GP

Example

Set date to June 26, 2000

excel.1.3.PXM.a > cnfdate 06/26/2000

cnfname

Configure Name

Specifies a name for the node. The case-sensitive name must begin with a letter. It can include:

After you enter the name, the system prompts you for confirmation. To see the configured name, execute dspcds or many of the other node-level display commands: the node name is the first item in the display.

Card(s) on Which Command Executes

PXM45

Syntax
cnfname 

<node name>
Syntax Description

node name

Node name consisting of up to 32 alpha-numeric characters.

Related Commands

None

Attributes

Log: log

State: active

Privilege: SUPER_GP

Example

Configure the node name to be "pinnacle_7." The system requests you to confirm the name. The CLI prompt returns with the new name. In this example, however, the name as it appears in the prompt is truncated to eight characters because of space limitations for information displayed in the prompt.

NODENAME.7.PXM.a > cnfname pinnacle_7
This node name will be changed to pinnacle_7. Please Confirm
Do you want to proceed (Yes/No)?
pinnacl.7.PXM.a >

cnfpasswd

Configure Password

Change your own password. After you enter the cnfpasswd command without parameters, the system prompts you to enter the new password then prompts you to re-enter it.

Note   The default password is for a user-account is newuser.
Card(s) on Which Command Executes

PXM45

Syntax
cnfpasswd 

<password>
Syntax Description

password

Your new password.

Related Commands

adduser, dspusers, cnfuser

Attributes

Log: log

State: active

Privilege: ANYUSER

Change your password. After you enter the command, it prompts you once to enter a new password then prompts you to re-enter it.

pinnacle.8.PXM.a > cnfpasswd

Enter password:
Re-enter password:

cnfserialif

Configure Serial Interface

The cnfserialif command lets you change the data rate on a serial interface on the PXM45-UI-S3 back card. The two types of serial ports are the console port and the maintenance port. These ports provide user-access for controlling the switch. The default speed n a serial interface is 9600 bits per second, but higher speed terminals are frequently available.

Each port connects to a different type of terminal implementation. Refer to the Cisco MGX 8850 Software Configuration Guide for a description of how to use these physical ports for switch control.

Cards on Which This Command Executes

PXM45

Syntax
cnfserialif 

<port#> 

<speed>

port#

Specifies the physical port:

  • 1=maintenance port.

  • 2=console port.

speed

Specifies a data rate in bits per second. Valid entries are 1200, 2400, 4800, 9600, 19200, and 38400.

Related Commands

delserialif, dspserialif

Attributes

Log: log

State: active

Privilege: SUPER_GP

Example

Configure the console port to have a data rate of 19200 bits per second.

node19.8.PXM.a > cnfserialif 2 19200

cnfsnmp

Configure SNMP Strings

Configure the SNMP strings. The three strings are community, contact, and system location. You can configure only one of these strings with a single execution of cnfsnmp.

Cards on Which This Command Executes

PXM45

Syntax
cnfsnmp 

-community [string <ro | rw>] 

-contact [string] 

-location [string]
Syntax Description

-

-community

Keyword that establishes the community access string to permit access to SNMPv1 protocol.

The string acts like a password and permits access to the SNMP Protocol. Further, the access of either read-only or read-write allows operations on MIB Objects according to the setting. The setting can be either "ro" for read-only or "rw" for read-write. The default is read-only With read-only, authorized management stations are only able to retrieve MIB objects.

With read-write access, authorized management stations are able to retrieve and modify MIB objects.

-contact

Keyword that specifies the system contact string for sysContact MIB object in MIB-II. The string in this case is text that describes the contact. For example, the contact could be an administrator's email address. The default is no text.

-location

Keyword that specifies the location of the system. The default is no text. The system location string is used for sysLocation MIB object in MIB-II.

Attributes

Log: log

State: active

Privilege: SUPER_GP

Related Commands

dspsnmp

Example

Configure various community strings.

node19.8.PXM.a > cnfsnmp community ro
node19.8.PXM.a >cnfsnmp community comaccess 
node19.8.PXM.a >community string "comaccess" , read-only access
node19.8.PXM.a >cnfsnmp community comaccess ro
node19.8.PXM.a >community string "comaccess" read-only access
node19.8.PXM.a >cnfsnmp community superaccess rw 
node19.8.PXM.a >community string "superaccess" , read-write access

Give an email address for t he system contact

node19.8.PXM.a > cnfsnmp contact Dial System, Email :

Specify the location of the system as Building 3, Room 214.

node19.8.PXM.a >cnfsnmp location Building 3/Room 214

cnftime

Configure Time

Configures the time for the node. To see the time after you execute cnftime, use dspdate. The system displays the time in 24-hour format.

Note   Configure a timezone through cnftmzn and optional GMT offset through cnftmzngmt before you configure the time through cnftime.
Card(s) on Which Command Executes

PXM45

Syntax
cnftime 

<hh:mm:ss>
Syntax Description

hh:mm:ss

The format for time specification is:

  • hh is the hour in the range 01-24.

  • mm is the minute in the range 01-6.

  • ss is the second in the range 01-60.

Related Commands

cnfdate, cnftmzn, dspdate

Attributes

Log: log

State: active

Privilege: SUPER_GP

Example

Set time for 2 PM. plus 11 minutes and 22 seconds.

excel.1.3.PXM.a > cnftime 14:11:22

cnftmzn

Configure Timezone

Configures the timezone in the Western Hemisphere for the switch. To configure a timezone outside the four standard timezones of the Western Hemisphere, enter the GMT argument, then execute cnftmzngmt to specify an offset in hours from Greenwich Mean Time.

The system returns no messages unless an error occurs. To see the timezone, execute dspdate.

Card(s) on Which Command Executes

PXM45

Syntax
cnftmzn 

<timezone>
Syntax Description

timezone

The possible timezones requires all uppercase characters.

GMT, Greenwich Mean Time

EST, Eastern Standard Time

CST, Central Standard Time

MST, Mountain Standard Time

PST, Pacific Standard Time

Related Commands

cnftime, cnfdate, cnftmzngmt, dspdate

Attributes

Log: log

State: active

Privilege: SUPER_GP

Example

Configure the timezone in the node to U.S. Pacific Standard Time.

excel.1.3.PXM.a > cnftmzn PST

cnftmzngmt

Configure Timezone Relative to GMT

Configures the timezone for the node relative to GMT. Typically, this command applies to nodes outside the four standard timezones of the Western Hemisphere. Use cnftmzngmt according to the following sequence:

Use dspdate to see the time.

Card(s) on Which Command Executes

PXM45

Syntax
cnftmzngmt 

<timeoffsetGMT>
Syntax Description

timeoffsetGMT

Number of hours offset from GMT in the range -12 through 12.

Related Commands

cnftmzn, cnftime, cnfdate, dspdate

Attributes

Log: log

State: active

Privilege: SUPER_GP

Example

Set time zone in the shelf to GMT plus 4 hours.

excel.1.3.PXM.a > cnftmzngmt 4

cnfuser

Configure User

Configure a new password or privilege level for a user. If the user does not already exist, executing cnfuser with a new user-name creates that user.

If you do not specify a user-name (userID) but include one or more of the other parameters, the command applies to the current user.

Card(s) on Which Command Executes

PXM45

Syntax
cnfuser 

-u <userID> 

[-p <password>] 

[-l <accessLevel>]
Syntax Description

-u

Keyword that specifies a string of 1-12 characters that identifies a user. The maximum number of users a system can accept is 50.

-p

(Optional) Keyword that specifies a new password with 5-15 characters for userId.

-l

Optional) Keyword that specifies a new access level for the user. The accessLevel can be SERVICE_GP, SUPER_GP, GROUP1, or ANYUSER. The new level you type must be lower than the privilege of the current user. See adduser description for an explanation of privilege levels.

Related Commands

adduser, deluser, dspusers

Attributes

Log: log

State: active, standby

Privilege: GROUP1

Example

Change the password and privilege lever of user "rocky." New password is "nevermind," and the privilege level is GROUP1. Note that the you must be logged in at a higher than GROUP1 privilege level to specify GROUP1 for "rocky." If the "-u" and userID (rocky) were not entered, this command would change the password and privilege of the current user.

raviraj.7.PXM.a > cnfuser -u rocky -p nevermind -l GROUP1

commitrev

Commit Revision

Completes a graceful upgrade by committing to the operating firmware image as the primary version. The commitrev command is the necessary conclusion to a graceful upgrade. See the loadrev description for more details about graceful firmware changes.

The impact of commitrev is:

The order of commands in a graceful upgrade, including the option of aborting the revision change, appears in the following list. For clarification of where firmware resides after each stage of the upgrade, refer to Table 2-7 for a single card and Table 2-8 for a redundant card pair.

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

The stages of a graceful upgrade and the reset actions appear in Table 2-7 and Table 2-8. For a single-card upgrade, see Table 2-7. For a redundant-pair upgrade, see Table 2-8. 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. If you execute abortrev before commitrev, one or two cards (redundant pair only) are reset, as the tables show.


Table 2-7: 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 abortrev, the card is reset.
Note   Of special note in Table 2-8, 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-8: 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.
Card(s) on Which Command Executes

PXM45

Syntax
commitrev 
<slot> 

<revision>

delclksrc

Delete Clock Source

Deletes a user-specified primary or secondary clock source. Changing a clock source or changing the priority of the source (primary or secondary) are the most frequent uses of delclksrc. See the description of cnfclksrc for these common uses of delclksrc.

Note   If the node has a redundant PXM45, it automatically receives changes you make to the clock configuration as well as automated changes to clock status that occur under node management. For example, executing delclksrc is a configuration change that the standby card automatically implements. Also, a switch from primary to secondary clock source is also recorded by the standby PXM45.
Card(s) on Which Command Executes

PXM45

Syntax
delclksrc 

<priority>
Related Commands

cnfclksrc, dspclksrcs, dspclkalms

Attributes

Log: log

State: active

Privilege: SUPER_GP

Example

Delete the primary clock source.

pinnacle.7.PXM.a> delclksrc primary

deltrapmgr

Delete Trap Manager

Delete a trap manager. The deltrapmgr command requires an IP address for deletion. To see existing trap managers, use dsptrapmgr. For more information about trap managers, see the Cisco MGX 8850 Switch Software Configuration Guide or the addtrapmgr description in this book.

Card(s) on Which Command Executes

PXM45

Syntax
deltrapmgr 

<ip_addr>
Syntax Description

ip_addr

IP address in dotted decimal format:

nnn.nnn.nnn.nnn, n=0-9 and nnn < 256

Related Commands

addtrapmgr, dsptrapmgr

Attributes

Log: log

State: active

Privilege: SUPER_GP

Example

Delete trap manager with IP address 161.10.144.56.

node501.7.PXM.a > deltrapmgr 161.10.144.56

deluser

Delete User

Removes a user from the list of users on an MGX 8850 node. The system does not allow you to delete a user with a privilege level higher than the level at which you execute the command. For example, if the current user privilege is 2 (GROUP2), you cannot delete a user at level 1 (GROUP1). See the adduser description for the user-privilege hierarchy. No screen output appears unless an error occurs.

Card(s) on Which Command Executes

PXM45

Syntax
deluser 

<user ID>
Syntax Description

user ID

User name, consisting of up to 12 characters.

Related Commands

dspusers, adduser

Attributes

Log: log

State: active

Privilege: GROUP1

 downloadflash

 
 Download the Flash 



 Use the downloadflash command to load the first boot code found by the PXM45 hard drive into flash memory. This command does execute at the runtime prompt. It operates in bootmode only.


 A downloadflash session concludes the sequence of tasks for performing a PXM45 boot code load. Prior to executing this command, you must access the boot code and transfer the file to the PXM45 hard drive by using a "put" command). Arguments within the "put" command let you load boot code to any combination of standby or active PXM45s. (See Example section for details.) Once firmware is installed in slot 7, the bootcode is mirrored to a new PXM45 in slot 8 if present. However, to ensure that the boot code is correct, use downloadflash as a manual way to download the boot code to the standby PXM45. 







Note   Make sure only one version of backup boot code resides in the firmware directory: either delete or rename old versions to ensure that downloadflash uses the correct version.




 Card(s) on Which Command Executes


 PXM45


 Syntax


downloadflash


 Related Commands	


 None


 Attributes


  



 Log: log


 State: active, standby


 Privilege: SUPER_GP 














 Example


 Do a PXM45 boot code load. Start with a tftp to the boot code source. Conclude with the download to the standby and the active PXM45. Despite the ".fw" argument in the command string, this is NOT a firmware load. The first lines show an attempt to run downloadflash within the runtime image.


Unknown.7.PXM.a > downloadflash 
Error: flash_file supported only at backup boot 
 
> ftp <switch_dest_addr>

> bin

> put <pxm_bkup_version>.fw PINNACLE@PXM45.BT

> quit

wilco.7.PXM.a > downloadflash

 



 dspclksrcs

 
 Display Clock Sources



 Displays the configuration and status of the clock sources on the node. (For details about network synchronization, see the description of cnfclksrc.) The dspclksrcs output consists of:








Note   Changes to the configuration and status of clocks go into the database on the active PXM45. If a standby (redundant) PXM45 exists, it receives the initial clock configuration and status but receives internal status updates only when you interact with the node in a way that changes a configuration or when the standby PXM45 switches to the active state.




 Type of Clock Source


 The type is either BITS or generic. Currently, generic applies to only an AXSM-sourced clock. If a user-specified priority of clock is not configured, the source is null. For the current release, the null source is presumed to be the internal oscillator.


 Possible Sources


 The source of the clock has the format [shelf.]slot[:subslot].port[:subport]. More typically, the source has the two-part, short-hand form slot.line or slot.port. If the source is an AXSM, the format is slot.line. 


 For a BITS clock, the format is slot.port. The slot for a BITS clock is 7. The logical port is always 35 or 36. Port 35 refers to the upper external clock connector, and port 36 refers to the lower connector.


 Clock Status


 The status of a particular clock source can be one of the following:



 Reason for Status Change


 The reasons that clock status can change are numerous. The dspclksrcs command displays a Reason field for both the primary and the secondary clock source. The reason can include first-time, user-specification of the clock source. The reason strings and their meaning appear in Table 2-9.



Table 2-9: Reasons for Change of Clock State 



Reason
Meaning



 okay


 The clock source is okay.




 unknown reason


 The clock manager has no information for Reason.




 no clock signal


 Loss of signal (LOS) on the clock source.




 frequency too high


 The frequency has drifted too high.




 frequency too low


 The frequency has drifted too low




 excessive jitter


 Jitter has exceeded tolerance for this stratum.




 missing card or component


 The active PXM45 has no clock hardware support.




 non-existent logical interface


 The interface is non-existent or not functioning.




 interface does not support clocking


 The interface does not support clocking.




 phase error


 The clock manger has detected a phase error in the clock.




 unlockable


 The clock manager has attempted to lock the source but found that the clock signal from this source is unlockable.




 out of lock or null


 The clock circuitry is again trying to lock a source that has gone out of locking range. Note that for Reason, "out of lock" and "null" is synonymous.




 reset—not a valid state


 The clock source has been reset.




 in locking—wideband test


 The clock circuitry is in wide bandwidth mode of the locking process. In this mode, the circuit tests the integrity of the source but with wide latitude for frequency accuracy. If the source passes this test, the circuit proceeds to the narrowband test.




 in locking—narrowband test


 The clock circuitry is in narrow bandwidth locking mode. In this mode, the circuit stringently tests the integrity of the source.




 locked


 The clock circuitry is locked to this source.













 Revertive Behavior


 For information on revertive behavior, see the cnfclksrc description.


 Card(s) on Which Command Executes


 PXM45


 Syntax


dspclksrcs


 Related Commands


 cnfclksrc, delclksrc, dspclkalms


 Attributes


  



 Log: nolog


 State: active, standby


 Privilege: ANYUSER 














 Example


 Display the current clock sources. The display shows that both the primary and secondary clocks are good. They are sourced at lines 2 and 3 of the AXSM in slot 6. Also, the active clock is provided by the the primary source. The primary and secondary clock reason is "okay" in each case.


pinnacle.7.PXM.a> dspclksrcs

Primary clock type:     generic  
Primary clock source:   6.2            
Primary clock status: good
Primary clock reason:   okay 
Secondary clock type:   generic  
Secondary clock source: 6.3            
Secondary clock status:   good 
Secondary clock reason:   okay 
Active clock:           primary 
source switchover mode: non-revertive 
 

 Display information on the clock sources. The display shows that nothing has been configured, so the internal oscillator generates the primary and secondary clocks. The primary and secondary clock reason is "okay" in each case.


Unknown.7.PXM.a > dspclksrcs

Primary clock type:     null
Primary clock source:   0.0
Primary clock status:   not configured
Primary clock reason:   okay
Secondary clock type:   null
Secondary clock source: 0.0
Secondary clock status:   not configured
Secondary clock reason:   okay
Active clock:           internal clock
source switchover mode: non-revertive
 
 

 Display information about the clock sources. This example shows a BITS clock for the primary source with revertive mode enabled.


pop20one.7.PXM.a > dspclksrcs

Primary clock type:     bits t1
Primary clock source:   7.35
Primary clock status:   ok
Primary clock reason:   okay
Secondary clock type:   generic
Secondary clock source: 9:1.1:1
Secondary clock status:   ok
Secondary clock reason:   okay
Active clock:           primary
source switchover mode: revertive
 

 dspdisk

 
 Display Disk



 Display utilization for all partitions on the hard disk. The display shows the allocated space and the free space. A likely application of dspdisk is a routine check of disk utilization by running a script that includes this command.







Note   The capacity of the disk is very large relative to typical usage and therefore does not present potential restrictions. The output shows the allocated space rather than the physical capacity of the drive.




 Card(s) on Which Command Executes


 PXM45


 Syntax


dspdisk


 Syntax Description


 This command takes no parameters.


 Related Commands


 cd


 Attributes


  



 Log: nolog


 State: active, standby


 Privilege: ANYUSER 














 Example


 Display the utilization for the default partition C.


orpswp3.2.PXM.a > dspdisk

==========================================================
 Partition C: Allocated Size:  800 MB Free Space:  574 MB
 Partition D: Allocated Size:  600 MB Free Space:  564 MB
 Partition E: Allocated Size:  100 MB Free Space:   99 MB
 Partition F: Allocated Size:  800 MB Free Space:  799 MB
========================================================== 

 dspipconntask

 
 Display IP Connectivity Task



 Display the current state of the IP connectivity task. As a part of a troubleshooting regimen, the dspipconntask command can help you isolate a problem related to IP connectivity. 


 Card(s) on Which Command Executes


 AXSM


 Syntax


dspipconntask


 Related Commands


 ipifconfig, dspipif, dspipifcache, setipconndebug


 Attributes


  



 Log: nolog


 State: active, standby


 Privilege: ANYUSER 














 Example


 Display the task information IP connection on the PXM45. Note that the Task Debug Level can be modified through the setipconndebug command.


pinnacle.8.PXM.a > dspipconntask

 
IP CONNECTIVITY TASK INFORMATION
----------------------------------------------------------
Task State:                  ACTIVE
Card State:                  READY
Task Id:                     0x10009
Subtask Id:                  0x10044
Disk API State:              OK
SyncRam API State:           OK
Task SyncRam State:          NO SYNCHRONIZATION
Task Disk Update Bitmap:
    Device Table:     0  0  0
Task SyncRam Update Bitmap:
    Disk:             0  0  0
    IO Links:         0  0  0
    Interface Cache:  0  0  0
Task Debug Level:            0x1
Task Logging To:             Event Log 

 dspipif

 
 Display IP Interface Configuration



 Display configuration and other information for either one or all IP interfaces on the current PXM45. If you request all interfaces by entering dspipif with no parameters, the display shows information for all interface types. The displayed information comes from the current state of the interface and the configuration specified through ipifconfig. The information consists of the:



 Card(s) on Which Command Executes


 PXM45


 Syntax


dspipif 

[interface]

 Syntax Description


  



 interface


 (Optional) An alphanumeric string that identifies a type of interface for display.Without this parameter, the system displays the configuration state of all interface types. The choices for interface are as follows:


  • lnPci0 specifies the Ethernet interface (the default on power-up).
    

  • atm0 specifies the ATM interface.
    

  • sl0 specifies the SLIP interface
    















 Related Commands


 ipifconfig, dspipifcache


 Attributes


  



 Log: nolog


 State: active, standby


 Privilege: ANYUSER














 Example


 Display information for all IP interfaces. The output shows that no configuration exists for the ATM interface but do for Ethernet and SLIP. Note that for each interface in the current release, the "unit number" has no meaning. The Flags field for Ethernet shows that the interface is UP, a broadcast address has been configured, ARP is enabled, and that the interface is running. (See the ipifconfig description for the meaning of these parameters. The output also shows the number of packets that have crossed the Ethernet interface. Although a configuration exists for SLIP, the display shows that no packets have crossed this interface.


pinnacle.7.PXM.a > dspipif

Unknown                          System Rev: 00.00   Jan. 04, 2000 12:16:22 GMT
MGX8850                                              Shelf Alarm: NONE
IP INTERFACE CONFIGURATION
--------------------------------------------------------------------
atm (unit number 0):
     Not Configured
lnPci (unit number 0):
     Flags: (0x63) UP BROADCAST ARP RUNNING
     Internet address: 172.29.52.88
     Broadcast address: 172.29.255.255
     Netmask 0xffff0000 Subnetmask 0xffff0000
     Ethernet address is 00:00:1a:53:c8:2c
     Metric is 0
     Maximum Transfer Unit size is 1500
     265475 packets received; 18864 packets sent
     0 input errors; 0 output errors
     0 collisions
     BRAM IP address: Not Configured Additional Flags: (0x0) 
sl (unit number 0):
     Flags: (0x71) UP POINT-TO-POINT ARP RUNNING
     Internet address: 0.0.0.0
     Destination Internet address: 0.0.0.0
     Netmask 0xff000000 Subnetmask 0xff000000
     Metric is 0
     Maximum Transfer Unit size is 576
     0 packets received; 0 packets sent
     0 input errors; 0 output errors
     0 collisions
     BRAM IP address: 0.0.0.0

 dspipifcache

 
 Display IP Interface Cache



 The command shows the mapping of SVCs that connect the PXM45s to workstations.


 Cards on Which This Command Executes


 PXM45


 Syntax


dspipifcache 

[interface]

 Syntax Description


  



 interface


 (Optional) The interface type. If you do not specify an interface type, the display contains cache contents for all interface types. The types are:


  • lnPci0 for Ethernet (the default on power-up)
    

  • atm0 for the ATM.
    

  • sl0 for SLIP
    















 Related Commands


 dspipif, ipifconfig


 Attributes


  



 Log: nolog


 State: active, standby


 Privilege: ANYUSER 














 Example


 Display the contents of the IP interface cache. The display shows that the cache currently is empty.


node19.8.PXM.a > dspipifcache
node19-                          System Rev: 02.00   Apr. 07, 2000 16:22:18 PST
MGX8850                                              Shelf Alarm: NONE
IP CONNECTIVITY INTERFACE CACHE
Interface         IpAddress       VcId    Age(Flush@120000)    Flags
--------------------------------------------------------------------------
    No Entries 
 

 dspload

 
 Display Load



 Display the current level of usage of various parameters on a partition. To convey a picture of what is available on a resource partition, the display shows the configured bandwidth and connection numbers and what has actually been utilized.


 Card(s) on Which Command Executes


 AXSM


 Syntax


dspload 

<ifNum> 

<partId>


 Syntax Description


  



 ifNum


 The logical port number. On the AXSM, the range is 1-60.




 partId


 The partition identifier. The range is 1-20. If necessary, use dsprscprtns to see the existing partitions.














 Related Commands


 dsprscprtn, addcon, dspcons, dspcon, cnfcon


 Attributes


  



 Log: nolog


 State: active, standby


 Privilege: ANYUSER 














 Example


 Display the load on partition number 1 on logical port 1. The display shows that very little of the available connections and bandwidth have been used. Also, no exceptions have been recorded. 


node19.1.AXSM.a > dspload 1 1
        +--------------------------------------------+
        |   I N T E R F A C E    L O A D   I N F O   |
        +--------------------------------------------+
        | Maxm Connections     : 0010000             |
        | Guaranteed Connections:0001000             |
        | Maximum Bandwidth    : 1412831             |
        | Guaranteed Bandwidth : 1412831             |
        | Available Igr Connections: 0009997         |
        | Available Egr Connections: 0009997         |
        | Available Igr Bandwidth  : 1411931         |
        | Available Egr Bandwidth  : 1411931         |
        +--------------------------------------------+
        |          E X C E P T -- V A L U E S        |
        +--------------------------------------------+
        | SERV-CATEG | VAR-TYPE | INGRESS  | EGRESS  |
        +--------------------------------------------+
        +--------------------------------------------+ 

 dsppvcif

 
 Display PVC Interface



 Display details about the PVC interface for IP connectivity. The output shows the:



 Cards on Which This Command Executes


 PXM45


 Syntax


 dsppvcif


 Syntax Description


 This command takes no parameters.


 Related Commands


 dspipif, pvcifconfig, ipifconfig, dspipifcache


 Attributes


  



 Log: nolog


 State: active


 Privilege: ANYUSER














 Example


 Display the current ATM interface state.


orioses5.1.PXM.a > dsppvcif

orioses5                         System Rev: 01.00   Aug. 10, 2000 18:36:01 GMT
SES-CNTL                                             Node Alarm: NONE
IP CONNECTIVITY PVC CACHE
--------------------------------------------------------------------
atm (unit number 0):
    Feeder VPI.VCI: 3.8
        Flags:           (0x38) VCMUX,PVC,FEEDER
        State:           (0x1) UP
        RxLCN:           722           TxLCN:            32776
        LCNindex:        0             Feeder Name:      svcbpx16
        Input Frames:    10            Output Frames:    10
        Input Errors:    0             Output Errors:    0 
 

 dspserialif

 
 Display Serial Interface



 The dspserialif command displays the data rate on one of the serial interfaces on the PXM45-UI-S3 back card. See cnfserialif for an explanation. (See the Cisco MGX 8850 Software Configuration Guide for an explanation of the application of these physical ports.)


 Cards on Which This Command Executes


 PXM45


 Syntax


cnfserialif 

<port#>

  

 


 port#


 Specifies the physical port:


  • 1=maintenance port.
    

  • 2=console port.
    













 Related Commands


 addserialif, delserialif, cnfserialif


 Attributes


  



 Log: nolog


 State: active


 Privilege: ANYUSER














 Example


 Display the console port speed.


Jupiter_Lower.7.PXM.a > dspserialif 2
  SerialPortNum   : 2
  SerialPortType  : console
  SerialPortSpeed : 19200
 

 dspsnmp

 
 Display SNMP Strings



 The dspsnmp command displays the SNMP strings. 


 Cards on Which This Card Executes


 PXM45


 Syntax


dspsnmp


 Syntax Description


 This command takes no parameters.


 Attributes


  



 Log: nolog


 State: ACTIVE


 Privilege: ANYUSER














 Example


 Display the current SNMP strings. This example shows that the only specified string is the community "ro."


node19.8.PXM.a > dspsnmp

node19-                          System Rev: 02.00   Apr. 11, 2000 15:04:00 PST
MGX8850                                              Shelf Alarm: NONE
 
Community:                                               ro
System Location:
System Contact 

 dsptrapmgr

 
 Display Trap Manager



 Display details about all existing trap managers. The dsptrapmgr output shows:



 Of these elements, the IP address and port number result from addtrapmgr.


 Card(s) on Which Command Executes


 PXM45


 Syntax


dsptrapmgr


 Syntax Description


 This command takes no parameters.


 Related Commands


 addtrapmgr, deltrapmgr


 Attributes


  



 Log: nolog


 State: active


 Privilege: ANYUSER 














 Example


 Display trap managers.


node19.8.PXM.a > dsptrapmgr

     ipAddress     PortNum  RowStatus   ReadTrapFlag  NextTrapSeqNum
  ---------------  -------  ----------  ------------  --------------
  171.71.55.21      2500       Add           Off       0
  172.29.65.87      2500       Add           Off       348
  172.71.59.21      2500       Add           Off       0
 
  LastTrapSeqNum:     385
  NumOfValidEntries:  3 
 

 dspusers

 
 Display Users



 Displays all current users and their access levels if the keyword -u is not given. If the key word -u is specified, it displays the user ID and access level of that user only.


 Card(s) on Which Command Executes


 PXM45


 Syntax


dspusers 

[-u <userID>]

 Syntax Description


  



 -u


 Keyword that specifies the user (userId) to display.














 Related Commands


 adduser, deluser, cnfuser


 Attributes


  



 Log: nolog


 State: active, standby


 Privilege: ANYUSER 














 Example


 	Show all configured users.


raviraj.7.PXM.a > dspusers

 
UserId        AccessLevel

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

cisco         CISCO_GP

service       SERVICE_GP

superuser     SUPER_GP

 

 Show access level for a specified user. The user ID is "raoul."


raviraj.7.PXM.a > dspusers -u raoul
 
UserId        AccessLevel

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

raoul	 SUPER_GP

 

 dspversion

 
 Display Version



 Show details for the versions of boot and runtime firmware residing on a card. You can execute dspversion. Typically, you would use dspversion in conjunction with the commands for changing a card's firmware version. (See Related Commands section.) For example, you can use dspversion to see if a particular firmware version is currently running.


 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


 For example, a firmware file may have the name "axsm_002.000.001.001_mgx.fw." Within this filename, the version-portion is 002.000.001.001. 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.000.001.001_mgx.fw, the version is 2.0(1.1). Similarly, if no patch were present, the version number would be 2.0(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 0, and the minimal maintenance number of 1 (per the IOS precedent). The last three bullets show developmental revision numbers:



 Cards on Which This Command Executes


 PXM45, AXSM


 Syntax


dspversion


 Syntax Description


 This command takes no parameters.


 Related Commands


 abortrev, commitrev, loadrev, runrev, setrev, dspcd


 Attributes


  



 Log: log


 State: active, standby


 Privilege: ANYUSER 














 Example


 Display the firmware version for the current PXM45.


pop20two.7.PXM.a > dspversion

 
  Image Type   Shelf Type    Card Type         Version   Built On
  ----------   ----------   ----------    ------------   ------------
     Runtime          MGX        PXM45         2.0(1)D   Jun 21 2000, 18:11:39
        Boot          MGX        PXM45      2.0(210)A1   - FW ID: 002.000.001 
 

 Display firmware image on the AXSM in slot 1. As the example shows, the command executes on the CLI of the AXSM after you have switched (cc) to that CLI.


Unknown.1.AXSM.a > dspversion

 
  Image Type   Shelf Type    Card Type         Version   Built On 
  ----------   ----------   ----------    ------------   ------------ 
     Runtime          MGX         AXSM         2.0(2)   Mar 31 2000, 16:36:39 
        Boot          MGX         AXSM      2.0(128)A1   - 
 

 ipifconfig

 
 IP Interface Configuration



 Configure an interface to provide IP connectivity for user-control of the switch. Typically, the Cisco WAN Manager application running on a local or remote work station uses this connection to control the switch.


 (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 Switch Software Configuration Guide Release 2.0 and the Cisco MGX 8850 Hardware Installation Release 2.0.)


 The ipifconfig command lets you specify:



 Usage Guidelines

 
 Except for the first-time, mandatory configuration of an IP address for the interface, the ipifconfig parameters are optional details that you can use to modify the interface. The design of the parameters includes default states that apply to a broad range of network designs. The purpose of this default design 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 PXM45 and workstation. Particularly, any attached routers should be feature-rich. For example, the most likely configuration consists of:








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




 Card(s) on Which Command Executes


 PXM45


 Syntax


ipifconfig 

<interface> 

[ip_address] 

[netmask <mask>] 

[broadcast <broad_addr>] 

[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 


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




 broadcast


 (Optional) Broadcast address—applies to only Ethernet.




 up | down


 (Optional) Set the interface to be either up or down. 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


 (Optional) 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


 (Optional) Specify 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


 (Optional) Specify 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


 (Optional) Specifies whether to use this interface as 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


 (Optional) Clear 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


 dspipif, pvcifconfig, dsppvcif, svcifconfig, dspsvcif, dspipifcache


 Attributes


  



 Log: log


 State: active


 Privilege: SUPER_GP














 Example


 Specify a IP interface with an ATM interface type, 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



 Downloads a firmware image from the FW directory on the disk to RAM on the targeted card. Executing is the first step in performing 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.


 Although loadrev runs on a PXM45, the target can be either a service 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 PXM45 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-10 and Table 2-11 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).
    



 A graceful upgrade takes a single card or a redundant card pair through different stages. Also, if you must execute abortrev on a redundant pair, the card (or possibly both cards in a redundant pair) are reset. The stages of a graceful upgrade and the reset actions appear in Table 2-10 for a single-card upgrade and Table 2-11 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-10: 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 abortrev, the card is reset.


 


















Note   Of special note in Table 2-11, 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-11: 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 PXM45 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


 For example, a firmware file may have the name "axsm_002.000.001.001_mgx.fw." Within this filename, the version-portion is 002.000.001.001. 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.000.001.001_mgx.fw, the version is 2.0(1.1). Similarly, if no patch were present, the version number would be 2.0(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 0, and the minimal maintenance number of 1 (per the IOS precedent). The last four bullets show developmental revision numbers:



 Card(s) on Which Command Executes


 PXM45


 Syntax


loadrev 

<slot> 

<revision>

 Syntax Description


  



 slot


 The number of the targeted card slot. 




 revision


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














 Related Commands


 abortrev, commitrev, runrev, setrev, dspversion, dspcd


 Attributes


  



 Log: log


 State: active


 Privilege: SERVICE_GP 














 Example


 Load version 2.0(4) to the AXSM in slot 5.


pinnacle.7.PXM.a > loadrev 5 2.0(4)

 pvcifconfig

 
 PVC Interface Configuration



 Configure a PVC for IP connectivity between the PXM45 and a workstation. Using a PVC for IP connectivity is appropriate if a connecting interface or device (such as a router) cannot support SVCs.


 Card(s) on Which Command Executes


 PXM45


 Syntax


pvcifconfig 

<interface>. 

<router | local>

<pvc_address> 

[ atmarp | noatmarp ]

[ llcencap | vcmux ] 

[ default | nodefault] 

[ reset ] 

[ delete ] 

[ clrstats ]

 Syntax Description


  



 interface


 An alphanumeric string that identifies the interface type for the current PVC 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 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) Force a reset of the PVC. After the PVC is freed, the call is attempted again.




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


 State: active


 Privilege:  SUPER_GP 














 resetsys

 
 Reset System



 Reset the entire node.


 Card(s) on Which Command Executes


 PXM45


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


 State: active


 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



 Restores all configuration files saved in the CNF directory on the hard drive. The saved configuration is the result of a prior execution of the saveallcnf command.


 Card(s) on Which Command Executes


 PXM45


 Syntax


restoreallcnf


 Related Commands


 saveallcnf


 Attributes


  



 Log: log


 State: active


 Privilege: SERVICE_GP














 Example


 Restore the system configuration.


pinnacle.7.PXM.a > restoreallcnf


 


 runrev

 
 Run Revision



 Causes a new firmware version to start running. In a redundant card pair, runrev first causes the standby card to become the active card. The runrev command is the second of the required commands in a graceful upgrade. It runs on the PXXM45 but can target either a service module or the PXM45.


 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-12 and Table 2-13.


    

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



 A graceful upgrade takes a single card or a redundant card pair through different stages. Also, if you must execute abortrev on a redundant pair, the card (or possibly both cards in a redundant pair) are reset. The stages of a graceful upgrade and the reset actions appear in Table 2-12 for a single-card upgrade and Table 2-13 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-12: 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 abortrev, the card is reset.


 


















Note   Of special note in Table 2-13, 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-13: 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.


 


 


















Note   After you execute runrev, the PXM45 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 this topology change.




 Card(s) on Which Command Executes


 PXM45


 Syntax


runrev 

<slot> 

<revision>

 Syntax Description


  



 slot


 Number of the targeted card slot.




 revision


 Revision number derived 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: log


 State: active


 Privilege: SERVICE_GP














 Example


 Run version 2.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.0(4) are present.


excel.8.PXM.a > runrev 7 2.0(4)

 routeShow

 
 Route Show



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


 Card(s) on Which Command Executes


 PXM45


 Syntax


routeShow


 Related Commands


 routestatShow


 Attributes


  



 Log: nolog


 State: active, standby


 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



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


 Card(s) on Which Command Executes


 PXM45


 Syntax


routestatShow


 Related Commands


 routeShow


 Attributes


  



 Log: nolog


 State: active, standby


 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 >
 

 saveallcnf

 
 Save All Configurations



 Use saveallcnf to save all configuration files to the CNF directory on the hard drive. This command takes significant time, so a warning message prompts you for confirmation before the system performs the task. To restore the system configuration, use restoreallcnf.


 You should execute saveallcnf only if no provisioning is occurring, otherwise you could lose some of the connections that are being added.


 Card(s) on Which Command Executes


 PXM45


 Syntax


saveallcnf


 Related Commands


 restoreallcnf


 Attributes


  



 Log: log


 State: active


 Privilege: SERVICE_GP














 Example


 Save the system configuration.


pinnacle.7.PXM.a > saveallcnf

The 'saveallcnf' command can be time-consuming. The shelf
must not provision new circuits while this command is running.
 
Do not run this command unless the shelf configuration is stable
or you risk corrupting the saved configuration file.
 
Do you want to proceed (Yes/No)?

 sesntimeout

 
 Session Timeout



 Specifies the number of seconds of idle time for the current user-session. 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. 


 To disable the session timeout function, specify 0 seconds. 


 Card(s) on Which Command Executes


 PXM45


 Syntax


sesntimeout 

[time_out]

 Syntax Description


  



 time_out


 Number of idle seconds time allowed for the session.














 Related Commands


 None


 Attributes


  



 Log: nolog


 State: active, standby


 Privilege: ANYUSER 














 Examples


 Display the current timeout.


pinnacle.7.PXM.a > sesntimeout

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

 Set the session timeout threshold to 5 minutes (300 seconds).


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

 setipconndebug

 
 Set IP Connection Debug



 Specify a debug mode and whether to use console or no console for debugging IP connectivity. This debugging 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


 Specifies whether you are executing the command from as console (ASCII) terminal or elsewhere.




 debuglevel


 Specifies a debug level. To select one or all of the following debug 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: nolog


 State: active, standby


 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



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







Note   For the first-time power-up of the system, you should execute burnboot to burn in the bootcode. For details, refer to the Cisco MGX 8850 Software Configuration Guide, Rel 2.0.




 From a high-level perspective, the setrev command has two effects. It causes the PXM45 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 non-graceful 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 PXM45, 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. The format of a firmware filename is:


 cardtype_version-element_platform.fw


 For example, a file may have the name "axsm_002.000.001.001_mgx.fw." Within this filename, the version-portion is 002.000.001.001. 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 maintenance is the only number that 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.000.001.001_mgx.fw, the version is 2.0(1.1). Similarly, if no patch were present, the version number would be 2.0(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 0, and the minimal maintenance number of 1 (per the IOS precedent). The remaining bullets show developmental revision numbers:








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




 Card(s) on Which Command Executes


 PXM45


 Syntax


setrev 

<slot> 

<version>






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




 Syntax Description


  



 slot


 Slot number of the card targeted for firmware specification.




 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 take the same version for the current release.














 Related Commands


 loadrev, runrev, commitrev, abortrev, dspversion, dspcd


 Attributes


  



 Log: nolog


 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 PXM45 to see the changing status of the target card. After setrev finishes, execute 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 PXM45, 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 PXM45 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 execution 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	  Execute dspversion to see the version of the runtime image.


pinnacle.9.AXSM.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   - 
 




 



 svcifconfig

 
 SVC Interface Configure



 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 execute svcifconfig twice. The first execution identifies the ATM end-station address (AESA) and encapsulation type at the router end. The second execution identifies the AESA—but no encapsulation type—for the switch.


 Card(s) on Which Command Executes


 PXM45


 Syntax


svcifconfig 

<interface> 

<router | local> 

<svc_address> 

[atmarp | noatmarp]

[llcencap | vcmux] 

[default | nodefault] 

[reset] 

[delete] 

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




 svc_address


 The NSAP portion for the SVCs that the switch 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) Force a reset of the SVC. The SVC is freed, then the call is attempted again.




 delete


 (Optional) Delete the specified AESA configuration.




 clrstats


 (Optional) Clear all SVC statistics on this interface.














 Related Commands


 ipifconfig, dspipif, dspsvcif, dspipifcache


 Attributes


  



 Log: nolog


 State: active


 Privilege: SUPER_GP














 Example


 First configure the AESA for the local (PXM45) 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

 switchcc

 
 Switch Core Cards



 Switch control of the MGX 8850 node from the present slot to the other PXM45 slot. If a standby PXM45 is not available, the node blocks the switchcc command.


 You cannot execute switchcc during a configuration-copy. If you attempt it, the system displays the message "Core card redundancy unavailable."


 Card(s) on Which Command Executes


 PXM45


 Syntax


 switchcc


 Related Commands


 None


 Attributes


  



 Log: log


 State: active


 Privilege: SERVICE_GP 














 Example


 Attempt a switchcc without a standby PXM45.


raviraj.7.PXM.a > switchcc

Do you want to proceed (Yes/No)? y
 
 Core card redundancy unavailable

raviraj.7.PXM.a > 

 timeout

 
 Timeout



 Display or change the maximum time that a user session can be idle before the system terminates that user's session. The units of measure are seconds. To change the timeout period, type a number that is less than or equal to 600 after the timeout command.


 Card(s) on Which Command Executes


 PXM45, AXSM


 Syntax


timeout 

[timeout_period]

 Syntax Description


  



 timeout_period


 (Optional) Number of seconds for the new timeout period. The maximum is 600. If you do not enter a timeout_period, the system displays the current timeout period.














 Related Commands


 sesntimeout


 Attributes


  



 Log: log


 State: active, standby


 Privilege: ANYUSER 














 Examples


 Display the current timeout.


pinnacle.7.PXM.a > timeout

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

 

 Set the session timeout to 3 minutes (180 seconds).


pinnacle.7.PXM.a > timeout 180

 
The timeout period for this session is now set to 180 seconds.

 





hometocprevnextglossaryfeedbacksearchhelp


Posted: Mon Oct  2 19:34:12 PDT 2000

Copyright 1989-2000©Cisco Systems Inc.