This procedure is for installing or replacing a Terabit Switch Router Series II (TSR II) server module. Before beginning this procedure, carefully inspect the package to ensure no damage occurred during shipping or delivery. If you suspect any possible damage to any field replacement unit, contact Customer Service immediately.
Tools Needed
You will need a 1/2-inch flat-head screwdriver.
Support Services
To obtain information on customer service and training, there are three ways to contact Avici Customer Service:
- Phone:
United States Support: 877-292-8424 (TSR-BY-AVICI)
International Support: 01-978-964-2350
- E-mail: support@avici.com
- World Wide Web: http://www.avici.com
Server Modules
The TSR II offers two identical servers, the primary (active) and secondary (passive) server. The TSR II only accepts a "red triangle" server. A red triangle server is identified by the red triangle located at the top of the module. Refer to Table 1 for a list of the available server types.
NOTE A TSR II only accepts a red triangle server. Do not try to insert a red circle server, blue server, or green server into an TSR II.
Table 1. Avici Server Modules Type SSR Series II TSR Red server
--
--
Yes
Blue server
--
--
Yes
Red triangle server
--
Yes
Yes
Green server
Yes
--
--
Each red triangle server provides a 300 Mhz PowerPC 604e CPU, 576 Mbytes of memory (64 Mb on the baseboard and 512 Mb of add-on PMC memory), and 32Kbytes of NVRAM for maintaining configuration and software images.
The red triangle server also supports five 10/100BaseT Ethernet ports and one DB-9 console port connection (see Figure 1).
Each red triangle server resides in a module enclosure together with a power conversion card, persistent file storage, and a pair of solid state disks.
Physically identical to the primary server, the passive server is designed and implemented to take over in the event the primary server becomes unusable. The servers connect to the bay controllers via the server connector panel. The server's ETH 3 and ETH 4 ports connect to the server connector panel and these connections lead to an Ethernet repeater located on the bay controllers. This repeater allows the bay controller and servers to look like one logical LAN.
Figure 1. Server Ethernet Ports
The primary and secondary servers contain two heartbeat connections for redundancy. The ETH 3 and ETH 4 multicast connections are required to form the first peering session. The first heartbeat is a multicast message over the bay controller network. The second heartbeat is over the server's ETH 0 port and this unicast connection requires an external network. The two heartbeats ETH 3/ETH 4 and ETH 0 work in unison and begin as soon as you have established an active/backup pair also known as "final" state.
NOTE The server's ETH 0 port provides a redundant warm stand-by connection between the servers in the event the primary warm server communication path via ETH 3 and ETH 4 goes down.
If a server stops receiving heartbeats (multicast or unicast) a trap will be immediately sent (within one second) stating that the communication (primary or secondary) is no longer available. After four minutes of non-connection to the other server via both paths, the server will send a trap notifying that the server is gone and the central office critical alarm is activated. The central office alarm is based on loss of communication with the bay controller. Because every server must register with the bay controller and constantly update itself with the bay controllers, servers must see each other; it is the same physical link/protocol. Warm stand-by relies on the bay controller to create the central office alarm if a server goes down. After 5 minutes of no communication on both paths, the backup server will assume the active role.
For server software configuration details, refer to the IPriori Software Configuration Guide (Vol. 1). When configuring the servers, keep in mind that the server configured with the lowest ID number will be the active or primary server.
Removing and Installing Server Modules
NOTE Before you perform these procedures you must remove the EMI front cover (if installed) as outlined in the TSR II Hardware Install Guide chapter entitled "EMI Front Covers Removal."
Server Modules may be installed in slots S1, S2, S3, and S4. (Which correspond to the right most slots of shelves 1, 2, 3, and 4 respectively).
Server Attached Modules
In each TSR bay, the server attaches to one or two router modules known as Server-Attached Modules (SAMs). The power receptacle on the server module plugs directly into three power pins on the inside of the system near the backplane and does not plug into a module slot in the backplane.
Removal of the server module is detected by the SAM module after the SAM attempts to communicate with the server and receives no response. The SAMs act as intermediaries by providing access to all router modules. It is necessary to re-cable the connection to the SAM when replacing the server. When removing a server module you must do a controlled shut down. Refer to IPriori Software Configuration Guide (Vol.1) for information about removing a module.
NOTE You may choose any two modules to act as your SAM modules. For maximum fault tolerance, we recommend that the primary and backup SAM module be on different shelves.
Population Rules for Server Modules
In a TSR II Full Bay configuration, the primary and secondary servers can be installed in any of the four server slots. It is recommended that the primary server be installed in S4 and the secondary server be installed in S2.
In a TSR II Split Bay configuration, the upper bay servers populate S1 and S2 only; the lower bay servers populate S3 and S4 only.
NOTE Do not insert router modules into a dedicated server module slot as this may damage the VDHM connector. If you accidentally insert a router module into a dedicated server slot, you must inspect the VDHM connector for damage prior to inserting the module into a module slot.
Removing the Server Module
NOTE If you are installating the Server Module for the first time, skip to "Installing the Server Module" on page 7.
Prior to removing the server module take note of the position of the interface cables on the module enclosure faceplate and the color of the label located on the top of the server module. The label color and shape (red triangle for TSR II) indicates which module can be inserted into a particular slot in the shelf. If you have a server module with the wrong indicator mark, call Support Services.
PROCEDURE: Use the following steps to remove the server module from the TSR bay shelf:
CAUTION (1) Risk of electrostatic damage. You must wear antistatic wrist strap or equivalent protection to avoid damaging electronics parts.
CAUTION (2) Within five minutes of removal of a module, a replacement module or a filler module must be installed in the empty slot.
Step 1 Push on the server module where instructed. The server door opens and displays the module cable connections (see Figure 2 and Figure 3).
Figure 2. Server Module Door
Step 2 Record the Ethernet and console cable connections for each port on a piece of paper.
Step 3 Disconnect the cables from the interface ports on the module faceplate (see Figure 3).
Figure 3. Server Module Faceplate
Step 4 Using a 1/2-inch flat-blade screwdriver, turn the two captive screws on the server faceplate counter clockwise to loosen. The server module lock latch releases.
Step 5 Carefully pull the server module straight out to release it from the backplane and remove it from the shelf (see Figure 4).
Figure 4. Server Module Removal
Step 6 Place the removed server module in the static-proof bag.
Installing the Server Module
NOTE If you are replacing the Server Module go to "Removing the Server Module" on page 5.
PROCEDURE: Use the following procedure to install the server module to the TSR II shelf:
CAUTION (3) Risk of electrostatic damage. You must wear a grounded antistatic wrist strap or equivalent protection to avoid damaging electronics parts.
Step 1 Remove the server module from its static-proof bag.
Step 2 Check that the door of the server module is closed. If the door is open, close it.
Figure 5. Server Module Faceplate
Step 3 Check the color indicator on the top of the module to determine if it is the right type for this slot (red triangle). If it is not the correct color, contact Support Services (see Figure 6).
NOTE TSR II only accepts RED Triangle Server Modules An unmodified RED Dot server modules will not fit TSR II. The modification involves a tab built into the card cage which prevents any unmodified RED Dot Server module. (Note that the RED triangle server is backwards compatible to M1 TSR).
Figure 6. Red Triangle Server Module Color Indicator
Step 4 Position the metal tabs of the lock latch release levers under the lip of the server.
Step 5 Align the module with the card guides of the slot and slide the server module into the slot (see Figure 7).
Figure 7. Server Module Installation
.
Step 6 Using a 1/2-inch flat-blade screwdriver, turn the captive screws on the server faceplate clockwise to tighten, continuing to turn carefully until screw rotation is no longer possible. This ensures full engagement. The server module locks into place.
Installing Server Module Cables
Each server module supports five Ethernet ports (ETH 0-4) and one female console (DB-9) port. The Ethernet ports provide for interconnection to the Server-Attached Modules (SAM) within the bay and to the network management system via the bay controllers. The console port provides for interconnection to a console terminal for access to CLI configuration.
Redundant Bay Controllers
The TSR II Full Bay configuration offers server to bay controller fault tolerance via a connection from both the primary and secondary server's ETH 3 and ETH 4 ports to the bay controller network on the server connector panel. For Full Bay configuration, the primary server's ETH3 and ETH4 ports connect to the bay controller network via the server connector pannel. A single ETH3 connection provides connectivity to the bay controller network for the secondary server.
These server connector panel ports can be found on the Server Connector Panel located between shelves 2 and 3 and are labeled BCx/y where x specifies the bay controller (1 or 2) and y specifies the connection port (1-3) (see Figure 8).
Figure 8. Server Connector Panel
To further illustrate the recommended Full Bay ETH 3 and ETH 4 connections on the server connector panel for both the primary and secondary servers, please refer to Figure 9. This logical view depicts the recommended port hook ups for the primary server in slot S4 (server ETH3 to server connector panel BC1/1 and server ETH4 to server connector panel BC2/1) and for the secondary server in slot S2 (server ETH3 to server connector panel BC1/2 and server ETH4 to server connector panel BC2/2). The dotted lines illustrate the connections between each of the server connector panel ports to the bay controllers.
Figure 9. Server to Server Connector Panel Port Connections for the Full Bay Configuration
NOTE IPriori determines whether a server is primary or secondarty based upon server ID not the server slot location. The primary server is the lower of the two server IDs.
In order to maintain bay controller to server redundancy, it is desirable to connect one of the two server ports to each side of the server connector panel as the left-hand three ports of the server connector panel connect to the left bay controller (BC1) and the right-hand three ports connect to the right bay controller (BC2). This minimizes shared components in each path.
Table 2 specifies the recommended port connections for each server.
Table 2. Server Ethernet to Server Connection Panel Port Configurations (Full Bay) Server ETH 3 ETH 4 Primary
BC 1/1
BC 2/1
Secondary
BC 1/2
BC 2/2
Server Set-Up for TSR II Full Bay Configuration
Each server module in the Full Bay configuration attaches to two router modules, also called Server-Attached Modules (SAMs). Any router module can serve as a SAM. The dual SAM system provides system redundancy.
PROCEDURE: Use the following steps to install the Ethernet and console cables for the server modules. Refer to Figure 10 for an illustration of the cable and connector types described in these procedures.
Figure 10. Server Module Cable Connections
Step 1 Primary ETH 0 - Attach an RJ-45 Ethernet cable from this connector on the primary server module (S4) to the remote network management system within the central office.
Step 2 Secondary ETH 0 - Optionally attach an RJ-45 Ethernet cable from this connector on the secondary server module (S2) to the remote network management system within the central office. This connection will have no affect upon network management unless the secondary becomes the primary. It does provide a redundant communication between servers should both the ETH3 and ETH4 connections go down.
Step 3 Primary CONSOLE - Attach a DB-9 RJ-45 adapter from this connector on the primary server module (S4) to one end of the UTP cable with RJ-45 connectors on each end. Take the RJ-45 connector on the other end of the UTP cable and plug it into the female adapter, which can plug into a console terminal (PC) port, or connection of your choice. There is no need to configure a secondary module unless it should become the primary due to a primary failure. Cabling a console port for the secondary is therefore optional.
Step 4 Primary ETH 1 - Attach an RJ-45 Ethernet cable from this connector on the primary server module (S4) to the RJ-45 connector located in the AUX tray of any other router module. (Slide out the AUX tray to make the connection.) This router module is the primary SAM (see Figure 11).
Step 5 Secondary ETH 1 - Attach an RJ-45 Ethernet cable from this connector on the secondary server module (S2) to the RJ-45 connector located in the AUX tray of any other router module (slide out the AUX tray to make this connection). This router module will become the primary SAM should this secondary server become primary (see Figure 14).
NOTE You may choose any two modules per server to act as your SAM modules. For maximum fault tolerance, we recommend that the primary and backup SAM module be on different shelves.
Step 6 Primary ETH 2 - Attach an RJ-45 Ethernet cable from this connector on the primary server (S4) to the RJ-45 connector located in the AUX tray of any other router module. Slide out the AUX tray to make the connection.
- This router module is referred to as the secondary SAM (see Figure 11).
Step 7 Secondary ETH 2 - Attach an RJ-45 Ethernet cable from this connector on the secondary server module (S2) directly to the connector located in the AUX tray of any router module. (Slide out the AUX tray to make this connection.) This router module will become the secondary SAM should this secondary server become primary (see Figure 11).
Figure 11. RJ-45 Ethernet Cable Connection
Step 8 Open the server connector panel cover to expose the server connector panel (see Figure 12).
Step 9 Primary ETH 3 - Attach the RJ-45 Ethernet cable from the primary server module (S4) to the appropriate server connector panel port as depicted in Figure 9 "Server to Server Connector Panel Port Connections for the Full Bay Configuration". Each of the six server connector panel ports is connected internally to the bay controller.
Step 10 Secondary ETH 3 - Attach the RJ-45 Ethernet cable from the secondary server module (S2) to the appropriate server connector panel port as depicted in Figure 9 "Server to Server Connector Panel Port Connections for the Full Bay Configuration".
Step 11 Primary ETH 4 - Attach the RJ-45 Ethernet cable from the primary server module (S4) to the appropriate server connector port as depicted in Figure 9 "Server to Server Connector Panel Port Connections for the Full Bay Configuration". Each of the six server connector panel ports is connected internally to the bay controller.
Step 12 Secondary ETH 4 - Attach the RJ-45 Ethernet cable from the secondary server module (S2) to the appropriate server connector port as depicted in Figure 9 "Server to Server Connector Panel Port Connections for the Full Bay Configuration".
Figure 12. Server Panel Ethernet Connections
Server Set-Up for TSR II Split Bay Configuration
The server modules in the Split Bay configuration attach to dual SAMs. Any router module can serve as a SAM.
NOTE Because of the six port limitation of the server connector pannel, with Split Bay you retain redundancy for the primary server to bay controller connection (four of the six ports are used), but loose redundancy on the secondary server (two ports remain to connect each secondary server to a single bay controller).
To complete the replacement of the server module all cables must be reconnected to the replacement server module.
Each server module supports five Ethernet ports (ETH 0 - ETH 4) and one female console (DB-9) port. The Ethernet ports provide for interconnection to other modules within the bay and to the network management system. The console port provides for interconnection to a console terminal for use when configuring via the CLI.
Figure 13. Server to Server Connector Panel Port Connections for the Split Bay Configuration
Table 3 specifies the recommended port connections for each server.
Upper Router (S1 and S2)
PROCEDURE: Use the following steps to install the Ethernet and console cables for the server modules in the upper router:
Step 1 Primary ETH 0 - Attach an RJ-45 Ethernet cable from this connector on the primary server module (S2) to the remote network management system within the central office.
Step 2 Secondary ETH 0 - Optionally attach an RJ-45 Ethernet cable from this connector on the secondary server module (S1) to the remote network management system within the central office. This connection will have no affect upon network management unless the secondary becomes the primary. It does provide a redundant communication between servers should both the ETH3 and ETH4 connections go down.
Step 3 Primary CONSOLE - Attach a DB-9 RJ-45 adapter from this connector on the primary server module (S2) to one end of the UTP cable with RJ-45 connectors on each end. Take the RJ-45 connector on the other end of the UTP cable and plug it into the female adapter, which can plug into a console terminal (PC) port, or connection of your choice. There is no need to configure a secondary module unless it should become the primary due to a primary failure. Cabling a console port for the secondary is therefore optional.
Step 4 Primary ETH 1 - Attach an RJ-45 Ethernet cable from this connector on the primary server module (S2) to the RJ-45 connector located in the AUX tray of any other router module (slide out the AUX tray to make this connection). This router module is referred to as the primary SAM (see Figure 14).
Step 5 Secondary ETH 1 - Attach an RJ-45 Ethernet cable from this connector on the secondary server module (S1) to the RJ-45 connector located in the AUX tray of any other router module (slide out the AUX tray to make this connection). This router module will function as the primary SAM should this secondary server become primary (see Figure 14).
NOTE You may choose any two modules to act as your SAM modules. For maximum fault tolerance, we recommend that the primary and backup SAM module be on different shelves for power redundancy and separate columns for communications.
Figure 14. RJ-45 Ethernet Cable Connection
Step 6 Primary ETH 2 - Attach an RJ-45 Ethernet cable from this connector on the primary server module (S2) to the RJ-45 connector located in the AUX tray of any router module (slide out the AUX tray to make this connection). This router module is referred to as the secondary SAM (see Figure 14).
Step 7 Secondary ETH 2 - Attach an RJ-45 Ethernet cable from this connector on the secondary server module (S1) directly to the connector located in the AUX tray of any router module. (Slide out the AUX tray to make this connection.) This router module will become the secondary SAM should this secondary server become primary (see Figure 14).
Step 8 Open the server connector panel cover to expose the server connector panel (see Figure 12).
Step 9 Primary ETH 3 - Attach the RJ-45 Ethernet cable from this connector on the primary server module (S2) to the appropriate server connector panel port as specified in Figure 13.
Step 10 Secondary ETH 3 - Attach the RJ-45 Ethernet cable from this connector on the secondary server module (S1) to the appropriate server connector panel port as specified in Figure 9.
Step 11 Primary ETH 4 - Attach the RJ-45 Ethernet cable from the primary server module (S2) to the appropriate server connector port as depicted in Figure 13. Each of the six server connector panel ports is connected internally to the bay controller.
Step 12 Secondary ETH 4 - This server port is unused.
Lower Router (S3 and S4)
PROCEDURE: Use the following steps to install the Ethernet and console cables for the server modules in the lower router:
Step 1 Primary ETH 0 - Attach an RJ-45 Ethernet cable from this connector on the primary server module (S4) to the remote network management system within the central office.
Step 2 Secondary ETH 0 - Optionally attach an RJ-45 Ethernet cable from this connector on the secondary server module (S3) to the remote network management system within the central office. This connection will have no affect upon network management unless the secondary becomes the primary. It does provide a redundant communication between servers should both the ETH3 and ETH4 connections go down.
Step 3 Primary CONSOLE - Attach a DB-9 RJ-45 adapter from this connector on the Primary server module (S4) to one end of the UTP cable with RJ-45 connectors on each end. Take the RJ-45 connector on the other end of the UTP cable and plug it into the female adapter, which plugs into the console terminal (PC) port.
Step 4 Primary ETH 1 - Attach an RJ-45 Ethernet cable from this connector on the primary server module (S4) to the RJ-45 connector located in the AUX tray of any router module. (Slide out the AUX tray to make this connection.) This router module is the primary SAM (see Figure 14).
Step 5 Secondary ETH 1 - Attach an RJ-45 Ethernet cable from this connector on the secondary server module (S3) to the RJ-45 connector located in the AUX tray of any other router module (slide out the AUX tray to make this connection). This router module will function as the primary SAM should this secondary server become primary (see Figure 14).
NOTE You may choose any two modules to act as your SAM modules. For maximum fault tolerance, we recommend that the primary and backup SAM module be on different shelves for power redundancy and separate columns for communications.
Step 6 Primary ETH 2 - Attach an RJ-45 Ethernet cable from this connector on the primary server module (S4) directly to the connector located in the AUX tray of any router module. (Slide out the AUX tray to make this connection.) This router module is the secondary SAM (see Figure 14).
Step 7 Secondary ETH 2 - Attach an RJ-45 Ethernet cable from this connector on the secondary server module (S3) directly to the connector located in the AUX tray of any router module. (Slide out the AUX tray to make this connection.) This router module will become the secondary SAM should this secondary server become primary (see Figure 14).
Step 8 Open the server connector panel cover to expose the server connector panel (see Figure 12.
Step 9 Primary ETH 3 - Attach the RJ-45 Ethernet cable from this connector on the primary server module (S4) to the appropriate server connector panel port as specified in Figure 13.
Step 10 Secondary ETH 3 - Attach the RJ-45 Ethernet cable from this connector on the secondary server module (S3) to the appropriate server connector panel port as specified in Figure 13.
Step 11 Primary ETH 4 - Attach the RJ-45 Ethernet cable from the primary server module (S4) to the appropriate server connector port as depicted in Figure 13.
Copyright © 2001
Avici Systems Inc.
Avici® and TSR® are registered
trademarks of Avici Systems Inc.
IPriori™ is a trademark of Avici Systems Inc.
Source File Name: 02131-02_revAA.fm
HTML File Name: 02131-02_revAA.html
Last Updated: 10/24/01 at 13:55:25
Please email suggestions and comments to: doc@avici.com