About this article: This article is reviewed against the cited sources. This is source research, not lab validation. Check the stated versions and your own requirements before making changes.
When you configure vSphere HA, vCenter can show a warning that a host has no management network redundancy. Broadcom's KB prints it as Host <xxx> currently has no management network redundancy. It means the host reaches the rest of the HA cluster over one network path only. Broadcom's fix is a second vmnic on the management vSwitch, or a second management network on a different vSwitch and subnet. An HA advanced option hides the warning, but the single path stays.
What the message means
vSphere HA agents exchange heartbeats over the host's management network. On ESXi hosts this is, by default, a VMkernel network. Broadcom's vSphere 8.0 guidance on HA networking says "A single management network ends up being a single point of failure and can result in failovers although only the network has failed." A failed NIC, a pulled cable or a switch reset on that one path is enough.
The vSphere 8.0 HA checklist asks for at least one management network in common between hosts, and recommends two. Broadcom's networking page gives two ways to get redundancy:
- A NIC team of two NICs on separate physical switches, set Active or Standby.
- A second management network connection on a separate virtual switch. HA then sends heartbeats over both.
Broadcom KB 317612 says the cause is "if the network redundancy configuration within the Service Console/VMkernel Port Management Network is incorrect" and adds "This message can be safely ignored." That is Broadcom's wording. This guide treats the warning as a real finding, because a single path can cause the false failover the networking page describes.
Version scope matters for the silencing option. KB 313261 lists das.ignoreRedundantNetWarning for vSphere 5.0, 5.1 and 5.5, and says HA reports a config issue "if the host is not configured with redundant networks for the networks used by HA". Broadcom's vSphere 8.0 page of HA advanced options does not list it. KB 317612 gives no version range. Check whether your vCenter Server accepts the option before you rely on it.
NetLeverage runs VMware vCenter, vSphere and ESXi.
Likely causes
| Cause | What you see | How to confirm |
|---|---|---|
| Management vSwitch has one uplink | The warning appears on one host or on every host built the same way | esxcli network vswitch standard list shows one uplink on the vSwitch that carries the management VMkernel adapter |
| Two uplinks exist but one is not in the team | Warning stays after you cabled a second NIC | esxcli network vswitch standard policy failover get -v vSwitch0 shows the second vmnic under Unused Adapters |
| Second NIC has no link | Two uplinks listed, one with link down | esxcli network nic list shows Link Status Down for it |
| Warning stays although two uplinks work | Summary tab still shows the message | Broadcom KB 308058: the message can display "even though there are two available uplinks" |
| HA agent was not reconfigured after a NIC was added | Warning predates the network change | Broadcom's guide: after adding a NIC "you must reconfigure vSphere HA on that host" |
Prove the cause before changing anything
All of these are read-only. Run them in an ESXi shell on the host named in the warning. The commands are those Broadcom lists in KB 326175 for viewing a standard vSwitch.
List the standard switches and their uplinks:
esxcli network vswitch standard list
List the VMkernel interfaces and the physical adapters with their link state:
esxcli network ip interface list
esxcli network nic list
Read the teaming policy of the switch that carries management traffic. KB 326175 says this command shows the active, standby and unused NICs:
esxcli network vswitch standard policy failover get -v vSwitch0
A good result is two vmnics, both with link up, both under Active Adapters or one under Standby Adapters. A bad result is one uplink, a second uplink under Unused Adapters, or a second uplink with link down. Broadcom's KB 311349 shows output of the failover command with the fields Load Balancing, Network Failure Detection, Notify Switches, Failback, Active Adapters, Standby Adapters and Unused Adapters.
If the host uses a distributed switch, read the uplinks of the host's management port group in the vSphere Client instead. The esxcli standard-switch commands above do not describe a distributed switch.
Fix
Choose the fix that matches the cause. The first is Broadcom's recommended one.
Broadcom's HA networking guidance says: "When changing the networks that your clustered ESXi hosts are on, suspend the Host Monitoring feature." It says to re-enable Host Monitoring after you reconfigure vSphere HA on all hosts. Suspending and re-enabling it is a change in its own right and belongs in your change process. It is not given as a step here, and the warning under the uplink step repeats the vendor's precaution.
If the warning stays although two uplinks work (the KB 308058 case), Broadcom's first listed remedy is to reconfigure vSphere HA on the host, with the Reconfigure HA menu item, as in the steps below. The same KB also lists disabling and re-enabling HA and restarting the management agents. Those two are disruptive and are not covered here.
Add a second uplink to the management vSwitch
The second NIC's physical port must be in the same Layer 2 broadcast domain as the first. Broadcom's teaming guidance says "All ports on the physical switch in the same team must be in the same Layer 2 broadcast domain."
First save the current switch settings. Keep the output in your change record:
esxcli network vswitch standard list
esxcli network vswitch standard policy failover get -v vSwitch0
esxcli network nic list
Disruptive step: the next command adds a physical NIC to the standard switch that carries this host's management traffic. The steps after it may also change the teaming order and reconfigure the HA agent on the host. If the NIC's cable goes to the wrong VLAN or network, the host can lose its management connection or the HA agent can report a new fault. Broadcom also says that changing network hardware or settings "can interrupt the heartbeats that vSphere HA uses to detect host failures, which might result in unwanted attempts to fail over virtual machines", and that Host Monitoring should be suspended first on a clustered host.
If your change process has suspended Host Monitoring, add the uplink (KB 326175 gives this form), then read the policy again:
esxcli network vswitch standard uplink add --uplink-name=vmnic1 --vswitch-name=vSwitch0
esxcli network vswitch standard policy failover get -v vSwitch0
If vmnic1 appears under Unused Adapters, move it to Active or Standby in the vSphere Client: on the host, Configure, Networking, Virtual Switches, Edit settings, Teaming and failover. Then, in the vSphere Client, right-click the host and choose Reconfigure HA (KB 317612 calls the same menu item Reconfigure for vSphere HA).
To undo it: if you moved the uplink between groups, move it back to the group recorded in the saved failover output. First check with esxcli network nic list that the original uplink (vmnic0 in the example below) shows Link Status Up. If it does not, do not remove vmnic1. Then remove the uplink, compare the result with the saved output, and reconfigure the host with Reconfigure HA again.
esxcli network vswitch standard uplink remove --uplink-name=vmnic1 --vswitch-name=vSwitch0
esxcli network vswitch standard policy failover get -v vSwitch0
Add a second management network instead
Broadcom's alternatives are "a second service console on a different vSwitch and subnet" (KB 317612) and a second management network connection on a separate virtual switch (HA networking guidance). Broadcom's guidance says to keep the vmkNICs used by vSphere HA and by other features on different subnets. Creating a VMkernel adapter and a switch is a larger change, and it belongs in your normal change process. Broadcom's guidance is to reconfigure HA on the host after the network changes.
Silence the warning (hides the finding)
Broadcom's Set Advanced Options page says "Because these options affect the functioning of vSphere HA, change them with caution." Use this only when a second path is not wanted.
First save the current option list. In the vSphere Client, browse to the cluster, Configure, vSphere Availability, Edit, Advanced Options, and write down every option name and value shown.
Risk: adding the das.ignoreRedundantNetWarning option hides the warning for every host in the cluster. A host that later loses its second path will not warn you. Reconfiguring HA on each host afterwards reconfigures that host's HA agent.
In the same Advanced Options list choose Add, type das.ignoreRedundantNetWarning as the option and true as the value, and click OK. Then right-click each affected host and choose Reconfigure HA. KB 317612 adds "If the warning continues to appear, disable and re-enable VMware High Availability in the cluster." That step turns HA off for the whole cluster and is not covered here.
To undo it: reset the option to its default value in the vSphere Client, so the list matches what you saved. Then reconfigure each host with Reconfigure HA again. Broadcom's page says an advanced option you set "persists" until you reset it, so confirm the list afterwards.
Example (illustrative): esx01.example.com is in a cluster with esx02.example.com. Its vSwitch0 has vmnic0 only, and vmk0 carries management traffic. vCenter shows the warning for esx01. The saved failover output shows vmnic0 under Active Adapters and nothing under Standby. vmnic1 is cabled to a second switch, in the same VLAN, and esxcli network nic list shows it with link up. The administrator adds it to vSwitch0, finds it under Unused Adapters, moves it to Standby, and reconfigures esx01 for vSphere HA. The warning clears. esx02 was built the same way, so it needs the same change.
Confirm the fix
esxcli network vswitch standard listshows two uplinks on the management vSwitch.esxcli network vswitch standard policy failover get -v vSwitch0shows both under Active Adapters or Standby Adapters.esxcli network nic listshows Link Status Up for both.- After you reconfigure the host for vSphere HA, the warning no longer appears on the host's Summary tab.
What to watch afterwards
- Tell the vSphere HA administrator before network maintenance, as Broadcom's guidance asks.
- After adding any NIC to a clustered host, reconfigure HA on that host.
- Apply the same change to every host built the same way. Compare their uplink lists.
- If you used the advanced option, record it where the next administrator will see it.
Read next
Related articles you may want next.
- VMware'Cannot complete the configuration of the vSphere HA agent on the host': read the second half of the messagevSphere HA fails with 'Cannot complete the configuration of the vSphere HA agent on the host'? Match the message suffix to its cause and fix it in order.Read article
- VMwarevSphere HA did not restart some VMs: reading the event trail and checking admission control and isolation settingsSome VMs stayed down after a host failure, or isolation powered VMs off? Read the HA events and fdm.log per VM, then check policy without pulling a cable.Read article
- VMwareHow to design and troubleshoot VMware networkingBuild a distributed-switch network and diagnose VLAN, MTU, uplink and vMotion failures without guessing.Read article
Risks and limits
- These commands have not been run or lab-tested.
- Broadcom's KB 317612 covers vCenter Server and ESXi, was updated 07-07-2025 and gives no version range. The option table in KB 313261 gives versions up to 5.5.
- Teaming settings other than the uplink list (load balancing, failover detection, failback) are not changed here. Broadcom's HA networking guidance names route based on originating port ID and Failback set to No as recommended settings for a management NIC team.
- Adding a NIC to a host that uses a distributed switch is done through the distributed switch in the vSphere Client, not with the standard-switch commands.
Sources
- Network redundancy message when configuring vSphere High Availability in vCenter Server — Broadcom Knowledge Base 317612, updated 07-07-2025, accessed 22 November 2026
- ESX/ESXi host displays warning message when test condition is false — Broadcom Knowledge Base 308058, updated 08-28-2026, accessed 22 November 2026
- Advanced configuration options for VMware High Availability in vSphere 5.x, 6.x, 7.x and 8.x — Broadcom Knowledge Base 313261, updated 03-19-2025, accessed 22 November 2026
- Configuring Standard vSwitch (vSS) or virtual Distributed Switch (vDS) from the command line in ESXi — Broadcom Knowledge Base 326175, updated 09-23-2026, accessed 22 November 2026
- Changing Beacon Probing settings using the command line — Broadcom Knowledge Base 311349, updated 10-18-2026, accessed 22 November 2026
- Best Practices for Networking — Broadcom TechDocs, vSphere 8.0, last updated 19 November 2026, accessed 22 November 2026
- vSphere HA Checklist — Broadcom TechDocs, vSphere 8.0, last updated 19 November 2026, accessed 22 November 2026
- Set Advanced Options — Broadcom TechDocs, vSphere 8.0, last updated 19 November 2026, accessed 22 November 2026
- vSphere HA Advanced Options — Broadcom TechDocs, vSphere 8.0, last updated 19 November 2026, accessed 22 November 2026
- What is Teaming and Failover Policy — Broadcom TechDocs, vSphere 8.0, last updated 19 November 2026, accessed 22 November 2026
- Configure NIC Teaming, Failover, and Load Balancing on a vSphere Standard Switch or Standard Port Group — Broadcom TechDocs, vSphere 8.0, last updated 19 November 2026, accessed 22 November 2026
This article was originally published on .