Cisco Data Center Nexus 9000v VXLAN 002 - Legacy L2 Network Problem Statement and Demo

[@naingaung7827]

Hi Rob Riker. Thanks alot for your real life experience sharing. Please share like that more in this channel.

[@RedneckTechcontrolle]

Great job and good real life examples. So many networks are filled with these issues, largely because folks don't move beyond " just enough to make things talk" in their design.

[@RobRikerTechChannel]

Indeed, which is why I started with this video. I'm always a bit floored when I see what people still run today that was installed from 2001.

[@HUCERBH3947]

hey Rob you might missed it, but you need to clear the mac address on each switch to simulate mac address flooding again, cuz the N9K1,3 SPINE1 already know where these mac address and on which port they been learned :), great video like always

[@cd8496]

Great video sir! Learned a lot!

[@siddharth2107]

Hi Rob , What is the OS version for SW6,SW7, SW8, SW9 and P1, PE1, PE2,PE3 , ASAv11 and ASAv12 and INET router , If you can please help ?

[@thomasschaffer8452]

Hi Rob, great video. Two questions: Q1: Could VTP pruning help with overpopulating mac address tables in “legacy” environments? Q2: With VXLAN. If you use a single multicast address for several VNIs. Will this also reduce the amount of mac address as compared to traditional environments? I mean every VTEP that is part of that multicast group will still learn all the mac addresses of the hosts that send out BUM traffic, right? So I would say in order for it to scale, you should really divide the various VNIs into corresponding multicast group. Please correct me if I’m wrong or missing something. Thank you in advance!

[@MMLAB442]

Rob, how many videos do you plan to share? Will you explain how to install Nexus 9k in Eve-ng in further videos?

[@RobRikerTechChannel]

I can add that in as an add on video. It's not hard, but I'll add it.