ESX Host Currently Has No Management Network Redundancy Error
After upgraded to virtual center version 2.5 recently, I found an error message "host ESXhostname currently has no management network redundancy" when I tried to create a new cluster with 2 ESX hosts.
My test setup has one service console & one VMkernel connected to vswitch0 with single network card for both ESX host. The funny part is the problem only happen in one of the ESX host instead of both. I believe somehow this is due to my network design/setup in my test environment.
Again the similar error posted in VMware Communities forum solved my problem.
Basically you have to assign an additional NIC into the service console and VMkernel. Click 'Reconfigure for HA' for any ESX host that showing the error message.
Possibly Related Posts:
- SSH Remote Access Authentication Tips
- Your Password is Disclose
- Ask Google Engineer a Questions
- Set a Good Password Policy On SuSE Linux
- How To Check Which Port Is Listern or Open on Linux
January 22nd, 2008 at 3:57 am
[...] ESX Host Currently Has No Management Network Redundancy Error: This is new to ESX Server 3.5; VMware HA reports a warning when it detects that there is no redundancy for the Service Console. Clearly, this is an attempt to prevent situations where isolation response kicks in, and as the author points out can be mitigated by adding another NIC to the vSwitch where the Service Console port group is located. I have also found that creating a second Service Console port group on another vSwitch will also remove the warning. Duncan of Yellow Bricks also goes into more detail on Service Console redundancy on his blog as well. [...]
April 1st, 2008 at 5:26 am
I noticed the same thing… I had to reconfigure VMWare HA in order to get the message to disappear.