Quote:
Originally Posted by
johnf
Right the good news is the NIM server knows that the LPAR is there and ready to be installed. It also knows that certain resources are allocated to it.
Please excuse me if I am "Teaching my Granny how to suck eggs".
How did you try to boot the LPAR, from the NIM server? Or have you started the LPAR to SMS and setup the network boot configuration. This as you well know includes the IP address of the server, its subnet mask, and the IP address of the gateway. You can then PING the NIM master to make sure the network between the NIM master and client is open with no firewall in the way, which often happens.
Again if I am telling you things you already know please excuse me. The things I have outlined above are the usual reasons a NIM client will not boot from the NIM master.
Johnf, don't worry I do not get offended if you will tell me something I know already
I'm happy if someone is trying to help me .
Every time I go to SMS and set up IPL and ping NIM server. But the thing is that I can ping NIM server but I can not use bootps for some reason.
I have contacted our network team to confirm, that ports 67 and 68 are not blocked to this particular managed system.
If they say that there are no ports blocked I will assign physical ethernet adapter to lpar to avoid VIOS and will see if it was caused by VIOS or not.
---------- Post updated at 12:31 PM ---------- Previous update was at 12:06 PM ----------
So I have tried to boot up via physical ethernet adapter from another NIM server and avoided VIO server and still I can not boot. I can ping the NIM server but not use bootps protocol.
Still waiting for network team to confirm if bootps ports are blocked or not.