NSX: Be VERY careful rebooting vSphere Server instance when running NSX (for now).
I thought I'd throw out a warning in case this can bite other NSX users (especially if they're running it in prod).
We hit a bug (which turned out to be a known problem and is being worked on) where if you restart your vCenter Server services (for an instance that's using NSX), random hosts will 'lose track' of their NSX VTEP(s) and refuse to do any virtual network traffic (it tries to create new VTEPs multiple times, but fails, as well). This seems to have something to do with how vCenter Server pushes out the VDS config to the host when it comes back up? I don't know. I just know it bit us (although thankfully just on our test instance), and any VMs on the host that were going over a vxlan network dropped off the air, as expected when VTEPs/NSX are broken.
NSX's Installation area will show the affected host(s) broken for VXLAN.
I'm not sure how wide-spread it is. I didn't see it mentioned in the release notes so I'm guessing not too big, but still. It took VMware Support a couple hours to figure it out, but then determined it was a known issue and being looked at. Be careful ;)
Environment, in case it's based off that and you're similar:
NSX 6.2.1
vSphere 6.0
NSX Config: Load Balanced/SRCMAC (switching to SRCID later), 2 VTEPs/host.
Edit: Got word back from support, it's a known issue that will be fixed in 6.2.2 (which has no ETA).
Posted Feb 10, 2016, 9:44 PM UTC · edited
I hit a huge bug with NSX. Pricing.
We hit the same bug. We're not a small company, but until the pricing comes down, it's WAY to expensive for us.
Funny we hit that bug too, it's KB:6Kx2
What is your use case for NSX and what alternative did you end up using in it's place?
This little piggy had none :(
We have tons of VLANs with firewalls dotted all over the shop managed by a network team. We've got devs wanting to throw up environments left right and centre and another team looking heavily at AWS. We either need to bite the bullet and go NSX or look at a parallel setup of OpenStack in the coming year, IMO..
Definitely a prime use case for NSX. Automated provisioning of networks, firewall rules and a simplified physical network. I asked the OP what their use case was specifically because I see a lot of folks barking about the cost of the product. But in most circumstances, they either didn't understand OpEx or have a valid enough use case to make the shift to SDN in the first place. That's most cases, there will always be those that are just driven away to the CapEx to set it up in the first place too.
Yep, but I just got pricing (literally today) and it'd cost us close to $800k to implement across all our environments. NOT gonna happen :(
We plan on rolling it out for 5 different labs. Price for vdi is a fraction of the price for our server cluster. It's 5 times more expensive to use it for half the machines.
Static lab environments? Or are you talking 5 different internal private clouds that will be used for automatic provisioning of labs? If it's the former, you wouldn't use 90% of what makes NSX expensive, and I can understand why it would turn you off. If it's the latter, I'm curious what you'll be using in it's place as an alternative.
This makes me think you're talking about 5 static lab environments as opposed to a self service internal cloud. To this point, you have alternatives in the VDI market to accomplish roughly the same thing. NSX is in a league of it's own in many ways. It sounds like you may have just wanted bits and pieces of what NSX offers instead of the full suite. And to that point, I wouldn't expect the price of NSX to be remotely justifiable.
Not trying to be combative btw. I just see a lot of folks (and obviously you have a ton of people that agree with you) comment about how the price tag of NSX turns them off. But more often than not I find that there wasn't a valid use case to justify the cost to begin with.
We'll be using NSX. The labs will be auto provisions based on customer needs, but they are going to be VDI labs. That's why I feel like there is a bug in pricing. The vsphere servers are all pretty static, but cost 5x as much to license. The benefits make sense in R&D, but don't fit the bill for production at the current price point.