Table of Contents
About This BookAudience
Organization
Related Documentation
Text Conventions
CLI Command Reference
The set Command
Arguments
set card
Syntax
Arguments
set chassis
Syntax
Arguments
set cli
Syntax
Arguments
set collection
Syntax
Action Arguments of set collection
Attribute Arguments of set collection
set config
Syntax
Arguments
Description
set modem
Syntax
Description
set pid
Syntax
Arguments
set port
Description
Syntax
State Arguments of set port
Characteristics Arguments of set port
ATM VCI Arguments of set port
Bridge Arguments of set port
Frame Forwarding Arguments of set port
Frame Relay Arguments of set port
FDDI Arguments of set port
VLI Arguments of set port
set snmp
Syntax
Arguments
Description
set stb
Description
Syntax
Arguments
set tcs
Syntax
Arguments
Description
set trap
Description
Syntax
Arguments
Examples
Syntax
Arguments
show bflt
Syntax
Argument
show card
Syntax
Explanation
Arguments
show chassis
Syntax
Arguments
show cli
Syntax
Arguments
show collection
Syntax
Description
show config
Syntax
Description
show file
Syntax
Arguments
Description
show gid
Syntax
Arguments
show modem
Syntax
Arguments
Description
show nd
Syntax
Arguments
show pid
Syntax
Arguments
show port
Description
Syntax
General Arguments of show port
ATM VCI Arguments of show port
Bridge Arguments of show port
FDDI Arguments of show port
Frame Forwarding Arguments of show port
Frame Relay Arguments of show port
VLI Arguments of show port
show snmp
Syntax
show spt
Syntax
Explanation
show stb
Syntax
Arguments
show tcs
Description
Syntax
Arguments
show trap
Syntax
Arguments
Description
Examples
Syntax
exit
Syntax
Arguments
Description
Example
help
Syntax
Arguments
Description
Example
password
Syntax
Arguments
Description
Example
ping
Syntax
Arguments
Description
Example
protected
Syntax
Arguments
Description
Example
quit
Syntax
Arguments
Description
Example
shell
Syntax
Arguments
Description
Example
source
Syntax
Arguments
Description
Examples
Description
Syntax
Arguments
Examples
getsnmp
Description
Syntax
Arguments
Examples
getnextsnmp
Description
Syntax
Arguments
Examples
setsnmp
Description
Syntax
Arguments
Example
walksnmp
Description
Syntax
Arguments
Example
Diagnostics Commands
Description
Syntax
Arguments
loadcard
Description
Syntax
Arguments
test
Description
Syntax
Switches
read
Description
write
Configuration Attributes
Setting Configuration Attributes
How to Change Attribute Values
Synchronizing Databases
Working with Temporary Configuration Changes
Port Attributes that are Stored in EEPROM
Node Attributes that Look Like Port Attributes
Card Attributes
Port Attributes
Internetworking Attributes
PVC Attributes
VLI Attributes
Card Attributes
Port Attributes
Internetworking Attributes
PVC Attributes
VLI Attributes
MIB Overview
MIB Addresses
Determining MIB Variable Names
Object Identifiers
Port Identifiers
Multiply-Indexed Objects
The cardInfo Subtree
The portInfo Subtree
The portTransmission Subtree
The congestionAvoidance Subtree
The mmaInfo Subtree
The collectInfo Subtree
The lsPort Protocols Subtree
The lsPrivate Subtree
The lsExperimental Subtree
The lsIR Subtree
The lsStatistics Subtree
The tcsInfo Subtree
The lsGID Subtree
The lsPID Subtree
The lsND Subtree
The lwmaInfo 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 AlsoName
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
Colon Commands That Specify Files
Commands That Tailor the Editing Environment
Command Summary
Notes on LynxOS vi
BASH Shell Reference
Name
Copyright
Options
Arguments
Definitions
Reserved Words
Shell Grammar
Comments
Quoting
Parameters
Expansion
Tilde Expansion
Parameter Expansion
Command Substitution
Arithmetic Expansion
Word Splitting
Pathname Expansion
Quote Removal
Redirecting Output
Appending Redirected Output
Redirecting Standard Output and Standard Error
Here Documents
Duplicating File Descriptors
Opening File Descriptors for Reading and Writing
Aliases
Job Control
Signals
Command Execution
Environment
Exit Status
Prompting
Readline
History
Arithmetic Evaluation
Shell Builtin Commands
Invocation
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.
The system overview explains what a LightStream switch is and how it works. It outlines ATM technology and describes LightStream hardware and software.
The site planning and cabling guide (SPCG) tells you how to prepare your site to receive LightStream hardware. It includes space, environmental and electrical requirements, rack selection guidelines, requirements for the management workstation, and information on cables and connectors.
The installation and troubleshooting manual (I&TM) tells you how to install LightStream hardware and software, how to diagnose hardware problems, and how to replace faulty hardware components.
The configuration guide provides the information you need to configure LightStream switches. It describes the configuration tools and how to use them. It describes the configuration database and defines all configurable attributes and their settings. The guide also provides step-by-step configuration procedures.
The 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.
The administration guide describes LightStream network management functions such as setting up a new network, troubleshooting, and optimizing the load across trunks. The guide describes network management tools, then presents step-by-step procedures for performing the functions.
This manual presents an overview of LightStream traps (error and event messages) and a list of operational, SNMP, and informational traps generated by the LightStream switch.
The reference card compactly summarizes the syntax and arguments of all CLI commands.
The release notes provide a software upgrade procedure and describe new features and special considerations, including information on known software bugs.
The LightStream command line interface (CLI) and configuration program both produce online help facilities.
Before attempting to install, configure, operate, or troubleshoot a network of LightStream switches, read the LightStream 2020 System Overview. This overview provides important background information about the LightStream product and the ATM technology on which the product is based. 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: |
|---|---|
|
LightStream 2020 Release Notes1 |
|
|
LightStream 2020 Release Notes1 |
|
|
LightStream 2020 Release Notes1 |
|
|
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 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 Release Notes1 |
| 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:
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 |
|---|---|
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.
| Type | Name | Function |
|---|---|---|
|
Change the state of the specified attribute. See the section "The set Command." |
||
|
Display the value of the specified attribute(s). See the section "The show Command." |
||
|
Send ICMP echo packets to a host and report on any returned packets. |
||
|
Display the value of the object in the MIB tree that follows the specified object. |
||
|
Display the values of all MIB objects in the MIB tree starting with the specified object. |
||
|
Logically attach the console or modem I/O ports to a given card within a LightStream node. |
||
|
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. |
||
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:
| type Argument | Function |
|---|---|
| set card | |
| set chassis | |
| set cli | |
| set collection | |
| set config | |
| set modem | |
| set pid | |
| set port | |
| set snmp | |
| set stb | |
| set tcs | |
| set trap |
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
Arguments
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.
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.
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
Arguments
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:
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.
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 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.
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.
Turn the logging of traps in the traplog file on or off.
set cli
Set values of specified CLI attributes.
Syntax
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.
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"
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.
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
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
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:
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
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
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.
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 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
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
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.
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).
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
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.
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.
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).
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.
