Standalone Diagnostic Operation; Perform Slow Boot; Partitioned System Considerations For Standalone Diagnostics; Running Standalone Diagnostics From A Network Installation Management (Nim) Server - IBM pseries 655 Installation Manual

Table of Contents

Advertisement

7. Press Ctrl-D to log off from root user or CE Login.
8. Complete the installation by going to "Step 26. Install the Rack Doors" on page 28.

Standalone Diagnostic Operation

Use standalone diagnostics to test the system when the online diagnostics are not installed and as a
method of testing the disk drives that cannot be tested by the online diagnostics.
Note: No error log analysis is done by the standalone diagnostics. The standalone diagnostics:
v Are resident on a Network Installation Management (NIM) server
v Provide a method to test the system when the online diagnostics are not installed or cannot be
loaded from the disk drive
v Allow testing of the disk drives and other resources that cannot be tested by the online
diagnostics
v Do not have access to the AIX configuration data
v Do not have access to the AIX error log
v Do not allow for running of error log analysis

Perform Slow Boot

To fully analyze all of the available information, perform the following steps before doing a hardware repair
or replacement:
1. Record the 8-character error code (and location code if present) displayed as the operator panel value
displayed on the HMC or that was reported by the customer.
2. Do a slow boot in service mode. This boot can be specified using the System Power Control Menu on
the Service Processor Main Menu. (A fast boot skips much of the built-in diagnostic testing.) A slow
boot may yield a new 8-character error code displayed as an operator panel value on the HMC and
new errors in the service processor error log. If a new error code is reported, use this code to continue
problem analysis. See "Running Online Diagnostics in Service Mode" on page 34.

Partitioned System Considerations for Standalone Diagnostics

To run standalone diagnostics on a full system partition, you must reboot the entire system. However, for a
partition in a partitioned system, you can boot standalone diagnostics either in a given partition or on the
entire system (which is the same procedure as a full system partition). For a partitioned system, before
running standalone diagnostics on a given partition, the user must move the device from the existing
location where standalone diagnostics is booted (the network adapter connected to the NIM server, in the
case of NIM boot of standalone diagnostics), to the partition that will run standalone diagnostics. Devices
in a partitioned system are moved on an I/O-slot basis.
Running Standalone Diagnostics from a Network Installation
Management (NIM) Server
A client system connected to a network with a NIM server can boot standalone diagnostics from the NIM
server if the client-specific settings on both the NIM server and client are correct.
Notes:
1. All operations to configure the NIM server require root user authority.
2. If you replace the network adapter in the client, the network adapter hardware address settings for the
client must be updated on the NIM server.
3. The Cstate for each standalone diagnostics client on the NIM server should be kept in the diagnostic
boot has been enabled state.
4. On the client partition, the NIM server network adapter can be put in the bootlist after the boot disk
drive. This allows the system to boot in standalone diagnostics from the NIM server if there is a
Chapter 3. Verifying the Hardware Operations
35

Advertisement

Table of Contents
loading

Table of Contents