Running Standalone Diagnostics from a Network Installation
Management (NIM) Server
A client system connected to a network with a Network Installation Management (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 system, the NIM server network adapter should 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
problem booting from the disk drive. Refer to the
Multiboot
section under “SMS” in the client system’s
service guide for information on setting the bootlist.
NIM Server Configuration
Refer to the “Advanced NIM Configuration Tasks” chapter of the
AIX Installation Guide and Reference
,
order number SC23-4389 for information on doing the following:
v
Registering a client on the NIM server
v
Enabling a client to run diagnostics from the NIM server
Documentation for the AIX operating system is available from the IBM
Eserver
pSeries Information
Center at http://publib16.boulder.ibm.com/pseries/en_US/infocenter/base. Select
AIX documentation
. The
AIX Documentation
CD contains the base set of publications for the operating system, including
system-management and end-user documentation.
To verify that the client system is registered on the NIM server and the diagnostic boot is enabled, run the
command
lsnim -a Cstate -Z
ClientName
from the command line on the NIM server. Refer to the
following table for system responses.
Note:
The
ClientName
is the name of the system on which you want to run standalone diagnostics.
System Response
Client Status
#name:Cstate:
ClientName:diagnostic boot has been
enabled:
The client system is registered on the NIM server and
enabled to run diagnostics from the NIM server.
#name:Cstate:
ClientName:ready for a NIM operation:
or
#name:Cstate:
ClientName:BOS installation has been
enabled:
The client is registered on the NIM server but not enabled
to run diagnostics from the NIM server.
Note:
If the client system is registered on the NIM server
but Cstate has not been set, no data will be returned.
0042-053 lsnim: there is no NIM object
named "ClientName"
The client is not registered on the NIM server.
706
Eserver
pSeries 670 Service Guide
Summary of Contents for pSeries 670
Page 1: ...pSeries 670 Service Guide SA38 0615 03 ERserver...
Page 2: ......
Page 3: ...pSeries 670 Service Guide SA38 0615 03 ERserver...
Page 12: ...x Eserver pSeries 670 Service Guide...
Page 16: ...xiv Eserver pSeries 670 Service Guide...
Page 18: ...xvi Eserver pSeries 670 Service Guide...
Page 324: ...Yes Go to Step 154A 14 on page 302 304 Eserver pSeries 670 Service Guide...
Page 718: ...698 Eserver pSeries 670 Service Guide...
Page 848: ...L3 Cache Shorts Test Step 4 828 Eserver pSeries 670 Service Guide...
Page 849: ...L3 Cache Shorts Test Step 5 Chapter 9 Removal and Replacement Procedures 829...
Page 851: ...L3 Cache Shorts Test Step 2 Chapter 9 Removal and Replacement Procedures 831...
Page 853: ...L3 Cache Shorts Test Step 4 Chapter 9 Removal and Replacement Procedures 833...
Page 854: ...L3 Cache Shorts Test Step 5 834 Eserver pSeries 670 Service Guide...
Page 971: ...7040 Model 671 Media Subsystem 1 2 3 4 5 6 7 8 9 10 Chapter 10 Parts Information 951...
Page 973: ...Power and SCSI Cables to the Media Subsystem 1 2 3 5 4 6 Chapter 10 Parts Information 953...
Page 986: ...966 Eserver pSeries 670 Service Guide...
Page 990: ...970 Eserver pSeries 670 Service Guide...
Page 1018: ...998 Eserver pSeries 670 Service Guide...
Page 1020: ...1000 Eserver pSeries 670 Service Guide...
Page 1028: ...1008 Eserver pSeries 670 Service Guide...
Page 1031: ......