AlphaServer ES45 Owner's Guide Order Number: EK-ES450-UG. B01 This manual is for managers and operators of ES45 systems.
First Printing, Februrary 2002 © 2002 Compaq Computer Corporation Compaq, the Compaq logo, Compaq Insight Manager, AlphaServer, StorageWorks, and TruCluster Registered in U.S. Patent and Trademark Office. OpenVMS and Tru64 are trademarks of Compaq Information Technologies Group, L.P. in the United States and other countries. Linux is a registered trademark of Linus Torvalds in several countries. UNIX is a trademark of The Open Group in the United States and other countries.
Japanese Notice Canadian Notice This Class A digital apparatus meets all requirements of the Canadian Interference-Causing Equipment Regulations. Avis Canadien Cet appareil numérique de la classe A respecte toutes les exigences du Règlement sur le matériel brouilleur du Canada. European Union Notice Products with the CE Marking comply with both the EMC Directive (89/336/EEC) and the Low Voltage Directive (73/23/EEC) issued by the Commission of the European Community.
Contents Preface ....................................................................................................................... xv Chapter 1 1.1 1.2 1.3 1.4 1.5 1.6 1.7 1.8 1.7.1 1.7.2 1.7.3 1.9 1.10 1.11 1.12 1.13 Model Differences.................................................................................. 1-2 System Enclosures................................................................................. 1-3 System Chassis—Front View/Top View.............................................
2.4.2 2.4.3 2.4.4 2.5 2.6 2.6.1 2.6.2 2.6.3 2.6.4 2.7 2.7.1 2.7.2 2.7.3 2.7.4 2.7.5 Displaying the Logical Hardware Configuration................................ 2-16 Displaying the Bootable Devices......................................................... 2-22 Viewing the Memory Configuration.................................................... 2-24 Setting SRM Environment Variables ................................................. 2-25 Setting Console Security ..............................................
4.8 4.9 4.10 4.11 4.11.1 4.11.2 4.11.3 4.12 4.13 4.13.1 4.14 4.15 4.15.1 4.16 Installing CPUs................................................................................... 4-21 Memory Configuration ........................................................................ 4-23 Installing DIMMs................................................................................ 4-28 PCI Configuration ............................................................................... 4-31 Model 1B PCI Backplane ..
5.14.3 5.14.4 5.14.5 5.14.6 5.14.7 5.14.8 5.14.9 5.14.10 5.14.11 5.14.12 5.14.13 5.14.14 5.14.15 5.14.16 5.14.17 5.14.18 5.14.19 5.14.20 5.14.21 5.14.22 5.14.23 boot_file......................................................................................... 5-46 boot_osflags................................................................................... 5-47 com*_baud .................................................................................... 5-51 com*_flow....................................
Chapter 7 7.1 7.1.1 7.1.2 7.1.3 7.2 7.3 7.4 7.4.1 7.4.2 7.4.3 7.4.4 7.4.5 7.4.6 7.4.7 7.5 7.6 Power-Up Error Messages .................................................................... 7-2 Messages with Beep Codes ................................................................... 7-2 Checksum Error .................................................................................... 7-4 No MEM Error ......................................................................................
2–9 2–10 2–11 2–12 2–13 3–1 3–2 3–3 3–4 3–5 3–6 3–7 4–1 5–1 5–2 5–3 5–4 5–5 5–6 5–7 5–8 5–9 5–10 5–11 5–12 5–13 5–14 5–15 5–16 5–17 5–18 5–19 6–1 6–2 7–1 7–2 7–3 7–4 7–5 7–6 7–7 x Set Password....................................................................................... 2-27 Set Secure ........................................................................................... 2-29 Login ...................................................................................................
7–8 7–9 Show Power Command ....................................................................... 7-17 Crash Command ................................................................................. 7-18 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 2–1 4–1 4–2 4–3 4–4 4–5 4–6 4–7 4–8 4–9 4–10 4–11 4–12 4–13 4–14 4–15 4–16 4–17 4–18 4–19 4–20 ES45 Systems........................................................................................ 1-3 Top/Front Components (Pedestal) ...
4–21 4–22 4–23 4–24 4–25 6–1 6–2 6–3 6–4 xii Installing a 5.25-Inch Device (Pedestal/Rack View) ........................... 4-44 Disk Cage Installation ........................................................................ 4-47 Disk Cage Installation (Continued) .................................................... 4-49 Fan Locations...................................................................................... 4-51 Cabling a Second Disk Cage .......................................................
Tables 1–1 1–2 1–3 1–4 2–1 2–2 2–3 2–4 3–1 4–1 5–1 5–2 5–3 5–4 5–5 5–6 5–7 5–8 5–9 6–1 6–2 6–3 7–1 7–2 7–3 7–4 7–5 7–6 7–7 7–8 7–9 7–10 8–1 8–2 8–3 8–4 8–5 ES45 Model Summary .......................................................................... 1-2 How Physical I/O Slots Map to Logical Slots: Model 1B..................... 1-15 How Physical I/O Slots Map to Logical Slots: Model 2B .................... 1-17 How Physical I/O Slots Map to Logical Slots: Model 3B.....................
8–6 8–7 8–8 xiv Electrical Characteristics — All System Variants................................ 8-7 Regulatory Approvals............................................................................ 8-9 Acoustic Data ......................................................................................
Preface Intended Audience This manual is for managers and operators of AlphaServer ES45 systems. Document Structure This manual uses a structured documentation design. Topics are organized into small sections, usually consisting of two facing pages. Most topics begin with an abstract that provides an overview of the section, followed by an illustration or example. The facing page contains descriptions, procedures, and syntax definitions. This manual has eight chapters.
• Chapter 7, Troubleshooting, gives basic troubleshooting procedures. • Chapter 8, Specifications, gives system specifications.
Chapter 1 System Overview This chapter provides an overview of the system, including: • System Enclosures • System Chassis—Front View/Top View • System Chassis—Rear View • Rear Ports and Slots • Operator Control Panel • System Motherboard • I/O Backplane • Power Supplies • Removable Media Storage • Storage Subsystem • System Access • Console Terminal NOTE: See Chapter 4 for warnings and procedures for accessing internal parts of the system.
1.1 Model Differences The AlphaServer ES45 has four different models (Models 1B, 2, 2B, and 3B). Table 1–1 describes the model differences in detail.
1.2 System Enclosures The ES45 family consists of a standalone tower, a pedestal with expanded storage capacity, and a rackmount system.
Model Variants ES45 systems are offered with the following four models: • Model 1B – Six PCI slots with four slots at 66 MHz, two slots at 33 MHz, and one AGP 4x slot. • Model 2 – Ten PCI slots with six slots at 66 MHz and four slots at 33 MHz • Model 2B – Ten PCI slots with six slots at 66 MHz and four slots at 33 MHz. • Model 3B – Ten PCI slots with two at 66 MHz and eight slots at 33 MHz.
1.
Operator control panel CD-ROM drive Removable media bays Floppy diskette drive Storage drive bays Fans CPUs Memory PCI cards 1-6 ES45 Owner’s Guide
1.
1.
Rear Panel Connections Modem port—Dedicated 9-pin port for modem connection to remote management console. COM2 serial port—Extra port to modem or any serial device. Keyboard port—To PS/2-compatible keyboard. Mouse port—To PS/2-compatible mouse. COM1 MMJ-type serial port/terminal port—For connecting a console terminal. Parallel port—To parallel device such as a printer. SCSI breakouts. PCI slots—For option cards for high-performance network, video, disk controllers, and so forth.
1.6 Operator Control Panel The control panel provides system controls and status indicators. The controls are the Power, Halt, and Reset buttons. A 16-character backlit alphanumeric display indicates system state. The panel has two LEDs: a green Power OK indicator and an amber Halt indicator. Figure 1–5 Operator Control Panel 1 2 3 4 5 6 PK0204 Control panel display. A one-line, 16-character alphanumeric display that indicates system status during power-up and testing.
Power LED (green). Lights when the power button is pressed. Reset button. A momentary contact switch that restarts the system and reinitializes the console firmware. Power-up messages are displayed, and then the console prompt is displayed or the operating system boot messages are displayed, depending on how the startup sequence has been defined. Halt LED (amber). Lights when you press the Halt button. Halt button. Halts the system and returns to the SRM console.
1.7 System Motherboard The system motherboard is located on the floor of the system card cage and has the majority of the logic for the system. The system motherboard has connectors for the CPUs and memory motherboards (MMBs) and a connector to the I/O subsystem. Figure 1–6 shows the location of these modules on the motherboard.
CPU Card The system can have up to four CPU cards. The CPU cards are installed on the system board. Each CPU card contains an EV68 microprocessor, a current implementation of the Alpha architecture. The microprocessor is a superscalar CPU with out-of-order execution and speculative execution to maximize speed and performance. It contains four integer execution units and dedicated execution units for floating-point add, multiply, and divide. It has an instruction cache and a data cache on the chip.
1.8 I/O Backplane The ES45 server has three I/O versions: Models 1B, 2B, and 3B. 1.8.1 Model 1B Model 1B has six PCI slots with four at 66 MHz, two at 33 MHz, and one AGP 4x slot.
There is no direct correspondence between the physical numbers of the slots on the I/O backplane and the logical slot identification reported with the SRM console show config command (described in Chapter 2). Table 1–2 maps the physical slot numbers to the SRM logical ID numbers. See Chapter 4 for instructions on installing PCI options.
1.8.2 Model 2B Model 2B has ten slots with six slots at 66 MHz and four slots at 33 MHz (Model 2 uses the same configuration).
There is no direct correspondence between the physical numbers of the slots on the I/O backplane and the logical slot identification reported with the SRM console show config command (described in Chapter 2). Table 1–3 maps the physical slot numbers to the SRM logical ID numbers. See Chapter 4 for instructions on installing PCI options.
1.8.3 Model 3B The Model 3B has ten slots with eight at 33 MHz and two at 66 MHz.
There is no direct correspondence between the physical numbers of the slots on the I/O backplane and the logical slot identification reported with the SRM console show config command (described in Chapter 2). Table 1–4 maps the physical slot numbers to the SRM logical ID numbers. See Chapter 4 for instructions on installing PCI options.
1.9 Power Supplies The power supplies provide power to components in the system chassis. The number of power supplies required depends on the system configuration.
One to three power supplies provide power to components in the system chassis. The system supports redundant power configurations to ensure continued system operation if a power supply fails (The Model 2 has a minimum configuration of two power supplies). The power supplies select line voltage and frequency are automatically selected for 200–240 V and 50 Hz or 60 Hz. Power Supply LEDs Each power supply has two green LEDs that indicate the state of power to the system.
1.10 Removable Media Storage The system chassis houses a CD-ROM drive and a high-density 3.5inch floppy diskette drive and supports two additional 5.25-inch half-height devices or one additional full-height device. See Chapter 4 for information on installing a removable media drive.
1.11 Storage Subsystem The system chassis can house up to two universal storage disk cages. The storage subsystem supports “hot pluggable" hard disk drives that can be replaced while the storage backplane is powered and operating. You can install up to six 1-inch universal hard drives in each storage disk cage. See Chapter 4 for installation and swap procedures.
1.12 System Access At the time of delivery, the system keys are taped inside the small front door that provides access to the operator control panel and removable media devices.
Both the tower and pedestal systems have a small front door through which the control panel and removable media devices are accessible. At the time of delivery, the system keys are taped inside this door. The tower front door has a lock that lets you secure access to the disk drives and to the rest of the system. The pedestal has two front doors, both of which can be locked. The upper door secures the disk drives and access to the rest of the system, and the lower door secures the expanded storage.
1.13 Console Terminal The console terminal can be a serial (character cell) terminal connected to the COM1 or COM2 port or a VGA monitor connected to a VGA adapter on PCI0. A VGA monitor requires a keyboard and mouse.
Chapter 2 Operation This chapter gives instructions for basic system operation.
2.1 Powering Up the System To power up the system, press the power button. Testing begins, and status shows on the console terminal screen and in the control panel display.
2.2 Power-Up Displays Power-up information is displayed on the operator control panel and on the console terminal startup screen. Messages sent from the SROM (serial read-only memory) program are displayed first, followed by messages from the SRM console. NOTE: The power-up text that is displayed on the screen depends on what kind of terminal is connected as the console terminal: VT or VGA.
2.2.1 SROM Power-Up Display Example 2–1 Sample SROM Power-Up Display SROM V2.15 CPU # 00 @ 1000 MHz SROM program starting Reloading SROM SROM V2.15 CPU # 00 @ 1000 MHz System Bus Speed @ 0125 MHz SROM program starting PCI66 bus speed check Reloading SROM SROM V2.
When the system powers up, the SROM code is loaded into the I-cache (instruction cache) on the first available CPU, which becomes the primary CPU. The order of precedence is CPU0, CPU1, and so on. The primary CPU attempts to access the PCI bus. If it cannot, either a hang or a failure occurs, and this is the only message displayed. The primary CPU interrogates the I2C EEROM on the system board and CPU modules through shared RAM. The primary CPU determines the CPU and system configuration to jump to.
2.2.2 SRM Console Power-Up Display At the completion of SROM power-up, the primary CPU transfers control to the SRM console program, described in Section 2.3. The console program continues the system initialization. Failures are reported to the console terminal through the power-up screen and a console event log. Example 2–2 SRM Power-Up Display OpenVMS PALcode V1.88-28, Tru64 UNIX PALcode V1.
probing hose 2, PCI Hose 3 - PCI bus running at 33Mhz probing hose 3, PCI probing PCI-to-PCI bridge, bus 2 bus 2, slot 4 -- eib -- DE602-AA bus 2, slot 5 -- eic -- DE602-AA bus 2, slot 6 -- eid -- DE602-FA bus 0, slot 2 -- fwa -- DEFPA starting drivers The primary CPU prints a message indicating that it is running the console. Starting with this message, the power-up display is sent to any console terminal, regardless of the state of the console environment variable.
Example 2–2 SRM Power-Up Display (Continued) initializing keyboard starting console on CPU 1 initialized idle PCB initializing idle process PID lowering IPL CPU 1 speed is 1000 MHz create powerup entering idle loop starting console on CPU 2 initialized idle PCB initializing idle process PID lowering IPL CPU 2 speed is 1000 MHz create powerup starting console on CPU 3 initialized idle PCB initializing idle process PID lowering IPL CPU 3 speed is 1000 MHz create powerup initializing GCT/FRU at 220000 initiali
The console is started on the secondary CPUs. The example shows a fourprocessor system. Various diagnostics are performed. The console terminal displays the SRM console banner and the prompt, Pnn>>>. The number n indicates the primary processor. In a multiprocessor system, the prompt could be P00>>>, P01>>>, P02>>>, or P03>>>. From the SRM prompt, you can boot the operating system.
2.3 SRM Console The SRM console is the command-line interface that allows you to set up and boot the operating system, display the system configuration, set environment variables, and perform basic system troubleshooting. SRM firmware is located in a flash ROM (read-only memory) on the system board. The SRM console firmware is described in detail in Chapter 5, Firmware. The following sections cover functions you can perform from SRM.
2.3.1 Selecting the Display Device The SRM console environment variable determines to which display device (VT-type terminal or VGA monitor) the console display is sent. The console terminal that displays the SRM user interface can be either a serial terminal (VT320 or higher, or equivalent) or a VGA monitor. The SRM console environment variable determines the display device. • If you use a VT-type device as the console terminal, set the console environment variable to serial.
2.3.2 Setting a Control Panel Message You can create a customized message to be displayed on the operator control panel after startup self-tests and diagnostics have been completed. When the operating system is running, the control panel displays the console revision. It is useful to create a customized message if you have a number of systems and you want to identify each system by a node name. You can use the SRM set ocp_text command to change this message.
2.4 Displaying the Hardware Configuration View the system hardware configuration from the SRM console. It is useful to view the hardware configuration to ensure that the system recognizes all devices, memory configuration, and network connections. Use the following SRM console commands to view the system configuration. show boot* Displays the boot environment variables. show config Displays the logical configuration of interconnects and buses on the system and the devices found on them.
2.4.1 Displaying Boot Environment Variables Use the show boot* command to list the boot environment variables. Use the set command with a variable to set up the boot environment. See Chapter 3 for more information on setting boot environment variables. Example 2–5 Show Boot* P00>>> show boot* boot_dev boot_file boot_osflags boot_reset bootdef_dev booted_dev booted_file booted_osflags 2-14 ES45 Owner's Guide dka0.0.0.1.1 a OFF dka0.0.0.1.
boot_dev Device or device list from which booting is to be attempted, here SCSI device dka0. boot_file The default file name used for the primary bootstrap when no file name is specified by the boot command. boot_osflags Boot flags, here the Tru64 UNIX “a” (autoboot) flag. boot_reset Action taken in response to an error halt or boot command. OFF, the default, indicates a warm boot (no full reset is performed).
2.4.2 Displaying the Logical Hardware Configuration Use the show config command to display the logical configuration. To display the physical configuration, issue the show fru command. Example 2–6 Show Config P00>>> show config Compaq Computer Corporation Compaq AlphaServer ES45 Model 2B Firmware SRM Console: PALcode: Serial ROM: RMC ROM: RMC Flash ROM: V5.9-9 OpenVMS PALcode V1.91-33, Tru64 UNIX PALcode V1.87-27 V2.18-F V1.8 V1.
Firmware. Version numbers of the SRM console, PALcode, serial ROM, RMC ROM, and RMC flash ROM Processors. Processors present, processor version and clock speed, and amount of backup cache Core logic. Version numbers of the chips that form the interconnect on the system board Memory.
Example 2–6 Show Config (Continued) Slot 7 8 9 10 11 12 16 Option Acer Labs M1543C ELSA GLoria Synergy DECchip 21152-AA DECchip 21041-AA DE500-AA Network Con Yukon PCI Hot-Plug C Acer Labs M1543C IDE Hose 0, Bus 0, PCI − 33 MHz Bridge to Bus 1, ISA vga0.0.0.8.0 Bridge to Bus 2, PCI ewe0.0.0.10.0 00-00-F8-1F-AE-0A ewf0.0.0.11.0 00-00-F8-1B-0B-24 dqa.0.0.16.0 dqb.0.1.16.0 dqa0.0.0.16.0 TOSHIBA CD-ROM XM- 6302B Option Floppy Hose 0, Bus 1, ISA dva0.0.0.1000.
NOTE: The naming of devices (for example,dqa.0.0.15.0) follows the conventions given in Table 2–4. The slots in Example 2–6 are from the Model 2B ten-slot backplane and are explained below. An asterisk (*) indicates slots that contain a PCI card. Hose 0, Bus 0, PCI Slot 7 Onboard Acer chip. Provides bridge to Bus 1, ISA Slot 8* VGA card Slot 9* Bridge chip to Bus 2, PCI Slot 10* Ethernet card Slot 11* Ethernet card Slot 12 Onboard PCI hot-plug controller Hose 0, Bus 1, ISA The floppy drive.
Table 2–1 Physical I/O Slots Map to Logical Slots: Model 1B Physical Slot SRM Logical ID (7-Slot) 1 Hose 0 Slot ID 11 2 Hose 0 Slot ID 10 3 Hose 2 Slot ID 5 4 Hose 3 Slot ID 2 5 Hose 3 Slot ID 1 7 Hose 1 Slot ID 2 8 Hose 1 Slot ID 1 Table 2–2 Physical I/O Slots Map to Logical Slots: Model 2B Physical Slot 2-20 SRM Logical ID 1 Hose 2 Slot ID 1 2 Hose 2 Slot ID 2 3 Hose 0 Slot ID 11 4 Hose 3 Slot ID 2 5 Hose 3 Slot ID 1 6 Hose 0 Slot ID 10 7 Hose 1 Slot ID 2 8 Hose 1 Slot ID
Table 2–3 Physical I/O Slots Map to Logical Slots: Model 3B Physical Slot SRM Logical ID (10-Slot Legacy PCI) 1 Hose 2 Slot ID 1 2 Hose 2 Slot ID 2 3 Hose 0 Slot ID 11 4 Hose 3 Slot ID 2 5 Hose 3 Slot ID 1 6 Hose 0 Slot ID 10 7 Hose 1 Slot ID 2 8 Hose 1 Slot ID 1 9 Hose 0 Slot ID 9 10 Hose 0 Slot ID 8 Operation 2-21
2.4.3 Displaying the Bootable Devices Use the show device command to display the devices from which the operating system can be booted. Example 2–7 Show Device P00>>> show device dka0.0.0.1.1 dka100.1.0.1.1 dka200.2.0.1.1 dkb0.0.0.3.1 dqa0.0.0.15.0 dva0.0.0.1000.0 ewa0.0.0.4.1 ewb0.0.0.2002.1 pka0.7.0.1.1 pkb0.7.0.3.1 pkc0.7.0.2000.1 pkd0.7.0.2001.
Table 2–4 Device Naming Conventions Category Description The device, dqa0 is used as an example in the following device category and description. Two-letter designator of port or class driver dq Driver ID dk SCSI drive or CD ew Ethernet port dq IDE CD-ROM fw FDDI device dr RAID set device mk SCSI tape du DSSI disk mu DSSI tape dv Diskette drive pk SCSI port ei Ethernet port pu DSSI port pz KZPCC-CE RAID controller Storage adapter ID One-letter designator of storage adapter a (a, b, c…).
2.4.4 Viewing the Memory Configuration Use the show memory command to view the configuration of main memory. Example 2–8 Show Memory P00>>> show memory Array Size --------- ---------0 4096Mb 1 1024Mb 2 4096Mb 3 1024Mb Base Address Intlv Mode ---------------- ---------0000000000000000 2-Way 0000000200000000 2-Way 0000000100000000 2-Way 0000000240000000 2-Way 10240 MB of System Memory The show memory display corresponds to the memory array configuration described in Chapter 4.
2.5 Setting SRM Environment Variables You may need to set several SRM console environment variables and built-in utilities to configure the system. Set environment variables at the P00>>> prompt. • To check the setting for a specific environment variable, enter the show envar command, where the name of the environment variable is substituted for envar. To see a list of the environment variables, enter the show* command.
2.6 Setting Console Security You can set the SRM console to secure mode to prevent unauthorized persons from modifying the system parameters or otherwise tampering with the system from the console. When the SRM is set to secure mode, you can use only two console commands: • The boot command, to boot the operating system. • The continue command, to resume running the operating system if you have inadvertently halted the system.
2.6.1 Setting the Console Password Set the console password with the set password command. A password is required for operating the system in secure mode.
The set password command sets the console password for the first time or changes an existing password. It is necessary to set the password only if the system is going to operate in secure mode. The syntax is: set password Setting a password. If a password has not been set and the set password command is issued, the console prompts for a password and verification. The password and verification are not echoed. Changing a password.
2.6.2 Setting the Console to Secure Mode To set the console to secure mode, first set the password. Then enter the set secure command. The system immediately enters secure mode. Example 2–10 Set Secure P00>>> set secure Console is secure. Please login. P00>>> b dkb0 Console is secure - parameters are not allowed. P00>>> login Please enter the password: P00>>> b dkb0 (boot dkb0.0.0.3.1) . . . The set secure command enables secure mode.
2.6.3 Turning Off Security During a Console Session The login command turns off the security features, enabling access to all SRM console commands during the current console session. The system automatically returns to secure mode as soon as the boot or continue command is entered or when the system is reset. Example 2–11 Login P00>>> Secure P00>>> Please Please P00>>> Please P00>>> login not set. Please set the password.
When you enter the login command, you are prompted for the current system password. If a password has not been set, a message is displayed indicating that there is no password in NVRAM. If a password has been set, this prompt is displayed: Please enter the password: If the password entered matches the password in NVRAM, when the prompt is redisplayed the console is no longer in secure mode and all console commands can be performed during the current console session.
2.6.4 Returning to User Mode The clear password command clears the password environment variable, setting it to zero. Once the password is cleared, you are returned to user mode. Example 2–12 Clear Password P00>>> clear password Please enter the password: Console is secure P00>>> clear password Please enter the password: Password successfully cleared. P00>>> The wrong password is entered. The system remains in secure mode. The password is successfully cleared.
2.7 Updating Firmware Typically, you update system firmware whenever the operating system is updated. You might also need to update firmware if you add I/O device controllers and adapters, if enhancements are made to the firmware, or if the serial ROM or RMC firmware become corrupted. Sources of Firmware Updates The system firmware resides in the flash ROM located on the system board. The Alpha Systems Firmware Update Kit comes on a CD-ROM, which is updated quarterly.
2.7.1 Firmware Update Utility The system firmware is updated from a Loadable Firmware Update Utility (LFU). When you boot the medium containing the update image, the LFU banner and command descriptions are displayed. Enter commands at the UPD> prompt. Before updating the firmware, enter the list command to list the current revision of the firmware. Enter the update command to update the firmware automatically. Example 2–13 Update Utility Display Checking dqa0.0.0.16.0 for the option firmware files. . .
Device Current Revision Filename Update Revision SRM V5.9-8 srm_fw V5.9-9 srom V2.17-F srom_fw V2.18-F UPD> u Confirm update on: SRM srom [Y/(N)]y WARNING: updates may take several minutes to complete for each device. DO NOT ABORT! SRM Updating to V5.9-9... Verifying V5.9-9... PASSED. srom Updating to V2.18-F... Verifying V2.18-F...PASSED.
2.7.2 Manual Updates If RMC firmware or serial ROM (SROM) become corrupted, you can perform a manual update. 1. Boot the update medium. 2. At the UPD> prompt, enter the exit command and answer y at the prompt: UPD> exit Do you want to do a manual update [y/(n)] y AlphaServer ES45 Console V5.9-9, built on Jan 9,2001 at 05:02:30 3. To update RMC firmware, enter update rmc. To update the serial ROM (SROM), enter update srom.
2.7.3 Updating from the CD-ROM You can update the system firmware from CD-ROM. 1. At the SRM console prompt, enter the show device command to determine the drive name of the CD-ROM drive. 2. Load the Alpha Systems Firmware Update CD into the drive. 3. Boot the system from the CD, using the drive name determined in step 1 (for example, dqa0). P00>>> boot dqa0 4. Enter the update command at the UPD> prompt. 5. When the update is complete, exit from the Firmware Update Utility.
2.7.4 Updating from an OpenVMS System Disk You can update the firmware from an OpenVMS system disk. 1. Download the firmware update image from the Firmware Updates Web site. 2. Rename the downloaded file to fwupdate.exe. 3. Enter the following commands on the OpenVMS Alpha system: $ set file/attr=(rfm:fix,lrl:512,mrs:512,rat:none) fwupdate.exe $ copy/contiguous fwupdate.exe "system_disk":[sys0.sysexe] NOTE: Insert the name of your system disk in place of "system_disk,” for example, dka100:. 4.
2.7.5 Updating from the Network You can update firmware from the network using the MOP protocol for OpenVMS or the BOOTP protocol for Tru64 UNIX. Updating Firmware Using BOOTP 1. Download the firmware update image from the Firmware Updates Web site. 2. Copy the downloaded file to a UNIX based network server for BOOTP booting on the system. For details on configuring the BOOTP server, refer to Tru64 UNIX documentation or the system's Firmware Release Notes document. 3.
Chapter 3 Booting and Installing an Operating System This chapter gives instructions for booting the Tru64 UNIX, OpenVMS, or Linux operating systems and for starting an operating system installation. Refer to your operating system documentation for complete instructions on booting or starting an installation.
3.1 Setting Boot Options You can set a default boot device, boot flags, and network boot protocols by using the SRM set command with environment variables. Once these environment variables are set, the boot command defaults to the stored values. You can override the stored values for the current boot session by entering parameters on the boot command line. For more information on setting boot options, see Chapter 5.
3.1.1 auto_action The SRM auto_action environment variable determines the default action the system takes when the system is power cycled, reset, or experiences a failure.
3.1.2 bootdef_dev The bootdef_dev environment variable specifies one or more devices from which to boot the operating system. When more than one device is specified, the system searches in the order listed and boots from the first device. Enter the show bootdef_dev command to display the current default boot device. Enter the show device command for a list of all devices in the system.
3.1.3 boot_file The boot_file environment variable specifies the default file name to be used for booting when no file name is specified by the boot command. The syntax is: set boot_file filename Example P00>>> set boot_file “” NOTE: This command clears the boot file setting and sets the string to empty.
3.1.4 boot_osflags The boot_osflags environment variable sets the default boot flags and, for OpenVMS, a root number. Boot flags contain information used by the operating system to determine some aspects of a system bootstrap. Under normal circumstances, you can use the default boot flag settings. To change the boot flags for the current boot only, use the flags_value argument with the boot command. The syntax is: set boot_osflags flags_value The flags_value argument is specific to the operating system.
Linux Systems If aboot.conf contains (0: 1/vmlinux.gz ro root=/dev/sda2), the system can be booted by one of the following methods: 1. set boot_file set boot_osflags 0 boot dka0 ---or--2. boot dka0 -file "" -flags 0 ---or--3. set boot_file 1/vmlinuz.gz set boot_osflags "ro root=/dev/sda2" boot dka0 Example Single-user mode is typically used for troubleshooting. To make system changes at this run level, you must have read/write privileges.
OpenVMS Systems OpenVMS systems require an ordered pair as the flags_value argument: root_number and boot_flags. root_number boot_flags 3-8 Directory number of the system disk on which OpenVMS files are located. For example: root_number Root Directory 0 (default) [SYS0.SYSEXE] 1 [SYS1.SYSEXE] 2 [SYS2.SYSEXE] 3 [SYS3.SYSEXE] The hexadecimal value of the bit number or numbers set. To specify multiple boot flags, add the flag values (logical OR).
Table 3–1 OpenVMS Boot Flag Settings Flags_Value Bit Number Meaning 1 0 Bootstrap conversationally (enables you to modify SYSGEN parameters in SYSBOOT). 2 1 Map XDELTA to a running system. 4 2 Stop at initial system breakpoint. 8 3 Perform diagnostic bootstrap. 10 4 Stop at the bootstrap breakpoints. 20 5 Omit header from secondary bootstrap image. 80 7 Prompt for the name of the secondary bootstrap file. 100 8 Halt before secondary bootstrap.
Legal values are nvram and bootp. The default value is bootp. Set this environment variable if you are booting Tru64 UNIX from a RIS server. To list the network devices on your system, enter the show device command. The Ethernet controllers start with the letters “ei” or “ew,” for example, ewa0. The third letter is the adapter ID for the specific Ethernet controller. Replace the asterisk (*) with the adapter ID letter when entering the command.
3.1.6 ei*0_protocols or ew*0_protocols The ei*0_protocols or ew*0_protocols environment variable sets network protocols for booting and other functions. To list the network devices on your system, enter the show device command. The Ethernet controllers start with the letters “ei” or “ew,” for example, ewa0. The third letter is the adapter ID for the specific Ethernet controller. Replace the asterisk (*) with the adapter ID letter when entering the command.
Example P00>>> show device . . . ewa0.0.0.1001.0 EWA0 ewb0.0.0.12.0 EWB0 ewc0.0.0.13.0 EWC0 . . .
3.2 Booting Tru64 UNIX Tru64 UNIX can be booted from a CD-ROM on a local drive (a CD-ROM drive connected to the system), from a local SCSI disk, or from a UNIX RIS server. Example 3–1 Booting Tru64 UNIX from a Local SCSI Disk P00>>> sho dev dka0.0.0.1.1 dka100.1.0.1.1 dka200.2.0.1.1 dka300.3.0.1.1 dkc0.0.0.1.0 dkc100.1.0.1.0 dkc200.2.0.1.0 dkc300.3.0.1.0 dqa0.0.0.15.0 dva0.0.0.1000.0 ewa0.0.0.4.1 pka0.7.0.1.
using 39275 buffers containing 306.83 megabytes of memory Master cpu at slot 0 Starting secondary cpu 1 Starting secondary cpu 2 Starting secondary cpu 3 Firmware revision: 5.9-9 PALcode: UNIX version 1.87-27 Compaq AlphaServer ES45 Model 2 . . . . The system is ready. Compaq Tru64 UNIX V5.1A-8 (Rev. 1764) console login: Example 3–1 shows a boot from a local SCSI drive. The example is abbreviated. For complete instructions on booting UNIX, see the Tru64 UNIX Installation Guide.
3.2.1 Booting Tru64 UNIX over the Network To boot your Tru64 UNIX system over the network, make sure the system is registered on a Remote Installation Services (RIS) server. See the Tru64 UNIX document entitled Sharing Software on a Local Area Network for registration information. Example 3–2 RIS Boot P00>>> show device dka0.0.0.1.1 DKA0 dka100.1.0.1.1 DKA100 dka200.2.0.1.1 DKA200 dkb0.0.0.3.1 DKB0 dqa0.0.0.15.0 DQA0 dva0.0.0.1000.0 DVA0 ewa0.0.0.4.1 EWA0 ewb0.0.0.2002.1 EWB0 pka0.7.0.1.1 PKA0 pkb0.7.0.
Systems running Tru64 UNIX support network adapters, designated ew*0 or ei*0. The asterisk stands for the adapter ID (a, b, c, and so on). 1. Power up the system. The system stops at the SRM console prompt, P00>>>. 2. Set boot environment variables, if desired. See Section 3.1. 3. Enter the show device command drive for your device. 4. Enter the following commands. Example 3–2 assumes you are booting from ewa0. If you are booting from another drive, enter that device name instead.
3.3 Starting a Tru64 UNIX Installation Tru64 UNIX is installed from the CD-ROM drive connected to the system. The display that you see after you boot the CD depends on whether your system console is a VGA monitor or a serial terminal. Example 3–3 Text-Based Installation Display P00>>> b dqa0 (boot dqa0.0.0.15.0 -flags a block 0 of dqa0.0.0.15.0 is a valid boot block reading 16 blocks from dqa0.0.0.15.
There are two types of installations: o The Default Installation installs a mandatory set of software subsets on a predetermined file system layout. o The Custom Installation installs a mandatory set of software subsets plus optional software subsets that you select. You can customize the file system layout. The UNIX Shell with superuser perienced UNIX system or disk option puts your system in single-user mode privileges.
3.4 Booting Linux Obtain the Linux installation document and install Linux on the system. Then verify the firmware version, boot device, and boot parameters, and issue the boot command. The procedure for installing Linux on an Alpha system is described in the Alpha Linux installation document for your Linux distribution. The installation document can be downloaded from the following Web site: http://www.compaq.com/alphaserver/linux You need V5.6-3 or higher of the SRM console to install Linux.
3. After installing Linux, set boot environment variables appropriately for your installation. The typical values indicating booting from dka0 with the first aboot.conf entry are shown in this example. P00>>> set bootdef_dev dka0 P00>>> set boot_file P00>>> set boot_osflags 0 P00>>> show boot* boot_dev dka0.0.0.17.0 boot_file boot_osflags 0 boot_reset OFF bootdef_dev booted_dev booted_file booted_osflags 4. From SRM enter the boot command. The following example shows an abbreviated boot output.
Booting GENERIC on Titan variation Privateer using machine vector PRIVATEER from SRM Command line: root=/dev/sda2 console=ttyS0 memcluster 0, usage 1, start 0, end 362 memcluster 1, usage 0, start 362, end 262135 memcluster 2, usage 1, start 262135, end 262144 freeing pages 362:1024 freeing pages 1700:262135 SMP: 4 CPUs probed -- cpu_present_mask = f On node 0 totalpages: 262144 . . . autorun ... ... autorun DONE. NET4: Linux TCP/IP 1.0 for NET4.
3.5 Booting OpenVMS OpenVMS can be booted from a CD-ROM on a local drive (the CD-ROM drive connected to the system) or from a CD-ROM drive on the InfoServer. Example 3–5 Booting OpenVMS from the Local CD-ROM Drive P00>>> show device dka0.0.0.1.1 DKA0 RZ2CA-LA dka100.1.0.1.1 DKA100 RZ2CA-LA dqa0.0.0.15.0 DQA0 TOSHIBA CD-ROM XM-6302B dva0.0.0.1000.0 DVA0 ewa0.0.0.6.1 EWA0 00-00-F8-10-D6-03 pka0.7.0.1.1 PKA0 SCSI Bus ID 7 P00>>> . . . P00>>> boot -flags 0,0 dqa0 (boot dqa0.0.0.1.
Example 3–5 shows a boot from a CD-ROM on a local drive. The example is abbreviated. For complete instructions on booting OpenVMS, see the OpenVMS installation document. 1. Power up the system. The system stops at the SRM console prompt, P00>>>. 2. Set boot environment variables, if desired. See Section 3.1. 3. Install the boot medium. For a network boot, see Section 3.2.1. 4. Enter the show device command drive for your device. 5.
3.5.1 Booting OpenVMS from the InfoServer You can boot OpenVMS from a LAN device on the InfoServer. The devices are designated EW*0 or EI*0. The asterisk stands for the adapter ID (a, b, c, and so on). Example 3–6 InfoServer Boot P00>>> show device dka0.0.0.1.1 DKA0 RZ2CA-LA dka100.1.0.1.1 DKA100 RZ2CA-LA dqa0.0.0.15.0 DQA0 TOSHIBA CD-ROM XM-6302B dva0.0.0.1000.0 DVA0 ewa0.0.0.6.1 EWA0 00-00-F8-10-D6-03 pka0.7.0.1.1 PKA0 SCSI Bus ID 7 P00>>> . . . P00>>> boot -flags 0,0 -file apb_073 ewa0 (boot ewa0.
Network Initial System Load Function Version 1.2 FUNCTION FUNCTION ID 1 Display Menu 2 Help 3 Choose Service 4 Select Options 5 Stop Enter a function ID value: Enter a function ID Value: 3 OPTION OPTION ID 1 Find Services 2 Enter known Service Name Enter an Option ID value: 2 Enter a Known Service Name: ALPHA_V72-1_SSB OpenVMS (TM) Alpha Operating System, Version V7.3 1. Power up the system. The system stops at the P00>>> console prompt. 2.
3.6 Starting an OpenVMS Installation After you boot the operating system CD-ROM, an installation menu is displayed on the screen. Choose item 1 (Install or upgrade OpenVMS Alpha). Refer to the OpenVMS installation document for information on creating the system disk. Example 3–7 OpenVMS Installation Menu OpenVMS (TM) Alpha Operating System, Version V7.3 Copyright © 1999 Digital Equipment Corporation. All rights reserved. Installing required known files... Configuring devices...
1. Boot the OpenVMS operating system CD-ROM. 2. Choose option 1 (Install or upgrade OpenVMS Alpha). To create the system disk, see the OpenVMS installation document.
Chapter 4 Configuring and Installing Components This chapter shows how to configure and install components in a tower or pedestal system. Installation of components in a rackmount system is reserved for service providers and self-maintenance customers.
! WARNING: To prevent injury, access is limited to persons who have appropriate technical training and experience. Such persons are expected to understand the hazards of working within this equipment and take measures to minimize danger to themselves or others. These measures include: 1. Remove any jewelry that may conduct electricity. 2. If accessing the system card cage, power down the system and wait 2 minutes to allow components to cool. 3.
4.1 Removing Enclosure Panels Open and remove the front door. Loosen the screws that allow you to remove the top and side panels.
To Remove Enclosure Panels from a Tower The enclosure panels are secured by captive screws. , lift up and away to remove the front door . To remove the top panel, loosen the top left and top right screws . Slide the top panel back and lift it off the system. To remove the left panel, loosen the screw at the top and the screw at 1. From the open position 2. 3. the bottom. Slide the panel back and then tip it outward. Lift it off the system. 4. Go to Section 4.
Figure 4–2 Enclosure Panel Removal (Pedestal) 1 3 2 PK0234A Configuring and Installing Components 4-5
To Remove Enclosure Panels from a Pedestal The enclosure panels are secured by captive screws. 1. From the open position, lift up and away doors are removed in the same way). to remove the front door (both 2. Remove the top enclosure panel by loosening the captive screws shown in . Slide the top panel back and lift it off the system. 3. To remove the right enclosure panel, loosen the captive screw shown in . Slide the panel back and then tip it outward. Lift the panel from the three tabs. 4.
4.2 Removing Covers from the System Chassis WARNING: To prevent injury, access is limited to persons who have appropriate technical training and experience. Such persons are expected to understand the hazards of working within this equipment and take measures to minimize danger to themselves or others. V @ >240VA WARNING: High current area. Currents exceeding 240 VA can cause burns or eye injury. Avoid contact with parts or remove power prior to access.
Figure 4–3 and Figure 4–4 show the location and removal of covers on the tower and pedestal/rackmount systems, respectively. The numbers in the illustrations correspond to the following: 4-8 3mm Allen captive quarter-turn screw that secures each cover. Pull-up spring-loaded ring that releases cover. Each cover has at least one pull-up ring. Fan area cover. This area contains the main system fan and a redundant fan. System card cage cover. This area contains CPUs and memory DIMMs.
Figure 4–3 Removing Covers from a Tower 5 2 1 2 3 1 4 2 2 1 PK0216A Configuring and Installing Components 4-9
Figure 4–4 Removing Covers from a Pedestal/Rack 4 2 1 2 1 2 3 1 2 5 4-10 ES45 Owner's Guide PK0215A
4.3 Before Installing Components You must shut down the operating system, turn off power to the system, and unplug the power cord from each supply before installing CPUs, memory DIMMs, or removable media devices. NOTE: You can install a power supply for redundancy at any time without shutting down the system. WARNING: To prevent injury, access is limited to persons who have appropriate technical training and experience.
4.4 Memory Allocation The SRM console allocates enough memory for most configurations. If you install options that require more memory than the SRM console has allocated, the console dynamically resizes itself to provide additional memory to support the new configuration. A crash and reboot cycle can occur several times until the console has allocated enough memory. Example 4–1 shows an abbreviated example of the output to a serial console screen. Example 4–1 Memory Allocation Crash/Reboot Cycle . . .
SYSFAULT CPU0 - pc = 0014faac exception context saved starting at 001FD7B0 GPRs: 0: 00000000 00048FF8 16: 00000000 0000001E 1: 00000000 00150C80 17: 00000000 EFEFEFC8 2: 00000000 001202D0 18: 00000000 001FD2F8 . . .
After the console completes its final reinitialization, the console banner is displayed, followed by the P00>>> prompt. Enter the show heap_expand command to verify that the console has allocated more memory. You can then boot the operating system. No other action is required, and the crash/reboot cycle should not occur again.
4.5 Power Supply Configuration The system can have a single power supply (Model 2 has minimum of two power supplies) or redundant configurations. You can add a power supply for redundancy at any time without shutting down the system.
System Models 1B, 2B, and 3B have a minimum configuration of one power supply and the Model 2 has a minimum configuration of two power supplies. Minimum Power Supply Configurations The following is the maximum system configuration for Models 1B, 2B, and 3B with one power supply: • • • Two CPUs One storage cage (six hard drives) Four to sixteen DIMMs Two Power Supply Configuration. Two power supplies are required if the system has more than two CPUs, a second storage cage, or more than 16 DIMMs.
4.
WARNING: Hazardous voltages are contained within the power supply. Do not attempt to service. Return to factory for service. 1. Unplug the AC power cord. 2. that secure the power supply bracket. Loosen the three Phillips screws (There is no need to remove the screws.) Remove the bracket . 3. If you are installing a new supply, remove the screw and blank cover . If you are replacing a power supply, release the latch on the supply and pull the supply out of the system. 4.
4.7 CPU Configuration Before installing additional CPUs, become familiar with the location of the CPU slots and the configuration rules.
Figure 4–8 CPU Slot Locations (Tower View) CPU 2 CPU 0 CPU 1 CPU 3 PK0229A CPU Configuration Rules 1. A CPU must be installed in slot 0. The system will not power up without a CPU in slot 0. 2. CPU cards must be installed in numerical order, starting at CPU slot 0. See Figure 4–7 and Figure 4–8. 3. CPUs must be identical in speed.
4.8 Installing CPUs Figure 4–9 CPU Card Installation (Pedestal/Rack View) Slot 3 3 Slot 1 Slot 0 Slot 2 1 2 PK0240B ! WARNING: To prevent injury, access is limited to persons who have appropriate technical training and experience. Such persons are expected to understand the hazards of working within this equipment and take measures to minimize danger to themselves or others.
! WARNING: Do not remove CPUs until the green LEDs are off (approximately 20 seconds after a power-down). ! WARNING: Modules have parts that operate at high temperatures. Wait 2 minutes after power is removed before touching any module. WARNING: To prevent injury, unplug the power cord from each power supply before installing components. 1. Shut down the operating system and turn off power to the system. Unplug the power cord from each power supply. 2.
4.9 Memory Configuration Become familiar with the rules for memory configuration before adding the dual inline memory modules (DIMMs) to the system. Memory Performance Considerations Interleaved operations reduce the average latency and increase the memory throughput over non-interleaved operations. With one memory option (4 DIMMs) installed, memory interleaving will not occur. With two identical memory options (8 DIMMs) installed, memory read-write operations are twoway interleaved.
Figure 4–10 Stacked and Unstacked DIMMs Unstacked DIMMS Stacked DIMMS PK1209 4-24 ES45 Owner's Guide
Rules for DIMM Installation Refer to Figure 4–11 or Figure 4–12 and observe the following rules for installing DIMMs. • • • • • You can install up to 32 DIMMs (Models 2, 2B, and 3B) and up to 16 DIMMs (Model 1B). An option consists of a set of 4 DIMMs. You must install all 4 DIMMs. Fill sets in numerical order. Populate all 4 slots in Set 0, then populate Set 1, and so on.
Figure 4–11 Memory Configuration (Pedestal/Rack View) Set # 0 4 6 2 0 4 6 2 MMB 0 Array 0 Set # 0 & 4 Set # 1 5 7 3 1 5 7 3 MMB 1 Set # 0 4 6 2 0 4 6 2 Set # 1 5 7 3 1 5 7 3 Array 1 Set # 1 & 5 Array 2 Set # 2 & 6 MMB 2 Array 3 Set # 3 & 7 MMB 3 J9 J8 J7 J6 J5 J4 J3 J2 PK0202A 4-26 ES45 Owner's Guide
Figure 4–12 Memory Configuration (Tower View) J9 J8 J7 J6 73 15 Set # 73 15 J5 J4 J3 J2 MMB 3 Set # 0 46 2 0 46 2 MMB 2 Set # 73 15 73 15 MMB 1 Set # 0 4 MMB 0 62 0 46 2 Array 0 Set # 0 & 4 Array 2 Set # 2 & 6 Array 1 Set # 1 & 5 Array 3 Set # 3 & 7 PK0203A Configuring and Installing Components 4-27
4.
! WARNING: To prevent injury, access is limited to persons who have appropriate technical training and experience. Such persons are expected to understand the hazards of working within this equipment and take measures to minimize danger to themselves or others. ! WARNING: Do not remove memory modules until the green LEDs are off (approximately 20 seconds after a power-down). ! WARNING: Modules have parts that operate at high temperatures.
7. To install the DIMM, align the notches on the gold fingers with the connector keys as shown in Figure 4–14. 8. Secure the DIMM with the clips on the MMB slot. Figure 4–14 Aligning DIMM in MMB 1 2 3 1 3 PK0953A 9. Reinstall the MMB. 10. Replace the system card cage cover and enclosure covers. 11. Reconnect the power cords. Verification 1. Turn on power to the system. 2. During power-up, observe the screen display for memory. The display shows how much memory is in each array. 3.
4.11 PCI Configuration This section describes the Model 1B six-slot (one slot AGP), Model 2B ten-slot, and Model 3B legacy ten-slot PCI I/O backplanes. PCI modules are either designed specifically for 5.0 volts or 3.3 volts, or are universal in design and can plug into either 3.3 or 5.0 volt slots. CAUTION: PCI modules designed specifically for 5.0 volts or 3.3 volts are keyed differently. Check the keying before you install the PCI module and do not force it in.
4.11.1 Model 1B PCI Backplane Figure 4–15 Model 1B Backplane (Seven Slots) 6-Slot PCI, 1-Slot AGP, I/O Backplane Quick Reference SRM Console to Physical Slot Location SRM Console Physical Slot 1 2 3 Max Speed Voltage 33 MHz 5.0V 33 MHz 5.0V AGP 4X 1.5V 4 5 66 MHz 3.3V 66 MHz 3.3V Yes Yes Hose 3 Slot ID 2 Hose 3 Slot ID 1 Hose 1 Slot ID 2 Slot ID 1 7 8 66 MHz 3.3V 66 MHz 3.
4.11.2 Model 2B PCI Backplane Figure 4–16 Model 2B (Ten Slots) 10-Slot PCI I/O Backplane 1 2 3 Max Speed 66 MHz 66 MHz 33 MHz Voltage 3.3V 3.3V 5.0V 4 5 6 7 8 9 10 66 MHz 66 MHz 33 MHz 66 MHz 66 MHz 33 MHz 33 MHz 3.3V 3.3V 5.0V 3.3V 3.3V 5.0V 5.
4.11.3 Model 3B PCI Backplane Figure 4–17 Model 3B (10-Slot Legacy Backplane) 10-Slot PCI I/O Backplane 1 2 3 Max Speed 33 MHz 33 MHz 33 MHz Voltage 5.0V 5.0V 5.0V 4 5 6 7 8 9 10 66 MHz 66 MHz 33 MHz 33 MHz 33 MHz 33 MHz 33 MHz 3.3V 3.3V 5.0V 5.0V 5.0V 5.0V 5.
4.12 Installing PCI Cards Some PCI options require drivers to be installed and configured. These options come with a floppy or a CD-ROM. Refer to the installation document that came with the option and follow the manufacturer's instructions. ! WARNING: To prevent injury, access is limited to persons who have appropriate technical training and experience. Such persons are expected to understand the hazards of working within this equipment and take measures to minimize danger to themselves or others.
Figure 4–18 PCI Card Installation (Pedestal/Rack View) 6 2 1 4 3 7 5 MR0027 CAUTION: Hot swap is not currently available with the ES45, however the hardware is on the system. Do not press switch or latch on the hot-swap board when the system is running. Pressing any of these switches may result in loss of data. Complete the following procedure to add or remove a PCI option card. 1. Turn off the system power. 2. Press in latch button 3. Remove screw 4-36 and open the latch. if present.
If you are removing a PCI option card, perform step 4. or If you are inserting a PCI option into a blank slot, perform step 5. 4. Remove the PCI option card . 5. To install a PCI option card into an unused slot, remove the blank bulkhead . Replace screw if one was present . Close latch . 6. Install the new PCI option card 7. 8. Verification 1. Turn on the system power. 2. During power-up, observe the screen display for PCI information. The new option should be listed in the display. 3.
4.13 Installing Universal Hard Disk Drives The system uses hot-pluggable universal hard disk drives. Hotpluggable drives can be replaced without removing power from the system or interrupting the transfer of data over the SCSI bus. ! 4-38 WARNING: To prevent injury, access is limited to persons who have appropriate technical training and experience. Such persons are expected to understand the hazards of working within this equipment and take measures to minimize danger to themselves or others.
Figure 4–19 Installing a Hard Drive 3 2 1 4 MR0064 Configuring and Installing Components 4-39
Installing a Drive 1. Access the storage drive area and remove the drive blank for the next available slot (drives are installed left to right, SCSI ID 0 – 5). 2. Insert the new drive into the cage and push it in while pivoting the release lever towards the drive. 3. Push the release lever in until it engages the ejector button . Swapping a Drive 1. Press the ejector button tion. in and pivot the release lever to the open posi- 2.
4.13.1 Disk Drive Status LEDs Three LEDs are located on the front of the disk drive carrier: a Drive Activity LED, an On-Line LED, and a Drive Failure LED. Figure 4–20 shows the location of the LEDs and Table 4–1 explains the status LED displays. Figure 4–20 Location of Drive Status LEDs LEDs Drive Activity LED (Green) Depending on the host controller, this LED can either flash by itself or in unison with the On-Line LED when there is SCSI bus activity. This LED is off when there is no bus activity.
Table 4–1 Disk Drive Status LED Conditions LED is off LED is on LED is flashing This display at initial startup may mean: The operational drive is not being accessed. The drive status is one of the following: • • • • The drive is a replacement drive to be rebuilt. The drive is an inactive spare disk. The drive is spinning up during POST. The SCSI controller cannot control the LED If the display does not change within a few minutes, the drive is non-operational.
LED is off LED is on LED is flashing The drive is being accessed or spinning up. The drive status is one of the following: • • • • Replacement drive to be rebuilt The drive is an active spare disk. The drive is spinning up during POST. The SCSI controller cannot control LED. The drive is being accessed. The drive status is one of the following: • • • • Drive is being rebuilt Array capacity expansion in progress The drive is operational and active. The drive is configured as part of an array.
4.14 Installing a Removable Media Device Figure 4–21 Installing a 5.
! WARNING: To prevent injury, access is limited to persons who have appropriate technical training and experience. Such persons are expected to understand the hazards of working within this equipment and take measures to minimize danger to themselves or others. WARNING: To prevent injury, unplug the power cord from each power supply before installing components. ! WARNING: Modules have parts that operate at high temperatures. Wait 2 minutes after power is removed before touching any module. 1.
7. Set the SCSI ID on the device as desired. 8. Slide the storage device into the desired storage slot and secure the device to the unit with four of the screws provided inside the removable media drive cage. 9. Pull the floppy cables back in. 10. Slide the removable media cage back in and replace the four screws set aside previously. , route it into the PCI cage, and attach it to the 12. Plug the power cable (4-conductor) into the storage device. 11.
4.15 Installing Disk Drive Cages Install a drive cage in the left bay opening first.
! WARNING: To prevent injury, access is limited to persons who have appropriate technical training and experience. Such persons are expected to understand the hazards of working within this equipment and take measures to minimize danger to themselves or others. WARNING: To prevent injury, unplug the power cord from each power supply before installing components. 1. Shut down the operating system and turn off power to the system. Unplug the power cord from each power supply. 2.
Figure 4–23 Disk Cage Installation 7 8 3 6 PKO975-0B Configuring and Installing Components 4-49
into the system chassis. 10. Connect the power source cable (located inside enclosure) to the drive cage. 11. Attach the 10-pin cable and 68-pin cable to the drive cage. 9. Partially slide the drive cage 12. Slide the cage in the rest of the way and attach it with the four screws set aside previously. 13. Replace fans 3 and 4 (if removed previously), PCI card cage cover, and enclosure panels. 14. Install disk drives. CAUTION: Disk drives must be installed from left to right.
Figure 4–24 Fan Locations 5 6 1 2 3 4 PK0208a Configuring and Installing Components 4-51
4.15.1 Cabling a Second Disk Drive Cage If you are installing a second six-disk drive cage, refer to the following illustration for cable routing.
4.16 External SCSI Expansion External SCSI devices, such as tabletop or rack-mounted storage devices, can be connected to the system using PCI-based SCSI adapters. Use the following rules to determine if a particular device can be used: • The device must be supported by the operating system. Consult the supported options list. • Do not exceed the maximum number of devices supported on the SCSI controller to be used. • Each device on the bus must have a unique SCSI ID.
Chapter 5 Firmware The SRM user interface is the command-line interface that allows you to configure and boot the operating system and verify the configuration of devices. This chapter describes typical functions performed from the SRM console and the commands and environment variables used for these functions.
5.1 Console Overview The system has a console consisting of firmware programs and an attached terminal. The firmware programs consist of software code that is stored within computer chips called flash ROMs that are located on the system board. The chips can be electronically reprogrammed, allowing you to upgrade the code without installing new chips.
console terminal can be either a serial terminal (VT320 or higher, or equivalent) or a VGA monitor. 5.2 Invoking the SRM Console You can invoke the SRM console at power-up or restart, after a system failure, or from RMC. Once you invoke SRM, you enter commands at the console prompt, P00>>>. Invoking SRM from Tru64 UNIX, Linux, or OpenVMS The SRM console is invoked automatically at power-up or after a reset or failure.
5.3 SRM Command Overview Table 5–1 summarizes alphabetically the most frequently used SRM console commands; Table 5–2 gives the command notation formats; and Table 5–3 shows special characters used on the command line. Table 5–1 Summary of SRM Console Commands Command Function boot Loads and starts the operating system. continue Resumes program execution on the specified processor or on the primary processor if none is specified. crash Forces a crash dump at the operating system level.
Table 5–1 Summary of SRM Console Commands (Continued) Command Function show config Displays the logical configuration at the last system initialization. show device Displays a list of controllers and bootable devices in the system. show error Reports errors logged in the EEPROMs. show fru Displays the physical configuration of all field-replaceable units (FRUs). show memory Displays information about system memory. show pal Displays the versions of Tru64 UNIX and OpenVMS PALcode.
Table 5–2 Notation Formats for SRM Console Commands Attribute Conditions Length Up to 255 characters, not including the terminating carriage return or any characters deleted as the command is entered. To enter a command longer than 80 characters, use the backslash character for line continuation (see Table 5–3). Case Upper- or lowercase characters can be used for input. Characters are displayed in the case in which they are entered. Abbreviation Only by dropping characters from the end of words.
Table 5–3 Special Characters for SRM Console Character Function Return or Enter Terminates a command line. No action is taken on a command until it is terminated. If no characters are entered and this key is pressed, the console just redisplays the prompt. Backslash (\) Continues a command on the next line. Must be the last character on the line to be continued. Delete Deletes the previous character. Ctrl/A Toggles between insert and overstrike modes. The default is overstrike.
Table 5–3 Special Characters for SRM Console (Continued) Character Function Ctrl/Q Resumes output to the console terminal that was suspended by Ctrl/S. Ctrl/R Redisplays the current line. Deleted characters are omitted. This command is useful for hardcopy terminals. Ctrl/S Suspends output to the console terminal until Ctrl/Q is entered. Cleared by Ctrl/C. Ctrl/U Deletes the current line. * Wildcarding for commands such as show.
5.4 Management Tasks Performed from SRM This section lists system management tasks and the related SRM commands.
5.5 Getting Help on SRM Commands The help (or man) command displays basic information about a command. Example 5–1 Help (or Man) P00>>> help set NAME set FUNCTION Set or modify the value of an environment variable. SYNOPSIS set [-integer] [-string] where ={auto_action,bootdef_dev,boot_file,boot_osflags,...} The help (or man) command displays basic information about the use of console commands when the system is in console mode. The syntax is: help (or man) [command . . .
5.5.1 Displaying the Logical Configuration Use the show config command to display the logical configuration of the system. Example 5–2 uses the Model 2B ten-slot backplane. For the physical configuration, see the show fru command (Section 5-18). Example 5–2 Show Config P00>>> show config Compaq Computer Corporation Compaq AlphaServer ES45 Model 2B Firmware SRM Console: PALcode: Serial ROM: RMC ROM: RMC Flash ROM: V5.9-9 OpenVMS PALcode V1.91-33, Tru64 UNIX PALcode V1.87-27 V2.18-F V1.8 V1.
5-12 Firmware. Version numbers of the SRM console, PALcode, serial ROM, RMC ROM, and RMC flash ROM Processors. Processors present, processor version and clock speed, and amount of backup cache Core logic. Version numbers of the chips that form the interconnect on the system board Memory.
Example 5–2 Show Config (Continued) Slot 7 8 9 10 11 12 16 Option Acer Labs M1543C ELSA GLoria Synergy DECchip 21152-AA DECchip 21041-AA DE500-AA Network Con Yukon PCI Hot-Plug C Acer Labs M1543C IDE Option Floppy Option DE500-BA DE500-BA DE500-BA DE500-BA Slot 1/0 Option Adaptec AIC-7899 Slot 1 2 Slot 1/0 1/1 6 P00>> dqa.0.0.16.0 dqb.0.1.16.0 dqa0.0.0.16.0 TOSHIBA CD-ROM XM-6302B Hose 0, Bus 1, ISA dva0.0.0.1000.0 Slot 0 1 2 3 1/1 6 Hose 0, Bus 0, PCI − 33 MHz Bridge to Bus 1, ISA vga0.0.
NOTE: The naming of devices (for example,dqa.0.0.15.0) follows the conventions given in Table 5–8. The slots in Example 5–2 are from the Model 2B ten-slot PCI backplane and are explained below. An asterisk (*) indicates slots that contain a PCI card. Hose 0, Bus 0, PCI Slot 7 On-board Acer chip. Provides bridge to Bus 1, ISA Slot 8* VGA card Slot 9* Bridge chip to Bus 2, PCI Slot 10* Ethernet card Slot 11* Ethernet card Slot 12 Onboard PCI hot-plug controller Hose 0, Bus 1, ISA The floppy drive.
Table 5–5 How Physical I/O Slots Map to Logical Slots: Model 1B Physical Slot SRM Logical ID (7-Slot) 3 Hose 2 Slot ID 5 2 Hose 3 Slot ID 2 3 Hose 3 Slot ID 1 4 Hose 1 Slot ID 2 5 Hose 1 Slot ID 1 6 Hose 0 Slot ID 9 7 Hose 1 Slot ID 8 Table 5–6 How Physical I/O Slots Map to Logical Slots: Model 2B Physical Slot SRM Logical ID 1 Hose 2 Slot ID 1 2 Hose 2 Slot ID 2 3 Hose 0 Slot ID 11 4 Hose 3 Slot ID 2 5 Hose 3 Slot ID 1 6 Hose 0 Slot ID 10 7 Hose 1 Slot ID 2 8 Hose 1 Slot ID
Table 5–7 How Physical I/O Slots Map to Logical Slots: Model 3B Physical Slot 5-16 SRM Logical ID (10-Slot Legacy PCI) 1 Hose 2 Slot ID 1 2 Hose 2 Slot ID 2 3 Hose 0 Slot ID 11 4 Hose 3 Slot ID 2 5 Hose 3 Slot ID 1 6 Hose 0 Slot ID 10 7 Hose 1 Slot ID 2 8 Hose 1 Slot ID 1 9 Hose 0 Slot ID 9 10 Hose 0 Slot ID 8 ES45 Owner's Guide
5.5.2 Displaying the Bootable Devices Use the show device command to display the bootable devices. Example 5–3 Show Device P00>>> show device dka0.0.0.1.1 dka100.1.0.1.1 dka200.2.0.1.1 dkb0.0.0.3.1 dqa0.0.0.15.0 dva0.0.0.1000.0 ewa0.0.0.4.1 ewb0.0.0.2002.1 pka0.7.0.1.1 pkb0.7.0.3.1 pkc0.7.0.2000.1 pkd0.7.0.2001.
5.5.3 Displaying the System FRUs Use the show fru command to view the physical configuration of FRUs. Use the show error command to display FRUs with errors. For the logical configuration, see Section 5.5.1. Example 5–4 Show Fru P00>>> show fru FRUname SMB0 SMB0.CPU0 SMB0.CPU1 SMB0.CPU2 SMB0.CPU3 SMB0.MMB0 SMB0.MMB0.J4 SMB0.MMB0.J8 SMB0.MMB0.J5 SMB0.MMB0.J9 SMB0.MMB0.J2 SMB0.MMB0.J6 SMB0.MMB0.J3 SMB0.MMB0.J7 SMB0.MMB1 SMB0.MMB1.J4 SMB0.MMB1.J8 SMB0.MMB1.J5 SMB0.MMB1.J9 SMB0.MMB1.J2 SMB0.MMB1.
SMB0.CPB0.PCI1 SMB0.CPB0.PCI2 SMB0.CPB0.PCI3 SMB0.CPB0.PCI5 SMB0.CPB0.PCI7 SMB0.CPB0.PCI8 SMB0.CPB0.PCI9 OCP0 PWR0 PWR1 PWR2 FAN1 FAN2 FAN3 FAN4 FAN5 FAN6 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 70-33894-0x 30-49448-01. C05 30-49448-01. C05 30-49448-01.
Misc. Miscellaneous information about the FRUs. For Compaq FRUs, a model name, number, or the common name for the entry in the Part # field. For vendor FRUs, the manufacturer's name.
5.5.4 Displaying FRUs with Errors The show error command displays FRUs that have errors logged to the serial control bus EEPROMs. Example 5–5 Show Error P00>>> show error SMB0 TDD - Type: 1 Test: 1 SubTest: 1 Error: 1 SMB0 SDD - Type: 4 LastLog: 1 Overwrite: 0 P00>>> The output of the show error command is based on information logged to the serial control bus EEPROMs. Both the operating system and the ROM-based diagnostics log errors to the EEPROMs.
5.5.5 Displaying the Memory Configuration Use the show memory command to view the total memory size and location. Example 5–6 Show Memory P00>>> show memory Array Size Base Address Intlv Mode --------- ---------- ---------------- ---------0 4096Mb 0000000000000000 2-Way 1 1024Mb 0000000200000000 2-Way 2 4096Mb 0000000100000000 2-Way 3 1024Mb 0000000240000000 2-Way 10240 MB of System Memory The show memory display corresponds to the memory array configuration shown in Chapter 4.
5.5.7 Displaying the Power Status Use the show power command to display the status of power supplies, fans, and system temperature. If you are not able to access SRM, invoke RMC and issue the env command.
5.5.8 Displaying the SRM Console Version Use the show version command to display the version of the SRM console that is installed. Example 5–9 Show Version P00>>> show version version V5.9-9 Jan 8 2001 17:39:58 The show version command displays the version of the SRM console program that is installed on the system.
5.6 Booting an Operating System The boot command boots the Tru64 UNIX, Linux, or OpenVMS operating system. You can specify a boot device, operating system-specific boot information (boot flags), and an Ethernet protocol for network boots. You can also specify whether the boot program should halt and remain in console mode. Example 5–10 OpenVMS Boot P00>>> boot dkb0 (boot dkb0.0.0.2.1 -flags 0) block 0 of dkb0.0.0.2.1 is a valid boot block reading 1002 blocks from dkb0.0.0.2.
-file filename Specifies the name of a file to load into the system. Use the set boot_file command to set a default boot file (Section 5.14.3). NOTE: For booting from Ethernet, the filename is limited by the MOP V3 load protocol to 15 characters. The MOP protocol is used with OpenVMS systems. -flags [value] Provides additional operating system-specific boot information. In Tru64 UNIX, specifies boot flags. In OpenVMS, specifies system root number and boot flags.
5.7 Testing the System The test command verifies the configuration of the devices in the system.
To run a complete diagnostic test using the test command, the system configuration must include: • A serial loopback connected to the COM2 port (not included) • A parallel loopback connected to the parallel port (not included) • A formatted diskette • A formatted CD-ROM The test script tests devices in the following order: 1. Memory tests (one pass) 2. Read-only tests: DK* disks, DU* disks, DR* disks, DQ* disks, DF* disks, MK* tapes, DV* floppy.
5.8 Forcing a System Crash Dump The crash command causes an operating system that has hung to crash so that you can capture a crash dump to the selected device. Example 5–12 Crash P00>>> crash CPU 0 restarting DUMP: 19837638 blocks available for dumping. DUMP: 118178 wanted for a partial compressed dump. DUMP: Allowing 2060017 of the 2064113 available on 0x800001 device string for dump = SCSI 1 1 0 0 0 0 0. DUMP.
Description The crash command forces an operating system that has stopped responding to crash so that you can capture a crash dump. Syntax crash Press the Halt button or use the RMC halt in command to invoke the SRM console, then enter the crash command to restart the primary CPU and force a crash dump to the selected device. • See the OpenVMS Alpha System Dump Analyzer Utility Manual for information on how to interpret OpenVMS crash dump files.
5.9 Resuming Program Execution The continue command resumes the execution of the operating system on the processor you specify or on the primary processor, if none is specified. Example 5–13 Continue P00>>> halt P00>>> continue continuing CPU Description Typically, you use the continue command if you inadvertently halt the system and want to resume operating system mode.
5.10 Reading a File The more command displays a file one screen at a time. Example 5–14 More P00>>> more el *** Error - CPU 1 failed powerup diagnostics *** Secondary start error . . . P00>>> help * | more Displays the contents of the SRM console’s event log one screen at a time. Displays the contents of online help one screen at a time. Description The SRM more command is similar to the UNIX more command. It is useful for displaying output that scrolls too quickly to be viewed.
5.11 Initializing the System The init command resets the SRM console firmware and reinitializes the hardware. Example 5–15 shows an abbreviated example. Example 5–15 Init P00>>> init Initializing... OpenVMS PALcode V1.90-31, Tru64 UNIX PALcode V1.
starting drivers initializing keyboard starting console on CPU 1 initialized idle PCB initializing idle process PID lowering IPL CPU 1 speed is 1000 MHz create powerup starting console on CPU 2 initialized idle PCB initializing idle process PID lowering IPL CPU 2 speed is 1000 MHz create powerup starting console on CPU 3 initialized idle PCB initializing idle process PID lowering IPL CPU 3 speed is 1000 MHz create powerup initializing GCT/FRU at 21c000 initializing pka pkb ewe ewa ewb ewc ewd dqa dqb Memory
Description The init command restarts the SRM console and reinitializes the hardware. This command is similar to performing a reset, but a reset causes full start-up diagnostics to be performed, whereas init performs only the SRM diagnostics. Syntax init After you use the init command, the system stops in the SRM console because the auto_action environment variable is set by default to halt.
5.12 Creating a Power-Up Script A script (set of commands) named “nvram” is stored in EEROM. Nvram is a user-created power-up script that is always invoked during the power-up sequence. Use the SRM edit command to create or alter the nvram script.
Description You can create an nvram script to include any commands you want the system to execute at power-up. You create and edit the nvram script using the SRM edit command. With edit, lines may be added, overwritten, or deleted. To clear the script, enter line numbers without any text. This deletes the lines. In Example 5–16 an environment variable called “mop3_boot” is created and set to 1 on each power-up. By default, MOP boots send four MOP V4 requests before defaulting to MOP V3.
5.13 Entering the RMC from the Local VGA Monitor Use the rmc command to enter the remote management console from a VGA monitor connected to the system. All RMC commands are available and all output is redirected to the VGA monitor. Example 5–18 Entering RMC from a VGA Monitor Failing Connection P00>>> rmc Unable to allocate COM1.
Description The rmc command allows you to invoke the remote management console (RMC) from a VGA monitor connected to the VGA port. After entering the rmc command, type the default escape sequence to connect to the RMC. The default escape sequence is: ^[^[rmc This sequence is equivalent to Ctrl/left bracket, Ctrl/left bracket, rmc. On some keyboards, the escape key functions like the Ctrl/left bracket combination.
5.14 Setting and Viewing Environment Variables Use the set envar and show envar commands to set and view environment variables. Example 5–19 Set envar and Show envar P00>>> set bootdef_dev dkb0 P00>>> show bootdef_dev Bootdef_dev dkb0 Environment variables pass configuration information between the console and the operating system. Their settings determine how the system powers up, boots the operating system, and operates. Environment variables are set or changed with the set envar command.
set envar Description The set command sets or modifies the value of an environment variable. It can also be used to create a new environment variable if the name used is unique. Environment variables pass configuration information between the console and the operating system. Their settings determine how the system powers up, boots the operating system, and operates. Syntax set envar value envar The name of the environment variable to be modified.
envar The name of the environment variable to be displayed. The show* command displays all environment variables. Table 5–10 summarizes the SRM environment variables. These environment variables are described in the following sections. Table 5–10 Environment Variable Summary Environment Variable Function auto_action Specifies the console’s action at power-up, a failure, or a reset. bootdef_dev Specifies the default boot device string.
Table 5–10 Environment Variable Summary (Continued) Environment Variable Function ei*0_mode or ew*0_mode Specifies the connection type of the default Ethernet controller. ei*0_protocols or ew*0_protocols Specifies network protocols for booting over the Ethernet controller. kbd_hardware_ type Specifies the default console keyboard type. language Specifies the console keyboard layout. memory_test Specifies the extent to which memory will be tested.
5.14.1 auto_action The auto_action environment variable specifies the action the console takes any time the system powers up, fails, or resets. The value of auto_action takes effect only after you reset the system by pressing the Reset button or by issuing the init command. The default setting for auto_action is halt. With this setting, the system stops in the SRM console after being initialized.
Examples In the following example, the operator sets the auto_action environment variable to restart. The device specified with the bootdef_dev environment variable is dka0. When Tru64 UNIX is shut down and rebooted, the system will reboot from dka0. P00>>> show auto_action auto_action halt P00>>> set auto_action restart P00>>> init . . . P00>>> show auto_action auto_action restart P00>>> show bootdef_dev bootdef_dev dka0 P00>>> boot ... (Log into UNIX and shutdown/reboot) #shutdown -r now ...
5.14.2 bootdef_dev The bootdef_dev environment variable specifies one or more devices from which to boot the operating system. When more than one device is specified, the system searches in the order listed and boots from the first device with operating system software. Enter the show bootdef_dev command to display the current default boot device. Enter the show device command for a list of all devices in the system.
5.14.3 boot_file The boot_file environment variable specifies the default file name to be used for booting when no file name is specified by the boot command. The factory default value is null. Syntax set boot_file filename Example In this example, a boot file is specified for booting the Redhat version of Linux. P00>>> set boot_file “” P00>>> boot NOTE: This command clears the boot file setting and sets the string to empty.
5.14.4 boot_osflags The boot_osflags environment variable sets the default boot flags and, for OpenVMS, a root number. Boot flags contain information used by the operating system to determine some aspects of a system bootstrap. Under normal circumstances, you can use the default boot flag settings. To change the boot flags for the current boot only, use the flags_value argument with the boot command. Syntax set boot_osflags flags_value The flags_value argument is specific to the operating system.
Linux Systems If aboot.conf contains (0: 1/vmlinux.gz ro root=/dev/sda2), the system can be booted by one of the following methods: 1. set boot_file set boot_osflags 0 boot dka0 ---or--2. boot dka0 -file "" -flags 0 ---or--3. set boot_file 1/vmlinuz.gz set boot_osflags "ro root=/dev/sda2" boot dka0 Single-user mode is typically used for troubleshooting. To make system changes at this run level, you must have read/write privileges.
OpenVMS Systems OpenVMS systems require an ordered pair as the flags_value argument: root_number and boot_flags. root_number Directory number of the system disk on which OpenVMS files are located. For example: boot_flags root_number Root Directory 0 (default) [SYS0.SYSEXE] 1 [SYS1.SYSEXE] 2 [SYS2.SYSEXE] 3 [SYS3.SYSEXE] The hexadecimal value of the bit number or numbers set. To specify multiple boot flags, add the flag values (logical OR).
Examples In the following OpenVMS example, root_number is set to 2 and boot_flags is set to 1. With this setting, the system will boot from root directory SYS2.SYSEXE to the SYSBOOT prompt when you enter the boot command. P00>>> set boot_osflags 2,1 In the following OpenVMS example, root_number is set to 0 and boot_flags is set to 80. With this setting, you are prompted for the name of the secondary bootstrap file when you enter the boot command.
5.14.5 com*_baud The default baud rate for the system is 9600. The com*_baud commands set the baud rate for COM1 and COM2. com1_baud The com1_baud environment variable sets the baud rate for the internal COM1 serial interface. com2_baud The com2_baud environment variable sets the baud rate to match that of the device connected to the COM2 port. Syntax set com*_baud baud_value baud_value The new baud rate. A list of possible values is displayed by entering the command without a value.
5.14.6 com*_flow The com1_flow and com2_flow environment variables set the flow control on the COM1 and COM2 serial ports, respectively. Syntax set com*_flow flow_value flow_value Defined values are: none—No data flows in or out of the serial ports. Use this setting for devices that do not recognize XON/XOFF or that would be confused by these signals. software—Use XON/XOFF(default). This is the setting for a standard serial terminal. hardware—Use modem signals CTS/RTS.
5.14.7 com1_mode The set com1_mode command specifies the COM1 data flow paths, so that data either flows through the RMC or bypasses it. You can also set com1_mode from the RMC. By default all data passes through the RMC. Data and control signals flow from the system COM1 port, through the RMC, and to the active external port, either the COM1 serial port (MMJ) or the 9-pin modem port. If a modem is connected, the data goes to the modem. This mode is called through mode.
Syntax set com1_mode value value Defined values are: through All data passes through RMC and is filtered for the RMC escape sequence. This is the default. snoop Data partially bypasses RMC, but RMC taps into the data lines and listens passively for the RMC escape sequence. soft_bypass Data bypasses RMC, but RMC switches automatically into snoop mode if loss of carrier occurs. firm_bypass Data bypasses RMC. RMC remote management features are disabled.
5.14.8 com*_modem The com1_modem and com2_modem environment variables are used to tell the operating system whether a modem is present on the COM1 or COM2 ports, respectively. From the settings of these variables, the operating system determines whether the port should assert a signal DTR. Syntax set com*_modem modem_value modem_value Defined values are: on—Modem is present. off—Modem is not present (default value). If you attach a modem to the COM1 or COM2 port, set the modem_value to on.
5.14.9 console The console terminal can be either a VGA monitor or a serial terminal. The console environment variable specifies which type of console is used. Syntax set console output_device The options for output_device are: graphics (default) The console terminal is a VGA monitor or a device connected to the VGA port. serial The console terminal is the device connected to the COM1 port.
5.14.10 cpu_enabled The cpu_enabled environment variable sets a bit mask that enables or disables specific CPUs on a multiprocessor system. Disabling a CPU may be necessary if a number of errors are reported on a specific CPU. These errors might be displayed during power-up or might be displayed with the show fru or show config command. Disabled CPUs are prevented from running the console or the operating system. Bit 0 of the mask corresponds to CPU 0, bit 1 to CPU 1, and so on.
Syntax set cpu_enabled hex_digit The hex_digit values are shown in the table.
5.14.11 ei*0_inet_init or ew*0_inet_init The ei*0_inet_init or ew*0_inet_init environment variable determines whether the interface's internal Internet database is initialized from nvram or from a network server (through the bootp protocol). Legal values are nvram and bootp. The default value is bootp. Set this environment variable if you are booting Tru64 UNIX from a RIS server. To list the network devices on your system, enter the show device command.
5.14.12 ei*0_mode or ew*0_mode The ei*0_mode or ew*0_mode environment variable sets an Ethernet controller to run an AUI, ThinWire, or twisted-pair Ethernet network. For the fast setting, the device defaults to fast. To list the network devices on your system, enter the show device command. The Ethernet controllers start with the letters “ei” or “ew,” for example, ewa0. The third letter is the adapter ID for the specific Ethernet controller.
5.14.13 ei*0_protocols or ew*0_protocols The ei*0_protocols or ew*0_protocols environment variable sets network protocols for booting and other functions. To list the network devices on your system, enter the show device command. The Ethernet controllers start with the letters “ei” or “ew,” for example, eia0. The third letter is the adapter ID for the specific Ethernet controller. Replace the asterisk (*) with the adapter ID letter when entering the command.
5.14.14 kbd_hardware_type The kbd_hardware_type environment variable sets the keyboard hardware type as either PCXAL or LK411 and enables the system to interpret the terminal keyboard layout correctly. Syntax set kbd_hardware_type keyboard_type The options for keyboard_type are: pcxal (default) Selects the 102-type keyboard layout. lk411 Selects the LK411 keyboard layout.
5.14.15 language The language environment variable specifies the keyboard layout, which depends on the language. The setting of the language environment variable must match the language of the keyboard variant. The factory keyboard setting is 36 English (American). The value of language takes effect only after you reset the system by pressing the Reset button or issuing the init command.
5.14.16 memory_test The memory_test environment variable determines the extent of memory testing on the next reset. You can set this variable for systems running Tru64 UNIX. Syntax set memory_test value The options for value are: full (default) Specifies that the full memory test will be run. Systems using the OpenVMS operating system must run the full memory test. partial Specifies that the first 256 MB of memory will be tested. none Specifies that memory will not be tested.
5.14.17 ocp_text The ocp_text environment variable specifies a message to be displayed on the control panel display after self-tests and diagnostics have been completed. It is useful to set this environment variable if you have a number of systems and you want to identify each system by a node name. Syntax set ocp_text message The message is the message you want to be displayed, typically the network node name you have defined for the system.
5.14.18 os_type The os_type environment variable specifies the default operating system. This variable is set at the factory to the setting for the operating system you purchased. Use this command to change the factory default setting. The value of os_type takes effect only after you reset the system by pressing the Reset button or by issuing the init command. Syntax set os_type os_type The options for os_type are: unix Sets the default to Tru64 UNIX. The SRM firmware is started during power-up or reset.
5.14.19 pci_parity The pci_parity environment variable disables or enables parity checking on the PCI bus. Some PCI devices do not implement PCI parity checking, and some have a parity-generating scheme in which the parity is sometimes incorrect or is not fully compliant with the PCI specification. A side effect of this behavior is that superfluous PCI parity errors are reported by the host PCI bridge. In such cases, the device can be used as long as parity is not checked.
5.14.20 pk*0_fast The pk*0_fast environment variable enables fast SCSI to perform in either standard or fast mode. If the system has at least one fast SCSI device, set the default controller speed to fast SCSI (1). Devices on a controller that connects to both standard and fast SCSI devices will perform at the appropriate rate for the device. If the system has no fast SCSI devices, set the default controller speed to standard SCSI (0).
5.14.21 pk*0_host_id The pk*0_host_id environment variable sets the controller host bus node ID to a value between 0 and 15. Each SCSI bus in the system requires a controller. Buses can support up to sixteen devices; however, the eighth device must be a controller. Each device on the bus, including the controller, must have a unique ID, which is a number between 0 and 15. This is the bus node ID number. On each bus, the default bus node ID for the controller is set to 7.
5.14.22 pk*0_soft_term The pk*0_soft_term environment variable enables or disables SCSI terminators for optional SCSI controllers. This environment variable applies to systems that use the QLogic SCSI controller, though it does not affect the onboard controller. The QLogic ISP1020 SCSI controller implements the 16-bit wide SCSI bus. The QLogic module has two terminators, one for the low eight bits and one for the high eight bits. To list the controllers on your system, enter the show device command.
Examples In this example, both terminators are disabled. P00>>> set pkb0_soft_term off P00>>> init . . . P00>>> show pkb0_soft_term pkb0_soft_term off In this example, the terminator for the high 8 bits is enabled. P00>>> set pkb0_soft_term high P00>>> init . . .
5.14.23 tt_allow_login The tt_allow_login environment variable enables or disables login to the SRM console firmware on alternative console ports. “Login” refers to pressing the Return or Enter key to activate the console device. If the console environment variable is set to serial, the primary console device is the terminal connected through the COM1 port. The set tt_allow_login 1 command lets you activate a console device through COM2 or a VGA monitor.
Chapter 6 Remote Management You can manage the system through the remote management console (RMC). The RMC is implemented through an independent microprocessor that resides on the system board. The RMC also provides configuration and error log functionality. This chapter explains the operation and use of the RMC.
6.1 RMC Overview The remote management console provides a mechanism for monitoring the system (voltages, temperatures, and fans) and manipulating it on a low level (reset, power on/off, halt). The RMC performs monitoring and control functions to ensure the successful operation of the system.
The RMC logic is implemented using an 8-bit microprocessor, PIC17C44, as the primary control device. The firmware code resides on the microprocessor and in flash memory. If the RMC firmware should ever become corrupted or obsolete, you can update it manually using a Loadable Firmware Update Utility. See Chapter 2 for details. The microprocessor can also communicate with the system power control logic to turn on or turn off power to the rest of the system. The RMC is powered by an auxiliary 5V supply.
6.2 Operating Modes The RMC can be configured to manage different data flow paths defined by the com1_mode environment variable. In Through mode (the default), all data and control signals flow from the system COM1 port through the RMC to the active external port. You can also set bypass modes so that the signals partially or completely bypass the RMC. The com1_mode environment variable can be set from either SRM or the RMC. See Section 6.8.
Through Mode Through mode is the default operating mode. The RMC routes every character of data between the internal system COM1 port and the active external port, either the local COM1 serial port (MMJ) or the 9-pin modem port. If a modem is connected, the data goes to the modem. The RMC filters the data for a specific escape sequence. If it detects the escape sequence, it enters the RMC CLI. Figure 6–1 illustrates the data flow in Through mode.
6.2.1 Bypass Modes For modem connection, you can set the operating mode so that data and control signals partially or completely bypass the RMC. The bypass modes are Snoop, Soft Bypass, and Firm Bypass.
Figure 6–2 shows the data flow in the bypass modes. Note that the internal system COM1 port is connected directly to the modem port. NOTE: You can connect a serial terminal to the modem port in any of the bypass modes. The local terminal is still connected to the RMC and can still enter the RMC to switch the COM1 mode if necessary. Snoop Mode In Snoop mode data partially bypasses the RMC.
After downloading binary files, you can set the com1_mode environment variable from the SRM console to switch back to Snoop mode or other modes for accessing the RMC, or you can hang up the current modem session and reconnect it. Firm Bypass Mode In Firm Bypass mode all data and control signals are routed directly between the system COM1 port and the external modem port. The RMC does not configure or monitor the modem.
6.3 Terminal Setup You can use the RMC from a modem hookup or the serial terminal connected to the system. As shown in Figure 6–3, a modem is connected to and a terminal is connected to the the dedicated 9-pin modem port COM1 serial port/terminal port (MMJ) .
6.4 SRM Environment Variables for COM1 Several SRM environment variables allow you to set up the COM1 serial port (MMJ) for use with the RMC. You may need to set the following environment variables from the SRM console, depending on how you decide to set up the RMC. com1_baud Sets the baud rate of the COM1 serial port and the modem port. The default is 9600. See Chapter 5. com1_flow Specifies the flow control on the serial port. The default is software. See Chapter 5.
6.5 Entering the RMC You type an escape sequence to invoke the RMC. You can enter RMC from any of the following: a modem, the local serial console terminal, the local VGA monitor, or the system. The “system” includes the operating system, SRM, or an application. • You can enter the RMC from the local terminal regardless of the current operating mode. • You can enter the RMC from the modem if the RMC is in Through mode, Snoop mode, or Local mode.
Entering from the Local VGA Monitor To enter the RMC from the local VGA monitor, the console environment variable must be set to graphics. Invoke the SRM console and enter the rmc command. P00>>> rmc You are about to connect to the Remote Management Console. Use the RMC reset command or press the front panel reset button to disconnect and to reload the SRM console. Do you really want to continue? [y/(n)] y Please enter the escape sequence to connect to the Remote Management Console.
6.6 Using the Command-Line Interface The remote management console supports setup commands and commands for managing the system. For detailed descriptions of the RMC commands, see Section 6.8. Command Conventions Observe the following conventions for entering RMC commands: • Enter enough characters to distinguish the command. NOTE: The reset and quit commands are exceptions. You must enter the entire string for these commands to work.
6.6.1 Displaying the System Status The RMC status command displays the system status and the current RMC settings. Table 6–1 explains the status fields. See Section 6.8 for information on the commands used to set the status fields. RMC> status PLATFORM STATUS On-Chip Firmware Revision: V1.0 Flash Firmware Revision: V1.
Table 6–1 Status Command Fields Field Meaning On-Chip Firmware Revision: Revision of RMC firmware on the microcontroller. Flash Firmware Revision: Revision of RMC firmware in flash ROM. Server Power: ON = System is on. OFF = System is off. System Halt: Asserted = System has been halted. Deasserted = Halt has been released. RMC Power Control: ON= System has powered on from RMC. OFF = System has powered off from RMC. Escape Sequence: Current escape sequence for access to RMC console.
6.6.2 Displaying the System Environment The RMC env command provides a snapshot of the system environment. RMC> env System Hardware Monitor Temperature (warnings at 48.00C, power-off at 53.00C) CPU0: 27.00C Zone0: 26.00C Fan RPM CPU1: 28.00C Zone1: 28.00C CPU2: 27.00C CPU3: 28.00C Zone2: 26.
CPU temperature. In this example four CPUs are present. Zone 0, 1, and 2 measure the temperature of the PCI compartment and are reported from three thermal sensors located in different areas of the PCI backplane. Fan RPM. With the exception of Fan 5, all fans are powered as long as the system is powered on. Fan 5 is Off unless Fan 6 fails. The normal power supply status is either OK (system is powered on) or OFF (system is powered off or the power supply cord is not plugged in).
6.6.3 Using Power On and Off, Reset, and Halt Functions The RMC power {on, off}, halt {in, out}, and reset commands perform the same functions as the buttons on the operator control panel. Power On and Power Off The RMC power on command powers the system on, and the power off command powers the system off. The Power button on the OCP, however, has precedence. • If the system has been powered off with the Power button, the RMC cannot power the system on.
Halt In and Halt Out The halt in command halts the system. The halt out command releases the halt. When you issue either the halt in or halt out command, the terminal exits RMC and reconnects to the server's COM1 port. RMC> halt Returning RMC> halt Returning in to COM port out to COM port The halt out command cannot release the halt if the Halt button is latched in. If you enter the halt out command, the message “Halt button is IN” is displayed, indicating that the command will have no effect.
6.6.4 Configuring Remote Dial-In Before you can dial in through the RMC modem port or enable the system to call out in response to system alerts, you must configure RMC for remote dial-in. Connect your modem to the 9-pin modem port and turn it on. Enter the RMC from either the local serial terminal or the local VGA monitor to set up the parameters.
Sets the password that is prompted for at the beginning of a modem session. The string cannot exceed 14 characters and is not case sensitive. For security, the password is not echoed on the screen. When prompted for verification, type the password again. Sets the initialization string. The string is limited to 31 characters and can be modified depending on the type of modem used.
6.6.5 Configuring Dial-Out Alert When you are not monitoring the system from a modem connection, you can use the RMC dial-out alert feature to remain informed of system status. If dial-out alert is enabled, and the RMC detects alarm conditions within the managed system, it can call a preset pager number. You must configure remote dial-in for the dial-out feature to be enabled. See Section 6.6.4. To set up the dial-out alert feature, enter the RMC from the local serial terminal or local VGA monitor.
The elements of the dial string and alert string are shown in Table 6–2. Paging services vary, so you need to become familiar with the options provided by the paging service you will be using. The RMC supports only numeric messages. Sets the string to be used by the RMC to dial out when an alert condition occurs. The dial string must include the appropriate modem commands to dial the number. Sets the alert string, typically the phone number of the modem connected to the remote system.
Table 6–2 Elements of Dial String and Alert String Dial String The dial string is case sensitive. The RMC automatically converts all alphabetic characters to uppercase. ATXDT AT = Attention. X = Forces the modem to dial “blindly” (not seek the dial tone). Enter this character if the dial-out line modifies its dial tone when used for services such as voice mail. D = Dial T = Tone (for touch-tone) 9, The number for an outside line (in this example, 9).
6.7 Resetting the RMC to Factory Defaults If the non-default RMC escape sequence has been lost or forgotten, RMC must be reset to factory settings to restore the default escape sequence. WARNING: To prevent injury, access is limited to persons who have appropriate technical training and experience. Such persons are expected to understand the hazards of working within this equipment and take measures to minimize danger to themselves or others. The following procedure restores the default settings: 1.
Figure 6–4 RMC Jumpers (Default Positions) 1 2 3 J7 J6 J5 J4 1 2 J3 J2 J1 PK0211A 7. Plug a power cord into one power supply, and then wait until the control panel displays the message “System is down.” 8. Unplug the power cord. Wait until the +5V Aux LED on the power supply goes off before proceeding. 9. Install jumper J6 over pins 2 and 3. 10. Reinstall CPU1, the card cage cover and fan cover and the enclosure panels. 11. Plug the power cord into each of the power supplies.
6.8 RMC Command Reference This section describes the RMC command set. Commands are listed in alphabetical order. clear {alert, port} dep disable {alert, remote} dump enable {alert, remote} env halt {in, out} hangup help or ? power {on, off} quit reset send alert set {alert, com1_mode, dial, escape, init, logout, password, user} status NOTE: The dep and dump commands are reserved for service providers.
clear port The clear port command clears any “stuck” conditions on the system’s COM1 port. The clear port command attempts to free the port by resetting all UARTs controlled by the RMC if the port is currently locked by an application program, without resetting the entire system. RMC> clear port RMC> NOTE: This command also causes the modem to disconnect. disable alert The disable alert command disables the RMC from paging a remote system operator.
enable alert The enable alert command enables the RMC to page a remote system operator. Before you can enter the enable alert command, you must configure remote dial-in and call-out, set an RMC password, and enable remote access to the RMC modem port. See Section 6.6.4 and Section 6.6.5.
enable remote The enable remote command enables remote access to the RMC modem port by configuring the modem with the setting stored in the initialization string. This command also allows the RMC to automatically dial the pager number set with the set dial command upon detection of alert conditions. Before you can enter the enable remote command, you must configure remote dial-in by setting an RMC password and initialization string. See Section 6.6.4.
halt in The halt in command is equivalent to pressing the Halt button on the control panel. The halt in command halts the managed system. When the halt in command is issued, the terminal exits RMC and returns to the server’s COM1 port. Toggling the Power button on the operator control panel overrides the halt in condition. RMC> halt in Returning to COM port halt out The halt out command is equivalent to releasing the Halt button on the control panel. The halt out command releases a halt.
help or ? The help or ? command displays the RMC command set. RMC> help clear {alert, port} deposit disable {alert, remote} dump enable {alert, remote} env halt {in, out} hangup help or ? power {off, on} quit reset send alert set {alert, com1_mode, dial, escape, init, logout, password, user} status power off The power off command is equivalent to turning off the system power from the operator control panel. If the system is already powered off, this command has no effect.
The power on command does not turn on the system if the Power button on the operator control panel is in the Off position. If you issue the command, the following message is displayed: RMC> power on Power button is OFF quit The quit command exits RMC and returns the terminal to the server’s COM1 port. You must enter the entire word for the command to take effect. RMC> quit Returning to COM port reset The reset command is equivalent to pushing the Reset button on the operator control panel.
set alert The set alert command sets the alert string that is transmitted through the modem when an alert condition is detected. Set the alert string to the phone number of the modem connected to the remote system. The alert string is appended after the dial string, and the combined string is sent to the modem. The example shown below is generic. Because paging services vary, be sure to listen to the options provided by the paging service to determine the appropriate delay and the menu options.
• In Snoop mode, you can type an escape sequence to enter the RMC. RMC mode provides a command-line interface for issuing commands to monitor and control the system. • In Soft Bypass mode, you cannot enter the RMC. But if an alert condition or loss of carrier occurs, the RMC switches into Snoop mode. From Snoop mode you can enter RMC. • In Firm Bypass mode you cannot enter the RMC.
set dial The set dial command sets the string to be used by the RMC to dial out when an alert condition occurs. The dial string must be in the correct format for the attached modem. If a paging service is to be contacted, the string must include the appropriate modem commands to dial the number. The dial string is case sensitive. The RMC automatically converts all alphabetic characters to uppercase. RMC> set dial Dial String: ATXDT9,15085553333 RMC> For more information, see Section 6.6.5.
set init The set init command sets the modem initialization string. The initialization string is limited to 31 characters and can be modified, depending on the type of modem used. RMC> set init Init String: AT&F0E0V0X0S0=2 RMC> Because the modem commands disallow mixed cases, the RMC automatically converts all alphabetic characters entered in the init string to uppercase. The RMC automatically configures the modem's flow control according to the setting of the SRM com1_flow environment variable.
set password The set password command allows you to set or change the password that is prompted for at the beginning of a modem session. A password must be set to enable access through a modem. The string cannot exceed 14 characters. For security, the password is not echoed on the screen. When prompted for verification, type the password again. If you mistype, reenter the set password command.
6.9 Troubleshooting Tips Table 6–3 lists possible causes and suggested solutions for symptoms you might see. Table 6–3 RMC Troubleshooting Symptom Possible Cause Suggested Solution You cannot enter the RMC from the modem. The RMC may be in soft bypass or firm bypass mode. Issue the show com1_mode command from SRM and change the setting if necessary. If in soft bypass mode, you can disconnect the modem session and reconnect it. The terminal cannot communicate with the RMC correctly.
Table 6–3 RMC Troubleshooting (Continued) Symptom Possible Cause Suggested Solution RMC will not answer when modem is called. (continued from previous page) On AC power-up, RMC defers initializing the modem for 30 seconds to allow the modem to complete its internal diagnostics and initializations. Wait 30 seconds after powering up the system and RMC before attempting to dial in. After the system is powered up, the COM1 port seems to hang or you seem to be unable to execute RMC commands.
Chapter 7 Troubleshooting This chapter describes procedures for resolving problems with the system. To correct a problem, locate the troubleshooting table for that problem type and follow the guidelines provided. If you cannot correct the problem, report it to your service provider.
7.1 Power-Up Error Messages Three sets of diagnostics are performed at power-up: RMC, SROM, and SRM. As the diagnostics run, messages are displayed on the control panel. Some messages are also displayed on the console terminal. Error messages that are displayed can be used to diagnose problems. 7.1.1 Messages with Beep Codes A few error messages that appear on the operator control panel are announced by audible error beep codes, an indicated in Table 7–1.
Table 7–1 Error Beep Codes Beep Code Associated Messages 1 Jump to Console 1-3 Meaning SROM code has completed execution. System jumps to SRM console. SRM messages should start to be displayed. If no SRM messages are displayed, there is a problem. See Section 7.1.2. VGA monitor not plugged in. The first beep is a long beep. 1-1-4 ROM err The ROM err message is displayed briefly, then a single beep is emitted, and Jump to Console is displayed.
7.1.2 Checksum Error If no messages are displayed on the operator control panel after the Jump to Console message, the console firmware is corrupted. When the system detects the error, it attempts to load a utility called the failsafe loader (FSL) so that you can load new console firmware images. A sequence similar to the one in Example 7–1 occurs. Example 7–1 Checksum Error and Fail-Safe Loader Loading console Console ROM checksum error Expect: 00000000.000000FE Actual: 00000000.
The system detects the checksum error and writes a message to the console screen. The system attempts to automatically load the FSL program from the floppy drive. As the FSL program is initialized, messages similar to the console power-up messages are displayed. This example shows the beginning and ending messages.
7.1.3 No MEM Error If the SROM code cannot find any available memory, a 1-3-3 beep code is issued (one beep, a pause, a burst of three beeps, a pause, and another burst of three beeps), and the message “No MEM” is displayed. The system does not come up to the console program. This error indicates missing or bad DIMMs.
7.2 RMC Error Messages Table 7–2 lists the error messages that might be displayed on the operator control panel by the remote management console during power-up. Most fatal error messages prevent the system from completing its power-up. Contact your service provider if a fatal error is displayed. Warning messages require prompt attention but may not prevent the system from completing its power-up. The VTERM and CTERM regulators referenced in the table are located on the system motherboard.
NOTE: The CPUn failed message does not necessarily prevent the completion of power-up. If the system finds a good CPU, it continues the power-up process. Table 7–2 RMC Error Messages (Continued) Message Meaning PSn failed Power supply failed. “n” is 0, 1, or 2. OverTemp Warning System temperature is near the high threshold. Fann failed Fan failed. “n” is 0 through 6. PCI door opened Cover to PCI card cage is off. Reinstall cover. Fan door opened Cover to main fan area (fans 5 and 6) is off.
7.3 SROM Error Messages The SROM power-up identifies errors that may or may not prevent the system from coming up to the console. It is possible that these errors may prevent the system from successfully booting the operating system. Errors encountered during SROM power-up are displayed on the operator control panel (OCP). Some errors are also displayed on the console terminal if the console output is set to serial. Table 7–3 lists the SROM error messages. Contact your service provider.
Table 7–3 SROM Error Messages (Continued) Code SROM Message OCP Message E2 Memory address line error Mem Err E1 E0 Memory pattern error Memory pattern ECC error Mem Err Mem Err 7F Configuration error on CPU #3 CfgERR 3 7E 7D Configuration error on CPU #2 Configuration error on CPU #1 CfgERR 2 CfgERR 1 7C 7B 7A Configuration error on CPU #0 Bcache failed on CPU #3 error Bcache failed on CPU #2 error CfgERR 0 BC Bad 3 BC Bad 2 79 78 77 Bcache failed on CPU #1 error Bcache failed on CPU #0 e
7.4 SRM Diagnostics The SRM console event log and SRM console commands help you troubleshoot problems that do not prevent the system from coming up to the console. 7.4.1 Console Event Log A console event log consists of status messages received during powerup self-tests. If problems occur during power-up, error messages indicated by asterisks (***) may be embedded in the console event log. To display a console event log one screen at a time, use the more el command.
7.4.2 Show Device Command Use the SRM show device command to list the controllers and bootable devices in the system. If storage devices are missing from the display, see Table 7–7. Example 7–4 Show Device Command P00>>> show device dka0.0.0.1.1 dka100.1.0.1.1 dka200.2.0.1.1 dkb0.0.0.3.1 dqa0.0.0.15.0 dva0.0.0.1000.0 ewa0.0.0.4.1 ewb0.0.0.2002.1 pka0.7.0.1.1 pkb0.7.0.3.1 pkc0.7.0.2000.1 pkd0.7.0.2001.1 7.4.
The test command also does a quick test on the system speaker. A beep is emitted as the command starts to run. The tests are run sequentially, and the status of each subsystem test is displayed to the console terminal as the tests progress. If a particular device is not available to test, a message is displayed. The test script does no destructive testing; that is, it does not write to disk drives. The syntax is: test [argument] Use the -lb (loopback) argument for console loopback tests.
7.4.4 Show FRU Command The show fru command displays a table showing the physical configuration of the field-replaceable units (FRUs) in the system. Use the show fru command with the show error command (Section 0) to determine if any FRUs have errors logged. P00>>> show fru FRUname SMB0 SMB0.CPU0 SMB0.CPU1 SMB0.CPU2 SMB0.CPU3 SMB0.MMB0 SMB0.MMB0.J4 SMB0.MMB0.J8 SMB0.MMB0.J5 SMB0.MMB0.J9 SMB0.MMB0.J2 SMB0.MMB0.J6 SMB0.MMB0.J3 SMB0.MMB0.J7 SMB0.MMB1 SMB0.MMB1.J4 SMB0.MMB1.J8 SMB0.MMB1.J5 SMB0.MMB1.
SMB0.CPB0.PCI3 SMB0.CPB0.PCI5 SMB0.CPB0.PCI7 SMB0.CPB0.PCI8 SMB0.CPB0.PCI9 OCP0 PWR0 PWR1 PWR2 FAN1 FAN2 FAN3 FAN4 FAN5 FAN6 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 70-33894-0x 30-49448-01. C05 30-49448-01. C05 30-49448-01.
Table 7–4 Bit Assignments for Error Field Bit Meaning Bit 0 is 1 Failure Bit 1 is 1 TDD error has been logged Bit 2 is 1 At least one SDD error has been logged Bit 3 is 1 FRU EEPROM is unreadable Bit 4 is 1 Checksum failure on bytes 0-62 Bit 5 is 1 Checksum failure on bytes 64-126 Bit 6 is 1 Checksum failure on bytes 128-254 Bit 7 is 1 FRU’s system serial does not match system’s NOTE: Contact your service provider if the E (error) field shows any of these errors. 7.4.
7.4.6 Show Power Command Use the SRM show power command to determine whether the failure of a system running Tru64 UNIX or OpenVMS was related to a fan, temperature, or power supply problem. You can use this command if you are able to restart the system. Otherwise, invoke RMC and use the env command.
7.4.7 Crash Command For fatal errors, the operating systems will save the contents of memory to a crash dump file. Crash dump files can be used to determine why the system crashed. Example 7–9 Crash Command P00>>> crash CPU 0 restarting DUMP: 19837638 blocks available for dumping. DUMP: 118178 wanted for a partial compressed dump. DUMP: Allowing 2060017 of the 2064113 available on 0x800001 device string for dump = SCSI 1 1 0 0 0 0 0. DUMP.
7.5 Troubleshooting Tables This section describes some strategies for troubleshooting problems that might prevent the system from completing its power-up or that might prevent you from booting the operating system. Use the troubleshooting tables on the following pages to diagnose the following types of problems.
Table 7–5 Power Problems Symptom Action System does not power on. Check that AC power is available and all power cords are plugged in. Check the Power setting on the control panel. Toggle the Power button to off, then back on to clear a remote power disable. Check error messages on the control panel. Check that the ambient room temperature is within environmental specifications (10–35°C, 50–95°F). Internal power supply cables might not be plugged in at the system board. Contact your service provider.
Table 7–6 Problems Getting to Console Mode Symptom Action Power-up screen is not displayed. Interpret the error beep codes and observe the control panel display at power-up for a failure detected during self-tests. Check keyboard and monitor connections. Press the Return key. If the system enters console mode, check that the console environment variable is set correctly. If you are using a VGA monitor as the console terminal, the console variable should be set to graphics.
Table 7–7 Problems Reported by the Console Symptom Action Power-up tests are not completed. Interpret the error beep codes at power-up and check the power-up screen for a failure detected during self-tests. The system attempts to boot from the floppy drive after a checksum error is reported (error beep code 1-1-4). The system automatically reverts to the failsafe loader to load new SRM firmware. See Section 7.1.2.
Table 7–8 Boot Problems Symptom Action System cannot find boot device. Check the system configuration for the correct device parameters (node ID, device name, and so on). Use the show config and show device commands. Check the system configuration for the correct environment variable settings. Examine the auto_action, bootdef_dev, boot_osflags, and os_type environment variables. For network boots, make sure ei*0_protocols or ew*0_protocols is set to bootp for Tru64 UNIX or mop for OpenVMS.
Table 7–9 Errors Reported by the Operating System Symptom Action System has crashed, but SRM console is operating. Press the Halt button and enter the SRM crash command to provide a crash dump file for analysis. If the problem is intermittent, run the SRM test command. Refer to the OpenVMS Alpha System Dump Analyzer Utility Manual for information on how to interpret OpenVMS crash dump files. Refer to the Guide to Kernel Debugging for information on using the Tru64 UNIX Krash Utility.
7.6 Option Card Problems Option card problems can include problems related to network options and PCI options. Network Problems Network problems can vary, depending on the type of network option card that you have installed. See the option card documentation for information on troubleshooting network problems. Make sure you have correctly set the network type for the network interface card.
PCI Bus Problems PCI bus problems at startup are usually indicated by the inability of the system to detect the PCI device. Use Table 7–10 to diagnose the likely cause of the problem. Table 7–10 Troubleshooting PCI Bus Problems Step Action 1 Check the cabling and confirm that the PCI card is correctly seated. 2 Run system console PCI diagnostics for devices on the Supported Options List. (If the device is not on the list, refer to the device's documentation.
Chapter 8 Specifications This chapter gives specifications for ES45 systems: • Physical Specifications • Environmental Specifications • Electrical Specifications • Regulatory Approvals • Acoustic Data Specifications 8-1
8.1 Physical Specifications Table 8–1 Physical Characteristics — Tower Dimensions Height Width Depth Weight 50.8 cm (20.0 in.) 38.7 cm (15.25 in.) 80.5 cm (31.7 in.) Nominal: 65 kg (143 lb) Max: 96 kg (211 lb) Shipping Container Height Width Depth Weight 82.4 cm (32.2 in.) 60.2 cm (24.0 in.) 101.6 cm (40.0 in.) Nominal: 78 kg (172 lb) Max: 110 kg (242 lb) Clearances Front Rear Left side Right side 8-2 ES45 Owner’s Guide Operating Service 75 cm (29.5 in.) 15 cm (6 in.) None None 75 cm (29.5 in.
Table 8–2 Physical Characteristics — Pedestal Dimensions Height Width Depth Weight 78.2 cm (30.8 in.) 50.8 cm (20.0 in.) 82.3 cm (32.4 in.) Nominal: 127 kg (280 lb) Max: 159 kg (350 lb) Shipping Container Height Width Depth Weight 107.7 cm (42.4 in.) 100.3 cm (39.5 in.) 60.7 cm (23.9 in.) Nominal: 149 kg (328 lb) Max: 185 kg (407 lb) Clearances Front Rear Left side Right side Operating Service 75 cm (29.5 in.) 15 cm (6 in.) None None 75 cm (29.5 in.) 75 cm (29.5 in.) None 75 cm (29.5 in.
Table 8–3 Physical Characteristics — Rackmount Dimensions Height 35.2 cm (13.87 in.) Width 44.7 cm (17.6 in.) Depth Weight 1. When lifting 2. Total added to cabinet (includes brackets, slides, and cables) 78.2 cm (30.8 in.) Nominal: 50 kg (110 lb) Nominal: 59 kg (130 lb) Fits 14 in. [8U] standard RETMA cabinets Max: 76 kg (167.2 lb) Max: 92 kg (202.4 lb) Shipping Container Height Width Depth Weight 73.2 cm (28.8 in.) 60.7 cm (24.0 in.) 101.6 cm (40.0 in.
Table 8–4 Physical Characteristics — Cabinets Dimensions H9A10 M-Series Height Width Depth Weight 170 cm (67.0 in.) 60 cm (23.6 in.) 110 cm (43.27 in.) Configuration-dependent Max payload 1000 lb H9A15 M-Series Height Width Depth Weight 200 cm (79.0 in.) 60 cm (23.6 in.) 110 cm (43.27 in.) Configuration-dependent Max payload 1000 lb Shipping Container H9A10 M-Series Height Width Depth Weight 185.5 cm (73 in.) 91.5 cm (36 in.) 122 cm (48 in.
8.
8.3 Electrical Specifications Table 8–6 Electrical Characteristics — All System Variants Nominal voltage (Vac) Voltage range (Vac) (temporary condition) Power source phase Nominal frequency (Hz) Frequency range (Hz) RMS current (max. steady state) Tower and Rackmount Single power cord Multiple power cords Max VA Pedestal Each power cord Max VA M-Series cab config.-dependent Each power cord 200–240 180–250 Single 50/60 47–53/57–63 5.6 A 3.6 A 1440 VA 6.
Table 8–6 Electrical Characteristics — All System Variants (Cont.) Power Cord System Variant Quantity Tower up to 3 190 cm (75 in.) IEC 320 C13 to NEMA 6–15, 200–240 V (N. America) or 200–240 V IEC 320 C13 to country-specific 2 275 cm (108 in.) IEC 320 C13 to NEMA 6-15 200–240 V (N. America) or IEC 320 C13 to country-specific 3 452 cm (14 ft 10 in.
8.4 Regulatory Approvals Table 8–7 Regulatory Approvals Agency approvals Reviewed to UL: Listed to UL1950 3rd edition UL CNL: Certified to CAN/CSA-C22.2 No. 950-1995 TUV: EN60950/A11:1997, GS marked FCC: Part 15.B Class A IC ICES-003 Class A CE: EN55022:1998, EN55024:1998, EN61000-3-2:1995, EN61000-3-3:1995 VCCI: V-3/97.
8.5 Acoustic Data Table 8–8 gives the noise declaration for ES45 systems. Table 8–8 Acoustic Data Acoustics — Declared Values per ISO 9296 and ISO 7779 LWAd, B LpAm, dBA (bystander positions) Product Idle Operate Idle Operate Rackmount or Tower 6.4 6.4 47 47 Pedestal 6.6 6.6 48 48 StorageWorks Model 43xx 6.3 6.4 44 45 Current values for specific configurations are available from Compaq representatives. 1 B = 10 dBA.
Index A Acoustics, 8-10 Allocation memory, 4-12 APB program, 3-25 auto_action environment variable, 3-3, 5-3, 5-44 auto_action environment variable, SRM, 5-35 Autoboot, 5-44 Auxiliary power supply, RMC, 6-3 B Baud rate, setting, 5-52 boot command (SRM), 5-25 Boot devices, specifying, 5-46 Boot file, specifying, 5-47 Boot flags OpenVMS, 3-8, 5-50 UNIX, 3-6, 5-48 Boot options, 3-2 Boot problems, 7-23 Boot procedure OpenVMS, 3-23 UNIX, 3-14 Linux, 3-19 boot_file environment variable, 3-5, 5-47 boot_osflags
Connectors, rear, 1-8 Console commands list (SRM), 5-4 Console device, activating, 5-73 console environment variable, 5-57 console environment variable (SRM), 2-3 Console event log, 7-11 Console mode, 5-2 Console password, 2-27 clearing, 2-32 Console program, 2-10, 5-2 Console terminal, 1-26 Console tests, 5-28, 7-13 Console, specifying, 5-57 Control panel, 1-10 Control panel messages, 2-3, 5-66 Controllers, SCSI, 5-70 Controls halt button, 1-11 power button, 1-10 reset button, 1-11 Covers removing from ped
F Factory-installed software (FIS), 3-1 Fail-safe loader, 7-4 Fan failure, 7-20 Fans, status of, 5-23 Fast SCSI, 5-69 File, displaying, 5-32 Firm bypass mode, 6-8 Firmware updating, 2-33 updating from OpenVMS system disk, 238 updating using BOOTP, 2-39 updating using MOP, 2-39 Firmware update utility, 2-34 Firmware updates manual, 2-36 sources of, 2-33 Flash ROM, updating, 2-36 Flash SROM, 2-5 FRUs, displaying, 5-18, 7-14, 7-16 FRUs, displaying errors, 5-21 H Halt button, 1-11 Halt button, with login comma
Memory, displaying, 5-22 memory_test environment variable, 5-65 Messages, power-up, 2-3 MMBs, 1-13 Model 1B backplane slot information, 4-32 overview, 1-14 rules and requirements, 4-32 Model 2B backplane slot information, 4-33 overview, 1-16 rules and requirements, 4-33 Model 3B backplane slot information, 4-34 overview, 1-18 rules and requirements, 4-34 Modules, system motherboard, 1-12 MOP protocol, 3-11, 5-62 MOP V3 software, 5-37 more command (SRM), 5-32 more el command (SRM), 7-11 Motherboard, 1-12 N
SRM, 5-65 Power-up procedure, 2-5 Power-up script, creating, 5-36 Problems getting to console mode, 7-21 Problems reported by console, 7-22 Processor card, 1-13 Processor, enabling, 5-58 Program, resuming, 5-31 Q QLogic controller, 5-71 quit command (RMC), 6-11, 6-33 R Reading a file, 5-32 Redundant power supply, 4-16 Regulatory approvals, 8-9 Remote power-on/off, 6-18 Removable media, 1-22 Removable media device, installing, 4-44 Removing enclosure panels, 4-3 from a pedestal, 4-6 from a tower, 4-4 Reset
S SCSI bus length, 4-53 SCSI controller IDs, 5-70 SCSI devices, speed of, 5-69 SCSI expansion, 4-53 SCSI terminators, enabling, 5-71 Secure function commands, 2-26 Secure mode, setting SRM to, 2-29 Security features, turning off, 2-30 send alert command (RMC), 6-33 Serial ports determining presence of modem on, 5-56 flow control, 5-53 set alert command (RMC), 6-34 set com1_mode command (RMC), 6-34 set command (SRM), 5-40, 5-41 set dial command (RMC), 6-36 set escape command (RMC), 6-36 set init command (RMC
SROM error messages, 7-10 power-up display, 2-4, 2-5 power-up messages, 2-3 status command (RMC), 6-14, 6-38 Storage hard drive, 1-23 removable media, 1-22 Storage subsystem, 1-23 System chassis components, 1-4 front view, 1-5 rear view, 1-7 System diagnostics, 7-2 System enclosures, 1-3 System motherboard block diagram, 1-12 U UART ports, 6-5 UNIX booting, 3-13 booting from SCSI disk, 3-13 booting over the network, 3-15 installing, 3-17 text-based installation display, 3-17 Updating firmware, 2-33 V VGA
