Preparing the Physical Pod IPN Connectivity Using REST API
The physical spines in the on-premises data center communicate with the Cisco Application Centric Infrastructure (ACI) Virtual Pod (vPod) virtual spine (vSpines) in the remote site over a Layer 3 interpod network (IPN). Before you create the Cisco ACI vPod on the remote site, you first ensure that a physical pod can communicate with it. You also configure a unique unicast IP address and a routable subnet for each physical pod.
Note |
The procedures using the Cisco Application Policy Infrastructure Controller (APIC) refer to routable subnets as external tunnel endpoint (TEP) pools. |
Procedure
Step 1 |
Log in to Cisco APIC: Example:
|
Step 2 |
Configure the TEP pool: Example:
|
Step 3 |
Configure the node ID policy: Example:
|
Step 4 |
Configure infra L3Out and external connectivity profile: Example:
|
Step 5 |
Configure a routable subnet for each physical pod. Example:
In the example, Note the following:
|
Step 6 |
Configure a unique unicast TEP IP address and an IP addressed used as the Border Gateway Protocol (BGP) next hop for each physical pod: You can configure these addresses from the reserved portion of the external TEP pool (routable subnet). Example:
|
Step 7 |
Configure a multiprotocol BGP (MP-BGP) route reflector. Example:
If you configure a route reflector and want to remove the spine switch from the controller in the future, you must disable Route Reflector on the BGP Route Reflector Cisco APIC page before removing the spine switch from the controller. Not doing so results in an error. To disable a route reflector, right-click on the appropriate route reflector in the Route Reflector Nodes area in the BGP Route Reflector page and select Delete. See the section "Configuring an MP-BGP Route Reflector Using the GUI" in the chapter "MP-BGP Route Reflectors" in the Cisco APIC Layer 3 Networking Configuration Guide. |