NSv Firmware Upgrade

Ive run into a fun issue where I have deployed the 6.5.0.2 version that was presented as my download in my portal. I have downloaded, unpacked, configured, registered, repacked, and shipped off to my data center to be uploaded and installed. After a couple of fun "I didnt expect that to happen" with the registration, I find out there is a new firmware. However, I cannot upgrade from 6.5.0.2 to 6.5.4.4 and have to perform this all over again! This requires a day of my time, and the involvement of multiple people from my data center. Do you foresee this being the case with future firmware releases? I hope not as this becomes a very expensive process for upgrades.
Best Answer
-
TIJU Moderator
Hi @JustMe This issue is only there on 6.5.0.v version. Starting 6.5.4.v, user can make use use of system upgrade option and does not need to redeploy the image. i.e. say a user is running 6.5.4.4-44v-21-757 version and wants to upgrade to the latest version which is 6.5.4.4-44v-21-987 he just needs to make use of system upgrade feature.
0
Answers
Hi @Saravanan do you have any thoughts on this one?
🖐️ Self-Service Sr. Manager at SonicWall. Say "hi" by tagging me at @micah.
Hi @JUSTME,
Sorry for the late response.
Unfortunately, upgrade from 6.5.0.x to 6.5.4.x is unsupported at this time. The possible way of migrating to 6.5.4.x series of NSv is as follows,
I know this is a time consuming process but due to technical enhancement reasons on 6.5.4.x series, the support is unextended. We can definitely raise an RFE (Requesting Feature Enhancement) to avail the upgrade support from 6.5.0.x to 6.5.4.x release.
Once again sorry for the delay in response. Hope this information helps.
Regards
Saravanan V
Technical Support Advisor - Premier Services
Professional Services
Hi @Saravanan , due to https://psirt.global.sonicwall.com/vuln-detail/SNWLID-2020-0010
It looks like I might have to do this for my Azure based NSv's. Do you have a more comprehensive guide on this:
NOTE: For Upgrade to Firmware Version 6.5.4.4
How do I do this in azure and keep the assigned interfaces/VNet IP's and PIP?