This soft copy for use by IBM employees only.
#------------------ Network Install Manager ---------------
# warning - this file contains NIM configuration information
# and should only be updated by NIM
export NIM_NAME=sphps03
export NIM_HOSTNAME=speth03.aixedu
export NIM_CONFIGURATION=standalone
export NIM_MASTER_HOSTNAME=spcntl.aixedu
export NIM_MASTER_PORT=1058
export RC_CONFIG=rc.diag
export SPOT=spcntl.aixedu:/usr
export NIM_BOSINST_DATA=/NIM_BOSINST_DATA
export NIM_BOS_IMAGE=/SPOT/usr/sys/inst.images/bos
export NIM_BOS_FORMAT=rte
export NIM_HOSTS=
″ 192.168.0.3:
speth03.aixedu
192.168.0.200:spcntl.aixedu
″
export NIM_MOUNTS=
″
spcntl.aixedu:/spdata/sys1/install/pssp/ \
bosinst_data_prompt:/NIM_BOSINST_DATA:file
″
2.10.2 Node Installation Diagnostics
If a node fails to install a mksysb image from its boot/install server in network
boot mode, then try the node conditioning method. Node conditioning may
provide you with information as to where the node install is failing.
The following steps can be used to determine the cause of the node install
failure and how to resolve them.
Step 1: Verify Boot/Install Server is Available
Do the following steps to verify that the boot/install server is available:
1. Determine the client
′
s boot/install server by issuing:
splstdata -b -l
<client_node_number>
and looking at the srvr field, which lists the
boot/install server
′
s node_number.
# splstdata -b -l 3
List Node Boot/Install Information
Node#
hostname
hdw_enet_addr srvr
response
install
last_install_image
last_install_time
next_install_image
-------------------------------------------------------------------------
3 sp2n03
10005AFA082C
1
disk
hdisk0
bos.obj.ssp.41
Sat_May__4_12:57:38
bos.obj.ssp.41
2. Determine the boot/install server
′
s host name by issuing
splstdata -b
-l <server_node_number>
and looking at the hostname.
# splstdata -b -l 1
List Node Boot/Install Information
node#
hostname
hdw_enet_addr srvr
response
instal
last_install_image
last_install_time
next_install_image
-------------------------------------------------------------------------
1 sp2n01
10005AFA18CF
0
disk
bos.obj.ssp.41
Sat_May__4_10:42:40
bos.obj.ssp.41
3. Login to the boot/install server by using
telnet
or the
rsh
command.
# telnet sp2n01
4. Check /etc/bootptab for the node that you are installing. If the node is
not listed in this file, then review the NIM client definition as follows:
•
Determine the client
′
s NIM master.
66
SP PD Guide
Summary of Contents for RS/6000 SP
Page 2: ......
Page 14: ...This soft copy for use by IBM employees only xii SP PD Guide...
Page 16: ...This soft copy for use by IBM employees only xiv SP PD Guide...
Page 106: ...This soft copy for use by IBM employees only 86 SP PD Guide...
Page 178: ...This soft copy for use by IBM employees only 158 SP PD Guide...
Page 214: ...This soft copy for use by IBM employees only 194 SP PD Guide...
Page 248: ...This soft copy for use by IBM employees only 228 SP PD Guide...
Page 290: ...This soft copy for use by IBM employees only 270 SP PD Guide...
Page 292: ...This soft copy for use by IBM employees only 272 SP PD Guide...
Page 300: ...This soft copy for use by IBM employees only 280 SP PD Guide...
Page 304: ...This soft copy for use by IBM employees only 284 SP PD Guide...
Page 308: ...This soft copy for use by IBM employees only 288 SP PD Guide...
Page 310: ...This soft copy for use by IBM employees only 290 SP PD Guide...
Page 316: ...IBML This soft copy for use by IBM employees only Printed in U S A SG24 4778 00...