The following information describes how an enclosure managed by Virtual Connect Manager (VCM) can be migrated into HPE OneView through the UI.
More information
| Prepare a VCEM enclosure for migration into HPE OneView |
| “Planning for enclosure migration from VCM into HPE OneView” in the HPE OneView User Guide |
| About migrating c7000 enclosures managed by other management systems |
-
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.
-
Review Prerequisites for bringing a c7000 enclosure into HPE OneView for prerequisites and preparation that must be in place.
-
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.
-
From the main menu, select Enclosures and do one of the following:
-
Click + Add enclosure in the master pane.
-
Select Actions→Add.
-
-
Enter the following information:
-
OA IP address or host name of the Virtual Connect enclosure
-
Your OA credentials (user name and password)
-
-
Enter the data requested on the screen. See Add enclosure screen details.
![[NOTE: ]](images/note.gif)
NOTE: To migrate to a new enclosure group, select Create new enclosure group.
To migrate to an existing enclosure group, select one from the enclosure group list.
-
Does the summary indicate errors?
-
Yes. Click migration report to view and resolve any blocking issues.
-
No. Review each acknowledgment.
Each acknowledgment must be read in full (clicking each learn more link where applicable). After understanding the implications, check each acknowledgement to proceed with the migration.
-
-
-
Yes, power off the servers in the enclosure that is being migrated.
-
-
Do you want to migrate another enclosure?
-
The migration for the current enclosure is started. When the HPE OneView resources (enclosure group, logical interconnect group, networks, network sets, server hardware types, and server profiles) have been created for the current enclosure, the Add Enclosure screen prompts you to add the OA IP address for the next enclosure.
![[NOTE: ]](images/note.gif)
NOTE: If the maximum number of four simultaneous migrations has been reached, an error displays indicating to wait until the number of migrations is below four.
-
The migration for the current enclosure is started and the Activities screen displays showing the migration tasks.
If the migration is successful, the migration task shows
Completed. If not, follow the proposed resolution. See Migration is unsuccessful for more information. -
-
Was the migration an offline migration?
-
Yes, power on the servers in the migrated enclosure.
-
-
Optional: Recreate server profiles in HPE OneView, if server profiles were not assigned to server hardware before migration.
-
Recreate the server profiles using the information from the VCMCLI
show config –includepoolinfocaptured before the migration. -
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.
-
-
Perform the following best practices:
-
Back up the new configuration in HPE OneView.
-
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: ]](images/note.gif)
NOTE: During an in-service migration, some changes do not take effect until the servers are rebooted for the first time following a migration.
-
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.
Resolving compatibility issues
-
Review each issue and suggested resolution.
![[NOTE: ]](images/note.gif)
NOTE: If performing an offline migration, resolve all non-power related issues first before powering down the server to limit application downtime.
-
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.
-
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.
-
-
Re-execute the test compatibility report until all blocking issues are resolved.
-
Continue with the migration process.
More information
| About blocking issues during migration |
| About migrating c7000 enclosures managed by other management systems |