Compaq AlphaServer ES45 1B Owner's Manual
  1. Manuals
  2. Brands
  3. Compaq Manuals
  4. Server
  5. AlphaServer ES45 1B
  6. Owner's manual

Compaq AlphaServer ES45 1B Owner's Manual

Hide thumbs
Table of Contents

Advertisement

Quick Links

Download this manual
AlphaServer ES45
Owner's Guide
Order Number: EK-ES450-UG. B01
This manual is for managers and operators of ES45 systems.
Compaq Computer Corporation

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the AlphaServer ES45 1B and is the answer not in the manual?

Questions and answers

Related Manuals for Compaq AlphaServer ES45 1B

Summary of Contents for Compaq AlphaServer ES45 1B

  • Page 1 AlphaServer ES45 Owner's Guide Order Number: EK-ES450-UG. B01 This manual is for managers and operators of ES45 systems. Compaq Computer Corporation...
  • Page 2 Open Group in the United States and other countries. All other product names mentioned herein may be trademarks of their respective companies. Compaq shall not be liable for technical or editorial errors or omissions contained herein. The information in this document is provided “as is” without warranty of any kind and is subject to change without notice.
  • Page 3 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.

  • Page 5: Table Of Contents

    Contents Preface ........................xv Chapter 1 System Overview Model Differences.................. 1-2 System Enclosures................. 1-3 System Chassis—Front View/Top View..........1-5 System Chassis—Rear View ..............1-7 Rear Ports and Slots ................1-8 Operator Control Panel............... 1-10 System Motherboard................1-12 I/O Backplane..................1-14 1.7.1 Model 1B .....................
  • Page 6 2.4.2 Displaying the Logical Hardware Configuration........ 2-16 2.4.3 Displaying the Bootable Devices............2-22 2.4.4 Viewing the Memory Configuration............ 2-24 Setting SRM Environment Variables ..........2-25 Setting Console Security ..............2-26 2.6.1 Setting the Console Password............. 2-27 2.6.2 Setting the Console to Secure Mode............ 2-29 2.6.3 Turning Off Security During a Console Session .........
  • Page 7 Installing CPUs................... 4-21 Memory Configuration ................ 4-23 4.10 Installing DIMMs................4-28 4.11 PCI Configuration ................4-31 4.11.1 Model 1B PCI Backplane ..............4-32 4.11.2 Model 2B PCI Backplane ..............4-33 4.11.3 Model 3B PCI Backplane ..............4-34 4.12 Installing PCI Cards ................4-35 4.13 Installing Universal Hard Disk Drives..........
  • Page 8 5.14.3 boot_file..................5-46 5.14.4 boot_osflags................... 5-47 5.14.5 com*_baud ..................5-51 5.14.6 com*_flow..................5-52 5.14.7 com1_mode..................5-53 5.14.8 com*_modem................. 5-55 5.14.9 console................... 5-56 5.14.10 cpu_enabled .................. 5-57 5.14.11 ei*0_inet_init or ew*0_inet_init............ 5-59 5.14.12 ei*0_mode or ew*0_mode.............. 5-60 5.14.13 ei*0_protocols or ew*0_protocols........... 5-61 5.14.14 kbd_hardware_type ..............
  • Page 9 Chapter 7 Troubleshooting Power-Up Error Messages ..............7-2 7.1.1 Messages with Beep Codes ..............7-2 7.1.2 Checksum Error ..................7-4 7.1.3 No MEM Error ..................7-6 RMC Error Messages ................7-7 SROM Error Messages................7-9 SRM Diagnostics................. 7-11 7.4.1 Console Event Log................7-11 7.4.2 Show Device Command...............
  • Page 10 2–9 Set Password..................2-27 2–10 Set Secure ................... 2-29 2–11 Login ....................2-30 2–12 Clear Password ................... 2-32 2–13 Update Utility Display................ 2-34 3–1 Booting Tru64 UNIX from a Local SCSI Disk ........3-13 3–2 RIS Boot ....................3-15 3–3 Text-Based Installation Display ............
  • Page 11 7–8 Show Power Command ............... 7-17 7–9 Crash Command ................. 7-18 Figures 1–1 ES45 Systems..................1-3 1–2 Top/Front Components (Pedestal) ............1-5 1–3 Rear Components (Pedestal)..............1-7 1–4 Rear Connectors..................1-8 1–5 Operator Control Panel............... 1-10 1–6 System Motherboard Block Diagram..........1-12 1–7 Location of I/O Slots: Model 1B............
  • Page 12 4–21 Installing a 5.25-Inch Device (Pedestal/Rack View) ......4-44 4–22 Disk Cage Installation ................ 4-47 4–23 Disk Cage Installation (Continued) ............ 4-49 4–24 Fan Locations..................4-51 4–25 Cabling a Second Disk Cage ............... 4-52 6–1 Data Flow in Through Mode ..............6-4 6–2 Data Flow in Bypass Mode ..............
  • Page 13 Tables 1–1 ES45 Model Summary ................1-2 1–2 How Physical I/O Slots Map to Logical Slots: Model 1B..... 1-15 1–3 How Physical I/O Slots Map to Logical Slots: Model 2B ....1-17 1–4 How Physical I/O Slots Map to Logical Slots: Model 3B..... 1-19 2–1 Physical I/O Slots Map to Logical Slots: Model 1B ......
  • Page 14 8–6 Electrical Characteristics — All System Variants........ 8-7 8–7 Regulatory Approvals................8-9 8–8 Acoustic Data ..................8-10...

  • Page 15: Preface

    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.
  • Page 16 Service Guide HTML CD (includes IPB) AG–RPJ5A–TS Loose Piece Items EK–ES450–PD Basic Installation Card EK–ES450–RG Rackmount Installation Guide EK–ES450–TP Rackmount Installation Template Support Resources Support resources for this system are available on the Internet, including a supported options list, firmware updates, and patches. http://www.compaq.com/alphaserver/es45/es45.html...

  • Page 17: Chapter 1 System Overview

    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 •...

  • Page 18: Model Differences

    AA) Setting must be same 128K for all members of cluster. See Quickspecs Memory Channel configuration notes at: http://www.compaq.com/ alphaserver/es45/ For Models 1B, 2B, and 3B the 3X-H7514-AA power supply is required to meet additional DIMM power requirements. 1-2 ES45 Owner’s Guide...

  • Page 19: System Enclosures

    System Enclosures The ES45 family consists of a standalone tower, a pedestal with ex- panded storage capacity, and a rackmount system. Figure 1–1 ES45 Systems Cabinet Pedestal Tower PK0212B System Overview 1-3...
  • Page 20 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 •...

  • Page 21: System Chassis-Front View/Top View

    System Chassis—Front View/Top View Figure 1–2 Top/Front Components (Pedestal) PK0201B System Overview 1-5...
  • Page 22 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...

  • Page 23: System Chassis-Rear View

    System Chassis—Rear View Figure 1–3 Rear Components (Pedestal) PK0206B Power supplies PCI bulkhead I/O ports Power harness access cover Speaker System Overview 1-7...

  • Page 24: Rear Ports And Slots

    Rear Ports and Slots Figure 1–4 Rear Connectors Pedestal Tower PK0209A 1-8 ES45 Owner’s Guide...
  • Page 25 Rear Panel Connections Modem port—Dedicated 9-pin port for modem connection to remote man- agement 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 termi- nal.

  • Page 26: Operator Control Panel

    Operator Control Panel The control panel provides system controls and status indicators. The controls are the Power, Halt, and Reset buttons. A 16-character back- lit 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 PK0204 Control panel display.
  • Page 27 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.

  • Page 28: System Motherboard

    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 mother- boards (MMBs) and a connector to the I/O subsystem. Figure 1–6 shows the location of these modules on the motherboard.
  • Page 29 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 im- plementation of the Alpha architecture. The microprocessor is a superscalar CPU with out-of-order execution and specu- lative execution to maximize speed and performance.

  • Page 30: I/O Backplane

    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. Figure 1–7 Location of I/O Slots: Model 1B MR0262A 1-14 ES45 Owner’s Guide...

  • Page 31: How Physical I/O Slots Map To Logical Slots: Model 1B

    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 con- sole 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.

  • Page 32: Model 2B

    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). Figure 1–8 Location of I/O Slots: Model 2B (Pedestal/Rack View) 10-Slot PK0226D 1-16 ES45 Owner’s Guide...

  • Page 33: How Physical I/O Slots Map To Logical Slots: Model 2B

    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 con- sole 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.

  • Page 34: Model 3B

    1.8.3 Model 3B The Model 3B has ten slots with eight at 33 MHz and two at 66 MHz. Figure 1–9 Location of I/O Slots: Model 3B 10-Slot MR0263 1-18 ES45 Owner’s Guide...

  • Page 35: How Physical I/O Slots Map To Logical Slots: Model 3B

    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 con- sole 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.

  • Page 36: Power Supplies

    Power Supplies The power supplies provide power to components in the system chas- sis. The number of power supplies required depends on the system configuration. Figure 1–10 Power Supplies Tower Pedestal/Rack 1 1 1 2 2 2 PK0207A 1-20 ES45 Owner’s Guide...
  • Page 37 One to three power supplies provide power to components in the system chassis. The system supports redundant power configurations to ensure continued sys- tem operation if a power supply fails (The Model 2 has a minimum configura- tion 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.

  • Page 38: Removable Media Storage

    1.10 Removable Media Storage The system chassis houses a CD-ROM drive and a high-density 3.5- inch 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. Figure 1–11 Removable Media Drive Area PK0233 1-22 ES45 Owner’s Guide...

  • Page 39: Storage Subsystem

    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.

  • Page 40: System Access

    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. Figure 1–13 System Keys Tower Pedestal PK0224A 1-24 ES45 Owner’s Guide...
  • Page 41 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.

  • Page 42: Console Terminal

    1.13 Console Terminal The console terminal can be a serial (character cell) terminal con- nected 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. Figure 1–14 Console Terminal Connections Tower Pedestal/Rack...

  • Page 43: Chapter 2 Operation

    Chapter 2 Operation This chapter gives instructions for basic system operation. The following topics are covered: • Powering Up the System • Power-Up Displays • SRM Console • Displaying the Hardware Configuration • Setting SRM Environment Variables • Setting Console Security •...

  • Page 44: Powering Up The System

    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. Figure 2–1 Operator Control Panel PK0204A Power button Control panel display ES45 Owner's Guide...

  • Page 45: Power-Up Displays

    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.

  • Page 46: Srom Power-Up Display

    2.2.1 SROM Power-Up Display Example 2–1 Sample SROM Power-Up Display SROM V2.15 CPU # 00 @ 1000 PCI Test SROM program starting Power on Reloading SROM SROM V2.15 CPU # 00 @ 1000 System Bus Speed @ 0125 SROM program starting RelCPU PCI66 bus speed check Reloading SROM...
  • Page 47 When the system powers up, the SROM code is loaded into the I-cache (in- struction cache) on the first available CPU, which becomes the primary CPU. The order of precedence is CPU0, CPU1, and so on. The primary CPU at- tempts to access the PCI bus.

  • Page 48: Srm Console Power-Up Display

    2.2.2 SRM Console Power-Up Display At the completion of SROM power-up, the primary CPU transfers con- trol 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.
  • Page 49 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.
  • Page 50 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...
  • Page 51 The console is started on the secondary CPUs. The example shows a four- processor 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 multiproces- sor system, the prompt could be P00>>>, P01>>>, P02>>>, or P03>>>.

  • Page 52: Srm Console

    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 sys- tem board.

  • Page 53: Selecting The Display Device

    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.

  • Page 54: Setting A Control Panel Message

    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 com- pleted. When the operating system is running, the control panel displays the console revision.

  • Page 55: Displaying The Hardware Configuration

    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 connec- tions. Use the following SRM console commands to view the system configuration. show boot* Displays the boot environment variables.

  • Page 56: Displaying Boot Environment Variables

    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 vari- ables.
  • Page 57 boot_dev Device or device list from which booting is to be at- tempted, 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 com- mand.

  • Page 58: 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: V5.9-9 PALcode: OpenVMS PALcode V1.91-33, Tru64 UNIX PALcode V1.87-27...
  • Page 59 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.
  • Page 60 Hose 1, Bus 0, PCI − 66 MHz Slot Option Adaptec AIC-7899 pka0.7.0.1.1 SCSI Bus ID 7 dka0.0.0.1.1 COMPAQ BD018122C9 Adaptec AIC-7899 pkb0.7.0.101.1 SCSI Bus ID 7 Yukon PCI Hot-Plug C Hose 2, Bus 0, PCI − 66 MHz Slot...
  • Page 61 NOTE: The naming of devices (for example,dqa.0.0.15.0) follows the con- ventions 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.

  • Page 62: Physical I/O Slots Map To Logical Slots: Model 1B

    Table 2–1 Physical I/O Slots Map to Logical Slots: Model 1B Physical Slot SRM Logical ID (7-Slot) Hose 0 Slot ID 11 Hose 0 Slot ID 10 Hose 2 Slot ID 5 Hose 3 Slot ID 2 Hose 3 Slot ID 1 Hose 1 Slot ID 2 Hose 1 Slot ID 1 Table 2–2 Physical I/O Slots Map to Logical Slots: Model 2B...

  • Page 63: Physical I/O Slots Map To Logical Slots: Model 3B

    Table 2–3 Physical I/O Slots Map to Logical Slots: Model 3B Physical Slot SRM Logical ID (10-Slot Legacy PCI) Hose 2 Slot ID 1 Hose 2 Slot ID 2 Hose 0 Slot ID 11 Hose 3 Slot ID 2 Hose 3 Slot ID 1 Hose 0 Slot ID 10 Hose 1 Slot ID 2 Hose 1 Slot ID 1...

  • Page 64: Displaying The Bootable Devices

    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 DKA0 RZ2DD-LS 0306 dka100.1.0.1.1 DKA100 RZ2DD-LS 0306 dka200.2.0.1.1 DKA200 RZ1CB-CS 0844 dkb0.0.0.3.1 DKB0...

  • Page 65: Device Naming Conventions

    Table 2–4 Device Naming Conventions Category Description The device, dqa0 is used as an example in the following device category and description. Driver ID Two-letter designator of port or class driver SCSI drive or CD Ethernet port IDE CD-ROM FDDI device RAID set device SCSI tape DSSI disk...

  • Page 66: Viewing The Memory Configuration

    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 Base Address Intlv Mode --------- ---------- ---------------- ---------- 4096Mb 0000000000000000 2-Way 1024Mb 0000000200000000 2-Way 4096Mb 0000000100000000 2-Way...

  • Page 67: Setting Srm Environment Variables

    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 sub- stituted for envar.

  • Page 68: Setting Console Security

    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: •...

  • Page 69: Setting The Console Password

    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. Example 2–9 Set Password P00>>> set password Please enter the password: Please enter the password again: P00>>>...
  • Page 70 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.

  • Page 71: Setting The Console To Secure Mode

    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>>>...

  • Page 72: Turning Off Security During A Console Session

    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.
  • Page 73 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 dis- played: Please enter the password: If the password entered matches the password in NVRAM, when the prompt is...

  • Page 74: Returning To User Mode

    2.6.4 Returning to User Mode The clear password command clears the password environment vari- able, 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>>>...

  • Page 75: Updating Firmware

    You can also obtain Alpha firmware updates from the Inter- net. Quarterly Update Service The Alpha Systems Firmware Update Kit CD-ROM is available by subscription from Compaq. Alpha Firmware Internet Access You can also obtain Alpha firmware update files from the Internet: http://ftp.digital.com/pub/DEC/Alpha/firmware/ If you do not have a Web browser, you can access files using anonymous ftp: $ ftp ftp.digital.com...

  • Page 76: Firmware Update Utility

    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 im- age, 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 revi- sion of the firmware.
  • Page 77 Device Current Revision Filename Update Revision V5.9-8 srm_fw V5.9-9 srom V2.17-F srom_fw V2.18-F UPD> u Confirm update on: srom [Y/(N)]y WARNING: updates may take several minutes to complete for each de- vice. DO NOT ABORT! Updating to V5.9-9... Verifying V5.9-9... PASSED. srom Updating to V2.18-F...

  • Page 78: Manual Updates

    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...

  • Page 79: Updating From The Cd-Rom

    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.

  • Page 80: Updating From An Openvms System Disk

    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) fwup- date.exe $ copy/contiguous fwupdate.exe "system_disk":[sys0.sysexe]...

  • Page 81: Updating From The Network

    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.

  • Page 83: Chapter 3 Booting And Installing An Operating System

    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. Re- fer to your operating system documentation for complete instructions on booting or starting an installation.

  • Page 84: Setting Boot Options

    Setting Boot Options You can set a default boot device, boot flags, and network boot proto- cols 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.
  • Page 85 3.1.1 auto_action The SRM auto_action environment variable determines the default ac- tion the system takes when the system is power cycled, reset, or ex- periences a failure. Systems can boot automatically (if set to autoboot) from the default boot device under the following conditions: •...
  • Page 86 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 de- vice.
  • Page 87 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. Booting and Installing an Operating System 3-5...
  • Page 88 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.
  • Page 89 The command to boot Linux into single-user mode is similar to the following example, where “/” root is in partition 2 of dka0, and the kernel is in /boot/compaq.gz. P00>>> boot –file “1/vmlinux.gz” –flags “root=/dev/sda2 rw single”...
  • Page 90 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: root_number Root Directory 0 (default) [SYS0.SYSEXE] [SYS1.SYSEXE] [SYS2.SYSEXE] [SYS3.SYSEXE] boot_flags The hexadecimal value of the bit number or numbers set.

  • Page 91: Openvms Boot Flag Settings

    Table 3–1 OpenVMS Boot Flag Settings Flags_Value Bit Number Meaning Bootstrap conversationally (enables you to mod- ify SYSGEN parameters in SYSBOOT). Map XDELTA to a running system. Stop at initial system breakpoint. Perform diagnostic bootstrap. Stop at the bootstrap breakpoints. Omit header from secondary bootstrap image.
  • Page 92 Legal values are nvram and bootp. The default value is bootp. Set this envi- ronment 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.

  • Page 93: Ei*0_Protocols Or Ew*0_Protocols

    3.1.6 ei*0_protocols or ew*0_protocols The ei*0_protocols or ew*0_protocols environment variable sets net- work 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.
  • Page 94 Example P00>>> show device ewa0.0.0.1001.0 EWA0 08-00-2B-3E-BC-B5 ewb0.0.0.12.0 EWB0 00-00-C0-33-E0-0D ewc0.0.0.13.0 EWC0 08-00-2B-E6-4B-F3 P00>>> set ewa0_protocols bootp P00>>> show ewa0_protocols ewa0_protocols bootp 3-12 ES45 Owner's Guide...

  • Page 95: Booting Tru64 Unix

    1616192 Starting at 0xfffffc00004403e0 Alpha boot: available memory from 0xc9d4000 to 0x27ffee000 Compaq Tru64 UNIX V5.1A-8 (Rev. 1764); Mon Jun 11 16:12:47 EDT 2001 physical memory = 10240.00 megabytes. available memory = 10038.09 megabytes. Booting and Installing an Operating System 3-13...
  • Page 96 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.

  • Page 97: Booting Tru64 Unix Over The Network

    3.2.1 Booting Tru64 UNIX over the Network To boot your Tru64 UNIX system over the network, make sure the sys- tem 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.
  • Page 98 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.

  • Page 99: Starting A Tru64 Unix Installation

    Starting a Tru64 UNIX Installation Tru64 UNIX is installed from the CD-ROM drive connected to the sys- tem. 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>>>...
  • Page 100 There are two types of installations: The Default Installation installs a mandatory set of software subsets on a predetermined file system layout. 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 option puts your system in single-user mode with superuser privileges.

  • Page 101: Booting Linux

    V5.6-3 Mar 12 2001 08:36:11 P00>> 2. Enter the show device command to determine the unit number of the drive for your boot device, in this case dka0.0.0.17.0. P00>>> sh dev dka0.0.0.17.0 DKA0 COMPAQ BD018122C9 B016 dka200.2.0.7.1 DKA200 COMPAQ BD018122C9 B016 dqa0.0.0.105.0...
  • Page 102 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>>>...
  • Page 103 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 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...

  • Page 104: Booting Openvms

    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...
  • Page 105 Example 3–5 shows a boot from a CD-ROM on a local drive. The example is ab- breviated. 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>>>.

  • Page 106: Booting Openvms From The Infoserver

    3.5.1 Booting OpenVMS from the InfoServer You can boot OpenVMS from a LAN device on the InfoServer. The de- vices 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>>>...
  • Page 107 Network Initial System Load Function Version 1.2 FUNCTION FUNCTION Display Menu Help Choose Service Select Options Stop Enter a function ID value: Enter a function ID Value: OPTION OPTION Find Services 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.

  • Page 108: Starting An Openvms Installation

    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 ©...
  • Page 109 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. Booting and Installing an Operating System 3-27...

  • Page 111: Chapter 4 Configuring And Installing Components

    Chapter 4 Configuring and Installing Components This chapter shows how to configure and install components in a tower or ped- estal system. Installation of components in a rackmount system is reserved for service providers and self-maintenance customers. The following topics are covered: •...
  • Page 112 WARNING: To prevent injury, access is limited to persons who have appropriate technical training and experience. Such per- sons are expected to understand the hazards of working within this equipment and take measures to minimize danger to them- selves or others. These measures include: 1.

  • Page 113: Removing Enclosure Panels

    Removing Enclosure Panels Open and remove the front door. Loosen the screws that allow you to remove the top and side panels. Figure 4–1 Enclosure Panel Removal (Tower) PK0221B Configuring and Installing Components...
  • Page 114 To Remove Enclosure Panels from a Tower The enclosure panels are secured by captive screws. 1. From the open position , lift up and away to remove the front door 2. To remove the top panel, loosen the top left and top right screws .

  • Page 115: Enclosure Panel Removal (Pedestal)

    Figure 4–2 Enclosure Panel Removal (Pedestal) PK0234A Configuring and Installing Components...
  • Page 116 To Remove Enclosure Panels from a Pedestal The enclosure panels are secured by captive screws. 1. From the open position, lift up and away to remove the front door (both doors are removed in the same way). 2. Remove the top enclosure panel by loosening the captive screws shown in .

  • Page 117: Removing Covers From The System Chassis

    Removing Covers from the System Chassis WARNING: To prevent injury, access is limited to persons who have appropriate technical training and experience. Such per- sons are expected to understand the hazards of working within this equipment and take measures to minimize danger to them- selves or others.
  • Page 118 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: 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.

  • Page 119: Removing Covers From A Tower

    Figure 4–3 Removing Covers from a Tower PK0216A Configuring and Installing Components...

  • Page 120: Removing Covers From A Pedestal/Rack

    Figure 4–4 Removing Covers from a Pedestal/Rack PK0215A 4-10 ES45 Owner's Guide...

  • Page 121: Before Installing Components

    Before Installing Components You must shut down the operating system, turn off power to the sys- tem, 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.

  • Page 122: Memory Allocation

    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 ad- ditional memory to support the new configuration. A crash and reboot cycle can occur several times until the console has allocated enough memory.
  • Page 123 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 P00>>> show memory Array Size Base Address Intlv Mode --------- ---------- ----------------...
  • Page 124 After the console completes its final reinitialization, the console banner is dis- played, followed by the P00>>> prompt. Enter the show heap_expand com- mand 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.

  • Page 125: Power Supply Configuration

    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. Figure 4–5 Power Supply Locations Pedestal/Rack Tower 1 1 1...
  • Page 126 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: •...

  • Page 127: Removing And Replacing Power Supplies

    Removing and Replacing Power Supplies Figure 4–6 Installing a Power Supply (Pedestal/Rack View) PK0232A Configuring and Installing Components 4-17...
  • Page 128 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. Loosen the three Phillips screws that secure the power supply bracket. (There is no need to remove the screws.) Remove the bracket 3.

  • Page 129: Cpu Configuration

    CPU Configuration Before installing additional CPUs, become familiar with the location of the CPU slots and the configuration rules. Figure 4–7 CPU Slot Locations (Pedestal/Rack View) CPU 3 CPU 1 CPU 0 CPU 2 PK0228B Configuring and Installing Components 4-19...

  • Page 130: Cpu Slot Locations (Tower View)

    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.

  • Page 131: Installing Cpus

    Installing CPUs Figure 4–9 CPU Card Installation (Pedestal/Rack View) Slot 3 Slot 1 Slot 0 Slot 2 PK0240B WARNING: To prevent injury, access is limited to persons who have appropriate technical training and experience. Such per- sons are expected to understand the hazards of working within this equipment and take measures to minimize danger to them- selves or others.
  • Page 132 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.

  • Page 133: Memory Configuration

    Memory Configuration Become familiar with the rules for memory configuration before add- ing 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.

  • Page 134: Stacked And Unstacked Dimms

    Figure 4–10 Stacked and Unstacked DIMMs Unstacked DIMMS Stacked DIMMS PK1209 4-24 ES45 Owner's Guide...
  • Page 135 Rules for DIMM Installation Refer to Figure 4–11 or Figure 4–12 and observe the following rules for install- ing DIMMs. • You can install up to 32 DIMMs (Models 2, 2B, and 3B) and up to 16 DIMMs (Model 1B). •...

  • Page 136: Memory Configuration (Pedestal/Rack View)

    Figure 4–11 Memory Configuration (Pedestal/Rack View) Set # Set # Set # MMB 0 Array 0 Set # Set # 0 & 4 MMB 1 Array 1 Set # 1 & 5 Array 2 MMB 2 Set # 2 & 6 Array 3 Set # 3 &...

  • Page 137: Memory Configuration (Tower View)

    Figure 4–12 Memory Configuration (Tower View) Set # MMB 3 Set # MMB 2 Set # MMB 1 Set # Array 2 Array 0 Set # 2 & 6 Set # 0 & 4 MMB 0 Array 1 Array 3 Set # 1 &...

  • Page 138: Installing Dimms

    4.10 Installing DIMMs Figure 4–13 Installing DIMMs Pedestal/Rack Tower PK0205B 4-28 ES45 Owner's Guide...
  • Page 139 WARNING: To prevent injury, access is limited to persons who have appropriate technical training and experience. Such per- sons are expected to understand the hazards of working within this equipment and take measures to minimize danger to them- selves or others. WARNING: Do not remove memory modules until the green LEDs are off (approximately 20 seconds after a power-down).

  • Page 140: Aligning Dimm In Mmb

    7. To install the DIMM, align the notches on the gold fingers with the connec- tor 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 PK0953A 9.

  • Page 141: Pci Configuration

    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 uni- versal 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.

  • Page 142: Model 1B Pci Backplane

    (described in Chapter 2). The table in Figure 4–15 maps the physical slot numbers to the SRM logical ID numbers for the back- plane. For information on restriction, see http://www.compaq.com/alphaserver/. NOTE: To take advantage of 66 MHz, all modules in that hose must be 66 MHz capable.

  • Page 143: Model 2B Pci Backplane

    (described in Chapter 2). The table in Figure 4–16 maps the physical slot numbers to the SRM logical ID numbers for the back- plane. For information on restriction, see http://www.compaq.com/alphaserver/. NOTE: To take advantage of 66 MHz, all modules in that hose must be 66 MHz capable.

  • Page 144: Model 3B Pci Backplane

    (described in Chapter 2). The table in Figure 4–17 maps the physical slot numbers to the SRM logical ID numbers for the back- plane. For information on restriction, see http://www.compaq.com/alphaserver/. NOTE: To take advantage of 66 MHz, all modules in that hose must be 66 MHz capable.

  • Page 145: Installing Pci Cards

    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 installa- tion document that came with the option and follow the manufac- turer's instructions. WARNING: To prevent injury, access is limited to persons who have appropriate technical training and experience.

  • Page 146: Pci Card Installation (Pedestal/Rack View)

    Figure 4–18 PCI Card Installation (Pedestal/Rack View) MR0027 CAUTION: Hot swap is not currently available with the ES45, however the hardware is on the system. Do not press switch or latch the hot-swap board when the system is running. Pressing any of these switches may result in loss of data.
  • Page 147 If you are removing a PCI option card, perform step 4. 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 6.

  • Page 148: Installing Universal Hard Disk Drives

    4.13 Installing Universal Hard Disk Drives The system uses hot-pluggable universal hard disk drives. Hot- pluggable drives can be replaced without removing power from the system or interrupting the transfer of data over the SCSI bus. WARNING: To prevent injury, access is limited to persons who have appropriate technical training and experience.

  • Page 149: Installing A Hard Drive

    Figure 4–19 Installing a Hard Drive MR0064 Configuring and Installing Components 4-39...
  • Page 150 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 re- lease lever towards the drive.

  • Page 151: Disk Drive Status Leds

    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.

  • Page 152: Disk Drive Status Led Conditions

    Table 4–1 Disk Drive Status LED Conditions LED is on LED is off 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. •...
  • Page 153 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.

  • Page 154: Installing A Removable Media Device

    4.14 Installing a Removable Media Device Figure 4–21 Installing a 5.25-Inch Device (Pedestal/Rack View) PK0235A 4-44 ES45 Owner's Guide...
  • Page 155 WARNING: To prevent injury, access is limited to persons who have appropriate technical training and experience. Such per- sons are expected to understand the hazards of working within this equipment and take measures to minimize danger to them- selves or others. WARNING: To prevent injury, unplug the power cord from each power supply before installing com- ponents.
  • Page 156 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.

  • Page 157: Installing Disk Drive Cages

    4.15 Installing Disk Drive Cages Install a drive cage in the left bay opening first. Figure 4–22 Disk Cage Installation PKO974-0A Configuring and Installing Components 4-47...
  • Page 158 WARNING: To prevent injury, access is limited to persons who have appropriate technical training and experience. Such per- sons are expected to understand the hazards of working within this equipment and take measures to minimize danger to them- selves or others. WARNING: To prevent injury, unplug the power cord from each power supply before installing com- ponents.
  • Page 159 Figure 4–23 Disk Cage Installation PKO975-0B Configuring and Installing Components 4-49...
  • Page 160 9. Partially slide the drive cage 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. 12. Slide the cage in the rest of the way and attach it with the four screws set aside previously.

  • Page 161: Fan Locations

    Figure 4–24 Fan Locations PK0208a Configuring and Installing Components 4-51...

  • Page 162: Cabling A Second Disk Drive Cage

    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. Figure 4–25 Cabling a Second Disk Cage PKO976-00 4-52 ES45 Owner's Guide...

  • Page 163: External Scsi Expansion

    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 sup- ported options list.

  • Page 165: Chapter 5 Firmware

    Chapter 5 Firmware The SRM user interface is the command-line interface that allows you to config- ure 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. Key sec- tions in this chapter are: •...

  • Page 166: Console Overview

    Console Overview The system has a console consisting of firmware programs and an at- tached 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, al- lowing you to upgrade the code without installing new chips.

  • Page 167: Invoking The Srm Console

    console terminal can be either a serial terminal (VT320 or higher, or equiva- lent) or a VGA monitor. 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>>>.

  • Page 168: Srm Command Overview

    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 Loads and starts the operating system.
  • Page 169 Table 5–1 Summary of SRM Console Commands (Continued) Command Function show config Displays the logical configuration at the last system initiali- zation. show device Displays a list of controllers and bootable devices in the sys- tem. Reports errors logged in the EEPROMs. show error show fru Displays the physical configuration of all field-replaceable...

  • Page 170: Notation Formats For Srm Console Commands

    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 back- slash character for line continuation (see Table 5–3).

  • Page 171: Special Characters For Srm Console

    Table 5–3 Special Characters for SRM Console Character Function Return or En- Terminates a command line. No action is taken on a com- mand until it is terminated. If no characters are entered and this key is pressed, the console just redisplays the prompt.
  • Page 172 Table 5–3 Special Characters for SRM Console (Continued) Character Function Ctrl/Q Resumes output to the console terminal that was sus- pended by Ctrl/S. Ctrl/R Redisplays the current line. Deleted characters are omit- ted. This command is useful for hardcopy terminals. Ctrl/S Suspends output to the console terminal until Ctrl/Q is entered.

  • Page 173: Management Tasks Performed From Srm

    Management Tasks Performed from SRM This section lists system management tasks and the related SRM com- mands. Table 5–4 Management Tasks and Related SRM Commands Task Commands Get help on SRM commands help or man Display the item indicated (such as the logical con- show (config, device, figuration or the system FRUs) error, fru, memory,...

  • Page 174: Getting Help On Srm Commands

    Getting Help on SRM Commands The help (or man) command displays basic information about a com- mand. Example 5–1 Help (or Man) P00>>> help set NAME FUNCTION Set or modify the value of an environment variable. SYNOPSIS set <envar> <value> [-integer] [-string] where <en-...

  • Page 175: Displaying The Logical Configuration

    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: V5.9-9 PALcode: OpenVMS PALcode V1.91-33, Tru64 UNIX PALcode V1.87-27...
  • Page 176 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.
  • Page 177 Hose 1, Bus 0, PCI − 66 MHz Slot Option Adaptec AIC-7899 pka0.7.0.1.1 SCSI Bus ID 7 dka0.0.0.1.1 COMPAQ BD018122C9 Adaptec AIC-7899 pkb0.7.0.101.1 SCSI Bus ID 7 Yukon PCI Hot-Plug C Hose 2, Bus 0, PCI − 66 MHz Slot...
  • Page 178 NOTE: The naming of devices (for example,dqa.0.0.15.0) follows the con- ventions 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.

  • Page 179: How Physical I/O Slots Map To Logical Slots

    Table 5–5 How Physical I/O Slots Map to Logical Slots: Model 1B Physical Slot SRM Logical ID (7-Slot) Hose 2 Slot ID 5 Hose 3 Slot ID 2 Hose 3 Slot ID 1 Hose 1 Slot ID 2 Hose 1 Slot ID 1 Hose 0 Slot ID 9 Hose 1 Slot ID 8 Table 5–6 How Physical I/O Slots Map to Logical Slots: Model 2B...
  • Page 180 Table 5–7 How Physical I/O Slots Map to Logical Slots: Model 3B Physical Slot SRM Logical ID (10-Slot Legacy PCI) Hose 2 Slot ID 1 Hose 2 Slot ID 2 Hose 0 Slot ID 11 Hose 3 Slot ID 2 Hose 3 Slot ID 1 Hose 0 Slot ID 10 Hose 1 Slot ID 2...

  • Page 181: Displaying The Bootable Devices

    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 DKA0 RZ2DD-LS 0306 dka100.1.0.1.1 DKA100 RZ2DD-LS 0306 dka200.2.0.1.1 DKA200 RZ1CB-CS 0844 dkb0.0.0.3.1 DKB0 RZ25 0900 dqa0.0.0.15.0 DQA0 TOSHIBA CD-ROM XM-6302B 1012 dva0.0.0.1000.0...

  • Page 182: Displaying The System Frus

    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 Part# Serial#...
  • Page 183 See Table 5–9. Part # The part number of the FRU in ASCII, either a Compaq part number or a vendor part number. Serial # The serial number. For Compaq FRUs, the serial number has the form XXYWWNNNNN.

  • Page 184: Bit Assignments For Error Field

    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 manufac- turer's name. Table 5–9 Bit Assignments for Error Field Meaning...

  • Page 185: Displaying Frus With Errors

    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>>>...

  • Page 186: Displaying The Memory Configuration

    5.5.5 Displaying the Memory Configuration Use the show memory command to view the total memory size and lo- cation. Example 5–6 Show Memory P00>>> show memory Array Size Base Address Intlv Mode --------- ---------- ---------------- ---------- 4096Mb 0000000000000000 2-Way 1024Mb 0000000200000000 2-Way 4096Mb...

  • Page 187: Displaying The Power Status

    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, in- voke RMC and issue the env command. Example 5–8 Show Power P00>>>...

  • Page 188: Displaying The Srm Console Version

    5.5.8 Displaying the SRM Console Version Use the show version command to display the version of the SRM con- sole 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.

  • Page 189: Booting An Operating System

    Booting an Operating System The boot command boots the Tru64 UNIX, Linux, or OpenVMS operat- ing 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.
  • Page 190 -file file- Specifies the name of a file to load into the system. Use the set name 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.

  • Page 191: Testing The System

    Testing the System The test command verifies the configuration of the devices in the sys- tem. Example 5–11 Test P00>>> test Testing the Memory Testing the DK* Disks(read only) No DU* Disks available for testing No DR* Disks available for testing Testing the DQ* Disks(read only) Testing the DF* Disks(read only) No MK* Tapes available for testing...
  • Page 192 4. VGA console tests: These tests are run only if the console environment variable is set to serial. The VGA console test displays rows of the word compaq. 5. Network internal loopback tests for EW* networks. 5-28 ES45 Owner's Guide...

  • Page 193: Forcing A System Crash Dump

    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.
  • Page 194 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 con- sole, then enter the crash command to restart the primary CPU and force a crash dump to the selected device.

  • Page 195: Resuming Program Execution

    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.

  • Page 196: Reading A File

    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.

  • Page 197: Initializing The System

    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.86-26 starting console on CPU 0 initialized idle PCB initializing semaphores initializing heap...
  • Page 198 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...
  • Page 199 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.

  • Page 200: Creating A Power-Up Script

    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.
  • Page 201 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.

  • Page 202: Entering The Rmc From The Local Vga Monitor

    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 avail- able and all output is redirected to the VGA monitor. Example 5–18 Entering RMC from a VGA Monitor Failing Connection P00>>>...
  • Page 203 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.

  • Page 204: Setting And Viewing Environment Variables

    5.14 Setting and Viewing Environment Variables Use the set envar and show envar commands to set and view environ- ment 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.
  • Page 205 Reset button or by issuing the init command. A reset or init is also required when setting up environment variables for an OpenVMS Galaxy configuration. See the DS20E-ES45 Remedial Kit available from http://www.service.compaq.com/patches. auto_action console...

  • Page 206: Environment Variable Summary

    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,...
  • Page 207 Table 5–10 Environment Variable Summary (Continued) Environment Variable Function ei*0_mode or Specifies the connection type of the default Ethernet controller. ew*0_mode ei*0_protocols or Specifies network protocols for booting over the Ethernet controller. ew*0_protocols Specifies the default console keyboard type. kbd_hardware_ type language Specifies the console keyboard layout.

  • Page 208: Auto_Action

    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.
  • Page 209 Examples In the following example, the operator sets the auto_action environment vari- able to restart. The device specified with the bootdef_dev environment vari- able is dka0. When Tru64 UNIX is shut down and rebooted, the system will reboot from dka0. P00>>>...

  • Page 210: Bootdef_Dev

    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 de- vice.

  • Page 211: Boot_File

    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>>>...
  • Page 212 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.

  • Page 213: Boot_Osflags

    The command to boot Linux into single-user mode is similar to the following example, where “/” root is in partition 2 of dka0, and the kernel is in /boot/compaq.gz. P00>>> boot –file “1/vmlinux.gz” –flags “root=/dev/sda2 rw single”...

  • Page 214: Openvms Boot Flag Settings

    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: root_number Root Directory 0 (default) [SYS0.SYSEXE] [SYS1.SYSEXE] [SYS2.SYSEXE] [SYS3.SYSEXE] boot_flags The hexadecimal value of the bit number or numbers set.
  • Page 215 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.
  • Page 216 5.14.5 com*_baud The default baud rate for the system is 9600. The com*_baud com- mands 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.

  • Page 217: Com*_Flow

    5.14.6 com*_flow The com1_flow and com2_flow environment variables set the flow con- trol 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 set- ting for devices that do not recognize XON/XOFF or that would be confused by these signals.

  • Page 218: Com1_Mode

    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.
  • Page 219 Syntax set com1_mode value value Defined values are: through All data passes through RMC and is filtered for the RMC escape se- quence. This is the default. snoop Data partially bypasses RMC, but RMC taps into the data lines and listens passively for the RMC escape sequence.
  • Page 220 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 op- erating system determines whether the port should assert a signal DTR.

  • Page 221: Console

    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: The console terminal is a VGA monitor or a device con- graphics (default) nected to the VGA port.

  • Page 222: Cpu_Enabled

    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 spe- cific CPU. These errors might be displayed during power-up or might be dis- played with the show fru or show config command.
  • Page 223 Syntax set cpu_enabled hex_digit The hex_digit values are shown in the table. Binary Equivalent Hex_Digit Value CPU enable 3210 (bit) Enabled CPUs 0000 No CPUs (CPU 0 still comes up) 0001 CPU 0 0010 CPU 1 0011 CPU 0,1 0100 CPU 2 0101 CPU 0,2...

  • Page 224: Ei*0_Inet_Init Or Ew*0_Inet_Init

    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 envi- ronment variable if you are booting Tru64 UNIX from a RIS server.

  • Page 225: Ei*0_Mode Or Ew*0_Mode

    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”...
  • Page 226 When both are listed, the system attempts to use the mop protocol first, regardless of which is listed first. If not successful, it then attempts the bootp protocol. Example P00>>> show dev dka0.0.0.8.0 DKA0 COMPAQ BD018122C9 B016 dka100.1.0.8.0 DKA100 COMPAQ BD018122C9 B016 dka200.2.0.8.0...

  • Page 227: Kbd_Hardware_Type

    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 in- terpret the terminal keyboard layout correctly. Syntax set kbd_hardware_type keyboard_type The options for keyboard_type are: Selects the 102-type keyboard layout. pcxal (default) lk411 Selects the LK411 keyboard layout.

  • Page 228: Language

    5.14.15 language The language environment variable specifies the keyboard layout, which depends on the language. The setting of the language environ- ment 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.

  • Page 229: Memory_Test

    5.14.16 memory_test The memory_test environment variable determines the extent of mem- ory testing on the next reset. You can set this variable for systems run- ning Tru64 UNIX. Syntax set memory_test value The options for value are: full (default) Specifies that the full memory test will be run. Systems us- ing the OpenVMS operating system must run the full mem- ory test.

  • Page 230: Ocp_Text

    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.

  • Page 231: Os_Type

    5.14.18 os_type The os_type environment variable specifies the default operating sys- tem. 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.

  • Page 232: Pci_Parity

    5.14.19 pci_parity The pci_parity environment variable disables or enables parity check- ing on the PCI bus. Some PCI devices do not implement PCI parity checking, and some have a par- ity-generating scheme in which the parity is sometimes incorrect or is not fully compliant with the PCI specification.
  • Page 233 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.
  • Page 234 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 six- teen 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 be- tween 0 and 15.
  • Page 235 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.
  • Page 236 Examples In this example, both terminators are disabled. P00>>> set pkb0_soft_term off P00>>> init P00>>> show pkb0_soft_term pkb0_soft_term In this example, the terminator for the high 8 bits is enabled. P00>>> set pkb0_soft_term high P00>>> init P00>>> show pkb0_soft_term pkb0_soft_term high 5-72 ES45 Owner's Guide...

  • Page 237: Tt_Allow_Login

    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.

  • Page 239: Chapter 6 Remote Management

    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 func- tionality. This chapter explains the operation and use of the RMC. Sections are: •...

  • Page 240: Rmc Overview

    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. •...
  • Page 241 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.

  • Page 242: Operating Modes

    Operating Modes The RMC can be configured to manage different data flow paths de- fined 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.
  • Page 243 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.

  • Page 244: Bypass Modes

    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 by- pass modes are Snoop, Soft Bypass, and Firm Bypass. Figure 6–2 Data Flow in Bypass Mode System DUART COM1...
  • Page 245 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 by- pass modes.
  • Page 246 After downloading binary files, you can set the com1_mode environment vari- able from the SRM console to switch back to Snoop mode or other modes for ac- cessing the RMC, or you can hang up the current modem session and reconnect 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.

  • Page 247: Terminal Setup

    Terminal Setup You can use the RMC from a modem hookup or the serial terminal con- nected to the system. As shown in Figure 6–3, a modem is connected to the dedicated 9-pin modem port and a terminal is connected to the COM1 serial port/terminal port (MMJ) Figure 6–3 Setup for RMC (Tower View) PK0934A...

  • Page 248: Srm Environment Variables For Com1

    SRM Environment Variables for COM1 Several SRM environment variables allow you to set up the COM1 se- rial 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.

  • Page 249: Entering The Rmc

    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 oper- ating system, SRM, or an application.
  • Page 250 Entering from the Local VGA Monitor To enter the RMC from the local VGA monitor, the console environment vari- able 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 but- ton to disconnect and to reload the SRM console.

  • Page 251: Using The Command-Line Interface

    Using the Command-Line Interface The remote management console supports setup commands and com- mands 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.

  • Page 252: Displaying The System Status

    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.6...

  • Page 253: Status Command Fields

    Table 6–1 Status Command Fields Field Meaning On-Chip Firmware Revision of RMC firmware on the microcontroller. Revision: Flash Firmware Revi- Revision of RMC firmware in flash ROM. sion: Server Power: ON = System is on. OFF = System is off. System Halt: Asserted = System has been halted.

  • Page 254: Displaying The System Environment

    6.6.2 Displaying the System Environment The RMC env command provides a snapshot of the system environ- ment. RMC> env System Hardware Monitor Temperature (warnings at 48.00C, power-off at 53.00C) CPU0: 27.00C CPU1: 28.00C CPU2: 27.00C CPU3: 28.00C Zone0: 26.00C Zone1: 28.00C Zone2: 26.00C Fan RPM Fan1: 2149...
  • Page 255 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.

  • Page 256: Using Power On And Off, Reset, And Halt Functions

    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 com- mand powers the system off.
  • Page 257 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>...

  • Page 258: Configuring Remote Dial-In

    6.6.4 Configuring Remote Dial-In Before you can dial in through the RMC modem port or enable the sys- tem 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 pa- rameters.
  • Page 259 Sets the password that is prompted for at the beginning of a modem ses- sion. 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.

  • Page 260: Configuring Dial-Out Alert

    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 sys- tem status. If dial-out alert is enabled, and the RMC detects alarm conditions within the managed system, it can call a preset pager num- ber.
  • Page 261 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.

  • Page 262: Elements Of Dial String And Alert String

    Table 6–2 Elements of Dial String and Alert String Dial String The dial string is case sensitive. The RMC automatically con- verts all alphabetic characters to uppercase. AT = Attention. ATXDT X = Forces the modem to dial “blindly” (not seek the dial tone).

  • Page 263: Resetting The Rmc To Factory Defaults

    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 se- quence. WARNING: To prevent injury, access is limited to persons who have appropriate technical training and experience.

  • Page 264: Rmc Jumpers (Default Positions)

    Figure 6–4 RMC Jumpers (Default Positions) 1 2 3 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.

  • Page 265: Rmc Command Reference

    RMC Command Reference This section describes the RMC command set. Commands are listed in alphabetical order. clear {alert, port} disable {alert, remote} dump enable {alert, remote} 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.
  • Page 266 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 con- trolled by the RMC if the port is currently locked by an application program, without resetting the entire system.
  • Page 267 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.
  • Page 268 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.
  • Page 269 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.
  • Page 270 help or ? The help or ? command displays the RMC command set. RMC> help clear {alert, port} deposit disable {alert, remote} dump enable {alert, remote} 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...
  • Page 271 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 fol- lowing 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.
  • Page 272 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.
  • Page 273 • 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.
  • Page 274 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 pag- ing service is to be contacted, the string must include the appropriate modem commands to dial the number.
  • Page 275 set init The set init command sets the modem initialization string. The initialization string is limited to 31 characters and can be modified, depend- ing 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.
  • Page 276 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.

  • Page 277: Troubleshooting Tips

    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 The RMC may be in Issue the show RMC from the modem. soft bypass or firm by- com1_mode command pass mode.
  • Page 278 Table 6–3 RMC Troubleshooting (Continued) Symptom Possible Cause Suggested Solution RMC will not answer On AC power-up, RMC Wait 30 seconds after when modem is called. defers initializing the mo- powering up the system (continued from previ- dem for 30 seconds to allow and RMC before at- ous page) the modem to complete its...

  • Page 279: Chapter 7 Troubleshooting

    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. This chapter covers the following topics: •...

  • Page 280: Power-Up Error Messages

    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...

  • Page 281: Error Beep Codes

    Table 7–1 Error Beep Codes Beep Associated Code Messages Meaning Jump to SROM code has completed execution. System jumps to Console 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.

  • Page 282: Checksum Error

    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 fail- safe loader (FSL) so that you can load new console firmware images. A sequence similar to the one in Example 7–1 occurs.
  • Page 283 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.

  • Page 284: No Mem Error

    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.

  • Page 285: Rmc Error Messages

    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.
  • Page 286 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.

  • Page 287: Srom Error Messages

    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).
  • Page 288 Table 7–3 SROM Error Messages (Continued) Code SROM Message OCP Message Memory address line error Mem Err Memory pattern error Mem Err Memory pattern ECC error Mem Err Configuration error on CPU #3 CfgERR 3 Configuration error on CPU #2 CfgERR 2 Configuration error on CPU #1 CfgERR 1...

  • Page 289: Srm Diagnostics

    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 power- up self-tests.

  • Page 290: Show Device 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 DKA0 RZ2DD-LS 0306...
  • Page 291 4. VGA console tests: These tests are run only if the console environment variable is set to serial. The VGA console test displays rows of the word compaq. 5. Network internal loopback tests for EW* networks. NOTE: No write tests are performed on disk and tape drives. Media must be installed to test the diskette drive and tape drives.

  • Page 292: Show Fru Command

    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>>>...
  • Page 293 See Table 7–4. Part # The part number of the FRU in ASCII, either a Compaq part number or a vendor part number. Serial # The serial number. For Compaq FRUs, the serial number has the form XXYWWNNNNN.

  • Page 294: Show Error Command

    Table 7–4 Bit Assignments for Error Field 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...

  • Page 295: Show Power Command

    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.

  • Page 296: Crash 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.

  • Page 297: Troubleshooting Tables

    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.

  • Page 298: Power Problems

    Table 7–5 Power Problems Symptom Action System does not Check that AC power is available and all power cords power on. 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.

  • Page 299: Problems Getting To Console Mode

    Table 7–6 Problems Getting to Console Mode Symptom Action Power-up screen is Interpret the error beep codes and observe the control not displayed. 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.

  • Page 300: Problems Reported By The Console

    Table 7–7 Problems Reported by the Console Symptom Action Power-up tests are not Interpret the error beep codes at power-up and completed. check the power-up screen for a failure detected during self-tests. The system attempts to boot The system automatically reverts to the fail- from the floppy drive after a safe loader to load new SRM firmware.

  • Page 301: Boot Problems

    Table 7–8 Boot Problems Symptom Action System cannot find Check the system configuration for the correct device boot 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.

  • Page 302: Errors Reported By The Operating System

    Table 7–9 Errors Reported by the Operating System Symptom Action System has crashed, but Press the Halt button and enter the SRM crash SRM console is operating. command to provide a crash dump file for analysis. If the problem is intermittent, run the SRM test command.

  • Page 303: Option Card Problems

    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.

  • Page 304: Troubleshooting Pci Bus Problems

    Options List. (If the device is not on the list, refer to the device's documentation.) The Supported Options List is on the World Wide Web: http://www.compaq.com/alphaserver/options/ases40/ases40_options.html • Storage adapter—Run the test command to exercise the storage devices off the PCI controller option.

  • Page 305: Chapter 8 Specifications

    Chapter 8 Specifications This chapter gives specifications for ES45 systems: • Physical Specifications • Environmental Specifications • Electrical Specifications • Regulatory Approvals • Acoustic Data Specifications 8-1...

  • Page 306: Physical Specifications

    Physical Specifications Table 8–1 Physical Characteristics — Tower Dimensions Height 50.8 cm (20.0 in.) Width 38.7 cm (15.25 in.) Depth 80.5 cm (31.7 in.) Weight Nominal: 65 kg (143 lb) Max: 96 kg (211 lb) Shipping Container Height 82.4 cm (32.2 in.) Width 60.2 cm (24.0 in.) Depth...

  • Page 307: Physical Characteristics - Pedestal

    Table 8–2 Physical Characteristics — Pedestal Dimensions Height 78.2 cm (30.8 in.) Width 50.8 cm (20.0 in.) Depth 82.3 cm (32.4 in.) Weight Nominal: 127 kg (280 lb) Max: 159 kg (350 lb) Shipping Container Height 107.7 cm (42.4 in.) Width 100.3 cm (39.5 in.) Depth...

  • Page 308: Physical Characteristics - Rackmount

    Table 8–3 Physical Characteristics — Rackmount Dimensions Height 35.2 cm (13.87 in.) Fits 14 in. [8U] standard RETMA cabinets Width 44.7 cm (17.6 in.) Depth 78.2 cm (30.8 in.) Weight 1. When lifting Nominal: 50 kg (110 lb) Max: 76 kg (167.2 lb) 2.

  • Page 309: Physical Characteristics - Cabinets

    Table 8–4 Physical Characteristics — Cabinets Dimensions H9A10 M-Series Height 170 cm (67.0 in.) Width 60 cm (23.6 in.) Depth 110 cm (43.27 in.) Weight Configuration-dependent Max payload 1000 lb H9A15 M-Series Height 200 cm (79.0 in.) Width 60 cm (23.6 in.) Depth 110 cm (43.27 in.) Weight...

  • Page 310: Environmental Specifications

    Environmental Specifications Table 8–5 Environmental Characteristics — All System Variants Temperature Operating 10–35 C (50–95 Nonoperating –40 to 66 C (–40 to 151 Storage (60 days) –40 to 66 C (–40 to 151 Rate of change C/hr (20 F/hr) Relative humidity Operating 10 to 90% Nonoperating...

  • Page 311: Electrical Specifications

    Electrical Specifications Table 8–6 Electrical Characteristics — All System Variants Nominal voltage (Vac) 200–240 Voltage range (Vac) 180–250 (temporary condition) Power source phase Single Nominal frequency (Hz) 50/60 Frequency range (Hz) 47–53/57–63 RMS current (max. steady state) Tower and Rackmount Single power cord 5.6 A Multiple power cords...
  • Page 312 Table 8–6 Electrical Characteristics — All System Variants (Cont.) Power Cord System Variant Quantity Length Type 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 Pedestal 275 cm (108 in.)

  • Page 313: Regulatory Approvals

    Regulatory Approvals Table 8–7 Regulatory Approvals Agency approvals 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.04 Class A BSMI: CNS13438 Class A C-Tick: AS/NZS 3548:1995 Class A UL 60950, 3rd edition, 2000...

  • Page 314: Acoustic Data

    Acoustics — Declared Values per ISO 9296 and ISO 7779 , dBA (bystander positions) Product Idle Operate Idle Operate Rackmount or Tower Pedestal StorageWorks Model 43xx Current values for specific configurations are available from Compaq representatives. 1 B = 10 dBA. 8-10 ES45 Owner’s Guide...

  • Page 315: Index

    Index Bus node ID, SCSI, 5-70 Bypass modes, 6-6 Bypassing the RMC, 6-6 Acoustics, 8-10 Allocation memory, 4-12 APB program, 3-25 Chassis auto_action environment variable, 3-3, 5-3, 5-44 system building blocks, 1-4 auto_action environment variable, SRM, 5-35 Checksum error, 7-4 Autoboot, 5-44 clear alert command (RMC), 6-27 Auxiliary power supply, RMC, 6-3...
  • Page 316 Connectors, rear, 1-8 disable remote command (RMC), 6-28 Console commands list (SRM), 5-4 Display device, verifying, 2-11 Console device, activating, 5-73 Displaying logical configuration, 5-11 console environment variable, 5-57 DPR, 6-3 console environment variable (SRM), 2-3 Drive status LEDs, 4-41 Console event log, 7-11 DTR, asserting, 5-56 Console mode, 5-2...

  • Page 317: Installing Dimms

    init command (SRM), 5-33 Initializing the system, 5-33 Factory-installed software (FIS), 3-1 Installing CPUs, 4-21 Fail-safe loader, 7-4 Installing DIMMs, 4-28 Fan failure, 7-20 Installing hard drives, 4-38 Fans, status of, 5-23 Installing OpenVMS, 3-26, 3-27 Fast SCSI, 5-69 Installing PCI cards, 4-35 File, displaying, 5-32 Installing power supplies, 4-17 Firm bypass mode, 6-8...

  • Page 318: Operator Control Panel

    Memory, displaying, 5-22 memory_test environment variable, 5-65 Pagers, 6-23 Messages, power-up, 2-3 PALcode version, displaying, 5-22 MMBs, 1-13 Parity checking, 5-68 Model 1B Password, setting SRM, 2-27 backplane slot information, 4-32 PCI backplane overview, 1-14 Model 1B overview, 1-14 rules and requirements, 4-32 Model 2B overview, 1-16 Model 2B Model 3B overview, 1-18...
  • Page 319 SRM, 5-65 firm bypass mode, 6-8 Power-up procedure, 2-5 hangup command, 6-21 Power-up script, creating, 5-36 local mode, 6-5 Problems getting to console mode, 7-21 logic, 6-3 Problems reported by console, 7-22 operating modes, 6-4 Processor card, 1-13 overview, 6-2 Processor, enabling, 5-58 PIC processor, 6-3 Program, resuming, 5-31...

  • Page 320: Set Ocp_Text Command

    console password, 2-27 console password clearing, 2-32 SCSI bus length, 4-53 SRM console SCSI controller IDs, 5-70 command syntax, 5-6 SCSI devices, speed of, 5-69 device naming, 2-23 SCSI expansion, 4-53 device naming conventions, 5-17 SCSI terminators, enabling, 5-71 displaying system configuration, 5-11 Secure function commands, 2-26 finding help, 5-10 Secure mode, setting SRM to, 2-29...

  • Page 321: System Motherboard Block Diagram

    SROM error messages, 7-10 UART ports, 6-5 power-up display, 2-4, 2-5 UNIX power-up messages, 2-3 booting, 3-13 status command (RMC), 6-14, 6-38 booting from SCSI disk, 3-13 Storage booting over the network, 3-15 hard drive, 1-23 installing, 3-17 removable media, 1-22 text-based installation display, 3-17 Storage subsystem, 1-23 Updating firmware, 2-33...

This manual is also suitable for:

Alphaserver es45 2Alphaserver es45 2bAlphaserver es45 3b

Table of Contents