hypervisor integration + DVS + LACP

[bruno.fernandes]

Hello guys,

I´m currently configuring Hypervisor Integration with an ACI Pod, and I have the following question:

1. I have a 3 node cluster, on each node and I will let the vSwitch0 in standard mode for things like (management and vmotion), bur for production networks I'm creating a dVS trough APIC integration (so it's the APIC that creates the DVS on the vCenter side), per host this dVS will have two uplinks , each uplink is connected on different leaves (leaf101 and leaf102), I want to use an 802.3ad bundle , I have checked that LACP is configured in Active mode ..... I have checked that lacp-bpdu are received and sent (on both sides .... leaf .... esxi) ....... but per documentation on VMware site it states that I should configure a "LAG" entity .... but I don't see this anywhere :(    .... Is this normal ? Am I missing something ?

Facts just to clarify:

1. 2xSpines + 4xLeaves

2. Vmware 6.0 , Ent-Plus licensing for all hosts

3. 3 x hosts cluster ..... this hosts are pizza-boxes .... no blades here

4. 2 x uplinks on vSwitch0 for management and vmotion purpose

5. 2 x uplinks on new dVS for production ..... I want this 2 x uplinks to form an 802.3ad bundle .... On the Fabric side the two ports where this uplinks connect area configured has a vPC-bundle in active mode

Thanks,

Bruno

[Robert Burns · Accepted solution]

No need to create the VMware LAG.  Since the APIC handles management of the switch all the bundling is done automatically.  This is referenced in the Virtualization Guide as well.'

http://www.cisco.com/c/en/us/td/docs/switches/datacenter/aci/apic/sw/1-x/virtualization/b_ACI_Virtualization_Guide_1_2_1x/b_ACI_Virtualization_Guide_chapter_1_2_1x_0300.html

Note

When working with ACI and vSphere VMM integration, Link Aggregation Groups (LAGs) are not a supported method of creating interface teams on distributed switches created by the APIC. The APIC pushes the necessary interface teaming configuration based on the settings in the Interface Policy Group and/or AEP vSwitch policy. It is not supported or required to manually create interface teams in vCenter.

Regards,

Robert

[bruno.fernandes]

Thanks Robert

Regards,

Bruno