Overview
Yet another annoying issue with vSphere 4.1 upgrades. This seems to happen when there are only 2 servers in the cluster with HA configured. As always, this site is here to provide a central repository of information for VMWare vSphere and related products. I am working on vCloud 1.0 as well, so stay tuned for further details regarding Chargeback, etc.. View 4.5 is rocking!!!! 7 vSphere upgrades so far this month from ESX 3.5 using VMWare Update Manager...Works great!!!
Network redundancy message when configuring VMware High Availability in vCenter Server
Symptoms
When configuring the VMware High Availability (HA) in a vCenter Server, you see the message:
Host <xxx> currently has no management network redundancy.
Resolution
This message appears if the Service Console does not have network redundancy configured properly and can be safely ignored.
To prevent this message from appearing and to comply with proper network redundancy, VMware recommends that you add a second service console on a different vSwitch and subnet. Alternatively, you can add a second vmnic to the service console vSwitch.
To suppress this message on ESX hosts in the VMware High Availability (HA) cluster or if the warning appears for a host already configured in a cluster, set the VMware HA advanced option das.ignoreRedundantNetWarning to true and reconfigure VMware HA on that host. This advanced option is available in VMware Virtual Center 2.5 Update 3 and later.
Note: If the warning continues to appear, disable and re-enable VMware High Availability in the cluster.
To set das.ignoreRedundantNetWarning to true:
- From VMware Infrastructure Client, right-click on the cluster and click Edit Settings.
- Select VMware HA and click Advanced Options.
- In the Options column, enter das.ignoreRedundantNetWarning.
- In the Value column, enter true.
Note: Steps 3 and 4 create a new option.
- Click OK.
- Reconfigure HA.
No comments:
Post a Comment