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

and you want to continue to run Systems Insight Manager in the future, upgrade to Systems Insight
Manager using one of the following upgrade scenarios:
• If HP Servicecontrol Manager 3.0 is configured on your system and you do not want to lose
your data, you must upgrade HP Servicecontrol Manager before upgrading your system
from HP-UX 11i v2 to HP-UX 11i v3.
• If you do not want to keep any of the data from HP Servicecontrol Manager, you can remove
SCM before starting the upgrade. Determine if HP Servicecontrol Manager is installed on
your system by entering the following commands:
swlist -l bundle B8337BA B8339BA B8338BA
swlist -l product ServControlMgr AgentConfigSysMgmtServer
SysMgmtAgent
Uninstall HP Servicecontrol Manager using the following command:
swremove ID
where ID is the product or bundle ID. For example:
swremove -x enforce_dependencies=false B8339BA
or
swremove -x enforce_dependencies=false SysMgmtServer SysMgmtAgent
Remove the old product subdirectories by executing the following command:
rm -fr /opt/mx /etc/opt/mx
The database for the ServiceControl Manager, mysql, can be removed by executing the
following command:
swremove mysql
• If SCM is not configured or if Systems Insight Manager 4.x is installed and you want to
continue to use Systems Insight Manager, you must select Systems Insight Manager 5.x for
upgrade.
Execute the following command:
-x match_target=true
Use this option or use the interactive mode to select HPSIM-HP-UX.
You can also specify HPSIM-HP-UX on the command line. The Systems Insight Manager 5.x
installer will upgrade both a configured and an unconfigured Systems Insight Manager 4.X.
If you chose to remove either HP Servicecontrol Manager or Systems Insight Manager,
execute the following command to remove subdirectories that were used in the product:
rm -fr /opt/mx /etc/opt/mx
If these subdirectories are not removed, you might encounter database errors when trying
to run mxinitconfig -a when installing Systems Insight Manager 5.x.
8.5 Security
8.8.5.1 Attempts to import the Systems Insight Manager certificate from cert.pem or server_cert.pem into
a separate application result in failure.
Solution: This could be caused by an improperly formed certificate file. Backup the certificate
file. Then view the file using a text editor, and compare the last two lines before the "END
CERTIFICATE" line. The following is an example of a certificate file with duplication that can
cause the failure:
O/4Hcl9nRz0uZGcdsypjgW5CUDqZyzzeEB17DHWnC8qzEC7/D+VpW+5RdRTlhh5c
DzdIjLZnRz0uZGcdsypjgW5CUDqZyzzeEB17DHWnC8qzEC7/D+VpW+5RdRTlhh5c
-----END CERTIFICATE-----
If there is some duplication in the last two lines, manually edit the file to repair it. Be sure you
have the file backed up before attempting this. On the last line only, delete the characters, in
groups of four, at the end of the line that duplicate the characters from the line above it. All four
37