Enclosures > Migrate a c7000 VCM enclosure using REST API |  | next

# Migrate a c7000 VCM enclosure using REST API

An enclosure managed by Virtual Connect Manager (VCM) can be migrated into HPE OneView through the UI or through REST API. The Virtual Connect (VC) enclosure can be migrated to a new enclosure group or an existing enclosure group.

VCEM-managed enclosures can be migrated to HPE OneView through the VCEM GUI or a PowerShell module. See Prepare a VCEM enclosure for migration into HPE OneView for more information.

##### More information

“Planning for enclosure migration from VCM into HPE OneView” in the HPE OneView User Guide
About migrating c7000 enclosures managed by other management systems

## Prerequisites

- Required privileges: HPE OneView Infrastructure administrator, Onboard Administrator, and VCM Domain Administrator.

- OA and VCM credentials as well as the OA IP address for the enclosure.

- For VCEM-managed enclosures: VCEM credentials to remove the Virtual Connect domain from the domain group using the VCEM web interface, or the HPE PowerShell module. See Prepare a VCEM enclosure for migration into HPE OneView for more information.

- Back up and secure the VCM configuration (including the output from `show config -includepoolinfo`). See VCM configuration backup acknowledgment for more information.

- Review the HPE OneView Support Matrix and verify the enclosure contains supported servers, interconnect modules, and mezzanine cards.

- Assign server profiles before the migration or recreate server profiles after the migration, if applicable. See Server profile acknowledgment for more information.

- Ensure network connectivity with OA and iLOs in the Virtual Connect domain.

- Ensure all interconnect modules are present and powered on within the enclosure.

## Migrating a VCM enclosure using REST APIs

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.

## 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.

## Resolve compatibility issues

The migration tool detects if the features and hardware within a VCM-managed enclosure are compatible with HPE OneView. Each detected issue is grouped into a category such as hardware, domain, logical interconnect group, or server profile to identify the part of the Virtual Connect domain or HPE OneView system that is impacted. An issue is also given one of the following compatibility issue levels.

Medium | An issue has been identified where you may lose some functionality, but the functional loss would not be significant. Within the report, both Medium and High issues are denoted as a warning.
High | The issue identified is considered serious. Depending on how you use the feature, there may be significant consequences. Determine whether to resolve this issue before continuing with the migration.
Critical | The issue identified is likely to cause an outage if the migration were to continue. This is a blocking issue and must be resolved before continuing with the 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.

#### More information

About blocking issues during migration
About migrating c7000 enclosures managed by other management systems

prev | up | next
Delete a c7000 enclosure from management | home | Move a monitored c7000 enclosure to managed status

Copyright © 2013-2016 Hewlett Packard Enterprise Development LP