How To
Summary
Systems that use VMware Virtual Volumes (vVols) might require reconfiguration before you update the software to version 8.6.1 or later.
If you configured vVols on the system with a software version earlier than 8.6.0 or using Spectrum Connect as a VASA provider, reconfiguration is required. This document explains how to check the current configuration and lists the steps to reconfigure if required.
Environment
The information in this document applies to systems with Storage Virtualize software version 8.6.0 and earlier using VMware Virtual Volumes (vVols).
Steps
IBM Storage Virtualize 8.6.0 and later versions support a new version of metadata volume for using VMware Virtual Volumes (vVols). A metadata volume created on earlier versions uses an older format that is not supported beyond 8.6.0. To update to 8.6.1 or later, the metadata volume must be upgraded to version 2.
Step 1: Check whether a version 1 metadata volume is configured on the system
When you prepare to update the system software, the upgrade test utility checks whether the system has a version 1 metadata volume. If any actions are required, the results of the test include a link to this page. If you have already run the utility and the results directed you to this page, continue to step 2.
Alternatively, you can use the command-line interface to check the configuration:
- List the version 1 metadata volumes on the system:
- If the current software version is 8.6.0, use the following command:
- If the current software version is earlier than 8.6.0, use the following command:
- If any results are displayed, actions are required before you update the system software. Go to step 2.
- If no results are displayed, no actions are required.
Step 2: Update the system to version 8.6.0
- If the system is already running software version 8.6.0, continue to step 3.
- If the system is running a software version earlier than 8.6.0, you must update the system to 8.6.0. Once the update is complete, continue to step 3.
Step 3: Reconfigure the system
The steps to remove a version 1 metadata volume depend on the current configuration for vVols. Identify the scenario that matches your situation.
Scenario 1: vVols are configured using the embedded VASA provider
In this scenario, the VMware vCenter is configured directly with the storage system.
Before the system can be updated to 8.6.1 or later, you must migrate the vVol metadata volume from version 1 to version 2. For more information, refer to the "Migrating vVol metadata volumes from Version 1 to Version 2 format" topic in the product documentation for version 8.6.0.
Scenario 2: vVols are configured using an external VASA provider, such as IBM Spectrum Connect
In this scenario, the VMware vCenter is configured to use IBM Spectrum Connect or IBM Spectrum Control Base Edition as an external VASA provider.
Before the system can be updated to 8.6.1 or later, you must reconfigure the system to use the embedded VASA provider. This process configures a version 2 metadata volume. For more information, refer to the "Migrating from existing IBM Spectrum Connect vVol configurations" topic in the IBM FlashSystem and VMware Implementation and Best Practices Guide Redbook.
Scenario 3: vVols are configured on the system but are no longer required
In this scenario, the system has previously been configured for vVols but they are no longer used and can be removed.
- Use the following command to identify any vVols on the system:
- If any results are displayed, confirm that each vVol is no longer required, then use VMware vCenter to remove the volumes.
- If there is no longer a vCenter configured to manage vVols, contact IBM Support for guidance on how to manually remove the volumes.
- When there are no vVols on the system, use the following command to remove the metadata volume:
When the reconfiguration tasks are complete, the system can be updated to version 8.6.1 or later.
Related Information
Document Location
Worldwide
[{"Type":"MASTER","Line of Business":{"code":"LOB26","label":"Storage"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"STSLR9","label":"IBM FlashSystem 9x00"},"ARM Category":[{"code":"a8m0z000000bqQ5AAI","label":"Code (Code\/Drive firmware\/IFix)-\u003EUpgrade (CCU)"}],"ARM Case Number":"","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"All Versions"},{"Type":"MASTER","Line of Business":{"code":"LOB26","label":"Storage"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSA76Z4","label":"IBM FlashSystem 7x00"},"ARM Category":[{"code":"a8m0z000000bqQ5AAI","label":"Code (Code\/Drive firmware\/IFix)-\u003EUpgrade (CCU)"}],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"All Versions"},{"Type":"MASTER","Line of Business":{"code":"LOB26","label":"Storage"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"ST3FR9","label":"IBM FlashSystem 5x00"},"ARM Category":[{"code":"a8m0z000000bqQ5AAI","label":"Code (Code\/Drive firmware\/IFix)-\u003EUpgrade (CCU)"}],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"All Versions"},{"Type":"MASTER","Line of Business":{"code":"LOB26","label":"Storage"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"STPVGU","label":"SAN Volume Controller"},"ARM Category":[{"code":"a8m0z000000bqQ5AAI","label":"Code (Code\/Drive firmware\/IFix)-\u003EUpgrade (CCU)"}],"Platform":[{"code":"PF025","label":"Platform Independent"}]}]
Was this topic helpful?
Document Information
Modified date:
14 September 2023
UID
ibm16983196