Guest

Cisco Lightstream ATM Switches

LightStream 2020 Command and Attribute Reference Guide


Table of Contents

About This Book
Audience
Organization
Related Documentation
Text Conventions

CLI Command Reference
The set Command

The show Command
CLI Control Commands
MIB Commands
VLI Commands
Diagnostics Commands
Setting and Displaying
Configuration Attributes

Setting Configuration Attributes
Displaying Configuration Parameters
LightStream MIB Reference
MIB Overview
MIB Addresses
The atmSwitch Subtree
The lightStreamInternet Subtree
The lightStreamVLI Subtree
Table 4-48   lightStreamVliPortCtlTable Objects
Table 4-49   lightStreamVliPortWorkGroup Objects

LynxOS Command Reference
Name
Synopsis
Copyright
Description
Name
Synopsis
Description
Options
Note
See Also
Name
Synopsis
Description
Options
Name
Synopsis
Description
Options
Examples
See Also
Name
Synopsis
Description
Name
Synopsis
Description
Options
Examples
Name
Synopsis
Description
Name
Synopsis
Description
Options
Commands
File Naming Conventions
File Transfer Conventions
Note
Acknowledgements
Name
Synopsis
Description
Example
See Also
Name
Synopsis
Description
Options

See Also
Name
Synopsis
Description
Options
See Also
Name
Synopsis
Description
Options
See Also
Name
Synopsis
Description
Options
Note
See Also
Name
Synopsis
Description
Files
See Also
Name
Synopsis
Description
Options
Files
Diagnostics
See Also
Name
Synopsis
Description
Options
Message Logging
Distfiles
Files
See Also
Notes
Bugs
Name
Synopsis
Description
Options
See Also
Name
Synopsis
Description
Options
Diagnostics
See Also
Name
Synopsis
Description
Options
Conflicts During Extraction
Examples
See Also
Name
Synopsis
Description
Commands
Acknowledgements
Name
Synopsis
Description
Options
Name
Synopsis
Description
Options
See Also
Name
Synopsis
Description
Option
See Also
Vi Editor User's Guide
Introduction
Editing Basics
Getting Started
Terminology
vi Regular Expressions
Position Movement Commands
Secondary Movement Commands
Text-Changing Commands
Miscellaneous Commands
Colon Commands
Editor Initialization
Command Summary
Notes on LynxOS vi
BASH Shell Reference
Name
Copyright
See Also
Files
Authors
Bug Reports
Bugs

About This Book


This guide provides detailed information on commands available from the command line interface (CLI), and a table that correlates the attributes used in the CLI, the configuration program, and the Management Information Base (MIB). It provides a description of the MIB used to manage LightStream 2020 enterprise ATM switches. It also contains manual pages for LynxOS commands and a user's guide for the vi text editor.

Audience

The LightStream 2020 Command and Attribute Reference Guide is intended for anyone who operates a LightStream network.

Users of the LightStream document set are expected to have a general understanding of basic data communications concepts and some knowledge of UNIX.

Organization

This guide is organized as follows:

  • About This Book — Describes the audience, organization, and conventions for this book.
  • CLI Command Reference — Lists all CLI commands and provides detailed descriptions of syntax, arguments, etc.
  • Setting and Displaying Configuration Attributes — Lists the configuration parameters that you can configure with the LightStream configuration tool, and shows the functionally equivalent CLI commands for displaying and setting a node's configuration if the configuration tool is not available to you.
  • LightStream MIB Reference — Shows the complete LightStream enterprise MIB and lists the address and type of each attribute.
  • LynxOS Command Reference — Provides manual pages for LynxOS commands that you might need to operate your LightStream network.
  • Vi Editor User's Guide — Provides complete user information for the vi text editor.
  • BASH Shell Reference — This appendix provides instructions on using the bash shell.

Related Documentation

The following is a list of LightStream manuals and other material relevant to LightStream users.

  • LightStream 2020 System Overview

The system overview explains what a LightStream switch is and how it works. It outlines ATM technology and describes LightStream hardware and software.

  • LightStream 2020 Site Planning and Cabling Guide

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.

  • LightStream 2020 Installation and Troubleshooting Manual

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.

  • LightStream 2020 Configuration Guide

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.

  • LightStream 2020 Operations Guide

The operations guide is a task-oriented book that tells you how to operate a network of LightStream switches. The guide presents an overview of network operations tasks, describes the command line interface (CLI), and presents procedures for performing monitor and control tasks such as displaying the status of nodes, cards and ports, viewing statistics, and creating collections of traffic data.

  • LightStream 2020 Administration Guide

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.

  • LightStream 2020 Traps Reference Manual

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.

  • LightStream 2020 Command Line Interface (CLI) Reference Card

The reference card compactly summarizes the syntax and arguments of all CLI commands.

  • LightStream 2020 Release Notes

The release notes provide a software upgrade procedure and describe new features and special considerations, including information on known software bugs.


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


  • LightStream 2020 Online Help

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. Read the LightStream 2020 System Overview first. Then use Table 1-1 to determine which manuals you should read next.

Table 1-1   LightStream Reading Path

If you want to: Read the following manuals in the order listed below:

Install LightStream switches

LightStream 2020 Release Notes1

LightStream 2020 Site Planning and Cabling Guide

LightStream 2020 Installation and Troubleshooting Manual

Configure LightStream switches

LightStream 2020 Release Notes1

LightStream 2020 Configuration Guide

LightStream 2020 Online Help Screens

Set up or expand a LightStream network

LightStream 2020 Release Notes1

LightStream 2020 Administration Guide

LightStream 2020 Online Help Screens

Operate a LightStream network

LightStream 2020 Release Notes1

LightStream 2020 Operations Guide

LightStream 2020 Command and Attribute Reference Guide

LightStream 2020 Command Line Interface (CLI) Reference Card

LightStream 2020 Traps Reference Manual

LightStream 2020 Online Help Screens

Manage or troubleshoot a LightStream network

LightStream 2020 Release Notes1

LightStream 2020 Operations Guide

LightStream 2020 Administration Guide

LightStream 2020 Command and Attribute Reference Guide

LightStream 2020 Command Line Interface (CLI) Reference Card

LightStream 2020 Traps Reference Manual

LightStream 2020 Online Help Screens

Troubleshoot LightStream hardware

LightStream 2020 Release Notes1

LightStream 2020 Installation and Troubleshooting Manual

LightStream 2020 Site Planning and Cabling Guide

1We recommend that you review the release notes before attempting to install, configure, operate, or troubleshoot a LightStream switch. The release notes contain important information that does not appear in other documents.

Text Conventions

Table 1-2 describes conventions used to distinguish different types of text:

Table 1-2   Text Conventions

Convention Purpose Example

Bold screen literal type

Represents user input.

$ date

Screen literal type

Represents system output

Wed May 6 17:01:03 EDT 1994

Boldface type

Denotes names of commands, command arguments, and switches. Command names are case sensitive; enter them exactly as they appear in the text.

Issue the clear command.

Italic type

Used for titles of documents and for emphasis.

LightStream 2020 Configuration Guide

File names are case sensitive.

Angle brackets < >

Indicate user-specified parameters or classes of user responses. When you see this notation in a syntax statement, make the substitution but do not type the angle brackets.

If you see:

set port <c.p> <state>

 

you might type:

set port 4.3 active

Square brackets [ ]

Indicate keys on the keyboard, or optional arguments or parameters for commands. You can omit optional arguments and parameters in any command.

Press [Return].

 

cli> help [<topic>]

Caret symbol ^

When the caret symbol precedes a character, it refers to the control key.

^X is the same as [Control] X

Curly braces { }

Indicate a choice of arguments or parameters for commands. Arguments or parameters are separated by a vertical line {|}, and you must select one.

cli> set cli traplevel {off|info|oper|trace|debug}


CLI Command Reference

The LightStream 2020 enterprise ATM switch supports a command line interface (CLI). This chapter lists all the CLI commands in alphabetical order, and provides detailed information on each command.

The CLI commands may be grouped by function as shown in Table 2-1:

Table 2-1   CLI Commands and Functions

Command Type Function

CLI control commands

Monitoring and control

MIB commands

Advanced monitoring and control

VLI commands

Virtual LAN internetworking

Diagnostics commands

Diagnostic tests

If you can identify in Table 2-1 the type of action that you wish to perform, refer to Table 2-2 for the commands that you can use to perform that action. Table 2-2 describes the various CLI commands. The commands that you are most likely to use for normal day-to-day operation are the CLI control commands and the MIB commands.

In Table 2-2, the monitoring and control commands set and show are singled out and separated from the CLI control commands because of their complexity.

Table 2-2  

Type Name Function

The set Command

set

Change the state of the specified attribute. See the section "The set Command."

The show Command

show

Display the value of the specified attribute(s). See the section "The show Command."

CLI Control Commands

clear

Clear the screen.

exit

Exit CLI or protected mode.

help

Display CLI help information.

password

Change the password for protected mode.

ping

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

protected

Enter protected mode.

quit

Exit CLI or protected mode.

shell

Execute a LynxOS command under a copy of the LynxOS shell.

source

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

MIB Commands

browse

Browse the MIB tree.

getsnmp

Display the value of a MIB object.

getnextsnmp

Display the value of the object in the MIB tree that follows the specified object.

setsnmp

Change the state of the specified MIB object.

walksnmp

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

VLI Commands

define

Define a bridge filter.

delete

Delete a bridge filter.

Diagnostics Commands

connect

Logically attach the console or modem I/O ports to a given card within a LightStream node.

loadcard

Load the specified file into the specified card, start the card, and establish a console connection between the CLI and the TCS slave on the card.

test

Run field diagnostics tests from the CLI.

CLI Commands

Two other commands are described in the "Diagnostics Commands" section. They require detailed knowledge of the contents and functions of hardware registers and memory locations. These are the commands read and write.

The CLI help facility lists all the commands alphabetically. Refer to Chapter 3 of the LightStream 2020 Operations Guide for a detailed description of the online help facility in the CLI.

The set Command

Use the set command to set the value of a specified MIB object within a LightStream node, or to set the state of the CLI program.

Syntax

set type [ID] parameter1 [parameter2]

Arguments

The type argument may be any of those shown in Table 2-3:

Table 2-3   type Arguments

type Argument Function
set card

Per-card attributes

set chassis

Chassis-wide attributes

set cli

CLI attributes

set collection

Collection records

set config

Configuration changes saved in local database

set modem

Modem attributes

set pid

Per-process attributes

set port

Per-port attributes

set snmp

SNMP control attributes

set stb

Spanning-tree bridge attributes

set tcs

Per-card attributes under TCS

set trap

Display of traps




Note      The set command requires protected mode for set modem, set tcs and set trap only.



Note      The set command requires that the read/write community name be set first to a name that has been assigned the value write in the mma.communities file (unless parameter1 is cli, modem, or snmp). Because the default community name "public" is read only, the set command fails if the read/write community name has not been set first. See the description of the command set snmp community and Chapter 6 of the LightStream 2020 Operations Guide for information on setting the read/write community.


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

  • card#

A card number.

  • active

Set the administrative state of the specified card to active.


Note      When the card is set active from some other state, card parameters are set to defaults, then overwritten from on-board memory (if temporary changes were made) and from the configuration database, in that order. The result can be a combination of defaults, "temporary" changes, and database settings, depending upon which parameters were set in EEPROM and in the configuration database.



Note      After a power reset or reboot of the node, the operational status of a card may be down while its administrative status and configuration register value are both up. To bring the card up in these circumstances, set it to inactive and then to active.


  • inactive

Set the administrative state of the specified card to inactive.


Note      Do not use the Verify function of the configurator when a card is set to inactive. The Verify function copies attribute values from run-time memory. When a card is inactive (or down for any reason), the Verify function can access only the card's type, number, and administrative status. If you choose to write values to the local database, it deletes all other configured attribute values stored there. See the LightStream 2020 Configuration Guide for details about the Verify function.


  • testing

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

  • activeip IPaddress

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.

  • congestion interval ms

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:

  • maxpermitinterval ms

minpermitinterval ms

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

  • mincainfointerval ms

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

  • consoletraplevel {off|oper|info|trace|debug}

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.


Note      There must be a compelling reason to use any arguments other than off or oper. Use set trap for individual traps instead, to avoid flooding the node with traps, which could cripple it.


  • defrouter IPaddress

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.

  • ethernetaddr etheraddr

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

  • ethernetmask mask

Set the subnet mask for the Ethernet address.

  • name chassis_name

Set the chassis name (node name).

  • netmask mask

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

  • primaryswitch {switcha|switchb}

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


Note      This operation resets all cards on the affected device.


  • traplevel {oper|info|trace|debug}

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.


Note      There must be a compelling reason to use any arguments other than off or oper. Use set trap for individual traps instead to avoid flooding the node with traps, which could cripple it.


  • traplog {on|off}

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

  • debug {on|off}

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.

  • echosource {on|off}

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

  • lineedit {on|off}

Turn line editing capability with control keys on or off.

  • log {"logfile"|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.


Note      Always surround the file name or pathname of logfile with quotation marks, as in the following example:


cli> set cli log "cli.log.9502"
  • term termtype

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

  • timer

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

  • traplevel {off|oper|info|trace|debug}

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.


Note      There must be a compelling reason to use any arguments other than off or oper. Use set trap for individual traps instead, to avoid flooding the node with traps, which could cripple it.


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

  • addvar MIB_object

Add MIB_object to the objects subject to the specified collection.

  • create

Create the specified collection.

  • del

Remove the specified collection from the system.

  • delvar MIB_object

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

  • halt

Halt the specified collection.

  • start

Start the specified collection.

Attribute Arguments of set collection

  • begintime [[[yy:]mm:]dd:]hh:mm:ss

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

  • endtime [[[yy:]mm:]dd:]hh:mm:ss

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

  • filesize bytes [: begintime [: endtime]]

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.

  • frequency ss [: begintime [: endtime]]

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

  • lock

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.

  • unlock

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:

SNMP error

Note      After you make configuration changes and write them to the disk, as described above, the local database is out of synch with the global database. As soon as possible, use the verify function in the configuration tool on the network management station to copy configuration changes from the local configuration database on the LightStream node to the global configuration database on the network management station. The verify function retrieves the local settings and allows you to write them over the global values.


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.


Note      The set modem command requires CLI protected mode. (See the protected command.)


set pid

Set the trap level or administrative status of a process.

Syntax

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

Arguments

  • traplevel {oper|info|trace|debug}

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.


Note      There must be a compelling reason to use any arguments other than off or oper. Use set trap for individual traps instead, to avoid flooding the node with traps, which could cripple it.


  • adminstatus {active|inactive}

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

  • active|inactive|testing

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

  • loop {external|internal|remote}

Loop the specified port externally, internally, or remotely.

  • unloop

Unloop the specified port.

Characteristics Arguments of set port

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

  • characteristics csu {none|larse}

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

  • characteristics {dce-bitrate Kbits|dte-bitrate bits}

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.

  • characteristics dce-dte-type {dce|dte|dce-internal}

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.

  • characteristics executechange

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

  • characteristics protocol {trunk|framerelay|frameforward|atm-uni}

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


Note      Trunk and edge protocols cannot be intermixed on a single card.



Note      Use the set config lock command before changing between trunk and any edge protocol. The reason is that the card resets and the value is read back from the local configuration database.


ATM VCI Arguments of set port

  • set port c.p vci vci# {activate|deactivate|del|attribute value}

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:

  • vci vci# activate

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

  • vci vci# deactivate

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

  • vci vci# del

Deactivate and delete VCI vci# from the specified port.

  • vci vci# destnode {chassisID|IPaddress|chassisname}

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).

  • vci vci# destport c.p

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

  • vci vci# destvci destvci#

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.

  • vci vci# insured-rate cells/sec

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

  • vci vci# insured-burst cells

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

  • vci vci# max-rate cells/sec

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).

  • vci vci# max-burst cells

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

  • vci vci# bwtype {guaranteed|insured}

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

  • vci vci# pri {0|1}

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 port c.p bcast-limit {discard-all|forward-all|packets/sec}

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

Discard all broadcast packets sent to this port.

  • forward-all

Forward all broadcast packets sent to this port.

  • packets/sec

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

  • set port c.p bflt ID {block priority|forward priority|del}

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.


Note      These attributes are not affected when the card is reset.


The arguments used with the bflt parameter are as follows:

  • ID

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 port c.p bflt-def {block|forward}

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


Note      This attribute is not affected when the card is reset.


  • set port c.p stb {pri #|enable|disable|pathcost #}

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


Note      These attributes are not affected when the card is reset.


The arguments are as follows:

  • pri #

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

  • { enable | disable }

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.

  • pathcost #

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 port c.p frameforwarding {activate|deactivate|attribute value}

Set the following frame forwarding parameters:

  • frameforwarding {activate | deactivate}

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

  • frameforwarding destnode {chassisID|chassisname}

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).

  • frameforwarding destport c.p

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

  • frameforwarding insured-rate bps

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

  • frameforwarding insured-burst bytes

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

  • frameforwarding max-rate bps

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

  • frameforwarding max-burst bytes

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 port c.p framerelay {lmiconfig|netinterfacetype} value

Set the frame relay parameters as follows:

  • framerelay lmiconfig {none|frif|ansi_t1_617d|q933a}

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

  • framerelay netinterfacetype {uni|nni}

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.

  • set port c.p dlci dlci# {attribute value|activate|deactivate|del}

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:

  • dlci dlci# activate

Enable the circuit on the specified DLCI.

  • dlci dlci# deactivate

Deactivate the specified DLCI.

  • dlci dlci# del

Remove the specified DLCI from the system.

  • dlci dlci# destnode {chassisID|IPaddress|chassisname}

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).

  • dlci dlci# destport c.p

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

  • dlci dlci# destdlci dlci#

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

  • dlci dlci# insured-rate bps

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

  • dlci dlci# insured-burst bytes

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

  • dlci dlci# max-rate bps

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

  • dlci dlci# max-burst bytes

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

FDDI Arguments of set port

  • set port c.p fddi {{aport|bport}parameter|smt action}

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

  • fddi {aport|bport} parameter

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 e