KB ID 0000231 Dtd 17/04/10
As far as errors go this one’s pretty straight forward (and very common). I’ve seen it in ESX3 and VSphere networks, with high availability clusters.
To fix the problem you can do any one of the following.
1. Ignore the error, HA will still work (though it’s simple to stop it giving an error).
2. Present another physical NIC to the virtual switch that has the Service Console/Management port. On a host with loads of NIC’s that easy, but if your pushed for NIC’s then that’s not an option.
3. The easiest, and my preferred option; You already have Vmotion running for HA, so simply add a Service Console (or a vmkernel management port if your running ESXi) to the vmotion switch, you will never need to connect to it anyway, and it will stop the system presenting this error.
Select your Vmotion switch and select “Add Networking” If you’re on an ESXi host then select “vmkernel”, or on an ESX host select “Service Console”
Now you can either wait, or right click each host and select “Reconfigure for HA“
Related Articles, References, Credits, or External Links