Managing Uplinks for VMM Domains
Beginning with Cisco Application Policy Infrastructure Controller (APIC) Release 4.2(1), you can specify the number of uplinks for endpoint groups (EPGs) that you associate with virtual domains. You can also rename, add, or delete uplinks. You can also configure failover by defining some uplinks as active and some as standby.
Cisco APIC supports specifying and modifying uplinks for VMware vSphere Distributed Switch (VDS) and Cisco Application Centric Infrastructure (ACI) Virtual Edge Virtual Machine Manager (VMM) domains. Cisco APIC supports failover for EPG uplinks for VDS and Cisco Application Centric Infrastructure (ACI) Virtual Edge when it is in native switching mode.
You can specify from one to 32 uplinks for a VMware VDS or Cisco ACI Virtual Edge. However, you are not required to do so; if you do not, Cisco APIC by default specifies eight uplinks, all active. Specifying more uplinks makes it easier to configure failover. You do not need to rename uplinks, but doing so makes it easier to manage them.
Defining some uplinks as active and others as standby is optional; however, doing so enables failover, ensuring that EPG traffic continues to flow even if some uplinks fail.
Note |
You can also manage uplinks by applying different enhanced Link Aggregation Control Protocol (LACP) policies to different distributed virtual switch (DVS) uplink port groups. Enhanced LACP is supported for VMware VDS and for Cisco ACI Virtual Edge. For VMware VDS, see the Enhanced LACP Policy Support section in this guide; for Cisco ACI Virtual Edge, see the section "Enhanced LACP Policy Support" in the Cisco ACI Virtual Edge Configuration Guide . |