Pick a Topic for NSX Deep Dive Software Gone Wild Episode
Dmitri Kalintsev, one of the networking guys from VMware NSX team, has kindly agreed to do an NSX technical deep dive Software Gone Wild episode… and you have the opportunity to tell him what you’d like to hear. It’s as easy as writing a comment, and we’ll pick one of the most popular topics.
Do keep in mind that we plan to do a technical deep dive, and it has to fit within an hour or so or nobody will ever listen to it, so please keep your suggestions focused. “Troubleshooting NSX”, “NSX Design”, or “NSX versus ACI ” is not what we’re looking for ;)
http://content.ipspace.net/get/NSXArch
Fantastic. Please share the business drivers and technical requirements that led you to those decisions. What were the adoption hurdles? Did your CIO simply pick your solution for you, or did you do a bakeoff between several vendors? Was cost the primary driver or was it features (such as automation)? Or the support model?
Let's face it... we all talk to vendors and get their sales pitch. We all read tech blogs and news sites to get the latest emerging trends. Some of us talk to Gartner and other sites to get their opinions. But the community of network engineers is lacking a good way to share success/horror stories that would help other engineers who are about to go down that same path.
1) How to build vSphere/NSX environment with least L2 (i.e. most L3) connectivity i.e. ESXi VTEPs in own subnets, Vmotion, mgmt, ...
2) how to do NSX to physical routing using BGP with multuple edge routers (i.e. traffic engineering/route selection influecing) + connected route redist vs. advertising networks