1s & 0s-Current Trends in DC Networking - Arista VXLAN

Started by that1guy15, July 21, 2016, 12:04:51 AM

Previous topic - Next topic

that1guy15

Current Trends in DC Networking - Arista VXLAN

In my last post I covered the fundamentals and basic design of VxLAN. Now its time to get to the fun stuff, configuration! This post will focus on Arista's VxLAN configuration using vEOS.  Arista has been making serious traction in the DC space.

Throughout this series we will be building on the following topology. EBGP will be used as the routing protocol between spine and leaf nodes as it is
Source: Current Trends in DC Networking - Arista VXLAN

From http://blog.movingonesandzeros.net/
That1guy15
@that1guy_15
blog.movingonesandzeros.net

wintermute000

#1
Interesting!
totally coincidentally....

https://github.com/wintermute000/arista-template

its more of a learning exercise since the arista roles they share on ansible-galaxy are superior (include more conditions, error checking etc.) but it was a useful learning exercise nonetheless.


I have done nothing with cumulus (only so many hours in a day) so look forward to your cumulus writeup

that1guy15

Nicely done dude, Looks good! I will absolutely be jumping into the deep end when I try to automate the deployment of this blog series.

Fired up cumulus last night on ESXi, built a template VM and spun up the same topology minus config.

Honestly if you are comfortable with linux (Ubuntu) then you will be fine.  It is a far stretch from the "industry standard" CLI. But once you get vtysh going it provides a similar UI to the CLI.
That1guy15
@that1guy_15
blog.movingonesandzeros.net

burnyd

Quote from: wintermute000 on July 21, 2016, 06:27:50 AM
Interesting!
totally coincidentally....

https://github.com/wintermute000/arista-template

its more of a learning exercise since the arista roles they share on ansible-galaxy are superior (include more conditions, error checking etc.) but it was a useful learning exercise nonetheless.


I have done nothing with cumulus (only so many hours in a day) so look forward to your cumulus writeup

Go ahead and get into the Ansible 2.1 release with EOS.  You do not need roles anymore so pretty much anything within the CLI you are able to put a playbook against it in Jinja2 format.  Previously you have to go in and put all the eos devices into pyeapi so it could do the translation of Python libraries(Ansible) into CLI on the API wise. 

wintermute000

Yep running the new ones now!

The roles shared by arista on galaxy are nice, exception handling etc

burnyd

Yah they are haha.  All the stuff on galaxy makes it really easy.  But honestly, any part of whats exposed you can now do the whole j2 templates.  Some people are not really into that cli into api but meh it works out pretty well.