Has anyone had any issues with the integrated NICs on the R900 management card not working properly with LACP in vSphere 5.5u2? I have two 6800s using add-in cards on my Extreme Summit 400 stack that seem to work just fine (other than ping amplification), but whenever I plug in more than one interface on the R900s, I lose connectivity to the R900. All ports in the group work individually, none work together. These are new to me R900s. I made an update CD yesterday with DRM, so the firmware should be current. The switch is configured exactly the same for those ports, verified with a config dump. Going back and forth from the R900s to the 6800s in vCenter the vSwitch appears to be configured the same. I'm not sure what else to try at this point.
There are some limitations for LACP on Standard vSwitches (see e.g. http://kb.vmware.com/kb/1004048). Assuming the physical side is configured properly, ensure that the related vSwitches as well as the Port Groups are also configured correctly (IP-Hash load balancing).
André
I wouldn't use IP-Hash as IMO, Beacon Probing is the only real way to detect link failure. Beacon Probing and IP hash aren't compatible with each other.
Okay, so if the desired configuration seemingly isn't supposed to happen... why does it seemingly work on the existing hosts with standard vSwitches?
Beacon Probing and IP hash aren't compatible with each other.
How many vmnics do you use? For Beacon Probing you should have at least 3 vmnics. Anyway, IMO there's no use for Beacon Probing with channeling ports, since a failover should be handled by the network protocol itself.
...why does it seemingly work on the existing hosts with standard vSwitches?
Great question. However, without being aware of your exact network configuration (physical as well as virtual) it's hard to tell why this is working.
André
I have all four assigned to the vSwitch.
Sorry, I guess it's called teaming and not real LACP. Oh God I hate vendors that cripple their products.
