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

30
Step 3: Verifying SMTP settings on the target CMS
After a migration to a new host, it is possible that the SMTP configurations might need to be updated. Log
into the CMS console, select OptionsEventsAutomatic Event HandlingE-mail settings, and then verify
that the SMTP server is correct. If these settings are incorrect, automatic event handling and the emailing of
reports might fail.
Step 4: Post-migration steps for Cluster CMS
This step is applicable only for Cluster CMS.
1. Start the other node in the cluster.
2. Log in with the service account credentials you provided to the Insight Software Installer, the username,
password, and domain of your cluster. After you have successfully logged in, the HP SIM home page
appears.
3. Navigate to OptionsProtocol SettingsGlobal Protocol Settings. The Global Protocol Settings page
appears.
a. Click the Global Credentials link under SNMP. The Global Credentials page appears.
b. Under Sign-in Credentials, verify that the credentials are set to the service account credentials you
provided to the Insight Software 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, which appears, is the WMI Mapper proxy for the source CMS.
a. If WMI Mapper was not installed by the Insight Software Installer on the target cluster, then ensure
that the WMI Mapper proxy is set to the FullyQalifiedDomainName (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 Software 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 ,target CMS will have source CMS’s WMI mapper proxy data .if the
user wants to use the WMI mapper proxy data different from the source machine,
then user has to update the WMI mapper proxy data manually.[ie
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:
i. The Microsoft SQL Server 2008 virtual server IP address of the target cluster (a public network
IP address).