|
|
Audience ² Organization ² Related Documentation ² Text Conventions
This document describes Light-Stream 2020 hardware, tells you how to install LightStream 2020 enterprise ATM switches, and covers the following troubleshooting tasks:
The audience for this book includes Light-Stream customers and employees of LightStream and partner companies who need information on installing LightStream systems, configuring the hardware, and resolving hardware problems.
| Warning This book is intended for use only by qualified service personnel. Tasks described here can expose unqualified personnel to mechanical and electrical hazards. |
This manual is organized as follows:
The following is a list of LightStream manuals and other material relevant to LightStream users.
The system overview describes what a LightStream switch is and how it works. It outlines ATM technology and describes LightStream hardware and software.
The site planning and cabling guide (SPCG) describes how to prepare your site to receive LightStream hardware. It includes space, environmental and electrical requirements, rack selection guidelines, requirements for the management workstation, and information on cables and connectors.
The configuration guide provides the information you need to configure LightStream switches. It describes the configuration tools and how to use them. It describes the configuration database and defines all configurable attributes and their settings. The guide also provides step-by-step configuration procedures.
The operations guide is a task-oriented book that tells you how to operate a network of LightStream switches. The guide presents an overview of network operations tasks, describes the command line interface (CLI), and presents procedures for performing monitor and control tasks such as displaying the status of nodes, cards and ports, viewing statistics, and creating collections of traffic data.
The administration guide describes LightStream network management functions such as setting up a new network, troubleshooting, and optimizing the load across trunks. The guide describes network management tools, then presents step-by-step procedures for performing the functions.
This manual presents an overview of LightStream traps (error and event messages) and a list of operational, SNMP, and informational traps generated by the LightStream switch.
The reference guide provides detailed descriptions of the syntax and functions of all CLI commands. It also indicates CLI equivalents of configuration procedures, describes the LightStream private MIB, and gives UNIX-style manual pages for LynxOS commands.
The reference card compactly summarizes the syntax and arguments of all CLI commands.
The release notes provide a software upgrade procedure and describe new features and special considerations, including information on known software bugs.
LightStream provides online help for its command line interface and its configuration program.
Before attempting to install, configure, operate, or troubleshoot a network of LightStream switches, read the LightStream 2020 System Overview. This overview provides important background information about the LightStream product and the ATM technology on which the product is based. After reading the LightStream 2020 System Overview, refer to Table 1-1 to determine which manuals you should read next.
Table 1-1 LightStream Reading Path
| If you want to: | Read the following manuals in the order listed below: |
|---|---|
LightStream 2020 Release Notes1 |
|
LightStream 2020 Release Notes1 |
|
LightStream 2020 Release Notes1 |
|
LightStream 2020 Release Notes1 LightStream 2020 Operations Guide LightStream 2020 Command and Attribute Reference Guide LightStream 2020 Command Line Interface (CLI) Reference Card |
|
LightStream 2020 Release Notes1 LightStream 2020 Operations Guide LightStream 2020 Administration Guide LightStream 2020 Command and Attribute Reference Guide LightStream 2020 Command Line Interface (CLI) Reference Card |
|
LightStream 2020 Release Notes1 |
| 1We recommend that you review the release notes before attempting to install, configure, operate, or troubleshoot a LightStream switch. The release notes contain important information that does not appear in other documents. |
In this document, several conventions distinguish different types of graphics.
Chassis ² Midplane ² Switch Card ² Network Processor Card ² Disk Assembly ² Line Cards ² Access Cards ² Fantails² Card LEDs ² Test and Control System ² Cooling ² Power Options
The hardware elements of a LightStream 2020 enterprise ATM switch are outlined in Figure 2-1. This chapter describes each component of a LightStream node, starting with the chassis and midplane.
The chassis serves as a skeleton and container for the LightStream system. It provides access to components from both the front and back. The chassis measures 18.9 inches (48 cm) wide by 26 inches (66 cm) high by 24.7 inches (63 cm) deep. It contains all the hardware elements shown in Figure 2-1. Figure 2-2 shows the front view of a fully loaded, redundantly configured LightStream chassis and Figure 2-3 shows the rear view.
From the front of the LightStream chassis, you have access to network processor cards, line cards, switch cards, disk drive units, and one of the two blowers. Power supplies, access cards, fantails (if any), external cabling, connectors for consoles and modems, and the other blower are accessible from the rear of the chassis.
The LightStream chassis can be mounted in a standard 19 inch wide rack. Guidelines for selecting racks are provided in the LightStream 2020 Site Planning and Cabling Guide; rack mounting instructions appear in "Installing a LightStream Switch" section of this manual.
Each LightStream node has a midplane that contains most of the internal wiring for the node. The midplane, which is a field-replaceable unit (FRU), connects the NPs and line cards to switch cards and also connects the function cards (NPs and line cards) to their I/O access cards. The midplane simplifies system assembly, increases reliability, and improves mean time to repair. The midplane carries 48-volt power to all the cards in the system and interconnects the Test and Control System hub and slave processors.
Figure 2-4 shows a conceptual view of a midplane with several cards connected to it.
NPs, line cards and switch cards plug into the front of the midplane, and I/O access cards associated with each function card plug into the rear of the midplane. The connections between function cards and their I/O access cards pass through the midplane on connector pins, but do not make electrical connection with the midplane. The midplane contains all the internal wiring to connect the function cards to the switch cards.
The midplane provides connections for up to:
Up to 12 cards (10 function cards and 2 switch cards) can be connected to the front of the LightStream midplane. The twelve slots in the chassis are divided into function card slots, numbered 1 through 10, and switch card slots, designated A and B. Switch card slots A and B are located in the center of the chassis, between function card slots 5 and 6. (See Figure 2-4.)
The function cards connect to the switch card via the center 96-pin DIN connector in each slot. The upper and lower 96-pin DIN connectors are used to connect the function card to the access card on the other side of the midplane.
| Caution Although function cards and switch cards are the same size, their midplane connectors are completely different. Do not attempt to place a function card in a switch card slot or vice versa. Attempts to do so may result in damage to the connectors on the midplane or the cards. |
Figure 2-5 shows the connectors on the front of the midplane.
Up to 10 I/O access cards, two console/modem assemblies, and two power supplies can be connected to the back of the LightStream midplane.
Figure 2-6 shows the connectors on the back of the midplane.
The 96-pin DIN connectors in each slot connect the access card to the function card on the other side of the midplane.
Each bulk power tray connects to one connector on the rear of the midplane. The console and modem ports for each switch card share one shrouded pin-header connector located on the rear of the midplane behind the switch card.
On the midplane are two EEPROM chips whose contents, which are written in the factory, include:
(A modem port is associated with each switch card.)
If you replace the midplane, you may need to program some of the information listed above into the EEPROMs on the new midplane. Refer to the midplane replacement procedure in "Replacing FRUs" section of this manual and to the EEPROM programming procedures in the LightStream 2020 Operations Guide.
The chassis IDs in the two midplane EEPROMs in a LightStream switch must be identical, and they must be otherwise unique in your network. For this reason, LightStream Corp. assigns a unique chassis ID number to every LightStream 2020. To ensure that the correct chassis ID is restored in the even of an EEPROM failure, you should keep a record of the chassis ID for every system in your network.
You may wish to change the modem initialization string and modem password on your system. If you change these values for one switch card slot, be sure to change the values for other slot to match. If modem information is not consistent across slots, you could have modem access problems if you move a switch card from one slot to another or if, in a redundant configuration, your backup switch card becomes active.
The midplane acts as the main logic ground point in the LightStream chassis.
The midplane distributes high current bulk power to the function and switch cards. Bulk power arrives on the midplane through connectors mounted on the power tab, a projection on the left side of the midplane.
The midplane is 16 in. (40.6 cm.) high by 12 in. (30.5 cm.) wide. Bulk power connectors are mounted on the power tab, a 2.3 in. (5.8 cm.) by 2.2 in. (5.6 cm.) projection on the left side of the midplane. (See Figure 2-5.) Connectors on the front and back of the midplane carry signals between each line card, NP and switch card in the front of the chassis and the corresponding access card in the back of the chassis.
The LightStream switch card, an FRU, provides the interconnection through which line cards and network processors (NPs) in the same LightStream chassis communicate with one another. Communications between NPs and line cards can take place over high-speed switch paths that carry payload traffic between LightStream nodes. In addition, low-speed Test and Control System (TCS) data paths carry control and diagnostic information between the TCS hub on the switch card and the TCS slaves on the NP and line cards.
Two versions of the switch card exist: the Release 1 version and the Release 2 version. Differences between the two are noted as they come up throughout this section. Except as noted, functionality is identical on the two cards.
Switch cards can be inserted in one or both of the dedicated switch card slots on the front of the midplane, slots A and B. A redundant system has two switch cards; a nonredundant system has one. In a redundant system, one switch card is active and the other serves as a hot spare, ready to take over if the active card fails.
Figure 2-7 shows a Release 1 switch card; Figure 2-8 shows a Release 2 switch card.
The switch card has four key functional areas:
Figure 2-9 shows a high-level functional block diagram of the switch card. Each of the functional areas shown in Figure 2-9 is described in the sections that follow.
The concurrent cell switch provides the connection through which NPs and line cards communicate, allowing them to transport cells of data between function cards within a LightStream chassis. The concurrent cell switch has 10 ports, one per function card slot.
The concurrent cell switch on each switch card takes the place of a bus in a conventional computer system. It eliminates the need for high-power drivers for high-speed, high-fanout buses. It provides physical isolation between function card data paths for power-on, nondisruptive servicing, and it provides a very high aggregate bandwidth in the chassis without requiring each function card to accept data at the aggregate rate.
The switch carries cells in fixed length time slots, which are common to all the traffic. All function cards transmit their cells into the switch simultaneously and receive cells from the switch simultaneously.
The decision of which transmitting function card gets a connection to its requested receiving function card is made in the time-slot preceding the actual data transfer. The switch therefore has nearly an entire time slot to make its decision. The switch sends an acknowledgment back to those transmitters whose destination card requests will be fulfilled in the next time slot. The acknowledgment arrives before the end of the requesting time slot, so that the transmitter can begin the data flow as the next time slot begins.
The function cards are connected to the switch by private links. There are three paths between each function card and the switch. One is used to transmit cells from the function card to the switch, and two are used to deliver cells from the switch to the function card. Each of these data paths is eight bits wide and is clocked at 25 MHz, for a raw path bandwidth of 200 Mbps.
The data passing on these links is divided into cells. Each link is unidirectional, but the three data paths between the function card and the switch can all pass cells simultaneously. The double data paths flowing from the switch to the function cards reduce blocking probability so the switch delivers better performance than ordinary "nonblocking" switches. Under typical traffic loads, the concurrent cell switch delivers an average of 160 Mbps of cell payload throughput. This is more than enough to handle the 149.8 Mbps OC-3c SONET payload bandwidth, and sufficient to handle wire-speed FDDI traffic with enough margin to accommodate inefficiencies due to packet fragmentation.
The TCS hub is located on the switch card. It controls the switch card and acts as a communications hub for the system-wide Test and Control System. It provides communication among the TCS slaves, itself, the console, the TCS hub on the redundant switch card if one is present, and the modem.
The switch card provides power for the entire TCS system. The TCS hub can monitor the "DC OK" signal on the bulk power supply.
In a system with two switch cards, the TCS hub on one card is primary and the TCS hub on the other is secondary. The primary TCS hub is not necessarily located on the active switch card. To determine which switch card in a redundant system has the primary hub, look at the TCS SEL LEDs. This LED is lit on the card with the primary TCS hub.
Via the local console and modem ports, both TCS hubs can provide some access to function cards. For example, you can display the status of a function card from either hub. However, if you need to establish a console connection to a card—to use CLI, for example, or to run diagnostics—you must connect to the card via the console or modem port of the switch card with the primary TCS hub.
If the primary hub fails to poll the secondary hub within a specified time period, the secondary hub takes over and becomes primary. In addition, you can force the secondary hub to become primary, as described in the LightStream 2020 Administration Guide. Forcing the hubs to switch roles may be necessary, for example, if you need to remove a switch card from the chassis.
More information on the TCS can be found in the "Test and Control System" section.
On the Release 1 switch card, there are two power supplies. One supplies TCS power for the entire LightStream unit, and the other supplies power to the concurrent cell switch and clock circuitry. On the Release 2 switch card, a single power supply serves both purposes.
The switch card converts internally distributed bulk power to the voltages it needs to operate its switch circuitry and generates power for the TCS system on all the function cards.
The switch card generates a 25 MHz clock signal for the system and distributes it to all the function cards.
The Release 2 switch card has network synchronization logic that allows all LightStream nodes in a network to be referenced from the same time base. The BITS CLK port and the BITS OK LED, which are not functional in Release 2.0, will be used for network synchronization in a future release. (BITS is building-integrated time source, a type of T1 line that supports only clock signals.) This will be useful for constant bit rate applications.
A LightStream node's optional second switch card is used for redundancy rather than loadsharing. The two cards are configured identically. One switch card is active while the other is available as a hot spare. If a failure occurs in the active switch card, cutover to the backup card happens automatically. The active card is always the card in slot A, unless that card is absent, failed, or not powered, or an operator has forced a cutover.
In Release 1 switch cards, cutover—when an active switch card goes out of service and the backup card becomes active—is an unplanned event caused by a problem on the active card. (It may also be caused by an operator's reset or removal of the active card.) Cutover in Release 1 cards causes the system to reboot and involves some loss of data.
In Release 2 switch cards, cutover from one card to the other can happen in the following ways:
A planned cutover is initiated by you, and involves no loss of data. See the LightStream 2020 Operations Guide for instructions on how to perform a planned switch card cutover.
An unplanned cutover occurs when a hardware problem renders the active switch card inoperable. Because the system is not able to prepare for it, an unplanned cutover involves some data loss. It also causes any low-speed and medium-speed line cards in the chassis to reboot. In certain circumstances, an unplanned cutover can cause the system to reboot.
If you mix Release 1 and Release 2 switch cards in the same chassis, the Release 2 card will behave like a Release 1 card. (That is, planned cutovers will not be possible. Any cutover involving Release 1 and Release 2 switch cards, whether caused by operator action or initiated by the system itself, will cause the system to reboot.)
The switch card measures 14.4 in. (36.6 cm.) high by 11 in. (27.9 cm.) deep. (See Figure 2-7.) The switch card weighs 3.4 pounds (1.5 kg.).
The LEDs on the switch card are described in Table 2-4.
There is a recessed reset push-button on the card's front bulkhead. Pushing it causes a full reset of the card.
Release 2 switch cards have a BITS OK LED and a BITS CLK port on the front bulkhead that are not used in Release 2.0.
At the back of the chassis, behind each switch card, is a console/modem assembly consisting of a bulkhead with two connectors mounted on it. The connectors are labeled CNSL and MODEM. The console/modem assembly connects to the midplane via a ribbon cable. Its ports can be used to connect a terminal and modem to the TCS hub on the switch card; from there you can connect to the NP, or to any other function card.
The NP card, an FRU, is the LightStream system's primary computing and storage resource.
In conjunction with the line cards, network management systems, and NPs in other LightStream nodes, the NP performs system-level functions for the LightStream node. These functions include virtual circuit management, network management, maintenance of routing databases, distribution of routing information, and file system management.
Each NP is paired with an NP access card, which resides directly behind the NP in the chassis. The access card provides an Ethernet port that may be connected to carry network management traffic.
Associated with each NP is a 120-Mbyte hard disk drive and a 3.5-inch floppy disk drive. The NP and the disk assembly are connected by a ribbon cable. See "Disk Assembly" section for more information on the disk assembly.
Figure 2-10 shows front, rear, and component side views of the NP.
The Network Processor (NP) is a single-card microcomputer with an interface to the concurrent cell switch. Each NP uses a Motorola 68040 CPU and has 32 Mbytes of DRAM. In addition, the NP has an Ethernet interface to carry network management traffic to and from a network management station or other LightStream nodes, and a SCSI interface for the NP's local hard disk and floppy drive. The NP also has a battery-backed clock/calendar, several counter/timers for performance measurements and event logging, and a TCS slave. Figure 2-11 is a functional block diagram of an NP.
The components in Figure 2-11 are described below.
Note In Release 1, NPs had 16 Mbytes of memory. 16-Mbyte NPs are not capable of running Release 2 software. If you have Release 1 NPs in your network, you must upgrade them before installing Release 2.0.
A LightStream node's optional second NP card serves as a backup. The two cards are configured exactly alike. One NP operates as primary while the other is available as a hot spare. When a failure is detected in the primary NP or in its associated disk assembly, switchover to the backup card happens automatically.
NPs measure 14.4 in. (36.6 cm.) high by 11 in. (27.9 cm.) deep, as shown in Figure 2-10.
Signals are carried from the NP to both the switch card and the NP access card by three 96-pin DIN connectors on the midplane, the NP itself, and the access card.
The LEDs on the NP are described in Table 2-5.
There is a recessed reset push-button on the card's front bulk-head. Pressing it causes a full reset of the card.
Note The reset button does not bring the NP down gracefully. Particularly in a system that's operating in an active network, you should reboot the NP to bring it down gracefully, as described in "Performing an Orderly Shutdown" section of this manual.
Associated with each NP in a LightStream chassis is a disk assembly (see Figure 2-12). The disk assembly is an FRU; it includes a 120-Mbyte hard disk drive, a 3.5-inch floppy disk drive, and a power supply.
The hard disk stores the node's system and application software, hardware diagnostics, and local configuration files.
The lower disk assembly is connected to the NP in slot 1; the upper disk assembly, if present, is connected to the NP in slot 2.
For communicating with other systems, the LightStream 2020 uses four types of line cards:
Line cards allow LightStream systems to connect to various other networks and systems, including local area networks (LANs), wide area networks (WANs), metropolitan area networks (MANs), directly connected hosts, and other LightStream systems.
Line cards can be divided into two categories:
In Release 2.0, packet line cards support only edge interfaces. Otherwise, you can configure any line card to be either a trunk or an edge card.
A line card reformats each incoming unit of data as needed, makes the necessary low level routing and congestion avoidance decisions, and forwards the data toward its destination. For each outgoing unit of data, a line card checks for errors, queues the data for transmission through the appropriate interface port, supplies the buffering needed to match the rate between the concurrent cell switch and the interface port, and handles congestion events. Edge cards that handle packets or continuous data streams must also segment incoming data into cells and reassemble outgoing cells into the format required by the external interface.
Since line cards must be capable of handling high data rates and the processing requirements are relatively simple, all routine packet and cell forwarding operations are handled by hardware and firmware. Each line card also includes a line card control processor that handles the more complex tasks that must be executed in a few tens of milliseconds or less. The line card control processor acts as an agent for the NP when an NP needs to query or change the state of a line card. To gather statistics from a line card, for example, an NP sends a message to the line card control processor, and the line card control processor reads the appropriate hardware registers and returns a result to the NP.
Low-speed and packet edge cards accept packets from up to eight lines, chop them into cells, and inject the resulting stream of cells into the switch. In addition, they receive cells from the switch, repackage the data as packets, and send them out of the network. Edge LSCs and edge PLCs also enforce LightStream's backward congestion control scheme by discarding traffic on channels that send faster than their committed and excess rates allow. The cards smooth all datagram traffic that is injected into the switch. Isochronous traffic is injected into the switch on a fixed schedule, to avoid statistical effects that result in unpredictable delays.
Medium-speed edge cards accept ATM cells from up to two T3 or E3 lines, update the cell headers, and forward them to the switch. They send cells received from the switch out of the network. MS cards do not enforce traffic shaping.
Cell edge cards accept ATM cells from up to two OC-3c lines, update the cell headers, and forward them to the switch. They send cells received from the switch out of the network.
Trunk cards of all types accept LightStream cells from one to 15 trunk lines and replace their headers with new values for the next hop. The cells are then injected into the switch. Trunk cards also receive cells from the switch and send them on to the lines with no ATM header field replacement.
A LightStream line card has two major logical portions: a line- specific portion and a generic portion. See Figure 2-13.
The line-specific portion attaches to the external media or system and performs the functions required by that system.
The generic portions of line-card logic perform functions that occur regardless of the line type. These are the functions that pertain to transferring packets through the LightStream network. These functions are summarized below.
Note Because MSCs and CLCs deal only with ATM cells, they do not contain the Segmentation and Reassembly blocks. MSCs also lack Recognition blocks, while CLCs have simple Recognition logic for parsing cell headers.
Each line card also has a TCS slave, which provides initialization and bootstrap for the line card. It performs local monitoring and power control functions required to support the mission critical features of the LightStream node. The TCS slave communicates with the TCS hub through the midplane.
All line cards measure 14.4 in. (36.6 cm.) high by 11 in. (27.9 cm.) deep. (See Figure 2-14 and Figure 2-15.)
Signals are carried from the line cards to both the switch card and the access cards for the NP by three 96-pin DIN connectors on the midplane, the line card, and the access card. The center connector connects the line card to the switch card and the upper and lower connectors connect the line card to the access card.
Refer to Table 2-6 and Table 2-7 for descriptions of the LEDs on the line cards.
There is a recessed reset push-button on each line card's front bulkhead. Pressing it causes the TCS to reset the line card.
This section describes low-speed line cards. See Figure 2-14 for an illustration.
A low-speed line card configured as an edge card provides eight full-duplex serial lines. The card supports frame forwarding and frame relay interfaces, and a single card can have any mix of frame relay and frame forwarding ports. Physical line interfaces include V.35, X.21 and RS-449. Each port on a low-speed card can operate at speeds up to 3.584 Mbps, although the ports are limited to a maximum aggregate speed of 6 Mbps per line card (regardless of where clock is sourced).
The LS edge card is capable of providing clock in DCE mode. The card can source clock at the following speeds: 56K, 64K, 128K, 192K, 256K, 384K, 448K, 512K, 768K, 896K, 1.344M, 1.536M, 1.792M, 2.688M, 3.584M, 4.000M, and 5.376M.
Each LS edge card requires a low-speed access card. Separate fantails provide V.35, RS-449, or X.21 interfaces.
Access to T1 (DS1) or E1 lines is accomplished through the use of external data service units and channel service units (DSU/CSUs) connected to LightStream fantails over V.35, RS-449 or X.21 serial interfaces. DSU/CSUs are used primarily for long-distance connections with leased lines. A DSU/CSU is not generally necessary for connection to a device in the same building. It is the responsibility of the customer to provide DSU/CSUs; they are not available from LightStream Corp.
Support of fractional T1/E1 services is provided by allowing line speed settings in selected increments of 56 Kbps and 64 Kbps up to a maximum of T1 and E1 rates supported by the external DSU/CSU.
Each line on the LS line card includes a separate interface to control the external DSU/CSU. The interface allows setting loopbacks and carrier channel access configuration in the case of fractional T1. In addition, the interface is used to query traffic and error statistics as well as alarm conditions for local and remote carrier equipment. The control interface is supported by 9-pin male connectors for each port on the V.35 and RS-449 fantails. (X.21 lines do not require DSU/CSU control ports.)
The LSC configured as a trunk card uses the same hardware as the LS edge card, but different software. The number of ports, physical interfaces, line speeds, external DSU/CSU control ports, and access cards are identical to those for the LS edge card. Instead of handling frame relay and frame forwarding traffic, the LS trunk card carries ATM cells embedded in HDLC frames.
This section describes medium-speed line cards. See Figure 2-15 for an illustration.
The MSC configured as a trunk card provides two full duplex lines, each of which can operate at DS3/T3 (45 Mbps) or E3 (34 Mbps) speeds in each direction. ATM cells are carried over these lines.
A single access card for each MS trunk card supports two ports. (No fantails are needed for MS trunk ports.) Three MS access cards are available; one supports DS3/T3 lines and the other two support E3 lines.
The MSC configured as an edge card uses the same hardware as the MS trunk card, described above, but uses different software. The number of ports, physical interfaces, VCCs, line speeds, and access cards are identical to those for the MS trunk card. Instead of handling ATM cell traffic between LightStream nodes, the MS edge card handles ATM UNI traffic between the LightStream network and other ATM devices.
The packet line card (PLC) supports up to 8 full duplex ports with over 100 Mbps of continuous aggregate packet bandwidth. (For future expansion, the card is designed to support up to 15 ports.)
The PLC supports the following access cards:
In Release 2.0, the PLC supports only edge interfaces.
The PLC's control processor is a 25 MHz Motorola 68EC030 microprocessor. Associated with the control processor are 4 Mbytes of DRAM and 1 Mbyte of Flash EPROM that stores bootstrap and POST code.
The PLC supports internetworking functions on the LightStream switch. An important mechanism in this area is the PLC's ability to set up virtual circuits (VCs) on the fly when it encounters streams of traffic not associated with previously known VCs. The PLC's from-line unit (FLU) attempts to recognize incoming traffic as belonging to an established VC. When no match is detected, it buffers the incoming packets of unrecognized traffic and sends the NP the information it needs to set up the VC. Once the setup is complete, the FLU will recognize any subsequent packets for this flow and packet processing proceeds as usual.
The packet line card is shown in Figure 2-16.
The cell line card (CLC) supports up to 2 full duplex ports with over 357K cells per second aggregate bandwidth and can handle bursts up to 893K cells per second. (For future expansion, the card is designed to support up to 15 ports.)
The CLC supports the OC-3c access cards. It supports both trunk and edge interfaces; it can support either one trunk port or two edge ports.
The CLC's control processor is a 25 MHz Motorola 68EC030 microprocessor. Associated with the control processor are 4 Mbytes of DRAM and 1 Mbyte of Flash EPROM that stores bootstrap and POST code.
The cell line card is shown in Figure 2-17.
A LightStream chassis contains one access card per function card. The access cards, which are FRUs, provide the physical interface to which other devices can be connected. Access cards are accessible from the rear of the chassis. Each access card connects to its function card through the midplane.
If you remove or power down an access card, service is disrupted on the associated function card.
Table 2-1 lists the access cards and shows which function card is required for each one.
Table 2-1 Access Cards and Corresponding Function Cards
| Access Card | Function Card |
|---|---|
(In addition, console/modem cable assemblies provide connectors for each switch card.)
Each access card measures 14.4 in. (36.6 cm.) high by 7 in. (17.9 cm.) deep.
The V.35/RS-449/X.21 low-speed access card (LSAC) operates in conjunction with the low-speed line card. It can support up to eight I/O ports. To accommodate those ports, the card has two 100-pin connectors. These connectors can be attached to interface-specific fantails (V.35, RS-449, or X.21) that hold the connectors for the I/O ports. (See "Fantails" section for more information on fantails.)
In conjunction with external DSU/CSUs, low-speed access card ports can be connected to DS1 (T1) or E1 lines.
The low-speed access card has a group of user-settable jumpers that allow you to select the card's interface type (V.35 or RS-449/X.21). For instructions on setting the interface jumpers, see "Setting Interface Jumpers on the LS Access Card" section.
Figure 2-18 shows front, rear and component side views of the low-speed access card.
T3 medium-speed access cards (which are labeled MSAC) operate in conjunction with medium-speed line cards. T3 access cards support up to two ports each. Each T3 access card has four 75-ohm BNC coaxial jacks that provide DS3-compliant connections. Each port consists of two connectors: one for the receive channel and one for the transmit channel.
The LEDs on the T3 access card are described on Table 2-10.
Each access card contains internal DSU/CSUs that can connect directly to a leased T3 line. T3 access card ports can also connect LightStream nodes directly at distances up to 900 feet (274 meters).
Figure 2-19 shows front, rear and component side views of the T3 access card.
E3 medium-speed access cards (which are labeled MSAC) operate in conjunction with medium-speed line cards. E3 access cards support up to two ports each. Each E3 access card has four 75-ohm BNC coaxial jacks that provide G.703-compliant connections. Each port consists of two connectors: one for the receive channel and one for the transmit channel. The LEDs on the E3 access card are described in Table 2-10.
Each access card contains internal DSU/CSUs that can connect directly to an E3 line. E3 access card ports can also connect LightStream nodes directly at distances up to 1900 feet (579 meters).
Two versions of the E3 access card are offered to support different methods of framing:
Figure 2-20 shows front, rear and component side views of the E3 access card.
The Ethernet access card (EAC) operates in conjunction with a packet line card. Each Ethernet access card supports up to eight IEEE 802.3 Ethernet ports. The ports are of two types:
Although it supports eight ports, the access card has 10 I/O connectors. Ports 1 through 6 are female RJ-45 connectors that support twisted pair only. Ports 0 and 7 each have two connectors: one female RJ-45 for twisted pair connections and one female DB-15 for AUI (attachment unit interface) connections. Only one of the two connectors for each port may be used at a time.
A line attached to a twisted pair port on the EAC must be connected to a 10Base-T hub or concentrator. As shown in Figure 2-21, a line attached to an AUI port must be connected to a 10Base2 or 10Base5 transceiver, or medium attachment unit (MAU). The EAC's LEDs are described in Table 2-11. Figure 2-22 shows front, rear and component side views of the card.
The FDDI access card (FAC) operates in conjunction with a packet line card. It allows the LightStream 2020 to connect to any network compliant with the ANSI standards for FDDI.
Figure 2-23 shows front, rear and component side views of the FDDI access card. The LEDs on the FDDI access card are described in Table 2-12.
Each FDDI access card supports two multimode FDDI ports. Each port supports a single-MAC station that can function in either dual-attached mode or dual-homed mode. The station management task (SMT) facility adheres to SMT version 7.3 as defined in ANSI X3T9.5.
Each port consists of two media interface connectors (MIC), keyed and labelled as MIC A and MIC B. In addition, one 6-pin DIN connector per port is provided for an optional optical bypass cable. This connector lets you attach an external optical bypass relay to provide additional fault tolerance in the dual ring. The FAC senses the presence of the optical bypass relay and switches it in or out at the appropriate times.
The power loss budget for LightStream FDDI connections is 11 dB. Higher loss, which could result from passing the signal through overly long cables or through too many connectors, may cause signal attenuation and data loss.
We recommend that you attach a protective cover to any FDDI port that will be unconnected for more than a brief period. (Covers are shipped with each FDDI card.) The cover protects the optical media from dust and damage, which can cause signal attenuation and data errors.
The FAC has two CAM (content-addressable memory) chips that filter out incoming packets that are addressed to stations on the same FDDI ring as the LightStream FDDI interface (and hence do not need to be bridged). The CAMs relieve the packet line card of much of the filtering load.
OC-3c access cards operate in conjunction with cell line cards. Four versions of the OC-3c access card are available, with the options shown in Table 2-2. The cards are labelled OC3AC MM (for multimode) or OC3AC SM (for single mode). All versions of the card operate at a wavelength of 1300 nanometers.
Table 2-2 OC-3c Access Card Options
| No.of ports | Fiber Type | Connector Type | Transmit Power | Receive Power |
|---|---|---|---|---|
A one-port OC-3c access card can run at full duplex at full line speed. A two-port card handles cells as fast as the switch card can deliver and receive them. The maximum sustained rate is about 1.1 OC-3c's total. Both ports can simultaneously receive bursts at full OC-3c speed, but the TSU cell buffers eventually fill, and TSU flow control forces the card to drop cells at the receive ports.
Figure 2-24 and Figure 2-25 show 2-port multimode and single mode OC-3c access cards, respectively. The LEDs on OC-3c access cards are described on Table 2-13.
The power loss budgets for OC-3c connections are as follows:
Higher loss, which could result from passing the signal through overly long cables or through too many connectors, may cause signal attenuation and data loss.
Each port on the single mode version of the OC-3c access card has a toggle switch and a green LED labelled Safe. The switch enables and disables the port's transmit laser, which can cause eye damage if left enabled when the port is unconnected. See "Turning Off the Transmit Laser on the OC-3c Access Card" section if you need instructions on turning the transmit laser on or off.
| Warning Do not look directly into the connectors on a single mode OC-3c access card whose Safe LED is turned off. The transmit laser can damage your eyes. |
(Multimode ports are not dangerous, and therefore do not have disable switches.)
We recommend that you attach a protective cover to any OC-3c port that will be unconnected for more than a brief period. (Covers are shipped with each OC-3c card.) The cover protects the optical media from dust and damage, which can cause signal attenuation and data errors.
The NP access card supports one Ethernet port and a pair of serial ports. The Ethernet port can be used to connect the NP to an Ethernet for purposes of managing the LightStream system. The two serial ports are used for module testing and debugging.
Figure 2-26 shows front, rear and component side views of the NP access card.
Each low-speed interface module (line card/access card pair) supports up to eight ports. The necessary connectors are provided by fantail devices, shown in Figure 2-27. Fantails, which are FRUs, provide connectors for four to eight ports each. Up to two fantails per low-speed interface module may be required.
Three types of fantail are available:
LightStream fantails measure 1.75 in. (1 rack unit, or 4.5 cm.) high by 19 in. (48.3 cm.) wide, and weigh 2 lb. (0.9 kg.). They are designed to fit standard 19-inch equipment racks.
Special 100-pin cables, supplied by LightStream Corp., are used to connect fantails to low-speed access cards (LSACs). To connect a V.35 or RS-449 fantail to its access card, one cable is required. To connect an X.21 fantail to its LSAC, you can use one or two cables, depending on the number of ports you wish to use. Each of the connectors on the back of the X.21 fantail (see Figure 2-27) serves four ports on the front of the fantail. (The connector on the left serves ports 0 - 3; the connector on the right serves ports 4 - 7.) If you wish to use up to four ports on the X.21 fantail, you can connect it to the LSAC with a single cable. If you wish to use 5 or more ports, you must use two cables.
In addition to the four port connectors, each V.35 and RS-449 fantail has four 9-pin male D-type RS-232 connectors for DSU/CSU control ports (also known as craft ports). (X.21 fantails do not have DSU/CSU connectors.) If a port's DSU/CSU control port is connected to an external DSU/CSU device, you can use the csumon utility to set up and monitor the DSU/CSU from the LightStream 2020. See the LightStream 2020 Operations Guide for more information on csumon.
Using switches on the X.21 fantail, each X.21 port can be set to either DTE or DCE. The connectors on the fantail are female, the standard for DCE. If you set an X.21 port to be a DTE, you must attach a 15-pin male-to-male gender converter to change the connector on the fantail from female to male.
The X.21 cable available from LightStream can be used for both DTE and DCE X.21 ports. See the LightStream 2020 Site Planning and Cabling Guide for information on cables.
Figure 2-28 shows how fantails connect to the LS access card.
There are a number of LEDs on the bulkheads of many cards in a LightStream switch. They serve several purposes:
The switch card, NP and line card LEDs are visible from the front of the LightStream chassis. The LEDs on the access cards are visible from the rear of the chassis.
The fault (FLT) LED on a line card, NP, or switch card may turn on for several reasons, which are described in the Table 2-3 below.
Table 2-3 Causes of Lit Fault LEDs
| Cause of Lit FLT LED | Confirming the Cause | What to Do About It |
|---|---|---|
Use show tcs <slot#> command in CLI. If POST field says Failed, see column at right. |
See "Hardware Troubleshooting" section for instructions on running diagnostics on the card. (You may want to bring up the rest of the system first.) |
|
Use show tcs <slot#> command in CLI. Current temperature readings and maximums are listed in Slot State section of display, near bottom. If temp reading exceeds warning or shutdown temp, see column at right. |
Check blowers (see "Troubleshooting Blowers" section) and make sure air flow into, through and away from chassis is unrestricted. Note that leaving chassis open can cause temp problems. To ensure proper air flow, make sure all components, cards, and bulkhead filler panels are firmly screwed in place. |
|
Use show tcs <slot#> command in CLI. Voltage readings are listed in Slot Voltage section of display, near bottom. If any voltage is outside the listed normal range, see column at right. |
Call your support representative for instructions on margining the voltage. |
|
Use show tcs <slot#> command in CLI. If Application field says Disabled, see column at right. |
Use the CLI command set card <slot#> active to enable the card. |
|
Function card and access card in this slot are not compatible |
Check cards in slot at front and rear for mismatches. (Mismatched cards also fail to power up.) |
Ensure that function card and access card in each slot are compatible. Refer to Table 2-1 for compatibility. |
Wait 7 to 8 minutes. When flash load is complete, FLT LED goes off. |
This section describes the LEDs on all LightStream cards.
Table 2-4 LEDs on the Switch Card
Table 2-6 LEDs on the Low-Speed Line Card
Table 2-7 LEDs on the Medium-Speed Line Card
Table 2-8 LEDs on the Packet Line Card
Table 2-9 LEDs on the Cell Line Card
Table 2-10 LEDs on the Medium-Speed Access Cards (T3 and E3)
Table 2-11 LEDs on the Ethernet Access Card
Table 2-12 LEDs on the FDDI Access Card
Table 2-13 LEDs on the OC-3C Access Cards (SM and MM)
Most communications between components (cards) within a LightStream node involve the passing of messages through the concurrent cell switch. However, there are some LightStream functions that cannot be performed through the switch, including initialization, low-level control, and nondisruptive servicing (diagnostics and maintenance). LightStream has an integrated Test and Control System (TCS) to perform these functions.
The TCS provides diagnostic and control functions that
To meet these needs, the TCS consists of a single-chip microcomputer on every line card, NP, and switch card in the LightStream node. The microcomputer on line cards and NPs is called a TCS slave: the microcomputer on the switch card is called a TCS hub. Each slave is connected to one hub (or in systems with redundant switch cards, two hubs) by a point-to-point serial link. Messages can flow from slave to hub, from hub to slave, or from slave to slave (using the hub as an intermediary).
Each TCS microcomputer (hub or slaves) stores a copy of its card's vital statistics (for example, serial number, card type), and data needed to initialize and run the card. The job of each TCS chip is to manage the low-level functionality of its card. It supervises such functions as power supply sequencing, logic reset, soft logic loading, loading and monitoring of power-on self tests, and application program loading and startup. It also provides on/off control and voltage margining of the on-card DC-DC converters, handles updates to the card's EEPROM memory, and monitors air temperature.
The TCS provides access to each card in the system for diagnostics and maintenance operations via a local or remote console connection. When a card has been newly installed, for example, you can load and run diagnostics on the card without disturbing the rest of the system.
The LightStream chassis takes in cooling air from the front. The air is drawn up through the chassis and is exhausted from the back and the right side by blower units like the one shown in Figure 2-29.
There are two blowers in each LightStream system, located at the top of the chassis. One blower is accessible from the front and the other is accessible from the rear. Each blower is an FRU. During normal operation, both blowers should be running. If one blower fails, the system can continue to operate; however, the failed blower should be replaced as soon as possible.
Each blower has a green LED that illuminates to indicate that the impeller is spinning at a rate of at least 1500 rotations per minute. On the rear blower, the LED is visible through the blower cover. You must remove the blower cover to see the LED on the front blower.
The blowers have two speeds, and normally run at low speed. They run at high speed for 90 seconds after the system is first powered on, and then slow down. The decrease in speed is audible to anyone standing near the chassis.
In addition to the main air flow through the LightStream chassis, each bulk power tray in an AC-powered system contains its own fans.
The cooling system operates properly only when all cards, bulkheads, filler panels, covers, and components are in place. Removing these items disrupts the flow of air through the chassis. As a result, components may be shut down due to overheating.
In a LightStream switch, a bulk power tray unit converts power from an external source to bulk DC voltage before distributing DC power to the individual function and switch cards. The nominal voltage of the bulk power unit is 48 volts.
There can be one or two power trays in each LightStream chassis; each power tray is an FRU. If there are two power trays, both are connected to a 48-volt rail so that either tray can drive the entire system.
LightStream systems are available with two power options:
Power trays are accessible from the rear of the chassis; they are located to the right of the access cards. The power tray slots are designated A (on top) and B (on the bottom).
Each card in a LightStream switch converts bulk power to its point-of-use voltages. The power converters on each card are controlled separately by the associated on-card TCS slaves. Each TCS slave can turn its converter on and off and voltage-margin the converter. This arrangement allows for a non-disruptive hot-swap capability and aids in fault diagnosis.
The TCS is powered independently from the rest of the system so that it can control power and run margining tests without impairing its own operation. TCS power is distributed from the switch card to all other cards in the chassis.
AC power supplies accept input power over a continuous range from 100VAC to 240VAC and from 50 Hz to 60 Hz. No adjustment or configuration is required. An AC power supply is shown in Figure 2-30.
Each power supply has a green LED, visible through the cover from the rear of the chassis, that comes on when the system is powered up.
Each AC-powered LightStream system has a recessed male power inlet that conforms to IEC standard 320 C20; it requires a power cord with an IEC 320 C19 connector. See the LightStream 2020 Site Planning and Cabling Guide for more information on power cords.
DC-powered LightStream systems accept power over a continuous range from -43VDC to -60VDC. No adjustment or configuration is required. Power from an external -48VDC source is brought into the system by the DC power tray. A DC power tray is shown in Figure 2-31.
The green LED on each DC power tray illuminates to indicate the presence of DC power. The LED, which is mounted on the power tray and is visible from the rear of the chassis, is connected after the circuit breaker and before the isolation diodes. This allows the LED to indicate the presence or absence of power individually for each tray, prior to the or-ing of the power feeds.
DC-powered LightStream systems do not use detachable power cords; they must be permanently wired to a DC power source by qualified service personnel. Systems with the optional second power tray can be wired from a dual power feed. (For more information, refer to the procedure Wiring a DC-Powered System on "Wiring a DC-Powered System" section.)
Each DC power tray has a circuit breaker that turns system power on and off; it can be tripped by an electrical event or operated manually.
| Warning To turn off power in a DC system with two power trays, you must set the circuit breakers on both trays to off. |
The DC power tray is equipped with a circuit breaker alarm that can optionally be connected to an external device such as a light panel. When the circuit breaker is tripped, the alarm is triggered, notifying you that the system is no longer receiving power through that power tray.
The COM (common), NO (normally open), and NC (normally closed) contacts on the DC power tray provide the alarm signal by indicating whether the circuit breaker is open (off/tripped) or closed (on). Table 2-14 summarizes the possible positions of the contacts.
Table 2-14 Circuit Breaker Alarm Conditions
Safety Instructions ² Installing the Switch in a Rack ² Wiring a DC-Powered System ² Installing Fantails ² Attaching Data Cables ² Closing the Chassis ² Powering Up ² Basic Configuration ² Installing Management Software on a Sun
This chapter provides procedures for unpacking a LightStream 2020 enterprise ATM switch, installing it in an equipment rack, installing fantails and cables, powering up the system, and performing basic configuration. It also tells you how to install LightStream management software on a Sun workstation.
Before starting the procedures in this chapter, do the following:
Note For information on installing redundant components in an existing system, see "Installing Redundant Components" section.
| Warning LightStream switches are designed and manufactured to meet accepted safety standards. However, improper use can result in electrical shock, fire hazards, and personal injury. Read all of the following instructions carefully before installation and use. Note and adhere to all Cautions and Warnings. |
Static electricity can damage or degrade electronic components. To avoid damage, observe the following precautions when you touch hardware.
Before you expose circuitry, you, the rack, and the circuit boards must be at the same ground potential to prevent damaging ESD. To connect yourself to ground, use a wrist strap connected to one of the system's grounding jacks, or to the bare metal surface of the system frame.
All spare cards are shipped in reusable antistatic shielding bags. When cards are not installed in the machine, keep them in antistatic bags. Do not remove cards from their bags unless you are grounded. Do not place these bags on exposed electrical contacts, where they can cause short circuits.
If you haven't done so already, unpack the LightStream switch following the steps below.
Step 1 Before moving the shipping container from your loading dock, inspect it for any signs of in-transit damage.
Step 2 Transfer the container to the systems area.
Step 3 Cut the straps and lift the cardboard box off the chassis. Remove the packing material.
Step 4 Inspect all external surfaces for signs of damage. Pay special attention to any areas where you noticed damage to the shipping container.
Step 5 Document any damage noted during the inspections and notify your LightStream vendor.
This section explains how to rack mount a LightStream chassis.
Note For physical stability, when a LightStream chassis is installed in a rack, the combination should comply with UL Standard 1950, Par. 4.1.1, and IEC 950, 4.1.1.
A LightStream chassis takes in cooling air through the bottom of the front panel and exhausts it at the top rear and the right side. (The air vents on the right side can safely be covered by the rack side panels, but should not be otherwise blocked.) To minimize thermal problems, position the chassis such that:
Have the following items on hand before you begin rack installation:
Follow these steps to rack-mount the LightStream chassis:
Step 2 Put on the ESD wrist strap and connect it to a grounding jack. (There are jacks on LightStream's front and rear panels.)
Step 3 To make the chassis lighter, remove the blowers (top front and rear) and power supplies (right rear). Blowers and power supplies are located behind removable covers, shown in Figure 3-1 and Figure 3-2. If your system is fully configured with line cards, you may also want to remove some or all of these cards. Place all removed components in antistatic shielding bags or on antistatic mats.
Step 4 Determine the position in the rack that the LightStream switch will occupy. Then attach the clip nuts from your country kit or rack mounting kit to appropriate places on the rack rails. See Figure 3-1 for screw positions. (If your rack has metric-threaded or nonstandard rails, you may need to provide your own mounting hardware.)
Step 5 Lift the LightStream chassis into the rack.
| Caution Do not use the handles on the disk assemblies to lift the chassis. These handles, shown in Figure 3-1, are not designed to support the system's weight; they will break off under stress. |
Step 6 Using the mounting screws and washers included in your country kit or rack mounting kit, attach the flanges on the front of the chassis to the rack.
Step 7 Replace the blowers, power supplies, boards, and covers that you removed before you lifted the chassis into the rack.
The procedure in this section explains how to wire a DC-powered LightStream switch to a DC power source. This task should be performed by qualified service personnel or a licensed electrician.
This section applies only to systems with the DC power option. If you have a standard AC-powered system, skip to "Installing Fantails" section.
For more information on DC-powered LightStream systems, see "DC-Powered Systems" section and the LightStream 2020 Site Planning and Cabling Guide.
The person who wires the system should have several items on hand:
| Warning This wiring task should be performed only by a licensed electrician or by qualified service personnel. It may expose untrained personnel to hazardous voltages. |
Step 2 Ensure that power to the circuit you will connect to the LightStream system is off.
Step 3 Connect the power wires, using the slot-tipped screwdriver to adjust the terminals. Do not remove the terminal covers at the base of the terminal block.
Step 4 If you plan to connect the alarm circuit, first remove the plastic terminal block cover (see Figure 3-3) and save it.
Step 5 Connect the alarm wires, using the Phillips screwdriver to adjust the terminals.
Step 6 Replace the terminal block cover you removed in step.
Step 7 If the LightStream system has two power trays, repeat this procedure for the second tray.
Step 8 When you turn on the power, check the green power LED on the front of each power tray. If the LED does not light up, check for misconnected wires or problems in your power circuit.
This section explains how to mount and connect LightStream fantails (Figure 3-4), which provide connectors for data cables on low-speed (V.35, X.21 and RS-449) lines.
If your system has no low-speed line cards, skip this section and proceed to "Attaching Data Cables."
Follow the steps below to install LightStream fantails.
Note Before installing fantails, check the interface jumpers on the low-speed access cards. The jumpers on each card must be set to the interface displayed on the fantail(s) for that card. For instructions on setting interface jumpers, see "Setting Interface Jumpers on the LS Access Card" section.
Step 2 Put on the ESD wrist strap and connect it to the grounding jack on the rear of the chassis.
Step 3 Attach the fantail cable (or cables, if you're installing an X.21 fantail) to the back of the fantail and to the corresponding access card in the chassis. (It's easiest to do this now; if you install the fantail first, you have to reach behind it and attach the cable to a connector you can't see.) The cable is reversible; you can connect either end to the fantail. Don't rest the weight of the fantail on the cable.
Step 4 Using a slot-tip screwdriver and the mounting screws and washers provided, attach the fantail to the equipment rack.
Step 5 Label the fantail with the slot number or name of the interface module it's connected to.
Step 6 If you are mounting an X.21 fantail, set the DTE/DCE switches for each port to the desired mode. (See "Configuring X.21 Ports as DTE or DCE" section for complete instructions on configuring X.21 ports as DTEs or DCEs.) If you select a DTE interface, note that you must install a gender converter on each DTE port to change the female connector to male.
Step 7 Repeat this procedure to install additional fantails.
This section tells you how to attach data cables to your LightStream switch.
Step 2 If you have any OC-3c or FDDI cards, remove and save the protective covers on the ports that will be used. Leave any unused ports covered.
Step 3 Connect any available external data cables. (Refer to the LightStream 2020 Site Planning and Cabling Guide for details on data cables and connectors.) If you have any Ethernet cards, note that although there are 10 physical connectors, each card supports only eight ports.
Note For ease of maintenance, arrange your data cables so that only those cables connected to a given access card must be disconnected in order to remove the access card. (In other words, route cables at the back of the chassis in a way that will enable you later to remove any access card without disconnecting cables attached to other access cards or fantails.)
Before powering up, check the front and back of the system to see that all boards, disks, blowers, bulkheads, filler panels, and covers are in place and firmly screwed to the chassis frame. When all these items are in place, they form an enclosure that serves three important functions:
Use the procedure below to turn on a LightStream switch.
Step 2 For AC-powered systems: Flip the power switch located on the rear of the system next to the power inlet.
For DC-powered systems: Flip the power switch located on the power tray panel. If your system has two power trays, you must flip the switches on both trays to turn the system on or off.
When the system powers up, the blowers start running, then TCS powers up the cards and starts the power-on self tests (POST). LEDs indicate the status of the cards and other components, as described in the flow chart in Figure 3-5. The power-up sequence including POST takes 1 minute or less.
Step 3 If the green ready (RDY) LED on each card comes on, proceed to the next section, "Install Modems." If a yellow fault (FLT) LED stays lit on any card (indicating a problem), do one of the following:
This section explains how to attach a terminal to a newly-installed LightStream switch and enter basic configuration information in response to prompts from LightStream software. You must perform basic configuration for each NP in your system.
Note If you have a problem such as a hung system while you're performing basic configuration, you may need to shut the system down and start over. Refer to "Performing an Orderly Shutdown" section for instructions on performing an orderly shutdown.
Before you start the procedures, collect the following information:
Details on the required information are presented in the subsections that follow.
You must create a password for each of the four default login accounts on the switch—root, oper, npadmin and fldsup. (See the LightStream 2020 Administration Guide for more information on the default login accounts.)
A password must be at least six characters long. It can be as long as you wish, but only the first eight characters are used. Any combination of characters is acceptable, including spaces.
You must assign a host name to each LightStream network node. Typically, the host name might be chosen to remind you of the node's location, either geographically (e.g. Tokyo2) or within the functional structure of the enterprise (e.g. mfg3 for a manufacturing function).
The name can be made up of any combination of letters and numbers, up to 32 characters long, but it must not begin with a number. Thus, Pensacola23 is a valid host name, but 23Pensacola is not a valid name (it begins with a number) and Pensacola.23 is not a valid name (it contains a character that is neither a letter nor a number).
For each node, you must provide from one to four IP addresses and the associated network masks, as follows:
Nodes in a LightStream network use their primary NP addresses to communicate network management traffic to one another.
Note All NP addresses within the same LightStream network must have the same network number, and each must have a unique host ID.
The subnet mask specifies which portion of the IP address is the network number and which portion is the host ID. This mask is the same for all nodes on a given LightStream network.
If a node has a backup NP, then it uses its primary and secondary NP addresses to pass network management traffic between the two NPs within the node. The primary NP address is used by whichever NP is active. All NP addresses within the same LightStream network must have the same network number, and each must have a unique host ID.
An Ethernet LAN may be attached to the NP for communicating management traffic between the node and a network management system (NMS). If an Ethernet LAN is connected to the NP, then the NP's Ethernet IP address must be configured. If there is a backup NP, then both NPs must be attached to the same Ethernet segment. The NP's Ethernet IP address is used by whichever NP is primary.
Note This IP address has the network number for the attached Ethernet LAN (which must be different from the network number of the LightStream network) plus a host number that is assigned by the network administrator of the Ethernet LAN.
The subnet mask for the NP's Ethernet address specifies which portion of the IP address is the network number and which portion is the host ID. This mask is the same for all nodes on the Ethernet that is attached to the primary NP. You obtain it from the administrator of that Ethernet LAN.
If an Ethernet LAN is attached to the primary NP, but the NMS is not directly connected to that LAN, a router on the Ethernet LAN may be configured as the default router. The default router on a LightStream node provides a route from the node to the network management system (NMS). This IP address has the network number for the attached Ethernet LAN (which must be different from the network number of the LightStream network) plus a host number that is assigned by the network administrator of the Ethernet LAN.
If you plan to handle just one physical LightStream network under your network ID number, and the LightStream network is a class C network, then record 255.255.255.0 as the subnet mask. (The mask is 255.255.0.0 for a class B network with no subnetting, and 255.0.0.0 for a class A network with no subnetting.)
Note Network management can also be done via an Ethernet LAN that is connected to an ordinary Ethernet data port on the LightStream node (that is, an Ethernet access card port). The NMS must be directly attached to that Ethernet LAN. In this case, do not configure the NP's Ethernet address or default router address.
For more information on management addresses, see the LightStream 2020 Configuration Guide. If you do not understand IP addresses, if you do not understand subnetting, or if you do not know what the class of your LightStream network is, refer to Appendix B.
For each trunk port you configure, you need to know:
If you need more information on trunk port configuration, refer to the LightStream 2020 Configuration Guide.
The procedures in this section use the following commands:
Follow this procedure to connect a terminal to your switch. Go on to the procedure that follows to establish a connection to the network processor (NP).
Note If your system has two switch cards, you must connect to the console port of the one that holds the primary TCS hub. To determine which card has the primary hub, look for a green LED labelled TCS SEL on the front bulkhead of each switch card. The TCS SEL LED is lit on the switch card with the primary hub.
Switch card slots on the front of the chassis are labeled A and B, as are the slots that hold the console and modem ports on the back of the chassis. If the primary TCS hub is on the switch card in slot A, connect to the console port in rear slot A. If the primary hub is on switch card B, connect to console port B.
Step 2 Set up the terminal as described in Table 3-1 below.
Table 3-1 Terminal Settings
Step 3 If you can connect at 9600 baud, skip the rest of this procedure and go on to Connecting to an NP, below. If you don't have 9600 baud but you do have 1200 baud, 2400 baud, or 19,200 baud, press [Break] three times as soon as you connect. This activates the baud rate selection mechanism.
Step 4 Once baud rate selection is activated, the port's baud rate changes every time you press [Break] again. Press [Break] slowly until you can read "OK" on your screen. (At each new baud rate, the system attempts to display "OK" on your screen. Your display becomes legible when the terminal and port baud rates match.)
Follow this procedure to establish a terminal connection to the network processor (NP) in you LightStream switch. (This procedure assumes that you have already connected a terminal to the switch, as described the previous procedure.)
Step 2 Use the connect <slot#> command to connect to the NP that you want to configure. This example assumes that you're connecting to the NP in slot 1:
Step 3 When you connect, part or all of the following countdown appears on your screen. Do not press [Return]; allow the system to boot.
The screen displays for the boot sequence are shown in "Entering Configuration Data" section.
In the procedure that follows, Entering Configuration Data, two scripts that prompt you for basic configuration information are automatically invoked. If you make a mistake in entering any of the information for which the scripts prompt you, you can run them again separately. Just type the name of the script you want to run (see below) at the bash# or single-user$ prompt. Note that these scripts are intended for use only during installation.
When you run them from the command line, the scripts behave very much as they do in the procedure. One difference is that setsnmpconfig checks for the presence of configuration files (these files will not be present during a typical installation of a new switch). If the system finds configuration files, it asks if you want to delete them:
| Caution If you answer y (yes) to this query, the system overwrites the existing configuration files for this node; their contents are lost. |
If configuration files are present and you choose not to delete them, the setsnmpconfig script cannot continue; it exits and returns you to the command line.
If no configuration files are present, or if they are present and you choose to delete them, the script prompts you for network management information, as shown in the procedure below.
In this procedure, you are prompted to enter basic configuration information such as IP addresses and login passwords. (The information you must enter is listed in "Required Information" section.) This procedure assumes that you have already started booting, as previously described. The boot initiates the scripts that prompt you for configuration information.
Note If there's a problem with your system's hard disk or with the software loaded on it, you'll see an error message instead of the display shown below in step.
Step 2 The system prompts you to enter time and date information:
(The second Enter date prompt is for confirmation.)
Note If your switch contains two NPs, ensure that their clocks agree to within one minute. You can do this by using a single reliable source (e.g. a wristwatch) to set the time for both NPs. (If the clocks differ by more than a minute, the software that synchronizes files between the two NPs may have problems.)_(_IREFOBJ:4669_) _
Step 3 You are prompted to enter passwords for the switch's four default login accounts, as shown below. For each account, enter y, then enter the password twice as prompted.
Step 4 Next, the system prompts you for network management information. Enter the host name for this switch, the IP address and the subnet mask for the active NP in the chassis, as shown in the example below. Note that the IP address and subnet mask shown here are samples; you must supply actual addresses.
Note In a redundant system, you will perform this procedure twice—once for each NP. Make sure you enter exactly the same information for both NPs. Do not reverse the active and secondary IP addresses on the second NP. These addresses are assigned to the entire chassis, and not to individual NPs. If you do not enter the same addresses on both NPs, your system will not function.
Step 5 The system asks if this switch has a backup NP:
If you answer n at this point, go on to the next step. If you answer y, you are prompted to enter an address for your backup NP. Note that the IP address shown here is a sample; you must supply the actual address.
Step 6 The following questions are about the NP's Ethernet connection and default router. If you answer n to any question shown below, skip from there to the next step. Note that the Ethernet and default router addresses shown here are samples; you must supply actual addresses.
Step 7 The system displays a summary of the information you have just entered. If the information is correct, answer y at the prompt and skip to the next step. If you want to change something, answer n and return to step; you will be prompted to re-enter all the information from that point.
Step 8 When you confirm that the chassis information you've entered is correct, the system prompts you to configure a trunk port, as shown in the example below. (The trunk port will be used to load a full configuration over the network.)
As with the chassis information, if you answer n to the confirmation prompt, you will be prompted to enter all the trunk information over again. If you answer y, you will be prompted to configure another trunk:
Step 9 When you have configured all the trunks you need to load full configurations throughout the network, answer n to the prompt about configuring additional trunks. The system now reports that it is creating a minimum configuration, loading the line cards, starting the switch software, and starting the neighborhood discovery process. Then the login prompt appears.
Step 10 You have completed basic configuration for this NP. If you're installing a new switch with two NPs, go back to "Connecting to an NP" section. Repeat the procedures from that point to configure the second NP.
When you've completed basic configuration for each NP in your system, read How to Proceed, below.
This section lists things you should do or consider doing after you finish installing a new LightStream switch.
To ensure that the newly installed system is in good working order, you may wish to do one of the following:
Keep a maintenance log for each LightStream switch. At a minimum, the log should list the following information:
You may also want to record unusual behavior. The maintenance log is an essential tool in identifying and correcting chronic or hard-to-diagnose problems.
We recommend that you obtain and install a modem for each switch card in the chassis. In the event that a problem isolates a LightStream node from the rest of the network, the modem may be your only means of communicating with the node. The modem connects to the modem port on the console/modem assembly at the back of the LightStream chassis, using the modem cable described in the LightStream 2020 Site Planning and Cabling Guide. Modems attached to LightStream nodes must be Hayes-compatible and capable of operating at 2400 baud. For information on LightStream's default modem settings and how to change them, see the LightStream 2020 Administration Guide.
You must install LightStream's CLI, monitor, configuration and private MIB software on the Sun workstation you will use to manage your LightStream network. The installation procedure is in "Installing Management Software on A Sun" section.
The LightStream 2020 Administration Guide contains procedures and information about options that let you tailor your network environment in various ways. (You can enable the security mechanism that prevents unauthorized network access, change the default SNMP community names, and change the default trap delivery addresses, among other things.) In the LightStream 2020 Administration Guide, read the "Set-Up Procedures" section before you start operating your LightStream network.
Use LightStream's configuration program to create a configuration database for your network and load a configuration onto each node, as described in the LightStream 2020 Configuration Guide.
You can monitor, control and configure your LightStream network from a Sun SPARCstation running StreamView` configuration, CLI, and monitor software, and the LightStream enterprise-specific MIB. The procedures in this section tell you the following:
Two installation procedures are given, as follows:
When you complete the appropriate installation procedure, you will be able to run the StreamView management software on your Sun workstation.
| For information on º | See º |
|---|---|
Note Refer to the LightStream 2020 Site Planning and Cabling Guide for a list of hardware and software requirements the network management workstation must meet.
Follow all the procedures in this subsection if you are installing LightStream management software on a Sun SPARCstation running HP OpenView. In these procedures, we assume that HP OpenView is installed and functioning properly.
This portion of the LightStream software is provided in two pieces called LS-Configure and LS-Monitor. HP OpenView documentation refers to software packages of this kind as "products." Note that the CLI and the LightStream enterprise-specific MIB are packaged with LS-Configure and LS-Monitor.
In this procedure, you use the ovinstall command. The ovinstall programs do the following things:
The configurator and monitor tools will create log files in the /usr/OV/log directory.
Note This directory and the log files in it must be writeable by everyone who will use the LightStream software on the management station.
Step 2 Create a user account called npadmin. The CLI uses the password for this account as the password for its protected mode. (If no npadmin account is present on the workstation, the CLI uses the root password as the CLI protected mode password.)
Step 3 Ensure that /usr/OV/bin is in your path. The installation procedure uses this directory. To display your path, use the command echo $PATH at the SunOS prompt. To set your path in a Bourne shell or a bash shell, use the following command:
To set your path in a csh shell, use the following command:
Step 4 To stop any running OpenView processes, enter the following command (where the initial % represents the prompt):
Step 5 Insert the tape of LightStream software into the Sun's quarter-inch tape drive.
Step 6 In any directory, use the HP OpenView ovinstall command to extract the LS-Configure software from the tape. Here, <tape-drive> may be /dev/rst0, /dev/rst1, or /dev/rst2, depending on which port your tape drive uses. The command takes 5 to 15 minutes to run. It installs the configuration utilities and associated files. For example, you might type:
Note Note: The command above is for a first-time installation of LightStream software. If you are re-installing the software, use this command instead:
Step 7 In any directory, use the HP OpenView ovinstall command to extract the LS-Monitor software from the tape. Here, <tape-drive> may be /dev/rst0, /dev/rst1, or /dev/rst2, depending on which port your tape drive uses. The command takes 5 to 15 minutes to run. It installs the monitor utility and associated files. For example, you might type:
Note Note: The command above is for a first-time installation of LightStream software. If you are re-installing the software, use this command instead:
Note Before starting this procedure, you or someone at your site must load the configurator, the monitor, and the CLI, as described in the procedure in "Installing Management Software Under HP OpenView" section.
This procedure tells you how to set up the environment to run the LightStream management tools on a Sun SPARCstation running HP OpenView.
Note Steps 2 through 5 in this procedure must be completed for each user who will run the LightStream management tools with HP OpenView.
If the entry isn't present, add it.
Step 2 Determine what type of shell each user is using. In an NFS environment using the yellowpages facility, type the following command:
In an environment that does not use the yellowpages facility, type the following command:
The last field of the password entry identifies the shell, as in the following example entry:
Note Note: Steps are given here for the Bourne shell (sh) and the GNU Bourne-Again shell (bash), and for the C shell (csh). Other shells may differ in their details; consult the documentation for the shell.
Step 3 For each user who will run the LightStream management tools, several environment variables must be defined. In each user's home directory, edit the file that the shell reads on login, as shown in the appropriate subprocedure below.
Note Note: To determine the value <pathname> for the XKEYSYMDB variable shown in the following Bourne shell and C shell subprocedures, consult your local Sun system administrator. The file XKeysymDB should be in the subdirectory lib or lib/X11 under the directory containing your X Windows executables. You can use the command find / -name XKeysymDB -print to search for it, but this could take a long time, and could disclose multiple copies. The distinction between upper- and lower-case letters is critical.
For Bourne shells and their derivatives:
You must first determine whether a UIDPATH variable is already set in your login environment. To do so, type the following command:
If the system displays UIDPATH: unbound variable or no message, skip to next step. If the system displays a path, add the following to the .profile or the .bash_profile:
If the system displays UIDPATH: unbound variable or no message in response to echo $UIDPATH, edit the .profile file or the .bash_profile file. Add the following lines to the file:
You have completed this subprocedure. The main procedure continues with Step 4 below.
For C shells and their derivatives:
You must first determine whether a UIDPATH variable is already set in your login environment. To do so, type the following command:
If the system displays the message UIDPATH: Undefined variable, skip to the next step. If the system displays some other message (usually a path), add the following to the .cshrc file:
If the system displays the message UIDPATH: Undefined variable, add this to the .cshrc file:
Step 4 Any user who is logged in during the installation process should exit and log in again. Alternatively, a user can use the command . (dot) or its alias source to activate the new variables in the current execution environment. As an argument, this command requires the name of the file in which you entered the variables. For example, you might type one of the following:
Note Note: In the Bourne shell, only the command . (dot) is available; in the csh, only the command source is available.
Step 5 To the .Xdefaults file in each user's home directory, append the contents of the file /usr/OV/newconfig/xdefaults. (This step gives the LightStream tools access to the screen fonts they need to display properly.) In each user's home directory, type
If you need to revert to the old .Xdefaults file, you'll find the contents in the backup file Xdef.sav.
Step 6 To ensure that the LightStream applications have been installed correctly, type
This program takes less than a minute to run and prints the names of the objects it verifies. (If the verification fails, you'll see a message on the screen. Call your service representative for assistance.)
Step 7 To start OV daemons, enter the following command:
Step 8 To restart HP OpenView, enter the following command:
Note Note: If you wish to put the OpenView process in the background and keep using the window you're currently in, you can instead type:
If you need help, refer to the HP OpenView documentation.
Note Note: LightStream applications inherit the privileges of the user account from which HP OpenView is started. For example, the access permissions for the database file created by the LightStream configurator correspond to the access rights of the user who started HP OpenView with the ovw command.
Step 9 To update variables associated with the SNMP community, do only one of the following:
Use the following field values:
You may also consider setting the polling interval to 1 minute. The default is 5 minutes. The polling interval determines how long it will be before the display indicates changes in the network.
By default, LightStream nodes require the use of the "write" community for SNMP set operations. You may choose to use another name for the community that has read/write privileges, or you may choose to allow SNMP sets from any community. You must configure this in the HP OpenView environment using the xnmsnmpconf tool, or change the files at the LightStream nodes to conform to HP OpenView's behavior. (See the LightStream 2020 Administration Guide for information on setting up SNMP communities in a LightStream network.)
Step 10 LightStream utilities are now available. Select the LightStream menu from the Root window.
Follow the procedures in this subsection to install LightStream management software on a Sun workstation that is not running HP OpenView.
Step 2 Create a user account called npadmin. The CLI uses the password for this account as the password for its protected mode. (If no npadmin account is present on the workstation, the CLI uses the root password as the CLI protected mode password.)
Step 3 Use the following command to change to the root directory:
Step 4 Insert the tape of LightStream software into the Sun's quarter-inch tape drive.
Step 5 Type the following commands in the order shown to extract the files from the tape. The process takes 10 to 20 minutes to complete.
Here, <tape-drive> is, for example, /dev/nrst0, /dev/nrst1, or /dev/nrst2, depending on which port your tape drive uses.
Note It is important to include the letter n before the tape drive designation (i.e. nrst0 for device rst0). The n means "no rewind;" if you omit the n, you will not be able to read from the tape.
This procedure creates the following directory structure:
Note Before starting this procedure, you or someone at your site must load the LightStream software, as described in the procedure in "Installing Management Software Without HP OpenView" section.
This procedure tells you how to set up the environment to run the LightStream management tools on a Sun SPARCstation that is not running HP OpenView.
Note Steps 2 through 5 in this procedure must be completed for each user who will run the LightStream management tools.
If the entry isn't present, add it.
Step 2 Determine what type of shell each user is using. In an NFS environment using the yellowpages facility, type the following command:
In an environment that does not use the yellowpages facility, type the following command:
The last field of the password entry identifies the shell, as in the following example entry:
Note Note: Steps are given here for the Bourne shell (sh) and the GNU Bourne-Again shell (bash), and for the C shell (csh). Other shells may differ in their details; consult the documentation for the shell.
Step 3 For each user who will run the LightStream management tools, several environment variables must be defined. In each user's home directory, edit the file that the shell reads on login, as shown in the appropriate subprocedure below.
Note Note: To determine the value <pathname> for the XKEYSYMDB variable shown in the following Bourne shell and C shell subprocedures, consult your local Sun system administrator. The file XKeysymDB should be in the subdirectory lib or lib/X11 under the directory containing your X Windows executables. You can use the command find / -name XKeysymDB -print to search for it, but this could take a long time, and could disclose multiple copies.
For Bourne shells and their derivatives:
You must first determine whether a UIDPATH variable is already set in your login environment. To do so, type the following command:
If the system displays UIDPATH: unbound variable or no message, skip to the next step. If the system displays a path, add the following to the .profile or the .bash_profile:
If the system displays UIDPATH: unbound variable or no message in response to echo $UIDPATH, edit the .profile file or the .bash_profile file. Add the following lines to the file:
You have completed this subprocedure. The main procedure continues with Step 4 below.
For C shells and their derivatives:
You must determine whether a UIDPATH variable is already set in your login environment. To do so, type the following command (where the initial % represents the prompt):
If the system displays the message UIDPATH: Undefined variable, skip to the next step. If the system displays some other message (usually a path), add this to the .cshrc file:
If the system displays the message UIDPATH: Undefined variable, add this to the .cshrc file:
Step 4 Any user who is logged in during the installation process should exit and log in again. Alternatively, a user can use the command . (dot) or its alias source to activate the new variables in the current execution environment. (In the Bourne shell, only the command . (dot) is available; in the csh, only the command source is available.) As an argument, this command requires the name of the file in which you entered the variables. For example, you might enter any of the following commands:
Step 5 To the .Xdefaults file in each user's home directory, append the contents of the file /usr/LightStream-2.0/templates/xdefaults. (This step gives the LightStream tools access to the screen fonts they need to display properly.) In each user's home directory, type
If you need to revert to the old .Xdefaults file, you'll find the contents in the backup file Xdef.sav.
Step 6 To remove a directory that is created when the LightStream applications run, type the following while logged in as root:
After you modify your environment, the LightStream applications recreate this directory with new information.
Step 7 By default, LightStream nodes require the use of the "write" community for SNMP set operations. You may choose to use another name for your community with read/write privileges, or you may choose to allow SNMP sets from any community.
To configure this in your Sun environment, edit the file /usr/LightStream-2.0/templates/ovsnmp.conf, or change the files at each LightStream node to conform to your Sun's behavior. (See the LightStream 2020 Administration Guide for information on setting up SNMP communities in a LightStream network.) Use a text editor such as emacs or vi to modify the file ovsnmp.conf. The file contains instructions on how to format each entry.
Configuring X.21 Ports as DTE or DCE ² Setting Interface Jumpers on the LS Access Card ² Turning Off the Transmit Laser on the OC-3c Access Card ² Component Configuration
This chapter shows how to set jumpers and switches in LightStream hardware, and explains how many of each major hardware component—NPs, switch cards, line cards, and power supplies—can coexist in a LightStream 2020 enterprise ATM switch.
| Caution Before removing any components from the chassis, read the safety instructions in "Electrostatic Discharge (ESD) Protection" section. If you handle components without taking proper ESD precautions, you can damage the system. |
The X.21 fantail has eight ports, and each can be set to function either as DTE or as DCE. Next to each connector is a pair of slider switches with settings labelled DTE and DCE (see Figure 4-1). The two switches in each pair are linked, so it's impossible to set them to different modes.
Note Changing a port's DTE/DCE setting while it is operating halts the flow of traffic through the port.
To change a port's DTE/DCE setting, do the following:
Step 2 If you're setting the port to DTE, attach a male-to-male gender converter to change the female connector on the fantail to a male connector.
Step 3 Use the LightStream configurator to change the port's configuration to reflect the new DTE/DCE mode. Refer to the LightStream 2020 Configuration Guide for details.
This section describes the user-settable jumpers on LightStream's low-speed access card (LSAC) and shows how to set them. The jumpers allow you to select one of two interface types:
These jumpers are set for you in the factory based on the configuration specified in your system order, so you should not have to change the jumpers unless you change your configuration.
Figure 4-2 shows the location of the 16 sets of interface jumpers on the card, and illustrates how to set them. For V.35, put jumpers on the left and center pins. For RS-449 and X.21, put jumpers on the right and center pins. (The settings are indicated on the card, as shown.)
Each LSAC serves up to eight I/O ports. If you want all eight ports to use the same interface, set all the jumpers the same way. If you prefer, you can set the LSAC to give you four ports of one type and four of another (four V.35 and four X.21, for example). You'll need one fantail of each type.
The interface jumpers are labelled E1 through E8 and E11 through E18. (E9 and E10 are not interface jumpers and are not located near the interface jumpers on the card.) The interface jumpers can be divided functionally into two groups:
(The two connectors on the rear edge of the card are labelled with the numbers of the ports they serve. Each connector can be attached to a fantail that provides four I/O ports.)
Single-mode ports on the OC-3c access card have transmit lasers whose emissions can be dangerous to the eye. When a single-mode port is not being used, we recommend that you turn off its transmit laser. Turning off the laser turns on the port's green Safe LED. (When the LED is on, you know that it's safe to look at the connector for that port.)
| Warning Do not look directly into the connectors on a single mode OC-3c access card whose Safe LED is turned off. The transmit laser can damage your eyes. |
The toggle switch has two positions:
To turn off the laser, move the toggle switch, shown in Figure 4-3. The green Safe LED comes on to tell you the laser is off.
| Caution If you turn off the transmit laser while the port is passing traffic, the flow of traffic will halt. |
Guidelines in this section help you determine how many of each major component (NPs, switch cards, line cards, power supplies) can be installed in a single LightStream chassis. You'll find this information useful if you're considering adding line cards or redundancy to your system, or if you want to rearrange the cards in a chassis.
The number of NPs, switch cards, and bulk power trays installed in a LightStream chassis depends on whether redundancy is desired. A fully redundant system has two NPs (each with its own disk assembly, including a hard disk and floppy drive), two switch cards, and two power trays.
Some LightStream switches are partially redundant; they have redundancy in some subsystems, and not in others. For example, a partially redundant system might have two power trays and two NPs, but only one switch card.
A nonredundant system has only one NP, one switch card, and one power tray.
The two power trays in a redundant system load-share, and if either one fails, the other can power the entire switch. NPs and switch cards do not load-share; only one card of each type is active at any given time. The second NP and switch card serve as hot spares. If an active NP or switch card fails, its backup takes over automatically.
The list below outlines the types of cards that can be installed in each slot in the front of a LightStream chassis. Figure 4-4 shows the slot numbers.
Filler panels are provided to cover empty slots.
Up to 10 I/O access cards and two console/modem assemblies can be installed in the back of a LightStream chassis. The type and placement of cards in the back of the chassis is determined by the cards installed in the front. Behind each NP and line card, an access card of the correct type must be installed. (See Table 2-1 matching access cards to function cards.) If there is a mismatch between the function card and access card in the same slot, the cards will not power up. A console/modem assembly must be installed behind each switch card.
Every LightStream switch has two blowers. (Blowers are located at the top of the chassis; one is accessible from the front, one from the rear.) If one fails, a single blower can, under normal conditions, cool the entire chassis. However, a failed blower should be replaced as soon as possible.
This section outlines the requirements for installing redundant components (switch cards, NP modules, and power trays) in an existing system.
Step 2 Follow the instructions in "Software Installation" section to load software for the new NP.
Step 3 Follow the instructions in "Installing a LightStream Switch" section to perform basic configuration for the new NP.
Step 4 Use the LightStream configurator to add the new NP to the configuration, then load the updated configuration into the node.
To install a second AC power tray, simply insert the new tray into the unoccupied slot at the rear of the chassis. This procedure does not disrupt the operation of the system.
To install a second DC power tray, insert the tray into the unoccupied slot at the rear of the chassis, then follow the DC wiring procedure starting in "Wiring a DC-Powered System" section. This procedure requires you to turn off the system's power. For instructions on shutting down the system, see "Performing an Orderly Shutdown" section.
Overview ² Installing Software on a LightStream Switch
This chapter explains how to install LightStream software onto the hard disk(s) of a LightStream 2020 enterprise ATM switch.
Note If you are upgrading the software on an operational system, do not use the instructions in this chapter. See the release notes you received with the upgrade.
Each LightStream switch is shipped with all system and application software installed on its hard disk(s). A copy of the software is included on a set of floppy diskettes accompanying the hardware. Installing software from floppies is not part of a routine system installation. It is necessary only when a problem or the installation or replacement of new hardware occurs. For example, you must install software:
Each system is shipped with several sets of software diskettes, each set containing one or more diskettes. In addition, software for the management workstation is provided on a quarter-inch tape. (The procedure for installing management software is outlined in"Installing Management Software on A Sun" section.) The diskette sets are described below.
Before installing the software, ensure that the write protection switch on each diskette is set to "protect" or "read only."
Follow the procedures in this section to transfer LightStream software from floppy diskettes to the hard disk(s) in your LightStream switch. If your system has two NPs, you must install the software on each NP's hard disk. (It's important for the active and backup NPs in the same node to have the same software.)
During the installation process, the system prompts you for basic configuration information such as the date, IP and Ethernet IP addresses. The information you must enter is listed in "Basic Configuration" section.
The installation takes about 25 minutes per NP.
To ensure a clean installation, this section includes a procedure for reformatting the hard disk. Reformatting destroys all existing files on the disk.
If you are upgrading an operating LightStream system to a new software release, follow the instructions in the release notes you received with the software. Those instructions will preserve site-specific information on your system, such as configuration files. The procedures in this chapter tell you how to clear the hard disk and perform a full software installation; they are not designed for upgrades.
The procedures in this section use the following commands:
Note Procedures in this section assume that you have already connected a terminal or established a modem connection to the LightStream switch (as described in "Attaching a Terminal and Connecting to an NP" section). A telnet connection will not work for this purpose.
Follow this procedure to establish a connection to the NP you want to load, and reboot it in preparation for loading the software.
Step 2 Power up the system or use the reset <slot#> command at the TCS hub prompt to reset the NP in a running node. (The NPs reside in slots 1 and 2.) This example assumes that you're resetting the NP in slot 1:
Step 3 Quickly use the connect <slot#> command to connect to the NP where you want to install the software. This example assumes that you're connecting to the NP in slot 1:
Step 4 When you connect, the NP may still be running POST. Then the following countdown appears on your screen. Press [Return] immediately.
Note Note: If the system is already booting, type `. to get to the TCS hub again, then use the reset <slot#> command as described in step. Repeat steps and.
Step 5 Insert the boot diskette into the disk drive of the active NP. (Hold the disk with the label facing up and insert the edge with the metal slider first.)
Step 6 The following menu appears on the screen:
At the Option> prompt, type 2 and press [Return].
The system takes about 4 minutes to boot, then displays the single-user$ prompt.
| Caution Do not remove the boot diskette from the drive until instructed to do so. The NP is now using the boot diskette as its root file system, and will not function properly if the diskette is removed before rebooting. |
Follow the steps below to reformat the hard disk, run the date and time script, and load the boot diskette.
| Caution This procedure destroys the contents of the hard disk. |
Step 2 The system prompts you to enter time and date information:
Note Note: Indicate the daylight savings method that is followed at your site, regardless of whether daylight savings is actually in effect at the time of installation.
(The second Enter date prompt is for confirmation.)
Step 3 Next, the system prepares to reformat the hard disk by asking you for confirmation:
The system proceeds to reformat the hard disk, divide it into four partitions, build file systems, and copy files from the floppy to the hard disk. The whole process takes about 4 minutes. You'll see this on the screen:
Step 4 At the single-user$ prompt, reboot the NP by entering:
Step 5 The following menu appears on the screen:
At the Option> prompt, type 5 and press [Return].
Step 6 The system boots from the hard disk in about 10 seconds, then displays the single-user$ prompt.
Step 7 If you're using the boot diskette, press the button on the floppy drive to eject it.
This section tells you how to install software from floppy diskettes to the hard disk, and what to do afterwards.
Note If you are upgrading the software in an operating node, use the installation procedure in the release notes. Do not use the procedure given here.
There are three possible states for an NP whose power is on:
The NP on which you perform the Loading Procedure, below, must be in the inert state. If you have followed the previous procedures in this chapter, which leave the NP in single-user mode, the NP will be inert. (If there is a second NP in the chassis, it can be in any state.)
This procedure loads the software onto the hard disk, starting with the set of System diskettes.
When you press [Return], the swinstall script copies the system distribution files onto the hard disk. The script prompts you to insert the remaining System diskettes and displays progress messages. When the single-user$ prompt reappears, you can remove the last System diskette from the drive.
Step 2 Use the swinstall command to install software from the remaining diskette sets. (You must re-enter the command for each set.) The diskettes in each series are numbered; always insert diskette number 1 first. Install the remaining software in the following order:
Step 3 At the prompt, type the swchgver command, which activates the newly installed software, copies new images to the flash EEPROMs on the function cards if needed and then resets the line cards, and reboots the NP. If there is another NP in this chassis, and it is active (so that the chassis is operational), use the switches -nolinecardreset and -noflashupdate. The switches prevent the execution of swchgver on this inert NP from disrupting the rest of your system.
The commands and their output are shown below.
For the case of a second NP in a system that is operating:
For the first of two inert NPs being installed or for a system with a single NP:
Note Note: swchgver usually takes about a minute to run, but may take up to 75 minutes if flash images need to be loaded into all 10 function cards in a fully loaded system. (Flash loading takes about 7.5 minutes per card.) While a flash image is being loaded into a card, the card's yellow FLT LED illuminates.
Step 4 The bootstrap sequence and basic configuration procedure are described in "Installing a LightStream Switch" section. Turn to the section entitled "Entering Configuration Data" and follow the instructions there. When you complete basic configuration, return to step 5 below for instructions on how to proceed.
Step 5 Find the best description of your situation in the table below and proceed as indicated.
| Number of NPs | What You've Already Done | What to Do Now |
|---|---|---|
Use the LightStream configurator to download a full configuration to this node. Refer to the LightStream 2020 Configuration Guide for instructions on using the configurator. |
||
Installed software and performed basic configuration on the first NP |
Return to the procedure "Connecting to an NP" section. For the second NP, repeat all steps from "Connecting to an NP" section. |
|
Installed software and performed basic configuration on both NPs |
Use the LightStream configurator to load a full configuration into this node. Refer to the LightStream 2020 Configuration Guide for instructions on using the configurator. |
|
Installed software on the second (new) NP and performed basic configuration |
Use the LightStream configurator to add the new NP to the configuration, and then load the updated configuration into this node. Refer to the LightStream 2020 Configuration Guide for instructions on using the configurator. |
Overview ² Troubleshooting ² Using the Diagnostic Software
Read this chapter to learn how to use diagnostics and other methods to isolate faults in LightStream 2020 enterprise ATM switches.
| Caution Before removing any components from the chassis, read the safety instructions in "Electrostatic Discharge (ESD) Protection" section. If you handle components without taking proper ESD precautions, you may damage the system. |
This chapter will help you isolate problems in a LightStream switch to a single field-replaceable unit (FRU), such as a line card, blower, or power supply. Once you've identified the faulty FRU, refer to "Replacing FRUs" section for instructions on removing and replacing it.
This section briefly describes three methods of identifying problems in a LightStream switch:
POST diagnostics are described below, and instructions for general troubleshooting and running hardware diagnostics are provided later in this chapter.
LightStream's power-on self test (POST) diagnostics are the first line of defense for identifying hardware problems. POST runs on each card whenever the system or the slot is powered up or when the card is reset; it takes one minute or less. There are POSTs for the following components:
If a card passes POST, the green RDY LED on its front bulkhead turns on. If a card fails POST, its yellow FLT LED turns on. To display POST results, use one of these commands:
In the resulting display, look at the POST: line and the Application: line. If the Application: line says DISABLED, you may be able to correct the problem by enabling (activating) the card. See the LightStream 2020 Operations Guide for instructions.
Note The FLT LED doesn't necessarily indicate a POST failure or a disabled application; the LED stays on under other conditions as well. (See Table 2-3.) If the LED is on but the POST result is OK, try operating the card.
Some additional information on POST and the LEDs appears in the section "Powering Up".
If a card fails POST, review the troubleshooting tips for the card in question in the "Troubleshooting" section. In most cases, you should also run the hardware diagnostics to confirm that a problem exists. (Hardware diagnostics are described briefly below; the instructions for running them start on "Using the Diagnostic Software" section.)
LightStream's hardware diagnostics are used to discover the location of hardware faults. You can run diagnostics on a line card or a backup NP while the rest of the system continues to operate. Unless you're testing the single NP in a non-redundant system, only the card under test comes out of service during the diagnostics. To run diagnostics on the active NP in a redundant system, you first force the active and backup cards to switch roles. To run diagnostics on the only NP in a system, you must take the system off line.
Note that certain tests should not be run while the system is operating, and other restrictions may apply as well. See the "Test Notes" section.
You can run diagnostics either remotely over a telnet or modem connection, or locally from a console connected to the console port. (The exceptional case is running diagnostics on the sole NP in a non-redundant system. This task requires a local console.)
The diagnostics reside on each NP's hard disk. Several parts of the system can be tested:
Procedures for running the diagnostics appear in the section "Using the Diagnostic Software".
General troubleshooting tasks can be performed before, after, instead of, or in addition to running the diagnostic software. These tasks provide additional ways of identifying faults in NPs, switch cards, and line cards. They are the only way to identify faults in subsystems that are not covered by POST or diagnostics, such as blowers and power supplies. The section that follows describes general troubleshooting tasks.
Use the information in this section to help isolate faults in a LightStream switch. This section is to be used in conjunction with the diagnostic software. Some of these procedures require you to be in the same room with the faulty system; others can be performed remotely.
If your LightStream switch doesn't operate properly after you've tried the suggestions below, call your customer support representative.
Before resorting to the diagnostics or to complex troubleshooting, check simple things:
If you're bringing up a new LightStream node, a new card, or a new kind of port for the first time, a likely source of problems is configuration. The problem may exist at either the LightStream side or the remote side of the connection; be sure to check both configurations. Refer to the LightStream 2020 Configuration Guide for information on LightStream software configuration.
The symptoms listed below indicate problems that may require replacement of a switch card. Switch card replacement instructions in "Replacing a Switch Card" section.
Note If the switch card's fault (FLT) LED is lit, see Table 2-3 for a list of possible causes and solutions.
If the NP fails to power up, check its access card at the back of the chassis. An NP requires an NP access card (NPAC); it can't operate with any other kind of access card.
Replace the NP if any of the following applies. NP replacement instructions begin "Replacing a Network Processor card" section.
This section provides information on how to isolate faults in interface modules. (An interface module consists of a line card and its access card.)
Note If the line card's fault (FLT) LED is lit, see Table 2-3 for a list of possible causes and solutions.
The following will help you distinguish between problems in a line card and problems in an access card.
If you're having trouble bringing up a line card, check the following:
Note To prevent complications from dirty or damaged connectors, keep any unused optical connector covered with its protective cap.
The following conditions may require replacement of either a line card or its access card.
The following conditions indicate failure of a blower. See "Replacing a Blower" section for replacement instructions.
In a system with one power tray, no power will be present if the power tray is faulty. Suspect a problem with the power tray if cycling the system's power has no effect.
A system with two power trays can operate normally when only one is working; if you suspect a problem, use the CLI command show chassis powersupply. The display for a healthy dual-tray system is shown below. (In a system with only one power tray, both lines for the unused slot will read "Empty.")
If a status line for an occupied slot says anything other than Good, check the faulty power tray to see that it's properly connected. (Power tray slot A is on top; slot B is on the bottom.) If the problem persists, replace the power tray as described in "Replacing a Power Tray" section.
Disk assembly problems are indicated by the following symptoms:
If a disk problem is indicated, check the disk assembly connector for bent or broken pins. To do so, remove the disk assembly as described in "Replacing a Disk Assembly" section. Then examine the 64-pin male connector at the back of the slot. If any pins are bent or damaged, they are the likely source of the problem.
If the connector is in good condition, the problem may be in the disk assembly itself, or in the software on the disk. If you suspect a problem with the software, you should be able to correct it by reinstalling the software. If that doesn't solve the problem, or if you believe the problem lies in the hardware, see "Replacing a Disk Assembly" section for instructions on replacing the disk assembly.
Midplane problems are indicated by the following symptoms. Midplane replacement instructions begin in "Replacing The Midplane" section.
This section tells you how to run diagnostics on specified cards in a LightStream switch. You can access the diagnostics in three ways:
The rest of this section is arranged into five subsections:
This section tells you how to use the test command in CLI to run field diagnostics on a line card in a specified slot or on a backup NP.
Note You cannot use the test command to run diagnostics on a cell line card (OC-3c interfaces), a packet line card (FDDI and Ethernet interfaces), or an NP. Instead, you must load the diagnostics manually, and use the manufacturing diagnostic interface. The procedures describing this start in "Loading Manufacturing Diagnostics" section.
The first subsection below describes the switches you can use with the test command. The second subsection explains how to use the test command to test a line card.
The syntax of the CLI test command is as follows:
If you run the test command with no switches, diagnostics are loaded and run on the specified card in the background, and your CLI prompt returns so you can perform other tasks. The diagnostics complete in a minimum of 5 minutes. To display their status, type test <slot#> -r.
This procedure explains how to use the test command in CLI to run diagnostics on a line card. CLI must be running on the system you plan to test.
Note The test command does not work on cell and packet line cards (OC-3c, FDDI and Ethernet interfaces). To test these cards, you must load the diagnostics manually, and use the manufacturing diagnostic interface. The procedures describing this start in "Loading Manufacturing Diagnostics" section.
Step 2 Log in to CLI.
Step 3 Enter protected mode:
You will be prompted to enter the protected mode password.
Step 4 Use the set command to set the SNMP community to a community with write privileges. (If you don't know the appropriate community name for this system, contact the network administrator.) The example below gives the syntax of the command; replace write-community with a real community name.
Step 5 Issue the test command. (Replace the 4 in the example below with the number of the card you want to test, and add any switches you need.)
Step 6 Wait at least 15 minutes for the diagnostics to load and run. If you used the -x switch with test, wait at least 30 minutes. Then use the following command to retrieve test results, replacing the 4 with the slot number of the card you just tested:
The result indicate that the tests passed, that they failed, or that they're still running. If the last case, wait a few minutes for the tests to finish and type test 4 -r again.
Step 7 If the tests passed, the card is OK—skip to the next step. If the tests failed, you should replace the card; (In the case of failure, you should also record the list of test numbers and error numbers displayed when you type test -r, and return this list to the repair depot along with the failed card.)
Step 8 To return a card to service after running diagnostics, use following command:
Note Note: After you set the card back to active status, you can no longer use test -r to retrieve diagnostic results.
Step 9 Use the set command to change the SNMP community back to a read-only community. Replace read-community in the example below with the name of a read-only SNMP community.
You must use manufacturing diagnostics to test NPs, CLCs and PLCs. If you wish, you can also use them to test other line cards.
This section contains the following procedures:
The diagnostic programs in each LightStream switch reside on the NP's hard disk in the directory /usr/diag. (Backup copies of the diagnostics are shipped to you on floppy diskettes; if you need to re-install them, refer to "Software Installation" section for instructions on using the swinstall script.) The following files are included:
Note The /usr/diag directory also includes files of switch card diagnostics. These diagnostics are reserved for use by customer support personnel.
After loading the diagnostics, see the section "Running Manufacturing Diagnostics" for instructions on what to do next.
This procedure explains how to load the manufacturing diagnostics into an NP. Note that this procedure requires the system under test to stop passing traffic. It also requires you to have a local console connection or a modem connection to the switch whose NP you are testing. You cannot use telnet or rlogin.
The commands used in the procedure are listed below, followed by the procedure itself.
Step 2 Establish a local console connection or a modem connection to the system under test. (See "Attaching a Terminal and Connecting to an NP" section for information on terminal settings and how to determine which console port to use.)
Step 3 If the command line prompt you see does not contain the words TCS hub, type `. to get a TCS hub prompt.
Step 4 At the TCS hub prompt, use the connect <slot#> command to connect to the NP. The example below assumes that the NP is in slot 1.
Step 5 When you connect, you'll see a login prompt. Log in as root or fldsup.
Step 6 Type reboot -n to enter the boot sequence. You'll see the following display:
Step 7 Type 6 at the prompt to escape to the bootstrap command line interpreter:
Step 8 At the boot prompt, enter the following command to load the diagnostic software:
You'll see the following display:
Step 9 For instructions on executing tests in NP diagnostics, see the section "Running Manufacturing Diagnostics."
Step 10 When you finish your diagnostic session, you must reset the NP. Type `. to return to the TCS hub. Then use the command reset <slot#> to reset the NP.
If you wish, you can use the manufacturing diagnostics to test medium-speed and low-speed line cards. (The test command in CLI, described earlier, is the easiest way to test MSCs and LSCs.) Use the procedure in this section to load the manufacturing diagnostics, then go on the following section, "Running Manufacturing Diagnostics," for further instructions.
As you follow the procedure below, you'll use these commands:
Sets the SNMP community of the target node to community, a valid community name. You must set to a community with write privileges in order to load and run the diagnostics.
Changes the status of the card in the specified slot to testing mode. (Other valid modes are active and inactive.) When the card enters testing mode, it stops operating.
Loads the file specified by path/file name into the card in the specified slot. For diagnostics, use one of the /usr/diag files listed in "Loading Manufacturing Diagnostics" section.
Establishes a terminal connection to the card in the specified slot. Use the optional argument diagnostic when you use this command to run diagnostics. (Omit diagnostic when connecting for other purposes.)
Used after the connect command, ~. breaks your connection with the card under test and returns you to CLI, leaving the diags still running. Use connect as described above to return to the diags.
Step 2 Use the set command to set the SNMP community to a community with write privileges. (If you don't know the appropriate community name for this system, contact the network administrator.) The example below gives the syntax of the command; replace write-community with a real community name.
Step 3 Use the set command to set the status of the card to be tested to "testing". The example below gives the syntax of the command; replace slot# with a real slot number.
Step 4 Use the loadcard command to load the appropriate diagnostic program into the card to be tested. (The syntax is provided above.) Two typical loadcard commands are shown below.
Loads the NP diagnostics into the card in slot 1.
Loads the LSC diagnostics into the card in slot 3.
Step 5 Use the connect command to establish a connection to the slot number (card) you want to test. For example:
You'll see a banner describing the diagnostic package, followed by a command prompt. You can use the _0 command in any package to select and run a set of tests. The section "Running Manufacturing Diagnostics" provides detailed procedures for running tests.
Note If you need to return to CLI before completing your session with the diagnostics, you can toggle back and forth using the command ~. to get to CLI and connect <slot#> diagnostic to return to the diagnostics. Be sure to exit from the diagnostics when your session is finished.
Refer to the "Command Reference" section for information on commands.
Read this section for information on running manufacturing diagnostics. The first subsection, Running Sets of Tests, applies to all four of the procedures that follow.
In each of the four diagnostics packages, commands are provided to run preselected sets of tests:
Note If you use the sel or dsel commands, the tests executed by run may change. run executes tests that are currently selected; the test set outlined here is selected by default, but you can change it.
Use this procedure to run diagnostics on an NP card. It assumes that you have already loaded the diagnostics onto the card, as described in one of the procedures in Loading Manufacturing Diagnostics in "Loading Manufacturing Diagnostics" section.
Note The screens that follow use the arun command in order to display a complete list of tests. It is recommended that you use _0 or run instead.
Step 2 To run or rerun a particular test or group of tests, you can use the run command in conjunction with test numbers. For example:
(To display a list of tests and test numbers, use the lst all command.)
Step 3 The status command displays a message giving the status of diagnostic tests. Use status fail to get information only on tests that have failed.
Step 4 For explanations of the error codes used in the status display, use the help command in conjunction with the number of the test in question. For example,
Note If you need to return to CLI before completing your session with the diagnostics, you can toggle back and forth using the command ~. to get to CLI and connect <slot#> diagnostic to return to the diagnostics. Be sure to exit from the diagnostics when your session is finished.
Step 5 If the card passes the diagnostics, return the card to active mode. First exit from the diagnostics:
Note If you're running diagnostics on an active NP, the exit command has no effect; you must reset the NP. You can either press the reset button on the front of the card, or type `., then reset <slot#> to reset the NP, then connect <slot#> to reconnect to the NP. Replace <slot#> with the slot number of the card you were testing.
Step 6 When the login prompt appears, log into the node, enter CLI's protected mode, and use the set command as shown below to reset the card's status to active. Replace <slot#> with the slot number of the card you were testing.
If any tests fail, replace the card being tested.
If all tests pass but you're still experiencing a problem, test the other cards in the chassis. Replace any cards that fail diagnostics. If the problem persists, investigate causes outside the LightStream hardware, including leased lines and edge devices.
Use this procedure to run diagnostics on a low-speed line card. It assumes that you have already loaded the diagnostics onto the card, as described in one of the procedures in Loading Manufacturing Diagnostics in "Loading Manufacturing Diagnostics" section.
Note The screens that follow use the arun command in order to display a complete list of tests. It is recommended that you use _0 or run instead.
Note Tests flagged in the list above with (L) require looping plugs. See "LSC Tests with Special Requirements" section for details.
Step 2 To run or rerun a particular test or group of tests, you can use the run command in conjunction with test numbers. For example:
(To display a list of tests and test numbers, use the lst all command.)
Step 3 The status command displays a message giving the status of diagnostic tests. Use status fail to get information only on tests that have failed.
Step 4 For explanations of the error codes used in the status display, use the help command in conjunction with the number of the test in question. For example,
Note If you need to return to CLI before completing your session with the diagnostics, you can toggle back and forth using the command ~. to get to CLI and connect <slot#> diagnostic to return to the diagnostics. Be sure to exit from the diagnostics when your session is finished.
Step 5 If the card passes the diagnostics, return the card to active mode. First exit from the diagnostics:
Step 6 When the login prompt appears, log into the node, enter CLI's protected mode, and use the set command as shown below to reset the card's status to active. Replace <slot#> with the slot number of the card you were testing.
If any tests fail you may need to replace either the line card being tested or its access card. Look at the numbers of the tests that failed to determine which card to replace:
Note Tests 111-118 normally fail if you run them in an operating system using test -m; this failure does not indicate a problem and should be ignored.
Note Tests 43, 46 and 50 pass only when looping plugs are installed; disable or disregard them when testing without looping plugs.
If all tests pass but you're still experiencing a problem, test the other cards in the chassis. Replace any cards that fail diagnostics. If the problem persists, investigate causes outside the LightStream hardware, including leased lines and edge devices.
Use this procedure to run diagnostics on a medium-speed line card. It assumes that you have already loaded the diagnostics onto the card, as described in one of the procedures in "Loading Manufacturing Diagnostics" section.
Note The screens that follow use the arun command in order to display a complete list of tests. It is recommended that you use _0 or run instead.
Step 2 To run or rerun a particular test or group of tests, you can use the run command in conjunction with test numbers. For example:
(To display a list of tests and test numbers, use the lst all command.)
Step 3 The status command displays a message giving the status of diagnostic tests. Use status fail to get information only on tests that have failed.
Step 4 For explanations of the error codes used in the status display, use the help command in conjunction with the number of the test in question. For example,
Note If you need to return to CLI before completing your session with the diagnostics, you can toggle back and forth using the command ~. to get to CLI and connect <slot#> diagnostic to return to the diagnostics. Be sure to exit from the diagnostics when your session is finished.
Step 5 If the card passes the diagnostics, return the card to active mode. First exit from the diagnostics:
Step 6 When the login prompt appears, log into the node, enter CLI's protected mode, and use the set command as shown below to reset the card's status to active. Replace <slot#> with the slot number of the card you were testing
If any tests fail you may need to replace either the line card being tested or its access card. Look at the numbers of the tests that failed to determine which card to replace:
Note Tests 70 - 80 normally fail if you run them in an operating system using test -m; this failure does not indicate a problem and should be ignored.
Note Test 95 passes only on the E3 access card; disable or disregard it when testing a T3 card. Tests 93 and 94 pass only when looping plugs are installed; disable or disregard them when testing without looping plugs.
If all tests pass but you're still experiencing a problem, test the other cards in the chassis. Replace any cards that fail diagnostics. If the problem persists, investigate causes outside the LightStream hardware, including leased lines and edge devices.
Use this procedure to run diagnostics on a packet line card. It assumes that you have already loaded the diagnostics onto the card, as described in one of the procedures in "Loading Manufacturing Diagnostics" section.
When they are loaded, the PLC diagnostics determine which type of access card (Ethernet or FDDI) is installed with the line card under test. Tests appropriate for the access card are enabled. You can use the "access" command to display the type of the access card.
Note The screens that follow use the arun command in order to display a complete list of tests. It is recommended that you use run instead.
Step 2 To run or rerun a particular test or group of tests, you can use the run command in conjunction with test numbers. For example:
(To display a list of tests and test numbers, use the lst all command.)
Step 3 The status command displays a message giving the status of diagnostic tests. Use status fail to get information only on tests that have failed.
Step 4 For explanations of the error codes used in the status display, use the help command in conjunction with the number of the test in question. For example,
Note If you need to return to CLI before completing your session with the diagnostics, you can toggle back and forth using the commands ~. to get to CLI and connect <slot#> diagnostic to return to the diagnostics. Be sure to exit from the diagnostics when your session is finished.
Step 5 If the card passes the diagnostics, return the card to active mode. First exit from the diagnostics:
Step 6 When the login prompt appears, log into the node, enter CLI's protected mode, and use the set command as shown below to reset the card's status to active. Replace <slot#> with the slot number of the card you were testing.
If test 55 (or any of its subtests, 55.01 through 55.15) fails, this indicates a failure in the access card. In this case replace the access card.
If any other tests fail, replace the card being tested.
If all tests pass but you're still experiencing a problem, test the other cards in the chassis. Replace any cards that fail diagnostics. If the problem persists, investigate causes outside the LightStream hardware, including leased lines and edge devices.
Use this procedure to run diagnostics on a cell line card. It assumes that you have already loaded the diagnostics onto the card, as described in one of the procedures in "Loading Manufacturing Diagnostics" section.
Note The screens that follow use the arun command in order to display a complete list of tests. It is recommended that you use run instead.
Step 2 To run or rerun a particular test or group of tests, you can use the run command in conjunction with test numbers. For example:
(To display a list of tests and test numbers, use the lst all command.)
Step 3 The status command displays a message giving the status of diagnostic tests. Use status fail to get information only on tests that have failed.
Step 4 For explanations of the error codes used in the status display, use the help command in conjunction with the number of the test in question. For example,
Note If you need to return to CLI before completing your session with the diagnostics, you can toggle back and forth using the commands ~. to get to CLI and connect <slot#> diagnostic to return to the diagnostics. Be sure to exit from the diagnostics when your session is finished.
Step 5 If the card passes the diagnostics, return the card to active mode. First exit from the diagnostics:
Step 6 When the login prompt appears, log into the node, enter CLI's protected mode, and use the set command as shown below to reset the card's status to active. Replace <slot#> with the slot number of the card you were testing.
If test 51 (or any of its subtests) fails, this indicates a failure in the access card. In this case replace the access card.
If any other tests fail, replace the card being tested.
If all tests pass but you're still experiencing a problem, test the other cards in the chassis. Replace any cards that fail diagnostics. If the problem persists, investigate causes outside the LightStream hardware, including leased lines and edge devices.
This section lists special requirements for tests in each diagnostic package.
The NP tests listed below send data through the switch card. Take the LightStream node off line before running these tests, as described in the procedure following the list of tests. Do not run them on a system that's passing traffic. (If the node is running, these tests may fail when they would otherwise pass. In addition, the "bad" data passed to the switch by the tests may cause traps.)
If you wish to run these tests, use the procedure below to disable the system and all the other cards in the chassis. This prevents the other cards from sending packets to the card under test that cause these tests to fail even when no problem exists.
Step 2 At the bash prompt, use the command reboot -n to bring down the NP. (Bring down both if there are two.)
Step 3 Type `. to get a TCS hub prompt.
Step 4 From the TCS hub, type reset <slot#> to reset each slot that has a line card in it. (Don't reset the switch card or NP slots.)
Step 5 Type connect <slot#> to return to the NP, then press [Return] to display a menu of boot options.
Step 6 At the menu's Option prompt, enter 6, as shown below.
Step 7 The system displays the following message and a boot prompt. Enter the string shown below to load the NP diagnostics.
Step 8 When the diagnostics finish loading, you can select and run the desired tests.
The NP tests listed below will fail if they are run on a system that does not have looping plugs installed on the NP Ethernet port and Diag2 port. (In field diagnostics, these tests are invoked when you use the test command's -l switch.) If you do not have looping plugs installed, it's recommended that you avoid running these tests:
The NP memory tests listed below take longer than one minute to run. (Some take many minutes.) Avoiding these tests saves time. (In field diagnostics, these tests are invoked when you use the test command's -x switch.)
The NP diagnostics include tests for the battery-backed RAM clock that keeps time for the whole system. If the tests fail, you will be prompted to reset the clock; you must supply the current time and date. If the system under test has two NPs, make certain that their clocks agree to within one minute. (If the clocks don't agree, file consistency problems between the two NPs may result.)
The low-speed line card tests listed below send data through the switch card. (In field diagnostics, these tests are invoked when you use the test command's -s switch.) Take the LightStream node off line before running these tests. Do not run them on a system that's passing traffic. (If the node is running, these tests may fail when they would otherwise pass. In addition, the "bad" data passed to the switch by the tests may cause traps.)
If you wish to run these tests, use the procedure below to disable the system and all the other cards in the chassis, and then to load the diagnostics into the card you wish to test. This procedure prevents the other cards from sending packets to the card under test that cause these tests to fail even when no problem exists.
Step 2 At the bash prompt, enter the command reboot -n to bring down the NP. If your system has two NPs, do the following to reboot the second one:
Type `. to get a TCS hub prompt.
Type connect <slot#> to get to the other NP, replacing <slot#> with the number of the NP's slot in the chassis.
Log in to the NP as root or fldsup.
At the bash prompt, enter the command reboot -n to bring down the NP.
Step 3 Type `. to get a TCS hub prompt.
Step 4 From the TCS hub, type reset <slot#> to reset each slot that has a line card in it. (Don't reset the switch card or NP slots.)
Step 5 Type connect <slot#> to return to the NP, then press [Return] to display a menu of boot options.
Step 6 At the menu's Option prompt, enter 6, as shown below.
Step 7 The system displays the following message and a boot prompt. Enter the string shown below to load the system monitor, which you will use to load the diagnostics.
Step 8 When the system monitor finishes loading, you'll see an identifying message and a prompt, as shown below. To load diagnostics, type the command shown, replacing <slot#> with the number of the card you want to test.
Step 9 Wait about 5 minutes for the diagnostics to load. Then type `. to return to the TCS hub.
Step 10 At the TCS hub prompt, use the command connect <slot#> to connect to the card you just loaded.
Step 11 Run the desired tests.
The LSC tests listed below will fail if they are run on a system that does not have looping plugs installed on the I/O ports. (In field diagnostics, these tests are invoked when you use the test command's -l switch.) If you do not have looping plugs installed, it's recommended that you avoid running these tests:
The low-speed line card memory tests listed below take longer than one minute to run. (Some take many minutes.) Avoiding these tests saves time. (In field diagnostics, these tests are invoked when you use the test command's -x switch.)
The medium-speed line card tests listed below send data through the switch card. (In field diagnostics, these tests are invoked when you use the test command's -s switch.) Take the LightStream node off line before running these tests. Do not run them on a system that's passing traffic. (If the node is running, these tests may fail when they would otherwise pass. In addition, the "bad" data passed to the switch by the tests may cause traps.)
If you wish to run these tests, use the procedure below to disable the system and all the other cards in the chassis, and then to load the diagnostics into the card you wish to test. This procedure prevents the other cards from sending packets to the card under test that cause these tests to fail even when no problem exists.
Step 2 At the bash prompt, enter the command reboot -n to bring down the NP. If your system has two NPs, do the following to reboot the second one:
Step 3 Type `. to get a TCS hub prompt.
Step 4 From the TCS hub, type reset <slot#> to reset each slot that has a line card in it. (Don't reset the switch card or NP slots.)
Step 5 Type connect <slot#> to return to the NP, then press [Return] to display a menu of boot options.
Step 6 At the menu's Option prompt, enter 6, as shown below.
Step 7 The system displays the following message and a boot prompt. Enter the string shown below to load the system monitor, which you will use to load the diagnostics.
Step 8 When the system monitor finishes loading, you'll see an identifying message and a prompt, as shown below. To load diagnostics, type the command shown, replacing <slot#> with the number of the card you want to test.
Step 9 Wait about 5 minutes for the diagnostics to load. Then type `. to return to the TCS hub.
Step 10 At the TCS hub prompt, use the command connect <slot#> to connect to the card you just loaded.
Step 11 Run the desired tests.
The MSC tests listed below will fail if they are run on a system that does not have looping plugs installed on the I/O ports. (In field diagnostics, these tests are invoked when you use the test command's -l switch.) If you do not have looping plugs installed, it's recommended that you avoid running these tests:
The medium-speed line card memory tests listed below take longer than one minute to run. (Some take many minutes.) Avoiding these tests saves time. (In field diagnostics, these tests are invoked when you use the test command's -x switch.)
The packet line card tests listed below send data through the switch card. (In field diagnostics, these tests are invoked when you use the test command's -s switch.) Take the LightStream node off line before running these tests. Do not run them on a system that's passing traffic. (If the node is running, these tests may fail when they would otherwise pass. In addition, the "bad" data passed to the switch by the tests may cause traps.)
If you wish to run these tests, use the procedure below to disable the system and all the other cards in the chassis, and then to load the diagnostics into the card you wish to test. This procedure prevents the other cards from sending packets to the card under test that cause these tests to fail even when no problem exists.
Step 2 At the bash prompt, enter the command reboot -n to bring down the NP. If your system has two NPs, do the following to reboot the second one:
Type `. to get a TCS hub prompt.
Type connect <slot#> to get to the other NP, replacing <slot#> with the number of the NP's slot in the chassis.
Log in to the NP as root or fldsup.
At the bash prompt, enter the command reboot -n to bring down the NP.
Step 3 Type `. to get a TCS hub prompt.
Step 4 From the TCS hub, type reset <slot#> to reset each slot that has a line card in it. (Don't reset the switch card or NP slots.)
Step 5 Type connect <slot#> to return to the NP, then press [Return] to display a menu of boot options.
Step 6 At the menu's Option prompt, enter 6, as shown below.
Step 7 The system displays the following message and a boot prompt. Enter the string shown below to load the system monitor, which you will use to load the diagnostics.
Step 8 When the system monitor finishes loading, you'll see an identifying message and a prompt, as shown below. To load diagnostics, type the command shown, replacing <slot#> with the number of the card you want to test.
Step 9 Wait about 5 minutes for the diagnostics to load. Then type `. to return to the TCS hub.
Step 10 At the TCS hub prompt, use the command connect <slot#> to connect to the card you just loaded.
Step 11 Run the desired tests.
The PLC tests listed in this section will fail if they are run on a system that does not have looping cables installed on the I/O ports. (In field diagnostics, these tests are invoked when you use the test command's -l switch.) The individual tests vary depending on whether your PLC is paired with an FDDI access card or an Ethernet access card. If you do not have looping cables installed, it's recommended that you avoid running these tests.
If you choose to run these tests, use looping cables to connect the ports on the Ethernet card to each other in the following manner:
Note This list uses the port numbers as shown on the Ethernet card, but the diagnostics number the ports 1 through 8 instead of 0 through 7.
The packet line card memory tests listed below take longer than one minute to run. (Some take many minutes.) Avoiding these tests saves time. (In field diagnostics, these tests are invoked when you use the test command's -x switch.)
The cell line card tests listed below send data through the switch card. (In field diagnostics, these tests are invoked when you use the test command's -s switch.) Take the LightStream node off line before running these tests. Do not run them on a system that's passing traffic. (If the node is running, these tests may fail when they would otherwise pass. In addition, the "bad" data passed to the switch by the tests may cause traps.)
If you wish to run these tests, use the procedure below to disable the system and all the other cards in the chassis, and then to load the diagnostics into the card you wish to test. This procedure prevents the other cards from sending packets to the card under test that cause these tests to fail even when no problem exists.
Step 2 At the bash prompt, enter the command reboot -n to bring down the NP. If your system has two NPs, do the following to reboot the second one:
Type `. to get a TCS hub prompt.
Type connect <slot#> to get to the other NP, replacing <slot#> with the number of the NP's slot in the chassis.
Log in to the NP as root or fldsup.
At the bash prompt, enter the command reboot -n to bring down the NP.
Step 3 Type `. to get a TCS hub prompt.
Step 4 From the TCS hub, type reset <slot#> to reset each slot that has a line card in it. (Don't reset the switch card or NP slots.)
Step 5 Type connect <slot#> to return to the NP, then press [Return] to display a menu of boot options.
Step 6 At the menu's Option prompt, enter 6, as shown below.
Step 7 The system displays the following message and a boot prompt. Enter the string shown below to load the system monitor, which you will use to load the diagnostics.
Step 8 When the system monitor finishes loading, you'll see an identifying message and a prompt, as shown below. To load diagnostics, type the command shown, replacing <slot#> with the number of the card you want to test.
Step 9 Wait about 5 minutes for the diagnostics to load. Then type `. to return to the TCS hub.
Step 10 At the TCS hub prompt, use the command connect <slot#> to connect to the card you just loaded.
Step 11 Run the desired tests.
The CLC tests listed below will fail if they are run on a system that does not have looping plugs installed on the I/O ports. (In field diagnostics, these tests are invoked when you use the test command's -l switch.) If you do not have looping plugs installed, it's recommended that you avoid running these tests:
The cell line card memory tests listed below take longer than one minute to run. (Some take many minutes.) Avoiding these tests saves time. (In field diagnostics, these tests are invoked when you use the test command's -x switch.)
This section alphabetically lists and describes selected commands that are available in LightStream's hardware diagnostic packages. Many commands are available in all three packages; others are specific to one or two packages. Each entry lists the packages in which the command is available.
Note LightStream diagnostics contain many commands that are not listed in this section. Such commands are for use by support personnel only.
Causes the specified command to loop indefinitely. For example, the arun command runs all tests once; !arun cycles through all the tests repeatedly until you stop the loop, or, if stop on fail mode is on, until a test fails.
Without argument: Displays a list of available commands.
With argument: Displays information on the specified command.
With no argument, displays the type of access card installed with the PLC line card under test. With an argument, forces activation of the access card tests for the access card type indicated.
Runs all tests once. Not recommended if you don't have looping plugs or if you are running diagnostics remotely, as this command runs tests that require looping plugs.
Checks the status of the battery for the NP's battery-backed RAM. A screen display tells you that the battery is OK, or that it's low.
Note The results of this command are only valid the first time the command is executed after powering up the NP. To get valid results again, you must power cycle the board.
In NP diags: Causes the green RDY LED and/or the yellow FLT LED on the NP bulkhead to blink, turn on, or turn off.
In PLC and CLC diags: Causes LNS OK LED on the bulkhead to blink (on) or not blink (off) during long-running tests. Blinking gives an indication that the tests are still running.
Changes the diagnostics command prompt. Maximum prompt length is 30 characters.
Specifies the count, or number of times the selected tests will be executed when you use the run command. Use cnt with no argument to display the current loop count.
Deselects all selected tests, a particular test, or a range of tests.
Displays the firmware revision levels of the switch interface daughterboard's PCP, CMP, and FSU digital signal processors.
Displays the current test run environment as selected with the mod command.
Runs selected tests (with no argument), or specified tests. The switches, which temporarily override the mode settings, are as follows:
execute is the same as run and go.
You can also run tests using the execute or go commands, or by typing specific test numbers or ranges of numbers. (For example, type 22 to run test 22.) You can use the switches for the run command with test numbers as well. Thus, for example, these two commands both cause tests 22 through 24 to loop indefinitely:
Halts the diagnostics, resets the board, and transfers control to POST. (Same as quit.)
Formats the diskette in the floppy drive.
Displays information on the floppy disk drive, including firmware revision level and model number.
Runs the specified test or range of tests. go is the same as execute and run.
Displays the last 50 commands entered. This command is useful in conjunction with ^P to yank previous commands from the history buffer.
Displays the current setting of the jumpers that determine whether the low-speed line card presents V.35 or RS-449 interfaces.
Turns the channel LEDs on the line card bulkhead on or off. Without an argument, led flashes the LEDs in succession until you press any key to stop the test. led on turns all the LEDs on; led off turns them all off. In conjunction with the on/off argument, the channel argument lets you turn particular LEDs on or off. On medium-speed cards, the channels are 0 and 1; on low-speed cards, the channels are 0 - 7. The following example turns LED 0 on:
Availability: LSC and MSC diags
Sets the loop counter to the specified number. When you use execute, go or run, the selected tests repeat, or loop, the specified number of times.
Lists selected tests (with no argument), all tests, a specific test, or a range of tests. (A range is expressed with a dash. For example, you might type lst 1-6.)
In PLC and CLC diagnostics, tests are numbered hierarchically using both decimal and whole numbers. Similar tests are grouped together under the same number. For example, all the access card tests in PLC diagnostics are subtests of test number 55, and are numbered 55.01 to 55.15. If you type lst or list in PLC or CLC diags, only the top-level tests are listed. Type lst all to list all the tests, including subtests.
Lists all installed macros. Refer to the "Macros" section for information on installing and using macros.
Sets up the test environment, where mode is one of the following:
0 turns the specified mode off; 1 turns it on. For example, mod sof = 1 turns stop on fail mode on. 0 and 1 can be replaced with off and on. Thus, mod sof = on has the same effect as mod sof = 1.
Halts the diagnostics, resets the board, and transfers control to POST. (Same as exit.)
Displays information identifying the current revision of the diagnostics. rev is the same as ver.
Runs selected tests (with no argument), or specified tests. The switches, which temporarily override the mode settings, are as follows:
run is the same as execute and go.
You can also run tests using the execute or go commands, or by typing specific test numbers or ranges of numbers. (For example, type 22 to run test 22.) You can use the switches for the run command with test numbers as well. Thus, for example, these two commands both cause tests 22 through 24 to loop indefinitely:
Resets the SCSI bus that communicates with the hard and floppy disk drives.
Selects the test or tests to be run. The argument can be a single test number, a range of numbers (6 - 12, for example), or all (select all tests). Use run to execute selected tests. Use dsel to deselect tests.
Displays the status of selected tests (with no argument); all displays status for all tests; clr clears the status of selected tests; and fail displays the status of failed tests only. To display detailed status, use status and help together:
The help display explains the error codes used in the status display.
Displays temperature readings for the card under test.
Displays information identifying the current version of the diagnostics. ver is the same as rev.
Displays voltage information for the card under test, as measured and reported by the TCS.
Any command can be abbreviated to the shortest string that uniquely identifies it in its diagnostic package.
Each diagnostics package lets you configure up to five macros, numbered 0 through 4. (Macros 0 and 1 are preconfigured; see "Running Sets of Tests" section for descriptions of what they do.) A macro can be a command or string of commands. Use the following syntax to install a macro:
Where x is a macro number (0 - 4), and command is a command or a chain of commands.
In the following example, two macros are installed; the second incorporates the first.
To execute a macro, type its number preceded by an underscore: for example, _1. To list all the installed macros, use the macro command.
Overview ² Replacing a Switch Card ² Replacing a Network Processor Card ² Replacing a Line Card ² Replacing an Access Card ² Replacing a Power Tray ² Replacing a Blower ² Replacing a Disk Assembly ² Replacing a Disk Assembly Connector ² Replacing the Midplane ² Replacing a Console/Modem Assembly ² Replacing a Fantail ² Performing an Orderly Shutdown
Read this chapter for instructions on removing and replacing field-replaceable units (FRUs) in LightStream 2020 enterprise ATM switches.
For instructions on how to isolate hardware problems to the FRU level, see "Hardware Troubleshooting" section.
| Warning Procedures in this chapter can expose you to electrical and mechanical hazards. Carefully read and adhere to all cautions and warnings in the instructions. |
| Caution Do not swap one line card for another unless you're sure that the cards are of the same type. Most line cards can be configured as either edge or trunk cards. You can't determine by looking at a card whether it's an edge or a trunk; check the configuration or use the show card command in CLI. |
| Caution Before removing any components from or adding any components to the chassis, read the safety instructions on "Electrostatic Discharge (ESD) Protection" section. If you handle components without proper ESD precautions, you may damage the system. |
LightStream switches are designed to have a low mean time to repair (MTTR). FRUs are easily accessible and easy to replace. You should be able to complete each of the procedures detailed here within 15 minutes, except where otherwise noted.
Most of the procedures in this chapter can be completed by one person. The exception is the disk assembly connector replacement, which should be done by two people.
LightStream provides power-on servicing, which means that most portions of the system can be serviced while the unit continues to operate. You can perform power-on servicing on the following FRUs:
Before replacing the following FRUs, you must perform an orderly shutdown of the LightStream system and turn off power:
Note Replacing the bulk power tray in a nonredundant system causes the system to power down. Replacing an NP in a nonredundant system interrupts the flow of traffic. Replacing a switch card in a nonredundant system effectively shuts down the system.
Refer to "Performing an Orderly Shutdown" section for instructions on performing an orderly shutdown of a LightStream switch.
Figure 7-1 and Figure 7-2 show the locations of FRUs from the front and rear of the chassis.
When you remove a faulty component from a LightStream system, you can return it for repair. Here's what to do:
Step 2 Attach a tag to the FRU that lists the RMA number and describes the problem you experienced. Include instructions on how to reproduce the problem and a list of the test numbers of the diagnostics that the FRU failed.
Step 3 Pack the FRU securely and ship as directed.
Step 4 Record the replacement in your system's maintenance log.
The following is a complete list of tools and equipment you must supply and have on hand for LightStream FRU replacement:
This section explains how to remove and replace a switch card. If the LightStream system is passing traffic, note the following:
Step 2 Unscrew the captive screws at the top and bottom of the card.
Step 3 Using the extractor handles, pull the card out of its slot. (See Figure 7-3.)
| Warning 48-volt current is present on the midplane at high levels. Be very careful when accessing this area; don't touch the midplane unnecessarily, and avoid contact with connectors. |
Step 2 Lock down the extractor handles and tighten the screws that hold the card in place.
Step 3 Refer to the LightStream 2020 Administration Guide for instructions on powering up and reactivating the slot.
Note When you complete this procedure, check the front and back of the system to see that all boards, disks, blowers, bulkheads, filler panels, and covers are in place and firmly screwed to the chassis frame. When all these items are in place, they form an enclosure that prevents the escape of electro-magnetic interference and maintains air flow through the chassis.
This section explains how to remove and replace an NP card. If the LightStream system is passing traffic, note the following:
Step 2 Unscrew the retaining screws at the top and bottom of the card.
Step 3 Using the extractor handles, pull the card out of its slot. (See Figure 7-4.)
Step 2 Lock down the extractor handles and tighten the screws that hold the card in place.
Step 3 Refer to the LightStream 2020 Administration Guide for instructions on powering up and reactivating the slot.
Note When you complete this procedure, check the front and back of the system to see that all boards, disks, blowers, bulkheads, filler panels, and covers are in place and firmly screwed to the chassis frame. When all these items are in place, they form an enclosure that prevents the escape of electro-magnetic interference and maintains air flow through the chassis.
This section explains how to remove and replace a line card.
Step 2 Unscrew the retaining screws at the top and bottom of the card.
Step 3 Using the extractor handles, pull the card out of its slot. (See Figure 7-5.)
Step 2 Lock down the extractor handles and tighten the screws that hold the card in place.
Step 3 Refer to the LightStream 2020 Administration Guide for instructions on powering up and reactivating the slot.
Note When you complete this procedure, check the front and back of the system to see that all boards, disks, blowers, bulkheads, filler panels, and covers are in place and firmly screwed to the chassis frame. When all these items are in place, they form an enclosure that prevents the escape of electro-magnetic interference and maintains air flow through the chassis
This section explains how to remove and replace an access card.
Step 2 Disconnect any cables attached to the access card. Label them so that you will be able to reconnect them to the new access card in exactly the same configuration.
Step 3 Unscrew the retaining screws at the top and bottom of the card.
Step 4 Using the extractor handles, pull the card out of its slot. (See Figure 7-6.)
| Caution Before installing the new access card, ensure that the function card in that slot is turned off. (Check the VCC (power) LED on the card.) Connecting an access card to a powered-on function card can damage the access card. |
Step 2 Lock down the extractor handles and tighten the screws that hold the card in place.
Step 3 Reconnect any cables that you disconnected when you removed the old access card.
Step 4 Refer to the LightStream 2020 Administration Guide for instructions on powering up and reactivating the slot.
Note When you complete this procedure, check the front and back of the system to see that all boards, disks, blowers, bulkheads, filler panels, and covers are in place and firmly screwed to the chassis frame. When all these items are in place, they form an enclosure that prevents the escape of electro-magnetic interference and maintains air flow through the chassis.
This section explains how to remove and replace a bulk power tray. Power trays are accessible from the rear of the chassis, as shown in Figure 7-7.
Note Removal and replacement of DC power trays should be performed by qualified service personnel or a licensed electrician.
Step 2 Unscrew the two captive screws that hold the power tray's cover in place. Remove the cover.
| Warning When you remove the power tray cover, live power circuits are exposed. Touch only the front lip and the sides of the power tray. Do not insert tools or hands into the power supply tray or into the chassis. |
Step 3 Unscrew the two captive retaining screws that hold the power tray assembly in place. (See Figure 7-7.)
Step 4 Slowly slide the power tray out of the chassis.
Step 2 Disconnect the power wires and the alarm wires (if any) from the front of the power tray.
Step 3 Unscrew the two captive retaining screws that hold the power tray assembly in place. (See Figure 7-7.)
Step 4 Slowly slide the power tray out of the chassis.
Step 2 Tighten the two screws that hold the power tray assembly in place.
Step 3 If you're installing a DC power tray, reconnect the power wires and the alarm wires (if any) to the terminals on the front of the power tray.
Step 4 If you're installing an AC power tray, replace the cover. Secure the cover with the two captive screws that hold it in place.
Step 5 Check the green LED on the power tray to ensure that the power is on. (On a DC power tray, the LED is just below the power switch. On an AC tray, you should be able to see the LED through the cover.)
Note When you complete this procedure, check the front and back of the system to see that all boards, disks, blowers, bulkheads, filler panels, and covers are in place and firmly screwed to the chassis frame. When all these items are in place, they form an enclosure that prevents the escape of electro-magnetic interference and maintains air flow through the chassis.
This section explains how to remove and replace a blower.
The blowers are at the top of the LightStream chassis. One is accessible from the front and the other is accessible from the rear.
Step 2 Unscrew the retaining screws (bottom front of the blower, shown in Figure 7-8) and slowly slide the blower out until its power LED goes out. When the impeller inside the blower stops spinning, remove the blower completely from the chassis.
| Warning The impeller inside the blower box may still be turning when you loosen the retaining screws. Keep fingers, screwdrivers and other objects away from the openings in the blower's housing. Do not remove the blower from the chassis until the impeller stops moving. |
Step 2 Check the power LED on the front of the blower. It should be on if the system is powered up. (If the LED does not light up, the system may have a connector problem or a power problem.)
Step 3 Replace the cover and tighten the two screws that hold it in place.
Note When you complete this procedure, check the front and back of the system to see that all boards, disks, blowers, bulkheads, filler panels, and covers are in place and firmly screwed to the chassis frame. When all these items are in place, they form an enclosure that prevents the escape of electro-magnetic interference and maintains air flow through the chassis.
This section explains how to remove and replace a disk assembly.
The disk assembly is a single FRU consisting of a hard disk drive, a floppy disk drive and an associated power supply. A LightStream switch can have up to two disk assemblies. Each disk assembly is associated with a network processor card, and is connected to the network processor card by a ribbon cable attached to a male connector at the rear of the disk assembly slot.
Note There are two versions of the disk assembly: one for AC-powered systems, the other for DC-powered systems.
Step 2 Slowly slide the disk assembly out of the enclosure.
| Warning When you remove the disk assembly, live power circuits are exposed. Touch only the handle on the front of the disk assembly until you can remove it from the chassis. Do not insert tools or hands into the disk assembly or into the chassis. |
Step 2 Tighten the two screws that hold the disk assembly in place.
Note Check the front and back of the system to see that all boards, disks, blowers, bulkheads, filler panels, and covers are in place and firmly screwed to the chassis frame. When all these items are in place, they form an enclosure that prevents the escape of electro-magnetic interference and maintains air flow through the chassis.
Step 3 Turn to "Software Installation" section and follow the procedures for installing software on the replacement disk.
This section tells you how to replace the 64-pin male DIN connector at the back of each disk assembly slot. You should replace this connector if you notice that any of the pins are bent or broken.
The disk assembly connector is a two-piece "press fit" connector, shown in Figure 7-10. One piece inserts from the rear of the chassis; the other inserts from the front. Have a second person on hand to help you with this procedure.
Step 2 Remove the bulk power tray behind the connector that is being replaced. (See the section on "Replacing a Power Tray" if you need instructions on removing the power tray.)
Step 3 Following the instructions in the section, "Replacing a Disk Assembly), remove the disk assembly from the enclosure.
Step 4 From the rear of the chassis, unscrew the two Phillips-head screws that hold the SCSI ribbon cable in place at the rear of the disk assembly connector. Remove the ribbon cable. (Figure 7-11 shows how these pieces fit together.)
Step 5 Remove the two 3/16 lug screws from the rear of the connector. (These lugs held the screws removed in the previous step.)
Step 6 From the front of the chassis, remove the two Phillips-head screws from the front of the connector.
Step 7 Make a note of how the connector is keyed so that you can install the new one in the same manner.
Step 8 Disassemble the connector and remove it.
Step 2 From the rear of the chassis, insert the pins on the back of the connector through the hole in the sheet metal and through the front piece of the connector (which is held in place by your helper). When the two pieces of the connector begin to engage, push slowly and gently to avoid damaging the pins.
Step 3 Have your helper replace the two Phillips-head screws in the front of the connector.
Step 4 While your helper holds the two Phillips-head screws in place from the front, replace the two 3/16 lug screws in the rear of the connector.
Step 5 Replace the SCSI ribbon cable at the rear of the connector and secure it with the two Phillips-head screws that hold it in place.
Step 6 Carefully slide the disk assembly back into the enclosure. When the connectors begin to engage, push slowly and gently to avoid damaging the pins. Tighten the retaining screws that hold the disk assembly in place.
Step 7 Replace the power tray behind the connector that was replaced.
Step 8 Turn on the power and bring the system back up.
Note When you complete this procedure, check the front and back of the system to see that all boards, disks, blowers, bulkheads, filler panels, and covers are in place and firmly screwed to the chassis frame. When all these items are in place, they form an enclosure that prevents the escape of electro-magnetic interference and maintains air flow through the chassis.
This section explains how to remove and replace the midplane. The first procedure tells you how to learn the chassis ID, which is stored in EEPROM on the midplane. You must find and record this number before removing the old midplane so you can store it in the EEPROM on the new midplane. (The EEPROMs are located on the back of the midplane near the middle of the top edge; the positions are labelled u1 and u2.)
Estimated time to complete these procedures: two hours
The chassis ID should be recorded in each node's maintenance log. If the chassis ID isn't in the log, you can use this procedure to learn it, provided the EEPROMs on the midplane are healthy.
Step 2 Run the sysver command at the bash prompt:
Step 3 In the resulting display, locate the chassis ID. (If you have two switch cards, the chassis ID should be the same for both.) The chassis ID is displayed in hex and looks something like this example:
Record the pair of digits following each 0x. For the example above, you would record:
If you have changed the modem init string and modem password from the factory defaults, record them as well, as you will need to restore them later.
Step 2 Cut off the power to the system by detaching the power cord or turning off the power feed.
Step 3 Remove all the cards from the front of the chassis.
Step 4 From the rear of the chassis, unseat all the access cards and disconnect the console/modem assemblies. (It's not necessary to remove these items from the chassis.)
Step 5 From the rear of the chassis, remove the NP access card(s). Behind each NP access card, at the bottom of the slot, you'll see a ribbon cable attached to the midplane. Disconnect each ribbon cable. (If you have two NPs—and thus two ribbon cables—you should label the cables so you can reconnect them properly later.)
Step 6 From the rear of the chassis, remove the lower power tray. (See "Replacing a Power Tray" section for instructions.)
Step 7 Reach into the lower power tray slot and unplug the two power connectors (J15 and J16) from the midplane power tab, as shown in Figure 7-12.
Step 8 From the front of the chassis, remove four #2 Phillips-head screws from the top and bottom of the frame surrounding the card cage. (See Figure 7-13.) The screws are located behind slots 3 and 7.
Step 9 Reach into the chassis and remove two #2 Phillips-head screws from the top and bottom corners of left side of the midplane. (Figure 7-13 shows the screw positions.) The midplane is now disconnected from the chassis.
Step 10 Pull the card cage (with the midplane still attached at the rear) out of the chassis. As you remove this assembly, rotate it slightly clockwise to allow the power tab to clear the chassis. (See Figure 7-14.)
Step 11 To separate the midplane and card cage, remove all the Phillips-head screws from the back of the midplane.
Step 2 Slide the midplane-card cage assembly into the chassis, holding the assembly so that the midplane enters with the power tab foremost. When the power tab clears the corner of the disk housing, rotate the assembly counterclockwise until it fits snugly.
Step 3 Replace the two screws at the left corners of the midplane.
Step 4 Replace the four screws in the top and bottom of the frame surrounding the card cage.
Step 5 Reinsert the line cards, NPs and switch cards into the chassis.
Step 6 From the rear of the chassis, reach into the lower power tray slot and reconnect plugs J15 and J16 to the midplane power tab. (The plugs are keyed to their sockets so that they cannot be connected incorrectly.)
Step 7 Replace the lower power tray.
Step 8 Locate the ribbon cable(s) behind the NP access card(s) and reconnect the cable(s) to the midplane. (There is one cable per NP.)
Step 9 Reconnect the console/modem assemblies and reseat the access cards; be sure to tighten all the retaining screws.
Note When you complete this procedure, check the front and back of the system to see that all boards, disks, blowers, bulkheads, filler panels, and covers are in place and firmly screwed to the chassis frame. When all these items are in place, they form an enclosure that prevents the escape of electro-magnetic interference and maintains air flow through the chassis.
This procedure differs depending on whether your system has one switch card or two. If you have two switch cards, you need only type two commands to program the two EEPROMs. If you have just one switch card, you must move the card from one switch slot to the other between commands. This is necessary because each midplane EEPROM is connected to one switch card slot, and you can't program the EEPROM without a switch card in the slot. It is very important to have the same chassis ID on both midplane EEPROMs.
Step 2 Attach a terminal to the console port of the active switch card.
Step 3 The terminal connects to the TCS hub. At the prompt, type the following command, replacing the placeholder at the end with your chassis ID, which you recorded at the beginning of this section:
Note This command assumes you are programming the EEPROM for switch slot A. If you wish to begin with slot B, begin the command with set sb instead of set sa.
Step 4 To verify that you entered the chassis ID in slot A correctly, type the following command and check the chassis ID in the resulting display. (If you just set the chassis ID for slot B, begin this command with show sb instead of show sa.)
Step 5 If this system contains two switch cards, skip to step 8. If this system contains only one switch card, type the following:
Note Again, this command assumes you are programming the EEPROM for switch slot A. If you wish to begin with slot B, begin the command with set sb instead of set sa.
Step 6 Remove the switch card from the chassis and put it into the other switch card slot.
Step 7 From the rear of the chassis, move the console/modem assembly (keeping the console connection intact) to the other switch card slot. Note that when you return to the console, the TCS hub prompt changes from A to B (or from B to A, if you started with switch slot B). Press [Return] to display the new prompt.
Step 8 At the console, type the following:
Note This command assumes you are programming the EEPROM for switch slot B. If you are doing slot A, begin the command with set sa instead of set sb.
Step 9 To verify that you entered the chassis ID in slot B correctly, type the following command and check the chassis ID in the resulting display. (If you just set the chassis ID for slot A, begin this command with show sa instead of show sb.)
Step 10 If the modem initialization string and modem password stored in midplane EEPROMs have not been changed from the factory defaults, skip to the next step. If the modem information has been changed, you must bring the new midplane up to date. Refer to the LightStream 2020 Operations Guide for instructions on programming the modem init string and password into the EEPROMs on the new midplane.
Step 11 To reset the system with the new EEPROM information, use the command shown below. Replace the <slot#> with the slot number of the NP (1 or 2). If your system has two NPs, repeat this command for the second one.
Step 12 You can now bring the system up. To connect to the primary NP, use the command shown below. Replace the <slot#> with the slot number of the active NP in the system (1 or 2).
This section tells you how to remove and replace a console/modem assembly.
A console/modem assembly is located behind each switch card, at the rear of the chassis. The assembly consists of a bulkhead with console and modem ports mounted on it, with cables to connect to the midplane.
Step 2 Pull the bulkhead away from the chassis (see Figure 7-15). You'll see a ribbon cable that attaches the bulkhead to the midplane; disconnect it at the midplane end.
Step 2 Line up the bulkhead against the card cage and tighten the top and bottom retaining screws.
Note When you complete this procedure, check the front and back of the system to see that all boards, disks, blowers, bulkheads, filler panels, and covers are in place and firmly screwed to the chassis frame. When all these items are in place, they form an enclosure that prevents the escape of electro-magnetic interference and maintains air flow through the chassis.
This section tells you how to remove and replace LightStream fantails, which provide connectors for data cables on low-speed (X.21, V.35 and RS-449) lines. Figure 7-16 shows how fantails are connected to access cards.
Step 2 Remove the fantail cable (or cables, in the case of an X.21 fantail) from the back of the fantail, leaving the cable(s) attached to the access card in the chassis.
Step 3 Using a 5/16-inch slotted-tip screwdriver, unscrew the mounting screws and remove the fantail from the equipment rack.
Step 2 Attach the fantail cable(s) to the back of the fantail.
Step 3 Using a 5/16-inch slotted-tip screwdriver and the mounting screws and washers provided, attach the fantail to the equipment rack.
Step 4 Label the fantail with the slot number or names of the line and access cards that it is connected to.
Step 5 Reconnect any data cables that were disconnected to remove the old fantail.
This section explains how to shut down a LightStream switch gracefully, which involves rebooting the NPs. You may need to use this shutdown procedure before performing other procedures in this manual.
Two shut-down procedures are provided: the first is for switches with two NPs, the second for switches with one NP. Following the shut-down procedures are instructions for returning to service.
In a system with two NPs, you must reboot the backup NP before you reboot the active NP. (If you reboot the active NP first, the backup takes over and the system continues to operate.)
Step 2 Log in to the root account on the switch you want to shut down.
Step 3 To determine which NP is active (primary), start the CLI and use the command show chassis general and look for Slot of Primary NP in the resulting display. This is the NP you'll reboot last.
Step 4 To log into the backup NP (the one whose slot number was not displayed in step 3), do the following:
Type `. to get a TCS hub prompt.
At the TCS hub prompt, use connect <slot#> to connect to the backup NP. The example below assumes that you are connecting to the NP in slot 2.
Step 5 From the bash# prompt, type
Step 6 Type `. to return to the TCS hub.
Step 7 At the TCS hub prompt, use connect <slot#> to connect to the active NP. The example below assumes that you are connecting to the NP in slot 1.
Step 8 If necessary, type quit to exit from CLI and get a bash prompt.
Step 9 From the bash# prompt, type
Step 10 You can now turn off the power.
Use this procedure to shut down a system with one NP, or to shut down one NP in a redundant system where you want the other NP to continue operating.
Step 2 Log in to the root account on the switch you want to shut down.
Step 3 From the bash# prompt, type
Step 4 You can now turn off the power.
If you turned off the power, you can return the system to service by turning the power on again.
If you did not turn off the power, use the command shown below at the TCS hub to bring the system back to service. Replace slot# with the slot number of the NP card (1 or 2):
Note that you must issue the reset command to both NPs in a redundant system.
(An expansion module includes everything needed to add a particular kind of card to an existing system.)
At least one part number is listed for each item. For many items, two part numbers are provided: the LightStream-internal manufacturing number, and the order number.
| Caution Before removing any components from the chassis, read the safety instructions in the "Electrostatic Discharge (ESD) Protection" section. Removing components when you are not grounded can damage the system. |
Table 8-1 FRUs and Part Numbers
2422865-0X2
2422865-0X2
2X = 2 for 4-ft. cables, 3 for 8-ft. cables, or 4 for 12-ft. cables.
Component
Manufacturing Number
Order Number
1Base system is a chassis with a switch card, midplane, and blowers only.
IP Addresses ² Address Masks ² Subnetting
This appendix provides some background information for readers who are not familiar with the considerations involved in assigning IP addresses to networks and hosts. For additional information, see:
An IP address is a 32-bit identifier assigned to hosts that use the Internet Protocol. The address is represented by four octets (8-bit fields). In decimal form, an IP address comprises four fields separated by dots, where each field contains a value in the range 0-255. (This is called dotted decimal notation.)
An IP address consists of two parts. The first part of the address, called the network number, identifies a network on the internet; the remainder, called the host ID, identifies an individual host on that network. Historically, there are three types of addresses, class A, class B, and class C, as follows:
Example: 26.4.0.1, for host 4.0.1 on net number 26.
Example: 192.15.28.16, for net number 192.15.28, host 16.
Each host ID must be unique within a given network, and each network number must be unique within a given internet. Host IDs are assigned by the administrator of the network. The network number is assigned by the administrator of the internetwork. For a public network on the Internet, you must obtain a network number assigned by the Network Information Center (NIC).
An address mask determines which portion of an IP address identifies the network and which portion identifies the host. Like the IP address, the mask is represented by four octets. (An octet is an 8-bit binary number equivalent to a decimal number in the range 0-255). If a given bit of the mask is 1, the corresponding bit of the IP address is in the network portion of the address, and if a given bit of the mask is 0 the corresponding bit of the IP address is in the host portion.
The following illustration shows the mask 255.255.255.0 in both decimal and binary form, aligned with the class C address 192.15.28.16, also in both decimal and binary:
| Network | Host | |||
|---|---|---|---|---|
If a field of the network address is entirely used for the network number, then the corresponding field of the mask has the decimal value 255 (binary 11111111), and if an address field is entirely used for the host ID, then the corresponding field of the mask has the decimal value 0, as follows:
| Decimal Value in Field of Mask | Binary Value in Field of Mask | Used to Identify: |
|---|---|---|
Accordingly, the address masks for the three classes of networks described above are as follows:
The boundary between the network portion and the host portion of IP addresses can be shifted by replacing the first zero in the host portion with a different number. By this means, more than one physically distinct network can be managed under a single class A, class B, or class C network number.
When a modified address mask is used to partition a network into subnets, it is called a subnet mask. The simplest subnet masks for the three classes of networks are as follows, where n is a number other than zero:
(The other zeros in the mask for a class A or class B address can also be replaced by a different number, but for simplicity we will ignore that possibility here.)
Note Do not be confused by use of the term subnetwork for the individual networks that make up an internetwork. Each "subnetwork" in this latter sense has a different network number, but when a network is partitioned into subnets by a subnet mask, they all have the same network number.
A simple example of subnetting partitions a class B network by setting the third octet of the mask to 255, that is, by using the address mask of a class C network. The following illustration shows the mask 255.255.255.0 in both decimal and binary form, aligned with the class B address 128.89.2.26, also in both decimal and binary:
| Network | Host | |||
|---|---|---|---|---|
Outside the network, packets are routed to net 128.89. It is only when packets reach a router that is directly connected to the network that routing software takes account of the subnet mask. The mask partitions net 128.89 into 254 subnets (numbers 0 and 255 are reserved), each supporting up to 254 hosts.
Other values than 255 may be used, however, and obviously 255 cannot be used in the host field of a class C network. The mask value n that is substituted for 0 must be one of the decimal values shown in the first column of the following table:
| Decimal Value | Binary Value | Subnets | Hosts |
|---|---|---|---|
Note Any number other than these results in discontinuous strings of 1s and 0s, with undesirable consequences for software that interprets addresses subnetted under this mask.
Decimal value 254 (binary 11111110) is omitted from the above table because it allows 0 hosts. Decimal value 0 (binary 00000000) and decimal value 128 (binary 10000000) are omitted because they allow 0 subnets.
The reserved network numbers and host IDs that were subtracted from 2n in columns 3 and 4 are as follows:
For example, the address 192.15.28.0 refers to class C network 192.15.28.
For example, in a class C network with no subnetting, the address 0.0.0.16 refers to host 16 on "this" network. (Address 0.0.0.16 refers to host 0.16 in a class B net, or to host 0.0.16 in a class A net.)
For example, within the class C network 192.15.28, with no subnetting, the address 192.15.28.255 broadcasts to all hosts in this network.
The range 224.0.0.0 through 255.255.255.254 is reserved for experimental use (address classes D and E), and 255.255.255.255 is the universal broadcast address.
You know how to partition a network with a subnet mask, but you may not be able to determine which IP addresses fall in each of the subnets. An example will clarify this.
Suppose you want to partition class C network 192.15.28 into five physical networks. Look in the "Subnets" column of the table in the section "Subnet Masks." The closest approximation is to configure six subnets. To do this, enter 224 in the last field of the subnet mask. Thus, 255.255.255.224 is the subnet mask that you must specify to partition a class C network into six subnets.
The following illustration shows the mask 255.255.255.224 in both decimal and binary form, aligned with the class C address 192.15.28.16, also in both decimal and binary:
| Network | Host | ||||
|---|---|---|---|---|---|
By putting 224 in the last field of the mask, you tell the software to use the leftmost three bits of the last octet (the high-order bits) to differentiate subnets. In an 8-bit field, in binary notation, the high-order 3 bits naturally partition the range of numbers (and the range of possible IP addresses) into eight equal parts, corresponding to the eight binary numbers 000 through 111.
If you are not familiar with manipulating binary numbers and this is not clear to you, please refer to the following table:
| Decimal Range | Binary Range | High Bits |
|---|---|---|
The high-order three bits of the IP address field thus partition the full range of 256 possible 8-bit numbers that can appear in the last octet of an IP address into eight groups of 32 addresses (256/8 = 32), as shown in the following table:
| IP Addresses | Subnet | High 3 Bits |
|---|---|---|
However, addresses reserved for broadcast and for "this net" must be excluded. These are as follows:
Suppose we want to subnet class B network 128.89 into six subnets. Referring to the "Decimal Value" column of the table in the section "Subnet Masks" we see that the number to substitute for n is 224 if we want six subnets. The mask is 255.255.224.0 with six subnets. Recall that the mask is 255.255.0.0 with no subnetting. These two masks have the following binary representations:
With the subnet mask 255.255.224.0, the first three bits of the third octet are included in the network identifier. As we saw at the end of the previous section, we must divide 256 by the number of subnets to get the ranges of addresses for each subnet. The mask divides the range of numbers 0-255 that can appear in the third field of an IP address into eight ranges of 32 numbers: 0-31, 32-64, and so on.
Because there are 11 bits in all for the host ID (8 in the last field plus 3 in the third field), the mask 255.255.128.0 provides for 2046 (211 -2) hosts in each of the eight subnets. The ranges of addresses for each subnet are as follows:
| IP Addresses | Subnet | First 3 Bits |
|---|---|---|
Subnet 0 is reserved because the addresses 128.89.0.1 - 128.89.31.254 have 000 as the high-order bits. Subnet 7 is reserved because the addresses 128.89.224.1 - 128.89.255.254 have 111 as the high-order bits.
The first address in each subnet address range is reserved to refer to the subnet as a whole because the last five bits of the address field are zeros, and the last address in each subnet address range is reserved as a broadcast address for the subnet because the last five bits of the address field are ones. For example, in subnet 3, 128.89.96.0 is the subnetwork address and 128.89.127.255 is the broadcast address.
Posted: Thu Jan 23 00:29:31 PST 2003
All contents are Copyright © 1992--2002 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.
.
