So sorry for the very late reply, somehow I missed this until now. My comment about cheaper devices was not about bandwidth or latency processing, but about memory for routes. The routing tables on these underlay devices will be exponentially smaller, requiring less memory and therefore will be much cheaper. I hope that helps!

The two can absolutely work apart from one another. LISP traditionally uses its own tunneling mechanism, which is how it's deployed into the service provider space. However, that tunneling mechanism is L3-only, and Cisco needed a tunnel that works for L2 in SDA. Hence VXLAN. Likewise, VXLAN is traditionally deployed into the data center with a control plane protocol like EVPN.

Great question! Every tunneling mechanism is different, and therefore the overhead amount will also be different. VXLAN requires an additional 50-54B depending on the configuration, so we would need the MTU to be set to at least 1550, or 9050 when using jumbo frames. This is one reason we set it to 9216B on Nexus switches - it covers all the overhead we need for jumbo frames. I hope that helps!

@@KishSquared thank you very much.

Overall ISE is meant to be a part of SDA, so it should be well integrated. If you're looking for details/examples then I would reach out to your Cisco team. Hope that helps!

Campus firewalling is performed by ISE integration. Firewalls would still exist at the Internet/DC boundaries, which is just part of the L3 routed network. Hope that helps!

Hey homeslacks! Yes, it comes with preconfigured nodes and I believe I removed those before recording the videos. Unfortunately, I don't have that configuration anymore, so I have nothing I can share from that setup. Are you watching the Cisco UCS Configuration skill? About 5 minutes into the first video, I show how you can change the hardware configuration using the web GUI that comes included. Once you remove any hardware you no longer want, you should just need to go into the UCS GUI and decommission any chassis you removed. I know it's a pain and not as straightforward as a clean slate. Alternatively, you could just use the configuration Cisco provides, there's nothing particular bad about it and you can always modify it to your preferences. I do wish they started you clean, but it's better than nothing for sure. Feel free to hit me up here or on Twitter DM (@KishSquared) if you need more help!

@@KishSquared Hey dude. So i did see and start to mess with the web ui adding/removing hardware but the one area that i have had some blanks on is where one makes the virtual network connections (add/remove). I thought, ahhh easy, i can quick remove the hardware then just add the stuff as i see you used and connect how needed. I think i've seen where/how to create those physical connections. Lame as it is, if you can give me a quick pointer on how to create those physical connections with the emulator i'd be set to just delete the stuff/add what i need/connect as needed to follow along nice and clean. :) Thanks for getting back man, ;)

@@homeslacks Let me take a look and get back to you. It's been a while since I spun up the PE so I'll see what I can find and let you know!

i guess not

I watched this video with playback speed 1.75, worked fine ;)

I enjoy the extra talk that makes me settled in here