VMWare Management Network Redundancy Problem

[DefenderAtkins]

There is a very strange thing happening here.

1. my network setup; Fibre A and B NICs from the host are connected to the fabric switch which has trunk to core switch.
2. Copper port is connected to copper switch which has separate trunk to core switch. 
3. I run continuous ping from a physical PC which has access to management network.
4. when I shut the port from the switch going to Fibre A NIC on the host, management network fails over to Fibre B.
5. I lost 5 pings and it comes back up.
6. I re-enable link to Fibre A.
7. when I shut the port from the switch going to Fibre B NIC on the host, management network fails over to Fibre B.
8. I lost 5 pings and it comes back up.
9. when I shut ports from the switch going to both Fibre A and B, management network does not fail over to copper.
10. 100% ping lost from both PC ... AND Copper switch.
11. When I re-enable Fibre A or B or both, then I can ping from PC  AND Copper switch can ping the management IP again.
12. I don't understand why the state of Fibre A and Fibre B could have such effect on the Copper port.

Here is how my teaming and failover is set up for Mgmt portgroup in the DVSwitch:

[pwilk · Accepted solution]

Hi DefenderAtkins,

It seems like your Ethernet uplink has no access to the management network (either on the VMware side of things or the trunk to core network is broken) - could you provide me with your full network configuration on the hosts? (uplinks, networks, port groups etc.)