tl/dr: If you upgrade from NSX 6.3.x to 6.4.0 make sure you remove the Control VM HA IP if it is set. Note that I have checked this with DLR and UDLRs.
So I wrote about this the other day and decided to see if it would blow things up during an upgrade to 6.4.0.
With my lab environment running 6.3.2 and the Control VM configured for HA with an IP address set:
I uploaded the 6.4.0.7564187 bundle using the NSX Manager (note that with 6.4 you do it from the vSphere client!)
And started uploading
Enable SSH but don’t join CEiP for a temp environment
And wait …
[Note that I just did 6.3.1 to 6.3.2 to 6.4 and going to 6.4 is taking *a lot* longer for NSX manager.]
oops. I see why it is taking long…
You should not be reading this error message
I hit enter and it came up, so I’ve got that going for me. Which is nice.
Ok, so did the Edge blow up with the IP set like it does in 6.4 if you set the IP and then enable HA?
Nope
Ok, great so upgrading to 6.4 removed the HA IP?
Nope
Oops. And if you disable HA…
Its still there.
Re-enable HA…
Note that repeated tests show that this might not error unless you open the window to change the IP address – even if you don’t change anything!
So, again – remove the HA IP configuration if you set it before upgrading! and then don’t set it in HA during the install or while playing with HA.
