Page 1 ATM Switch Configuration Manual...
Page 3 Notice Notice Cabletron Systems reserves the right to make changes in speciﬁcations and other information contained in this document without prior notice. The reader should in all cases consult Cabletron Systems to determine whether any such changes have been made. The hardware, ﬁrmware, or software described in this manual is subject to change without notice.
Page 4: Fcc Notice
Notice FCC Notice This device complies with Part 15 of the FCC rules. Operation is subject to the following two conditions: (1) this device may not cause harmful interference, and (2) this device must accept any interference received, including interference that may cause undesired operation. NOTE: This equipment has been tested and found to comply with the limits for a Class A digital device, pursuant to Part 15 of the FCC rules.
Page 5 Notice DOC Notice This digital apparatus does not exceed the Class A limits for radio noise emissions from digital apparatus set out in the Radio Interference Regulations of the Canadian Department of Communications. Le présent appareil numérique n’émet pas de bruits radioélectriques dépassant les limites applicables aux appareils numériques de la class A prescrites dans le Règlement sur le brouillage radioélectrique édicté...
Page 6 Notice...
Page 7: Table Of Contents
1.4.1 Listing Virtual Channels ... 1-13 1.5 Creating Permanent Virtual Circuits (PVCs) ... 1-15 1.5.1 Creating a Virtual Path... 1-15 1.5.1.1 Terminating a PVC at a Switch ... 1-18 1.5.1.2 Creating ATM ARP Entries... 1-19 1.5.1.3 Listing ATM ARP Entries ... 1-20 1.5.2 Creating a Virtual Channel...
Page 8 2.3.2.2 Conﬁguring a Host as a Permanent ARP Server... 2-9 2.3.2.3 Conﬁguring a Hewlett-Packard Computer as an ARP Server 2-10 2.3.3 Conﬁguring a Cabletron Switch to be an ARP Server ... 2-11 2.3.4 Classical IP Operation ... 2-12 2.3.5 Operational Issues... 2-13 2.4 Classical IP PVCs...
Page 9 Chapter 4 SONET Conﬁguration 4.1.1 Transmit Indicators... 4-1 4.1.2 Receive Indicators... 4-2 4.2 Conﬁguring SONET Mode ... 4-2 4.3 Conﬁguring SONET Empty Cells... 4-3 4.4 Conﬁguring SONET Loopback ... 4-4 4.4.1 Diagnostic Loopback ... 4-4 4.4.2 Line Loopback ... 4-4 4.5 Displaying SONET Error Counters ...
Page 10 Contents Chapter 7 TP25 Conﬁguration 8.1.1 Transmit Indicators ... 7-1 8.1.2 Receive Indicators ... 7-1 8.2 Conﬁguring TP25 Loopback... 7-2 8.2.1 Line Loopback ... 7-2 8.3 Displaying TP25 Error Counters... 7-4 8.4 TP25 Error Counter Descriptions... 7-4 Chapter 8 TAXI Conﬁguration 9.1.1 Transmit Indicators ...
Page 11 B.2.7 Creating a FORE IP PVC ARP Entry ...B-9 B.2.8 Displaying the ATM ARP Entries...B-10 B.3 Switch Board Conﬁguration Commands ... B-11 B.3.1 Conﬁguring the Clock Scaling Factor on a Switch Board... B-11 B.3.2 Displaying the Board Conﬁguration ...B-12 B.3.3 Displaying the Board Topology...B-13 B.4 IP Conﬁguration Commands...B-14...
Page 12 C.1.4 Restoring the Database... C-4 C.2 Environment Commands ... C-5 C.2.1 CPU Operation ... C-5 C.2.2 Switch Fabric Operation... C-6 C.2.3 Showing Switch Fabric Temperature Information ... C-6 C.2.4 Conﬁguring the Switch Fabric Temperature Thresholds ... C-7 C.2.5 Fan Operation ... C-8...
Page 13 C.4.8 Renaming a FLASH File... C-19 C.5 Setting or Changing the Password ... C-19 C.6 Upgrading the Switch... C-20 C.7 Displaying and Changing the Version of Software ... C-21 C.8 Rebooting the Switch ... C-21 Appendix D AMI Statistics Commands D.2 AAL4 Statistics ... D-2 D.3 AAL5 Statistics ...
Page 14 F.1.2 Topology Database Exchange...F-2 F.1.3 Flooding...F-2 F.1.4 Hierarchical Routing...F-3 F.2 The Physical Network...F-5 F.2.1 Peer Groups...F-8 F.2.2 Peer Group Topology...F-8 F.2.3 Border Switches ...F-8 F.2.4 Peer Group Summary Node (PGSN) ...F-9 F.2.5 Backbone Topology ...F-9 F.2.6 Single Switch Perspective ...F-9...
Page 15: Preface
If you have any questions or problems, please contact Cabletron Systems’ Technical Support. Chapter Summaries Chapter 1 - Conﬁguring PVCs - Describes how to create PVCs on a switch through the ATM Management Interface (AMI). Chapter 2 - Conﬁguring a Classical IP ATM Network - Describes how to design, conﬁgure, and maintain a Classical IP ATM network.
Page 16: Technical Support
AMI commands. Appendix E - SNMP Conﬁguration - Describes the remote SNMP conﬁgura- tion of a switch. Appendix F - PNNI - Describes how this scalable routing and signalling pro- tocol can be used to simplify large network topologies.
Page 17: Typographical Styles
To call your attention to safety and otherwise important information that must be reviewed to ensure correct and complete installation, as well as to avoid damage to the ATM Switch or your system, this manual utilizes the fol- lowing WARNING/CAUTION/NOTE indicators.
Page 18 You risk damaging your equipment and/or software if you do not follow these instructions. It is strongly recommended that you discon- nect the serial cable once you have conﬁgured the ATM switch and then access the switch over the ATM network.
Page 19: Laser Warning
Laser Warning Class 1 Laser Product: This product conforms to applicable requirements of 21 CFR 1040 at the date of manufacture. Class 1 lasers are deﬁned as products which do not permit human access to laser radiation in excess of the accessible limits of Class 1 for applicable wave- lengths and durations.
Page 20: Safety Agency Compliance
PREFACE Safety Agency Compliance This preface provides safety precautions to follow when installing a product. Safety Precautions For your protection, observe the following safety precautions when setting up your equipment: • Follow all warnings and instructions marked on the equipment. •...
Page 21: Modiﬁcations To Equipment
Modiﬁcations to Equipment Do not make mechanical or electrical modiﬁcations to the equipment. Cabletron Systems, Inc., is not responsible for regulatory compliance of a modiﬁed product. Placement of a Product CAUTION To ensure reliable operation of the product and to protect it from overheating, openings in the equipment must not be blocked or cov- ered.
Page 22 PREFACE...
Page 23: Chapter 1 Conﬁguring Pvcs
A1 with VPI|VCI = 0|32 is switched to port B2 with VPI|VCI = 0|35. The translation from input port, VPI, and VCI to output port, VPI, and VCI is achieved via a mapping table in the switch fabric’s memory.
Page 24 The set of mappings in the ATM network used to route cells from a source to a destination are generally referred to as virtual channels and virtual paths. The switch control software will normally use the SPANS protocol, FORE Sys- tems‘ pre-standard signalling protocol, to create the virtual channels and vir- tual paths needed to establish a connection between two ATM endpoints.
Page 25: Virtual Paths
Virtual Paths Virtual paths are used to establish connections between two switch fabrics in an ATM network. Once the switch fabrics are connected via a virtual path, they can use this virtual path to route virtual channels. Virtual Channels Figure 1.2 - Virtual Channels in a Virtual Path A single virtual path can be used to route many virtual channels through the ATM network.
Page 26: Through Paths
Through paths route an entire virtual path through an ATM switch fabric. When a cell is received by a switch fabric on a through path, the VPI is exam- ined to determine the output port and VPI. The VCI component of the ATM header remains unchanged and can have any value.
Page 27 A4|10 -> B4|20 Figure 1.5 - An Example of a Through Path By deﬁnition, through paths will only switch cells in one direction; they are unidirectional. For example, switch fabric X is conﬁgured with the through path B1|20 -> C1|20. If a cell is received on port C1 with VPI: 20, it will not be transmitted on port B1 with a new VPI: 20.
Page 28: Originating And Terminating Paths
As previously noted, originating and terminating paths are points at which a virtual path originates and terminates. For example, if a virtual path exists from switch fabric A to switch fabric B, then there must be an originating path on switch fabric A and a terminating path on switch fabric B.
Page 29: Listing Virtual Paths
AMI), it is possible to display either all of the existing virtual paths on an individual switch fabric or all of the existing virtual paths on a speciﬁed port. To list all of the existing virtual paths on an individual switch fabric, enter the following parameters: conﬁguration vpc show...
Page 30 Configuring PVCs MaxBW MaxVCs Protocol To list advanced information about all of the existing virtual paths, enter the following parameters: conﬁguration vpc show advanced Input Output Port Port terminate terminate terminate terminate terminate terminate terminate terminate 1CTL terminate originate originate originate originate originate...
Page 31 Configuring PVCs The ﬁelds in this display are deﬁned as follows: Input Port Lists the number of the input port of the virtual path. Lists originate if it is an originating path. Indicates the input virtual path. Input VPI Output Port Lists the number of the output port of the virtual path.
Page 32: Virtual Channels
Virtual Channels Virtual channels “ride” inside of virtual paths. The combination of the two speciﬁes a virtual connection. On a switch fabric, each virtual channel switches cells with a speciﬁc VPI and VCI received on a speciﬁc port to another port with a new VPI and a new VCI. Unlike through paths, virtual channels describe a single virtual connection between two endpoints con- nected to a switch fabric.
Page 33 Virtual channels switch cells using both the VPI and VCI values. Both the VPI and VCI values may change when a cell is switched via a virtual channel. For example, the virtual channel C2|1|20 -> D2|9|25 will switch cells received on port C2 with VPI: 1 and VCI: 20 such that they are transmitted out port D2 with VPI: 9 and VCI: 25.
Page 34 Configuring PVCs Before a virtual channel can be created, the corresponding terminating and origi- nating paths must exist. For example, before the channels shown on the switch fabric in Figure 1.11 can be created, the terminating path C3|3 must exist.
Page 35: Listing Virtual Channels
AMI), it is possible to display either all of the existing virtual channels on an individual switch fabric or all of the existing virtual channels on a speciﬁed port. To list all of the existing virtual channels on an individual switch fabric, enter the following parameters: conﬁguration vcc show...
Page 36 Configuring PVCs Output VCI Indicates the outgoing virtual channel number. Shows the integer index that refers to the speciﬁc trafﬁc contract assigned to this VCI. Displays what type of protocol is running on this Protocol channel. Can be spans, pvc, or uni30. 1-14...
Page 37: Creating Permanent Virtual Circuits (Pvcs)
PVC will be created every time the switch control proces- sor (SCP) is restarted. Note that this conﬁgu- ration database can not be edited. The user can, however, enter AMI and manually delete the PVC that was created.
Page 38 Configuring PVCs -upc <index> -reserved <Kbs> -maxvci <maxvci> -reserved <Kbs> -maxvci <maxvci> The advanced options are as follows: -shapeovpi <vpi> 1-16 ovpi Indicates the outgoing virtual path number. Indicates the integer index that refers to a spe- ciﬁc trafﬁc contract. If no index is speciﬁed, then no trafﬁc policing will take place on this VPI.
Page 39 -vbrob <percent> Indicates the bandwidth overbooking level assigned to this path, speciﬁed as a percentage. Enter an integer value greater than or equal to 1. The default is 100, which means that no over- booking has been deﬁned. Values less than 100 cause underbooking.
Page 40: Terminating A Pvc At A Switch
Configuring PVCs The following is an example of how to create a virtual path on an SFCS-1000. To create a through path going in port 2A1, vpi 1 on on the switch board installed in slot 2 and going out port 4B1, vpi 1 on on the switch board installed in slot 4, enter the following: localhost::configuration vpc>...
Page 41: Creating Atm Arp Entries
1.5.1.2 Creating ATM ARP Entries To create a FORE IP PVC ARP entry, log in to AMI (see Appendix A of this manual for information about logging into AMI). Data on this PVC is encap- sulated using null encapsulation (also known as VC-based multiplexing) as speciﬁed in RFC-1483.
Page 42: Listing Atm Arp Entries
Configuring PVCs 1.5.1.3 Listing ATM ARP Entries To verify that the ARP entries exist correctly for the outgoing PVC connection from the SCP to the host, log in to AMI (see Appendix A of this manual for information about logging into AMI). To display the ATM ARP cache, enter the following parameters: conﬁguration atmarp show IPaddress...
Page 43: Creating A Virtual Channel
1.5.2 Creating a Virtual Channel To create a new virtual channel, log in to AMI and enter the following param- eters: conﬁguration vcc new <iport> <ivpi> <ivci> <oport> <ovpi> <ovci> -upc <index> -upc<index> Indicates the incoming port number. iport ivpi Indicates the incoming virtual path number.
Page 44 The following is an example of how to create a virtual channel on an SFCS-1000. To create a vcc going in port 2A1, vpi 0, vci 100 on the switch board installed in slot 2 and going out port 4B1, vpi 0, vci 100 on the switch board installed in slot 4, enter the following: localhost::configuration vcc>...
Page 45: Trafﬁc Types
Trafﬁc Types Quality of Service (QOS) Management is based on the bandwidth parameters associated with a virtual connection and the class of service and ATM Adap- tation Layer (AAL) used for that connection. In order to support voice, video, and data, the ATM Forum has deﬁned four classes of service, or trafﬁc types: Constant Bit Rate (CBR), Variable Bit Rate (VBR), Available Bit Rate (ABR), and Unspeciﬁed Bit Rate (UBR).
Page 46: Trafﬁc Policing (Usage Parameter Control)
1.7.2 Leaky Bucket Algorithm The next important concept is the leaky bucket algorithm. Leaky buckets are a mechanism by which cells entering the switch fabric are monitored for com- pliance with UPC trafﬁc contracts that have been negotiated at connection set-up time.
Page 47: Uni 3.0 Upc Trafﬁc Contract Parameters
The leaky bucket algorithm is a timer which measures the cells entering the switch fabric against the parameters listed above. As a cell arrives, the timer assesses if the cell is on time, late, or early. If the cell is determined to be on time or late (within the trafﬁc parameters speciﬁed), the cell is allowed to pass...
Page 48 Configuring PVCs The ubr contract is for UBR trafﬁc. Since this is best-effort trafﬁc with no bandwidth guarantees provided, this type of trafﬁc can not be policed against bandwidth parameters. The cbr <pcr01> contract is for CBR trafﬁc. It only uses the ﬁrst leaky bucket to assess the PCR of the combination of CLP = 0 cells plus the CLP = 1 cells.
Page 49: Ami Upc Commands
1.7.4 AMI UPC Commands AMI allows the user to create a UPC contract using these combinations of trafﬁc parameters. To create a UPC contract, log into AMI and enter the fol- lowing parameters: localhost::configuration upc> new <index> [<UPC>] [-cdvt <us>] [aal5epd] [-name <name>] Where UPC is one of the following combinations of traffic parameters: <pcr01>...
Page 50 Configuring PVCs 1-28...
Page 51: Conﬁguring A Classical Ip Atm Network
CHAPTER 2 Introduction This chapter describes how to design, conﬁgure, and maintain a Classical IP ATM network. The term classical indicates that the ATM network has the same properties as existing legacy LANs. That is, even though ATM technol- ogy allows for large, globally connected networks, for example, it is only used in the LAN environment as a direct replacement of existing LAN technology.
Page 52: Logical Ip Subnets
Configuring a Classical IP ATM Network 2.1.1 Logical IP Subnets An important concept in Classical IP networks is that of a Logical IP Subnet (LIS). An LIS is a group of hosts conﬁgured as members of the same IP subnet (that is, they have the same IP network and subnetwork numbers).
Page 53: Spans Interface
2.1.3 SPANS Interface While each of the qa interfaces for a given physical interface is designed to support Classical IP using Q.2931 signalling, a SPANS interface (usually called fa, but user conﬁgurable) also exists for each physical interface. The fa interface supports FORE IP on top of SPANS signalling.
Page 54: Address Registration And Ilmi
Configuring a Classical IP ATM Network Address Registration and ILMI Before a host can establish connections over a physical interface, the host must know the NSAP address for that interface. The primary purpose of Interim Local Management Interface (ILMI) is to discover and register these NSAP addresses dynamically.
Page 55: Operating With Ilmi Support
If ILMI is not supported on a particular SCP or host in a given network, then the NSAP addresses must be manually configured. Because a non-Cabletron switch does not support ILMI, it can not supply an NSAP prefix to the hosts. Therefore, the user must assign a unique, valid prefix to the switch. Addition- ally, the same prefix should be used for all hosts in the LIS.
Page 56: Arp And Arp Servers
Configuring a Classical IP ATM Network ARP and ARP Servers 2.3.1 Theory In order for a host to establish a connection to another host, it must ﬁrst deter- mine the other host’s NSAP address. ATM ARP (ATM address resolution pro- tocol) is the procedure used to resolve an IP address into an ATM address.
Page 57: Conﬁguring A Host To Be An Arp Server
2.3.2 Conﬁguring a Host to be an ARP Server The following procedures list the required steps to conﬁgure a host as an ARP server. Before proceeding, several preconditions MUST be met. You must also obtain both the interface name and ARP server NSAP address. The preconditions are as follows: 1.
Page 58: Conﬁguring A Host As An Arp Server For One-Time Use
Configuring a Classical IP ATM Network NOTE: If you are using a windowed graphical user interface, keep the window with the NSAP address open because you will need to cut and paste this address into several locations. If not, carefully write down the address so you can add it correctly to the other locations.
Page 59: Conﬁguring A Host As A Permanent Arp Server
3. From the command prompt in this directory, issue the following command: atmarp -p <NSAP address> <interface name> The location of the ATM boot ﬁle is a function of the type of host in which the FORE adapter has been installed. On your system, the ﬁles may have been copied to another location during the installa- tion process.
Page 60: Conﬁguring A Hewlett-Packard Computer As An Arp Server
Configuring a Classical IP ATM Network 3. On each host requiring service from the ARP server, in the direc- tory in which the ATM boot ﬁle is stored, edit the boot ﬁle. For example, for an ESA-200 adapter, the ﬁle name is fore_atm. In this ﬁle, add the following line: atmarp -p <ARP_server_NSAP_address>...
Page 61: Conﬁguring A Cabletron Switch To Be An Arp Server
2.3.3 Conﬁguring a Cabletron Switch to be an ARP Server Cabletron’s ATM switches also have the capability of being an ARP server. To conﬁgure a Cabletron ATM switch as an ARP server, perform the following steps on only one of the SCPs: 1.
Page 62: Classical Ip Operation
Configuring a Classical IP ATM Network 2.3.4 Classical IP Operation Once a host knows its own ATM address and the ATM address of its ARP server it will attempt to establish a connection to the ARP server, which will be used to send ARP requests and receive ARP replies. When the connection to the ARP server has been established, the ARP server sends an inverse ARP (InARP) request on the new VC to learn the host’s IP address.
Page 63: Operational Issues
2.3.5 Operational Issues Certain hosts in an LIS may not support Classical IP. It is still possible to com- municate with these hosts (and for these hosts to communicate with one another) by using static ARP entries. If a host does not support Classical IP, its IP-to-ATM address mapping should be placed in its ARP server’s cache as a static entry.
Page 64: Classical Ip Pvcs
Classical ARP or ILMI, it is still possible to set up an SVC using work-arounds. If a host or a switch in an LIS does not support Q.2931, how- ever, it is not possible to establish an SVC. In this case, a Classical IP PVC can be used for communication.
Page 65: Revalidation And Removal
Configuring a Classical IP ATM Network 2.4.2 Revalidation and Removal Normally, the device driver periodically checks that its PVCs are still estab- lished and functioning. A host revalidates a PVC every 15 minutes by sending InARP requests over the PVC, if the user speciﬁes that revalidation should occur by choosing 1 as the revalidate option to atmarp -c.
Page 66: Debugging
• On the host, atmarp -g displays the ATM address of the current ARP server for the LIS associated with the given interface. For the switch, AMI command conﬁguration atmarp arpserver show interface provides the same information.
Page 67: Conﬁguring The Network
• Conﬁguring a third-party host that has no ILMI and no RFC-1577 support • Conﬁguring a third-party switch that has ILMI support, but no RFC-1577 support • Conﬁguring a third-party switch that has no ILMI support, but has RFC-1577 support Configuring a Classical IP ATM Network 2-17...
Page 68: Third-Party Host With No Ilmi And No Rfc-1577 Support
NSAP address that has the same preﬁx as the switch fabric to which it is connected. 3. Conﬁgure the switch so that it has a static route to the third-party host using the following AMI command: conﬁguration nsap route new <NSAP> <mask> -port <port> -vpi <vpi>...
Page 69: Third-Party Switch With Ilmi And No Rfc-1577 Support
Switch A = FORE Systems host Figure 2.2 - Conﬁguring a Third-Party Switch with ILMI Support and No RFC-1577 1. Be sure that FORE software has been installed on all of the hosts and that ILMI was set in the process. Let ILMI dynamically per- form address registration for all of the hosts.
Page 70: Third-Party Switch With Rfc-1577 And No Ilmi Support
Configuring a Classical IP ATM Network 2.6.3 Third-Party Switch with RFC-1577 and No ILMI Support To conﬁgure a network with a third-party vendor’s switch that does not sup- port ILMI, but does support RFC-1577 (as shown in Figure 2.3), perform the...
Page 71 Configuring a Classical IP ATM Network 4. Conﬁgure two static NSAP routes on the third-party switch, one to each of the Cabletron switches to which the third-party switch is connected, using the third-party vendor’s conﬁguration software. 2-21...
Page 72 Configuring a Classical IP ATM Network 2-22...
Page 73: Chapter 3 Conﬁguring An Emulated Lan
ATM host system (PC, Macintosh, UNIX workstation, switch, or bridge device). In the current software release, the LECS, LES, and BUS may reside either in a Cabletron switch or in a UNIX workstation running SunOS version 4.1.x. Additional software features include a colocated BUS (also referred to as an intelligent BUS or a LES/BUS pair) and a LEC “failover”...
Page 74: Emulated Lan Components
For exam- ple, the LECS could reside in a switch, while the LES and BUS reside in a workstation. In the current 4.0 software, the LECS, LES, and BUS are sup- ported only for switches and for SunOS.
Page 75: Lan Emulation Client (Lec)
3.2.1 LAN Emulation Client (LEC) The LEC is the component in an end system that performs data forwarding, address resolution, and other control functions when communicating with other components within the ELAN. It also provides a MAC level emulated Ethernet interface and appears to higher level software as though a physical Ethernet interface is present.
Page 76: Emulated Lan Operation
Configuring an Emulated LAN Emulated LAN Operation This section describes the operation of an ELAN and its components from the point of view of a LEC. The operation of an ELAN may be divided into three phases: 1. Initialization 2. Registration and Address Resolution 3.
Page 77 LEC1 CONFIGURATION - DIRECT CONTROL - DIRECT CONTROL - DISTRIBUTE MULTICAST - SEND MULTICAST - FORWARD DATA - DIRECT LEC2 Figure 3.2 - ELAN Operation Configuring an Emulated LAN LECS engineering...
Page 78: Initialization
Configuring an Emulated LAN 3.3.1 Initialization Upon initialization, LEC1 obtains its own ATM address via address registra- tion. LEC1 obtains the address of the LECS in one of three ways: via manual conﬁguration, via the “well-known” address deﬁned by the ATM Forum’s LANE standards (47.0079.00.000000.0000.0000.0000.00A03E000001.00), or via PVC (0,17).
Page 79: Data Transfer
3.3.3 Data Transfer When LEC1 receives a network-layer packet from a higher layer protocol to transmit to some destination MAC address (for example, LEC2), LEC1 ini- tially does not know the corresponding ATM address of the destination. Con- sequently, LEC1 transmits an LE_ARP request to the LES. NOTE: The example shown in Figure 3.2 assumes that LEC2 has already registered with the...
Page 80: Conﬁguring An Elan
Configuring an Emulated LAN Conﬁguring an ELAN To conﬁgure an ELAN on a switch, you must log into AMI on a switch run- ning software version 4.0 and use the commands found under conﬁguration lane. NOTE: There are three major steps that the system administrator should follow in order to conﬁgure and maintain ELANs:...
Page 81: Conﬁguring An Lecs Conﬁguration Database File
3.4.1 Conﬁguring an LECS Conﬁguration Database File The LECS uses a text conﬁguration ﬁle to contain the conﬁguration informa- tion needed by LECs that wish to participate in an ELAN. The LECS conﬁgu- ration ﬁle may be built and edited using a text editor such as vi or emacs. 3.4.1.1 Before You Begin Before building or modifying the LECS conﬁguration ﬁle, you should ﬁrst determine the topology of the ELAN or ELANs that you want to administer.
Page 82: Lecs Conﬁguration File Syntax
Configuring an Emulated LAN 3.4.1.2 LECS Conﬁguration File Syntax Each line that you enter in the conﬁguration ﬁle takes the general form: [[group].]key : value The group ﬁeld may represent: • ELANs (by name) - ELAN names are case-sensitive, and may not exceed 32 characters in length •...
Page 83 Table 3.1 deﬁnes the various key parameters that may be entered in the con- ﬁguration ﬁle. The default value for each parameter is also given. Table 3.1 - LECS Conﬁguration File Parameters Parameter .LAN_Type: Ethernet/IEEE 802.3 .Maximum_Frame_Size: 1516 .Control_TimeOut: 120 .Maximum_Unknown_Frame_Count: 1 .Maximum_Unknown_Frame_Time: 1 .VCC_TimeOut_Period: 1200...
Page 84: Deﬁning An Elan
Configuring an Emulated LAN Lines beginning with # may be inserted if you wish to include comments or to improve the clarity of the presentation when the ﬁle is viewed or printed. These lines are ignored when the ﬁle is read. Lines may be continued by escaping the end-of-line with a backslash “\”...
Page 85 If you want to control which clients may or may not join a given ELAN, two additional keys, Accept and Reject, whose values are comma-separated lists of matching elements, may be used. These values may be: a MAC address, engineering.Accept: 0020480605b2 , 002048080011 , 0020481020ef an ATM address and equal-length bit mask, engineering.Accept: 47000580FFE10000000000000000204800000000 \ or an ATM address containing “don’t-care”...
Page 86: Deﬁning A Client
Configuring an Emulated LAN 3.4.1.4 Deﬁning a Client Clients need not be deﬁned in the LECS conﬁguration ﬁle. Typically, you would deﬁne a client for the purpose of overriding one or more of the default conﬁguration parameters for that particular client. A client is deﬁned by using its ATM or MAC address in the group ﬁeld, and perhaps giving the name of its ELAN as the value of the LAN_Name key.
Page 87: Lecs Control Parameters
3.4.1.5 LECS Control Parameters Specifying values for keys in the LECS group provides control over the opera- tion of the LECS process. NOTE: If you change the values of the LECS control parameters while the LECS process is running, the new values do not take effect until the LECS process is stopped, and then restarted.
Page 88: Sample Lecs Conﬁguration File
Configuring an Emulated LAN 3.4.2 Sample LECS Conﬁguration File CAUTION NOTE: The sample LECS conﬁguration ﬁle shown at the end of this section in Figures 3.3 and 3.4 deﬁnes three ELANs: • default • engineering • marketing The Match.Ordering statement speciﬁes the ELAN names in the order that prospective clients will attempt to join.
Page 89 LEC “failover” mechanism. marketing|0 deﬁnes the primary services for the ELAN. If marketing|0 fails, LECs connected to it can auto- matically switch to marketing|1 and continue operating (while periodically attempting to rejoin marketing|0). If marketing|1 were also to fail, the LECs could then switch to services on marketing|2.
Page 90 Configuring an Emulated LAN # Parameters for elan: engineering engineering.Address: 47.0005.80.ffe100.0000.f21a.01b9.0020480605b2.11 engineering.Accept: 002048080011 , 0020481020ef engineering.Maximum_Frame_Size: 4544 # Parameters for elan: marketing|0 marketing|0.Address: 47.0005.80.ffe100.0000.f21a.01b9.0020480605b2.21 marketing|0.Accept: 002048080011 , 0020481020ef # Parameters for elan: marketing|1 marketing|1.Address: 47.0005.80.ffe100.0000.f21a.01b9.0020480605b2.23 marketing|1.Accept: 002048080011 , 0020481020ef # Parameters for elan: marketing|2 marketing|2.Address: 47.0005.80.ffe100.0000.f21a.01b9.0020480605b2.25 marketing|2.Accept: 002048080011 , 0020481020ef...
Page 91: The Default Lecs Conﬁguration File
3.4.3 The Default LECS Conﬁguration File A default LECS conﬁguration ﬁle is installed with software version 4.0. It is reproduced below for reference. # This sample LECS configuration file contains the minimum information # needed to start a default ELAN that all clients can join. # replace the '4's below with the ATM address of the LES.
Page 92 Configuring an Emulated LAN As supplied, this ﬁle allows you to set up a default ELAN that accepts any client that wants to join. Before you can use the supplied ﬁle, you must mod- ify it as follows: 1. Obtain the ATM address of the machine where the LES for the default ELAN will be started.
Page 93: Starting The Lan Emulation Services
SFCS-1000 is lecs.cfg. NOTE: On a 9A000, an SFCS-200BX, an SFCS- 200WG, and an SFCS-1000, this ﬁle is retrieved via tftp. After you have retrieved the LECS conﬁguration database ﬁle, use the follow- ing AMI command to start the LECS service on the switch: conﬁguration lane lecs new <LECS Selector byte (HEX)>...
Page 94 Configuring an Emulated LAN enter something similar to the following: conﬁguration lane lecs new 0x0c -db lecs.cfg Use the following AMI command to verify that the LECS has been started and is running. The OperStatus ﬁeld should display up, meaning that the LECS is enabled.
Page 95: Creating A Les And A Bus
LES, which means that the LES and BUS services for a particular ELAN will be started together and will be running on the same switch. This conﬁguration may pro- vide better BUS performance. To do this, use the following AMI command: conf lane les new <LES Selector byte (HEX)>...
Page 96: Starting The Lec(S) And Joining An Elan
ﬁle), enter the following: conﬁguration lane lec new 0 default 3-24 The switch software only allows you to create an instance of a LEC on a switch. To create an instance of a LEC on a host, you must use the ForeRunner VLAN Manager ForeRunner host adapter.
Page 97 If you decide to use the manual mode, you must enter either a LECS address other than the well-known address or you must enter a LES address. If you enter a LES address, this means that the LEC bypasses the LECS and directly contacts the speciﬁed LES.
Page 98: Conﬁguring The Lec Failover Mechanism
Configuring an Emulated LAN 3.4.5.2 Conﬁguring the LEC Failover Mechanism An added feature of 4.0 software is the LEC failover mechanism. This feature allows multiple redundant services to be conﬁgured for an ELAN as shown in the sample LECS conﬁguration ﬁle in 3.4.2. Consequently, to start LECs that join ELAN marketing and make use of the failover mechanism set up in the sample LECS conﬁguration ﬁle, enter the following AMI commands: conﬁguration lane lec new aa marketing|0...
Page 99: Chapter 4 Sonet Conﬁguration
CHAPTER 4 SONET network modules may require some additional conﬁguration. There are several parameters that can be conﬁgured in order to work with other SONET equipment or to perform testing on the SONET ports. SONET Front Panel LEDs There is an LED corresponding to both the transmit and receive lines of each SONET port.
Page 100: Receive Indicators
SONET Configuration 4.1.2 Receive Indicators The LED corresponding to the receive line of the port has the following mean- ings depending on the color: Conﬁguring SONET Mode There are two modes of operation that the SONET ports support: sonet and sdh.
Page 101: Conﬁguring Sonet Empty Cells
The <port> variable indicates the SONET port that is to be modiﬁed and the (sonet|sdh) variable indicates the mode of operation that is to be used for the speciﬁed port. If there are no SONET ports on the switch fabric, then this option is disabled.
Page 102: Conﬁguring Sonet Loopback
After the loopback mode is modiﬁed on a SONET port, the SCP immediately puts that change into effect on that switch fabric. At the same time, that infor- mation is entered into the conﬁguration database ﬁle on the SCP so that the change will be put into effect every time the switch control software starts on that particular SCP.
Page 103 To Network P a r / S e r Diagnostic Line S e r / P a r From Network Figure 4.1 - SONET Single Port Loopback Diagram SONET Configuration Section Section...
Page 104: Displaying Sonet Error Counters
SONET Configuration Displaying SONET Error Counters AMI allows the user to display several SONET counters. The counters can be accessed by logging in to AMI. Enter the following parameters at the prompt to display the SONET network module statistics: sonet Port 1A1 Counter ------------------------------ sonetSectionBIPs sonetSectionLOSs...
Page 105: Sonet Error Counter Descriptions
SONET Error Counter Descriptions sonetSectionBIPs sonetSectionLOSs sonetSectionLOFs sonetLineBIPs sonetLineFEBEs SONET Configuration The number of Section BIP-8 (Bit Interleaved Parity) errors that have been detected since the last time the port has been reset. The calculated BIP-8 code is compared with the BIP-8 code extracted from the B1 byte of the following frame.
Page 106: Sonetlineferfs
SONET Configuration sonetLineAISs sonetLineFERFs sonetPathBIPs sonetPathFEBEs sonetPathLOPs sonetPathAISs The number of seconds in which line Alarm Indi- cation Signal (AIS) has occurred. A line AIS is asserted when a 111 binary pattern is detected in bits 6, 7, 8 of the K2 byte for ﬁve consecutive frames.
Page 107: Sonetpathyellows 23997
sonetPathYellows The number of seconds in which path yellow alarm has occurred. A path yellow alarm is detected by extracting bit 5 of the path status byte. If bit 5 is high for ten consecutive frames, a yellow alarm is declared. A yellow alarm is cleared when bit 5 is low for ten consecutive frames.
Page 108: Conﬁguring Sonet Timing
After the clocking source is changed on a SONET port, the SCP immediately puts that change into effect on that switch fabric. At the same time, that infor- mation is entered into the conﬁguration database ﬁle on the SCP so that the change will be put into effect every time the switch control software starts on that particular SCP.
Page 109: Conﬁguration
CHAPTER 5 If your Cabletron switch is equipped with one or more DS-3 network mod- ules, some additional conﬁguration may be necessary. There are several parameters which can be conﬁgured in order to work with other DS-3 equip- ment or to perform testing on the switch‘s DS-3 ports.
Page 110: Conﬁguring Ds-3 Mode
(plcp|hcs) variable is the mode of operation to be used for the port. It is crit- ical that both ends of the DS-3 link be conﬁgured with the same mode, regard- less of which one is chosen. If there are no DS-3 ports on the switch fabric, then this option is disabled.
Page 111: Conﬁguring Ds-3 Empty Cells
(idle|unassigned) variable indicates the type of cells that the speciﬁed port sends as ﬁller when the port is not sending data. The default setting is unas- signed. If there are no DS-3 ports on the switch fabric, then this option is dis- abled.
Page 112: Conﬁguring Ds-3 Framing
The <port> variable indicates the DS-3 port that is to be modiﬁed and the (cchannel|cbit) variable is the type of framing for the port. The default set- ting is cbit (cbitparity). If there are no DS-3 ports on the switch fabric, then this option is disabled.
Page 113: Conﬁguring Ds-3 Payload Scrambling
After scrambling is enabled or disabled on a DS-3 port, the SCP immediately puts that change into effect on that switch fabric. At the same time, that infor- mation is entered into the conﬁguration database ﬁle so that the change will be put into effect every time the switch control software starts on that particu- lar SCP.
Page 114: Conﬁguring Ds-3 Loopback
After the loopback state is modiﬁed on a DS-3 port, the SCP immediately puts that change into effect on that switch fabric. At the same time, that informa- tion is entered into the conﬁguration database ﬁle so that the change will be put into effect every time the switch control software starts on that particular SCP.
Page 115: Cell Loopback
This connects the receiver to the transmitter. The DS-3 stream transmitted by the switch to a port is looped back to the switch. The DS-3 stream is still trans- mitted to the network, but the incoming DS-3 stream is ignored.
Page 116: Displaying Ds-3 Error Counters
DS-3 Configuration Displaying DS-3 Error Counters The user can display several DS-3 counters by logging in to AMI. Enter the following parameters to display the DS-3 network module statistics: ds3 Port 1C1 Counter ------------------------------ ds3FramingLOSs ds3FramingLCVs ds3FramingSumLCVs ds3FramingFERRs ds3FramingOOFs ds3FramingFERFs ds3FramingAISs ds3FramingPbitPERRs ds3FramingCbitPERRs...
Page 117: Error Counter Descriptions
DS-3 Error Counter Descriptions ds3FramingLOSs ds3FramingLCVs ds3FramingSumLCVs ds3FramingFERRs ds3FramingOOFs ds3FramingFERFs ds3FramingAISs ds3FramingPbitPERRs ds3FramingCbitCERRs ds3FramingFEBEs ds3PlcpFERRs Indicates the number of seconds in which Loss of Signal (LOS) errors were detected by the DS3 Receive Framer block. Shows the number of Line Code Violations (LCV) that were detected by the DS3 Receive Framer block.
Page 118 DS-3 Configuration ds3PlcpLOFs ds3PlcpBIP8s ds3PlcpFEBEs ds3PlcpYellows ds3AtmHCSs ds3AtmRxCells ds3AtmTxCells 5-10 Shows the number of seconds in which Loss Of Frame (LOF) errors were detected by the PLCP (Physical Layer Convergence Protocol) receiver. LOF is declared when an Out-Of-Frame state persists for more than 1ms. LOF is removed when an in-frame state persists for more than 12ms.
Page 119: Conﬁguring Ds-3 Timing
After the clocking source is changed on a DS-3 port, the SCP immediately puts that change into effect on that switch fabric. At the same time, that infor- mation is entered into the conﬁguration database ﬁle so that the change will be put into effect every time the switch control software starts on that particu- lar SCP.
Page 120 DS-3 Configuration 5-12...
Page 121: Conﬁguration
CHAPTER 6 E-3 network modules may require some additional conﬁguration. There are several parameters that can be conﬁgured in order to work with other E-3 equipment or to perform testing on the E-3 ports. E-3 Front Panel LEDs There is an LED corresponding to both the transmit and receive lines of each E-3 port.
Page 122: Conﬁguring E-3 Mode
(SCP) immediately puts that change into effect on that switch fabric. At the same time, that information is entered into the conﬁguration database ﬁle on the SCP so that the change will be put into effect every time the switch control software starts on that particular SCP.
Page 123: Conﬁguring E-3 Loopback
(cell|payload|diag|line|none) variable indicates the type of loopback on the port. The default loopback setting is none which means that no loopback will take place on that port. If there are no E-3 ports on the switch fabric, then this option is disabled.
Page 124: Cell Loopback
E-3 Configuration Network TRAN D I A G N O S T I C P A Y L O A D From FRMR Network 6.4.1 Cell Loopback When enabled, the E-3 stream received from the network is unframed into ATM cells. The cells are then reframed and transmitted back to the network. 6.4.2 Payload Loopback When enabled, the E-3 stream received from the network has the E-3 over- head bits re-inserted and is retransmitted to the network.
Page 125: Conﬁguring E-3 Empty Cells
ﬁller when the port is not sending data. The default setting is unas- signed. If there are no E-3 ports on the switch, then this option is disabled. After the type of empty cells is modiﬁed on a E-3 port, the SCP immediately puts that change into effect on that switch fabric.
Page 126: Displaying E-3 Error Counters
E-3 Configuration Displaying E-3 Error Counters The user can display several E-3 counters by logging in to AMI. Enter the fol- lowing parameters to display the E-3 network module statistics: e3 Port 1D1 Counter ------------------------------ e3FramingLOSs e3FramingLCVs e3FramingFERRs e3FramingOOFs e3FramingFERFs e3FramingAISs e3FramingBIP8s e3FramingFEBEs...
Page 127: Error Counter Descriptions
E-3 Error Counter Descriptions e3FramingLOSs e3FramingLCVs e3FramingFERRs e3FramingOOFs e3FramingFERFs e3FramingAISs e3FramingFEBEs e3FramingBIP8s e3PlcpFERRs e3PlcpLOFs Speciﬁes the number of seconds in which Loss Of Signal (LOS) errors were detected by the E3 Receive Framer block. Displays the number of Line Code Violations (LCV) that were detected by the E3 Receive Framer block.
Page 128 E-3 Configuration e3PlcpBIP8s e3PlcpFEBEs e3PlcpYellows e3AtmHCSs e3AtmRxCells e3AtmTxCells Indicates the number of BIP-8 (Bit Interleaved Parity - 8) error events. The BIP-8 is calculated over the Path Overhead ﬁeld and the associated ATM cell of the previous frame. A BIP-N is a method of error monitoring.
Page 129: Conﬁguring E-3 Timing
If the port source becomes unavailable, the on-board crystal takes over as the transmit clock source. If there are no E-3 ports on the switch fabric, then this option is disabled. For more information about how to conﬁg- ure the internal timing source, please refer to the section on Network Module Conﬁguration in Appendix B of this manual.
Page 130 E-3 Configuration 6-10...
Page 131: Chapter 7 Tp25 Conﬁguration
CHAPTER 7 If your switch fabric is equipped with one or more TP25 (25 Mbps) network modules, there is some additional conﬁguration that may be necessary. There are several parameters which can be conﬁgured in order to work with other TP25 equipment or to perform testing on the TP25 ports.
Page 132: Conﬁguring Tp25 Loopback
If there are no TP25 ports on the switch, then this option is disabled. After the loopback mode is modiﬁed on a TP25 port, the SCP immediately puts that change into effect on that switch fabric.
Page 133 TP25 Configuration Cell TC Layer Buffer Switch LINE Fabric Figure 7.1 - TP25 Single Port Loopback Diagram...
Page 134: Displaying Tp25 Error Counters
TP25 Configuration Displaying TP25 Error Counters The user can display several TP25 counters by logging in to AMI. Enter the following parameters to display the TP25 network module statistics: tp25 Port 1A1 Counter ------------------------------ tp25ErrorSymbol tp25AtmHCSs tp25AtmRxCells tp25AtmTxCells Press return for more, q to quit: q TP25 Error Counter Descriptions tp25ErrorSymbols tp25AtmHCSs...
Page 135: Chapter 8 Taxi Conﬁguration
TAXI format and are shipped preconﬁgured. No additional conﬁguration is needed for the TAXI network modules to interoperate with another Cabletron Systems switch or with any other 4B/5B TAXI interface. TAXI Front Panel LEDs There is an LED corresponding to both the transmit and receive lines of each TAXI port.
Page 136: Conﬁguring Taxi Loopback
(diag|none) variable indicates the type of loopback to be used on the speci- ﬁed port. The default loopback setting is none, which means that no loop- back will take place on that port. If there are no TAXI ports on the switch fabric, then this option is disabled.
Page 137: Appendix Aami Overview
The switch software provides switch and connection management, IP connec- tivity, and SNMP network management. The Switch Control Software (SCS) is the “brains” of the switch. The SCS controls the switch board(s) and handles connection set-up and tear-down duties. The SCS can also communicate with other FORE Systems switches using the SPANS NNI protocol to learn net- work topology and establish connections across multiple switches.
Page 138 AMI Overview Additionally, the user only needs to enter the minimum number of letters in a command which would make the command unique to that level. For exam- ple, the user could enter co m s instead of conﬁguration module show. However, the minimum number of letters entered must also distinguish the command from global commands, such as top or up.
Page 139: Login From Serial Port
A.1 Initial Login from Serial Port or Telnet The user can log in to the switch either through the serial port or through the Ethernet port using telnet. A.1.1 Login from Serial Port When connecting to the switch via the serial port, output similar to the fol- lowing will be displayed on your console: ForeThought_4.0.0 (1.15) (asx200bx) (fishtank)
Page 140: Login From Telnet
Above, ForeThought_4.0.0 (1.15) indicates the version of software, (asx200bx) indicates what type of switch this is, and (ﬁshtank) indicates the name that has been assigned to this SCP. If (ATM SWITCH) is displayed for the switch name, this means that no host name has been assigned yet.
Page 141 If another user already has an AMI session open on that SCP, then you will not be permitted to log in and will receive the following message: Another ami is running on this switch. . Exiting... Connection closed by foreign host.
Page 142: Ami Commands Not Available When Running Remotely
A.2 AMI Commands Not Available When Running Remotely Some AMI commands are not available when you telnet or log in to a switch remotely. For example, if you are logged in locally to a switch called ﬁshtank (you will see localhost::> as your prompt) and you open a session to a switch called shark (you will see shark::>...
Page 143: Ami Root Menu For An Open Session
A.3 AMI Root Menu for an Open Session This menu is the root submenu for an AMI session. When AMI is ﬁrst entered from the serial port or telnet, the localhost session is the only open session. The following information is displayed: ATM Management Interface v1.2 Copyright (c) 1994, 1995 FORE Systems, Inc.
Page 144: About Command
FORE ATM switches. When AMI is executed on a host, you must first use the OPEN command to specify the switch to manage. If AMI is started on the switch, it immediately opens a connection to the local switch.
Page 145: Close Command
SCP as follows: switch1::> close localhost::> If all sessions are closed, the user is sent back to the root prompt as follows: localhost::> close > At this point, the user can open another session or exit the switch.
Page 146: Conﬁguration Commands
- Display help for each command - Display command history - Open a connection - Switch operation submenu - Ping a host or switch - Repeat a history command - Get/set number of rows - Switch statistics submenu - Go to the root menu...
Page 147: History Command
A.3.6 History Command By typing history at any prompt, the user can list up to the last 20 previously typed commands for that particular session as follows: localhost::> history open fishtank stat module port spans help history AMI Overview A-11...
Page 148: Open Command
AMI Overview A.3.7 Open Command The open command lets the user begin a session on a remote switch. At the prompt, enter the following parameters: localhost::> open <host> [<community>] host community NOTE: For example, to log in to a remote switch named ﬁshtank using the public community string, enter the following parameters: localhost:>...
Page 149: Operation Commands
Appendix C of this manual. A.3.9 Ping Command The ping command lets the user send a ping to another switch or a host to see if it is “alive,” or reachable, by sending it an ICMP echo request and waiting for a response.
Page 150: Redo Command
This is the command and the number associated with that command which was previously per- formed by the switch during this same session. The user should enter the history command to list the previous commands and their associated numbers as...
Page 151 Type history at the prompt to list the last 20 previously typed commands for that particular session as follows: localhost::> history open localhost stat module port spans help history Then, to repeat a previously given command, type redo and the command number at the prompt.
Page 152: Rows Command
By entering statistics at the root level, the user can access several commands that display operational performance and error information for the various hardware and software features of the switch and the network modules. The statistics commands are described in Appendix D of this manual.
Page 153 ? alarms> lane> rs232> switch> upc> Each of these commands has a submenu of commands which are described in the following subsections. Alarms Conﬁguration Commands This submenu allows the user to conﬁgure alarms. The user can display the list of available subcommands by typing alarms ? at the conﬁguration level.
Page 154: Displaying Alarm Conditions
Cabletron switches. The power- SupplyInputFailed and tempSensorOverTemp alarms are available on all switches. The powerSupplyOutputFailed alarm is only available on a 9A000, SFCS-200BX and an SFCS-1000. The fanBankFailed alarm is only available on an SFCS-1000. Enter the following parameters: localhost::configuration alarms> show...
Page 155: Enabling An Alarm
Major alarm relay status Off means that no major alarms are currently active. On means that one or more major alarms are cur- rently active. Look at the AlarmStatus ﬁeld to see which condition is in a state of alarm. Minor alarm relay status Off means that no minor alarms are currently active.
Page 156: Disabling An Alarm
AMI Configuration Commands B.1.3 Disabling an Alarm This command lets the user disable an alarm. Enter the following parameters: localhost::configuration alarms> disable (major | minor) <alarm type> major|minor alarm type For example, to disable a link failure as a minor alarm, enter the following parameters: localhost::configuration alarms>...
Page 157: Resetting An Alarm
B.1.4 Resetting an Alarm This command lets the user reset either the linkFailed alarm, the spansFailed alarm, or both alarms. Enter the following parameters: localhost::configuration alarms> reset (<alarm type> | all) Indicates which alarm to reset. Enter either link or alarm type spans.
Page 158: Atm Arp Conﬁguration Commands
Enter the name of one of the classical IP interfaces, such as qaa0, qaa1, qaa2, or qaa3. The default is qaa0, so that if no interface is entered, the switch shows the ARP server address for qaa0. getnsap show...
Page 159: Deleting An Arp Entry
The default is qaa0. The switch itself can be used as an ARP server. To do this, set the ARP server address to be the NSAP address of the switch’s control port. B.2.2...
Page 160: Flushing The Atm Arp Cache
This command enables the user to delete the contents of the ATM ARP cache. Only dynamic ARP cache entries are removed. The switch asks the user to verify that ﬂushing the ARP cache is the desired action. Enter the following parameters: localhost::configuration atmarp>...
Page 161: Creating A Classical Ip Pvc
B.2.6 Creating a Classical IP PVC This command allows the user to create a new Classical IP PVC ARP entry. All data is sent LLC/SNAP encapsulated. Enter the following parameters: localhost::configuration atmarp> newclassicalip <host> <vpi> <vci> [<interface>] host Indicates the host IP address of the remote IP endstation. Indicates the virtual path number of the Classical IP PVC.
Page 162: Displaying The Atm Arp Entries
AMI Configuration Commands B.2.8 Displaying the ATM ARP Entries This command displays the current ATM ARP cache. Enter the following parameters: localhost::configuration atmarp> show localhost::configuration atmarp> When the prompt is returned with no information displayed, as shown above, then the ATM ARP cache is empty. The following is an example of an ATM ARP cache.
Page 163: Switch Board Conﬁguration Commands
(i.e., burst tolerances) in internal units of clock ticks. Because of the 40 MHz clock used on the switch fabric, the maximum unit of time that can be used by the trafﬁc policing hardware is 0.838 seconds. However, the burst tol- erance of some VBR connections is larger than 0.838 seconds, so they can not...
Page 164: Displaying The Board Conﬁguration
AMI Configuration Commands B.3.2 Displaying the Board Conﬁguration This command shows the current conﬁguration of the switch board. Enter the following parameters: localhost::configuration board> show Board Version Model asx200bx 4465 The ﬁelds in this display are deﬁned as follows: Board...
Page 165: Displaying The Board Topology
B.3.3 Displaying the Board Topology This command displays the SPANS topology of the ATM network of which this switch is a part. All SPANS-NNI links appear in the topology. Enter the following parameters: localhost::configuration board> topology B Source Ipaddress 1 f21a013a.08.0 198.29.22.46...
Page 166: Ip Conﬁguration Commands
SCP is enabled. The IP addresses must be conﬁgured individ- ually on each SCP on an SFCS-1000. Indicates the name of the IP interface to be managed. Valid interfaces are: ie0 (the Ethernet interface), asx0 (the switch’s SPANS interface), qaa0, qaa1, qaa2,...
Page 167: Conﬁguring The Ip State
Entering up changes the state of the designated interface to up. Entering down changes the state of the designated interface to down. NOTE: The switch’s localhost interface, lo0, must always be up to allow AMI to run on the switch. B.4.3 Conﬁguring the IP Broadcast Address...
Page 168: Conﬁguring Ip Forwarding
This command allows the user to turn IP forwarding on or off. If IP forward- ing is turned off, the switch will not forward (i.e., route) IP packets from one IP interface to another IP interface. It is generally not necessary to turn IP for- warding off, except for security reasons.
Page 169: Conﬁguring Ip Routes
B.4.6 Conﬁguring IP Routes This command allows the user to add a static IP route to the local IP routing table, delete a static IP route from the local IP routing table, or list the current static IP routes in the local IP routing table. The user can display the list of available subcommands by typing route ? at the ip level.
Page 170 AMI Configuration Commands B.4.6.2 Deleting an IP Route This command lets the user delete an IP route. Enter the following parame- ters: localhost::configuration ip route> delete (default|<destination-ipaddress>) <gateway> default destination-ipaddress gateway B.4.6.3 Showing the IP Routes This command lets the user display the current IP routes. Enter the following parameters: localhost:: configuration ip route>...
Page 171: Displaying The Ip Interface Conﬁguration
B.4.7 Displaying the IP Interface Conﬁguration This command allows the user to display information about the conﬁguration of the IP interfaces. Enter the following parameters: localhost::configuration ip> show interface state asx0 qaa0 qaa1 down qaa2 down qaa3 down IP Forwarding State: forwarding The ﬁelds in this display are deﬁned as follows: interface Indicates the name of the IP interface.
Page 172: Lan Emulation Conﬁguration Commands
AMI Configuration Commands LAN Emulation Conﬁguration Commands These commands allow the user to conﬁgure LAN Emulation (LANE) on a switch. The user can display the list of available subcommands by typing lane ? at the conﬁguration level. localhost::configuration> lane ? bus>...
Page 173 <BUS Selector byte (HEX)> <BUS name> BUS Selector byte (HEX) Indicates the 20th byte of the ATM address of the switch that is to run a BUS service (entered in hexa- decimal format). Use the conf atmarp getnsap command to display the entire ATM address.
Page 174 BUS is currently active. Down means the BUS is currently inactive. Displays the selector byte portion (20th byte) of the ATM address of the host or switch that is the BUS in hexadecimal format. Lists the name of the ELAN that this BUS services.
Page 175 1 localhost::configuration lane bus> show Index AdminStatus OperStatus The ﬁelds in this display are deﬁned in the same manner as those listed above in the example showing every BUS conﬁgured on the switch. AMI Configuration Commands Selector Name 0x0b marketing...
Page 176: Lan Emulation Client (Lec) Conﬁguration Commands
AMI Configuration Commands B.5.2 LAN Emulation Client (LEC) Conﬁguration Commands These commands let the user conﬁgure the LAN Emulation Client (LEC). The user can display the list of available subcommands by typing lec ? at the lane level. localhost::configuration lane> lec ? admin B.5.2.1 Conﬁguring the LEC Administrative Status...
Page 177 B.5.2.2.1 Deleting LANE ARP Cache Information This command allows the user to remove an ARP entry from the LANE ARP cache or to delete the contents of the LANE ARP cache. Enter the following parameters: localhost::configuration lane lec arp> delete all | <MAC address> Indicates that all of the entries are to be ﬂushed from the LANE ARP cache.
Page 178 Indicates the unique, integer index of the LEC that is to be deleted. This number is dynamically assigned by the switch when a LEC is created and can be found under the Index ﬁeld when you enter the conf lane lec show command.
Page 179 B.5.2.4.1 Setting the Default LEC Conﬁguration Mode This command lets the user set the default mode for conﬁguring all of the ELANs that may be created on this switch. NOTE: If you chose manual mode, you must specify the LECS address of the machine that will be used as the LECS.
Page 180 -lecs <LECS address> -les <LES address> B-28 This AMI command only allows you to create an instance of a LEC on a switch. To create an instance of a LEC on a host, you must use the ForeRunner VLAN Manager ForeRunner adapter.
Page 181 The ﬁelds in this display are deﬁned as follows: Index Shows the unique, integer index that identiﬁes this LEC. It is dynamically assigned by the switch when the LEC is created. AdminStatus Reﬂects any changes that the user has made to the status of the LEC.
Page 182 LECS:0x47.0079.00.000000.0000.0000.0000.00a03e000001.00 LES :0x47.0005.80.ffe100.0000.f215.096b.00204815096b.a2 The ﬁelds in this display are deﬁned in the same manner as those listed above in the example showing all of the LECs conﬁgured on the switch. B-30 Shows the conﬁguration mode that is used when a LEC joins the ELAN.
Page 183: Lan Emulation Conﬁguration Server (Lecs) Commands
Indicates the unique, positive integer index of the LECS that is to be deleted. This number is dynami- cally assigned by the switch when a LECS is created and can be found under the Index ﬁeld when you enter the conf lane lecs show command.
Page 184 Indicates the full path to the location and name of the LECS database ﬁle. The default ﬁle for a 9A000, SFCS-200BX, SFCS-200WG, and an SFCS-1000 is lecs.cfg. For information about conﬁguring this ﬁle, refer to Chapter 3 of this manual.
Page 185 Database Shows the full path to the location and name of the LECS database ﬁle. The default ﬁle for a 9A000, SFCS-200BX, an SFCS-200WG, and an SFCS-1000 is lecs.cfg. Default LES Shows the default LES address to use in case the LECS conﬁguration ﬁle is inaccessible.
Page 186 AdminStatus Default LES :0000000000000000000000000000000000000000 The ﬁelds in this display are deﬁned in the same manner as those listed above in the example for all of the LECS conﬁgured on the switch. B-34 When you change the administrative status of a LECS down to up, it takes a few seconds for the operational change to occur and to be reﬂected in the OperStatus ﬁeld.
Page 187 SFCS-200BX, SFCS-200WG, and an SFCS-1000 is lecs.cfg. NOTE: On a 9A000, SFCS-200BX, an SFCS-200WG, and an SFCS-1000, this ﬁle will be retrieved via tftp. NOTE: For information about conﬁguring this ﬁle, refer to Chapter 3 of this manual. AMI Configuration Commands local ﬁle...
Page 188: Lan Emulation Server (Les) Conﬁguration Commands
Indicates the unique, positive integer index of the LES that is to be deleted. This number is dynamically assigned by the switch when a LES is created and can be found under the Index ﬁeld when you enter the conf lane les show command.
Page 189 AMI Configuration Commands Indicates the 20th byte of the ATM address of the host or switch that is to run a LES service (entered in hexadecimal format). Use the conf atmarp get- nsap command to display the entire ATM address.
Page 190 LES is currently active. Down means the LES is currently inactive. Displays the selector byte portion (20th byte) of the ATM address of the host or switch that is the LES in hexadecimal format. Shows the name of the ELAN that this LES services.
Page 191 BUS:0x47.0005.80.ffe100.0000.f21a.00d0.0020481a00d0.1b (Co-Located) The ﬁelds in this display are deﬁned in the same manner as those listed above in the example showing every LES conﬁgured on the switch. To display advanced information about every LES that is currently conﬁg- ured on the switch, enter the following parameters: localhost::configuration lane les>...
Page 192 Proxy Control Distribute Control Direct VCC B-40 Shows the names of any ELANs associated with this switch. Displays the ATM address of the LES that services this particular ELAN. Displays the ATM address of the BUS that services this particular ELAN.
Page 193 To display advanced information about a particular LES that is currently con- ﬁgured on the switch, enter the following parameters: localhost::configuration lane les> show [<LES index>] [(advanced)] For example, to display advanced information about the LES with an index number of 2, enter the following parameters: localhost::configuration lane les>...
Page 194: Network Module Conﬁguration Commands
B.6.1 Displaying Network Module Conﬁguration Information This command allows the user to display information about the conﬁguration of the network modules that are currently installed in a particular switch board. Enter the following parameters: localhost::configuration module> show Module Speed...
Page 195: Conﬁguring Distributed Timing On A Network Module
Shows each distributed timing network module that is currently installed in the switch. The 1 means that it is the ﬁrst switch fabric. The C indicates the posi- tion of the network module in the switch fabric. AMI Configuration Commands...
Page 196 This can be designated as the export clock of a different network module on the same switch fabric. Import Current Lists the current import timing source for the speci- ﬁed network module.
Page 197 Conﬁguring the Internal Clock Timing of a Network Module Each network module installed in a switch has its own internal clock as a tim- ing source. This timing source can be either the export clock or it may be the import clock.
Page 198 AMI Configuration Commands B.6.2.3 Conﬁguring the Export Clock Timing of a Network Module This command allows the user to conﬁgure the timing source for the export clock on a speciﬁed network module. NOTE: Enter the following parameters: localhost::configuration module timing> exportclock <module> (primary | secondary) (<mod-port#>...
Page 199 Indicates the import timing source will be taken from the export clock from another (A - bottom left, B - bottom right, C - top left, or D - top right) network module on this switch fabric. B-47...
Page 200: Conﬁguring Trafﬁc On A Network Module
AMI Configuration Commands B.6.3 Conﬁguring Trafﬁc on a Network Module These commands enable the user to conﬁgure or to display information about the trafﬁc on the network modules. NOTE: Enter the following parameters to show the commands for network module trafﬁc: localhost::configuration module>...
Page 201 B.6.3.2 Displaying Trafﬁc Models for a Network Module This command allows the user to display the different types of trafﬁc memory models on a network module. NOTE: This command applies to FORE Systems’ Series C network modules only. Enter the following parameters: localhost::configuration module traffic>...
Page 202 Indicates the predeﬁned memory model to be used for this network module. The various models make different trade-offs between the number of cell buff- ers, and the number of unicast and multicast connec- tions. The switch software must be restarted for this command to take effect.
Page 203 Module Model Unicasts Mcasts McastOuts Cells Shared The ﬁelds in this display are deﬁned as follows: Module Shows the network module that has been conﬁgured. The number indicates the switch fabric and the letter indicates the position of the network module in the switch fabric. Model Indicates the memory model used for this network module.
Page 204 AMI Configuration Commands B.6.3.5 Setting FIFO Blocking on a Network Module This command lets the user set FIFO blocking on a speciﬁc network module when the queues are full. NOTE: Enter the following parameters: localhost::configuration module traffic> fifoblock <module> (normal | enabled) module normal|enabled B-52...
Page 205: Nsap Conﬁguration Commands
The default mask for the route to the host is 152 and the default mask for the route to the switch is 104. port Speciﬁes the port on which this NSAP route is to be deleted.
Page 206 The default mask for a static route to a host is 152 and the default mask for a static route to another switch is 104. Speciﬁes the port through which this NSAP route can be reached.
Page 207 104. Lists the port number on which the NSAP route exists. The 1 indicates that it is the ﬁrst switch fabric. The letter C indicates the position of the network module in the switch. The 1, 2, 3 indicate the speciﬁc port number on the network module.
Page 208: Nsap Preﬁx Conﬁguration Commands
AMI Configuration Commands Cost FLAGS B.7.2 NSAP Preﬁx Conﬁguration Commands These commands enable the user to delete an NSAP preﬁx, create an NSAP preﬁx, and display NSAP preﬁx information. The user can display the list of available subcommands by typing preﬁx ? at the nsap level. localhost::configuration nsap>...
Page 209 B.7.2.1 Deleting an NSAP Preﬁx This command lets the user remove an existing NSAP preﬁx. Enter the fol- lowing parameters: localhost::config nsap prefix> delete <port> <vpi> <prefix> port Indicates the port number on which the NSAP preﬁx is to be deleted. Indicates the number of the virtual path on which the NSAP preﬁx is to be deleted.
Page 210 The letter B indi- cates that the network module is installed in the bot- tom right-hand slot in the switch. The 1, 2, 3, 4, 5, 6 indicate the speciﬁc port number on the network module.
Page 211: Nsap Ilmi Conﬁguration Command
This command enables the user to display the NSAP addresses of all of the ports on a switch fabric that have been registered via ILMI. ILMI address reg- istration occurs between the switch and host. The switch sends the host its 13-byte NSAP preﬁx.
Page 212: Port Conﬁguration Commands
AMI Configuration Commands Port Conﬁguration Commands These commands let the user manage the conﬁguration of the various ports. The user can display the list of available subcommands by typing port ? at the conﬁguration level. localhost::configuration> port ? cdvt tp25> sonet>...
Page 213: Port Conﬁguration Commands
E-3 network module. The following E-3 commands are available only when an E-3 network module is installed in the switch fabric. The user can display the list of available subcommands by typing e3 ? at the port level.
Page 214 Choosing diagnostic loopback connects the receiver to the transmitter. The E-3 stream transmitted by the switch to a port is looped back to the switch. The E-3 stream is still transmitted to the network, but the incoming E-3 stream is ignored.
Page 215 B.8.2.3 Conﬁguring E-3 Port Mode This command allows the user to change the method used for cell delineation on an E-3 network module port. Enter the following parameters: localhost::configuration port e3> mode <port> (plcp | hcs) port Indicates the port number on which the type of fram- ing is to be changed.
Page 216 ﬁrst switch fabric. The letter D means that the E-3 network module is installed in the bot- tom right-hand slot in the switch. The 1, 2, 3, 4 spec- ify the port number on the network module.
Page 217 ClockSource For all network modules, network means that the timing for this port is derived externally from the incoming clock on this port. Internal means that the timing is derived from either the on-board crystal oscillator or is set to be derived from a speciﬁc port number on a Series C network module that is deﬁned by the user.
Page 218: Tp25 Port Conﬁguration Commands
TP25 network module. The following tp25 commands are available only when a TP25 network module is installed in the switch fab- ric. The user can display the list of available subcommands by typing tp25 ? at the port level.
Page 219 Timing Sync Marker. These markers can be used to derive an 8kHz signal that can be transmitted from all ports on the network module and back to the switch fabric (on switches that support timing features). No means that the port is not receiving sync pulses. Yes means that the port is receiving sync pulses.
Page 220: Port Conﬁguration Commands
DS-3 network module. The following DS-3 commands are available only when a DS-3 network module is installed in the switch fab- ric. The user can display the list of available subcommands by typing ds3 ? at the port level.
Page 221 Choosing diagnostic loopback connects the receiver to the transmitter. The DS-3 stream transmitted by the switch to a port is looped back to the switch. The DS-3 stream is still transmitted to the network, but the incoming DS-3 stream is ignored.
Page 222 AMI Configuration Commands B.8.4.4 Conﬁguring the DS-3 Port Mode This command allows the user to change the type of framing on a port on a DS-3 network module. Enter the following parameters: localhost::configuration port ds3> mode <port> (plcp | hcs) port plcp|hcs B.8.4.5...
Page 223 Gt225 Indicates the port number of the network module that is currently installed in the switch. Shows whether or not a carrier has been detected on the port. If a carrier has been detected, yes is dis- played.
Page 224 AMI Configuration Commands IdleCells B.8.4.7 Conﬁguring the DS-3 Port Timing This command allows the user to change the timing source on a port on a DS-3 network module. Enter the following parameters: localhost::configuration port ds3> timing <port> (network | internal) port network|internal B.8.4.8...
Page 225: Port Conﬁguration Commands
These commands let the user modify various aspects of the conﬁguration of a J-2 network module. The following J-2 commands are available only when a J-2 network module is installed in the switch fabric. The user can display the list of available subcommands by typing j2 ? at the port level.
Page 226 Choosing diagnostic loopback connects the receiver to the transmitter. The J-2 stream transmitted by the switch to a port is looped back to the switch. The stream is still transmitted over the cable, but the incoming stream is ignored.
Page 227 B.8.5.3 Showing J-2 Port Conﬁguration This command allows the user to display information about the conﬁguration of the ports on a J-2 network module. Enter the following parameters: localhost::configuration port j2> show Port LineLength Loopback short none short none short none short none...
Page 228: Port Policing Conﬁguration Command
AMI Configuration Commands B.8.5.4 Conﬁguring J-2 Port Timing This command allows the user to change the timing source on a port on a J-2 network module. Enter the following parameters: localhost::configuration port j2> timing <port> (network | internal) port network|internal B.8.6 Port Policing Conﬁguration Command This command lets the user decide whether or not trafﬁc policing is enabled...
Page 229: Sonet Port Conﬁguration Commands
SONET network module. The following SONET commands are available only when a SONET network module is installed in the switch fabric. The user can display the list of available subcommands by typing sonet ? at the port level.
Page 230 AMI Configuration Commands B.8.7.2 Conﬁguring SONET Port Loopback This command enables the user to conﬁgure the type of loopback mode on a SONET port. Enter the following parameters: localhost::configuration port sonet> loopback <port> (line| diag | none) port line diag none B.8.7.3 Conﬁguring SONET Port Mode...
Page 231 Indicates the port number of the network module that is currently installed in the switch fabric. The 1 means that it is the ﬁrst switch fabric. The letter A means that the SONET network module is installed in the bottom left-hand slot in the switch fabric. The 1, 2, 3, 4 indicate the speciﬁc port number on the net-...
Page 232 AMI Configuration Commands Mode Indicates the mode of operation for this port. Can be sonet or sdh. Loopback Indicates the loopback mode on this port. Can be one of the following: none, line, or diagnostic. ClockSource For all network modules, network means that the timing for this port is derived externally from the incoming clock on this port.
Page 233 B.8.7.5 Conﬁguring SONET Port Timing This command allows the user to change the timing source on a port on a SONET network module. NOTE: This option is not available on an OC-12 net- work module because it always uses internal timing.
Page 234: Showing The Port Conﬁguration
Showing the Port Conﬁguration This command lets the user display port information about all of the ports on an individual switch fabric or about just a speciﬁed port. To show general information about all of the ports, enter the following parameters: localhost::configuration port>...
Page 235 The ﬁelds in this display are deﬁned as follows: Port Indicates the port number of the network modules that are currently installed in the switch fabric. CDVT Shows the default value for the cell delay variation tolerance setting in microseconds.
Page 236 The ﬁelds in this display are deﬁned in the same manner as those listed previ- ously in the example for all of the ports on an individual switch fabric. To list advanced port information for just a speciﬁed port, (for example, port 1C1), enter the following parameters: localhost::configuration port>...
Page 237: Taxi Port Conﬁguration Commands
TAXI network module. The following TAXI com- mands are available only when a TAXI network module is installed in the switch fabric. The user can display the list of available subcommands by typ- ing taxi ? at the port level.
Page 238 Indicates the port number of the network module that is currently installed in the switch fabric. The 4 means that it is the fourth switch fabric. The letter B indicates that the TAXI network module is installed in the bottom right-hand slot in the switch fabric.
Page 239: Trafﬁc Port Conﬁguration Commands
These commands enable the user to conﬁgure various trafﬁc features on an individual port on a Series C network module on the switch. The user can dis- play the list of available subcommands by typing trafﬁc ? at the port level.
Page 240 Available Bit Rate (ABR) cells and Unspeciﬁed Bit Rate (UBR) cells have their explicit forward congestion indicator (EFCI) code point set. When the EFCI code point is set, this signals congestion to downstream switch fab- rics and to future ABR and UBR ﬂow control mechanisms. Once this thresh- old is surpassed, EFCI continues to be set until the queue empties.
Page 241 <port> (CBR | VBR | ABR) <number of cells> port CBR|VBR|ABR number of cells NOTE: The switch control software must be restarted for this command to take effect. AMI Configuration Commands Indicates the port on which the dedicated queue size will be set.
Page 242 TxCells Shows the port that has been conﬁgured. The 4 indi- cates the fourth switch fabric, the letter indicates the position of the network module in the switch fabric, and the 1, 2, 3, or 4 indicates the speciﬁc port num-...
Page 243 Port Shows the port that has been conﬁgured. The 4 indi- cates the fourth switch fabric, the letter indicates the position of the network module in the switch fabric, and the 1, 2, 3, or 4 indicates the speciﬁc port num- ber.
Page 244 AMI Configuration Commands This command also lets the user show port trafﬁc information and port prior- ity queue information for an individual port on a Series C network module. Enter the following parameters: localhost::configuration port traffic> show [<port>] localhost::configuration port traffic> show 4A4 Port configuration: Port Qsize...
Page 245: Vbrob Port Conﬁguration Commands
B.8.11 VBROB Port Conﬁguration Commands This command is an advanced option that allows the user to set an output bandwidth overbooking level for VBR trafﬁc on a particular port. Enter the following parameters: localhost::configuration port> vbrob <port> <percent> port Indicates the port number on which the bandwidth overbooking level for VBR trafﬁc is to be changed.
Page 246: Serial Port Conﬁguration Commands
AMI Configuration Commands Serial Port Conﬁguration Commands These commands let the user manage an RS-232 serial port. The user can dis- play the list of available subcommands by typing rs232 ? at the conﬁgura- tion level. localhost::configuration> rs232 ? show B.9.1 Displaying Serial Port Information This command allows the user to show information about the conﬁguration...
Page 247: Snmp Conﬁguration Commands
B.10 SNMP Conﬁguration Commands These commands enable the user to manage the SNMP communities and traps. The user can display the list of available subcommands by typing snmp ? at the conﬁguration level. localhost::configuration> snmp ? community trap> B.10.1 Conﬁguring the SNMP Community Access This command lets the user modify the SNMP community access to AMI.
Page 248 AMI Configuration Commands B.10.2.1 Deleting an SNMP Trap Entry This command allows the user to delete an existing SNMP trap destination. Before deleting a trap that may need to be recreated later, show the list of cur- rent SNMP traps and either copy and save the screen or write down the trap destinations.
Page 249 B.10.2.2 Creating an SNMP Trap Entry This command allows the user to specify a host to which a switch can send SNMP traps. The SNMP traps supported by this switch are detailed in the FORE-Switch-MIB. Enter the IP address of the SNMP trap destination to be added.
Page 250: Spans Conﬁguration Commands
AMI Configuration Commands B.11 SPANS Conﬁguration Commands These commands allow the user to manage SPANS (Simple Protocol for ATM Network Signalling), FORE Systems’ pre-standard signalling protocol. The user can display the list of available subcommands by typing spans ? at the conﬁguration level.
Page 251: Creating A Spans Signalling Path
B.11.2 Creating a SPANS Signalling Path This command allows the user to create a SPANS signalling path. NOTE: Before a SPANS signalling path can be cre- ated on a given VPI, an originating and a ter- minating path must exist for that same VPI. Enter the following parameters: localhost::configuration spans>...
Page 252 AMI Configuration Commands -clsupc <index> Indicates the integer index that refers to a speciﬁc trafﬁc contract that is used to police the connection- less VCI. If no index is speciﬁed, then no trafﬁc polic- ing will take place on this VCI. It is assigned a UPC index of 0, and all trafﬁc on this VCI is treated as UBR trafﬁc.
Page 253: Showing The Spans Signalling Path Conﬁguration
B.11.3 Showing the SPANS Signalling Path Conﬁguration This command lets the user list an individual switch fabric’s current SPANS signalling path information. Enter the following parameters: localhost::configuration spans> show Port State Type down down down down down down down 1CTL The ﬁelds in this display have the following meanings:...
Page 254 AMI Configuration Commands To show advanced SPANS signalling path information about all of the ports, enter the following parameters: localhost::configuration spans> show advanced Port VPI SigVCI CLSVCI AAL MinVCI MaxVCI SigBW CLSUPC 1CTL The ﬁelds in this display have the following meanings: Port SigVCI ClsVCI...
Page 255 VPI SigVCI CLSVCI AAL MinVCI MaxVCI SigBW CLSUPC The ﬁelds in this display are deﬁned in the same manner as those listed previ- ously in the example for displaying advanced SPANS information on all of the ports on an individual switch fabric. AMI Configuration Commands Action RemoteAddress...
Page 256: Spvc Conﬁguration Commands
SPVCs are more robust than PVCs. If a link carrying a PVC goes down, then the PVC goes down. If a link carrying an SPVC goes down and there is an alternate route, then the end switch fabrics of the SPVC automati- cally reroute the SPVC around the failed link.
Page 257: Creating An Spvc
Indicates the virtual channel number on the remote switch fabric. Source means the SPVC to be deleted is a unidirec- tional SPVC going from the local switch fabric to the remote switch fabric. Destination means the SPVC to be deleted is a unidirectional SPVC going from the remote switch fabric to the local switch fabric.
Page 258 To create an SPVC, you need to conﬁgure the two ends concurrently on the two switch fabrics. Therefore, you ﬁrst need to open an AMI session to the destination switch fabric by either using the SCP’s IP address or its name, along with the SNMP read-write community string.
Page 259: Displaying Spvc Information
Indicates the unique number that the local switch Local ID fabric’s SCP assigned to this SPVC when the SPVC was created. Local Port Indicates the port number on the local switch fabric. Local VPI Indicates the virtual path number on the local switch fabric. Local VCI Indicates the virtual channel number on the local switch fabric.
Page 260: Switch Conﬁguration Commands
B.13.1 Setting or Changing the Switch Name This command enables the user to set or change the name of the switch. The switch name is shown on the front panel display LED. Enter the following parameters: localhost::configuration switch> name <name>...
Page 261: Setting The Minimum Number Of Reserved Vcis For Pmps
LAN Emulation point-to-multipoint use. This block of VCIs will be reserved on all paths and on all ports on this switch fabric. PVCs can be created on these VCIs, but no point-to-point connections may use these VCIs.
Page 262: Setting The Maximum Number Of Reserved Vcis For Pmps
LAN Emulation point-to-multipoint use. This block of VCIs will be reserved on all paths and on all ports on this switch fabric. PVCs can be created on these VCIs, but no point-to-point connections may use these VCIs.
Page 263: Displaying The Switch Conﬁguration
SPANS address of the switch, and the range of the mini- mum and maximum number of reserved VCIs for point-to-multipoint connections.
Page 264: System Conﬁguration Commands
AMI Configuration Commands B.14 System Conﬁguration Commands These commands let the user conﬁgure system message log features, conﬁg- ure the amount of time of non-activity after which an AMI session times out, and change the units for designating UPC contracts. The user can display the list of available subcommands by typing system ? at the conﬁguration level.
Page 265: System Log Conﬁguration Commands
Displaying the Address of the System Log Host This command allows the user to display the address of the host to which the switch’s system messages are logged. Enter the following parameters: NOTE: This command is only available on the local switch.
Page 266 B.14.2.2 Setting the Address of the System Log Host This command sets the address of the host to which the switch’s system mes- sages are being logged. You may also opt to assign a speciﬁc facility name so that the remote syslog can automatically differentiate between switches with different facilities.
Page 267 The switch prompts the user to conﬁrm that the address should be deleted. Entering y causes the switch to delete the address, as shown above. If you do not want the address to be deleted, enter n or press <RETURN> and you will be sent back to the syslog prompt.
Page 268 B.14.2.4 Turning Off or Turning On System Log Messages to the Console On a 9A000, SFCS-200WG, an SFCS-200BX, and an SFCS-1000, the system log messages may be directed to three places: to syslog, to the console, and to a remote host. These types of switches are defaulted to send log messages to both the console and to syslog.
Page 269: Ami Timeout Conﬁguration Command
AMI session will time out and exit the user out of the session. The default is 5 minutes. To con- ﬁgure the switch so that an AMI session does not time out, enter 0. It is displayed as off when you use conﬁguration system show.
Page 270: Topology Conﬁguration Commands
ForeThought PNNI Conﬁguration Commands These commands allow the user to modify various aspects of ForeThought PNNI on a switch. The user can display the list of available subcommands by typing forepnni ? at the topology level. localhost::configuration topology> forepnni ?
Page 271 B.15.1.2 Changing the ForeThought PNNI Border Switch Functionality A switch that has a link to another switch that belonging to a different peer- group is considered a border switch. A border switch advertises reachability to its peergroup to switches outside of its peergroup, but it does not share its peergroup’s topology with the other switches.
Page 272 A peergroup mask is the length (in the number of bits) of the peergroup ID of a switch. This command enables the user to set the ForeThought PNNI peer- group mask value. This value should be the same for all members of a peer- group.
Page 273 B.15.1.5 Setting the Hello Indication Interval Hello indication messages are the “keep alive” messages that two switches send to one another to verify their existence. This command lets the user change the interval for ForeThought PNNI hello indication messages. Enter the following parameters: localhost::configuration topology forepnni>...
Page 274 B.15.1.8 Setting the Maximum Hop Count By setting a maximum hop count, the user tells the switch to consider only those paths that have less than or equal to the number of hops speciﬁed when setting up a connection. If a connection is routed using a path with a large hop count, there is a greater chance that the connection may experience con- gestion and be delayed or discarded.
Page 275 B.15.1.10 Setting a Minimum Threshold for NSAP Updates The minimum threshold is the smallest capacity value that the threshold value for determining the signiﬁcant change in ACR can take. This minimum value ensures that the threshold value does not become a very small value in cases in which product of the ACR and the proportional multiplier is a very small number.
Page 276 NSAP Indication Interval Static Route Update Interval Max hop count for NSAP router Proportional Multiplier Minumum Threshold for NSAP updates Minimum VC level FORE PNNI border switch functionality is disabled B-124 0x47.0005.80.ffe100.0000.f215.0df6 500 msec 10000 msec 10000 msec 20 hops...
Page 277 VCs has dropped to zero. FORE PNNI border switch If this functionality is enabled, this switch acts as a functionality is disabled ForeThought PNNI border switch. If this functionality is disabled, this switch does not act as a ForeThought PNNI border switch.
Page 278: Spans Topology Conﬁguration Commands
B.15.2.1 Setting the SPANS-NNI Border Switch Functionality A switch that has a link to another switch belonging to a different SPANS area is considered a border switch. A border switch advertises reachability to its area to switches outside of its area, but it does not share its area’s topology with the other switches.
Page 279 SPANS ATM address. SPANS NNI border switch If this functionality is enabled, this switch is a functionality is disabled SPANS-NNI border switch. If it is disabled, this switch is not a SPANS-NNI border switch.
Page 280: Uni 3.0 Conﬁguration Commands
AMI Configuration Commands B.16 UNI 3.0 Conﬁguration Commands These commands let the user conﬁgure UNI 3.0 signalling paths. The user can display the list of available subcommands by typing uni30 ? at the conﬁgu- ration level. localhost::configuration> uni30 ? delete B.16.1 Deleting a UNI 3.0 Signalling Path This command allows the user to delete an existing UNI 3.0 signalling path.
Page 281: Creating A Uni 3.0 Signalling Path
Indicates the conﬁguration type. PublicUNI means that this link is used between this switch and a public switch. Auto means that the operation type is deter- mined dynamically. IISP is used for switch-to-switch signalling for static NNI routes.
Page 282 AMI Configuration Commands -ilmivci <vci> -minvci <vci> -maxvci <vci> -sigbw <Kbps> -ilmibw <Kbps> B-130 Indicates the VCI to use for ILMI signalling mes- sages. The default reserved VCI is 16. Indicates the bottom number for the range of VCIs to be reserved for UNI 3.0 signalling messages.
Page 283: Displaying Uni 3.0 Signalling Paths
B.16.3 Displaying UNI 3.0 Signalling Paths This command allows the user to list an individual switch fabric’s current UNI 3.0 signalling path information. Enter the following parameters: localhost::configuration uni30> show Port State ILMI down down down down down down down...
Page 284 Indicates the port number of the network modules that are currently installed in the switch. The 1 indi- cates that it is the ﬁrst switch fabric. The letter indi- cates the position of the network module in the switch. The 1, 2, 3, 4 indicate the speciﬁc port num- ber.
Page 285 The ﬁelds in this display are deﬁned in the same manner as those listed previ- ously in the example for displaying advanced UNI 3.0 signalling path infor- mation on all of the ports on an individual switch fabric. AMI Configuration Commands...
Page 286: Usage Parameter Control Conﬁguration Commands
AMI Configuration Commands B.17 Usage Parameter Control Conﬁguration Commands These commands let the user create or delete usage parameter control (UPC) trafﬁc contracts. The user can display the list of available subcommands by typing upc ? at the conﬁguration level. localhost::configuration>...
Page 287: Creating A Upc Trafﬁc Contract
B.17.2 Creating a UPC Trafﬁc Contract This command allows the user to create a UPC contract. Enter the following parameters: localhost::configuration upc> new <index> [<UPC>] [-cdvt <us>] [aal5epd] [-name <name>] Where UPC is one of the following combinations of traffic parameters: cbr <pcr01>...
Page 288 AMI Configuration Commands [tag] -cdvt <us> aal5epd -name <name> The following is an example of how to create a UPC contract: localhost::configuration upc> new 5 vbr0 500 200 250 -cdvt 1000 aal5epd -name vbr0_upc This example speciﬁes a contract named “vbr0_upc”, which is a VBR0 con- tract with an index of 5, a pcr01 of 500 cells/sec (or kbps), an scr0 of 200 cells/ sec (or kbps), an mbs0 of 250 cells (or kilobits), a CDVT of 1,000 microseconds, and EPD enabled.
Page 289: Displaying The Upc Trafﬁc Contracts
B.17.3 Displaying the UPC Trafﬁc Contracts This command lets the user display all of the UPC contracts. Enter the follow- ing parameters: localhost::configuration upc> show Index PCR01 SCR01 MBS01 PCR0 Index PCR01 SCR01 MBS01 PCR0 SCR0 MBS0 CDVT Name NOTE: The units for PCR0, PCR01, SCR0, SCR01, MBS0, and MBS01 are shown either in cps or in kbps, depending on what you have conﬁg-...
Page 290: Virtual Channel Conﬁguration Commands
AMI Configuration Commands B.18 Virtual Channel Conﬁguration Commands These commands let the user conﬁgure permanent virtual channels (PVCs). The user can display the list of available subcommands by typing vcc ? at the conﬁguration level. localhost::configuration> vcc ? delete modify B.18.1 Deleting a Virtual Channel This command allows the user to delete an existing permanent virtual chan-...
Page 291: Modifying A Virtual Channel
B.18.2 Modifying a Virtual Channel This command enables the user to modify the UPC trafﬁc contract of an exist- ing permanent virtual channel without having to delete the channel and then recreate it. Enter the following parameters: localhost::configuration vpc> modify <port> <vpi> <vci> -upc <index> port -upc<index>...
Page 292 The following is an example of how to create a virtual channel on an SFCS-1000. To create a vcc going in port 2A1, vpi 0, vci 100 on the switch board installed in slot 2 and going out port 4B1, vpi 0, vci 100 on the switch board installed in slot 4, enter the following: localhost::configuration vcc>...
Page 293: Displaying The Virtual Channel Conﬁguration
This command allows the user to display existing virtual channels. The user can display either all of the existing virtual channels on an individual switch fabric or all of the existing virtual channels on a speciﬁc port. To list all of the...
Page 294 The ﬁelds in this display are deﬁned in the same manner as those listed above in the example for all of the permanent virtual channels on an individual switch fabric. To list all of the existing permanent virtual channels on a speciﬁc port and path, (for example, port 1C1 and VPI 0), enter the following parameters: localhost::configuration vcc>...
Page 295: Virtual Path Conﬁguration Commands
Used to delete an originating path. orig NOTE: Virtual Path 0 cannot be deleted on any of the connections to the intra-fabric ports on an SFCS-1000. NOTE: Before deleting a virtual path, you must ﬁrst delete all VCCs which use that path. AMI Configuration Commands...
Page 296: Modifying A Virtual Path
AMI Configuration Commands B.19.2 Modifying a Virtual Path This command lets the user modify the UPC contract of a through path or modify the amount of reserved bandwidth for an existing virtual path with- out having to delete the path and then recreate it. Enter the following param- eters: localhost::configuration vpc>...
Page 297: Creating A Virtual Path
B.19.3 Creating a Virtual Path This command lets the user add a virtual path in three different ways. The ﬁrst line is used for creating a through path. The second line is used for creat- ing a terminating path. The third line is used for creating an originating path. Both through paths and originating paths have advanced options which may be used in combination with the required parameters for that type of path.
Page 298 AMI Configuration Commands The following parameters make up a terminating path: port term -reserved <Kbs> -maxvci <maxvci> The following parameters make up an originating path: port orig -reserved <Kbs> -maxvci <maxvci> The following are advanced options for originating paths: -shapeovpi <vpi> -vbrob <percent>...
Page 299 NOTE: Terminating and originating paths cannot be created across the intra-fabric ports on an SFCS-1000; only through paths can be created across the intra-fabric ports as shown in the following example. AMI Configuration Commands B-147...
Page 300 AMI Configuration Commands The following is an example of how to create a virtual path on an SFCS-1000. To create a through path going in port 2A1, vpi 1 on the switch board installed in slot 2 and going out port 4B1, vpi 1 on the switch board installed in slot 4, enter the following: localhost::configuration vpc>...
Page 301: Displaying Virtual Paths
This command lets the user display existing virtual paths. The user can show either all of the existing virtual paths on an individual switch fabric or all of the existing virtual paths on a speciﬁc port. Enter the following parameters: localhost::configuration vpc>...
Page 302 AMI Configuration Commands MaxVCs Protocol To list all of the advanced options about existing virtual paths, enter the fol- lowing parameters: localhost::configuration vpc> show advanced Input Output Port Port terminate terminate terminate terminate terminate terminate terminate terminate terminate terminate 1CTL terminate originate originate...
Page 303 Port MaxBW terminate originate The ﬁelds in this display are deﬁned in the same manner as those listed above in the example for all of the virtual paths on an individual switch fabric. AMI Configuration Commands BW MaxVCs Prot 0.0K 0.0K...
Page 304 The ﬁelds in this display are deﬁned in the same manner as those listed above in the example for all of the permanent virtual paths on an individual switch fabric. To list all of the advanced options about existing permanent virtual paths on a speciﬁc port and path, (for example, port 1A1 and VPI 0) enter the following...
Page 305 APPENDIX C This chapter contains a detailed description of the AMI operation com- mands. The main operation menu can be found at the root level. There are several commands available under operation. Commands that are sub- menus are immediately followed by a “>” symbol. Typing operation ? at the prompt at the root level displays the operation commands for the i960-based switches as follows: localhost::operation>...
Page 306: Backing Up The Database
ﬁle will be backed up must be running the tftp server code. Since the SCP on a 9A000, SFCS-200WG, SFCS-200BX, and an SFCS-1000 uses tftp to perform the CDB backup, you must ﬁrst create an empty ﬁle in the /tft- pboot directory on the remote host to receive the CDB.
Page 307: Initializing The Database
AMI Operation Commands C.1.2 Initializing the Database This command lets the user initialize the CDB. The switch asks you to verify this action before it re-initializes the CDB. Enter the following parameters: localhost::operation cdb> init This command will re-initialize the CDB and reboot the switch...
Page 308: Resetting The Database
Are you sure you want to reset the CDB [n]? y The switch will restart momentarily. At this point, the switch resets the CDB, closes the user out of all active ses- sions, and restarts the switch. The user must then log in to AMI again to per- form any more actions on the switch.
Page 309: Environment Commands
? fabric> temperature C.2.1 CPU Operation This command lets the user display information about the CPU on a 9A000, SFCS-200WG, an SFCS-200BX, and an SFCS-1000. Enter the following param- eters: localhost::operation environment> cpu Type State i960 normal The ﬁelds in this display are deﬁned as follows:...
Page 310: Switch Fabric Operation
Switch Fabric Operation These commands allow the user to monitor the temperature of the individual switch fabrics on an SFCS-1000 only. Typing fabric ? at the prompt at the environment level displays the cdb commands as follows: localhost::operation environment> fabric ? show C.2.3...
Page 311: Conﬁguring The Switch Fabric Temperature Thresholds
This command allows the user to set the thresholds at which a temperature alarm will be tripped and then later reset on an SFCS-1000. Any temperature can cause the switch to display a state of normal or overTemp, depending on the trip and reset thresholds set by the user.
Page 312: Fan Operation
AMI Operation Commands C.2.5 Fan Operation This command enables the user to display information about the fans on an SFCS-1000 only. Enter the following parameters: localhost::operation environment> fans FanBank FanBank FanBankState FanBankState normal normal normal normal FanBank corresponds to a single fan, indicating the number of the fan.
Page 313: Power Supply Operation
Enter the following parameters to display information for a DC-powered SFCS-1000: localhost::operation environment> power PowerSupply Type ps48VDC ps48VDC Enter the following parameters to display information for an SFCS-1000 with tall AC power supplies: localhost::operation environment> power PowerSupply Type psAutoRangeAC psAutoRangeAC...
Page 314: Temperature Sensor Operation
On an SFCS-200BX, 1 indicates the left power supply and 2 indicates the right power supply. On an SFCS-1000, 1 indicates the power supply in slot 1 in the chassis and 2 indicates the power supply in slot 2 in the chassis.
Page 315: Panic Acknowledgment Commands
C.2.8 Panic Acknowledgment Commands On occasion, the SCP may go into a state called panic, in which it reboots, closes a user out of session, or goes into a hung or frozen state as the result of a software bug. When the SCP returns to a normal state and an active session is running again, the ﬁrst thing the user should do is to use the operation panic show AMI command to display information about what happened to the SCP when it panicked.
Page 316: Displaying The Panic Dump File
AMI Operation Commands Enter the following parameters to clear a panic condition: localhost::operation panic> clear The message above is shown when a panic has been cleared. The message below is shown when no panic dump ﬁle exists (i.e., the SCP did not panic).
Page 317 There is no panic dump to show you. Thank goodness. NOTE: If the switch panics, the panic ﬁle is automat- ically written to syslog upon reboot, provided that a syslog host had been set prior to the panic.
Page 318: Displaying And Setting The Date And Time
AMI Operation Commands Displaying and Setting the Date and Time This command allows the user to display the current date and time on the switch. To display this information, enter date at the operation level. localhost::operation> date Jan 11 16:32:01 -05:00 1996 This command also enables the user to set the current date and time on the switch.
Page 319: Flash Operation Commands
FLASH Operation Commands These commands enable management of the FLASH memory system. Typing ﬂash ? at the prompt at the operation level displays the ﬂash commands as follows: localhost::operation> flash ? copy delete init C.4.1 Copying a File to FLASH Memory This command allows the user to copy a ﬁle within the FLASH memory sys- tem.
Page 320: Deleting A File From Flash Memory
AMI Operation Commands C.4.2 Deleting a File from FLASH Memory This command allows the user to delete a ﬁle from the FLASH memory sys- tem. Enter the following parameters: localhost::operation flash> delete <file> In order to delete a directory from the FLASH memory system (e.g., ft343.24), you must ﬁrst delete all ﬁles in that directory.
Page 321: Displaying The Flash Memory Directory
C.4.3 Displaying the FLASH Memory Directory This command enables the user to display the directory listing of the FLASH memory system. Enter the following parameters: localhost::operation flash> dir ft343.24 ft343.25 CURRENT C.4.4 Displaying Free Space on the FLASH File This command lets the user display the amount of remaining free space in the FLASH memory system.
Page 322: Initializing The Flash File
Initializing the FLASH File This command lets the user initialize the FLASH ﬁle. CAUTION Because this action results in the removal of data, the switch asks you to ver- ify this action before it re-initializes the FLASH ﬁle. Enter the following parameters: localhost::operation flash>...
Page 323: Renaming A Flash File
Indicates the current name of the ﬁle to be renamed. Indicates the new name of the ﬁle to be renamed. Setting or Changing the Password This command allows the user to set or to change the switch’s administrative password. NOTE:...
Page 324: Upgrading The Switch
C-20 The remote host on which the upgrade ﬁle resides must be a tftpboot server. To perform the initial switch software upgrade successfully, the bootp server and the tftpboot server must be conﬁgured prop- erly. For complete instructions about per-...
Page 325: Displaying And Changing The Version Of Software
You are asked to verify that you want to take this action. Enter the following parameters: localhost::operation> reboot Are you sure you want to reboot this switch [n]? y Upon reboot, the SCP immediately closes the user out of all open AMI ses- sions.
Page 326 AMI Operation Commands C-22...
Page 327: Appendix Dami Statistics Commands
This chapter contains a detailed description of the AMI statistics commands that display operational performance and error information for the various hardware and software features of the switch and the network modules. The main statistics menu can be found at the root level. There are several com- mands available under statistics.
Page 328: Aal4 Statistics
AMI Statistics Commands D.2 AAL4 Statistics You can display AAL4 statistics for an individual switch fabric by entering aal4 at the statistics level. localhost::statistics> aal4 Intfce XmtCell RcvCell asx0 291691 The ﬁelds in this display have the following meanings: Interface...
Page 329: Aal5 Statistics
D.3 AAL5 Statistics You can display AAL5 statistics for an individual switch fabric by entering aal5 at the statistics level. localhost::statistics> aal5 Intfce XmtCell RcvCell XmtPDU asx0 77683 3840 45888 qaa0 1322913 103970 719509 The ﬁelds in this display have the following meanings:...
Page 330: Atm Statistics
AMI Statistics Commands D.4 ATM Statistics You can display ATM statistics for an individual switch fabric by entering atm at the statistics level. localhost::statistics> atm Interface XmtCell asx0 412064 qaa0 6958226 The ﬁelds in this display have the following meanings:...
Page 331: Switch Board Statistics
Displays the number of cells that do not match any VCI lookup tables. D.6 Control Port Statistics You can list the control port statistics for an individual switch fabric by enter- ing ctlport at the statistics level. localhost::statistics> ctlport Interface...
Page 332: Statistics
You can list statistics about all of the DS-3 network modules in an individual switch fabric by entering ds3 at the statistics level. This command is available only when at least one DS-3 network module is installed in the switch fabric. localhost::statistics> ds3...
Page 333 The ﬁelds in this display have the following meanings: ds3FramingLOSs Speciﬁes the number of seconds in which Loss Of Signal (LOS) errors were detected by the DS3 Receive Framer block. ds3FramingLCVs Indicates the number of Line Code Violations (LCV) that were detected by the DS3 Receive Framer block. ds3FramingSumLCVs Shows the number of DS3 information blocks (85 bits) which contain one or more Line Code Violations...
Page 334 AMI Statistics Commands ds3PlcpBIP8s ds3PlcpFEBEs ds3PlcpYellows ds3AtmHCSs ds3AtmRxCells ds3AtmTxCells Lists the number of BIP-8 (Bit Interleaved Parity - 8) error events. The BIP-8 is calculated over the Path Overhead ﬁeld and the associated ATM cell of the previous frame. A BIP-N is a method of error moni- toring.
Page 335: Statistics
You can display statistics about all of the E-3 network modules in an individ- ual switch fabric by entering e3 at the statistics level. This command is avail- able only when at least one E-3 network module is installed in the switch fabric.
Page 336 AMI Statistics Commands The ﬁelds in this display have the following meanings: e3FramingLOSs e3FramingLCVs e3FramingFERRs e3FramingOOFs e3FramingFERFs e3FramingAISs e3FramingFEBEs e3FramingBIP8s e3PlcpFERRs e3PlcpLOFs D-10 Speciﬁes the number of seconds in which Loss Of Signal (LOS) errors were detected by the E3 Receive Framer block.
Page 337 e3PlcpBIP8s Shows the number of BIP-8 (Bit Interleaved Parity-8) error events. The BIP-8 is calculated over the Path Overhead ﬁeld and the associated ATM cell of the previous frame. A BIP-N is a method of error moni- toring. An N-bit code is generated by the transmit- ting equipment in such a manner that the ﬁrst bit of the code provides even parity over the ﬁrst bit of all N-bit sequences in the previous VT SPE, the second...
Page 338: Icmp Statistics
AMI Statistics Commands D.9 ICMP Statistics You can list ICMP statistics for an individual switch fabric by entering icmp at the statistics level. localhost::statistics> icmp icmp Counter ------------------------------ -------------------- -------------------- icmpInMsgs icmpInErrors icmpInDestUnreachs icmpInTimeExcds icmpInParmProbs icmpInSrcQuenchs icmpInRedirects icmpInEchos icmpInEchoReps icmpInTimestamps...
Page 339 AMI Statistics Commands The ﬁelds in this display have the following meanings: icmpInMsgs Indicates the total number of ICMP messages which the entity received. Note that this counter includes all those counted by icmpInErrors. icmpInErrors Shows the number of ICMP messages which the entity received but determined as having ICMP-spe- ciﬁc errors (bad ICMP checksums, bad length, etc.).
Page 340 AMI Statistics Commands icmpOutErrors Displays the number of ICMP messages which this entity did not send due to problems discovered within ICMP such as a lack of buffers. This value should not include errors discovered outside the ICMP layer such as the inability of IP to route the resultant datagram.
Page 341: Interface Statistics
D.10 Interface Statistics You can list interface statistics for an individual switch fabric by entering interface at the statistics level. localhost::statistics> interface Interface lo0 Counter ------------------------------ -------------------- -------------------- ifInOctets ifInUcastPkts ifInNUcastPkts ifInDiscards ifInErrors ifInUnknownProtos ifOutOctets ifOutUcastPkts ifOutNUcastPkts ifOutDiscards ifOutErrors ifOutQLen Press return for more, q to quit: q The ﬁelds in this display have the following meanings:...
Page 342 AMI Statistics Commands ifInErrors Indicates the number of inbound packets that con- tained errors preventing them from being deliverable to a higher-layer protocol. ifInUnknownProtos Shows the number of packets received via the inter- face which were discarded because of an unknown or unsupported protocol.
Page 343: Ip Statistics
D.11 IP Statistics You can display IP statistics for an individual switch fabric by entering ip at the statistics level. localhost::statistics> ip ip Counter ------------------------------ -------------------- -------------------- ipInReceives ipInHdrErrors ipInAddrErrors ipForwDatagrams ipInUnknownProtos ipInDiscards ipInDelivers ipOutRequests ipOutDiscards ipOutNoRoutes ipReasmReqds ipReasmOKs ipReasmFails...
Page 344 AMI Statistics Commands ipInAddrErrors Shows the number of input datagrams discarded because the IP address in their IP header’s destina- tion ﬁeld was not a valid address to be received at this entity. This count includes invalid addresses (e.g., 0.0.0.0) and addresses of unsupported Classes (e.g., Class E).
Page 345 AMI Statistics Commands ipOutNoRoutes Lists the number of IP datagrams discarded because no route could be found to transmit them to their destination. This counter includes any packets counted in ipForwDatagrams which meet this “no- route” criterion. Note that this includes any data- grams which a host cannot route because all of its default gateways are down.
Page 346: Network Module Statistics
You can list network module statistics about all of the network modules in an individual switch fabric by entering module at the statistics level. The fol- lowing statistics are displayed on all switches, except an SFCS-1000: localhost::statistics> module Module Priority The following statistics are displayed on an SFCS-1000 only: localhost::statistics>...
Page 347 Module Shows the number of each network module that is currently installed in the switch fabric. The 1 means that it is the ﬁrst switch fabric. The letters show the position of the network module in the switch fabric. Priority Indicates the priority level for each network module.
Page 348: Port Statistics
AMI Statistics Commands D.13 Port Statistics You can display port statistics about all of the ports on an individual switch fabric by entering port at the statistics level. localhost::statistics> port Port Received-Cells 1CTL 241397 The ﬁelds in this display have the following meanings:...
Page 349: Sonet Statistics
D.14 SONET Statistics You can display statistics about all of the SONET network modules on an individual switch fabric by entering sonet at the statistics level. This com- mand is available only when at least one SONET network module is installed in the switch fabric.
Page 350 AMI Statistics Commands sonetSectionLOFs sonetLineBIPs sonetLineFEBEs sonetLineAISs sonetLineFERFs sonetPathBIPs D-24 Speciﬁes the number of seconds in which Loss Of Frame (LOF) has occurred. A LOF is declared when an out-of-frame (OOF) condition persists for 3ms. The LOF is cleared when an in-frame condition per- sists for 3ms.
Page 351 AMI Statistics Commands sonetPathFEBEs Displays the number of path Far End Block Errors (FEBE) that have been detected since the last time the port has been reset. FEBEs are detected by extracting the 4-bit FEBE ﬁeld from the path status byte (G1). The valid range for the 4-bit ﬁeld is between 0000 and 1000, representing zero to eight errors.
Page 352: Spans Statistics
AMI Statistics Commands D.15 SPANS Statistics You can list SPANS statistics for an individual switch fabric by entering spans at the statistics level. localhost::statistics> spans Port 1D1 Counter ---------------------------------- --------------- -------------------- sigPathVCCs sigPathRestarts sigPathCallsCompletions sigPathCallsFailures sigPathCallsRejections sigPathSpansTransmittedMessages sigPathSpansReceivedMessages sigPathClsTransmittedMessages sigPathClsReceivedMessages Press return for more, q to quit: q The ﬁelds in this display have the following meanings:...
Page 353: Tcp Statistics
D.16 TCP Statistics You can display TCP statistics for an individual switch fabric by entering tcp at the statistics level. localhost::statistics> tcp tcp Counter ------------------------------ -------------------- -------------------- tcpActiveOpens tcpPassiveOpens tcpAttemptFails tcpEstabResets tcpCurrEstab tcpInSegs tcpOutSegs tcpRetransSegs The ﬁelds in this display have the following meanings:...
Page 354 AMI Statistics Commands tcpCurrEstab Shows the number of TCP connections for which the current state is either ESTABLISHED or CLOSE- WAIT. tcpInSegs Lists the total number of segments received, includ- ing those received in error. This count includes seg- ments received on currently established connections. tcpOutSegs Displays the total number of segments sent, includ- ing those on current connections but excluding those...
Page 355: Tp25 Statistics
D.17 TP25 Statistics You can display statistics about all of the TP25 network modules in an indi- vidual switch fabric by entering tp25 at the statistics level. The following TP25 command is available only when at least one TP25 network module is installed in the switch fabric.
Page 356: Udp Statistics
AMI Statistics Commands D.18 UDP Statistics You can display UDP statistics for an individual switch fabric by entering udp at the statistics level. localhost::statistics> udp udp Counter ------------------------------ -------------------- -------------------- udpInDatagrams udpNoPorts udpInErrors udpOutDatagrams The ﬁelds in this display have the following meanings:...
Page 357: Uni 3.0 Statistics
D.19 UNI 3.0 Statistics You can show UNI 3.0 statistics for an individual switch fabric by entering uni30 at the statistics level. localhost::statistics> uni30 Port 1D1 Counter ---------------------------------- ---------------- -------------------- q2931VCCs q2931Restarts q2931CallsCompletions q2931CallsFailures q2931CallsRejections q2931TransmittedMessages q2931ReceivedMessages Press return for more, q to quit: q The ﬁelds in this display have the following meanings:...
Page 358: Vcc Statistics
AMI Statistics Commands D.20 VCC Statistics You can display virtual channel statistics for an individual switch fabric by entering vcc at the statistics level. localhost::statistics> vcc Input Output Port VCI Port 5 4CTL 14 4CTL 15 4CTL 16 4CTL 5 4CTL...
Page 359: Vpc Statistics
D.21 VPC Statistics You can display virtual path statistics for an individual switch fabric by enter- ing vpc at the statistics level. localhost::statistics> vpc Input Output Port Port Uptime terminate 0d:01:56 terminate 0d:01:56 terminate 0d:01:56 terminate 0d:01:56 terminate 0d:01:56 terminate...
Page 360 AMI Statistics Commands D-34...
Page 361: Appendix Esnmp Conﬁguration
APPENDIX E SNMP Conﬁguration The switch control software for the ATM switches includes an SNMP agent. The SNMP agent enables the remote monitoring and conﬁguration of these switches. SNMP Indexing There are two main SNMP indexing schemes used: software port indices and hardware port indices.
Page 362 SNMP Configuration Table E.1 - 9A000/SFCS-200WG/SFCS-200BX Port Software Port Board-Netmod- Name Number Port Index Port Software Port Name Number 0.0.0 0.0.1 0.0.2 0.0.3 0.0.4 0.0.5 0.1.0 0.1.1 0.1.2 0.1.3 0.1.4 0.1.5 Board-Netmod- Port Index 0.2.0 0.2.1 0.2.2 0.2.3 0.2.4 0.2.5 0.3.0 0.3.1 0.3.2...
Page 363: Snmp Traps
The SNMP agent on the switch supports several SNMP traps. The traps generated by the switch’s SNMP agent can be sent to as many desti- nations as needed. These destinations are conﬁgurable via the ATM Manage- ment Interface (AMI).
Page 364 This trap alerts that one ATM switch fan bank failed. The fan bank that failed is identiﬁed by the fan bank index. This trap alerts that one ATM switch fan bank is up. The fan bank that is back up is identiﬁed by the fan bank index.
Page 365 Table E.2 - SNMP Traps Supported on the SFCS Switches Trap Trap Name Number asxLinkUp asxSpansDown asxSpansUp asxTempSensorOverTemp asxTempSensorRegularTemp This trap alerts that one of the temperature sensors asxFabricTemperature- OverTemp asxFabricTemperature- RegularTemp asxSonetLOSon asxSonetLOSoff Description This trap alerts that the link that is identiﬁed by {hwPortBoard, hwPortModule, hwPortNumber} is back up.
Page 366 SNMP Configuration Table E.2 - SNMP Traps Supported on the SFCS Switches Trap Trap Name Number asxSonetPathLabelOn asxSonetPathLabelOff asxSonetLineAISon asxSonetLineAISoff asxDS3FERFOn asxDS3FERFOff asxDS3PLCPYellowOn asxDS3PLCPYellowOff asxDS3PLCPYellowDetected This trap indicates that the speciﬁed DS3 port has asxDS3PLCPYellowCleared asxDS3PLCPLOFDetected Description This trap indicates that the speciﬁed SONET port is receiving and errored C2 Path Label byte.
Page 367 Table E.2 - SNMP Traps Supported on the SFCS Switches Trap Trap Name Number asxDS3PLCPLOFCleared asxDS3LOFDetected asxDS3LOFCleared asxDS3AISDetected asxDS3AISCleared asxDS3LOSDetected asxDS3LOSCleared asxDS1YellowOn asxDS1YellowOff asxDS1PLCPYellowOn asxDS1PLCPYellowOff asxDS1PLCPYellowDetected This trap indicates that the speciﬁed DS1 port has asxDS1PLCPYellowCleared asxDS1PLCPLOFDetected Description This trap indicates that the speciﬁed DS3 port has detected clearance of incoming LOF Alarm.
Page 368 SNMP Configuration Table E.2 - SNMP Traps Supported on the SFCS Switches Trap Trap Name Number asxDS1PLCPLOFCleared asxDS1YellowDetected asxDS1YellowCleared asxDS1AISDetected asxDS1AISCleared asxDS1LOSDetected asxDS1LOSCleared asxDS1LOFDetected asxDS1LOFCleared asxDS3FERFDetected asxDS3FERFCleared asxJ2YellowOn asxJ2YellowOff asxJ2YellowDetected Description This trap indicates that the speciﬁed DS1 port has detected clearance of an incoming LOF Alarm.
Page 369 This trap indicates that a series A or B network mod- ule was inserted into a switch board running in extended mode. This trap indicates that a series C or greater network module was inserted into a switch board running in non-extended mode.
Page 370 This trap is generated when Callrecord functionality is unable to allocate memory as speciﬁed by crMemory- Allocated. This can happen when the crConfAdmin- Status changes state from “off” or when the switch reboots when Callrecords is conﬁgured “on”. This trap is generated when any of the callrecord related functionality fails for any reason.
Page 371: Adding Snmp Trap Destinations
E.2.1 Adding SNMP Trap Destinations To create one or more SNMP trap destinations on a Cabletron switch, log in to AMI and open a session on the switch. Enter the following parameters: conﬁguration snmp trap new <ipaddress> The <ipaddress> variable indicates the IP address of the SNMP trap destina- tion that is to be created.
Page 372: Removing Snmp Trap Destinations
To delete one or more SNMP trap destinations for a Cabletron switch, log in to AMI and open a session on the switch. Prior to deleting any trap that may need to be recreated later, as a precaution, a recommended practice is to list all trap destinations using AMI and either copy the screen or write down the destinations.
Page 373: Appendix F Forethought Pnni
This appendix provides a broad overview of Cabletron Systems’ version of PNNI, ForeThought PNNI (FT-PNNI), and its use in a multiple-switch net- work. FT-PNNI is a scalable routing and signalling protocol used in networks containing multiple Cabletron switches. FT-PNNI simpliﬁes large network topologies by organizing the nodes (switches) in that network into smaller groups.
Page 374: Hello Protocol
• Hierarchical Routing F.1.1 Hello Protocol At regular intervals, each switch transmits a hello indication on each of its FT-PNNI routing channels. The time between these hello indications is called the Hello Indication Interval. When a switch receives a hello indication from one of its neighbors, it initializes the logical link (loglink) from that neighbor to itself in the topology database.
Page 375: Hierarchical Routing
Each switch in a FT-PNNI network is conﬁgured with a 13-byte preﬁx called the switch preﬁx. Hosts that are attached to the switch are presented with this preﬁx during ILMI address registration. It is in this way that end systems are...
Page 376 ID. The peer group ID is a unique identiﬁer for every node (switch or end system) in a particular peer group. Every switch and host in peer group A, for exam- ple, will have the same peer group ID.
Page 377: The Physical Network
Eventually, and within a very brief period of time, every switch in the network is aware of the new addition and the links by which that new addition can be reached. This topology is stored by each switch in a topology database.
Page 378 ForeThought PNNI Figure F.2 - Private ATM Network with 21 Switches and 34 Bidirectional Links It is in these large, single-level networks that FT-PNNI is most useful, because it lets you simplify large network topologies by creating a two-level hierarchy. In this hierarchy, communities of contiguous switches are grouped together and they are collectively summarized by a single, logical node.
Page 379 ForeThought PNNI Peer Group C Peer Group Peer Group D Border Switch Switch/Node Logical Link (loglink) Peer Group A Peer Group B Figure F.3 - Example of FT-PNNI Hierarchy Showing Lowest-Level Peer Groups...
Page 380: Peer Groups
F.2.3 Border Switches A border switch is any switch that has at least one link to a switch in another peer group. Border switches play an important role in FT-PNNI because they are responsible for summarizing reachability information for their respective peer groups, appropriately ﬁltering the ﬂow of topology database informa-...
Page 381: Peer Group Summary Node (Pgsn
For example, each switch in peer group A is aware of every other switch in peer group A, the border switches in the rest of the network, the links between them, and the backbone topology.
Page 382 ForeThought PNNI F-10...
Page 383 GLOSSARY 802.1d Spanning Tree Bridging - the IEEE standard for bridging; a MAC layer standard for transparently connecting two or more LANs (often called subnetworks) that are running the same protocols and cabling. This arrange- ment creates an extended network, in which any two workstations on the linked LANs can share data.
Page 384 Assigned Cell - a cell that provides a service to an upper layer entity or ATM Layer Management entity (ATMM-entity). asxmon - a FORE program that repeatedly displays the state of the switch and of all its active ports. Asynchronous time division multiplexing - a multiplexing technique in which a transmission capability is organized into a priori, unassigned time slots.
Page 385 GLOSSARY ATM Link - a virtual path link (VPL) or a virtual channel link (VCL). ATM Peer-to-Peer Connection - a virtual channel connection (VCC) or a vir- tual path connection (VPC) directly established, such as workstation-to-work- station. This setup is not commonly used in networks. ATM Trafﬁc Descriptor - a generic list of parameters that can be used to cap- ture the intrinsic trafﬁc characteristics of a requested ATM connection.
Page 386 ATM network (e.g., digital information such as video and digitized voice). cchan - a FORE program used to manage virtual channels on a FORE Systems ATM switch running asxd. CCITT (International Telephone and Telegraph Consultative Committee) - the international standards body for telecommunications.
Page 387 ATM switch running asxd. cport - a FORE program used to monitor and change the state of ports on a FORE Systems ATM switch running asxd. CRC (Cyclic Redundancy Check) - an error detection scheme in which a number is derived from the data that will be transmitted. By recalculating the CRC at the remote end and comparing it to the value originally transmitted, the receiving node can detect errors.
Page 388 SDUs from a single connection to more than one connection. (See multiplexing.) DIP Switch (Dual In-line Package) - a device that has two parallel rows of contacts that let the user switch electrical current through a pair of those con- tacts to on or off.
Page 389 GLOSSARY elconﬁg - a FORE program that shows and modiﬁes LEC conﬁguration. Allows the user to set the NSAP address of the LAN Emulation Conﬁguration Server (LECS), display the list of Emulated LANs (ELANs) conﬁgured in the LECS for this host, display the list of ELANs locally conﬁgured along with the membership state of each, and locally administer ELAN membership.
Page 390 GLOSSARY Frame Relay - a fast packet switching protocol based on the LAPD protocol of ISDN that performs routing and transfer with less overhead processing than X.25. FT-PNNI (ForeThought PNNI) - a FORE Systems routing and signalling pro- tocol that uses private ATM (NSAP) addresses; a precursor to ATM Forum PNNI (see PNNI).
Page 391 GLOSSARY ICMP (Internet Control Message Protocol) - the protocol that handles errors and control messages at the IP layer. ICMP is actually a part of the IP protocol layer. It can generate error messages, test packets, and informational mes- sages related to IP. IEEE (Institute of Electrical and Electronics Engineers) - the world’s largest technical professional society.
Page 392 GLOSSARY In a Class A network, the ﬁrst of the numbers is the network number, the last three numbers are the local host address. In a Class B network, the ﬁrst two numbers are the network, the last two are the local host address.
Page 393 GLOSSARY ISA Bus - a bus standard developed by IBM for expansion cards in the ﬁrst IBM PC. The original bus supported a data path only 8 bits wide. IBM subse- quently developed a 16-bit version for its AT class computers. The 16-bit AT ISA bus supports both 8- and 16-bit cards.
Page 394 GLOSSARY LEC (LAN Emulation Client) - the component in an end system that per- forms data forwarding, address resolution, and other control functions when communicating with other components within an ELAN. lecs - a FORE program that implements the assignment of individual LECs to different emulated LANs.
Page 395 Network Module - ATM port interface cards which may be individually added or removed from any Cabletron ATM switch to provide a diverse choice of connection alternatives. Each network module provides between one and six full-duplex ATM physical connections to the Cabletron switch.
Page 396 PBX (Private Branch Exchange) - a private phone system (switch) that con- nects to the public telephone network and offers in-house connectivity. To reach an outside line, the user must dial a digit like 8 or 9.
Page 397 GLOSSARY Physical Layer (PHY) Connection - an association established by the PHY between two or more ATM-entities. A PHY connection consists of the concat- enation of PHY links in order to provide an end-to-end transfer capability to PHY SAPs. PMD (Physical Medium Dependent) - a sublayer concerned with the bit transfer between two network nodes.
Page 398 GLOSSARY Proxy - the process in which one system acts for another system to answer protocol requests. Proxy Agent - an agent that queries on behalf of the manager, used to monitor objects that are not directly manageable. PSN (Packet Switched Network) - a network designed to carry data in the form of packets.
Page 399 GLOSSARY trailer are added to this basic segment. The header identiﬁes the message type (beginning, end, continuation, or single) and contains sequence numbering and message identiﬁcation. The trailer gives the SAR-PDU payload length, exclusive of pad, and contains a CRC check to ensure the SAR-PDU integrity. The result is a 48-byte PDU that ﬁts into the payload ﬁeld of an ATM cell.
Page 400 GLOSSARY snmpd - an SMNP agent for a given adapter card. SONET (Synchronous Optical Network) - a new and growing body of stan- dards that deﬁnes all aspects of transporting and managing digital trafﬁc over optical facilities in the public network. Source Trafﬁc Descriptor - a set of trafﬁc parameters belonging to the ATM Trafﬁc Descriptor used during the connection set-up to capture the intrinsic trafﬁc characteristics of the connection requested by the source.
Page 401 - a program interrupt mechanism that automatically updates the state of the network to remote network management hosts. The SNMP agent on the switch supports these SNMP traps. UBR (Unspeciﬁed Bit Rate) - a type of trafﬁc that is not considered time-criti- cal (e.g., ARP messages, pure data), allocated whatever bandwidth is avail-...
Page 402 VPCs and translates VCI values. The Virtual Channel Switch is directed by Control Plane functions and relays the cells of a VC. Virtual Path Switch - a network element that connects VPLs, it translates VPI (not VCI) values and is directed by Control Plane functions. The Virtual Path Switch relays the cells of a Virtual Path.
Page 403 GLOSSARY VPC (Virtual Path Connection) - a concatenation of VPLs between virtual path terminators (VPTs). VPCs are unidirectional. VPDN (Virtual Private Data Network) - a private data communications net- work built on public switching and transport facilities rather than dedicated leased facilities such as T1s.
Page 404 GLOSSARY g-22...

Cabletron Systems SFCS-1000 Configuration Manual

Preface

Chapter 1 Conﬁguring Pvcs

Chapter 2 Conﬁguring a Classical IP ATM Network

Chapter 3 Conﬁguring an Emulated LAN

Chapter 4 SONET Conﬁguration

Chapter 5 DS-3 Conﬁguration

Conﬁguration

Chapter 6 E-3 Conﬁguration

Conﬁguration

Chapter 7 TP25 Conﬁguration

Chapter 8 TAXI Conﬁguration

Appendix Aami Overview

Appendix B AMI Configuration Commands

Appendix C AMI Operation Commands

Quick Links

Related Manuals for Cabletron Systems SFCS-1000

Summary of Contents for Cabletron Systems SFCS-1000