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:

  1. Tiny Datacenters, PROD is 4 racks, DR is 2 racks, our network is 100sites of warehouses on a WAN.
  2. 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.
  3. 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.
  4. 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

1330
beef-o-lipso•

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.

7
wolffstarrCCNA R&S / Security, Studying CCNP (1/3)•

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.

1
OrsonScottHard•

I feel very bad for you. 450 APs and no controller? And they want to implement SDN? That's mind bottling.

5
andpassword•

mind bottling.

The trouble is, their minds have already had too many bottles.

9
devrdanderOP•

I was shocked too, thankfully 90% of the sites are cookie cutter so the vlan's are all identical. So we can template the AP Config. That doesn't mean if the day came that we needed to add an SSID or change a WPA Key we'd be screwed.

Should note, our first 500AP Licensed 5508 arrived last week, and we're in the process of implementing it.

1
UnethicalCatLawyerUnethical Cat Lawyer•

You should poke your Cisco partner in the eye.

The 5508 is being replaced by the 5520, which at this point should easily be available in distribution channels. It supports up to 1500 APs, and its licensing model is slightly cheaper. Because it is the new thing, it'll have a longer distance to EOL too.

5
devrdanderOP•

We got the WLC Grey Market (9k for a 500lic model), they wouldn't pay for a new one. The idea is to show them all the things the WLC can do, and use that experience to justify buying new ones in FY2017

edit: Should note, 95% of our wireless is used for handheld scanners in warehouses, we're still phasing out 802.11b handhelds from small sites. They just don't need the throughput.

3
UnethicalCatLawyerUnethical Cat Lawyer•

Ahh that makes sense then. In that case then the 5508 will be great for you, it's a nice unit.

Life will be much better for you on the WLC.

1
junglizer•

What kind of handhelds? We've got a bunch of those shitty Motorolas. Standard to warehousing, but terrible wifi issues.

1
snorkel42•

I stopped reading when you wrote that they could barely keep vcenter running. Perhaps instead of getting drunk at VMWorld vendor parties they should be going to some VMware classes.

5
devrdanderOP•

Yeh, vcenter is down for maintenance weekly, the VM guys at my last job never had this many problems. Don't really know what is up.

2
snorkel42•

VMware is some of the most reliable software I've ever dealt with. Nearly every problem I've ever seen with it was self inflicted or due to shitty vendor drivers (looking at you HP)

My current company had all sorts of VMware issues when I started and I was shocked at all the crashes. Then I got to know the senior admin....

2
TooMuchBinturongCCNP•

What problem are they trying to solve whereby SDN is the solution?

3
devrdanderOP•

The only reason they've told me so far is MicroSegmentation (ZeroTrust Firewalling between hosts) and DR Failover, though I have no idea which systems need NSX for DR Failover and I could do it cheaper with some 4K's and VXLAN. The 7206's we are using now are up for replacement finally in 2016.

1
mathech~]$ cd /pub && more whisky•

LOL, they haven't even priced out NSX have they?

3
devrdanderOP•

HAH nope, i'm hoping the price alone will shut this down, but I've been surprised before.

1
EtherealMind2etherealmind.com & CCIE•

NSX licenses are the same cost as ESX licenses. So, whatever you are paying today for VMware, you will pay that much again to get a network.

2
realged13Network Analyst•

500k for us hahaha.

1
dcoulson•

We use NSX for micro-segmentation with Palo Alto HV-1000 integration - Awesome stuff, and does what it says it will do. The native NSX firewall is pretty basic, so don't expect too much out of it.

That said, to do that you don't need all the VXLAN crap.

2
EtherealMind2etherealmind.com & CCIE•

Negatives.

  1. Price. NSX is really expensive.
  2. Hard. NSX is hard to learn. Much harder than vCenter/ESX
  3. Buggy. lots of reports of bugs, getting better now but expect to have some sort problems that need vendor support.
  4. Resellers. Too new for them to have skills.

Disclaimer: I am very impressed by NSX and think it will be a great SDN solution. I would use it, but the question was how to burn it with fire.

Positives:

  1. tightly integrated SDN solution with VMware - the only solution that will tightly integrate with VMware, probably ever.
  2. the oldest and most mature SDN platform.
  3. Big vendor, trusted already. Existing supplier.
  4. Lots of certified (brainwashed?) engineers who can untangle the hard bits because its complicated.
2
wintermute000 alphabets•

Its not that 'mature' from what I hear. We've been deploying it in several environments (large telco) and the stories I hear are hair raising (frankly, on the same level as some of the ACI 1.0 WTFs). OTOH I know a few people online who swear by it, so what do I know (only have lab/VCP-NV XP personally). I do enjoy driving it, that's for sure, though my initial enthusiasm has waned a little upon realising that yes, everyone else is doing virtual distributed routers/switches stitched together with overlays (contrail, openstack etc.)

This is another hilarious thread right here for example

https://www.reddit.com/r/vmware/comments/45570r/nsx_be_very_careful_rebooting_vsphere_server/

NSX is a great system in many ways but in the hands of a bunch of amateurs I see much hilarity. Also from what OP has described, I can't really see the use case - what's there to automate/multi-tenant?

1
My-RFC1918-Dont-LieAsk me about Netgear!•
1
EtherealMind2etherealmind.com & CCIE•

LOL

It depends ™

3
pugl33t5aa85bcffaef7b16c05ad2bd6b3e9505•

What is the deal with people on this thread claiming NSX == SDN? Have the marketers really got that much of a hold?

1
HotGoreSpooky Skeleton•

If meraki can say they are SDN, then anyone can!

2
pugl33t5aa85bcffaef7b16c05ad2bd6b3e9505•

My device forwards packets. My device runs software. Ergo my device is software defined networking. QED.

5
realged13Network Analyst•

Copying what I posted on another thread. We are a software company and have warehouses like you as well.

We have had our private cloud team working on the vRA platform for like 2 years now and still are no closer to being done (mainly because they're idiots, but I digress).

Then we started looking into doing a POC for NSX. As soon as our company saw the price tag of about $500k to implement it into our environment, it stopped dead in its tracks. We've already heavily invested in our current data center when we moved into our new building about 2 years ago.

If a company is in the middle of a hardware refresh and new data center build, I could see NSX being implemented, but with a lot of companies, they already have their large flavor of Cisco, Juniper and HP gear that the costs savings just aren't there yet.

1
EdibleFeces•

There are a couple of uses for SDN out there imo, 98% of business will spend more money on it that what they will gain at this point in time. Are you guys exceeding the 4096 unique vlans that you can fit into a vlan header?

Are you adding servers at a rapid pace to your data center? I'm talking hadoop like rapid pace.

Those are the 2 biggest drivers I see causing people to move to an environment like this. If this is not you (which it sounds like it is not) I would not give it a 2nd look for another 3-5 years.

-1
devrdanderOP•

That's my understanding too, and we don't have anywhere near that. We spin up maybe 1 server a month tops, and most of the time its just decomissioning old physical servers and migrating them to VMs. By the end of 2016 though, we should be 100% virtualized and that will only be about 300 VM's in total. The Unix systems will stay on their dedicated hardware/san. Only Windows/Linux is being virtualized.

1