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

35
b. Under Sign-in Credentials, verify 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. Update the credentials as needed.
c. Ensure that under SNMP Credentials the SNMP Community String is public.
d. Click OK.
4. In HP SIM, navigate to OptionsProtocol SettingsWMI Mapper Proxy. The WMI Mapper
Proxy page appears. The host that appears is the WMI Mapper proxy for the source CMS.
a. If WMI Mapper was not installed by the Insight Management Installer on the target cluster,
then ensure that the WMI Mapper proxy is set to the FullyQualifiedDomainName (FQDN) of
the host that is providing this service for the target cluster. This host is not part of the cluster. If
the WMI Mapper proxy is not set to the correct host:
i. Check the box to select the current host and click Delete.
ii. Click New.
iii. Enter the FQDN of the host that is providing this service for the target cluster. This host is
not part of the cluster.
iv. Verify the port number and adjust as needed.
v. Click OK.
b. If WMI Mapper was installed by the Insight Management Installer on the target cluster, then
follow the steps to configure the WMI Mapper proxy.
i. Check the box to select the current host and click Delete.
ii. Click New.
iii. Enter the FQDN of the Systems Insight Manager virtual server name in the target cluster.
iv. Verify the port number and adjust as needed.
v. Click OK.
Note:
After import, the target CMS will have the source CMS WMI mapper proxy
data. If you want to use the WMI mapper proxy data that is different from
the source machine, then you must update the WMI mapper proxy data
manually (wbemportlist.xml).
5. Navigate to OptionsDiscovery. The Systems Insight Manager discovery page appears.
a. Click the link for Configure general settings under For all automatic discoveries.
b. In the list box named Ping exclusion ranges, templates and/or hosts files: add the following
items:
• The Microsoft SQL Server 2008 virtual server IP address of the target cluster (a public
network IP address).
• The Microsoft Distributed Transaction Coordinator virtual server IP address of the target
cluster (a public network IP address).
• The private network IP address of the target cluster primary node.
• The private network IP address of the target cluster secondary node.
HP recommends that the balance of the private network IP address range also be
entered. The private network exists to facilitate the cluster heartbeat. The private network
IP address range is generally not of any use and must be excluded to prevent possible
confusion.
c. Click OK.