Posted on March 30, 2018 1:55 pm
 |  Asked by David Ron
 |  12982 views
1
2
Print Friendly, PDF & Email

Hello

I’m seeking for a white paper\best practice document that can cover deploying a topology of spine-leaf data center.

The points i’m seeking clarifications are

1. underlay L3 connectivity – is IGP required to be configured between spine and leafs.

2. is multicast a must between spine and leaf for control plan operation? (forwarding BUM packets?)

3. with vxlan, are there any problems using mlags? how can i advertise a certain MAC address is available from two different VTEPs and encapsulate into vxlan from both connections?

4. in terms of configuration, how can i deploy such a scenario?

5. unconventional as it may sound, are there any issues connecting the spines directly to the network, with isis+bgp, as oppose to use some kind of edge leaf or dci leaf.

will appreciate any reference for any document\full config\explanation for those (more may arrive later)

 

Thanks in advanced

David

1
Posted by Stuti Gor
Answered on April 3, 2018 11:01 pm

Hi David,

 Please check if this document helps

https://eos.arista.com/evpn-configuration-ebgp-design-for-evpn-overlay-network/ 

1
Answered on April 4, 2018 7:32 pm

1. Yes, you need some form of dynamic routing protocol between Leaf and Spine. EBGP is typically recommended for several reasons including simplicity, fast failover, “less chatty” etc., Refer to the following links for more information:

https://tools.ietf.org/html/rfc7938#page-13

https://www.arista.com/custom_data/downloads/?f=/support/download/DesignGuides/Arista_L3LS_Design_Deployment_Guide.pdf

2. Multicast is not a requirement although Arista supports Multicast decapsulation to interop with third-party VTEPs. Within the Arista L3 UCN fabric, control-plane options for VxLAN are (a) HER with static flood-lists (b) CVX (c) EVPN

3. VxLAN is supported with MLAG and the MLAG’ed leaf pair seen as one logical VTEP. These links explain VxLAN Bridging and Routing operation with MLAG.

https://eos.arista.com/vxlan-with-mlag-configuration-guide/

https://eos.arista.com/vxlan-routing-with-mlag/

4. Above links should help.

5. You can certainly tie the Spines to other parts of your network. However, general rule of thumb is to keep the Spines “simple” with minimum number of features enabled. This promotes better stability and easier maintenance (Example: software upgrades). External Routing, DCI and services such as Firewall, Load Balancer are usually concentrated on a pair of Service Leafs. 

0
0
Answered on June 12, 2018 3:32 pm

The link does work for me; you’ll need to be logged in to access the link. Alternatively, you can go to https://www.arista.com/en/solutions/design-guides and look for “Layer 3 Leaf & Spine Design and Deployment Guide”

0
Posted by Leonardo Espinosa
Answered on October 10, 2018 1:40 am

Hi,
i’m new to the Arista world. i’m curious about the choise of BGP for the underlay. how come BGP provide best failover than OSPF? can someone explain that or forwarding me to some documents related.
Thanks.
Leo

1
Answered on October 10, 2018 6:41 pm

Hi Leo,

The benefits of BGP including fast fallover and sub-second convergence are covered in RFC7938 and L3LS Design & Deployment guide; links quoted earlier in the thread.

The key to fast convergence is running eBGP single-hop sessions over direct point-to-point Leaf-Spine routed links on 10/40/100G Ethernet which inherently offers Link Fault Signaling.

Cheers
Naveen

Post your Answer

You must be logged in to post an answer.