AlphaServer DS25 Owner’s Guide Order Number: EK-DS250-UG. D01 This manual is for managers and operators of HP AlphaServer DS25 systems.
April 2003 © 2002, 2003 Hewlett-Packard Company. Linux is a registered trademark of Linus Torvalds in several countries. UNIX is a trademark of The Open Group in the United States and other countries. All other product names mentioned herein may be trademarks of their respective companies. HP shall not be liable for technical or editorial errors or omissions contained herein. The information in this document is provided “as is” without warranty of any kind and is subject to change without notice.
• • • • Reorient or relocate the receiving antenna. Increase the separation between the equipment and receiver. Connect the equipment into an outlet on a circuit different from that to which the receiver is connected. Consult the dealer or an experienced radio or television technician for help.
Taiwanese Notice Japanese Notice Canadian Notice (Avis Canadien) Class A Equipment This Class A digital apparatus meets all requirements of the Canadian Interference-Causing Equipment Regulations. Cet appareil numérique de la classe A respecte toutes les exigences du Règlement sur le matériel brouilleur du Canada. Class B Equipment This Class B digital apparatus meets all requirements of the Canadian Interference-Causing Equipment Regulations.
Contents Preface ..................................................................................................................... xiii 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 Enclosures ................................................................................ 1-2 System Chassis—Front View/Top View................................................ 1-4 Rear Ports and Slots .............................................................................
2.6.1 2.6.2 2.6.3 2.6.4 2.7 2.7.1 2.7.2 2.7.3 2.7.4 2.7.5 Setting the Console Password............................................................. 2-23 Setting the Console to Secure Mode.................................................... 2-25 Turning Off Security During a Console Session ................................. 2-26 Returning to User Mode...................................................................... 2-28 Updating Firmware..................................................................
4.9.1 4.10 4.11 4.11.1 4.12 4.13 4.13.1 4.13.2 Ethernet Connection Status LEDs...................................................... 4-30 Disk Drive Configuration .................................................................... 4-31 Installing Disk Drives ......................................................................... 4-32 Drive Status LEDs........................................................................ 4-34 External SCSI Expansion .....................................................
5.21.4 5.21.5 5.21.6 5.21.7 5.21.8 5.21.9 5.21.10 5.21.11 5.21.12 eg*0_mode or ei*0_mode or ew*0_mode ....................................... 5-53 kbd_hardware_type ...................................................................... 5-55 language........................................................................................ 5-56 os_type .......................................................................................... 5-57 pci_parity .....................................................
7.11.2 7.11.3 7.11.4 Starting the FSB manually........................................................... 7-16 Required Firmware....................................................................... 7-18 Updating Firmware ...................................................................... 7-19 Chapter 8 Specifications 8.1 8.2 8.3 8.4 8.5 8.5.1 8.5.2 Physical Specifications.......................................................................... 8-2 Environmental Specifications ......................
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 5–20 5–21 5–22 5–23 5–24 6–1 6–2 7–1 Show Config ........................................................................................ 5-12 Show Device ........................................................................................ 5-15 Show Memory...................................................................................... 5-16 Show Power...................................................................
1–12 2–1 4–1 4–2 4–3 4–4 4–5 4–6 4–7 4–8 4–9 4–10 4–11 4–12 4–13 4–14 4–15 4–16 4–17 4–18 4–19 4–20 4–21 4–22 4–23 4–24 6–1 6–2 6–3 6–4 7–1 7–2 Console Terminal Connections............................................................ 1-20 Operator Control Panel......................................................................... 2-2 Pedestal Kit Contents ........................................................................... 4-3 Installing the Lower Panel.............................................
4–1 4–2 4–3 4–4 4–5 5–1 5–2 5–3 5–4 5–5 5–6 6–1 6–2 6–3 7–1 7–2 7–3 7–4 7–5 7–6 7–7 7–8 7–9 8–1 8–2 8–3 8–4 8–5 xii Pedestal Kit Contents ........................................................................... 4-4 DIMM and Array Reference................................................................ 4-16 Ethernet Status LEDs......................................................................... 4-33 SCSI ID Orientation............................................................................
Preface Intended Audience This manual is for HP AlphaServer DS25 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 HP AlphaServer DS25 Documentation Title Order Number User Documentation Kit QA–6WEAA–G8 Owner’s Guide EK–DS250–UG Documentation CD (6 languages) AG–RT2DA–BE Maintenance Kit Service Guide QA–6WEAB–G8 EK–DS250–SV Loose Piece Items Basic Installation Card EK–DS250–PD Rackmount Installation Guide EK–DS250–RG Rackmount Installation Template EK–DS250–TP AlphaServer DS25 in a 9000 Series Cabinet Installation Information EK–BA57R–IN Information on the Internet Visit th
Chapter 1 System Overview This chapter provides an overview of the system, including: • System Enclosures • System Chassis—Front View/Top View • System Chassis—Rear View • Rear Ports and Slots • Operator Control Panel • System Motherboard • PCI Slots • Power Supplies • Power Requirements • Removable Media Storage • Storage Subsystem • System Access (pedestal) • Console Terminal NOTE: See Chapter 4 for warnings and procedures for accessing internal parts of the system.
1.1 System Enclosures The DS25 family consists of a standalone 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 two CPUs (EV68 Alpha chip) • 200-pin memory DIMMs (up to 16 with a minimum of 4) • I/O (located on system motherboard) with six 64-bit PCI slots: Four hot-swap PCI slots with two at 66 MHz (3.3 V) and two at 33 MHz (5.0 V).
1.
X Y Z [ \ ] ^ _ Operator control panel CD-ROM read/write drive Hard disk drives Power supplies System motherboard Memory CPUs Speaker System Overview 1-5
1.
Rear Panel Connections n o p q r s t u ` a Parallel port Serial port (COM2) Serial port (COM1) Keyboard port Mouse port Ethernet A (10/100) Ethernet B (10/100/1000) SCSI breakout AC power outlets System fan 0 System fan 1 System Overview 1-7
1.4 Operator Control Panel The control panel provides system controls and status indicators. The controls are the Power, Halt, and Reset buttons. The panel has a green power LED, a yellow halt LED, and four diagnostic LEDs.
n o p q r s Power button. This button is a latching switch. Pressing the Power button on powers up the system. Pressing the button to standby turns off all DC volt ages except Aux 5 volts. The 5 volt standby powers the remote management console (RMC). See Chapter 6. Power LED (green). Lights when the Power button is pressed. Reset button. A latch contact switch that restarts the system and reinitializes the console firmware. Halt LED. Halt condition (yellow). Lights when you press the Halt button.
1.5 System Motherboard The system motherboard has the majority of the logic for the system. It is located on the floor of the system card cage in rack systems and is vertical and on the right side for the pedestal systems. The system motherboard has connectors for the CPUs and DIMMs Figure 1–5 shows these locations on the motherboard.
See Figure 1–5 for sections of the motherboard: X Y Z [ \ CPU slots (CPU 0 is right slot). I/O slots Memory slots IDE SCSI All components are on a single system motherboard that contains a memory subsystem, PCI bus, integrated dual Ultra3 SCSI controllers, and slots for PCI options. CPU Module The system can have up to two CPU modules. The CPU modules are installed on the system motherboard. Each module contains an Alpha EV68 microproc essor.
1.6 PCI Slots The system motherboard has six, 64-bit PCI slots. The callouts in Figure 1–6 show the PCI slot locations. In systems with part numbers Dx-57AAA-xx, slot 6 supports a half-length card only. In systems with part numbers Dx-57AAB-xx, slot 6 supports full-length cards. Slots 1 through 5 support full-length cards.
There is no direct correspondence between the physical numbers of the slots and the logical slot identification reported with the SRM console show config com mand (described in Chapter 2). Table 1–1 maps the physical slot numbers to the SRM logical ID numbers. See Chapter 4 for instructions on installing PCI options.
1.7 Power Supplies Depending on the system model and amount of memory, either two or three power supplies are required. Systems with two supplies can add a third power supply for redundancy.
A power backplane integrates the supplies for power distribution, monitoring, and control. The power supplies can be accessed and removed from the front of the enclosure. See Chapter 4 for instructions on adding or replacing a power supply. The following voltages are provided: +3.3, +5.0, +12.0, -12.0 Aux (+5.0 Aux al ways powered). Two internal fans for each power supply cool the power supply. The fans are temperature controlled and speed up as the power supply tempera ture increases.
1.8 Power Requirements The system automatically detects the voltage source when it powers up (auto-sensing from 100 V – 240 V) and adjusts the power supply input to accept that voltage. Figure 1–8 shows the maximum current ratings for a fully loaded system (without monitor or terminal). It also shows where to plug in the AC power cords. Power supply ratings and power cord requirements are in Chapter 8.
1.9 Removable Media Storage The system chassis houses a CD-ROM read/write drive n.
1.10 Storage Subsystem The system comes with a six-slot storage subsystem that holds 1-inch drives. You can install up to six 1-inch universal hard drives in the storage disk cage. See Chapter 4 for installation and swap procedures. Figure 1–10 Storage Cage MR0296A The storage system backplane contains on-board multimode terminators that provide LVD (low voltage differential) termination to the bus when all devices are LVD.
1.11 System Access (Pedestal) 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.
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. A VGA monitor requires a keyboard and mouse.
Chapter 2 Operation This chapter gives instructions for basic system operation.
2.1 Powering Up the System To power up the system, press the power button. Testing begins, and status shows on the console terminal screen and in the control panel display.
n o Z [ \ ] Power button Power LED (Green) Reset button Halt LED Halt button Diagnostic LEDs Operation 2-3
2.2 Power-Up Displays Power-up information is displayed on the operator control panel LEDs 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 RMC Power-Up Display Example 2–1 RMC Power-Up Display RMC RMC RMC RMC RMC RMC RMC - 2.2.2 System is Down Starting to Test Max Fan Speeds Power Supplies OK System DC is OK System is up System Fans OK Powerup Complete SROM Power-Up Display Example 2–2 Sample SROM Power-Up Display SROM V1.3-F CPU # 00 @ 1000 MHz SROM program starting Reloading SROM SROM V1.
2.2.3 SRM Console Power-Up Display At the completion of SROM power-up, the primary CPU transfers con trol to the SRM console program, described in Section 2.3. The console program continues the system initialization. Failures are reported to the console terminal through the power-up screen and a console event log. Example 2–3 SRM Power-Up Display OpenVMS PALcode V1.96-40, Tru64 UNIX PALcode V1.
Hose 3 - PCI bus running at 33Mhz probing hose 3, PCI starting drivers [ n 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 ter minal, 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.
Example 2–3 SRM Power-Up Display (Continued) \ starting console on CPU 1 initialized idle PCB initializing idle process PID lowering IPL CPU 1 speed is 1000 MHz create powerup initializing GCT/FRU at 23e000 Initializing ega dqa dqb eia pka pkb Memory Testing and Configuration Status Array Size Base Address --------- ---------- ---------------0 512Mb 0000000040000000 2 1024Mb 0000000000000000 ] Intlv Mode ---------1-Way 1-Way 1536 MB of System Memory Testing the System Testing the Disks (read only) Testi
r s t The console is started on the secondary CPU. The example shows a twoprocessor system. Various diagnostics are performed. The console terminal displays the SRM console banner and the prompt, Pnn>>>. The number n indicates the primary processor. In a multiproces sor system, the prompt could be P00>>> or P01>>>. From the SRM prompt, you can boot the operating system.
2.3 SRM Console The SRM console is the command-line interface that allows you to set up and boot the operating system, display the system configuration, set environment variables, and perform basic system troubleshooting. SRM firmware is located in a flash ROM (read-only memory) on the sys tem board. The SRM console firmware is described in detail in Chapter 5, Firmware. The following sections cover functions you can perform from the SRM console.
2.3.1 Selecting the Display Device The SRM console environment variable determines to which display device (VT-type terminal or VGA monitor) the console display is sent. The console terminal that displays the SRM user interface can be either a serial terminal (VT320 or higher, or equivalent) or a VGA monitor. The SRM console environment variable determines the display device. • If you use a VT-type device as the console terminal, set the console envi ronment variable to serial.
2.4 Displaying the Hardware Configuration View the system hardware configuration from the SRM console. It is useful to view the hardware configuration to ensure that the system recognizes all devices, memory configuration, and network connec tions. Use the following SRM console commands to view the system configuration: show boot* Displays the boot environment variables. show config Displays the logical configuration of interconnects and buses on the system and the devices found on them.
2.4.1 Displaying Boot Environment Variables Use the show boot* command to list the boot environment variables. Use the set command with a variable to set up the boot environment. See Chapter 3 for more information on setting boot environment vari ables. Example 2–5 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.
boot_dev Device or device list from which booting is to be at tempted, here SCSI device dka0. boot_file The default file name used for the primary bootstrap when no file name is specified by the boot command. boot_osflags Boot flags, here the Tru64 UNIX “a” (autoboot) flag. boot_reset Action taken in response to an error halt or boot com mand. OFF, the default, indicates a warm boot (no full reset is performed).
2.4.2 Displaying the Logical Hardware Configuration Use the show config command to display the logical configuration. To display the physical configuration, issue the show fru command. Example 2–6 Show Config P00>>> sho config hp AlphaServer DS25 X Firmware SRM Console: PALcode: Serial ROM: RMC ROM: RMC Flash ROM: V6.3-1 OpenVMS PALcode V1.96-40, Tru64 UNIX PALcode V1.90-31 V1.3-F G1.4 V1.1 Processors CPU 0 CPU 1 Alpha EV68CB pass 2.4 1000 MHz Alpha EV68CB pass 2.
1/1 5 Slot 1 6 P00>>> n o p q r Adaptec AIC-7899 BCOM Gigabit 5703c Option ELSA GLoria Synergy Yukon PCI Hot-Plug C dka100.1.0.1.2 pkb0.7.0.101.2 ega0.0.0.5.2 COMPAQ BF01863644 SCSI Bus ID 7 00-02-A5-20-7F-AC Hose 3, Bus 0, PCI - 66 MHz vga0.0.0.1.3 Firmware. Version numbers of the SRM console, PALcode, serial ROM, RMC ROM, and RMC flash ROM Processors. Processors present, processor version and clock speed, and amount of backup cache Core logic.
Table 2–1 How Physical I/O Slots Map to Logical Slots Physical Slot SRM Logical Slot ID 1 Hose 1 Slot ID 1 2 Hose 1 Slot ID 2 3 Hose 3 Slot ID 2 4 Hose 3 Slot ID 1 5 Hose 0 Slot ID 9 6 Hose 0 Slot ID 10 Operation 2-17
2.4.3 Displaying the Bootable Devices Use the show device command to display the devices from which the operating system can be booted. Example 2–7 Show Device P00>>> show device dqa0.0.0.16.0 dva0.0.1000.0* ega0.0.0.5.2 eia0.0.0.8.0 pka0.7.0.1.2 pkb0.7.0.101.2 DQA0 DVA0 EGA0 EIA0 PKA0 PKB0 P00>>> * DS25 systems have no floppy drive. 2-18 DS25 Owner’s Guide HL-DT-ST GCE-8302B 2.
Table 2–2 Device Naming Conventions Category Description The device, dqa0 is used as an example in the following device category and description. Two-letter designator of port or class driver dq Driver ID dk SCSI drive or CD ew Ethernet port dq IDE CD-ROM fw FDDI device dr RAID set device mk SCSI tape du DSSI disk mu DSSI tape dv Diskette drive pk SCSI port eg Ethernet port pu DSSI port pz KZPCC-CE RAID ei Ethernet port controller Storage adapter ID One-letter designator of storage adapter a (a, b, c…).
2.4.4 Viewing the Memory Configuration Use the show memory command to view the configuration of main memory. Example 2–8 Show Memory P00>>> show memory Array Size --------- ---------0 1024Mb Base Address ---------------0000000000000000 Intlv Mode ---------1-Way 1024 MB of System Memory P00>>> The show memory display corresponds to the memory array configuration de scribed in Chapter 4. The display does not indicate the number of DIMMs or the DIMM size.
2.5 Setting SRM Environment Variables You may need to set several SRM console environment variables and built-in utilities to configure the system. Set environment variables at the P00>>> prompt. • To check the setting for a specific environment variable, enter the show envar command, where the name of the environment variable is sub stituted for envar. To see a list of the environment variables, enter the show * command.
2.6 Setting Console Security You can set the SRM console to secure mode to prevent unauthorized persons from modifying the system parameters or otherwise tampering with the system from the console. When the SRM is set to secure mode, you can use only two console commands: • The boot command, to boot the operating system. • The continue command, to resume running the operating system if you have inadvertently halted the system.
2.6.1 Setting the Console Password Set the console password with the set password command. A password is required for operating the system in secure mode.
The set password command sets the console password for the first time or changes an existing password. It is necessary to set the password only if the system is going to operate in secure mode. The syntax is: set password n o p Setting a password. If a password has not been set and the set password command is issued, the console prompts for a password and verification. The password and verification are not echoed. Changing a password.
2.6.2 Setting the Console to Secure Mode To set the console to secure mode, first set the password. Then enter the set secure command. The system immediately enters secure mode. Example 2–10 Set Secure P00>>> set secure Console is secure. Please login. P00>>> b dkb0 Console is secure - parameters are not allowed. P00>>> login Please enter the password: P00>>> b dkb0 (boot dkb0.0.0.3.1) . . . n o The set secure command enables secure mode.
2.6.3 Turning Off Security During a Console Session The login command turns off the security features, enabling access to all SRM console commands during the current console session. The sys tem automatically returns to secure mode as soon as the boot or con tinue command is entered or when the system is reset. Example 2–11 Login P00>>> Secure P00>>> Please Please P00>>> Please P00>>> n o p login not set. Please set the password.
When you enter the login command, you are prompted for the current system password. If a password has not been set, a message is displayed indicating that there is no password in NVRAM. If a password has been set, this prompt is dis played: Please enter the password: If the password entered matches the password in NVRAM, when the prompt is redisplayed the console is no longer in secure mode and all console commands can be performed during the current console session.
2.6.4 Returning to User Mode The clear password command clears the password environment vari able, setting it to zero. Once the password is cleared, you are returned to user mode. Example 2–12 Clear Password P00>>> clear password Please enter the password: Console is secure P00>>> clear password Please enter the password: Password successfully cleared. P00>>> n o n o The wrong password is entered. The system remains in secure mode. The password is successfully cleared.
2.7 Updating Firmware Typically, you update system firmware whenever the operating system is updated. You might also need to update firmware if you add I/O de vice controllers and adapters, if enhancements are made to the firm ware, or if the serial ROM or RMC firmware become corrupted. Sources of Firmware Updates The system firmware resides in the flash ROM located on the system board. The Alpha Systems Firmware Update Kit comes on a CD-ROM, which is up dated quarterly.
2.7.1 Firmware Update Utility The system firmware is updated from a Loadable Firmware Update Utility (LFU). When you boot the medium containing the update image, the LFU banner and command descriptions are displayed. Enter com mands at the UPD> prompt. Before updating the firmware, enter the list command to list the current revi sion of the firmware. Enter the update command to update the firmware automatically. Example 2–13 Update Utility Display Checking dqa0.0.0.16.0 for the option firmware files. .
UPD> list Device Current Revision Filename Update Revision FSB V6.3-2 fsb_fw V6.3-2 SRM V6.3-1 srm_fw V6.3-1 srom V1.3-F srom_fw V1.3-F cipca_fw dfxaa_fw A420 3.20 fca_2354_fw CS3.81A4 kgpsa_8k_fw kzpcc_smor kzpcc_fw DS3.81A4 1.12 CQ16 kzpsa_fw A12 UPD> UPD> u srm Confirm update on: srm [Y/(N)]y WARNING: updates may take several minutes to complete for each device. DO NOT ABORT! srm Updating to 6.3-1... Verifying 6.3-1... PASSED.
2.7.2 Manual Updates If the RMC firmware or serial ROM (SROM) become corrupted, you can perform a manual update. 1. Boot the update medium. 2. At the UPD> prompt, enter the exit command and answer y at the prompt: UPD> exit Do you want to do a manual update [y/(n)] y AlphaServer DS25 Console V6.3-1, built on May 2,2002 at 05:02:30 3. To update RMC firmware, enter update rmc. To update the serial ROM (SROM), enter update srom.
Example 2–14 Update RMC Example UPD> update rmc Confirm update on: rmc [Y/(N)]y WARNING: updates may take several minutes to complete for each device. DO NOT ABORT! rmc Updating to V1.1... RMC - Starting to Test Max Fan Speeds RMC - Power Supplies OK RMC - System DC is OK RMC - System is up RMC - System Fans OK RMC - Powerup Complete Verifying V1.1... PASSED.
2.7.3 Updating from the CD-ROM You can update the system firmware from CD-ROM. 1. At the SRM console prompt, enter the show device command to determine the drive name of the CD-ROM drive. 2. Load the Alpha Systems Firmware Update CD into the drive. 3. Boot the system from the CD, using the drive name determined in step 1 (for example, dqa0). P00>>> boot dqa0 4. Enter the update command at the UPD> prompt. 5. When the update is complete, exit from the Firmware Update Utility.
2.7.4 Updating from an OpenVMS System Disk You can update the firmware from an OpenVMS system disk. 1. Download the firmware update image from the Firmware Updates Web site. 2. Rename the downloaded file to fwupdate.exe. 3. Enter the following commands on the OpenVMS Alpha system: $ set file/attr=(rfm:fix,lrl:512,mrs:512,rat:none) fwupdate.exe $ copy/contiguous fwupdate.exe "system_disk":[sys0.sysexe] NOTE: Insert the name of your system disk in place of "system_disk," for example, dka100:. 4.
2.7.5 Updating from the Network You can update firmware from the network using the MOP protocol for OpenVMS or the BOOTP protocol for Tru64 UNIX. Updating Firmware Using BOOTP 1. Download the firmware update image from the Firmware Updates Web site. 2. Copy the downloaded file to a UNIX based network server for BOOTP boot ing on the system. For details on configuring the BOOTP server, refer to Tru64 UNIX documentation or the system’s Firmware Release Notes docu ment. 3.
Chapter 3 Booting and Installing an Operating System This chapter gives instructions for booting the Tru64 UNIX, OpenVMS, and 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.
3.1 Setting Boot Options You can set a default boot device, boot flags, and network boot proto cols for Tru64 UNIX or OpenVMS using the SRM set command with en vironment 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 SRM boot-related environment variables are listed below and described in the following sections.
3.1.1 auto_action The auto_action environment variable specifies the action the console takes any time the system powers up, fails, or resets. The value of auto_action takes effect only after you reset the system by pressing the Reset button or by issuing the init command. The default setting for auto_action is halt. With this setting, the system stops in the SRM console after being initialized.
Examples In the following example, the operator sets the auto_action environment vari able to restart. The device specified with the bootdef_dev environment vari able is dka0. When Tru64 UNIX is shut down and rebooted, the system will reboot from dka0. P00>>> show auto_action auto_action halt P00>>> set auto_action restart P00>>> init . . . P00>>> show auto_action auto_action restart P00>>> show bootdef_dev bootdef_dev dka0 P00>>> boot ... [Log in to UNIX and shutdown/reboot] #shutdown -r now ...
3.1.2 bootdef_dev The bootdef_dev environment variable specifies one or more devices from which to boot the operating system. When more than one device is specified, the system searches in the order listed and boots from the first device with operating system software. Enter the show bootdef_dev command to display the current default boot de vice. Enter the show device command for a list of all devices in the system.
3.1.3 boot_file The boot_file environment variable specifies the default file name to be used for booting when no file name is specified by the boot command. The factory default value is null. The syntax is: set boot_file filename Example In this example, the system is set to boot from dka0.
3.1.4 boot_osflags The boot_osflags environment variable sets the default boot flags and, for OpenVMS, a root number. Boot flags contain information used by the operating system to determine some aspects of a system bootstrap. Under normal circumstances, you can use the default boot flag settings. To change the boot flags for the current boot only, use the flags_value argument with the boot command. The syntax is: set boot_osflags flags_value The flags_value argument is specific to the operating system.
Linux Systems The flags_value argument for Linux is 0 (zero). Flags_value Arguments for Red Hat Distribution 0 Halt. (Do not set init default to this value.) 1 Single-user mode. 2 Multiuser, without NFS (same as 3, if you do not have networking) 3 Full multiuser mode (Default) 4 Unused 5 X11 6 Reboot. (Do not set init default to this value.) Flags_value Arguments for SuSE Distribution 0 Halt. (Do not set init default to this value.) S Single-user mode.
OpenVMS Systems OpenVMS systems require an ordered pair as the flags_value argument: root_number and boot_flags. root_number Directory number of the system disk on which OpenVMS files are located. For example: boot_flags root_number Root Directory 0 (default) [SYS0.SYSEXE] 1 [SYS1.SYSEXE] 2 [SYS2.SYSEXE] 3 [SYS3.SYSEXE] The hexadecimal value of the bit number or numbers set. To specify multiple boot flags, add the flag values (logical OR).
Examples In the following OpenVMS example, root_number is set to 2 and boot_flags is set to 1. With this setting, the system will boot from root directory [SYS2.SYSEXE] to the SYSBOOT prompt when you enter the boot command. P00>>> set boot_osflags 2,1 In the following OpenVMS example, root_number is set to 0 and boot_flags is set to 80. With this setting, you are prompted for the name of the secondary boot strap file when you enter the boot command.
3.1.5 ex*0_inet_init The eg*0_inet_init, ei*0_inet_init, or ew*0_inet_init environment vari able determines whether the interface’s internal Internet database is initialized from nvram or from a network server (through the bootp protocol). Legal values are nvram and bootp. The default value is bootp. Set this environment variable if you are booting Tru64 UNIX from a RIS server. To list the network devices on your system, enter the show device command.
3.1.6 ex*_protocols The eg*0_protocols, 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 “eg,” “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 Tru64 UNIX can be booted from a CD-ROM on a local drive (a CD-ROM drive connected to the system), from a local SCSI disk, or from a UNIX RIS server. Example 3–1 shows a boot from a local SCSI disk drive. The example is abbreviated. For complete instructions on booting Tru64 UNIX, see the Tru64 UNIX Installation Guide. Example 3–1 Booting Tru64 UNIX from a Local SCSI Disk P00>>> boot dka200 (boot dka200.2.0.1.2 -flags 0,0) block 0 of dka200.2.0.1.
Mounting Memory filesystems evmstart: Daemon started Jun 3 14:38:12 esmd: Started monitoring the EVM daemon security configuration set to default (BASE). File /etc/sia/matrix.conf updated successfully. Successful SIA initialization /usr/sbin/autopush: Can’t push requested modules on STREAM for entry 36 /usr/sbin/autopush: Device (6,-1) already configured . . . LAT started. Printer service started SysMan authentication server (smauthd) started SysMan Station server (smsd) started The system is ready.
Perform the following tasks to boot a Tru64 UNIX system: 1. Power up the system. The system stops at the SRM console prompt, P00>>>. 2. Set boot environment variables, if desired. See Section 3.1. 3. Install the boot medium. For a network boot, see Section 3.2.1. 4. Enter the show device command to determine the unit number of the drive for your device. 5. Enter the boot command and command-line parameters (if you have not set the associated environment variables).
3.2.1 Booting Tru64 UNIX over the Network To boot your Tru64 UNIX system over the network, make sure the sys tem is registered on a Remote Installation Services (RIS) server. See the Tru64 UNIX document entitled Sharing Software on a Local Area Network for registration information. Example 3–2 RIS Boot P00>>> show device dqa0.0.0.16.0 dva0.0.1000.0* ega0.0.0.5.2 eia0.0.0.8.0 pka0.7.0.1.2 pkb0.7.0.101.2 DQA0 DVA0 EGA0 EIA0 PKA0 PKB0 X HL-DT-ST GCE-8302B 2.
Systems running Tru64 UNIX support network adapters, designated eg*0, ew*0, or ei*0. The asterisk stands for the adapter ID (a, b, c, and so on). 1. Power up the system. The system stops at the SRM console prompt, P00>>>. 2. Set boot environment variables, if desired. See Section 3.1. 3. Enter the show device command drive for your device. 4. Enter the following commands. Example 3–2 assumes you are booting from ewa0. If you are booting from another drive, enter that device name in stead.
3.3 Starting a Tru64 UNIX Installation Tru64 UNIX is installed from the CD-ROM drive connected to the sys tem. The display that you see after you boot the CD depends on whether your system console is a VGA monitor or a serial terminal. Example 3–3 Text-Based Installation Display P00>>>b dqa0 (boot dqa0.0.0.16.0 -flags 0,0) block 0 of dqa0.0.0.16.0 is a valid boot block reading 15 blocks from dqa0.0.0.16.
o The "Exit Installation" option stops the installation and puts your system in single-user mode with superuser privileges. This option is intended for experienced UNIX system administrators who want to perform file system or disk maintenance tasks before the installation. This option may also be used for disaster recovery on a previously installed system. Remember, you can always get extra information by typing help. 1) U.S.
3.4 Booting Linux Obtain the Linux installation document and install Linux on the sys tem. Then verify the firmware version, boot device, and boot parame ters, and issue the boot command. The procedure for installing Linux on an Alpha system is described in the Alpha Linux installation document for your Linux distribution. The installation document can be downloaded from the following Web site: http://www.compaq.com/alphaserver/linux You need V6.3 or higher of the SRM console to install Linux.
3. After installing Linux, set boot environment variables to configure boot pa rameters for Red Hat, SuSE, or TurboLinux. This example shows settings for booting from the system hard drive (dka0). P00>>> set bootdef_dev dka0 P00>>> set boot_file P00>>> set boot_osflags 0 P00>>> show boot* boot_dev dka0.0.0.17.0 boot_file boot_osflags 0 boot_reset OFF bootdef_dev booted_dev booted_file booted_osflags 4. From SRM enter the boot command. The following example shows abbre viated boot output.
Kernel command line: root=/dev/sda2 console=ttyS0 Using epoch = 1952 Console: colour dummy device 80x25 Calibrating delay loop... 1993.
Vendor: COMPAQ Model: BF01863644 Rev: 3B05 Type: Direct-Access ANSI SCSI revision: 02 scsi0:A:0:0: Tagged Queuing enabled. Depth 253 scsi0:A:1:0: Tagged Queuing enabled. Depth 253 Attached scsi disk sda at scsi0, channel 0, id 0, lun 0 Attached scsi disk sdb at scsi0, channel 0, id 1, lun 0 (scsi0:A:0): 160.000MB/s transfers (80.000MHz DT, offset 63, 16bit) SCSI device sda: 35565080 512-byte hdwr sectors (18209 MB) Partition check: sda: sda1 sda2 sda3 (scsi0:A:1): 160.000MB/s transfers (80.
3.5 Booting OpenVMS OpenVMS can be booted from a CD-ROM on a local drive (the CD-ROM drive connected to the system) or from a CD-ROM drive on the InfoServer. Example 3–5 Booting OpenVMS from the Local CD-ROM Drive P00>>> show device dqa0.0.0.16.0 dva0.0.1000.0* ega0.0.0.5.2 eia0.0.0.8.0 pka0.7.0.1.2 pkb0.7.0.101.2 DQA0 DVA0 EGA0 EIA0 PKA0 PKB0 X HL-DT-ST GCE-8302B 2.01 00-00-00-00-00-00 40-00-04-A5-F8-00 SCSI Bus ID 7 SCSI Bus ID 7 P00>>> . . . P00>>> boot -flags 0,0 dqa0 (boot dka0.0.0.7.
Example 3–5 shows a boot from a CD-ROM on a local drive. The example is abbreviated. For complete instructions on booting OpenVMS, see the OpenVMS installation document. 1. Power up the system. The system stops at the SRM console prompt, P00>>>. 2. Set boot environment variables, if desired. See Section 3.1. 3. Install the boot medium. For a network boot, see Section 3.6. 4. Enter the show device command drive for your device. 5.
3.6 Booting OpenVMS from the InfoServer You can boot OpenVMS from InfoServer with a LAN device. The de vices are designated eg*0, ew*0, or ei*0. The asterisk stands for the adapter ID (a, b, c, and so on). Example 3–6 InfoServer Boot P00>>> show device dqa0.0.0.16.0 dva0.0.1000.0* ega0.0.0.5.2 eia0.0.0.8.0 pka0.7.0.1.2 pkb0.7.0.101.2 DQA0 DVA0 EGA0 EIA0 PKA0 PKB0 X HL-DT-ST GCE-8302B 2.01 00-00-00-00-00-00 40-00-04-A5-F8-00 SCSI Bus ID 7 SCSI Bus ID 7 P00>>> . . .
Z 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_V73-1_SSB OpenVMS (TM) Alpha Operating System, Version V7.3-1 1. Power up the system. The system stops at the P00>>> console prompt. 2.
3.7 Starting an OpenVMS Installation After you boot the operating system CD-ROM, an installation menu is displayed on the screen. Choose item 1 (Install or upgrade OpenVMS Alpha). Refer to the OpenVMS installation document for information on creating the system disk. Example 3–7 OpenVMS Installation Menu OpenVMS (TM) Alpha Operating System, Version V7.3-1 %SMP-I-SECMSG, CPU #01 message: P01>>>START %SMP-I-CPUTRN, CPU #01 has joined the active set.
Chapter 4 Configuring and Installing Components This chapter shows how to configure and install user-replaceable components, including DIMMs, PCI options, power supplies, disk drives, and tape drives. It also covers configuring CPUs, installing the storage cage, configuration utilities, and updating firmware. Installation of components not covered in this chapter is reserved for service providers and customers who have purchased a selfmaintenance contract.
4.1 Installing a Pedestal Kit This section is for customers who ordered a pedestal kit. The pedestal kit is used to convert a rackmount system to a pedestal. CAUTION: The system is very heavy. Two people are needed to lift and maneu ver it. NOTE: Before you begin the conversion procedure, shut down the operating sys tem, turn off power to the system, and unplug the power cord. Review Figure 4–1 and Table 4–1 to verify the contents of the pedestal kit.
Figure 4–1 Pedestal Kit Contents 5 1 8 8 7 9 6 4 2 3 3 7 MR0298A Configuring and Installing Components 4-3
Table 4–1 Pedestal Kit Contents X Y Z [ \ ] ^ _ ` Hardware Part Number Quantity Upper panel 74-60248-01 1 Lower panel 74-60248-02 1 Slide feet 74-51716-01 2 (may already be installed on Side dress panel 74-60250-01 1 Side access cover (painted) 74-60247-02 1 Front door assembly 70-40254-01 1 Screws, M3x6mm 90-09984-20 9 (for attaching slide feet. If slide feet are attached, only 1 screw loose piece.
Figure 4–2 Installing the Lower Panel 2 1 MR0299 Conversion Procedure 1. Remove the top cover from the rack system by loosening the captive screw and sliding the cover to the rear. Set aside the cover; it will not be reused. 2. Rotate the system chassis so that the operator control panel (OCP) the lower right. X is at Y 3. Place the lower panel slide feet up , with the large tabs to the right as you face the front of the unit. Slide the panel to the left and seat it firmly.
5. Place the upper panel with the painted surface up and the large tabs to the left on the top of the unit. Slide the panel to the right. Insert a thumbscrew into the tab on the panel and insert it in the box and tighten. See Figure 4–3.
6. Place the right side dress panel on the right side of the unit and engage the tabs in the slots. Push the panel toward the front of the unit. Insert one M3x6mm screw in the hole on the rear of the panel and tighten. See Figure 4–4.
7. Install the side access cover by inserting the cover tabs (4 top, 4 bottom) into the slots in the chassis. Slide the cover forward and secure it with the captive screw . See Figure 4–5.
8. Hold the door so that the hinge is to the right as you face the front of the unit. Rotate the door until it is at a 90-degree angle with the right edge of the unit. Insert the door hinge pins into the mating holes recessed on the right edge of the unit and push down slightly. Close the door.
4.2 Preparing to Install Components To prepare your system for installation or replacement of components, assemble the required equipment, perform shutdown procedures, and attach an antistatic wrist strap. Who should install components? Refer to the following table to determine who should install or replace compo nents. Components in the "Customer" column can be added or replaced by cus tomers with appropriate technical training and experience.
4.3 Removing the Side Cover (Pedestal) Figure 4–7 Removing the Side Cover 1 MR0415 1. Open the front door. 2. Loosen the thumbscrew X that secures the side cover to the chassis. 3. Slide the cover rearward and remove it.
4. Attach an antistatic wrist strap as shown in Figure 4–8.
4.4 Removing the Top Cover (Rackmount) Figure 4–9 Removing Top Cover 1 CAT0033a To remove the top cover: 1. Remove the bezel. 2. Loosen the thumbscrew X that secures the cover to the chassis. 3. Slide the cover rearward and remove it. 4. Attach an antistatic wrist strap as shown in Figure 4–8.
4.5 Memory Configuration The system supports a total of 16 DIMMs, divided into four arrays of four slots each. DIMMs within an array must be of the same size and speed. The system supports a maximum of 16 GB of memory. The minimum memory configuration is 512 MB. 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.
Figure 4–10 Stacked and Unstacked DIMMs Unstacked DIMMs Stacked DIMMs PK1209 Memory Configuration Rules • • • • • You can install up to 16 DIMMs. A maximum of 16 GB of memory is supported. If your system is model Dx57AAA-xx and contains model FR-H7910-AA power supplies, three supplies are required to support memory greater than 8GB. There are four memory arrays, numbered 0–3, with four slots per array. A memory array must be populated with four DIMMs of the same size and speed.
Figure 4–11 Memory Slots 15 7 13 5 14 12 6 4 0 2 1 8 3 9 10 11 MR0304A Table 4–2 DIMM and Array Reference DIMM W Y [ ] _ a Connector Array J15 0 J12 2 J45 0 J48 2 J9 1 J3 Connector Array J14 0 J10 2 J47 0 J50 2 J6 1 3 J1 3 J51 1 J53 1 J55 3 J56 3 4-16 DS25 Owner’s Guide DIMM X Z \ ^ `
4.5.1 Installing and Removing DIMMs Before installing DIMMs, shut down the operating system, turn off power to the system, and unplug the power cord. Remove the side cover (pedestal) or top cover (rackmount) and attach an antistatic wrist strap. Figure 4–12 Removing DIMMs 1 2 CAT0125A 1. Shut down the operating system and turn off power to the system. Unplug the power cord from each power supply. 2.
Figure 4–13 Installing DIMMs 1 2 1 Y CAT0124A 1. To install the DIMM , align the notches on the gold fingers with the con nector keys as shown in Figure 4–13. 2. Shut down the operating system and turn off power to the system. Unplug the power cord from each power supply. 3. Use Table 4–2 and the Memory Configuration Rules for determining where sets of memory DIMMs should be installed. Y 4. To install the DIMM , align the notches on the gold fingers with the con nector keys as shown in Figure 4–13.
4.6 CPU Configuration If your system came with one 1 GHz Alpha processor installed, you can upgrade by installing a second Alpha processor. Processor Upgrade Guidelines • • • In a single processor configuration, the CPU must be installed in the CPU slot 0 socket. A single processor configuration does not require termination in the empty socket. Dual processors must be the same speed and same cache size.
Figure 4–14 CPU Installation 1 2 2 MR0310A X into the slot until the gold fingers meet the system 1. Push the CPU module motherboard CPU connector. Y 2. Push the clips inward and down until the clips are horizontal and a complete connection is made.
4.7 Installing a PCI Option PCI slot 1 is the leftmost slot in a rackmounted system or the bottom most slot in a pedestal system. In systems with part numbers Dx57AAA-xx, slot 6 supports a half-length card only. In systems with part numbers Dx-57AAB-xx, slot 6 supports full-length cards. Slots 1 through 5 support full-length cards. Figure 4–15 PCI Slots 1 2 3 4 5 6 MR0294 When installing PCI option modules, you do not normally need to perform any configuration procedures.
4.7.1 PCI Configuration PCI modules are either designed for 5.0 volts or 3.3 volts, or are univer sal in design and can plug into either 3.3 or 5.0 volt slots. PCI slots are split across three independent 64-bit PCI buses, two buses at 66 MHz and one bus at 33 MHz. These buses correspond to Hose 0, 1, and 3 in the system logical configuration. The slots on each bus are listed below. Some PCI options require drivers to be installed and configured. These options come with a CD-ROM.
Figure 4–16 PCI Slot Voltages and Hose Numbers 6 5 4 3 2 1 Max Speed Voltage 33 MHz 5.0V 33 MHz 5.0V 66 MHz 3.3V 66 MHz 3.3V 66 MHz 3.3V 66 MHz 3.
4.7.2 Installing a PCI Option Some PCI options require drivers to be installed and configured. These options come with a CD-ROM. Refer to the installation document that came with the option and follow the manufacturer’s instructions. ! WARNING: To prevent injury, access is limited to persons who have appropriate technical training and experience. Such per sons are expected to understand the hazards of working within this equipment and take measures to minimize danger to them selves or others.
Figure 4–17 Installing a PCI Option 3 7 2 8 1 5 4 6 MR0394 Configuring and Installing Components 4-25
X Z CAUTION: Hot plug is not currently supported by the operating systems. Do not press switches or on the hot-swap board. Pressing these switches can result in the loss of data. Complete the following procedure to add or remove a PCI option module. 1. Turn off the system power. Y. Press in latch button Z and open the latch [. 2. Unscrew captive screw 3. 4. When replacing a PCI module, remove the bad module by pulling straight out. \ 5.
4.8 Installing a Redundant Power Supply Systems containing model FR-H7910-AA power supplies (part number 30-50662-01) require a minimum of three power supplies if the system contains more than 8GB of memory. Systems containing model 3XH7911-AA power supplies (part number 30-10047-01) require a minimum of two power supplies. A third supply may be added for redundancy.
To add a third power supply 1. Loosen the thumbscrews set aside the grid. X securing the power supply grid and remove and 2. Insert a flat-head screwdriver into one of the holes in the power supply blank, engage the slot on the locking tab, and push the tab away from the chassis. Y 3. Insert the screwdriver into the other hole and free the second locking tab. 4. Slide the blank out of the chassis. [ Z Y 5.
4.9 Network Configuration An Ethernet option can be installed in any open PCI slot. Figure 4–19 Network Connection 2 1 10 / 100 A 10 / 100 / 1000 B ENET 10/100 0 6 5 1 4 3 2 2 1 MR0306 The DS25 has dual Ethernet and supports various Ethernet network options. The system is configured with 10/100 and 10/100/1000 onboard Ethernet adapters. Supported options are also offered to connect to Fiber Distributed Data Interface (FDDI) networks.
4.9.1 Ethernet Connection Status LEDs Figure 4–20 and Table 4–3 contain information about the Ethernet status LEDs.
4.10 Disk Drive Configuration Table 4–4 shows the slot numbering. The SCSI ID for disk drives is pre set on the backplane. Table 4–4 SCSI ID Orientation Backplane Connector No.
4.11 Installing Disk Drives The storage subsystem backplane is designed to support hot swap, the installation or removal of drives while the system is powered and operating. Hot swap allows for removal of non-operating drives and does not affect the power for the drives that are in operation.
CAUTION: Do not remove a drive that is in operation. A drive should be re moved only when its Activity LED is off. Installing Drives X 1. Insert the drive carrier into the cage with the front handle fully open. With the carrier resting on top of the rail guides of the cage, slide the car rier in until it stops. 2. Push the handle into the cage. Y in to make the backplane connection and to secure it Removing Drives 1. To remove the carrier, press the colored rubber button handle.
4.11.1 Drive Status LEDs Three status LEDs display activity, power, and fault. Figure 4–23 shows the LEDs and their positions on the carrier, and Table 4–5 ex plains the status of each. Figure 4–23 Disk Drive LEDs MR0308 Table 4–5 Drive Status LED Status Green indicates activity. Green indicates drive state. Amber indicates drive state fault.
4.12 External SCSI Expansion There are two ways to connect external SCSI devices, such as tabletop or rackmount storage: (a) PCI-based SCSI adapters and (b) the embed ded SCSI controller that is accessed through its external bulkhead connector . See Figure 4-24. X SCSI Expansion Rules Observe the following rules to determine if a particular device can be used: • The device must be supported by the operating system. Consult the sup ported options list.
Figure 4–24 External SCSI 2 10 / 100 A 10 / 100 / 1000 B 1 0 6 5 1 4 3 2 2 1 MR0305 4-36 DS25 Owner’s Guide
4.13 Updating Firmware Typically, you update system firmware whenever the operating system is updated. You might also need to update firmware if you add I/O de vice controllers and adapters or if enhancements are made to the firmware. Firmware is updated from the Loadable Firmware Update utility (LFU). The LFU banner is shown in Figure 4–25.
4.13.1 Sources of Firmware Updates The system firmware resides in the flash ROM located on the system board. The Alpha Systems Firmware Update Kit comes on a CD-ROM, which is updated quarterly. You can also obtain Alpha firmware up dates from the Internet. Quarterly Update Service The Alpha Systems Firmware Update Kit CD-ROM is available by subscription from HP. Alpha Firmware Internet Access You can also obtain Alpha firmware update files from the Internet: http://ftp.digital.
4.13.2 Updating Firmware from the CD-ROM Use the following procedure to update the firmware from the quarterly CD-ROM. See the Alpha Firmware Web site listed in the Preface for other methods of updating the firmware and to obtain files if you are not updating from the CD. 1. Shut down the operating system. 2. Turn the system off and then on. 3. At the SRM console prompt, enter the show device command to determine the drive name of the CD-ROM drive. 4.
Chapter 5 Firmware The SRM user interface is the command-line interface that allows you to config ure and boot the operating system and verify the configuration of devices. This chapter describes typical functions performed from the SRM console and the commands and environment variables used for these functions.
5.1 SRM Console Overview The SRM console is the command-line interface that supports the Tru64 UNIX and OpenVMS operating systems and Linux. The SRM con sole is used to bootstrap the operating system, configure and test the system hardware, examine system options for errors, and set or change environment variables. The SRM console works much like a UNIX shell. It views your NVRAM and de vices as a pseudo file system.
Environment Variables SRM has environment variables, a number of which are predefined and corre spond to locations in NVRAM. You can view the entire list of environment vari ables and their values with the show command (there are quite a few of them, so you will probably want to pipe its output to more). You can also use the * (asterisk) wildcard to show variables matching a pattern. For example, show boot* displays all the variables starting with “boot.
5.1.1 Invoking the SRM Console You can invoke the SRM console at power-up or restart or after a sys tem failure. Once you invoke SRM, you enter commands at the console prompt. Invoking SRM from Tru64 UNIX, Linux, or OpenVMS The SRM console is invoked automatically at power-up or after a reset or fail ure. The auto_action environment variable is set by default to halt, which causes the system to stop in the SRM console.
5.2 Command Summary Table 5–1 summarizes alphabetically the most frequently used SRM console commands; Table 5–2 gives the command notation formats; and Table 5–3 shows special characters used on the command line. Table 5–1 Summary of SRM Console Commands Command Function boot Loads and starts the operating system. clear envar Resets an environment variable to its default value. continue Resumes program execution on the specified processor or on the primary processor if none is specified.
Table 5–1 Summary of SRM Console Commands (Continued) Command Function lfu Runs the Loadable Firmware Update utility. login Turns off secure mode, enabling access to all SRM console commands during the current session. more [filename] Displays a file one screen at a time. set envar Sets or modifies the value of an environment variable. show envar Displays the state of the specified environment variable. stop Halts the specified processor. (Same as halt.
Table 5–2 Notation Formats for SRM Console Commands Attribute Conditions Length Up to 255 characters, not including the terminating carriage return or any characters deleted as the command is entered. To enter a command longer than 80 characters, use the back slash character for line continuation (see Table 5–3). Case Upper- or lowercase characters can be used for input. Charac ters are displayed in the case in which they are entered. Abbreviation Only by dropping characters from the end of words.
Table 5–3 Special Characters for SRM Console Character Function Return or Enter Terminates a command line. No action is taken on a com mand until it is terminated. If no characters are entered and this key is pressed, the console just redisplays the prompt. Backslash (\) Continues a command on the next line. Must be the last character on the line to be continued. Delete Deletes the previous character. Ctrl/A Toggles between insert and overstrike modes. The default is overstrike.
Table 5–3 Special Characters for SRM Console (Continued) Character Function Ctrl/Q Resumes output to the console terminal that was sus pended by Ctrl/S. Ctrl/R Redisplays the current line. Deleted characters are omit ted. This command is useful for hardcopy terminals. Ctrl/S Suspends output to the console terminal until Ctrl/Q is entered. Cleared by Ctrl/C. Ctrl/U Deletes the current line. * Wildcarding for commands such as show.
5.3 Getting Help The help (or man) command displays basic information about a com mand. Example 5–1 Help (or Man) P00>>> help set NAME set FUNCTION Set or modify the value of an environment variable. SYNOPSIS set [-integer] [-string] where ={auto_action,bootdef_dev,boot_file,boot_osflags,...
The help (or man) command displays basic information about the use of console commands when the system is in console mode. The syntax is: help (or man) [command . . . ] command . . . Command or topic for which help is requested. The options are: none Displays the complete list of commands for which you can receive help. command_name Displays information about the console command. argument_string (such as “sh”) Displays information about all commands that begin with that string.
5.4 Displaying the Configuration Use the show config command to display a list of devices found on the system interconnect and I/O buses. This is the configuration at the most recent initialization. Example 5–2 Show Config P00>>> sho config hp AlphaServer DS25 X Firmware SRM Console: PALcode: Serial ROM: RMC ROM: RMC Flash ROM: V6.3-1 OpenVMS PALcode V1.96-40, Tru64 UNIX PALcode V1.90-31 V1.3-F G1.4 V1.1 Processors CPU 0 CPU 1 Alpha EV68CB pass 2.4 1000 MHz Alpha EV68CB pass 2.
5 Slot 1 6 P00>>> n o p q r BCOM Gigabit 5703c ega0.0.0.5.2 00-02-A5-20-7F-AC Option ELSA GLoria Synergy Yukon PCI Hot-Plug C Hose 3, Bus 0, PCI - 66 MHz vga0.0.0.1.3 Firmware. Version numbers of the SRM console, PALcode, serial ROM, RMC ROM, and RMC flash ROM Processors. Processors present, processor version and clock speed, and amount of backup cache Core logic. Version numbers of the chips that form the interconnect on the system board Memory.
Table 5–4 How Physical I/O Slots Map to Logical Slots Physical Slot 5-14 SRM Logical Slot ID 1 Hose 0 Slot ID 1 2 Hose 0 Slot ID 2 3 Hose 3 Slot ID 2 4 Hose 3 Slot ID 1 5 Hose 1 Slot ID 9 6 Hose 1 Slot ID 10 DS25 Owner’s Guide
5.5 Displaying the Bootable Devices The show device command displays the devices and controllers in the system, including the bootable devices. Example 5–3 Show Device P00>>> show device dqa0.0.0.16.0 dva0.0.1000.0* ega0.0.0.5.2 eia0.0.0.8.0 pka0.7.0.1.2 pkb0.7.0.101.2 DQA0 DVA0 EGA0 EIA0 PKA0 PKB0 HL-DT-ST GCE-8302B 2.01 00-00-00-00-00-00 40-00-04-A5-F8-00 SCSI Bus ID 7 SCSI Bus ID 7 P00>>> * DS25 systems have no floppy drives.
5.6 Displaying the Memory Configuration Use the show memory command to display information about each memory array: array number, size in megabytes, starting address, and interleave mode. The display also shows the total amount of good memory. It does not indicate the number of DIMMs or their size.
5.7 Displaying the Power Status Use the show power command to display information about status of the power supplies, system fans, CPU fans, and temperature. See Chapter 7 for troubleshooting with the show power command.
5.8 Displaying the SRM Console Version Use the show version command to display the version of the SRM con sole that is installed. Example 5–6 Show Version P00>>> sho version version P00>>> 5-18 DS25 Owner’s Guide V6.
5.9 Displaying the CPU Status Use the show cpu command to display the status of each CPU. CPU slot 0 is the right slot in a rack system and the top slot in a pedestal system. Example 5–7 Show CPU P00>>> show cpu Primary CPU: Active CPUs: Configured CPUs: X 00 00 00 01 01 X The CPUs have been brought successfully online and are ready to run an operating system.
5.10 Displaying the PALcode Version Use the show pal command to display the version of Tru64 UNIX or OpenVMS PALcode. The PALcode is the Alpha Privileged Architecture Library code, written to support Alpha processors. It implements ar chitecturally defined processor behavior. Example 5–8 Show Pal P00>>> sho pal pal PALcode V1.90-31 P00>>> 5-20 DS25 Owner’s Guide OpenVMS PALcode V1.
5.11 Booting an Operating System The boot command boots the Tru64 UNIX, Linux, or OpenVMS operat ing system. You can specify a boot device, operating system-specific boot information (boot flags), and an Ethernet protocol for network boots. You can also specify whether the boot program should halt and remain in console mode. Example 5–9 Tru64 UNIX Boot (Abbreviated) P00>>> boot dka200 boot dka200.2.0.1.2 -flags 0,0) block 0 of dka200.2.0.1.2 is a valid boot block reading 14 blocks from dka200.2.0.1.
boot [-file filename] [-flags [value]] [-halt] [-protocols enet_protocol] [boot_dev] -file filename Specifies the name of a file to load into the system. Use the set boot_file command to set a default boot file. See Chapter 4. NOTE: For booting from Ethernet, the filename is limited by the MOP V3 load protocol to 15 characters. The MOP protocol is used with OpenVMS systems. -flags [value] Provides additional operating system-specific boot information. In Tru64 UNIX, specifies boot flags.
5.12 Testing the System Use the test command to run firmware diagnostics for components of the system. Use Ctrl/C to abort testing. Example 5–10 Test P00>>> test Default zone extended at the expense of memzone. Use INIT before booting Testing Ethernet device(s) Testing Memory Testing IDE/ATAPI disks (read-only) Testing SCSI disks (read-only) dqa0.0.0.105.0 has no media present or is disabled via the RUN/STOP switch file open failed for dqa0.0.0.105.
The test command tests the entire system, a subsystem, or a specified device. If no device or subsystem is specified, the entire system is tested. To run a complete diagnostic test using the test command, the system configu ration must include a CD ROM and loopback connectors on COM2 and the par allel port.
5.13 Starting and Stopping CPUs Use the halt and continue commands to stop and continue a program on the specified CPU. Example 5–11 Halt and Continue P00>>> halt 1 halted CPU 1 halt code = 1 operator initiated halt PC = ffffffff8007cc68 P00>>> continue &p1 continuing CPU 1 5.13.1 halt (or stop) The halt (or stop) command stops program execution on a secondary CPU that is still running a booted program.
The syntax is: continue [&pn] [address] &pn Specifies the processor. n is 0 or 1. address The starting address of the program. NOTE: Some console commands, for example, boot, can alter the machine state so that program mode cannot be successfully resumed (unless you in clude -halt in the boot command). If you cannot resume program exe cution, reboot the operating system. Other commands that alter machine state are lfu and test.
5.14 Updating Firmware Use the lfu command to update firmware. Example 5–12 shows a typi cal update from a CD-ROM. For more information on updating firm ware, see Chapters 2 and 4 of this manual and the Alpha Systems Firm ware Web site. Example 5–12 Updating Firmware from a CD P00>>> lfu Checking dqa0.0.0.16.0 for the option firmware files. . . dqa0.0.0.16.0 has no media present or is disabled via the RUN/STOP switch Checking dva0.0.0.1000.0 for the option firmware files. . .
Procedure for Updating from a CD 1. Copy the firmware files, as described on the Alpha Systems Firmware Web site. 2. The update utility runs and says that files were not found on CD, but then asks on which device the files are located. 3. Insert the CD into the drive on the system and enter the lfu command from SRM. 4. Type dqa0. 5. The LFU then prompts for the name of the firmware files list. Press Return. The default file, DS25fw.txt, will be on the CD. 6. When completed, type done.
Example 5–13 Updating Firmware from a CD (Continued) UPD> list Device Current Revision Filename Update Revision FSB V6.3-2 fsb_fw V6.3-2 SRM V6.3-1 srm_fw V6.3-1 srom V1.3-F srom_fw V1.3-F cipca_fw A420 dfxaa_fw 3.20 fca_2354_fw CS3.81A4 kgpsa_8k_fw kzpcc_smor kzpcc_fw DS3.81A4 1.12 CQ16 kzpsa_fw A12 UPD> UPD> u srm Confirm update on: srm [Y/(N)]y WARNING: updates may take several minutes to complete for each device. DO NOT ABORT! srm Updating to 6.3-1... Verifying 6.3-1...
5.15 Forcing a System Crash Dump For fatal errors the operating system will save the contents of memory to a crash dump file. Crash dump files can be used to determine why the system crashed. Use the crash command to force a crash dump. Example 5–14 Crash P00>>> crash CPU 0 restarting DUMP: 401408 blocks available for dumping. DUMP: 38535 required for a partial dump. DUMP:0x805001is the primary swap with 401407,start our last 38534 of dump at 362873, going to end (real end is one more,for header) DUMP.
5.16 Initializing the System The init command resets the system and executes the power-up tests. Example 5–15 Init P00>>> init Initializing... OpenVMS PALcode V1.96-40, Tru64 UNIX PALcode V1.
bus 0, slot 16 -- dqa -- Acer Labs M1543C IDE bus 0, slot 16 -- dqb -- Acer Labs M1543C IDE Hose 1 - PCI bus running at 66Mhz probing hose 1, PCI Hose 2 - PCI bus running at 66Mhz probing hose 2, PCI bus 0, slot 1, function 0 -- pka -- Adaptec AIC-7899 bus 0, slot 1, function 1 -- pkb -- Adaptec AIC-7899 bus 0, slot 5 -- ega -- BCOM NIC Gigabit Hose 3 - PCI bus running at 33Mhz probing hose 3, PCI starting drivers initializing keyboard starting console on CPU 1 initialized idle PCB initializing idle process
The init command resets the system. Issuing this command is equivalent to pressing the Reset button. The syntax is: init After self-tests are executed, the system autoboots unless one of the following is true: • A halt assertion exists (see Chapter 6). • The auto_action environment variable is set to halt. If the auto_action environment variable is set to boot or restart and no halt assertion condition exists, the system autoboots.
5.17 Reading a File The more command displays a file one screen at a time. Example 5–16 More P00>>> more el *** keyboard not plugged in...
The more command is similar to the UNIX more command. It is useful for dis playing output that scrolls too quickly to be viewed. For example, when you power up the system, the system startup messages scroll, and the messages are logged to an event log. When the P00>>> prompt displays, you can use the more command to display the contents of the event log file. See Example 5–16. The syntax is: more [file...] The file is the name of the file to be displayed.
5.18 Creating a Power-Up Script The system comes with a special nonvolatile file named “nvram” that is stored in EEROM. Nvram is a user-created power-up script (set of commands) that is always invoked during the power-up sequence. Use the SRM edit command to create or alter the nvram script.
Editing the Nvram Script You can create an nvram script to include any commands you want the system to execute at power-up. You create and edit the nvram script using the SRM edit command. With edit, lines may be added, overwritten, or deleted. The syntax is: edit file file is the name of the file to be edited. The editing commands are: help Displays the brief help file. list Lists the current file prefixed with line numbers. renumber Renumbers the lines of the file in increments of 10.
5.19 Setting Console Security The SRM console firmware has console security features intended to prevent unauthorized personnel from modifying the system parame ters or otherwise tampering with the system from the console. The se curity features include a secure mode and commands to set console se curity. 5.19.1 Overview of Secure Mode The SRM console has two modes, user mode and secure mode. • User mode allows you to use all SRM console commands. User mode is the default mode.
5.19.2 Setting the Console Password Set the console password with the set password command. A password is required for operating the system in secure mode.
X Y Z Setting a password. If a password has not been set and the set password command is issued, the console prompts for a password and verification. The password and verification are not echoed. Changing a password. If a password has been set and the set password command is issued, the console prompts for the new password and verifica tion, then prompts for the old password. The password is not changed if the validation password entered does not match the existing password stored in NVRAM.
5.19.3 Setting the Console to Secure Mode To set the console to secure mode, first set the password. Then enter the set secure command. The system immediately enters secure mode. Example 5–20 Set Secure P00>>> set secure Console is secure. Please login. P00>>> b dkb0 Console is secure - parameters are not allowed. P00>>> login Please enter the password: P00>>> b dkb0 (boot dkb0.0.0.3.1) 1 Y . . .
5.19.4 Turning Off Security During a Console Session The login command turns off the security features, enabling access to all SRM console commands during the current console session. The sys tem automatically returns to secure mode as soon as the boot or con tinue command is entered or when the system is reset. Example 5–21 Login P00>>> login Secure not set. Please set the password. P00>>> set password Please enter the password: Please enter the password again: P00>>> login Please enter the password.
When you enter the login command, you are prompted for the current system password. If a password has not been set, a message is displayed indicating that there is no password in NVRAM. If a password has been set, this prompt is dis played: Please enter the password: If the password entered matches the password in NVRAM, when the prompt is redisplayed the console is no longer in secure mode and all console commands can be performed during the current console session.
From the RMC 1. From the SRM console, enter the login command: P00>>> login 2. At the Enter Password: prompt, type the RMC escape sequence. 3. AT the RMC>>> prompt, enter the halt command and then the quit com mand: RMC>>> halt RMC>>> quit 4. At the SRM console, clear the password P00>>> clear password Please enter the password: Password successfully cleared.
5.19.5 Returning to User Mode The clear password command clears the password environment vari able, setting it to zero. Once the password is cleared, you are returned to user mode. Example 5–22 Clear Password P00>>> clear password Please enter the password: Console is secure P00>>> clear password Please enter the password: Password successfully cleared. P00>>> X Y X Y The wrong password is entered. The system remains in secure mode. The password is successfully cleared.
5.20 Setting and Viewing Environment Variables Use the set envar and show envar commands to set and view environ ment variables. Example 5–23 Set envar and Show envar P00>>> set bootdef_dev dkb0 P00>>> show bootdef_dev Bootdef_dev dkb0 Environment variables pass configuration information between the console and the operating system. Their settings determine how the system powers up, boots the operating system, and operates. Environment variables are set or changed with the set envar command.
set envar The set command sets or modifies the value of an environment variable. It can also be used to create a new environment variable if the name used is unique. Environment variables pass configuration information between the console and the operating system. Their settings determine how the system powers up, boots the operating system, and operates. The syntax is: set [-default] envar value -default Restores an environment variable to its default setting.
Table 5–6 summarizes the most commonly used SRM environment variables. These environment variables are described in the following pages. NOTE: The environment variables for setting boot options are described in Chapter 3, Booting and Installing an Operating System. Table 5–6 Environment Variable Summary Environment Variable Function auto_action Specifies the console’s action at power-up, a failure, or a reset. bootdef_dev Specifies the default boot device string.
Table 5–6 Environment Variable Summary (Continued) Environment Variable Function kbd_hardware_ type Specifies the default console keyboard type. language Specifies the console keyboard layout. os_type Specifies the operating system and sets the appro priate console interface. password Sets a console password. Required for placing the SRM into secure mode. pci_parity Disables or enables parity checking on the PCI bus. pk*0_fast Enables fast SCSI mode.
5.20.1 com*_baud The default baud rate for the system is 9600. The com*_baud com mands set the baud rate for COM1 and COM2. com1_baud The com1_baud environment variable sets the baud rate for the internal COM1 serial interface. com2_baud The com2_baud environment variable sets the baud rate to match that of the device connected to the COM2 port. The syntax is: set com*_baud baud_value baud_value The new baud rate. A list of possible values is displayed by en tering the command without a value.
5.20.2 console The console terminal can be either a VGA monitor or a serial terminal. The console environment variable specifies which type of console is used. The syntax is: set console output_device The options for output_device are: graphics (default) The console terminal is a VGA monitor or a device con nected to the VGA port. serial The console terminal is the device connected to the COM1 port.
5.20.3 cpu_enabled The cpu_enabled environment variable sets a bit mask that enables or disables specific CPUs in a multiprocessor system. Disabling a CPU may be necessary if a number of errors are reported on a spe cific CPU. These errors might be displayed during power-up or might be dis played with the show config command. Disabled CPUs are prevented from running the console or the operating system. Bit 0 of the mask corresponds to CPU 0 and bit 1 to CPU 1.
5.20.4 eg*0_mode or ei*0_mode or ew*0_mode The eg*0_mode or ei*0_mode or ew*0_mode environment variable sets an Ethernet controller to run an AUI, ThinWire, or twisted-pair Ethernet network. For the fast setting, the device defaults to fast. To list the network devices on your system, enter the show device command. The Ethernet controllers start with the letters “eg”, “ei,” or “ew,” for example, ewa0. The third letter is the adapter ID for the specific Ethernet controller.
The options for eg*_mode value are: auto Auto negotiate 10mbps 10 Mb half duplex 10mbps_full_duplex 10 Mb full duplex 100mbps 100 Mb half duplex 100mbps_full_duplex 100 Mb full duplex 1000mbps 1000 Mb half duplex 1000mbps_full_duplex 1000 Mb full duplex 5-54 DS25 Owner’s Guide
5.20.5 kbd_hardware_type The kbd_hardware_type environment variable sets the keyboard hardware type as either PCXAL or LK411 and enables the system to in terpret the terminal keyboard layout correctly. The syntax is: set kbd_hardware_type keyboard_type The options for keyboard_type are: pcxal (default) Selects the 102-type keyboard layout. lk411 Selects the LK411 keyboard layout.
5.20.6 language The language environment variable specifies the keyboard layout, which depends on the language. The setting of the language environ ment variable must match the language of the keyboard variant. The factory keyboard setting is 36 English (American). The value of language takes effect only after you reset the system by pressing the Reset button or issuing the init command.
5.20.7 os_type The os_type environment variable specifies the default operating sys tem. This variable is set at the factory to the setting for the operating system you purchased. Use this command to change the factory default setting. The value of os_type takes effect only after you reset the system by pressing the Reset button or by issuing the init command. The syntax is: set os_type os_type The options for os_type are: unix Sets the default to Tru64 UNIX.
5.20.8 pci_parity The pci_parity environment variable disables or enables parity check ing on the PCI bus. Some PCI devices do not implement PCI parity checking, and some have a parity-generating scheme in which the parity is sometimes incorrect or is not fully compliant with the PCI specification. A side effect of this behavior is that super fluous PCI parity errors are reported by the host PCI bridge. In such cases, the device can be used as long as parity is not checked.
5.20.9 pk*0_fast The pk*0_fast environment variable enables fast SCSI to perform in ei ther standard or fast mode. If the system has at least one fast SCSI device, set the default controller speed to fast SCSI (1). Devices on a controller that connects to both standard and fast SCSI devices will perform at the appropriate rate for the device. If the system has no fast SCSI devices, set the default controller speed to standard SCSI (0).
5.20.10 pk*0_host_id The pk*0_host_id environment variable sets the controller host bus node ID to a value between 0 and 7. Each SCSI bus in the system requires a controller. Buses can support up to eight devices; however, the eighth device must be a controller. Each device on the bus, including the controller, must have a unique ID, which is a number be tween 0 and 7. This is the bus node ID number. On each bus, the default bus node ID for the controller is set to 7.
5.20.11 pk*0_soft_term The pk*0_soft_term environment variable enables or disables SCSI terminators for optional SCSI controllers. This environment variable applies to systems that use the QLogic SCSI controller, though it does not affect the onboard controller. The QLogic ISP1020 SCSI controller implements the 16-bit wide SCSI bus. The QLogic module has two terminators, one for the low eight bits and one for the high eight bits. To list the controllers on your system, enter the show device command.
Examples In this example, both terminators are disabled. P00>>> set pkb0_soft_term off P00>>> init . . . P00>>> show pkb0_soft_term pkb0_soft_term off In this example, the terminator for the high 8 bits is enabled. P00>>> set pkb0_soft_term high P00>>> init . . .
5.20.12 tt_allow_login The tt_allow_login environment variable enables or disables login to the SRM console firmware on alternative console ports. “Login” refers to pressing the Return or Enter key to activate the console device. If the console environment variable is set to serial, the primary console device is the terminal connected through the COM1 port. The set tt_allow_login 1 command lets you activate a console device through COM2 or a VGA monitor.
Chapter 6 Remote Management You can manage the system through the remote management console (RMC). The RMC is implemented through an independent microprocessor that resides on the system board. The RMC also provides configuration and error log func tionality. This chapter explains the operation and use of the RMC.
6.1 RMC Overview The remote management console provides a mechanism for monitoring the system (voltages, temperatures, and fans) and manipulating it on a low level (reset, power on/off, halt). The RMC performs monitoring and control functions to ensure the successful operation of the system.
The RMC logic is implemented using an 8-bit microprocessor, PIC17C44, as the primary control device. The firmware code resides on the microprocessor and in flash memory. If the RMC firmware should ever become corrupted or obsolete, you can update it manually using the Loadable Firmware Update Utility. See Chapters 2 and 4 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 sys tem.
6.2 Operating Modes The RMC can be configured to manage different data flow paths de fined by the com1_mode environment variable. In Through mode (the default), all data and control signals flow from the system COM1 port through the RMC to the active external port. You can also set bypass modes so that the signals partially or completely bypass the RMC. The com1_mode environment variable can be set from either SRM or the RMC. See Section 6.8.
Through Mode Through mode is the default operating mode. The RMC routes every character of data between the internal system COM1 port and the active external port, or the 9-pin modem port. If a modem is connected, the data goes to the modem. The RMC filters the data for a specific escape sequence. If it detects the escape sequence, it enters the RMC CLI. Figure 6–1 illustrates the data flow in Through mode.
6.2.1 Bypass Modes For modem connection, you can set the operating mode so that data and control signals partially or completely bypass the RMC. The by pass modes are Snoop, Soft Bypass, and Firm Bypass.
Figure 6–2 shows the data flow in the bypass modes. Note that the internal system COM1 port is connected directly to the modem port. NOTE: You can connect a serial terminal to the modem port in any of the by pass modes. Snoop Mode In Snoop mode data partially bypasses the RMC. The data and control signals are routed directly between the system COM1 port and the external modem port, but the RMC taps into the data lines and listens passively for the RMC escape sequence.
After downloading binary files, you can set the com1_mode environment vari able from the SRM console to switch back to Snoop mode or other modes for ac cessing the RMC, or you can hang up the current modem session and reconnect 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 con figure or monitor the modem.
6.3 Terminal Setup To set up the RMC to monitor a system remotely, connect the modem to the COM1 port at the back of the system; then configure the modem port for dial-in.
6.4 SRM Environment Variables for COM1 Several SRM environment variables allow you to set up the COM1 se rial port (MMJ) for use with the RMC. You may need to set the following environment variables from the SRM console, depending on how you decide to set up the RMC. com1_baud Sets the baud rate of the COM1 serial port and the modem port. The default is 9600. See Chapter 5. com1_flow Specifies the flow control on the serial port. The de fault is software. See Chapter 5.
6.5 Entering the RMC You type an escape sequence to invoke the RMC. You can enter RMC from any of the following: a modem, the local serial console terminal, the local VGA monitor, or the system. The “system” includes the oper ating system, SRM, or an application. • You can enter the RMC from the COM1 terminal regardless of the current operating mode. • You can enter the RMC from the modem if the RMC is in Through mode or Snoop mode.
Entering from the Local VGA Monitor To enter the RMC from the local VGA monitor, the console environment vari able must be set to graphics. Invoke the SRM console and enter the rmc command. P00>>>set Com1_mode through P00>>> rmc You are about to connect to the Remote Management Console. Use the RMC reset command or press the front panel reset but ton to disconnect and to reload the SRM console.
6.6 Using the Command-Line Interface The remote management console supports setup commands and com mands for managing the system. For detailed descriptions of the RMC commands, see Section 6.8. Command Conventions Observe the following conventions for entering RMC commands: • Enter enough characters to distinguish the command. NOTE: The reset and quit commands are exceptions. You must enter the entire string for these commands to work.
6.6.1 Displaying the System Status The RMC status command displays the system status and the current RMC settings. Table 6–1 explains the status fields. See Section 6.8 for information on the commands used to set the status fields. RMC> status PLATFORM STATUS On-Chip Firmware Revision: V1.0 Flash Firmware Revision: V1.
Table 6–1 Status Command Fields Field Meaning On-Chip Firmware Revision: Revision of RMC firmware on the microcontroller. Flash Firmware Revision: Revision of RMC firmware in flash ROM. Server Power: ON = System is on. OFF = System is off. System Halt: Asserted = System has been halted. Deasserted = Halt has been released. RMC Power Control: ON= System has powered on from RMC. OFF = System has powered off from RMC. Escape Sequence: Current escape sequence for access to RMC console.
6.6.2 Displaying the System Environment The RMC env command provides a snapshot of the system environ ment. RMC> env System Hardware Monitor System Temperatures (warnings at 50.00C, power-off at 55.00C) CPU1: 33.00C CPU0: 29.00C Zone1: 33.00C Zone2: 29.00C Zone0: 34.00C Fan RPMs Sys Fan0: 2428 Sys Fan1: 2428 PCI Fan: 1695 CPU0 Fan: 3590 CPU1 Fan: 3629 Power Supply(OK, FAIL, OFF, ’----’ means not present) PS0 : OK PS1 : OK PS2 : OK CPU0: OK CPU1: OK CPU CORE voltage CPU0: +1.650V CPU1: +1.
n o p q r s CPU temperature. Zone 0, 1, and 2 measure the temperature of the PCI compartment and are reported from three thermal sensors located in different areas of the back plane. Fan RPM (system fans, CPU fans, and PCI fan). 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, CPU I/O voltage, and CPU cache voltage.
6.6.3 Using Power On and Off, Reset, and Halt Functions The RMC power {on, off}, halt {in, out}, and reset commands perform the same functions as the buttons on the operator control panel. Power On and Power Off The RMC power on command powers the system on, and the power off com mand powers the system off. 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 dis played, indicating that the command will have no effect.
6.6.4 Configuring Remote Dial-In Before you can dial in through the RMC modem port or enable the sys tem to call out in response to system alerts, you must configure RMC for remote dial-in. Connect your modem to the 9-pin modem port and turn it on. Enter the RMC from either the Com1 serial terminal or the local VGA monitor to set up the pa rameters. NOTE: Com1_mode must be in either Snoop or Through to start the Dial-In Configuration.
n o p q Sets the password that is prompted for at the beginning of a modem ses sion. The string cannot exceed 14 characters and is not case sensitive. For security, the password is not echoed on the screen. When prompted for verification, type the password again. Sets the initialization string. The string is limited to 31 characters and can be modified depending on the type of modem used.
6.6.5 Configuring Dial-Out Alert When you are not monitoring the system from a modem connection, you can use the RMC dial-out alert feature to remain informed of sys tem status. If dial-out alert is enabled, and the RMC detects alarm con ditions within the managed system, it can call a preset pager number. You must configure remote dial-in for the dial-out feature to be enabled. See Section 6.6.4. To set up the dial-out alert feature, enter the RMC from the COM1 serial ter minal or local VGA monitor.
The elements of the dial string and alert string are shown in Table 6–2. Paging services vary, so you need to become familiar with the options provided by the paging service you will be using. The RMC supports only numeric messages. n o p q r s t Sets the string to be used by the RMC to dial out when an alert condition occurs. The dial string must include the appropriate modem commands to dial the number. Sets the alert string, typically the phone number of the modem connected to the remote system.
Table 6–2 Elements of Dial String and Alert String Dial String The dial string is case sensitive. The RMC automatically con verts all alphabetic characters to uppercase. ATXDT AT = Attention. X = Forces the modem to dial “blindly” (not seek the dial tone). Enter this character if the dial-out line modifies its dial tone when used for services such as voice mail. D = Dial T = Tone (for touch-tone) 9, The number for an outside line (in this example, 9).
6.7 Resetting the RMC to Factory Defaults If the non-default RMC escape sequence has been lost or forgotten, RMC must be reset to factory settings to restore the default escape se quence. WARNING: To prevent injury, access is limited to persons who have appropriate technical training and experience. Such per sons are expected to understand the hazards of working within this equipment and take measures to minimize danger to them selves or others.
6. On the system board, install the following jumpers for default mode (see Figure 6–4 for locations. a) Install jumper J36 over pins 3 and 2 (RMC flash ROM Write Enable). b) Install jumper J43 over pins 2 and 1 (Temperature Fail System Shut down Disable). c) Install jumper J66 over pins 3 and 2 (RMC Environmental Control). d) Jumpers J69, J70, and J71 are not jumpered (RMC Features). e) Install jumper J68 over pins 2 and 3 (selects COM1 mode).
Figure 6–4 RMC Jumpers (Default Positions) J68 J71 1 2 J70 J43 J66 3 2 1 3 2 1 J36 3 2 1 3 2 1 1 2 J69 1 2 MR0392A Remote Management 6-27
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 and wait several seconds before proceeding. 9. Reinstall CPU1, the card cage cover and fan cover and the enclosure panels. 10. Plug the power cord into each of the power supplies. NOTE: After the RMC has been reset to defaults, perform the setup procedures to enable remote dial-in and call-out alerts. See Section 6.6.4.
6.8 RMC Command Reference This section describes the RMC command set. Commands are listed in alphabetical order. clear {alert, port} dep disable {alert, remote} dump enable {alert, remote} env halt {in, out} hangup help or ? power {on, off} quit reset send alert set {alert, com1_mode, dial, escape, init, logout, password, user} status NOTE: The dep and dump commands are reserved for service providers.
clear port The clear port command clears any “stuck” conditions on the system’s COM1 port. The clear port command attempts to free the port by resetting all UARTs con trolled by the RMC if the port is currently locked by an application program, without resetting the entire system. RMC> clear port RMC> NOTE: This command also causes the modem to disconnect. disable alert The disable alert command disables the RMC from paging a remote system operator.
enable alert The enable alert command enables the RMC to page a remote system operator. Before you can enter the enable alert command, you must configure remote dial-in and call-out, set an RMC password, and enable remote access to the RMC modem port. See Section 6.6.4 and Section 6.6.5.
enable remote The enable remote command enables remote access to the RMC modem port by configuring the modem with the setting stored in the initialization string. This command also allows the RMC to automatically dial the pager number set with the set dial command upon detection of alert conditions. Before you can enter the enable remote command, you must configure remote dial-in by setting an RMC password and initialization string. See Section 6.6.4.
halt in The halt in command is equivalent to pressing the Halt button on the control panel. The halt in command halts the managed system. When the halt in command is issued, the terminal exits RMC and returns to the server’s COM1 port. Toggling the Power button on the operator control panel overrides the halt in condition. RMC> halt in Returning to COM port halt out The halt out command is equivalent to releasing the Halt button on the control panel. The halt out command releases a halt.
help or ? The help or ? command displays the RMC command set. RMC> help clear {alert, port} deposit disable {alert, remote} dump enable {alert, remote} env halt {in, out} hangup help or ? power {off, on} quit reset send alert set {alert, com1_mode, dial, escape, init, logout, password, user} status power off The power off command is equivalent to turning off the system power from the operator control panel. If the system is already powered off, this command has no effect.
The power on command does not turn on the system if the Power button on the operator control panel is in the Off position. If you issue the command, the fol lowing message is displayed: RMC> power on Power button is OFF quit The quit command exits RMC and returns the terminal to the server’s COM1 port. You must enter the entire word for the command to take effect. RMC> quit Returning to COM port reset The reset command is equivalent to pushing the Reset button on the operator control panel.
set alert The set alert command sets the alert string that is transmitted through the modem when an alert condition is detected. Set the alert string to the phone number of the modem connected to the remote system. The alert string is appended after the dial string, and the combined string is sent to the modem. The example shown below is generic. Because paging services vary, be sure to listen to the options provided by the paging service to determine the appropriate delay and the menu options.
• In Snoop mode, you can type an escape sequence to enter the RMC. RMC mode provides a command-line interface for issuing commands to monitor and control the system. • In Soft Bypass mode, you cannot enter the RMC. But if an alert condition or loss of carrier occurs, the RMC switches into Snoop mode. From Snoop mode you can enter RMC. • In Firm Bypass mode you cannot enter the RMC. To enter, reset the com1_mode environment variable from the SRM console.
set dial The set dial command sets the string to be used by the RMC to dial out when an alert condition occurs. The dial string must be in the correct format for the attached modem. If a pag ing service is to be contacted, the string must include the appropriate modem commands to dial the number. The dial string is case sensitive. The RMC automatically converts all alphabetic characters to uppercase. RMC> set dial Dial String: ATXDT9,15085553333 RMC> For more information, see Section 6.6.5.
set init The set init command sets the modem initialization string. The initialization string is limited to 31 characters and can be modified, depend ing on the type of modem used. RMC> set init Init String: AT&F0E0V0X0S0=2 RMC> Because the modem commands disallow mixed cases, the RMC automatically converts all alphabetic characters entered in the init string to uppercase. The RMC automatically configures the modem’s flow control according to the setting of the SRM com1_flow environment variable.
set password The set password command allows you to set or change the password that is prompted for at the beginning of a modem session. A password must be set to enable access through a modem. The string cannot exceed 14 characters. For security, the password is not echoed on the screen. When prompted for verification, type the password again. If you mistype, reen ter the set password command.
6.9 Troubleshooting Tips Table 6–3 lists possible causes and suggested solutions for symptoms you might see. Table 6–3 RMC Troubleshooting Symptom Possible Cause Suggested Solution You cannot enter the RMC from the modem. The RMC may be in soft bypass or firm by pass 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 ses sion and reconnect it. The terminal cannot communicate with the RMC correctly.
Table 6–3 RMC Troubleshooting (Continued) Symptom Possible Cause Suggested Solution RMC will not answer when modem is called. (continued from previ ous 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 at tempting to dial in. After the system is powered up, the COM1 port seems to hang or you seem to be unable to execute RMC com mands.
Chapter 7 Troubleshooting This chapter describes procedures for basic troubleshooting.
7.1 Error Beep Codes Audible beep codes announce errors encountered while the system is powering up. For example, if the firmware in flash ROM is unavailable, you would hear a 1-1-4 beep code (one beep, a pause, a another beep, a pause, and a burst of four beeps). Table 7–1 identifies the error beep codes. Table 7–1 Error Beep Codes Beeps Message/Meaning 1-1-4 SROM code is unable to load the console code; a flash ROM header area or checksum error has been detected. See Section 3.4.1.
7.2 Diagnostic LEDs on OCP Diagnostic LEDs on the operator control panel indicate error conditions and power-up information. When the green power LED is lit, use Table 7–2 and Table 7–3. When the green power LED is not lit, use Table 7–4.
\ is On in all cases except In Table 7–2 and Table 7–3, the green power LED for two. These two cases are indicated in the table. In Table 7–4 the green power LED is always Off ( = On / = Off). z { Table 7–2 System Warning Messages LED 1 z { z { LED 2 z z { { LED 3 { { { { LED 4 { { { { Problem Condition PS0 failed PS1 failed PS2 failed Warning – Use the RMC to view specific failure ( See Chapter 6).
Table 7–4 Fatal Errors and System Is Down LED 1 z { z { z { z z { z { z { z LED 2 z z { { z z { z z { { z z { LED 3 z z z z { { { z z z z { { { LED 4 z z z z z z z { { { { { { { Power-Up Message Door open too long CPU0 failed CPU1 failed VTERM or CTERM failed Both system fans failed CPU fan0 failed CPU fan1 failed Over temperature failure CPU0 missing TIG error Bad CPU data PS configuration error Power supply 2 5 volt failure Bad DPR Troubleshooting 7-5
7.3 Power Problems Table 7–5 Troubleshooting Power Problems If the power indicator is: Check: Off • Front-panel power switch • Power at the wall receptacle • AC cord • Power cable connectors • Side cover (pedestal) or top cover (rack). Interlocking sensor switch shuts off power if the cover is removed. Unplug the power cords for 15 seconds, then reconnect. On for a few seconds and then goes Off Power supply fan. Listen to hear if the power supply fan is spinning at power-up.
7.4 Console-Reported Failures Table 7–6 Troubleshooting Console-Reported Failures Symptom Action Power-up tests do not complete. Use error beep codes or console serial terminal to determine what error occurred. Check the power-up screen for error messages. Console program reports an error. Interpret the error beep codes at power-up and check the power-up screen for a failure detected during self-tests.
7.5 Boot Problems Table 7–7 Troubleshooting Boot Problems Problem/Possible Cause Action Operating system (OS) software is not installed on the hard disk drive. Install the operating system and license key. Target boot device is not listed in the SRM show device or show config command. Check the cables. Are the cables oriented properly and not cocked? Are there bent pins? Check all the SCSI devices for incorrect or conflicting IDs. Refer to the device’s documentation.
Table 7–7 Troubleshooting Boot Problems (Continued) Problem/Possible Cause Action System does not boot. Verify that no unsupported adapters are installed. Environment variables are incorrectly set. This could happen if the main logic board has been replaced, which would cause a loss of the previous configuration information. Use the SRM show and set commands to check and set the values assigned to boot-related variables such as auto_action, bootdef_dev, and boot_osflags.
7.6 Thermal Problems and Environmental Status Overtemperature conditions can cause the system to shut down. The DS25 system operates in an ambient temperature range of 10ºC–35ºC. Internal sensors monitor system and power supply temperature and shut down the system if maximum limits are exceeded. If the system shuts down unexpectedly: • Ensure that the side cover (pedestal) or top cover (rack) are properly secured. • Verify that the ambient temperature does not exceed the specified limits.
7.7 Operating System Reported Failures Table 7–8 Operating System Reported Failures Symptom Action System is hung or has crashed. If possible, halt the system with the Halt button or the RMC halt command. Then enter the SRM crash command and examine the crash dump file. Refer to the Guide to Kernel Debugging (AAPS2TD-TE) for information on using the Tru64 UNIX Crash utility. Errors have been logged and the operating system is up. Examine the operating system error log files.
7.8 Memory Problems Table 7–9 Troubleshooting Memory Problems Symptom Action DIMMs ignored by system, or system unstable. System hangs or crashes. Ensure that each memory array has identical DIMMs installed. DIMMs failing memory powerup self-test. Try another set of four DIMMs. DIMMs may not have ECC bits. Some third-party DIMMs may not be compatible with DS25 systems. Ensure memory DIMMs are qualified. Noticeable performance degradation. The system may appear hung or run very slowly.
7.9 PCI Bus Problems PCI bus problems at startup are usually indicated by the inability of the system to detect the PCI device. The following steps can be used to diagnose the likely cause of PCI bus problems. 1. Confirm that the PCI option card is supported and has the correct firmware and software versions. 2. Confirm that the PCI option card and any cabling are properly seated. 3. Check for a bad PCI slot by moving the last installed PCI controller to a different slot. 4.
7.10 SCSI Problems SCSI problems are generally manifested as data corruption, boot problems, or poor performance. Check SCSI bus termination. • Cable is properly seated at system board or option connector. • Bus must be terminated at last device on cable or at physical cable end. • No terminators in between. • Old 50-pin (narrow) devices must be connected with wide-to-narrow adapter (SN-PBXKP-BA). Do not cable from the connector on the card.
7.11 Fail-Safe Booter Utility The fail-safe booter (FSB) is another variant of the SRM console. The FSB provides an emergency recovery mechanism if the firmware image contained in flash memory becomes corrupted. You can run the FSB and boot another image from a CD-ROM or network that is capable of reprogramming the flash ROM.
7.11.2 Starting the FSB Manually 1. Power the system off, unplug the power supplies, and remove the cover. 2. Remove CPU0 to gain access to J25 jumper on the system board. See Figure 7–2. 3. Move jumper from pins 1-2 to 2-3 on J25. 4. Reconnect CPU0. 5. Reconnect the power supplies and reinstall the system cover. Power up the system to the FSB console.
7.11.3 Required Firmware The required firmware for your system is preloaded onto the flash ROM. Copies of the firmware files are included on your distribution CD. You can also download the latest firmware files from the Alpha systems firmware Web site: ftp://ftp.digital.com/pub/Digital/Alpha/firmware/readme.html The utilities that are used to reload or update the firmware expect to find the files on a CD.
7.11.4 Updating Firmware Be sure to read the information on starting the FSB before continuing with this section. Example 7–1 Running LFU P00>>> lfu Checking dqa0.0.0.16.0 for the option firmware files. . . dqa0.0.0.16.0 has no media present or is disabled via the RUN/STOP switch Checking dva0.0.0.1000.0 for the option firmware files. . . Option firmware files were not found on CD or floppy.
Perform the following steps to update the console firmware. Refer to Example 7–1. 1. Insert the Alpha Firmware CD named DS25SRM.ROM into the CD-ROM drive. 2. At the SRM console prompt, issue the lfu command. This command invokes the Loadable Firmware Update (LFU) utility. 3. At the UPD> prompt, enter the update command. 4.
Chapter 8 Specifications This chapter contains the following system specifications and requirements: • Physical Specifications • Environmental Specifications • Electrical Specifications • Acoustical Data • Power Cord Requirements Specifications 8-1
8.1 Physical Specifications Table 8–1 Physical Specifications Pedestal Dimensions (HxWxD) 18.5 x 8.85 x 27.5 in. / 47.0 x 22.5 x 69.9 cm Shipping Dimensions 24 x 26.25 x 40 in. / 61.0 x 66.0 x 101.6 cm Weight Typical Configuration 80 lb / 36 kg Maximum Configuration 88 lb / 40 kg Shipping Weight Nominal 100 lb / 45 kg Maximum 110 lb / 50 kg Clearances Operating Service Front 15 in. / 38.1 cm 15 in. / 38.1 cm Rear 6 in. / 15 cm 29.5 in.
Table 8–1 Physical Specifications (Continued) Rackmount Dimensions (HxWxD) 8.75 x 17.5 x 26 in. / 22.2 x 44.5 x 66.0 cm (5U) Shipping Dimensions 24 x 26.25 x 40 in. / 61.0 x 66.0 x 101.6 cm Weight When lifting: Nominal 80 lb /36 kg Maximum 86 lbs/39 kg Total added to cabinet (brackets, slides, cables): Nominal 84 lb/38 kg Maximum 88 lbs/40 kg Shipping Weight Nominal 100 lb /45 kg Maximum 110 lbs/50 kg Clearance for Service Minimum 4 ft / 121.9 cm, 28 in.
8.
8.3 Electrical Specifications Table 8–3 Electrical Specifications Nominal Voltage (Vac) 100 120 200–240 Voltage Range (Vac) temporary condition 90–100 110–128 180–250 Power Source Phase 1–3 1–3 1–3 Nominal Frequency (Hz) 50/60 50/60 50/60 Frequency Range (Hz) 49–51/59–61 49–51/59–61 49–51/59–61 4.2A 3.0A (3x for rack) 1010 2.5A 1.75A (3x for rack) 975 RMS Current (maximum steady state) Pedestal and Rackmount Each cord, two PS Each cord, three PS Maximum VA 5.2A 3.
Table 8–3 Electrical Specifications (Continued) Product Safety Approvals UL: Listed to UL1950 (3rd edition) CSA: Certified to CAN/CSA-C22.2 No.
8.4 Acoustical Data Table 8–4 lists the noise declaration for the DS25 system. Table 8–4 Acoustical Data Acoustics — Declared Values per ISO 9296 and ISO 7779 LwAd, B LpAm, dBA (bystander positions) Product Idle Operate Idle Operate AlphaServer DS25 6.3 6.4 45 46 Current values for specific configurations are available from HP representatives. 1 B = 10 dBA.
8.5 Power Cord Requirements The power cord set meets the requirements for use in the country where you purchased your equipment. Power cord sets for use in other countries must meet the requirements of the country where you use the system. For more information on power cord set requirements, contact your Authorized HP Dealer. 8.5.1 General Requirements The requirements listed below apply to all countries. • The length of the power cord must be at least 6.0 ft (1.8 m) and a maximum of 12 ft (3.7 m).
8.5.2 Country-Specific Requirements Table 8–5 Power Cord Requirements by Country Country Accredited Agency Applicable Note Numbers Australia Austria Belgium EANSW OVE CEBC 1 1 1 Canada Denmark Finland France CSA DEMKO SETI UTE 2 1 1 1 Germany Italy Japan VDE IMQ JIS 1 1 3 Norway Sweden Switzerland United Kingdom NEMKO SEMKO SEV BSI 1 1 1 1 United States UL 2 NOTES: 1. Flexible cord must be Type HO5VV-F, 3-conductor, 1.0 mm2 conductor size.
Index A Acoustics, 8-7 Antistatic wrist strap, 4-12 APB program, 3-27 auto_action environment variable, 3-3, 5-4 Autoboot, 3-3 Auxiliary power supply, RMC, 6-3 B Baud rate, setting, 5-50 Beep codes, 7-2 boot command, 5-21 Boot devices, specifying, 3-5 Boot file, specifying, 3-6 Boot flags OpenVMS, 3-9 UNIX, 3-7 boot options setting, 3-2 Boot problems, 7-8 boot_file environment variable, 3-6 boot_osflags environment variable, 3-7 Bootable devices displaying, 2-18 bootdef_dev environment variable, 3-5 Booti
setting, 2-22 Console terminal, 1-20 Console, specifying, 5-51 Console-reported failures, troubleshooting, 7 7 Continue command, 5-25 Control panel messages, 2-4 Controllers, SCSI, 5-60 Converting rack system to pedestal, 4-2 CPU card, 1-11 CPU configuration, 4-19 CPU, enabling, 5-52 cpu_enabled environment variable, 5-52 crash command, 5-30 D Device naming, 5-15 Device naming, SRM, 2-19 Diagnostic LEDs, 7-3 Dial-in configuration, 6-20 Dial-out alert, 6-22 DIMMs installing, 4-18 removing, 4-17 Disable ale
H Halt button, with login command, 2-27, 5-43 Halt command, 5-25 Halt in command (RMC), 6-33 Halt in/out command (RMC), 1-9 Halt out command (RMC), 6-33 Halt, remote, 1-9, 6-19 Hangup command (RMC), 6-21, 6-33 Hard drives, 1-18 Hardware configuration displaying, 2-15 viewing, 2-12 help command, 5-10 help or ? command (RMC), 6-34 I I/O slot mapping, 1-13 I/O slots, locations, 1-12 InfoServer, 3-27 Init command, 5-31, 5-33 Installation tools, 4-1 Installing door, 4-9 multichannel SCSI option, 4-27 options, 4
Operator control panel LEDs, 1-8 start-up messages, 2-4 Order numbers for documents, xiv os_type environment variable, 5-57 Overtemperature, 7-10 P Pagers, 6-23 Parity checking, 5-58 Password, setting SRM, 2-23 PCI buses, 4-22 overview, 1-12 slot locations, 1-12 PCI bus problems, 7-13 PCI option, installing, 4-25 PCI parity error, 7-13 PCI slots, 1-13, 2-17, 4-21, 5-14 pci_parity environment variable, 5-58 Pedestal kit, 4-2 contents of, 4-3 conversion procedure, 4-5 hardware part numbers, 4-4 Physical spec
hangup command, 6-21 local mode, 6-5 logic, 6-3 operating modes, 6-4 overview, 6-2 PIC processor, 6-3 quit command, 6-11 remote power on/off, 6-18 remote reset, 6-19 resetting to factory defaults, 6-25 snoop mode, 6-7 soft bypass mode, 6-7 status command, 6-14 through mode, 6-5 troubleshooting, 6-41 RMC commands clear alert, 6-29 clear port, 6-30 disable alert, 6-30 disable remote, 6-30 enable alert, 6-31 enable remote, 6-32 env, 6-32 halt in, 6-33 halt out, 6-33 hangup, 6-33 help or ?, 6-34 power off, 6-34
show version command, 5-18 Side cover, removing, 4-11 Slot numbers PCI, 4-22 Snoop mode, 6-7 Soft bypass mode, 6-7 Special characters, SRM console, 5-8 Specifications, 8-1 SRM console password, 2-23 console password clearing, 2-28 SRM console command syntax, 5-7 device naming, 2-19 invoking, 5-4 overview, 5-2 power-up display, 2-6 returning to from RMC, 5-4 setting environment variables, 5-46 special characters, 5-8 SRM console commands clear password, 2-28 login, 2-26 set password, 2-23 set secure, 2-25 sh
