Lists the operational constraints, compatibility requirements, and downgrade behavior for external bridge domain profiles that group SVIs with different access encapsulations.
Review these guidelines and limitations before you configure an external bridge domain profile.
-
The external device or hypervisor must block Layer 2 loops. A loop can occur when an external switch relies on Spanning Tree Protocol to prevent loops.
-
When you configure an external bridge domain profile for an SVI, the system deletes and re-creates the SVI.
-
An external bridge domain profile is scoped to an L3Out. On a node, you cannot map two different access encapsulations to the same external bridge domain profile.
-
Bridge domain grouping does not support the
ctxencapsulation scope, which corresponds to the VRF option in the Cisco APIC GUI. -
Grouped SVIs with different access encapsulations cannot share a node.
-
If you downgrade from release 5.2(3) to an earlier release that does not support multiple encapsulations for L3Out SVIs, the system makes these changes to an L3Out configured with multiple encapsulations, an external bridge domain profile, or both:
-
Deletes the
l3extBdProfileEncapAllocatormanaged object that allocates multiple encapsulations. -
Deletes all
l3extBdProfilemanaged objects. -
Deletes all
l3extBdProfileContmanaged objects. -
Deletes all
l3extRsBdProfilemanaged objects.
-