Page 1 AlphaServer ES40 and AlphaStation ES40 Owner’s Guide Order Number: EK-ES240-UG. B01 This manual is for managers and operators of ES40 systems. Compaq Computer Corporation...
Page 2 Alpha, AlphaServer, and OpenVMS are registered in the U.S Patent and Trademark Office. COMPAQ, the Compaq logo, and Tru64 are copyrighted and are trademarks of Compaq. Linux is a registered trademark of Linus Torvalds. UNIX is a registered trademark in the U.S. and other countries, licensed exclusively through X/Open Company Ltd.
Page 3 FCC Notice: The equipment described in this manual generates, uses, and may emit radio frequency energy. The equipment has been type tested and found to comply with the limits for a Class A digital device pursuant to Part 15 of FCC rules, which are designed to provide reasonable protection against such radio frequency interference.
Page 5: Table Of Contents
Contents Preface ........................xiii Chapter 1 System Overview System Enclosures ................1-2 System Chassis—Front View/Top View..........1-4 System Chassis—Rear View ..............1-5 Rear Ports and Slots ................1-6 Operator Control Panel................. 1-8 System Board ..................1-10 PCI Backplane ..................1-12 Power Supplies..................
Page 6 Setting Automatic Booting..............2-25 2.7.1 Setting Auto Start................. 2-25 Changing the Default Boot Device............2-26 Running AlphaBIOS-Based Utilities ..........2-27 2.9.1 Running Utilities from a VGA Monitor ........2-28 2.9.2 Setting Up Serial Mode..............2-30 2.9.3 Running Utilities from a Serial Terminal ........2-31 Chapter 3 Booting and Installing an Operating System Setting Boot Options ................
Page 7 4.6.7 Resetting the Escape Sequence ............ 4-27 Resetting the RMC to Factory Defaults..........4-28 Troubleshooting Tips ................4-30 Chapter 5 Configuring and Installing Components Removing Enclosure Panels..............5-2 Removing Covers from the System Chassis.......... 5-6 Before Installing Components............... 5-9 Memory Allocation ................5-10 Power Supply Configuration ...............
Page 8 RMC Error Messages ................7-8 SROM Error Messages................ 7-10 SRM Diagnostics ................. 7-12 7.4.1 Console Event Log ................ 7-12 7.4.2 Show Device Command ..............7-13 7.4.3 Test Command................7-14 7.4.4 Show FRU Command..............7-16 7.4.5 Show Error Command ..............7-19 7.4.6 Show Power Command ..............
Page 9 4–2 Dial-Out Alert Configuration .............. 4-24 5–1 Memory Allocation Crash/Reboot Cycle..........5-10 6–1 Update Utility Display................6-3 7–1 Checksum Error and Fail-Safe Load ............ 7-4 7–2 Sample Console Event Log..............7-12 7–3 Show Device Command............... 7-13 7–4 Test Command ..................7-14 7–5 Show Fru Command ................
Page 10 5–7 CPU Slot Locations (Pedestal/Rack View) .......... 5-16 5–8 CPU Slot Locations (Tower View)............5-17 5–9 CPU Card Installation (Pedestal/Rack View) ........5-18 5–10 Stacked and Unstacked DIMMs ............5-22 5–11 Memory Configuration (Pedestal/Rack View) ........5-24 5–12 Memory Configuration (Tower View)..........5-25 5–13 Installing DIMMs................
Page 11 8–7 Regulatory Approvals................8-8 8–8 Acoustic Data ..................8-9...
Page 13: Preface
Preface Intended Audience This manual is for managers and operators of ES40 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 14 Documentation Titles Table 1 ES40 Documentation Title Order Number User Documentation Kit QA-6E88A-G8 Owner’s Guide EK-ES240-UG User Interface Guide EK-ES240-UI Tower and Pedestal Basic EK-ES240-PD Installation Release Notes EK-ES240-RN Documentation CD (6 languages) AG-RF9HA-BE Maintenance Kit QZ-01BAB-GZ Service Guide EK-ES240-SV Service Guide HTML CD AG-RKAKA-BE Illustrated Parts Breakdown...
Page 15: 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 Board PCI Backplane Power Supplies Removable Media Storage Hard Disk Storage System Access Console Terminal NOTE: See Chapter 5 for warnings and procedures for accessing internal parts...
Page 16: System Enclosures
System Enclosures The ES40 family consists of a standalone tower, a pedestal with expanded storage capacity, and a rackmount system. Figure 1–1 ES40 Systems Rackmount Pedestal Tower PK0212 ES40 Owner’s Guide...
Page 17 Common Components The basic building block of the system is the chassis, which houses the following common components: Up to four CPUs, based on the EV6 or EV67 Alpha chip Memory DIMMs (200-pin); up to 16 or up to 32 Six or ten 64-bit PCI slots Floppy diskette drive (3.5-inch, high density) CD-ROM drive...
Page 18: System Chassis-Front View/Top View
System Chassis—Front View/Top View Figure 1–2 Top/Front Components (Pedestal/Rack View) PK0201 Operator control panel CD-ROM drive Removable media bays Floppy diskette drive Storage drive bays Fans CPUs Memory PCI cards ES40 Owner’s Guide...
Page 19: System Chassis-Rear View
System Chassis—Rear View Figure 1–3 Rear Components (Pedestal/Rack View) PK0206 Power supplies PCI bulkhead I/O ports System Overview...
Page 20: Rear Ports And Slots
Rear Ports and Slots Figure 1–4 Rear Connectors Pedestal/ Rack Tower PK0209 ES40 Owner’s Guide...
Page 21 Rear Panel Connections Modem port—Dedicated 9-pin port for modem connection to remote management console. COM2 serial port—Extra port to modem or any serial device. Keyboard port—To PS/2-compatible keyboard. Mouse port—To PS/2-compatible mouse. COM1 MMJ-type serial port/terminal port—For connecting a console terminal.
Page 22: 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 23 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 24: System Board
System Board The system motherboard is located on the floor of the system card cage. It has slots for the CPUs and memory motherboards (MMBs). The system motherboard has the majority of the logic for the system. It has slots for the CPUs and memory motherboards (MMBs) and has the PCI backplane interconnect.
Page 25 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 EV6 or EV67 microprocessor, a current implementation of the Alpha architecture. The microprocessor is a superscalar CPU with out-of-order execution and speculative execution to maximize speed and performance.
Page 26: Pci Backplane
PCI Backplane The PCI backplane has two 64-bit, 33 MHz PCI buses that support 64-bit PCI slots. The 64-bit PCI slots are split across two independent 64-bit, 33 MHz PCI buses. The PCI buses support 3.3 V or 5 V options. Figure 1–7 shows the location of the PCI slots in a 6-slot system and a 10-slot system.
Page 27: Pci Slot Mapping
Table 1–1 shows the correspondence between the physical locations of the slots on the PCI backplane and the logical numbering reported with the SRM console show config command (described in Chapter 2). See Chapter 5 for instructions on installing PCI options. Table 1–1 PCI Slot Mapping Physical Slot Logical Slot...
Page 28: Power Supplies
Power Supplies The power supplies provide power to components in the system chassis. The number of power supplies required depends on the system configuration. Figure 1–8 Power Supplies Tower Pedestal/Rack 1 1 1 2 2 2 PK0207 1-14 ES40 Owner’s Guide...
Page 29 One to three power supplies provide power to components in the system chassis. The system supports redundant power configurations to ensure continued system operation if a power supply fails. When more than one power supply is installed, the supplies share the load. The power supplies select line voltage and frequency automatically (100 V or 120 V or 200–240 V and 50 Hz or 60 Hz).
Page 30: Removable Media Storage
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 drives or one additional full-height drive. The 5.25-inch half height area has a divider that can be removed to mount one full-height 5.25-inch device.
Page 31: 1.10 Hard Disk Storage
1.10 Hard Disk Storage The system chassis can house up to two storage disk cages. You can install four 1.6-inch hard drives in each storage disk cage. See Chapter 5 for information on installing hard disk drives. Figure 1–10 Hard Disk Storage Cage with Drives (Tower View) PK0935 System Overview 1-17...
Page 32: 1.11 System Access
1.11 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–11 System Keys Tower Pedestal PK0224 1-18 ES40 Owner’s Guide...
Page 33 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 34: 1.12 Console Terminal
1.12 Console Terminal The console terminal can be a serial (character cell) terminal connected to the COM1 or COM2 port or a VGA monitor connected to a VGA adapter on PCI 0. A VGA monitor requires a keyboard and mouse. Figure 1–12 Console Terminal Connections Tower Pedestal/Rack...
Page 35: Chapter 2 Operation
Chapter 2 Operation This chapter gives basic operating instructions, including powering up and configuring the machine. This chapter has the following sections: Powering Up the System Power-Up Displays System Consoles Displaying a Hardware Configuration Setting SRM Environment Variables Setting SRM Console Security Setting Automatic Booting Changing the Default Boot Device Running AlphaBIOS-Based Utilities...
Page 36: 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 2-2 ES40 Owner’s Guide...
Page 37: 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 38: Srom Power-Up Display
2.2.1 SROM Power-Up Display Example 2–1 Sample SROM Power-Up Display SROM Power-Up Display OCP Message PCI Test SROM V2.3 CPU #00 @ 0500 Power on SROM program starting Reloading SROM SROM V2.5-F CPU # 00 @ 0667 RelCPU SROM program starting Starting secondary on CPU #1 BC Data Starting secondary on CPU #2...
Page 39 When the system powers up, the SROM code is loaded into the I-cache (instruction cache) on the first available CPU, which becomes the primary CPU. The order of precedence is CPU0, CPU1, and so on. The primary CPU attempts to access the PCI bus. If it cannot, either a hang or a failure occurs, and this is the only message displayed.
Page 40: Srm Console Power-Up Display
2.2.2 SRM Console Power-Up Display At the completion of SROM power-up, the primary CPU transfers control to the SRM console program. The console program continues the system initialization. Failures are reported to the console terminal through the power-up screen and a console event log. Example 2–2 SRM Power-Up Display OpenVMS PALcode V1.69-2, Tru64 UNIX PALcode V1.62-1...
Page 41 The primary CPU prints a message indicating that it is running the console. Starting with this message, the power-up display is sent to any console terminal, regardless of the state of the console environment variable. If console is set to graphics, the display from this point on is saved in a memory buffer and displayed on the VGA monitor after the PCI buses are sized and the VGA device is initialized.
Page 42 Example 2–2 SRM Power-Up Display (Continued) entering idle loop initializing keyboard starting console on CPU 1 initialized idle PCB initializing idle process PID lowering IPL CPU 1 speed is 667 MHz create powerup starting console on CPU 2 initialized idle PCB initializing idle process PID lowering IPL CPU 2 speed is 667 MHz...
Page 43 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 multiprocessor system, the prompt could be P00>>>, P01>>>, P02>>>, or P03>>>.
Page 44: System Consoles
System Consoles System console programs are located in a flash ROM (read-only memory) on the system board. From the SRM console interface, you can set up and boot the operating system, display the system configuration, and perform other tasks. From AlphaBIOS you can run AlphaBIOS-compliant utilities.
Page 45 SRM Console The operating system is configured from the SRM console, a command-line interface (CLI). From the CLI you can enter commands to configure the system, view the system configuration, and boot. For example, to verify that the system sees the bootable devices that are attached, enter: P00>>>...
Page 46: 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 or AlphaBIOS 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 47: Setting The Control Panel Message
2.3.2 Setting the Control Panel Message You can create a customized message to be displayed on the operator control panel after startup self-tests and diagnostics have been completed. When the operating system is running, the control panel displays the console revision.
Page 48: Displaying A Hardware Configuration
Displaying a 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 devices, memory configuration, network connections. Use the following SRM console commands to view the system configuration. Additional commands to view the system configuration are described in the ES40 User Interface Guide.
Page 49: Displaying Boot Environment Variables
2.4.1 Displaying Boot Environment Variables Use the show boot* command to list the boot environment variables. Example 2–4 Show Boot* P00>>> show boot* boot_dev dka0.0.0.1.1 boot_file boot_osflags boot_reset bootdef_dev dka0.0.0.1.1 booted_dev booted_file booted_osflags Operation 2-15...
Page 50: Displaying The Logical Configuration
Displaying the Logical Configuration Use the show config command to display the logical configuration. To display the physical configuration, issue the show fru command. Example 2–5 Show Config P00>>>sh config Compaq Computer Corporation Compaq AlphaServer ES40 Firmware SRM Console: V5.6-102 ARC Console: v5.70...
Page 51 Firmware. Version numbers of the SRM console, AlphaBIOS (ARC) 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 52 Example 2–5 Show Config (Continued) Slot Option Hose 0, Bus 0, PCI ELSA GLoria Synergy Acer Labs M1543C Bridge to Bus 1, ISA Acer Labs M1543C IDE dqa.0.0.15.0 dqb.0.1.15.0 dqa0.0.0.15.0 TOSHIBA CD-ROM XM-6302B Acer Labs M1543C USB Option Hose 0, Bus 1, ISA Floppy dva0.0.0.1000.0 Slot...
Page 53 PCI bus information. The “Slot” column lists the logical slots seen by the system. They are not the physical slots into which devices are installed. See Table 2–1 for the correspondence between logical slots and physical slots. The NCR 53C896 on Hose 0, Bus 0 is a dual-channel Ultra2 SCSI multifunction controller.
Page 54: Correspondence Between Logical And Physical Pci Slots
Table 2–1 Correspondence Between Logical and Physical PCI Slots Physical Slot Logical Slot PCI 0 Device Device Device Device Physical Slot Logical Slot PCI 1 Device Device Device Device Device Device NOTE: PCI 0 and PCI 1 correspond to Hose 0 and Hose 1 in the logical configuration.
Page 55: Displaying The Bootable Devices
2.4.3 Displaying the Bootable Devices Use the show device command to display the bootable devices. DK = SCSI drive; DQ = IDE drive; DV = diskette drive; EI or EW = Ethernet controller; PK = SCSI controller. Example 2–6 Show Device P00>>>...
Page 56: Viewing Memory Configuration
2.4.4 Viewing Memory Configuration Use the show memory command to view the configuration of main memory. Example 2–7 Show Memory P00>>>show memory Array Size Base Address Intlv Mode --------- ---------- ---------------- ---------- 256Mb 0000000060000000 2-Way 512Mb 0000000040000000 2-Way 256Mb 0000000070000000 2-Way 1024Mb 0000000000000000...
Page 57: 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 substituted for envar.
Page 58: Setting Srm Console Security
Setting SRM Console Security You can set the SRM console to secure mode to prevent unauthorized personnel from modifying the system parameters or otherwise tampering with the system from the console. When the SRM is set to secure mode, you can use only two console commands: The boot command, to boot the operating system The continue command, to resume running the operating system if you have inadvertently halted the system...
Page 59: Setting Automatic Booting
Setting Automatic Booting The system is factory set to halt in the SRM console. You can change this default, if desired. Systems can boot automatically (if set to autoboot) from the default boot device under the following conditions: When you first turn on system power When you power cycle or reset the system When system power comes on after a power failure After a bugcheck (OpenVMS) or panic (Tru64 UNIX or Linux)
Page 60: Changing The Default Boot Device
Changing the Default Boot Device You can change the default boot device with the set bootdef_dev command. You can designate a default boot device. You change the default boot device by using the set bootdef_dev SRM console command. For example, to set the boot device to the IDE CD-ROM, enter commands similar to the following: P00>>>...
Page 61: Running Alphabios-Based Utilities
Running AlphaBIOS-Based Utilities Depending upon the type of hardware you have, you may have to run hardware configuration utilities. Hardware configuration diskettes are shipped with your system or with options that you order. Typical configuration utilities include: Œ RAID standalone configuration utility for setting up RAID devices Œ...
Page 62: Running Utilities From A Vga Monitor
2.9.1 Running Utilities from a VGA Monitor Enter the alphabios command to bring up the AlphaBIOS console. Figure 2–4 AlphaBIOS Utilities Menu AlphaBIOS Setup F1=Help Display System Configuration... Upgrade AlphaBIOS Hard Disk Setup... CMOS Setup... Install Windows NT Utilities Display Error Frames... OS Selection Setup...
Page 63: Run Maintenance Program Dialog Box
4. In the Run Maintenance Program dialog box, type the name of the program to be run in the Program Name field. Then Tab to the Location list box, and select the hard disk partition, floppy disk, or CD-ROM drive from which to run the program.
Page 64: Setting Up Serial Mode
2.9.2 Setting Up Serial Mode Serial mode requires a VT320 or higher (or equivalent) terminal. To run AlphaBIOS-compliant utilities in serial mode, set the console environment variable to serial and enter the init command to reset the system. Set up the serial terminal as follows: 1.
Page 65: Running Utilities From A Serial Terminal
2.9.3 Running Utilities from a Serial Terminal Utilities are run from a serial terminal the same way as from a VGA monitor. The menus are the same, but some key mappings are different. Table 2–3 AlphaBIOS Option Key Mapping AlphaBIOS Key VTxxx Key Ctrl/A Ctrl/B...
Page 66 1. Enter the alphabios command to start the AlphaBIOS console. 2. From the AlphaBIOS Boot screen, press F2. 3. From AlphaBIOS Setup, select Utilities, and select Run Maintenance Program from the sub-menu that is displayed. Press Enter. 4. In the Run Maintenance Program dialog box, type the name of the program to be run in the Program Name field.
Page 67: 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. It also describes how to switch from one operating system to another. Refer to your operating system documentation for complete instructions on booting or starting an installation.
Page 68: Setting Boot Options
Setting Boot Options You can set a default boot device, boot flags, and network boot protocols by using the SRM set command with environment variables. Once these environment variables are set, the boot command defaults to the stored values. You can override the stored values for the current boot session by entering parameters on the boot command line.
Page 69: Bootdef_Dev
3.1.1 bootdef_dev The bootdef_dev environment variable specifies one or more devices from which to boot the operating system. When more than one device is specified, the system searches in the order listed and boots from the first device. Enter the show bootdef_dev command to display the current default boot device.
Page 70: Boot_File
3.1.2 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 For Linux systems, the filename is specific to the distribution of Linux: 2/boot/vmlinux.gz (Red Hat) 2/boot/vmlinuz (SuSE) Example...
Page 71: Boot_Osflags
3.1.3 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 72 Linux Systems The flags_value argument for Linux on an ES40 system is: “root=/dev/sda2” Flags_value Arguments for Red Hat Distribution Halt. (Do not set init default to this.) Single-user mode. Multiuser, without NFS (same as 3, if you do not have networking) Full multiuser mode (Default) Unused Reboot.
Page 73: 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 74: Ei*0_Inet_Init Or Ew*0_Inet_Init
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 75: Ei*0_Protocols Or Ew*0_Protocols
3.1.5 ei*0_protocols or ew*0_protocols The ei*0_protocols or ew*0_protocols environment variable sets network protocols for booting and other functions. To list the network devices on your system, enter the show device command. The Ethernet controllers start with the letters “ei” or “ew,” for example, ewa0. The third letter is the adapter ID for the specific Ethernet controller.
Page 76: Booting Tru64 Unix
Booting Tru64 UNIX UNIX can be booted from a CD-ROM on a local drive (a CD-ROM drive connected to the system), from a local SCSI disk, or from a UNIX RIS server. Example 3–1 Booting UNIX from a Local SCSI Disk P00>>>...
Page 77 1958 buffers containing 15.29 megabytes of memory Master cpu at slot 0. Firmware revision: 5.6-102 PALcode: Tru64 UNIX version 1.62-1 Compaq AlphaServer ES40 Tru64 UNIX Version V4.0F Login: Example 3–1 shows a boot from a local SCSI drive. The example is abbreviated.
Page 78: 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 system is registered on a Remote Installation Services (RIS) server. See the UNIX document entitled Sharing Software on a Local Area Network for registration information.
Page 79 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 80: Starting A Tru64 Unix Installation
Starting a Tru64 UNIX Installation Tru64 UNIX is installed from the CD-ROM drive connected to the system. The display that you see after you boot the CD depends on whether your system console is a VGA monitor or a serial terminal. Example 3–3 Text-Based Installation Display P00>>>...
Page 81 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 82: Booting Linux
Booting Linux Obtain the Linux installation document and install Linux on the system. Then verify boot parameters and issue the boot command. The procedure for installing Linux on an ES40 is documented in the Linux Installation and Configuration Guide for AlphaServer DS10, DS20, ES40, and AlphaStation XP1000 Computers.
Page 83 secondary_console_message: on 0 from 1 HALT_REASON 0x0 FLAGS 0x1ee secondary_console_message: on 0 message is ’P01>>>START P01>>>’ smp_boot_cpus: Total of 2 Processors activated (1992.29 BogoMIPS). start_secondary: commencing CPU 1 current fffffc003ffe0000 Alpha PCI BIOS32 revision 0.04 PCI: Probing PCI hardware Linux NET4.0 for Linux 2.2 General self-test: passed.
Page 84: 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 85 Example 3–5 shows a boot from a CD-ROM on a local drive. The example is abbreviated. For complete instructions on booting OpenVMS, see the OpenVMS installation document. 1. Power up the system. The system stops at the SRM console prompt, P00>>>.
Page 86: Booting Openvms From The Infoserver
3.5.1 Booting OpenVMS from the InfoServer You can boot OpenVMS from a LAN device on the InfoServer. devices are designated EW*0 or EI*0. The asterisk stands for the adapter ID (a, b, c, and so on). Example 3–6 InfoServer Boot P00>>>...
Page 87 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.2-1 1.
Page 88: 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.2-1 Copyright ©...
Page 89 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-23...
Page 90: Openvms Galaxy
Documentation for creating an OpenVMS Galaxy computing environment on the ES40 is available on the DS20E-ES40 remedial kit that supports this functionality. The remedial kit is located on the Compaq Services patch site: http://www.service.digital.com/patches Click on Search Patches and enter the following kit name: DEC-AXPVMS-VMS721-DS20E_ES40-V0100--4.PCSI...
Page 91: Switching Between Operating Systems
Switching Between Operating Systems The system supports three operating systems. You can install Tru64 UNIX, OpenVMS, or Linux. You can switch from one operating system to another by removing the disk for the operating system that is currently installed and installing the disk for the operating system you want to run.
Page 92: Switching Between Unix And Openvms
3.8.1 Switching Between UNIX and OpenVMS Follow this procedure if you have already installed an operating system and want to switch to another supported operating system. CAUTION: Before switching operating systems, make a note of the boot path and location of the system disk (controller, SCSI ID number, and so on) of the operating system you are removing so that you can restore that operating system at a later date.
Page 93: Chapter 4 Using The Remote Management Console
Chapter 4 Using the Remote Management Console You can manage the system through the remote management console (RMC). The RMC is implemented through an independent microprocessor that resides on the system board. The RMC also provides configuration and error log functionality.
Page 94: 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. Monitors thermal sensors on the CPUs, the PCI backplane, and the power supplies Monitors voltages, power supplies, and fans...
Page 95 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 6 for details.
Page 96: Operating Modes
Operating Modes The RMC can be configured to manage different data flow paths defined by the com1_mode environment variable. In Through mode (the default), all data and control signals flow from the system COM1 port through the RMC to the active external port. You can also set bypass modes so that the signals partially or completely bypass the RMC.
Page 97 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 98: Bypass Modes
4.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. bypass modes are Snoop, Soft Bypass, and Firm Bypass. Figure 4–2 Data Flow in Bypass Mode System DUART SRM/AlphaBIOS...
Page 99 Figure 4–2 shows the data flow in the bypass modes. Note that the internal system COM1 port is connected directly to the modem port. NOTE: You can connect a serial terminal to the modem port in any of the bypass modes. The local terminal is still connected to the RMC and can still enter the RMC to switch the COM1 mode if necessary.
Page 100 After downloading binary files, you can set the com1_mode environment variable from the SRM console to switch back to Snoop mode or other modes for accessing the RMC, or you can hang up the current modem session and reconnect it. Firm Bypass Mode In Firm Bypass mode all data and control signals are routed directly between the system COM1 port and the external modem port.
Page 101: Terminal Setup
Terminal Setup You can use the RMC from a modem hookup or the serial terminal connected to the system. As shown in Figure 4–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 4–3 Setup for RMC (Tower View) PK0934 Using the Remote Management Console...
Page 102: 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 operating system, SRM, AlphaBIOS, or an application. You can enter the RMC from the local terminal regardless of the current operating mode.
Page 103 Entering from the Local VGA Monitor To enter the RMC from the local VGA monitor, the console environment variable must be set to graphics. Invoke the SRM console and enter the rmc command. P00>>> rmc You are about to connect to the Remote Management Console. Use the RMC reset command or press the front panel reset button to disconnect and to reload the SRM console.
Page 104: Srm Environment Variables For Com1
SRM Environment Variables for COM1 Several SRM environment variables allow you to set up the COM1 serial port (MMJ) for use with the RMC. You may need to set the following environment variables from the SRM console, depending on how you decide to set up the RMC. com1_baud Sets the baud rate of the COM1 serial port and the modem port.
Page 105: Rmc Command-Line Interface
RMC Command-Line Interface The remote management console supports setup commands and commands for managing the system. The RMC commands are listed below. clear {alert, port} disable {alert, remote} dump enable {alert, remote} halt {in, out} hangup help or ? power {on, off} quit reset send alert...
Page 106 Command Conventions Observe the following conventions for entering RMC commands: Enter enough characters to distinguish the command. NOTE: The reset and quit commands are exceptions. You must enter the entire string for these commands to work. For commands consisting of two words, enter the entire first word and at least one letter of the second word.
Page 107: Defining The Com1 Data Flow
4.6.1 Defining the COM1 Data Flow Use the set com1_mode command from SRM or RMC to define the COM1 data flow paths. You can set com1_mode to one of the following values: All data passes through RMC and is filtered for the escape through sequence.
Page 108: Displaying The System Status
4.6.2 Displaying the System Status The RMC status command displays the current RMC settings. Table 4–1 explains the status fields. RMC> status PLATFORM STATUS On-Chip Firmware Revision: V1.0 Flash Firmware Revision: V2.2 Server Power: ON System Halt: Deasserted RMC Power Control: ON Escape Sequence: ^[^[RMC Remote Access: Enabled RMC Password: set...
Page 109: Status Command Fields
Table 4–1 Status Command Fields Field Meaning On-Chip Firmware Revision of RMC firmware on the microcontroller. Revision: Flash Firmware Revision of RMC firmware in flash ROM. Revision: Server Power: ON = System is on. OFF = System is off. System Halt: Asserted = System has been halted.
Page 110: Displaying The System Environment
4.6.3 Displaying the System Environment command provides a snapshot of the system environment. RMC> env System Hardware Monitor Temperature (warnings at 45.0°C, power-off at 50.0°C) CPU0: 26.0°C CPU1: 26.0°C CPU2: 27.0°C CPU3: 26.0°C Zone0: 29.0°C Zone1: 30.0°C Zone2: 31.0°C Fan RPM Fan1: 2295 Fan2: 2295 Fan3: 2205...
Page 111 CPU temperature. In this example four CPUs are present. Temperature of PCI backplane: Zone 0 includes PCI slots 1–3, Zone 1 includes PCI slots 7–10, and Zone 2 includes PCI slots 4–6. Fan RPM. With the exception of Fan 5, all fans are powered as long as the system is powered on.
Page 112: Power On And Off, Reset, And Halt
4.6.4 Power On and Off, Reset, and Halt The RMC power {on, off}, halt {in, out}, and reset commands perform the same functions as the buttons on the operator control panel. Power On and Power Off The RMC power on command powers the system on, and the power off command powers the system off.
Page 113 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 114: Configuring Remote Dial-In
4.6.5 Configuring Remote Dial-In Before you can dial in through the RMC modem port or enable the system to call out in response to system alerts, you must configure RMC for remote dial-in. Connect your modem to the 9-pin modem port and turn it on. Enter the RMC from either the local serial terminal or the local VGA monitor to set up the parameters.
Page 115 Sets the password that is prompted for at the beginning of a modem session. The string cannot exceed 14 characters and is not case sensitive. For security, the password is not echoed on the screen. When prompted for verification, type the password again. Sets the initialization string.
Page 116: Configuring Dial-Out Alert
4.6.6 Configuring Dial-Out Alert When you are not monitoring the system from a modem connection, you can use the RMC dial-out alert feature to remain informed of system status. If dial-out alert is enabled, and the RMC detects alarm conditions within the managed system, it can call a preset pager number.
Page 117 The elements of the dial string and alert string are shown in Table 4–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 118: Elements Of Dial String And Alert String
Table 4–2 Elements of Dial String and Alert String Dial String The dial string is case sensitive. The RMC automatically converts all alphabetic characters to uppercase. ATXDT AT = Attention. X = Forces the modem to dial “blindly” (not seek the dial tone).
Page 119: Resetting The Escape Sequence
4.6.7 Resetting the Escape Sequence The RMC set escape command sets a new escape sequence. The new escape sequence can be any character string, not to exceed 14 characters. A typical sequence consists of two or more control characters. It is recommended that control characters be used in preference to ASCII characters.
Page 120: 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 sequence. WARNING: To prevent injury, access is limited to persons who have appropriate technical training and experience.
Page 121: Rmc Jumpers (Default Positions)
Figure 4–4 RMC Jumpers (Default Positions) 1 2 3 PK0211 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 122: Troubleshooting Tips
Troubleshooting Tips Table 4–3 lists possible causes and suggested solutions for symptoms you might see. Table 4–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 com1_mode command bypass mode.
Page 123 Table 4–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 powering up the system (continued from modem for 30 seconds to and RMC before previous page) allow the modem to...
Page 125: Configuring And Installing Components
Chapter 5 Configuring and Installing Components This chapter shows how to configure and install components in a tower or pedestal system. Installation of components in a rackmount system is reserved for service providers and self-maintenance customers. WARNING: To prevent injury, access is limited to persons who have appropriate technical training and experience.
Page 126: 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 5–1 Enclosure Panel Removal (Tower) PK0221 ES40 Owner’s Guide...
Page 127 To Remove Enclosure Panels from a Tower The enclosure panels are secured by captive screws. 1. Remove the front door. 2. To remove the top panel, loosen the top left and top right screws . Slide the top panel back and lift it off the system. 3.
Page 128: Enclosure Panel Removal (Pedestal)
Figure 5–2 Enclosure Panel Removal (Pedestal) PK0234 ES40 Owner’s Guide...
Page 129 To Remove Enclosure Panels from a Pedestal The enclosure panels are secured by captive screws. 1. Open and remove the front doors. 2. To remove the top enclosure panel, loosen the captive screws shown in Slide the top panel back and lift it off the system. 3.
Page 130: 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 persons are expected to understand the hazards of working within this equipment and take measures to minimize danger to themselves or others.
Page 131: Removing Covers From A Tower
Figure 5–3 Removing Covers from a Tower PK0216 Configuring and Installing Components...
Page 132: Removing Covers From A Pedestal/Rack
Figure 5–4 Removing Covers from a Pedestal/Rack PK0215 ES40 Owner’s Guide...
Page 133: Before Installing Components
Before Installing Components You must shut down the operating system, turn off power to the system, and unplug the power cord from each supply before installing CPUs, memory DIMMs, PCI cards, or removable media devices. NOTE: You can install a power supply for redundancy at any time without shutting down the system.
Page 134: 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 additional memory to support the new configuration. A crash and reboot cycle can occur several times until the console has allocated enough memory.
Page 135 Memory Testing and Configuration Status Array Size Base Address --------- ---------- ---------------- 512Mb 0000000040000000 1024Mb 0000000000000000 256Mb 0000000060000000 256Mb 0000000070000000 2048 MB of System Memory Testing the System Testing the Disks (read only) Testing the Network Partition 0, Memory base: 000000000, size: 080000000 initializing GCT/FRU at offset 1dc000 AlphaServer ES40 Console V5.5-3059, built on May 14 1999 at 01:57:42 P00>>>show heap_expand...
Page 136: Power Supply Configuration
Power Supply Configuration system have single power supply redundant configurations. You can add a power supply for redundancy at any time without shutting down the system. Figure 5–5 Power Supply Locations Pedestal/Rack Tower 1 1 1 2 2 2 PK0207A 5-12 ES40 Owner’s Guide...
Page 137 The system can have the following power configurations: Single Power Supply. A single power supply is provided with entry-level systems, such as a system configured with: One or two CPUs One storage cage Two Power Supplies. Two power supplies are required if the system has more than two CPUs or if the system has a second storage cage.
Page 138: Removing And Replacing Power Supplies
Removing and Replacing Power Supplies Figure 5–6 Installing a Power Supply (Pedestal/Rack View) PK0232 5-14 ES40 Owner’s Guide...
Page 139 1. Loosen the three Phillips screws that secure the power supply bracket. (There is no need to remove the screws.) Remove the bracket 2. If you are installing a new supply, remove the screw and blank cover you are replacing a power supply, release the latch on the supply and pull the supply out of the system.
Page 140: Cpu Configuration
CPU Configuration Before installing additional CPUs, become familiar with the location of the CPU slots and the configuration rules. Figure 5–7 CPU Slot Locations (Pedestal/Rack View) CPU 3 CPU 2 CPU 1 CPU 0 PK0228 5-16 ES40 Owner’s Guide...
Page 141: Cpu Slot Locations (Tower View)
Figure 5–8 CPU Slot Locations (Tower View) CPU 3 CPU 2 CPU 1 CPU 0 PK0229 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 142: Installing Cpus
Installing CPUs Figure 5–9 CPU Card Installation (Pedestal/Rack View) PK0240 WARNING: To prevent injury, access is limited to persons who have appropriate technical training and experience. Such persons are expected to understand the hazards of working within this equipment and take measures to minimize danger to themselves or others.
Page 143 WARNING: CPU cards have parts that operate at high temperatures. Wait 2 minutes after power is removed before touching any module. WARNING: High current area. Currents exceeding V @ >240VA 240 VA can cause burns or eye injury. Avoid contact with parts or remove power prior to access. WARNING: To prevent injury, unplug the power cord from each power supply before installing components.
Page 144 Verification 1. Turn on power to the system. 2. During power-up, observe the screen display. The newly installed CPU should appear in the display. 3. Issue the show config command to display the status of the new CPU. 5-20 ES40 Owner’s Guide...
Page 145: Memory Configuration
Memory Configuration Become familiar with the rules for memory configuration before adding DIMMs to the system. Memory Performance Considerations Interleaved operations reduce the average latency and increase the memory throughput over non-interleaved operations. With one memory option (4 DIMMs) installed, memory interleaving will not occur. With two identical memory options (8 DIMMs) installed, memory read-write operations are two- way interleaved.
Page 146: Stacked And Unstacked Dimms
(see Figure 5–10). Stacked DIMMs provide twice the capacity of unstacked DIMMs, and, at the time of shipment, are the highest capacity DIMMs offered by Compaq. The system may have either stacked or unstacked DIMMs. You can mix stacked and unstacked DIMMs within the system, but not within an array.
Page 147: Installing Dimms
Rules for DIMM Installation Refer to Figure 5–11 or Figure 5–12 and observe the following rules for installing DIMMs. You can install up to 16 DIMMs or up to 32 DIMMs, depending on the system model you purchased. A n option consists of a set of 4 DIMMs. You must install all 4 DIMMs. Fill sets in numerical order.
Page 148: Memory Configuration (Pedestal/Rack View)
Figure 5–11 Memory Configuration (Pedestal/Rack View) Sets Sets Sets MMB 2 Sets MMB 0 Array 1 Sets 1 & 5 Array 3 Array 0 MMB 3 Sets 3 & 7 Sets 0 & 4 Array 2 Sets 2 & 6 MMB 1 PK0202 5-24...
Page 149: Memory Configuration (Tower View)
Figure 5–12 Memory Configuration (Tower View) Sets MMB 1 Sets MMB 3 Sets MMB 0 Sets Array 0 Array 1 MMB 2 Sets 0 & 4 Sets 1 & 5 Array 3 Array 2 Sets 3 & 7 Sets 2 & 6 PK0203 Configuring and Installing Components 5-25...
Page 150: 5.10 Installing Dimms
5.10 Installing DIMMs Figure 5–13 Installing DIMMs Pedestal Mini-Tower PK0205 5-26 ES40 Owner’s Guide...
Page 151 WARNING: To prevent injury, access is limited to persons who have appropriate technical training and experience. Such persons are expected to understand the hazards of working within this equipment and take measures to minimize danger to themselves or others. WARNING: Memory DIMMs have parts that operate at high temperatures.
Page 152: Aligning Dimm In Mmb
7. To install the DIMM, align the notches on the gold fingers with the connector keys as shown in Figure 5–14. Figure 5–14 Aligning DIMM in MMB PK0953 5-28 ES40 Owner’s Guide...
Page 153 8. Secure the DIMM with the clips on the MMB slot. 9. Reinstall the MMB. 10. Replace the system card cage cover and enclosure covers. 11. Reconnect the power cords. Verification 1. Turn on power to the system. 2. During power-up, observe the screen display for memory. The display shows how much memory is in each array.
Page 154: 5.11 Pci Configuration
5.11 PCI Configuration Note the operating system configuration restrictions before installing PCI cards. The PCI slot locations are shown in Figure 5–15 and Figure 5–16. The PCI slots are split across two independent 64-bit, 33 MHz PCI buses: PCI0 and PCI1. These buses correspond to Hose 0 and Hose 1 in the system logical configuration.
Page 155: Pci Slot Locations (Pedestal/Rack)
Figure 5–15 PCI Slot Locations (Pedestal/Rack) 10-Slot System 6-Slot System PK0226 Configuring and Installing Components 5-31...
Page 156: Pci Slot Locations (Tower)
Figure 5–16 PCI Slot Locations (Tower) 10-Slot System 1 2 3 4 5 6 7 8 9 10 6-Slot System 8 9 10 1 2 3 PK0227 5-32 ES40 Owner’s Guide...
Page 157: 5.12 Installing Pci Cards
5.12 Installing PCI Cards Some PCI options require drivers to be installed and configured. These options come with a floppy or a CD-ROM. Refer to the installation document that came with the option and follow the manufacturer’s instructions. WARNING: To prevent injury, access is limited to persons who have appropriate technical training and experience.
Page 158: Pci Card Installation (Pedestal/Rack View)
Figure 5–17 PCI Card Installation (Pedestal/Rack View) PK0245 5-34 ES40 Owner’s Guide...
Page 159 NOTE: Some full-length PCI cards may have extender brackets for installing into ISA/EISA card cages. Remove the extender brackets before installing the card. 1. Shut down the operating system and turn off power to the system. Unplug the power cord from each power supply. 2.
Page 160: 5.13 Installing A Hard Drive
5.13 Installing a Hard Drive WARNING: To prevent injury, access is limited to persons who have appropriate technical training and experience. Such persons are expected to understand the hazards of working within this equipment and take measures to minimize danger to themselves or others.
Page 161 1. Shut down the operating system. 2. Unlock the front door to access the storage drive area. 3. Remove a blank bezel for the next available slot. 4. Push the button to release the plastic handle on the front of the drive carrier.
Page 162: 5.14 Installing A Removable Media Device
5.14 Installing a Removable Media Device Figure 5–19 Installing a 5.25-Inch Device (Pedestal/Rack View) PK0235 5-38 ES40 Owner’s Guide...
Page 163 WARNING: To prevent injury, access is limited to persons who have appropriate technical training and experience. Such persons are expected to understand the hazards of working within this equipment and take measures to minimize danger to themselves or others. WARNING: To prevent injury, unplug the power cord from each power supply before installing components.
Page 164 10. Plug the power cable (4-conductor) into the storage device. 11. Plug the signal and power cables back into the CD. 12. Replace the PCI card cage cover and enclosure covers. 13. Reconnect the power cords. Verification 1. Turn on power to the system. 2.
Page 165: 5.15 Installing Four-Slot Disk Cages
5.15 Installing Four-Slot Disk Cages WARNING: To prevent injury, access is limited to persons who have appropriate technical training and experience. Such persons are expected to understand the hazards of working within this equipment and take measures to minimize danger to themselves or others.
Page 166: Installing Disk Cages
Figure 5–20 Installing Disk Cages Left Cage Right Cage Left Cage Right Cage PK0299 5-42 ES40 Owner’s Guide...
Page 167 Installing the Right Cage (or Top Cage) NOTE: In a pedestal or rackmount system, install the right cage first. In a tower system, install the top cage first. 1. Shut down the operating system and turn off power to the system. Unplug the power cord from each power supply.
Page 168 7. Slide the cage part way into the system chassis. 8. Connect the power source cable to the storage backplane. 9. Plug one end of the 68-conductor SCSI cable (17-04867-01) into the SCSI controller . Route it through the opening in the PCI cage.
Page 169: 5.16 External Scsi Expansion
5.16 External SCSI Expansion External SCSI devices, such as tabletop or rack-mounted storage devices, can be connected to the system using PCI-based SCSI adapters. Use the following rules to determine if a particular device can be used: The device must be supported by the operating system. Consult the supported options list.
Page 171: Chapter 6 Updating Firmware
Chapter 6 Updating Firmware This chapter describes how to update to a later version of system firmware. Typically, you update system firmware whenever the operating system is updated. You might also need to update firmware: If you add I/O device controllers and adapters If enhancements are made to the firmware If the serial ROM or RMC firmware should ever become corrupted This chapter contains the following topics:...
Page 172: Sources Of Firmware Updates
You can also obtain Alpha firmware updates from the Internet. 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/pub/DEC/...
Page 173: Firmware Update Utility
Firmware Update Utility The system firmware is updated from a Loadable Firmware Update Utility. When you boot the medium containing the update image, the Loadable Firmware Update Utility banner is displayed. Before updating the firmware, enter the list command to list the current revision of the firmware.
Page 174 UPD> update Confirm update on: Abios [Y/(N)]y WARNING: updates may take several minutes to complete for each device. DO NOT ABORT! Abios Updating to V5.70... Verifying V5.70... PASSED. Updating to V5.6-102.. Verifying V5.6-102. PASSED. UPD> exit ES40 Owner’s Guide...
Page 175: Manual Updates
Manual Updates If RMC firmware or serial ROM (SROM) ever 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 ES40 Console V5.6-102, built on Dec 6, 1999 at 05:02:30...
Page 176: Updating From The Cd-Rom
Updating from the CD-ROM You can update the system firmware from CD-ROM. 6.4.1 Updating from the SRM Console 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 177: Updating From An Openvms System Disk
Updating from an OpenVMS System Disk You can update the firmware from an OpenVMS system disk. 1. Download the firmware update image from the Firmware Updates Web site. 2. Rename the downloaded file to fwupdate.exe. 3. Enter the following commands on the OpenVMS Alpha system: $ set file/attr=(rfm:fix,lrl:512,mrs:512,rat:none) fwupdate.exe $ copy/contiguous fwupdate.exe "system_disk":[sys0.sysexe]...
Page 178: Updating From The Network
Updating from the Network You can update firmware from the network using the MOP protocol for OpenVMS or the BOOTP protocol for Tru64 UNIX. 6.6.1 Updating Firmware Using BOOTP 1. Download the firmware update image from the Firmware Updates Web site. 2.
Page 179: Updating Firmware Using Mop
6.6.2 Updating Firmware Using MOP 1. Download the firmware update image from the Firmware Updates Web site. 2. Copy the downloaded file to an OpenVMS based network server for MOP booting on the system. For details on configuring the MOP server, refer to OpenVMS documentation or the system’s Firmware Release Notes document.
Page 180: Updating Firmware In A Galaxy Environment
Updating Firmware in a Galaxy Environment Before updating the console firmware in an OpenVMS Galaxy environment you must set the lp_count environment variable to zero and initialize the system to return to a traditional SMP configuration. P00>>> set lp_count 0 P00>>>...
Page 181: 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: Power-Up Error Messages RMC Error Messages...
Page 182: 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 183: 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 184: Checksum Error
7.1.2 Checksum Error If Jump to Console is the last message displayed on the operator control panel, 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. Example 7–1 Checksum Error and Fail-Safe Load Loading console Console ROM checksum error...
Page 185 ***** Loadable Firmware Update Utility ***** ------------------------------------------------------------- Function Description ------------------------------------------------------------- Display Displays the system’s configuration table. Exit Done exit LFU (reset). List Lists the device, revision, firmware name, and update revision. Readme Lists important release information. Update Replaces current firmware with loadable data image.
Page 186: 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 187 Indicates failed DIMMs. M identifies the MMB; D identifies the DIMM. In this line, DIMM 2 on MMB1 failed. Indicates that some DIMMs in this array are not the same. All DIMMs in the affected array are marked as incompatible (incmpat). Indicates that a DIMM in this array is missing.
Page 188: 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 189 Table 7–2 RMC Error Messages (Continued) Message Meaning Warning Messages PSn failed Power supply failed. “n” is 0, 1, or 2. OverTemp Warning System temperature is near the high threshold. Fann failed Fan failed. “n” is 0 through 6. PCI door opened Cover to PCI card cage is off.
Page 190: 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 191 Table 7–3 SROM Error Messages (Continued) Code SROM Message OCP Message Configuration error on CPU #2 CfgERR 2 Configuration error on CPU #1 CfgERR 1 Configuration error on CPU #0 CfgERR 0 Bcache failed on CPU #3 error BC Bad 3 Bcache failed on CPU #2 error BC Bad 2 Bcache failed on CPU #1 error...
Page 192: 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 193: 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–3 Show Device Command P00>>> show device dka0.0.0.1.1 DKA0 RZ2DD-LS 0306...
Page 194: Test Command
7.4.3 Test Command The test command verifies all the devices in the system. Example 7–4 Test Command 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 No MU* Tapes available for testing...
Page 195 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 196: 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 7.4.5) to determine if any FRUs have errors logged. Example 7–5 Show Fru Command P00>>>...
Page 197 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 198: Bit Assignments For Error Field
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 199: Show Error Command
7.4.5 Show Error Command The show error command displays FRUs that have errors logged. If the devices installed do not have any errors in their EEPROM, a show error command redisplays the SRM console prompt. Example 7–6 shows errors logged in the system board's EEPROM. Contact your service provider if the show error command displays an error.
Page 200: Show Power Command
7.4.6 Show Power Command Use the SRM show power command to determine whether the failure of a system running 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.
Page 201 Power supplies. Power supply 2 is not installed. System fans. Fan 3 is not working. Temperature sensors on CPUs. CPU 0 is above threshold. Temperature sensors on PCI backplane. Troubleshooting 7-21...
Page 202: 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–8 Crash Command P00>>> crash CPU 0 restarting DUMP: 19837638 blocks available for dumping.
Page 203 The SRM crash command forces a crash dump to the selected device. Use this command when the system has hung and you are able to halt it with the Halt button or the RMC halt in command. The crash command restarts the operating system and forces a crash dump to the selected device.
Page 204: 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 205: 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 206: 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 207: 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 and AlphaBIOS checksum error is reported...
Page 208: 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 209: 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 210: 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 211: Troubleshooting Pci Bus Problems
PCI Bus Problems PCI bus problems at startup are usually indicated by the inability of the system to detect the PCI device. Use Table 7–10 to diagnose the likely cause of the problem. Table 7–10 Troubleshooting PCI Bus Problems Step Action Check the cabling and confirm that the PCI card is correctly seated.
Page 213: Chapter 8 Specifications
Chapter 8 Specifications This chapter gives specifications for ES40 systems: Physical specifications Environmental specifications Electrical specifications Regulatory approvals Acoustic data Specifications...
Page 214: 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 78.7 cm (31.0 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 215: 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 80.6 cm (31.75 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 216: 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 76.5 cm (30.1 in.) Weight 1. When lifting Nominal: 50 kg (110 lb) Max: 76 kg (167.2 lb) 2.
Page 217: 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 218: 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 20 to 80% Nonoperating...
Page 219: Electrical Specifications
Electrical Specifications Table 8–6 Electrical Characteristics — All System Variants Nominal voltage (Vac) 200–240 Voltage range (Vac) 90–110 110–128 180–250 temporary condition) Power source phase Single Single Single Nominal frequency (Hz) 50/60 50/60 50/60 Frequency range (Hz) 49–51/59–61 49–51/59–61 49–51/59–61 RMS current (max.
Page 220: Regulatory Approvals
Table 8–6 Electrical Characteristics — All System Variants (Cont.) System Variant Power Cords Quantity Length Type Tower Up to 3 190 cm (75 in.) IEC 320 C13 to NEMA 5–15 (N. America) or IEC 320 C13 to country-specific Pedestal 190 cm (75 in.) 120 V nonremovable NEMA 5–15 (N.
Page 221: Acoustic Data
Product Idle Operate Idle Operate DH–64AAA-AA (AlphaStation ES40) [with 0 x HDD] DH–64AAA–AA + DS–RZ2ED–16 DH–64AAA–AA + DS-RZ2ED–16 + BA36R–R* + 6 x DS-RZ1ED–VW Current values for specific configurations are available from Compaq representatives. 1 B = 10 dBA. Specifications...
Page 223: Index
Index Acoustics, 8-9 alphabios command, 2-11 Checksum error, 7-4 AlphaBIOS console, 2-11 COM1 data flow, defining, 4-15 running in serial mode, 2-31 COM1 environment variables, 4-12 AlphaBIOS utilities, 2-27 com1_mode environment variable, 4-4 APB program, 3-21 Command conventions, RMC, 4-14 Auto start, 2-25 Components auto_action environment variable, 2-25...
Page 224 Fan failure, 7-25 Firm bypass mode, 4-8 Device naming, SRM, 2-21 Firmware Diagnostic tests, 7-14 updating, 6-1 Diagnostics, 7-2 updating from OpenVMS system Dial-in configuration, 4-22 disk, 6-7 Dial-out alert, 4-24 updating from SRM, 6-6 DIMMs updating using BOOTP, 6-8 configuring, 5-23 updating using MOP, 6-9 installing, 5-26...
Page 225 customized message, 2-13 start-up messages, 2-3 Key mapping, AlphaBIOS, 2-31 Option card problems, 7-30 LEDs Pagers, 4-25 control panel, 1-8 PCI bus problems, 7-31 power supply, 1-15 PCI cards, installing, 5-34 LFU, 6-3, 7-5 PCI parity errors, 7-30 Linux PCI slot locations booting, 3-16 pedestal, 5-31 Local mode, 4-5...
Page 226 Regulatory approvals, 8-8 troubleshooting, 4-30 Remote power-on/off, 4-20 RMC firmware, updating, 6-5 Removable media, 1-16 Removable media device, installing, 5- SCSI bus length, 5-45 Removing enclosure panels, 5-2 SCSI expansion, 5-45 from a pedestal, 5-5 Security, for SRM console, 2-24 from a tower, 5-3 Serial mode, setting up, 2-30 Reset button, 1-9...
Page 227 SRM environment variables, setting, 2- PCI bus problems, 7-31 PCI parity errors, 7-30 SROM power problems, 7-25 error messages, 7-11 problems getting to console mode, 7- power-up display, 2-4, 2-5 power-up messages, 2-3 problems reported by console, 7-27 status command (RMC), 4-16 RMC, 4-30 Storage system diagnostics, 7-2...

This manual is also suitable for:

Alphaserver es40 Alphastation es40

Compaq DH-64BAA-AA - AlphaServer - ES40 Owner's Manual

Preface

Chapter 1 System Overview

Chapter 2 Operation

Chapter 3 Booting and Installing an Operating System

Chapter 4 Using the Remote Management Console

Chapter 5 Configuring and Installing Components

Chapter 6 Updating Firmware

Chapter 7 Troubleshooting

Chapter 8 Specifications

Index

Quick Links

Troubleshooting

Related Manuals for Compaq DH-64BAA-AA - AlphaServer - ES40

Summary of Contents for Compaq DH-64BAA-AA - AlphaServer - ES40