AlphaServer GS80/160/320 System Management Console Installation Guide Order Number: EK–GSCON–IN. E01 This manual provides installation and configuration instructions for the system management console. This manual is for service providers, managers, and operators of Compaq AlphaServer GS80/160/320 systems.
Revised, February 2002 © 2002 Compaq Computer Corporation. Compaq, the Compaq logo, Compaq Insight Manager, AlphaServer, StorageWorks, and TruCluster Registered in U.S. Patent and Trademark Office. OpenVMS, Tru64, and Carbon Copy are trademarks of Compaq Information Technologies Group, L.P. in the United States and other countries. Acrobat is a trademark of Adobe Systems Incorporated. ConsoleWorks is a trademark of TECSys Development Incorporated. Java is a trademark of Sun Microsystems, Inc.
Japanese Notice Canadian Notice This Class A digital apparatus meets all requirements of the Canadian Interference-Causing Equipment Regulations. Avis Canadien Cet appareil numérique de la classe A respecte toutes les exigences du Règlement sur le matériel brouilleur du Canada. European Union Notice Products with the CE Marking comply with both the EMC Directive (89/336/EEC) and the Low Voltage Directive (73/23/EEC) issued by the Commission of the European Community.
Contents Preface............................................................................................................ xiii Chapter 1 Overview and Preparation 1.1 1.2 1.3 1.4 System Management Console Overview ............................................... 1-2 Installation Flow ................................................................................... 1-4 Check the Installation Kits ................................................................... 1-8 Set Up the SMC .....................
4.3 4.4 Connect the Network Hub to the SMC ............................................... 4-10 Cable the SMC to the Corporate Network .......................................... 4-12 Chapter 5 5.1 5.1.1 5.1.2 5.1.3 5.1.4 5.2 5.3 5.4 5.5 Cable New AS System to New Terminal Server ................................... 5-2 Power New AS System to Vaux ...................................................... 5-2 Cable New AS System to New Terminal Server............................. 5-4 Record the Connections....
.6.1 7.6.2 7.6.3 7.7 7.7.1 7.7.2 7.8 Terminal Server ........................................................................... 7-18 Open Access Server Manager ....................................................... 7-18 Test the Connection ...................................................................... 7-20 Configure Access Server Manager ................................................ 7-22 Update Configuration: Modify the Default. config File...................... 7-24 Add Consoles.............
Chapter 11 11.1 11.2 11.3 11.4 11.5 11.6 Validating Console Groups Starting CGValidator.......................................................................... 11-2 Review Validated Groups.................................................................... 11-4 Displaying Data for a Group ............................................................... 11-6 Disabling a Valid Group...................................................................... 11-8 Invalid Groups ...................................
Figures 1–1 Components of the System Management Console (SMC)......................... 1-1 1–2 SMC in Multi-System Configuration ........................................................ 1-2 1–3 SMC Installation Flowchart ..................................................................... 1-4 1–4 SMC Desktop at Startup......................................................................... 1-10 2–1 Cabling Procedure Described in This Chapter ......................................... 2-1 2–2 COM1 Port ....
6–1 Cabling Procedure Described in this Chapter .......................................... 6-1 6–2 GS80/160/320 Keyswitch on New System.................................................. 6-2 6–3 Local Port Location on Standard I/O Module ........................................... 6-4 6–4 Terminal Server Ports .............................................................................. 6-5 6–5 Terminal Server Cable..............................................................................
8–9 Verifying the Network Setup .................................................................. 8-13 8–10 Internet Accounts Dialog Box ............................................................... 8-16 8–11 account_name Properties Dialog Box.................................................... 8-17 9–1 Configuration Files Folder on Installation Disk....................................... 9-2 9–2 Add Telnet Console Screen .......................................................................
B–1 COM1 Port................................................................................................B-2 B–2 PCI Box Rear – Local Port Connection ....................................................B-3 B–3 Mounting Brackets...................................................................................B-4 B–4 Position Identifier Dial.............................................................................B-6 B–5 Terminal Server Placement in the GS80 System.....................................
Preface Intended Audience This manual is for service providers, managers, and operators of Compaq AlphaServer GS80/160/320 systems. Document Structure This manual uses a structured documentation design. Topics are organized into small sections, usually consisting of two facing pages. Most topics begin with an abstract that provides an overview of the section, followed by an illustration or example. The facing page contains descriptions, procedures, and syntax definitions.
• Chapter 6, Adding a System to a Multiple-System Configuration with One SMC, describes cabling for this situation. • Chapter 7, Consolidating Multi-SMC/AS Configurations to One SMC, describes the process (both cabling and software procedures) needed when you are upgrading your multi-AS, multi-SMC configuration to a multi-AS, one SMC configuration. Part 2 – Software Setup. This section of the manual provides instructions on software setup for the SMC.
Documentation Titles Table 1 AlphaServer GS80/160/320 Documentation Order Number Title QA–6GAAA–G8 AlphaServer GS80/160/320 Documentation Kit EK–GS320–UG AlphaServer GS80/160/320 User’s Guide EK–GS320–RM AlphaServer GS80/160/320 Firmware Reference Manual EK–GSPAR–RM AlphaServer GS80/160/320 Getting Started with Partitions EK–GS320–IN AlphaServer GS160/320 Installation Guide EK–GSR80–IN AlphaServer GS80 Installation Guide AG–RKSWB–BE AlphaServer GS80/160/320 User Information CD (HTML files) A
Chapter 1 Overview and Preparation The system management console, or SMC, is the console device for managing one or more AlphaServer GS systems. The SMC provides a central point for monitoring events and managing these systems, as well as creating and managing partitions on each individual system.
1.1 System Management Console Overview The system management console makes it possible to monitor and control one or more AlphaServer GS systems, each of which may have multiple partitions, with a single console device.
With the system management console (SMC), multiple AlphaServer GS80/160/ 320 systems with multiple partitions can be managed from a single device. Hardware The system management console is a specially configured Compaq Deskpro PC, one or more network hubs such as the 8-port SMC EZ Hub-8DS (when multiple systems are being managed from one console device), one or more DECserver 90M terminal servers (one terminal server for each system), and associated cables, connectors, and software.
1.2 Installation Flow Choose your situation from the choices in Figure 1–3 and follow the steps listed to install an SMC. Figure 1–3 SMC Installation Flowchart Check Installation Kit(s) (Sec. 1.3) Bring up and, if necessary, upgrade SMC software (Section 1.
Figure 1–3 SMC Installation Flowchart (Continued) B Adding AS system to single AS system with 1 SMC already installed? Yes No Adding AS system to multiple AS systems with 1 SMC already installed? Yes No Consolidating multi-SMC/multi-AS systems to single SMC? No (No other choices for SMC install) Yes Turn new AS system to Vaux Cable new AS system to new terminal server Disconnect old teminal server from SMC Cable new and old terminal server to hub Cable hub to SMC Cable SMC to corporate network (Ch
Figure 1–3 SMC Installation Flowchart (Continued) C Software Configuration -- Part 2 Define the SMC Network Connection to the Corporate LAN, etc. (Chapter 8) D Installing SMC to one and only one AS system? Yes Plan to define partitions in system? Yes No Replace Default.config file (Section 9.1) No Upgrade Default.config file (Section 9.
Figure 1–3 SMC Installation Flowchart (Continued) E Adding AS system to one or more AS systems with 1 SMC already installed? Yes Run ConsoleWorks to add new group(s) (Section 9.
1.3 Check the Installation Kits The system management console consists of two or more kits: the SMC PC kit and as many terminal server kits as there are systems to be connected to the SMC. Typically, the terminal server kits are installed in the AlphaServer GS systems at the factory. Table 1–1 SMC PC Kit Part Number Description 3X–DS8BA–xx BOM for SMC PC kit; contains these items: Compaq Deskpro PC (minitower or desktop box) including keyboard, mouse, and Windows NT 4.0 CD Worldwide V.
Appendix A for GS160/320 systems and Appendix B for GS80 systems.) The order number for the terminal server kit is 3X–DS8AA–AA. Components of the kit are listed in Table 1–2. Table 1–2 3X–DS8AA–AA Terminal Server Kit Quantity Item Description 1 DECserver 90M Terminal server 4 BN25G–04 4-meter cable 4 1 8 BN25G–07 BN24Q–07 H8585–AA Mounting hardware 7-meter cable 7-meter crossover cable¹ Connector ¹Not used when a network hub is used.
1.4 Set Up the SMC Install the SMC PC and bring up the operating system. version of the SMC software and upgrade if necessary.
1. Set up the Compaq Deskpro computer and monitor according to the accompanying instructions. 2. Start the SMC system. As the SMC operating system software loads, enter information when requested: user name, company name, product ID, and SMC PC system name (the name that will be seen on the corporate LAN).See the AlphaServer GS80/160/320 System Management Console Installation and Release Notes for instructions. 3.
Part 1 Cabling
Chapter 2 Cabling the SMC to One System with One Console Line A GS80/160/320 system with a single console line is a system that has only one standard I/O (SIO) module. The SIO module is in a PCI box connected to a quad building block, and on it is the SRM console firmware, which provides a command-line interface for operator control of the system. Sections in this chapter are listed in the box in Figure 2–1.
2.1 Cable the SMC to the GS80/160/320 Connect the COM1 port of the SMC system to the local port of the GS80/160/320. Figure 2–2 COM1 Port Minitower Model DPENCM Desktop Box Model DPENL COM1(A) COM1(A) Minitower Model DPENM Desktop Box Model DPEND COM1(A) COM1(A) PK-1735-00 NOTE: The model type is on a label on the top or side of the SMC box.
Install H8585–AA connectors (12–36054–01) on the COM1 (or A) port of the SMC system (Figure 2–2) and the local port of the standard I/O module in the GS80/160/320 system primary PCI box ( in Figure 2–3). Connect these ports with a BN24Q cable (17–04308–05).
2.2 Cable the SMC to the Corporate Network Connect to the corporate network from the network adapter on the SMC system. Figure 2–4 Network Adapter 1 Minitower Model DPENCM Desktop Box Model DPENL Minitower Model DPENM Desktop Box Model DPEND PK-1727-00 NOTE: The model type is on a label on the top or side of the SMC box.
Connect a network cable to network adapter 1 on the SMC system, as shown in Figure 2–4. (This cable is not included in the SMC installation kit.) The network adapters are numbered from left to right on the minitower and from bottom to top on the desktop.
2.3 Check the COM1 Settings Check that the baud rate for the COM1 port is 9600. Change it if it is set to any other speed. Check the other COM1 settings.
1. From the Start button select Settings|Control Panel. 2. In the control panel, double-click the Ports icon. The Ports dialog box displays (Figure 2–5). 3. Select COM1 and click the Settings… button. The Settings for COM1 dialog box displays (Figure 2–6). 4. If the baud rate displayed is not 9600, change it to 9600. Set the Data Bits to 8, Parity to None, Stop Bits to 1, and Flow Control to XON/XOFF. If these settings are not compatible with your environment, change them to settings that are.
Chapter 3 Cabling the SMC to One System with Multiple Serial Console Lines A GS80/160/320 system with multiple console lines has more than one standard I/O (SIO) module. The SIO modules are in PCI boxes connected to quad building blocks. On each SIO is the SRM console firmware, which provides a commandline interface for operator control of the system or a partition. Sections in this chapter are listed in the box in Figure 3–1.
3.1 Cable the Terminal Server to the SMC Connect the management channel connector on the terminal server to network adapter 2 on the SMC system. Figure 3–2 Terminal Server Management Channel Connector 1 PK-1769-00 1. Connect one end of the BN24Q–07 cable (17–04308–05) to the management channel connector on the terminal server ( in Figure 3–2). 2. Connect the other end of the cable to network adapter 2 on the SMC system (Figure 3–3).
Figure 3–3 Network Adapter 2 Minitower Model DPENCM Minitower Model DPENM Desktop Box Model DPENL Desktop Box Model DPEND PK-1723-00 NOTE: The model type is on a label on the top or side of the SMC box.
3.2 Cable the Terminal Server to the GS80/160/320 For PCI boxes in an expander cabinet, make the cable connection to the terminal server. Then record the connections and dress the cables. 3.2.1 Make the Cable Connection Cable the local port of the PCI box to the appropriate port on the terminal server with a BN25G cable.
Table 3–1 Terminal Server Cabling QBB Number Terminal Server Port GS80 GS160 GS320 1 0 0 0 2 1 1 1 3 — 2 2 4 — 3 3 5 — — 4 6 — — 5 7 — — 6 8 — — 7 Figure 3–5 Terminal Server Ports 1 PK-1770-00 Cabling the SMC to One System with Multiple Serial Console Lines 3-5
3.2.2 Record the Connections Record the connections made for this installation in Table 3–2.
3.2.3 Dress the Cables Form a service loop and tie wrap the BN25G cable to the rail. Figure 3–6 Terminal Server Cable 2 3 1 2 3 4 5 6 7 8 1 PK-1753-00 1. At the PCI box end, tie wrap the BN25G cable (17–03212–05) to the CSB junction cable (17–04936–xx) to form a service loop ( in Figure 3–6). 2. Tie wrap the BN25G cable down the rail of the expander cabinet ( ). 3. At the bottom of the rail, coil the BN25G cable and place the extra length in the rail ( ).
3.3 Cable the SMC to the Corporate Network Connect to the corporate network from network adapter 1 on the SMC system. Figure 3–7 Network Adapter 1 Minitower Model DPENCM Desktop Box Model DPENL Minitower Model DPENM Desktop Box Model DPEND PK-1727-00 NOTE: The model type is on a label on the top or side of the SMC box.
Connect a network cable to network adapter 1 on the SMC system, as shown in Figure 3–7. (This cable is not included in the SMC installation kit.) The network adapters are numbered from left to right on the minitower and from bottom to top on the desktop.
Chapter 4 Cabling an SMC to a Multi-System Configuration You can control multiple AlphaServer systems from one SMC. This chapter tells how to cable an SMC to a new multi-system configuration. Sections in this chapter are shown as callout items in the box in Figure 4–1.
4.1 Cable Each AS System to a Terminal Server This installation requires a new DECsystem 90 Terminal Server for each system and a network hub. Power each AS system to Vaux, and cable it to a terminal server. 4.1.1 Power Each AS System to Vaux Turn the keyswitch to Off, and turn on the AC input box breakers.
Check that the keyswitch on the each GS80/160/320 system is turned to Off (as shown in Figure 4–2). Turn on the breakers on the AC input boxes. The breakers are accessible from the rear of both the GS80 cabinet and the GS160/320 power cabinet.
4.1.2 Cable Each AS System to Terminal Server Cable the local port of each PCI box with a standard I/O module in a given system to the appropriate port on a terminal server with a BN25G cable. Figure 4–3 Local Port Location on Standard I/O Module 1 PK-1724-00 The cable connections are made at the factory from the standard I/O modules in PCI boxes in the GS160/320 power cabinet and in the GS80 cabinet.
Table 4–1 Terminal Server Cabling QBB Number Terminal Server Port GS80 GS160 GS320 1 0 0 0 2 1 1 1 3 — 2 2 4 — 3 3 5 — — 4 6 — — 5 7 — — 6 8 — — 7 Figure 4–4 Terminal Server Ports 1 PK-1770-00 Cabling an SMC to a Multi-System Configuration 4-5
4.1.3 Record the Connections Record the connections made for this installation in Table 4–2.
4.1.4 Dress the Cables Form a service loop and tie wrap the BN25G cable to the rail. Figure 4–5 Terminal Server Cable 2 3 1 2 3 4 5 6 7 8 1 PK-1753-00 1. At the PCI box end, tie wrap the BN25G cable (17–03212–05) to the CSB junction cable (17–04936–xx) to form a service loop ( in Figure 4–5). 2. Tie wrap the BN25G cable down the rail of the expander cabinet ( ). 3. At the bottom of the rail, coil the BN25G cable and place the extra length in the rail ( ).
4.2 Cable All Terminal Servers to Network Hub Cable all the terminal servers to the network hub.
Figure 4–7 Ports on an 8-port Network Hub Front view LEDs Port 1 Port 2 Rear view ... 8 Electrical outlet MR0203-01 1. Connect one end of each BN25G cable (17–03212–05) to the management channel connector on the terminal server ( in Figure 4–6). 2. Connect the other end of the cable to any port on the network hub except port 1, which is reserved for the cable to the SMC. (See Figure 4–7 for an example of an 8-port network hub. Yours may be different.
4.3 Connect the Network Hub to the SMC Connect the network hub to network adapter 2 on the SMC.
1. Connect the appropriate cable (as defined by the instructions that come with the network hub, not a part of the SMC kits) to network adapter 2 on the SMC (see Figure 4–8). 2. Connect the other end of the cable to port 1 in the network hub (see Figure 4–9). NOTE: The SMC must be connected to port 1, or the SMC will not work. Figure 4–9 shows an 8-port hub. Hubs with more ports are available.
4.4 Cable the SMC to the Corporate Network Connect to the corporate network from network adapter 1 on the SMC system. Figure 4–10 Network Adapter 1 Minitower Model DPENCM Desktop Box Model DPENL Minitower Model DPENM Desktop Box Model DPEND PK-1727-00 NOTE: The model type is on a label on the top or side of the SMC box.
Connect a network cable to network adapter 1 on the SMC system, as shown in Figure 4–10. (This cable is not included in the SMC installation kit.) The network adapters are numbered from left to right on the minitower and from bottom to top on the desktop.
Chapter 5 Adding an AS System to Single AS System with SMC Already Installed You can control multiple AlphaServer systems from one SMC. This chapter tells how to cable a new AlphaServer system to a single AlphaServer system with an SMC already installed. Sections in this chapter are shown as callout items in the box in Figure 5–1.
5.1 Cable New AS System to New Terminal Server This installation requires a new DECsystem 90 Terminal Server and a new network hub. Power the new AS system to Vaux, and cable it to the new terminal server. 5.1.1 Power New AS System to Vaux Turn the keyswitch to Off, and turn on the AC input box breakers.
Check that the keyswitch on the new GS80/160/320 system is turned to Off (as shown in Figure 5–2). Turn on the breakers on the AC input boxes. The breakers are accessible from the rear of both the GS80 cabinet and the GS160/320 power cabinet.
5.1.2 Cable New AS System to New Terminal Server Cable the local port of each PCI box with a standard I/O module in the new system to the appropriate port on the new terminal server with a BN25G cable. Figure 5–3 Local Port Location on Standard I/O Module 1 PK-1724-00 The cable connections are made at the factory from the standard I/O modules in PCI boxes in the GS160/320 power cabinet and in the GS80 cabinet.
Table 5–1 Terminal Server Cabling QBB Number Terminal Server Port GS80 GS160 GS320 1 0 0 0 2 1 1 1 3 — 2 2 4 — 3 3 5 — — 4 6 — — 5 7 — — 6 8 — — 7 Figure 5–4 Terminal Server Ports 1 PK-1770-00 Adding an AS System to Single AS System with SMC Already Installed 5-5
5.1.3 Record the Connections Record the connections made for this installation in Table 5–2.
5.1.4 Dress the Cables Form a service loop and tie wrap the BN25G cable to the rail. Figure 5–5 Terminal Server Cable 2 3 1 2 3 4 5 6 7 8 1 PK-1753-00 1. At the PCI box end, tie wrap the BN25G cable (17–03212–05) to the CSB junction cable (17–04936–xx) to form a service loop ( in Figure 5–5). 2. Tie wrap the BN25G cable down the rail of the expander cabinet ( ). 3. At the bottom of the rail, coil the BN25G cable and place the extra length in the rail ( ).
5.2 Disconnect Cable from Old Terminal Server to SMC Disconnect the cable from the old terminal server to the SMC.
Disconnect the SMC from the old terminal server. NOTE: You do not need to power down or halt the AlphaServer GS80/160/320 to which the old terminal server is connected. Any events that may have been logged to the SMC will be lost, however, until the SMC is reconnected through the network hub to the old terminal server.
5.3 Cable New and Old Terminal Servers to Network Hub Cable both the new and old terminal servers to the network hub.
Figure 5–8 Ports on an 8-port Network Hub Front view LEDs Port 1 Port 2 Rear view ... 8 Electrical outlet MR0203-01 1. Connect one end of the BN25G cable (17–03212–05) to the management channel connector on the terminal server ( in Figure 5–7). 2. Connect the other end of the cable to a port on the network hub. (See Figure 5–8 for an example of an 8-port network hub – yours may be different.
5.4 Connect the Network Hub to the SMC Connect the network hub to network adapter 2 on the SMC.
1. Connect appropriate cable (as defined by the instructions that come with the network hub, not a part of the SMC kits) to network adapter 2 on the SMC (see Figure 5–9). 2. Connect the other end of the cable to a port in the network hub (see Figure 5–10). Note that Figure 5–10 shows an 8-port hub. Hubs with more ports are available. Also, some network hubs can be daisy-chained to provide more ports, as described in the instruction booklets that come with the hub.
5.5 Cable the SMC to the Corporate Network Connect to the corporate network from network adapter 1 on the SMC system. Figure 5–11 Network Adapter 1 Minitower Model DPENCM Desktop Box Model DPENL Minitower Model DPENM Desktop Box Model DPEND PK-1727-00 NOTE: The model type is on a label on the top or side of the SMC box.
Connect a network cable to network adapter 1 on the SMC system, as shown in Figure 5–11. (This cable is not included in the SMC installation kit.) The network adapters are numbered from left to right on the minitower and from bottom to top on the desktop.
Chapter 6 Adding a System to a Multiple-System Configuration with One SMC You can control multiple AlphaServer systems from one SMC. This chapter tells how to add a new AS system to one or more AS systems with one SMC already installed. Sections in the chapter are shown as callout items in the box in Figure 6–1.
6.1 Cable New AS System to New Terminal Server This installation requires a new DECsystem 90 Terminal Server and a network hub. Power the new AS system to Vaux, and cable it to the new terminal server. 6.1.1 Power New AS System to Vaux Turn the keyswitch to Off, and turn on the AC input box breakers.
Check that the keyswitch on the new GS80/160/320 system is turned to Off (as shown in Figure 6–2. Turn on the breakers on the AC input boxes. The breakers are accessible from the rear of both the GS80 cabinet and the GS160/320 power cabinet.
6.1.2 Cable New AS System to New Terminal Server Cable the local port of each PCI box with a standard I/O module in the new system to the appropriate port on the new terminal server with a BN25G cable. Figure 6–3 Local Port Location on Standard I/O Module 1 PK-1724-00 The cable connections are made at the factory from the standard I/O modules in PCI boxes in the GS160/320 power cabinet and in the GS80 cabinet.
Table 6–1 Terminal Server Cabling QBB Number Terminal Server Port GS80 GS160 GS320 1 0 0 0 2 1 1 1 3 — 2 2 4 — 3 3 5 — — 4 6 — — 5 7 — — 6 8 — — 7 Figure 6–4 Terminal Server Ports 1 PK-1770-00 Adding a System to a Multiple-System Configuration with One SMC 6-5
6.1.3 Record the Connections Record the connections made for this installation in Table 6–2.
6.1.4 Dress the Cables Form a service loop and tie wrap the BN25G cable to the rail. Figure 6–5 Terminal Server Cable 2 3 1 2 3 4 5 6 7 8 1 PK-1753-00 1. At the PCI box end, tie wrap the BN25G cable (17–03212–05) to the CSB junction cable (17–04936–xx) to form a service loop ( in Figure 6–5). 2. Tie wrap the BN25G cable down the rail of the expander cabinet ( ). 3. At the bottom of the rail, coil the BN25G cable and place the extra length in the rail ( ).
6.2 Cable New Terminal Server to Network Hub Cable the new terminal server to the network hub.
Figure 6–7 Ports on an 8-port Network Hub Front view LEDs Port 1 Port 2 Rear view ... 8 Electrical outlet MR0203-01 1. Connect one end of the BN25G cable (17–03212–05) to the management channel connector on the terminal server ( in Figure 6–6). 2. Connect the other end of the cable to a port on the network hub. (See Figure 6–7 for an example of an 8-port hub. Yours may be different.
Chapter 7 Consolidating Multi-SMC/AS Configurations to One SMC You can consolidate a multi-AS configuration with each AS controlled by a separate SMC to one controlled by a single SMC. Sections in the chapter are shown as callout items in the box in Figure 7–1. Note that this procedure involves more than just cabling, unlike the other chapters in Part 1.
7.1 Choose the SMC to Remain and Add Hub Pick the SMC to remain in the configuration (usually the one with the most connections/partitions), and if it has a terminal server, connect it to the network hub. Then cable the hub to the remaining SMC. (If the SMC does not have a terminal server, cable the AlphaServer to a new terminal server, the terminal server to the new hub, and the hub to the SMC.) 7.1.
1. From the configurations, select an SMC to serve as the single SMC in the new configuration. It is assumed that the software for the selected SMC has been set up for its original connection (as described for other configurations in Chapters 8, 9, and 10.) This chapter includes software steps that add information to the chosen SMC from the SMC’s being removed).
7.1.2 Connect the Network Hub to the Chosen SMC Connect the network hub to network adapter 2 on the SMC chosen to remain in the configuration.
1. Connect appropriate cable (as defined by the instructions that come with the network hub, not a part of the SMC kits) to network adapter 2 on the SMC (see Figure 7–4). 2. Connect the other end of the cable to port 1 in the network hub (see Figure 7–5). Note that Figure 7–5 shows an 8-port hub. Hubs with more ports are available. Also, some network hubs can be daisy-chained to provide more ports, as described in the instruction booklets that come with the hub.
7.2 Copy Information from SMCs to Be Removed While each SMC is still running, copy the information from each SMC to be removed, so that you can re-create it at the remaining SMC.
1. From the START task button, select Programs| Access Server Manager. When the Browser window comes up, select a server and click on it. When the server window appears, copy down all the information for the console line: IP address, Ethernet address, type, name, and Telnet Remote Console TCP Port Number, as shown in Figure 7–6. 2. Close the Access Server Manager window. 3. Start ConsoleWorks from the desktop and click on “Consoles” in the top of the left column. The window in Figure 7–7 displays. 4.
Figure 7–8 Copy Console Information 5. Copy information for each console, as shown in Figure 7–8, including the name (likely to be modified when recreated in Section 7.7), description, logged state and file location, type as Telnet, IP port number, raw data state, and profile access information. Note that the display is longer than shown in the Figure (see slide bar at right). Be sure to copy all the 1 information. 6. Repeat steps 3 through 5 for each console on the system.
7. Copy the hardware address label for the terminal server (see 7–9). in Figure 8. Disconnect the power from this terminal server (attached to the SMC being replaced).
7.3 Cable Terminal Server to the Network Hub Cable the terminal server being transferred to the network hub.
1. Cable the terminal server being transferred to the network hub. Connect one end of a BN25G cable (17-03212-05) to the management channel connector on the terminal server (see in Figure 7–10). 2. Connect the other end of the cable to a port on the network hub (see Figure 7–11 ). Use any port except port 1. Figure 7–11 Ports on an 8-Port Network Hub Front view LEDs Rear view Port 1 Port 2 ...
7.4 Create New Address and Name for Terminal Server at Remaining SMC Go to the SMC that is to remain in the configuration. Run the Access Server Loader to define the terminal server being added to the remaining SMC, giving it a new IP address and the old Ethernet (hardware) address. 7.4.
1. Start Access Server Loader. From the Start menu select Programs|Access Server Loader|Access Server Loader. The Access Server Loader window displays (Figure 7–12). 2. Click Setup. If you are running from a newly installed SMC, the Confirm dialog box displays (Figure 7–13). Click Yes. (If not, the database will open as described on the following page.
7.4.2 Add Consolidated Terminal Server Information to the Database Add the information taken from the SMC being removed to the configuration data base.
1. The Access Server Loader Configuration dialog box displays (Figure 7–14). On the Clients tab, enter new and old information for the terminal server being replaced: Host Name: Name for each terminal server (GSSMC1, GSSMC2,…) Hardware Addr: from the label on each terminal server (Figure 7–9). IP Addr: 90.0.0.x2 Subnet Mask: 255.255.255.0 NOTE: The IP address you enter in the dialog box is the IP address for the terminal server, not the host. 2. Click OK. The Access Server Loader window displays.
7.5 Verify the Connection Reapply power to the terminal server and verify the new connection through the network hub.
Verify the new terminal server/hub connection. 1. Open a Command window: From the Start menu select Programs | Command Prompt. 2. At the prompt, type ping 90.0.0.x, where x defines the new IP address created for this terminal server in Section 7.4.2. The response should be similar to that shown in Figure 7–15. 3. Close the Command window.
7.6 Run Access Server Manager to Connect SMC to Each Terminal Server Use the Access Server Manager to configure the added terminal server for access by the SMC system. 7.6.
1. Start Access Server Manager. From the Start menu select Programs| Access Server Manager|Access Server Manager. The Access Server Manager window displays. 2. From the File menu select New. The New Access Server dialog box displays (Figure 7–16). The default Login Password is access and the default Privileged Password is system. Click OK. 3. The Access Server dialog box displays (Figure 7–17).
7.6.
1. In the Access Server dialog box, select the Utilities tab (Figure 7–18). Select Test Connection. Click the Do It Now… button. The message “Access Server connection test successful” displays. Click OK. 2. Select Connect to Telnet Console. Click the Do It Now… button. The Telnet window displays (Figure 7–19). 3. At the Local> prompt type show server. A snapshot of the server displays. This confirms the connection. 4. Close the Telnet window.
7.6.
1. From the Utilities tab of the Access Server dialog box (Figure 7–18), select Run Command File. 2. Click the Do It Now… button. The Select a Command File dialog box displays (Figure 7–20). 3. Select the file GS_CON.cmds. Click Open. The Run Command File dialog box displays (Figure 7–21). Click OK. The command file runs. 4. Close the Access Server dialog box and return to Access Server Manager. 5. Close Access Server Manager.
7.7 Update Configuration: Modify the Default. config File Now you need to run ConsoleWorks to add consoles and groups to the Default.config file to reflect the changes in the configuration resulting from consolidating this particular system into those handled by one SMC. 7.7.
1. Start ConsoleWorks from the SMC desktop. The Show Consoles screen displays. 2. At the top of the Show Consoles screen select Add Console. The Add Console screen displays. NOTE: If the addition is such that there are more than 8 consoles, you need to have the appropriate licenses, as noted in Chapter 1. 3. From the Type dropdown menu select Telnet. Click the Add Console button. The Add Telnet Console screen displays (Figure 7–22). Enter the information requested for the console. 4.
Figure 7–23 7-26 console_name Configuration Screen SMC Installation Guide
9. Click the Add Console button. The console_name Configuration screen displays (Figure 7–23). 10. Enter the profile access information copied in Section 7.2 at the bottom of the main data panel. Click the Update button. At the top of the screen, select Connect. A window displays showing console line activity. Press Enter to validate the connection. The connection is working if the SCM, SRM, or operating system prompt displays.
7.7.2 Add Groups Figure 7–24 Add Group Screen 1. Start ConsoleWorks from the SMC desktop. 2. In the left navigation panel select Manage. From the selection links select Groups. The Show Groups screen displays. 3. At the top of the Show Groups screen select Add Group. The Add Group screen displays (Figure 7–24). 4. Enter a name in the Group Name box. The name is limited to 31 characters. 5. Optionally, enter a description. 6. Click the Add Group button. The Group group_name screen displays ( 7.
8. Add a console to the group by selecting the checkbox next to the console's name. Remove a console by toggling the console's checkbox. 9. When you have selected all consoles that belong to the system, click the Update Group button. Figure 7–25 Group group_name Screen NEXT STEP: Repeat the steps in Sections 7.2 through 7.7 for all AlphaServer GS systems being consolidated onto this SMC. Then go to Section 7.8.
7.8 Cable the Remaining SMC to the Corporate Network Connect to the corporate network from network adapter 1 on the SMC system. Figure 7–26 Network Adapter 1 Minitower Model DPENCM Desktop Box Model DPENL Minitower Model DPENM Desktop Box Model DPEND PK-1727-00 NOTE: The model type is on a label on the top or side of the SMC box.
Connect a network cable to network adapter 1 on the SMC system, as shown in Figure 7–26. (This cable is not included in the SMC installation kit.) The network adapters are numbered from left to right on the minitower and from bottom to top on the desktop. NEXT STEP: Go to Chapter 11.
Part 2 Software Setup
Chapter 8 SMC Definitions When you boot an SMC PC for the first time (see note below for upgrades), the Windows NT4 Operating System and SMC software need some preliminary setup. These sections apply to all configurations: • Set the SMC System Time, Date, and Time Zone • Define the SMC’s Network Connections • Configure Outlook Express NOTE: You can proceed directly to Chapter 9 if you are upgrading to SMC V4 from V3.2.
8.1 Set the SMC System Time, Date, and Time Zone Use the Date/Time icon in the Control Panel to set the time, date, and time zone.
1. From the Start button, select Settings|Control Panel. The Control Panel window displays. 2. In the Control Panel double-click the Date/Time icon. The Date/Time Properties dialog box displays. 3. In the Date & Time tab, set the date and time (Figure 8–1). 4. Select the Time Zone tab (Figure 8–2). 5. From the drop-down menu select the time zone for this installation. Click OK.
8.2 Define the SMC’s Network Connections Verify the SMC computer name and the protocol for the private LAN. Specify the SMC IP address. Finally, set up the adapter for the corporate network. 8.2.
1. Open the Windows Control Panel: From the Start menu select Settings|Control Panel. 2. Double-click the Network icon. The Network dialog box displays with the Identification tab selected. 3. Click the Change… button. The Identification Changes dialog box displays (Figure 8–3). Check that the box labeled Computer Name correctly identifies the SMC system as a management station on the corporate network. (In the example shown in Figure 8–3, that name is MySMC.) If it does not, enter the correct name.
8.2.
1. In the Network dialog box, select the Protocols tab (Figure 8–4). If the protocol shown is TCP/IP, skip the rest of this page and go on to Section 8.2.3. 2. If the protocol shown is not TCP/IP, highlight the protocol and click the Remove button. A message box displays; click Yes. 3. In the Network dialog box, click the Add… button. The Select Network Protocol dialog box displays (Figure 8–5). Highlight TCP/IP Protocol. Click OK.
8.2.3 Define the SMC’s Network Adapter 1 Figure 8–6 Microsoft TCP/IP Properties NOTE: The IP address values in the illustration are an example only. Obtain the correct values for this installation from the network administrator.
Enter the static IP address, subnet mask, and gateway. Ask the network administrator for this information. The SMC requires a static IP address; it cannot have a dynamic address (that is, an address assigned by a DHCP server). 1. In the Adapter box of the Microsoft TCP/IP Properties dialog box (Figure 8– 6), select adapter 1. 2. Select the option button labeled Specify an IP address. Enter the IP address, subnet mask, and gateway. Click OK. NOTE: The network card shown in Figure 8–6 is an example only.
8.2.
1. In the Network dialog box, select the Protocols tab. Click the Properties button. 2. The Microsoft TCP/IP Properties dialog box displays (Figure 8–7). Select adapter 2. 3. Select the option button labeled Specify an IP address. Enter the following information: IP address: Subnet mask: 90.0.0.100 255.255.255.0 Leave the Default Gateway blank. Click OK. NOTE: The network card shown in Figure 8–7 is an example only. Another type of network card might be used.
8.2.5 Bind the Protocol Figure 8–8 Bindings Tab in the Network Dialog Box 1. In the Network dialog box, select the Bindings tab. A box with a progress bar displays. 2. When the progress bar indicates that the operation is finished, click Close. 3. Restart the SMC system.
8.2.6 Verify the Network Setup Figure 8–9 Verifying the Network Setup 1. Open a Command window: From the Start menu select Programs| Command Prompt. 2. At the prompt type ping 90.0.0.100. The response should look similar to the first command in Figure 8–9. 3. At the prompt type ping name, where name is the fully qualified computer name displayed in Section 8.2.1. The response should look similar to the second command in Figure 8–9.
8.3 Configure Outlook Express Obtain mail server information from the network administrator before configuring. Figure 8–10 Internet Accounts Dialog Box 1. Double-click the Outlook Express icon on the desktop. If this is the first time Outlook Express is opened, a box displays asking where messages should be stored. Select a folder and click OK. The Outlook Express window displays. 2. From the Tools menu select Accounts. The Internet Accounts dialog box displays (Figure 8–10). 3.
c. The names of the incoming and outgoing mail servers. 5. When Outlook Express sends or receives mail, by default it removes the messages from the server. To leave a copy of messages on the server: a. From the Tools menu select Accounts. In the Internet Accounts window right-click on the account name and select Properties from the pop-up menu. The account_name Properties dialog box displays (Figure 8–11). b. Select the Advanced tab.
Chapter 9 Create or Update Default.config File Use this chapter after preliminary SMC setup (Chapter 8). This chapter includes the sections: • New Installation: Replace the Default.config File • Upgrade Configuration: Add Console(s) and Groups(s) to the Configuration Choose the section appropriate to your installation and follow the steps. Create or Update Default.
9.1 New Installation: Replace the Default.config File Make sure the Default.config file is appropriate for the installation.
The default configuration file put in place by the SMC software installation process is for a single system with multiple consoles. If this system has only one console line, or if the SMC is being installed to a multi-AlphaServer configuration, the default.config file will have to be modified. 1. Stop the ConsoleWorks Server. 2. In Windows Explorer go to the folder C:\Cwks\Default\Config. (The files in this directory are the same as those shown in Figure 9–1 from the installation disk.) 3.
9.2 Upgrade Configuration: Add Console(s) and Groups(s) to the Configuration If you are upgrading your configuration to include new console lines or AlphaServers, you need to run ConsoleWorks to add consoles and groups to reflect your new configuration. 9.2.
1. Start ConsoleWorks from the SRM Console desktop. 2. Select Consoles in the left navigation panel, then Add Console at the top of the screen. The type is Telnet. Do not attempt to add a console if eight consoles already exist. (Privileges required: Admin – R W C; Console – none) 3. In the left navigation panel select Consoles. The Show Consoles screen displays. NOTE: If the addition is such that there are more than 8 consoles, you need to have the appropriate licenses, as noted in Chapter 1. 4.
Figure 9–3 9-6 console_name Configuration Screen SMC Installation Guide
12. Click the Add Console button. The console_name Configuration screen displays (Figure 9–3). 13. Enter the profile access information at the bottom of the main data panel. Click the Update button. At the top of the screen select Connect. A window displays showing console line activity. Press Enter to validate the connection. The connection is working if the SCM, SRM, or operating system prompt displays. Create or Update Default.
9.2.2 Add Groups For each AlphaServer system being added to this SCM, you need to use ConsoleWorks to add a group and then select the consoles that belong to this group (system). Figure 9–4 Add Group Screen 1. Start ConsoleWorks from the SMC desktop. 2. In the left navigation panel select Manage. From the selection links select Groups. The Show Groups screen displays. 3. At the top of the Show Groups screen select Add Group. The Add Group screen displays (Figure 9–4). 4.
5. Optionally, enter a description. 6. Click the Add Group button. The Group group_name screen displays (Figure 9–5). 7. Add a console to the group by selecting the checkbox next to the console's name. Remove a console by toggling the console's checkbox. 8. When you have selected all consoles that belong in the group, click the Update Group button. The screen redisplays with the selected consoles in the Included Consoles column. Figure 9–5 Group group_name Screen NEXT STEP: Go to Chapter 10.
Chapter 10 Run Access Server Software Use this chapter when installing a new SMC to a single, partitionable AlphaServer GS80/160/320 system, or to multiple AlphaServer GS80/160/320 systems, or when upgrading an existing SMC/AlphaServer GS80/160/320 configuration. Here, you define IP addresses and connect the SMC to each new terminal server.
10.1 Run Access Server Loader to Define Addresses The Access Server Loader configures the IP address and subnet mask of each of the terminal servers connected to the SMC – one for each AlphaServer connected to the SMC. 10.1.
1. Start Access Server Loader: From the Start menu select Programs|Access Server Loader|Access Server Loader. The Access Server Loader window displays (Figure 10–1). 2. Click Setup. If the Confirm dialog box displays (Figure 10–2), click Yes.
10.1.
1. The Access Server Loader Configuration dialog box displays (Figure 10–3). On the Clients tab, enter the following information: Host Name: Name for each terminal server (GSSMC1, GSSMC2, …) Hardware Addr: from the label on each terminal server ( in Figure 10–4) 1 IP Addr: 90.0.0.x Subnet Mask: 255.255.255.0 NOTE: The IP address you enter in the Access Server Loader Configuration dialog box is the IP address for the terminal server, not for the host. 2. Click OK.
10.1.
Verify each terminal server connection. 1. Open a Command window: From the Start menu select Programs|Command Prompt. 2. At the prompt, type ping 90.0.0.x. , where x ranges from 0, 3, 5, …99. Each response should be similar to Figure 10–5. 3. Close the Command window.
10.2 Run Access Server Manager to Connect SMC to Each Terminal Server Use the Access Server Manager to configure each terminal server for access by the SMC system. Repeat the steps in Sections 7.6.1 through 7.6.3 for each terminal server in the network. 10.2.
1. Start Access Server Manager. From the Start menu select Programs| Access Server Manager|Access Server Manager. The Access Server Manager window displays. 2. From the File menu select New. The New Access Server dialog box displays (Figure 10–6). The default Login Password is access and the default Privileged Password is system. Click OK. 3. The Access Server dialog box displays (Figure 10–7).
10.2.
1. In the Access Server dialog box, select the Utilities tab (Figure 10–8). Select Test Connection. Click the Do It Now… button. The message “Access Server connection test successful” displays. Click OK. 2. Select Connect to Telnet Console. Click the Do It Now… button. The Telnet window displays (Figure 10–9). 3. At the Local> prompt type show server. A snapshot of the server displays. This confirms the connection. 4. Close the Telnet window.
10.2.
1. From the Utilities tab of the Access Server dialog box (Figure 10–8), select Run Command File. 2. Click the Do It Now… button. The Select a Command File dialog box displays (Figure 10–10). 3. Select the file GS_CON.cmds. Click Open. The Run Command File dialog box displays (Figure 10–11). Click OK. The command file runs. 4. Close the Access Server dialog box and return to Access Server Manager. 5. Close Access Server Manager. Figure 10–11 Run Command File Dialog Box NEXT STEP: Go to Chapter 11.
Chapter 11 Validating Console Groups In this chapter, you run the CGValidator program to validate the groups of console lines attached to particular AlphaServer GS80/160/320 systems. A group is defined in Consoleworks as a set of console lines. Usually, all the lines in a particular group are connected to a single AlphaServer GS80/160/320 system. The CGValidator program displays all the groups defined in ConsoleWorks.
11.1 Starting CGValidator Start the CGValidator program and log in; you must be of console manager status to be able to log in to the CGValidator.
1. From the Start menu select Run. When the Run window displays, type the location of CGValidator (see Figure 11–1). 2. When CGValidator starts, it displays a login screen. Type the same username and password that you would use to log in to ConsoleWorks (see Figure 11–2). Figure 11–2 Login Screen for CGValidator NOTE: The CGValidator user must have ConsoleWorks WRITE admin privileges, or must have READ Admin privileges and WRITE privileges on all consoles.
11.2 Review Validated Groups CGValidator communicates with ConsoleWorks to find all the groups defined there and the consoles in each group.
CGValidator examines the groups defined in ConsoleWorks and compares them with the systems connected to the SMC. It displays the group names it finds. It can take time to locate all the systems connected to the SMC; CGValidator displays a “waiting” message in the status field in the window until all groups have been located and verified. The checkboxes next to the group names indicate that CGValidator has verified that all the consoles in the group are connected to the same AlphaServer GS80/160/320 system.
11.3 Displaying Data for a Group When you select a group, CGValidator displays data for the system connected to that terminal server.
In the example in Figure 11–4, the user has selected GS80 for review (shown by dashed lines around the group name). Data for the system connected to this terminal server is displayed clearly, because it has been selected as a group (checked box). Figure 11–5 shows saving the enabled group in Figure 11–4 as part of the Group Parameter Data maintained by ConsoleWorks by clicking on the “Save GPD” box at the bottom of the screen. CGValidator displays a message saying that the data has been saved.
11.4 Disabling a Valid Group By unchecking a valid group’s box and clicking “Save GPD”, you can disable a valid group, making it impossible to partition using CAPM.
The user has unchecked the box at GS320; the data for the group is grayed out. By clicking on the “Save GPD” the group is saved as disabled for partitioning by CAPM (partitions can still be created using SRM console commands). NOTE: If the group is already partitioned, these partitions remain in effect until changed by SRM console commands.
11.5 Invalid Groups Some console lines may be attached to different AlphaServer systems, making the group not eligible for partitioning.
In Figure 11–7, the user selects a group name that does not have a checkbox. The display is grayed out. Note that it shows two different serial numbers for QBBs in the system; this is not possible on an AlphaServer GS80/160/320 system.
11.6 Save All Data to GPD You save settings for groups made with CGValidator by using the Save buttons on the screen.
Figure 11–8 shows the display after the user has clicked the “Save All” box on the CGValidator screen. A window is displayed showing the information on disabled and enabled groups and requesting confirmation for the save. You can select “OK,” which will save the data to the GPD. In this case, only group GS80 can be partitioned using CAPM. If you select “Cancel” you return to working with groups using CGValidator. NEXT STEP: If you are planning to access the SMC remotely, go to Chapter 12.
Chapter 12 Configuring the SMC for Remote Use Sections in this chapter are: • Set Up the Modem • Configure the Remote Access Software NOTE: When you have finished setting up the modem and configuring the remote access software, restart the SMC system and set the keyswitch on the GS80/160/320 to On.
12.1 Set Up the Modem Follow the manufacturer’s instructions for cabling the modem. Figure 12–1 COM2 Port Minitower Model DPENCM Desktop Box Model DPENL COM2 (B) COM2 (B) Minitower Model DPENM Desktop Box Model DPEND COM2 (B) COM2 (B) PK-1735A-00 NOTE: The model type is on a label on the top or side of the SMC box. 1. Cable the modem, following the manufacturer’s instructions. Connect the RS-232C cable from the SMC installation kit to COM2 on the SMC system (Figure 12–1; COM2 might be marked B).
2. Open the Control Panel: From the Start menu select Settings|Control Panel. 3. Double-click the Modems icon. The Install New Modem dialog box displays. Click Next. The operating system detects the modem and tests it. 4. The Install New Modem dialog box displays, with the words Standard Modem in the box. Click the Change… button. Click the Have Disk… button. Insert the disk that came with the modem in the appropriate drive. 5. In the dialog box click the Browse button, and select the drive and file.
12.2 Configure the Remote Access Software Configure both remote access applications, Carbon Copy Access Edition and WinVNC. 12.2.
1. Start Carbon Copy Access Edition: From the Start menu select Programs|Carbon Copy Access Edition|Carbon Copy. 2. From the Options menu select Communications. The Communication Properties dialog box displays (Figure 12–3). NOTE: Check with the customer before setting up the Wait for Call feature. 3. In the tab labeled Wait for Call, select the modem and the corporate network in the box labeled Select the connection types. In the Options block, select Wait for Call on Startup. Click OK. 4.
12.2.2 WinVNC Figure 12–5 Default Local System Properties Dialog Box 1. Display the WinVNC settings: from the Start menu select Programs| VNC|Administrative Tools|Show Default Settings. The Default Local System Properties dialog box displays (Figure 12–5). 2. Enter a password and select the checkboxes shown in Figure 12–5.
Appendix A Installing a Terminal Server in a GS160/320 System When a GS160/320 system is reconfigured from a single-console-line to a multiple-console-line system, the system management console must be upgraded. This appendix contains instructions for installing the hardware for that upgrade.
A.1 Remove the Existing Connection from the SMC System to the GS160/320 Remove the cable between the SMC system and the GS160/320. Figure A–1 COM1 Port Minitower Model DPENCM Desktop Box Model DPENL COM1(A) Minitower Model DPENM COM1(A) Desktop Box Model DPEND COM1(A) COM1(A) PK-1735-00 NOTE: The model type is on a label on the top or side of the SMC box.
1. Remove the BN24Q cable (17–04308–05) from the H8585–AA connectors (12–36054–01) on the COM1 port of the SMC system (Figure A–1) and the local port of the GS160/320 ( in Figure A–2). NOTE: The COM1 port might be labeled A. 2. Remove the H8585–AA connector from the COM1 port.
A.2 Attach the Mounting Brackets Position the top rear holes over the alignment pins. Fasten the brackets with the M5 screws.
1. Position the holes in the bracket (indicated by in Figure A–3) over the alignment pins ( ) on the terminal server tray. The front end of the bracket should be 2 inches (5 cm) from the front of the terminal server. (The front is the face that has the port connectors.) 2. Fasten the bracket to the terminal server with the M5 screws ( ). 3. Repeat with the bracket on the other side.
A.3 Install the Terminal Server in the GS160/320 Power Cabinet Set the position identifier dial to management agent and install the terminal server in the power cabinet.
1. Set the position identifier dial at the rear of the terminal server to management agent (the position after 14; Figure A–4). 2. Attach the power cord to the rear of the terminal server power supply. Do not plug the other end into the power source yet. 3. From the rear of the GS160/320 power cabinet, install the U-type fasteners in holes 14 and 16 from the bottom on both side rails, above the AC input boxes (Figure A–5). 4. Install the terminal server in the power cabinet.
A.4 Connect the Terminal Server to the Power Source Connect the power cord to J19 of the bottom AC input box.
Plug the power cord of the terminal server into J19 of AC input box 1 (the bottom AC input box) in the GS160/320 power cabinet. If the GS160/320 system is powered up, the terminal server powers up when it is plugged in.
A.5 Cable the Terminal Server to the SMC System Connect the management channel connector on the terminal server to network adapter 2 on the SMC system. Figure A–7 Terminal Server Management Channel Connector 1 PK-1769-00 1. Connect one end of the BN24Q–07 cable (17–04308–05) to the management channel connector on the terminal server ( in Figure A–7). 2. Connect the other end of the cable to network adapter 2 on the SMC system (Figure A–8).
Figure A–8 Network Adapter 2 Minitower Model DPENCM Minitower Model DPENM Desktop Box Model DPENL Desktop Box Model DPEND PK-1723-00 NOTE: The model type is on a label on the top or side of the SMC box.
A.6 Cable the Terminal Server to the GS160/320 For each console, connect a terminal server port to the local port of the PCI box. A.6.1 Make the Cable Connection Figure A–9 PCI Box Rear — Local Port Location 1 PK-1724-00 Make the connection for each console: 1. Attach an H8585–AA connector (12–36054–01) to the local port of the PCI box ( in Figure A–9). 2.
Table A–1 Terminal Server Cabling QBB Number Terminal Server Port GS160 GS320 1 0 0 2 1 1 3 2 2 4 3 3 5 — 4 6 — 5 7 — 6 8 — 7 Figure A–10 Terminal Server Ports 2 PK-1770A-00 Installing a Terminal Server in a GS160/320 System A-13
A.6.2 Record the Connections Record the connections made for this installation in Table A–2.
A.6.3 Dress the Cable Figure A–11 Terminal Server Cable 2 3 1 2 3 4 5 6 7 8 1 PK-1753-00 1. At the PCI box end, tie wrap the 17–03212–cable to the CSB junction cable (17–04936–xx) to form a service loop ( in Figure A–11). 2. Tie wrap the 17–03212–05 cable down the rail of the cabinet ( ). 3. At the bottom of the rail, coil the cable and place the extra length in the rail ( ).
Appendix B Installing a Terminal Server in a GS80 System When a GS80 system is reconfigured from a single-console-line to a multipleconsole-line system, the system management console must be upgraded. This appendix contains instructions for installing the hardware for that upgrade.
B.1 Remove the Existing Connection from the SMC System to the GS80 Remove the cable between the SMC system and the GS80. Figure B–1 COM1 Port Minitower Model DPENCM Desktop Box Model DPENL COM1(A) Minitower Model DPENM COM1(A) Desktop Box Model DPEND COM1(A) COM1(A) PK-1735-00 NOTE: The model type is on a label on the top or side of the SMC box.
1. Remove the BN24Q cable (17–04308–05) from the H8585–AA connectors (12–36054–01) on the COM1 port of the SMC system (Figure B–1) and the local port of the GS80 ( in Figure B–2). NOTE: The COM1 port might be labeled A. 2. Remove the H8585–AA connector from the COM1 port of the SMC.
B.2 Attach the Mounting Brackets Position the top rear holes over the alignment pins. Fasten the brackets with the M5 screws.
1. Position the holes in the bracket (indicated by in Figure B–3) over the alignment pins ( ) on the terminal server tray. The front end of the bracket should be 2 inches (5 cm) from the front of the terminal server. (The front is the face that has the port connectors.) 2. Fasten the bracket to the terminal server with the M5 screws ( ). 3. Repeat with the bracket on the other side.
B.3 Install the Terminal Server in the GS80 Rack Set the position identifier dial to management agent and install the terminal server in the power cabinet.
1. Set the position identifier dial at the rear of the terminal server to management agent (the position after 14; Figure B–4). 2. Attach the power cord to the rear of the terminal server power supply. Do not plug the other end into the power source yet. 3. At the front of the GS80 rack, install the U-type fasteners in holes 1 and 3 at the bottom of both side rails (Figure B–5). 4. Install the terminal server in the rack.
B.4 Connect the Terminal Server to the Power Source Connect the power cord to J5A or J1 of the bottom AC input box.
Plug the power cord of the terminal server into AC input box 1 (the bottom AC input box) in the GS80 rack: • North America systems (–CA variant), use outlet J4A. • Europe and Japan systems (–CB and –CC variants), use outlet J1. Figure B–6 shows the location of these outlets. If the GS80 system is powered up, the terminal server powers up when it is plugged in.
B.5 Cable the Terminal Server to the SMC System Connect the management channel connector on the terminal server to network adapter 2 on the SMC system. Figure B–7 Terminal Server Management Channel Connector 1 PK-1769-00 1. Connect one end of the BN24Q–07 cable (17–04308–05) to the management channel connector on the terminal server ( in Figure B–7). 2. Connect the other end of the cable to network adapter 2 on the SMC system (Figure B–8).
Figure B–8 Network Adapter 2 Minitower Model DPENCM Minitower Model DPENM Desktop Box Model DPENL Desktop Box Model DPEND PK-1723-00 NOTE: The model type is on a label on the top or side of the SMC box.
B.6 Cable the Terminal Server to the GS80 For each console, connect a terminal server port to the local port of the PCI box. B.6.1 Make the Cable Connection Figure B–9 PCI Box Rear — Local Port Location 1 PK-1724-00 Make the connection for each console: 1. Attach an H8585–AA connector (12–36054–01) to the local port of the PCI box ( in Figure B–9). 2.
Table B–1 Terminal Server Cabling Terminal Server Port QBB Number 1 0 2 1 3 — 4 — 5 — 6 — 7 — 8 — Figure B–10 Terminal Server Ports 1 PK-1770-00 Installing a Terminal Server in a GS80 System B-13
B.6.2 Record the Connections Record the connections made for this installation in Table B–2.
Index A Access Server Loader, 10-2 creating the database, 10-4 verifying the connection, 10-6 Access Server Manager, 7-18, 10-8 Telnet window, 7-21, 10-11 Administrator account, 1-11 B Baud rate COM1, 2-6 BN24Q cable, 2-3, A-3, A-10, B-3, B-10 BN25G cable, 3-4, 3-7, 4-4, 4-7, 5-4, 5-7, 6-4, 6-7, A-10, B-10 C Cables BN24Q, 2-3, A-3, A-10, B-3, B-10 BN25G, 3-4, 3-7, 4-4, 4-7, 5-4, 5-7, 64, 6-7, A-10, B-10 RS-232C, 12-2 Cables, dressing, 3-7, 4-7, 5-7, 6-7, A-15 Cabling new one system/one console line, 2-1
saving data to GPD, 11-12 GS80/160/320 local port, 2-3, 3-4, 4-4, 5-4, 6-4 H H8585–AA connector, 2-3, 3-4, 4-4, 5-4, 6-4, A-3, A-12, B-3, B-12 Hardware address label, terminal server, 7-9, 10-5 I Installation kit contents, 1-8 terminal server, A-1–A-15, B-1–B-14 IP address, 8-10 K Kits SMC, 1-8 terminal server, 1-9 selecting, 8-7 Network setup, verifying, 8-13 O Outlook Express, 8-16 Overview, 1-2 P PCI box local port, 2-3, 3-4, 4-4, 5-4, 6-4, A-12, B-3, B-12 Ports COM1, 2-2, 2-6, A-2, B-2 COM2, 12-2
network adapter 2, 3-3, A-10 setting up the modem, 12-2 software, 1-11 Software Access Server, 10-1 creating Default.config file, 9-2 CGValidator, 11-1 modifying Default.
