Migrate a c7000 VCM enclosure using REST API

1. Determine if a migration is already in progress.

   GET /rest/migratable-vc-domains

   A collection of compatibility reports are returned along with the number of concurrently executing migrations and the ability to create a compatibility report or migrate an enclosure while other operations are in progress. The migratabilityState must be MigrationValid to continue.

2. Validate the enclosure configuration.

   POST /rest/migratable-vc-domains

   See /rest/migratable-vc-domains for a list of required URIs. The enclosure VCM IP address is retrieved from Onboard Administrator (OA). The following URIs are optional.

   • For enclosure group, do one of the following:

     • If you want to migrate the enclosure into an existing enclosure group, use enclosureGroupUri.

     • If you want to migrate the enclosure into a new enclosure group, the enclosure group name is automatically generated based on the serial number.

   A tasks/{id} is returned identifying the compatibility report.

   	NOTE: GET /rest/tasks/{id} until the validation task is completed.

   Once the task has completed, a /rest/migratable-vc-domains/{id} URI is returned.

3. Retrieve a compatibility report using a /rest/migratable-vc-domains/{id} URI obtained in step 2.

   GET /rest/migratable-vc-domains/{id}

4. Does the report indicate errors?

   1. Yes, resolve compatibility errors. Repeat step 3 until all blocking issues are resolved.

   2. No, continue to the next step.

5. Is this an offline migration?

   1. Yes, power off the servers in the enclosure that is being migrated, and run a final compatibility report.

   2. No, run a final compatibility report.

6. Respond to the acknowledgments and import the VC enclosure.

   PUT /rest/migratable-vc-domains/{id}

   Include migrationState set to Migrated and AcknowledgementKey for each acknowledgment.

   The migration for the current enclosure is started.

7. Do you want to migrate another enclosure?

   1. Yes. Go to step 1.

   2. No, proceed to the next step.

8. Check for the completion of the migrations.

   GET /rest/migratable-vc-domains

   The migrationSubState shows Completed. If not, follow the proposed resolution.

9. Perform post-migration tasks.

1. Was the migration an offline migration?

   1. Yes, power on the servers in the migrated enclosure.

   2. No, proceed to the next step.

2. Optional: Recreate server profiles in HPE OneView, if server profiles were not assigned to server hardware before migration.

   1. Recreate the server profiles using the information from the VCMCLI show config –includepoolinfo captured before the migration.

   2. Enter the MAC, WWN, Serial Number, UUID information as “user specified” to retain the same values in HPE OneView that were present in the VCM server profile.

3. Perform the following best practices:

   1. Back up the new configuration in HPE OneView.

   2. Test network and storage connectivity.

   3. Plan a reboot if one of the acknowledgements, such as an SR-IOV virtual function configuration, indicated a change which would impact your operation.

      	NOTE: During an in-service migration, some changes do not take effect until the servers are rebooted for the first time following a migration.

Resolving compatibility issues

1. Review each issue and suggested resolution.

   	NOTE: If performing an offline migration, resolve all non-power related issues first before powering down the server to limit application downtime.

   1. Evaluate warnings to determine if action needs to be taken.

      If the warning indicates that the issue will affect your use of the configuration, then take action. Otherwise, the warning can be ignored.

   2. Resolve all blocking migration errors by modifying the configuration in VCM or HPE OneView.

      Resolving an issue may require disabling a feature within Virtual Connect, changing a configuration in Virtual Connect, or in some cases, changing the HPE OneView logical interconnect group.

      For example, if there is a mismatch with uplink sets and one of those uplink sets already exists in HPE OneView and 10 enclosures with the same configuration are to be migrated into the same enclosure group, update the uplink set in HPE OneView.

2. Re-execute the test compatibility report until all blocking issues are resolved.

3. Continue with the migration process.