Data migration of an existing Microsoft Windows CMS to a new Insight Management 7.0 system

38
wrapper.java.additional.15=-Dfed.cms.name=cms1.org.domain
This value should also match what was configured on the source CMS.
15. In a cluster environment, configure the managed_cms_list property in
globalsettings.props for HP IO server pools.
a. Edit the <SIM>\config\globalsettings.props file.
b. Update the target cluster host name in the managed_cms_list property in the
globalsettings.props file.
For example:
managed_cms_list =target_node_fqdn, secondary_1,secondary_2
After import, managed_cms_list should be updated to the following:
managed_cms_list = HP_SIM_virtual_server_name, secondary_1,
secondary_2
16. In the left pane, click All Systems. You can find the cluster virtual server name, the Systems Insight
Manager virtual server name, and the cluster nodes in All Systems. Figure 3 is an example of the
display. Your configuration might contain additional systems.
Figure 3: Two node ProLiant cluster after Systems Insight Manager discovery
17. Click the virtual server name of the Failover Cluster. In Figure 3, it is cms-c2-cluster. The Cluster
Monitor appears. Browse through the tabs and verify the consistency with the same data as
shown by Windows Failover Cluster Manager.
18. To verify that the HP SIM Group resources can be moved between both systems, as in a failover,
perform the following steps from either one of the cluster systems:
a. In the left pane of Failover Cluster Manager Window, right-click the HP SIM group. Select
Move this service or application to another node. Be sure that the group fails over to the other
system, and that all of the HP SIM Group cluster resources come online.
b. After waiting a few minutes to ensure that the Systems Insight Manager service has started,
connect to the Systems Insight Manager service through a client Web browser, as done
previously in Steps 1, 2, and 3.
c. Verify that the following settings configured remain in place: