Software Owner manual
NOTE: The source CMS cannot be powered on again unless you provide a new VCEM
subrange. If you want to use the source CMS for other purposes, you must uninstall it along
with the whole Insight Management stack or guarantee that the CMS will be cleaned by either
installing a new operating system or reformatting the hard disk.
3. At the target CMS, browse to the MAC address management page and remove MAC exclusion
range1 from the VCEM-defined exclusion ranges.
4. At the target CMS, browse to the WWN management page and remove the WWN exclusion
range 1 from the VCEM-defined exclusion ranges.
5. At the target CMS, import all VC Domains which were removed from the source CMS into the
VCEM VC Domain Group. If the VC Domains configuration is not identical on the source and
target VCEM instances then create a new VC Domain Group on the target CMS with the
imported VC Domains.
For more information, go to: http://www.hp.com/go/matrixoe/docs, select the Product
Documentation Quick Link, then look in the White Papers section for the HP Matrix Operating
Environment Federated CMS Overview White Paper.
Transferring one managed VC Domain from one VCEM instance to another
Use the procedure in the following example to transfer a managed VC Domain from one VCEM
instance to another VCEM instance. This example assumes that the source CMS is the VCEM
instance using subrange 1 and the target CMS is the VCEM instance using subrange 2. In this
example one VC Domain (VC Domain A) is transferred from the source to the target VCEM instance
and both VCEM instances will continue to operate.
1. Identify which MAC and WWN addresses are used in the server profiles assigned to VC
Domain A. There are two options to do this:
• Manually inspect each server profile MAC and WWN address in use and take notes.
• Run the VCEM CLI Export Server Profile command which will export all server profile
information to a CSV file. For more information about the VCEM CLI, see the HP Virtual
Connect Enterprise Manager Command Line Interface User Guide.
2. Remove VC Domain A from the VC Domain Group which is managed by the source CMS.
3. Ensure that all VCEM MAC and WWN addresses in use by server profiles assigned to VC
Domain A are marked as “External” within the VCEM source CMS.
4. (Optional) Before other users reclaim those external MAC or WWN addresses, create a VCEM
exclusion range with those MAC and WWN addresses within the source CMS. This excludes
other users from reclaiming those external MAC or WWN addresses in use by VC Domain
A (which will be managed by another VCEM instance in the target CMS).
5. In the target CMS, browse to the MAC address management page and ensure that the specific
MAC addresses in use by each server profile in Domain A are removed from the VCEM
exclusion range. This can result in splitting an existing VCEM exclusion range into two or more
ranges. For example if VCEM MAC exclusion range for subrange 1 is defined as
00-21-5A-9B-00-00 to 00-21-5A-9B-03-FF and if MAC addresses in use by server profiles are
00-21-5A-9B-00-02, 00-21-5A-9B-00-03, 00-21-5A-9B-00-04, and 00-21-5A-9B-00-05 then
you must redefine the VCEM MAC subrange 1 as displayed in Table 19:
Table 19 Redefining VCEM MAC subrange 1
EndStartMAC Exclusion ranges
00-21-5A-9B-00-0100-21-5A-9B-00-00ExclusionSubrange1-part1
00-21-5A-9B-03-FF00-21-5A-9B-00-06ExclusionSubrange1-part2
6. At the target CMS, browse to the WWN management page and make sure the specific
WWNs in use by each server profile in Domain A are removed from the VCEM exclusion
Address management tasks 141