Table Of Contents
Tracing All Calls or Specific AESAs
enableaxsmbaps
Enable AXSM/B for APS—PXM45
The enableaxsmbaps command lets you specify that an AXSM/B runs in AXSM/B mode. This command addresses a carry-over from releases prior to Release 3.0. The enableaxsmbaps command is necessary only if you intend the AXSM/B to support APS.
The enableaxsmbaps command runs in the context of a graceful upgrade of AXSM/B firmware from a version of 2.x to 3.0 or higher. If you have an AXSM/B that ran with any version of 2.x firmware and you upgrade to 3.0 or higher and intend to configure APS, you must run the sequence of commands for a graceful upgrade and follow the upgrade by using the enableaxsmbaps command. The sequence of commands is as follows:
1.
loadrev
2.
3.
4.
Note
Syntax
enableaxsmbaps <primary/secondary slot>
Syntax Description
Related Commands
loadrev, runrev, commitrev
Attributes
Example
Set the card pair in slot 1 and slot 2 to run in AXSM/B mode.M8850_LA.8.PXM.a > enableaxsmbaps 1/2This command will enable the software to use Model B hardwarefor APS. Make Sure that Hardware is AXSM Model B and the cardis running the correct software revision.enableaxsmbaps: Do you want to proceed (Yes/No)? yERR: The card present in this slot does not have this featureERR: Syntax: enableaxsmbaps <primary/secondary slot>exit
Exit from User Session—PXM45, PXM1E
Use exit to exit the current user session and log out. To start another session, you must log in by using telnet (for example).
Syntax
exit
Related Commands
bye, logout
Attributes
Example
Exit from the current user session.
MGX8850.8.PXM.a > exit(session ended)forcecdnative
Force Card Native—PXM45, PXM1E
The forcecdnative command is used to recover from a PXM failure because of non-nativity issues. This command forces the PXM to ignore nativity and rebuild from the configuration on the disk Running the forcecdnative command causes the PXM to reset, so you are prompted to confirm the operation before it actually runs.
Note
Syntax
forcecdnative
Syntax Description
This command takes no parameters.
Related Commands
none
Attributes
Example
Force the card to recover its native configuration from the hard drive. (If the PXM were not in the failed state, the following error message would appear: "ERR: This command is applicable only in FAILED state.")
London21.7.PXM.a > forcecdnativeThis command will cause the system to reset and bring up the shelfwith the configuration on the hard disk.Please confirm now!forcecdnative: Do you want to proceed (Yes/No)?
help
Help—PXM45, PXM1E
Use help to view commands associated with the current card. The help command is case-sensitive. Its behavior with or without parameters is:
•
•
•
Syntax
Help [string]
Related Commands
?
Attributes
history
History—PXM45, PXM1E
Use history to display the recent commands that have run on the current card. The default number of commands in the display is 10, but you can specify a much larger number of commands (see Syntax Description).
To repeat a previous command and its parameters, type an exclamation mark followed by the associated number and no spaces, then press Return.
Syntax
history [history]
Syntax Description
Related Commands
None
Attributes
Example
Display the last 10 commands executed on the PXM. Repeat the previous execution of dspdate.
MGX8850.7.PXM.a > dspdateSep 09 2000 16:37:37 GMTMGX8850.7.PXM.a > historySize of cmdHistory is currently 10 line(s)1 q2 help dsp3 help dspdate4 q5 help dspdate6 history7 68 help dspdate9 dspdate10 historyMGX8850.7.PXM.a > !9dspdateSep 09 2000 16:38:06 GMTinsbiterror
Insert Bit Error—PXM1E
Inserts single bit errors into the transmitted BERT pattern.
Syntax
insbiterror -ln <bay.line>
Syntax Description
Related Commands
cnfbert, startbert, stopbert
Attributes
ipifconfig
IP Interface Configuration—PXM45, PXM1E
The ipifconfig command lets you configure an IP address and other user-interface parameters to provide runtime IP connectivity for control of the switch. The name of the IP address for runtime user-control is the disk IP address. (When the PXM is either in boot mode or in the standby state, its IP address is called the boot IP address.) The interface type can be ATM, Ethernet, or SLIP. Typically, the Cisco WAN Manager application on a local or remote work station controls a switch through this interface.
(Note that ipifconfig and related commands have no bearing on the Console Port for an ASCII terminal that is co-located with the node. For details on the hardware connections and initial start-up through the console port, see the Cisco MGX 8850 (PXM1E/PXM45), Cisco MGX 8950, and Cisco MGX 8830 Software Configuration Guide, Release 4.)
The ipifconfig command lets you specify:
•
•
•
•
•
•
•
Behavioral Characteristics
Note the following characteristics of IP connectivity in general and the disk IP address in particular:
•
•
–
–
•
•
•
Usage Guidelines
Except for the first-time, mandatory configuration of an IP address for the interface, the ipifconfig parameters are optional details you can use to modify the interface. The parameters include default states that apply to a broad range of network designs. The purpose of these defaults is to minimize the need to change the optional parameters.
The IP interface configuration requires knowledge of the capabilities of the devices or interfaces that exist between the PXM and workstation. Particularly, any attached routers should be feature-rich. For example, the most likely configuration consists of:
•
•
•
Note
Syntax
ipifconfig <interface> [ip_address] [netmask <mask>] [broadcast <broad_addr>]
[dest <peer_ip_address>] [up | down ] [arp | noarp] [svc | nosvc] [pvc | nopvc] [default | nodefault] [clrstats]Syntax Description
Related Commands
bootchange, dspipif, pvcifconfig, dsppvcif, svcifconfig, dspsvcif, dspipifcache
Attributes
Example
Specify an IP interface of type ATM, address of 163.72.29.177, and a net mask of 255.255.255.000, and use the defaults for all other parameters.
wilco.7.PXM.a > ipifconfig atm0 163.72.29.177 mask 255.255.255.000loadrev
Load Revision—PXM45, PXM1E
Use the loadrev command to download a firmware image from the FW directory on the disk to flash memory on the targeted card. Running loadrev is the first step in a graceful firmware upgrade. A graceful revision change preserves the configuration of the card and minimizes any data loss that could result from the brief disruption in service.
Syntax
loadrev <slot> <revision>
Syntax Description
slot
The number of the targeted card slot. You cannot use loadrev for the following slots:
•
•
•
revision
Revision number derived from the firmware file. See "Version Numbering Conventions."
Usage Guidelines
Although loadrev runs on a PXM, the target can be either a service module or the PXM45 itself. The system automatically determines which card in a redundant setup is active and which is standby. Specifying the active card slot is sufficient. For example, if a PXM is the target, you can specify either slot 7 or slot 8 regardless of the active slot number.
The sequence of commands for a graceful revision change appear in the following list. See Table 2-18 and Table 2-19 for a clarification of the various states within this sequence.
1.
2.
3.
4.
Note
A graceful upgrade takes a single card or a redundant card pair through different stages. If you must execute abortrev on a redundant pair, the card (or possibly both cards in the case of a redundant pair) is reset. The stages of a graceful upgrade and the reset actions appear in Table 2-18 for a single-card upgrade and Table 2-19 for a redundant-pair upgrade.
The tables start by showing that, initially, the primary and secondary versions of firmware are 2.x, so the only possible operational version is 2.x. The loadrev command loads a generic version called 2.y, and the upgrade sequence progressively changes the primary and secondary firmware versions.
Note
After you execute runrev, the PXM updates the database records on disk if changes occur (such as changes to the configuration or network topology). If you revert to the previous version by executing abortrev, the post-runrev changes are lost. For example, if a switch was added to the network between runrev and abortrev, the restored database has no record of the topology change.
Version Numbering Conventions
This section describes how to interpret the version number of a firmware image. Commands such as loadrev and setrev require a version number rather than a filename. Similarly, dspversion shows the firmware version number rather than the firmware filename. Although the version number derives from the firmware filename, they are distinctly different.
Firmware Filenames
The FW directory on the hard drive contains firmware files of possibly many revisions. (Each firmware file has the fw file extension.) The format of a firmware filename is:
cardtype_version-element[_platform].fw
Note that platform is an optional field because it applies to only the PXM. For example, a firmware file may have the name "axsm_002.000.001.001.fw." Within this filename, the version-portion is 002.000.001.001. (Note the absence of "mgx.") This version-portion has the following format:
major-release.minor-release.maintenance.patch-phase
The range for major release numbers is 0-31. The range for all other release numbers—minor, maintenance, and patch—is 0-255. Note that, as you read left-to-right, each element is a superset of the element on the right, and the number on the right resets to 0 or 1 when the element on its left is incremented. For example, if the minor-release number 010 rolls to 011, the maintenance on its right is reset to 1, so the new version in the example is 002.011.001.000. (Note the anomaly here is that the maintenance number resets to 1 rather than 0 because of the IOS convention of starting maintenance numbers at 1.)
Version Numbers
To derive the firmware version number, the firmware filename is altered by removing insignificant zeroes and being reformatted to include parentheses. The format of a version number is:
major-release.minor-release(maintenance.patch)phase
For example, the significance of 2.1(60.8)P1 is shown below:
The first two revision numbers in the following list represent released product. These two bullets show major release 2, minor release 1, and the maintenance number 70. The last three bullets show developmental revision numbers. Pre-release, developmental versions have alphanumeric characters at the end of the revision number. Having a pre-release version is not typical, but it may appear in various contexts. An easy way of seeing a pre-release number is the on-line help for either the loadrev or setrev command. The following are examples:
•
•
•
Note
Related Commands
abortrev, commitrev, runrev, setrev, dspversion, dspcd
Attributes
Example
Load version 2.1(70.4) to the AXSM in slot 5.
pinnacle.7.PXM.a > loadrev 5 2.1(70.4)logout
Log Out—PXM45, PXM1E
Use logout to end the current user session.
Syntax
logout
Syntax Description
This command takes no parameters.
Related Commands
bye, exit
Attributes
Example
Log out of the current CLI shell.
MGX8850.8.PXM.a > logout(session ended)ls
List—PXM45, PXM1E
Use ls to list the contents of the working directory. The filename is listed for each entry. The total space of the file system and free space is also summarized at the end of the output.
Syntax
ls [dir]
Syntax Description
You can specify an optional directory or path to list.
Related Commands
cd, pwd, rename, copy
Attributes
Examples
For the first example, list all the files at the highest level of the disk.
MGX8850.7.PXM.a > lsSMFWDIAGSTATSTMPCNFRPMLOGclrDBupgrade.stateconfig.sysDBIn the file system:total space: 819200 K bytesfree space: 700583 K bytesChange to the SCT directory. List all files in the SCT directory, then list the files in the AXSM directory.
MGX8850.7.PXM.a > cd /SCTMGX8850.7.PXM.a > ls...AXSMIn the file system :total space : 819200 K bytesfree space : 660582 K bytesMGX8850.7.PXM.a > ls AXSM...AXSM_SCT.CARD.2AXSM_SCT.CARD.3AXSM_SCT.PORT.2AXSM_SCT.PORT.3In the file system :total space : 819200 K bytesfree space : 660582 K bytesMGX8850.7.PXM.a >optrte
Optimize Routes—PXM45, PXM1E
The optrte command lets you force immediate optimization of all SPVCs and SPVPs on a PNNI logical port. Optionally, you optimize a single connection or a range of connections. (Connection grooming is a common word for optimization.)
Re-routing depends on a reduction in the cost of the route. If the PXM can find a route with sufficiently lower cost, the connection is de-routed then re-routed. Route cost-reduction depends on the percent of cost reduction and an absolute grooming threshold. These grooming are configurable through the cnfrteoptthld command. For a detailed explanation of route optimization, see the cnfrteopt description.
Note
Note
Syntax
optrte <portid> [-vpi <vpi>] [-vci <vci>] [-range <starting-vpi/vci..ending-vpi/vci>]
Syntax Description
portid
The format of the PNNI physical port identifier can vary, as follows:
•
•
–
–
•
For more details, see the section, "PNNI Format," in "Introduction."
-vpi
Keyword that specifies the vpi. The range is 0-4095.
-vci
Keyword that specifies the vci. The range is 1-65535.
-range
The range of connections for grooming. The VPI of the starting SPVC must be less than the ending VPI, and the starting VCI must be less than the ending VCI.
Use the notation as it appears on the syntax line: type a slash between the VPI and VCI and two dots with no spaces between the starting and ending values. For example, 100/1000..200/10000 is a valid entry. The ranges are as follows:
•
•
In the variable parameter starting-vpi/vci..ending-vpi/vci, the starting and ending VPIs are independent of the starting and ending VCIs. For example, -range 3/40..5/50 means the following:
Optimize all SPVCs that have a VPI in the range 3-5 and a VCI in the range 40-50.
This example range could include 3/40, 3/45, 4/45, 5/45 and 5/50 but not 4/60.
Note that the default for -range is all connections on the PNNI port specified by portid. Therefore, to groom all connections on the port, leave out the -range parameter.
Related Commands
cnfrteopt, cnfrteoptthld, dsprteoptcnf, dsprteoptstat
Attributes
Example
Immediately find a better route for the SPVC with VPI.VCI 1000.50000 on port 1:2.1:1.
pop20two.7.PXM.a > optrte 1:2.1:1 -vpi 1000 -vci 50000pathtraceie
Path Trace IE—PXM45, PXM1E
This command determines whether the PNNI trace feature removes or inserts the path trace information element (IE) at the port level. If the choice is remove, PNNI removes the path trace IE before the SETUP message goes to the next node. If the choice is insert, the IE continues in the SETUP message tot the next node.
In most cases, the default is insert. In contrast, for AINI/IISP links, PNNI automatically removes the IE. See also the descriptions of the pathtraceie and pathtraceport commands.
Syntax
pathtraceie <portid> {rmv | ins}
Syntax Description
portid
The format of the PNNI physical port identifier can vary, as follows:
•
•
–
–
•
For more details, see the section, "PNNI Format," in "Introduction."
rmv
Allow the deletion of the Trace Transit List IE at the port.
ins
Allow the insertion of the Trace Transit List IE at the port.
Related Commands
conntrace, pathtraceport, pathracenode, dsppathtraceie
Attributes
pathtracenode
Path Trace Node—PXM45, PXM1E
Enables or disables the path trace feature at the node level. The default at the node-level is for path tracing to be enabled. (The default capability for path traces at the port level is disabled. Therefore, you need to enable path tracing on a per-port basis.)
Syntax
pathtracenode {enable | disable}
Syntax Description
enable or disable
Enter the word "enable" or "disable" for the path trace at the node level.
Default: enable
Related Commands
dsppathtracenode, pathtraceport
Attributes
pathtraceport
Path Trace Port—PXM45, PXM1E
The pathtraceport command lets you enable (or disable) the path trace feature at the port level. Path tracing means that the trace occurs only during call setup. Therefore, tracing is enabled before call set up then actually occurs while PNNI routes the connection. The applicable connections are SPVCs, SPVPs, SVCs, or SVPs.
(Tracing a route for a call that has already been routed is a connection trace. See the conntrace description. However, if the connection fails to route, conntrace cannot show the route. You can use a path trace to find where the routing breaks down.)
With path tracing, you can observe routing behavior to improve load sharing or for isolating points of routing failure. Examples of events that trigger a path trace are as follows:
•
•
•
You can use these triggers as often as necessary for researching the path that a call setup takes.
By default, path tracing is disabled at the port level but enabled at the node level. With path trace enabled, you can view either a trace for an individual connection or a list of all traces by using the dsppathtracebuffer or dsppathtracebuffers command, respectively. You can clear one or all trace buffers by using the clrpathtracebuffer or clrpathtracebuffers command.
Crankback Option
By enabling the crankback option, you can see in the trace buffer where the call was cranked back and therefore isolate the point of failure. If the crankback option is disabled, the system does not keep a record of the route if the call is cranked back.
Tracing All Calls or Specific AESAs
When you enable path tracing, the feature stores the routes for all calls on the port in the trace buffers. The capacity for this feature is ten trace buffers with 100 trace records in each buffer. When a buffer is full, the system deletes the oldest entry as it performs each new trace. For a port with many calls, the traces can fill up the buffers and be flushed before you check them. Therefore, this command has filter options to let you narrow the scope of the trace.
Two pairs of options let you create filters based on ATM addresses. You can specify up to five calling party ATM addresses and five called party ATM addresses on each list. With these options, the feature traces only the connections for these addresses when they go through a particular port. As soon as you add one address to either list, the feature stops the default of tracing all calls on the port. Thereafter, only the calls on the list are traced during call setup.
Typically, you would specify the option of one called AESA or one calling AESA per iteration of the command. You can specific both a called address and a calling address in one command iteration, but then the trace occurs only if both the called address and calling address match what you specified. Put another way: the calling and called AESAs are ANDed instead of ORed before the system traces the call.
Path Trace Limits
Note the following limits for path trace:
•
•
•
•
The switch stores the port-level, path trace configuration on the disk of the active and standby PXM. Exceptions are the calling party and called party filters: only the standby PXM retains these values.
Syntax
pathtraceport <portid> {enable | disable} [-X {on | off}] [-CB {on | off}] [-V {on | off}]
[-CR {on | off}] [-cldnum called-AESA -cldopt {add | del}]
[-clgnum calling-AESA -clgopt {add | del}]Syntax Description
portid
The format of the PNNI physical port identifier can vary, as follows:
•
•
–
–
•
For more details, see the section, "PNNI Format," in "Introduction."
enable or
disableEnables or disables path trace on the port. If path tracing is enabled on a port and you specify that the switch disable it, the other parameters for this command are meaningless.
For SPVCs and SPVPs, enable path tracing at the master and slave UNIs.
Default: disabled
-X
Specifies the clear call option. If this option is specified, the call's route is traced, but the call is released after the trace—and therefore never routed as long as this option is on. This option has limited application. Type either "on" or "off."
Default: off
-CB
Specifies the crankback option as on or off. With the crankback option on, you can see in the trace buffer where the call was cranked back. Also, the failure cause for crankback is included in the TTL IE. Type either "on" or "off."
Note
Default: off
-V
Specifies the VPI/VCI option. If enabled, VPI/VCI values of the egress port are added in the TTL IE at every node.
Default: on
-CR
Specifies the call reference option. If enabled, call reference values of all egress ports are added in the TTL IE.
Default: on
-cldnum
Specifies a called party AESA. This address is either added to or deleted from the list of called party addresses on this port for tracing purposes. This option works in conjunction with -cldopt. The -cldopt option specifies whether to add or delete the address from the list. The port can retain up to five such addresses.
-cldopt
This option either adds or deletes the called party AESA you specified with the -cldnum option for the purpose of tracing calls.
-clgnum
Specifies a calling party AESA. This address is either added to or deleted from the list of calling party addresses on this port for tracing purposes. This option works in conjunction with -clgopt. The -clgopt option specifies whether to add or delete the address from the list. The port can retain up to five such addresses.
-clgopt
This option either adds or deletes the calling party AESA you specified with the -clgnum option for the purpose of tracing calls.
Related Commands
conntrace, pathracenode, pathraceie, dsppathtracebuffer, dsppathtracebuffers
Attributes
Examples
Enable path tracing on port 5:1.1:1 with crankback also enabled, then display the path trace configuration for the same port.
r18pop157.7.PXM.a > pathtraceport 5:1.1:1 enable -CB onr18pop157.7.PXM.a > dsppathtraceport 5:1.1:1Port option :onClear :offCrankback :onVPI/VCI :onCall Reference :onCalling address:noneCalled address:noneEnable path trace on port 9:1.1:1 with crankback on and a called address filter of 4755500000000000000000000000000000000000.
p2spvc8.7.PXM.a > pathtraceport 9:1.1:1 enable -CB on -cldnum 4755500000000000000000000000000000000000 -cldopt addThe following example illustrates how the configuration would appear if you specified five calling party AESAs and five called party AESAs.
p2spvc8.7.PXM.a > dsppathtraceport 9:1.1:1Port option :onClear :offCrankback :onVPI/VCI :onCall Reference :onCalling address(es):47aaa00000000000000000000000000000000000:4799900000000000000000000000000000000000:4788800000000000000000000000000000000000:4777700000000000000000000000000000000000:4766600000000000000000000000000000000000Called address(es) :4755500000000000000000000000000000000000:4744400000000000000000000000000000000000:4733300000000000000000000000000000000000:4722200000000000000000000000000000000000:4711100000000000000000000000000000000000ping
Ping—PXM45, PXM1E
Use ping to determine whether a host is operational. The command causes the switch to send an ICMP packet to a destination address.
Syntax
ping <IP_Addr> [<Num_Packets>]
Syntax Description
IP_Addr
IP address of the destination host in dotted decimal format.
Num_Packets
Number of packets, in the range 0-65535.
•
•
Related Commands
None
Attributes
Example
Ping IP address 172.29.23.148.
MGX8850.7.PXM.a > ping 172.29.23.148PING 172.29.23.148: 56 data bytes64 bytes from 172.29.23.148: icmp_seq=0. time=0. ms64 bytes from 172.29.23.148: icmp_seq=1. time=0. ms64 bytes from 172.29.23.148: icmp_seq=2. time=0. ms----172.29.23.148 PING Statistics----3 packets transmitted, 3 packets received, 0% packet lossround-trip (ms) min/avg/max = 0/0/0pvcifconfig
PVC Interface Configuration—PXM45, PXM1E
Modifies an existing PVC to support IP connectivity to a feeder such as a BPX switch or an MGX Release 1 switch.
Syntax
pvcifconfig <interface> <router | local> <pvc_address> [atmarp | noatmarp] [llcencap | vcmux]
[default | nodefault] [reset] [delete] [up] [clrstats]Syntax Description
Related Commands
dsppvcif, ipifconfig, setipconndebug
Attributes
pwd
Present Working Directory—PXM45, PXM1E
Use pwd to identify the current working directory on the PXM.
Syntax
pwd
Syntax Description
This command takes no parameters.
Related Commands
cd, rmdir, rm, ls, copy
Attributes
Example
Identify the present working directory.
MGX8850.7.PXM.a > pwdC:MGX8850.7.PXM.a >resetcd
Reset Card—PXM45, PXM1E
The resetcd command lets you reset one of the following:
•
•
•
Note
Using the resetcd command without defining a slot number results in an ungraceful (disruptive) upgrade. This is the fastest method to upgrade a card, but it disrupts service.
A graceful (non-disruptive) upgrade requires that the loadrev, runrev, and commitrev commands have already been executed and that the card is identified in the command string.
Syntax
resetcd [slot] [-f]
Syntax Description
Related Commands
resetsys
Attributes
Example
Reset the current PXM45.
pinnacle.7.PXM.a > resetcdThe card in slot number 7, will be reset. Please confirm actionDo you want to proceed (Yes/No)? n(command not executed)Reset the failure history of the card in slot 1.
8850_NY.7.PXM.a > resetcd 1 -fClearing (-F) Failed state on slot 1. Please confirm actionresetcd: Do you want to proceed (Yes/No)?resetevtlogsem
Reset Event Log Semaphore—PXM45, PXM1E
This special troubleshooting command applies to a situation where the dsplog or dsplogs function hangs because it was previously interrupted by Ctrl-C.
Syntax
resetevtlogsem
Syntax Description
This command takes no parameters.
Related Commands
dsplog, dsplogs
Attributes
Example
Reset the event log.
PXM1E_SJ.7.PXM.a > resetevtlogsemWARNING:This command should be executed only if the dsplog/dsplogswas previously interrupted by Ctrl-C. And now, dsplog hangs*** Ensure that NO other user is executing dsplogs*** or dsplog on this switch before proceeding.*** Otherwise, this command may corrupt the log file.resetevtlogsem: Do you want to proceed (Yes/No)?resetsys
Reset System—PXM45, PXM1E
Reset the entire node.
Syntax
resetsys
Syntax Description
This command takes no parameters but displays a warning and prompts you to continue the execution.
Related Commands
resetcd
Attributes
Example
Reset the system.
pinnacle.7.PXM.a > resetsysThis command resets the entire shelf, a destructive command.Please confirm now!Do you want to proceed (Yes/No)? n(command not executed)restoreallcnf
Restore All Configurations—PXM45, PXM1E
Restores all configuration files saved to the CNF directory on the hard drive. The saved configuration is the result of a prior execution of the saveallcnf command. To see a list of existing configurations that have been zipped by saveallcnf, cd to the C drive and list the contents of the CNF directory.
Syntax
restoreallcnf -f filename [-v]
Syntax Description
-f
Specifies the filename of the zipped version of the configuration.
-v
(Optional) Specifies that a list of the restored configuration files goes to the default printer. The default is no printout.
Related Commands
saveallcnf, abortallsaves
Attributes
Example
Restore the system configuration created on February 5, 2001. The system responds with a statement of what the command would do and prompts you to accept the action before it proceeds with command execution.
pinnacle.7.PXM.a > restoreallcnf -f pop20two_01_200102051156.zipThe current configuration will be replaced with the contentsof the specified file and the shelf will be rebooted.restoreallcnf: Do you want to proceed (Yes/No)? n(command not executedrouteShow
Route Show—PXM45, PXM1E
Show the current IP routing of the network layer of the operating system.
Syntax
routeShow
Related Commands
routestatShow
Attributes
Example
Display the current IP routing of the network layer of the operating system.
pinnacle.8.PXM.a > routeShowROUTE NET TABLEdestination gateway flags Refcnt Use Interface------------------------------------------------------------------------0.0.0.0 172.29.23.149 1 1 21778 lnPci00.0.0.0 172.29.23.1 3 0 2755 lnPci0172.1.1.0 172.1.1.149 1 0 0 atm0172.29.23.0 172.29.23.149 1 2 5275 lnPci0------------------------------------------------------------------------ROUTE HOST TABLEdestination gateway flags Refcnt Use Interface------------------------------------------------------------------------0.0.0.0 0.0.0.0 5 0 0 sl0127.0.0.1 127.0.0.1 5 1 0 lo0172.29.23.3 172.1.1.149 5 0 3555 atm0172.29.23.5 172.1.1.149 5 0 3304 atm0172.29.23.7 172.1.1.149 5 0 3335 atm0171.71.29.18 172.1.1.149 5 0 3304 atm0172.29.23.18 172.1.1.149 5 0 3304 atm0172.29.23.28 172.1.1.149 5 0 6127 atm0172.29.23.29 172.1.1.149 5 1 6065 atm0171.71.29.32 172.1.1.149 5 0 5842 atm0171.71.29.44 172.1.1.149 5 0 3304 atm0172.29.23.53 172.1.1.149 5 0 3304 atm0171.71.29.59 172.1.1.149 5 0 3304 atm0171.71.28.126 172.1.1.149 5 0 3309 atm0------------------------------------------------------------------------pinnacle.8.PXM.a >routestatShow
Show Routing Statistics—PXM45, PXM1E
Use the routestatShow command to view the current IP routing statistics for the network layer of the operating system.
Syntax
routestatShow
Related Commands
routeShow
Attributes
Example
Display the current IP routing statistics for the network layer of the operating system
pinnacle.8.PXM.a > routestatShowrouting:0 bad routing redirect0 dynamically created route0 new gateway due to redirects0 destination found unreachable11095 uses of a wildcard routepinnacle.8.PXM.a >rrtparty
Re-route Party—PXM45, PXM1E
The rrtparty command forces PNNI to search for a better route between the root and party on a point-to-multipoint (P2MP) connection.
Syntax
rrtparty portid vpi vci endpointRef
Syntax Description
portid
The format of the PNNI physical port identifier can vary, as follows:
•
•
–
–
•
For more details, see the section, "PNNI Format," in "Introduction."
vpi
The local VPI of the connection is in one of the following ranges:
•
•
vci
The local VCI of the connection has a range of 35-65535.
endpointRef
The endpoint reference has a range of 1-32767
Related Commands
addcon, delparty, dnparty, upparty, addparty, dspparty, dspparties, dsppartiespercon, dspcon, dspcons, dsppnport, dsppnports, clrspvcnonpers
Attributes
Example
rstrtimagrp
Restart IMA Group—PXM1E
The rstrtimagrp command restarts the IMA group at the near end, restarts all the internal IMA state machines, and causes the IMA group to attempt to re-establish the IMA protocol with far end.
The order of commands for downing and upping an IMA group is as follows:
1.
2.
3.
Syntax
rstrtimagrp <group>
Syntax Description
group
The group identifier consists of a bay number as well as a group number in the format bay.group. The possible values are as follows:
•
•
Related Commands
dspimagrp, dspimalnk
Attributes
Example
Restart IMA group 1.
MGX8850.7.PXM1E.a> rstrtimagrp 2.1rrtcon
Re-route Connection—PXM1E
The rrtcon command lets you trigger the immediate re-routing of a connection.
If the connection is a point-to-multipoint connection, all parties on the connection also are re-routed. To re-route an individual party, use the rrtparty command.
Grooming a point-to-multipoint (P2MP) connection depends on branching concerns rather than routing costs. The optrte, cnfrteopt, and cnfrteoptthld commands are not appropriate for P2MP connections because these commands depend on routing costs. The rrtcon command merely triggers the re-route, then PNNI determines route improvements based on branching.
Note
Syntax
rrtcon <ifNum> <vpi> <vci>
Syntax Description
Related Commands
dspcons, dspcon, dspparty, dspparties, dsppartiespercon
Attributes
runrev
Run Revision—PXM45, PXM1E
The runrev command causes a new firmware version to start running. The runrev command is the second of the required commands in a graceful upgrade. It runs on a PXM but can target either a service module or the PXM.
The order of commands in a graceful upgrade, including the option of aborting the upgrade, appears in the following list. For clarification of the states in a graceful upgrade, see Table 2-20 and Table 2-21.
1.
2.
3.
4.
The tables start by showing that, initially, the primary and secondary versions of firmware are 2.x, so the only possible operational version is 2.x. The loadrev command loads a generic version called 2.y, and the upgrade sequence progressively changes the primary and secondary firmware versions.
Note
After you use the runrev command, the PXM updates the database records on disk if changes occur (such as changes to the configuration or network topology). If you revert to the previous version by running abortrev, the post-runrev changes are lost. For example, if a switch was added to the network between runrev and abortrev, the restored database has no record of the topology change.
Syntax
runrev <slot> <revision>
Syntax Description
slot
Number of the targeted card slot.You cannot use runrev for the following slots:
•
•
•
revision
The revision number comes from the name of the firmware file. If the standby card does not have the specified image, runrev has no effect, and the system displays an error message. For an explanation, see the section, "Version Numbering Conventions," in the loadrev description.
Related Commands
abortrev, commitrev, loadrev, setrev, dspcd, dspversion
Attributes
Example
Run version 2.1(0.4) in logical slot 7. A previous check of the cards (by using dspcds) and firmware images (by using dspcd) would show whether a redundant card and version 2.1(0.4) are present.
excel.8.PXM.a > runrev 7 2.1(0.4)saveallcnf
Save All Configurations—PXM45, PXM1E
The saveallcnf command saves all configurations to a zipped file in the CNF directory on the hard drive. Use the saveallcnf configuration only if no connection provisioning is occurring.
This command takes significant time, so a warning message prompts you for confirmation before the system performs the task. Upon completion, the system displays the name of the saved configuration file. The system stores up to two zipped configuration files. If you want to save more than two configurations, use FTP to transfer the files to another device.
To restore the system configuration, use restoreallcnf. To abort a configuration save, use abortallsaves.
Note
Syntax
saveallcnf
Related Commands
restoreallcnf, abortallsaves
Attributes
Example
Save the system configuration. Note that the system displays the name of the saved configuration file.
MGX8850.7.PXM.a > saveallcnfThe 'saveallcnf' command can be time-consuming. The shelfmust not provision new circuits while this command is running.Do not run this command unless the shelf configuration is stableor you risk corrupting the saved configuration file.ATTENTION PLEASE NOTE:-> If you want to abort the save, please use abortallsaves CLI.If you use cntrl-C, you will risk hanging the whole telnetsession and may lose capability of being able to performsubsequent saves-> The save command will only store the2 most recent saved files in C:/CNF directory.If you have 2 or more files already saved in C:/CNF,the older ones will be deleted by the current save,keeping the 2 most recent.saveallcnf: Do you want to proceed (Yes/No)? n(command not executed)setcugdefaddr
Set Closed User Group Default Address—PXM45, PXM1E
The port-level setcugdefaddr command lets you specify an ATM address prefix as the default address for CUG validation. See the addcug description for details on the CUG feature.
The default address has the following uses:
•
•
Syntax
setcugdefaddr <portid> <atm-address> <length> [-plan {e164 | nsap}]
Syntax Description
portid
The format of the PNNI physical port identifier can vary, as follows:
•
•
–
–
•
For more details, see the section, "PNNI Format," in "Introduction."
atm-address
The NSAP or E.164 address on the local UNI interface is 20 bytes.
length
Address length. The units of measure differ for each address plan. The -plan option lets you specify E.164 or NSAP.
•
20 bytes x 8 bits per byte = 160 bits•
-plan
The plan is either NSAP or E.164 and is set when you add the ATM address by using the addaddr command. Type either e164 or nsap in its entirety.
Default: nsap
Related Commands
addcug, cnfcug, clrcugdefaddr, cnfaddrcug, cnfnodecug, delcug, dspaddrcug, dspcug, dspcugdefaddr, dspnodecug
Attributes
Example
At port 12:12.1:1, specify the following default address for CUGs:
•
•
•
pswpop3-1.7.PXM.a > setcugdefaddr 12:12.1:1 47.0091.8100.0000.0001.4444.7777 104 nsapsetipconndebug
Set IP Connection Debug—PXM45, PXM1E
Specify a debug mode and whether to use a console for debugging IP connectivity. This command requires SUPER_GP privilege. After you set the debug level, a status message states the current level.
Syntax
setipconndebug [-console | -noconsole] [debuglevel]
Syntax Description
Attributes
Example
Set IP connection debug to console and specify a debug level of 20 for SVC call events.
node19.8.PXM.a > setipconndebug -console 20setrev
Set Revision—PXM45, PXM1E
Force-load and run a firmware version for a card. You must execute setrev from the CLI of the active PXM whether the target is a service module or the PXM.
Note
Note
Syntax
setrev <slot> <version>
Note
Syntax Description
slot
Number of the targeted card slot.
You cannot use the setrev command for the following slots:
•
•
•
version
An alphanumeric string derived from the name of the firmware file. For an explanation of the numbering scheme, see the section, "Version Numbering Conventions," earlier in the setrev description. Note that primary and secondary firmware images have the same version for the current release.
Usage Guidelines
From a high-level perspective, the setrev command has two effects. It causes the PXM to load a firmware image from the hard drive to a card, then it causes the receiving card to run that image. The impact is a forced revision change. (A graceful revision path is available through the sequence of loadrev, runrev, and commitrev. A revision is an upgrade if the new firmware version has a higher numerical value or a downgrade if the new version has a lower value.)
At the time you initially bring up a node or after executing clrallcnf, the service modules have no runtime firmware image, so you must execute setrev for each service module in the switch. For the PXM, Cisco ships the product with firmware installed, so executing setrev is not necessary until you need to change firmware version or after you execute clrallcnf.
Version Numbering Conventions
This section describes how to interpret the version number of a firmware image. Commands such as loadrev and setrev require a version number rather than a filename. Similarly, dspversion shows the firmware version number rather than the firmware filename. Although the version number derives from the firmware filename, they are distinctly different.
Firmware Filenames
The FW directory on the hard drive contains firmware files of possibly many revisions. (Each firmware file has the fw file extension.) The format of a firmware filename is:
cardtype_version-element[_platform].fw
Note that platform is an optional field because it applies to only the PXM. For example, a firmware file may have the name "axsm_002.000.001.001.fw." Within this filename, the version-portion is 002.000.001.001. (Note the absence of "mgx.") This version-portion has the following format:
major-release.minor-release.maintenance.patch
The range for each release, maintenance, and patch is 0-255. Note that, as you read left-to-right, each element is a superset of the element on the right, and the number on the right resets to 0 or 1 when the element on its left is incremented. For example, if the minor-release number 010 rolls to 011, the maintenance on its right is reset to 1, so the new version in the example is 002.011.001.000. (Note the anomaly here is that the maintenance number resets to 1 rather than 0 because of the IOS convention of starting maintenance numbers at 1.)
Version Numbers
To derive the firmware version number, the firmware filename is altered by removing insignificant zeroes and being reformatted to include parentheses. The format of a version number is:
major-release.minor-release(maintenance.patch)
Using the example of axsm_002.001.001.001.fw, the version is 2.1(1.1). Similarly, if no patch were present, the version number would be 2.1(1).
Pre-release, developmental versions have one or two alphanumeric characters at the end of the version number, and these versions may appear in various contexts. For example, the help display for setrev gives examples of revision, but only the first two in the following list could be in released product. These two bullets show major release 2, minor release 1, and the minimal maintenance number of 1 (per the IOS precedent). The last three bullets show developmental revision numbers:
•
•
•
Note
Related Commands
loadrev, runrev, commitrev, abortrev, dspversion, dspcd
Attributes
Example
Specify version 2.0(2) for the card in slot 9. In addition to setrev, this example shows other commands you could use before and after setrev. The sequence begins with a display of all the cards. While the firmware is going into the RAM on the card, periodically execute dspcds on the PXM to see the changing status of the target card. After setrev finishes, run dspcd on the targeted service module to see the version and other details of the card or dspversion to see just the version.
Step 1
pinnacle.7.PXM.a > dspcdspxm45tl System Rev: 00.00 Jan. 05, 2000 15:18:40 GMTBoot F/W Rev: 0.0(0) H/W Rev: 00.00 GMT Offset 0Backplane Serial No: _UNKNOWN___ Backplane HW Rev: 00.00Statistics Master IP Address: 0.0.0.0 Shelf Alarm: NONECard Front/Back Card Alarm Redundant RedundancySlot Card State Type Status Slot Type--- ---------- -------- -------- ------- -----01 Empty --- --- --- ---02 Empty --- --- --- ---03 Empty --- --- --- ---04 Empty --- --- --- ---05 Empty --- --- --- ---06 Empty --- --- --- ---07 Active/Empty UNKNOWN_FC NONE 08 PRIMARY SLOT08 Empty Resvd/Emp UNKNOWN_FC MAJOR 07 SECONDARY SLOT09 Failed/Empty UNKNOWN_FC NONE NA NO REDUNDANCY10 Empty --- --- --- ---11 Empty --- --- --- ---12 Empty --- --- --- ---13 Empty --- --- --- ---14 Empty --- --- --- ---Step 2
pinnacle.7.PXM.a > cd /FWStep 3
pinnacle.7.PXM.a > lsThe display shows the names of the firmware files. Extract the AXSM version number—2.0(2):
pxm45_002.000.001-D.fwpxm45_002.000.014-A1_bt.fwaxsm_002.000.002.fwStep 4
Note
pinnacle.7.PXM.a > setrev 9 2.0(2)Step 5
pxm45tl System Rev: 00.00 Jan. 05, 2000 15:21:01 GMTBoot F/W Rev: 0.0(0) H/W Rev: 00.00 GMT Offset 0Backplane Serial No: _UNKNOWN___ Backplane HW Rev: 00.00Statistics Master IP Address: 0.0.0.0 Shelf Alarm: NONECard Front/Back Card Alarm Redundant RedundancySlot Card State Type Status Slot Type--- ---------- -------- -------- ------- -----01 Empty --- --- --- ---02 Empty --- --- --- ---03 Empty --- --- --- ---04 Empty --- --- --- ---05 Empty --- --- --- ---06 Empty --- --- --- ---07 Active/Empty UNKNOWN_FC NONE 08 PRIMARY SLOT08 Empty Resvd/Emp UNKNOWN_FC MAJOR 07 SECONDARY SLOT09 Init/Empty AXSM_16OC3 NONE NA NO REDUNDANCY10 Empty --- --- --- ---11 Empty --- --- --- ---12 Empty --- --- --- ---13 Empty --- --- --- ---14 Empty --- --- --- ---Step 6
pxm45tl System Rev: 00.00 Jan. 05, 2000 15:21:11 GMTBoot F/W Rev: 0.0(0) H/W Rev: 00.00 GMT Offset 0Backplane Serial No: _UNKNOWN___ Backplane HW Rev: 00.00Statistics Master IP Address: 0.0.0.0 Shelf Alarm: NONECard Front/Back Card Alarm Redundant RedundancySlot Card State Type Status Slot Type--- ---------- -------- -------- ------- -----01 Empty --- --- --- ---02 Empty --- --- --- ---03 Empty --- --- --- ---04 Empty --- --- --- ---05 Empty --- --- --- ---06 Empty --- --- --- ---07 Active/Empty UNKNOWN_FC NONE 08 PRIMARY SLOT08 Empty Resvd/Emp UNKNOWN_FC MAJOR 07 SECONDARY SLOT09 Active/Active AXSM_16OC3 NONE NA NO REDUNDANCY10 Empty --- --- --- ---11 Empty --- --- --- ---12 Empty --- --- --- ---Step 7
pinnacle.7.PXM.a > dspversionImage Type Shelf Type Card Type Version Built On---------- ---------- ---------- ------------ ------------Runtime MGX AXSM 2.0(2) Jan 03 2000, 16:36:39Boot MGX AXSM 2.0(128)A1 -
smclrscrn
Service Module Clear Screen—PXM45, PXM1E
The smclrscrn command lets you enable or disable at the node level certain clear-screen commands for narrowband service modules (NBSMs). The two commands on the NBSMs are clear and cls. If these commands are not enabled by the smclrscrn command on the PXM, they do nothing. The applicable NBSMs are AUSM, FRSM, and CESM, and so on.
To see the current enable state, enter smclrscrn with no parameters.
Note
Syntax
smclrscrn [enable | disable]
Syntax Description
enable
disable
Type enable or disable to enable or disable the cls and clear commands on the NBSMs.
Default: disabled
Related Commands
clrscrn, cls, clear (on the NBSMs)
Attributes
stackdump
Stack Dump—PXM45, PXM1E
The stackdump command writes stack data to an error file. You can view the file by using dsplog.
Syntax
stackdump
Syntax Description
This command takes no parameters.
Related Commands
dsplog
Attributes
Example
Run the stackdump command then view the resulting log file by using the dsplog command.
M8850_NY.7.PXM.a > stackdumpThe trace is saved in file error01.logM8850_NY.7.PXM.a > dsplog -log error01.log07A09583 08/25/2001-11:56:31 SSI-4-STKCHKtChunkMon ssiCheckAllTaskStackStack usage exceeds threshold (70 percent): Task=pnCliTask (0x82ea2060),Size=8176, Usage=703205A03052 08/25/2001-11:45:40 STAT-4-ERRORE:01588 StatFileMg sfm_fileCreateMsgHFunc-sfm_fileCreateMsgH, Line-911, Errno-0x20643: sfm_sumEpidResolveDBSyncreturned error05A03051 08/25/2001-11:45:40 STAT-5-WARNINGStatFileMg sfm_sumEpidResolveDBSynFunc-sfm_sumEpidResolveDBSync, Line-768, Errno-0x20643: ipcSend failed to sendlistResMsg, 1508-times failed so far06A01484 08/25/2001-11:45:20 STAT-4-ERRORE:00777 StatFileMg sfm_fileCreateMsgHFunc-sfm_fileCreateMsgH, Line-911, Errno-0x20643: sfm_sumEpidResolveDBSyncreturned error06A01483 08/25/2001-11:45:20 STAT-5-WARNINGStatFileMg sfm_sumEpidResolveDBSynFunc-sfm_sumEpidResolveDBSync, Line-768, Errno-0x20643: ipcSend failed to sendlistResMsg, 734-times failed so far01A01963 08/25/2001-11:45:20 STAT-4-ERRORE:01707 StatFileMg sfm_fileCreateMsgHstartimalnktst
Start IMA Link Test—PXM1E
The startimalnktst command starts an IMA link connectivity test on an IMA link. This test can confirm that an IMA link connection is valid by sending a test pattern to the link. The test pattern is a number in the range 0-254. A 0 causes the system to select a number for the pattern. If the transmitted number is the same as the number that arrives at the receiving end of the link, the link is valid. If the test pattern is different or does not arrive at all, the link is invalid.
The order of commands for configuring and using an IMA link is as follows:
1.
2.
3.
Syntax
startimalnktst <group> <link> -pat <testPat>
Syntax Description
Related Commands
stopimalnktst, cnfimalnktst
Attributes
Example
Start an IMA link test with the following values:
•
•
•
For group 1 and link 1, specify a test pattern of 77.
MGX8850.7.PXM1E.a> startimalnktst 2.1 2.1 -pat 77startuplinkbert
Start Uplink Bit Error Rate Testing—PXM1E
The startuplinkbert command starts BERT on one of the lines on the PXM1E UNI/NNI back card. Before you start the test, it must have been configured through the cnfuplinkbert command. To stop the test, use the stopuplinkbert command. To display BERT-related information, use the dspuplinkbert or dspuplinkbertstats command.
Syntax
startuplinkbert <bay.line>
Syntax Description
bay.line
The required parameter identifies the bay and line for the test. The possible values are as follows:
•
•
Related Commands
cnfuplinkbert, dspuplinkbert, dspuplinkbertstats, stopuplinkbert
Attributes
stopimalnktst
Stop IMA Link Test—PXM1E
This command stops the IMA link test that you started by using the startimalnktst command.
Syntax
stopimalnktst group
Syntax Description
group
The group identifier consists of a bay number as well as a group number in the format bay.group. The possible values are as follows:
•
•
Related Commands
startimalnktst, cnfimalnktst
Attributes
Example
Stop the IMA link test for group 1.
MGX8850.7.PXM1E.a> stopimalnktst 2.1stopuplinkbert
Stop Uplink Bit Error Rate Testing—PXM1E
The stopuplinkbert command stops the BERT that is running on one of the lines on the PXM1E UNI/NNI back card.
Syntax
stopuplinkbert <bay.line>
Syntax Description
bay.line
The required parameter identifies the bay and line that is under test. The possible values are as follows:
•
•
Related Commands
cnfuplinkbert, dspuplinkbert, dspuplinkbertstats, startuplinkbert
Attributes
svcifconfig
SVC Interface Configure—PXM45, PXM1E
Configure IP-related parameters for the SVCs that support network control at a workstation.The configuration applies to all the SVCs on one of the three physical port types. Note that a complete configuration requires you to use svcifconfig twice. The first instance identifies the ATM end-station address (AESA) and encapsulation type at the router end. The second instance identifies the AESA—but no encapsulation type—for the switch.
Syntax
svcifconfig <interface> <router | local> <svc_address> [atmarp | noatmarp] [llcencap | vcmux] [default | nodefault] [reset] [delete] [force] [clrstats]
Syntax Description
Enter all keywords in their entirety.
Related Commands
ipifconfig, dspipif, dspsvcif, dspipifcache
Attributes
Example
First configure the AESA for the local (PXM) side, then configure the AESA for the router. This case uses the defaults for encapsulation (llcencap) and ARP (enabled).
sfo.7.PXM.a > svcifconfig arm0 local 47.0091.8100.0000.1010.1010.1010.1010.1010.1010.10sfo.7.PXM.a > svcifconfig arm0 router 47.0091.8100.0000.0101.0101.0101.0101.0101.0101.01switchapsln
Switch APS Line—PXM45, PXM1E
The switchapsln command switches traffic from the working line to the protection line. See the addapsln description for details on Automatic Protection Switching (APS) on the current product. When entered on a PXM, this command applies to the following hardware:
•
•
–
–
Syntax
switchapsln <slot> <bay> <line> <switchOption> [serviceSwitch]
Syntax Description
Related Commands
addapsln, cnfapsln, delapsln, dspapsln, dspapslns, dspapsbkplane, clrbecnt, dspbecnt
Attributes
Example
On line number 8 of the active PXM1E, force a switch to the protection line.
Goa.2.PXM.a > switchapsln 7 1 8 3Forced line switch from working to protection succeeded on line 7.2.8Goa.2.PXM.a >switchcc
Switch Core Cards—PXM45, PXM1E
The switchcc command lets you activate a standby controller card and make the active card in the redundant pair go to standby. (To switch the state of redundant service modules, use the switchredcd command.) If a standby PXM is not available, the switchcc command fails.
You cannot run switchcc during a configuration-copy. If you attempt it, the system blocks the operation. Also, the operation fails if the switch is unstable or if the standby PXM is not in the standby state (for example, if the card is in the init state).
Note
Syntax
switchcc
Related Commands
switchredcd, dspred
Attributes
Example
Attempt a switchcc without a standby PXM in the backplane.
raviraj.7.PXM.a > switchccDo you want to proceed (Yes/No)? yCore card redundancy unavailableraviraj.7.PXM.a >switchredcd
Switch Redundant Card—PXM45, PXM1E
The switchredcd command lets you activate a standby service module and make the active card in the redundant pair go to standby. (To switch the state of redundant PXMs, use the switchcc command.)
Syntax
switchredcd <fromSlot> <toSlot>
Syntax Description
fromSlot
The active card in the redundant pair.
toSlot
The standby card in the redundant pair—which you are switching to active.
Related Command
dspred, delred, switchcc
Attributes
Example
mgx8850a.7.PXM.a > switchredcd 8 7telnet
Telnet—PXM45, PXM1E
The telnet command lets you directly telnet to another switch from the current CLI session. Therefore, you do not have to exit the current CLI session and start a new telnet session to reach another switch. The limit of nodes to which you can telnet is one. This command requires 2.1 or higher software.
To return to the CLI from which you telnetted—to break the connection and end the telnet session—enter the exit or bye command.
Syntax
telnet [-E <escape character>] [-R <traceroute character>] <ip addr> [[0x|X|x] <tcp port>]
Syntax Description
Related Commands
exit, bye
Attributes
Example
First telnet to IP address 172.29.65.40, then try to telnet to a second switch.
jeffrey-u10\> telnet 172.29.65.40telnet 172.29.65.40Trying 172.29.65.40...Connected to 172.29.65.40.Escape character is '^]'.Login: ciscopassword:jeff.7.PXM.a > telnet 172.29.65.40Trying 172.29.65.40...Connected to 172.29.65.40.Escape character is ^]Login: ciscopassword:jeff.7.PXM.a > telnet 172.29.65.49Err: telnet node-to-node is limited to one hoptimeout
Timeout—PXM45, PXM1E
The timeout command lets you extend the amount of idle time in a user-session from the default of
10 minutes. If you do not specify a timeout period, the system displays the current timeout. At the end of the session, the system logs you out.
Note
Syntax
timeout [time_out]
Syntax Description
time_out
Number of idle seconds allowed for the session.
Range: 0-43200 seconds. Note that entering a 0 actually specifies the maximum of 43200 seconds (12 hours).
Related Commands
sesntimeout
Attributes
Examples
Display the current timeout.
pinnacle.7.PXM.a > timeoutThe timeout period for this session is currently 600 second(s)pinnacle.7.PXM.a >Set the session timeout threshold to 100 minutes (6000 seconds).
pinnacle.7.PXM.a > timeout 6000The timeout period for this session is now set to 5000 second(s)pinnacle.7.PXM.a >tstconseg
Test Connection Segment—PXM1E
Test the integrity of an SVC or SPVC. With tstconseg, a single collection of supervisory cells is sent in the egress direction between the card and service equipment (CPE). (See tstdelay for ingress direction.)
When the test successfully starts, the system displays a message stating that the test has begun and directs you to use either dspcon or dspchantests to see the results. The dspcon command shows detailed information about the connection and has a field for the results of this test. The dspchantests command display only the results of the test.
Note
Syntax
tstconseg <ifNum> <vpi> <vci> [-num <iterations>]
Syntax Description
Related Commands
dspcon, tstdelay, dspchantests
Attributes
Example
Test the integrity of 1 10 1000 in the egress direction.
node19.7.PXM1E.a > tstconseg 1 10 100Test started; Use dspcon/dspchantests to see test resultststdelay
Test Delay—PXM1E
Test the integrity of the connection in the ingress direction by sending a collection of supervisory cells to the remote end of the network and back. (See tstconseg for the egress direction.) The tstdelay command applies to only SPVCs. It does not apply to point-to-multipoint connections.
If the test successfully begins, the display states the fact and directs you to use the dspcon or dspchantests command to view the round trip time in microseconds. The dspcon display shows detailed information on the connection and has a field for the test results. The dspchantests display shows the results of only the round trip delay test.
Note
Note
Syntax
tstdelay <ifNum> <vpi> <vci> [-num <iterations>]
Syntax Description
Related Commands
dspcons, tstconseg, dspcon
Attributes
Example
Get the round-trip delay for connection 1 10 100. This example contains four tasks to illustrate how to obtain a list of logical ports; obtain a connection number; start the test; and view the results. The commands are dspports, dspcons, tstdelay, and dspcon.
Step 1
node19.7.PXM1E.a > dspportsifNum Line Admin Oper. Guaranteed Maximum Port SCT Id ifType VPIState State Rate Rate (VNNI only)----- ---- ----- ----- ---------- --------- ----------------- ------ ----------1 2.1 Up Up 1412831 1412831 6 UNI 0Step 2
node19.7.PXM1E.a > dspconsrecord Identifier Type SrvcType M/S Upld Alarm------ ---------- ---- -------- --- ---- -----0 01.0010.00100 VCC ubr1 S 0000ebfb none1 01.0011.00101 VCC ubr1 M 0000ec27 noneStep 3
node19.7.PXM1E.a > tstdelay 1 10 100Test started; Use dspcon/dspchantests to see test resultsStep 4
node19.7.PXM1E.a > dspchantests 1 10 100Connection Id Test Type Direction Result Round Trip Delay============= ========= ========= ======= ================01.0010.00100: OAM Lpbk ingress Success 30000Step 5
node19.7.PXM1E.a > dspcon 1 10 100--------------------------------------------------------------------------Local : NSAP Address port vpi vci(S) 4700918100000000001A53C82D00000101180100 1.01.01 10 100Remote : NSAP Address port vpi vci(M) 4700918100000000001A53C82D00000101180100 1.01.01 11 101--------------------------------------------------------------------------Conn. Type : VCC Admn Status : ADMN-UPService Type : ubr1 Rtng Status : -67372037Controller : 2--------------------------------------------------------------------------Local PCR : 14 Remote PCR : 14Local SCR : 3 Remote SCR : 3Local CDV : -1 Remote CDV : -1Local CTD : -1 Remote CTD : -1Local MBS : 1 Remote MBS : 1Local CDVT : -1 Remote CDVT : -1Admin weight : -1 Frame discard: N--------------------------------------------------------------------------OAM CC Config : DISABLED Statistics : DISABLED--------------------------------------------------------------------------Loopback Type : OAM Lpbk | Dir: ingress | Status: Success | RTD: 30000 us----------------------------------------------------------------------------------------------------------------------------------------------------Port side Tx : normal Swth side Tx : normalPort side Rx : normal Swth side Rx : normal--------------------------------------------------------------------------I-AIS/RDI E-AIS/RDI CONDITIONED CCFAIL IfFail MismatchNO NO NO NO NO NO--------------------------------------------------------------------------tstpndelay
Test PNNI Port Delay—PXM45, PXM1E
Initiates loopback test for a connection. If you provide both a VPI and VCI, the segment endpoint is an F5 flow endpoint (for VCCs). If you provide only a VPI, the segment endpoint is a F4 flow endpoint (for VPCs). This command displays the round trip delay in microseconds.
Use cnfconsegep to specify the segment endpoint if one does not already exist.
Syntax
tstpndelay <portid> <vpi> [vci] [-direction {inbound | outbound}]
Syntax Description
portid
The format of the PNNI physical port identifier can vary, as follows:
•
•
–
–
•
For more details, see the section, "PNNI Format," in "Introduction."
vpi
VPI of the connection.
vci
VCI of the connection.
Default: 0
-direction
Specifies the direction of loopback.
inbound: endpoint towards the backplane
outbound: endpoint departing the port
Default: inbound
Related Commands
cnfconsegep
Attributes
Example
After confirming that the endpoints are configured to be OAM segment endpoints, run tstpndelay on connection 0 2929 on port 9:1.1:11. Make the direction outbound.
cokemt20.8.PXM.a > tstpndelay 9:1.1:11 0 2929 -direction outboundcokemt20.8.PXM.a > Response for the cli Command -- tstpndelay:In ProgressIt is Primary OAM Endpoint vpi:0, vci:2929Successful, Cell round trip delay time = 117 uSec
upcon
Up Connection—PXM1E
Activate a connection that was previously brought down by the dncon command. (The typical purpose of dncon is some form of operational modification or troubleshooting.)
Syntax
upcon <ifNum > <vpi> <vci>
Syntax Description
Related Commands
dncon
Attributes
upilmi
Up Integrated Local Management Interface—PXM1E
Use upilmi to activate integrated local management interface (ILMI) for a particular resource partition on a logical port. Before using the upilmi command, you must:
1.
2.
3.
After activating ILMI, you can configure it by using the cnfilmi command.
Syntax
upilmi <ifNum> <partId>
Syntax Description
ifNum
The range for logical interface (or port) numbers is 1-31.
partId
The range for partition identifier is 1-20.
Related Commands
cnfilmi, dspilmi
Attributes
Example
Determine whether ILMI is up on logical port 1, resource partition 1. If ILMI is down (or off), activate it by using the upilmi command. Note the second time you run the dspilmi command, the ILMI state now appears as "on."
M8850_NY.7.PXM1E.a > dspilmi 1 1Sig. rsrc Ilmi Sig Sig Ilmi S:Keepalive T:conPoll K:conPollPort Part State Vpi Vci Trap Interval Interval InactiveFactor---- ---- ---- ---- ---- --- ------------ ---------- ----------1 1 Off 0 16 Off 1 5 4M8850_NY.7.PXM1E.a > upilmi 1 1Warning: connections (if any) on port could get rerouted.Do you want to proceed (Yes/No) ? yM8850_NY.7.PXM1E.a > dspilmi 1 1Sig. rsrc Ilmi Sig Sig Ilmi S:Keepalive T:conPoll K:conPollPort Part State Vpi Vci Trap Interval Interval InactiveFactor---- ---- ---- ---- ---- --- ------------ ---------- ----------1 1 On 0 16 Off 1 5 4upimagrp
Up IMA Group—PXM1E
The upimagrp command administratively activates an IMA group and is necessary only after the group has been deactivated through the dnimagrp command.
The order of commands for downing and upping an IMA group is as follows:
1.
2.
3.
Syntax
upimagrp <group>
Syntax Description
group
The group identifier consists of a bay number as well as a group number in the format bay.group. The possible values are as follows:
•
•
Related Commands
addimagrp, delimagrp, dspimagrp, dnimagrp
Attributes
Example
Activate IMA group 1.
MGX8850.7.PXM1E.a> upimagrp 2.1upln
Up Line—PXM45, PXM1E
On a PXM1E, the upln command activates a line on one of two different card types. The line can be on the PXM1E UNI/NNI back card or on a service resource module (SRME or SRM-3T3). An upln command also runs on the AXSMs in a switch with a PXM45. See the other upln description for details.
If the line is on the PXM1E back card, consider the resource partitioning issues for the lines. See the description of cnfcdsct for important information.
After you have activated the line, use the cnfln command to configure the line characteristics, such as the type of line (SONET, T3, or E3), line signaling, and so on.
Until you take certain configuration steps, the following is true for the SRMs and the PXM1E back card:
•
•
Note that the PXM1E can operate without SRMs and without a UNI/NNI back card. For the back card, you must up at least one line. For an SRM, you can either up a line or configure non-bulk mode redundancy by adding a link (see addlink description).
Syntax
upln <X>.<line>
Syntax Description
Related Commands
dspln, dsplns, cnfln, dnln
Attributes
upparty
Up Party—PXM45, PXM1E
This command lets you administratively up a party on a point-to-multipoint (P2MP) connection. The down state results from the use of the dnparty command. See the addparty description for details about parties on a P2MP.
Syntax
upparty portid vpi vci endpointRef
Syntax Description
portid
The format of the PNNI physical port identifier can vary, as follows:
•
•
–
–
•
For more details, see the section, "PNNI Format," in "Introduction."
vpi
The local VPI of the connection is in one of the following ranges:
•
•
vci
The local VCI of the connection has a range of 35-65535.
endpointRef
The endpoint reference has a range of 1-32767
Related Commands
addcon, delparty, rrtparty, dnparty, addparty, dspparty, dspparties, dsppartiespercon, dspcon, dspcons, dsppnport, dsppnports, clrspvcnonpers
Attributes
Example
uppnport
Up PNNI Port:—PXM45, PXM1E
The uppnport command lets you put a UNI or NNI port into service (administratively "up" the port). The circumstances in which you would use the uppnport command are as follows:
•
•
Syntax
uppnport <portid>
Syntax Description
portid
The format of the PNNI physical port identifier can vary, as follows:
•
•
–
–
•
For more details, see the section, "PNNI Format," in "Introduction."
Related Commands
addpnport, delpnport, dnpnport, dsppnport, dsppnports
Attributes
Example
Check for any downed ports by executing dsppnports. Use uppnport to up any ports that are down. The output of dsppnports shows that only one user port exists (not the 7.3x ports, the first two of which are the BITS clock ports).
8850_NY.8.PXM.a > dsppnportsSummary of total connections(p2p=point to point,p2mp=point to multipoint,SpvcD=DAX spvc,SpvcR=Routed spvc)Type #Svcc: #Svpc: #SpvcD: #SpvpD: #SpvcR: #SpvpR: #Total:p2p: 0 0 0 0 0 0 0p2mp: 0 0 0 0 0 0 0Total= 0/50000Summary of total configured SPVC endpointsType #SpvcR #SpvpR #SpvcD #SpvpD Totalp2p: 0 0 0 0 0p2mp: 0 0 0 0 0Total=0Summary of total active SVC/SPVC intermediate endpointsType #Svcc #Svpc #SpvcR #SpvpR Totalp2p: 0 0 0 0 0p2mp: 0 0 0 0 0Total=0EndPoint Grand Total = 0/100000Per-port status summaryPortId LogicalId IF status Admin status ILMI state #Conns7.35 17251107 up up Undefined 07.36 17251108 up up Undefined 07.37 17251109 up up Undefined 07.38 17251110 up up Undefined 03:1.1:1 16979969 down down Disable 08850_NY.8.PXM.a >SanJose.7.PXM.a > uppnport 3:1.1:1Check the administrative status of 3:1.1:1.
8850_NY.8.PXM.a > dsppnport 3:1.1:1Port: 3:1.1:1 Logical ID: 16979969IF status: up Admin Status: upUCSM: enableAuto-config: enable Addrs-reg: enableIF-side: network IF-type: uniUniType: private Version: uni3.1PassAlongCapab: n/aInput filter: 0 Output filter: 0minSvccVpi: 0 maxSvccVpi: 4095minSvccVci: 35 maxSvccVci: 65535minSvpcVpi: 1 maxSvpcVpi: 4095upport
Up Port—PXM1E
The upport command returns a logical port to the up state ("ups" the port) so the port can again carry traffic. The upport command concludes possible re-configuration or troubleshooting steps. Before you use upport, you must have downed the port by using dnport. Throughout the sequence of downing and upping a port, the configuration for the port remains intact whether the logical port is a UNI or an NNI.
The routes for connections vary by interface type:
•
•
Syntax
upport <ifNum>
Syntax Description
ifNum
The range for is ifNum is 1-31.
Use dspports or dspport as needed to determine which port to bring up.
Related Commands
dspport, dspports, dnport
Attributes
Example
Restore port 1 on the current card to operation.
MGX8850.1.PXM1E.a > upport 1users
Users—PXM45, PXM1E
The users command displays the following information about user sessions that are currently running:
•
•
•
•
•
Note that users shows the current user sessions, whereas the dspusers command shows the names of all the user accounts on the switch.
Syntax
users
Syntax Description
This command takes no parameters.
Related Commands
dspusers, adduser, cnfuser, timeout
Attributes
Example
Display the current users on the switch. Only one user-session is currently running. The user telnetted to the switch from IP address 10.18.247.21. The idle time is 0 because the current user has just executed the users command. If other user-sessions were running and one or more were idle, the idle time for each user would be a non-zero number. Change to the AXSM CLI and execute users.
pop20one.7.PXM.a > usersPort Slot Idle UserId From-------------------------------------------------------------telnet.01 * 7 0:00:00 davids4 10.18.247.21pop20one.10.AXSM.a > usersPort Slot Idle UserId From-------------------------------------------------------------telnet.01 10 0:00:00 cisco 0.0.0.0smterm.03 * 10 0:00:00 davids4 slot 7
verifydiskdb
Verify Disk Database—PXM45, PXM1E
The verifydiskdb command activates a utility that validates the database synchronization between the active and standby PXMs. This database includes information about all slots. The compared information resides in the D:/DB directory (see the section, "Structure of the D:\DB2 Directory," for its contents). You can configure the scope of the comparison and the output displays.
The most common use of the verifydiskdb command is in connection with a switchover. If you suspect the active card is bad, you can first run verifydiskdb to check databases before switchover. If discrepancies appear, you can reset the standby then switch over after the standby comes up. You can verify database synchronization before and after running the switchcc or switchredcd command. Similarly, after doing substantial provisioning or configuration changes or after you insert a card, you can verify that the databases have synchronized on the active and standby PXMs.
Note
This utility does the following:
•
•
•
–
–
•
•
•
The options for the verifydiskdb command let you specify the following:
•
•
•
•
Two levels of verification are available. Level 1 is control records only. Level 2 is control information plus data records (complete records). For level 2, the utility sequentially compares the flags, commit IDs, checksums, and data records. See Figure 2-18 for an illustration of these levels of comparison.
Figure 2-18
Hierarchy of Level 1 and Level 2 Comparisons
Control Records
The control records consist of the items in the following hierarchy:
1.
2.
3.
Structure of the D:\DB2 Directory
Figure 2-19 Contents of the DB2 Directory
•
•
In regard to actions performed by the utility on the items in the DB2 directory, note the following:
•
•
•
•
Operational Characteristics of verifydiskdb
The Disk Sync Verify feature has the following operational characteristics:
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
Usage Guidelines
The maximum of discrepancies is 20. If you see 20 discrepancies, you may want to consider further actions. You can synchronize the databases by resetting the standby PXM. After the standby comes up, run the verifydiskdb command again.
If discrepancies appear for a slot, you should focus subsequent iterations of the utility on that slot.
For persistent discrepancies, consider the following:
•
•
If you provision connections while the verifydiskdb check command is running, discrepancies might be flagged even if the information on the active and the standby disk is synchronized. To ensure an accurate log of discrepancies, wait for verifydiskdb check to finish before you provision connections.
Troubleshooting Discrepancies Between the Active and Standby Disk
If the disk verification utility finds discrepancies, you can take one of the following approaches:
If the utility presents you with a list of discrepancies, try to gather any log files associated with the slot that shows discrepancies. If possible, attempt application-specific tasks to resync the records (for example, remove and re-provision, add a user, and so on). You can use the following commands for this approach:
1.
2.
3.
The other approach is to enter the resetcd command to reset the standby PXM to re-synchronize it with the active disk.
Syntax
The verifydiskdb command runs with any of the following syntax forms:
verifydiskdb check [-l <level>] [-sl <slot>] [-p <iterations>]
verifydiskdb abort
verifydiskdb status
verifydiskdb display -l <log>
Syntax Description
Related Commands
dsplogs, dsplog, dsperr
Attributes
Display Contents for verifydiskdb
This section introduces the contents of the display when you include the status or display parameter. Details for these contents are explained in the Example section.
In addition to the types of records that the utility compares (control records and data records), the status display shows the three layers of hierarchy that are a part of the database:
•
•
•
These layers are illustrated out in the forthcoming section.
If you enter verifydiskdb status, the display states whether or not a verification is running. If the utility is running, it displays the following snapshot of information (see the example that accompanies this list):
•
•
–
–
–
–
–
–
–
–
–
–
–
M8850_LA.8.PXM.a > verifydiskdb statusVerification is currently running with the following parameters:Request: Slot(s): ALL Level: 1 Passes: 3Current StatusSlot: 7, Databases: 13 Tables 88DB Index: 12 DB Name: spvcRedTable Details:Table Index: 81 Table Name: Disk_spvc_pep_db19Total Records: 10000 Records Verified: 0–
The range of index numbers for the tables and databases includes 0, so the range for tables in the preceding example is 0-87. In the snapshot shown here, the current table index number is 81, and number of tables verified so far is 6.
Examples
Use the following series of commands:
1.
2.
3.
4.
5.
6.
M8850_LA.8.PXM.a > verifydiskdb statusDisk Sync Verification is currently not running.M8850_LA.8.PXM.a >M8850_LA.8.PXM.a > verifydiskdb checkM8850_LA.8.PXM.a > verifydiskdb displayDisk Sync Verification is currently running.M8850_LA.8.PXM.a > verifydiskdb statusVerification is currently running with the following parameters:Request: Slot(s): ALL Level: 1 Passes: 3Current StatusSlot: 7, Databases: 13 Tables 88DB Index: 12 DB Name: spvcRedTable Details:Table Index: 81 Table Name: Disk_spvc_pep_db19Total Records: 10000 Records Verified: 0Databases Verified: 0, Tables Verified 6M8850_LA.8.PXM.a >M8850_LA.8.PXM.a > verifydiskdb displayDisk Sync Verification is currently running.In the preceding use of verifydiskdb display, the utility was still running. In the next use, the utility has finished, so it displays the results. A description for each slot in the display precedes the screen capture.
•
•
•
•
•
•
•
•
•
•
M8850_LA.8.PXM.a > verifydiskdb displayVerify Req Level: 1 All Slots Req Iter: 3-------------------------------------------------------------------------------- Information for Slot 1 ------------------Start: 20/04/2002-17:43:49 - End: 20/04/2002-17:43:57Verify DONETotalofDbs= 4, TotalofTbls= 20, #DbVerf=4, #TblVerf= 20=============================================================dbInd: 2 - dbName: EmDiskDbtblInd: 17 - tblName: LineTableRecord: 8 ActvChkSum: 0 StdbyChkSum: 549=============================================================dbInd: 2 - dbName: EmDiskDbtblInd: 17 - tblName: LineTableRecord: 9 ActvChkSum: 0 StdbyChkSum: 549===============================================================Verification Slot SummaryStart: 20/04/2002-17:43:49 - End: 20/04/2002-17:43:57Total Discrepancies Found: 2, Total Discrepancies Synced: 0---------------------------------------------------------------------------------------------------------------------------------------------- Information for Slot 2 ------------------Start: 20/04/2002-17:43:58 - End: 20/04/2002-17:43:58Verify SKIPPED - INV_SLOTTotalofDbs= 0, TotalofTbls= 0, #DbVerf=0, #TblVerf= 0No Discrepancies found for slot 2---------------------------------------------------------------------------------------------------------------------------------------------- Information for Slot 3 ------------------Start: 20/04/2002-17:43:58 - End: 20/04/2002-17:44:06Verify DONETotalofDbs= 4, TotalofTbls= 20, #DbVerf=4, #TblVerf= 20No Discrepancies found for slot 3---------------------------------------------------------------------------------------------------------------------------------------------- Information for Slot 4 ------------------Start: 20/04/2002-17:44:06 - End: 20/04/2002-17:44:06Verify SKIPPED - UNSTABLE SLOTTotalofDbs= 0, TotalofTbls= 0, #DbVerf=0, #TblVerf= 0No Discrepancies found for slot 4---------------------------------------------------------------------------------------------------------------------------------------------- Information for Slot 5 ------------------Start: 20/04/2002-17:44:06 - End: 20/04/2002-17:44:14Verify DONETotalofDbs= 2, TotalofTbls= 15, #DbVerf=2, #TblVerf= 15No Discrepancies found for slot 5---------------------------------------------------------------------------------------------------------------------------------------------- Information for Slot 6 ------------------Start: 20/04/2002-17:44:14 - End: 20/04/2002-17:44:14Verify SKIPPED - REV_CHGTotalofDbs= 0, TotalofTbls= 0, #DbVerf=0, #TblVerf= 0No Discrepancies found for slot 6---------------------------------------------------------------------------------------------------------------------------------------------- Information for Slot 7 ------------------Start: 20/04/2002-17:44:14 - End: 20/04/2002-17:44:54Verify DONETotalofDbs= 13, TotalofTbls= 88, #DbVerf=13, #TblVerf= 88=============================================================dbInd: 3 - dbName: provRedtblInd: 28 - tblName: Disk_prov_Ncdp_portRecord: 7 ActvChkSum: 0 StdbyChkSum: 905===============================================================Verification Slot SummaryStart: 20/04/2002-17:44:14 - End: 20/04/2002-17:44:54Total Discrepancies Found: 1, Total Discrepancies Synced: 0---------------------------------------------------------------------------------------------------------------------------------------------- Information for Slot 8 ------------------Start: 20/04/2002-17:44:54 - End: 20/04/2002-17:44:54Verify SKIPPED - INV_SLOTTotalofDbs= 0, TotalofTbls= 0, #DbVerf=0, #TblVerf= 0No Discrepancies found for slot 8---------------------------------------------------------------------------------------------------------------------------------------------- Information for Slot 9 ------------------Start: 20/04/2002-17:44:54 - End: 20/04/2002-17:44:57Verify SKIPPED - UNSTABLE SLOTTotalofDbs= 2, TotalofTbls= 6, #DbVerf=0, #TblVerf= 0=============================================================dbInd: 1 - dbName: sm_mib_v21tblInd: 5 - tblName: mib29Record: 1782 ActvComdID: 0 StdbyComID: 7=============================================================dbInd: 1 - dbName: sm_mib_v21tblInd: 5 - tblName: mib29Record: 1783 ActvComdID: 0 StdbyComID: 7=============================================================dbInd: 1 - dbName: sm_mib_v21tblInd: 5 - tblName: mib29Record: 1784 ActvComdID: 0 StdbyComID: 7=============================================================dbInd: 1 - dbName: sm_mib_v21tblInd: 5 - tblName: mib29Record: 1785 ActvComdID: 0 StdbyComID: 7=============================================================dbInd: 1 - dbName: sm_mib_v21tblInd: 5 - tblName: mib29Record: 1786 ActvComdID: 0 StdbyComID: 7=============================================================dbInd: 1 - dbName: sm_mib_v21tblInd: 5 - tblName: mib29Record: 1787 ActvComdID: 0 StdbyComID: 7=============================================================dbInd: 1 - dbName: sm_mib_v21tblInd: 5 - tblName: mib29Record: 1788 ActvComdID: 0 StdbyComID: 7=============================================================dbInd: 1 - dbName: sm_mib_v21tblInd: 5 - tblName: mib29Record: 1789 ActvComdID: 0 StdbyComID: 7=============================================================dbInd: 1 - dbName: sm_mib_v21tblInd: 5 - tblName: mib29Record: 1790 ActvComdID: 0 StdbyComID: 7=============================================================dbInd: 1 - dbName: sm_mib_v21tblInd: 5 - tblName: mib29Record: 1791 ActvComdID: 0 StdbyComID: 7=============================================================dbInd: 1 - dbName: sm_mib_v21tblInd: 5 - tblName: mib29Record: 1792 ActvComdID: 0 StdbyComID: 7=============================================================who
Who—PXM45, PXM1E
Use who to see details about the user currently logged into a card. The information consists of the:
•
•
•
•
•
Syntax
who
Syntax Description
This command takes no parameters.
Related Commands
adduser, deluser, whoami
Attributes
Example
Display information about the user currently logged into the card.
MGX8850.7.PXM.a > whoPort Slot Idle UserId From-------------------------------------------------------------telnet.01 * 7 0:00:00 admin 171.71.25.240whoami
Who Am I—PXM45, PXM1E
View the current login Cards on Which This Command Runs
Syntax
whoami
Syntax Description
This command takes no parameters.
Related Commands
adduser, deluser, who
Attributes
Example
Display information about the user of the current terminal session.
MGX8850.7.PXM.a > whoamiUser ID: ciscoAccess Level: CISCO_GPTerminal Port: telnet.01MGX8850.7.PXM.a >zip
Zip-PXM45, PXM1E
The zip utility lets you zip a file or directory. A common application is for quickly copying an event or error log (and, if necessary, transferring to a workstation). Note the following characteristics:
•
•
•
•
Syntax
zip <dir | file> <destination zip file>
Syntax Description
Related Commands
ls, ll, dir
Attributes
Example
Zip the file named "foo."
M8830_SF.2.PXM.a > zip C:/FW/foo C:/TEMP/foo.zip
