Netboot problem

UNIX AIX
1

I have a 55A which is connected to a solitary HMC and a CMS management server. I fired off a netboot from the CMS server which was working fine restoring a NIM mksysb image. I left it running and when I came in this morning code 554 was displayed (Boot device problem!) I have subsequently tried to fire off the netboot again and it fails in the "spanning tree" part. The operator code for the LPAR is CA00E1F7. Anyone any ideas?

2

hello,
try this website:
http://publib.boulder.ibm.com/infocenter/eserver/v1r3s/index.jsp?topic=/ipha6/firmwareprogcodes.htm

hth....

lt0001us

3

Many thanks useful site address as it lists all the codes. However it confirms what I thought as the code I mentioned before results in the meaning "Cannot find the boot device" well there's a surprise. What I do not understand is this is in answer to a netboot! That does not make any sense!

4

hey, did u follow the link in the CA00E1F7? subsequent research shows that the boot issue(s) could be:

  • did u setup and execute the "ping test" and and am assuming is was successful as u executed the NIM install
  • bootlist is screwed up
  • the installed image may not be viable
  • it may help to shut the image down completely, then reactivate from the profile
    • this will refresh the boot image by picking up any changes
  • most importantly: if u can, turn off spanning tree..........
    • a direct connect if possible but if u have to cross subnets, then use spanning tree.....

all ideas & as in any NIM install, good luck is required.....
once you do succeed, try to capture all u did that worked and catalog that, that did not.

5

normally , if the ping work , is a firewall port dropped problems , you're in a firewalled environment ??

post more information please ...

6

hhhmmm, firewalls are not necessarily the issue all the time. sometimes nim does not like hopping vlans.... static routes must be established in this case. firewall rules play much havoc with nim though, your are correct.
the URL posted earlier is a useful tool.
pay attention to the LED values as well.
each LED value is significant and will tell you LOADS of info just from the LED.
keep posting if issues still exist but pls be as specific with postings to allow for better feedback.

hth.... lt0001us

7

you have reason ... firewall is not the cause all the time , others network problems .... or the nim master environment itself . Without more informations the analysis is a sort of bingo :wink: