[TheDogBoy]

I have a 7310 CR3 6.1.1 with one 9115-505 attached. This is in a lab environment. I have 3 lpars a VIO server, a NIM Master and an AIX.

On the HMC in the network settings I changed eth0 from private to open and rebooted the HMC and lost the managed server. Is this normal?

[duke900ssd]

Yes, this is quite normal.
By configuring the adapter that is supposed to talk to the managed systems (eth0) as an "open" adapter, you have told the HMC that this adapter is not a "Managed System" adapter, but that it is connected to an open network so the HMC wil no longer apply the deamon used to manage systems (rmc) to this adapter, hence it can no longer see the managed systems.

[TheDogBoy]

Thank you very much..I understand....I thought that eth0 could be either private or public... I guess you have to decide that on the initial setup..

[TheDogBoy]

Also ,is this a recoverable error? Can I still save my test lpars?

[duke900ssd]

eth0 should always be the private adapter, things go all funny if you try and use another adapter.
You should be able to reset it to private and then select discover managed systems they will come back. If not try rebooting the HMC to refresh the ip configuration and the RMC deamon.

[TheDogBoy]

None of that worked what happened when I reset back to Private and rebooted console was that the HMC still did not see the managed 505 server. Also when this happened I noticed i could not access the ASMi VIA ethernet nor the sp via the serial port...I think I am %$#$%..

[duke900ssd]

Pull the ethernet cable fron the HMC port on the system, count to 30 (slowly), plug it back in and try again. This should force the service processor to renew its connection (issue a new dhcp request for it's config).
It will help the HMC discover the managed system if it knows it has server the address.
Also make sure all adapterd on the HMC have been configured, on 6.1 things (again) go all funny if you have unconfigured adapters......
HMCs, don't you just love them?