Log in to ask questions, share your expertise, or stay connected to content you value. Don’t have a login? Learn how to become a member.
Video: 8. DCI Addendum: Direct Peering - Apstra 4.2.1 in eve-ng
Video hashtag: #4.2.1_eve_video-8
I created this video as a direct result of viewer request. While building a physical lab with a higher-ed customer, and lacking spare L3 devices to provide OTT DCI connectivity, it was readily apparent that the DCI would need to be direct between fabric devices.
Considering this use-case, I found it to be compelling and put together these instructions.
In this video, we will add a direct link between our spines for DCI. While the workflow is similar to OTT DCI, it is not the same. Because each fabric is treated as a separate entity, using an IP pool for external connectivity results in a transit net (/31) being assigned to the blueprint you're working on. This means one IP assigned to the local blueprint, and the other IP reserved.
This reservation prevents us from assigning the IP to the other fabric, so instead, we skip the pool and manually assign a unique transit net!
As always, I'll take you through the steps which include using Time Voyager to restore the lab to its starting state (in case you want to test this, but revert back to just OTT DCI).
Thank you for watching!