Cannot re-configure HA after upgrade vCenter 5.1 to 5.5

[jasiele]

Hi,

I've upgraded vCenter Server Appliance from 5.1 to 5.5 as indicated in KB 2058441.

The upgrade process finished with no problems and I can connect to new VCA 5.5, but now the HA is not working. I've tried re-configuring host for HA but I'm getting an error.

I've tried with a new install of VCA 5.5 and I can add one host (the other one gets me an error) but I cannot enable HA on the new clúster. Maybe the hosts have damaged vCenter or HA agents

Any suggestions?

Thanks in advance,

Jerry

[nkrishnan]

Hi,

50x release onwards vCenter HA (AAM) agent is part of ESXi, it is not pushing from vCenter. The center server host name is resolving (both forward and reverse look up).

After the upgrade, all your inventory and other details are intact, which make sure DB is working fine.

Did you upgrade ESXi server, does it stateless ESXi or installed on Thin. Can you please check the /var/log/vmware/aam logs

[jasiele]

Hi,

I've tried to uninstall the vCenter and HA agents on hosts following KB 1031919 but no luck with this. Folder /opt/vmware/uninstallers/ is empty on the first host and no SSH acces on the other host.

VCA hostname is resolving in both ways and db is correct after the upgrade. I can see all the inventory.

The ESXi hosts are 5.1 from fresh install.

I've checked the AAM logs but can't identify the errors.

Thanks,

Jerry

[jasiele]

Hi,

Getting some advances:

I tried to enable SSH using KB 1039095 but no luck with this. Changes to inetd.conf are not saved and service does not start.

Jerry.

[its_arun]

Hi ,

    Can you post the error message and upload logs w.r.t the issue for better understanding.  You upgraded to 5.5 or 5.5U1?

[nkrishnan]

To do SSH, enable the option provided in ESXi Console

Remote Access to ESXi Shell Using SSH

If Secure Shell is enabled for the ESXi Shell, you can run shell commands by using a Secure Shell cl...as SSH or PuTTY.

Enabling SSH for the ESXi Shell

By default, you cannot access the ESXi Shell using a Secure Shell client. You can enable SSH access ...direct console.

To enable SSH access in the direct console

1	At the direct console of the ESXi host, press F2 and provide credentials when prompted.

2	Scroll to Troubleshooting Options, and press Enter.

3	Select Enable SSH and press Enter once.

On the left, Enable SSH changes to Disable SSH. On the right, SSH is Disabled changes to SSH is Enabled.

4	Press Esc until you return to the main direct console screen.

When 5.1 to 5.5 vCenter Server upgrads, its expected to push new agent of HA in to ESXi to work HA seemlessly with new upgraded vCenter. Looks its failed here.

Try installing new agent by doing following steps

- Login to ESXi

- run command esxcli software install https://<;vCenter Server IP address>/vSphere-HA-depot/index.xml

- It install the agent named vmware-fdm, make sure the agent installation completed by list down the agent by running

#esxcli software vib list |grep -i vmware-fdm

- follow the above step on second esxi server

- Reconfigure HA

Hope it helps

[markdjones82]

I ran into the same issue.  I just evacuated the few hosts that has issues, rebooted, and then reconfigured HA and that resolved the issue.

[jasiele]

Hi,

We are planning a maintenance window so we can shutdown all virtual machines. I'll try to get all possible logs.

nkrishnan: I've tried to enable SSH with these steps but SSH service does not start. The file inetd.conf is empty and I can't save changes on it. I'll try to install vmware-fdm on the maintenance window.

markdjones82: vMotion does not work, so I can't evacuate the hosts. I'll try with the virtual machines powered off.

Thanks for your help,

Jerry

[markdjones82]

Good luck, any reason why vmotion doesn't work???

[jasiele]

Hi,

I'm getting an error each time I try to move a VM to other host. I think the damaged cluster/HA agent is the reason.

Jerry.

[markdjones82]

I have never seen HA cause Vmotion not to work, but if that is the case.  Disable HA temporarily on the cluster, evacuate host, and re-enable.  Then reboot host.