Introduction
This document belongs to WAN link terminating on border leaf between two datacenters.
OR
Border Leaf to Border Leaf communication between two datacenters / two sites.
OR
L3OUT configuration of Site 1 Border connecting to Site 2 Border leaf Point to Point directly.
Prerequisites
- ACI fabric ready
- WAN link between two datacenters.
Requirements
Devices: APIC, Leaf, Spine, Border leaf.
Link - WAN link working fine between two Datacenters with CRC errors.
Components Used
This is built on test Setup to simulate the connectivity between two DC connecting on BL.
Network Diagram
Configurations
Site 2 configuration:
- Create vlan pool
2.Create L3 Domain
- Create AAEP
4.Create interface policy group (IPG)
5.Create switch profile.
- Create Tenant and VRF
8.Applying VZANY contract
9.Create static L3out
Rest configuration of Site 1 L3out is same as Site 2 L3out.
10.L3out Node profile.
11.Create L3out Interface profile.
12.Changing the mac address of L3out to have communication from Border Leaf to Border Leaf.
13.Create External EPG of L3out.
Site 1 L3out configuration
14.Site 1 L3out
- Create Node profile
16.Create Interface profile of L3out
17.Here in L3out ip address assigning, not changed the mac address kept same as already changed the mac address on other end.
Verify
Testing the site point to point ping connectivity.
Pinging continously Site 1 to site 2 p2p IP address.
Keeping same mac address both side, there is ping drop.
As soon as mac address changed of L3out at either side of L3out. Ping starts.
Ping response
Troubleshoot
show ip interface brief vrf PROD_VRF (on Border leaf)
show ip route vrf PROD_VRF (on Border leaf)
iping -V PROD_VRF 10.1.1.2
Note:
Change the mac address of the L3out. Step 12
It is like HSRP mac address between two connecting device is having same because of the same Group id. If we change the mac address of the hsrp then, it will work.
Likewise L3out has mac address same, if we change then it will work.
