Network failure detection Link status onlyĪruba 8320 VSX Primary VSX Static LAG (lag30) status:Īruba 8320 VSX Secondary VSX Static LAG (lag30) status: INFO: IP hash load balancing should be set for all port groups using the same set of uplinks. INFO: In the IP hash load balancing policy all physical switch ports connected to the active uplinks must be in link aggregation mode. The more I dive deeply into VSX Static LAG the more this configuration become interesting from the management standpoint.below my findings about VSX diagnostic done against my configured lag30 and its member interfaces 1/1/33.ĪrubaOS-CX GUI reports the VSX (Multi-Chassis) Static LAG lag30 as Up (both interfaces are Up on both nodes):ĮSXi host reported Up state for involved NICs' ports:ĮSXi vSwitch2 used to test VSX Static LAG (lag30): (2) As far as I understood Static LAG member ports are, once aggregated, all partecipating but, with regards to Static LAG versus LACP LAP, the difference is that Static LAG has no control protocol to manage member ports status and relationship with peer's LACP LAG (so this explain the term 'Non Protocol' used by HP/HPE).this main difference means less control-related features (like no Failover, no Hot-Standby port, no canditate aggregable port configuration verification.illuminating blog articles here and here).the interesting point is that Static LAG versus LACP LAG doesn't necessarily mean that load balancing algorithms are different in favour of LACP LAG (they are, indeed, the same).it's just that vSphere requires specifically to use 'Route based on IP Hash' with Static LAG (so operating on VSS).which basically means using the well known 'src-dst IP' load balancing algorithm (as it often happens using LACP LAG). (1) OK.still I don't understand if a Static LAG (so in a scenario, as you said, with some 'intelligence' on Host's physical network ports side and on the peer Switch side) is better or worst than leaving the vSphere Host's physical network ports in Active/Active and letting the vSwitch to balance egress traffic (generated by VM) to physical network.is using Static LAG overcomplicating the scenario (considering that we have VSX as peer) or not?

How to fix lag on mac os x in vmware