|
|
This chapter describes seven diagnostic and troubleshooting commands used with a LightStream 2020 multiservice ATM switch (LS2020 switch):
| circuit-trace | Traces a circuit from the source edge. |
| connect | Logically attach the console or modem I/O port to a specified card in the node in which the CLI session is running. |
| list-port-vc | Lists circuits for a specified port on the local chassis. |
| loadcard | Load the specified file into the specified card, start the card, and establish a console connection between the CLI and the TCS slave on the card. |
| test | Run field diagnostics tests from the CLI. |
| read | Read memory and hardware registers accessible by the TCS. For qualified personnel only. |
| write | Write hex values to memory and hardware registers. For qualified personnel only. |
See also the ping command, described in the chapter entitled "CLI Control Commands;" ping is also used for diagnostic purposes.
Use the circuit-trace command to trace circuits from the source to the destination. The circuit-trace command can be used to trace circuits on a local chassis or on a remote chassis without first connecting to the remote chassis
There are two formats for the circuit-trace command--one for tracing circuits on a local chassis and one for tracing circuits using a global connection identifier. Both versions let you initiate a circuit trace from the source to the destination and display circuit and port statistics for the edge cards and intermediate trunk cards.
If a trace fails at an intermediate trunk card, the path position and reason for failure is displayed. No information is available beyond the failure point. If a process cannot get statistics from a line card, but can process the request, the partial results for that particular line card are displayed.
circuit-trace c.p {dlci | vci | frameforward | cbrpvc | stb | ctrl} [statistics]
Arguments
| c.p | Card and port number in card.port format (card=1-10; port=0-8, 255) |
| dlci dlci# | Source dlci for the circuit. |
| vci vci# | Source vci for the circuit. |
| frameforward | Frameforward circuit. |
| cbrpvc pvc# | Source pvc for the circuit. |
| stb [conn_id.end_id] | Bridge circuit connection identifier and endpoint identifier. To find the connection ID and end ID, use the list-port-vc command first. |
| ctrl [conn_id.end_id] | Control circuit connection identifier and endpoint identifier. To find the connection ID and end ID, use the list-port-vc command first. |
| statistics | Displays circuit statistics (optional) |
circuit-trace chassis:c.p [sap:identifier] [statistics]
Arguments
| chassis:c.p[sap:identifier] | Global connection identifier (GCI). The GCI value specifies the circuit's source edge port, SAP (vci, dlci, cbrpvc, and frameforward), name, and unique identifier.
You determine the GCI for a circuit by entering the list-port-vc command on any edge port or trunk port a circuit traverses. |
| statistics | Displays circuit statistics (optional). |
Use the connect command to connect the CLI to a line card as a console.
Use the connect command to connect the CLI to the specified line card so it can act as a terminal for a program, such as diagnostics, running on the line card. Type ~. (tilde-dot) to interrupt the connection.
connect card# [force] [diagnostic]
Use the list-port-vc command to list circuits for a specified port on the local chassis.
The list-port-vc command enables you to get information about active circuits transmitting user data for any edge or trunk port. You can invoke the list-port-vc command periodically on a trunk to see which circuits are normally routed through the chassis and where they originated.
list-port-vc c.p {all | dlci | vci | frameforward | cbrpvc | stb | ctrl}[summary]
Arguments
| c.p | Card and port number in card.port format (card=1-10; port=0-8, 255) |
| all | Lists all the circuits on the port. This is the default argument. |
| dlci | Lists all the Frame Relay circuits on the port. |
| vci | Lists all the ATM UNI cirucits on the port. |
| frameforward | Lists the frame forwarding circuit on the port. |
| cbrpvc | Lists the constant bit rate circuit on the port. |
| stb | Lists all the bridge circuits on the port. |
| ctrl | Lists all the control circuits on the port |
| summary | Lists only the summary information. |
Use the loadcard command to load a file into a card and run the program.
The loadcard command loads a line card program, such as the operational software or a diagnostic program, into the specified card. The command resets the card and then loads and starts the line card software.
loadcardcard#[load-address] [filename]
Arguments
| card# | The card number, in the range 3 - 10. |
| load-address | The load address (optional). Normally, you omit this argument and use the default load address. |
| filename | The name of the file containing the program you want to load (optional). If no filename is specified, this command loads the operational software for the card. |
Use the test command to run diagnostics on a specified card.
The test command runs diagnostic tests on a specified card. These tests indicate whether the card should be replaced. If a card fails, record the displayed error codes and report them when returning the card. When you invoke the test command, the software automatically takes the card out of service (changing its status to testing), identifies the type of card, and runs tests that are appropriate for the card, as specified in files in /usr/diag.
testcard#[-l][-p][-s][-x][-Ffile] testcard#-rtestcard#-m[-Ffile]
Switches
The switches that can be used with the test command are, in alphabetical order, as follows:
| -Ffile | Load diagnostics from file rather than from the default file for the card. Here, file can only be a copy of the default file, and you must ensure that file matches the card type. |
| -l | Run tests that require looping plugs or cables. For additional details, see the LightStream 2020 Hardware Reference & Troubleshooting Guide. |
| -m | Access the diagnostics interface to run tests interactively. This is equivalent to loading the manufacturing diagnostics with loadcard and connecting to the card (see the LightStream 2020 Hardware Reference & Troubleshooting Guide). The following message is the last displayed after the diagnostics have been loaded:
fcload: slot card#: releasing per-slot synchronization lock.
Press Return periodically until the prompt appears. Type ? for a list of tests. Type ^C to terminate a test in progress. Type ~. to exit. You cannot use the -r switch to retrieve output of test -m. |
| -p | Poll test output approximately once every second until completion or timeout. Tests completed between these snapshots are not displayed. If a test runs longer than one polling interval, successive dots in the display indicate the successive polls. You can terminate a test in progress with ^C. You can use the -r switch after tests have been completed. |
| -r | Retrieve results of tests, until the card status changes to active or inactive or until the card is loaded with some other software, overwriting the memory locations in which test results are stored. If the same test is active over successive polls with test -r, the heartbeat value in the display indicates whether the diagnostics are running.
The -r switch does not retrieve results of tests run interactively with the -m switch. |
| -s | Run tests that loop data through the switch fabric for the specified slot.
Do not use the -s switch on an operational system. If the card is defective, spurious data could be communicated over the network. |
| -x | Run long memory tests. These extended tests may take an hour or more to run. |
The default behavior, with only the card# argument, is to run standard pass/fail tests in the background. The -l, -s, and -x switches add other tests to the default set.
Use the read command to read memory and hardware registers accessible by the TCS.
Use the write command to write values into memory and hardware registers that are accessible by the TCS.
 | Caution The write command is for use by support personnel only. Using this command without detailed knowledge of memory locations, hardware registers, their contents, and their purposes will almost certainly destroy the functioning of the LS2020 node. |
|
|