Originally posted by: alaix

Hi guys,

I am trying to install a new machine (lpar on p520 aix 5.3) via nim but it is hanging on 0608
the server nim and the client are not on the same vlan. I have created a network and allocated the resources to my client.
The ping test is successful but when I launch the isntall it hangs on 0608

I have checked the /etc/bootptab file and is correct.
I have checked the /tftpboot and is correct.
I have checked the NIC and everything is correctly defined.
I have rechecked the network used by the client and is correctly defined.
Everything is exported properly.
I have done another installation to another client in the same vlan and on another vlan (not the same for the one I have a pb as it is the only client in this vlan) of the nim master and it works well.

The client has all the resources allocated to be installed.
Cstate = BOS installation has been enabled
prev_state = ready for a NIM operation

I have put the tftpd on verbose mode and have this on syslog.log:

Jun 30 08:10:33 myservernim daemon:info tftpd4694168: 00000108 EZZ7044I : mytestmachine RRQ <file=Received , mode=/tftpboot/mytestmachine.info, recognized options: octet>
Jun 30 08:10:33 myservernim daemon:info tftpd4694168: 00000108 EZZ7029I : Status Read request for mytestmachine : /tftpboot/mytestmachine .info
Jun 30 08:10:39 myservernim daemon:err|error tftpd4694168: 00000206 EZZ7039I : Status Timeout
The status Timeout of the tftpd could be generated by a firewall ?
Any idea ?

thanks in advance
Cheers
Al.

Originally posted by: bassemir

Just this week I had the exact same problem. Also installing on a p520 (I am using IVM, not that it makes a difference). The problem I had was the route on the NIM server was not correct. Take a look at your /etc/niminfo, the last line will be something like: export ROUTES=" default:0:9.3.245.1 ". Mine was wrong. It was not pointing to my client's gateway system.

Now I can't tell you what my NIM support guy did but when he changed that route so it pointed to my client's gateway I was off and running. After he made his change I had to delete and recreate the niminfo file (using smitty nim).

Hope that helps....

Rich

Originally posted by: SystemAdmin

In the mean time, firewalls are definitely one of the major things to check while using NIM. Make sure port 69, etc. is open. It's funny that I faced similar situation (I can't remember the error code) and I ended up loading the OS from CD then installing mksysb via NIM and it worked fine. So, in your case you probably want to assign CD/DVD drive to that LPAR, load it from CD and then try to build it via NIM. This is given that you made sure all the nim definitions are correct.

I also ran across this link talking about 0608:

http://www.ibm.com/developerworks/forums/dw_thread.jsp?message=13861322&thread=132328&forum=907&ca=drs-fo

Please let us know the outcome.

hth

Originally posted by: alaix

Hi,

thanks for the reply. It was definitly a firewall pb. I used a spare IP adress and install aix and then reconfigure the network on my lpar.

Cheers