HP Insight Management 7.3 DMT White Paper

Technical White Paper | HP Insight Management 7.3

12. Click on more in third line

13. Browse the file which you have downloaded from “Download certificate” link.

14. Click on import.

Step 15: If this is a secondary CMS migration, perform the following operations

1. Log in to the primary CMS in the federation that the migrated secondary CMS is part of.

2. Stop the HP Matrix infrastructure orchestration windows service.

3. Remove the source CMS from the federated CMS list using SIM Federated Configuration.

4. Add the target CMS to the federated CMS list using SIM Federated Configuration.

5. Open a prompt window, go to <IO Install path>/support, and run the

following script:

fix_fqdn_dmt.pl – f <input_file>

6. Start the HP Matrix infrastructure orchestration windows service.

For details on how to run the fix_fqdn_dmt.pl script, see Appendix G: Running the

fix_fqdn_dmt.pl script.

Note: In a federated CMS migration, the data migration tool does not migrate SSL certificates; therefore, SSL certificates

should be configured manually after the import operation is complete.

Step 16: Updating bookmarks

1. Notify users that bookmarked URLs to the source CMS will no longer be valid after migration

to the target CMS.

2. Provide new links to the target CMS; for example, https://<newcmsname>:50000.

Step 17: Registering deployment server with new IP address

After migrating data from source CMS to target CMS with a different IP address, IO templates

that reference deployment servers (such as Insight Control server deployment, HP Server

Automation, and Ignite-UX) are still valid and published. However, provisioning using these

templates fails with the error Task for Logical Server logical-server-name

has failed. Logical server job completed with a failure status.

Failure: Deployment server credentials not found.

Once the import operation has completed in the target CMS with a different IP address, open a

command prompt and enter the following commands to register the deployment servers in your

environment using the new IP address.

Insight Control server deployment

mxnodesecurity –a –p dsc_rdp –c username:password -t on -n

Ignite-UX

mxnodesecurity –a –p dsc_ignite –c username:password -t on -n

HP Server Automation (SA)