|
This chapter is an introduction to the command line interface (CLI) that you use to operate and manage LightStream 2020 (LS2020) enterprise ATM switches. It contains a list of the CLI commands, procedures to start the CLI, and information on performing basic CLI functions.
The CLI is a simple line-oriented interface that you use to perform network operations from any node in the network. The CLI can also be loaded and run on a Sun SPARCstation. It allows you to operate your LS2020 network with or without a network management system (NMS).
The CLI lets you issue commands to only one node at a time. This means that you cannot view the status of several switches by entering a single command. You must issue a separate command to each chassis.
From the CLI, you can access any LS2020 switch in the network and perform network operations on that switch. To issue a CLI command, type the command, then press [Return]. Output is displayed on the screen. Error messages or traps may be displayed on a separate terminal or window, or they may be interleaved with the CLI commands and their output. Figure 2-1 shows a sample CLI session with traps interleaved with the commands and output.
If you are running the CLI on an NP, any command you issue is executed on the switch you are logged in to. However, you have the option of executing any of the commands listed in Table 2-2 from another switch. To do this, you must first specify the name of the other switch. This is called setting the target switch. (Refer to the section "Setting the Target Switch for CLI Commands" later in this chapter.)
If you run the CLI on a Sun SPARCstation, you must set the target switch before executing any commands.
When you install your switch, the system automatically creates the four accounts shown in Table 2-1 for your network node. None of these accounts has default passwords. Passwords for the accounts are usually set when the LS2020 switch is installed. If you do not know the password for these accounts, see your network administrator.
Account Name | Purpose | Default Prompt |
Operator (oper) | Used to access the CLI in the normal mode | cli> |
NP Administration (npadmin)1 | Used primarily for protected mode. Can also be used to access the CLI in the normal mode. | *cli> |
Field Support (fldsup) | Used primarily by field support personnel to perform advanced troubleshooting and maintenance using the LynxOS bash shell. | LSnode:2$ 2 |
root | Used for installation and for certain administration tasks using the LynxOS bash shell. | LSnode:2#3 |
When you access either the operator or the NP administration account, the switch automatically runs the CLI so you can start operations immediately. If you access either of the other accounts, the switch runs the bash shell and displays the bash (UNIX) prompt. The bash shell prompt includes the name of the chassis and the slot number of the NP. For example, LSnode:2$ means that the primary NP is on LSnode in slot 2. The dollar sign ($) indicates that you are logged in as field support. If the bash shell prompt has a pound (#) sign instead of a $, you are logged in as root (see Table 2-1).
All users can access shared accounts to operate and manage the network from the CLI. If you prefer, additional accounts can be created so that each user has his or her own account. For more information, see your network administrator.
The CLI supports the following types of command:
Table 2-2 lists the commands, their functions, and their type. For a description of each command, see the LightStream 2020 CLI Reference Manual or the LightStream 2020 Command Line Interface (CLI) Reference Card.
Name | Function | Type of Command |
---|---|---|
clear | Clears the screen. | General |
exit | Exits either the CLI program or the protected mode of the CLI program. | |
help | Provides online help for the CLI commands. | |
password | Allows you to change the password for the protected mode of CLI. | |
ping | Sends ICMP echo packets to any IP address and reports on any returned packets. | |
protected | Allows access to protected mode commands. | |
quit | Exits protected mode or the CLI program. | |
shell | Executes a shell command to allow you access to the LynxOS shell. | |
source | Executes a CLI script file stored on a disk.
| |
define | Defines bridge filters, traffic profiles, or multicast group. | MIB monitor/control |
delete | Deletes filters, traffic profiles, or multicast group. | |
set | Changes the state of the object specified. | |
show | Displays the state of the object specified. | |
browse | Allows you to move through the MIB tree and follow any branch down to its endpoint. | |
getnextsnmp | Displays the value of the object in the MIB tree that follows the object specified in this command. | |
getsnmp | Displays the value of the specified MIB object. | |
setsnmp | Changes the state of the specified MIB object. | |
walksnmp | Displays the values of all MIB objects in the MIB subtree starting with the object that you specified. | |
connect | Connects the card in the specific slot. | TCS |
loadcard | Loads the specified file into the card located in the specified slot, starts the card, and establishes a console connection between CLI and the TCS slave on the card. | |
read | Reads memory and hardware registers accessible by the TCS. For qualified personnel only. | |
test | Runs field diagnostic tests from the CLI. | |
write | Writes to TCS/board memory. For qualified personnel only. |
The CLI has two modes: normal and protected. Normal mode allows you to perform most routine operations. Protected mode provides access to additional commands for running hardware diagnostics and performing advanced troubleshooting.
Caution Protected mode is dangerous. You can bring the chassis down if you are not careful. |
Table 2-3 lists the protected commands and their functions.
Name | Function |
---|---|
connect | Connects the CLI to a card as a console. |
loadcard | Loads diagnostics. |
password | Changes the password for protected mode. |
set | Sets the values of certain CLI attributes in the runtime environment. Not all set commands are protected. Protected commands include set modem, set trap, and set tcs. |
setsnmp | Sets the value of a MIB object. |
shell | Executes a shell command and gives the user access to the LynxOS shell. |
write | Writes to TCS/board memory. For qualified personnel only. |
This section shows you some sample CLI commands and describes their syntax. All CLI commands start with the command name. Some commands require no further information; others require arguments such as file names, component names, or values. For a description of the CLI command syntax, see the LightStream 2020 CLI Reference Manual or the LightStream 2020 Command Line Interface (CLI) Reference Card.
Table 2-4 lists sample CLI syntax and command examples. In the syntax examples, optional arguments are surrounded by square brackets ([ ]); placeholders that you must replace with meaningful arguments are surrounded by angle brackets (< >).
Syntax | Command Example |
---|---|
exit | exit |
protected | protected |
help [<topic>] | help help setsnmp |
show <object type> [<component name>] <parameter> | show card 1 status show chassis cards |
set <object type> [<component name>] <parameter> [<value>] | set chassis traplevel debug set port 3.4 loop internal |
getsnmp <MIB-address> [<MIB-address>] | getsnmp cardName.4 pidName.23 |
Several CLI commands require port numbers. The port number must be entered in the card.port format. The card number is between 1 and 10 for line cards. The port number is between 0 and 7 for line cards. For example, to issue a show port command to port 4 on card 3 in card.port format, you would enter the following command:
show port 3.4
It is not always necessary to enter the full name of a CLI command or its argument. In most cases, if you enter enough letters to make the command or argument unambiguous, the CLI accepts the abbreviated name in most cases, not all. Once you type enough letters of a command name or command argument to make it unambiguous, you can usually use the [Tab] key to complete the name unless the argument is at the end of a very long command. (See the examples in Table 2-5.)
If you type... | The CLI completes the command. |
br[Tab] | browse |
walk[Tab] | walksnmp |
If you type,
cli> show por 4.2 statistics
the CLI cannot interpret the command because the component name (port) is not fully spelled out. However, the CLI does recognize por followed by a [Tab].
Any of the following commands would work:
cli> show port 4.2 statistics
cli> sho port 4.2 stati
cli> sho[TAB] por[TAB] 4.2 stati[TAB]
The CLI uses a set of line editing keys that is a subset of those found in the Emacs editor. In general you can use these line editing keys for any terminal type except a hardcopy terminal. Table 2-6 lists the line editing keys that are available in the CLI.
Key Sequence | Result |
---|---|
^A | Moves cursor to beginning of line. |
^B | Moves cursor back one space. |
^C | Interrupts command being executed. |
^D | Deletes character at cursor position. |
^E | Moves cursor to end of line. |
^F | Moves cursor forward one character. |
^K | Deletes all characters from cursor position to end of line. |
^L | Redisplays current line. |
^N | Scrolls forward through all commands that have been entered. (You must scroll backwards using ^P before this command provides any results.) |
^O | Toggles between overwrite mode and insert mode. |
^P | Scrolls backward through all commands, beginning with the most recent command. |
^R | Searches backward through all commands for a particular word that you specify at the question mark prompt. |
^S | Searches forward through all commands for a particular word that you specify at the question mark prompt. (You must scroll backward using ^P before this command provides any results.) |
^T | Transposes the character at the cursor position with the previous character. |
^U | Deletes all characters on line, regardless of cursor position. |
[Backspace] | Deletes character to left of cursor. |
[Rubout] | Deletes character to left of cursor. |
[Return] | Executes command. |
[Line feed] | Executes command. |
[Tab] | Completes command entry. |
This section describes how to start the CLI and how to perform basic CLI functions. The method you use to log in varies depending on the network management option you select. See Table 1-1 in the chapter entitled "The Command Line Interface" for a description of different network operation and management possibilities. If you choose an option that requires you to run the CLI on a Sun SPARCstation, see the LightStream 2020 Installation Guide for installation instructions.
If you use Telnet to reach the NP, check with your network administrator to be sure a basic configuration to define the IP address of that NP was entered during installation. If you access the CLI through one of the console ports, it is not necessary to have the IP addresses defined for the NP.
Step 1 If the CLI has been installed on your SPARCstation, log in to your SPARCstation. If you have trouble starting the CLI, ensure that the directory containing the CLI is included in your search path. (For more details, see the LightStream 2020 Installation Guide.)
Step 2 Open the CLI on the SPARCstation by typing cli at the prompt.
Step 3 Set the target switch by entering the following at the cli> prompt:
set snmp hostname {name|IPaddress}
where
name or IPaddress = the name (a text string) or IP address of the LS2020 switch to which you want to set the target. This is the switch to which the CLI commands are sent until you change the target again.
The following text appears on the screen when you have successfully logged in to the CLI:
If you are unable to start the CLI, you might see messages that indicate the shell cannot find the program, permission was denied because the CLI is not an executable file, or this user is not allowed to access the CLI. (See your network administrator if you need assistance.)
Step 1 From the terminal attached to the console (or modem) port on the console/modem assembly, enter the following at the TCS prompt:
connect <slot #>
where
<slot #> = The slot number of the NP card on which you want to run the CLI (1 or 2).
If you do not see the TCS prompt, enter a backquote followed by a period:
'.
Step 2 Enter the user name when you see the following prompt:
Step 3 Enter the password when you see the following prompt:
If you log in correctly to either the oper or npadmin account, the CLI opens automatically. If you log in to the fldsup or root account, the LSnode:2$ or LSnode:# prompt is displayed.
Step 4 To start the CLI from the LSnode:2 prompt, enter cli at the prompt:
Step 1 Determine the name and password for the user account you will be using. (See your network administrator if you need assistance.)
Step 2 Enter the following at the prompt on the system from which you are using Telnet:
telnet <IP address of the NP>
telnet <name>
The system displays the following information while it makes the connection:
Step 3 Enter the user name when you see the following prompt:
You usually log in to the oper account. However, you can also log in to npadmin, root, fldsup, or any other user account that your network administrator has defined.
Step 4 Enter the password when you see the following prompt:
If you log in correctly to either the oper or npadmin account, the CLI opens automatically. If you log in to the fldsup or root accounts, you are placed at the LSnode:2 prompt.
Step 5 To start the CLI from the LSnode:2 prompt, enter the following:
cli
The CLI browse command lets you travel through the MIB from the top down and display the value of any MIB object. The browse command is easy to use and allows you to move through the MIB even if you are not familiar with its structure. When the MIB tree branches, you can go in any direction. At any time you can return to the branch and go in a different direction. For an illustration of the MIB tree, see the LightStream 2020 CLI Reference Manual.
To travel down through the MIB tree and obtain the value of any MIB object you see, follow these steps.
Step 1 Enter the following at the cli> prompt:
browse [<mib-address>]
where
[<mib-address>] = An optional argument. If you do not enter a MIB address, the browse command starts at the top of the MIB tree (at the iso object). If you enter a MIB address, the browse command starts at the address you specify. For example, the MIB address can be mib2 or chassisInfo.
Step 2 Continue down the "org" subtree by entering the following at the browse> prompt.
1
Step 3 Exit by entering the exit or quit command at the browse> prompt.
Step 4 When you enter the browse command, the following information is displayed.
The highest level object of the MIB tree is the iso object and the only subtree below it is the org subtree.
Figure 2-2 shows an example of how you can use the browser to travel through the MIB and look at the values of the chassisId and chassisActiveIpAddr objects. (Bold type indicates user input.)
The next screen shows how you can access information quickly by entering the name of the subtree you want to look at. For example, instead of going through all of the steps to get to the chassisId as shown in the previous figures, you can enter the command browse chassisInfo as shown in Figure 2-3 and immediately access the chassisId object.
This section includes steps on how to perform these frequently used CLI functions..
To display a list of all CLI commands, enter help or a question mark [?] at the cli> prompt. Commands preceded by an asterisk can be used only in protected mode. All other commands are available in normal mode and protected mode. Figure 2-6 shows the output of the help command when you execute it without an argument.
To display detailed help on a particular topic, enter the following at the cli> prompt:
cli> help [<topic>]
where
[<topic>] = An optional argument that allows you to enter the name of a command on which you want help.
Figure 2-7 shows the output of the help command with the argument quit.
To display the options available for a particular command, enter a question mark [?] in a command to display a list of the options.
cli> show card 5 ?
The CLI displays a list of the objects that you can show for card 5. This command also redisplays the command that you typed, so that you do not have to retype it; just enter the name of the object you want to show as shown in the following example:
cli> show card 5 ?
all
name
processid
status
version
hardware
peak-cell-rate
ports
cli> show card 5
The show command is redisplayed after the help text.
You can continue to use the question mark to complete your show command as shown in the following example:
cli> show card ?
Card number required
cli> show card 5 ?
all
name
processid
status
version
hardware
ports
cli> show card 5 name
Card Name: ls-card-5
cli>
The CLI indicates that you must enter the card number. If you enter show card 5 ? at this point, the CLI displays a list of the options you can enter for card 5. It automatically redisplays show card 5. Then, you enter the option you want to view (name, for example).
To clear the screen, enter the following at the cli> prompt.
cli> clear
The screen clears and the cli> prompt reappears at the top of the screen.
You use the set cli command to set the attributes listed here. These attributes determine how the CLI operates. You use the show cli command to view the current settings of the attributes.
For example, to set the line edit attribute (the default is on), follow these steps.
Step 1 Enter the following at the cli> prompt:
set cli lineedit on
Step 2 To verify that the command has been executed, enter:
show cli lineedit
A screen similar to the following displays.
show cli lineedit
For more information about these attributes, see the LightStream 2020 CLI Reference Manual. It provides more information about the set and show commands, including command attributes, syntax, and arguments.
Your network administrator can provide you with the protected mode password, if you need access.
Caution Protected mode is dangerous. You can bring down the chassis if you are not careful. |
Step 1 To enter protected mode, type the following at the cli> prompt:
protected
Step 2 Enter the protected mode password when you see the following prompt:
If you enter the password correctly, you enter protected mode. The cli> prompt changes to *cli>. You can now execute protected mode commands in addition to normal mode commands.
If you enter an invalid password, the following message appears:
If you enter a command that requires protected mode while you are in normal mode, the following message appears:
Once you enter protected mode, you remain in that mode until you take explicit action to return to normal mode. To prevent unauthorized access, always return to normal mode when you are finished or before you leave your terminal. It is also good practice to log out whenever you leave your terminal to prevent unauthorized access.
To exit from protected mode, enter exit or quit at the *cli> prompt. The *cli> prompt reverts to cli>.
In an LS2020 switch with two switch cards (SA and SB), one card is the active switch card and the other card is the backup switch card. In case of a problem with the active switch card, the backup switch card automatically becomes the active switch card.
In addition, you can force either of the switch cards to become the active (or backup) switch card. This is called a planned cutover. You would do this, for example, if you planned to swap out the active switch card. When you force the backup switch card to become the (new) active switch card, the process forces the (original) active switch card to become the (new) backup switch card. The procedure below shows how to do this.
Step 1 Verify that the target switch is correct by entering the following at the cli> prompt:
show snmp
A screen similar to the following is displayed:
show snmp
Step 2 To determine which switch card is active, enter the following at the cli> prompt:
show chassis primaryswitch
A screen similar to the following is displayed:
show chassis primaryswitch
Step 3 At the cli> prompt, enter:
set chassis primaryswitch <slot #>
where
<slot #> = SA, SB
The switch card you designate is set to be the active switch card.
You set the target switch by issuing the set snmp hostname command.
These steps tell you how to display a list of all LS2020 switches in the network and then describe how to set the target switch.
Step 1 Enter the protected mode (see "Accessing Protected Mode " earlier in this chapter).
Step 2 To display a list of all LS2020 switches in your network and their IP addresses, enter the following at the *cli> prompt:
cli>
show gid ip
The following is a sample of the output from that command:
The first column lists all of the IP addresses of the LS2020 switches in the network. The fourth column lists the Advertising-NP host name.
Find the host name or IP address of the switch you want from this list.
Step 3 To change the target switch, enter the following at the *cli> prompt:
set snmp hostname {name|IPaddress}
where
{name | IPaddress} = The name (a text string) or IP address of the LS2020 switch to which you want to set the target. CLI commands are now sent to the target switch.
Step 4 To reset the target switch to the local switch, enter the following at the *cli> prompt:
set snmp hostname {localhost|128.0.0.1}
Step 5 To verify the name of the current target switch, enter the following at the *cli> prompt:
show snmp
When you issue commands that affect the operation of a particular switch, be sure to check that the target is set to the correct switch.
The log files include the trap log file, the configurator log file, and the collection files. You can use the LynxOS cbufpr command to display these files. Both commands begin the display with the oldest entry and end with the most current entry.
Fixed-size, circular files are used to limit the amount of space required to store data. When a log file becomes full, the oldest data is overwritten by new data.
Step 1 To display a circular file from the LynxOS shell, enter the following at the LSnode:2 prompt:
cbufpr [-h] [-v] [-all] [-tail] -<number> [-f] [-trap] <file> |more
To display a circular file from CLI, enter the following at the *cli> prompt:
shell "cbufpr [-h] [-v] [-all] [-tail] -<number> [-f] [-level] <file> |more"
where
-h=Displays this help message.
-v=Displays cbufpr version information.
Depending on the switches and file you select, the results displayed using cbufpr will vary. A screen similar to the one in Figure 2-8 is displayed if you enter shell "cbufpr -tail /usr/tmp/mma/mma.traplog" at the *cli> prompt.
Step 2 To exit from the log file display, press q.
By using the CLI show chassis cards command, you can quickly differentiate between edge cards and trunk cards and see how the physical configuration is set up. The display differs depending on your system configuration. A sample screen output looks similar to the following:
cli> show chassis cards
Slot 1: NP
Slot 2: LS Trunk
Slot 3: LS Edge
Slot 4: MS Trunk
Slot 5: OC3 Trunk
Slot 6: T3 Trunk
Slot 7: Cemac
Slot 8: Ethernet
Slot 9: FDDI
Slot 10: Cemac
Slot SA: Switch2
Slot SB: Empty
Once you see the cards that populate the system, you can display the port status for any ports. The LS2020 switch supports several interfaces to connect LS2020 systems to one another or to other devices.
Table 2-7 lists the supported port types, their configuration (edge or trunk port), and the line module necessary to configure a specific type of port.
Port Type | Configuration | Line Module |
---|---|---|
OC3 ATM UNI | Edge | Cell line card with OC3 access card (single mode or multimode) |
OC3 trunk | Trunk | Cell line card with OC3 access card (single mode or multimode) |
T3 ATM UNI1 | Edge | Cell line card with 8T3 access card or medium speed card with T3 medium-speed access card (2 port) |
T3 trunk | Trunk | Cell line card with 8T3 access card or medium speed card with T3 medium-speed access card (2 port) |
E3 ATM UNI1 | Edge | Cell line card with 8E3 access card or medium speed card with E3 medium-speed access card (2 port) |
E3 Trunk1 | Trunk | Cell line card with 8E3 access card or medium speed card with E3 medium-speed access card (2 port) |
Ethernet | Edge | Packet line card with Ethernet access card |
Fiber Ethernet | Edge | Packet line card with fiber Ethernet access card |
FDDI | Edge | Packet line card with FDDI access card |
CEMAC | Edge | Packet line card with circuit emulation access card |
Frame relay 1 | Edge | Low-speed card with low-speed access card |
Frame forwarding1 | Edge | Low-speed card with low-speed access card |
Low-speed trunk1 | Trunk | Low-speed card with low-speed access card |
|
The next sections include sample port status displays for a low-speed trunk port, an OC-3c ATM UNI port, and an Ethernet port. These sample displays include additional statistical data. The additional data is contained in parentheses and is preceded by the term Delta. To get this extra data, you must re-enter the show port command.
When you enter a show port command for a low-speed trunk port (for a second time), a display similar to the following appears:
cli> show port 2.0
Description: Low Speed Trunk Line Card Rev 1.0
Port Name:
Port Type: LS Trunk
MIB2 Type: ds1
Port MTU: 52 Octets
Port Speed: 1536000 bps
Admin Status: Up
Oper Status: Down
Oper loop: No Loop
Admin loop: No Loop
Last Oper Change 2 Hr 25 Min 5 Sec ago
Octets Rcvd: 0 (Delta:0 Rate:0.00/sec)
Normal Packets Rcvd: 0 (Delta:0 Rate 3.18/sec)
Multicast Packets Sent: 0 (Delta:0 Rate:0.00/sec)
Receive Errors: 0 (Delta:0 Rate: 0.00/sec)
Unknown Protocols Rcvd: 0 (Delta:0 Rate: 0.00/sec)
Octets Sent: 3618940 (Delta:934700 Rate:172.64/sec)
Normal Packets Sent: 69595 (Delta:1795 Rate: 3.32/sec)
Multicast Packets Sent: 0 (Delta: 0 Rate: 0.00/sec)
Discarded Output Packets: 0 (Delta: 0 Rate: 0.00/sec)
Output Errors: 0 (Delta: 0 Rate: 0.00/sec)
Port Type: v35
Oper CSU Type: Unknown
Admin CSU Type: Unknown
Oper DCE Rcv Bit Rate: 1536000 bps
Admin DCE Rcv Bit Rate: 1536000 bps
Oper DCE Xmit Bit Rate: 1536000 bps
Measured Bit Rate: 1536600 bps
Link Transmit Utilization 2 cells/sec
Admin Expected DTE Rate: 1536000 bps
Oper Net Interface Type: dte
Admin Net Interface Type: dte
Oper Protocol: T1 Trunk
Admin Protocol: T1 Trunk
LC Auto Enable State: Disabled
LC Debug Level 0
Port Data Cell Capacity: 3316 cells
Port Available Capacity 0 cells
Modem Status: DCD:0 DSR:1
When you enter a show port command for an ATM UNI port, a display similar to the following appears:
cli> show port 7.0
Description: LC1 OC3 Edge Line Card Rev 1.0
Port Name:
Port Type: OC3 Edge
MIB2 Type: sonet
OC3 Medium Type: Sonet (STS-3c)
Port MTU: 53 Octets
Port Speed: 155520000 bps
Admin Status: Up
Oper Status: Up
Transmit safety: Enabled
Oper loop: No Loop
Admin loop: No Loop
Last Oper Change: 2 Hr 5 Min 47 Sec ago
Octets Rcvd: 0 (Delta:0 Rate: 0.00/sec)
Normal Cells Rcvd: 0 (Delta:0 Rate: 0.00/sec)
Multicast Rcvd Cells: 0 (Delta:0 Rate: 0.00/sec)
Discarded Rcvd Cells: 0 (Delta:0 Rate: 0.00/sec)
Receive Errors: 25800 (Delta:38 Rate: 3.16/sec)
Unknown Protocols Rcvd 0 (Delta:0 Rate: 0.00/sec)
Octets Sent: 0 (Delta:0 Rate: 0.00/sec)
Normal Cells Sent: 0 (Delta:0 Rate: 0.00/sec)
Multicast Cells Sent: 0 (Delta:0 Rate: 0.00/sec)
Discarded Output Cells: 0 (Delta:0 Rate: 0.00/sec)
Output Errors: 26594 (Delta:15367 Rate: 1.46/sec)
Oper Protocol: ATM-UNI
Admin Protocol: ATM-UNI
Port Data Cell Capacity: 353208 cells
Port Available Capacity: 353208 cells
Link Transmit Utilization:0/cells/sec.
Clocking: internal
ATM-UNI VCI list:
-----------------
S Node Port VCI Node Port VCI IR IB MR MB*
spanky1 7.0 40->alfalfa2 5.0 40 0 0 1000 100
spanky1 7.0 40->alfalfa2 5.0 40 0 0 1000 100
*spanky1 7.0 40<-alfalfa2 5.0 40 0 0 0 0
*spanky1 7.0 41->alfalfa2 5.0 41 1000 100 1000 100
*spanky1 7.0 41<-alfalfa2 5.0 41 0 0 0 0
*spanky1 7.0 42->alfalfa2 5.0 42 1000 100 2000 200
Medium
Time Elapsed in current interval: 474
Number of valid interval(s): 8
Section
Status: <No defects>
Error seconds: 474
Severe error seconds: 474
Severe error seconds: 474
Severe framing error seconds: 474
Coding violations: 0
Continued
Line
Status: <No defects>
Error seconds: 0
Severe error seconds: 0
Unavailable seconds: 0
Coding violations: 0
Path
Path width: sts3cSTM1
Status: <STSLOP><STSRDI>
Error seconds: 0
Severe error seconds:
Unavailable seconds: 513
Coding violations: 0
When you enter a show port command for an Ethernet port, a display similar to the following appears:
cli> show port 8.0
Description: Ethernet CSMACD
Port Name: ECC Port 0
Port Type: Ethernet
MIB2 Type: ethernet-csmacd
Interface address: 8:0:8:0:28:78
Ethernet Medium Type: AUI
Port MTU: 1500 Octets
Port Speed: 10000000 bps
Admin Status: Up
Oper Status: Down
Last Oper Change: 2 Hr 18 Min 44 Sec ago
Octets Rcvd: 0 (Delta: 0 Rate: 0.00/sec)
Normal Packets Rcvd: 0 (Delta: 0 Rate: 0.00/sec)
MOctets Sent: 384 (Delta: 0 Rate: 0.00/sec)
Normal Packets Sent: 0 (Delta: 0 Rate: 0.00/sec)
Multicast Packets Sent: 6 (Delta: 0 Rate: 0.00/sec)
Discarded Rcvd Packets: 0 (Delta: 0 Rate: 0.00/sec)
Output Errors: 6 (Delta: 0 Rate: 0.00/sec)
Alignment Errors: 0
FCS Errors 0
Single Collision Frames: 0
Multiple Collision Frames: 0
SQE Test Errors 0
Deferred Transmissions: 0
Late Collisions: 0
Excessive Collisions: 0
Internal Mac Transmit Errors: 0
Carrier Sense Errors: 6
Excessive Deferrals 0
Frame Too Longs: 0
In Range Late Errors 0
Out of Range Length Fields: 0
Internal Mac Receive Errors: 0
Continued
WorkGroup List:
---------------
Card Port WgrpId Mode
---- ---- ------ ----
8 0 1 Include
Default Bridge Filter action is FORWARD
Default IP Filter action is FORWARD
Default IPX Filter action is FORWARD
NP Deliver: block
Port STB data:
Port State: disable
Priority: 128
Path Cost: 100
|