IBM RS/6000 SP, Руководство по определению проблем

Страница: 75 / 316

This soft copy for use by IBM employees only.
psspscript resources script
mksysb_1 resources mksysb
cw_tr0
networks tok
sp2n02 machines standalone
sp2n03 machines standalone
sp2n04 machines standalone
sp2n05 machines standalone
sp2n06 machines standalone
sp2n07 machines standalone
sp2n08 machines standalone
5. While still on NIM master, issue lsnim -l <client_name> to list the NIM
client definition for the node that is having the problem:
# lsnim -l sp2n03
sp2n03:
class = machines
type = standalone
Cstate = ready for a NIM operation
Mstate = currently running
Cstate_result = success
prev_state
= not running
platform = rs6k
if1 = spnet sp2n03 10005AFA082C ent
cable_type1 = bnc
cpuid
= 000116875700
6. From the first step (output of
splstdata -b -l 3
), node 3 (sp2n03) had a
response (bootp_response) of
disk. The Cstate
attribute for the client
Ready for nim operation from the output of
lsnim -l sp2n03
is correct.
Based on the bootp_response for the node, the Cstate attribute is fixed and
will have fixed NIM object allocations for the client. The following table could
be used as a ready reckoner for NIM client definition information.
Table 5. NIM Client Definition Information
bootp_response Cstate Allocation
install BOS installation has been
enabled spot psspspot
lpp_source lppsource
bosinst_data n o p r o m p t
script psspscript
mksysb mksysb_1
diag Diagnostic boot has been
enabled spot psspspot
bosinst_data p r o m p t
maintenance BOS installation has been
enabled spot psspspot
bosinst_data p r o m p t
disk or customize Ready for a NIM
operation
2.9.1.1 Export Problems
Following is an example of a successful export by the
exportfs
command from
NIM master node sp2n01 of a NIM client sp2n08, which is ready to be installed.
Chapter 2. The Installation Process
55