User Service Guide HP Integrity Superdome/sx2000 and HP 9000 Superdome/sx2000 Servers HP Part Number: A9834-9001D_ed6 Published: September 2009 Edition: 6
Legal Notices © Copyright 2009 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein.
Table of Contents About This Document.......................................................................................................13 Intended Audience................................................................................................................................13 Document Organization.......................................................................................................................13 Typographic Conventions.......................................................
Link Interleaving...................................................................................................................35 Memory Error Protection...........................................................................................................35 DRAM Erasure...........................................................................................................................36 PDC Functional Changes....................................................................................
Verifying Site Preparation...............................................................................................................60 Gathering LAN Information......................................................................................................60 Verifying Electrical Requirements..............................................................................................60 Checking the Inventory..........................................................................................
System Boot Configuration Options...................................................................................................114 HP 9000 Boot Configuration Options............................................................................................114 HP Integrity Boot Configuration Options.....................................................................................114 Booting and Shutting Down HP-UX.......................................................................................
RL Command......................................................................................................................................165 RR Command......................................................................................................................................166 RS Command......................................................................................................................................166 SA Command..........................................................
List of Figures 1-1 1-2 1-3 1-4 1-5 1-6 1-7 1-8 1-9 1-10 1-11 1-12 1-13 1-14 1-15 1-16 2-1 2-2 3-1 3-2 3-3 3-4 3-5 3-6 3-7 3-8 3-9 3-10 3-11 3-12 3-13 3-14 3-15 3-16 3-17 3-18 3-19 3-20 3-21 3-22 3-23 3-24 3-25 3-26 3-27 3-28 3-29 3-30 3-31 3-32 3-33 3-34 8 Superdome History.......................................................................................................................17 Superdome Cabinet Components......................................................................................
3-35 3-36 3-37 3-38 3-39 3-40 3-41 3-42 3-43 3-44 3-45 3-46 3-47 3-48 3-49 3-50 3-51 3-52 3-53 3-54 3-55 3-56 A-1 A-2 C-1 C-2 C-3 C-4 C-5 C-6 C-7 C-8 C-9 C-10 C-11 C-12 C-13 C-14 C-15 C-16 C-17 D-1 D-2 D-3 D-4 D-5 D-6 D-7 D-8 D-9 D-10 D-11 D-12 D-13 D-14 Routing I/O Cables........................................................................................................................92 Front Panel with HKP and Present LEDs..............................................................................
List of Tables 1-1 1-2 1-3 2-1 2-2 2-3 2-4 2-5 2-6 2-7 2-8 2-9 2-10 2-11 2-12 2-13 2-14 2-15 2-16 2-17 3-1 3-2 3-3 A-1 A-2 A-3 A-4 10 HSO LED Status Indicator Meaning.............................................................................................28 Supported Processors and Minimum Firmware Versions............................................................32 SMS Lifecycles.........................................................................................................................
List of Examples 3-1 3-2 4-1 B-1 B-2 B-3 B-4 B-5 B-6 B-7 B-8 B-9 B-10 B-11 B-12 B-13 B-14 B-15 B-16 B-17 B-18 B-19 B-20 B-21 B-22 B-23 B-24 B-25 B-26 B-27 B-28 B-29 B-30 B-31 B-32 Directory Example.........................................................................................................................95 Directory Example.........................................................................................................................95 Single-User HP-UX Boot...........................
About This Document This document contains the system overview, system-specific parameters, installation procedures of the system, operating system specifics, and procedures for components in the system. Intended Audience This document is intended for HP trained Customer Support Consultants.
• Text to be replaced with text that you supply is represented using this font. Example: “Enter the ls -l filename command” means you must replace filename with your own text. • Keyboard keys and graphical interface items (such as buttons, tabs, and menu items) are represented using this font. Examples: The Control key, the OK button, the General tab, the Options menu. • Menu —> Submenu represents a menu selection you can perform.
HP Encourages Your Comments HP welcomes your feedback on this publication. Direct your comments to http://docs.hp.com/ en/feedback.html and note that you will not receive an immediate reply. All comments are appreciated.
1 Overview Server History and Specifications Superdome was introduced as the new platform architecture for high-end HP servers between the years 2000 and 2004. Superdome represented the first collaborative hardware design effort between traditional HP and Convex technologies. Superdome was designed to replace T- and V-Class servers and to prepare for the transition from PA-RISC to Intel® Itanium® processors. The new design enabled the ability of running different operating systems on the same server.
• • • • • • • the new CEC chipset board changes including cell board system backplane I/O backplane associated power boards interconnect a redundant, hot-swappable clock source Server Components A Superdome system consists of the following types of cabinet assemblies: • • • Minimum of one Superdome left-side cabinet. The Superdome cabinet contains the processors, the memory, and the core devices of the system. They also house the system's PCI cards.
SD64 consists of left backplane and right backplane cabinets, which are connected using 12 m-Link cables. When the PA-RISC dual-core or the Itanium dual-core processors are used, the CPU counts are doubled by the use of the dual-die processors, as supported on the Intel® Itanium® cell boards. Up to 128 processors can be supported.
AC Power The ac power system includes the PDCA, one FEPS, and up to six BPS. The FEPS is a modular, 2n+2 shelf assembly power system that can consume up to 17 KVA of power from ac sources. The purpose of the FEPS chassis is to provide interconnect, signal and voltage busing between the PDCAs and BPSs, between the BPSs and utility subsystem, and between the BPS and the system power architecture. The FEPS subsystem comprises three distinct modular assemblies: six BPS, two PDCAs, and one FEPS chassis.
Power Sequencing The power on sequence is as follows: 1. 2. 3. 4. 5. 6. 7. When the main power circuit breaker is turned on, the housekeeping (HKP) voltage turns on first and provides 5.3 V dc to the UGUY, Management Processor (MP), system backplane, cells, and all HIOB. Each BPS provides 5.3 V. When HKP voltage is on the MP performs the following steps: a. De-asserts the Reset and begins to boot SBC. b. Loads VxWorks from flash (can be viewed from the local port). c.
One minute after setting the main blower fan Reference to the desired speed or powering on the cabinet, the PM uses the tach select register to cycle through each fan and measure its speed. When a fan is selected, Timer 1 is used in counter mode to count the pulses on port T1 over a period of one second. If the frequency does not equal the expected frequency plus some margin of error, the fan is considered to have failed and is subtracted from the working fan count.
UGUY Every cabinet contains one UGUY. See (Figure 1-3). The UGUY plugs into the HUCB. It is not hot-swappable. Its MP microprocessor controls power monitor functions, executing the Power Monitor 3 (PM3) firmware and the CLU firmware. Figure 1-3 UGUY CLU Functionality The CLU collects and reports the configuration information for itself, the main backplane, I/O backplanes, and the SUB/HUB.
1. FEPS control and monitoring. Superdome has six BPS and the UGUY sends 5V to the BPS for use by the fault collection circuitry. 2. Fan control and monitoring. In addition to the blowers, there are five I/O system fans above and between the I/O bays. These fans run at full speed all the time. There is no fan speed signal. 3. Cabinet mode and cabinet number fan out. The surface mount dip switch on the HUCB (UGUY backplane) is used to configure a Superdome cabinet for normal use or as an SD16 cabinet.
Figure 1-4 Management Processor The SBCH provides the physical and electrical interface to the SBC, the fanning out of the USB to internal and external subsystems, and a LAN 10/100BT ethernet connection. It plugs into the HUCB and is hot-swappable. Every CPU cabinet contains one SBCH board, but only one SBCH contains an SBC board used as the MP for the complex. The remaining SBCH boards act as USB hubs. The SBC board is an embedded computer running system utility board (SUB) firmware.
Figure 1-5 HUCB Backplane The system backplane assembly fabric provides the following functionality in an sx2000 system: • • • • • • • • Interfaces the CLU subsystem to the system backplane and cell modules Houses the system crossbar switch fabrics and cell modules Provides switch fabric interconnect between multiple cabinets Generates system clock sources Performs redundant system clock source switching Distributes the system clock to crossbar chips and cell modules Distributes HKP to cell modules Termin
a hard cell reset, which causes secure firmware to be entered. This bit is cleared by secure firmware before passing control to an OS. Switch Fabrics The system backplane houses the switch fabric that connects to each of the cell modules. The crossbar switch is implemented by a three-link-per-cell topology: three independent switch fabrics connected in parallel. This topology provides switch fabric redundancy in the crossbar switch.
if it is providing a signal of the correct amplitude to the cell boards and XBCs. Its output is also an alarm signal to the RPM FPGA. System clocks can originate from these input sources: • the single-ended external clock input MCX connector • the 280 MHz margin oscillator on the redundant clock source (RCS) board • one of the 266.667 MHz oscillators on one of the HSO modules The source selection is determined either by firmware or by logic in the RCS.
Figure 1-6 HSO and RCS Locations If only one HSO is plugged in and its output is of valid amplitude, then it is selected. If its output is valid, then a green LED on the HSO is lit. If its output is not valid, then a yellow LED on the HSO lights and an alarm signal goes from the RCS to the RPM. The RCS provides a clock that is approximately 100 KHz less than the correct frequency, even if the output of the HSOs are not of valid amplitude or no HSOs are plugged in.
The backplane has two slots for power supply modules. The power supply connector for each slot has a 1-bit slot address to identify the slot. The address bit for power supply slot 0 is grounded. The address bit for slot 1 floats on the backplane. The power supply module provides a pull-up resistor on the address line on slot 1. The power supply module uses the slot address bit as bit A0 for generating a unique I2C address for the FRU ID prom.
Figure 1-9 Cell Board Cell Controller The heart of the cell design is the cell controller. The cell controller provides two front side bus (FSB) interfaces, with each FSB connected to two processor modules. The communication bandwidth is 6.8 GB/s sustained at 266.67 MHz on each FSB. This bandwidth is shared by the two processor modules on the FSB. Interfaces external to the cell provided by the cell controller consist of three crossbar links, called the fabric interface, and a remote I/O subsystem link.
Processors There are several Itanium and PA-RISC processor families supported by the processors are already installed on the cell board. All processors require that a minimum firmware version be installed. For the processors supported, seeTable 1-2. Table 1-2 Supported Processors and Minimum Firmware Versions Processor Family Minimum Firmware Version Core Frequency Intel ® Itanium® single-core processors with 9 MB cache 4.3e (IPF SFW 004.080.000) 1.
Figure 1-10 Cell Memory DIMMs are named according to both physical location and loading order. The physical location is used for connectivity on the board and is the same for all quads. Physical location is a letter (A or B) followed by a number (0, 1, 2, or 3). The letter indicates which side of the quad the DIMM is on. A is the left side, or the side nearest CC. The DIMMs are then numbered 0 through 3, starting at the outer DIMM and moving inwards the memory controllers.
configuration of at least eight DIMMs (two in each quadrant) activates all four MID buses. The theoretical bandwidth of the memory subsystem can be calculated as follows: (533 MT/s * 8 Bytes/T * 4) = 17 GB/s The MID buses are bit-sliced across two memory controllers with 36-bits of data going to each memory controller. In turn, each memory controller takes that high-speed data (533 MT/s) from the MID, and combines four consecutive MID transfers to form one 144-bit DRAM bus.
The 16 echelons in the memory subsystem can be subdivided into four independent memory quadrants accessed by four independent MID buses. Each quadrant contains two independent SDRAM buses. Four echelons can be installed on each SDRAM bus. The CC contains four MBATs, one for each memory quadrant. Each MBAT contains eight sets of routing CSRs (one per rank). Each routing CSR specifies the bits of the address that are masked or compared to select the corresponding rank, referred to as interleave bits.
DRAM Erasure A common cause of a correctable memory error is a DRAM failure; the ability to correct this type of memory failure in hardware is called chip kill. Address or control bit failure is a common cause. Chip kill ECC schemes have added hardware logic that enables them to detect and correct more than a single-bit error when the hardware is programmed to do so.
• • • • • • • • • • • • • • Memory mapped control and status registers (CSRs) control the cell for management needs. System management bus (SMBus) reads the processor module information EEPROM, scratch EEPROM, and thermal sensing device. I2C bus reads PDH, cell, and cell power board FRU ID information. Serial presence detect (SPD) bus detects and investigates loaded DIMMs. Timing control of cell reset signals. Logic analyzer ports for access to important PDH signals.
A new concept for the sx2000 is a fat rope. A fat rope is logically one rope that has 32 wires. It consists of two single ropes but has the four command wires in the second single rope removed. The concept of a single rope remains unchanged. It has 18 signals, of which 10 are bidirectional, single-ended address and data bits. Two pairs of unidirectional, single-ended lines carry commands in each direction and a differential strobe pair for each direction.
encoded differential data bits operating at 2.36 GT/s. This yields a peak total bidirectional HSS link bandwidth of 8.5 GB/s. Internally, SBA routes this high-speed data to and from one of two rope units. Each rope unit spawns four single ropes and four fat ropes. A maximum of two like ropes can connect to an LBA. This means that the SBA to LBA rope configurations can be single, dual, or fat ropes and the SBA-to-LBA rope configurations can be single, dual, fat or dual fat ropes.
Cards that allow only 5 V signaling are not supported; PCI connector keying prevents insertion of such cards. Each LBA has control and monitor signals for use with a PCI hot-swap chip. It also converts PCI interrupts into interrupt transactions which are fed back to the CPUs. PCI Slots For maximum performance and availability, each PCI slot is sourced by its own LBA chip and is supported by its own portion of a hot-plug controller. All slots are designed to Revision 2.
Figure 1-12 PCIe I/O Rope Mapping PCI Hot-Swap Support All 12 slots support PCI hot-plug permitting OLA and OLD of individual I/O cards without impacting the operation of other cards or requiring system downtime. Card slots are physically isolated from each other by nonconductive card separators that also serve as card ejectors to aid in I/O card removal.
management LAN of each system MP on which it is used. If possible, locate the SMS close to the system being tested so field support has convenient access to both machines. Table 1-3 SMS Lifecycles Superdome SMS Console Legacy prior to April 2004 rp2470 Supported PC/workstation (e.g. B2600) Legacy after April 2004 UNIX SMS: rx2600 TFT5600 HP-UX 11i v2 ONLY Legacy upgraded to sx1000 and sx2000 Windows SMS: ProLiant ML350 G4P, TFT5600 & Ethernet switch Windows 2000 Server SP4 Any HP-UX 11.
cable connects the cells to a remote PCI-X chassis. Because both the e-Link and the external e-Link use the same cable material as the legacy REO cable, cable routing and management of these cables in sx2000 system remain unchanged relative to Superdome. The external e-Link cable requires a bend radius no smaller than two inches. The e-Link cable requires a bend radius no smaller than four inches. Figure 1-13 illustrates an e-Link cable.
Figure 1-14 Backplane Cables Clock Cable The clock distribution to a second cabinet for the sx2000 requires a new cable (A9834-2003A). Firmware The newer Intel® Itanium® Processor firmware consists of many components loosely coupled by a single framework. These components are individually linked binary images that are bound together at run time.
Figure 1-15 Itanium Firmware Interfaces • • • • Processor Abstraction Layer (PAL) provides a seamless firmware abstraction between the processor, the system software, and the platform firmware. System Abstraction Layer (SAL) provides a uniform firmware interface and initializes and configures the platform. Extensible Firmware Interface (EFI) provides an interface between the OS and the platform firmware.
The following seven firmware packages installed in the sx2000 to support the IPMI manageability environment: • • • • • • Management Processor (h_mp.xxx.xxx.xxx.frm) Power Monitor (h_pm.xxx.xxx.xxx.frm) Cabinet-Level Utilities (h_clu.xxx.xxx.xxx.frm) Cell (h_cell_pdh.xxx.xxx.xxx.frm) Processor-Dependent Hardware Code (h_pdhc.xxx.xxx.xxx.frm) Event Dictionary (h_ed.xxx.xxx.xxx.frm) • Intel® Itanium® Processor Family Firmware (ipf.x.xx.
Figure 1-16 PA-RISC Firmware Interfaces PA-RISC System Firmware Functions • • • • • • • • • • • • • • • • • • • Supports only HP-UX Supports mixing of PA-RISC and Itanium cell boards in the same complex but in different partitions Detects and rejects Itanium cell boards mixing in a partition with PA-RISC cell boards Support all system management tools available with sx1000 systems FRU isolation and event ID reporting as enabled by the hardware and manageability firmware Cell OLAD (COLAD) of cells with non
• • Minimum of one cell Maximum of eight cells Dual-Cabinet System: • • • • • Six to 64 CPU cores per complex with single-core processors Twelve to 128 CPU cores per complex with dual-core processors Minimum of three cells Maximum of 16 cells No master/checker support for dual-core processors The rules for mixing processors are as follows: • • • • No mixing of frequencies on a cell or within a partition No mixing of cache sizes on a cell or within a partition No mixing of major steppings on a cell or w
2 System Specifications The following specifications are based on ASHRAE Class 1. Class 1 is a controlled computer room environment, in which products are subject to controlled temperature and humidity extremes. Throughout this chapter each specification is defined as thoroughly as possible to ensure that all data is considered, to ensure a successful site preparation and system installation.
Table 2-3 System Component Weights (continued) Component Weight Per Unit Quantity Weight (lb/kg) (lb/kg) Cell power board 8.50/3.86 8 68.00/30.88 DIMMs 0.20/0.09 256 51.20/23.04 Bulk power supply 3.83/1.74 6 23.00/10.44 PDCA 26.00/11.80 2 52.00/23.59 I/O card cage 36.50/16.56 4 146.00/66.24 I/O cards 0.45/0.20 48 21.60/9.80 1 1354.65/614.412 Fully configured server (SD32 cabinet) 1 2 The listed weight for a chassis includes the weight of all components not listed in Table 2-3.
Grounding The site building must provide a safety ground or protective earth for each ac service entrance to all cabinets. WARNING! This equipment is Class 1 and requires full implementation of the grounding scheme to all equipment connections. Failure to attach to protective earth results in loss of regulatory compliance and creates a possible safety hazard.
NOTE: A qualified electrician must wire the PDCA receptacle to site power using copper wire and in compliance with all local codes. All branch circuits used within a complex must be connected together to form a common ground. All power sources such as transformers, UPSs, and other sources, must be connected together to form a common ground. When only one PDCA is installed in a system cabinet, it must be installed as PDCA 0. For the location of PDCA 0, see Figure 2-1.
Table 2-8 Power Requirements (Without SMS) (continued) Requirement Value Comments Power factor correction 0.95 minimum Ground leakage current (mA) > 3.5 mA See the following WARNING. WARNING! Beware of shock hazard. When connecting or removing input power wiring, always connect the ground wire first and disconnect it last.
Table 2-12 I/O Expansion Cabinet ac Power Cords Part Number A5499AZ Where Used Connector Type -001 North America L6-20 -002 International IEC 309 Environmental Requirements This section provides the environmental, power dissipation, noise emission, and air flow specifications.
cooling and electrical power. Table 2-15 also lists the recommended breaker sizes for 4-wire and 5-wire sources. WARNING! Do not connect a 380 to 415 V ac supply to a 4-wire PDCA. This is a safety hazard and results in damage to the product. Line-to-line or phase-to-phase voltage measured at 380 to 415 V ac must always be connected using a 5-wire PDCA.
Table 2-16 HP Integrity Superdome/sx2000 Single-Core CPU Configurations (continued) Cell (in cabinet) Memory (DIMMs per Cell) I/O (fully populated) Typical Power (Watts) Cooling (BTU/Hr) Breaker Power (Watts)2 8 8 2 6823 23302 8596 8 4 4 7260 24794 9147 8 4 2 6300 21516 7938 6 16 4 6968 23797 8779 6 16 2 6008 20518 7570 6 8 4 6640 22677 8366 6 8 2 5680 19398 7156 6 4 4 6325 21601 7969 6 4 2 5365 18322 6759 4 16 4 5813 19852 7324 4 16 2 4853
NOTE: Approximately 5% of the system airflow draws from the rear of the system and exits the top of the system. Figure 2-2 Airflow Diagram A thermal report for the HP Integrity Superdome/sx2000 server is provided in Table 2-17 (page 57).
1 Derate maximum dry bulb temperature 1oC/300 m above 900 m. 2 The system deviates slightly from front to top and rear airflow protocol. Approximately 5 percent of the system airflow is drawn in from the rear of the system. See Figure 2-2 (page 57) for more details. See Table 2-15 (page 55) and Table 2-16 (page 55) for additional details regarding minimum, maximum, and typical configurations.
3 Installing the System This chapter describes installation of HP Integrity Superdome/sx2000 and HP 9000/sx2000 systems. Installers must have received adequate training, be knowledgeable about the product, and have a good overall background in electronics and customer hardware installation. Introduction The instructions in this chapter are written for Customer Support Consultants (CSC) who are experienced at installing complex systems.
Public Telecommunications Network Connection Instructions are issued to the installation site that modems cannot be connected to public telecommunications networks until full datacomm licenses are received for the country of installation. Some countries do not require datacomm licenses.
Inspecting the Shipping Containers for Damage HP shipping containers are designed to protect their contents under normal shipping conditions. After the equipment arrives at the customer site, carefully inspect each carton for signs of shipping damage. WARNING! Do not attempt to move the cabinet, packed or unpacked, up or down an incline of more than 15 degrees. A tilt indicator is installed on the back and side of the cabinet shipping container (Figure 3-1 (page 61)).
Figure 3-2 Abnormal Tilt Indicator NOTE: If the tilt indicator shows that an abnormal shipping condition has occurred, write “possible hidden damage” on the bill of lading and keep the packaging. Inspection Precautions • • When the shipment arrives, check each container against the carrier's bill of lading. Inspect the exterior of each container immediately for mishandling or damage during transit. If any of the containers are damaged, request the carrier's agent be present when the container is opened.
Tools Required The following tools are required to unpack and install the system: • • • • • • • • • • • • Standard hand tools, such as a adjustable-end wrench ESD grounding strap Digital voltmeter capable of reading ac and dc voltages 1/2-inch socket wrench 9/16-inch wrench #2 Phillips screwdriver Flathead screwdriver Wire cutters or utility knife Safety goggles or glasses T-10, T-15, T-20, T-25, and T-30 Torx drivers 9-pin to 25-pin serial cable (HP part number 24542G) 9-pin to 9-pin null modem cable Unp
1. Position the packaged cabinet so that a clear area about three times the length of the package (about 12 feet or 3.66 m) is available in front of the unit, and at least 2 feet (0.61 m) are available on the sides. Figure 3-3 Front of Cabinet Container WARNING! Do not stand directly in front of the strapping while cutting it. Hold the band above the intended cut and wear protective glasses. These bands are under tension. When cut, they spring back and can cause serious eye injury. 2.
3. 4. Lift the cardboard corrugated top cap off the shipping box. Remove the corrugated sleeves surrounding the cabinet. CAUTION: Cut the plastic wrapping material off rather than pulling it off. Pulling the plastic covering off creates an ESD hazard to the hardware. 5. 6. Remove the stretch wrap, the front and rear top foam inserts, and the four corner inserts from the cabinet. Remove the ramps from the pallet and set them aside (Figure 3-5 (page 65)).
7. Remove the plastic antistatic bag by lifting it straight up off the cabinet. If the cabinet or any components are damaged, follow the claims procedure. Some damage can be repaired by replacing the damaged part. If you find extensive damage, you might need to repack and return the entire cabinet to HP. Inspecting the Cabinet To inspect the cabinet exterior for signs of shipping damage, follow these steps: 1. 2. Look at the top and sides for dents, warping, or scratches.
Unpacking and Inspecting the System 67
Moving the Cabinet Off the Pallet 1. Remove the shipping strap that holds the BPSs in place during shipping (Figure 3-8 (page 68)). Failure to remove the shipping strap will obstruct air flow into the BPS and FEPS. Figure 3-8 Shipping Strap Location 2. 68 Remove the pallet mounting brackets and pads on the side of the pallet where the ramp slots are located (Figure 3-9).
Figure 3-9 Removing the Mounting Brackets WARNING! Do not remove the bolts on the mounting brackets that attach to the pallet. These bolts prevent the cabinet from rolling off the back of the pallet. 3. 4. On the other side of the pallet, remove only the bolt on each mounting bracket that is attached to the cabinet. Insert the ramps into the slots on the pallet. CAUTION: Make sure the ramps are parallel and aligned (Figure 3-10). The casters on the cabinet must roll unobstructed onto the ramp.
Figure 3-10 Positioning the Ramps WARNING! Do not attempt to roll a cabinet without help. The cabinet can weigh as much as 1400 pounds (635 kg). Three people are required to roll the cabinet off the pallet. Position one person at the rear of the cabinet and one person on each side. WARNING! Do not attempt to move the cabinet, either packed or unpacked, up or down an incline of more than 15 degrees. 5. Carefully roll the cabinet down the ramp (Figure 3-11). Figure 3-11 Rolling the Cabinet Down the Ramp 6.
Unpacking the PDCA At least one PDCA ships with the system. In some cases, the customer might order two PDCAs, the second to be used as a backup power source. Unpack the PDCA and ensure it has the power cord option for installation. Several power cord options are available for the PDCAs. Only options 6 and 7 are currently available in new system configurations (Table 3-1 (page 71)). Table 3-2 (page 71) details options 6 and 7.
4. 5. 6. 7. 8. Reattach the ramps to the pallet. Replace the plastic antistatic bag and foam inserts. Replace the cardboard surrounding the cabinet. Replace the cardboard caps. Secure the assembly to the pallet with straps. The cabinet is now ready for shipment. Setting Up the System After a site is prepared, the system is unpacked, and all components are inspected, the system can be prepared for booting.
2. Remove the cardboard from the blower housing (Figure 3-13). This cardboard protects the housing baffle during shipping. If it is not removed, the fans can not work properly. Figure 3-13 Removing Protective Cardboard from the Housing NOTE: 3. Double-check that the protective cardboard has been removed.
4. Using the handles on the housing labeled Blower 0 Blower 1, align the edge of the housing over the edge at the top front of the cabinet, and slide it into place until the connectors at the back of each housing are fully mated (Figure 3-15). Then tighten the thumbscrews at the front of the housing. Figure 3-15 Installing the Front Blower Housing 5. 6. 74 Unpack each of the four blowers. Insert each of the four blowers into place in the blower housings with the thumbscrews at the bottom (Figure 3-16).
Figure 3-16 Installing the Blowers 7. 8. Tighten the thumbscrews at the front of each blower. If required, install housings on any other cabinets that were shipped with the system. Attaching the Side Skins and Blower Side Bezels Two cosmetic side panels affix to the left and right sides of the system. In addition, each system has bezels that cover the sides of the blowers.
Figure 3-17 Attaching the Rear Side Skin 3. 76 Attach the skin without the lap joint (Front) over the top bracket and under the bottom bracket and gently slide the skin into position.
Figure 3-18 Attaching the Front Side Skins 4. Push the side skins together, making sure the skins overlap at the lap joint. Attaching the Blower Side Bezels The bezels are held on at the top by the bezel lip, which fits over the top of the blower housing frame, and are secured at the bottom by tabs that fit into slots on the cabinet side panels (Figure 3-19). Use the same procedure to attach the right and left blower side bezels.
1. Place the side bezel slightly above the blower housing frame. Figure 3-19 Attaching the Side Bezels 2. 3. Align the lower bezel tabs to the slots in the side panels. Lower the bezel so the bezel top lip fits securely on the blower housing frame and the two lower tabs are fully inserted into the side panel slots. IMPORTANT: Use four screws to attach the side skins to the top and bottom brackets, except for the top bracket on the right side (facing the front of the cabinet).
Attaching the Leveling Feet and Leveling the Cabinet After positioning the cabinet in its final location, to attach and adjust the leveling feet, follow these steps: 1. 2. Remove the leveling feet from their packages. Attach the leveling feet to the cabinet using four T-25 screws. Figure 3-20 Attaching the Leveling Feet 3. Screw down each leveling foot clockwise until it is in firm contact with the floor. Adjust each foot until the cabinet is level.
Figure 3-21 Installing the Lower Front Door Assembly 4. 5. 80 Using a T-10 driver, secure the lower door bezel to the front door chassis with 10 of the screws provided. Insert all screws loosely, then tighten them after the bezel is aligned. While another person holds the upper door bezel near the door chassis, attach the ribbon cable to the back of the control panel on the bezel and tighten the two flathead screws (Figure 3-22).
Figure 3-22 Installing the Upper Front Door Assembly 6. 7. 8. 9. Feed the grounding strap through the door and attach it to the cabinet. Insert the shoulder studs on the upper door bezel into the holes on the front door metal chassis. Using a T-10 driver, secure the upper door bezel to the metal door with eight of the screws provided. Be sure to press down on the hinge side of the bezel while tightening the screws to prevent misalignment of the bezel. Reattach all filters removed in step 1.
Figure 3-23 Installing the Rear Blower Bezel 3. 4. Align the bezel over the nuts that are attached to the bracket at the rear of the cabinet. Using a T-20 driver, tighten the two captive screws on the lower flange of the bezel. NOTE: 5. Tighten the screws securely to prevent them from interfering with the door. Close the cabinet rear door. Installing the Front Blower Bezel The front blower bezel is a cosmetic cover for the blowers and is located above the front door.
Figure 3-24 Installing the Front Blower Bezel 3. 4. Align the bezel over the nuts that are attached to the bracket at the front of the cabinet. Using a T-20 driver, tighten the two captive screws on the lower flange of the bezel. NOTE: 5. Tighten the screws securely to prevent them from interfering with the door. Close the front door. Wiring Check WARNING! LETHAL VOLTAGE HAZARD—Hazardous voltages can be present in the cabinet if incorrectly wired into the site AC power supply.
To verify that the product ground connects to the site AC power supply ground, follow these steps: 1. 2. 3. 4. Ensure that the site AC power supply circuit breakers serving the cabinet are set to OFF. Ensure that the cabinet main circuit breaker is set to OFF. Touch one test probe to the site AC power supply ground source. Touch the other test probe to an unpainted metal surface of the cabinet.
Figure 3-25 PDCA Assembly for Options 6 and 7 Figure 3-26 A 4-Wire Connector Setting Up the System 85
Figure 3-27 A 5-Wire Connector To install the PDCA, follow these steps: WARNING! 1. 2. 3. Make sure the circuit breaker on the PDCA is OFF. Remove the rear PDCA bezel by removing the four retaining screws. Run the power cord down through the appropriate opening in the floor tile. Insert the PDCA into its slot (Figure 3-28 (page 86)). Figure 3-28 Installing the PDCA 4. 5. 86 Using a T-20 driver, attach the four screws that hold the PDCA in place.
6. Reinstall the rear PDCA bezel. CAUTION: Do not measure voltages with the PDCA breaker set to ON. Make sure the electrical panel breaker is ON and the PDCA breaker is OFF. 7. 8. Plug in the PDCA connector. Check the voltage at the PDCA: a. Using a T-20 driver, remove the screw on the hinged panel at the top of the PDCA. (Figure 3-29). b.
Checking Voltage The voltage check ensures that all phases (and neutral, for international systems) are wired correctly for the cabinet and that the AC input voltage is within specified limits. NOTE: If you use a UPS, see applicable UPS documentation for information to connect the server and to check the UPS output voltage. UPS User Manual documentation is shipped with the UPS and is available at http://docs.hp.com. 1. 2. 3. 4. Verify that site power is OFF. Open the site circuit breakers.
11. Check that the indicator LED on each power supply is lit. See Figure 3-31. Figure 3-31 Power Supply Indicator LED Removing the EMI Panels Remove the front and back electromagnetic interference (EMI) panels to access ports and to visually check whether components are in place and the LEDs are properly illuminated when power is applied to the system.
1. Using a T-20 driver, loosen the captive screw at the top center of the front EMI panel (Figure 3-32). Figure 3-32 Removing Front EMI Panel Screw 2. Use the handle provided to remove the EMI panel and set it aside. When in position, the EMI panels (front and back) are tightly in place. Removing them takes controlled but firm exertion. 3. Loosen the captive screw at the lower center of the back EMI panel (Figure 3-33 (page 90)). Figure 3-33 Removing the Back EMI Panel 4.
Connecting the Cables The I/O cables are attached and tied inside the cabinet. When the system is installed, these cables must be untied, routed, and connected to the cabinets where the other end of the cables terminate. Use the following guidelines and Figure 3-34 to route and connect cables. For more information on cable routing, see “Routing the I/O Cables” (page 91). • Each cabinet is identified with a unique color. The cabinet color label is located at the top of the cabinet.
Figure 3-35 Routing I/O Cables To route cables through the cable groomer at the bottom rear of the cabinet, follow these steps: 1. 2. Remove the cable access plate at the bottom of the groomer. Beginning at the front of the cabinet, route the cables using the following pattern: a. Route the first cable on the left side of the leftmost card cage first. Route it under the PCI-X card cage toward the back of the cabinet and down through the first slot at the right of the cable groomer. b.
Installing the Support Management Station The Support Management Station (SMS) ships separately in boxes. The SMS software and 3 Revisions of Superdome Firmware history are preloaded at the factory. NOTE: The SMS Shelf may or may not be installed in the factory prior to shipping. Installing the SMS Support Shelf 1. 2. Unpack the SMS rp5700 PC and Support Shelf from their respective shipping containers.
Connecting the SMS to the Superdome The Superdome Cookbook document is found through the following website (requires authentication): http://athp.hp.com/portal/site/sig/menuitem.260d6c199fc475a058b9d8a989806e01/ In the Search the Sales Library: field, enter the keywords: SMS Cookbook. A second window is displayed with the file information. Select Worldwide, English (US) to download. NOTE: The SMS Cookbook file is presented as a Windows Visio file.
Superdome Firmware Instructions NOTE: Reference to pa or ia denotes two firmware types: one for PARISC Processors (pa) and one for Itanium Processors (ia). This is applicable for the sx1000, the sx2000, and the Legacy Servers. The Legacy Servers will only have the PARISC Processors (pa) installed. PC SMS 1. Create a c:\opt\firmware\sxX000\X.Xx directory. Example 3-1 Directory Example sx2000\8.7f 2. Copy the h_ipf_(pa or iA)_sxX000_X.Xx tar.gz file to the c:\opt\firmware\sxX000\X.Xx directory. 3. 4.
EIT Tools Functionality The Console Logger captures the commands typed at the console, the response displayed, and alert messages generated by the system. It stores them on the SMS disk drive in a continuous log format. The IPMI Log Acquirer acquires FPL and FRUID logs from the remote system and stores them on the SMS disk drive. The IPMI Event Viewer analyzes the FPL logs captured by the IPMI Log Acquirer and displays the system event information through either a command-line or Web-based interface.
Figure 3-36 Front Panel with HKP and Present LEDs Turning On Housekeeping Power 97
5. Examine the BPS LEDs (Figure 3-37). When on, the breakers on the PDCA distribute ac power to the BPSs. Power is present at the BPSs when: • The amber LED next to the AC0 Present label is on (if the breakers on the PDCA are on the left side at the back of the cabinet). • The amber LED next to the AC1 Present label is on (if the breakers on the PDCA are on the right side at the back of the cabinet).
1. Connect one end of the RJ-45 LAN cable to the LAN port on the MP (Figure 3-38). Figure 3-38 MP LAN Connection Location 2. Connect the other end of the LAN cable to the customer-designated LAN port. Obtain the IP address for the MP from the customer. Connect the dial-up modem cable between the MP modem and the customers phone line connection. Setting the Customer IP Address NOTE: The default IP address for the customer LAN port on the MP is 192.168.1.1.
1. From the MP Command Menu prompt MP:CM>, enter lc (LAN configuration). The screen displays the default values and asks if you want to modify them. TIP: Write down the information, as it may be required for future troubleshooting. If you are not already in the Command Menu, enter ma to return to the Main Menu, then enter cm. The LAN configuration screen appears (Figure 3-39). Figure 3-39 LAN Configuration Screen 2.
Figure 3-40 The ls Command Screen To return to the MP Main Menu, enter ma. To exit the MP, enter x at the MP Main Menu. 10. Check the settings for the model string, UUID, and Creator Product Name using the ID command. For example: MP modifiable stable complex configuration data fields.
1. On the SMS, open the following command prompt windows: • One console window for each partition (MP CO option) • One for initializing the RS command from the MP • One for monitoring partition status (MP VFP option) In each window, connect to the MP by entering the following: telnet Or telnet 2. Enter the appropriate login and password at the MP prompts (Figure 3-41). Figure 3-41 Logging In The MP Main Menu appears (Figure 3-42). Figure 3-42 Main MP Menu 3. 4.
Figure 3-43 MP Command Option 5. In the another window, open the Virtual Front Panel (VFP) by entering vfp at the MP prompt (Figure 3-44). Use this window to observe partition status. Figure 3-44 MP Virtual Front Panel 6. From the VFP menu, enter s to select the whole system, or enter the partition number to select a particular partition. An output similar to Figure 3-45 appears. In this example, no status is listed because the system 48 V has not been switched on.
7. For each of the remaining windows, open the partition console for each partition by enter co at the MP> prompt (Figure 3-46). These windows open blank. NOTE: If information appears in the windows, it means nothing because the cabinet is powered off. Figure 3-46 MP Console Option Powering On the System 48 V Power Supply To power on the system 48 V power supply, follow these steps: 1. Switch on the 48 V supply from each cabinet front panel.
Figure 3-47 HP Integrity Superdome/sx2000 EFI Boot Manager Use the up and down arrow keys on the keyboard to highlight EFI Shell (Built-in) and press Enter. Do this for all partitions. After you start the EFI Shell, the console window displays the EFI shell prompt (Figure 3-48). Figure 3-48 EFI Shell Prompt NOTE: If autoboot is enabled for an nPartition, you must interrupt it to stop the boot process at the EFI firmware console.
Figure 3-49 HP Integrity Superdome/sx2000 Partitions at System Firmware Console Booting an HP 9000 sx2000 Server to BCH After you power on the server or use the MP BO command to boot an nPartition past boot-is-blocked (BIB), the nPartition console shows activity while the firmware initializes and stops at the BCH Main Menu (the Main Menu: Enter command or menu> prompt). To redisplay the current menu and its available commands, enter the BCH DI command.
1. To observe the power status, enter ps at the CM> prompt. A status screen similar to the one in Figure 3-50 appears. Figure 3-50 Power Status First Window 2. At the Select Device: prompt, enter b then the cabinet number to check the power status of the cabinet. Observe Power Switch: on and Power: enabled (Figure 3-51). Figure 3-51 Power Status Window Figure 3-51 shows that cells are installed in slots 0 and 4. In the cabinet, verify that cells are physically located in slots 0 and 4. 3.
Figure 3-52 Power Status Showing State of UGUY LEDs 4. Verify that there is an asterisk (*) in the columns marked MP, CLU, and PM. IMPORTANT: An asterisk (*) appears in the MP column only for cabinet 0; that is, the cabinet containing the MP. Verify that there is an asterisk (*) for each of the cells installed in the cabinet by comparing what is in the Cells column with the cells located inside the cabinet.
See the JET User Guide, JUST Users Guide, and other related documentation for testing located in: • • \opt\scansw\docs\stt directory on the Windows® Support Management Station /opt/scansw/docs/stt directory on the HP-UX Support Management Station IMPORTANT: power. After scan testing successfully completes, reset the complex by cycling the AC Power Cycling After Using JET After using JET, you must recycle the system power because the offline diagnostic can deallocate the CPUs.
Figure 3-53 Attaching Rear Kick Plates 4. 5. 6. Perform steps 1–3 on the right kick plate. Position the upper flange of the center kick plate under the I/O trays complementary mounting bracket, to retain the center kick plate top flanges. No top screws are needed on the center kick plate. Orient this asymmetrical bracket with the hole located nearest the edge in the up position. Using a T-20 driver, tighten the thumbscrews at the bottom of the center kick plate.
Figure 3-54 Cell Board Ejectors 4. Reinstall the front EMI panel (Figure 3-55). Figure 3-55 Front EMI Panel Flange and Cabinet Holes a. b. Hook the flange at the lower corners of the EMI panel into the holes on the cabinet. Position the panel at the top lip, and lift the panel up while pushing the bottom into position. If needed, compress the EMI gasket to seat the panel properly. c. 5. Reattach the screw at the top of the EMI panel. Check that the cables inside the rear enclosure are secure.
6. Reinstall the back EMI panel (Figure 3-56 (page 112)). a. Align the lip inside the cabinet with the lip on the EMI panel. Figure 3-56 Reinstalling the Back EMI Panel b. c. Push the EMI panel up and in. If needed, compress the EMI gasket at the top of the enclosure to get the panel to seat properly. Reattach the screw at the bottom of the EMI panel. Conducting a Post-Installation Check After the system is installed in a computer room and verified, conduct the post-installation check.
4 Booting and Shutting Down the Operating System This chapter presents procedures for booting an operating system (OS) on an nPartition (hardware partition) and procedures for shutting down the OS. Operating Systems Supported on Cell-based HP Servers HP supports nPartitions on cell-based HP 9000 servers and cell-based HP Integrity servers. The following list describes the OSes supported on cell-based servers based on the HP sx2000 chipset.
NOTE: SuSE Linux Enterprise Server 10 is supported on HP rx7640 and rx8640 servers, and will be supported on other cell-based HP Integrity servers with the Intel® Itanium® dual-core processor (Superdome) with SuSE Linux Enterprise Server 10 Service Pack 1. Refer to “Booting and Shutting Down Linux” (page 138) for details. NOTE: On servers based on the HP sx2000 chipset, each cell has a cell local memory (CLM) parameter, which determines how firmware may interleave memory residing on the cell.
NOTE: In some versions of EFI, the Boot Configuration menu is listed as the Boot Option Maintenance Menu. To manage the boot options list for each system use the EFI Shell, the EFI Boot Configuration menu, or OS utilities. At the EFI Shell, the bcfg command supports listing and managing the boot options list for all OSs except Microsoft Windows. On HP Integrity systems with Windows installed the \MSUtil\nvrboot.efi utility is provided for managing Windows boot options from the EFI Shell.
Details of the cpuconfig command are given below and are available by entering help cpuconfig at the EFI Shell. — — — cpuconfig threads — Reports Hyper-Threading status for the nPartition cpuconfig threads on — Enables Hyper-Threading for the nPartition. After enabling Hyper-Threading the nPartition must be reset for Hyper-Threading to be active. cpuconfig threads off — Disables Hyper-Threading for the nPartition.
— Red Hat Enterprise Linux ACPI Configuration: default On cell-based HP Integrity servers, to boot or install the Red Hat Enterprise Linux OS, you must set the ACPI configuration value for the nPartition to default. For details, refer to “ACPI Configuration for Red Hat Enterprise Linux Must Be default” (page 140).
NOTE: On HP Integrity servers, nPartitions that do not have the parconfig EFI shell command do not support virtual partitions and are effectively in nPars boot mode. HP recommends that you do not use the parconfig EFI shell command and instead use the \EFI\HPUX\vparconfig EFI shell command to manage the boot mode for nPartitions on cell-based HP Integrity servers. Refer to Installing and Managing HP-UX Virtual Partitions (vPars), Sixth Edition, for details.
NOTE: list. On HP Integrity servers, the OS installer automatically adds an entry to the boot options Procedure 4-1 Adding an HP-UX Boot Option This procedure adds an HP-UX item to the boot options list from the EFI Shell. To add an HP-UX boot option when logged in to HP-UX, use the setboot command. For details, refer to the setboot(1M) manpage. 1. Access the EFI Shell environment. Log in to the management processor, and enter CO to access the system console.
Refer to “Shutting Down HP-UX” (page 127) for details on shutting down the HP-UX OS. CAUTION: ACPI Configuration for HP-UX Must Be default On cell-based HP Integrity servers, to boot the HP-UX OS, an nPartition ACPI configuration value must be set to default. At the EFI Shell interface, enter the acpiconfig command with no arguments to list the current ACPI configuration. If the acpiconfig value is not set to default, then HP-UX cannot boot.
• BOOT Issuing the BOOT command with no arguments boots the device at the primary (PRI) boot path. • BOOT bootvariable This command boots the device indicated by the specified boot path, where bootvariable is the PRI, HAA, or ALT boot path. For example, BOOT PRI boots the primary boot path. • BOOT LAN INSTALL or BOOT LAN.ip-address INSTALL The BOOT... INSTALL commands boot HP-UX from the default HP-UX install server or from the server specified by ip-address.
1. Access the EFI Boot Manager menu for the nPartition on which you want to boot HP-UX. Log in to the management processor, and enter CO to access the Console list. Select the nPartition console. When accessing the console, confirm that you are at the EFI Boot Manager menu (the main EFI menu). If you are at another EFI menu, select the Exit option from the submenus until you return to the screen with the EFI Boot Manager heading. 2. At the EFI Boot Manager menu, select an item from the boot options list.
The file system number can change each time it is mapped (for example, when the nPartition boots, or when the map -r command is issued). 5. When accessing the EFI System Partition for the desired boot device, issue the HPUX command to initiate the HPUX.EFI loader on the device you are accessing. The full path for the loader is \EFI\HPUX\HPUX.EFI. When initiated, HPUX.EFI references the \EFI\HPUX\AUTO file and boots HP-UX using the default boot behavior specified in the AUTO file.
1. Access the BCH Main Menu for the nPartition on which you want to boot HP-UX in single-user mode. Log in to the management processor, and enter CO to access the Console list. Select the nPartition console. When accessing the console, confirm that you are at the BCH Main Menu (the Main Menu: Enter command or menu> prompt). If you are at a BCH menu other than the Main Menu, then enter MA to return to the BCH Main Menu. 2.
4. Exit the console and management processor interfaces if you are finished using them. To exit the BCH environment, press ^B (Control+B); this exits the nPartition console and returns to the management processor Main Menu. To exit the management processor, enter X at the Main Menu. Procedure 4-6 Single-User Mode HP-UX Booting (EFI Shell) From the EFI Shell environment, boot in single-user mode by stopping the boot process at the HPUX.
loading MFSFILES Directory(bootfs) to MFS ...... Launching /stand/vmunix SIZE: Text:25953K + Data:3715K + BSS:3637K = Total:33306K Console is on a Serial Device Booting kernel... 6. Exit the console and management processor interfaces if you are finished using them. To exit the EFI environment, press ^B (Control+B); this exits the nPartition console and returns to the management processor Main Menu. To exit the management processor, enter X at the Main Menu.
1. Access the EFI Shell environment for the nPartition on which you want to boot HP-UX in LVM-maintenance mode. Log in to the management processor, and enter CO to access the Console list. Select the nPartition console. When accessing the console, confirm that you are at the EFI Boot Manager menu (the main EFI menu). If you are at another EFI menu, select the Exit option from the submenus until you return to the screen with the EFI Boot Manager heading.
2. Issue the shutdown command with the appropriate command-line options. The command-line options you specify dictate the way in which HP-UX is shut down, whether the nPartition is rebooted, and whether any nPartition configuration changes take place (for example, adding or removing cells). Use the following list to choose an HP-UX shutdown option for your nPartition: • Shut down HP-UX and halt the nPartition.
HP OpenVMS I64 Support for Cell Local Memory On servers based on the HP sx2000 chipset, each cell has a cell local memory (CLM) parameter, which determines how firmware interleaves memory residing on the cell. IMPORTANT: HP OpenVMS I64 does not support using CLM. Before booting OpenVMS on an nPartition, you must ensure that the CLM parameter for each cell in the nPartition is set to zero (0).
1. Access the EFI Shell environment. Log in to the management processor, and enter CO to access the system console. When accessing the console, confirm that you are at the EFI Boot Manager menu (the main EFI menu). If you are at another EFI menu, select the Exit option from the submenus until you return to the screen with the EFI Boot Manager heading. From the EFI Boot Manager menu, select the EFI Shell menu option to access the EFI Shell environment. 2.
Booting HP OpenVMS To boot HP OpenVMS I64 on a cell-based HP Integrity server use either of the following procedures. • • “Booting HP OpenVMS (EFI Boot Manager)” (page 131) “Booting HP OpenVMS (EFI Shell)” (page 131) CAUTION: ACPI Configuration for HP OpenVMS I64 Must Be default On cell-based HP Integrity servers, to boot the HP OpenVMS OS, an nPartition ACPI configuration value must be set to default.
2. At the EFI Shell environment, issue the map command to list all currently mapped bootable devices. The bootable file systems of interest typically are listed as fs0:, fs1:, and so on. 3. Access the EFI System Partition for the device from which you want to boot HP OpenVMS (fsX:, where X is the file system number). For example, enter fs2: to access the EFI System Partition for the bootable file system number 2. The EFI Shell prompt changes to reflect the file system currently accessed.
2. At the OpenVMS command line (DCL) issue the @SYS$SYSTEM:SHUTDOWN command and specify the shutdown options in response to the prompts given.
IMPORTANT: Microsoft Windows supports using CLM on cell-based HP Integrity servers. For best performance in an nPartition running Windows, HP recommends that you configure the CLM parameter to 100 percent for each cell in the nPartition. To check CLM configuration details from an OS, use Partition Manager or the parstatus command.
fs0:\> ls EFI\Microsoft\WINNT50 Directory of: fs0:\EFI\Microsoft\WINNT50 09/18/03 09/18/03 12/18/03 11:58a
11:58a 08:16a 1 File(s) 2 Dir(s) 1,024 1,024 354 354 bytes . .. Boot0001 fs0:\> 4. At the EFI Shell environment, issue the \MSUtil\nvrboot.efi command to launch the Microsoft Windows boot options utility. fs0:\> msutil\nvrboot NVRBOOT: OS Boot Options Maintenance Tool [Version 5.2.3683] 1. 2. * 3. 4. SUSE SLES 9 HP-UX Primary Boot: 0/0/1/0/0.2.Refer to “Shutting Down Microsoft Windows” (page 137) for details on shutting down the Windows OS. CAUTION: ACPI Configuration for Windows Must Be windows On cell-based HP Integrity servers, to boot the Windows OS, an nPartition ACPI configuration value must be set to windows. At the EFI Shell, enter the acpiconfig command with no arguments to list the current ACPI configuration. If the acpiconfig value is not set to windows, then Windows cannot boot.
5. Exit the console and management processor interfaces if you are finished using them. To exit the console environment, press ^B (Control+B); this exits the console and returns to the management processor Main menu. To exit the management processor, enter X at the Main menu. Shutting Down Microsoft Windows You can shut down the Windows OS on HP Integrity servers using the Start menu or the shutdown command.
3. Issue the shutdown command and the appropriate options to shut down the Windows Server 2003 on the system. You have the following options when shutting down Windows: • To shut down Windows and reboot: shutdown /r Alternatively, you can select the Start —> Shut Down action and select Restart from the drop-down menu.
than 512 MB of noninterleaved memory, then use Partition Manager or the parstatus command to confirm the CLM configuration details. To set the CLM configuration, use Partition Manager or the parmodify command. For details, refer to the HP System Partitions Guide or the Partition Manager Web site (http://docs.hp.com/en/ PARMGR2/). Adding Linux to the Boot Options List This section describes how to add a Linux entry to the system boot options list.
Likewise, bcfg boot add 1 \efi\SuSE\elilo.efi "SLES 9"adds a SuSE Linux item as the first entry in the boot options list. Refer to the help bcfg command for details. 4. Exit the console and management processor interfaces if you are finished using them. To exit the EFI environment press ^B (Control+B); this exits the system console and returns to the management processor Main Menu. To exit the management processor, enter X at the Main Menu.
Refer to “ACPI Configuration for Red Hat Enterprise Linux Must Be default” (page 140) for required configuration details. 1. Access the EFI Shell. From the system console, select the EFI Shell entry from the EFI Boot Manager menu to access the shell. 2. Access the EFI System Partition for the Red Hat Enterprise Linux boot device. Use the map EFI Shell command to list the file systems (fs0, fs1, and so on) that are known and have been mapped.
After choosing the file system for the boot device (for example, fs0:), you can initiate the Linux loader from the EFI Shell prompt by entering the full path for the ELILO.EFI loader. On a SuSE Linux Enterprise Server boot device EFI System Partition, the full paths to the loader and configuration files are: \efi\SuSE\elilo.efi \efi\SuSE\elilo.conf By default the ELILO.EFI loader boots Linux using the kernel image and parameters specified by the default entry in the elilo.
time When to shut down (required). You can specify the time option in any of the following ways: • Absolute time in the format hh:mm, in which hh is the hour (one or two digits) and mm is the minute of the hour (two digits). • Number of minutes to wait in the format +m, in which m is the number of minutes. • now to immediately shut down; this is equivalent to using +0 to wait zero minutes. Refer to the shutdown(8) Linux manpage for details. Also refer to the Linux manpage for the poweroff command.
A sx2000 LEDs Table A-1 Front Panel LEDs LED Driven By State Meaning 48V Good PM On (green) 48V is good HKP Good PM On (green) Housekeeping is good. MP Present PM On (green) MP is installed in this cabinet.
Table A-2 Power and OL* LEDs LED Location Driven By State Cell Power Chassis beside cell and on cell Cell LPM Solid Green HKP, PWR_GOOD Cell Attention Chassis beside cell CLU Solid Yellow Cell OL* PDHC Post PDHC 0x0 PDHC Post or run state Cell Meaning oxf 0xe->0x1 PM Post 0x0 No HKP 0xf MOP is reset or dead 0xe->0x1 PM Post or run state 0x0 No HKP 0xf CLU is reset or dead 0xe->0x1 CLU Post or run state PCI Card cage Chassis behind PCI card CLU Attention cage Solid Yellow PCI
Figure A-1 Utilities Table A-3 OL* LED States Description Power (Green) OL* (Yellow) Normal operation (powered) On Off Fault detected, power on On Flashing Slot selected, power on, not ready for On OLA/D On Power off or slot available Off Off Fault detected, power off Off Flashing Ready for OL* Off On Figure A-2 PDH Status A label on the outside of the SDCPB Frame indicates PDH Status, dc/dc converter faults that shutdown the sx2000 cell, and loss of dc/dc converter redundancy.
NOTE: The Power Good LED is a bicolor LED (green and yellow). Table A-4 PDH Status and Power Good LED States LED Description Definition BIB Boot Is Blocked When illuminated, it tells the end user that the system is ready to boot. SMG Shared Memory Good This references non-volatile memory that manageability and system firmware share. When illuminated, the system is ready to begin fetching code. USB Universal Serial Bus When illuminated, PDHC is communicating with the MP.
B Management Processor Commands This appendix summarizes the management processor (MP) commands. In the examples, MP is used as the command prompt. NOTE: The term Guardian Service Processor has been changed to Management Processor, but some code already written uses the old term. BO Command BO - Boot partition • Access level—Single PD user • Scope—partition This command boots the specified partition.
Example B-2 CA Command CC Command CC - Complex Configuration • Access level—Administrator • Scope—Complex This command performs an initial out-of-the-box complex configuration. The system can be configured as either a single (user specified) cell in partition 0 (the genesis complex profile) or the last profile can be restored. The state of the complex prior to command execution has no bearing on the changes to the configuration.
NOTE: This command does not boot any partitions. Use the BO command to boot needed partitions. NOTE: If possible, use a cell in the genesis complex profile that has a bootable device attached. Example B-3 CC Command CP Command CP - Cells Assigned by Partition • Access Level - Single Partition User • Scope - Complex The cp command displays a table of cells assigned to partitions and arranged by cabinets.
NOTE: This is for display only, no configuration is possible with this command. Example B-4 CP Command DATE Command DATE Command - Set Date and Time. • Access level—Administrator • Scope—Complex This command changes the value of the real time clock chip on the MP. Example B-5 DATE Command DC Command DC - Default Configuration • Access level—Administratrix • Scope—Complex This command resets some or all of the configuration parameters to their default values.
Example B-6 DC Command DF Command DF - Display FRUID • Access level—Single Partition User • Scope—Complex This command displays the FRUID data of the specified FRU. FRU information for the SBC, BPS, and processors are constructed because they do not have a FRU ID EEPROM. This makes the list of FRUs different than the list presented in the WF command.
Example B-7 DF Command DI Command DI - Disconnect Remote or LAN Console • Access level—Operator • Scope—Complex This command initiates separate remote console or LAN console disconnect sequences. For the remote console, the modem control lines are deasserted, forcing the modem to hang up the telephone line. For the LAN console, the telnet connection is closed.
NOTE: On the HUCB board, there is a remote RS232 connector. The remote RS232 system was used to connect to a modem on legacy systems. For sx2000 servers, modem support is removed, so connections to the remote RS232 connector are ignored. Example B-8 DI Command DL Command DL - Disable LAN Access • Access level—Administrator • Scope—Complex This command disables telnet LAN access.
Example B-10 EL Command MP:CM> el Enable telnet access? (Y/[N]) y -> Telnet access enabled. MP:CM> See also: DI, DL. Note that this command is deprecated and does not support SSH. Use the SA command instead. HE Command HE - Help Menu • Scope—N/A • Access level—Single PD user This command displays a list of all MP commands available to the level of the MP access (administrator, operator, or single PD user).
Example B-11 HE Command ID Command ID - Configure Complex Identification ID Command 157
• Access level—Operator • Scope—Complex This command configures the complex identification information. The complex identification information includes the following: • Model number • Model string • Complex serial number • Complex system name • Original product number • Current product number • Enterprise ID and diagnostic license This command is similar to the SSCONFIG command in ODE. The command is protected by an authentication mechanism.
Example B-13 Example: • MP:CM> io--------------------------+Cabinet | 0 | 1 |--------+--------+--------+Slot |01234567|01234567|--------+--------+--------+Cell |XXXX....|........|IO Cab |0000....|........|IO Bay |0101....|........|IO Chas |1133....|........|MP:CM>• See also: PS IT Command IT - View / Configure Inactivity Timeout Parameters • Access level—Operator • Scope—Complex This command sets the two inactivity timeouts.
Example B-15 LC Command LS Command LS - LAN Status • Access level—Single Partition User • Scope—Complex This command displays all parameters and current connection status of the LAN interface.
• Access level—Single Partition User • Scope—N/A The command returns you from the command menu to the main menu. Only the user that enters the command is returned to the private main menu. Example B-17 MP Main Menu ND Command ND - Network Diagnostics • Access level—Administrator • Scope—Complex This command enables or disables network diagnostics. This enables or disables the Ethernet access to MP Ethernet ports other than the main telnet port (TCP port 23).
being forced to enter a partition in commands that require a partition for their operation. For example, this prevents a user from accidentally TOCing the wrong partition. A default partition is automatically set for users who are assigned the Single Partition User access level when they log in into the MP handler. A user assigned the Single Partition User access level can not change the default partition.
Example B-20 PE Command for a Compute Cabinet [spudome] MP:CM> pe This command controls power enable to a hardware device. B - Cabinet C - Cell I - IO Chassis P - Partition Select Device: b Enter cabinet number: 0 WARNING: Cabinet 0 is connected to cabinet 1. Cabinets 0 and 1 must be powered off and on such that both cabinets are off for an overlapping interval. If one cabinet is powered off then on while the other cabinet remains on, communications between the two cabinets will be lost.
Example B-21 PS Command RE Command RE - Reset Entity 164 Management Processor Commands
• Access level—Operator • Scope—Complex This command resets the specified entity. Be careful when resetting entities because of the side effects. Resetting an entity has the following side effects: • The CLU sends the backplane_reset signal on the main backplane, which results in the following being reset: • All XBCs, RCs, cells plugged into backplane, PDH interface chips, CCs, all CPUs except PDHC, any attached RIOs, all I/O adapters installed in the I/O backplanes associated with the above RIOs.
Example B-22 Re-key lock for partition 3 RR Command RR - Reset Partition for Re-configuration • Access level—Single Partition User • Scope—Partition This command resets the specified partition, but does not automatically boot it. The utility system resets each cell that is a member of the specified partition. If the user is either Administrator or Operator, you can choose a partition.
This command resets and boots the specified partition. The utility system resets each cell that is a member of the specified partition. Once all cells have reset, the partition boots. If you are either Administrator or Operator, you can choose a partition. Example B-24 RS Command SA Command SA - Set Access Parameters • Access level—Administrator • Scope—Complex This command modifies the enablement of interfaces including telnet, SSH, modem, network diagnostics, IPMI LAN, Web console, and so on.
• • Flow control timeouts User parameters: — User name — Organization name — Access level — Mode — User state Example B-26 SO Command SYSREV Command SYSREV - Display System and Manageability Firmware Revisions • Access level—Single Partition User • Scope—Complex This command will display the firmware revisions of all of the entities in the complex.
Example B-27 SYSREV Command MP:CM> sysrev Manageability Subsystem FW Revision Level: 7.14 | Cabinet #0 | -----------------------+-----------------+ | SYS FW | PDHC | Cell (slot 0) | 32.2 | 7.6 | Cell (slot 1) | 32.2 | 7.6 | Cell (slot 2) | 32.2 | 7.6 | Cell (slot 3) | 32.2 | 7.6 | Cell (slot 4) | | | Cell (slot 5) | | | Cell (slot 6) | | | Cell (slot 7) | | | | | MP | 7.14 | CLU | 7.6 | PM | 7.12 | CIO (bay 0, chassis 1) | 7.4 | CIO (bay 0, chassis 3) | 7.4 | CIO (bay 1, chassis 1) | 7.
• Access level—Single Partition User • Scope—Complex This command treats all characters following the TE as a message that is broadcast when is pressed. The message size is limited to 80 characters. Any extra characters are not broadcast. Also, any message that is written is not entered into the console log. NOTE: All users connected to the MP handler receive the message, irrespective of what partition the user sending the message has access to.
This command displays the login name of the connected console client user and the port on which they are connected. For LAN console clients, the remote IP address is displayed. Example B-31 WHO Command XD Command XD - Diagnostic and Reset of MP • Access level—Operator • Scope—Complex This command tests certain functions of the SBC and SBCH boards.
IMPORTANT: Some of the tests are destructive. Do not run this command on a system running the operating system.
C Powering the System On and Off This appendix provides procedures to power a system on and off. Shutting Down the System Use this procedure to shut down the system. Checking System Configuration To check the current system configuration in preparation for shutdown, follow these steps: 1. Open a command prompt window and connect to the MP (Figure C-1): telnet Figure C-1 Connecting to the Host 2. Enter the login and password at the MP prompt. The Main Menu appears (Figure C-2).
3. 4. Open the Command Menu by entering cm at the MP prompt. Make sure that no one else is using the system by entering who at the CM prompt. Only one user should be seen, as indicated in Figure C-3. Figure C-3 Checking for Other Users 5. Read and save the current system configuration by entering cp and the CM prompt. Cabinet and partition information appear (Figure C-4). Figure C-4 Checking Current System Configuration 6. 7. Go back to the Main Menu by entering ma at the CM prompt.
8. From the VFP, enter s to select the whole system or enter the partition number to select a particular partition. You should see an output similar to that shown in Figure C-6. Figure C-6 Example of Partition State 9. Press ctrl+B to exit the Virtual Front Panel and return to the Main Menu. Shutting Down the Operating System You must shut down the operating system on each partition. From the Main Menu prompt, enter co to bring up the Partition Consoles Menu (Figure C-7).
3. 4. 5. At the console prompt, shut down and halt the operating system by entering the shutdown command. • HP-UX: Enter the shutdown -h command • Linux: Enter the shutdown -h
Figure C-9 Using the de -s Command 7. Repeat step 1 through step 6 for each partition. Powering Off the System To power off the system, follow these steps: 1. From the Command Menu, enter pe (Figure C-10). Figure C-10 Power Entity Command 2. 3. 4. Enter the number of the cabinet to power off. In Figure C-10, the number is 0. When prompted for the state of the cabinet power, enter off. Enter ps at the CM> prompt to view the power status (Figure C-11).
Figure C-11 Power Status First Window 5. Enter b at the select device prompt to ensure that the cabinet power is off. The output should be similar to that in Figure C-12. The power switch is on, but the power is not enabled. Figure C-12 Power Status Second Window The cabinet is now powered off. Turning On Housekeeping Power To turn on housekeeping power to the system, follow these steps: 1. Verify that the ac voltage at the input source is within specifications for each cabinet being powered on.
2. 3. Ensure the following: • The ac breakers are in the OFF position. • The cabinet power switch at the front of the cabinet is in the OFF position. • The ac breakers and cabinet switches on the I/O expansion (IOX) cabinet (if one is present) are in the OFF position. If the complex has an IOX cabinet, power on this cabinet first. IMPORTANT: 4. The 48 V switch on the front panel must be OFF at this time. Turn on the ac breakers on the PDCAs at the back of the each cabinet.
5. Examine the bulk power supply (BPS) LEDs (Figure C-14). When on, the breakers on the PDCA distribute power to the BPSs. Power is present at the BPSs when: • The amber LED labeled AC0 Present is on (if the breakers are on the PDCA on the left side at the back of the cabinet). • The amber LED labeled AC1 Present is on (if the breakers are on the PDCA on the right side at the back of the cabinet).
Figure C-15 Power Entity Command 3. 4. Enter on to power on the cabinet. From the CM> prompt, enter ps to observe the power status. The status screen shown in Figure C-16 appears.
5. At the Select Device prompt, enter B then the cabinet number to check the power status of the cabinet. Observe that the power switch is on and power is enabled as shown in Figure C-17.
D Templates This appendix contains blank floor plan grids and equipment templates. Combine the necessary number of floor plan grid sheets to create a scaled version of your computer room floor plan. Templates Figure D-1 illustrates the locations required for the cable cutouts. Figure D-2 “SD16 and SD32 Space Requirements” illustrates the overall dimensions required for SD16 and SD32 systems. Figure D-3 “SD64 Space Requirements” illustrates the overall dimensions required for an SD64 complex.
Figure D-2 SD16 and SD32 Space Requirements 184 Templates
Figure D-3 SD64 Space Requirements Equipment Footprint Templates Equipment footprint templates are drawn to the same scale as the floor plan grid (1/4 inch = 1 foot). These templates show basic equipment dimensions and space requirements for servicing. The service areas shown on the template drawings are lightly shaded. Use equipment templates with the floor plan grid to define the location of the equipment to be installed in the computer room.
4. 5. Cut out each template selected in step 3, then place it on the floor plan grid created in step 2. Position pieces until the desired layout is obtained then fasten the pieces to the grid. Mark the locations of the computer room doors, air conditioning floor vents, utility outlets, and so on.
Figure D-5 Computer Floor Template Templates 187
Figure D-6 Computer Floor Template 188 Templates
Figure D-7 Computer Floor Template Templates 189
Figure D-8 Computer Floor Template 190 Templates
Figure D-9 SD32, SD64, and IOX Cabinet Templates Templates 191
Figure D-10 SD32, SD64, and IOX Cabinet Templates 192 Templates
Figure D-11 SD32, SD64, and IOX Cabinet Templates Templates 193
Figure D-12 SD32, SD64, and IOX Cabinet Templates 194 Templates
Figure D-13 SD32, SD64, and IOX Cabinet Templates Templates 195
Figure D-14 SD32, SD64, and IOX Cabinet Templates 196 Templates
Index A ac power verification 4-wire PDCA, 84 5-wire PDCA, 84 AC0 Present LED, 98, 180 AC1 Present LED, 98, 180 acoustic noise specifications sound power level, 56 sound pressure level, 56 air handling spaces, 20 American Society of Heating, Refrigerating and Air-Conditioning Engineers, (see ASHRAE) ASHRAE Class 1, 49, 50, 57 attention LED, 179 B bezel attaching front bezel, 82 attaching rear bezel, 81 attaching side bezels, 75 blower bezels (See also "bezel"), 75 blower housings installing, 72 unpacking,
door installation back, 79 front, 79 DP rated power cables, 20 dual in-line memory module, (see DIMM) dual-die processors, 19 E e-Link cable description, 42 ejectors cell board, 110 electrical specifications, 50 electrostatic discharge, 59 EMI panel installing, 111 removing, 89 environmental requirements, 54 equipment returning, 71 equipment footprint templates, 185 external e-Link cable description, 42 F facility guidelines computer room layout, 185 equipment footprint templates, 185 FEPS, 19 description
LPM, 19 M m-Link cable description, 42 MAC address, 100 management processor, (see MP) moving the system, 72 MP detailed description, 24 displaying the customer LAN parameters, 100 exiting the main menu, 101 general description, 22 invoking a partition console, 104 invoking the virtual front panel, 103 physical connection to the customer LAN, 98 returning to the main menu, 101 setting the customer LAN parameters, 100 shown in system, 24 viewing the virtual front panel screen, 103 N noise emission specific
general description, 26 housekeeping supply pinouts, 29 I2C bus distribution, 27 I2C device addresses, 27 location of power supply modules, 30 monitor and control functions, 27 power distribution, 29 sustained total bandwidth, 26 system clocks differences from sx1000 system, 24 system specifications, 49 T temperature range IOX cabinet, 22 Normal, 22 OverTempHigh, 22 OverTempLow, 22 OverTempMid, 22 temperature specifications, 54 thermal report full configuration, 57 minimum configuration, 57 typical configu
