VMware Networking Community
Obearon
Contributor
Contributor

NSX 4.1 for Mission Critical Environment?

My understanding is that NSX 3.2.x is the current VMware recommended NSX build. 

I am having requests to upgrade to NSX 4.1.x specifically so they can go vCenter 8.x and update TKR version for a DEV environment..

I am hesitant as I consider NSX 4.1 pretty much release code with way more bugs/less adoptability. We have our most important mission critical environment dealing with life safety on NSX and I believe it is a risk to upgrade from 3.2.x at this time. 

Does anyone have a different opinion? Anyone running anything critical on 4.1.x? What is your experience? 

 

Thanks

0 Kudos
6 Replies
bmcb555
Enthusiast
Enthusiast

Personally I've stuck with 3.2.X for the same reasons as yourself, however, going to 4.X maybe a non-starter for you depending on which version of 3.2 you are on. Currently there is no direct upgrade path from 3.2.2 so it maybe a non-starter for you anyway depending on your environment

https://docs.vmware.com/en/VMware-NSX/4.1/upgrade/GUID-FAFED150-0652-4B7D-9B5E-5F655C22FE48.html

All the bug fixes from the latest 4.1 release are available in 3.2.3 without any of the new additions of 4.X which for me wasn't a big deal. Unless there is something in 4.x you want to use 3.2.3 would be my own recommendation. Stable and no issues thus far

 

0 Kudos
Brisk
Enthusiast
Enthusiast

We deployed NSX 4.0.1 in our environment a couple of months ago but haven't upgraded to 4.1 yet. Mainly because there was nothing in the release that was super compelling for us and because we heavily rely on Terraform for our automation.

No issues with 4.0.1 to report though.

Tags (1)
0 Kudos
Obearon
Contributor
Contributor

It seems that 3.2.2.x can still upgrade to 4.1.0.2, but there is no path for 3.2.3 

https://interopmatrix.vmware.com/Upgrade?productId=912&isHidePatch=false

 

The only requirement for 4.x would be the support for vCenter 8.x. Which is only required because they want to upgrade Tanzu TKR to 1.25.7, however I don't believe it's worth the risk. I will recommend to just build out K8s on openshift since VMware support for new Kubernetes version is pretty much non-existent. They have no details on when 1.26 will be supported and it's been out for a year. 

 

Obearon
Contributor
Contributor

Thanks for the input Brisk. 

 

Hoping to hear from others as well if they experience any issues in 4.x

0 Kudos
bmcb555
Enthusiast
Enthusiast

I'd to recently upgrade from 3.2.2 and was told by VMware it is not supported, about 3 weeks ago so things might have changed.

0 Kudos
DanielKrieger
Enthusiast
Enthusiast

Currently I have no problems with NSX. 4.1.0.2. It is also part of VCF5 and I currently see no reason not to use it. If you are on NSX 4.1.0, I would definitely update to 4.1.0.2 as there is a nasty bug.
https://kb.vmware.com/s/article/92309

----------------------------------------------------------------------
My Blog: https://evoila.com/blog/author/danielkrieger/
0 Kudos