Storwize V7000 and SVC Code release 6.3 is now available

The latest release of SVC and Storwize V7000 firmware is now available for download.   The major new features that are added with this release are:

  • Global Mirror with Change Volumes
  • Native LDAP Authentication
  • Extended distance split clusters (for SVC)
  • Support for 4096 host WWPNs 

These are some great new features.   The ability to use Global Mirror with Change Volumes means clients can now mirror across far smaller pipes, while the increase in host WWPNs is very welcome news for NPIV installations that are suffering from WWPN sprawl.

If you plan to upgrade, firstly grab the new Upgrade Test Utility from here.  The links to the Storwize V7000 and SVC versions are both on that page.   Remember you can run this test as many times as you want whenever you want, to check the health of your device for upgrade.  When you run the upgrade test utility on a Storwize V7000 you may get a message that your disks have down-level firmware.   The process to update them is documented here.

If you’re using a Storwize V7000 you can grab the code from here.  If you’re using an SVC you can grab the code from here.  I am sending you to the compatibility matrix page because you should always check that your from level is ok for your to level.

To run the upgrade go to Configuration (the spanner icon) → AdvancedUpgrade Software  →  Launch Upgrade Wizard

I have not shown all the panels you will see because it is very much a follow-your-nose task, but in essence, first we feed it the Upgrade Test Utility file and run that test.

If you get warnings you may need to act on these.   If you are unsure what to do to resolve a warning message, place a service call.

Once the test passes or you’re happy you understand the warnings, we now point it at the code package and wait for it to copy across and keep hitting Next.

The application of the code shuts down and reboots each controller, with a 30 minute gap in between.   You will transition from this (both nodes down-level, node1 being upgraded):

To this (node1 upgraded, node2 still online but waiting for 30 minutes):

When node2 starts the upgrade the GUI will failover to node1 and be upgraded to the new version.  You will notice the difference immediately, it has a different look and feel.   Please don’t be tempted to play with the new functions until both controllers are upgraded!   Wait until you see this (note a slight change, the GUI flow is now Settings (the spanner icon) → General → Upgrade Software:

Now your complete it is time to start checking out what is new…   but that’s a whole different blog post!


About Anthony Vandewerdt

I am an IT Professional who lives and works in Melbourne Australia. This blog is totally my own work. It does not represent the views of any corporation. Constructive and useful comments are very very welcome.
This entry was posted in IBM Storage, Storwize V7000, SVC and tagged , , , , , . Bookmark the permalink.

10 Responses to Storwize V7000 and SVC Code release 6.3 is now available

  1. Pingback: Storwize V7000 and SVC Code release 6.3 is now available « Storage CH Blog

  2. Errol says:

    Great stuff….When is native IP replication coming…

  3. Pingback: SVC and Storwize V7000 Release 6.3: Performance Monitor Panel | Aussie Storage Blog

  4. Pingback: SVC and Storwize V7000 Release 6.3: Performance Monitor Panel « Storage CH Blog

  5. Pingback: SVC and Storwize V7000 Release 6.3: Keys now optional! - The Business of IT Storage Blog - IBM Storage Community

  6. Warkem says:

    Any idea when IBM will update the SRA for VMware SRM 4.1 or 5 to be compatible with this code version? After updating to 6.3 from 6.2.3 the SRA can no longer see any replicated peers?

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s