HP Integrity rx4640 Operations Guide: Regulatory Model Number: RSVLA-0201
HP Integrity rx4640 Operations Guide: Regulatory Model Number: RSVLA-0201
Operations Guide
Regulatory Model Number: RSVLA-0201
Version 2.0
U.S.A.
© Copyright 2004 Hewlett-Packard Development Company, L.P..
Legal Notices
Copyright Notices. © Copyright 2004 Hewlett-Packard Development Company, L.P.
The information contained herein is subject to change without notice. The only warranties for HP products
and services are set forth in the express warranty statements accompanying such products and services.
Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for
technical or editorial errors or omissions contained herein.
Adobe and Acrobat are trademarks of Adobe Systems Incorporated. HP-UX Release 10.20 and later and
HP-UX Release 11.00 and later (in both 32 and 64-bit configurations) on all HP 9000 computers are Open
Group UNIX 95 branded products. Intel and Itanium are trademarks or registered trademarks of Intel
Corporation or its subsidiaries in the United States and other countries. Linux is a registered trademark of
Linus Torvalds. UNIX is a registered trademark of The Open Group. Windows is a registered trademark of
Microsoft Corporation.
Printed in the U.S.A.
Reproduction, adaptation, or translation of this document without prior written permission is prohibited,
except as allowed under the copyright laws.
Related Documents. The HP Server Documentation CD-ROM has been provided with the server. It contains
a documentation set for the server, including localized versions of key documents. Included on the CD-ROM
are the Site Preparation and Operations guides, which contain in-depth troubleshooting and installation
information.
The CD will autorun when you insert it into a Windowsâ workstation, or, point your browser at the [Link]
file located under the Start directory of the CD. All users, including UNIXâ/Linux, can access a manual set
by viewing the directory manuals. The manuals are in Adobeâ Acrobatâ Reader (pdf) format.
IMPORTANT The latest versions of these documents, and any updates to these documents, are posted under
the appropriate server at [Link]
Where to Get Help. For online access to technical support information, self-solve tools, online assistance,
community forums of IT experts, broad multivendor knowledge base, and monitoring and diagnostic tools, go
to [Link]
2
Contents
3. External Connectors
Connector Pinouts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Universal Serial Bus (USB) Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
VGA Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Serial Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Management Processor LAN Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Additional Ports on Accessory Boards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
4. Utilities
Extensible Firmware Interface (EFI) Boot Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
EFI Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
EFI/POSSE Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
baud . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
boottest . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
cpuconfig . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
default . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
errdump. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
info . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
lanaddress . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
monarch. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
pdt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
sysmode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Specifying SCSI Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
3
Contents
4
Contents
5. Troubleshooting
Troubleshooting Tips . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Troubleshooting Methodology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Possible Problems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
The system will not power-up. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
The system will not boot. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
The system has intermittent failures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
The system LED or Diagnostic LEDs are not on and no error messages appear.. . . . . . . . . . . . . . . . 74
Power goes off on the server and does not come back on . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Troubleshooting Using LED Indicators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
Front Control Panel LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
QuickFind Diagnostic Panel LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
I/O Baseboard LED Indicators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
Troubleshooting Using Online Support Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Support Tools Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Event Monitoring Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
Instant Support Enterprise Edition (ISEE) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
Troubleshooting Using Offline Support Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Offline Diagnostic Environment (ODE). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
e-Diagtools. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Management Processor (MP) Event Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
Other Event Logs and General Diagnostic Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
6. Specifications
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
Hardware Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
Dimensions and Weights . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
Server Component Dimensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
5
Contents
6
Figures
7
Figures
8
1 About This Document
This document describes how to operate your hp Integrity rx4640 Server, Regulatory Model Number:
RSVLA-0201.
The document printing date and part number indicate the document’s current edition. The printing date will
change when a new edition is printed. Minor changes may be made at reprint without changing the printing
date. The document part number will change when extensive changes are made.
Document updates may be issued between editions to correct errors or document product changes. To ensure
that you receive the updated or new editions, you should subscribe to the appropriate product support service.
See your HP sales representative for details.
IMPORTANT The latest version of this document can be found online at [Link]
• Chapter 2, “Controls, Ports, and Indicators.” Use this chapter to learn about the front panel controls,
rear panel ports and connectors, and all system LED locations and functions.
• Chapter 3, “External Connectors.” Use this chapter to learn about all external connectors, plugs, and
their pinouts.
• Chapter 4, “Utilities.” Use this chapter to learn how to navigate in the EFI and management processor
environments.
• Chapter 5, “Troubleshooting.” Use this chapter to learn how to perform minimal troubleshooting of
your system
• Chapter 6, “Specifications.” Use this chapter to learn the basic mechanical specifications of your HP
Server.
Typographical Conventions
This document uses the following conventions.
Title The title of a document or a CD.
KeyCap The name of a keyboard key. Note that Return and Enter both refer to the same key.
Emphasis Text that is emphasized.
Bold Text that is strongly emphasized, such as the summary text in bulleted paragraphs.
ComputerOut Text displayed by the computer.
UserInput Commands and other text that you type.
Command A command name or qualified command phrase.
Chapter 1 9
About This Document
Related Documents
Related Documents
The HP Server Documentation CD-ROM has been provided with the server. It contains a documentation set
for the server, including localized versions of key documents. Included on the CD-ROM are the Site
Preparation and Operations guides, which contain in-depth troubleshooting and installation information.
The CD will autorun when you insert it into a Windows workstation, or, point your browser at the [Link]
file located under the Start directory of the CD. All users, including UNIX/Linux, can access a complete
manual set by viewing the directory manuals. The manuals are in Adobe Acrobat Reader (pdf) format.
IMPORTANT The latest version of this document can be found online at [Link]
Step 1. Check information on troubleshooting and attempt to solve the problem. See the hp Integrity
rx4640 Installation Guide.
• Note failure symptoms and error indications (LEDs and messages) by checking the SEL and
FPL logs.
10 Chapter 1
About This Document
Where to Get Help
• The product number of your server. This can be found on the identification label, which is found
at the front of the unit (typically A6837B A6838B, and so on).
• The serial number of your server. This can be found on the identification label.
• Are you using the LAN, RS232, or web interface to monitor the server?
• How many processors, DIMMs, and PCI cards have been installed?
• What versions of processor, memory, and PCI cards are used and where are they installed?
Chapter 1 11
About This Document
Where to Get Help
12 Chapter 1
2 Controls, Ports, and Indicators
Introduction
This chapter describes the controls, ports, and indicators found on the front panel, rear panel, and internal
locations of the hp Integrity rx4640 Server. The hp Integrity rx4640 Server comes in either rack mount or
pedestal configurations.
Chapter 2 13
Controls, Ports, and Indicators
Front Panel
Front Panel
The front panel of the hp Integrity rx4640 Server provides the controls and indicators commonly used for
operation.
Control Panel
14 Chapter 2
Controls, Ports, and Indicators
Front Panel
System LED
Power LED
Power Button Disk LED
TOC/NMI Button
Thermal LED
Locator
Button/LED
LED/
State Flash Rate Color Description
Button
System Fault Flashing at Red Flashing Red: Hard fault. system halted
2 Hz
Chapter 2 15
Controls, Ports, and Indicators
Additional Controls and Indicators
Button/Switch Description
Power Button The power switch turns the HP Server power on or off. If sleep states are
available, it also transitions between power-on and sleep states.
Sleep states are NOS dependent and only available if your NOS supports
power management based on the ACPI (Advanced Configuration and Power
Interface) standard.
NMI Button Press the nonmaskable interrupt (NMI) switch before restarting the system
(Paper clip may be used to after a hung condition occurs. NMI provides crash dump capture capability.
depress button.) Obtain a system hardware status dump to use in root cause analysis and
debugging.
• Drive Status LED - The drive status LED is tri-color and may display green, amber, or yellow at any given
time. These colors indicate a normal, warning, or failure condition.
• Drive Activity LED - The drive activity LED is green and indicates disk drive activity. This LED is
controlled by the disk drive directly and turns on when a drive is accessed.
Status LED
Activity LED
Activity LED Flashing green Drive access under hard drive control.
16 Chapter 2
Controls, Ports, and Indicators
Additional Controls and Indicators
DVD–ROM/DVD-R/DVD-RW Drives
The HP Server is delivered with one DVD-ROM drive (DVD-R and DVD-RW optional). Each of these devices
has one activity LED.
Activity LED Flashing green Drive access under hard drive control.
Chapter 2 17
Controls, Ports, and Indicators
Additional Controls and Indicators
Processor Socket 0 Socket 1 Socket 2 Socket 3 If the System LED (on front panel) is in
the attention or fault state and the
processor LED is lit, then the processor or
voltage regulator has failed—the
processor module in the specified socket
needs to be replaced.
18 Chapter 2
Controls, Ports, and Indicators
Additional Controls and Indicators
Subsystem CPU Memory I/O board n/a A soldered voltage regulator has
board board failed—the specified board must be
replaced.
I/O VRM 12 volt 5 volt 3 volt n/a A plug-in voltage regulator has
failed—specific VRM must be replaced.
Memory DIMM xA DIMM DIMM xC DIMM The specified DIMM has failed—the
Bank X xB xD DIMM must be replaced.
(0-7)
If all the LEDs for a rank (0-7) are lit and
the Memory Config Error LED is lit then
the DIMMs in the specified rank are
mismatched—replace mismatched DIMM.
Check n/a n/a n/a One of the power supply or power supply
Power fans has failed—replace the power supply.
Supply The faulty power supply LED (located on
power supply) will be lit.
Memory n/a n/a n/a The DIMMs in a rank are mismatched. All
Config the DIMMs in the specified rank (0-7) will
Error be lit.
Chapter 2 19
Controls, Ports, and Indicators
Additional Controls and Indicators
Battery
3.3VSB
Power
LED
BMC
Reset
Button
PCI Attention
LED
6X
PCI Attention
Button (Doorbell)
5V VRM 6X
LED
PCI Power LED
MP Soft 6X
Reset
Button MP Heartbeat LED 3.3V VRM LED PCI Attention LED
MP Self-Test BMC Heartbeat LED Locator Button/LED 6X
LED
20 Chapter 2
Controls, Ports, and Indicators
Rear Panel
MP Self Test Amber On The management processor is executing the internal self test.
LED
Off The management processor has passed the internal self test.
BMC Heartbeat Green Blinking The baseboard management controller is functioning correctly.
Rear Panel
The HP Server rear panel includes communication ports, I/O ports, AC power connectors, two power supply
bays, attention LED indicators for the hot-plug PCI boards, and the locator LED/button. LEDs located on the
rear panel of the HP Server signal the operational status of:
• Power supplies
• Management processor LAN
• 2 Port Gigabit Ethernet card LAN
Chapter 2 21
Controls, Ports, and Indicators
Rear Panel
22 Chapter 2
Controls, Ports, and Indicators
Rear Panel
Chapter 2 23
Controls, Ports, and Indicators
Rear Panel
USB Ports
Locator Button and LED
24 Chapter 2
Controls, Ports, and Indicators
Rear Panel
(Core I/O)
The 2-Port core I/O Gigabit Ethernet card uses an RJ-45 LAN connector. This connector has 4 LEDs (3 LAN
link and 1 LAN activity) that signal link speed and activity.
RJ-45 Connector
1000 Activity
100 10
Chapter 2 25
Controls, Ports, and Indicators
Rear Panel
26 Chapter 2
3 External Connectors
Connector Pinouts
The following ports and connectors are found on the rear panel of the hp Integrity rx4640 Server. The SCSI
Host Bus Adapter card in slot 1 and the Gigabit Ethernet card in slot 2 are factory installed.
Local Ax Remote
1 1
2 2
3 3
4 4
1 +5VDC
2 MR
Chapter 3 27
External Connectors
Connector Pinouts
3 PR
4 Ground
VGA Port
1 Red 9 +5VDC
28 Chapter 3
External Connectors
Connector Pinouts
Serial Ports
2 Receive data
3 Transmit data
5 Ground
7 Request to send
8 Clear to send
9 Ring indicator
Green Yellow
1 8
1 TXP
2 TXN
3 RXP
Chapter 3 29
External Connectors
Connector Pinouts
4 Not used
5 Not used
6 RXN
7 Not used
8 Not used
1 8
1 RXP
2 RXN
3 TXP
4 Not used
5 Not used
6 TXN
7 Not used
8 Not used
30 Chapter 3
External Connectors
Connector Pinouts
35 68
1 34
15 S15 49 S49
20 S20 54 S54
Chapter 3 31
External Connectors
Connector Pinouts
22 S22 56 S56
32 Chapter 3
4 Utilities
NOTE EFI and Pre-OS System Environment (POSSE) are similar. EFI is an Intel specification,
whereas POSSE is the HP implementation that aids HP support.
EFI consolidates boot utilities found in PA-RISC based systems, such as the Boot Console Handler (BCH),
and platform firmware into a single platform firmware. EFI allows the selection of any EFI OS loader from
any boot medium that is supported by EFI boot services. An EFI OS loader supports multiple options on the
user interface.
EFI supports booting from media that contain an EFI OS loader or an EFI-defined System Partition. An
EFI-defined System Partition is required by EFI to boot from a block device.
Chapter 4 33
Utilities
Extensible Firmware Interface (EFI) Boot Manager
The EFI boot manager loads EFI applications (including OS first stage loader) and EFI drivers from an
EFI-defined file system or image loading service. NVRAM variables point to the file to be loaded. These
variables contain application-specific data that is passed directly to the EFI application. EFI variables
provides system firmware a boot menu that points to all the operating systems, even multiple versions of the
same operating systems.
The EFI boot manager allows you to control the server’s booting environment. Depending on how you have
configured the boot options, after the server is powered up the boot manager presents you with different ways
to bring up the system. For example, you can boot to the EFI shell, to an operating system located on the
network or residing on media in the server, or the Boot Maintenance menu.
• Boot from a File—Automatically adds EFI applications as boot options or allows you to boot from a
specific file. When you choose this option, the system searches for an EFI directory. If the EFI directory is
found, then it looks in each of the subdirectories below EFI. In each of those subdirectories, it looks for the
first file that is an executable EFI application. Each of the EFI applications that meet this criterion can
be automatically added as a boot option. In addition, legacy boot options for A: and C: are also added if
those devices are present. You can also launch a specific application without adding it as a boot option. In
this case the EFI boot manager searches the root directories and the \EFI\TOOLS directories of all of the
EFI system partitions present in the system for the specified EFI application.
• Add a Boot Option—Adds a boot option to the EFI boot manager. You specify the option by providing the
name of the EFI application. Along with the name you can also provide either ASCII or UNICODE
arguments the file might use. Given the EFI application name and any options, the EFI boot manager
searches for the executable file in the same directories as described in “Boot from a File” option. When the
file is found, it is executed.
• Delete Boot Options—Deletes a specific boot option or all boot options
• Change Boot Order—Controls the relative order in which the EFI boot manager attempts boot options.
For help on the control key sequences you need for this option, refer to the help menu.
• Manage BootNext Setting—Selects a boot option to use one time (the next boot operation)
• Set Automatic Boot Timeout—Defines the value in seconds that pass before the system automatically
boots without user intervention. Setting this value to zero disables the timeout feature.
• Exit—Returns control to the EFI boot manager main menu. This displays the active boot devices,
including a possible integrated shell (if the implementation is so constructed).
EFI Commands
Table 4-1 lists EFI commands for the hp Integrity rx4640 Server. The equivalent BCH commands found in
PA-RISC based systems are also listed.
Table 4-1 EFI Commands
BCH
EFI Shell
Command BCH Command Parameters Definition
Command
Equivalent
34 Chapter 4
Utilities
Extensible Firmware Interface (EFI) Boot Manager
BCH
EFI Shell
Command BCH Command Parameters Definition
Command
Equivalent
MAin
COnfiguration
INformation
Chapter 4 35
Utilities
Extensible Firmware Interface (EFI) Boot Manager
BCH
EFI Shell
Command BCH Command Parameters Definition
Command
Equivalent
SERvice
36 Chapter 4
Utilities
EFI/POSSE Commands
EFI/POSSE Commands
This section describes the EFI/POSSE commands developed for the server.
NOTE EFI and Pre-OS System Environment (POSSE) are similar. EFI is an Intel specification,
whereas POSSE is the HP implementation that aids HP support.
help
Provides information on the EFI shell commands. It also has an additional feature to aid those familiar with
the BCH menus to adjust to their equivalent functions in EFI.
Syntax
help [-b] <category>
help [-b] <cmd>
help [-b] bch <bchmenu> <bchcmd>
Parameters
-b Enable page breaking
category Category of commands to view help on commands
cmd Shell command name on which to provide verbose information
bch Display the list of BCH commands and their corresponding EFI
bchmenu BCH menu name taken from the top level of the BCH menu
bchcmd BCH command on which to display information
Operation
If help is invoked with no parameters, it displays a list of shell command categories. To list all of the
commands within a category, the user should type help <category> (see examples). If invoked with the -b
switch, any output longer than one page pauses after each page is displayed. If a shell command name is used
as a parameter, verbose help is displayed for that command.
If help is invoked with the bch option, it displays a list of BCH commands and their corresponding
EFI/POSSE commands. It instructs the user to repeat the command line followed by a menu name for more
information on that menu. If help is invoked followed by bch and a menu name, it displays a list of commands
that appear under that BCH menu. The user may then invoke help followed by bch, the menu name, and a
BCH command name to display information on that command. This would point the user to the command
that has taken the place of that BCH functionality, or will inform the user that the functionality no longer
exists. As a shortcut, the user may enter help followed by bch and a BCH command name to go straight to
that command.
Chapter 4 37
Utilities
EFI/POSSE Commands
scripts -- EFI shell-script commandsType "help" followed by a class name for a list of commands in
that class
Type "help" followed by command name for full documentation
Type "help" followed by command name for full documentationon that command.
Type "help -a" to display a list of all commands.
Notes:
1. Cpu status will not change until next boot
Examples:
* To deconfigure CPU 0
fs0:\> cpuconfig 0 off
CPU will be deconfigured on the next boot
For more help on one of the commands above, at the prompt type:
help bch COMMAND
38 Chapter 4
Utilities
EFI/POSSE Commands
baud
Sets the baud rate and communication settings for a UART.
Syntax
baud <index> <baudrate>
Parameters
<index> 0 through the total number of UARTS minus one
<baudrate> baud rate.
Operation
This command is used to change the speed for a UART in the system. This command works for all UARTs
visible to EFI/POSSE. If the UART is part of PDH space and is initialized by the core firmware, this command
communicates the settings to core firmware so the UART can be initialized with the new settings on the next
boot. System default is 9600 baud.
Other Communication parameters are listed in Table 4-2.
Table 4-2 Communications Parameters
Parameter Value
RECEIVE_FIFO_DEPTH 1
TIMEOUT 1000000
PARITY No parity
DATA_BITS 8
STOP_BITS 1
CONTROL_MASK 0
boottest
Interacts with the speedy boot variable allowing it to be set appropriately.
Syntax
boottest Displays status of all speedy boot bits
boottest on Run all tests (for a normal boot time)
boottest off Skip all tests (for a faster boot time)
boottest [test] Displays status of specific Speedy Boot bit
boottest [test] [on|off] Sets or clears a specific Speedy Boot bit
Parameters
[test] Each test can be set or cleared:
booting_valid Enable/disable system firmware response to BOOTING
bit. If OS Speedy Boot aware set to on.
early_cpu Enable/disable early CPU selftests.
late_cpu Enable/disable late CPU selftests.
platform Enable/disable system board hardware tests.
chipset Enable/disable CEC tests.
Chapter 4 39
Utilities
EFI/POSSE Commands
cpuconfig
Displays the config/deconfig state of processors in the system and allows the user to configure or reconfigure
processors.
Syntax
cpuconfig <cpu> <on|off>
Parameters
<cpu> specify a processor
<on|off> state to set the processor to
Operation
Issuing cpuconfig with no parameters displays the config/deconfig status of all processors. A user can
reconfigure CPUs by specifying a CPU number and a state (on or off). If a valid state is entered and is
different from the current state of a CPU, its status changes on the next boot. The last remaining configured
CPU in a system cannot be deconfigured.
40 Chapter 4
Utilities
EFI/POSSE Commands
Shell> cpuconfig
PROCESSOR INFORMATION
# of L3 L4 Family/
CPU Logical Cache Cache Model Processor
Slot CPUs Speed Size Size (hex.) Rev State
--- ------- --------- ---- ----- ------ ---- ----------
0 1 1 GHz 3 MB None 1F/00 B2 Active
1 1 1 GHz 3 MB None 1F/00 B2 Active
2 1 1 GHz 3 MB None 1F/00 B2 Sched Deconf
3 1 1 GHz 3 MB None 1F/00 B2 Active
default
Allows the user to restore NVM to default values and clear NVM storage values.
Syntax
default [efi|sal]
default clear [bmc|efi|sal]
Parameters
clear clears NVM storage values
Operation
Default sets NVM and Stable Store values to predefined default values. To the normal user only a subset of
values are available for default. Executing “default clear” resets the system.
errdump
Displays the contents of processor internal memory logged on the first MCA for all processors present in the
system.
Syntax
errdump [mca | cpe | cmc | init | la | clear]
Parameters
mca dumps the Machine Check Abort error log
cpe dumps the Corrected Platform Error log
cmc dumps the Corrected Machine Check log
init dumps the Initialization log
la dumps the Logic Analyzer log
clear erases all of the logs (mca, cpe, cmc, init, la)
Chapter 4 41
Utilities
EFI/POSSE Commands
Operation
If a user enters no parameters, the usage is displayed. Otherwise, the specified error log is displayed. Adding
-n to the clear parameter disables the confirmation prompt. (The errdump command can also be accessed via
the System Configuration menu.)
info
Allows the user to display most system information.
Syntax
info [ -b] [target]
Parameters
target: valid targets are:
all display everything
cpu display information on cpus
cache display information on cache
mem display information on memory
io display information on io
boot display boot-related information
chiprev display information on chip revisions
fw display firmware version information
sys display system information
warning display warning and stop boot information
# of L3 L4 Family/
CPU Logical Cache Cache Model Processor
Slot CPUs Speed Size Size (hex.) Rev State
---- ------- -------- ------ ------ ------- ---- ------- -
0 1 1 GHz 3 MB None 1F/01 B2 Active
1 1 1 GHz 3 MB None 1F/01 B2 Active
2 1 1 GHz 3 MB None 1F/01 B2 Sched Deconf
3 1 1 GHz 3 MB None 1F/01 B2 Active
MEMORY INFORMATION
Extender 0:
--- DIMM A ----- ---- DIMM B ----- ----DIMM C ----- ---- DIMM D -----
DIMM Current DIMM Current DIMM Current DIMM Current
--- ------ ---------- ------ ----------- ------ ---------- ----- -------------
42 Chapter 4
Utilities
EFI/POSSE Commands
I/O INFORMATION
BOOTABLE DEVICES
Order Media Type Path
---- ---------- --------------------------------------------------------------------------------
1 HARDDRIVE Acpi(HWP0002,0)/Pci(2|0)/Scsi(Puno,Luno)/HD(Part1,Sig3D1F1
86A-846F-11D1-FB49BB94A768)
2 HARDDRIVE Acpi(HWP0002,0)/Pci(2|0)/Scsi(Pun2,Luno)/HD(Part1,Sig965900000
3 CDROM Acpi(HWP0002,0)/Pci(2|1)/Scsi(Pun4,Luno)/CDROM(Entry0)
4 HARDDRIVE Acpi(HWP0002,100)/Pci(1|0)/Pci(1|1)Scsi(Pun2,Luno)/HD(Part2,SigA45AC380-2588
-11D6-B48C-806D6172696F)
5 HARDDRIVE Acpi(HWP0002,100)/Pci(1|0)/Pci(1|1)/Scsi(Pun2,Luno)/HD(Part2,Sig9C82CD80-70D
2-4E88-A374-B029EBF1D8E4)
Seg Bus Dev Fnc Vendor Device Slot
# # # # ID ID # Path
--- --- --- --- ------ ------- ---- -------------
00 00 01 00 0x103C 0x1290 01 Acpi(HWP0002,0)/Pci(1|0)
00 00 01 01 0x103C 0x1048 01 Acpi(HWP0002,0)/Pci(1|1)
00 00 02 00 0x1000 0x000B 01 Acpi(HWP0002,0)/Pci(2|0)
00 00 02 01 0x1000 0x000B 01 Acpi(HWP0002,0)/Pci(2|1)
00 00 04 00 0x1011 0x0026 02 Acpi(HWP0002,0)/Pci(4|0)
00 01 04 00 0x1033 0x0035 02 Acpi(HWP0002,0)/Pci(4|0)/Pci(4|0)
00 01 04 01 0x1033 0x0035 02 Acpi(HWP0002,0)/Pci(4|0)/Pci(4|1)
00 01 04 02 0x1033 0x00E0 02 Acpi(HWP0002,0)/Pci(4|0)/Pci(4|2)
00 01 05 00 0x1002 0x5159 02 Acpi(HWP0002,0)/Pci(4|0)/Pci(5|0)
00 20 01 00 0x1014 0x01A7 03 Acpi(HWP0002,100)/Pci(1|0)
00 21 01 00 0x1000 0x0021 03 Acpi(HWP0002,100)/Pci(1|0)/Pci(1|0)
00 21 01 01 0x1000 0x0021 03 Acpi(HWP0002,100)/Pci(1|0)/Pci(1|1)
00 21 04 00 0x14E4 0x1645 03 Acpi(HWP0002,100)/Pci(1|0)/Pci(4|0)
BOOT INFORMATION
Monarch CPU :
Current Preferred
Monarch Monarch Possible Warnings
------- ------- ------------------
0 0
AutoBoot : ON - Timeout is : 7 sev
Boottest :
OS is not speedy boot aware
Selftest Setting
--------- --------------------
early_cpu Skip this test
late_cpu Run this test
platform Run this test
chipset Run this test
io_hw Run this test
mem_init Run this test
mem_test Run this test
Chapter 4 43
Utilities
EFI/POSSE Commands
# of L3 L4 Family/
CPU Logical Cache Cache Model Processor
44 Chapter 4
Utilities
EFI/POSSE Commands
Current Preferred
Monarch Monarch Possible Warnings
-------- --------- ------------------
0 0
Chapter 4 45
Utilities
EFI/POSSE Commands
Selftest Setting
---------- --------------
early_cpu Skip this test
late_cpu Run this test
platform Run this test
chipset Run this test
io_hw Run this test
mem_init Run this test
mem_test Run this test
LAN AddressInformation:
lanaddress
Allows the user to display the core I/O MAC address.
Syntax:
lanaddress
Parameters
none
monarch
Displays or modifies the ID of the bootstrap processor. The preferred monarch number is stored in NVM.
Syntax
monarch <cpu>
Parameters
<cpu> specifies a cpu
Operation
If specified with no parameters, monarch displays the Monarch processor for the system. Specifying a
processor number alters the preferred Monarch processor. None of these changes takes affect until after a
reboot.
46 Chapter 4
Utilities
EFI/POSSE Commands
| Processor
-----------------+-----------
current status | 0
next boot status | 0
| Processor
-----------------+-----------
current status | 0
next boot status | 1
pdt
Displays or clears the contents of the Page Deallocation Table.
Syntax
pdt (clear)
Parameters
<clear> clears the pdt
Operation
With no options specified, the command displays the PDT information for the system. The PDT is cleared and
a reboot is required for memory reallocation and safe booting.
Shell> pdt
PDT Information
Chapter 4 47
Utilities
EFI/POSSE Commands
sysmode
Display or modify the system mode.
Syntax
sysmode <normal | admin| service>
Parameters
<normal> sets system mode to normal
Operation
If specified alone, sysmode displays the system mode. If a mode is specified as a parameter, then the system
mode is changed. This new mode takes effect immediately. The system mode is retained on successive boots.
Interaction with sysmode in a variety of scenarios is outlined below.
48 Chapter 4
Utilities
Specifying SCSI Parameters
info io
A list of all the devices that are installed in the hp Integrity rx4640 Server and managed by EFI
drivers is displayed. The output may look like this:
Seg Bus Dev Fnc Vendor Device Slot
# # # # ID ID # Path
--- --- --- --- ------ ------ --- -----------
00 20 02 00 0x14E4 0x1645 XX Acpi(HWP0002,100)/Pci(2|0)
00 00 01 00 0x1033 0x0035 XX Acpi(HWP0002,0)/Pci(1|0)
00 00 01 01 0x1033 0x0035 XX Acpi(HWP0002,0)/Pci(1|1)
00 00 01 02 0x1033 0x00E0 XX Acpi(HWP0002,0)/Pci(1|2)
00 00 02 00 0x1095 0x0649 XX Acpi(HWP0002,0)/Pci(2|0)
00 00 03 00 0x8086 0x1229 XX Acpi(HWP0002,0)/Pci(3|0)
00 20 01 00 0x1000 0x0030 XX Acpi(HWP0002,100)/Pci(1|0)
00 20 01 01 0x1000 0x0030 XX Acpi(HWP0002,100)/Pci(1|1)
00 40 01 00 0x1000 0x0021 03 Acpi(HWP0002,200)/Pci(1|0)
00 40 01 01 0x1000 0x0021 03 Acpi(HWP0002,200)/Pci(1|1)
00 60 01 00 0x1000 0x0021 02 Acpi(HWP0002,300)/Pci(1|0)
00 60 01 01 0x1000 0x0021 02 Acpi(HWP0002,300)/Pci(1|1)
00 80 01 00 0x8086 0x1229 01 Acpi(HWP0002,400)/Pci(1|0)
00 C0 01 00 0x1000 0x0021 04 Acpi(HWP0002,600)/Pci(1|0)
00 E0 01 00 0x103C 0x1290 XX Acpi(HWP0002,700)/Pci(1|0)
00 E0 01 01 0x103C 0x1048 XX Acpi(HWP0002,700)/Pci(1|1)
00 E0 02 00 0x1002 0x5159 XX Acpi(HWP0002,700)/Pci(2|0)
In the example above, two SCSI boards are in the listing. The information for both channels of both
SCSI boards is shown in bold, for highlighting purposes.
For each channel of the SCSI board, you need to note certain information. As an example, look at
the information for the first SCSI board (the first two bold lines). For each channel of this SCSI
board, note the following information:
• Bus #—identifies the bus the device is on; for the SCSI board, this is the same for both
channels. In this example, the bus number is 40.
• Dev #—the ID the device is assigned on the bus; for the SCSI board, this is the same for both
channels. In this example, the SCSI board is device 01.
Chapter 4 49
Utilities
Specifying SCSI Parameters
• Fnc #—identifies the channel of the device (00 for channel A, 01 for channel B, and so on). In
this example, because the SCSI board has two channels, one channel is 00 and the other is 01.
• Vendor ID—shows the device’s vendor ID; for the SCSI board, this is the same for both
channels. For all SCSI board HBAs, the ID is 0x1000.
• Device ID—shows the device’s device ID; for the SCSI board, this is the same for both
channels. For all SCSI board HBAs, the ID is 0x0021.
• Slot #—identifies the physical card slot in the system where the HBA is installed; for the SCSI
board, this is the same for both channels. In this example, the HBA is in slot 03.
• Path—identifies the device’s path; for the SCSI board, this is the same for both channels. In
this example, the HBA’s path is Acpi(HWP0002,200)/Pci(1|0) for channel A and
Acpi(HWP0002,200)/Pci(1|1) for channel B.
Using the SCSI board’s information from the example above, the pieces of information that,
combined, tell you this is a SCSI board are the following (shown in bold, for highlighting purposes):
00 40 01 00 0x1000 0x0021 03 Acpi(HWP0002,200)/Pci(1|0)
00 40 01 01 0x1000 0x0021 03 Acpi(HWP0002,200)/Pci(1|1)
Looking at all of the above information together, the vendor (0x1000) and device (0x0021) are the
IDs for a SCSI board. Of the devices with those IDs, this device has two channels (Fnc # of 00
immediately followed by Fnc # of 01). Also, this SCSI board has a numeric (non-XX) slot # (03, in
this example).
Step 2. Still at the EFI shell prompt, type this command to obtain the controller’s handle for the SCSI card:
devtree
A tree of all EFI-capable devices installed in the system is displayed. The output could look like
this:
Device Tree
Ctrl[02]
Ctrl[04] Acpi(HWP0002,0)
Ctrl[76] Acpi(HWP0002,0)/Pci(1|0)
Ctrl[77] Acpi(HWP0002,0)/Pci(1|1)
Ctrl[78] Acpi(HWP0002,0)/Pci(1|2)
Ctrl[79] Acpi(HWP0002,0)/Pci(2|0)
Ctrl[7B] Acpi(HWP0002,0)/Pci(2|0)/Ata(Primary,Master)
Ctrl[7A] Acpi(HWP0002,0)/Pci(3|0)
Ctrl[7C] Acpi(HWP0002,0)/Pci(3|0)/Mac(00306E1ECE06)
Ctrl[05] Acpi(HWP0002,100)
Ctrl[32] Acpi(HWP0002,100)/Pci(2|0)
Ctrl[33] Acpi(HWP0002,100)/Pci(2|0)/Mac(00306E1E9EFA)
Ctrl[7D] LSI Logic Ultra320 SCSI Controller
Ctrl[7E] LSI Logic Ultra320 SCSI Controller
Ctrl[06] Acpi(HWP0002,200)
Ctrl[82] LSI Logic Ultra160 SCSI Controller
Ctrl[83] LSI Logic Ultra160 SCSI Controller
Ctrl[07] Acpi(HWP0002,300)
Ctrl[91] LSI Logic Ultra160 SCSI Controller
Ctrl[92] LSI Logic Ultra160 SCSI Controller
Ctrl[08] Acpi(HWP0002,400)
Ctrl[93] Acpi(HWP0002,400)/Pci(1|0)
Ctrl[94] Acpi(HWP0002,400)/Pci(1|0)/Mac(0002B35BE064)
Ctrl[09] Acpi(HWP0002,600)
50 Chapter 4
Utilities
Specifying SCSI Parameters
In the above example, this SCSI board’s information is shown in bold, for highlighting purposes.
You can tell the information is for this SCSI board because the path on the first
line—Acpi(HWP0002,200)— is the HBA’s path from the information displayed by the info io
command. The next two lines are for the SCSI board’s two channels, one line for each channel (they
contain the SCSI board’s description [LSI Logic Ultra160 SCSI Controller]). Note the value shown for
Ctrl—82 and 83—at the beginning of each of those lines; this is the controller’s handle for that
channel. You need to know it for the next step.
Step 3. Still at the EFI shell prompt, type this command to obtain the EFI driver’s handle for the SCSI
card:
drvcfg
A list of all EFI-capable configurable components in the system is displayed. The output may look
like this:
Drv[26] Ctrl[79] Lang[eng]
Drv[34] Ctrl[83] Lang[eng]
Drv[35] Ctrl[82] Lang[eng]
Drv[36] Ctrl[92] Lang[eng]
Drv[37] Ctrl[91] Lang[eng]
Drv[38] Ctrl[95] Lang[eng]
Drv[71] Ctrl[7D] Lang[eng]
Drv[71] Ctrl[7E] Lang[eng]
This listing shows which driver controls which device (controller). In the above example, this SCSI
board’s information is shown in bold, for highlighting purposes. You can tell the information is for
this SCSI board because the values shown for Ctrl—82 and 83—are the controller’s handles for the
SCSI board’s two channels (from the information displayed by the devtree command).
NOTE The EFI driver’s handle values will change on every boot.
TIP From this command (drvcfg), we recommend you record these two pieces of
information for each channel of each SCSI board HBA you want to change the SCSI
parameters for:
Step 4. Using the information (the driver’s handle [Drv] and the controller’s handle [Ctrl]) from the
drvcfg command, start the EFI SCSI Setup Utility for one channel of this SCSI board. Still at the
EFI shell prompt, type this command:
Chapter 4 51
Utilities
Specifying SCSI Parameters
where
• drvr_handle is the handle of the driver that controls the channel whose SCSI ID you want to
display or change
• cntrl_handle is the handle of the controller for the channel whose SCSI ID you want to
display or change
So, continuing the example for channel A of this SCSI board, you would type:
drvcfg -s 35 82
Step 5. The EFI SCSI Setup Utility starts and its main menu is displayed, showing a list of all the EFI
capable HBAs in the system.
TIP To move the cursor in the EFI SCSI Setup Utility, you can use these keys:
• Arrow keys: ¯ ¬ ®
• Alternate keys:
H = left
J = down
K = up
L = right
I = home
O = end
Move the cursor to highlight this channel of this SCSI board; press Enter. (To determine which
channel of the HBA to highlight, match the PCI Bus, PCI Dev, and PCI Func values on this screen
to the Bus #, Dev #, and Fnc # values from the info io command.)
CAUTION Do not select the <Global Properties> option on the main menu.
Step 6. The “Adapter Properties” screen for this channel of this SCSI board is displayed. If you like, you can
make sure the utility is running for this channel of this SCSI board by comparing the values shown
for PCI Bus, PCI Device, and PCI Function to the Bus #, Dev #, and Fnc # values from the
info io command.
CAUTION Do not change the value for any of these fields on the “Adapter Properties” screen:
• Auto Termination
• SCSI Parity
52 Chapter 4
Utilities
Specifying SCSI Parameters
CAUTION Do not change the value for any of these fields on the “Device Properties” screen:
• Scan Id
• Disconnect
• SCSI Timeout
• Queue Tags
• Format
• Verify
Step 7. You may display (and optionally change) any SCSI parameters listed below for this channel of this
SCSI board, or restore its SCSI parameters to their default values.
• SCSI ID
• Bus width
• Restore Defaults
Step 8. Use the arrow keys to navigate to the appropriate SCSI parameter.
Step 9. Use the plus (+) and minus (-) keys to scroll through the values until the value you want is
displayed.
Step 10. Press Esc to exit the “Adapter Properties” screen. You are given these choices:
• Cancel the exit from the screen (to stay in the “Adapter Properties” screen for this channel of
this SCSI board)
• Save the changes you made and then exit the screen
• Discard the changes you made and then exit the screen
Step 11. Move the cursor to the action (cancel, save, or discard) you want to take; press Enter.
If you selected cancel, you remain in the “Adapter Properties” screen for this channel of this SCSI
board. You can still change this channel’s parameters listed above.
If you selected save or discard, you are placed in the EFI SCSI Setup Utility’s main menu.
CAUTION Do not select the <Global Properties> option on the main menu.
Step 12. Press Esc to exit the main menu and the EFI SCSI Setup Utility.
Chapter 4 53
Utilities
Specifying SCSI Parameters
Step 14. When you are prompted to, press Enter to stop this SCSI board; you are now back at the EFI shell
prompt.
reset
The system starts to reboot. This is required to cause the new SCSI setting.
54 Chapter 4
Utilities
Management Processor
Management Processor
The management processor is an independent support system for the server. It provides a way for you to
connect to a server and perform administration or monitoring tasks for the server hardware.
The management processor controls power, reset, Transfer of Control (TOC) capabilities, provides console
access, displays and records system events, and can display detailed information about the various internal
subsystems. The management processor also provides a virtual front panel that can be used to monitor
system status and see the state of front panel LEDs. All MP functions are available via the LAN, local RS-232
and remote RS-232 ports.
The management processor is available whenever the system is connected to a power source, even if the
server main power switch is in the off position.
Access to the management processor can be restricted by user accounts. User accounts are password
protected and provide a specific level of access to the server and management processor commands.
Multiple users can interact with the management processor. From the MP Main Menu users can select any of
the following options: enter management processor command mode, enter console, view event logs, view
console history, display virtual front panel, enter console session, or connect to another management
processor. Multiple users can select different options from the MP Main Menu at the same time. However,
management processor command mode and console mode are mirrored, The MP allows only one user at a
time to have write access to the shared console.
Step 1. Log in using your management processor user account name and password.
NOTE If the management processor is not displaying the MP Main Menu, use CTRL+B to
access the MP Main Menu and the management processor (MP) prompt.
Step 2. Use the management processor menus and commands as needed. A list of available commands can
be displayed by using the management processor help function (in the MP Main Menu, enter HE
followed by LI at the MP HELP: prompt). Log out using the X command (in the MP Main Menu,
enter X at the MP> prompt) when done.
Chapter 4 55
Utilities
Management Processor Command Interface
MP Login: Admin
MP password: *****
Hewlett-Packard Management Processor
(C) Copyright Hewlett-Packard Company 1999-2003. All rights reserved
System Name: xxxxxxxxx
MP MAIN MENU:
CO:Console
VFP:Virtual Front Panel
CM:Command Menu
CL:Console Log
SL:Show Event Logs
CSP:Connect to Service Processor
56 Chapter 4
Utilities
Management Processor Command Interface
Command Description
DC Default configuration
FW Upgrade MP firmware
ID System information
LC LAN configuration
LM License Management
LS LAN Status
MR Modem reset
MS Modem status
PR Power restore
RB Reset BMC
Chapter 4 57
Utilities
Management Processor Command Interface
Command Description
SA Set access
SE Enter OS session
SO Security options
UC User configuration
IMPORTANT Do not mix HP and vt100 terminal types at the same time.
• MODEM PROTOCOL: Bell or CCITT (CCITT is a European standard; RTS/CTS signaling is used, as well
as the Ring signal. Bell is a U.S. or simple mode).
• BAUD RATES: Input and output data rates are the same; 300, 1200, 2400, 4800, 9600, 38400, 115200
bit/sec.
58 Chapter 4
Utilities
Management Processor Command Interface
1. The application takes the terminal information from the OS. This value is set in the CA command and
takes effect for all MP ports.
2. The $TERM shell environment variable.
3. The application directly queries the terminal (in this case, the write enabled terminal establishes the
terminal type).
Make sure that settings #1 and #2 agree with your terminal type.
Console Log
CL: Console Log—view the history of the Console output
This command displays up to 60 Kilobytes of console data (about 60 pages of display in text mode) sent from
the SPU to the Console path and stored for later analysis.
Console data is stored in a buffer in non-volatile memory. Data is displayed from the beginning of the buffer to
end of the buffer.
What is displayed is an image of the console history at the time the CL command is entered. Console output
will continue to be logged while this buffer is read. Nothing will be lost in the meantime.
Command Mode
CM: Command Mode—enter command mode
This command switches the console terminal from the MP Main Menu to mirrored command interface mode.
If the current mux authority is administrator and the new login is as an operator, the command mux will be
denied (remains in MP Main Menu mode). If a command is in progress, a message will be displayed warning
the new user of system status.
Chapter 4 59
Utilities
Management Processor Command Interface
Console
CO: Console—leave command mode and enter console mode
This command switches the console terminal from the MP Main Menu to mirrored/redirected console mode.
All mirrored data is displayed. Type CTRL+B to return to the MP command interface.
For VT100 and HPTERM, verify that the MP setting in the CA command is correct and all mirrored consoles
are of the same terminal type for proper operation.
Date
DATE: Displays the current date, as generated in the MP real-time clock.
Default Configuration
DC: Default Configuration—reset all MP parameters to the default configuration
This command sets all MP parameters back to their default values. The user may reset all or a subset of the
following parameters:
• IP configurations
• Modem configuration
• Paging configuration
• Command Interface configuration
• Disable remote access, security configuration
• Session configuration. For example: setting the security configuration to default erases all users and
passwords.
There are three ways to reset passwords in the MP:
NOTE All user information (logins, passwords, and so on) is erased in methods 2 and 3.
Display FRUID
DF: Display FRUID information
60 Chapter 4
Utilities
Management Processor Command Interface
This command displays FRUID information from the BMC for FRU devices. Information provided includes
serial number; part number; model designation; name and version number; and manufacturer.
DNS Configuration
DNS: Set DNS Configuration
This command allows a user to configure the DNS server settings when DHCP is enabled.
If no DNS server IP addresses are specified, or the DNS domain is undefined, then DNS will not be used.
If an IP address was obtained via DHCP then an add name request will be sent to the DDNS server if enabled
and registered.
MP Firmware Update
FW: Activates MP firmware upgrade mode
This command activates the upgrade mode. This command is only available from the LAN port and the local
serial port.
The upgrade is performed through the MP LAN by ftp, which must be operational. Information required for
the upgrade needs to be entered through the FW command interface.
CAUTION If the upgrade process is interrupted at any time, the core I/O will need to be repaired or
replacd.
Help
HE: Display help for menu or command
This command displays the MP hardware and firmware version identity, and the date and time of firmware
generation. If executed from the MP Main Menu, general information about the MP, and those commands
displayed in the MP Main Menu, will be displayed. If executed in command mode, this command displays a
list of command interface commands available to the user. It also displays detailed help information in
response to a topic or command at the help prompt.
Display System ID
ID: Display/modify system information
This command allows the user to display and modify the following:
Chapter 4 61
Utilities
Management Processor Command Interface
Inactivity Timeout
IT: Inactivity Timeout settings
The session inactivity timeout is up to 1,440 minutes—default is 60 minutes. This timeout prevents sessions
to the system from being inadvertently left open. A session can be started by the SE command. An open
session can prevent users from logging onto the MP through a port and can also prevent system applications
from initiating an outbound connection.
MP inactivity timeout is up to 1,440 minutes—default is 5 minutes. This timeout prevents a user from
inadvertently keeping the MP locked in a MP Command Interface mode preventing other users from looking
at the console output. The MP Command Interface inactivity. timeout may not be deactivated.
Flow control timeout is 0 to 60 minutes. If set to 0, no timeout is applied. This timeout prevents mirrored flow
control from blocking other ports when inactive.
• MP IP Address
• MP IP Address
• DHCP Status
• MP Host Name
• Subnet Mask
• Gateway Address
• Web Console port number
• Link State
• SSH Access Port Number
The MP Host Name set in this command is displayed at the MP command mode prompt. Its primary purpose
is to identify the MP LAN interface in a DNS database.
If the IP address, gateway IP address, or subnet mask were obtained via DHCP, then they cannot be changed
without first disabling DHCP. If the hostname is changed and the IP address was obtained via DHCP and
DDNS is registered then a delete old name request for the old hostname and an add name request for the new
hostname will be sent to the DDNS server.
If the DHCP status is changed from Enabled to Disabled, then the IP address, subnet mask and gateway
address will be set to their default values ([Link]:0xffffff00). Also the DNS parameters are voided. When
the DHCP Status is changed from Enabled to Disabled, the DNS parameters for use DHCP will be set to
Disabled and the Register with DDNS parameter will be set to No. When the DHCP Status is changed from
Disabled to Enabled, the DNS parameters for use DHCP will be set to Enabled and the Register with DDNS
parameter will be set to Yes.
LDAP Configuration
LDAP: LDAP Configuration
This command displays and allows modification of the following LDAP directory settings:
62 Chapter 4
Utilities
Management Processor Command Interface
• LDAP Directory Authentication (Enable or Disable): Designates whether a directory server is used to
authenticate a user login.
• Local MP User database (Enable or Disable): Specifies whether the local MP User database will be used
in case of authentication failure via LDAP Directory. Has to be enabled if LDAP is disabled.
• Directory Server IP Address: Designates the IP address of the directory server. This setting is required if
you directory services are used for user authentication.
• Directory Server LDAP Port: Designates the port used for LDAP communications.
• Object Distinguished Name (DN): Specifies the full distinguished name of the MP Device object in the
directory service.
• For example, CN=RILOE2OBJECT,CN=Users,DC=HP,DC=com. Distinguished names are limited to 256
characters.
• Directory User Search Context 1, 2, 3: Specifies search contexts when authenticating a user. These
settings point to areas in the directory service where users are located so the user does not have to enter
the complete tree structure when logging in. For example, CN=Users,DC=HP,DC=com. Directory User
Contexts are limited to 128 characters each.
License Management
LM: License Management
This command displays the current license status and is used to enter a license key to enable the following
features:
LAN Status
LS: LAN Status
This command displays all parameters and the current status of the MP LAN connections. The LAN
parameters are not modified by the execution of this command.
Modem Reset
MR: Modem Reset
This command makes the MP send an AT Z command to the modem, which resets it. Any modem connections
are lost. The initialization results can be viewed via the MS command.
Modem Status
MS: Modem Status—Display modem status
Chapter 4 63
Utilities
Management Processor Command Interface
The MS command displays the state of the modem lines connected to the remote/modem serial port. The
display can be updated by pressing Enter. The current state of the status signals DCD, CTS, DSR, RI and the
last state of the control signals DTR, RTS set by the firmware are displayed.
Power Control
PC: Power Control—turn system power on and off
For proper system shutdown, shutdown the OS before issuing this command or use the commands graceful
shutdown option.
This command allows you to switch the system power on or off. The user can have the action take place
immediately or after a specified delay.
Notice this is roughly the equivalent to turning the system power off at the front panel switch. There is no
signal sent to the OS to bring the software down before power is turned off. To turn the system off properly.
you must ensure that the OS is in the proper shutdown state before issuing this command. Use the proper OS
commands or use the graceful shutdown option of the Remote Power Control command.
Configure Paging
PG: Paging parameter setup—configures pagers
This command allows the user to configure the pagers and set triggering events.
A string description of the triggering event will be sent with the page.
Power Status
PS: Power status—display the status of the power management module
This command displays on the console the status of the power management module.
Reset BMC
RB: Reset BMC
This command resets the BMC by toggling a GPIO pin.
Reset System
RS: Reset system through RST signal
64 Chapter 4
Utilities
Management Processor Command Interface
IMPORTANT Under normal operation, shut down the OS before issuing this command.
This command causes the system (except the MP) to be reset through the RST signal.
Execution of this command irrecoverably halts all system processing and I/O activity and restarts the
computer system. The effect of this command is very similar to cycling the system power. The OS is not
notified, no dump is taken on the way down, and so on.
Set Access
SA: Set access options—configures access for LAN and remote/modem ports
If a remote/modem, LAN or Web user(s) are connected at the time a disable from this command is executed,
then they are disconnected. Any future incoming connection request to the corresponding port will be
rejected.
Display Logs
SL: Display contents of the system status logs
This command displays the contents of the event logs that have been stored in nonvolatile memory.
Chapter 4 65
Utilities
Management Processor Command Interface
66 Chapter 4
Utilities
Management Processor Command Interface
Severity Definition
2 Informational
3 Warning
5 Critical
7 Fatal
Security Options
SO: Configure security options and access control (users, passwords, and so on)
This command modifies the security parameters of the MP, which include login time-outs and allowed
password faults.
If configured, when you access the MP via the modem port, the MP hangs up and dials the user back. This
does not work if Modem Presence is set to not always connected with the CA command.
If the mode is Single, the State is changed to disabled after the first login.
A disabled user’s login is not accepted.
System Status
SS: Displays the status of the system processors
The SS command displays the status of the system processors and which processor is the monarch.
NOTE At the time of production of this guide, the firmware revisions were:
FIRMWARE INFORMATION
Chapter 4 67
Utilities
Management Processor Command Interface
Transfer Of Control
TC: System reset through INIT or TOC (Transfer of Control) signal
Under normal operation, shut down the OS before issuing this command.
This command causes the system to be reset through the INIT (or TOC) signal. Execution of this command
irrecoverably halts all system processing and I/O activity and restarts the computer system. It is different
from the RS command in that the processors are signaled to dump state on the way down.
Tell
TE: Tell—sends a message to other terminals
Up to 80 characters can be typed in. The message is broadcast to the other mirrored clients. Users in a session
or CSP are not shown the message.
User Configuration
UC: User Configuration—controls user access
This command is used to allow an administrator to add, modify, re-enable or delete any of the following user
parameters.
• Login ID
• Password
• User Name
• User Workgroup
• User Access Right
• User Operating Mode
• User Enabled
• Modem Dial-back
• Modem Dial-back Phone
An MP user will be able to have any (or all) of the following rights:
68 Chapter 4
Utilities
Management Processor Command Interface
• Login Access: Right to login to MP, and execute "Status" or "Read-only" commands (view event logs,
check system status, power status, etc) but not execute any commands that would alter the state of MP or
the system.
• Commands: CL, CSP, DATE, DF, HE, LS, MS, PS, SL, SS, SYSREV, TE, VFP, VDP, WHO, XD (status
options)
• Console Access: Right to access the system console (the host OS). This does not bypass host
authentication requirements, if any.
• Commands: CO, SE
• Power Control Access: Right to power on/off or reset the server, as well as to configure the Power Restore
policy.
• Commands: PC,PR, RS, TC
• Local User Administration Access: Right to configure locally stored user accounts.
Commands: UC
• MP Configuration Access: Right to configure all MP settings (as well as some system settings i.e. "Power
Restore Policy").
• Commands: BP, CA, CG, CL (clear option), DC, DI, FW, ID, IT, LC, LDAP, LOC, MR, PG, RB, SA, SL (clear
option), SO, XD (MP reset option)
Who
WHO: Displays a list of MP connected users
This command displays the login name and operating mode (Main Menu, command, and so on) of the
connected console client users, and the port on which they are connected. For the LAN and WEB console
clients the remote IP address is also displayed.
If the local console client user did not originate the MP command interface session, there is always one
default user listed for the local serial port: local user i. If the local console operator types CTRL+B, then the
login name that the local operator used is displayed instead.
Chapter 4 69
Utilities
Management Processor Command Interface
• MP Parameter Checksum
• Verify I2C connection (get BMC Device ID)
• LAN connectivity test using ping
• Modem self-tests
Also, the MP can be reset from this command. A MP reset can be safely performed without affecting the
operation of the server.
MP Help System
Use Ctrl-B to exit MP command interface and return to the main MP menu:
Q : Quit help
Enter one of the commands described above: OV, LI, <command>, TOP, HE, Q
70 Chapter 4
5 Troubleshooting
Troubleshooting Tips
WARNING Before removing a cover to service components that cannot be hot-swapped, always
disconnect the AC power cords and unplug telephone cables. Disconnect telephone
cables to avoid exposure to shock hazard from telephone ringing voltages.
Disconnect the AC power cords to avoid exposure to high energy levels that may
cause burns when parts are short-circuited by metal objects such as tools or jewelry.
CAUTION Do not operate the HP Server for more than 10 minutes with any cover (including power
supplies and disk drives) removed. Otherwise, damage to system components may result due to
improper cooling airflow.
However, you can safely remove a cover while the HP Server is running to remove and replace
PCI hot-plug boards. For any other service activity requiring access to the system board or
power distribution board, power-down the HP Server and observe all safety precautions.
Troubleshooting Methodology
Step 1. This is the entry point to the troubleshooting process. Here, you pick from a set of symptoms,
ranging from very simple (System LED is blinking) to the most difficult Machine Check Abort
(MCA) has occured. The following is a list of symptom examples:
Step 2. This step narrows down the observed problem to the specific troubleshooting procedure required.
Here you isolate the failure to a specific part of the server so that you can perform more detailed
troubleshooting. For example:
— Analyze the alert by using the system event log (SEL) to identify the last error logged by
the baseboard management controller. Use either the EFI shell command line interface
(CLI) or the optional management processor card is installed, use the MP commands to
view the SEL.
Chapter 5 71
Troubleshooting
Troubleshooting Tips
Step 3. At this point you will have a good idea about which area of the system requires further analysis.
For example, if the symptom was “system will not power-up” then the initial troubleshooting
procedure may have indicated a problem with the DC power supply not coming up after the power
switch was turned on.
Step 4. You have now reached the point where the failed Field Replaceable Unit (FRU or FRUs) have been
identified and need to be replaced. You must now perform the specific remove-and-replace
verification steps.
NOTE If multiple FRUs are identified as part of the solution, a fix cannot be guaranteed
unless all identified failed FRUs are replaced.
Step 5. There may be specific recovery procedures you need to perform to finish the repair. For example, if
the display panel is replaced, you will need to restore customer-specific information.
72 Chapter 5
Troubleshooting
Possible Problems
Possible Problems
This section contains example HP Server problems and their possible solutions.
Step 3. Verify that 200-240 VAC power is available at the AC power receptacle. Check the receptacle output
with another device.
Step 4. Check the power supply fans to see if they are operating. The fans will operate off the DC voltage
generated by the power supply.
Step 5. Check that the Power LED on Front Control Panel is illuminated. See“Front Control Panel LEDs”
on page 76.
Step 6. Check all connections from the power supply to the power distribution module.
Step 7. Verify that all cables and modules are correctly connected. Especially check the display panel
connection.
Step 8. If the system starts to power-on and then power-off, a voltage rail of the power supply may be out of
specification. The BMC monitors voltages and prevents power-on when power values are out of
specification.
Step 2. Examine the QuickFind Diagnostic Panel for indications of specific warning or fault indications.
The diagnostic LEDs present patterns that categorize the source of the warning or fault. See
“QuickFind Diagnostic Panel LEDs” on page 78.
Step 3. Display and examine the system event log (SEL) and forward progress log (FPL) for further
information relating to warning or fault isolation.
Step 5. Use the MP command to cycle the system power: pc off, pc on.
Step 6. Turn the server off, wait at least twenty seconds, then turn the server back on to see if the failure
can be cleared.
Step 8. Check that the DIMM configuration on the system board matches those approved. A minimum of
one DIMM pair must be installed.
Chapter 5 73
Troubleshooting
Possible Problems
Step 9. Verify that the DIMMs are fully seated. When the DIMM is fully seated in the mating connector,
the retaining latches are closed (they should be flush with the front of the DIMM). If the latches are
not closed, reseat the DIMM fully by engaging the retaining latches and closing them fully.
Step 10. Check that the processors are installed in the correct sockets and that each processor has a power
pod installed. Also verify that the processors are of the same type.
Step 11. Check the boot order with the SCSI configuration utility.
Step 12. If there are no obvious errors, reflash the BMC firmware, Refer to Chapter 4, “Utilities.”
Step 13. If the system will still not boot, it may be necessary to replace the base unit.
Step 2. Examine the QuickFind Diagnostic Panel for indications of specific warning or fault indications.
The diagnostic LEDs present patterns that categorize the source of the warning or fault. See
“QuickFind Diagnostic Panel LEDs” on page 78.
Step 3. Display and examine the system event log (SEL) and forward progress log (FPL) for further
information relating to warning or fault indications.
Step 4. Make sure that the system fan assemblies are fully seated.
Step 5. Verify that the server is plugged into a power source that is within specifications described on the
label of the power supply.
Step 6. Make sure that the internal SCSI chain is terminated and that termination is not enabled on any of
the drives. Note that LVD SCSI termination is provided on the cable.
Step 7. Check that the processors are installed in the correct sockets and that terminators are installed in
all unused sockets.
Step 9. If date and time or customer settings are being cleared, the system board battery may need to be
replaced.
The system LED or Diagnostic LEDs are not on and no error messages appear.
If the server does not work (with no LEDs illuminated) and no error messages appearing, check the following:
Step 1. Make sure that all cables and the AC power cord are plugged into their proper receptacles.
Step 2. Make sure that the AC outlet is working. If the server is plugged into a switched multiple-outlet
box, make sure that the switch on the outlet box is turned on.
Step 3. Make sure that the server is turned on (the power-on light should be green and the fans should be
on).
Step 4. Turn the server off, wait at least twenty seconds, then turn the server back on to see if the failure
can be cleared.
74 Chapter 5
Troubleshooting
Possible Problems
Step 5. Make sure that all boards are installed properly and the processors are installed in the correct slot.
They must be seated firmly in their slots and any cables must be connected firmly.
Step 6. If the server stopped working after you installed a new board, remove the board and turn on the
server. If your server now works, check the installation instructions received with the new board for
correct installation method. If the new board is preventing the server from powering on, it is likely
to have a serious electrical problem.
Step 7. If the server still does not work, remove all boards and options that you have installed (do not
remove the hard disk drives) and turn on the server.
Step 8. Add boards and options one at a time to determine which one is causing the problem.
Step 9. If you have added any memory, make sure that the DIMMs are seated properly in the board. Also
check the DIMM configuration, and that the DIMMs are matched pairs.
Power goes off on the server and does not come back on.
When certain critical conditions exist, the server shuts down all power.
The critical conditions that may shut down the server are:
Step 1. Examine the front panel LEDs for warning or fault indications. The system LED will be flashing
yellow with a warning indication and flashing red with a fault indication. See “Front Control Panel
LEDs” on page 76.
Step 2. Examine the QuickFind Diagnostic Panel for indications of specific warning or fault indications.
The diagnostic LEDs present patterns that categorize the source of the warning or fault. See
“QuickFind Diagnostic Panel LEDs” on page 78.
Step 3. Check to make sure power is getting to the server. Plug a known working device into the power
outlet.
Step 4. Check for proper ventilation for the server. The server should have at least three inches of space
around the front and rear for proper airflow when installed in a rack.
Step 5. Check the system specifications and make sure the environmental temperature and voltage are in
the specified guidelines.
Step 6. Monitor the system to make sure you are not experiencing further temperature and voltage
problems.
Chapter 5 75
Troubleshooting
Troubleshooting Using LED Indicators
System LED
Power LED
Power Button Disk LED
TOC/NMI Button Thermal LED
Locator
Button/LED
LED/
State Flash Rate Color Description
Button
System Fault Flashing at Red Flashing red: hard fault, system halted
2 Hz
76 Chapter 5
Troubleshooting
Troubleshooting Using LED Indicators
LED/
State Flash Rate Color Description
Button
Chapter 5 77
Troubleshooting
Troubleshooting Using LED Indicators
Processor Socket 0 Socket Socket Socket If the System LED (on front panel) is in the
1 2 3 attention or fault state and the processor
LED is on, then the processor or voltage
regulator has failed—the processor module
in the specified socket needs to be replaced.
Subsystem CPU Memory I/O n/a A soldered voltage regulator has failed—the
board board board specified board must be replaced.
I/O VRM 12 volt 5 volt 3 volt n/a A plug-in voltage regulator has
failed—specific VRM must be replaced.
Memory DIMM DIMM DIMM DIMM The specified DIMM has failed—the DIMM
Bank X (0-7) xA xB xC xD must be replaced.
Check Power n/a n/a n/a One of the power supply or power supply
Supply fans have failed—replace the power supply.
The faulty power supply LED (located on
Power supply) will be lit.
Memory n/a n/a n/a The DIMMs in a rank are mismatched. All
Config Error the DIMMs in the specified rank (0-7) will
be lit.
78 Chapter 5
Troubleshooting
Troubleshooting Using LED Indicators
System n/a n/a n/a The internal temperature of the server has
Temp exceeded the warning or critical level.
Check Event n/a n/a n/a An event has occurred that requires
Log attention.
Chapter 5 79
Troubleshooting
Troubleshooting Using LED Indicators
Battery
3.3VSB
Power
LED
BMC
Reset
Button
PCI Attention
LED 6X
PCI Attention
Button (Doorbell)
5V VRM 6X
LED PCI Power LED
MP Soft 6X
Reset
Button
MP Heartbeat LED 3.3V VRM LED PCI Attention LED 6X
MP Self-Test BMC Heartbeat LED Locator Button/LED
LED
80 Chapter 5
Troubleshooting
Troubleshooting Using Online Support Tools
Chapter 5 81
Troubleshooting
Troubleshooting Using Online Support Tools
CSTM>
Step 2. To verify the system operation, type the following at the CSTM> prompt:
CSTM> verify all
Step 3. Press Enter to return to CSTM> prompt after all test results are reported.
82 Chapter 5
Troubleshooting
Troubleshooting Using Offline Support Tools
• Offline Diagnostic Environment (ODE)—available on IPF Offline Diagnostics on the resource CD that
comes with your HP Server.
• e-Diagtools—available from IPF Offline Diagnostics on the resource CD that comes with your server.
NOTE For machines using HP-UX the HP service partition is not available and the IPF Offline
Diagnostics CD must be used.
• Management Processor (MP) event logs—available by logging on to the management processor via the
MP LAN or MP remote serial connectors.
Step 1. Power on your HP Server and insert the IPF Offline Diagnostics CD.
Step 2. Do not permit the server to boot into an operating system and at the EFI boot manager, select EFI
shell.
Step 3. Determine the file system that represents the CD and enter the appropriate command to access the
CD.
e-Diagtools
e-Diagtools is used to evaluate the hardware integrity of your HP Server. To access e-Diagtools from the IPF
Offline Diagnostics CD, perform the following steps:
Step 1. Power on your HP Server and insert the IPF Offline Diagnostics CD.
Step 2. Do not permit the server to boot into an operating system and at the EFI boot manager, select EFI
shell.
Step 3. Determine the file system that represents the CD and enter the appropriate command to access the
CD.
Step 4. After accessing the CD diagnostic menu, launch e-Diagtools for IPF and run the basic and
advanced tests according to the menus.
***************************************************************************
****** ******
****** ******
Chapter 5 83
Troubleshooting
Troubleshooting Using Offline Support Tools
****** ******
****** HP shall not be liable for any damages resulting from the ******
****** ******
****** ******
***************************************************************************
ODE> ls
-----------------------------------------------------------------------------
ODE>
NOTE The MP interface must be accessed from a terminal console that is attached to the MP via the
MP LAN or MP remote serial connector.
84 Chapter 5
Troubleshooting
Troubleshooting Using Offline Support Tools
Step 3. Press cl to display the console logs. This log displays console history from oldest to newest.
Step 4. Press sl to display the system logs. The system logs consist of:
• System event
• Forward progress
• Current boot
• Previous boot
• Live events
Step 5. For a complete explanation of the management processor and all commands see Chapter 4,
“Utilities.”
Slot Path
Slot 1 Acpi(HWP0002,100)/Pci(1|0)
Slot 2 Acpi(HWP0002,100)/Pci(1|1)
DVD Acpi(HWP0002,0)/Pci(3|0)
Slot 1 Acpi(HWP0002,100)/Pci(2|0)
Slot 2 Acpi(HWP0002,100)/Pci(1|0)
Slot 3 Acpi(HWP0002,400)/Pci(2|0)
Slot 4 Acpi(HWP0002,400)/Pci(1|0)
Slot 5 Acpi(HWP0002,500)/Pci(2|0)
Slot 6 Acpi(HWP0002,500)/Pci(1|0)
Slot 7 Acpi(HWP0002,200)/Pci(1|0)
Slot 8 Acpi(HWP0002,600)/Pci(1|0)
Chapter 5 85
Troubleshooting
Troubleshooting Using Offline Support Tools
— MCA analyzer
• Event logs not generated by the management processor include:
errdump mca
errdump cmc
errdump cpe
86 Chapter 5
6 Specifications
Introduction
This chapter provides the power requirements, operating conditions (environmental requirements), physical
requirements, hardware specifications, and video resolutions of the hp Integrity rx4640. The following tables
provide the specifications required for normal operation of the hp Integrity rx4640.
NOTE The specifications and requirements for the power supply and environment can vary if you
install a mass storage device in the server that has more stringent environmental limits than
required for the HP Server. Ensure that the operating environment for any mass storage
devices you intend to install are compatible with the server environmental requirements.
Hardware Specifications
Table 6-1 Hardware Specifications
Memory Supports up to eight Double Data Rate (DDR) registered ECC Memory, in PC1600
DIMMs. Supported DDR DIMM sizes: 128MB, 256MB, 513MB, 1GB, 2GB, and
4GB. Requires DIMMs to be added in quads of equal capacity.
Video Embedded
SCSI Integrated Ultra-3 SCSI dual channel controller; 80 MB/s transfer rate with two
68-pin connectors.
LAN PCI Gigabit, Fast Ethernet Controller; with Wake-on-LAN enabled/disabled via
BIOS setup.
Core I/O Three serial ports, 2 USB ports, Integrated RJ-45 LAN .
Chapter 6 87
Specifications
Introduction
Power Supply 1+1 configuration, redundant 200-240 VAC power supply (optional).
88 Chapter 6
Specifications
Dimensions and Weights
Dimension Value
Chapter 6 89
Specifications
Dimensions and Weights
90 Chapter 6
Index
A H
adapter handle
slot number, determining with info command, 50 controller, determining, 51
Hot-Plug disk drives
B LEDs, 16
Boot
EFI boot manager, 33 I
info command
C adapter path, determining, 50
commands adapter slot number, determining, 50
devtree Instant Support Enterprise Edition, ISEE, 82
controller handle, determining, 51
EFI-capable devices and controller handles, L
displaying, 50 LEDs
drvcfg Control Panel, 15
EFI configurable components, displaying, 51 DVD, activity, 17
EFI driver handle, determining, 51 locations and functions, 13
EFI SCSI Setup Utility, starting, 51 Power supply status, 23
info
adapter slot number, determining, 50 M
adapter’s path, determining, 50 Management processor
configurable components, EFI capable, displaying, 51 accessing, 55
controller handle, determining, 51 commands, 56
LEDs, 24
D
devtree command N
controller handle, determining, 51 NMI Button, 16
EFI-capable devices and controller handles,
displaying, 50 O
Dimensions
hp Integrity rx4640, 89 Offline Diagnostic Environment, ODE, 83
drvcfg command
EFI configurable components, displaying, 51 P
EFI driver handle, determining, 51 path, determining for adapter
EFI SCSI Setup Utility, starting, 51 with info command, 50
dump capture, 16 Pinouts
Connector, 27
E LAN, 30
E-Diag Tools, 83 SCSI Port, 31
EFI Power Button, Main, 16
capable devices
and controller handles, displaying, 50 Q
configurable components, displaying, 51 QuickFind Diagnostic Panel
driver handle, determining, 51 LEDs, 17
EFI SCSI Setup Utility
starting, 51 S
Event logs SCSI
CMC, 85
setup utility, 49
CPE, 85 specifying parameters, 49
Management processor, 84
SCSI adapter
MCA, 85 path
Event Monitoring Service, EMS, 82 determining with info command, 50
Extensible Firmware Interface
commands, 34 slot number of adapter, determining with info
command, 50
Extensible Firmware Interface, EFI, 33 Specifications
dimensions and weights, 89
G Hardware, 87
Gigabit Ethernet card LAN LEDs, 25 Support Tools Manager, 81
91
Index
T
Troubleshooting
Online Support Tools, 81
system I/O board, 80
U
Universal Serial Bus, 27
92