Invista Upgrade Process

Question

we have used Invista 2.1 to migrate off of 3 CX600 arrays onto CX3 and CX4 arrays. The 2.1 code has a number of gui related issues and we are planning the upgrade to 2.2.

for the most part, Invista performed well doing its Data Mobility moves. I had one Virtual lun that faulted numerous times during a Data Mobility session and I think it was because it trespassed on the Source Clariion side.

I am looking for any feedback on anyone who has performed a Production Invista upgrade process from 2.1 to 2.2 and their experiences with the process.

3riversff · Accepted Answer

We just completed this upgrade last week in our production environment. We went from 2.1 to 2.2. The upgrade was pretty smooth. All of our hosts lost one path to the storage which was expected and we did NOT experience any outages. The upgrade is very much like a Flare code upgrade on the Clariion, 1 SP at a time. This upgrade also required an upgrade to the code for SSI blade in our 9509. One of the issues we hit, was that the script doing the SSI code upgrade requires Telnet to be enabled on the switch. By default, we have this turned off. Once we turned it on the script and upgrade ran fine. The only other issue we encountered was a post upgrade issue. In our Dial home template, we had disabled the call home for when a host is rebooted. The error codes for this event were changed in the 2.2 code. An update to the template to disable this was all that was required.

All in all, it was a very smoth upgrade.

Kevin

daver3 · Answer

I have done the code upgrade on a new system that was deployed. Since Invista is based on Clariion FLARE, the upgrade is very similar to doing a code upgrade on a CX. It will do the SP B first, then reboot, then once its finished it will do SPA. Hope this helps!

Connectrix

Invista Upgrade Process

Was this post helpful?