Host xxx currently has no management network redundancy

[SomeClown]

Just upgraded my VC to 2.5 and have this error. Actually, to be fair I had a bunch of DRS/HA errors and a host that wouldn't migrate or do anything. So I unconfigured DRS and HA, then reconfigured, and life is good except for this annoying exclamation mark on my cluster. I read somewhere else that this was due to a lack of secondary Service Consoles, so I added those (on different physical NICs) but still have the error.

Thoughts?

[starz]

This happens when you do not have network redundancy for your Service Console, it does not have anything to do with you having several Service Consoles or not.

To get rid of this "problem", you need to connect at least 2 physical nics to the virtual switch that the Service Console Portgroup is connected to. I suggest putting Service Console and VMotion in one virtual switch, put two NICs into that virtual switch and manually loadbalance the Service Console to use one NIC as primary and the other as secondary, and do the same with VMotion but with the NIC order turned around.

[SomeClown]

Ahh... makes sense I suppose. I'll have to look at my structure and see how much I want to do that. As it stands right now I have the 1st Service Console on a dedicated NIC which is plugged into a switchport assigned to the appropriate VLAN, and the VMkernel is on a different dedicated NIC which is on a different VLAN. The rest of the NICs are assigned to a group and are connected to switchports in trunking mode so that I can dynamically assign networks.

I've attached a screenshot for anyone interested.

At least now I know why that message is there... though I wasn't immediately thinking MPIO when I heard redundancy... I just figured it wanted another console on a different NIC.

Thanks!

[SomeClown]

One other interesting thing: I lost the ability to manually migrate (High or Low Availability) virtual machines once I did this VC upgrade to 2.5. But... if I unconfigure HA, the errors referenced in this thread go away and I get back my ability to migrate. Seems as if 2.5 is locking-up my migration ability if I don't have the redundancy in management.

[Texiwill]

Hello,

I do not have redundant NICs for my SC and I can still use vMotion, so I think something else is going on..... I suggest opening a VMware Support case as this should not be the case.

Best regards,

Edward L. Haletky

VMware Communities User Moderator

====

Author of the book 'VMWare ESX Server in the Enterprise: Planning and Securing Virtualization Servers', Copyright 2008 Pearson Education. Available on Rough Cuts at http://safari.informit.com/9780132302074

[SomeClown]

I should clarify--I can migrate hosts if I unconfigure HA. Once I reconfigure HA, I have the network redundancy error and no ability to even manually migrate. So, for this second I'm running with no HA and we'll see what happens after I get the hosts upgraded to 3.5 (I'm on 3.02) later today. If I still have the problem after looking through the logs I'll open a case.

[Texiwill]

Hello,

I have HA/DRS configured as well and it works just fine with a non-redundant SC/vMotion. I think you have something else going on.

Best regards,

Edward L. Haletky

VMware Communities User Moderator

====

Author of the book 'VMWare ESX Server in the Enterprise: Planning and Securing Virtualization Servers', Copyright 2008 Pearson Education. Available on Rough Cuts at http://safari.informit.com/9780132302074

[SomeClown]

Dunno... worked before the VC upgrade to 2.5. Works now after the 3.02 upgrade of all hosts to 3.5. Basically upgraded the ESX Hosts, then unconfigured and reconfigured HA/DRS and now life is good again.

[kinsden]

Hi,

I have just done VC upgrade from 2.0.1 to 2.5. And there are 3 different ESX hosts in the cluster : 3.0.1, 3.0.2 and 3.5. I have got HA and DRS enabled on the Cluster. And I AM ABLE to manually migrate (hot and cold) VMs between the hosts. But I should admit that there were serious issues with our 3.0.2 host after VC 2.5 upgrade. It was completely 'messed up' in that service console was not pingable, it could not ping other hosts, the VC Agent service was crashing and the host could not even list the rpm pacakage details. Had to rebuilt the host!!! Not sure if there's a problem with VC2.5 and 3.0.2!!!

[uq_itee_jkloske]

Hi,

I'm getting this warning under "Configuration Issues" on the Summary screen of the VC Cluster tabs.

Thing is, we're getting it on two of the hosts but the third one in the cluster is fine.

They're all identical hardware and have the same network configs, two nics each (configured as an active and standby).

Originally, they only had a single nic connected to the virtual switch, however in this configuration we still had the two hosts complaining about no redundancy and the third being fine.

Anyway, it's driving us nuts trying to figure out how to get rid of the annoying yellow exclamation mark!

Can someone please provide some pointers on how we might go about getting this sorted?

Jon.

ps: ESX Server 3 for all three hosts, managed by Virtual Center (I think 3.5) with DRS and HA.

[uq_itee_jkloske]

Okay, I got brave and decided to just adopt a "Lets Try This One" approach to see if I could nut it out.

So the trick is you need two things to make the yellow exclamation marks go away:

# Redundant networking \\ This is fairly obvious - it doesn't seem to care if you plug both parts of the redundant link into the same switch (though this is obviously a stupid idea) but it just wants a second NIC added to the service console, or a second service console added to a different nic. Either way it wants two paths to the ESX server to prevent the isolation response kicking in. # HA Agent/Service to restart, reconfigure, or something like that \\ This is the trick - the redunancy message won't go away just by solving the redundancy issue - you need the HA stuff to find out about it, which only happens during a restart or reconfig or similar. I just hit the "Reconfigure for HA" command even though it was already configured for HA and it stopped and started the agent on the host and immediately the yellow mark for that host vanished.

Thanks for stopping by 🙂

[tweav]

Yellow question marks are gone after implementing a reconfigure for VMware HA.

I thought we had everything in the networking section squared away with two service console port on two physical nics, but the error message persisted. All we had to do is Reconfigure (or restart) for VMware HA, and all is well in VM land.

Thanks uq_itee_jkloske for the tip,

--TW

[DCStech]

I thought this information might be useful for those looking for answers.

Suppress "No management Network Redundancy" warning

This release introduces an option to suppress the warning message "Host

xxx currently has no management network redundancy" for a host

configured as a node in an HA cluster.

Set the advanced option das.ignoreRedundantNetWarning to "true" to

suppress the warning on hosts not configured in an HA cluster. If the

warning appears for host already configured in a cluster, set the

option and reconfigure HA on that host to clear the configuration issue.

Search VMware

-T

[vixflix]

Thanks

This solved our Problem

-

---

TheProTel.com

[tharpy]

Running release code (VCMS Build 162856 and ESX Build 164009)....

Cluster warning icon...in cluster Summary tab view, the system reports "configuration issues" that all three of our vSphere hosts do not have management network redundancy.

However, all three hosts have multiple uplinks on the vswitch that the management network is on...

AND

If you highlight the host and look at the summary tab, no such warning is evident.

Removed all the hosts and re-added them, problem went away....for awhile...now back.

Sometimes the system reports that only one of the hosts has no redundancy when, in fact, all are configured exactly the same.

[ejward]

The "das.ignoreRedundantNetWarning" "True" thing worked for me.  Yeah, I know 2 paths is best but, that's just not going to be happening at the moment.  Pop up an ocasional warning.  Not a constant warning that my make me less sensitive to more critical warnings.

[sayyidsaif]

Below is the steps to remove the configuration issue warning (No management network reduntancy) form the hosts.

Right click the cluster àClick edit settings àclick the V sphere HA and go to advance option àAdd the option and value as shown below.

Option is "das.ignoreRedundantNetWarning" and value is 'true'

Then right click each host and click Reconfigure for Vsphere HA.

[aaal]

just to add on something even if you find that you already have 2 or more nics set for redundancy network (and probably you have done the rest which the other posters mentioned) but the warning still persists, then you may have look at your port group settings again.

If you have vmotion enabled, re-check that your switch properties that you have the Vmotion and Management Traffic enabled (most likely its just the vmotion issue). I made this silly mistake once by not enabling it.