Page 1
AlphaServer ES47/ES80/GS1280 Installation Information Revision 1.0 This help file covers the installation of both the cabinet and pedestal forms of the hp AlphaServer ES47, the ES80 and all models of the hp AlphaServer GS1280.
Page 3
The ES47 tower comes in a single 2P drawer and embedded I/O. 1. Unpack and de-skid the system. 2. Place the tower to the desired location. 3. Install the floor stand. Pull the floor stands apart, place the tower on them, and press the floor stand against the sides of the tower.
Page 5
The ES47 tower weighs approximately 120 pounds. Take appropriate precautions when unpacking and moving the system. To unpack the ES47: 1. Cut the two packing straps holding the box to the pallet. 2. Open the top of the box. 3. Take out the two styrofoam packs at the top. 4.
Page 9
Making the hardware connection: 1. Open the front door. 2. Unscrew the captive screw that holds the top cover to the frame. 3. Pull the top cover back and off the frame. 4. Unscrew the captive screw that holds the right side panel to the frame. 5.
Page 11
With this connection you use the buttons on the OCP to power on and off the system. The graphics terminal has access to the SRM console and the operating system. It does not have access to the MBM. Making the hardware connection: 1.
Page 12
ES47 Tower Serial Line Console Connection...
Page 13
Making the hardware connection: 1. Open the front door. 2. Unscrew the captive screw that holds the top cover to the frame. 3. Pull the top cover back and off the frame. 4. Unscrew the captive screw that holds the right side panel to the frame. 5.
Page 15
Making the hardware connection: 1. Open the front door. 2. Unscrew the captive screw that holds the top cover to the frame. 3. Pull the top cover back and off the frame. 4. Unscrew the captive screw that holds the right side panel to the frame. 5.
Page 17
The ES47 comes in a single cabinet with one or two 2P drawers. 1. Unpack and de-skid the system. 2. Roll the cabinet to the desired location. 3. Level the system using the four leveling feet at the bottom four corners of the cabinet.
Page 18
ES47 Cabinet with 4 Separate Systems Using a PC...
Page 19
If the customer has decided to use a single or several PCs to control an ES47 cabinet that has 4 separate 2P systems, each system must have its own NAT box connecting to the MBM in each drawer. A single HUB is connected to the WAN side of each NAT box and a PC running AMU or telnet sessions act as the console.
Page 20
ES47 Cabinet with 4 Separate Systems Using a Graphic Terminal...
Page 21
If the customer has decided to use a single or several VGAs to control an ES47 cabinet that has 4 separate 2P systems, each system (drawer) must have its own graphics card connecting to a VGA or to a KVM switch . With this type of connection, the VGA only has SRM console access and each drawer must be powered up by using the OCP pushbuttons.
Page 22
ES47 Cabinet with 4 Separate Systems Using an AMS...
Page 23
If the customer has decided to use a AMS to control an ES47 cabinet that has 4 separate 2P systems, each system must have its own NAT box connecting to the MBM in the 2P drawer. A separate HUB is connected to the WAN side of each NAT box and an ethernet card in the AlphaServer Management Station.
Page 24
ES47 Cabinet with 4 Separate Systems Using Serial Lines...
Page 25
If the customer has decided to use the serial lines to control an ES47 cabinet that has 4 separate 2P systems, each system (drawer) must have its own PC connected to the MBM serial port or each serial port connected to a terminal server connected to a PC running telnet sessions.
Page 26
ES47 Cabinet with a Single M4 System Using a PC...
Page 27
Making the hardware connection: 1. Set up the NAT box between the internal LAN and the multi-server LAN. 2. Use the second BX25G-xx cable to connect the NAT box’s WAN connection to an ethernet card in the PC. If you followed the directions for setting up the NAT box, the WAN side of the NAT box has an address of 90.0.100.1 3.
Page 28
ES47 Cabinet with a Single M4 System Using AMS...
Page 29
Making the hardware connection: 1. Set up the NAT box between the internal LAN and the multi-server LAN. 2. Use the second BX25G-xx cable to connect the NAT box’s WAN connection to the HUB set up for the multi-server LAN. 3.
Page 31
The ES80 comes in a single cabinet with three or four 2P drawers. 1. Unpack and de-skid the system. 2. Roll the cabinet to the desired location. 3. Level the system using the four leveling feet at the bottom four corners of the cabinet.
Page 32
GS1280 - 8 Processor Model Installation...
Page 33
The 8 Processor model comes in two flavors: one with one with 8 processors in a single cabinet and one with 8 processors and one or two expander cabinets. In either case, power for the processors is in the cabinet with the processor drawer. 1.
Page 35
Expansion of the 8P system alternates from side to side. The system cabinet’s ID is 0, the first expansion cabinet is placed to the right and has a cabinet ID of 1, the second expansion cabinet is placed to the left of the system cabinet and has a cabinet ID of 2.
Page 36
GS1280 - 16 Processor Model Installation...
Page 37
The 16 Processor model consists of a cabinet with two 8P drawers and may or may not have an expander cabinet. Power is in the cabinet with the 8p drawers 1. Unpack and de-skid the system. 2. Roll the cabinets to the desired location and arrange them according to the cabinet placement rules for the given system.
Page 39
Expansion of the 16P system alternates from side to side. The system cabinet’s ID is 0, the first expansion cabinet is placed to the right and has a cabinet ID of 1, the second expansion cabinet is placed to the left of the system cabinet and has a cabinet ID of 2.
Page 40
Common Events Unpacking and De-Skidding...
Page 41
The larger of these systems are extremely heavy and require three people to de-skid them. System cabinets are 2 meters tall and will not fit through doors that are 80 inches tall while on their skids. You may have to de-skid them before getting them into the computer room.
Page 43
1. You should already have determined the location of the expander cabinet relative to other cabinets making up the system. 2. Remove the panel, either right or left of both the expander cabinet and its neighbor. 3. Roll the expander cabinet as close as possible to its neighboring cabinet and align the front and rear surfaces.
Page 45
Removal 1. Open the front door. 2. Lift the cabinet top cover and remove. 3. Loosen the screw at the front bottom right or bottom left that will free the side panel you are removing. 4. Lift the panel up until it stops (approximately 2 cm.), pull away from the frame and remove.
Page 47
The router box, sometimes referred to as a Cable/DSL router or a Network Address Translation box (NAT box), is the hardware bridge between two networks. In this case we are using NAT boxes to put individual internal LANs on a multi-server LAN or a corporate LAN. SMC makes a device that contains both the functions of a NAT box with a LAN HUB and it is this device we use.
Page 48
NAT box Installation Procedure 1. Using a BN25G-xx (RJ45) cable connect your PC to any LAN port on the front of the NAT box in the system. 2. Make sure or configure your PC network connection is set to DHCP. 1.
Page 49
the default, factory set address of the NAT box) - http://192.168.2.1:88. Once this is done the NAT box login scree appears. Leave the Password field empty and click on the Login button. The following window appears.
Page 50
Click on Setup. Click on Enter to bring up the setup wizard. Click on Enter again to leave the Password blank. On the left hand side of this screen select set time zone and set the time. Click Enter. Next, on the left hand side, select LAN and the following in screen appears.
Page 52
On this screen change the IP address from 192.168.2.1 to 10.253.0.2. (this now becomes the address of the NAT box on the internal LAN.) Leave the subnet mask as is and disable the NAT box’s DHCP Server. (When you disable the DHCP server, the IP address pool addresses are ignored.) Once the IP address is entered and Disable DHCP is selected, press Enter.
Page 54
Continue on the next screen. The NAT box immediately changes its address to 10.253.0.2, its address on the internal LAN and the connection to your PC through Internet Explorer is broken. To re-connect to the NAT box you must re-configure your PC to an internal LAN address on the system.
Page 55
third...) Subnet Mask field 255.255.0.0 255.255.0.0 (or provided by the customer) ISP Gateway Address 90.0.0.102 If the customer follows our field suggested addressing, this is the address of the AMS on the corporate LAN. If the customer did not follow our suggested addressing scheme, you’ll have to get this address from the customer.
Page 56
If the customer uses a Domain Name Server on the WAN to which the NAT box connects, enter the address assigned by the customer. These two addresses are necessary only if the customer uses a Domain Name Server. Note that these addresses are WINS addresses and differ from DNS addresses.
Page 58
Ignore the warning and click Enter. The first Advanced setting screen allows you to leave on or turn off the firewall. Click the no button disabling the firewall and then enter. The Virtual Server screen appears which you disregard. On the left side of the screen click on Misc and the following screen appears. The virtual DMZ host needs to be enabled and its address set to 10.253.0.1.
Page 60
With the advent of partitions and complex computer room environments, traditional single consoles for each system and partition are becoming obsolete. These systems use an internal LAN for server management operations like booting and configuring the system environment. There are several ways to connect consoles to the system.
Page 61
LAN. If you wish to use AMU, refer to the AMS 1.1.0 CD for instructions on installing and using the AlphaServer Management Utility (AMU) from a PC running Windows.
Page 62
Rules for Setting Cabinet IDs Each cabinet has a unique ID defined by the setting of the push-wheel switch on the back of the door OCP. The following rules apply to cabinet IDs: 1. The left most system cabinet has an ID of 0. 2.
Page 63
Rules for Setting Drawer IDs For each cabinet no matter whether it is a system cabinet, power cabinet, or expander cabinet, the following rules apply: 1. Platform component push-wheel numbering begins with 0. 2. CPU drawers are numbered first, power subracks second and IO drawers third.
Page 64
LAN Addressing The thirty two bit private LAN address is defined as follows: nnnnnnnn. mmmmmmmm . pppppppp . eeeeeeee The value of mmmmmmmm determines the meaning of the values of pppppppp and eeeeeeee. LAN Address The LAN address = nnnnnnnn = 10 Cabinet ID Cabinet IDs are unique and are determined by the setting of the OCP push- wheel on each cabinet door.
Page 65
push- wheel decimal) nnnnnnnn network number (10 network number (10 network number (10 decimal) decimal) decimal) mmmmm MBM in cab0, 1-4 See special addresses MBM in cab1, 11-14 pppppppp 0 for MBM, PBM push-wheel See special addresses 1-4 for CMM eeeeeeee 0 for CMM itself, Cabinet ID push- See special addresses...
Page 66
Set up the AMS on the Corporate LAN You will need a fixed address for the AMS on the corporate LAN which you’ll have to get from the customer. You’ll also need to know what mask is used on the network and get a name for the AMS if the customer wants one. This example uses a DS10 as the AlphaServer Management Station.
Page 67
5. Click on the Next> button The following screen appears:...
Page 68
6. Click on the Configure button. The following screen appears:...
Page 69
7. Click the User Supplied button. Enter the Host Name - a name created by the customer for the AMS on the corporate LAN. Enter the address of the AMS on the corporate LAN (Address supplied by the customer) Enter the network mask: in this case 255.255.252.0 - supplied by the customer Click the OK button.
Page 70
Setup the AMS on the MS LAN Since the multi-server LAN is a network owned and operated by the customer, we recommend that you use a TCP/IP address of the form 90.0.100.x for systems and a fixed address 90.0.0.102 for the AMS on that network. The example used here reflect that addressing scheme.
Page 71
5. Click on the Next> button The following screen appears:...
Page 72
6. Click on the Configure button. The following screen appears:...
Page 73
7. Click the user Supplied button. Enter the address of the AMS on the multi-server LAN (90.0.0.102) Enter the network mask (255.255.0.0) Click the OK button. 8. Use a BN25G-xx (RJ45) cable to connect tu1 to the multi-server LAN HUB.
Powering Up the System In general when the system is plugged in and the circuit breakers on the power distribution unit(s) are in the on position, the display on the console will be the MBM> prompt. When the key switch on the cabinet door or tower OCP is put into the on position power up will begin and its progress traced on the console screen and on the OCP display.
Page 76
The system can be controlled by the OCP. The MBM listens to the OCP switch and pushbuttons. When the state of the switch changes from off to on, the machine responds by executing its power-up routines, traces of which you’ll see on the OCP display and on the console, if you are using an AMS or PC as a console.
Page 77
OCP Pushbutton Operation Button Name Function Left Scroll down point to selected item Middle Execute Execute selected item or go to selected menu Right Back go back to previous screen OCP default view The OCP normally displays the Alert View. Alerts are messages from the server manager software.
Page 78
EV7-1 Running XSROM -------------------------------------------- CMM1 NOT PRESENT CMM2 NOT PRESENT CMM3 NOT PRESENT Left – scrolls down to show information beyond the initial display. Middle – No action Right – Back to top of main menu OCP Power ON/OFF Partition The left button scrolls down to show information beyond the initial display.
Page 79
OCP Show Version Displays the firmware versions of the MBM in that 8P or 2P drawers and the version of the CMM(s) in that 8P or 2P drawers. The display is similar to what would be seen from a show version command at the MBM> prompt. FW VERSIONS >MBM X1.0-11750...
Page 80
Hit the MIDDLE button to execute the Power On selection which brings you to another display: PARTITIONS >All Partitions Default_HP Hit the MIDDLE button to execute the selection, with brings you to the Are You Sure screen: Are you sure? >Y Hit the MIDDLE button to confirm that you want to power on all partitions.
Page 82
Though there are no pushbuttons on the door OCP, there are on both the 2P and 8P drawer OCPs. See OCP Pushbuttons for a description of there use. Refer to the AlphaServer ES47/ES80/GS1280 Service CD for a functional descriptions of all OCP functions.
Power-up display VxWorks System Boot This is the operating system running on the micros Copyright 1984-1998 Wind River Systems, Inc. CPU: AMD SC520 CDP Version: 5.4.2 BSP version: 1.2/0 Creation date: Nov 5 2001, 11:17:39 Press any key to stop auto-boot... 0 auto-booting...
Page 84
<mru 2560> <asyncmap 0x0>] ~DBS-W-(tRootTask) Using the free pool to save environment variables for HP: 1, SP: 255 ~DBS-W-(tRootTask) Using the free pool to save environment variables for HP: 1, SP: 0 done. PPP Connects to the CMMs ppp0: rcvd [LCP ConfAck id=0x3 <mru 2560> <asyncmap 0x0>] ppp0: rcvd [LCP ConfReq id=0x0 <mru 2560>...
Page 86
MBM> MBM> power on Begin Power On numActive after Reconstruction: 8 0 1 2 3 4 5 6 7 8 9 A B C D E F CPU grid w w w w............w = wrap ie routing CPUs with cable wP P P Pw............
Page 87
Running test 43, Software Alerts ... on 1 EV7s Running test 46, Other Local Interrupt Bits ... on 8 EV7s HP:1 SP:0 PRIMARY: ns:0 ew:0 10.0.1.1 Running test 50, Loop on Secondary Routine ... on 7 EV7s Error code 0: done Console Loads Here TFTP server: could not send client file "srmfw"...
Page 88
initializing semaphores initializing heap initial heap 500c0 memory low limit = 354000 heap = 500c0, 3ffc0 initializing driver structures initializing idle process PID initializing file system initializing timer data structures lowering IPL CPU 0 speed is 800 MHz create dead_eater create poll create timer create powerup...
Page 89
probing hose 1, PCI probing hose 2, PCI probing hose 3, PCI bus 0, slot 5 -- vga -- 3D Labs OXYGEN VX1 AGP probing hose 4, PCI probing PCI-to-PCI bridge, bus 2 do not use secondary IDE channel on CMD controller probing PCI-to-PCI bridge, bus 3 bus 2, slot 1 -- dqb -- CMD 649 PCI-IDE bus 2, slot 2 -- pkb -- Adaptec AIC-7892...
Verification Procedure Q-Vet is used to verify the installation. The following topics are covered here: • Q-Vet Installation Verification • Installing Q-Vet • Running Q-Vet • Reviewing the results of Q-Vet • Removing Q-Vet • Q-Vet Resources Q-Vet Installation Verification CAUTION: Misuse of Q-Vet may result in loss of customer data.
Page 91
Installing Q-Vet Install and run Q-Vet from the SYSTEM account on VMS or the root account on UNIX. Remember to install Q-Vet in each partition. Tru64 UNIX 1. Make sure that there are no old Q-Vet or DECVET kits on the system by using the following command: setld -i grep...
Page 92
Running Q-Vet Run Q-Vet on each partition in the system. We recommend that you review the Special Notices and the Testing Notes section of the Release Notes located at http://chump2.mro.cpqcorp.net/qvet/ before running Q-Vet. Follow the instructions listed for your operating system to run Q-Vet in each partition. Tru64 UNIX 1.
Page 93
Reviewing Results of the Q-Vet Run After running Q-Vet, check the results by reviewing the summary log. Q-Vet will run all exercisers until the slowest device has completed one full pass. Depending on the size of the system, this will typically take 2 to 12 hours. Q-Vet will then terminate testing and produce a summary log.
Page 94
• Release notes and kits are available from the Q-Vet web page: http://chump2.mro.cpqcorp.net/qvet/ • Training may be found at: http://learning1.americas.cpqcorp.net/wbt/cs127a-ewb/welcome.htm • A description of the IVP may be found at: http://chump2.mro.cpqcorp.net/qvet/IVP_description.html...