- CheckMates
- :
- Products
- :
- Quantum
- :
- Security Gateways
- :
- Info about VSX upgrade to R81.x
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
Are you a member of CheckMates?
×- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Info about VSX upgrade to R81.x
Hello, before upgrade from, for example, r80.40 to r81.10, the first step is use "vsx_util upgrade" utility from SMS/MDM.
This info is clear and indcated in the "Installation and Upgrade Guide R81" document.
In the VSX R81 Admin Guide, about "vsx_util upgrade" is also indicated: "After the command finishes, you must run the vsx_util reconfigure command".
This part isn't indicated in the "Installation and Upgrade Guide R81" document.
About your experience, "vsx_util upgrade" is sufficent or, after this, we need to use also "vsx_util reconfigure"?
Thanks
Accepted Solutions
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
vsx_util upgrade will upgrade the database on the management station.
After this, you need to upgrade your VSX appliances. vsx_util reconfigure is run in the case you have a freshly installed appliance with the corresponding physical interfaces configured (bonds for instance) to convert to VSX. If you go with in-place upgrade running CPUSE, you won't need to reconfigure them.
Beware you need to manually re-input extra VS configuration like DHCP relays or dynamic routing, only done on CLI.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
vsx_util upgrade will upgrade the database on the management station.
After this, you need to upgrade your VSX appliances. vsx_util reconfigure is run in the case you have a freshly installed appliance with the corresponding physical interfaces configured (bonds for instance) to convert to VSX. If you go with in-place upgrade running CPUSE, you won't need to reconfigure them.
Beware you need to manually re-input extra VS configuration like DHCP relays or dynamic routing, only done on CLI.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Additionally the very first thing:
- snapshot the Management server
- snapshot the VSX appliances
and if possible store these offline. If you need to rollback then you will need to do a snapshot restore.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
OK, thanks, is clear and logic.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi
Notice that it is much easier to use the Smart Console in order to upgrade your VSX
You can upload the new version to the management (Manage & Settings -> Package repository -> New and then either download from download center or brose the package)
Then simply right click the VSX and select actions -> version upgrade
No need to do vsx_util upgrade nor reconfigure. The Smart Console shall do it for you.
Boaz
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello, thanks for reply.
With this procedure (upgrade via Smart Console) we can opgrade only the enteire cluster, correct?
If I need to use MVC the only way at the moment is "legacy" mode via CPUSE, can you confirm?
Thanks
