Implementing Cisco ACI: Advertise Routes from Border Leaf Switches to Compute Leaf Switches

Advertise Routes from Border Leaf Switches to Compute Leaf Switches

Question

As part of a newly deployed ACI fabric, a pair of border leaf switches have been deployed to provide shared services for all tenants.

The configured L3Out runs OSPF as the routing protocol.

The requirement is to advertise the routes from the border leaf switches to the compute leaf switches.

Which configuration must be implemented to meet these requirements?

Answers

Explanations

Click on the arrows to vote for the correct answer

A. B. C. D.

A.

https://www.cisco.com/c/en/us/solutions/collateral/data-center-virtualization/application-centric-infrastructure/guide-c07-743150.html

In order to advertise the routes from the border leaf switches to the compute leaf switches, the following configuration must be implemented:

B. Define the shared L3Out in the common tenant.

Explanation:

L3Out is a term used in the Cisco Application Centric Infrastructure (ACI) to refer to an external Layer 3 (L3) connection that provides connectivity outside of the ACI fabric. In this scenario, a pair of border leaf switches have been deployed to provide shared services for all tenants, and the configured L3Out runs OSPF as the routing protocol.

To advertise the routes from the border leaf switches to the compute leaf switches, the L3Out must be defined in the common tenant. The common tenant is a pre-defined tenant in ACI that is used to configure and manage shared resources across all tenants in the fabric. By defining the L3Out in the common tenant, the route information can be shared across all tenants in the fabric.

Additionally, it may be necessary to configure OSPF on the L3Out interface of the border leaf switches to advertise the routes to the compute leaf switches.

Option A, Configure a BGP route reflector policy for the Cisco ACI pod, is not applicable to this scenario as the routing protocol being used is OSPF, not BGP.

Option C, Enable Import Route Control Enforcement in the L3Out policy, is not necessary to advertise the routes from the border leaf switches to the compute leaf switches.

Option D, Define the consumer subnet under the consumer EPG, is also not applicable to this scenario as it is not related to routing between the border leaf switches and the compute leaf switches.