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 your server. It
contains a complete documentation set for the server, including localized versions of key documents. Included
on the CD-ROM are the Site Preparation, Operations, and Maintenance guides, which contain in-depth
troubleshooting, installation, and repair information.
The CD will autorun when you insert it into a Windows® workstation, or, point your browser at the
index.htm 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 versions of these documents, and any updates to these documents, are posted under
the appropriate server at http://docs.hp.com.
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 http://www.hp.com/support.
This document describes how to operate your hp Integrity rx1620 Server, Regulatory Model Number:
RSVLA-0406.
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 http://docs.hp.com.
What’s in This Document
The hp Integrity rx1620 Operations Guide contains these chapters:
•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 utilize the extensible firmware interface (EFI)
and management processor commands.
•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.
•Appendix A, “Event, Error, and Warning Messages.” Use this appendix to learn more about event,
error, and warning messages.
•Appendix B, “System Information.” Use this appendix to learn the basic system information of your
HP Server.
Typographical Conventions
This document uses the following conventions.
TitleThe 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
11
About This Document
Related Documents
Related Documents
The HP Server Documentation CD-ROM has been provided with your server. It contains a complete
documentation set for the server, including localized versions of key documents. Included on the CD-ROM are
the Site Preparation, Operations, and Maintenance guides, which contain in-depth troubleshooting,
installation, and repair information.
The CD will autorun when you insert it into a Windows workstation, or, point your browser at the index.htm
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 http://docs.hp.com.
HP Encourages Your Comments
HP encourages your comments concerning this document. We are truly committed to providing
documentation that meets your needs.
Please send any comments by contacting us at http://docs.hp.com/assistance/index.html.
Please include document title, manufacturing part number, and any comment, error found, or suggestion for
improvement you have concerning this document.
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
http://www.hp.com/support.
For the latest information on HP-UX patches, check the HP IT Resource Center at http://itrc.hp.com.
Information to Collect Before You Contact Support
Before you contact HP support, you should:
Step 1. Check information on troubleshooting and attempt to solve the problem. See Chapter 5,
“Troubleshooting.”
12
•Note failure symptoms and error indications (LEDs and messages) by checking the SEL and
FPL logs.
•Try to determine precisely what did or did not happen.
Chapter 1
Step 2. Collect the following information:
•The model number of your server (for example, rx1620).
•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.
Step 3. Become familiar with your system configuration:
•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?
•What accessories are installed?
Step 4. Determine the following:
•Which firmware versions are in use?
•When did the problem start?
About This Document
Where to Get Help
•Have recent changes been made to the system?
•Which operating system and version is in use?
Chapter 1
13
About This Document
Where to Get Help
14
Chapter 1
2Controls, Ports and Indicators
This chapter describes the controls, ports, and indicators found on the front panel, rear panel, and internal
locations of the hp Integrity rx1620 Server. The hp Integrity rx1620 Server is designed to be rack mounted.
Control Panel
The control panel of the hp Integrity rx1620 Server provides the controls and indicators commonly used for
operation.
Figure 2-1Front View
DVD Drive Control Panel
0
1
LVD HDD 2LVD HDD 1
Figure 2-2Control Panel
System
LED
LAN
LED
Power On/Off
Button
Locator
Button and
LED
LED 2LED 4
LED 1LED 3
Diagnostics
LEDs
Table 2-1Control Panel LEDs and Switches
NameFunction
Power On/Off
LED
Power On/Off
Button
The green on/off LED is illuminated when the power is on.
This is the power on/off switch for the server.
System Product
Label
Power On/Off
LED
Chapter 2
15
Controls, Ports and Indicators
Control Panel
Table 2-1Control Panel LEDs and Switches (Continued)
NameFunction
System LEDThe System LED provides information about the system status. When the system is
running code other than Operating System, the LED is flashing green. When operation
is normal, the LED is green. When there is a system warning, the LED is flashing yellow.
When there is a system fault, the LED is flashing red.
LAN LEDThe LAN LED provides status information about the LAN interface. When the LAN LED
is flashing, there is activity on the LAN.
a
Diagnostic
LED 1
Diagnostic
LED 2
Diagnostic
LED 3
Diagnostic
LED 4
Locator
Button and
LED
The four diagnostic LEDs operate in conjunction with the system LED to provide
diagnostic information about the system.
a
The four diagnostic LEDs operate in conjunction with the system LED to provide
diagnostic information about the system.
a
The four diagnostic LEDs operate in conjunction with the system LED to provide
diagnostic information about the system.
a
The four diagnostic LEDs operate in conjunction with the system LED to provide
diagnostic information about the system.
a
The locator button and LED are used to help locate this server within a rack of servers.
When the button is engaged, the blue LED illuminates and an additional blue LED on
the rear panel of the server illuminates. This function may be remotely activated.
a. See Chapter 5, Troubleshooting, for details on information provided by the system and diagnostic
LEDs.
16
Chapter 2
Controls, Ports and Indicators
Additional Controls and Indicators
Additional Controls and Indicators
The hp Integrity rx1620 Server can have up to two low-voltage differential (LVD), 3.5 inch form factor hard
disk drives installed. These hard disk drives have LEDs that provide status and activity information.
Hard Disk Drive Indicators
The hard disk drives have two LEDs per drive, as described below.
•Activity LED—The Drive Activity LED is green and indicates disk drive activity. This LED is directly
controlled by the disk drive and turns on when a drive is accessed.
•Status LED—The Drive Status LED is not used on the hp Integrity rx1620.
Figure 2-3Hard Disk Drive LED Indicators
Status LED
(not used)
Table 2-2Hard Disk Drive LED Definitions
LEDActivityDescription
Status LEDNoneNot Used
Activity LEDFlashing greenDrive access under hard drive control
Activity LED
Chapter 2
17
Controls, Ports and Indicators
Additional Controls and Indicators
Optional Removable Media Drive
The hp Integrity rx1620 Server is delivered without a removable media drive. Either a DVD or CD-RW/DVD
drive may be added. Each of these optional devices has one activity LED.
Figure 2-4DVD
DVD
Eject ButtonActivity LED
Table 2-3DVD Drive LED Definitions
LEDActivityDescription
Activity LEDFlashing greenDrive activity
Emergency Eject
18
Chapter 2
Controls, Ports and Indicators
Rear Panel
Rear Panel
The hp Integrity rx1620 Server rear panel includes communication ports, I/O ports, AC power connector, and
the locator LED/button.
Figure 2-5Rear View
Optional
Management Board
Connectors
AC Power
Receptacle
10/100
LAN C
10/100/1000
LAN A 1Gb
LVD/SE SCSI
Video
10/100/1000
LAN B 1Gb
Serial
Serial
ToC
Locator Button
and LED
USB
PCI Slot 1
PCI Slot 2
Table 2-4Rear Panel Connectors and Switches
Connector/SwitchFunction
AC PowerPrimary power connection for the server
LVD/SE SCSI68-pin, low-voltage differential, single-ended U320 SCSI. This connector provides
external SCSI connection on SCSI Channel B.
10/100/1000 LAN A10/100/1000 base-T ethernet LAN A 1Gb connector
10/100/1000 LAN B10/100/1000 base-T ethernet LAN B 1Gb connector
Serial9-pin male serial connector — this is the console connector if the optional
management processor card is not installed.
USBTwo Universal Serial Bus (USB 2.0) connectors
ToCTransfer of Control button. Halts all system processing and I/O activity and
restarts the computer system.
Locator Button and
LED
The locator button and LED are used to help locate a server within a rack of
servers. When the button is engaged, the blue LED illuminates and an additional
blue LED on the front panel of the server illuminates. This function may be
remotely activated.
Video (optional)15-pin female video connector for the optional management processor card
Chapter 2
19
Controls, Ports and Indicators
Rear Panel
Table 2-4Rear Panel Connectors and Switches (Continued)
Connector/SwitchFunction
Serial (optional)25-pin female serial data bus connector for the optional management processor
card
10/100 LAN C
(optional)
10 Mb/100 Mb LAN C connector for the optional management processor card
10/100/1000 base-T ethernet LAN A 1Gb Connector
The rear panel 10/100/1000 base-T ethernet LAN A 1Gb connector has the following status and activity
LEDs.
Figure 2-610/100/1000 base-T ethernet LAN A 1Gb Connector LEDs
Not used
1000BT
100BT
Activity
Table 2-5 10/100/1000 base-T ethernet LAN A 1Gb Connector LEDs
LAN LEDLocationColorState
Not usedTopNoneNone
1000mb2nd from topAmberBlinking amber – the 1000 Mbps with ethernet protocol and
twisted-pair wiring is enabled.
Off – no link.
100mb2nd from bottomGreenBlinking green – the 100 Mbps with ethernet protocol and
twisted-pair wiring is enabled.
Off – no link.
ActivityBottomGreenBlinking green – the Activity LED lights, and all other
LEDs are off for a 10 Mbps connection.
Off – no activity
20
Chapter 2
Controls, Ports and Indicators
Rear Panel
10/100/1000 base-T ethernet LAN B 1 Gb Connector
The rear panel 10/100/1000 base-T ethernet LAN B 1 Gb connector has the following status and activity
LEDs.
Figure 2-710/100/1000 base-T ethernet LAN B 1Gb Connector LEDs
LED
Link LED
Table 2-610/100/1000 base-T ethernet LAN B 1Gb Connector LEDs
LocationLEDStatus
LeftOff
Green
Right
(link LED)
Off
Red
1000 MHz no link
1000 MHz with Ethernetand twisted-pair wiring enabled
No link
10/100/1000 MHz with Ethernetand twisted-pair wiring enabled
Chapter 2
21
Controls, Ports and Indicators
Rear Panel
Optional Management Processor Card LAN C 10/100 Connector LEDs
The optional management processor LAN C uses an RJ-45 type connector. This connector has four LEDs that
signal status and activity.
Figure 2-8Optional Management Processor Card LAN C 10/100 Connector LEDs
Self-test
10BT
100BT
Standby power
Table 2-7Optional Management Processor Card LAN C 10/100 Connector LEDs
LAN LEDLocationColorState
Self-testTopYellowManagement processor
running selftest or error
OffManagement processor has
booted
10BT2nd from topGreen10BT link established
Blinking green10BT activity
OffNo link or 100BT link
100BT2nd from bottomGreen100BT link established
Blinking green100BT activity
OffNo link or 10BT link
Standby
Power
BottomGreenStandby power on
OffStandby power off
22
Chapter 2
3External Connectors
This chapter describes the external connectors provided on the hp Integrity rx1620 Server.
Connector Pinouts
The following ports and connectors are found on the rear panel of the hp Integrity rx1620 Server.
•Dual USB 2.0
•Serial
•68-pin LVD, SE U320 SCSI
•10/100/1000 LAN
•AC power receptacle
Figure 3-1Rear View of Server
Optional
Management Board
Connectors
AC Power
Receptacle
10/100
LAN C
10/100/1000
LAN A 1Gb
LVD/SE SCSI
Video
10/100/1000
LAN B 1Gb
Serial
Serial
TOC
Locator Button
and LED
USB
PCI Slot 1
PCI Slot 2
Half size
Chapter 3
23
External Connectors
Universal Serial Bus (USB) Ports
Universal Serial Bus (USB) Ports
Figure 3-2Dual USB Port Connector
1234
1234
Table 3-1USB Pinouts
Pin NumberSignal Description
1+5VDC
2MR
3PR
4Ground
Serial Port
Figure 3-3Serial Port Connector
12345
6789
Table 3-2Serial Port Pinouts
Pin NumberSignal Description
1Data Carrier Detect
2Receive Data
3Transmit Data
24
Chapter 3
Table 3-2Serial Port Pinouts (Continued)
Pin NumberSignal Description
4Data Term Ready
5Ground
6Data Set Ready
7Request to Send
8Clear to Send
9Ring Indicator
SCSI Port, Ultra 3, 68-Pin
External Connectors
SCSI Port, Ultra 3, 68-Pin
A single, Ultra 3, 68 pin SCSI connector is located at the rear panel of the server. The external connector
supports SCSI channel “B.”
The hp Integrity rx1620 Server has 3 different LAN connectors. They are:
•10/100/1000 base-T ethernet LAN A Gb connector
•10/100/1000 base-T ethernet LAN A Gb connector
•Optional 10/100 MP card
10/100/1000 base-T ethernet LAN A 1Gb Connector
The rear panel 10/100/1000 base-T ethernet LAN A 1Gb connector has the following status and activity
LEDs.
Figure 3-510/100/1000 base-T ethernet LAN A 1Gb Connector LEDs
Not used
1000BT
100BT
Activity
Table 3-41Gb LAN A Connector LEDs
LAN LEDLocationColorState
Not usedTopNoneNone
1000mb2nd from topAmberBlinking amber – the 1000 Mbps with ethernet protocol and
twisted-pair wiring is enabled.
Off – no link.
100mb2nd from bottomGreenBlinking green – the 100 Mbps with ethernet protocol and
twisted-pair wiring is enabled.
Off – no link.
ActivityBottomGreenBlinking green – The Activity LED lights, and all other
LEDs are off for a 10 Mbps connection.
Off – no activity
Chapter 3
27
External Connectors
LAN Connectors
10/100/1000 base-T ethernet LAN B 1Gb Connector
The rear panel 10/100/1000 base-T ethernet LAN B 1Gb connector has the following status and activity
LEDs.
Figure 3-610/100/1000 base-T ethernet LAN B 1Gb Connector LEDs
LED
(not used)
Link LED
Table 3-510/100/1000 base-T ethernet LAN B 1Gb Connector LEDs
Link LEDOutput
ActivityBlinking Orange
Link w/no activitySolid Orange
No linkOff
28
Chapter 3
External Connectors
LAN Connectors
Optional Management Processor Card LAN C 10/100 Connector LEDs
The optional management processor LAN C uses an RJ-45 type connector. This connector has four LEDs that
signal status and activity.
Figure 3-7Optional Management Processor Card LAN C 10/100 Connector LEDs
Self-test
10BT
100BT
Standby power
Table 3-6Optional Management Processor Card LAN C 10/100 Connector LEDs
LAN LEDLocationColorState
Self-testTopYellowManagement processor
running selftest or error
OffManagement processor has
booted
10BT2nd from topGreen10BT link established
Blinking green10BT activity
OffNo link or 100BT link
100BT2nd from bottomGreen100BT link established
Blinking green100BT activity
OffNo link or 10BT link
Standby
Power
BottomGreenStandby power on
OffStandby power off
Chapter 3
29
External Connectors
LAN Connectors
30
Chapter 3
4Utilities
Extensible Firmware Interface (EFI) Boot Manager
EFI (Extensible Firmware Interface) is an OS and platform-independent boot and pre-boot interface. EFI lies
between the OS and platform firmware, allowing the OS to boot without having details about the underlying
hardware and firmware. EFI supports boot devices, uses a flat memory model, and hides platform and
firmware details from the OS.
NOTEEFI 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 similar to those 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.
Figure 4-1EFI Boot Sequence
EFI
Platform
Init
Standard
firmware
platform
initialization
Driver
EFI Image
Load
Drivers and
application
loaded
iteratively
Application
Application Program
Interface (API) specified
EFI
EFI
Bootcode
Retry
Failure
EFI
OS Loader
Load
Boot from
ordered list
of EFI OS
loaders
Value add implementation
OS Loader
EFI API
Boot Services
Ter minate
Operation
handed off to
OS Loader
Chapter 4
Boot managerEFI transfers
31
Utilities
Extensible Firmware Interface (EFI) Boot Manager
The EFI boot manager loads EFI applications (including operating system [OS] first stage loader) and EFI
drivers from an EFI-defined file system or image loading service. Non-volatile RAM (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, see “Using the Boot Option
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).
32
Chapter 4
Utilities
Extensible Firmware Interface (EFI) Boot Manager
EFI Commands
Table 4-1 lists EFI commands for the hp Integrity rx1620 Server. The equivalent BCH commands found in
PA-RISC based systems are also listed.
Table 4 -1EFI Com m ands
BCH
EFI Shell
Command
These commands are found in all other menus
info bootBoot[PRI|HAA|ALT|<path>]Boot from specified path
help <command>HElp[<menu>|<command>]Display help for specified
resetRESETReset the system (to
Command
Equivalent
(PA-RISC)
BCH Command Parameters
(PA-RISC)
Definition
command or menu
allow reconfiguration of
complex
exit (at EFI shell)MAinReturn to the main menu
MAin
EFI boot manager
“change boot
order”
bcfg SEArch[ALL]Search for boot devices
bcfg SEArch[DIsplay|IPL] [<path>]Search for boot devices
many commands
offer a [-b]
parameter to cause
25 line breaks
COnfiguration
autobootAUto[BOot|SEarch|STart] [ON|OFF]Display or set the auto
info bootBootID[<processor #>[<bootid #>]]Display or set processor
EFI boot managerBoot infoDisplay boot-related
PAth[PRI|HAA|ALT|CON|KEY|<path>]Display or modify a path
[<proc>] [HPMC|LPMC|TOC|ASIC]]Display PIM information
EFI/POSSE Commands
This section describes the EFI/POSSE commands developed for the server.
NOTEEFI 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>
Par am eters
-bEnable page breaking
categoryCategory of commands to view help on commands
cmdShell command name on which to provide verbose information
bchDisplay the list of BCH commands and their corresponding EFI
bchmenuBCH menu name taken from the top level of the BCH menu
bchcmdBCH 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
Chapter 4
35
Utilities
EFI/POSSE Commands
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.
Example 4-1help Command
Shell> help
List of classes of commands:
boot-- Booting options and disk-related commands
configuration -- Changing and retrieving system information
devices-- Getting device, driver and handle information
memory-- Memory related commands
shell-- Basic shell navigation and customization
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
Example 4-2help bch Command
COnfigurationhelp bch co
INformation help bch in
PAthhelp bch pa
ScRoolhelp bch sr
SEArchhelp bch sea
SERvicehelp bch ser
BOothelp bch bo
HElphelp bch he
RESEThelp bch reset
MAinhelp bch ma
For more help on one of the commands above, at the prompt type:
help bch COMMAND
Example 4-3help configuration Command
Shell> help configuration
Configuration commands:
cpuconfig -- Deconfigure or reconfigure cpus
date-- Display or set date
err-- Display or set error level
esiproc-- Make an ESI call
errdump-- View/Clear logs
info-- Display hardware information
monarch-- View or set the monarch processor
palproc-- Make a PAL call
salproc-- Make a SAL call
time-- Display or set time
ver-- Displays version info
Type "help" followed by command name for full documentationon that command.
Type "help -a" to display a list of all commands.
Example 4-4help cpuconfig Command
Shell> help cpuconfig
CPUCONFIG [cpu] [on|off]
cpuSpecifies which cpu to configure
on|off Specifies to configure or deconfigure a cpu
36
Chapter 4
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
* To display configuration status of cpus
fs0:\> cpuconfig
<CPU configuration data displayed>
baud
Sets the baud rate and communication settings for a UART.
Syntax
baud <index> <baudrate>
Par am eters
<index> 0 through the total number of UARTS minus one
<baudrate>baud rate.
Utilities
EFI/POSSE Commands
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 processor dependent hardware (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-2Communications Parameters
ParameterValue
RECEIVE_FIFO_DEPTH 1
TIMEOUT 1000000
PARITYNo parity
DATA_BITS8
STOP_BITS1
CONTROL_MASK0
boottest
Interacts with the speedy boot variable allowing it to be set appropriately.
Chapter 4
37
Utilities
EFI/POSSE Commands
Syntax
boottestDisplays status of all speedy boot bits
boottest onRun all tests (for a normal boot time)
boottest offSkip 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
Par am eters
[test] Each test can be set or cleared:
booting_validEnable/disable system firmware response to BOOTING
early_cpuEnable/disable early CPU selftests.
late_cpuEnable/disable late CPU selftests.
platformEnable/disable system board hardware tests.
chipsetEnable/disable CEC tests.
io_hwEnable/disable EFI driver Core I/O tests.
mem_initEnable/disable memory initialization.
mem_testEnable/disable full destructive memory tests.
-------------------------------------booting_validOn (OS speedy boot aware)
early_cpuRun this test
late_cpuRun this test
platformRun this test
chipsetRun this test
io_hwRun this test
mem_initRun this test
-------------------------------------booting_validOn (OS speedy boot aware)
early_cpuSkip this test
late_cpuRun this test
platformRun this test
chipsetRun this test
io_hwRun this test
mem_initRun this test
mem_testRun this test
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>
38
Chapter 4
Utilities
EFI/POSSE Commands
Par am eters
<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.
Allows the user to restore non-volatile memory (NVM) to default values and clear NVM storage values.
Syntax
default[efi|sal]
default clear [bmc|efi|sal]
Par am eters
clearclears 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 machine check abort (MCA) for all
processors present in the system.
Chapter 4
39
Utilities
EFI/POSSE Commands
Syntax
errdump [mca | cpe | cmc | init | la | clear]
Par am eters
mcadumps the Machine Check Abort error log
cpedumps the Corrected Platform Error log
cmcdumps the Corrected Machine Check log
initdumps the Initialization log
ladumps the Logic Analyzer log
clear erases all of the logs (mca, cpe, cmc, init, la)
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]
Par am eters
target: valid targets are:
alldisplay everything
cpudisplay information on cpus
cache display information on cache
memdisplay 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
Example 4-9info all Command
Shell> info all
SYSTEM INFORMATION
Date/Time: Oct 31, 2003 22:03:39 (20:03:10:31:22:03:39)
AutoBoot: on - Timeout is:7SEC
Boottest:
boottest Settings Default Variable
OS is not speedy boot aware.
SelftestSetting
-----------------------early_cpuSkip this test
late_cpuRun this test
platformRun this test
chipsetRun this test
io_hwRun this test
mem_initRun this test
mem_testRun this test
Utilities
EFI/POSSE Commands
lanaddress
Allows the user to display the core I/O MAC address.
Displays or modifies the ID of the bootstrap processor. The preferred monarch number is stored in NVM.
Chapter 4
45
Utilities
EFI/POSSE Commands
Syntax
monarch <cpu>
Par am eters
<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.
Example 4-15monarch Command
Shell> monarch
CurrentPreferred
MonarchMonarchPossible Warnings
--------------------------------00
00
To view monarch: fs0 :\ monarch
| Processor
-----------------+----------current status|0
next boot status |0
To set the monarch processor to 1: fs0 :\ monarch 1
-----------------+----------current status|0
next boot status |1
| Processor
pdt
Displays or clears the contents of the Page Deallocation Table.
Syntax
pdt (clear)
Par am eters
<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.
Example 4-16pdt Command
Shell> pdt
PDT Information
Last Clear time: PDT has not been cleared
Number of total entries in PDT:50
Number of used entries in PDT:0
46
Chapter 4
Number of free entries in PDT:50
Number of single-bit entries in PDT:0
Number of multi-bit entries in PDT:0
Address of first multi-bit error: x0000000000000000
Example 4-17pdt clear Command
Shell> pdt clear
Are you sure you want to clear the PDT? [y/N] y
Shell>
Shell> pdt
PDT Information
Utilities
EFI/POSSE Commands
Number of total entries in PDT:50
Number of used entries in PDT:0
Number of free entries in PDT:50
Number of single-bit entries in PDT:0
Number of multi-bit entries in PDT:0
Address of first multi-bit error: 0x0000000000000000
Last Clear time: 10/21/01 5:00p
sysmode
Display or modify the system mode.
Syntax
sysmode <normal | admin| service>
Par am eters
<normal>sets system mode to normal
<admin>sets system mode to admin
<service>sets system mode to service
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.
Example 4-18sysmode Command
Shell> sysmode
System Mode: NORMAL
Shell> sysmode admin
You are now in admin mode.
Shell> sysmode service
You are now in service mode.
Shell> sysmode normal
You are now in normal mode
Chapter 4
47
Utilities
Specifying SCSI Parameters
Specifying SCSI Parameters
The following SCSI parameters may be configured for the SCSI board:
•SCSI ID (SCSI initiator ID)
•Maximum data transfer rate (SCSI rate)
•Bus width
•Whether the HBA is bootable (driver support)
•Avoid bus resets (secondary cluster server)
Using the SCSI Setup Utility
Step 1. At the EFI shell prompt, type this command to map the parameters for all PCI cards installed in
the system:
info io
A list of all the devices that are installed in the hp Integrity rx1620 Server and managed by EFI
drivers is displayed. The output may look like this:
In the example above, a single SCSI interface is shown in the listing. The information for both
channels of the SCSI interface 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 SCSI interface (the first two bold lines). For each channel of this SCSI
interface, note the following information:
•Bus #—identifies the bus the device is on; for the SCSI interface, this is the same for both
channels. In this example, the bus number is 20.
•Dev #—the ID the device is assigned on the bus; for the SCSI interface, this is the same for
both channels. In this example, the SCSI interface is device 01.
•Fnc #—identifies the channel of the device (00 for channel A, 01 for channel B, and so on). In
this example, because the SCSI interface has two channels, one channel is 00 and the other is
01.
•Vendor ID—shows the device’s vendor ID; for the SCSI interface, this is the same for both
channels. For all the SCSI interface the ID is 0x1000.
•Device ID—shows the device ID; for the SCSI interface, this is the same for both channels. For
the SCSI interface the ID is 0x0030.
•Slot #—identifies the physical card slot in the system where the SCSI interface is installed;
for the SCSI interface, this is the same for both channels. In this example, the SCSI interface is
on the system board therefore the in slot number is xx.
•Path—identifies the device’s path; for the SCSI interface, this is the same for both channels. In
this example, the SCSI interface path is Acpi(HWP0002,200)/Pci(1|0) for channel A and Acpi(HWP0002,200)/Pci(1|1) for channel B.
Using the SCSI interface information from the example above, the pieces of information that,
combined, tell you this is a SCSI interface are the following (shown in bold, for highlighting
purposes):
Looking at all of the above information together, the vendor (0x1000) and device (0x0030) are the
IDs for a SCSI interface. Of the devices with those IDs, this device has two channels (Fnc # of 00
immediately followed by Fnc # of 01). Also, this SCSI interface has a non-numeric (XX) slot #
indicating that it is on the system board.
Step 2. Still at the EFI shell prompt, type this command to obtain the controller’s handle for the SCSI
interface:
devtree
A tree of all EFI-capable devices installed in the system is displayed. The output could look like
this:
In the above example, the SCSI interface information is shown highlighted bold. You can tell the
information is for the SCSI interface because the path on the first line—Acpi(HWP0002,100)— is the
path from the information displayed by the info io command. The next two lines are for the SCSI
interface two channels, one line for each channel (they contain the SCSI interface description [LSI
Logic Ultra160 SCSI Controller]). Note the value shown for Ctrl—17 and 18—at the beginning of each
of those lines; this is the controller’s handle for each channel. You need to know it for the next
step.
NOTEThe controller’s handle values will change on every boot.
Step 3. Still at the EFI shell prompt, type this command to obtain the EFI driver’s handle for the SCSI
interface:
drvcfg
A list of all EFI-capable configurable components in the system is displayed. The output may look
like this:
Shell> drvcfg
Configurable Components
Drv[3D] Ctrl[15] Lang[eng]
Drv[3F] Ctrl[19] Lang[eng]
Drv[45] Ctrl[17] Lang[eng]
Drv[45] Ctrl[18] Lang[eng]
This listing shows which driver controls which device (controller). In the above example, the SCSI
interface information is shown highlighted bold. You can tell the information is for this SCSI
interface because the values shown for Ctrl—17 and 18—are the controller’s handles for the SCSI
interface two channels (from the information displayed by the devtree command).
NOTEThe EFI driver’s handle values will change on every boot.
TIPFrom this command (drvcfg), we recommend you record these two pieces of
information for each channel of each SCSI interface for parameters to be changed:
Chapter 4
•Drv (the EFI driver’s handle)
•Ctrl (the controller’s handle)
51
Utilities
Specifying SCSI Parameters
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 interface. Still at
the EFI shell prompt, type this command:
drvcfg -s
where
•
•
So, continuing the example for channel A of this SCSI interface, you would type:
drvcfg -s 45 18
Step 5. The EFI SCSI Setup Utility starts and its main menu is displayed, showing a list of all the EFI
capable SCSI interfaces in the system.
drvr_handle cntrl_handle
drvr_handle
display or change
cntrl_handle
display or change
is the handle of the driver that controls the channel whose SCSI ID you want to
is the handle of the controller for the channel whose SCSI ID you want to
52
Chapter 4
Specifying SCSI Parameters
TIPTo move the cursor in the EFI SCSI Setup Utility, you can use these keys:
Utilities
•Arrow keys:
↑↓ ←→
•Alternate keys:
H = left
J = down
K = up
L = right
I = home
O = end
Move the cursor to highlight the channel of the SCSI interface; press
Enter. (To determine which
channel of the interface 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.)
CAUTIONDo not select the <Global Properties> option on the main menu.
Step 6. The “Adapter Properties” screen for this channel of the SCSI interface is displayed. If you like, you
can make sure the utility is running for the channel of the SCSI interface 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.
CAUTIONDo not change the value for any of these fields on the “Adapter Properties” screen:
•Auto Termination
•SCSI Parity
•SCSI Bus Scan Order
•Spinup Delay (Secs)
Changing any of these fields can cause unpredictable results.
CAUTIONDo not change the value for any of these fields on the “Device Properties” screen:
•Scan Id
•Scan LUNs > 0
•Disconnect
•SCSI Timeout
•Queue Tags
Chapter 4
53
Utilities
Specifying SCSI Parameters
•Format
•Verify
Changing any of these fields can cause unpredictable results.
Step 7. You may display (and optionally change) any SCSI parameters listed below for the channel of the
SCSI interface, or restore its SCSI parameters to their default values.
•SCSI ID
•Maximum data transfer rate
•Bus width
•Whether the SCSI interface is bootable (driver support)
•Avoid bus resets (secondary cluster server)
•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 the channel of the
SCSI interface)
•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
If you selected cancel, you remain in the “Adapter Properties” screen for the channel of the SCSI
interface. You can still change the channel’s parameters listed above.
If you selected save or discard, you are placed in the EFI SCSI Setup Utility’s main menu.
CAUTIONDo 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.
Step 13. Select the option for exiting the utility.
Step 14. When you are prompted to, press
Enter to stop the SCSI interface; you are now back at the EFI shell
prompt.
Enter.
Step 15. At the EFI shell prompt, type this command:
reset
The system starts to reboot. This is required to cause the new SCSI setting.
54
Chapter 4
Utilities
Using the Boot Option Maintenance Menu
Using the Boot Option Maintenance Menu
This menu allows you to select console output and input devices as well as various boot options. It contains
the following items:
•Boot from a File
•Add a Boot Option
•Delete Boot Option(s)
•Change Boot Order
•Manage BootNext setting
•Set Auto Boot TimeOut
•Select Active Console Output Devices
•Select Active Console Input Devices
•Select Active Standard Error Devices
•Cold Reset
•Exit
These items are described in the following sections.
In all menus, select:
•Help to display the help available for the command
•Exit to return to the main Boot Options Maintenance menu
•Enter to select an item after using the arrow keys to highlight the item
•Save Settings to NVRAM to save your changes
NOTEThe options shown here are examples. Your system may have different options available based
on the system configuration and installed hardware components.
Paths
All devices in the hp Integrity rx1620 Server are represented by paths in the EFI shell. To identify the correct
socket or disk drive, use the following tables.
Removable Media BootAcpi(HWP0002,0)/Pci(2|0)/ATA(Primary,Master)
Boot from a File
Use this option to manually run a specific application or driver.
NOTEThis option boots the selected application or driver one time only. When you exit the
application, you return to this menu.
This option displays the file systems that are on your server or workstation and lets you browse these file
systems for applications or drivers that are executable. Executable files end with the.efi extension. You can
also select remote boot (LAN) options that have been configured on your network.
For example:
Boot From a File. Select a Volume
NO VOLUME LABEL [Acpi(HWP0002,0)/Pci(2|0)/Ata(Primary,Master)/CDROM
•NO VOLUME LABEL is a hard drive. When you format a hard drive, the EFI tools provide an option to
LABEL the disk. In this example, the volume was not labelled.
•CD_FORMAT is the label created for the disk currently inside the DVD-ROM drive.
•Removable Media Boot allows you to boot from a removable media drive (CD/DVD drive). This option does
not support booting from a specific file on a specific removable media disc.
•The two Load Files are the EFI Shell and the LAN.
Add a Boot Option
Use this option to add items to the EFI boot menu.
This option displays the file systems that are on your system and lets you browse these file systems for
applications or drivers that are executable. Executable files end with the.efi extension. You can also select
remote boot (LAN) options that have been configured on your network. The option you have selected will be
added to the EFI boot menu.
56
Chapter 4
Utilities
Using the Boot Option Maintenance Menu
If you add a new drive to your system, you must manually add its boot options list if you want to make it a
bootable device.
When adding a boot option that already exists in the Boot Manager list of boot options, you can choose
whether to create a new option or modify the existing one. If you:
•Choose to modify an existing option, you may change the boot option name and/or add boot option
arguments to the existing option.
•Create a new boot option for an already existing option, multiple instances of the same boot option exist.
For example:
Add a Boot Option. Select a Volume
NO VOLUME LABEL [Acpi(HWP0002,0)/Pci(2|0)/Ata(Primary,Master)/CDROM
Removable Media Boot [Acpi(HWP0002,0)/Pci(2|0)/Ata(Secondary,Master)
•Most of the items are the same options in Boot From a File.
•NO VOLUME LABEL is a hard drive. You can search through the disk for bootable applications to add to
the Boot Manager list of Boot options.
•Removable Media Boot will treat the Removable Media (generally a CD) as a bootable device.
•Load File EFI Shell adds a new instance to the EFI Shell. Load File with the MAC address adds a
network boot option.
Delete Boot Option(s)
Use this option to remove boot options from the EFI boot menu.
NOTEThis does not delete any files, applications or drivers from your system.
This option displays a list of boot options that are configured on your system. The names will match the
options on the main Boot Manager menu (above).
If you remove a drive from your system, you must manually delete it from the boot options list.
•To delete an item from the list, use the arrow keys to highlight the item and press
Enter.
•To remove all of the entries from the EFI boot menu, select Delete All Boot Options. This setting may be
used as a security device on systems that are accessed remotely.
Change Boot Order
Use this option to change the order of boot options. The order in which options are listed in the EFI boot menu
also reflects the order in which the system attempts to boot. If the first boot option fails, the system tries
booting the second, then the third, and so forth, until a boot option succeeds or until all options have failed.
Chapter 4
57
Utilities
Using the Boot Option Maintenance Menu
For example, if you normally boot using a configuration on your LAN but would like to boot from a local hard
drive if the LAN is unavailable, move the LAN boot option to the top of the list, followed by the hard drive
boot option.
The menu lists boot options that currently exist in the main Boot Manager menu. You can change the priority
of the items by moving them up or down in the list:
•Press
•Press
U to move an option up.
D to move an option down.
•Select Save Settings to NVRAM to modify the order in the Boot Manager menu, which modifies the order
that the Boot Manager will attempt to boot the options.
•The items at the bottom of the screen (shown in bold in these examples) are descriptions of the selected
option.
For example:
Change boot order. Select an Operation
EFI Shell [Built-in]
Current OS
Save Settings to NVRAM
Help
Exit
VenHw(D65A6B8C-71E5-4DF0-A909-F0D2992B5AA9)
Boot0000
Manage BootNext Setting
Use this option to run the selected boot option immediately upon entering the main Boot Manager menu. This
option is useful for booting an option that only needs to be booted once, without changing any other setting in
the main Boot Manager menu. This is a one-time operation and does not change the permanent system boot
settings.
This option displays the file systems that are on your system and lets you browse these file systems for
applications or drivers that are executable. Executable files end with the.efi extension. You can also select
remote boot (LAN) options that have been configured on your network.
To restore the default boot next setting, select Reset BootNext Setting.
For example:
Manage BootNext setting. Select an Operation
EFI Shell [Built-in]
Current OS
Reset BootNext Setting
Save Settings to NVRAM
Help
58
Chapter 4
Utilities
Using the Boot Option Maintenance Menu
Exit
VenHw(D65A6B8C-71E5-4DF0-A909-F0D2992B5AA9)
Boot0000
Set Auto Boot TimeOut
Use this option to set the amount of time the system pauses before attempting to launch the first item in the
Boot Options list.
For example:
Set Auto Boot Timeout. Select an Option
Set Timeout Value
Delete/Disable Timeout
Help
Exit
Interrupting the timeout during the countdown stops the Boot Manager from loading any boot options
automatically. If there is no countdown, boot options must be selected manually.
•To set the auto boot timeout value, in seconds, select Set Timeout Value and enter the desired value.
•To disable the timeout function, select Delete/Disable Timeout.
NOTEWhen this option is selected, the system does not automatically boot. The system stops at the
EFI boot menu and waits for user input.
Select Active Console Output Devices
Use this option to define the devices that display output from the system console. This list normally includes
the VGA monitor and a serial port for directing output to a terminal emulation package.
NOTEIf you install a modem in your system, make sure you disable the modem serial port in both the
Active Console Input and Active Console Output device lists.
NOTESome operating systems support multiple consoles, such as a simultaneous serial and VGA
output. See your OS documentation to determine how many consoles are supported with your
system. Multiple consoles are not supported for HP-UX or Windows (use the Smart Setup CD
to switch between COM A and the MP on Windows systems).
This menu is identical to Console Error Devices. The hp Integrity rx1620 Server does not support different
configurations for Output and Error console. For correct operation:
•When changes are made to either Output or Error console menus, the identical change must be made in
both menus.
•When changing serial devices, changes must be made to Output, Input, and Error menus for proper
operation.
Table 4-5Console Output Devices
To select:Choose:
Serial A/Serial 1Acpi(PNP0501,0)/Uart(9600 N81)/VenMsg(Vt100+)
MP Serial ConsoleAcpi(HWP0002,700)/Pci(1|1)/Uart(9600 N81)/VenMsg(Vt100+)
MP VGA PortAcpi(HWP0002,700)/Pci(2|0)
•Each option is identified with an EFI device path. Not all options will be available, depending on the
configuration of the system and the options purchased. Device paths may differ slightly on different
product models.
•On both serial device examples, UART 9600 indicates the current baud rate of the serial device (can be
changed with the EFI shell baud command), VenMsg Vt100+ is the current emulation type (several
different terminal emulation protocols are supported, see list above).
•Only one terminal emulation type (PcAnsi, Vt100, and so on) can be selected for each serial console, but
multiple serial consoles can be selected at a time.
Select Active Console Input Devices
Use this option to define the devices that are used to provide input to the system console.
This option displays the console devices on your system. This normally includes a standard keyboard and
mouse, and a serial port for receiving output from a terminal emulation package on a laptop. Several different
terminal emulation protocols are supported.
•When changing serial devices, changes must be made to Output, Input, and Error menus for proper
operation.
60
Chapter 4
Utilities
Using the Boot Option Maintenance Menu
NOTEIf you install a modem in your system, make sure you disable the modem serial port in both the
Active Console Input and Active Console Output device lists.
NOTESome Operating Systems support multiple input devices, such as a simultaneous serial and
keyboard input. See your OS documentation to determine how many consoles are supported
with your system.
•Each option is identified with an EFI Device path. Not all options will be available, depending on the
configuration of the system and the options purchased. Device paths may differ slightly on different
product models.
•On both serial device examples, UART 9600 indicates the current baud rate of the serial device, VenMsg
Vt100+ is the current emulation type. Several different terminal emulation protocols are supported (see
list above).
•Only one terminal emulation type (PcAnsi, Vt100, and so on) can be selected for each serial console, but
multiple serial consoles can be selected at a time.
Table 4-6Console Input Devices
To select:Choose:
Serial A/Serial 1Acpi(PNP0501,0)/Uart(9600 N81)/VenMsg(Vt100+)
MP Serial ConsoleAcpi(HWP0002,700)/Pci(1|1)/Uart(9600 N81)/VenMsg(Vt100+)
Select Active Standard Error Devices
Use this option to define the devices that display error messages from the system console.
This menu is identical to Console Output Devices. The hp Integrity rx1620 Server does not support different
configurations for Output and Error console. For correct operation:
Chapter 4
61
Utilities
Using the Boot Option Maintenance Menu
•When changes are made to either Output or Error console menus, the identical change must be made in
both menus.
•When changing serial devices, changes must be made to Output, Input, and Error menus for proper
operation.
Using the System Configuration Menu
The System Configuration Menu (on systems with EFI firmware version 2.0 or higher) includes the following
options:
•The Security/Password Menu lets you change the administrator and user passwords
•The Advanced System Information Menu displays information about system and component
configuration
•Set System Date lets you modify the system date
•Set System Time lets you modify the system time
•Reset Configuration to Default lets you restore system settings to their original configuration
•Help displays additional information about the available options
•Exit returns to the EFI startup menu
Security/Password Menu
You can set administrator and user passwords to provide different levels of access to the system firmware:
Resetting Passwords
If you forget your passwords, they can be reset using an MP command. Follow theses steps.
•If your system has an MP card:
Run the MP card bp command to reset the administrator and user passwords (see “Management
Processor Command Interface”).
•If your system does not have an MP card, you must reset the passwords using a jumper on the system
board:
Step 1. Power down the system and unplug the AC power cord.
62
Chapter 4
Management Processor
Step 2. Place a jumper between pins 7 and 8 on J96 located on the system board near the battery.
Figure 4-2 Password Reset Jumper
Pin 7
J96
Pin 8
Step 3. Plug in the AC power cord and wait for the BMC heartbeat LED on the system board to start
blinking green. This should take about 5 seconds from the time you plug in the power cord.
Utilities
Step 4. Unplug the AC power cord again and remove the jumper.
Step 5. Plug in the power cord and boot the system.
Step 6. The passwords have been cleared. Follow the instructions above to set new system passwords.
Step 7. Store the system in a secure location and keep the system case locked at all times to protect against
unauthorized access.
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 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
Chapter 4
63
Utilities
Management Processor
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.
Accessing the Management Processor
You can connect to the management processor using the following methods:
•The local RS-232C port using a local terminal
•The remote RS-232C port using external modem (dial-up) access, if remote modem access is configured
•The management processor LAN port using Web Console or telnet if login access through the
management processor LAN is enabled
Interacting with the Management Processor
To interact with the management processor, perform the following steps:
Step 1. Log in using your management processor user account name and password.
NOTEIf 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.
64
Chapter 4
Utilities
Management Processor Command Interface
Management Processor Command Interface
Use the management processor menus and commands as needed. The login screen, which includes the Main
Menu, is shown below. Main Menu commands (CO, VFP, CM, CL, CSP, SE, SL, HE, and X) can be entered after the MP prompt. Commands not displayed in the MP Main Menu can be accessed in command mode by first using
the CM command at the MP prompt. (A list of available commands can be displayed by using the management
processor help function. Display the list of commands as follows: in the MP Main Menu, enter HE after the MP>
prompt, then enter LI after the MP HELP: prompt.) You can return to the MP Main Menu by typing
NOTEAt publication, the current version of the Management Processor Revision is E.02.25.
Check the HP website for the latest revision.
MP Welcome Screen
MP Welcome screen commands:
MP Login: Admin
MP password: *****
Hewlett-Packard Management Processor
(C) Copyright Hewlett-Packard Company 1999-2003. All rights reserved
System Name: xxxxxxxxx
CTRL+B.
MP MAIN MENU:
CO:Console
VFP:Virtual Front Panel
CM:Command Menu
CL:Console Log
SL:Show Event Logs
CSP:Connect to Service Processor
SE:Create OS Session
HE:Main Menu Help
X:Exit Connecion
Management Processor Help System
The MP has a robust help system. To invoke MP HELP, enter he after the MP> prompt. The following is
displayed:
HE
==== MP Help: Main Menu ============================================(Administrator)===
Hardware Revision a1 Firmware Revision E.02.20 May 30 2003,15:18:47
MP Help System
Use Ctrl-B to exit MP command interface and return to the main MP menu:
Enter a command at the help prompt:
OVerview : Launch the help overview
Chapter 4
LIst: Show the list of MP commands
<COMMAND> : Enter the command name for help on individual command
65
Utilities
Management Processor Command Interface
TOPics: Show all MP Help topics and commands
HElp: Display this screen
Q: Quit help
Enter one of the commands described above: OV, LI, <command>, TOP, HE, Q
Management Processor Commands
MP commands are listed in the following table and described in the following paragraphs.
Table 4-7Management Processor Commands and Descriptions
CommandDescription
BPReset BMC passwords
CAConfigure asynch/serial ports
CGCertificate generator
CLView console log
CMSelect command mode
Ctrl+BReturn to MP main menu
COSelect console mode
CSPConnect to service processor
DATEDate display
DCDefault configuration
DFDisplay FRU information
DIDisconnect remote or LAN console
FW (XU)Upgrade MP firmware
HEDisplay help for menu or command
IDSystem information
ITInactivity timeout settings
LCLAN configuration
LOCLocator LED display and configuration
LSLAN Status
MAReturn to Main Menu
MRModem reset
MSModem status
PCRemote power control
PGPaging parameter setup
66
Chapter 4
Management Processor Command Interface
Table 4-7Management Processor Commands and Descriptions (Continued)
CommandDescription
PRPower restore
PSPower management module status
RBReset BMC
RSReset system through RST signal
SASet access
SEEnter OS session (UNIX only)
SLShow event logs
SOSecurity options
SSSystem processor status
SYSREVCurrent system firmware revisions
Utilities
TCReset via transfer of control (TOC)
TETell- send a message to other users
UCUser configuration
VFPVirtual front panel
WHODisplay connected management processor users
XExit management processor and disconnect
XDDiagnostics and/or reset of management processor
Reset BMC Passwords
BP: Reset BMC Passwords
This command resets BMC passwords (both USER and ADMIN passwords).
Configure Serial Port Parameters
CA: Configure local and remote serial port parameters
Set up the local serial port parameters as follows:
•TERMINAL TYPE: Vt100 vs HPterm
•BAUD RATES: Input and output data rates are the same; 300, 1200, 2400, 4800, 9600, 38400, 115200
bit/sec.
•TRANSMIT CONFIGURATION STRINGS: Disable this setting whenever the modem being used is not
compatible with the supported modem (MT5634ZBA).
•MODEM PRESENCE: When the modem may not always be connected, set this parameter to “not always
connected”.
For example: A modem attached through a switch. In mode “not always connected,” no dial-out functions
are allowed: DIAL-BACK is disabled, and PAGING is not possible.
The MP mirrors the system console to the MP local, remote/modem, and LAN ports. One console output
stream is reflected to all of the connected console users. If several different terminal types are used
simultaneously by the users, some users may see strange results.
Example 4-19HP-UX
Applications that care about the terminal type (install, SAM, vi, and so on) running on HP-UX use three
methods to determine the terminal type:
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.
Certificate Generate
CG: Generate RSA key pair or Self Signed Certificate
This command generates a new RSA key pair and self signed certificate.
Console Log
CL: Console Log—view the history of the Console output
This command displays up to 60 Kilobytes of logged console data (about 60 pages of display in text mode) sent
from the system to the Console path.
Command Mode
CM: Command Mode—enter command mode
68
Chapter 4
Utilities
Management Processor Command Interface
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.
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
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.
CTRL+B to return to the MP command interface.
Connect to Service Processor
CSP: Connect to remote management processor over the LAN
This command allows the local or remote port user to connect over the MP LAN to another MP on the
network. The user that launches the command is given a private connection to the other MP over the LAN. To
return to the original MP, type
CTRL+] to disconnect the CSP session.
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:
1. In the SO command, change individual users.
2. In the DC command choose “Reset Security Configuration”.
3. Forgotten passwords can be reset by pressing the MP reset button on the back panel of your HP Server.
After the MP reboots, the local console terminal displays a message for five seconds. Responding to this
message in time will allow a local user to reset the passwords.
NOTEAll user information (logins, passwords, and so on) is erased in methods 2 and 3.
Chapter 4
69
Utilities
Management Processor Command Interface
Display FRUID
DF: Display FRUID information
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.
Disconnect Remote or LAN Console
DI: DIsconnect remote/modem or LAN/WEB console
This command disconnects (hang up) the remote/modem or LAN/WEB users from MP. It does not disable the
ports. The remote console is no longer mirrored.
MP Firmware Update
FW: Activates MP firmware upgrade mode
This command is available from either the LAN or local serial port. This command activates firmware
upgrade mode, which loads new firmware through the MP LAN by FTP (which must be operational). An MP
Reset is generated after the upgrade is complete.
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:
•SNMP contact information
•SNMP server information
•SPU hostname
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.
70
Chapter 4
Utilities
Management Processor Command Interface
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.
Configure LAN Console
LC: LAN configuration (IP address, and so on)
This command displays and allows modification of the LAN configuration. Configurable parameters include:
•MP IP Address
•MP Host Name
•Subnet Mask
•Gateway Address
•Web Console port number
•Link State
The MP Host Name set in this command is displayed at the MP command interface prompt. Typically the
DNS name for the LAN IP is entered.
This field can be programmed to any useful name or phrase. For clarity, it is useful to enter MP-on-SYSTEM as
the MP Host name, so both names show up in the prompt (limit 19 characters, no spaces allowed.) The web
access port number is also set by this command.
Locator LED Status
LOC: Locator LED Status
This command displays the current status of the Locator LED.
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.
Return to Main Menu
MA: Return to MP Main Menu
This command makes the MP return to the non mirrored MP Main Menu. This is the same as executing
CTRL+B.
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
71
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
last state of the control signals DTR, RTS set by the firmware are displayed.
Enter. The current state of the status signals DCD, CTS, DSR, RI and the
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
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
This command will disconnect modem, LAN, and web users if access is disabled.
72
Chapter 4
Utilities
Management Processor Command Interface
Create Local Session
SE: Log into the system on local or remote port
Only valid from the local or remote/modem port, SE allows the user to leave the MP Command Interface and
enter a system session. Other mirrored MP users are placed in console mode. The session user returns to the
mirrored MP session on exit.
The MP regularly checks the activity of the session, closes the connection with the system, and, if the timeout
period has elapsed, returns the port to mirroring. The timeout period is set with the IT command. On HP-UX,
the SE command works on the local and remote ports.
In HP-UX, use the System Administration Manager (SAM) to add modem device files for the session UARTS.
The modem type, CCITT or Bell must agree with the remote port settings for the remote session port and
always be Bell mode for the local session port.
If the system and the MP Command Interface local or remote ports have been configured with different port
speeds, the baud rate changes to the rate specified by the OS for the duration of the session.
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.
•System Event Log (SEL)—Events (filtered by alert level) and errors
•Forward progress—All events
•Current boot log—All events between “start of boot” and “boot complete”
•Previous boot log—The events from the previous boot
Reading the system event log turns off the system LED. Accessing this log is the only way to turn off the
system LED when it is flashing and alerts have not been acknowledged at the alert display level.
Events are encoded data that provide system information to the user. Some well-known names for similar
data would be Chassis Codes or Post Codes. Events are produced by intelligent hardware modules, the OS,
and system firmware. Use SL to view the event log.
Navigate within the logs as follows:
•+ — View the next block (forward in time)
•- — View the previous block (backward in time)
•Enter (<CR>) — View the next block in the previously selected direction (forward or backward in time)
•D — Dump the entire log for capture or analysis
•F — First entry
•L — Last entry
•J — Jump to entry number __
•V — View mode configuration (text, keyword, hex)
•? — Display this help menu
•Q — Quit
Chapter 4
73
Utilities
Management Processor Command Interface
Table 4-8 defines alert (or severity) levels.
Table 4 -8A l ert L evels
SeverityDefinition
0Minor forward progress
1Major forward progress
2Informational
3Warning
5Critical
7Fatal
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.
Firmware Revision Status
SYSREV: Displays the revision status of firmware in the system.
This command displays the revision status of firmware in the system.
NOTEAt the time of production of this guide, the firmware revisions were:
FIRMWARE INFORMATION
Firmware Revision: 1.10 [4341]
PAL_A Revision: 7.31/5.37
74
PAL_B Revision: 5.37
SAL Spec Revision: 3.01
SAL_A Revision: 2.00
SAL_B Revision: 1.10
Chapter 4
EFI Spec Revision: 1.10
EFI Intel Drop Revision: 14.61
EFI Build Revision: 1.10
POSSE Revision: 0.10
ACPI Revision: 7.00
BMC Revision: 2.24
IPMI Revision: 1.00
SMBIOS Revision: 2.3.2a
Management Processor Revision: E.02.25
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.
Utilities
Management Processor Command Interface
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 allows an administrator to add, modify, re-enable, or delete user logins. The administrator can
also enable or disable security warnings and change passwords.
Virtual Front Panel
VFP: Display Virtual Front Panel
The VFP command presents a summary of the system by using direct console addressing. If the terminal is
not recognized by the MP, VFP mode will be rejected. Each individual user will get this summary in order to
avoid issues related to terminal type and screen display mode.
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.
Chapter 4
75
Utilities
Management Processor Command Interface
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
login name that the local operator used is displayed instead.
CTRL+B, then the
Exit from MP
X: Exit from MP command interface and disconnect from the system
This command disconnects the executing user from the system. This command is available from the local
port.
Diagnostics
XD: Diagnostics and/or Reset of MP
This command allows the user to perform some simple checks to confirm the MP's health and its connectivity
status. The following tests are available:
•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.
76
Chapter 4
5Troubleshooting
This chapter provides troubleshooting instructions used in the maintenance of the hp Integrity rx1620
Server.
Troubleshooting Tips
WARNINGBefore removing a cover, always disconnect the AC power cord and unplug cables.
Disconnect the AC power cord to avoid exposure to high energy levels that may
cause burns when parts are short-circuited by metal objects such as tools or jewelry.
CAUTIONDo not operate the HP Server for more than 5 minutes with any cover (including disk drives)
removed. Damage to system components may result due to improper cooling airflow.
•For problems with an optional disk array controller board, refer to the appropriate manuals provided
with the array controller.
•For questions on the operation of HP e-DiagTools, refer to the HP e-DiagTools Administrator Guide on
the HP Web Site at http://docs.hp.com.
•For general information on HP Server products, refer to the HP Web Site and search for “management” at
http://docs.hp.com.
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 occurred. The following is a list of symptom examples:
•System LED blinking
•System Alert present on console
•System will not power-up
•System will not boot
•Error/Event Message received
•Machine Check Abort (MCA) occurred
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:
Chapter 5
•Problem-System LED blinking
— System Alert on console?
77
Troubleshooting
Possible Problems
— 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 if the optional management processor card is installed, use the MP commands to
view the SEL.
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 and
verification steps.
NOTEIf 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.
Possible Problems
This section contains example HP Server problems and their possible solutions.
The system will not power-up.
Step 1. Review the installation procedures for the server. Refer to the hp Integrity rx1620 Installation
Guide.
Step 2. Check all power connection cables.
Step 3. Verify that 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 of the dc voltage
generated by the power supply.
Step 5. Check that the STBY (power good) LED located near the SCSI connector on the system board is
illuminated.
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.
78
Chapter 5
Troubleshooting
Possible Problems
The system will not boot.
Step 1. Examine the display 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.
Step 2. Examine the four diagnostic LEDs for indications of specific warning or fault indications. The
diagnostic LEDs present patterns that categorize the source of the warning or fault.
Step 3. Display and examine the system event log (SEL) and forward progress log (FPL) for further
information relating to warning or fault indication.
Step 4. Review the firmware revisions of all firmware.
Step 5. Use the BMC command line interface (cli) to cycle the system power, cli>pc off, cli>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 7. Check that all DDR DIMMs are seated properly.
Step 8. Check that the DDR DIMM configuration on the system board matches those approved. A
minimum of one DDR DIMM pair must be installed.
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, for
instructions.
Step 13. If the system will still not boot, it may be necessary to replace the base unit.
The system has intermittent failures.
Step 1. Examine the display 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.
Step 2. Examine the four diagnostic LEDs for indications of specific warning or fault indications. The
diagnostic LEDs present patterns that categorize the source of the warning or fault.
Step 3. Display and examine the system event log (SEL) and forward progress log (FPL) for further
information relating to warning or fault indication.
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 with LVD SCSI, termination is provided in the cable.
Step 7. Check that the processors are installed in the correct sockets and that terminators are installed in
all unused sockets.
Chapter 5
79
Troubleshooting
Possible Problems
Step 8. Reseat the main memory DDR DIMMs.
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.
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 the 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 DDR DIMMs are seated properly in the board.
Also check the DDR DIMM configuration, and that the DDR 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:
•Critical temperature fluctuations or changes
•Voltage problems (external AC line)
•Power supply failure
If the server powers off, and before you try a restart, do the following:
Step 1. Examine the display 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.
Step 2. Examine the four diagnostic LEDs for indications of specific warning or fault indications. The
diagnostic LEDs present patterns that categorize the source of the warning or fault.
Step 3. Display and examine the system event log (SEL) and forward progress log (FPL) for further
information relating to warning or fault indication.
80
Chapter 5
Troubleshooting
Possible Problems
Step 4. First check to make sure power is getting to the server. Plug a known working device into the
power outlet.
Step 5. 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.
NOTETemperature problems may be caused by a fluctuating power supply.
Step 6. Check the system specifications and make sure the environmental temperature and voltage are in
the specified guidelines.
Step 7. Monitor the system to make sure you are not experiencing further temperature and voltage
problems.
Chapter 5
81
Troubleshooting
Troubleshooting and FRU identification
Troubleshooting and FRU identification
Once you have determined the current system state, you must troubleshoot the system to determine what the
problem symptoms are and what repair actions to take.
Use this guide to assist you in repairing the system by matching the problem symptom with the appropriate
troubleshooting step.
Table 5-1Problem Symptoms Repair Actions
Problem or
Symptom
No indication of
housekeeping
voltage present
when AC is
connected and
power switch is
in the off
position.
Problem
Indicators
• Standby
LED is off
when AC is
plugged into
system.
• BMC
“heartbeat”
not flashing.
Normal
Functioning
Indicators
• Power LED Off.
• Power LED on
MP board (if
installed) should
be lit solid green.
• Standby LED
on system board
is on steady.
• BMC
“heartbeat” LED
on system board
is flashing.(if
installed) should
be lit solid green.
Troubleshooting StepsPotential FRUs
1. AC must be present. Check
that PDU is plugged in.
2. Ensure there is a working
power supply. The LED on the
supply should be lit.
System will not
power on when
display panel
Power switch is
turned on.
Problem
Indicators
• Display
panel power
LED stays
off when
power is
turned on.
• System
LED may be
flashing
yellow
(attention
indication).
Normal
Functioning
Indicators
• Power switch
on.
• Power LED on
steady green.
• System LED is
off.
Troubleshooting StepsPotential FRUs
1. Ensure there is a working
power supply. The LED on the
supply should be lit.
2. Verify that standby voltage
is present. Check that the
STBY LED on the system
board is lit.
3. Verify that the baseboard
management controller is
functioning. Check the
heartbeat (BMC) LED on the
system board is lit.
4. Check system event log
(SEL). Look for event log
detail = Low Voltage DC
power. This indicates a failure
of one of the CPU power pods.
The failing CPU power pod is
indicated in the Source ID
field.
• Power supply
• CPU power pod
• System board
• Intrusion switch
on chassis (cover
not completely
closed)
No EFI Main
Menu prompt.
• Display
panel power
LED is not
steady green.
• No system
events are
being
displayed at
the console.
• There is no
EFI Main
Menu
prompt at
the console.
• Display panel
power LED is
steady green.
• System events
are being
displayed at the
console.
• EFI Main Menu
prompt.
1. Check that the console is
properly connected and that
you can communicate with the
BMC (
CTRL+B should get you
the MP login prompt).
2. Check system event log
(SEL). Look for entries related
to:
• Processors
• Processor support modules
(also known as power pods).
• Memory
3. Check for a red LED on the
MP card if installed. If lit red,
the problem is with the MP.
4. Reduce to minimum
configuration and
troubleshoot from there.
• Console
messages
indicating
problems
booting from
the primary
or alternate
boot path.
• Boot error
messages.
• System
LED
blinking.
Normal
Functioning
Indicators
• Console
messages and
prompt indicating
you are at ISL.
• OS prompt.
• OS boot
messages.
• System LED on
steady green.
Troubleshooting StepsPotential FRUs
1. Use EFI shell commands to
verify I/O and presence of
valid devices.
2. Use EFI boot manager boot info command to determine
boot related information.
3. Check system event log
(SEL) for detailed message(s).
4. Remove I/O cards to
eliminate them as cause of
problem.
1. Check system event logs for
possible problem indication.
2. Run ODE diagnostics.
• Boot path
configuration
error
• SCSI cable not
connected from
channel A to drive
cage
• Hard disk drive
• Disk drive cage
backplane
• SCSI interface
on system board
• Processor
• Hard disk drive
• Disk drive cage
backplane
• SCSI interface
on system board
84
• Corrupt OS
Chapter 5
Troubleshooting
Verifying Hard Disk Drive Operation
Verifying Hard Disk Drive Operation
Each hard disk drive has an activity LED indicator on the front of the drive.
NOTEOn the hp Integrity rx1620 Server only the Activity LED is used. The Status LED is
disconnected.
Figure 5-1LED Apertures on Hard Disk Drive
Status LED
(not used)
Activity LED
Lightpipes on the disk drive transmit light to these apertures from LEDs on the inside rear of the hot-swap
mass storage cage. Verify that the LED shows the correct activity indication for all disk drives that you
installed:
Step 1. Turn on power to the HP Server and display monitor.
Step 2. During the boot sequence, watch the Activity LED on each hard disk drive:
•Activity LED: The LED quickly cycles from amber to green. The LED stays steady green until
the drive spins up.
Step 3. If the status LED were illuminated on any disk drives, the drive cage may not be correctly
installed. Check installation as follows:
a. Turn off the HP Server power switch and unplug the AC power cords and any cables.
b. Disconnect the power distribution cable between the drive cage and the power distribution
module and then reconnect it.
c.Verify that the SCSI interface is correctly installed from SCSI A channel connector on the
system board to the connector on the SCSI cage.
d. Check the SCSI bus for proper loading,
e. Reconnect the AC power cords and any cables. Restart the HP Server to determine whether the
LEDs now become illuminated during the boot. If not, contact your reseller.
Step 4. If the LED indicator on a single disk drive is not illuminated during boot, the disk drive may be
installed incorrectly, or its lightpipes may be damaged.
Chapter 5
Check the lightpipe on the disk drive as follows:
a. Remove the disk drive.
85
Troubleshooting
Identifying and Diagnosing Hardware Problems
b. Inspect the lightpipes for damage. If a lightpipe is damaged, contact your reseller.
CAUTIONThe lightpipes are fragile. Be careful not to damage them when you inspect them
or when you reinsert the disk drive.
c.Reinstall the disk drive.
d. Restart the HP Server to determine whether the LED now becomes illuminated during the
boot. If not, contact your reseller.
Step 5. Use the EFI shell command info io to check the SCSI drives.
Identifying and Diagnosing Hardware Problems
Should a failure occur, the system LED, the LAN LED, the diagnostic LEDs, and the system event log (SEL)
will help you identify the problem:
•LEDs. The system LED, LAN LED, and diagnostic LEDs on the display panel of the server change color
and blink in different patterns to help identify specific problems. LEDs on the front and rear panels of the
server display LAN activity.
•The System Event Log (SEL) provides detailed information about the errors identified by the LEDs.
If the LEDs and SEL do not give you enough information for you to identify the problem you are experiencing,
HP also provides diagnostic tools with each operating system.
Power and System LEDs
The Power and System LEDs indicate the state of the system. When the System LED is blinking yellow or
red, a problem exists.
NOTEWhen the optional management processor (MP) card is installed, the four diagnostic LEDs on
the display panel are disabled.
Systems with the Optional Management Processor Card Installed
The following system LED states exist for systems having a optional management processor card installed.
Table 5-2System LED States
System LEDState
OffOff
Solid greenRunning OS
Blinking greenBooting or running code other than operating system (boot or
diagnostic).
86
Chapter 5
Troubleshooting
Identifying and Diagnosing Hardware Problems
Table 5-2System LED States (Continued)
System LEDState
Blinking yellow (1/sec.)Attention indication:
Alerts of levels 3-5 detected in the optional management processor logs.
The LED will turn off once the event log has been read.
Blinking red (2/sec.)Fault indication:
System alert level 7 detected, LED will blink until the problem is
resolved and the system boots successfully or until it is manually turned
off.
The LED will turn off once the event log has been read.
For system alerts of levels 3-5, the attention condition on the system LED can be cleared by accessing the logs
using the sl command available in the optional management processor command mode or the EFI cli cli>sl e command.
The fault condition for system alerts of level 7 can only be cleared with the dc command unless hardware
replacement is necessary.
NOTEAlways check the optional management processor system event logs (SEL) in the case of a
blinking yellow or red System LED before replacing any hardware.
Management Processor (MP) Card Event Logs
The management processor provides diagnostic and configuration capabilities. To access the management
processor, perform the following:
NOTEThe management processor must be accessed from a terminal console which has access to the
The server's built-in sensors have detected an open chassis door.
Logged by: BMC; Sensor: Physical Security - Chassis Open
Data1: State Asserted
0x200000000C020570 FFFF010302050300
Troubleshooting
NOTEMore detailed information on the system logs is presented in Chapter 4, “Utilities.”
Systems without a Management Processor Card
The system LED states operate the same with systems having the optional management processor card.
Table 5-3Power and System LED States
Power LEDSystem LEDState
OffOffOff
On (green)Solid greenRunning
On (green)Blinking greenBooting or running code other than
operating system (boot or
diagnostic).
On (green)Blinking yellow (1/sec.)Attention indication
On (green)Blinking red (2/sec.)Fault indication
Diagnostic LEDs
Four diagnostic LEDs are provided on the display panel of the system. Additional diagnostic LEDs are
provided on the system board and are described later in this chapter.
The diagnostic LEDs warn of impending failures or present failures and allow you to take preventive or
corrective action, such as making a system backup or replacing a component. These diagnostic LEDs are
labeled 1, 2, 3 and 4.
•If no management processor card is installed, the boot progress is monitored by diagnostic LEDs 1
through 4. During the boot-up the LEDs will turn on in sequence until the EFI prompt is reached.
Chapter 5
91
Troubleshooting
Identifying and Diagnosing Hardware Problems
•If a management processor card is installed, the boot process will be monitored by the management
processor card. The diagnostic LEDs are disabled.
Figure 5-2Diagnostic LEDs
LED 2LED 4
LED 1
LED 3
System
LED
Power
On/Off LED
LAN
Locator
Button and
LED
Diagnostics
LEDs
LED
Power On/Off
Button
•The system LED indicates the severity of the error. Check the system LED before proceeding to analyze
the sequence of diagnostic LEDs:
•System LED blinking YELLOW indicates a WARNING.
•System LED blinking RED indicates a FAULT.
•The diagnostic LEDs provide details about the specific error:
•Solid red indicates the failing part or sub-system.
•Off or solid green diagnostic LEDs provide additional details about the failure.
The pattern of illuminated LEDs may be used to identify the category of the fault or warning. For example, if
diagnostic LED one is red, there is a problem with memory. However, if diagnostic LEDs one and two are both
red, there is a problem with the system processor.
If the diagnostic LEDs indicate an error, check the EFI shell command line interface (CLI) cli>sl e to display
the system event log (SEL) for a more detailed explanations of the failure.
The faults and warnings fall into several general categories.
Table 5-4Diagnostic LEDs Fault and Warning Categories
LED 1LED 2LED 3LED 4Category
Red
Any
Any
Any
a
a
a
Any
Red
Any
Any
RedRed
a
a
a
Any
Any
Red
Any
Any
a
a
a
a
Any
Any
Any
a
a
a
Memory
Firmware
System Board
RedFan
Any
a
Processor
92
Chapter 5
Identifying and Diagnosing Hardware Problems
Table 5-4Diagnostic LEDs Fault and Warning Categories (Continued)
LED 1LED 2LED 3LED 4Category
Troubleshooting
Red
Red
Any
a
Any
a
Any
a
Red
Red
Any
Any
a
a
Any
a
BMC
RedTemperature
RedPower Supply
RedRedRedRedUnknown
a. This LED can display any color other than red (for example,
green or off).
Warnings
The following tables provide additional information about each specific warning associated with the various
possible LED lighting sequences when the system LED is yellow.
Table 5 - 5Un k nown Wa rning
System
LED
Flashing
Yellow
LED 1LED 2LED 3LED 4ProblemSolution
RedRedRedRedUnknown
warning.
View the SEL cli>sl e for
additional information. For
further assistance, contact your
HP Support Engineer.
Table 5-6Memory Warnings
System
LED
Flashing
Yellow
Flashing
Yellow
Flashing
Yellow
LED 1LED 2LED 3LED 4ProblemSolution
RedGreenOffOffMismatched
RedOffGreenGreenMemory
RedGreenGreenGreenBad serial
memory
pairs.
thermal load
order.
presence
detect (SPD)
information
(can't detect
type).
View the SEL for additional
information. Review the
information on installing
memory in “Installing and
Configuring” in the hp Integrity rx1620 Maintenance Guide.
View the SEL for additional
information.
View the SEL for additional
information. For further
assistance, contact your HP
Support Engineer.
Chapter 5
93
Troubleshooting
Identifying and Diagnosing Hardware Problems
Table 5-7System Board Warnings
System
LED
Flashing
LED 1LED 2LED 3LED 4ProblemSolution
GreenGreenRedOffBattery
Yellow
Table 5 -8Fan Warnin gs
System
LED
Flashing
Yellow
Flashing
Yellow
Flashing
Yellow
LED 1LED 2LED 3LED 4ProblemSolution
GreenOffOffRedCooling Unit 1
OffGreenOffRedCooling Unit 2
OffOffGreenRedCooling Unit 3
voltage low
(PSU) is not
functioning
properly
(memory) is
not functioning
properly
(CPU) is not
functioning
properly
Replace the system board
battery.
Replace the fan that is not
functioning.
a
Replace the fan that is not
functioning.
a
Replace the fan that is not
functioning.
a
a. Refer to “Removing and Replacing Components” in the hp Integrity rx1620 Maintenance Guide for
detailed instructions on the maintenance action.
Table 5-9Processor Warnings
System
LED
Flashing
Yellow
Flashing
Yellow
LED 1LED 2LED 3LED 4ProblemSolution
RedRedGreenOffProcessor 0
temperature
exceeds limit
RedRedOffGreenProcessor 1
temperature
exceeds limit
Make sure nothing is blocking the
system’s airflow and locate your
system in an air-conditioned room.
Make sure nothing is blocking the
system’s airflow and locate your
system in an air-conditioned room.
Table 5-10Temperature Warnings
System
LED
Flashing
Yellow
LED 1LED 2LED 3LED 4ProblemSolution
RedGreenGreenRedExternal air
temperature
too high
Make sure nothing is blocking
the system’s airflow and locate
your system in an
air-conditioned room.
94
Chapter 5
Table 5 - 11Vid eo Warn i n gs
Troubleshooting
Identifying and Diagnosing Hardware Problems
System
LED
Flashing
Yellow
LED 1LED 2LED 3LED 4ProblemSolution
OffRedRedOffNo video
adapter
present
Install a video adapter. See the
installation instructions shipped
with the video adapter.
Table 5-12Power Supply Warnings
System
LED
Flashing
Yellow
Faults
The following tables provide additional information about each specific fault associated with the various
possible LED lighting sequences when the system LED is red.
LED 1LED 2LED 3LED 4ProblemSolution
GreenRedOffRedPower
supply fault
Check the power supply LED.
Replace the power supply.
Table 5-13Unknown Faults
System
LED
LED 1LED 2LED 3LED 4ProblemSolution
Flashing
Red
RedRedRedRedUnknown
Table 5-14Memory Faults
System
LED
Flashing
Red
Flashing
Red
Flashing
Red
LED 1LED 2LED 3LED 4ProblemSolution
RedGreenOffOffMismatched
OffOffOffGreenFatal
RedGreenGreenOffNo memory
fault.
memory
pairs.
memory
error.
installed.
View the SEL for additional
information. For further
assistance, contact your HP
Support Engineer.
Review the information on
installing memory in
“Installing and Configuring” in
the hp Integrity rx1620 Maintenance Guide.
Replace memory.
Install memory.
Chapter 5
95
Troubleshooting
Identifying and Diagnosing Hardware Problems
Table 5-14Memory Faults (Continued)
System
LED
Flashing
LED 1LED 2LED 3LED 4ProblemSolution
RedGreenGreenGreenBad
Red
Table 5-15Firmware Errors
System
LED
Flashing
Red
LED 1LED 2LED 3LED 4ProblemSolution
OffRedOffOffSystem
Table 5-16System Board Faults
System
LED
LED 1LED 2LED 3LED 4ProblemSolution
Memory.
One or more
DIMMs are
bad or not
seated
properly.
Firmware
Hang
Reseat the DIMMs. If the error
persists, replace them.
View the SEL for additional
information. For further
assistance, contact your HP
Support Engineer.
Flashing
OffGreenRedOff VRM
Red
Flashing
GreenOffRedOffVRM
Red
Table 5 -17Fan Fault s
System
LED
Flashing
Red
Flashing
Red
Flashing
Red
LED 1LED 2LED 3LED 4ProblemSolution
GreenOffOffRedCooling Unit
OffGreenOffRedCooling Unit
OffOffGreenRedCooling Unit
overvoltage
undervoltage
1 (PSU) fault
2 (memory)
fault
3 (CPU) fault
View the SEL for additional
information. For further
assistance, contact your HP
Support Engineer.
View the SEL for additional
information. For further
assistance, contact your HP
Support Engineer.
Replace the fan that is not
functioning.
a
Replace the fan that is not
functioning.
a
Replace the fan that is not
functioning.
a
96
Chapter 5
Identifying and Diagnosing Hardware Problems
a. Refer to “Removing and Replacing Components” in the hp Integrity rx1620 Maintenance Guide for
detailed instructions on the maintenance action.
Table 5 -18Pr o cess or Faul ts
Troubleshooting
System
LED
Flashing
Red
Flashing
Red
Flashing
Red
LED 1LED 2LED 3LED 4ProblemSolution
RedRedGreenOffProcessor 0
RedRedOffGreenProcessor 1
RedRedGreenGreenNo processor
Table 5 -19BM C Faul ts
System
LED
Flashing
Red
LED 1LED 2LED 3LED 4ProblemSolution
RedGreenRedOffBMC
temperature
exceeds limit
temperature
exceeds limit
detected.
firmware is
damaged
Make sure nothing is blocking the
system’s airflow and locate your
system in an air-conditioned
room. In a single CPU
configuration, verify that the
airflow blocker is installed.
Verify that the processor or
processors are correctly installed.
See “Installing and Configuring”
in the hp Integrity rx1620 Maintenance Guide for
installation procedures.
Turn off and unplug the system.
Wait 20 seconds, then plug in and
restart the system. If the error
repeats, replace the base unit.
Flashing
Red
RedGreenRedGreenSystem
Table 5-20Temperature Faults
System
LED
Flashing
Red
Chapter 5
LED 1LED 2LED 3LED 4ProblemSolution
RedGreenGreenRedExternal air
board FRU
inventory
device
inaccessible
temperature
too high
Replace the base unit.
Make sure nothing is blocking
the system’s airflow and locate
your system in an
air-conditioned room.
97
Troubleshooting
Command Line Interface
Table 5-21Power Supply Errors
System
LED
Flashing
Red
Flashing
Red
Flashing
Red
LED 1LED 2LED 3LED 4ProblemSolution
OffRedOffRedVRM or power
pod fault
GreenRedOffRedPower Supply
fault
GreenRedGreenRed12V out of range
(power supply
interface fault)
View the SEL for additional
information.
View the SEL for additional
information. Replace the
power supply if necessary.
View the SEL for additional
information. If the power
supply interface has failed
it is necessary to replace
the base unit.
Command Line Interface
The baseboard management controller (BMC) is accessable by means of the BMC console commands or
command line interface (CLI). The commands are similar to the management processor (MP) commands but
are slightly less interactive.
Detailed information on the CLI commands is provided in Chapter 4, “Utilities.”
Command Line Interface Menu
The command line interface (CLI) provides the following menu selections:
date: Date display
help: List available commands
ipmi: Send IPMI cmd
loc: System locator LED
passwd: Change password
pc: Power control
pr: Power restore policy
ps: Power status
rs: System reset (through RST signal)
sl: Show logs
sr: Display firmware revisions
tc: System reset (through INIT signal)
exit: Exit
98
Chapter 5
Troubleshooting
Command Line Interface
Troubleshooting Example Using CLI
This example uses the cli and the SEL to display error messages indicating that no memory is installed.
cli>sl e
# Sev Generator/Sensor Description Event IDData, Timestamp