Data migration of an existing Microsoft Windows CMS to a new Insight Software 6.3 system

Figure 3: Two node ProLiant cluster after Systems Insight Manager discovery
14. 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.
15. 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 above in Steps 1, 2, and
3.
c. Verify that the following settings configured remain in place;
o WMI Mapper Proxy
o SNMP community name and credentials
o Ping exclusion ranges
o Discovery tasks edited
d. Verify the consistency of the All Systems and Cluster Monitor displays.
16. HP SIM Group resources are now owned by the secondary node. Repeat Step 14 to move the HP SIM
Group resources back to the primary node, and then verify the move.
Follow the steps in the Final configuration steps section of
Installing and upgrading to HP Insight Software
6.3 on Windows Server 2008 R2 Failover Clusters with SQL Server 2008 for high availability.
Step 5: Running daily system identification on the target CMS
Run the daily system identification task to ensure data is up to date in the target CMS.
1. In the CMS console, navigate to Task and LogsView All Scheduled Tasks.
2. Select the Daily System Identification task.
3. Click Run.