Specifications

4. PAL code configures all processors.
5. System Abstraction layer (SAL) code configures all platform central electronic complex (CEC)
chips, including shared memory and all responding I/O devices.
6. Firmware code and stack are relocated to shared memory, after all x4 DIMM ranks in shared
memory are configured and tested.
7. EFI Shell is launched from shared memory, and cache lines are retrieved 128 bytes at a time
by the memory controller in zx1.
8. HP-UX loader is launched using the EFI device driver.
9. HP-UX boots and starts its own device drivers.
10. HP-UX may use runtime PAL and SAL calls, and APCI features (these abstraction layers allow
platform independence).
Diagnostics
A suite of offline and online support tools are available to enable manufacturing, field support
personnel, and you to troubleshoot server blade problems. In general, if the operating system
(HP-UX) is already running, it is best not to shut it down. Use the online support tools.
If the OS cannot be booted, use the offline support tools to resolve the problem. The offline support
tools are available from the EFI partition. Once you resolve the problem preventing booting, boot
HP-UX, and use the online support tools for any further testing.
If it is not possible to reach the EFI from either the main disk or from LAN, you must troubleshoot,
using the visual fault indicators, console messages, and system error logs that are available.
Online Diagnostics/Exercisers
Online support tools are provided on the server blade. Centralized error archiving and hardware
inventory tools are available as long as the agents/providers that support them are installed on
the managed server blade.
On HP-UX servers, the legacy tools within OnlineDiag continue to be supported. The online support
tools, on HP-UX 11.23 and greater, include the Support Tool Manager (STM) tools, and the
additional Web-Based Enterprise Management (WBEM) features added by SysFaultMgmt.
The STM suite of tools includes verifiers, diagnostics, exercisers, information modules, and expert
tools.
Verifiers quickly determine whether or not a specific device is operational by performing tasks
similar in nature to the way applications use the device. No license is required to run the verifiers.
Diagnostics are tools designed to identify faulty or failed FRUs.
Exercisers stress devices in order to facilitate the reproduction of intermittent problems.
Information modules create a log of information specific to one device, including:
• The product identifier
• A description of the device
• The hardware path to the device
• The vendor
• Onboard log information (if applicable)
• Miscellaneous information associated with the device
• The firmware revision code, if firmware is present in the device, is also displayed
Expert tools are device-specific troubleshooting utilities for use by sophisticated users. Their
functionality varies from tool to tool, but they are intended to be interactive, and rely on users to
provide information necessary to perform a particular task. These tools require users to have the
appropriate license, if they wish to run them.
Troubleshooting Tools 95