AlphaServer ES40 Owner’s Guide Order Number: EK–ES240–UG. A01 This guide is intended for managers and operators of AlphaServer ES40 systems.
First Printing, April 1999 The information in this publication is subject to change without notice. COMPAQ COMPUTER CORPORATION SHALL NOT BE LIABLE FOR TECHNICAL OR EDITORIAL ERRORS OR OMISSIONS CONTAINED HEREIN, NOR FOR INCIDENTAL OR CONSEQUENTIAL DAMAGES RESULTING FROM THE FURNISHING, PERFORMANCE, OR USE OF THIS MATERIAL.
Attention! Ceci est un produit de Classe A. Dans un environnement domestique, ce produit risque de créer des interférences radioélectriques, il appartiendra alors à l'utilisateur de prendre les mesures spécifiques appropriées. FCC Notice: This equipment generates, uses, and may emit radio frequency energy.
Contents Preface Chapter 1 1.1 1.2 1.3 1.4 1.5 1.6 1.7 1.8 1.9 1.10 1.11 1.12 System Overview 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 Chapter 2 2.1 2.2 2.3 2.4 2.5 2.6 2.7 2.8 2.9 2.10 2.
Chapter 3 3.1 3.2 3.3 3.4 3.5 3.6 3.7 3.8 Chapter 4 4.1 4.2 4.3 4.4 4.5 4.6 4.7 4.8 vi 3-2 3-8 3-12 3-14 3-18 3-20 3-22 3-24 Using the Remote Management Console RMC Overview Operating Modes Terminal Setup Entering the RMC SRM Environment Variables for COM1 RMC Command-Line Interface Resetting the RMC to Factory Defaults Troubleshooting Tips Chapter 5 5.1 5.2 5.3 5.4 5.5 5.6 5.7 5.8 5.9 5.10 5.11 5.12 5.13 5.14 5.15 5.
Chapter 6 6.1 6.2 6.3 6.4 6.5 6.6 6.7 Chapter 7 7.1 7.2 7.3 7.4 7.5 7.6 7.7 6-2 6-4 6-6 6-7 6-9 6-10 6-12 Troubleshooting Power-Up Error Messages RMC Error Messages SROM Error Messages SRM Diagnostics Troubleshooting Tables Option Card Problems Troubleshooting the Windows NT Hard Disk Chapter 8 8.1 8.2 8.3 8.4 8.
2–2 2–3 2–4 2–5 2–6 2–7 2–8 3–1 3–2 4–1 4–2 4–3 4–4 5–1 5–2 5–3 5–4 5–5 5–6 5–7 5–8 5–9 5–10 5–11 5–12 5–13 5–14 5–15 5–16 5–17 5–18 5–19 6–1 AlphaBIOS Setup Screen Display System Configuration Screen CMOS Setup Screen Hard Disk Setup Screen Advanced CMOS Setup Screen AlphaBIOS Utilities Menu Run Maintenance Program Dialog Box AlphaBIOS Boot Screen Installing Windows NT Data Flow in Through Mode Data Flow in Bypass Mode Setup for RMC (Tower View) RMC Jumpers (Default Positions) Enclosure Panel Removal (Tow
4–1 4–2 4–3 7–1 7–2 7–3 7–4 7–5 7–6 7–7 7–8 7–9 7–10 7–11 8–1 8–2 8–3 8–4 8–5 8–6 8–7 8–8 Status Command Fields Elements of Dial String and Alert String RMC Troubleshooting Error Beep Codes RMC Error Messages SROM Error Messages Bit Assignments for Error Field Power Problems Problems Getting to Console Mode Problems Reported by the Console Boot Problems Errors Reported by the Operating System Troubleshooting PCI Bus Problems Troubleshooting the System Hard Disk Physical Characteristics — Tower Physical Cha
6–1 7–1 7–2 7–3 7–4 7–5 7–6 7–7 7–8 x Update Utility Display Checksum Error and Fail-Safe Load Sample Console Event Log Show Device Command Test Command Show Fru Command Show Error Command Show Power Command Crash Command 6-4 7-4 7-12 7-13 7-14 7-16 7-19 7-20 7-22
Preface Intended Audience This manual is for system managers and operators of Compaq AlphaServer 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. The facing page contains descriptions, procedures, and syntax definitions. This manual has eight chapters.
Documentation Titles Table 1 Compaq AlphaServer ES40 Documentation Title Order Number User Documentation Kit Owner’s Guide User Interface Guide Tower and Pedestal Basic Installation Release Notes Documentation CD (6 languages) QZ-01BAA-GZ EK-ES240-UG EK-ES240-UI EK-ES240-PD EK-ES240-RN AG-RF9HA-BE Maintenance Kit Service Guide Service Guide HTML Diskette Illustrated Parts Breakdown QZ-01BAB-GZ EK-ES240-SV AK-RFXDA-CA EK-ES240-IP Loose Piece Items Rackmount Installation Guide Rackmount Installation Tem
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 of the system.
1.1 System Enclosures The Compaq AlphaServer ES40 family consists of a standalone tower, a pedestal with expanded storage capacity, and a rackmount system.
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 21264 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 • Two half-height or one full-height removable media bays • Up to two storage disk cages that house up to four 1.
1.
1.
1.
Rear Panel Connections ➊ Modem port—Dedicated 9-pin port for modem connection to remote management console. ➋ ➌ ➍ ➎ COM2 serial port—Extra port to modem or any serial device. ➏ ➐ ➑ ➒ USB ports. ➓ PCI slot for VGA controller, if installed. Keyboard port—To PS/2-compatible keyboard. Mouse port—To PS/2-compatible mouse. COM1 MMJ-type serial port/terminal port—For connecting a console terminal. Parallel port—To parallel device such as a printer. SCSI breakouts.
1.5 Operator Control Panel The control panel provides system controls and status indicators. The controls are the Power, Halt, and Reset buttons. A 16-character backlit alphanumeric display indicates system state. The panel has two LEDs: a green Power OK indicator and an amber Halt indicator. Figure 1–5 Operator Control Panel 1 2 3 4 5 6 PK0204 ➊ Control panel display. A one-line, 16-character alphanumeric display that indicates system status during power-up and testing.
➌ Power LED (green). Lights when the power button is pressed. ➍ Reset button. A momentary contact switch that restarts the system and reinitializes the console firmware. Power-up messages are displayed, and then the console prompt is displayed or the operating system boot messages are displayed, depending on how the startup sequence has been defined. ➎ Halt LED (amber). Lights when you press the Halt button. ➏ Halt button. Halts the system.
1.6 System Board The system board is located on the floor of the system card cage. It has slots for the CPUs and memory motherboards (MMBs). The system board has the majority of the logic for the system. It holds the CPU cards and MMBs. Figure 1–6 shows the location of these modules on the system board.
CPU Card The system can have up to four CPU cards. The CPU cards are installed on the system board. Each CPU card contains a 21264 microprocessor, the thirdgeneration implementation of the Alpha architecture. The 21264 microprocessor is a superscalar CPU with out-of-order execution and speculative execution to maximize speed and performance. It contains four integer execution units and dedicated execution units for floating-point add, multiply, and divide.
1.7 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.
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.
1.8 Power Supplies The power supplies provide power to components in the system chassis. The number of power supplies required depends on the system configuration.
One to three power supplies provide power to components in the system chassis. The system supports redundant power configurations to ensure continued system operation if a power supply fails. 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). Power Supply LEDs Each power supply has two green LEDs that indicate the state of power to the system.
1.9 Removable Media Storage The system chassis houses a CD-ROM drive ➊ and a high-density 3.5inch floppy diskette drive ➋ and supports two additional 5.25-inch halfheight 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. See Chapter 5 for information on installing a removable media drive.
1.10 Hard Disk Storage The system chassis can have either one or 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.
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.
Both the tower and pedestal systems have a small front door through which the control panel and removable media devices are accessible. At the time of delivery, the system keys are taped inside this door. The tower front door has a lock that lets you secure access to the disk drives and to the rest of the system. The pedestal has two front doors, both of which can be locked. The upper door secures the disk drives and access to the rest of the system, and the lower door secures the expanded storage.
1.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.
Chapter 2 Operation This chapter gives basic operating instructions, including powering up and configuring the machine.
2.1 Powering Up the System To power up the system, press the power button. Testing begins, and status shows on the console terminal screen and in the control panel display.
2.2 Power-Up Displays Power-up information is displayed on the operator control panel and on the console terminal startup screen. Messages sent from the SROM (serial read-only memory) program are displayed first, followed by messages from the SRM console. NOTE: The power-up text that is displayed on the screen depends on what kind of terminal is connected as the console terminal: VT or VGA.
2.2.1 SROM Power-Up Display Example 2–1 Sample SROM Power-Up Display SROM Power-Up Display SROM V1.00 CPU #00 @ 0500 SROM program starting Reloading SROM OCP Message MHz SROM T1.
➊ When the system powers up, the SROM code is loaded into the I-cache (instruction cache) on the first available CPU, which becomes the primary CPU. The order of precedence is CPU0, CPU1, and so on. The primary CPU attempts to access the PCI bus. If it cannot, either a hang or a failure occurs, and this is the only message displayed. ➋ The primary CPU interrogates the I C EEROM on the system board and CPU modules through shared RAM. The primary CPU determines the CPU and system configuration to jump to.
2.2.2 SRM Console Power-Up Display At the completion of SROM power-up, the primary CPU transfers control to the SRM console program. 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.50-0, Tru64 UNIX PALcode V1.
➊ 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. ➋ The memory size is determined and memory is tested.
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 2.00 ns (500MHz) create powerup entering idle loop starting console on CPU 2 initialized idle PCB initializing idle process PID lowering IPL CPU 2 speed is 2.00 ns (500MHz) create powerup starting console on CPU 3 initialized idle PCB initializing idle process PID lowering IPL CPU 3 speed is 2.
➎ The console is started on the secondary CPUs. The example shows a fourprocessor system. ➏ Various diagnostics are performed. ➐ Systems running UNIX or OpenVMS display the SRM console banner and the prompt, Pnn>>>. The number n indicates the primary processor. In a multiprocessor system, the prompt could be P00>>>, P01>>>, P02>>>, or P03>>>. From the SRM prompt, you can boot the UNIX or OpenVMS operating system.
2.2.3 AlphaBIOS Startup Screens If the system is running the Windows NT operating system, the SRM console loads and starts the AlphaBIOS console. An initialization screen similar to Example 2–3 is displayed on the VGA monitor. Once AlphaBIOS initialization is complete, an AlphaBIOS boot screen similar to Example 2–4 is displayed. Example 2–3 AlphaBIOS Initialization Screen AlphaBIOS 5.
Example 2–4 AlphaBIOS Boot Screen AlphaBIOS 5.68 Please select the operating system to start: Windows NT Server 4.00 Use and to move the highlight to your choice. Press Enter to choose.
2.3 System Consoles System console programs are located in a flash ROM (read-only memory) on the system board. From the console interface, you can set up and boot the operating system, display the system configuration, and perform other tasks. For complete information on the SRM and AlphaBIOS consoles, see the Compaq AlphaServer ES40 User Interface Guide. Figure 2–2 AlphaBIOS Setup Screen AlphaBIOS Setup Display System Configuration... AlphaBIOS Upgrade... Hard Disk Setup... CMOS Setup... Network Setup..
SRM Console Systems running the Tru64 UNIX or OpenVMS operating systems are 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 the system. For example, to verify that the system sees the bootable devices that are attached, enter: P00>>> show device AlphaBIOS Console Systems running the Windows NT operating system are configured from the AlphaBIOS console, a menu interface.
2.3.1 Switching Between Consoles Under some circumstances, you may need to switch between the system consoles. For example, RAID devices are configured from the AlphaBIOS console. • To enter the SRM console from Windows NT, press the Reset button, then press the Halt button. You can also enter SRM by changing the Console Selection option on the AlphaBIOS Advanced CMOS Setup screen. See the Compaq AlphaServer ES40 User Interface Guide for details.
2.3.2 Selecting the Console and Display Device The SRM os_type environment variable determines which user interface (SRM or AlphaBIOS) is the final console loaded on a power-up or reset. The SRM console environment variable determines to which display device (VT-type terminal or VGA monitor) the console display is sent. Selecting the Console The os_type variable selects the console. Os_type is factory configured as follows: • For Windows NT, os_type is set to nt.
You can verify the display device with the SRM show console command and change the display device with the SRM set console command. If you change the display device setting, you must reset the system (with the Reset button or the init command) to put the new setting into effect. In the following example, the user displays the current console device (a graphics device) and then resets it to a serial device. After the system initializes, output will be displayed on the serial terminal.
2.3.3 Setting the Control Panel Message If you are running Tru64 UNIX or OpenVMS, you can create a customized message to be displayed on the operator control panel after startup self-tests and diagnostics have been completed. When the operating system is running, the control panel displays the console revision. It is useful to create a customized message if you have a number of systems and you want to identify each system by a node name.
2.4 Displaying a Tru64 UNIX or OpenVMS Configuration View the system hardware configuration for UNIX and OpenVMS systems from the SRM console. View a Windows NT hardware configuration from the AlphaBIOS console. It is useful to view the hardware configuration to ensure that the system recognizes all devices, memory configuration, and network connections. Use the following SRM console commands to view the system configuration for UNIX or OpenVMS systems.
2.4.1 Displaying Boot Environment Variables Use the show boot* command to list the boot environment variables. Example 2–6 Show Boot* P00>>> show boot* boot_dev boot_file boot_osflags boot_reset bootdef_dev booted_dev booted_file booted_osflags dka0.0.0.1.1 a OFF dka0.0.0.1.
2.4.2 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–7 Show Config P00>>> show config Compaq Computer Corporation Compaq AlphaServer ES40 ➊ Firmware SRM Console: ARC Console: PALcode: Serial Rom: RMC Rom: RMC Flash Rom: V5.4-5528 5.68 OpenVMS PALcode V1.50-0, Tru64 UNIX PALcode V1.47-5 V1.5-F V1.0 V1.
➊ 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.
Example 2–7 Show Config (Continued) Slot 2/0 2/1 4 7 15 Option NCR 53C896 NCR 53C896 DEC PowerStorm Acer Labs M1543C Acer Labs M1543C IDE 19 Acer Labs M1543C USB Option Floppy Slot Option 1 NCR 53C895 Hose 0, Bus 0, PCI ➎ pke0.7.0.2.0 SCSI Bus ID 7 pkf0.7.0.102.0 SCSI Bus ID 7 Bridge to Bus 1, ISA dqa.0.0.15.0 dqb.0.1.15.0 dqa0.0.0.15.0 TOSHIBA CD-ROM XM-6302B Hose 0, Bus 1, ISA dva0.0.0.1000.0 3 NCR 53C810 4 6 DE500-BA Network Con DECchip 21152-AA Hose 1, Bus 0, PCI pka0.7.0.1.
➎ PCI bus information. The “Slot” column lists the logical slots seen by the system. These 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. Two controllers reside on the same chip. They are shown as 2/0 and 2/1. The first number is the logical slot, and the second is the function.
Table 2–1 Correspondence Between Logical and Physical PCI Slots Physical Slot Logical Slot PCI 0 1 2 3 4 1 2 3 4 Device Device Device Device Physical Slot Logical Slot PCI 1 5 6 7 8 9 10 1 2 3 4 5 6 Device Device Device Device Device Device NOTE: PCI 0 and PCI 1 correspond to Hose 0 and Hose 1 in the logical configuration.
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–8 Show Device P00>>> show device dka0.0.0.1.1 dka100.1.0.1.1 dka200.2.0.1.1 dkb0.0.0.3.1 dqa0.0.0.15.0 dva0.0.0.1000.0 ewa0.0.0.4.1 ewb0.0.0.2002.1 pka0.7.0.1.1 pkb0.7.0.3.1 pkc0.7.0.2000.1 pkd0.7.0.2001.
2.4.4 Viewing Memory Configuration Use the show memory command to view the configuration of main memory. Example 2–9 Show Memory P00>>> show memory Array Size --------- ---------0 256Mb 1 512Mb 2 256Mb 3 1024Mb Base Address ---------------0000000060000000 0000000040000000 0000000070000000 0000000000000000 2048 MB of System Memory The show memory display corresponds to the memory array configuration described in Chapter 5. The display does not indicate the number of DIMMs or their size.
2.5 Setting SRM Environment Variables You may need to set several SRM console environment variables and built-in utilities to configure systems running the Tru64 UNIX or OpenVMS operating systems. 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.
2.6 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.
2.7 Displaying a Windows NT Hardware Configuration View a Windows NT configuration from AlphaBIOS. 1. From the AlphaBIOS Setup screen, select Display System Configuration and press Enter. 2. In the Display System Configuration screen, use the arrow keys to select the configuration category you want.
2.8 Setting Up a System for Windows NT Before you boot Windows NT, set the system date and time and set up the hard disks. Optionally, you can set the level of memory testing and set up system password protection. If you are installing Windows NT from CD-ROM, use the AlphaBIOS CMOS Setup screen and the Hard Disk Setup screen to set up your system. Use the Advanced CMOS Setup screen to set the level of memory testing and to set password protection, if desired.
2.8.1 Setting the Date and Time Set the date and time from the CMOS Setup screen. Figure 2–4 CMOS Setup Screen CMOS Setup Date: Time: Friday, 13:22:27 May 10 F1=Help 1999 Floppy Drive A: 3.5" 1.44 MB Floppy Drive B: None Keyboard: U.S. 101-key keyboard Auto Start: Enabled Auto Start Count: 30 Seconds Press or to modify date fields. take effect immediately. F3=Color F6=Advanced F7=Defaults Date modifications will ESC=Discard Changes F10=Save Changes PK0901 1. Start AlphaBIOS. 2.
2.8.2 Setting Up the Hard Disk Set up the hard disk from the Hard Disk Setup screen. Figure 2–5 Hard Disk Setup Screen Hard Disk Setup Disk Disk Disk 0 1 2 NCRC8xx #0, SCSI ID 0 Partition 1 7 Partition 2 4091 MB 4085 MB 5 6 MB FAT FAT NCRC8XX #0, SCSI ID 1 Partition 1 4091 MB 4091 MB NTFS NCRC8XX #0, SCSI ID 2 Partition 1 4091 MB 4091 MB NTFS INSERT =New DEL=Delete F6 =Format F7 =Express ESC=Exit PK0940a Set the date and time as described in Section 2.8.
2.8.3 Setting the Level of Memory Testing Set the level of memory testing that occurs when the system is power cycled from the advanced CMOS Setup screen. Figure 2–6 Advanced CMOS Setup Screen Advanced CMOS Setup F1=Help PCI Parity Checking: Power-up Memory Test: AlphaBIOS Password Option: SCSI BIOS Emulation: Disabled Partial Disabled Enabled For All Console Selection: Windows NT Console (AlphaBIOS) Press or to enable or disable power-up memory testing.
2.8.4 Setting Password Protection Password protection provides two levels of security for your Windows NT system: setup protection and startup protection. When system setup protection is enabled, a password is required to start AlphaBIOS Setup. When startup password protection is enabled, a password is required before the system initializes.
2.9 Setting Automatic Booting Windows NT systems are factory set to auto start; UNIX and OpenVMS systems are factory set to halt in the SRM console. You can change these defaults, if desired.
2.9.1 Windows NT and Auto Start On Windows NT systems the Auto Start option is enabled by default, which causes the operating system to start automatically whenever the machine is power cycled or reset. If you have more than one version of Windows NT installed (for example, Version 4.0 and Version 5.0), the version you select as the primary operating system starts automatically if Auto Start is enabled.
2.9.2 Setting Tru64 UNIX or OpenVMS Systems to Auto Start The SRM auto_action environment variable determines the default action the system takes when the system is power cycled, reset, or experiences a failure. On systems that are factory configured for UNIX or OpenVMS, the factory setting for auto_action is halt. The halt setting causes the system to stop in the SRM console. You must then boot the operating system manually. For maximum system availability, auto_action can be set to boot or restart.
2.10 Changing the Default Boot Device It is not necessary to modify the boot file setting for Windows NT. You can change the default boot device for UNIX or OpenVMS with the set bootdef_dev command. Windows NT AlphaBIOS boots Windows NT from the operating system loader program, OSLOADER.EXE. A boot file setting is created along with the operating system selection during Windows NT setup, and this setting is usually not modified by the user. You can, however, modify this setting, if necessary.
2.11 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 KZPSA configuration utility for configuring SCSI adapters These utilities are run from the AlphaBIOS console Utilities can be run either in graphics or serial mode.
2.11.1 Running Utilities from a VGA Monitor If you are running Windows NT, no terminal setup is required for running utilities. Figure 2–7 AlphaBIOS Utilities Menu AlphaBIOS Setup Display System Configuration... Upgrade AlphaBIOS Hard Disk Setup... CMOS Setup... Install Windows NT Utilities About AlphaBIOS... F1=Help Display Error Frames... OS Selection Setup... Run Maintenance Program... ESC=Exit PK0954a Running a Utility from a VGA Monitor 1. Start the AlphaBIOS console. 2.
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. 5. Press Enter to execute the program. Figure 2–8 Run Maintenance Program Dialog Box AlphaBIOS Setup Display System Configuration... Upgrade AlphaBIOS Hard Disk Setup... CMOS S Run Maintenance Program Networ Instal Utilit 1 Program Name: ra200rcu.
2.11.2 Setting Up Serial Mode Serial mode requires a VT320 or higher (or equivalent) terminal. To run AlphaBIOS and maintenance programs 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. From the General menu, set the terminal mode to VTxxx mode, 8-bit controls. 2. From the Comm menu, set the character format to 8 bit, no parity, and set receive XOFF to 128 or greater.
2.11.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.
1. Issue the alphabios command at the P00>>> prompt 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. 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. 5.
Chapter 3 Booting and Installing an Operating System This chapter gives instructions for booting the Tru64 UNIX, OpenVMS, or Windows NT 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.
3.1 Setting Boot Options for UNIX or OpenVMS You can set a default boot device, boot flags, and network boot protocols for UNIX or OpenVMS 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.
The syntax is: set bootdef_dev boot_device boot_device The name of the device on which the system software has been loaded. To specify more than one device, separate the names with commas. Example In this example, two boot devices are specified. The system will try booting from dkb0 and, if unsuccessful, will boot from dka0.
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. To change the boot flags for the current boot only, use the flags_value argument with the boot command. The syntax is: set boot_osflags flags_value The flags_value argument is specific to the operating system.
OpenVMS Systems OpenVMS systems require an ordered pair as the flags_value argument: root_number and boot_flags. root_number Directory number of the system disk on which OpenVMS files are located. For example: boot_flags root_number Root Directory 0 (default) [SYS0.SYSEXE] 1 [SYS1.SYSEXE] 2 [SYS2.SYSEXE] 3 [SYS3.SYSEXE] The hexadecimal value of the bit number or numbers set. To specify multiple boot flags, add the flag values (logical OR).
Example In the following UNIX example, the boot flags are set to autoboot the system to multiuser mode when you enter the boot command. P00>>> set boot_osflags a 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.
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. Replace the asterisk (*) with the adapter ID letter when entering the command.
3.2 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>>> sho dev dka0.0.0.1.1 dka100.1.0.1.1 dka200.2.0.1.1 dka300.3.0.1.1 dkc0.0.0.1.0 dkc100.1.0.1.0 dkc200.2.0.1.0 dkc300.3.0.1.0 dqa0.0.0.15.0 dva0.0.0.1000.0 ewa0.0.0.4.1 pka0.7.0.1.
Loading vmunix symbol table ... [1333528 bytes] sysconfigtab: attribute Per-proc-address-space not in subsystem proc Alpha boot: available memory from 0x134c000 to 0x1ffee000 Tru64 UNIX V4.0F-4 (Rev. 1180); Tue Feb 2 13:00:04 EST 1999 physical memory = 512.00 megabytes. available memory = 492.64 megabytes. using 1958 buffers containing 15.29 megabytes of memory Master cpu at slot 0. Firmware revision: 5.4-5160 PALcode: Tru64 UNIX version 1.45-5 Compaq AlphaServer ES40 . . . Tru64 UNIX Version V4.
3.2.1 Booting UNIX over the Network To boot your 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. Example 3–2 RIS Boot P00>>> show device dka0.0.0.1.1 DKA0 dka100.1.0.1.1 DKA100 dka200.2.0.1.1 DKA200 dkb0.0.0.3.1 DKB0 dqa0.0.0.15.0 DQA0 dva0.0.0.1000.0 DVA0 ewa0.0.0.4.1 EWA0 ewb0.0.0.2002.1 EWB0 pka0.7.0.1.1 PKA0 pkb0.7.0.3.
Systems running Tru64 UNIX support network adapters, designated ew*0 or ei*0. The asterisk stands for the adapter ID (a, b, c, and so on). 1. Power up the system. The system stops at the SRM console prompt, P00>>>. 2. Set boot environment variables, if desired. See Section 3.1. 3. Enter the show device command ➊ to determine the unit number of the drive for your device. 4. Enter the following commands. Example 3–2 assumes you are booting from ewa0.
3.3 Starting a Tru64 UNIX Installation UNIX is installed from the CD-ROM drive connected to the system. The display that you see after you boot the CD depends on whether your system console is a VGA monitor or a serial terminal. Example 3–3 Text-Based Installation Display P00>>> b dqa0 (boot dqa0.0.0.15.0 -flags a block 0 of dqa0.0.0.15.0 is a valid boot block reading 16 blocks from dqa0.0.0.15.
There are two types of installations: o The Default Installation installs a mandatory set of software subsets on a predetermined file system layout. o The Custom Installation installs a mandatory set of software subsets plus optional software subsets that you select. You can customize the file system layout. The UNIX Shell option puts your system in single-user mode with superuser privileges.
3.4 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–4 Booting OpenVMS from the Local CD-ROM Drive P00>>> show device ➊ dka0.0.0.1.1 DKA0 RZ2CA-LA dka100.1.0.1.1 DKA100 RZ2CA-LA dqa0.0.0.15.0 DQA0 TOSHIBA CD-ROM XM-6302B dva0.0.0.1000.0 DVA0 ewa0.0.0.6.1 EWA0 00-00-F8-10-D6-03 pka0.7.0.1.1 PKA0 SCSI Bus ID 7 P00>>> . . . ➋ P00>>> boot -flags 0,0 dka0 (boot dka0.0.0.1.
Example 3–4 shows a boot from a CD-ROM on a local drive. The example is abbreviated. For complete instructions on booting OpenVMS, see the OpenVMS installation document. 1. Power up the system. The system stops at the SRM console prompt, P00>>>. 2. Set boot environment variables, if desired. See Section 3.1. 3. Install the boot medium. For a network boot, see Section 3.4.1. 4. Enter the show device command ➊ to determine the unit number of the drive for your device. 5.
3.4.1 Booting OpenVMS from the InfoServer You can boot OpenVMS from a LAN device on the InfoServer. The devices are designated EW*0 or EI*0. The asterisk stands for the adapter ID (a, b, c, and so on). Example 3–5 InfoServer Boot P00>>> show device ➊ dka0.0.0.1.1 DKA0 RZ2CA-LA dka100.1.0.1.1 DKA100 RZ2CA-LA dqa0.0.0.15.0 DQA0 TOSHIBA CD-ROM XM-6302B dva0.0.0.1000.0 DVA0 ewa0.0.0.6.1 EWA0 00-00-F8-10-D6-03 pka0.7.0.1.1 PKA0 SCSI Bus ID 7 P00>>> . . .
Network Initial System Load Function Version 1.2 ➌ FUNCTION FUNCTION ID 1 Display Menu 2 Help 3 Choose Service 4 Select Options 5 Stop Enter a function ID value: Enter a function ID Value: 3 OPTION OPTION ID 1 Find Services 2 Enter known Service Name ➍ Enter an Option ID value: 2 Enter a Known Service Name: ALPHA_V71-2_SSB OpenVMS (TM) Alpha Operating System, Version V7.1-2 1. Power up the system. The system stops at the P00>>> console prompt. 2.
3.5 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–6 OpenVMS Installation Menu OpenVMS (TM) Alpha Operating System, Version V7.1-2 Copyright © 1999 Digital Equipment Corporation. All rights reserved. Installing required known files... Configuring devices...
1. Boot the OpenVMS operating system CD-ROM. 2. Choose option 1 (Install or upgrade OpenVMS Alpha). To create the system disk, see the OpenVMS installation document.
3.6 Booting Windows NT Microsoft Windows NT is started from the AlphaBIOS boot screen. Figure 3–1 AlphaBIOS Boot Screen AlphaBIOS 5.68 Please select the operating system to start: Windows NT Server 4.00 Use and to move the highlight to your choice. Press Enter to choose.
Before You Can Boot Windows NT • The AlphaBIOS console must be running. Windows NT systems are factory configured to start AlphaBIOS after the system has been fully initialized. • The SRM console environment variable must be set to graphics. This is the factory setting for systems with Windows NT. Preboot Tasks 1. Before you boot Windows NT, set the system date and time and set up the hard disks, as described in Chapter 2. 2. Perform other setup tasks, as described in Chapter 2.
3.7 Starting a Windows NT Installation Windows NT is installed from CD-ROM. Insert the CD-ROM in the drive connected to the system, start AlphaBIOS Setup, select the menu item Install Windows NT, and follow the prompts. Figure 3–2 Installing Windows NT AlphaBIOS Setup Display System Configuration... AlphaBIOS Upgrade... Hard Disk Setup... CMOS Setup... Network Setup... Install Windows NT Utilities About AlphaBIOS... Press ENTER to install or upgrade Windows NT from CD-ROM.
If this is a new Windows NT installation, set the system date and time and set up the hard disk as described in Chapter 2. Then install the operating system as follows: 1. Insert the Windows NT CD into the CD-ROM drive connected to the system. 2. Start AlphaBIOS Setup. 3. Select Install Windows NT and press Enter. 4. Follow the prompts to complete the installation. For more information on installing Windows NT, refer to the installation guide in your Windows NT software package.
3.8 Switching Between Operating Systems The system supports three operating systems. You UNIX, OpenVMS, or Windows NT. You can also operating system to another by removing the disk system that is currently installed and installing operating system you want to run. can install Tru64 switch from one for the operating the disk for the WARNING: To prevent injury, access is limited to persons who have appropriate technical training and experience.
3.8.1 Switching from UNIX or OpenVMS to Windows NT Follow this procedure if you have already installed UNIX or OpenVMS and want to switch to Windows NT. 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. 1. Shut down the operating system and power off the system. Unplug the power cord from each power supply.
3.8.2 Switching from Windows NT to UNIX or OpenVMS Follow this procedure if you have already installed Windows NT and want to switch to UNIX or OpenVMS. 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. 1. Shut down the operating system and power off the system. Unplug the power cord from each power supply.
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. This chapter explains the operation and use of the RMC.
4.1 RMC Overview The remote management console provides a mechanism for monitoring the system (voltages, temperatures, and fans) and manipulating it on a low level (reset, power on/off, halt). The RMC performs monitoring and control functions to ensure the successful operation of the system.
The RMC logic is implemented using an 8-bit microprocessor, PIC17C44, as the primary control device. The firmware code resides on the microprocessor and in flash memory. If the RMC firmware should ever become corrupted or obsolete, you can update it manually using a Loadable Firmware Update Utility. See Chapter 6 for details. The microprocessor can also communicate with the system power control logic to turn on or turn off power to the rest of the system. The RMC is powered by an auxiliary 5V supply.
4.2 Operating Modes The RMC can be configured to manage different data flow paths defined by the com1_mode environment variable. In through mode (the default), all data and control signals flow from the system COM1 port through the RMC to the active external port. You can also set bypass modes so that the signals partially or completely bypass the RMC. The com1_mode environment variable can be set from either SRM or the RMC. See Section 4.6.1.
Through Mode Through mode is the default operating mode. The RMC routes every character of data between the internal system COM1 port and the active external port, either the local COM1 serial port (MMJ) or the 9-pin modem port. If a modem is connected, the data goes to the modem. The RMC filters the data for a specific escape sequence. If it detects the escape sequence, it enters the RMC CLI. Figure 4–1 illustrates the data flow in through mode.
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. The bypass modes are snoop, soft bypass, and firm bypass.
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. Snoop Mode In snoop mode data partially bypasses the RMC.
After downloading binary files, you can set the com1_mode environment variable from the SRM console to switch back to snoop mode or other modes for accessing the RMC, or you can hang up the current modem session and reconnect it. Firm Bypass Mode In firm bypass mode all data and control signals are routed directly between the system COM1 port and the external modem port. The RMC does not configure or monitor the modem.
4.3 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) ➋.
4.4 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. • You can enter the RMC from the modem if the RMC is in through mode, snoop mode, or local mode.
Entering from the Local VGA Monitor To enter the RMC from the local VGA monitor, the console environment variable must be set to graphics. Invoke the SRM console and enter the rmc command. P00>>> rmc You are about to connect to the Remote Management Console. Use the RMC reset command or press the front panel reset button to disconnect and to reload the SRM console. Do you really want to continue? [y/(n)] y Please enter the escape sequence to connect to the Remote Management Console.
4.5 SRM Environment Variables for COM1 Several SRM environment variables allow you to set up the COM1 serial port (MMJ) for use with the RMC. You may need to set the following environment variables from the SRM console, depending on how you decide to set up the RMC. com1_baud Sets the baud rate of the COM1 serial port and the modem port. The default is 9600. com1_flow Specifies the flow control on the serial port. The default is software.
4.6 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} deposit disable {alert, remote} dump enable {alert, remote} env halt {in, out} hangup help or ? power {on, off} quit reset send alert set {alert, com1_mode, dial, escape, init, logout, password, user} status NOTE: The deposit and dump commands are reserved for service providers.
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. For example, you can enter disable a for disable alert. • For commands that have parameters, you are prompted for the parameter.
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: through All data passes through RMC and is filtered for the escape sequence. This is the default. snoop Data partially bypasses RMC, but RMC taps into the data lines and listens passively for the escape sequence. soft_bypass Data bypasses RMC, but RMC switches automatically into snoop mode if loss of carrier occurs.
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: V1.
Table 4–1 Status Command Fields Field Meaning On-Chip Firmware Revision: Revision of RMC firmware on the microcontroller. Flash Firmware Revision: Revision of RMC firmware in flash ROM. Server Power: ON = System is on. OFF = System is off. System Halt: Asserted = System has been halted. Deasserted = Halt has been released. RMC Power Control: ON= System has powered on from RMC. OFF = System has powered off from RMC. Escape Sequence: Current escape sequence for access to RMC console.
4.6.3 Displaying the System Environment The RMC env environment. command provides a snapshot of the system RMC> env System Hardware Monitor Temperature (warnings at 45.0°C, power-off at 50.0°C) CPU0: 26.0°C Zone0: 29.0°C Fan RPM Fan1: 2295 Fan4: 2235 CPU1: 26.0°C Zone1: 30.0°C Fan2: 2295 Fan5: OFF CPU2: 27.0°C CPU3: 26.0°C Zone2: 31.
➊ ➋ CPU temperature. In this example four CPUs are present. ➌ Fan RPM. With the exception of Fan 5, all fans are powered as long as the system is powered on. Fan 5 is OFF unless Fan 6 fails. ➍ The normal power supply status is either OK (system is powered on) or OFF (system is powered off or the power supply cord is not plugged in). FAIL indicates a problem with a supply. ➎ CPU CORE voltage and CPU I/O voltage.
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. The Power button on the OCP, however, has precedence. • If the system has been powered off with the Power button, the RMC cannot power the system on.
Halt In and Halt Out The halt in command halts the system. The halt out command releases the halt. When you issue either the halt in or halt out command, the terminal exits RMC and reconnects to the server’s COM1 port. RMC> halt Returning RMC> halt Returning in to COM port out to COM port The halt out command cannot release the halt if the Halt button is latched in. If you enter the halt out command, the message “Halt button is IN” is displayed, indicating that the command will have no effect.
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.
➊ Sets the password that is prompted for at the beginning of a modem session. The string cannot exceed 14 characters and is not case sensitive. For security, the password is not echoed on the screen. When prompted for verification, type the password again. ➋ Sets the initialization string. The string is limited to 31 characters and can be modified depending on the type of modem used.
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. You must configure remote dial-in for the dial-out feature to be enabled. See Section 4.6.5. To set up the dial-out alert feature, enter the RMC from the local serial terminal or local VGA monitor.
The elements of the dial string and alert string are shown in Table 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. The dial string must include the appropriate modem commands to dial the number. ➋ Sets the alert string, typically the phone number of the modem connected to the remote system.
Table 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). Enter this character if the dial-out line modifies its dial tone when used for services such as voice mail. D = Dial T = Tone (for touch-tone) 9, The number for an outside line (in this example, 9).
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. Use the status command to verify the new escape sequence before exiting the RMC. The following example consists of two instances of the Esc key and the letters “FUN.
4.7 Resetting the RMC to Factory Defaults If the non-default RMC escape sequence has been lost or forgotten, RMC must be reset to factory settings to restore the default escape sequence. WARNING: To prevent injury, access is limited to persons who have appropriate technical training and experience. Such persons are expected to understand the hazards of working within this equipment and take measures to minimize danger to themselves or others. The following procedure restores the default settings: 1.
Figure 4–4 RMC Jumpers (Default Positions) 1 2 3 1 2 J24 J25 J3 J2 J1 J26 J31 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. 9. Install jumper J25 over pins 2 and 3. 10. Reinstall CPU1, the card cage cover and fan cover and the enclosure panels. 11. Plug the power cord into each of the power supplies.
4.8 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 RMC from the modem. The RMC may be in soft bypass or firm bypass mode. Issue the show com1_mode command from SRM and change the setting if necessary. If in soft bypass mode, you can disconnect the modem session and reconnect it. The terminal cannot communicate with the RMC correctly.
Table 4–3 RMC Troubleshooting (Continued) Symptom Possible Cause Suggested Solution RMC will not answer when modem is called. (continued from previous page) On AC power-up, RMC defers initializing the modem for 30 seconds to allow the modem to complete its internal diagnostics and initializations. Wait 30 seconds after powering up the system and RMC before attempting to dial in. After the system is powered up, the COM1 port seems to hang or you seem to be unable to execute RMC commands.
Chapter 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.
5.1 Removing Enclosure Panels Open and remove the front door. Loosen the screws that allow you to remove the top and side panels.
To Remove Enclosure Panels from a Tower The enclosure panels are secured by captive screws. 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. To remove the left panel, loosen the screw ➋ at the top and the screw ➌ at the bottom. Slide the panel back and then tip it outward. Lift it off the system. 4. Go to Section 5.2 for instructions on removing covers from the system chassis.
Figure 5–2 Enclosure Panel Removal (Pedestal) 1 2 PK0234 5-4 Compaq AlphaServer ES40 Owner’s Guide
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. To remove the right enclosure panel, loosen the captive screw shown in ➋. Slide the panel back and then tip it outward. Lift the panel from the three tabs. 4. Go to Section 5.2 for instructions on removing covers from the system chassis.
5.2 Removing Covers from the System Chassis WARNING: To prevent injury, access is limited to persons who have appropriate technical training and experience. Such persons are expected to understand the hazards of working within this equipment and take measures to minimize danger to themselves or others. V @ >240VA WARNING: High current area. Currents exceeding 240 VA can cause burns or eye injury. Avoid contact with parts or remove power prior to access.
Figure 5–3 Removing Covers from a Tower 5 2 1 2 1 3 4 2 PK0216 Configuring and Installing Components 5-7
Figure 5–4 Removing Covers from a Pedestal/Rack 4 1 2 3 5 5-8 Compaq AlphaServer ES40 Owner’s Guide PK0215
5.3 Hot-Plug Components Power supplies and hard drives are hot-plug components. You can install these components without interrupting the operation of the system. WARNING: To prevent injury, access is limited to persons who have appropriate technical training and experience. Such persons are expected to understand the hazards of working within this equipment and take measures to minimize danger to themselves or others. These measures include the following: 1.
5.4 Power Supply Configuration You can add a power supply for redundancy at any time.
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. Redundant Power Supply. If one power supply fails, the redundant supply provides power and the system continues to operate normally.
5.
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 ➌. If you are replacing a power supply, release the latch ➎ on the supply and pull the supply out of the system. 3. Insert and seat the new power supply ➍. 4. Swing the latch ➎ to lock the power supply into place. Tighten the captive screw on the latch. 5.
5.6 Installing a Hard Drive You can install a hard drive while the system is running.
1. Unlock the front door to access the storage drive area. 2. Remove a blank bezel for the next available slot. 3. Release the plastic handle on the front of the drive carrier. Align the drive in the slot and push it into place. Push in the handle to secure the drive. Verification — SRM Console The SRM console polls for SCSI devices every 30 seconds. If the device does not appear to be working, access the SRM console and enter the show device command to view a list of the bootable devices.
5.7 Non-Hot-Plug Components CPUs, memory DIMMs, PCI cards, and removable media devices are not hot-plug components. You must shut down the operating system, turn off power to the system, and unplug the power cord from each supply before installing these components. WARNING: To prevent injury, unplug the power cord from each power supply before installing components.
Follow the procedure below before installing CPUs, memory DIMMs, PCI cards, or removable media devices: 1. Shut down the operating system according to the instructions in the operating system documentation. 2. Shut down power on all external options connected to the system. 3. Shut down power to the system. 4. Unplug the power cord from each power supply. 5. Become familiar with the location of the module slots and any configuration rules.
5.8 CPU Configuration Before installing additional CPUs, become familiar with the location of the CPU slots and the configuration rules.
Figure 5–9 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. CPU cards must be installed in numerical order, starting at CPU slot 0. The slots are populated from left to right on a pedestal or rackmount system and from bottom to top on a tower system. See Figure 5–8 and Figure 5–9. 3. CPUs must be identical in speed and cache size.
5.9 Installing CPUs Figure 5–10 CPU Card Installation (Pedestal/Rack View) 3 1 2 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.
WARNING: CPU cards have parts that operate at high temperatures. Wait 2 minutes after power is removed before touching any module. V @ >240VA WARNING: High current area. Currents exceeding 240 VA can cause burns or eye injury. Avoid contact with parts or remove power prior to access. WARNING: To prevent injury, unplug the power cord from each power supply before installing components. 1. Shut down the operating system and turn off power to the system. Unplug the power cord from each power supply. 2.
Verification — SRM Console 1. Turn on power to the system. 5. During power-up, observe the screen display. The newly installed CPU should appear in the display. 6. Issue the show config command to display the status of the new CPU. Verification — alphabios Console 1. Start AlphaBIOS Setup, select Display System Configuration, and press Enter. 2. Using the arrow keys, select Systemboard Configuration and check the Processor field to determine how many processors are present.
5.10 Memory Configuration Become familiar with the rules for memory configuration before adding DIMMs to the system. 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 set consists of 4 DIMMs. You must install all 4 DIMMs. • Fill sets in numerical order. Populate all 4 slots in Set 0, then populate Set 1, and so on.
Figure 5–11 Memory Configuration (Pedestal/Rack View) Sets 7 7 5 5 3 3 1 1 Sets 6 6 4 4 2 2 0 0 MMB 2 Sets 7 7 5 5 3 3 1 1 MMB 0 Array 1 Sets 1 & 5 Array 3 Sets 3 & 7 Array 0 Sets 0 & 4 MMB 3 Sets 6 6 4 4 2 2 0 0 Array 2 Sets 2 & 6 MMB 1 PK0202 5-24 Compaq AlphaServer ES40 Owner’s Guide
Figure 5–12 Memory Configuration (Tower View) Sets 6 6 4 4 2 2 0 0 MMB 1 7 Sets 3 3 5 5 7 1 1 MMB 3 6 0 Sets 2 2 4 4 6 0 MMB 0 7 Sets 3 3 5 5 7 MMB 2 1 1 Array 1 Sets 1 & 5 Array 0 Sets 0 & 4 Array 3 Sets 3 & 7 Array 2 Sets 2 & 6 PK0203 Configuring and Installing Components 5-25
5.
WARNING: To prevent injury, access is limited to persons who have appropriate technical training and experience. Such persons are expected to understand the hazards of working within this equipment and take measures to minimize danger to themselves or others. WARNING: Memory DIMMs 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.
7. To install the DIMM, align the notches on the gold fingers with the connector keys as shown in Figure 5–14.
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 — SRM Console 1. Turn on power to the system. 2. During power-up, observe the screen display for memory. The display shows how much memory is in each array. 3. Issue the show memory command to display the total amount of memory in the system. Verification — AlphaBIOS Console 1.
5.
Figure 5–16 PCI Slot Locations (Tower) 10-Slot System 1 2 3 4 5 6 7 8 9 10 6-Slot System 1 2 3 8 9 10 PK0227 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. The slots on each bus are listed below. System Variant Slots on PCI 0 Slots on PCI 1 Six-slot system 1–3 8–10 Ten-slot system 1–4 5–10 Some PCI options require drivers to be installed and configured.
5.13 Installing PCI Cards Figure 5–17 PCI Card Installation (Pedestal/Rack View) 3 1 2 PK0245 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 fire, use only modules with current limited outputs. See National Electrical Code NFPA 70 or Safety of Information Technology Equipment, Including Electrical Business Equipment EN 60 950. V @ >240VA WARNING: High current area. Currents exceeding 240 VA can cause burns or eye injury. Avoid contact with parts or remove power prior to access. WARNING: To prevent injury, unplug the power cord from each power supply before installing components.
Verification — SRM Console 1. Turn on power to the system. 2. During power-up, observe the screen display for PCI information. The new option should be listed in the display. 3. Issue the SRM show config command. Examine the PCI bus information in the display to make sure that the new option is listed. 4. If you installed a bootable device, enter the SRM show device command to determine the device name. For example, look for dq, dk, ew, and so on. Verification — AlphaBIOS Console 1.
5.14 Installing a Removable Media Device 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.
Figure 5–18 Installing a 5.
1. Shut down the operating system and turn off power to the system. Unplug the power cord from each power supply. 2. Remove the cover to the PCI card cage area. 3. Unplug the signal and power cables to the CD. 4. Remove and set aside the four screws ➊ securing the removable media cage. Remove the cage. CAUTION: Be careful not to tangle the wires to the CD-ROM and floppy. 5. Remove a blank storage panel ➋ for the desired storage slot by pushing from behind the panel.
5.
WARNING: To prevent injury, access is limited to persons who have appropriate technical training and experience. Such persons are expected to understand the hazards of working within this equipment and take measures to minimize danger to themselves or others. WARNING: To prevent injury, unplug the power cord from each power supply before installing components. 1. Remove the cover to the PCI card cage. 2. Install the SCSI controller ➊ in the PCI backplane. 3.
Verification — SRM Console 1. Turn on power to the system. 2. When the system powers up to the P00>>> prompt, enter the SRM show device command to determine the device name. For example, look for dq, dk, ew, and so on.
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. • Do not exceed the maximum number of devices supported on the SCSI controller to be used. • Each device on the bus must have a unique SCSI ID.
Chapter 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.
6.1 Sources of Firmware Updates The AlphaBIOS firmware for Windows NT and the SRM firmware for UNIX and OpenVMS reside in the flash ROM located on the system board. The Alpha Systems Firmware Update Kit comes on a CD-ROM, which is updated quarterly. 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.
AlphaBIOS Firmware The AlphaBIOS firmware is included on the Alpha Systems Firmware Update Kit CD-ROM. You can also obtain the latest version of the AlphaBIOS firmware from the World Wide Web. http://www.windows.digital.com/products/products.asp Click on the product name.
6.2 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. Enter the update command to update the SRM and AlphaBIOS firmware automatically.
UPD> update Confirm update on: Abios srm [Y/(N)]y WARNING: updates may take several minutes to complete for each device. Abios srm DO NOT ABORT! Updating to V5.6-9... Verifying V5.6-9... Updating to V5.4-7... Verifying V5.4-7... PASSED. PASSED.
6.3 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.4-5528, built on April 6, 1999 at 05:02:30 3. To update RMC firmware, enter update rmc. To update the serial ROM (SROM), enter update srom.
6.4 Updating from the CD-ROM You can update the system firmware from CD-ROM, either from the SRM console or the AlphaBIOS console. 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. Boot the system from the CD, using the drive name determined in step 1 (for example, dqa0). P00>>> boot dqa0 4. Enter the update command at the UPD> prompt. 5.
6.4.2 Updating from the AlphaBIOS Console 1. Insert the Alpha Systems Firmware Update CD into the CD-ROM drive. 2. Press F2 at the entry screen to start AlphaBIOS Setup. 3. Select AlphaBIOS Upgrade and press Enter. AlphaBIOS searches for the update file on disk, CD-ROM, and the network. When the update is found, the image is updated. 4. Once the update is complete, the system restarts with the updated AlphaBIOS. AlphaBIOS Setup Display System Configuration... AlphaBIOS Upgrade...
6.5 Updating from an OpenVMS System Disk You can update OpenVMS from a system disk. 1. Download the firmware update image from the Firmware Updates Web site. 2. Rename the downloaded file to fwupdate.exe. 3. Enter the following commands on the OpenVMS Alpha system: $ set file/attr=(rfm:fix,lrl:512,mrs:512,rat:none) fwupdate.exe $ copy/contiguous fwupdate.exe "system_disk":[sys0.sysexe] NOTE: Insert the name of your system disk in place of "system_disk," for example, dka100:. 4.
6.6 OpenVMS and UNIX Network Boots You can update OpenVMS using the MOP network protocol. You can update Tru64 UNIX with the BOOTP protocol. 6.6.1 Updating UNIX Using the BOOTP Protocol 1. Download the firmware update image from the Firmware Updates Web site. 2. Copy the downloaded file to a UNIX based network server for BOOTP booting on the AlphaServer system. For details on configuring the BOOTP server, refer to UNIX documentation or the system’s Firmware Release Notes document. 3.
6.6.2 Updating OpenVMS Using the MOP Protocol 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 AlphaServer system. For details on configuring the MOP server, refer to OpenVMS documentation or the system’s Firmware Release Notes document. 3.
6.7 Upgrading AlphaBIOS over the Network You can upgrade AlphaBIOS over the network if you have set up an AlphaBIOS server and AlphaBIOS client and if you have configured the Network Setup screen. See the Compaq AlphaServer ES40 User Interface Guide for information on the network setup feature. Figure 6–1 AlphaBIOS Upgrade Screens Upgrade AlphaBIOS Old Version: 5.68 New Version: 5.69 WARNING: This will take several seconds.
Requirements To upgrade AlphaBIOS over a network, you must meet the following requirements: • A DHCP and TFTP server or a BOOTP and TFTP server configured with the appropriate client information. • An AlphaBIOS-based client with: À À À A network adapter from the DEC DC21x4 family of Ethernet adapters 16 MB of RAM The Network Setup screen configured based on the AlphaBIOS server’s settings. Network Upgrade Procedure 1.
Chapter 7 Troubleshooting This chapter describes procedures for resolving problems with the system. To correct a problem, locate the troubleshooting table for that problem type and follow the guidelines provided. If you cannot correct the problem, report it to your service provider.
7.1 Power-Up Error Messages Three sets of diagnostics are performed at power-up: RMC, SROM, and SRM. As the diagnostics run, messages are displayed on the control panel. Some messages are also displayed on the console terminal. Error messages that are displayed can be used to diagnose problems. 7.1.1 Messages with Beep Codes Table 7–1 Error Beep Codes Beep Code Associated Messages 1 Jump to Console 1-3 Meaning SROM code has completed execution. System jumps to SRM console.
A few error messages that appear on the operator control panel are announced by audible error beep codes, an indicated in Table 7–1. For example, a 1-1-4 beep code consists of one beep, a pause (indicated by the hyphen), one beep, a pause, and a burst of four beeps. This beep code is accompanied by the message “ROM err.” Related messages are also displayed on the console terminal if the console device is connected to the serial line and the SRM console environment variable is set to serial.
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 Expect: 00000000.000000FE Actual: 00000000.000000FF XORval: 00000000.
➏ ***** 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. Verify Compares loadable and hardware images.
7.1.3 No MEM Error If the SROM code cannot find any available memory, a 1-3-3 beep code is issued (one beep, a pause, a burst of three beeps, a pause, and another burst of three beeps), and the message “No MEM” is displayed. The system does not come up to the console program. This error indicates missing or bad DIMMs.
➊ 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. All missing DIMMs in the affected array are marked as missing. ➍ Indicates that the DIMM data for this array is unreadable. All unreadable DIMMs in the affected array are marked as illegal.
7.2 RMC Error Messages Table 7–2 lists the error messages that might be displayed on the operator control panel by the remote management console during power-up. Most fatal error messages prevent the system from completing its power-up. Contact your service provider if a fatal error is displayed. Warning messages require prompt attention but may not prevent the system from completing its power-up. Table 7–2 RMC Error Messages Message Meaning Fatal Messages AC loss No AC power to the system.
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. Reinstall cover. Fan door opened Cover to main fan area (fans 5 and 6) is off. Reinstall cover. 3.3V bulk warn Power supply voltage over or under threshold. 5V bulk warn Power supply voltage over or under threshold.
7.3 SROM Error Messages The SROM power-up identifies errors that may or may not prevent the system from coming up to the console. It is possible that these errors may prevent the system from successfully booting the operating system. Errors encountered during SROM power-up are displayed on the operator control panel (OCP). Some errors are also displayed on the console terminal if the console output is set to serial. Table 7–3 lists the SROM error messages. Contact your service provider.
Table 7–3 SROM Error Messages (Continued) Code SROM Message OCP Message 7E 7D 7C 7B 7A 79 78 77 76 75 74 73 Configuration error on CPU #2 Configuration error on CPU #1 Configuration error on CPU #0 Bcache failed on CPU #3 error Bcache failed on CPU #2 error Bcache failed on CPU #1 error Bcache failed on CPU #0 error Memory thrash error on CPU #3 Memory thrash error on CPU #2 Memory thrash error on CPU #1 Memory thrash error on CPU #0 Starting secondary on CPU #3 error CfgERR 2 CfgERR 1 CfgERR 0 BC Bad
7.4 SRM Diagnostics The SRM console event log and SRM console commands help you troubleshoot problems that do not prevent the system from coming up to the console. 7.4.1 Console Event Log A console event log consists of status messages received during powerup self-tests. If problems occur during power-up, error messages indicated by asterisks (***) may be embedded in the console event log. To display a console event log one screen at a time, use the more el command.
7.4.2 Show Device Command Use the SRM show device command to list the controllers and bootable devices in the system. If storage devices are missing from the display, see Table 7–7. Example 7–3 Show Device Command P00>>> show device dka0.0.0.1.1 dka100.1.0.1.1 dka200.2.0.1.1 dkb0.0.0.3.1 dqa0.0.0.15.0 dva0.0.0.1000.0 ewa0.0.0.4.1 ewb0.0.0.2002.1 pka0.7.0.1.1 pkb0.7.0.3.1 pkc0.7.0.2000.1 pkd0.7.0.2001.
7.4.3 Test Command The test command verifies all the devices in the system. This command can be used on all supported operating systems.
• A trial diskette with files installed • A trial CD-ROM with files installed The test script tests devices in the following order: 1. Memory tests (one pass) 2. Read-only tests: DK* disks, DR* disks, DQ* disks, DU* disks, MK* tapes, DV* floppy. 3. Console loopback tests if -lb argument is specified: COM2 serial port and parallel port. 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.
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>>> show fru FRUname SMB0 SMB0.CPU0 SMB0.CPU1 SMB0.CPU2 SMB0.CPU3 SMB0.MMB0 SMB0.MMB0.DIM1 SMB0.MMB0.DIM2 SMB0.MMB0.DIM3 SMB0.MMB0.DIM4 SMB0.MMB0.DIM5 SMB0.MMB0.DIM6 SMB0.MMB1 SMB0.MMB1.DIM1 SMB0.MMB1.
PWR0 PWR1 FAN1 FAN2 FAN3 FAN4 FAN5 FAN6 JIO0 OCP0 00 00 00 00 00 00 00 00 00 00 30-49448-01.A02 30-49448-01.A02 70-40073-01 70-40073-01 70-40072-01 70-40071-01 70-40073-02 70-40074-01 54-25575-01 70-33894-0x 2P90700557 API-7850 2P90700558 API-7850 Fan Fan Fan Fan Fan Fan Junk I/O OCP P00>>> ➊ FRUname The FRU name recognized by the SRM console. The name also indicates the location of that FRU in the physical hierarchy.
Table 7–4 Bit Assignments for Error Field Bit Meaning Bit 0 is 1 Failure Bit 1 is 1 TDD error has been logged Bit 2 is 1 At least one SDD error has been logged Bit 3 is 1 FRU EEPROM is unreadable Bit 4 is 1 Checksum failure on bytes 0-62 Bit 5 is 1 Checksum failure on bytes 64-126 Bit 6 is 1 Checksum failure on bytes 128-254 Bit 7 is 1 FRU’s system serial does not match system’s NOTE: Contact your service provider if the E (error) field shows any of these errors.
7.4.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.
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. Otherwise, invoke RMC and use the env command.
➊ ➋ ➌ ➍ 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.
7.4.7 Crash Command For fatal errors, the UNIX and OpenVMS 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. DUMP: 118178 wanted for a partial compressed dump. DUMP: Allowing 2060017 of the 2064113 available on 0x800001 device string for dump = SCSI 1 1 0 0 0 0 0. DUMP.
The SRM crash command forces a crash dump to the selected device for UNIX and OpenVMS systems. 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.
7.5 Troubleshooting Tables This section describes some strategies for troubleshooting problems that might prevent the system from completing its power-up or that might prevent you from booting the operating system. Use the troubleshooting tables on the following pages to diagnose the following types of problems.
Table 7–5 Power Problems Symptom Action System does not power on. Check that AC power is available and all power cords are plugged in. Check the Power setting on the control panel. Toggle the Power button to off, then back on to clear a remote power disable. Check error messages on the control panel. Check that the ambient room temperature is within environmental specifications (10–40°C, 50–104°F). Internal power supply cables might not be plugged in at the system board. Contact your service provider.
Table 7–6 Problems Getting to Console Mode Symptom Action Power-up screen is not displayed. Interpret the error beep codes and observe the control panel display at power-up for a failure detected during self-tests. Check keyboard and monitor connections. Press the Return key. If the system enters console mode, check that the console environment variable is set correctly. If you are using a VGA monitor as the console terminal, the console variable should be set to graphics.
Table 7–7 Problems Reported by the Console Symptom Action Power-up tests are not completed. Interpret the error beep codes at power-up and check the power-up screen for a failure detected during self-tests. The system attempts to boot from the floppy drive after a checksum error is reported (error beep code 1-1-4). The system automatically reverts to the failsafe loader to load new SRM and AlphaBIOS firmware.
Table 7–8 Boot Problems Symptom Action System cannot find boot device. Check the system configuration for the correct device parameters (node ID, device name, and so on). For UNIX and OpenVMS, use the show config and show device commands. For Windows NT, use the AlphaBIOS Display System Configuration menu and the CMOS Setup menus. Check the system configuration for the correct environment variable settings.
Table 7–9 Errors Reported by the Operating System Symptom Action System has crashed, but SRM console is operating. Press the Halt button and enter the SRM crash command to provide a crash dump file for analysis. (OpenVMS and UNIX only.) If the problem is intermittent, run the SRM test command. Refer to the OpenVMS Alpha System Dump Analyzer Utility Manual for information on how to interpret OpenVMS crash dump files. Refer to the Guide to Kernel Debugging for information on using the UNIX Krash Utility.
7.6 Option Card Problems Option card problems can include problems related to network options and PCI options. Network Problems Network problems can vary, depending on the type of network option card that you have installed. See the option card documentation for information on troubleshooting network problems. Make sure you have correctly set the network type for the network interface card.
PCI Bus Problems PCI bus problems at startup are usually indicated by the inability of the system to detect the PCI device. Use Table 7–10 to diagnose the likely cause of the problem. Table 7–10 Troubleshooting PCI Bus Problems Step Action 1 Check the cabling and confirm that the PCI card is correctly seated. 2 Run system console PCI diagnostics for devices on the Supported Options List. (If the device is not on the list, refer to the device’s documentation.
7.7 Troubleshooting the Windows NT Hard Disk Table 7–11 gives AlphaBIOS error messages that indicate hard disk problems and suggests possible causes and solutions. Table 7–11 Troubleshooting the System Hard Disk Error Message Possible Cause Corrective Action “Internal error occurred” Incompatible or failed disk cables. Try another cable known to be good. Disk controller not configured.
Table 7–11 Troubleshooting the System Hard Disk (Continued) Error Message Possible Cause Corrective Action “No hard drives were found connected to your computer” No hard disk installed. Install hard disk. Cable not connected to either the disk or controller. Check the cable connections to ensure that cable connectors are fully seated. Cable not connected to either the disk or controller. Check the cable connections to ensure that cable connectors are fully seated. No power to drive.
Chapter 8 Specifications This chapter gives specifications for Compaq AlphaServer ES40 systems: • Physical specifications • Environmental specifications • Electrical specifications • Regulatory approvals • Acoustical data Specifications 8-1
8.1 Physical Specifications Table 8–1 Physical Characteristics — Tower Dimensions Height Width Depth Weight 50.8 cm (20.0 in.) 38.7 cm (15.25 in.) 78.7 cm (31.0 in.) Nominal: 65 kg (143 lb) Max: 96 kg (211 lb) Shipping Container Height Width Depth Weight 82.4 cm (32.2 in.) 60.2 cm (24.0 in.) 101.6 cm (40.0 in.) Nominal: 78 kg (172 lb) Max: 110 kg (242 lb) Clearances Front Rear Left side Right side 8-2 Operating Service 75 cm (29.5 in.) 15 cm (6 in.) None None 75 cm (29.5 in.) 75 cm (29.5 in.
Table 8–2 Physical Characteristics — Pedestal Dimensions Height Width Depth Weight 78.2 cm (30.8 in.) 50.8 cm (20.0 in.) 80.6 cm (31.75 in.) Nominal: 127 kg (280 lb) Max: 159 kg (350 lb) Shipping Container Height Width Depth Weight 107.7 cm (42.4 in.) 100.3 cm (39.5 in.) 60.7 cm (23.9 in.) Nominal: 149 kg (328 lb) Max: 185 kg (407 lb) Clearances Front Rear Left side Right side Operating Service 75 cm (29.5 in.) 15 cm (6 in.) None None 75 cm (29.5 in.) 75 cm (29.5 in.) None 75 cm (29.5 in.
Table 8–3 Physical Characteristics — Rackmount Dimensions Height 35.2 cm (13.87 in.) Width 44.7 cm (17.6 in.) Depth Weight 1. When lifting 2. Total added to cabinet (includes brackets, slides, and cables) 76.5 cm (30.1 in.) Nominal: 50 kg (110 lb) Nominal: 59 kg (130 lb) Fits 14 in. [8U] standard RETMA cabinets Max: 76 kg (167.2 lb) Max: 92 kg (202.4 lb) Shipping Container Height Width Depth Weight 73.2 cm (28.8 in.) 60.7 cm (24.0 in.) 101.6 cm (40.0 in.
Table 8–4 Physical Characteristics — Cabinets Dimensions H9A10 M-Series Height Width Depth Weight 170 cm (67.0 in.) 60 cm (23.6 in.) 110 cm (43.27 in.) Configuration-dependent Max payload 1000 lb H9A15 M-Series Height Width Depth Weight 200 cm (79.0 in.) 60 cm (23.6 in.) 110 cm (43.27 in.) Configuration-dependent Max payload 1000 lb Shipping Container H9A10 M-Series Height Width Depth Weight 185.5 cm (73 in.) 91.5 cm (36 in.) 122 cm (48 in.
8.
8.3 Electrical Specifications Table 8–6 Electrical Characteristics — All System Variants Nominal voltage (Vac) Voltage range (Vac) temporary condition) Power source phase Nominal frequency (Hz) Frequency range (Hz) RMS current (max. steady state) Tower and Rackmount Single power cord Multiple power cords Pedestal Each power cord M-Series cab config.
8.4 Regulatory Approvals Table 8–7 Regulatory Approvals Agency approvals Reviewed to 8-8 rd UL: Listed to UL1950 (3 edition) and to CAN/CSA-C22.2 No. 950-M95 TUV: EN 60950/A4:1997 GS marked FCC: Part 15.
8.5 Acoustical Data Table 8–8 gives the noise declaration for the AlphaServer ES40 system. Table 8–8 Acoustical Data Acoustics — Declared Values per ISO 9296 and ISO 7779 LWAd, B LpAm, dBA (bystander positions) Product Idle Operate Idle Operate DH–64AAA-AA (AlphaServer ES40) [with 0 x HDD] DH–64AAA–AA + DS–RZ2ED–16 6.6 6.6 48 48 6.6 6.6 48 48 DH–64AAA–AA + DS-RZ2ED–16 + BA36R–R* + 6 x DS-RZ1ED–VW 6.7 6.
Index A Acoustics, 8-9 AlphaBIOS console boot screen, 2-11, 2-13, 3-20 CMOS Setup screen, 2-31 Display System Configuration screen, 2-30 hard disk setup, 2-33 memory test, 2-34 running in serial mode, 2-44 setting date and time, 2-32 setup screen, 2-12 startup screens, 2-10 AlphaBIOS initialization screen, 2-10 AlphaBIOS utilities, 2-40 APB program, 3-17 Auto start, 2-36 UNIX or OpenVMS, 2-38 Windows NT, 2-37 auto_action environment variable, 2-38 Autoboot, 2-36 Auxiliary power supply, RMC, 4-3 B Boot dev
Console tests, 7-15 Console, selecting, 2-15 Consoles, switching between, 2-14 Control panel, 1-8 Control panel messages, 2-3 Controls halt button, 1-9 power button, 1-8 reset button, 1-9 Covers removing from pedestal or rack, 5-8 removing from tower, 5-7 CPU card, 1-11 CPU slot locations, 5-18 CPUs configuring, 5-19 installing, 5-20 crash command (SRM), 7-22 Crash dump, 7-23 D Date and time, setting in AlphaBIOS, 2-32 Device naming, SRM, 2-26 Diagnostic tests, 7-14 Diagnostics, 7-2 Dial-in configuration,
Hardware configuration viewing, 2-18 Windows NT, 2-30 Hot-plug components, 5-9 I InfoServer, 3-17 Initialization screen, AlphaBIOS, 2-10 Installing a disk cage, 5-38 Installing CPUs, 5-20 Installing DIMMs, 5-26 Installing hard drives, 5-14, 5-15 Installing OpenVMS, 3-18, 3-19 Installing PCI cards, 5-32 Installing power supplies, 5-12 Installing UNIX, 3-12 Installing Windows NT, 3-22, 3-23 ISL boot program, 3-17 K Key mapping, AlphaBIOS, 2-44 L LEDs control panel, 1-8 power supply, 1-15 LFU, 6-4, 7-5 Loca
redundant, 5-11 Power supply LEDs, 1-15 Powering up, 2-2 Power-on, remote, 1-9 Power-on/off, from RMC, 4-20 Power-up display SRM, 2-6 SROM, 2-4, 2-5 Power-up displays, 2-3 Power-up memory failure, 2-5 Power-up memory test, AlphaBIOS, 2-34 Power-up procedure, 2-5 Preboot tasks, Windows NT, 3-21 Problems getting to console mode, 7-26 Problems reported by console, 7-27 Processor card, 1-11 Q quit command (RMC), 4-10 R Redundant power supply, 5-11 Regulatory approvals, 8-8 Remote power-on/off, 4-20 Removable
PCI, 5-30, 5-31 Snoop mode, 4-7 Soft bypass mode, 4-7 Specifications, 8-2 SRM console, 2-13 device naming, 2-26 power-up display, 2-6 security, 2-29 SRM console commands crash, 7-22 show boot*, 2-19 show config, 2-20 show device, 2-26 show error, 7-19 show fru, 7-16 show memory, 2-27 show power, 7-20 test, 7-14 SRM diagnostics, 7-12 SRM environment variables, setting, 2-28 SROM error messages, 7-11 power-up display, 2-4, 2-5 power-up messages, 2-3 Startup screens, AlphaBIOS, 2-10 status command (RMC), 4-16
