Originally posted by: colinfer
>
> Hi All,
>
> I am facing very strange problem. I have created NIM server with 6.1 TL4SP3. Now I was having SPOT and MKsysb of the same version. I am able to install the client using this spot and mksysb. Now I got the requirement of installing the 5.3 ML11SP3 client. So using the mksysb of 5.3 ML11SP3, I have created one spot but when tried to install the client using this spot and mksysb of 5.3 it is getting stuck at 0608. One more thing I am trying on the same client where I have installed 6.1 using same NIM so no problem of network. Also NIM client is having just one adapter. client.info file is ok and /tftpboot is also ok, permission wise and other configuration. What must be stucking to install 5.3. As per my knowledge spot and mksysb is enough for installation, is it something else which is blocking specific for 5.3. Please guide.
>
> Thanks
My experience with this is that a LED 608 hang can be caused by an incorrect entry for the default gateway when defining a network for NIM.
If the NIM client is on a different logical subnet to the NIM, an additional network needs to be defined on the NIM.
The default gateway address is that
used by the client to access the NIM master.
NOTE: This is NOT used as a type of static route by the NIM master to route to the client.
At the time the client issues a bootp request to the NIM master, credentials are confirmed and the NIM master sets the default gateway of the client to the value used when defining the network on the NIM.
Example:
Define a Network
Type or select values in entry fields.
Press Enter AFTER making all desired changes.
Entry Fields Network Name
pnet4 Network Type ent
Ethernet Type Standard
Network IP Address
http://10.96.235.0 Subnetmask
http://255.255.255.0 Default Gateway for this Network
http://10.96.235.1 Other Network Type
Comments
VLAN 235 NOTE: The default gateway in this instance is NOT that of the NIM server but that of the network for the remote client.
A LED 608 hang can also be caused by the deletion of the 'nobody' user.
This is required for tftp which runs as TWO processes - one of which is
run by 'nobody'. A process listing (ps -ef | grep tftp) should show 2
active processes.
Regards