Detailed Configurations for the EVPN-VXLAN Network for the Data Centers
This section includes the complete configurations for the following devices:
Data Center 1 Border Spine 1 and Border Spine 2 (DC1-Spine1 and DC1-Spine2)
Data Center 1 Leaf 1 and Leaf 2 (DC1-Leaf1 and DC1-Leaf2)
Data Center 2 Border Spine 1 and Border Spine 2 (DC2-Spine1 and DC1-Spine2)
Data Center 2 Leaf 1 and Leaf 2 (DC2-Leaf1 and DC2-Leaf2)
A simplified WAN router configuration that can be used for testing
Figure 1 shows the detailed topology used in this example.
The configurations are shown as typed, rather than as displayed with a show configuration | display set command. As a result the BGP authentication key appears in plain text instead of the obfuscated form. The authentication key used is for testing purposes and should be changed to suit your environment.
The need to channelize for 10 GE interfaces varies by QFX switch model. Based on the equipment used in this example channelization is not needed at the leaf switches, but is used on the spines for the 10 GE links to the WAN cloud.
Border Spine Device 1 in Data Center 1
Border Spine Device 2 in Data Center 1
Leaf Device 1 in Data Center 1
Leaf Device 2 in Data Center 1
Border Spine 1 in Data Center 2
Border Spine Device 2 in Data Center 2
Leaf Device 1 in Data Center 2
Leaf Device 2 in Data Center 2
Simplified WAN router configuration for testing.
The focus of this example is on the configuration and operation of the spine devices for OTT DCI. As a result the WAN underlay is treated opaquely. From the perspective of the spine devices the WAN routers, and whatever complexity is used in the WAN cloud, for example an MPLS-based Layer 3 VPN, is of no concern. The spines simply use their local BGP peering to exchange underlay routes for the loopback addresses used in each DC.
A simplified WAN router configuration is provided to help in testing and to better illustrate the functionality provided by the WAN cloud, from the perspective of the spine devices. Figure 2 provides a topology that can be used for testing with a single routing device acting as a WAN cloud.