---

Note      The release notes contain important information that does not appear in other documents.

---

The additional arguments that may be used with each type argument are explained below.

set card

Set the administrative state of the card to active, inactive, or testing.

Syntax

set card card# {active|inactive|testing}

Arguments

A card number.

Set the administrative state of the specified card to active.

Set the administrative state of the specified card to inactive.

Set the administrative state of the specified card to testing. This is done during some troubleshooting procedures. The test command sets the card state to testing.

set chassis

Set values of specified chassis attributes.

Syntax

set chassis attribute [value [interval ms]]

Arguments

secondaryip IPaddress

Set the IP addresses that are used for network management. The active IP address designates whichever NP is active in a given chassis; the secondary IP address designates the backup NP. These addresses are known to both NPs and to all nodes in the LightStream network. To connect to either address via a host or router outside the LightStream network, the address must be included in the static routing table on that host or router.

Set three time values used to control congestion avoidance operations. The ms argument is a number of microseconds, and the interval arguments are as follows:

minpermitinterval ms

The maximum (minimum) interval, in microseconds, at which trunk cards and outgoing edge cards may report permit limits.

The minimum interval, in microseconds, at which congestion avoidance processes may distribute aggregated CA updates to input edge cards.

Set the level of traps that are reported by this node to the console. The info level includes oper traps, trace includes info and oper traps, and debug includes all traps. See the LightStream 2020 Traps Reference Manual for information about trap levels.

Set the default router address for network management traffic originating at the local NP. This address is used in the absence of any other routing information for such traffic.

Set the Ethernet address for the NP. It is used by whichever NP is active. Not all LightStream nodes need have an Ethernet connection.

Set the subnet mask for the Ethernet address.

Set the chassis name (node name).

Set the subnet mask for the active and secondary IP addresses.

Determine which switch, SA or SB, is the primary switch.

Set the level of traps that are reported for this node. The info level includes oper traps, trace includes info and oper traps, and debug includes all traps. See the LightStream 2020 Traps Reference Manual for information about trap levels.

Turn the logging of traps in the traplog file on or off.

set cli

Set values of specified CLI attributes.

Syntax

set cli attribute [value [interval ms]]

Arguments

If the debug flag is on, additional information about the course of command execution is displayed, including the names of MIB variables as they are queried or set, and each trap message becomes quite verbose.

Turn the echoing of sourced commands on or off. The default is to display shell commands as they are executed under the source command.

Turn line editing capability with control keys on or off.

Turn the CLI logging function on by directing its output to the specified file logfile. The file logfile must be in the current directory (usually the same directory as the user account you are using). If it is not, you must enter the full pathname of the file. All user input and output of the current CLI session is copied to logfile until you turn the logging function off with set cli log off or exit the CLI. (The new output cannot be displayed at the bash prompt from another window until this happens.) If you re-open the same log file, the new session is appended to the existing file.

cli> set cli log "cli.log.9502"

Set the terminal type to termtype. See the file /etc/termcap for possible termtype values.

Reinitialize the timer that normally indicates time elapsed since the current CLI session was started.

Set the level of traps that are reported to the CLI and to an NMS. The info level includes oper traps, trace includes info and oper traps, and debug includes all traps. See the LightStream 2020 Traps Reference Manual for information about trap levels.

set collection

Create, configure, or control the specified collection process.

Syntax

set collection collection# {action [MIB_object] | attribute value}

See Chapter 6 of the LightStream 2020 Operations Guide for information about data collections and how to use them, and see Chapter 5 of the Operations Guide for information about monitoring collections.

Action Arguments of set collection

Add MIB_object to the objects subject to the specified collection.

Create the specified collection.

Remove the specified collection from the system.

Remove MIB_object from the set of objects subject to the specified collection.

Halt the specified collection.

Start the specified collection.

Attribute Arguments of set collection

Set the time at which the specified collection begins. The default beginning time is the current time.

Set the time at which the specified collection ends. The default end time is December 31, 2037 23:59:59.

Set the maximum size of the collection file in kilobytes, the time at which the specified collection begins, and the time at which the specified collection ends. The optional times begintime and endtime are in [[[yy:]mm:]dd:]hh:mm:ss format. The default file size is 100 Kb. The collection file is a circular file: when the collection data attains the configured file size limit, the process begins overwriting the data in the file from the beginning.

Set the frequency (in seconds) at which collection is to be done, the time at which the specified collection begins, and the time at which the specified collection ends. The optional times begintime and endtime are in [[[yy:]mm:]dd:]hh:mm:ss format. The default frequency is 60 seconds.

set config

Control write access to the MMA configuration database.

Syntax

set config { lock | unlock }

Arguments

All changes to configuration parameters are written to the disk, and other concurrent users are prevented from making configuration changes with CLI commands. The CLI issues a periodic reminder that the chassis is locked. The lock times out automatically two minutes after the termination of the CLI session in which the lock was issued.

Multiple users can concurrently make configuration changes with CLI commands, none of which are written to disk. This is the default.

Description

Write configuration changes to the MMA database, and prevent other users from making configuration changes; or restore the default, so that the CLI affects configuration parameters in run-time memory only.

These commands are equivalent to setsnmp mmaSetLock 3 (chassis locked) and setsnmp mmaSetLock 1 (chassis unlocked). The command setsnmp mmaSetLock 2 locks the chassis to other users, but does not write changes to disk. This is useful for making experimental changes without interference. When setsnmp is used to set the mmaSetLock object to 2 or 3, the lock automatically times out after two minutes of no input from the user. With these commands, in contrast with the set config lock command, the CLI does not issue a periodic reminder that the chassis is locked.

If other users of the CLI attempt to use CLI set commands while the MMA is locked, they see the following generic SNMP error message:

set modem

Set the modem initialization string and modem password for the specified switch card.

Syntax

set modem {sa|sb} {initstring init_string|password password}

Description

This command affects only the node on which the CLI is running when you execute it, regardless of a target set with the command set snmp hostname name.

set pid

Set the trap level or administrative status of a process.

Syntax

set pid pid# {traplevel level |adminstatus {active|inactive} }

Arguments

Set the level of traps that are reported for process number pid#. The info level includes oper traps, trace includes info and oper traps, and debug includes all traps. See the LightStream 2020 Administration Guide for information about the relationships between traps, PIDs, and processes. See the LightStream 2020 Traps Reference Manual for trap levels.

Set the administrative status of process number pid# to active or inactive. When the operational status changes, the system restores it to this preferred state as soon as it can.

set port

Configure a port.

Description

Use the set port command to configure various attributes of a port. Most attributes can be configured only for an appropriate card type. The types of attributes include the port state (for all card types), bridging and VLI attributes, and protocol-specific characteristics. These are described under the following headings:

Syntax

set port c.p arguments

State Arguments of set port

Set the administrative state of the specified port to active, inactive, or testing. The test command sets the port state to testing.

Loop the specified port externally, internally, or remotely.

Unloop the specified port.

Characteristics Arguments of set port

Configure or modify port characteristics. The arguments with the characteristics parameter are as follows:

Set the CSU type to larse or specify that no CSU is present.

Set the DCE or DTE bit rate for the specified port, depending upon the dce-dte-type value described below. The value of Kbits for the DCE bit rate may be 56, 64, 128, 192, 256, 384, 448, 512, 768, 896, 1344, 1536, 1792, 2688, 3584, 4000, or 5376. The value of bits for the DTE bit rate is unrestricted in the range of decimal integers 9,000 — 6,000,000.

Set the specified port to be a DCE, DTE, or DCE internal. The dce setting connects the receive clock to the TT interface signal. The dce-internal setting connects the receive clock to a locally generated clock. A DCE internal port is able to interface with DTE devices that cannot return the TT signal. This value is interdependent with the dce-bitrate or dte-bitrate value described above.

Make previously set administrative values operational for the specified port. The other arguments with the characteristics parameter set the administrative value only.

Set the specified port to use the trunk protocol or one of the edgeprotocols (framerelay, frameforwarding, ATM-UNI).

ATM VCI Arguments of set port

Activate or deactivate the ATM VCI on the specified port, or delete it. The VCI number must be in the range 1-32399 inclusive, and may be further restricted depending upon the type of line card. The VCI must be activated after setting VCI parameters. For the restrictions on the sequences in which these commands may be applied, refer to the LightStream 2020 Administration Guide. The ATM VCI arguments are as follows:

Enable the specified VCI on the specified port after setting its parameters.

Deactivate the specified VCI without deleting it, for example, keeping it as a backup circuit.

Deactivate and delete VCI vci# from the specified port.

Set the destination node for ATM VCI on the specified port to a node identified by its chassis number, its IP address, or its chassis name (if previously set with set chassis name).

Set the destination port to c.p for the specified VCI.

Set the destination VCI to destvci# for the specified VCI. The VCI numbers vci# and destvci# must both be in the range 1-32399 inclusive.

Set the insured rate to cells/sec for the specified VCI.

Set the insured burst rate to cells for the specified VCI. The default is 128 cells.

Set the maximum rate to cells/sec for the specified VCI. The default rates are 109 cells/sec for MSC, 218 Cells/sec for CLC, and the line rate for LSC (frame forwarding and frame relay).

Set the maximum burst rate to cells for the specified VCI. The default is 128 cells.

Set the bandwidth type (cell-drop priority) on the primary portion of the specified VCI to guaranteed or insured. The default is insured.

Set the transmit priority of the specified VCI. This priority is used at each LightStream node in the VCI across the network. The default is 0 for frame relay circuits and for PVCs, and the default is 1 for frame forwarding circuits.

Bridge Arguments of set port

The set port command has four bridge arguments: bcast-limit, bflt, bflt-def, and stb. The arguments are described below.

Set the rate at which broadcast packets can be forwarded through this LAN port. Excess broadcast packets are dropped. To restore the default broadcast limit, enter this command with -1 as the number of packets per second.

The arguments used with the bcast-limit parameter are as follows:

Discard all broadcast packets sent to this port.

Forward all broadcast packets sent to this port.

The maximum number of broadcast packets per second to be forwarded through this port, in the range 1-127.

Associate a bridge filter with the specified port. The filter must already have been created with the define command. Up to 32 filters can be assigned to the same port (with a maximum of 1024 filters over all ports on a LightStream node), and a given filter can be associated with different ports.

The arguments used with the bflt parameter are as follows:

Identifies the filter that is to be associated with this port. The filter ID was assigned to the filter with the define command.

{ block | forward } priority

When a frame matches the filter, either block it or forward it, as indicated. The priority argument is a number that determines the sequence in which multiple filters are considered on this port. Each filter on a given port must have a unique priority number. The lowest number is considered first. We recommend assigning priority numbers by 100s (100, 200, 300, º), leaving large gaps for possible future insertions into the sequence.

del

Break the association between the specified bridge filter and the specified port. This must be done before the filter itself can be deleted with the delete command.

Set the default bridging action for the specified port to block or forward.

Set spanning-tree bridge parameters for the specified port (see also set stb parameter value).

The arguments are as follows:

Set the priority of the specified port for a path using STP. The range is 0-255, and the default is 128.

Enable or disable bridge forwarding on the specified port. Ports are enabled when they come up, but the spanning tree protocol may disable ports to prevent loops if the topology of the bridged networks connected to this port changes.

Set the cost of a path for the specified port (the contribution of this port to the path cost of those paths toward the root bridge that include it). The range is 1-65535, and the default value is calculated as 1000 divided by the speed of the network connection in Mbits/sec. Thus, Ethernet has a default cost of 100, FDDI has a default cost of 10.

Frame Forwarding Arguments of set port

Set the following frame forwarding parameters:

Enable or disable the frame-forwarding circuit on the specified port.

Set the destination node for frame forwarding on the specified port to a node identified by its chassis ID or its chassis name (if previously set with set chassis name).

Set the destination port to c.p for the specified port.

Set the insured rate for the specified port to the bit rate bps.

Set the insured burst rate for the specified port to bytes.

Set the maximum rate for the specified port to the bit rate bps.

Set the maximum burst rate for the specified port to bytes.

Frame Relay Arguments of set port

The set port command has two frame relay arguments: framerelay and dlci. The arguments are described below.

Set the frame relay parameters as follows:

Set the LMI configuration type to FRIF, ANSI T1 617D, or Q933A, or specify that there is no LMI for the specified port.

Set the frame relay net interface type to UNI or NNI for the specified port. Frame relay NNI is not supported in Release 2.0.

Enable the circuit on the specified DLCI (between 16 and 991 inclusive), deactivate the specified DLCI, or remove the specified DLCI from the system. The arguments are as follows:

Enable the circuit on the specified DLCI.

Deactivate the specified DLCI.

Remove the specified DLCI from the system.

Set the destination node for the specified DLCI to a node identified by its chassis number, its IP address, or its chassis name (if previously set with set chassis name).

Set the destination port for the specified DLCI to port c.p.

Set the destination DLCI for the specified DLCI to dlci# (a number between 16 and 991 inclusive).

Set the insured rate for the specified DLCI to the bit rate bps.

Set the insured burst rate for the specified DLCI to bytes.

Set the maximum rate for the specified DLCI to the bit rate bps.

Set the maximum burst rate for the specified DLCI to bytes.

FDDI Arguments of set port

Set FDDI port and station management (SMT) parameters as follows:

Set the characteristics of FDDI port A or port B. The possible parameter values are as follows:

action {enable|disable|start|stop}

Enable, disable, start, or stop the specified FDDI port.

connectpolicy {none|lct|loop|both}

Specify the FDDI connection policy for this port. Use the lct argument for a MAC link competence test with the remote station (remote loop). Use the loop argument for an internal loop at the MAC. Enter none for neither internal nor external loop, or enter both for both.

lercutoff error-rate

Set the link error rate estimate at which an FDDI link connection on this port is broken. The range is 4-15 and the default is 7, meaning 10-7 errors per second.

Set the characteristics of FDDI port A or port B, or set FDDI station management (SMT) parameters, as follows:

t-notify sec

Set the timer used in the Neighbor Notification protocol. The range is 2-30 seconds, and the default is 30 seconds.

stat-report {yes|no}

If this switch is set to yes (the default), then Status Reporting Frames for FDDI events and conditions are sent to the SMT management software. Depending on your network management system, SMT may pass some of these on to higher levels, where they become visible to the operator as SNMP traps.

station action

Control the port as an FDDI station. The action parameter of a set port c.p fddi smt station action command may be any of the following:

{connect|disconnect}

Begin an FDDI connection sequence, or break an FDDI connection, respectively.

path-test

Test the viability of the FLDSUP path. This is not supported in the current release.

{disable-a|disable-b}

Disable the FDDI circuit on the A port or B port, respectively, if the other end of the link is not master (i.e. if the port mode is peer).

VLI Arguments of set port

Set the Virtual LAN Internetworking (VLI) parameters. Only workgroups are currently supported.

Use these commands to maintain the workgroup list for each port. There is one list per port. The port is either included in or excluded from the listed workgroups (see include and exclude, below). The default is an include list that contains just workgroup 1. An empty include list is treated the same as this default case. An empty exclude list permits communication with every workgroup.

Add one or more workgroup IDs to the list for the specified port. There may be up to seven workgroup IDs per port (up to six in a list in the exclude sense). Use the show port c.p wgrp command to display the current list.

Change the sense of the workgroup list for the specified port, so that intercommunication is allowed with the workgroups in the list (include) or with all workgroups in the range 1—65,535 except those listed (exclude). An include list may name up to 7 workgroups per port, and an exclude list may name up to 6 workgroups per port. In practically all cases the workgroup list for a port should be defined in the include sense. The most important use of an exclude list is to enable a port to communicate with all workgroups. Do this by configuring an empty list (delete all workgroup IDs, including workgroup 1) and changing the sense to exclude.

Delete the specified workgroup, or all workgroups, from the list for the specified port. ID is a workgroup ID number in the range 1-65,535. An empty include list is equivalent to the default group 1. An empty exclude list permits communication with every workgroup.

set snmp

Set the value of SNMP attributes for the specified port.

Syntax

set snmp attribute value

Arguments

Set the read-write community name to name. The set command requires that the read/write community name be set first to a name that is assigned the value write in the mma.communities file.

Set the target host name to name or IPaddress. When the target is the node on which the CLI is running, name is localhost.

Description

set stb

Define the spanning-tree bridge parameters for the node.

Description

See also the command set port c.p stb parameters.

Syntax

set stb parameter value

Arguments

For the three arguments maxage, forwdelay, and hellotimer, the value is in hundredths of a second, truncated to seconds. For example, 400, 401, and 499 all signify 4 seconds. The limits on these three arguments are as follows (in seconds):

The maximum age (in hundredths of a second) that should be used to time out STP information. The range of age is 600-4000, and the default is 2000. This value takes effect only when this node becomes the root bridge.

The interval (in hundredths of a second) before changing to another state. The value is in hundredths of a second, truncated to seconds, e.g. 400, 401, and 499 all signify 4 seconds. The range of t is 400-3000, and the default is 1500. This value takes effect only when this node becomes the root bridge.

The interval (in hundredths of a second) between BPDUs sent out by this port. The value is in hundredths of a second, truncated to seconds, e.g. 400, 401, and 499 all signify 4 seconds. The range of t is 100-400, and the default is 200. This value takes effect only when this node becomes the root bridge.

The priority for using this node vs. others for a path using the spanning tree protocol. The range of pri is 0-65535, and the default is 32768.

static MACaddr rcv rcv-port xmit xmit-port [xmit-port . . .]

Enter static entries into the bridge forwarding database.

The MAC address to be used for forwarding, in the standard xx:xx:xx:xx:xx:xx format.

The port to which this MAC is assigned. The keyword any is a wildcard over all ports.

The port to which received frames are to be forwarded.

Set the status of the specified static bridge entry. The arguments are shown in Table 2-4:

Table 2-4   status Arguments

set tcs

For the specified card, set the midplane address, turn power on or off, or reset the card.

Syntax

set tcs card# attribute value | reset

Arguments

Set the midplane address for the specified card to the node address address.

Turn power on or off for the specified card.

Reset the specified card.

Description

This command affects only the node on which the CLI is running when you execute it, regardless of a target set with the command set snmp hostname name.

set trap

Control the display of specific traps.

Description

See the LightStream 2020 Administration Guide for information about the using LightStream traps. See the LightStream 2020 Traps Reference Manual for information about individual traps.

Syntax

set trap {disable|enable} traps [traps . . .]

set trap { [global] | pid {number|name} } {on|off} traps [traps . . .]

Arguments

Affect the trap identified by a trap name or a trap number. See the Traps Reference Manual for trap names and numbers. You may also specify a name for a group of traps as defined in the cli.groups file.

Disable specific traps that are being displayed on the console (normally, oper traps), or enable them again after they have been disabled. (This does not apply to traps that are being displayed because they were turned on with the set trap on command.)

Turn on traps that are currently being ignored (normally, trace traps and debug traps), or turn them back off again after they have been turned on. (This does not apply to traps that are being ignored because they were disabled with the set trap disable command.)

Make the on or off switch apply to all processes system wide. This is the default effect of trap on or trap off.

Make the on or off switch apply to the process with alias PIDname or number PID#. You may display process aliases as follows:

Examples

The following command sets the SNMP read/write community to write (a name to which the value write is assigned in the mma.communities file), so that you can use the set trap command:

cli> set snmp community write

The following command disables the oper trap LCC_1, which reports a high error rate:

cli> set trap disable lcc_16

After correcting the problem, re-enable the trap with the following command:

cli> set trap enable lcc_16

The following command sets the target system to be the node whose alias is boston:

cli> set snmp hostname boston

The following command makes port 5 on card 8 active:

cli> set port 8.5 active

The show Command

Display the value of the specified MIB object(s).

Description

The show command displays the value of the specified MIB object. The amount of information returned varies substantially, depending on the object.

Syntax

show type [id] [parameter1 [parameter2]]

Arguments

The type argument can be any of those shown in Table 2-5:

Table 2-5  

show Command type Arguments

The additional arguments that may be used with each type argument are described in the following pages.

show bflt

Display bridge filter conditions that have been defined with the define command.

Syntax

show bflt [ID]

Argument

The optional ID argument limits the display to the specified filter; otherwise, all currently defined filters are displayed.

show card

Display per-card attributes.

Syntax

show card card# parameter

Explanation

The card# argument is a card number. The parameter arguments are listed below.

Arguments

Display all card attributes (name, process ID, status, version, hardware information, and information about configured ports). The other parameter arguments display selected parts of this display.

Displays the card type (e.g. LS edge), temperature readings at the top and bottom of the chassis, Voltages for TCS VCC, VCC, and Vee (or SCSI voltage for NP, BULK voltage for switch card), and temperature readings from region 1 and region 2 of an access card. The voltages are also displayed by the show tcs card# voltage command, where the display includes the normal voltage range for each. The command show tcs card# temperature also displays these temperature readings, where the display includes the warning and shutdown temperature values for each.

The card name (in the form hostname.c, where c is the card number).

Displays information about each port configured on the card: the port number, the port type (e.g. Frame Relay), and the port name. The port number is displayed in long format, as described in the section "Port Identifiers." The port name is in the form hostname.c.p, where c is the card number and p is the port number on that card.

The process ID associated with the specified card.

Displays the status of the card. Operational status is the actual current status of the card. Administrative status is the preferred status to which the card is restored on reset. Configuration register is the status of the board hardware, as read from the TCS board status register. In each case, the status may be up, down, testing, or empty (if no card is present in the slot).

Displays version information for LC software and LCC software on the card.

show chassis

Display switch-wide attributes.

Syntax

show chassis parameter

Arguments

Display all chassis attributes (general, agent, congestion, primaryswitch, powersupply, cards, listff, listdlci, and listvci). The other parameter arguments display selected parts of this display.

Display the following MMA attributes: MMA trap filter level, MMA trap logging state, MMA collection size, on/off state of the Config DB Active attribute, MMA PID number, configuration host name, configuration author, and configuration ID number.

Display the type of card in each slot, or Empty if there is no card in a given slot.

Display the maximum and minimum intervals between permit limit updates, and the minimum interval between CA updates.

Display the host name, description (e.g. ATM Data Switch), contact person, location, system up time, console trap level, chassis ID, slot of NP being used by CLI, primary and secondary IP addresses and subnet mask, Ethernet address and mask, and default router address.

Display a table of frame forwarding connections. The display shows the source node and port, the destination node and port, insured rate rate and bandwidth, and the maximum rate and bandwidth. If the VC is unconnected, the operationally requested maximum rate is displayed. If it is connected, the displayed value (which is actually in use) may have been negotiated down.

Display a frame relay DLCI table for all frame forwarding ports. An asterisk (*) appears next to the port number if a circuit is deactivated. Compare the show port c.p listdlci command.

Display a VCI table for all ATM-UNI ports. Compare the show port c.p listvci command.

Display the state and type of power supply A and powersupply B.

Display which switch is primary (Switch A or Switch B).

show cli

Display CLI attributes.

Syntax

show cli parameter

Arguments

Display all cli attributes (echosource, lineedit, log, term, time, timer, traplevel, debug, banner). The other parameter arguments display selected parts of this display.

Display the banner that appears when you log in.

Display the on/off setting of the debug switch (for LightStream development and support personnel only).

Display the on/off status of the CLI echo source. If echo source has been turned on with the command set cli echosource on, then the CLI commands in a script file are echoed to the screen when you execute them with the source command.

Show whether command-line editing is on or off. This is controlled with set cli lineedit.

Display the status of the CLI trap logging function, either off or the name of the log file if it has been turned on with the command set cli log logfile.

Display the configured terminal type for the CLI, e.g. vt100.

Display the current date and time.

Display the time elapsed since this CLI session was started, or since the command set cli timer was last executed.

Display the current traplevel setting (Off, Oper, Info, Trace, or Debug). See the LightStream 2020 Traps Reference Manual for information about trap levels. See the LightStream 2020 Administration Guide for information about the using LightStream traps.

show collection

Display collection record number collection#.

Syntax

show collection collection#

Description

The record includes collection status, operational status of the node, beginning and ending time of the collection, the interval between taking collection entries, and the pathname and size of the file used for the collection record. This is followed by the name and value of a series of collection items, e.g. the 17th object in collection 1 is collectDBObjectID.1.17, whose value is an entry for card 7, port 4 (ifInOctets.7004 or ifInErrors.7004).

show config

Display status of configuration lock.

Syntax

show config

Description

This command displays the status (locked, unlocked) of the configuration database lock. See the set config command.

show file

Display contents of log files.

Syntax

show file filetype [tail]

The filetype argument of the show file command is not an actual file name, it is one of the following:

Arguments

Display both of the log files (trap log and MMA log).

Display the contents of the specified collection file.

Display the contents of the MMA log file.

Display the contents of the trap log file.

Description

With the tail parameter, display only the last 20 or so lines from the file.

show gid

Display attributes of the global information distribution (GID) system.

Syntax

show gid parameter

Arguments

Display all gid attributes (general, flooding, synchronization, cards, clients, neighbors, ports, and ip). The other parameter arguments display selected parts of this display.

Display a table of cards managed by GID, showing the host name (Chassis), slot number, sequence number, age (in seconds), originating NP, and number of configured ports.

Display a table of clients managed by GID, showing for each client PID the number of link state (LS) announcements received, IP address translation announcements received, generic global information announcements received, transmitted events, and paths generated.

Display counts of flooding announcements received and transmitted.

Display the software version number, the PID for GID, the amount of memory in use and the count of memory allocation failures for GID.

Display a table of IP addresses managed by GID, showing for each IP address its age, sequence number, the advertising NP, network mask, and port.

Display a table of neighbors managed by GID, showing for each host (chassis) name the VCI number, state, and counts of signals (SYNC, RLL, SLL, Hello, LSA, NLSA, IPA, GA, and NGA).

Display a table of ports managed by GID, showing for each host (chassis) name and port the type of service, up/down state, counts for BW0, BW1, and BW2, and the remote port ID. BW0 is raw link capacity, BW1 is data bandwidth, and BW2 is bandwidth in use.

Display counts of neighbors in the following states: existent sync, exchange start, exchange, loading sync, and full sync.

show modem

Display the modem initialization string.

Syntax

show modem {SA|SB} {all|initstring}

Arguments

Specify the switch.

Display the modem initialization string.

Display the modem initialization string.

Description

This command affects only the node on which the CLI is running when you execute it, regardless of a target set with the command set snmp hostname name.

show nd

Display attributes of the neighborhood discovery (ND) system.

Syntax

show nd parameter

Arguments

Display all ND attributes (general, ndcards, neighbors, switchupdown, switchstat, and clients). The other parameter arguments display selected parts of this display.

Display the software version number, PID for the ND, amount of memory in use by ND, and counts of timers processed, line cards managed by ND, neighbor NPs known to ND, and registered ND client processes.

Display a table of cards managed by ND showing EIA port, channel number, and up/down state.

Display a table of ND neighbors showing EIA port, channel number, and up/down state.

Display a table of the operational and administrative values of ND up/down parameters for each card, as follows:

These parameters may be used to fine-tune ND performance. They may be modified by setting the MIB objects ndAdminIntvl, ndAdminJ, etc., but this is not recommended.

Display a table of ND switch statistics showing for each slot the number of switch up/down cells in and out, with error counts for each.

Display a table of ND clients showing for each PID the type (e.g. sys, ca, gid, or lcc), subtype, and mask.

show pid

Display per-process attributes for process pid#.

Syntax

show pid pid# parameter

Arguments

Display all per-process attributes (name, clialias, createtime, adminstatus, operstatus, traplevel) for process pid#. The other parameter arguments display selected parts of this display.

Display the PID name for process pid#.

Display the alias used by the CLI for process pid#.

Display the time elapsed (up time) since process pid# was created.

Display the administrative status for process pid#.

Display the operational status of process pid#.

Display the trap level set for process pid#. See the LightStream 2020 Traps Reference Manual for information about trap levels.

show port

Display per-port attributes.

Description

Use the show port command to display various attributes of a port. Most attributes can be displayed only for an appropriate card type. The types of attributes include the port state (for all card types), bridging and VLI attributes, and protocol-specific characteristics. These are described under the following headings:

Syntax

show port c.p [arguments]

General Arguments of show port

Display all port attributes (name, status, statistics, physical, frameforward, framerelay, DLCI, and VCI). The other parameter arguments display selected parts of this display. This is the default, with show port c.p followed by no arguments.

Display the description, name, type, MIB2 type, MTU, and speed for the specified port.

Display some (depending upon port type) of the following physical attributes of the specified port: port type, operational and administrative CSU type, operational and administrative DCE receive bit rate, operational transmit bit rate, measured bit rate, link transmit utilization rate (data plus control), administrative expected dte rate and operational and administrative net interface type (dte/dce; these are for low-speed line cards only), operational and administrative protocol, LC auto enable state and debug level, data cell capacity and available capacity, call setup retry and backoff times, operational maximum frame size, and modem status (DCD, DSR)

Display the administrative status, operational status, and last change in operational status for the specified port.

Display statistical counts for the specified port.

ATM VCI Arguments of show port

Display a list of ATM PVCs in order of their VCI numbers for the specified port. The VCI numbers are in column 3 of the display. If the two virtual connections that form the virtual circuit do not have the same values, they are displayed on two lines. A displayed (operational) value may differ from the requested value if it has been negotiated down. An asterisk at the beginning of the line means that circuit is down, or has not been created; an uppercase I means that the circuit has been set to inactive manually with the set port c.p vci vci#deactivate command.

For the specified ATM-UNI port, display the following attributes of the PVC with the specified VCI: source node, port, and VCI; source insured rate, insured burst, maximum rate, and maximum burst (operational and administrative); destination operational node, port, VCI, insured rate, insured burst, maximum rate, and maximum burst; to-net and from-net circuit ID and circuit state, last error reported by ATMM, and cells required; counts of cells to the switch with CLP= 0 or 1, a count of cells to the switch with CLP = 0 upon arrival at the port, but forwarded with CLP = 1, and a count of discarded cells.

Bridge Arguments of show port

Display the bridging state of the specified port (enabled or disabled for bridging), its priority (a value used in the Spanning Tree Protocol), and the port path cost (the contribution of this port to the path cost of those paths toward the root bridge that include it).

Display the default broadcast rate limit that has been set for this port and the number of excess broadcast frames that have been dropped at this port as a result of applying this limit. Multicast is not supported in Release 2.0.

Display the filters that are associated with the specified port, plus some statistical information. The optional ID argument limits the display to the specified filter. The display includes the filter ID, priority, action, and a count of the number of times the filter was matched on this port.

Display the default bridging action that has been set for this port (drop or forward).

FDDI Arguments of show port

Display FDDI information. Displayed values include: TVX (valid transmit timer), TReq (target request time), TRT (token rotation time), TNeg (negotiated target token rotation time or TTRT), T Max. (maximum token rotation time) value, RMT (ring management), UNDA (upstream neighbor duplicate address) flag, For the meanings of these and other displayed items, refer to the specification FDDI SMT X3T9.5 (Rev. 7.2). The arguments of the show port c.p fddi command are as follows:

FDDI MAC addresses are displayed in MSB form (most significant bit first) and Ethernet MAC addresses are canonical form (least significant bit first). So, for example, Ethernet MAC address 08:00:2B:3C:7F:E2 is displayed as FDDI MAC address 10:00:4D:3C:FE:47.

Display the following MAC information for this FDDI port: station management (SMT) index, MAC index, frame status functions, maximum capability, TVX capability, available paths, current path, upstream number, downstream number, old upstream number, old downstream number, duplicate address test, requested paths, downstream port type, SMT address, TReq, TNeg, T Max value, TVX value, frame count, copied count, transmit count, error count, lost count, frame error ratio, RMT state, duplicate address flag, UNDA flag, frame error flag, unit data present, hardware present, unit data enable flag.

Display statistical information about FDDI traffic on this circuit. (The command is not case-sensitive, you may enter it as maccounters.) The items displayed are: MAC index, token count, TVX expirations, not copied count, TRT expirations, ring op count, not copied ratio, not copied flag.

Display the following information for FDDI path 1 (primary path) or 2 (secondary path): the SMT index (calculated per port), path index (same as the path number), minimum TVX value, minimum TMax value, and maximum TReq value.

Display the following information about FDDI port A or FDDI port B in this FDDI circuit: station management (SMT) index, path index, PC type, remote type, connection policy, MAC indicated, current path, requested paths, MAC placement, available paths, PMD type, connection capabilities, BS flag, failed confidence test count, LER estimate, link error count, LER cutoff, LER alarm, connect state, PCM state, PC withhold, LER flag, hardware present, and action. See the command set port c.p fddi {aport|bport} for details about these fields.

Display the following FDDI station management (SMT) information: the SMT index, Path index, Minimum TMax value, and Maximum TReq value.

Frame Forwarding Arguments of show port

Display the following frame forwarding attributes of the specified port: source node and port, and destination node and port (operational and administrative); source and destination insured rate, insured burst, maximum rate, and maximum burst (operational and administrative for source, operational for destination); to-net and from-net circuit ID and circuit state, last error reported by ATMM, and number of cells required; counts of frames and cells to and from the switch with CLP= 0 or 1, and counts of discarded frames and cells. If the VC is unconnected, the operationally requested maximum rate is displayed. If it is connected, the displayed value (which is actually in use) may have been negotiated down.

Frame Relay Arguments of show port

Display the following attributes of the specified frame relay DLCI: source node, port, and DLCI; source insured rate, insured burst, maximum rate, and maximum burst (operational and administrative); destination node, port, and DLCI (operational and administrative); destination operational insured rate, insured burst, maximum rate, and maximum burst; local and remote link management interface (LMI) state, to-net and from-net circuit ID and circuit state, last error reported by ATMM, and cells required; counts of frames and cells to and from the switch with cell loss priority (CLP) = 0 or 1, and counts of discarded frames and cells.

Display the following frame relay attributes: the type of active LMI system, address length, request interval, the maximum for status query errors, the status query period, the maximum supported VCs, the type of broadcast supported (e.g. Uni-cast), the user polling interval, full enquiry interval, a count of user monitored events, and the net interface type (e.g. NNI).

Display a list of frame relay PVCs for the port in order of their DLCI numbers. The DLCI numbers are in column 3 of the display. If the values specified for the two directions of the circuit are not the same, they are displayed on two lines. A displayed (operational) value may differ from the requested value if it has been negotiated down. An asterisk at the beginning of the line means that circuit is down, or has not been created; an uppercase I means that the circuit has been set to inactive manually with the set port dlci dlci#deactivate command. Compare the show chassis listdlci command.

VLI Arguments of show port

Display the ID numbers of the workgroups associated with the specified port (if any), and the sense of the workgroup list (include or exclude).

show snmp

Display SNMP control attributes.

Display the read/write community name, the host name (target), and the on/off state of the authentication attribute.

Syntax

show snmp

show spt

Display spanning bridge parameters (listed below).

Syntax

show spt

Explanation

Display the following spanning-tree bridge parameters: designated root bridge address, root path cost, port for lowest cost path, protocol used (e.g. IEEE 8021d), maximum age, hello time, forward delay, priority, base bridge address, bridge max age, bridge hello time, bridge forward delay, topology change time, hold time, topology changes, bridge aging time, and the list of bridge ports with the spanning state of each.

Two values are displayed for the maximum age, hello time, and forward delay. One set of values is provided by the root bridge; the other set of values is established with the set stb command and takes effect only when the present node becomes the root bridge. These pairs of values are as follows:

show stb

Display the spanning-tree bridge parameters that have been set with set stb and with set port c.p stb commands.

Syntax

show stb {general|static|fwd|ports}

Arguments

Display the following bridge parameters: maximum age, hello timer, forward delay, and priority (for the node). The values displayed for Bridge Max Age, Bridge Hello Timer, and Bridge Forward Delay are those provided by the root bridge.

Display static entries in the bridge forwarding table (see set stb static), including the following entries: MAC address, receive port, and allowed transmit ports.

Display the bridge forwarding table with the following entries: MAC address, static/dynamic, chassis, interface (card, port).

Display a list of all ports enabled for bridging, with the following parameters: port number, port state, received frames, forwarded frames, and dropped frames.

show tcs

Display per-card attributes that are accessible using TCS.

Description

This command affects only the node on which the CLI is running when you execute it, regardless of a target set with the command set snmp hostname name.

Syntax

show tcs card# {all|config|daughter|midplane|oem|paddle|power} [argument]

Arguments

Display all card attributes that are accessible using TCS (state, config, daughter, paddle, oem, midplane, temperature, voltage, and power). The other parameter arguments display selected parts of this display.

Display card configuration attributes that are accessible using TCS. With parameter2 the config argument is as follows:

Display all the card configuration attributes. For explanation of the display, see the descriptions of the other parameter2 arguments, below, which display selected parts of this display.

Display the assembly number (the manufacturing part number) of the board.

Display the revision number of the power-on self-test (POST) software on the board, not implemented in Release 2.0).

Display the board serial number.

Display the version number of the TCS slave on the board.

Display the card type, using abbreviations such as the following:

Display TCS daughter card attributes. With parameter2 the daughter argument is as follows:

Display both TCS daughter card attributes (assembly and serial number). The other parameter2 arguments each display just one part of this display.

Display the daughter card assembly number (part number).

Display the daughter card serial number.

Display midplane attributes that are accessible using TCS. The card# argument must be sa or sb. With parameter2 the midplane argument is as follows:

Display both TCS midplane attributes (assembly and serial number). The other parameter2 arguments each display just one part of this display.

Display the midplane assembly number (part number).

Display the midplane node address.

Display the midplane serial number.

Display attributes for the portion of the access card that is reserved for development partners, which are accessible using TCS. With parameter2 the oem argument is as follows:

Display both TCS access card attributes (assembly and serial number). The other parameter2 arguments each display just one part of this display.

Display the access card assembly number (part number).

Display the access card serial number.

Display attributes for the LightStream portion of the access (paddle) card, which are accessible using TCS. With parameter2 the paddle argument is as follows:

Display both TCS access (paddle) card attributes (assembly and serial number). The other parameter2 arguments each display just one part of this display.

Display the access (paddle) card assembly number (part number).

Display the access (paddle) card serial number.

Display on/off power state of the specified card.

Display the status of the following card attributes that are accessible using TCS power supply, temperature, clock, POST, XILINX load, application load, access (paddle) cards and overrides, flash memory, CP POST, application software, card, power (TCS VCC, VCC, VPP, and SCSI), temperature (top and bottom), board initialization, flash initialization, and TCS HUB.

Display temperature readings for the top and bottom regions of the specified card, which are accessible using TCS. The command show card card# hardware also displays these temperature readings.

Display voltage readings and normal voltage ranges for TCS VCC, VCC, VEE (or SCSI for NP), and VPP voltage (except for switch card) on the specified card, which are accessible using TCS. The command show card card# hardware also displays these voltages.

show trap

Display state of traps, either system-wide (the default) or by process.

Syntax

show trap {[global] | pid {pid#|pidname}} trapspec

[ {[global] | pid {pid#|pidname}} trapspec . . .]

Arguments

One of the following optional arguments may be used to filter traps by their origination:

Display traps from the process whose process ID is PID# or whose alias is PIDname.

Display traps from all processes, system wide. This is the default.

The trapspec arguments are used to specify which traps to display, as follows:

The trap identified by the name trapname. (See the Traps Reference Manual.)

The set of traps identified by the definition of the name trapgroup in the cli.groups file.

The trap identified by trap#.

The set of traps identified the range of traps trap#-trap#.

Description

See the LightStream 2020 Administration Guide for information about the using LightStream traps. See the LightStream 2020 Traps Reference Manual for information about trap levels and individual traps.

Examples

The following example shows how to determine what cards are configured on the switch that you are interrogating:

The following example shows how to determine what ports are configured on card 3 on the switch that you are interrogating:

The following example shows how to display port statistics for port 6 on card 3 in the switch that you are interrogating:

The following example shows how to identify the daughter board serial number for the TCS on card 3:

CLI Control Commands

This section lists the commands that you use to monitor and control the CLI session. It also includes the ping command, which may be used with the set and show commands, described in the sections "The set Command" and "The show Command," to monitor and control the LightStream node from the CLI.

clear

Clear the screen.

Use the clear command to clear the screen.

Syntax

clear

exit

Exit protected mode or the CLI program.

Syntax

exit

Arguments

None.

Description

In normal mode, the exit command halts the CLI program and returns you to the bash> prompt. If you are in protected mode, the exit command returns you to normal mode in the CLI, so that you must type exit a second time to halt the CLI.

Example

help

Provide online help for CLI commands.

Syntax

help [topic]

Arguments

Specifies the name of the command on which you want help.

By default (if you do not enter a topic argument), or if you enter the command help help or help ?, the help command displays a list of all CLI commands.

Description

The help command displays online help information about CLI commands.

Refer to Chapter 4 of the LightStream 2020 Operations Guide for a detailed description of the online help facility in the CLI.

Example

The following example shows the display that the help command displays with protected as its argument:

password

Change the password for the npadmin account, which is also the password for protected mode. Requires protected mode.

Syntax

password

Arguments

N/A

Description

Use the password command to change the password for the npadmin account, which is also the password for accessing protected mode in the CLI:

Example

ping

Send ICMP echo packets to a host and report on any returned packets.

Syntax

ping [packet-size] host-name

Arguments

Specifies the size of the packets that are sent.

Specifies the name of the host to which to send packets. The hostname argument is an IP address specified either by name (e.g. nnsc.nsf.net or boston5) or by number (e.g. 197.5.0.8 or 198.113.178.17). See Chapter 4 of the LightStream 2020 Administration Guide for information about creating the hosts file that defines host names.

Description

The ping command sends a series of ICMP echo packets at 1-second intervals to the specified IP address and reports on any returned ICMP echo-response packets. Press ^C (the control-C key) to stop the ping command and display a summary of the results.

Example

The following example shows four ping packets sent to the node named boston5:

The IP address 198.113.178.17 could have been used as the command argument instead of the alias boston5. The command used the default packet size of 64 bytes. The example shows the number of packets transmitted, the number received back from boston5, and the minimum, average, and maximum round-trip transmission time.

protected

Allow access to protected mode.

Syntax

protected

Arguments

None.

Description

The protected command is used to access the CLI in protected mode. When you are in protected mode, you have access to additional commands. The command prompts you for the password for protected mode. You cannot enter protected mode unless you enter the correct password. When you are operating in protected mode, the cli> prompt is preceded by an asterisk (*cli>). To terminate protected mode and return to the cli> prompt, use the exit or quit command.

Example

To enter protected mode, enter the protected command. You are prompted for the password for the protected mode. When you enter the correct password and press [Return], you enter protected mode. In protected mode, the cli> prompt is always preceded by an asterisk, *cli>.

quit

Exit protected mode or the CLI program.

Syntax

quit

Arguments

None.

Description

The quit command halts the CLI program. If you are in protected mode, the quit command exits from protected mode, but remains in the CLI (in normal mode), so that you must type quit a second time to exit from the CLI.

Example

shell

Execute a LynxOS command under a copy of the LynxOS shell. Requires protected mode.

Syntax

shell "LynxOS command"

Arguments

Any LynxOS command that you can normally execute from the bash shell. Place the command in quotation marks.

Description

The shell command executes a LynxOS command as if it were being run from the bash shell. The actual LynxOS command must be surrounded by quotes. For additional information about LynxOS commands, see the "LynxOS Command Reference" chapter. If more than one command is to be executed, it is often more convenient to start a subshell with the command shell bash at the cli> prompt. If you do this, it is very important to terminate the subshell afterward with the shell built-in command exit (see the "BASH Shell Reference" appendix).

Example

The following example shows use of the shell command to run a LynxOS command that displays the date and time as known to the system. Because the command is a single word, the quotation marks are optional:

The following example shows use of the ls command to display names of all files that begin with a dot (.). Note that ls .* or ls .?* would display contents of the parent directory (abbreviated .. by the shell). Because the command contains a space, it must be entered within quotation marks:

The following example shows use of the cbufpr command to display the last lines of the mma.traplog file. The command contains spaces, so it must be enclosed in quotation marks:

The following example shows use of the command bash to start a subshell for purpose of executing multiple commands. It then shows use of the shell built-in command exit to return to the CLI:

The effects of the cd command are lost when you terminate the subshell. The next use of the shell command will execute LynxOS commands in the user's login directory.

source

Execute a CLI script (CLI commands stored in a disk file).

Syntax

source "filename"

Arguments

Identifies the file that contains the CLI commands that you want to execute. The file filename must be in the current directory (usually the same directory as the user account you are using), or in the /etc, /bin, or /config directory. If it is not, you must enter the full pathname of the file.

Description

The source command executes CLI commands that are stored in a disk file (a script), each command beginning on a new line. Comments may be included with the CLI commands in C programming style, between an initial /* string and a final */ string.

Examples

MIB Commands

This section describes commands used to display and modify the values of MIB objects (see the "LightStream MIB Reference" chapter).

browse

Browse the MIB tree.

Description

Use the browse command to walk through the MIB tree and obtain the value of any object in the MIB tree.

Syntax

browse [mib-address]

Arguments

Specifies the point in the MIB tree at which the browse tool opens. If you do not specify this argument, the browse tool opens at the top of the MIB tree (at the iso object).

The address can be specified as a path of dot-separated numbers, or as a variable name, or a combination (where only the first element is a variable name). Thus, 1.3.6.1.2.1, mgmt.1, and mib all refer to the same variable. (See the section "Alternative Forms of MIB Addresses" for a description of alternative forms of MIB addresses.)

Examples

The following example shows how to start the browse command with the address of a particular object, mgmt in this example:

There is only one object under the mgmt object, so we select it by entering the menu number 1:

There are 12 objects under the mib object. We select the object system by entering the menu number 1:

All of the objects under the system object are "leaves" of the MIB tree, that is, there are no further branches under them. When we select one from the menu, the program displays the value for that object and returns to the mgmt.mib.system menu:

If we wish to explore a different branch of the mib subtree, we can enter "u" to return to the next higher level:

To exit to the cli> prompt, we enter "q" (or "e"):

getsnmp

Display the value of a specified MIB object.

Description

Given the addresses of one or more MIB objects, getsnmp displays the value of the MIB object at each address.

Syntax

getsnmp mib-address [mib-address [ . . .mib-address]]

Arguments

Specifies the address of a MIB object that you want to display. As an optional, repeated argument, it specifies the address of an additional MIB object that you want to display.

The address can be a path of dot-separated numbers, a variable name, or a combination (where only the first element is a variable name). Thus, 1.3.6.1.2.1.1.1.0, mib.1.1.0, system.1.0 and sysDescr.0 all refer to the same variable.

If you want to get more than one object, you can list more than one object identifier. You can use the walksnmp command to identify MIB objects and their addresses.

Examples

getnextsnmp

Display the value of the next object after the specified object in the MIB tree.

Description

Given the address of one or more MIB objects, getnextsnmp displays the value of the MIB object that comes next in the subtree after each address you specified. If you specify the last variable ("leaf" object) in a subtree, the command displays the first variable in the next following subtree.

Syntax

getnextsnmp mib-address [mib-address [ . . . mib-address]]

Arguments

Specifies the address of the MIB object just before the object that you want to display. As an optional, repeated argument, it specifies the address of an additional MIB object whose next-following neighbor in the MIB tree you want to display.

The address can be specified as a path of dot-separated numbers, or as a variable name, or a combination (where only the first element is a variable name). Thus, 1.3.6.1.2.1.1.1, mib.1.1, system.1 and sysDescr all refer to the same variable.

If you want to get more than one object, you can list more than one object identifier. You can use the walksnmp command to identify MIB objects and their addresses.

Examples

setsnmp

Change the value of the specified MIB object. Requires protected mode.

Description

Use setsnmp to set the value of a specified MIB object.

---

Caution Do not manipulate MIB objects unless you are familiar with SNMP.

---

Syntax

setsnmp MIBaddress value

Arguments

Identifies the MIB variable to be set.

The address can be a path of dot-separated numbers, or a variable name, or a combination (where only the first element is a variable name). Thus, 1.3.6.1.2.1.1.1.0, mib.1.1.0, system.1.0 and sysDescr.0 all refer to the same variable. You can use the walksnmp command to identify MIB objects and their addresses.

Specifies the new value for the MIB object at MIBaddress. If the value argument contains spaces, you must quote it. The value may be a number, a string, or an object ID in the form :MIBaddress. To determine the appropriate argument type for the specified MIB object, type ? after the first MIBaddress argument.

Example

The following example shows use of setsnmp to change the name of the contact person for the system (note quotation marks):

The following example shows use of the online help facility (typing ? after a partial command) with setsnmp to determine the type of value that can be assigned to a given object:

walksnmp

Display the values of all MIB objects in the MIB tree starting with the specified object.

Description

The walksnmp command displays the names and values of all variables that are "leaves" of the MIB tree below the specified MIB object. If you specify the head of a particular subtree (as shown in the figures in the "LightStream MIB Reference" chapter), the command displays all the "leaf" variables at the ends of branches in that subtree. This is equivalent to repeated getnextsnmp. If you specify an object that has no branches under it, it displays the value of that object, just like getsnmp.

Use the walksnmp command to survey a range of variables, to locate a variable quickly when you know only which part of the MIB it is in, or to identify the name of a MIB variable so that you can specify it as argument of another SNMP command.

Syntax

walksnmp mib-address

Arguments

The starting point. The address can be specified by a path of dot-separated numbers, by a variable name, or by a combination (where only the first element is a variable name). Thus, 1.3.6.1.2.1.1, mgmt.1.1, and system all refer to the same subtree.

Example

VLI Commands

This section describes two commands used for creating and deleting bridge filters.

See also the following commands:

define

Define a bridge filter.

Description

The define command defines a filter condition that determines the bridge ports to which traffic is forwarded.

A filter is a condition or a set of conditions that determine whether incoming frames are blocked or forwarded. If the contents of a field in an incoming frame header match the value specified for that field in a filter condition, then a specified action is taken with that frame.

A maximum of 512 filters may be defined.

Syntax

define bflt ID expression

Arguments

Specifies that it is a bridge filter that is to be defined. In the current release, this is the only object type that can be defined with this command.

A number in the range 1-64000. If ID is already in use for a filter, the command asks if you want to overwrite the old filter, and lets you assign a different number if you answer no. We recommend that you assign ID values by 10s (i.e. 10, 20, 30, etc.), leaving ample gaps for future assignments. Use the show bflt [ID] command to display currently defined filters.

A comparison expression or a boolean expression. In a comparison expression, the value of an incoming header field is compared with a constant. In a boolean expression, two or more expressions are combined with boolean operators.

A comparison expression has one of the following two forms:

field operator constant

(field & mask) operator constant

The syntax variables field, mask, operator, and constant are as follows:

A built-in identifier for a field in incoming frame headers. The field identifiers are not case sensitive (e.g. macsrc is equivalent to macSrc). They are listed below.

The field may be masked with a C-style bitwise AND operator in an expression of the form (field & mask). Thus, the following expression ignores the final hex digit of the macEther field and matches a zero in the corresponding position of the constant argument:

A comparison operator, as follows:

The constant must be of the appropriate form for the built-in field on the left side of a simple comparison expression. They are all sequences of hex digits x (with leading zeroes if necessary, but without leading 0x), as follows:

A boolean expression results from conjoining expressions with boolean operators, as follows:

Here, boolean-operator is && (logical AND) or || (logical OR), and expression may be either a boolean expression or a comparison expression. Evaluation of expressions is left to right. Parenthesized expressions are resolved first, so you may use parentheses to force a different evaluation sequence.

Examples

delete

Delete a bridge filter.

Syntax

delete bflt ID

Arguments

Specifies that it is a bridge filter that is to be deleted. In the current release, this is the only VLI object type that can be deleted.

A filter ID, previously set with the define bflt ID expression command.

Description

Delete a bridge filter condition previously set with a define command. If the filter has been assigned to a port with the command set port c.p bflt ID priority action, it cannot be deleted until the association is broken with the set port c.p bflt ID delete command.

Diagnostics Commands

This section describes the following diagnostics and troubleshooting commands:

connect

Connect the CLI to a line card as a console. Requires protected mode.

Description

Use the connect command to connect the CLI to the specified line card so it can act as a terminal for a program, such as diagnostics, running on the line card.

Type ~. (tilde-dot) to interrupt the connection. When the connect command is used to reconnect a previously existing connection, it prints outstanding output from the card, notifying you if any data was lost.

Syntax

connect card# [force] [diagnostic]

Arguments

The card number, as follows:

1 — NP (if there is an NP in slot 2, it must be active)

2 — NP (NP in slot 1 must be active) or line card (populate slots 3-10 before slot 2)

3-10 — Line cards

Forces this CLI session to take control of the slot even if the slot was being used by another CLI in the network.

Used only when connecting to a card to run diagnostics. See the LightStream 2020 Installation and Troubleshooting Manual.

loadcard

Load a file into a card, start it, and establish a console connection with its TCS slave. Requires protected mode.

Description

The loadcard command loads a line card program, such as the operational software or a diagnostic program, into the specified card. The command resets the card, then loads and starts the line card software.

Syntax

loadcard card# [load-address] [filename]

Arguments

The card number, as follows:

1 — NP (if there is an NP in slot 2, it must be active)

2 — NP (NP in slot 1 must be active) or line card (populate slots 3-10 before slot 2)

3-10 — Line cards

The load address. Normally, you omit this argument and use the default load address.

The name of the file containing the program you want to load. If no filename is specified, this command loads the operational software for the card.

test

Determine whether or not a specified card is functional.

Description

The test command runs diagnostic tests on a specified card to determine whether it should be replaced. The software automatically identifies the type of card and runs appropriate tests. (PLC/FDDI, PLC/Ethernet, and CLC/OC-3c modules are not tested.) You must specify the card number (3-10).

If a card fails, record the displayed error codes and report them when returning the card.

Syntax

test <card#> [-l][-p][-s][-x][-Ffile]

test <card#> -r

test <card#> -m [-Ffile]

Switches

The default behavior, with only the card# argument, is to run standard tests in the background (see the -r switch).

-Ffile

Load diagnostics from file rather than from the default file for the card. file can only be a copy of the default file, and you must ensure that file matches the card type. In the absence of this switch, the default files are automatically matched with the card type and loaded. They are as follows:

-l

If tests require looping plugs or cables (rare), use this switch.

-m

Stay connected and monitor output of standard PASS/FAIL tests plus manufacturing tests giving more detailed data until completion or timeout. A test in progress may be terminated with [^C] These tests are equivalent to using loadcard with the manufacturing diagnostics and connecting to the card (see the LightStream 2020 Installation and Troubleshooting Manual).

-p

Stay connected and poll standard test output approximately every second until completion or timeout. Tests completed between these snapshots are not displayed, and if a test runs longer than one polling interval, successive dots indicate the successive polls. The -r switch may be used after completion. A test in progress may be terminated with [^C].

-r

Retrieve and display status of standard diagnostics previously run in the background. The test command changes card status to test, and the -r switch may be used until the card status changes to active or inactive or until the card is loaded with some other software, overwriting the memory locations in which test results are stored. A heartbeat indication in the display serves to confirm that the diagnostics are running in case the same test is active over successive polls with test -r. Base your estimate of test run time on experience with test -p.

-x

Extended test, running long memory tests.

read

Read memory and hardware registers accessible by the TCS.

Description

This command is only for use by LightStream support personnel. It is of no value without detailed knowledge of memory locations, hardware registers, their contents, and their functions in the LightStream node.

write

Write memory and hardware registers accessible by the TCS. Requires protected mode.

---

Caution This command is only for use by LightStream support personnel. Without detailed knowledge of memory locations, hardware registers, their contents, and their purposes, use of this command will almost certainly destroy the functioning of the LightStream node.

---

Setting and Displaying
Configuration Attributes

---

This chapter lists the parameters that you can configure with the LightStream configuration tool on a workstation, and shows the functionally equivalent CLI commands for displaying and setting a node's configuration if the configuration tool is not available to you.

Setting Configuration Attributes

This section describes how to change configuration parameters with CLI commands, in case the configuration tool is not available.

Where Configuration Information is Stored

Configuration information is stored in five locations:

1. Pre-programmed defaults.

2. Run-time memory on the target node.

3. A copy in on-board EEPROM of the run-time values of certain line card attributes.

4. The local configuration database on the disk of the target node.

5. The global configuration database on the network management station (NMS) on which the configuration tool is running.

How to Change Attribute Values

The preferred method of setting attribute values in the local configuration database is by using the configuration tool on the network management station (NMS). See the LightStream 2020 Configuration Guide for details.

CLI commands may be used to change the values of configuration attributes. Normally, configuration changes made with CLI commands are made to run-time memory only. The next time the node is reset, these volatile changes are overwritten. This is useful for testing proposed configuration changes.

CLI commands may also be used to change the local configuration database. CLI set commands write to the local database as well as to run-time memory after you enter the following command:

The set config lock command also locks the MMA so that a CLI user connected from a different IP address cannot concurrently make configuration changes. The CLI issues a periodic reminder that the MMA is locked.

Use the following command to restore the default state (unlocked, no writes to database):

These commands are equivalent to setting the mmaSetLock MIB object to 3 (locked) or to 1 (unlocked). There is a third value of the mmaSetLock object that cannot be set by the set config command. If you are testing configuration changes, but do not want to save them yet in the local configuration database, you can use the following command to lock the MMA (so that a user connected from a different IP address cannot concurrently make configuration changes) without causing CLI sets to write to the local database:

You can restore the default state with the set config unlock command. The lock is automatically removed after two minutes of inactivity or when the CLI session is closed.

For additional details about these commands, refer to the description of the set config command.

Synchronizing Databases

After you make changes to the local configuration database with CLI commands, as described above, it is out of synch with the global database. The global configuration database is located on the NMS on which the configuration tool is running. To copy local configuration changes to the global database, you must use the verify function in the configuration tool. This function retrieves the local settings and allows you to write them over the global values. See the LightStream 2020 Configuration Guide.

Working with Temporary Configuration Changes

CLI changes in run-time memory may cause confusion.

How Attributes are Re-Initialized

When the NP is restarted (e.g. when the node is rebooted), or, for card or port attributes, when a card comes up, attribute values in run-time memory are reset in the following sequence:

Port Attributes that are Stored in EEPROM

Run-time values of the following port attributes are stored in EEPROM on the line card:

Normally, when you set the status of a card to inactive and then to active, changes made with CLI commands to run-time memory (but not to the database) are lost. However, changes to the above attributes are read back into run-time memory from EEPROM when the card comes up.

A value read in from EEPROM remains in effect if the default value for that attribute was never changed in the local configuration database.

For example, suppose you have used the CLI set port c.p characteristics command to specify the DCE bit rate for a port. This attribute is not configured in the local database because you have been using the default bit rate for this port, or perhaps you are configuring a new card with CLI commands. Because this was an experimental setting, you did not first use the set config lock command to write this change to the local database. The new run-time value of this attribute is stored in EEPROM on the line card. When the card is disabled and enabled (or the NP restarted), NP software reads EEPROM and writes the bit rate to run-time memory. There it remains because there is no bit rate setting in the local database to overwrite it.

Node Attributes that Look Like Port Attributes

A similar confusion is due to thinking of certain node attributes mistakenly as edge card and port attributes. These are the attributes concerned with the following LAN-related functions:

These attribute values are stored in the NP's run-time memory and not on the card. Consequently, they are overwritten from the local configuration database only when the NP is restarted, typically when the node is rebooted. They are not overwritten when a card is disabled and re-enabled, or even when the card is physically removed and reinstalled.

For example, suppose you have used the CLI to specify some custom filters and assign them to a port, but you did not first use the set config lock command to write them to the local database. These filter settings are retained in NP memory. When the edge card is disabled and re-enabled, the filter settings are not affected. You should use CLI commands or the configurator to delete them. They are also removed when you reboot the node or in some other way restart the NP.

Chassis and Switch Attributes

Table 3-1 shows the configurable chassis attributes and the corresponding CLI set and setsnmp commands:

Table 3-1   Chassis Attributes and CLI set and setsnmp Commands

The following switch-wide attribute may be configured only in expert mode in the configuration tool.

Card Attributes

Following are the configurable card attributes and the corresponding CLI set and setsnmp commands.

Port Attributes

Following are the configurable port attributes and the corresponding CLI set and setsnmp commands. There are common port attributes, low-speed trunk and edge port (LSC) attributes, T3 and E3 medium-speed trunk and edge port (MSC) attributes, FDDI port attributes, and OC3 trunk and edge port attributes. (For Ethernet ports, only the two attributes common to all ports may be configured.)

Internetworking Attributes

Following are the configurable attributes and the corresponding CLI set commands for internetworking.

PVC Attributes

Following are the configurable attributes and the corresponding CLI set and setsnmp commands used to provision PVCs. The source node is referred to as node A, and the destination node as node B.

The CLI commands take the source node, port, and VCI number from the target host. You must set the PVC attributes from both ends and then activate the PVC as follows:

setport c.p{dlci|frameforwarding|vci}activate

Following are the configurable per-port call setup and bandwidth attributes and the corresponding CLI set and setsnmp commands. These PVC attributes may be configured only in expert mode.

VLI Attributes

To add or delete a workgroup, use one of the following commands:

cli> set port c.p wgrp add ID

cli> set port c.p wgrp delete ID

To change the sense of a workgroup list for a port, use one of the following commands:

cli> set port c.p wgrp include ID

cli> set port c.p wgrp exclude ID

In practically every case, the workgroup list for a port should be configured in the include sense, to allow intercommunication with all ports that are members of the listed workgroups. There is one list per port with up to seven IDs in the include sense, up to six in the exclude sense (all 65,534 groups except those listed).

Displaying Configuration Parameters

The following sections contain tables that show how to display the current values of configuration parameters with CLI show commands.

Chassis and Switch Attributes

Following are the configurable chassis attributes and the corresponding CLI show commands:

Card Attributes

Following are the configurable card attributes and the corresponding CLI show commands.

One card attribute can be set only in expert mode with the configuration tool, and is displayed with a getsnmp command:

Port Attributes

Following are the configurable port attributes and the corresponding CLI show and getsnmp commands. There are common port attributes, low-speed trunk and edge port (LSC) attributes, T3 and E3 medium-speed trunk and edge port (MSC) attributes, FDDI port attributes, and OC3 trunk and edge port attributes. (For Ethernet ports, only the two attributes common to all ports may be configured.)

Internetworking Attributes

Following are the configurable attributes and the corresponding CLI show commands for internetworking.

PVC Attributes

Following are the configurable attributes and the corresponding CLI show commands used to provision PVCs. The source node is referred to as chassis A, and the destination node as chassis B.

The CLI commands take the source node, port, and VCI number from the target host. You may display the corresponding attributes after changing the target host as follows:

setsnmp hostname name

The following attributes may only be set in Expert Mode in the configuration tool:

The attributes for the destination (Node B) are identical to those for the source (Node A). To display them you must first set the target to Node B with the set snmp hostname name command.

VLI Attributes

To display VLI attributes, use the show port c.p wgrp command.

LightStream MIB Reference

---

Network management systems that use SNMP work with information stored in a Management Information Base (MIB). This chapter:

MIB Overview

Figure 4-1 shows a high-level diagram of the MIB that is used to manage LightStream switches. The organization of the MIB is defined in a document called the Structure of Management Information (SMI).

Figure 4-1   MIB Tree Structure

For information on some of the standard MIBs shown in Figure 4-1, refer to the following documents:

Under the Private subtree is the LightStream private MIB that is described in the remainder of this chapter. The high level structure of the LightStream private MIB is shown in Figure 4-2:

Figure 4-2   LightStream Private MIB Tree Structure

For detailed descriptions of those MIB objects that can be displayed and set, see the figures and tables in the following sections:

Examine the MIB files themselves for information at a level of detail much greater than can be given here.

MIB Addresses

A MIB address identifies a particular MIB object by its location in the MIB. Five CLI commands require MIB addresses in their arguments: the browse command, and the SNMP commands (getsnmp, getnextsnmp, setsnmp, and walksnmp). These commands are for monitoring and controlling the LightStream switch, as described in the "CLI Command Reference" chapter, in ways that are not available with the standard CLI control commands (see Table 2-2 for a list).

Alternative Forms of MIB Addresses

You can specify the MIB address in a number of ways:

Thus, the following addresses all refer to the same MIB variable:

Determining MIB Variable Names

To learn the names of the MIB variables in one of the subtrees shown in Figure 4-1 or Figure 4-2, you can specify the name of the subtree as the argument of the walksnmp command. This command displays all the "leaves" below the specified point in the MIB. You may also use the browse command to step through the branches of the MIB tree and, when you reach the end of a branch, to display the values of leaves one at a time.

Object Identifiers

The getsnmp, getnextsnmp, and setsnmp commands display and change the value of a single "leaf," that is, a single instance of a given MIB object. To identify a single instance of a MIB object at the end of a branch, you specify the object name followed by a numeric suffix known as an object identifier.

If there is only a single instance of the given object, then the identifier suffix for that instance is 0. For example, there is only one instance of the sysContact object, so its identifier is sysContact.0. The following command displays the name of the contact person for the target node:

cli> getsnmp sysContact.0

Just as with the SNMP commands and the browse command, described above, the first part of the object address, the MIB variable, may be specified in a number of ways. Thus, the following addresses all refer to the same MIB object:

This is the simplest form of object identifier. More complex types include port identifiers and object identifiers for multiply-indexed objects.

Port Identifiers

The usual way of specifying a port number in the argument of a CLI command is in the format c.p, where c is the card (slot) number and p is the number of the port on that card. However, the show command usually displays the value of the ifIndex object for the interface, which gives the port number in a more complex format. For example, the following command displays the ports on card 4:

when a MIB object identified by port number is given as the argument of the getsnmp, getnextsnmp, or setsnmp command, this more complex format is used. For example, the following command tells us which data link connection management scheme is active on frame relay port 4.2 (card 4, port 2), specified here as port 4002:

By looking this object up in Table 4-13, or by searching for it in the MIB file private_mib.asn, we find that the value 3 means that the default ANSI standard T1.617 Annex D is active on this port.

In effect, the long form of port number is ctpp or cctpp, where c is the card number, p is the port number, and t is the card type (2=FDDI, 1=Ether, 0=Other). The formula for determining the port number in this long format is as follows:

((c * 1000) + p + t)

The variables in this formula are as follows:

100 — Ethernet

200 — FDDI

0 — Other

For example, the MIB object that stores the alias or name for port 3 on card 4 is portInfoName.3004, or portInfoName.3104 if it is an Ethernet port, or portInfoName.3204 if it is an FDDI port.

Multiply-Indexed Objects

Some objects require us to specify more than one index number. For example, the following command tells us that the local LMI state of the frame relay circuit on DLCI 16, port 4, card 2 is inactive:

The double index 4002.16 means that this frCktInfoLclLMI object is indexed first by port number 4002 (equivalent to port 4.2) and then by DLCI number 16. For the fact that the value 2 means "inactive", see Table 4-15, or see the description text for frCktInfoLclLMI in the private_mib.asn MIB file.

In LightStream Release 2.0, the doubly-indexed entries in the LightStream private MIB include the following:

Objects in standard MIBs may also be multiply indexed. These appear with more than one number in the object identifier when you walk or browse the MIB. You can also identify these objects by examining the MIB file in which they are defined: the INDEX entry of the definition lists more than one object name as indexing objects.

An example is the fddimibPATHEntry object defined in the fddi.asn MIB file. The FDDI stations implemented in the LightStream node are single-MAC, dual-attachment FDDI stations. There are two paths per SMT. (An FDDI path is the sequence of MACs and ports in token order.) The paths are managed by the fddimibPATHTable object. The fddimibPATHTable object is defined as a sequence of fddimibPATHEntry objects.

The fddimibPATHEntry object is doubly indexed. The first indexing object is fddimibPATHSMTIndex, and the second is fddimibPATHIndex. LightStream software calculates the values of these SMT index objects as follows:

The following example shows the fddimibPATHTable objects for a LightStream node. These objects are defined for card 3 (SMT 5 and 6).

The atmSwitch Subtree

Figure 4-3 shows the atmSwitch subtree, which comprises most of the LightStream private MIB.

Figure 4-3   atmSwitch Subtree Structure

Following are the branches of the atmSwitch subtree:

The chassisInfo Subtree

Figure 4-4 shows the chassisInfo subtree, and Table 4-1 shows the address and value of each object in the subtree.

Figure 4-4   chassisInfo Subtree Structure

Table 4-1   Objects in the chassisInfo Subtree

The cardInfo Subtree

Figure 4-5 shows the cardInfo subtree, and Table 4-2 shows the address and value of each object in the subtree.

The objects in the cardInfo subtree comprise a table, cardTable, in which each cardEntry row contains information about one card in the chassis.

Figure 4-5   cardInfo Subtree Structure

Table 4-2   cardTable Objects

The portInfo Subtree

Figure 4-6 shows the portInfo subtree, and Table 4-3 shows the address of each object in the subtree and the type of each object.

Figure 4-6   portInfo Subtree Structure

The objects in the portInfo subtree comprise a table, portInfo-Table, in which each portInfoEntry row contains information about one port on a card.

Table 4-3   PortInfoTable Objects

The portTransmission Subtree

Figure 4-7 shows the portTransmission subtree, and Table 4-4 through Table 4-8 show the address and type of each object in the subtree.

The objects in the portTransmission subtree comprise three MIB object tables: ls1InfoTable for low speed line cards, ms1InfoTable for medium speed line cards, npInfoTable for NP cards, and clc1InfoTable for cell line cards. Each row of a table (ls1InfoEntry, ms1InfoEntry, or npInfoEntry) contains information about a port on a card.

Figure 4-7   portTransmission Subtree Structure

Table 4-4   ls1InfoTable Objects