|
|
Audience ² Organization ² Related Documentation ² Notation
The LightStream 2020 Operations Guide is a task-oriented guide that describes how to operate a network of LightStream 2020 enterprise ATM switches. The guide presents an overview of network operation tasks, describes the command line interface (CLI), and provides procedures for monitoring switches and collecting statistics.
Your network should be fully installed and configured before you attempt to operate it. Refer to the LightStream 2020 Installation and Troubleshooting Manual for installation instructions and to the LightStream 2020 Configuration Guide for information on configuration.
The LightStream 2020 Operations Guide is intended for anyone who operates a LightStream network. This guide provides detailed procedures to help you operate the LightStream network after the network has been installed and configured.
Users of the LightStream document set are expected to have a general understanding of basic data communications concepts, some knowledge of UNIX, and a familiarity with the interfaces used by the devices connecting to their LightStream network.
It is recommended that you have a working knowledge of TCP/IP networks. For more information about TCP/IP networks, refer to Internetworking with TCP/IP, Volume 1, Principals, Protocols, and Architecture by Douglas E. Comer, 1991, Prentice-Hall, Inc. (ISBN 0-13-468505-9).
This guide is organized as follows:
The following is a list of LightStream manuals and other material relevant to LightStream users.
The system overview explains what a LightStream switch is and how it works. It also outlines ATM technology.
The site planning and cabling guide (SPCG) tells you how to prepare your site to receive LightStream hardware. It includes space, environmental and electrical requirements, rack selection guidelines, requirements for the management workstation, and information on cables and connectors.
The installation and troubleshooting manual (I&TM) tells you how to install LightStream hardware and software, how to diagnose hardware problems, and how to replace faulty hardware components.
The configuration guide provides the information you need to configure LightStream switches. It describes the configuration tools and how to use them. It describes the configuration database and defines all configurable attributes and their settings. The guide also provides step-by-step configuration procedures.
The administration guide describes LightStream network management functions such as setting up a new network, troubleshooting, and optimizing the load across trunks. The guide describes network management tools, then presents step-by-step procedures for performing the functions.
This manual presents an overview of LightStream traps (error and event messages) and a list of operational, SNMP, and informational traps generated by the LightStream switch.
The reference guide provides detailed descriptions of the syntax and functions of all CLI commands. It also indicates CLI equivalents of configuration procedures, describes the LightStream private MIB, and gives UNIX-style manual pages for selected LynxOS commands.
The reference card compactly summarizes the syntax and arguments of all CLI commands.
The release notes provide a software upgrade procedure and describe new features and special considerations, including information on known software bugs.
The LightStream command line interface (CLI) and configuration program both produce online help facilities.
Before attempting to install, configure, operate, or troubleshoot a network of LightStream switches, read the LightStream 2020 System Overview. This overview provides important background information about the LightStream product and the ATM technology on which the product is based. After reading the LightStream 2020 System Overview, refer to Table 1-1 to determine which manuals you should read next.
Table 1-1 LightStream Reading Path
In this document, several conventions distinguish different types of graphics and text.
Where to Begin ² Network Operations Tasks ² Tools for Network Operation
This chapter provides a list of activities you should complete before you attempt to operate your network of LightStream 2020 enterprise ATM switches. It then describes operations activities that you can perform on a LightStream network.
This chapter also explains some of the different ways you can operate your LightStream network, depending on your hardware and software. Once you determine how you will operate your network, you can use that information to determine whether you need to start the command line interface (CLI) or a third-party network management system (NMS). The LightStream CLI is described in detail in this guide. For information on a third-party NMS, refer to the documentation that came with the NMS.
Before you attempt to operate your network, each LightStream switch should be fully installed, powered on, and configured. The following checklist describes the tasks that should be complete before you begin operating your network. For information on these tasks, refer to the LightStream 2020 Installation and Troubleshooting Manual and the LightStream 2020 Configuration Guide, or check with your network administrator.
1. Read the LightStream 2020 System Overview and become familiar with the LightStream documentation set.
2. Check with your network administrator to be sure that the installation is complete, the network is powered up, and basic configuration information has been entered.
3. Check with your network administrator to be sure that the appropriate set-up procedures in the "Administrative Tasks" chapter of the LightStream 2020 Administration Guide have been completed.
4. Become familiar with CLI and any other network management tools available to you. (Refer to Chapter 3 and Chapter 4 in this guide for a discussion of the CLI.)
You can perform a wide variety of tasks on your LightStream network. You will perform some tasks every day and others only occasionally. This section lists the different types of tasks that you can perform.
This guide covers general monitoring and control and statistics and data collection. General monitoring and control refers to all the day-to-day activities you perform on the LightStream network, except for monitoring traps. Trap monitoring is discussed in the LightStream 2020 Administration Guide.
A LightStream network can be operated and managed in two different ways:
This section describes these two methods of network operation.
The LightStream switch comes with a configuration program called the configurator. The configurator is a user-friendly graphical interface that, in many cases, reduces configuration tasks to the simple click of a mouse button. A network administrator uses the configurator (for the most part) to manage a network of LightStream 2020 enterprise ATM switches. See the LightStream 2020 Configuration Guide for further details.
LightStream technology provides graphical displays of individual LightStream switches, cards, and ports via the LightStream monitor. In most instances, you will want to monitor the network with the LightStream monitoring tool. (See Chapter 5 of this guide.) However, if the monitor is unavailable to you, you can use the CLI commands in this document to perform many monitoring tasks.
Every LightStream switch includes a software program called the CLI. The CLI is a simple, line-based interface that runs on a LightStream switch or a Sun SPARCstation. You can access the CLI by connecting a terminal to a LightStream switch, by telnetting to the NP, or by running the CLI on a Sun SPARCstation.
In many instances you will want to perform operational procedures with the LightStream monitor or configurator. However, if the LightStream monitor or configurator is unavailable to you, you can use the CLI to perform many procedures. You should be aware, however, if you make changes to any configuration attributes, those changes you make may cause the local configuration database to be out of synchronization with the global database.
You can use any industry-standard, SNMP-compatible NMS to manage a LightStream network. The following three systems can be used with the LightStream switch:
You cannot configure a LightStream network using a third-party NMS. The LightStream configurator that runs on a Sun 4 workstation running SunOS 4.1.x/Solaris 1.1.x is used to configure LightStream switches and networks. For information on the LightStream configurator, refer to the LightStream 2020 Configuration Guide.
The LightStream documentation set does not provide instructions on how to use a third-party NMS. Use the product documentation for your third-party NMS to get specific instructions.
You can perform operations tasks in a number of different ways, depending on your hardware and software and whether or not traps are interleaved with, or separated from, your general monitoring and control functions. (See Table 2-1.) In most cases, you will perform all monitoring and control functions from a central site. Before operating your LightStream network, you need to know what method of operation you will use. Refer to the "Before You Begin" chapter of the LightStream 2020 Administration Guide or see your network administrator to find the appropriate method for your network. The following table describes possible network operation scenarios.
Table 2-1 Network Operation Scenarios Note You can access traps from a single CLI application running on an NP or from one application
of a third-party trap monitoring tool running on a workstation. If you attempt to display traps on a
second copy of either program running on another single processor (the NP or workstation), a
message is displayed indicating that traps have been intercepted by another user.
Introduction to the CLI ² User Accounts ² Commands Available in the CLI ² CLI Command Syntax ² Port Number Formats ² Normal and Protected Mode ² Command Completion Feature ² Line Editing Keys
This chapter is an introduction to the command line interface (CLI) that is used to operate and manage LightStream 2020 enterprise ATM switches. It contains a list of CLI commands and describes their syntax and port number formats. It also discusses normal and protected modes, the command completion feature, line editing keys, and the user accounts that are provided with your LightStream switch.
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. The CLI allows you to operate your LightStream network with or without a third-party network management system (NMS).
The CLI allows you to issue commands to only one node at a time. This means that you cannot view the status of several LightStream chassis by entering a single command. You must issue a separate command to each chassis.
You can access the CLI in three different ways:
Refer to Chapter 4 for detailed instructions on how to access the CLI using each of the methods described above. From the CLI, you can access any LightStream node in the network and perform network operations on that node
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 3-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 LightStream switch you are logged in to. However, you have the option of executing any of the commands listed in Table 3-1 on another LightStream switch. To do this, you must first specify the name of the other switch. This is called setting the target switch. Once you set the target switch, you can issue any of the commands in Table 3-1 to that switch.
Note If you run the CLI on a Sun SPARCstation, you must set the target switch before executing
any commands.
Table 3-1 Commands Available for Use with a Specified Target Switch
bflt, card, chassis, cli, collection, gid, nd, pid, port stb
Figure 3-2 shows a CLI session displaying the primaryswitch attribute for two switches. Before viewing the primaryswitch attribute on the second switch, the target switch is reset to the appropriate switch. (Callouts in the figure indicate when the target is reset.)
When you install your LightStream switch, the system automatically creates the four accounts shown in Table 3-2. None of these accounts has default passwords. Passwords for the accounts are usually set when the LightStream switch is installed. If you do not know the password for these accounts, see your network administrator.
Table 3-2 System Accounts, Purposes, and Prompts
When you access either the operator or the NP administration accounts, the LightStream switch automatically runs the CLI so you can start operations immediately. If you access either of the other accounts, the LightStream switch runs the bash shell or command interpreter and displays the bash (UNIX) prompt.
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 commands:
Table 3-3 lists the commands by type and gives a brief description of what each command does. For a detailed description of each command, refer to the LightStream 2020 Command and Attribute Reference Guide or to the LightStream 2020 Command Line Interface (CLI) Reference Card.
Table 3-3 Commands Available in CLI
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 full description of the CLI command syntax, refer to the LightStream 2020 Command and Attribute Reference Guide or to the LightStream 2020 Command Line Interface (CLI) Reference Card.
Table 3-4 shows 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 (<>).
Table 3-4 CLI Syntax and Command Examples
Several CLI commands require port numbers. The port number must be entered in the card.port format. The card number is between 1 - 10 for line cards. The port number is between 0 - 7 for a low-speed line card(LSC) and a packet line card (PLC) and 0 - 1 for a medium-speed line card (MSC) and a cell line card (CLC). For example, to issue a show all command to port 4 on card 3 in card.port format, you would enter the following command:
The CLI has two modes: normal and protected.
The protected commands are shown in Table 3-5.
Table 3-5 Protected Commands and Their Functions
It is not always necessary to enter the full name of a CLI command or its argument. If you have typed enough letters to make the command or argument unambiguous, the CLI will accept the abbreviated name. Once you type enough letters of a command name or command argument to make it unambiguous, you can use the [Tab] key to complete the name. (See the examples in Table 3-6.)
Table 3-6 CLI Command Completion Examples
The CLI cannot interpret the command because the component name (port) is not fully spelled out.
However, any of the following commands would work:
Note The system does, however, recognize and use an unexpanded command or argument, if the
word is unique and is the last item in the command line. Thus, you could issue either of the following
commands:
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 hard copy terminal.
Table 3-7 shows the line editing keys that are available from the CLI.
Table 3-7 CLI Line Editing Keys
Procedures to Start CLI ² Basic CLI Functions
This chapter describes how to log in to the command line interface (CLI) and perform basic CLI functions.
This section describes how to start CLI and begin operating your network using the CLI.
The method you'll use to log in will vary depending on the network management option you select. Refer to Network Scenarios in Table 3-1 for a description of different network operation and management possibilities. If you choose an option that requires you to run CLI on a Sun SPARCstation, refer to the LightStream 2020 Installation and Troubleshooting Manual for installation instructions. To start a workstation (Sun or non-Sun) or load and start a third-party network management system (NMS), refer to the documentation for the workstation and NMS.
This section tells you how to log in to CLI. Step-by-step instructions are given for the following access methods:
If you will be using 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 will be accessing the CLI from either a terminal or modem port, it is not necessary to have the IP addresses defined for the NP.
Note If you do not log in to either the oper or npadmin accounts on CLI, you must start CLI
manually (issue the cli command) from the bash$ (UNIX) prompt.
IREF
OBJ:4964
Step 2 Enter the following at the prompt on the system from which you are telnetting:
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. If you do not know the user name, see your network administrator.
Step 4 Enter the password when you see the following prompt:
If you do not know the password, see your network administrator.
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 bash$ prompt.
Step 5 To start CLI from the bash$ prompt, enter the following:
The slot number of the NP card on which you want to run CLI (1 or 2).
Step 2 Enter the user name when you see the following prompt:
If you do not know the user name, see your network administrator.
Step 3 Enter the password when you see the following prompt:
If you do not know the password, see your network administrator.
If you log in correctly to either the oper or npadmin account, CLI opens automatically. If you log in to the fldsup or root accounts, the bash$ prompt is displayed.
Step 4 To start CLI from the bash$ prompt, enter the following at the prompt:
Step 2 Open CLI on the SPARCstation by entering the following command at the prompt:
where[<flags>] = any of the following options:
Step 3 Set the target switch by entering the following at the cli> prompt:
The name (a text string) or IP address of the LightStream switch to which you want to set the target. This is the switch that CLI commands are sent to until you change the target again.
When you have successfully logged in to CLI, the following text appears on the screen:
If you are unable to start the CLI, you might see messages that indicate the shell cannot find a program, permission was denied because CLI is not an executable file, or this user is not allowed to access CLI. (See your network administrator if you need assistance.)
This section describes the following CLI functions:
This section explains how to access online help.
A list of all the commands available from CLI is displayed as shown in Figure 4-1. Commands preceded by an asterisk (*) can be used only in protected mode. All other commands are available in normal mode and protected mode.
An optional argument that allows you to enter the name of a command on which you want help.
Whenever you use the help command with an argument, the display includes the command name, a syntax statement, and a description, as shown in Figure 4-2.
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. (See Figure 4-3.)
You can continue to use the question mark to complete your show command as shown in Figure 4-4.
CLI indicates that you must enter the card number. If you enter show card 5 ? at this point, CLI displays a list of the options you can enter for card 5. CLI automatically redisplays show card 5. Then, you enter the option you want to view (name, for example).
This section describes how to clear your screen of the current display.
The screen clears and the cli> prompt reappears at the top of the screen.
This section explains how to set a number of CLI attributes. These attributes determine how CLI operates. The attributes that you can set are:
This attribute specifies whether or not the commands in a script file are displayed as they are executed by the source command. If echosource is set to yes, the commands are displayed. If echosource is set to no, the commands are not displayed.
Step 2 To verify that the command has been executed, enter the following at the cli> prompt:
Set lineedit to on to use the emacs-like editing commands on the command line. Set lineedit to off if you use a hard copy terminal.
Step 2 To verify that the command has been executed, enter:
This attribute specifies whether the LightStream switch logs all input to and output from CLI. To keep a log of CLI activity, enter a log file name as the value shown in Step 1. Otherwise, set the value to off.
Note You cannot view this log file unless you use the set cli log off command or until the CLI
session in which the file was opened is closed. Logging from subsequent CLI sessions will be
appended to this file. No default log file name exists.
Step 2 To verify that the command has been executed, enter the following at the cli> prompt:
This attribute specifies the type of terminal you are using. Valid terminal types include VT100 and xterm. A complete list of valid terminal types can be found in the /etc/termcap file on your LightStream switch.
Step 2 To verify that the command has been executed, enter the following at the cli> prompt:
This attribute resets the CLI timer, which indicates the elapsed time since CLI was restarted or since this timer was reset.
Step 2 To verify that the command has been executed, enter the following at the cli> prompt:
This attribute specifies the severity level of traps to be displayed by CLI or sets the trap level so that no traps are displayed. (Refer to the LightStream 2020 Administration Guide for information on trap severity levels.)
Step 2 If you are setting the CLI traplevel attribute to off, enter the following additional command at the cli> prompt:
Step 3 To verify that the command has been executed, enter the following at the cli> prompt:
A screen similar to the following is displayed:
This attribute turns on the debugging mode. This feature is available in protected mode only and is used for development and testing purposes.
Step 2 To verify that the command has been executed, enter the following at the cli> prompt:
A screen similar to the following is displayed:
This procedure shows you how to access protected mode. Your network administrator can provide you with the protected mode password, if you need access.
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. (Refer to Procedure 2: Exiting Protected Mode, below.) 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.
When you exit protected mode, the *cli> prompt reverts to cli>.
In a LightStream switch with two switch cards (SA and SB), one card is the active switch card and the other card is the backup switch card (a hot spare). In case of a problem with the active switch card, the backup switch card automatically becomes the active switch card, assuming the IP address associated with 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.
Note This procedure is different from forcing the TCS hub on the switch card to become the
primary or secondary TCS hub. That procedure is part of the diagnostic process and is described in
the LightStream 2020 Administration Guide.
A screen similar to the following is displayed:
Step 2 To determine which switch card is the active, enter the following at the cli> prompt:
A screen similar to the following is displayed:
Step 3 At the cli> prompt, enter:
The switch card you designate is set to be the active switch card. It takes approximately four seconds to switch the active and backup switch cards.
If you are running CLI on an NP, CLI commands are executed on the LightStream switch you are logged in to. You can issue some CLI commands to a different LightStream switch. Table 3-1 lists those commands. However, to execute any of those commands on another switch, you must first specify the name of the other LightStream switch. This is referred to as setting the target switch. You set the target switch by issuing the set snmp hostname command.
Note If you are running CLI on a Sun workstation, you must set the target switch before executing
any other CLI commands.
This procedure tells you how to display a list of all LightStream switches in the network and then describes how to set the target switch.
Step 2 Enter the protected mode password when you see the following prompt:
Step 3 To display a list of all LightStream switches in your network and their IP addresses, enter the following at the *cli> prompt:
The following is a sample of the output from that command:
Step 4 Find the name or IP address of the switch you want from this list.
Step 5 To change the target switch, enter the following at the *cli> prompt:
The name (a text string) or IP address of the LightStream switch to which you want to set the target. This is the switch that CLI commands are sent to.
Step 6 To reset the target switch to the local switch, enter the following at the *cli> prompt:
Step 7 To verify the name of the current target switch, enter the following at the *cli> prompt:
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.
To display a circular file from CLI, enter the following at the *cli> prompt:
Step 2 To exit from the log file display, press q.
Depending on the switches and file you select, the results displayed using cbufpr will vary. A screen similar to the following is displayed if you enter shell "cbufpr -tail /usr/tmp/mma/mma.traplog" at the *cli> prompt.
This section explains how to execute a CLI script file. (Refer to the LightStream 2020 Administration Guide for instructions on how to create your own CLI script files.)
The name of the CLI script file containing CLI commands. The file name must be surrounded by quotes. If you are not running in the same directory that contains the CLI script file, the filename must be the full path name of the file.
The results of the source command depend upon the contents of the CLI script file that it runs and the value of the CLI attribute called echosource. If you have turned on the echosource attribute in CLI (the default), the command being executed by the CLI script file is echoed to the screen preceded by a plus sign (+).
Introduction to Monitoring ² Monitoring Hardware Components from CLI ² Using the LightStream Monitor ² Monitoring Software Components from CLI ² Monitoring the Test and Control System ² Accessing the MIB Tree
This chapter tells you how to determine the status of LightStream 2020 enterprise ATM switches and their components. It shows command examples and explains how you can obtain additional information.
The LightStream monitor is described in this chapter. The monitor displays a graphical representation of a LightStream switch, its cards and ports.
This chapter discusses the browse command, which allows you to view the value of any object in the LightStream management information base (MIB). Information about every object in a LightStream switch is stored in the MIB. You can issue CLI (command line interface) commands to retrieve and display the MIB information so you can determine how a switch is configured and how it is operating. This chapter also discusses the show command. When you issue a show command, the switch retrieves the requested information from the MIB. You may see a collection of MIB attributes displayed or you may see only a single attribute.
Two tools are available for monitoring: the LightStream monitor program and the CLI. In the CLI, you use the show command to monitor a switch or its components. In the monitor program, you click on components to display information about them. You can monitor the following LightStream components and subsystems:
CLI procedures to monitor all of these components and subsystems, except traps, are described next. Monitoring traps is described in the LightStream 2020 Administration Guide. Use of the LightStream graphical monitor to view switches, cards, and ports begins in the section entitled "Using the LightStream Monitor."
This section provides the procedures for monitoring the hardware components of a LightStream switch:
This procedure allows you to monitor the chassis. The information displayed by this procedure applies to the LightStream switch.
If you need instructions on changing the target switch, refer to the subsection entitled "Forcing a Switch Card to Become Active or Backup."
Step 2 Enter the following at the cli> prompt:
When you enter show chassis all, information similar to the following is displayed:
Note The column labeled S indicates the state of the connection. If there is an asterisk (*) in the
state column for a particular connection, the connection is down. If the state column is blank, the
connection is up.
IREF
OBJ:6096
If you enter any parameter except all, a subset of the screen shown above is displayed. For example, if you enter the command show chassis agent, information similar to the following is displayed:
This procedure allows you to monitor the cards in the LightStream switch. You can monitor network processor (NP) cards, edge cards, trunk cards, and switch cards. You select the card you want to monitor by specifying its card number (slot number). When you specify a card, you also get information on its associated access card.
If you need instructions on changing the target switch, refer to the subsection entitled "Forcing a Switch Card to Become Active or Backup."
Step 2 Enter the following at the cli> prompt:
The results of this command will very, depending on the type of card in the slot. If you enter any parameter except the all parameter, a subset of the attributes is displayed.
When you enter show card 5 all, information similar to the following (for a low speed edge card) is displayed:
The csumon tool, available from the bash shell, lets you monitor the DSU/CSU for the following:
In addition, you can use csumon to issue commands to an external DSU/CSU attached to a low-speed interface.
You can obtain CSU statistics by connecting to an external data service unit/channel service unit (DSU/CSU) from a LightStream switch through a serial line. This provides a terminal to the DSU/CSU. You use its own interface to set up and monitor the DSU/CSU. (Refer to the documentation for the DSU/CSU for details.)
Step 2 To access the bash prompt, log in as root or fldsup on the LightStream switch to which the DSU/CSU you want to monitor is attached.
Step 3 Test the connection by using the following command:
The target switch card and port number in the LightStream switch, entered in .card.port format (card 2 - 10; port 0 - 7).
Figure 5-5 shows a screen displaying the kind of information you might see in a DSU/CSU status display. The display you see will probably look different, depending on the DSU/CSU you are using.
Step 4 While the statistics are displayed, you can enter the input shown below to refresh the screen or alter the counter display.
Step 5 Terminate the display by pressing ^C. This returns you to the bash$ prompt.
Step 6 To learn about commands you can issue to the DSU/CSU, consult its documentation. To obtain help on csumon, enter the following command at the bash$ prompt:
The medium-speed line card has a built-in DSU/CSU. Use the procedure below to monitor and display the DS3 MIB statistics for MSC ports. MSC CSU statistics are available using the standard DS3 MIB variables.
Step 2 Enter the following at the bash prompt:
The target switch card and port number in the LightStream switch, entered in .card.port format (card 2 - 10; port 0 - 1).
A screen similar to Figure 5-6 will be displayed. Although you enter only one port number, information for both ports on the MSC is displayed.
The DS3 MIB maintains these counters over a 24-hour period in 15-minute intervals. The Total column in the display includes up to 96 complete intervals. The Current column includes all counts that will make up the next complete interval. The Intrvl column shows the selected complete interval (from 1 to 96), depending on the actual number of complete intervals. The values that change are updated once per second.
Table 5-1 explains the counters displayed in Figure 5-6.
Step 3 While the statistics are displayed, you can enter the input shown below to refresh the screen or alter the counter display.
Step 4 Terminate the display by pressing ^C. This returns you to the bash$ prompt.
Step 5 To obtain help on csumon, enter the following command at the bash$ prompt:
This procedure allows you to monitor the ports on a particular card. You can look at information for a single port, a collection of ports, or a range of ports.
If you need instructions on changing the target switch, refer to the subsection entitled "Forcing a Switch Card to Become Active or Backup."
Step 2 Enter the following at the cli> prompt:
The number of the port for which information will be displayed. The port number is in card.port format (card = 2 - 10; port = 0 - 7 for ports on an LS line card or 0 - 1 for ports on a CLC, PLC, or MSC).
An example for some of the port types is shown in this section. When you enter show port 5.0 all for an MS trunk port, information similar to the following is displayed:
Note When the Operational Status for the trunk port is down, the Port Unreserved Capacity field
shows the capacity that has been configured for the trunk port, rather than a capacity of zero (0).
When you enter show port 3.0 all for a frame forwarding port, information similar to the following is displayed:
This procedure allows you to monitor the modem port on the switch card's console/modem assembly. If you have a redundant switch card, you can monitor the modem port on either the active or backup switch card. (This command is not used for monitoring modems connected to line card ports.)
If you need instructions on changing the target switch, refer to the subsection entitled "Forcing a Switch Card to Become Active or Backup."
Step 2 Enter the following at the prompt:
SA or SB for the cli> switch cards
password (Only available from protected mode.)
When you enter show modem sa all, information similar to the following is displayed:
This procedure tells you how to monitor the status of your redundant components (switch cards, NP, and power supplies).
If you need instructions on changing the target switch, refer to the subsection entitled "Forcing a Switch Card to Become Active or Backup."
Step 2 To look at the status of switch cards, enter the following at the cli> prompt:
This command indicates which switch card is the active switch card. If you have a second switch card, you can assume it is the backup switch card.
Step 3 To look at the slot associated with each of the NPs, enter the following at the cli> prompt:
This command displays a number of details including the slot for the active NP, the slot of this NP, and the system up time. The system up time indicates how long this NP has been up.
Step 4 To look at the status of power supplies, enter the following at the cli> prompt:
This command displays the status and type of the two power supplies, A and B.
The following shows the output for the three commands described in the procedure above:
The LightStream monitor provides a graphical display of individual LightStream switches, cards, and ports. When the monitor is opened, it displays the front of a LightStream switch with bulkheads for the cards as they appear in the actual switch. Information pertinent to the switch is displayed above the bulkheads. This section shows you how to access the monitor to display switches, cards, and ports. You must have a color monitor to use the monitor software.
Step 2 Invoke the LightStream monitor by selecting it from the HP OpenView menu or by entering the following command at the system prompt:
is the name of the node you want to view
A display appears showing the front view of the LightStream switch, its components, and their status. The area above the bulkhead in the display contains general indicators and summary information about the switch. For a description of the LEDs displayed on each card in the monitor, refer to the "Hardware Description" chapter of the LightStream 2020 Installation and Troubleshooting Manual.
Step 3 To select an object in the display, point the mouse at the object and click on it with the left mouse button. The object will appear highlighted.
Step 4 To display the access card for a particular line card, click on the screw above it.
Step 5 To display more information for a particular object in the display, point the mouse at the object and double click with the left mouse button. If more information is available for the object, a screen will appear with the relevant information.
Step 6 Select Show All Access Cards from the Slot menu to obtain a rear view of the switch.
Step 7 To select a menu option from the menus at the top left of your display:
The possible options are shown in Table 5-2. All menu options may not be available at all times. Availability depends on the display in the window. Available options are highlighted.
Table 5-2 Monitor Menu Options
Step 8 You can also display the additional information for an object (discussed in Step 5) by selecting the object with a single click of the left mouse button and then choosing the Open Selected Object option from the Slot menu.
The color of the objects displayed by the monitor provide you with valuable information, as shown in Table 5-3. As you view an object with the monitor, note its color and refer to the table for an explanation. LEDs on the rear view of the switch are unreadable and appear in white.
Table 5-3 Monitor Object/Color Display Explanations
Step 9 To iconify a monitor display, click in the Close box in the bar at the top of the window.
Step 10 To exit the monitor, select Exit from the File menu.
This section provides procedures to monitor the software components (ATM UNI, frame relay, frame forwarding, Ethernet, FDDI, and OC3 connections; CLI; collector; GID; ND; processes; and SNMP) of a LightStream switch.
This procedure allows you to monitor the ATM UNI virtual channel identifiers (VCIs) configured on a particular ATM UNI port. It provides you with information on the individual connections configured on each port. This information is available for ATM UNI ports only.
If you need instructions on changing the target switch, refer to the subsection entitled "Forcing a Switch Card to Become Active or Backup."
Step 2 To get a list of all VCIs configured on a particular ATM UNI port, enter the following at the cli> prompt:
The number of the port for which information will be displayed. The port number is in card.port format (card = 2 - 10; port =0 - 1 for ports on an MS line card or CLC).
Step 3 Once you have a list of all ATM-UNI VCIs, you can look at a particular VCI by entering the following at the cli> prompt:
The number of the VCI for which information will be displayed.
When you enter show port 6.0 vci 16, information similar to the following is displayed:
This procedure allows you to monitor individual data link connections configured on frame relay ports. These connections are recognized by their data link connection identifiers (DLCIs).
If you need instructions on changing the target switch, refer to the subsection entitled "Setting the Target Switch for CLI Commands."
Step 2 To get a list of all data link connections configured on a particular frame relay port, enter the following at the cli> prompt:
The number of the port for which information will be displayed. The port number is in card.port format (card = 2 - 10; port = 0 - 7).
Step 3 Once you have a list of DLCIs, you can look at a particular circuit, by entering the following at the cli> prompt:
The DLCI number for which information will be displayed. The DLCI number must be between 16 and 991.
Note See the LightStream 2020 Configuration Guide for a description of the attributes displayed
by the show port commands and for information on setting them with the configurator. See the
LightStream 2020 Command and Attribute Reference Guide for information on setting port
attributes with the CLI.
When you enter show port 10.7 dlci 141, information similar to the following is displayed:
This procedure allows you to monitor the attribute settings for the CLI program.
When you enter show cli, information similar to the following is displayed:
The collector allows you to run up to 25 collections at one time. You can set up the collections to save user-defined data at a user-defined time interval and you can use this data for future analysis. This procedure describes how to monitor the status of a particular collection. For further information on creating collections, see Chapter 6.
If you need instructions on changing the target switch, refer to the subsection entitled "Forcing a Switch Card to Become Active or Backup."
Step 2 If you do not know what collections have been defined, enter the following at the cli> prompt:
This command lists the number of all the collections defined on the LightStream switch. You may see a display similar to the following:
This display tells you that collection numbers 2, 3, 5, and 6 have been defined.
Step 3 To look at the status of a particular collection, enter the following at the cli> prompt:
The number of any collection that has been defined. If you do not enter a collection number, CLI displays all collections that have been defined.
When you enter show collection 5, information similar to the following is displayed:
This procedure allows you to monitor the status of the global information distribution (GID) software.
If you need instructions on changing the target switch, refer to the subsection entitled "Forcing a Switch Card to Become Active or Backup."
Step 2 Enter the following at the cli> prompt:
When you enter show gid all, information similar to the following is displayed:
If you enter any parameter except all, a subset of the attributes is displayed.
This procedure allows you to monitor the status of the neighborhood discovery (ND) software. This information can tell you what hardware configuration the running software is using or the neighbors of the switch.
If you need instructions on changing the target switch, refer to the subsection entitled "Forcing a Switch Card to Become Active or Backup."
Step 2 Enter the following at the cli> prompt:
When you enter show nd all, information similar to the following is displayed:
If you enter any parameter except all, a subset of the attributes shown above is displayed.
This procedure allows you to monitor the status of a particular process. You select the process you want to monitor by entering either its number or name.
If you need instructions on changing the target switch, refer to the subsection entitled "Forcing a Switch Card to Become Active or Backup."
Step 2 If you do not know which processes are running, enter the following at the cli> prompt:
This command lists the process identification (pid) numbers and alias names of all the processes running on this LightStream switch. The pid numbers follow the term "Name: lwmaTrapCliAlias." and the alias names follow the term "Value:". For example, you may see
Step 3 Choose the processes that you want to monitor from this list.
Step 4 To display the status of a particular process, enter the following at the cli> prompt:
The number of the process or the alias name of the process from which you want to display status.
When you enter show pid 9 all, information similar to the following is displayed:
The same information is displayed when you enter show pid lcc9 (The lcc9 entry is the alias name for process 9).
If you enter any parameter except all, a subset of these attributes is displayed.
This procedure allows you to monitor the way in which SNMP operates. SNMP operation is controlled by a number of parameters that are set to default values when the system is started. These parameters can be changed using the set snmp command. (See the subsection entitled "Creating a Collection" for a discussion of this command.)
Information similar to the following is displayed:
This section gives you procedures to monitor the Test and Control System (TCS).
The procedure allows you to monitor the values collected by the TCS on a particular card in the chassis. The cards you can monitor are in slots 1 - 10, SA, and SB.
If you need instructions on changing the target switch, refer to the subsection entitled "Forcing a Switch Card to Become Active or Backup."
Step 2 Enter the following at the cli> prompt:
Table 5-4 describes <parameter1> and <parameter2>.
Table 5-4 Parameter Options—show tcs Command
When you enter show tcs 1 all, a display similar to Figure 5-18 is displayed. If you use any value except all for the argument, a subset of this information is displayed.
This section explains how to use the browse command. 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. Refer to the LightStream 2020 Command and Attribute Reference Guide for an illustration of the MIB tree.
Note While using the browse command, you enter a number to select the next branch of the MIB
tree. These numbers are not related to the actual MIB addresses for the objects shown in the
LightStream 2020 Command and Attribute Reference Guide.
This procedure allows you to travel down through the MIB tree and obtain the value of any MIB object you see.
If you need instructions on changing the target switch, refer to the subsection entitled "Forcing a Switch Card to Become Active or Backup."
Step 2 Enter the following at the cli> prompt:
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 3 Continue down the "org" subtree by entering the following at the browse> prompt.
Step 4 Exit by entering the exit or quit command at the browse> prompt:
The following example shows the information that is displayed when you enter the browse command.
The highest level object of the MIB tree is the iso object and the only subtree below it is the org subtree.
Figure 5-19 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. (User input is shown in bold.)
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 Figure 5-19, you can enter the command browse chassisInfo as shown in Figure 5-22 and immediately access the chassisId object.
Using LightStream Statistics ² Using Data Collection
Statistics are counters collected by a LightStream 2020 enterprise ATM switch. This chapter tells you how to monitor and evaluate the state and performance of your LightStream switch by reviewing and sometimes processing the statistics.
LightStream statistics are stored in MIB objects. Examples of statistics include the following MIB objects:
Many statistics of interest for the LightStream switch are defined in the Frame Relay DCE MIB, FDDI MIB, Ethernet MIB, OC3 MIB, and MIB-2. For a complete list of MIB objects, refer to the LightStream 2020 Command and Attribute Reference Guide.
All statistics in a LightStream switch are initialized at system startup. When they reach their maximum value (or if you do another startup), they are reset to 0. You can use the collector to collect statistics at regular intervals. Refer to the subsection entitled "Using Data Collection" for more information.
This procedure shows you how to view port statistics with the show command. All of the information displayed for port interfaces is generic and applies to all interfaces, regardless of the interface type.
If you need instructions on changing the target switch, refer to the subsection entitled "Forcing a Switch Card to Become Active or Backup."
Step 2 Enter the following at the cli> prompt:
The port number for which statistics will be displayed. The port number is in card.port format (card = 2 - 10; port = 0 - 7).
When you enter show port 2.0 statistics, information similar to the following is displayed:
The first time you request statistics for a particular port, you see a display like the one shown in Figure 6-1. However, if you again show statistics on that port, the current value of each statistic is displayed with additional information. The additional information shows the amount that each statistic increased since your last request and the rate at which the statistic is changing. The following figure shows the statistics display when you enter show port 2.0 statistics anytime after the first time.
In addition to displaying statistics, the LightStream switch provides a data collection facility called the collector. The collector allows you to define a set of MIB objects, collect their values at regular intervals, and save the information in a file. The set of MIB objects and their collected values is a collection.
The collector maintains a table called collectTable in the private section of the LightStream MIB. It uses the information in this table to control the operations of its collections. A sample collection table is shown in Table 6-1. Each row defines a collection.
Table 6-1 Sample Collection Table
You can use the begintime and endtime arguments to control the collection duration and the filesize argument to control the collection size. If you do not specify the begintime and endtime arguments, the collection runs continually.
The collector can run up to 25 collections simultaneously on a particular LightStream switch. If you attempt to start more than 25 collections, any additional collections will have an operational status of waiting. When the number of running collections falls below 25, the next waiting collection will begin running.
You can collect any set of MIB objects you want at any time interval you want. For example, you can define a collection of ifInErrors and ifOutErrors objects for a particular set of ports to be collected once an hour or once a day. Once the collection is started, the specified information is collected at the correct interval and appended to the collection file.
The collector automatically generates the file and file name for every collection that you create. The file name is of the form collect.<collection number>. All collection files are placed in the /usr/tmp/collector directory. Sample names are /usr/tmp/collector/collect.6 and /usr/tmp/collector/collect.128.
Collection files are circular ASCII files containing the time each object was collected, the object name, and the object value. Figure 6-3 shows a sample collection file. When the circular file is full, the oldest data is overwritten by newer data. Files are displayed in chronological order from the oldest entries to the newest.
You can view and use the collection files as they are or you can process the data. (You may want to sort the data or make calculations to determine when changes in performance or state occur.)
To begin a new collection, follow the procedures described in this chapter in the order listed below.
You may also want to perform the following functions on your collections.
Each of these procedures is explained in the sections that follow.
This procedure tells you how to create a collection. It sets up a row in the collectTable object for a collection with the number you specify.
The name for the SNMP community with read/write privileges that you want to access.
Step 2 Enter the following at the cli> prompt:
An integer between 1 and 128, inclusive.
Step 3 To verify that the collection has been created, enter the following at the cli> prompt:
This lists the collection numbers that have been created for this switch.
If you enter the number of a collection that already exists, a message is displayed telling you that you cannot create that collection.
If you enter the walk collectIndex command, you will see a display similar to the following:
The numbers that appear after Value: are the numbers of the collections that have been created. The display above indicates that collection numbers 2, 3, 5, and 6 have been defined.
This procedure shows you how to set the time interval for collecting data for a particular collection.
The name for the SNMP community with read/write privileges that you want to access.
Step 2 Enter the following at the cli> prompt:
The number of a collection for which you are setting the collection interval.
The interval (in seconds) at which you want to collect the data. The default is 60 seconds. Typical intervals include:
Table 6-2 Collection Interval Details
Step 3 To verify the collection interval for a particular collection, enter the following at the cli> prompt:
Check the information in the Collection Interval field.
This procedure explains how to specify a MIB object and add or delete it from a collection. Each MIB object is added or deleted individually.
The name for the SNMP community with read/write privileges that you want to access.
Step 2 If you do not know which MIB objects are available for collection, use the browse command or the walksnmp command to list the objects that are available.
Step 3 To add MIB objects to a collection, enter the following at the cli> prompt:
The number of a collection for which you are adding objects.
The MIB name or address of the object you want to add to the collection. The MIB address must include the instance identifier as described in the "SNMP Commands" chapter of the LightStream 2020 Administration Guide.
For example, to collect the ifInOctets MIB object for ports 1 and 2 on card 3, enter the following at the cli> prompt:
Step 4 To verify that the object(s) you specified in Step 3 will be collected, enter the following from the cli> prompt:
Check the information in the Collection Items field. You should see the MIB object(s) listed that you added to the collection.
The name for the SNMP community with read/write privileges that you want to access.
Step 2 To delete objects from a collection, enter the following from the cli> prompt:
The number of a collection for which you are deleting objects.
The MIB name or address of the object you want to delete from the collection.
Step 3 To display the current objects to be collected for the collection, enter the following from the cli> prompt:
Check the information in the Collection Items field. The MIB object you specified should not appear in the display.
This procedure tells you how to specify the size of a collection file.
The name for the SNMP community with read/write privileges that you want to access.
Step 2 Enter the following at the cli> prompt:
The number of a collection for which you are specifying the collection file size.
The size of the collection file in Kbytes. The default is 100 Kbytes. The actual file size is 100 x 1024 bytes.
Step 3 To display the size of the collection, enter the following from the cli> prompt:
Check the information in the Collection File Size.
This procedure tells you how to start the collector. Starting the collector causes the LightStream switch to collect the specified MIB objects (at the defined times) and store the data in the collection file.
The name for the SNMP community with read/write privileges that you want to access.
Step 2 Enter the following at the cli> prompt:
The number of a collection that you are starting.
Step 3 To confirm that the collection has been started, enter the following from the cli> prompt:
Look at the Collection Status field.
If the Collection Status field status is Valid, the collection has been started and is running. If the status is Waiting, you have more than 25 collections running on this switch, or the collection is scheduled to start at a future time.
This optional procedure tells you how to specify a start and end time for a collection.
The name for the SNMP community with read/write privileges that you want to access.
Step 2 To specify the start time, enter the following from the cli> prompt:
The number of a collection for which you are specifying the start time.
The time when you want the collection to start. Enter the time in [[[yy:]mm:]dd:]hh:mm:ss format. The default is the current time and date.
Step 3 To determine collection start time, enter the following from the cli> prompt:
The name for the SNMP community with read/write privileges that you want to access.
Step 2 To specify the stop time, enter the following from the cli> prompt:
The number of a collection for which you are specifying the end time.
The time when you want the collection to stop. Enter the time in [[[yy:]mm:]dd:]hh:mm:ss format. The default is the time when the LightStream system clock runs out (for example, Thu Dec 31 23:59:59 2037).
You can view the collection file from the command line interface (CLI) or you can copy it to a third-party network management system (NMS) or workstation where you can view it or process it.
Two procedures can be used to view the collection from CLI. The first is used if you are running CLI on the network processor (NP) of the LightStream switch on which the collection is being run and the second is used if you are running CLI on a remote NP or Sun SPARCstation.
Note You must be in protected mode to view a collection if CLI is running from a remote NP or
Sun SPARCstation, or if you are moving the collection file to a third-party NMS or workstation.
Refer to the subsection entitled "Accessing
Protected Mode" for instructions on accessing protected mode. You must also have an
account (user name and password) for the workstation or host to which you are moving the collection
file. Your network administrator should provide you with this information.
For more information on the circular buffer print (cbufpr) command, see the subsection entitled "Displaying Log Files."
Step 2 Enter the protected mode password when you see the following prompt:
Step 3 Enter the following at the *cli> prompt:
The LightStream switch responds with a message similar to the following:
Step 4 When you see the following prompt, enter the user name for the account on the workstation or host to which you are moving the collection file:
Step 5 Enter the password for the account when you see the following prompt:
If you enter the user name and password correctly, the workstation or host displays information similar to the following:
Step 6 Enter the following at the ftp> prompt:
The name of the file that identifies the chassis or appropriate directory name for the file. For example, if you are moving a trap log for a switch called Light5, the new name could be mma_Light5.traplog.
Step 7 To exit the file transfer program and return to CLI, enter the following at the ftp> prompt:
The put command sends the log file to the specified workstation or host. The system tells you when the transfer is complete.
You can use a standard UNIX command such as more or cat to view the collection file on the workstation or host. You can also use the text file with any text processing tool you have available.
Figure 6-3 shows a sample of a collection file that you may see if you perform either procedure 1 or 2 above.
This procedure tells you how to get a list of all defined collections. It also explains how to determine the status and contents of any defined collection.
The walksnmp command displays a list of all collections that have been defined, as follows:
The numbers following the term Value: are the collection numbers that have been defined.
Step 2 Once you know the numbers of the collections that have been defined, you can determine the contents and status of each collection by typing the following from the cli> prompt:
If you don't enter a collection number, all collections are displayed.
The following is an example of the output that is displayed when you enter show collection 10:
This procedure explains how to temporarily stop a collection. Use this procedure if you may want to resume this collection at a later time. If you restart this collection at a later time, new data is appended to the existing collection file.
The name for the SNMP community with read/write privileges that you want to access.
Step 2 Enter the following at the cli> prompt:
The number of a collection you are stopping.
Step 3 To determine if a collection has been stopped, enter the following from the cli> prompt:
The show collection <collection number> command displays the Collection Status field. If the status is Under Creation, the collection has been stopped.
If a collection has been restarted, the Collection Status changes from Under Creation to Valid.
If you have 25 collections running and you stop one or more of them, collections with a Collection Status of Waiting may be started as a result. (In this case, you may not be able to restart the collection you just stopped, unless you halt another collection.)
This procedure tells you how to delete the definition of a collection. It deletes the definition of the collection from the collecTable, but it does not delete the collection file itself. Once a collection is deleted, you can no longer restart it because its definition no longer exists.
The name for the SNMP community with read/write privileges that you want to access.
Step 2 Enter the following at the cli> prompt:
The number of a collection to be deleted.
Step 3 To list the collection numbers that have been defined for this switch, enter the following from the cli> prompt:
The walksnmp collectIndex command displays the collection numbers that have been defined for this switch. The number that you deleted should not appear on this list.
The following shows a list of commands used to create, define, and then start a collection. This sample collection is defined to collect the ifInErrors MIB object for two ports on card 1 and two ports on card 3 of the target LightStream switch. It is placed in /usr/tmp/collector/collect.2. The data is collected every hour starting when you issue the set collection start command and continuing until you stop it. (No end time has been defined.)
You can view the collection file by following the instructions in the subsection entitled "Viewing a Collection." The following is a sample display of the collection file:
This appendix contains an alphabetical list and description of all fields that may appear in a screen display as the result of a command line interface (CLI) command.
Table A-1 Field Names and Definitions
The Command Line Interface
Introduction to The CLI
Figure 3-1 A sample session of CLI. In this example, all commands that you type are shown in bold. Callouts show the different types of information you may see in a CLI session.
Command Type
Command Name
Command Arguments
Figure 3-2 Sample CLI session
User Accounts
Commands Available in the CLI
CLI Command Syntax
Syntax
Command Examples
Port Number Formats
Normal and Protected Mode
Command Completion Feature
Line Editing Keys
Getting Started
Procedures to Start CLI
Logging in to CLI
Procedure 1: Accessing CLI by Telnetting to the NP
Step 1 Determine the name and password for the user account you will be using. (See your network administrator if you need assistance.)
Procedure 2: Accessing CLI by Connecting a Terminal to the Console Port on the Console/Modem Assembly
Step 1 From the terminal attached to the console (or modem) port on the console/modem assembly, enter the following at the TCS prompt:
Procedure 3: Accessing CLI Running on a Sun SPARCstation
Step 1 If CLI has been installed on your SPARCstation, log in to your SPARCstation. If you have trouble starting CLI, ensure that the directory containing CLI is included in your Lynx search path. (Refer to the LightStream 2020 Installation and Troubleshooting Manual for further information.)
Expected Results
Basic CLI Functions
Accessing Online Help
Procedure 1: Displaying a List of All CLI Commands Available
Step 1 Enter the following at the cli> prompt:
Expected Results
Figure 4-1 The output of the help command when executed without an argument
Procedure 2: Displaying Detailed Help on a Particular Topic
Step 1 Enter the following at the cli> prompt:
Expected Results
Figure 4-2 The output of the help command when executed with the argument quit
Procedure 3: Displaying the Options Available for a Particular Command
Step 1 Enter a question mark [?] in a command to display a list of the options. For example, if you are using the show card 5 command and you do not know what type of objects you can display, enter:
Figure 4-3 Output of the show ? command
Figure 4-4 Sample CLI session showing how to use the question mark for help
Clearing the Screen
Step 1 Enter the following at the cli> prompt:
Setting CLI Attributes
Setting the Echo Source Attribute
Step 1 To set the CLI echosource attribute, enter the following at the cli> prompt:
Expected Results
Setting the Line Edit Attribute
Procedure
Step 1 To set the CLI line edit attribute, enter the following at the cli> prompt:
Expected Results
Setting the Logging Attribute
Step 1 To set the CLI logging attribute, enter the following at the cli> prompt:
Expected Results
Setting the Terminal Type Attribute
Step 1 To set the CLI terminal type, enter the following at the cli> prompt:
Expected Results
Setting the CLI Timer
Step 1 To reset the CLI timer, enter the following at the cli> prompt:
Expected Results
Setting the Traplevel Attribute
Step 1 To set the CLI traplevel attribute, enter the following at the cli> prompt:
Expected Results
Setting the Debug Attribute
Step 1 To set the CLI debug attribute, enter the following at the cli> prompt:
Expected Results
Accessing Protected Mode
Procedure 1: Entering Protected Mode
Step 1 To enter protected mode, type the following at the cli> prompt:
Expected Results
Operational Tips
Procedure 2: Exiting Protected Mode
Step 1 To exit from protected mode, enter the following at the *cli> prompt:
Expected Results
Forcing a Switch Card to Become Active or Backup
Procedure
Step 1 Verify that the target switch is correct by entering the following at the cli> prompt:
Expected Results
Setting the Target Switch for CLI Commands
Procedure
Step 1 Enter the following at the cli> prompt:
Operational Tips
Displaying Log Files
Procedure: Displaying a Log File Using the cbufpr Command
Step 1 To display a circular file from the LynxOS shell, enter the following at the bash$ prompt:
Expected Results
Figure 4-5 A typical cbufpr command
Executing a CLI Script File
Procedure
Step 1 Enter the following at the cli> prompt:
Expected Results
Monitoring LightStream Switches
Introduction to Monitoring
Monitoring Hardware Components from CLI
Monitoring a Chassis
Procedure
Step 1 Verify that the target switch is correct by entering the following at the cli> prompt:
Expected Results
Figure 5-1 Example of the show chassis all command
Figure 5-2 Example of the show chassis all command (concluded)
Figure 5-3 Example of the show chassis agent command
Monitoring Cards
Procedure
Step 1 Verify that the target switch is correct by entering the following at the cli> prompt:
Expected Results
Figure 5-4 Example of the show card all command
Monitoring DSU/CSU Statistics
Monitoring the DSU/CSU on a Low-speed Line Card
Procedure to Monitor a Low-speed Line Card DSU/CSU
Step 1 Connect the LightStream switch to the external DSU/CSU by connecting an RS-232 serial cable from the control port on the fantail to the CSU craft (or console) port.
Figure 5-5 Example - csumon display
Input
Action
Monitoring the DSU/CSU on a Medium-speed Line Card
Procedure to Monitor a Medium-speed Line Card DSU/CSU
Step 1 To access the bash prompt, log in as root or fldsup to the LightStream switch.
Figure 5-6 Example - csumon display
Counter*
Definition
Status Term
Definition
Input
Action
Monitoring Ports
Procedure
Step 1 Verify that the target switch is correct by entering the following at the cli> prompt:
Expected Results
Figure 5-7 Example of the show port all command for an MS trunk port
Figure 5-8 Example of the show port all command for a frame forwarding port
Figure 5-9 Example of the show port all command for a frame forwarding port (concluded)
Monitoring Modems
Procedure
Step 1 Verify that the target switch is correct by entering the following at the cli> prompt:
Expected Results
Monitoring Switch Cards, NPs, and Power Supplies
Procedure
Step 1 Verify that the target switch is correct by entering the following at the cli> prompt:
Expected Results
Figure 5-10 Example of the show chassis commands
Using the LightStream Monitor
Procedure
Step 1 Log into the NMS workstation.
Menu Name
Options
Monitoring Software Components from CLI
Monitoring ATM Connections
Procedure
Step 1 Verify that the target switch is correct by entering the following at the cli> prompt:
Expected Results
Figure 5-11 Example of the show port vci display
Monitoring Frame Relay Connections
Procedure
Step 1 Verify that the target switch is correct by entering the following at the cli> prompt:
Expected Results
Figure 5-12 Example of the show port dlci display
Monitoring CLI
Procedure
Step 1 Enter the following at the cli> prompt:
Expected Results
Monitoring the Collector
Procedure
Step 1 Verify that the target switch is correct by entering the following at the cli> prompt:
Expected Results
Figure 5-13 Example of the show collection display
Monitoring GID
Procedure
Step 1 Verify that the target switch is correct by entering the following at the cli> prompt:
Expected Results
Figure 5-14 Example of the show gid all command
Figure 5-15 Example of the show gid all command (concluded)
Monitoring ND
Procedure
Step 1 Verify that the target switch is correct by entering the following at the cli> prompt:
Expected Results
Figure 5-16 Example of the show nd all command
Figure 5-17 Example of the show nd all command (concluded)
Monitoring Processes
Procedure
Step 1 Verify that the target switch is correct by entering the following at the cli> prompt:
Expected Results
Monitoring SNMP Parameters
Procedure
Step 1 Enter the following at the cli> prompt:
Monitoring the Test and Control System
Monitoring TCS
Procedure
Step 1 Verify that the target switch is correct by entering the following at the cli> prompt:
Expected Results
Figure 5-18 Example show tcs 1 all
Accessing the MIB Tree
Browsing the MIB
Procedure
Step 1 Verify that the target switch is correct by entering the following at the cli> prompt:
Expected Results
Figure 5-19 Sample session of browse command
Figure 5-20 Sample session of browse command (continued)
Figure 5-21 Sample session of browse command (concluded)
Figure 5-22 Example of the browse command using a subtree name
LightStream Statistics and Data Collection
Using LightStream Statistics
Viewing Port Statistics
Procedure
Step 1 Verify that the target switch is set correctly by entering the following at the cli> prompt:
Expected Results
Figure 6-1 Sample port statistics display
Figure 6-2 Sample subsequent port statistics display
Using Data Collection
Collection Number
Collection Status
Operational Status
Begin Time
End Time
Interval
File Name
File Size
Figure 6-3 Sample collection file. In this collection, the ifInUcastPkts value is collected for several ports at one minute intervals
Creating a Collection
Procedure
Step 1 Set the SNMP community to a read/write community by entering the following at the cli> prompt:
Expected Results
Setting the Collection Interval
Procedure
Step 1 Set the SNMP community to a read/write community by entering the following at the cli> prompt:
Typical Time Interval
Number of Seconds in Interval
Adding or Deleting Collection Objects
Procedure 1: Adding Objects to a Collection
Step 1 Set the SNMP community to a read/write community by entering the following at the cli> prompt:
Procedure 2: Deleting Objects from a Collection
Step 1 Set the SNMP community to a read/write community by entering the following at the cli> prompt:
Specifying Collection Size
Procedure
Step 1 Set the SNMP community to a read/write community by entering the following at the cli> prompt:
Starting a Collection
Procedure
Step 1 Set the SNMP community to a read/write community by entering the following at the cli> prompt:
Expected Results
Specifying Collection Start and End Times
Procedure 1: Specifying Start Time
Step 1 Set the SNMP community to a read/write community by entering the following at the cli> prompt:
Procedure 2: Specifying End Time
Step 1 Set the SNMP community to a read/write community by entering the following at the cli> prompt:
Viewing a Collection
Procedure 1: Viewing a Collection
Step 1 Enter the following at the *cli> prompt:
Procedure 2: Copying a Collection File for Viewing or Processing
Step 1 Enter the following at the cli> prompt:
*cli> shell "ftp <name or address of workstation or host to which you want to move the collection file>"
Expected Results
Listing Defined Collections
Procedure
Step 1 Enter the following at the cli> prompt:
Expected Results
Figure 6-4 Sample individual collection display
Stopping a Collection
Procedure
Step 1 Set the SNMP community to a read/write community by entering the following at the cli> prompt:
Expected Results
Deleting a Collection
Procedure
Step 1 Set the SNMP community to a read/write community by entering the following at the cli> prompt:
Expected Results
Sample Collection Scenario
Field Descriptions Appendix
Posted: Thu Jan 23 00:13:16 PST 2003
All contents are Copyright © 1992--2002 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.
