Data migration of an existing Microsoft Windows CMS to a new Insight Management 7.0 system
37
10. Navigate to OptionsDiscovery. The Systems Insight Manager discovery page appears.
11. Create or update the discovery task for the primary and secondary physical servers.
a. If the source CMS is a Cluster CMS and a Discover physical cluster nodes discovery task is
already configured:
i. Select and edit the Discover physical cluster nodes discovery task.
ii. In the ping inclusion range list box, change the IP addresses to be the IP addresses of the
primary and secondary nodes in the target cluster.
iii. Click the Credentials… button.
iv. The Sign-in tab is selected. Under Use these credentials ensure that the credentials are set
to the service account credentials you provided to the Insight Management Installer on the
target CMS, for example, domain\username and password.
v. Clear the If these credentials fail box.
vi. Click OK.
vii. Click Save to complete.
b. If the source CMS is not a Cluster CMS and a Discover physical cluster nodes discovery task
is not configured:
i. Click New… to create a new discovery task.
ii. Select Discover a group of systems.
iii. In the Name field enter the task name, for example, Discover physical cluster nodes.
iv. Under Schedule, clear the box used to select automatic scheduling.
v. In the ping inclusion range list box, enter the IP addresses of the primary and secondary
nodes.
vi. Click Credentials…
vii. The Sign-in tab is selected. Under Use these credentials enter the service account
credentials you provided to the Insight Management Installer on the target CMS, for
example, domain\username and password.
viii. Clear the If these credentials fail box.
ix. Click OK.
x. Click Save to complete.
12. Run the updated discovery task.
a. In the discovery task list box, select Discover physical cluster nodes.
b. Click Run Now.
c. Wait for the task to complete. Minor error messages might appear.
13. Check that the Federation CMS Configuration is correct.
a. Select Options → Federation CMS Configuration…
• Verify that the appropriate systems are listed.
• Ensure that the HP SIM virtual server name of the target CMS is listed.
• Ensure that the individual node names of the cluster are NOT listed.
14. Configure the HP SIM virtual server name for IO.
a. Edit the <IO>\hpio.conf file.
b. Uncomment the following line by removing the leading # character:
#wrapper.java.additional.15=-Dfed.cms.name=[FQDN]
c. Supply the correct HP SIM virtual server name by replacing the [FQDN] portion of the line.
For example, if the HP SIM virtual server name was cms1.org.domain, then it would
appear as follows: