rebooting HMC

manoj.solaris · April 12, 2012, 4:01am

Hi,

I would like to know wheather rebooting HMC will impact on Management Systems or Lpar inside it is showing?

or I have to shutdown LPAR then only reboot HMC.

johnf · April 12, 2012, 5:44am

Rebooting the HMC does not have any affect on the running systems. The only consequence of such an action is if an LPAR / frame were to go defective whilst the HMC is coming back. Also the listing of the systems will not change when the HMC comes back unless system discovery has been set to run on reboot.

manoj.solaris · April 12, 2012, 6:54am

can you please let me know how to set system discovery off state. or how to check the current settings.

zxmaus · April 12, 2012, 8:03am

your lpars will report the reboot potentially as sysplanar error in errpt
there are certain firmware levels on the hmc that might cause loss of lpar profiles / corruption

But either way - no need to bring down your lpars or the frame ... but make sure you have a backup of your configuration

rbatte1 · April 12, 2012, 10:37am

Be sure that this really is an HMC, not a VIO server. We learnt 'the hard way' when someone performed an action that booted the (single) VIO server and suddenly the dependant LPARs ceased. As they were not set to auto-start, we spotted the problem pretty quickly, but still had the worry of crash recovery.

I hope that this is not the case for you.

Robin
Liverpool/Blackburn
UK

manoj.solaris · April 16, 2012, 2:33am

Thanks to all for your valueable input.

I am facing the issue of No Connection in HMC, Two Physical Servers are connected in HMC.

Servers are up and LPAR are running fine.

but I am getting NO Connection in HMC for Managed Systems.

I have checked the cables ,cables are connected properly.

How to troubleshoot the issue?

gito · April 16, 2012, 4:15am

Do you have one or 2 HMCs ?

I had problem with power5 servers sometimes they needed 24h or more to connect HMC. Probably it is related to dhcp expiration

If you have 2 HMCs - you can use second one to force network renew in ASMI

If you have physical access to server disconnect FSP (HMC) ports directly from managed system wait 1 min and connect them back they should rediscover faster.

If you have only remote access you can disable port on switch and connect it back.

kah00na · April 16, 2012, 5:29pm

I had the same issue and opened a PMR with IBM. This was our problem and resolution.

PROBLEM: The HMC is not connected to the p570. We rebooted it but it still did not connect. Its �State� says �No Connection�.

RESOLUTION: Remove the connection and read it.

Get the IP address for the managed system with the failed connection from:
lssysconn -r all

Remove the connection with:
rmsysconn -o remove --ip 192.168.255.254

Automatically find all the managed systems with:
mksysconn -o auto

The auto-find-managed-system should take about 5-10 minutes and the managed system should just appear. After 20 minutes, I replaced the network cable and the managed system came up within a few seconds. I had to reset the password for the user �HMC� so that the p570 could be brought back into the HMC. There were also some sysplanar errors that came out around 3:30 p.m. today about which we will need to open a hardware ticket with IBM.