There’s plenty of debate in the networking community about the merits of extending layer 2 networks, when you should do it, how you should do it, what pitfalls you should avoid, and what benefits you should expect. Join us as our panel discuss the finer points of what you should consider when you are considering extending layer 2 in your network.
—–
Outro Music:
Danger Storm Kevin MacLeod (incompetech.com)
Licensed under Creative Commons: By Attribution 3.0 License
http://creativecommons.org/licenses/by/3.0/
Chris Kane
Guest
Kevin Meyers
Guest
Nicolas Michel
Guest
Outro Music:
Danger Storm Kevin MacLeod (incompetech.com)
Licensed under Creative Commons: By Attribution 3.0 License
http://creativecommons.org/licenses/by/3.0/
Podcast: Play in new window | Download
Great discussion.
In my experience I’ve seen the requests come in from the Server guys, with the lame excuse of recoverability, when in fact all they seem to be doing is “saving” on hosts (and probably licenses). I agree that there are legitimate reasons for L2 between DC’s, but I’ve historically pushed back where possible and practical.
I’ve recently deployed an EVPN fabric using anycast gateways with a VxLAN overlay, and have found it much friendlier when needing to provide x-site L2 domains, very much MPLS’esque in nature. I’ve also incorporated routemaps to leak 32bit routes at the opposing DC when a host moves, as a means of addressing the tromboning and route symmetry concerns of my legacy DCI.