Cisco APIC Layer 3 Networking Configuration Guide, Release 6.2(x)
Is this content helpful?
Thank you for your feedback. Your response has been recorded.
AI responses are currently only available to logged in users. Log in
Only ask questions about this document. To ask questions about this product as a whole, go to Technical Documentation .
Suggestions
Sorry, we couldn't generate a response for this query.
Cisco APIC Layer 3 Networking Configuration Guide, Release 6.2(x)
Updated: April 17, 2026
Want to summarize with AI?
Log inConfigures a remote leaf resiliency group within the fabric using the GUI. This process involves defining the group name and associating a TEP pool to group remote leaves.
All the spines and the ToR switch in the fabric ACI site must be upgraded to R6.1.3 before enabling remote leaf resiliency group feature in the fabric.
Follow these steps to create a remote leaf resiliency group using the GUI.
On the menu bar, choose Fabric > Inventory .
In the Navigation pane, choose Pod Fabric Setup Policy .
The Pod Fabric Setup Policy pane appears.
Double-click a Pod.
The Fabric Setup Policy for a POD pane appears.
Navigate to the Autonomous RL Group area and click the + symbol.
The Create Autonomous RL Group dialog box appears.
Enter the remote leaf resiliency group name in the Group Name field.
Click the + symbol in the Remote IDs field and choose a TEP pool to group the remote leaves into this group.
Click Submit to create a remote leaf resiliency group.
The remote leaf resiliency group details appear in the Autonomous RL Group area of Fabric Setup Policy pane.
Need help?
(Requires a Cisco Service Contract)
The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.