Table of Contents

Command Line Prompt

Identifying the ATM Switching Service Module Types

Command Syntax

Keyword-Driven and Position-Dependent Commands

List of Commands
?
abortrev
addcon
addcontroller
addlnloop
addport
addrscprtn
addtrapmgr
adduser
bootChange
bye
cc
cd
clrconcnt
clrallcnf
clralmcnt
clrcdcnt
clrerr
clrilmicnt
clrlog
clrportcnt
clrscrn
cmdhistory
cnfalm
cnfatmln
cnfcdsct
cnfcon
cnfclksrc

Usage Guidelines

Specifying Primary and Secondary Clock Sources
Configuring a BITS Clock

cnfdate
cnfilmi
cnfln
cnfname
cnfpasswd
cnfport
cnfrscprtn
cnfrteopt
cnfspvclog
cnfrteoptthld
cnfsnmp
cnftime
cnftmzn
cnftmzngmt
cnfuser
commitrev
copy
cp
del
delcon
delcons
delclksrc
delcontroller
delln
dellnloop
delport
delrscprtn
deltrapmgr
deluser
dncon
dnln
downloadflash
dspalm
dspalmcnf
dspalmcnt
dspalms
dspatmln
dspcd
dspcdalms
dspcderrs
dspcdcnt
dspcds
dspcdsct
dspcdstatus
dspcon
dspconcnt
dspcons
dspcontests
dspclkalms
dspcontrollers
dspenvalms
dsperr
dspilmi
dspilmiaddr
dspilmicnt
dspilmis
dspipconntask
dspipif
dspipifcache
dspln
dsplns
dspclksrcs
dspload
dsplog
dspndalms
dspport
dspportcnt
dspports
dspportsct
dsprscprtn
dsprscprtns
dsprteoptcnf
dsprteoptstat
dspsct
dspslotalms
dspsnmp
dspspvc
dspspvclog
dspspvcs
dspswalms
dsptrapmgr
dspusers
dspversion
Version Numbering Conventions

Firmware Filenames
Version Numbers

exit
help
history
ipifconfig
Usage Guidelines
loadrev
Version Numbering Conventions

Firmware Filenames
Version Numbers

logout
ls
optrte
ping
pvcifconfig
pwd
resetcd
resetsys
routeShow
routestatShow
runrev
sesntimeout
setipconndebug
setrev
Version Numbering Conventions

Firmware Filenames
Version Numbers

svcifconfig
switchcc
timeout
tstconseg
tstdelay
upcon
upilmi
upln
who
whoami

AXSM and PXM45 Commands

During normal operation, the high-level tools for configuring, monitoring, and controlling an
MGX 8850 switch are the CiscoView application for equipment management and the Cisco WAN Manager application for connection management. (Formerly, all functionality existed in the Cisco StrataView Plus application.) However, during initial switch installation, troubleshooting, or situations where low-level control is important, the command line interface (CLI) may provide the best access to the switch.

This chapter includes usage examples. For information on how to configure an MGX 8850 switch and its basic network services, refer to Cisco MGX 8850 Switch Software Configuration Guide Release 2.0.

Note   Release 2.0 of the MGX 8850 node introduces the concept of a bay. The bay refers to the back card position. The T3/E3, OC-3, and OC-12 versions of the ATM Switching Service Module (AXSM) can have two back cards, one in bay 1 (upper 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 Release 2.0.

Command Line Prompt

The format of the CLI prompt is:

name.slot number.card type.card state >

where:

• name is the name of the node ("unknown" until a you assign name with the cnfname command).

• slot number is the slot of the card. It can apply to the front or back card (regardless of the bay).

• card type identifies the Processor Switching Module 45 (PXM45) or a service module type, such as the ATM Switching Service Module (AXSM).

• card state is "a" for active or "s" for standby. If a card is active, it is either fully configured and ready to carry out its function or is already carrying out its function with live traffic. Typically, a card goes into the standby state when it first receives power or when you purposely put it in the standby state. For many commands, a card must be active before the command can execute, so each description in this chapter states whether the command can execute in the active state or any state.

An example of a CLI prompt is:

excel.6.AXSM.a >
 

The preceding prompt shows the:

• Name of the node is "excel."

• Slot number is 6.

• Card type is AXSM.

• State of the card is active.

Identifying the ATM Switching Service Module Types

The model of the ATM Switching Service Module (AXSM) identifies the line speed, line count, and number of bays (see Table 3-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 model name indicates.

Table 3-1: Valid Line Numbers for the AXSM Card

Front Card	Speed	Lines	Bays
AXSM-1-2488	OC-48	1	1
AXSM-4-622	OC-12	1-4	1-2
AXSM-2-622	OC-12	1-2	1-2
AXSM-16-155	OC-3	1-8	1-2
AXSM-8-155	OC-3	1-4	1-2
AXSM-16-T3E3	T3 or E3	1-8	1-2

Command Syntax

The notation for command and argument parameters follows:

• Commands and their parameters are separated by a space.

• Variables are in italics.

• Required arguments appear within left and right arrowheads ("< >").

• Optional parameters appear within square brackets ("[ ]").

• A vertical bar ( | ) represents the logical OR function.

Keyword-Driven and Position-Dependent Commands

A command can contain parameters that are keyword-driven or position-dependent. For position-dependent parameters, you must type the parameters in the order shown in the syntax description or on-line help. For example, to create a logical port, the position-dependent syntax is:

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

For a keyword-driven parameter, a command delineator precedes the parameter 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, position-dependent parameters must appear as they do in the command syntax description.

In the following syntax example, the purpose of 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 >]

When entering a command, type all arguments, then press the Return key or Enter key. If you enter a command with incorrect parameters or no parameters (if the command requires parameters), a message displays the syntax and parameter ranges.

List of Commands

This section contains tables that show the full name and functional group of each command for each card type. The commands available on the PXM45 appear in Table 3-2. The commands available on the AXSM appear in Table 3-3. Many commands apply to the PXM45 and the service modules but may have different parameters. In some cases, although a command applies to a service module, you enter it on the command line of the PXM45.

Table 3-2: PXM45 Commands

Command	Description
PXM45 Shelf Group
abortrev	Abort Revision
addtrapmgr	Add Trap Manager
clrcdcnt	Clear Card Counters
cnfrteopt	Configure Route Optimization
cnfrteoptthld	Configure Route Optimization Threshold
cnfsnmp	Configure SNMP
commitrev	Commit Revision
deltrapmgr	Delete Trap Manager
dspcd	Display Card
dspcds	Display Cards
dsperr	Display Error
dsplog	Display Log
dsplogs	Display Logs
dsprteoptcnf	Display Route Optimization Configuration
dsprteoptstat	Display Route Optimization Status
dspsnmp	Display SNMP
dsptrapmgr	Display Trap Manager
dspversion	Display Version (of runtime images and boot loader)
loadrev	Load Revision
optrte	Optimize Route
resetcd	Reset Card
runrev	Run Revision
setrev	Set Revision
switchcc	Switch Core Cards
PXM45 User Group
adduser	Add User
cc	Change Card
clrscrn	Clear Terminal Screen
clrlog	Clear Log
cnfpasswd	Configure Password
cnfuser	Configure User
deluser	Delete User
dspusers	Display Users
Help or ?	Help or ? (list of commands per card)
users	Users
PXM45 Node Group
cnfclksrc	Configure Clock Source
cnfdate	Configure Date
cnfname	Configure Name
cnftime	Configure Time
cnftmzn	Configure Time Zone
cnftmzngmt	Configure Time Zone Relative to GMT
delclksrc	Delete Clock Source
dspclkalms	Display Clock Alarms
dspclksrcs	Display Clock Sources
PXM45 IP Interface Group
dspipconntask	Display IP Connectivity Task
dspipif	Display IP Interface
dspipifcache	Display IP Interface Cache
dsppvcif	Display PVC Interface
dspsvcif	Display SVC Interface
ipifconfig	IP Interface Configuration
pvcifconfig	PVC Interface Configuration
setipconndebug	Set IP Connection Debug
svcifconfig	SVC Interface Configuration
PXM45 Alarm Group
dspcdalms	Display Card Alarms
dspcdstatus	Display Card Status
dspclkalms	Display Clock Alarms
dspenvalms	Display Environment Alarms
dspndalms	Display Node Alarms
dspslotalms	Display Slot Alarms
dspswalms	Display Switching Alarms

?

Help

Enter ? or help to view all commands you can execute on the current card and at the current user log-in privilege. The display does not show any commands with a privilege level that is higher than that of the current user.

If you follow the ? with part of a command name, the output shows all commands that contain that string. If you follow the ? with the complete name of one command, the output simply states whether that command is available.

Card(s) on Which This Command Executes

PXM45, AXSM

Syntax

?
[command]

Syntax Description

command

Full or partial name of a command.

Related Commands

help

Attributes

Log: no

State: any

Privilege: ANYUSER

Examples

raviraj.1.AXSM.a >? con
 
Available commands
------------------
ddcon
clrconcnt
cnfcon
delcon
delcons
dspcon
dspconcnt
dspcons
 

abortrev

Abort Revision

Causes the card to revert to the previous firmware version when executed after loadrev or runrev but before you execute commitrev. (The commitrev command declares an upgrade to be valid and removes the previous firmware version from the card's memory, so the only way to restore the previous version is to force-load it by executing setrev.)

The sequence for a graceful upgrade is:

1. loadrev loads a firmware version from the hard disk to a card's memory as the new primary version.

2. runrev causes the standby card to become the active card and start running the new version. At this point, the card that was active and is now standby begins to receive the new firmware version. In this way, it is ready with the new firmware in case the active card fails.

3. If an unacceptable problem occurs, the optional abortrev restores the previous primary 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 abortrev command causes the target card to use the previous operational (primary) 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 be performing as expected in its new environment.

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 resurrected database has no information about this addition to the topology.

Card(s) on Which This Command Executes

PXM45

Syntax

abortrev
<logical slot>
<revision>

Syntax Description

logical slot	Logical number of the targeted card slot.
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: Yes

State: Active

Privilege: SUPER_GP

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

addcon

Add Connection

Adds a logical connection as an SPVC on a service module. (The addcon command does not apply to SVCs.) Before you can add a connection, the following tasks must have been completed:

1. Activate the line through the upln command or the CiscoView application.

2. Create the logical port through the addport command (and possibly modify the logical port through cnfport) or the CiscoView application.

Adding a connection requires specification of a slave endpoint (at the remote end) then a master endpoint (at the local end). The master-slave scheme results in the following characteristics of execution:

• When you add a slave endpoint, the system returns a value that identifies that slave endpoint.

• When you add the master endpoint, you must provide the slave endpoint identifier. After you finish adding the master endpoint, the switch starts routing the connection.

By adding first a slave then a master endpoint, you are required to copy an endpoint identifier from the slave-related command execution to the master-related command execution.

To modify the bandwidth parameters or configure the usage parameter control (UPC), use cnfcon.

Card(s) on Which This Command Executes

AXSM

Syntax

addcon
<ifNum>
<vpi>
<vci>
<service type>
<mastership>
[-slave <NSAP.vpi.vci>]
[-lpcr <local PCR >]
[-rpcr <remote PCR>]
[-lscr <local SCR>]
[-rscr <remote SCR>]
[-lmbs <local MBS>]
[-rmbs <remote MBS>]
[-lcdvt <local CDVT>]
[-rcdvt <remote CDVT>]
[-lcdv <local maxCDV>]
[<remote maxCDV>]
[-lctd <local maxCTD>]
[-rctd <remote maxCTD>]
[-cc <OAM CC Cnfg>]
[-stat <Stats Cnfg>]
[-frame <frame discard>]
[-aw <Administrative Weight>]

pinnacle1.AXSM.a >addcon 1 10 40 1 s
slave endpoint added successfully
slave endpoint id : 00000E1000001C008051B730FFFFFF010B180100.10.40

addcontroller

Add Controller

Identifies a network control protocol to the Virtual Switch Interface (VSI) that runs on the node. If you do not identify a network control protocol (or simply controller), the switch does not use it. Adding a controller through the addcontroller command requires the following information:

• The type of controller, such as PNNI

• Where the controller runs--internally, on the local PXM45, or externally, through a virtual connection

Note   Currently, the only supported controller is PNNI.

Execute addcontroller before you partition the resources for that controller on individual service modules. For information on resource partitions, refer to the description of addrscprtn.

Card(s) on Which This Command Executes

PXM45

Syntax

The syntax differs for internal and external controllers:

Internal controller:

addcontroller 
<cntrlrId> 
i <cntrlrType> 
<lslot> 
[cntrlrName]

External controller:

addcontroller 
<cntrlrId> 
x <cntrlrType> 
<lslot> 
<bay> 
<line> 
<vpi> 
<vci> 
[cntrlrName]

Syntax Description for Internal Controller

cntrlrId	A number in the range 1-3 that identifies a network controller. The numbers are reserved, as follows: 1=PAR (Portable AutoRoute)--currently not used 2=PNNI 3=LSC (Label Switch Controller, also known as MPLS for Multiprotocol Label Switch Controller)--currently not used For an internal controller, the controller ID (cntrlrId) must be the same as the controller type (cntrlrType). Because the only available controller at this time is PNNI, the sequence must be "2 i 2." See the example at the end of this description.
i	Keyword indicating that this controller is internal.
cntrlrType	A number in the range 1-3 that identifies a network controller. For internal controllers, the numbers are reserved, as follows: 1=PAR (Portable AutoRoute)--currently not used 2=PNNI 3=LSC (Label Switch Controller, also known as MPLS for Multiprotocol Label Switch Controller)--currently not used For an internal controller, the controller type (cntrlrType) must be the same as the controller ID (cntrlrId). Note that the only available controller at this time is PNNI.
lslot	The logical slot number of the PXM45 on which the controller resides. Regardless of which PXM45 is active, lslot is 7.
cntrlrName	(Optional) A string to serve as a name for the controller.

Note   Currently, the switch supports only an internal controller.

Syntax Description for External Controller

cntrlrId	A number in the range 4-20 that identifies an external controller. (cntrlrId 1-3 is reserved for internal controllers.) For external controllers, the cntrlrId does not need to be the same as the cntrlrType.
x	Keyword indicating that this controller is external.
cntrlrType	A number in the range 1-3 that identifies the controller: 1=PAR (Portable AutoRoute)--currently not used 2=PNNI 3=LSC (Label Switch Controller, also known as MPLS for Multiprotocol Label Switch Controller)--currently not used
lslot	The number of the slot that has the virtual connection through which the controller operates. The ranges are 1-6 and 9-16.
bay	Upper or lower position of the back card. Type a 1 for upper bay or a 2 for lower bay.
line	A number specifying the physical line number. The range is 1 through the highest number of lines on the back card. See Table 3-1 for a list.
vpi	VPI in the range 1-255.
vci	VCI in the range 1-65535.
cntrlrName	(Optional) A string to serve as a name for the controller.

Related Commands

dspcontrollers, delcontroller

pinnacle8.PXM45.a > addcontroller 2 i 2 7 pnni

addlnloop

Add Line Loop

Specifies a loopback state for a line on the current service module.

Card(s) on Which This Command Executes

AXSM

Syntax

addlnloop 
<-ds3 | -e3 | -sonet> <bay.line> 
-lpb <loopback type>

Syntax Description

addport

Add Port

Creates a logical port. A logical port is associated with a physical line. For NNI, a line can support more than one logical port. In contrast, a UNI line can support only one logical port.

The possible range of logical port numbers for the AXSMs is 1-60 regardless of the AXSM model. For an NNI, the typical maximum is no more than 3 logical ports (whether the port number is 1-3 or 58-60).

Before you execute addport, the line to which you add the logical port must be active. See the description for upln.

Card(s) on Which This Command Executes

AXSM

Syntax

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

Note   For standard ports (non-virtual trunk applications), guaranteedRate must be the same as maxrate. Currently, the MGX 8850 routing switch supports only standard ports.

Syntax Description

ifNum	A logical port (interface) number in the range 1-60. Although the range of port numbers is 1-60, only 1 port is allowed if the line operates as a UNI. When the interface supports more than one port, the typical maximum number of ports is 3.
bay.line	Identifies the bay (1 or 2) and the number of the line. The line number is from 1 to the highest numbered line on the back card. For the range of line numbers on specific AXSM models, see Table 3-1.
guaranteedRate	Guaranteed rate on a port in cells per second. The total guaranteed rate cannot exceed the highest value in the following ranges: OC48: 50-5651328 cps OC12: 50-1412832 cps OC3: 50-353208 cps T3: 50-96000 cps for PLCP or 104268 cps for ADM E3: 50-80000 cps
maxRate	Maximum rate on a logical port in cells/second. OC48: 50-5651328 cps OC12: 50-1412832 cps OC3: 50-353208 cps T3: 50-96000 cps for PLCP or 104268 cps for ADM E3: 50-80000 cps
sctID	The numeric ID of the service class template (SCT) for the egress direction. The file must exist on the PXM45 disk. See cnfsct.
ifType	Specifies the interface type: 1=UNI 2=NNI 3=Virtual path NNI
vpi	Virtual path identifier in the range 1-4095. Reserved for future use, it applies to logical ports on a virtual trunk.

Related Commands

cnfport, delport, dspport, dspports

Attributes

Log: Yes

State: Active

Privilege: ANYUSER

pinnacle.9.AXSM.a > addport 1 1.1 96000 96000 4 2

addrscprtn

Add Resource Partition

Add a resource partition. A resource partition consists of:

• Guaranteed percentage of bandwidth

• VPI and VCI ranges

• Minimum and maximum number of connections

Before adding a resource partition, you must have:

• Activated physical lines on the card (upln and optional cnfln).

• Added logical ports to the physical lines (addport and optional cnfport).

• Executed addcontroller on the PXM45 to identify a controller type to the Cisco Virtual Switch Interface (VSI) and give that controller an ID number. The addrscprtn command takes this controller ID as an argument.

The current network control application is PNNI. You may need to add or configure partitions to reflect future inclusion of MPLS or other controllers.

Note   On a virtual trunk, the min_vpi and max_vpi must be the same.

Card(s) on Which This Command Executes

AXSM

Syntax

addrscprtn 
<if_num> 
<part_id> 
<ctrlr_id> 
<egrminbw> 
<egrmaxbw> 
<ingminbw> 
<ingmaxbw> 
<min_vpi> 
<max_vpi> 
<min_vci> 
<max_vci>
minConns
maxConns

Syntax Description

if	Logical interface number in the range 1-60.
part_ID	The number of the partition in the range 1-250.
ctrlr_id	The number of the controller in the range 1-20.
egrminbw	A minimum percentage of the egress bandwidth, where each unit of egrMinBw is 0.00001 of the total bandwidth on the port. (An egrMinBw of 1000000=100%.) The purpose of this design is to provide a high degree of granularity.
egrmaxbw	A maximum percentage of the bandwidth, where each unit of egrMaxBw is 0.00001 of the total bandwidth available to the port. (An egrMaxBw of 1000000=100%.) Note that the resulting bandwidth must be at least 50 cps.
ingminbw	A minimum percentage of the ingress bandwidth, where each unit of ingMinBw is 0.00001 of the total bandwidth available to the port. For example, an ingMinBw of 1000000=100%.
ingmaxbw	A maximum percentage of the ingress bandwidth, where each increment of ingMaxBw is 0.00001 of the total bandwidth on the port. For example, an ingMaxBw of 1000000=100%. Note that the maximum ingress bandwidth must be at least 50 cps.
minvpi	Minimum VPI in the range 0-4095 for an NNI. For a UNI, the range is 0-255.
maxvpi	Maximum VPI in the range 0-4095 for an NNI. For a UNI, the range is 0-255. The maxvpi cannot be less than the minvpi.
minvci	Minimum VCI in the range 32-65535 or 32-131072 (on the OC-48 model only).
maxvci	Maximum VCI in the range 32-65535 or 32-131072 (on the OC-48 model only).
minConns	A guaranteed minimum number of connections. The range is between 0 and the maximum number of connections in the port group. See dspcd port group information.
maxConns	A guaranteed minimum number of connections. The range is between 0 and the maximum number of connections in the port group. See dspcd port group information. maxConns cannot be less than minConns.

Related Commands

cnfrscprtn, delrscprtn, dsprscprtns, dsprscprtn

Attributes

Log: no

State: any

Privilege: ANYUSER

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 This Command Executes

PXM45

Syntax

addtrapmgr 
<ip_addr> 
<portnum> 

Syntax Description

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 added user must be the same or 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 user at privilege level 1, SUPER_GP, or service level. You can execute commands that require the same or lower level. The minimum access level for a command appears in the Attributes section of each description.

In descending order of privilege:

• Service (for potentially dangerous configuration commands or complex troubleshooting commands

• Superuser

• Numerical levels 1-5 (specified in the case-sensitive range GROUP1-GROUP5): 1 is the highest, and 5 is the lowest.

Card(s) on Which This Command Executes

PXM45

Syntax

adduser <user ID> 
<accessLevel>

Syntax Description

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

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.

Note   Use the ipifconfig command to assign IP addresses for the PXM45 and the shelf.

Card(s) on Which This Command Executes

PXM45

Syntax

bootChange

Related Commands

Attributes

Log: Yes

State: any

Privilege: SERVICE_GP

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) : 172.19.52.61
inet on backplane (b):
host inet (h)        : 172.19.25.42
gateway inet (g)     : 172.19.52.2
user (u)             : rli
ftp password (pw) (blank = use rsh):
flags (f)            : 0x0
target name (tn)     : pxm45-71
startup script (s)   :
other (o)            :
 

bye

Bye

Use the bye command to exit the current CLI shell.

Card(s) on Which This Command Executes

PXM45, AXSM

Syntax

bye

Related Commands

logout, exit

Attributes

Log: Yes

State: any

Privilege: ANYUSER

pinnacle.8.PXM.a > bye
 
(session ended)

cc

Change Card

Change from the current command line to the command line of another card. The cc command takes a physical slot number.

Card(s) on Which This Command Executes

PXM45, AXSM

Syntax

cc 
<slot number>

Syntax Description

node1.12.AXSM.a > cc 8 
 
(session redirected)
 
node1.8.PXM.a >
 

cd

Change Directory

Change to another directory on the PXM45 hard disk.

Card(s) on Which This Command Executes

PXM45

Syntax

cd 
<directory_name>

Syntax Description

directory_name

Name of the destination directory.

Related Commands

ls, pwd, rename, rm/rmdir, copy

Attributes

Log:Yes

State:Any

Privilege: SERVICE_GP

raviraj.7.PXM.a > cd FW
 
raviraj.7.PXM.a >
 

Verify the current directory by using the pwd command.

raviraj.7.PXM.a > pwd
C:FW

raviraj.7.PXM.a > cd ..
 
raviraj.7.PXM.a > pwd
C:

clrconcnt

Clear Connection Counters

Clear all counters for ATM cells on a connection. The command applies to an SVC or an SPVC. For a list of displayed counters, see the output of dspconcnt.

Card(s) on Which This Command Executes

AXSM

Syntax

clrchancnt 
<ifNum> 
<vpi> 
<vci>

Syntax Description

ifNum	The logical port number in the range 1-60.
vpi	The VPI in the range 1-4095.
vci	The VCI in the range 1-65535.

Related Commands

dspconcnt

Attributes

Log: Yes

State: Active

Privilege: GROUP_1-GROUP_3

node1.1.AXSM.a > clrchancnt 3 100 1000

clrallcnf

Clear All Configurations

Clear all configuration elements for all the cards in the node.

Caution Be absolutely sure you need to execute this command because it clears all configuration files on the PXM45. After clrallcnf, you need to reconfigure the switch.

Card(s) on Which This Command Executes

PXM45

Syntax

clrallcnf

Related Commands

None

Attributes

Log: Yes

State: Active

Privilege: GROUP_1-GROUP_3

node1.7.PXM.a > clrallcnf

clralmcnt

Clear Alarm Counters

Clear all the alarm counters and statistics on the specified line on the current card. All counters are reset to 0. The system does not display a response unless it detects a syntax error.

Card(s) on Which This Command Executes

AXSM

Syntax

clralmcnt 
<bay.line>

Syntax Description

node1.1.2.AXSM.a > clralmcnt -ds3 1

clrcdcnt

Clear Card Counters

Clears the counters for received and transmitted cells on the current card. See dspcdcnt for examples of the counter contents.

Card(s) on Which This Command Executes

AXSM

Syntax

clrcdcnt

This command takes no parameters.

clrerr

Clear Error

Clear all error log files. The cleared information consists of system-level or internal errors and so applies more to developers and individuals capable of internal troubleshooting. To see the information that clrerr removes, refer to the examples in the dsperr description.

Card(s) on Which This Command Executes

PXM45

Syntax

clrerr

Syntax Description

After you enter clrerr, the system prompts you to confirm that you want to clear all error log files.

Related Commands

dsperr

Attributes

Log: no

State: any

Privilege: ANYUSER

pinnacle.7.PXM.a > clrerr
Do you want to clear error log file (Yes/No)? 
 

clrilmicnt

Clear ILMI Counters

Clears the ILMI statistics for a partition and logical port on a service module.

Card(s) on Which This Command Executes

AXSM

Syntax

clrilmicnt <ifNum> <partId>

Syntax Description

ifNum	Logical port in the range 1-60.
partId	Number of the partition in the range 1-255.

Related Commands

dspilmicnt

Attributes

Log: no

State: any

Privilege: ANYUSER

wilco.1.AXSM.a > clrilmicnt

clrlog

Clear Log

Use the clrlog command to clear either specified or all event log files. The log resumes accumulating event messages after the command executes.

Card(s) on Which This Command Executes

PXM45

Syntax

clrlog [-log <log>]

Syntax Description

wilco.7.PXM.a > clrlog

clrportcnt

Clear Port Counters

Clear counter values on a specific logical port.

Card(s) on Which This Command Executes

AXSM

Syntax

clrportcnt <ifNum>

flyers01.17.AXSM.a > clrportcnt 1

clrscrn

Clear Screen

Use the clrscrn command to clear the control terminal screen. After this command executes, only the current command line prompt appears on the screen.

Card(s) on Which This Command Executes

PXM45, AXSM

Syntax

clrscrn

Related Commands

flyers01.11.AXSM.a > clrscrn
flyers01.11.AXSM.a > 
 

cmdhistory

Display Command History

View the last 10 commands executed on the current card. To execute one of the commands with associated parameters, type the associated number then press Enter or Return.

Card(s) on Which This Command Executes

PXM45, AXSM

Syntax

cmdhistory

Related Commands

history

Attributes

Log: no

State: any

Privilege: ANYUSER

pinnacle.7.PXM.a > cmdhistory
Size of cmdHistory is currently 5 line(s)
  1 dspcd
  2 clrscrn
  3 ?
  4 q
  5 cmdhistory

cnfalm

Configure Alarm

Configures statistical alarm thresholds for a line. The configurable items are defined in RFC 2258 for SONET and PLCP and in RFC 2496 for DS3 and E3. The items that constitute a configuration are:

• Line types: SONET, ds3, e3, and PLCP

• Tested layer: section, line, or path (for example, SONET line)

• Test periods of 15 minutes and 24 hours

• Degrees of error-time: errored seconds and severely errored seconds

• Types of errors, including framing errors, code violations, and unavailable

• Type of alarm triggered when a threshold is crossed: minor or major

In the Syntax Description section, a table for each line type contains basic information for each parameter.

The format of each command delineator identifies the criteria. It contains the tested layer (line, and so on), the type of threshold (errored seconds, code violations, and so on), and the test period of 15 minutes or 24 hours. For example, -lnes15 identifies the number of errored seconds on a line during any 15 minute period.

Card(s) on Which This Command Executes

AXSM

Syntax

The required parameters are the line type (SONET, and so on) the line identifier in the form bay.line, and the severity of the alarm (minor or major). All other parameters are optional and must be preceded by the command delineator that identifies the type of parameter.

Generic Syntax Description

The generic syntax is.

cnfalm 
<line type> 
<bay.line> 
<alarm severity> 
<thresholds>

The meaning of the generic syntax appears in the following list. Refer to subsequent lists for the parameter descriptions for each line type.

line type	The line type expressed as one of the following command delineators: -sonet, -sonetline, -sonetpath, -ds3, -e3, or -plcp. As the subsequent tables show for the non-SONET line types, the syntax distinguishes between line, path, and so on.
bay.line	The logical port number in the range 1-60.
alarm severity	A number to identify alarm severity: 1=minor, and 2=major.
thresholds	The number of instances of whatever the command delineator identifies. The range for each threshold is 1-2^32-1. The command delineator precedes each threshold. For example, -lnsesf15 10 means 10 instances of severely errored framing seconds on a line during a 15-minute period.

Thresholds for SONET Section

-secsev <Severity>	Severity of the alarm (1=minor, 2=major) for SONET section
-seces15 <ES15min>	Errored seconds during a 15-minute period.
-seces24 <ES24Hr>	Errored seconds during a 24-hour period.
-secses15 <SES15min>	Severely errored seconds during a 15-minute period.
-secses24 <SES24Hr>	Severely errored seconds during a 24-hour period.
-secsefs15 <SEFS15min>	Severely errored frame seconds during a 15-minute period.
-secsefs24 <SEFS24Hr>	Severely errored frame seconds during a 24-hour period.
-seccv15 <UAS15min>	Code violations during a 15-minute period.
-seccv24 <UAS24Hr>	Code violations during a 24-hour period.

Thresholds for SONET Line

-lnsev <Severity>	Severity of the alarm (1=minor, 2=major) for SONET line
-lnes15 <ES15min>	Errored seconds during a 15-minute period.
-lnes24 <ES24Hr>	Errored seconds during a 24-hour period.
-lnses15 <SES15min>	Severely errored seconds during a 15-minute period.
-lnses24 <SES24Hr>	Severely errored seconds during a 24-hour period.
-lncv15 <CV15min>	Code violations during a 15-minute period.
-lncv24 <CV24Hr>	Code violations seconds during a 24-hour period.
-lnuas15 <UAS15min>	Unavailable seconds during a 15-minute period.
-lnuas24 <UAS24Hr>	Unavailable seconds during a 24-hour period.

Thresholds for SONET Path

-sev	Severity of the alarm (1=minor, 2=major) for SONET path
-es15 <ES15min>	Errored seconds during a 15-minute period.
-es24 <ES24Hr>	Errored seconds during a 24-hour period.
-ses15 <SES15min>	Severely errored seconds during a 15-minute period.
-ses24 <SES24Hr>	Severely errored seconds during a 24-hour period.
-cv15 <CV15min>	Code violations during a 15-minute period.
-cvt24 <CV24Hr>	Code violations seconds during a 24-hour period.
-uas15 <UAS15min>	Unavailable seconds during a 15-minute period.
-uas24 <UAS24Hr>	Unavailable seconds during a 24-hour period.

Thresholds for DS3

-dsev <severity>	Severity of the alarm (1=minor, 2=major) for DS3.
-lcv15 <LCV15min>	Code violations for a line during a 15-minute period.
-lcv24 <LCV24Hr>	Code violations for a line seconds during a 24-hour period.
-les15 <LES15min>	Line errored seconds during a 15-minute period.
-les24 <LES24Hr>	Line errored seconds during a 24-hour period.
-pcv15 <PCV15min>	P-bit coding violations for a line during a 15-minute period.
-pcv24 <PCV24Hr>	P-bit coding violations for a line during a 24-hour period.
-pes15 <PES15min>	P-bit errored seconds during a 15-minute period.
-pes24 <PES24Hr>	P-bit errored seconds during a 24-hour period.
-pses15 <PSES15min>	P-bit severely errored seconds during a 15-minute period.
-pses24 <PSES24Hr>	P-bit severely errored seconds during a 24-hour period.
-sefs15 <SEFS15min>	Severely errored frame seconds during a 15-minute period.
-sefs24 <SEFS24Hr>	Severely errored frame seconds during a 24-hour period.
-uas15 <UAS15min>	Unavailable seconds during a 15-minute period.
-uas24 <UAS24Hr>	Unavailable seconds during a 24-hour period.

Thresholds for E3

-dsev <severity>	Severity of the alarm (1=minor, 2=major) for DS3.
-lcv15 <LCV15min>	Code violations for a line during a 15-minute period.
-lcv24 <LCV24Hr>	Code violations for a line seconds during a 24-hour period.
-les15 <LES15min>	Line errored seconds during a 15-minute period.
-les24 <LES24Hr>	Line errored seconds during a 24-hour period.
-sefs15 <SEFS15min>	Severely errored frame seconds during a 15-minute period.
-sefs24 <SEFS24Hr>	Severely errored frame seconds during a 24-hour period.
-duas15 <UAS15min>	Unavailable seconds during a 15-minute period.
-duast24 <UAS24Hr>	Unavailable seconds during a 24-hour period.

Thresholds for PLCP

-psev <severity>	Severity of the alarm (1=minor, 2=major) for PLCP.
-bcv15 <CV15min>	Bipolar violation code violations during a 15-minute period.
-bcv24 <CV24Hr>	Bipolar violation code violations during a 24-hour period.
-bes15 <ES15min>	Bipolar violation errored seconds during a 15-minute period.
-bes24 <ES24Hr>	Bipolar violation errored seconds during a 24-hour period.
-bses15 <SES15min>	Bipolar violation severely errored seconds during a 15-minute period.
-bses24 <SES24Hr>	Bipolar violation severely errored seconds during a 24-hour period.
-psefs15 <SEFS15min>	PLCP severely errored frame seconds during a 15-minute period.
-psefs24 <SEFS24Hr>	PLCP severely errored frame seconds during a 24-hour period.
-puas15 <UAS15min>	PLCP unavailable seconds during a 15-minute period.
-puas24<UAS24Hr>	PLCP unavailable seconds during a 24-hour period.

Related Commands

dspalmcnf

Attributes

Log: Yes

State: Active

Privilege: SUPER_GP

node4.1.AXSM.a > dspalmcnf -sonetline 1.2
  LineNum: 1.2
  Line Stat Alarm Severity: No Alarm
               15min Threshold    24hr Threshold
  Line  ESs :  60                 600
  Line  SESs:  3                  7
  Line  CVs :  75                 750
  Line  UASs:  10                 10 
 

node4.1.AXSM.a > dspalmcnf -sonetsec 1.1
  LineNum: 1.1
  Section Stat Alarm Severity: No Alarm
                   15min Threshold    24hr Threshold
  Section ESs  :   60                 600
  Section SESs :   3                  7
  Section SEFSs:   3                  7
  Section CVs  :   75                 750 

cnfatmln

Configure ATM Line

Configures the ATM layer cell header for a line. Execute cnfatmln before you:

• Activate the lines on the card by executing upln.

• Add logical ports by executing addport.

Card(s) on Which This Command Executes

AXSM

Syntax

cnfatmln 
-ln <bay.line> 
-sps <PayloadScramble> 
-nch <cellhdr> 
-ncp <cellpayload> 
-hcs <hcs>

Syntax Description

bay.line	Identifies the bay (1 or 2) and the number of the line. The line number can be from 1 to the highest numbered line on the back card. For the line number ranges on an AXSM model, see Table 3-1.
PayloadScramble	A number that enables (1) or disables (2) payload scrambling. The default is enabled
cellhdr	A four-byte hexadecimal number to serve as the null cell header. The range is all 0s through ffffffff.
cellpayload	A hexadecimal byte to serve as the null cell header. The range is 1-ff. The default is 6a.
hcs	A number to disable (1) or enable (2) HCS coset The default is enabled.

Related Commands

dspatmln

Attributes

Log: no

State: any

Privilege: ANYUSER

local1.7.AXSM.a > cnfatmln -ln 1.1 -sps 2 -nch ab12abab
remote2.1.AXSM.a > cnfatmln -ln 1.1 -sps 1 -nch 1a1a1a1a -ncp aa 

cnfcdsct

Configure Port SCT

Assign a service class template (SCT) to logical ports. The template contains bandwidth and policing parameters for the ingress direction of the AXSM port. The following characteristics apply to cnfcdsct.

• A valid SCT file must exist on the PXM45 disk before you execute cnfcdsct.

• The system uses a default ingress SCT file (ID=0) when:

  • The AXSM is powered-up for the first time.

  • The card's database is rebuilt.

  • The card is rebooted and the user-specified SCT file for a particular port is corrupt or missing. In this situation, the default applies to only the affected port.

• To replace the default SCT file, use cnfcdsct to assign another file.

• You must execute cnfcdsct before adding or configuring resource partitions.

• The cnfcdsct command is a card-level command, so the ingress SCT file contents apply to all logical ports on the card.

To modify the template contents, you must use the Cisco WAN Manager application. To see the number of the current SCT, use dspport. To see the bandwidth parameters in the template (and therefore all ports in the ingress direction), use dspportsct. Note that if the default template is in effect, the display contains the message " !Default SCT used!."

Card(s) on Which This Command Executes

AXSM

Syntax

cnfcdsct 
<SCT-id> 

Syntax Description

cnfcon

Configure Connection

Modifies the connection bandwidth, policing, and routing parameters of an existing endpoint at the master endpoint. (Modifying bandwidth parameters on the slave endpoint has no effect.)

The command parameters consist of:

• A logical port, VPI, and VCI to identify the connection

• Bandwidth parameters for the local (master) end then the remote (slave) end

• Policing parameters for the connection as a whole

Note that after you specify the mandatory connection identifier, all other parameters are optional.

Card(s) on Which the Command Executes

AXSM

Syntax

cnfcon 
<ifNum> 
<vpi> 
<vci> 
[-lpcr <local PCR >] 
[-lmcr <local MCR>] 
[-lscr <local SCR>]
[-lmbs <local MBS> 
[-lcdvt <local CDVT>] 
[-lcdv <local maxCDV>] 
[-lctd <local maxCTD>]
[-rpcr <remote PCR>] 
[-rmcr <remote MCR>] 
[-rscr <remote SCR>] 
[-rmbs <remote MBS>]
[-rcdvt <remote CDVT>] 
[-rcdv <remote maxCDV>] 
[-rctd <remote maxCTD>] 
[-cc <OAM CC Cnfg>] 
[-stat <Stats Cnfg>] 
[-frame <Frame Discard>] 
[-aw <Administrative Weight>]

Syntax Description

ifNum	Logical port number. On the AXSM, the range is 1-60.
vpi	Virtual path identifier (VPI) value, in the range 1-255.
vci	Virtual connection identifier (VCI): For a VCC, the range is 32-65535. For a VPC, the vci is 0.
local PCR	(Optional) Local-to-remote peak cell rate (PCR). The range is 3-5651328 cells per second (cps).
local SCR	(Optional) Local-to-remote sustained cell rate (SCR). The range is 3-5651328 cells per second (cps).
local MBS	(Optional) Local-to-remote maximum burst size (MBS). The range is 1-5000000 cells.
local CDVT	(Optional) Local-to-remote, cell delay variation tolerance (CDVT). The range is 1-5000000 microseconds.
local maxCDV	(Optional) Local-to-remote, maximum cell delay variation (CDV). The range is 1-16777215 microseconds.
local maxCTD	(Optional) Local-to-remote maximum CTD. The range is 1-65535 milliseconds.
remote PCR	(Optional) Remote-to-local PCR. The range is 3-5651328 cps.
remote SCR	(Optional) Remote-to-local SCR. The range is 3-5651328 cps.
remote MBS	(Optional) Remote-to-local MBS. The range is 1-5000000 cells.
remote CDVT	(Optional) Remote-to-local CDVT. The range is 1-5000000 microseconds.
remote maxCDV	(Optional) Remote-to-local maximum CDV. The range is 1-16777215 microseconds.
remote maxCTD	(Optional) Remote-to-local maximum CTD. The range is 1-65535 milliseconds.
OAM CC	(Optional) OAM CC: Enter 1 to enable or 0 to disable. The default is 0.
Stats Cnfg	(Optional) Statistics collection: enter 1 to enable or 0 to disable. The default is 0.
frame	Frame discard: Enter a 1 to enable or a 0 to disable. The default is 0.
AW	(Optional) Administrative Weight (AW): a value that creates a routing priority. The range for AW is 0-2147483647. If you do not specify this optional parameter, the connection defaults to having the highest priority. You can impose a routing priority on a connection through the AW parameter and a cost-per-link specified through the cnfpnni-intf command. The PXM45 does not use a route if the cost for the route exceeds the AW. The cost of a route is the product of multiplying the cost-per-link times the number of links in a route. (Therefore, the routing priority is directly proportional to AW.) Note that the cost-per-link specification applies to all connections of a particular service type under control of PNNI. For example, cost-per-link is the same for all VBR.1 connections that PNNI controls. To illustrate: 1. If you specify an AW of 30000. 2. The cost-per-link for a service type is 5040 (the default for cnfpnni-intf). 3. The route under consideration by the PXM45 has 4 links. The PXM45 would use the route because the resulting cost of 20160 is less than the AW of 30000. Note that you can specify "no limit" for a service type by entering a cost-per-link of -1 through cnfpnni-intf. A -1 cost-per-link makes AW meaningless.

Related Commands

addcon, delcon, dspcon, dspcons, dspconstats

Attributes

Log: no

State: any

Privilege: ANYUSER

pinnacle.1.AXSM.a > cnfcon 16 1 5 2 65525 65525 100

cnfclksrc

Configure Clock Source

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

• An external device that connects to the PXM-UI S3 card.

• A line on an active AXSM. In this case, the prerequisite tasks are

  • Activating the applicable line through upln

  • Creating logical ports (subports) through addport

  • Creating resource partitions through addrscprtn

Currently, a typical configuration for synchronization in an MGX 8850 network uses a Building Integrated Timing System (BITS) clock source of stratum 3 or higher on one node and subsequent propagation of that clock through AXSMs to the other nodes. Thus, the node with the BITS clock becomes the master clock source. At the other nodes, you specify primary and secondary clocks derived from selected AXSMs. The examples in this description illustrate this scheme.

At each node, the current clock source drives the clock line on the backplane, and all devices on the backplane take the clock from this line. Note that another level of clock configuration exists for a physical line. The applicable command is cnfln and is significant only if you want to switch between a normal clock--which comes from the backplane as just described--and a looped clock. With looped timing, a clock arrives on the specified receive line of a back card and is redirected to become the transmit clock for that line. See the cnfln description.

When the switch first powers up, the internal oscillator on the PXM45 is the clock source. If both of the user-configured clock sources fail, the source reverts to this stratum 3, internal clock. This source is not available for you to configure or view, but you can see if the switch is using it by executing dspclksrcs.

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.

Card(s) on Which This Command Executes

PXM45

Syntax

The syntax for cnfclksrc varies according to the clock source:

For BITS clock:

cnfclksrc 
<priority> 
<portid> 

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

cnfclksrc 
<priority> 
<portid> 

Usage Guidelines

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:

• A switch can have one primary source and one secondary source.

• For each execution of cnfclksrc, you can specify only one clock source (either but not both primary and secondary). Therefore, you must repeat cnfclksrc to specify the other clock source.

• You do not need to specify both a primary and a secondary source. If you choose not to specify a particular source, the internal clock is the source for that priority of clock. Thus, you can specify a primary source but no secondary source, in which case the internal clock becomes the secondary.

• Cisco recommends that clock sources configured for AXSMs be on separate cards or at least on separate lines.

• When the primary BITS clock is restored on the master clock node, you must reconfigure the primary clock through cnfclksrc at each remote node where the source has switched from the primary source to the secondary source. This situation is not typical.

• The revertive option can be specified whether you are configuring the primary clock or the secondary clock. However, the revertive option is available for only a BITS clock. For more details on the revertive option, see the section, "Configuring a BITS Clock."

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:

• To change the priority of a clock from primary to secondary or secondary to primary, you must first execute delclksrc to deconfigure each source.

• To change from one primary source to another primary source, you need to execute only cnfclksrc for the new primary source--the system automatically deconfigures the existing primary source.

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 a dedicated, external devices. It 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 that if the secondary BITS clock source fails while the network is using the primary source, the internal clock becomes the secondary source. This event triggers a major alarm on the local node.

With the current BITS scheme on the MGX 8850 node, you can enable a revertive function for the primary clock source. The revertive mode pertains to the restoration of a failed primary clock. (A failure is either the loss of the signal or a clock that has drifted out of spec for its stratum.) 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 functioning 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."

The switch constantly monitors the state of the clocks. For information on clock alarms, see the dspclkalms description.

Related Commands

dspclksrcs, delclksrc, dspclkalms

Attributes

Log: Yes

State: Active

Privilege: GROUP_2

Examples

pinnacle.7.PXM.a> cnfclksrc primary 7.35 -bits e1
pinnacle.7.PXM.a> cnfclksrc secondary 3:1.1:10

pinnacle.7.PXM.a> cnfclksrc primary 7.36 -bits e1 -revertive enable

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 This Command Executes

PXM45

Syntax

cnfdate 
<mm/dd/yyyy>

Syntax Description

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

cnfilmi

Configure ILMI

Configure the interim local management interface (ILMI) for a particular resource partition on a logical port. Note that you must activate ILMI by executing upilmi before using cnfilmi. No response appears unless an error occurs.

Card(s) on Which This Command Executes

AXSM

Syntax

cnfilmi <ifNum> 
-id <partitionID> 
-ilmi <ilmiEnable> 
-vpi <vpi> 
-vci <vci> 
-trap <ilmiTrapEnable> 
-s <keepAliveInt> 
-t <pollingIntervalT491> 
-k <pollInctFact>

Syntax Description

cnfln

Configure Line

Configures characteristics for a line on the current card. Use cnfln after the line becomes active. On the CLI, activate a line by executing upln.

Card(s) on Which This Command Executes

AXSM

cnfln -ds3 <bay.line> -lc <LineCoding> -len <LineLength> -oof <LineOOFCriteria> -lt <LineType> -cb <LineAIScBitsCheck> -rfeac <LineRcvFEACValidation> -clk <clockSource> -lpb <Loopback>

bay.line	Identifies the bay (1 or 2) and the number of the line. The line number can be from 1 to the highest numbered line on the back card. For the line number ranges on an AXSM model, see Table 3-1.
LineCoding	The choice of line coding: 2=B3ZS 3=HDB3
LineLength	The length of the line in the range 0-64000 meters.
LineOOFCriteria	A number that specifies the occurrences of out of frame detections required to declare Out of Frame error: 1=3 out of 8: An Out Of Frame condition is declared if at least 3 of 8 framing bits are in error. 2=3 out of 16:An Out Of Frame condition is declared if at least 3 of 16 framing bits are in error.
LineType	A number that specifies the type of ds3 line: 1=ds3cbitadm 2=ds3cbitplcp 3=e3g832adm
LineAIScBitsCheck	A number that specifies whether to process the AIS check bit. Enter a 1 to check the C-bit or a 2 to ignore the C-bit.
LineRcvFEACValidation	A number that specifies the criteria setting for FEAC (far-end alarm and control) code validation. Type a 1 to specify that a FEAC code is declared if 4 out of 5 codes match. The default is 1. Type a 2 to specify that a FEAC code is declared if 8 out of 10 codes match.
clockSource	A number that identifies the transmit clock source for the line. 1=loop timing, where the clock signals received off the line are redirected to become the transmit clock. 2=local timing, where the clock from the backplane becomes the transmit clock.
Loopback	Loopback --1: NoLoop 2: PayloadLoop 3: RemoteLoop 5: LocalLoop

Syntax: (T3)

cnfln -ds3 <LineNum> -lc <LineCoding> -len <LineLength> -oof <LineOOFCriteria>
-cb <LineAIScBitsCheck> -lpb <LoopCmd> -rfeac <LineRcvFEACValidation>

Syntax Description

bay.line	Identifies the bay (1 or 2) and the number of the line to configure. The line number is from 1 to the highest numbered line on the back card. For the range of line numbers on specific AXSM models, see Table 3-1.
-ds3	Command delineator that precedes the LineNum entry.
LineNum	DS3 line number in the format slot.port. slot=enter the value 7, 15, or 31. Values 8, 16, and 32 are acceptable if PXM45 in slot 8 is active. port range=1-n, as needed for the physical installation.
-lc	Command delineator that precedes LineCoding value.
LineCoding	Value to set line coding for Zero Code Suppression B3ZS or HDB3. 1=B3ZS on a dsx3 line 2=HDB3 on an E3 line
-len	Command delineator that precedes the LineLength entry.
LineLength	Value to set number of line feet. 1=less than 225 feet 2=225 feet or more
-oof	Command delineator that precedes the LineOOFCriteria entry.
LineOOFCriteria	Value to set threshold for triggering an Out Of Frame condition. 1=3 out of 8 An Out Of Frame condition is declared if at least 3 of 8 framing bits are in error. 2=3 out of 16 An Out Of Frame condition is declared if at least 3 of 16 framing bits are in error.
-cb	Command delineator that precedes the LineAIScBitsCheck entry.
LineAIScBitsCheck	Value to set test of the c-bit in response to AIS status. 1=check the C-bit 2=ignore the C-bit
-lpb	Command delineator that precedes the LoopCmd entry.
LoopCmd	Loopback configuration of the DS3/E3 interface. dsx3NoLoop Not in the loopback state. A device that is not capable of performing a loopback on the interface shall always return this as its value. dsx3RemoteLineLoop Near end loops back remote data dsx3LocalLineLoop Near end loops back local data (outbound) dsx3InboundLoopback Near end in bound loopback local data (inbound)
-rfeac	Command delineator that precedes the LineRcvFEACValidation entry.
LineRcvFEACValidation	Value to set FEAC (far-end alarm and control) code validation criteria. 1=4 out of 5 A valid FEAC code is declared if 4 of 5 codes match. 2=8 out of 10 A valid FEAC code is declared when 8 of 10 codes match.

Syntax: (E3)

cnfln -e3 <bay.line> -lt <LineType> -lc <LineCoding> -len <LineLength> -lpb <LoopCmd> -clk <clockSource>

bay.line	Identifies the bay (1 or 2) and the number of the line to configure. The line number is from 1 to the highest numbered line on the back card. For the range of line numbers on specific AXSM models, see Table 3-1.
LineType	A number that identifies the type of E3 line: 1=ds3cbitadm 2=ds3cbitplcp 3=e3g832adm
LineCoding	A number that identifies the type of line coding: 2=B3ZS 3=HDB3
LineLength	The length of the line in the range 0-64000 meters.
LoopCmd	A number that identifies the type of loopback: 1=no loop. This choice just removes the current loop configuration for the command. 2=payload loopback. 3=remote loopback. 5=local loopback.
clockSource	Determines the method of clock sourcing if this line has been selected as a transmit clock source. 1=loop timing, where the clock signals received off the line are redirected to become the transmit clock. 2=local timing, where the clock from the backplane becomes the transmit clock.

Syntax: (SONET)

cnfln -sonet <bay.line> -slt <LineType> -sfs <FrameScramble> -lpb <Loopback> -clk <clockSource>

bay.line	Identifies the bay (1 or 2) and the number of the line to configure. The line number is from 1 to the highest numbered line on the back card. For the range of line numbers on specific AXSM models, see Table 3-1.
LineType	A number that identifies the type of SONET line 1=sonetSts3c 2=sonetStm1 3=sonetSts12c 4=sonetStm4 5=sonetSts48c 6=sonetSTM16
FrameScramble	Enables frame scrambling. 1=disable 2=enable
Loopback	Specifies a loopback state for the line: 1=no loopback. The purpose of this choice is to take the line out of loopback. 2=Put the line in local loopback. 3=Put the line in remote loopback. RemoteLoop
clockSource	Determines the method of clock sourcing if this line has been selected as a transmit clock source. 1=loop timing, where the clock signals received off the line are redirected to become the transmit clock. 2=local timing, where the clock from the backplane becomes the transmit clock.

Related Commands

delln, dsplns, dspln, upln

Attributes

Log: Yes

State: Active

Privilege: GROUP1

wilco.1.4.AXSM.a > cnfln -ds3 4 2 10 1

wilco.1.4.AXSM.a > cnfln -sonet 1.1 -sfs 2

cnfname

Configure Name

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

• Up to 32 letters or numbers

• Two special characters ("_" and "-")

• No spaces

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 resulting display.

Card(s) on Which This Command Executes

PXM45

Syntax

cnfname 
<node name>

Syntax Description

NODENAME.7.PXM.a > cnfname pinnacle_7
pinnacle.3.PXM.a >

cnfpasswd

Configure Password

Creates a password for a user. To change your own password, enter cnfpasswd with no arguments.

---

Note   The default password is newuser.

---

Card(s) on Which This Command Executes

PXM45

Syntax

cnfpasswd 
[<user_id>] 

Syntax Description

user_id

User name.

Related Commands

adduser, dspusers

Attributes

Log: Yes

State: Active

Privilege: ANYUSER

Example 3-33: Change your own password.

pinnacle.8.PXM.a > cnfpasswd
 
Enter password:
Re-enter password:

cnfport

Configure Port

Configures a logical port on a service module. The system does not display a confirmation upon successful execution, so use dspport to check the changes.

Note   You cannot configure parameters for a logical port if any resource partitions have been configured for the interface.

Card(s) on Which This Command Executes

AXSM

Syntax

cnfport 
-if <ifNum> 
[-min <guaranteedRate>] 
[-max <maxrate>] 
[-sct <sctID>]

Syntax Description

Note that this command uses the keyword (or command delineator) to identify the parameter that follows it. After you identify the logical port with the ifNum parameter, each of the remaining parameters is optional.

ifNum	A logical port (interface) number in the range 1-60. Although the range of port numbers is 1-60, only 1 port is allowed if the line operates as a UNI. When the interface supports more than one port, the typical maximum number of ports is 3.
guaranteedRate	Guaranteed rate on a logical port in cells/second. The cumulative guaranteed rate cannot exceed the highest value in the following ranges: OC48: 50-5651328 cps OC12: 50-1412832 cps OC3: 50-353208 cps T3: 50-96000 (PLCP) or 104268 (ADM) cps E3: 50-80000 cps
maxRate	Maximum rate on a logical port in cells/second. OC48: 50-5651328 cps OC12: 50-1412832 cps OC3: 50-353208 cps T3: 50-96000 (PLCP) or 104268 (ADM) cps E3: 50-80000 cps
sctID	The numeric ID of the service class template (SCT) for the egress direction. To see the ID of the current SCT for this port, use dspport.

Related Commands

addport, delport, dspport, dspports

Attributes

Log: Yes

State: Active

Privilege: ANYUSER

pinnacle3.1.6.AXSM.a > cnfport -if 1 -min 10000 max 20000

cnfrscprtn

Configure Resource Partition

Modifies a resource partition. A resource partition on an AXSM consists of minimum and maximum percentages of bandwidth, a VPI/VCI range, and a minimum and maximum number of connections available to a network control application. The current network controller is PNNI. Refer to the description of addrscprtn for information on resource partitions.

Card(s) on Which This Command Executes

AXSM

Syntax

cnfrscprtn 
-if <if> 
-id <partionID> 
-ctlr <controllerID> 
-emin <egrMinBw> 
-emax <egrMaxBw> 
-imin <ingMinBw> 
-imax <ingMaxBw> 
-vpmin <minVpi> 
-vpmax <maxVpi> 
-vcmin <minVci> 
-vcmax <maxVci> 
-mincon <min connections> 
-maxcon <max connections>

Syntax Description

if	Logical interface number, in the range 1-60.
partionID	The number of the partition in the range 1-250.
controllerID	The number of the controller in the range 1-20.
egrMinBw	A minimum percentage of the egress bandwidth, where each increment of egrMinBw is 0.00001 of the total bandwidth on the port. For example, an egrMinBw of 1000000=100%.
egrMaxBw	A maximum percentage of the bandwidth, where each increment of egrMaxBw is 0.00001 of the total bandwidth on the port. For example, an egrMaxBw of 1000000=100%.
ingMinBw	A minimum percentage of the ingress bandwidth, where each increment of ingMinBw is 0.00001 of the total bandwidth on the port. For example, an ingMinBw of 1000000=100%
ingMaxBw	A maximum percentage of the ingress bandwidth, where each increment of ingMaxBw is 0.00001 of the total bandwidth on the port. For example, an ingMaxBw of 1000000=100%
minVpi	Minimum VPI in the range 0-4095.
maxVpi	Maximum VPI in the range 0-4095. maxVpi cannot be less than minVpi.
minVci	Minimum VCI in the range 0-65535.
maxVci	Maximum VCI in the range 0-65535.
minconns	A guaranteed minimum number of connections. The range is between 0 and the maximum number of connections in the port group. See dspcd port group information.
maxconns	A guaranteed minimum number of connections. The range is between 0 and the maximum number of connections in the port group. See dspcd port group information. maxConns cannot be less than minConns.

Related Commands

addrscprtn, delrscprtn, dspifs, dsprscprtns, dsprscprtn

Attributes

Log: Yes

State: any

Privilege: SERVICE_GP

MGX-01.1.2.PXM.a > cnfrscprtn 1 2 2 100000 150000 10000 15000 20 100 1 32767 1000 2000

cnfrteopt

Configure Route Optimization

Configure route optimization to improve bandwidth utilization. This type of optimization is also known as connection grooming. To automate route optimization, cnfrteopt lets you specify an interval between new optimization cycles--every 2 hours, for example. (To force immediate route optimization, use the optrte command.)

You can specify a time period for optimization to minimize any disruption. (For example, you could specify that the switch starts grooming a range of SPVCs for one hour at midnight.) Note, however, that route optimization is a background process and does not attempt to optimize all possible connections at once. The load created by route optimization is extremely small and cannot cause congestion.

The nature of SPVCs provides a reason for periodic grooming: during the course of daily operation, better routes may become available. The determining factor for a better route is the administrative weight (AW). See the addcon description for the AW parameter for details.

Command Usage

Note the following characteristics of route optimization:

• Within a range of connections, the cnfrteopt command applies to only the master endpoints. The slave endpoints are unaffected by cnfrteopt.

• An existing connection must already have a route because the PXM45 needs an existing route to compare to a potential route.

By default, the PXM45 calculates that a route is better if its routing cost is 30% less than the current cost. You can change this cost threshold through the cnfrteoptthld command.

The following briefly characterizes the defaults for cnfrteopt:

• The default state is disabled, so you would not start optimization unless you enable it.

• If you do not specify a range, all connections on the port are subject to optimization.

• If you not specify an interval, optimization begins every 60 minutes.

• If you do not specify a time of day, the default is any time during the day (but still subject to the interval of minutes between optimization commencement.

Syntax

cnfrteopt 
<portid> 
[{enable | disable}] 
[-range <starting-vpi/vci..ending-vpi/vci>] 
[-interval <interval>] 
[-tod <start-time..end-time>]

Syntax Description

cnfrteopt 1:2.1:2 enable -range 100/1000..100/10000 -interval 60 -tod 01:00..03:00

cnfspvclog

Configure SPVC Log

Enable or disable the SPVC log.

Cards on Which This Command Executes

PXM45

Syntax

cnfspvclog 
<enable | disable>

Syntax Description

Unknown.8.PXM.a > cnfspvclog enable
 

cnfrteoptthld

Configure Route Optimization Threshold

Configure a threshold the system uses to decide whether one route is a sufficient improvement to warrant re-routing. The criterion for selecting a new route is the percent of difference in route cost. The default for route optimization is a 30% reduction of the cost of a route. Using this scheme, the PXM45 selects a given route if it costs 30% less than the cost of the current route. With cnfrteoptthld, you can change the percentage of routing cost improvement.

Syntax

cnfrteoptthld 
<percent>

Syntax Description

percent

The percent of reduction in routing cost that triggers re-routing. The range is 5-100. The default is 30.

Cards on Which This Command Executes

PXM45

Related Commands

cnfrteopt, optrte, dsprteoptcnf, dsprteoptstat

Attributes

Log: Yes

State: Active

Privilege: GROUP_2

Example

pinnacle.7.PXM>cnfrteoptthld 20

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 string ro | rw	This parameter 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 string	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 string	This parameter is text that describes 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: Yes

State: Active

Privilege: SUPER_GP

Related Commands

dspsnmp

Example

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
 

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

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 This Command Executes

PXM45

Syntax

cnftime 
<hh:mm:ss>

Syntax Description

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 This Command Executes

PXM45

Syntax

cnftmzn 
<timezone>

Syntax Description

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:

• First use cnftmzn to specify the timezone as GMT.

• Then specify an offset in hours relative to Greenwich Mean Time by executing cnftmzngmt. The values are GMT plus or minus an integer in the range 1-12.

Use dspdate to see the time.

Card(s) on Which This Command Executes

PXM45

Syntax

cnftmzngmt 
<timeoffsetGMT>

Syntax Description

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 the userID parameter creates that user. If you do not specify user name (userID) a but include one or more of the other parameters, the command applies to whomever is the current user.

Card(s) on Which This Command Executes

PXM45

Syntax

cnfuser 
-u <userID> 
[-p <password>] 
[-l <accessLevel>]

Syntax Description

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

commitrev

Commit Revision

Completes a graceful upgrade by committing to the operational firmware image as the primary version. The commitrev command is the necessary conclusion to a graceful upgrade.

The impact of commitrev is:

• It signifies that the primary firmware image activated through the runrev command is acceptable.

• The previous image is removed from the card's main memory (but continues to reside on disk).

• Starting another graceful revision change becomes possible. If you attempt loadrev on the same card before you execute commitrev, the system blocks loadrev and states that a revision change is in progress.

• You cannot use abortrev to revert to the previous image. To bring a previous image into memory and run it, you must use setrev to force-load the image (a non-graceful revision change).

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 resurrected database has no information about the topology change.

The order of commands in a graceful upgrade, including the option of aborting the revision change, is:

1. loadrev loads a firmware version from the hard disk to a card's memory as the new primary version.

2. runrev causes the standby card to become the active card and start running the new version. At this point, the card that was active and is now standby begins to receive the new firmware version. In this way, it is ready with the new firmware in case the active card fails.

3. If an unacceptable problem occurs, the optional abortrev restores the previous primary 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).

Card(s) on Which This Command Executes

PXM45

Syntax

commitrev 
<slot> 
<revision>

Syntax Description

slot	Number of the targeted card slot.
revision	Revision number derived from the firmware filename. For an explanation of the numbering scheme for firmware versions, see the section, "Version Numbering Conventions," in the loadrev description.

Related Commands

abortrev, loadrev, runrev, setrev

Attributes

Log: Yes

State: Active

Privilege: SUPER_GP

excel.8.PXM.a > commitrev 8 2.0(4)

copy

Copy

Use the copy command to replicate the selected firmware file into the PXM45.

Card(s) on Which This Command Executes

PXM45

Syntax

copy 
<fw_load>

Syntax Description

fw_load

Firmware file name.

Related Commands

cd, ls, rm, pwd, rename

Attributes

Log:Yes

State:Any

Privilege: SERVICE_GP

pinnacle.8.PXM.a > copy pxm_1.0.00Ef.fw
pinnacle.8.PXM.a > 

cp

Copy

Copies a firmware file into the PXM45.

Card(s) on Which This Command Executes

PXM45

Syntax

copy 
<fw_load>

Syntax Description

fw_load

Firmware file name.

Related Commands

abort, commit, copy

Attributes

Log: no

State: any

Privilege: ANYUSER

pinnacle.8.PXM.a > copy pxm_1.0.00Ef.fw
pinnacle.8.PXM.a > 

del

Delete

Use the del command to remove a file or directory from the PXM45 hard drive.

Card(s) on Which This Command Executes

PXM45

Syntax

del 
<path_name>

Syntax Description

path_name

Name of an existing file or directory.

Related Commands

None

Attributes

Log: Yes

State: any

Privilege: SERVICE_GP

delcon

Delete Connection

Use the delcon command to delete a connection. After you finish this command, no messages appear on-screen unless the command cannot execute as entered.

Card(s) on Which This Command Executes

AXSM

Syntax

delcon 
<connection number> 

Syntax Description

delcons

Delete Connections

Delete a range of ATM connections.

Card(s) on Which This Command Executes

AXSM

Syntax

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

Syntax Description

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 the delclksrc command.

When you execute delclksrc, include all the parameters that appear in the Syntax section of this description. For example, if you are deleting a BITS clock configuration, your specification must include the priority in addition to the keyword -revertive and "disable."

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. Executing delclksrc is a configuration change, so internal status updates would also go to the standby PXM45.

Card(s) on Which This Command Executes

PXM45

Syntax

delclksrc 
<priority> 
<portid>
[-bits <e1 | t1>]
[-revertive <enable | disable>]

where portid has the following format:

pinnacle.7.PXM.a> delclksrc primary 7.36 -bits e1 -revertive disable

delcontroller

Delete Controller

Delete a controller. The delcontroller command does not erase the controller software but directs the switch not to use it.

Card(s) on Which This Command Executes

PXM45

Syntax

delcontroller 
<cntrlrId>

Syntax Description

pinnacle1.8.PXM.a > delcontroller 3

delln

Delete Line

Use the delln command to remove a line from the current card.

Card(s) on Which This Command Executes

AXSM

Syntax

delln 
<-ds3 | -e3 | -sonet> 
<bay.line>

Syntax Description

pinnacle1.8.AXSM.a > delln 4

dellnloop

Delete Line Loop

Use the dellnloop command to remove a line loopback state for the current card.

Card(s) on Which This Command Executes

AXSM

Syntax

dellnloop 
<-ds3 | -e3 | -sonet> <line number>

Syntax Description

delport

Delete Port

Remove a logical port from a service module. Note that you must delete all connections and resource partitions on a port before you delete it.

Card(s) on Which This Command Executes

AXSM

Syntax

delport 
<ifNum>

Syntax Description

delrscprtn

Delete Resource Partition

Delete a resource partition. Note that you must delete all connections in the resource partition before you delete it. For information on resource partitions, refer to the description of addrscprtn.

Card(s) on Which This Command Executes

AXSM

Syntax

delrscprtn 
<if_num> 
<part_id>

Syntax Description

if_num	Logical port number. On the AXSM, the range 1-60.
part_id	The partition id number in the range 1-20. Use dsprscprtns to see all resource partitions if necessary.

Related Commands

addrscprtn, dsprscprtns

Attributes

Log: no

State: any State

Privilege: ANYUSER

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 additional information about trap managers, see the Cisco MGX 8850 Switch Software Configuration Guide or the addtrapmgr description in this book.

Card(s) on Which This Command Executes

PXM45

Syntax

deltrapmgr 
<ip_addr> 

Syntax Description

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 This Command Executes

PXM45

Syntax

deluser 
<user ID>

Syntax Description

dncon

Down Connection

Temporarily deactivates (or "downs") so you can modify or troubleshoot it. This operation applies to only an SVC. To reactivate the connection, use upcon.

Card(s) on Which This Command Executes

AXSM

Syntax

dncon 
<ifNum> 
<vpi> 
<vci>

Syntax Description

ifNum	The logical port (or logical interface) number. On the AXSM, the range is 1-60.
vpi	Virtual path identifier in the range 1-255.
vci	For a virtual connection (VCC), the VCI range is 0-65535. For a virtual path connection (VPC), the VCI is always 0.

Related Commands

upcon

Attributes

Log: no

State: Active

Privilege: GROUP_2

dnln

Down Line

De-activate a line on the current card. Before you can de-activate a line by using dnln, the tasks in the following order are necessary:

Step 2   Remove any resource partitions. Use dsprscprtn to see existing partitions and delrscprtn to remove partitions.

Step 3   Remove all logical ports. Use dspports to see existing logical ports on the line and delport to remove logical ports.

Card(s) on Which This Command Executes

AXSM

Syntax

dnln 
<-ds3 | -e3 | -sonet> <bay.line>b

Syntax Description

bay.line

Identifies the bay (1 or 2) and the number of the line. The line number is from 1 to the highest numbered line on the back card. For the range of line numbers on specific AXSM models, see Table 3-1.

Related Commands

dspln, dsplns, cnfln, upln

Attributes

Log: no

State: any

Privilege: ANYUSER

chicago.1.AXSM.a > dnln 1.1

downloadflash

Download the Flash

Use the downloadflash command to load the first boot code found by the PXM45 hard drive into flash memory. A downloadflash session concludes the sequence of tasks for performing a PXM45 boot code load. Prior to executing the this command, you must access the boot code, transfer the file to the PXM45 hard drive by using a "put" command). Using arguments with the "put" command enables boot code load to both the standby and active PXM45, or to the active PXM45 only, or to the standby PXM45 only. Details are provided in the example section.

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.

Once firmware is installed in slot 7, the firmware file is mirrored to a PXM45 subsequently installed in slot 8. However, to ensure that the boot code is correct, use the downloadflash command to manually download the boot code onto the standby PXM45.

Card(s) on Which This Command Executes

PXM45

Syntax

downloadflash

Related Commands

None

Attributes

Log: no

State: any

Privilege: SUPER_GP

> tftp <switch_dest_addr>
> bin
> put <pxm_bkup_version>.fw PINNACLE@PXM45.BT
>quit
wilco.7.PXM.a > downloadflash

Note   Despite the potentially deceptive ".fw" argument in the command string, this is NOT a firmware load.

• To place the boot code on the active PXM45 only, use the following "put" string:
  >put pxm_bkup_version>.fw PINNACLE@PXM45_ACTIVE.BT

• To place the boot code on the standby PXM45 only, use the following "put" string:
  >put pxm_bkup_version>.fw PINNACLE@PXM45_STANDBY.BT

dspalm

Display Alarms for a Line

Use the dspalm command to view the alarms associated with a specified line.

This command requires a command delineator to identify the line type

Card(s) on Which This Command Executes

AXSM

Syntax

dspalm 
-sonet <bay.line> | -ds3 <bay.line> | -e3 <bay.line> | -plcp <bay.line>

Syntax Description

node19.1.AXSM.a > dspalm -sonet 1.1
 Line Number             : 1.1
 Section Alarm State     : Clear
 Line Alarm State        : Clear
 Path Alarm State        : Clear
 Section Stat Alarm State: No Alarm
 Line Stat Alarm State   : No Alarm
 Path Stat Alarm State   : No Alarm 
 

dspalmcnf

Display Alarm Configuration

Display the threshold information about the alarm statistics being collected. Refer to the cnfalm description for details regarding alarm threshold configuration.

Card(s) on Which This Command Executes

AXSM

Syntax

dspalmcnf 
-sonetsec <bay.line> | -sonetline <bay.line> | -sonetpath <bay.line> | -ds3 <bay.line> | -e3 <bay.line> | -plcp <bay.line>

Syntax Description

pinnacle.10.AXSM.a > dspalmcnf -sonetline 1.1
  LineNum: 1.1
  Line Stat Alarm Severity: Minor
               15min Threshold    24hr Threshold
  Line  ESs :  20                 20
  Line  SESs:  3                  3
  Line  CVs :  25                 25
  Line  UASs:  10                 10 

dspalmcnt

Display Alarm Counters

Displays the performance monitoring alarm counters for either a SONET or a DS3 line.

Card(s) on Which This Command Executes

AXSM

Syntax

dspalmcnt 
-ds3 <bay.line> | -e3 <bay.line> | -sonet <bay.line> | -plcp <bay.line>

Syntax Description

Related Commands

clralmcnt

Attributes

Log: no

State: any

Privilege: ANYUSER

Examples

pinnacle.11.AXSM.a > dspalmcnt -ds3 1.1
  Line Num:      2.1
  CurrentLCV :      9109365
  CurrentLES :      13
  CurrentPCV :      1
  CurrentPES :      1
  CurrentPSES:      0
  CurrentSEFS:      11
  CurrentUAS :      0
  Num of LOS :      1
  Num of OOF :      1
  Num of RAI :      0
  Num of CCV :      0
  Num of FE :       0

pinnacle.6.AXSM.a > dspalmcnt -sonet 1.1
 Line Num:                        1.1
 Elapsed Time (in sec):             1634
Section PM:
-----------
  Num of LOSs:                   1
  Num of LOFs:                   1
  CurrentESs:                    0
  CurrentSESs:                   0
  CurrentSEFSs:                  1
  CurrentCVs:                    1
Line PM:
--------
  Num of AISs:         0
  Num of RFIs:         0
  Near End                            Far End
  CurrentESs :              1           CurrentESs : 1
  CurrentSESs:              0           CurrentSESs: 0
  CurrentCVs :              1           CurrentCVs : 1
  CurrentUASs:              0           CurrentUASs: 0
Path PM:
--------
  Num of AISs:                      1
  Num of RFIs:                      1
  Near End                            Far End
  CurrentESs :              0           CurrentESs : 0
  CurrentSESs:              0           CurrentSESs: 0
  CurrentCVs :              0           CurrentCVs:  0
  CurrentUASs:              0           CurrentUASs: 0

dspalms

Display Alarms

Display all alarms on the card. The command requires the line type in the form of a parameter called alarmTable. RFC 2258 describes the categories of alarms. The display can easily scroll for many pages if more than one line is active.

Card(s) on Which This Command Executes

AXSM

Syntax

dspalms

Syntax Description

node19.1.AXSM.a > dspalms
Line Number: 1.1
   Alarm State
      Section : Clear
      Line    : Clear
      Path    : Clear
   Statistical Alarm State
      Section : No Alarm
      Line    : No Alarm
      Path    : No Alarm
 
   Line Number: 1.2
   Alarm State
      Section : No Alarm
      Line    : No Alarm
      Path    : No Alarm
   Statistical Alarm State
      Section : No Alarm
      Line    : No Alarm
      Path    : No Alarm
 
   Line Number: 2.1
   Alarm State 
Section : No Alarm
      Line    : No Alarm
      Path    : No Alarm
   Statistical Alarm State
      Section : No Alarm
      Line    : No Alarm
      Path    : No Alarm
 
   Line Number: 2.2
   Alarm State
      Section : No Alarm
      Line    : No Alarm
      Path    : No Alarm
   Statistical Alarm State
      Section : No Alarm
      Line    : No Alarm
      Path    : No Alarm 

dspatmln

Display ATM Line

Display the cell header configuration for the line. The display indicates NNI or UNI cell headers. The configuration reflected in the display results from cnfatmln execution.

Card(s) on Which This Command Executes

AXSM

Syntax

dspatmln 
<bay.line>

Syntax Description

bay.line

Identifies the bay (1 or 2) and the number of the line. The line number is from 1 to the highest numbered line on the back card. For the range of line numbers on specific AXSM models, see Table 3-1.

Related Commands

cnfatmln, clratmlncnt

Attributes

Log: no

State: any

Privilege: ANYUSER

pinnacle.1.AXSM.a > dspatmln 1.1
 
 line  HCScoset PayloadScramble NullCellHdr NullCellPayload
----------------------------------------------------------------------
   1.1   Enable          Enable    1a1a1a1a              aa 

dspcd

Display Card

Display the following information about a card:

• Hardware serial number and revision level.

• Firmware revision level. (See the loadrev description for an explanation of how to interpret the revision filed.)

• Status, possibly including the reason for the last reset (FunctionModuleResetReason) and state of the integrated alarm (cardIntegratedAlarm).

• For a service module only, a count of configured lines, ports, and connections.

• For a service module, the maximum number of connections supported on each port group. Note that the numbers are not existing connection counts but rather the maximum. This maximum is a function of the hardware and varies with interface type (OC-3, OC-12, and so on). The purpose of this information is to help you configure resource partitions by showing the maximum number of supported connections. If the one partition has all or close to the maximum supported by hardware on a physical line, few or no connections would be possible in another partition on the same line.

Some of the information that dspcd shows is common to the version command, but version shows the boot code version in bold.

Card(s) on Which This Command Executes

PXM45, AXSM

Syntax

dspcd

Syntax Description

This command does not take parameters.

Related Commands

dspcds, version

Attributes

Log: no

State: any

Privilege: ANYUSER

Examples

Example 3-61: Display card details for the current PXM45.

---

Note   The "A1" at the end of the primary software revision and boot firmware revision numbers shows that these versions are pre-release. Refer to the setrev description for details.

---

jbscott.7.PXM.a > dspcd
 
jbscott                          System Rev:02.00   Apr. 05, 2000
09:57:41 GMT
MGX8850                                              Shelf Alarm:NONE
Slot Number    8    Redundant Slot: 7
 
                    Front Card          Upper Card          Lower Card
                    ----------          ----------          ----------
 
Inserted Card:     PXM45               UI Stratum3         PXM
HardDiskDrive
Reserved Card:     PXM45               UI Stratum3         PXM
HardDiskDrive
State:             Active              Active              Active
Serial Number:     SAK0405007Z         SAK0332009M         PCB-991107
Prim SW Rev:       2.0(1)D             ---                 ---
Sec SW Rev:        2.0(1)D             ---                 ---
Cur SW Rev:        2.0(1)D             ---                 ---
Boot FW Rev:       2.0(1)D             ---                 ---
HW Rev:            49.56               48.52               48.48
Orderable Part#:   800-6147-1          3104-5787-1         3104-12345-6
 
CLEI Code:         0000000000                              CLEI991107
Reset Reason:      On Reset From Shell
Card Alarm:        NONE
Failed Reason:     None
Miscellaneous Information:
 
Type <CR> to continue, Q<CR> to stop:
jbscott                          System Rev:02.00   Apr. 05, 2000
09:57:41 GMT
MGX8850                                              Shelf Alarm:NONE
 
Crossbar Slot Status:     EMPTY
 
Alarm Causes
------------
    NO ALARMS

Example 3-62: Display card details for the current AXSM-4-622.

node19.1.AXSM.a > dspcd
                    Front Card          Upper Card          Lower Card
                    ----------          ----------        ------------
 
Card Type:          AXSM-4-622          SMFIR-2-622         ---
 
State:              Active              Present             Absent
 
Serial Number:      THISISATEST         SAK0328001S         ---
 
Boot FW Rev:        2.0.77.252          ---                 ---
 
SW Rev:             2.0(1)D             ---                 ---
 
HW Rev:             0.0                 0.0                 ---
 
Orderable Part#:    800-5317-1          800-5383-1          ---
 
PCA Part#:          73-4102-1           73-4125-1           ---
 
Reset Reason:On Power up 
 
Card SCT Id: 6
 
#Lines #Ports #Partitions   #SPVC    #SVC
------ ------ ----------- ------- -------
     1      1           1      2      1 
 
Port Group[1]:
#Chans supported:32512  Lines:1.1
Port Group[2]:
#Chans supported:32512  Lines:1.2
Port Group[3]:
#Chans supported:32512  Lines:2.1
Port Group[4]:
#Chans supported:32512  Lines:2.2 

dspcdalms

Display Card Alarms

Display alarms that originate on a service module. The dspcdalms command runs on the PXM45, so if it shows an alarm for one of the following parts of the card, you can cc to that card and execute one of the applicable commands:

• Line (dsplns and dspln)

• Port (dspports and dspport)

• Connection (dspcons and dspcon)

In addition to the preceding, on the AXSM you can also exercise dspalm and dspalms.

The definition of each alarm severity comes from Bellcore TR-NWT-000474. An alarm can be:

• Critical, indicating complete, non-recoverable failure, loss of data, and do on. The failed entity must be restored. A power failure or a line being disconnected is an example.

• Major, indicating service-affecting errors. This event indicates that a major service is damaged or lost, but the existing traffic is not affected.

• Minor, indicating non-service affecting errors or errors on a remote node. Corrective action is appropriate to prevent a serious fault from developing. An example is a fan failure, where no subscribers are immediately affected, but calamity could result if the situation persists. Note that an accumulation of lower-level alarms does equal a higher-level alarm.

The dspcdalms command is part of a hierarchy of troubleshooting commands you can execute on the PXM45 or a service module. Frequently, dspcdalms follows the higher-level command dspndalms.

Cards on Which This Command Executes

PXM45

Syntax

dspcdalms [slot] 

Syntax Description

slot identifies a particular slot. For the current PXM45, slot is unnecessary. For any other card, you must include slot.

Related Commands

dspndalms, dspalm, dspalms

Attributes

Log: no

State: ACTIVE

Privilege: ANYUSER

Examples

node19.8.PXM.a > dspcdalms 8
Node Card Alarm Summary
 
Line Alarm       Slot   8  Critical    0   Major    0   Minor    0
Port Alarm       Slot   8  Critical    0   Major    0   Minor    0
Connect Alarm    Slot   8  Critical    0   Major    0   Minor    0 

node19.8.PXM.a > dspcdalms
Node Card Alarm Summary
 
Line Alarm       Slot   1  Critical    0   Major    0   Minor    0
Port Alarm       Slot   1  Critical    0   Major    0   Minor    0
Connect Alarm    Slot   1  Critical    0   Major    0   Minor    0
Line Alarm       Slot   8  Critical    0   Major    0   Minor    0
Port Alarm       Slot   8  Critical    0   Major    0   Minor    0
Connect Alarm    Slot   8  Critical    0   Major    0   Minor    0 

dspcderrs

Display Card Errors

Display information about card errors.

Card(s) on Which This Command Executes

PXM45

Syntax

dspcderrs

Related Commands

wilco.7.PXM.a > dspcderrs
 
dspcderrs
08/05/95-18:53:05 tRootTask    3 Task failed          : scm                     
09/05/95-09:14:08 tRootTask    3 Task failed          : scm                     
value = 0 = 0x0
 
wilco.7.PXM.a >

dspcdcnt

Display Card Counters

Displays the count for received and transmitted cells on the current AXSM.

Card(s) on Which This Command Executes

AXSM

Syntax

dspcdcnt

Related Commands

pinnacle.6.AXSM.a > dspcdcnt
Ingress Count                          Egress Count
-------------                          ------------
Cells to xbar plane[1]:              0  Cells from xbar plane[1]:9660
Cells to xbar plane[2]:              0  Cells from xbar plane[2]:9661
Cells to xbar plane[3]:          30910  Cells from xbar plane[3]:11593
Cells to xbar plane[4]:              0  Cells from xbar plane[4]:0
Cells to xbar plane[5]:              0  Cells from xbar plane[5]:0
Cells to xbar plane[6]:              0  Cells from xbar plane[6]:0
Cells to backplane    :          30910  Cells from backplane(QLSI):30914
Cells from QE 48      :          30914  CLP0 cells dropped :0
undef cells from port :              0  CLP1 cells dropped :0
errored OAM from port :0
invalid OAM from port :0
unsupported OAM from port :0
errored RM cells from port:0

dspcds

Display Cards

Displays high-level information for all the cards in the node. For more detailed information about a card, execute dspcd on the CLI of that card. The information that dspcds provides is the:

• Revision level of the boot firmware

• Revision level of the system software

• Date and time of command execution, including GMT offset

• Backplane serial number and its hardware revision level

• The IP address of the statistics master (a workstation)

• Type of card in the front and back slots and the (active/standby) state of each

• Alarm status for each card and the shelf itself

• Redundancy configuration for each slot

Card(s) on Which This Command Executes

PXM45

Syntax

dspcds

Related Commands

saturn2.8.PXM.a > dspcds
Unknown                          System Rev: 10.10   Nov. 06, 1999 20:15:06 GMT
Boot F/W Rev: 01.00.10           H/W Rev:    00.00   GMT Offset  0
Backplane Serial No: SAA02390010 Backplane HW Rev: 00.00
Statistics Master IP Address: Shelf Alarm: NONE
Card  Front/Back       Card           Alarm      Redundant  Redundancy
Slot  Card State       Type           Status     Slot       Type
---   ----------       --------       --------   -------    -----
 
01    Active/Active   AXSM_1OC48      NONE       NA         NO REDUND
02    Empty            ---            ---        ---         ---
03    Empty            ---            ---        ---         ---
04    Empty            ---            ---        ---         ---
05    Empty            ---            ---        ---         ---
06    Empty            ---            ---        ---         ---
07    Empty            ---            ---        ---         ---
08    Active/Active   UNKNOWN_FC      NONE       07         SECOND SLT
09    Empty            ---            ---        ---         ---
10    Empty            ---            ---        ---         ---
11    Empty            ---            ---        ---         ---
12    Empty            ---            ---        ---         ---
13    Empty            ---            ---        ---         ---
14    Empty            ---            ---        ---         --- 

dspcdsct

Display Card SCT

Displays the contents of an ingress service class template (SCT) file. For information about SCTs, see the cnfcdsct description. To see the number of the current SCT for the card, use dspcd. The examples in this description illustrate the contents of SCT number 4 for this dspcdsct description.

Card(s) on Which This Command Executes

AXSM

Syntax

dspcdsct 
<parameter_group>

Syntax Description

parameter_group can be:

• bw for bandwidth

• gen for policing and CAC

• cosb

• vcThr for VC thresholds

• cosThr for COSB thresholds

Related Commands

cnfcdsct, dspsct