HP Systems Insight Manager 5.2 Installation and Configuration Guide for HP-UX

Note: If the names contain characters such as underscore, space, and symbols, they might not be
migrated because these characters are not supported.
h. If, after taking the previous steps, items such as menus are still missing or out of place, run the
following command:
sh /opt/mx/bin/fixmenu.sh scmtdefs.data /var/opt/mx/bak/3.0/tools
/var/opt/mx/tools
10. Using the GUI, add the default WBEM user name and password to the Global Protocol Settings
page.
Note: An account for at least one of the WBEM user name and password combinations must exist on
the CMS.
a. Select Options→Protocol Settings→Global Protocol Settings.
b. In the Default WBEM settings section, ensure that the Enable WBEM checkbox is selected, and
add the default WBEM user name and password.
c. Click OK.
Note: After upgrading to HP Systems Insight Manager, you must run identification for all network devices,
racks, and enclosures to appear on the System Overview page.
11. The mysql database, can exist in the HPUX11i OE personality bundle or in its own bundle, MySQL.
But, if you no longer need the ServiceControl Manager database mysql and would like to remove it
completely from your system, execute the following command:
swremove mysql
After this initial upgrade, follow the procedure to upgrade HP SIM 4.2 to 5.x. Refer to Chapter 9 “Upgrading
from HP Systems Insight Manager 4.x or later ” for more information.
Upgrading existing managed systems
1. Install SSH on the managed systems:
On HP-UX:
a. Set up a depot that includes the SSH product.
b. Run the Install Software command on all HP-UX DTF managed systems.
mxexec -t "Install Software" -n <hpux_nodes>
This tool is MSA and requires a display to run a GUI.
2. Upgrade the CMS. Refer to “Upgrading from SCM 3.0 to HP Systems Insight Manager 4.2” for more
information.
3. On the CMS, copy the SSH-generated public key from the CMS to the managed system, and place it
in the authorized keys file of the execute-as user (root or administrator).
Important: If the CMS is not an HP-UX system, on a non-English CMS, ensure that an administrator
account exists on the CMS and that mxagentconfig has been run on the CMS for the created
administrator account.
a. Launch the Manage SSH Keys dialog box from the CMS command prompt:
mxagentconfig -a -n hostname -u username -p Password
b. Click Connect.
Alternatively, you can configure SSH through the command line version of mxagentconfig. On the CMS,
enter mxagentconfig -a -n hostname -u username -p Password for usage.
Note: Using the -p option makes the password available in "ps" output, so HP recommends using the
-f option (with a file only readable by root) when using mxagentconfig -a. When you use the –p option,
enclose the password in single quotes if the password has any special characters like & or $.
Upgrading existing managed systems 53