Two of our VM guys are Drinking the NSX Coolaid, should I talk them out of it?
We have two Admins at VMWorld and they now think that if we don't implement NSX our ESXi will fall apart. Hell they can barely keep vcenter working. I started here last December and I don't think we're near ready for any kind of SDN, and should work with one in a lab/dev environment for at-least a year or two before it moves into production. I also don't see a use case for it but I'm not technically knowledgeable about SDN having not used it, I just have ready quite a bit haven't seen a use case yet. Here's a bullet point list of our environment:
- Tiny Datacenters, PROD is 4 racks, DR is 2 racks, our network is 100sites of warehouses on a WAN.
- We don't develop 99% of our software. What development we do is mostly outsourced, on old UNIX servers running automation software that talks to PLCs, and Sharepoint/Database reporting.
- Most of our infrastructure should just be setup Active/Active. AD, File Servers, Exchange, don't need a SDN to support DR, they systems were built with redundancy in-mind years ago.
- MicroSegmentation (Though one guy keeps says micro segregation :-\ ) We can't get the warehouse operations team to let us turn on the windows firewall on our servers/workstations. Since they "make the money" according to upper management, they get their way. Security is an uphill battle for us right now. We're just starting to look at NG firewalls in 2016, I'm still talking management out of split tunnelling on our VPN routers and pushing all external traffic through centralized firewall/ips/ids/webfiltering. We're not ready for zero trust security, and I don't think our systems could really live in a world like that.
So give me your top 3 yay's or nay's on SDN right Now. I'd like to add I'm not against new technology, i'd love to learn SDN, however I've been doing corporate IT for 10 years, and hearing things from the VM admins like "We're going to be on NSX within 6 months" makes me cringe. You just don't implement unknown technology that quickly. Also on my top 10 shit to get fixed list, SDN is about #99 right now. Replacing the ancient CAT OS switches still in production, implementing proper QoS on our WAN and getting our 450 AP's onto a controller come first.
TLDR; We're an enterprise stuck in AIX and windows 2008r2 land. We don't have Programmers, and our security is just starting to become a focus. How do I talk management out of SDN besides showing them the pricetag? Or should I just let it happen and add the bullet point to my resume?
Posted Sep 3, 2015, 1:58 PM UTC
NSX makes sense if you're
bringing up and dropping VM's daily/hourly
if your making use of DRS and/or live vmotions often
if you want to experiment with microsegmentation
If you want to leverage the internal load balancing, firewalling, and any other service that is integrated with it
If you have more than on vCenter and want to manage between them.
If your DC is pretty static, then NSX won't help. It won't hurt, but it won't help.
Frankly, I'd make them come up with use cases that demonstrate an immediate need and how NSX will help.
With a small DC and 100's of warehouses, I'd think a SD-WAN product like Nuage would be more useful simply because they thnig is so damn simple to use it will save you management time.
That's what I was thinking too. If you're going to let SD-Anything near your network right now, SD-WAN is the thing. Generally if you do it right - meaning, you start using internet-grade circuits to replace high-bandwidth private WAN connections - your net-cost after a year or so is actually a negative number.