Ingram2
Contributor
Contributor

"This host currently has no management network redundancy", but there is?

Jump to solution

While in vcenter, the summary tab for a host displays this message:

"This host currently has no management network redundancy"

I attached pictures of the Host > Configuration > Networking and Host > Configuration > Networking Adapters pages. It looks to me like the management network is behind 2 nics teamed together.

What am I doing wrong? How can I fix this?

Thanks

Tags (4)
1 Solution

Accepted Solutions
a_p_
Leadership
Leadership

One more idea. Righ click the hosts and run "Reconfigure for HA".

André

View solution in original post

12 Replies
a_p_
Leadership
Leadership

Are both vmnics "Active Adapters" in the Management port group's settings?

André

0 Kudos
Ingram2
Contributor
Contributor

Yes, they are, I think. I attached a picture.

Should they be?

0 Kudos
a_p_
Leadership
Leadership

The screen shot looks like the vSwitch settings. What about the port group settings?

André

0 Kudos
Ingram2
Contributor
Contributor

Yes, it is too. Here is another screenshot

0 Kudos
a_p_
Leadership
Leadership

Did you add the second uplink just recently? Is there an uncleared warning/alarm which needs to be acknowledged?

If this is not the case you may try to restart the Management Network on the host.

Adré

0 Kudos
Ingram2
Contributor
Contributor

I setup the 2nd nic about a week ago. I restarted the vcenter server, as well as all the hosts, but the message is still there.

Any idea?

0 Kudos
a_p_
Leadership
Leadership

One more idea. Righ click the hosts and run "Reconfigure for HA".

André

View solution in original post

Ingram2
Contributor
Contributor

Hmmm...

After doing that, the warning was gone. Thanks. I'm not sure why, but...

I guess that's something you are supposed to do after setting up a cluster or HA?

0 Kudos
a_p_
Leadership
Leadership

It looks like the HA agent (FDM) on the host did not automatically update its configuration after you added the second NIC to the vSwitch. "Reconfigure for HA" or disable/enable HA in the cluster settings basically force the configuration.

André

MauriceD
Contributor
Contributor

I had something similar for 2 of 3 hosts - my conclusion was it was because those hosts were rebooted while vCenter was offline/frozen a few days ago.

Yes,  "Reconfigure for HA" fixed the problem for both, now that vCenter was up.

Then, many of my machines suddenly displayed error with current time "VSphere HA machine failover failed" - not sure if this indicates the HA action failed back when the vCenter was offline 2 days ago but it was only logging it with time-tag now since I restarted HA -  or that the reconfigure was threatening to reboot my guests???

0 Kudos
coolsport00
Enthusiast
Enthusiast

The "Reconfig HA" worked for me. Thanks for the solution! (because the KB: http://kb.vmware.com/kb/1006421 , didn't apply)

Shane

(@coolsport00)

0 Kudos
ConwyGogledd
Contributor
Contributor

ReConfig HA worked for me too.  I got this error message after upgrading our vCenter to 5.1 and our hosts up to 5.1.  Thanks for the top tip!

0 Kudos