README - HP Systems Insight Manager 5.3 with Update 1

When you uninstall HP Serviceguard Manager 4.0 after it has been integrated with HP SIM, you receive
an HTTP 404 error. This error occurs because the Serviceguard Manager uninstall application deletes the
webapps\sgmgr directory, which is located:
on HP-UX and Linux:
/opt/hpwebadmin/webapps
on Windows:
\ProgramFiles\HP\Systems Insight Manager\hpwebadmin\webapps
To avoid the HTTP 404 error in the future, you must remove the tool from HP SIM using the following command
from the path /var/opt/mx/tools on Linux or HP-UX:
mxtool -r -f sgmw-web-tools.xml
If Serviceguard Manager is reinstalled in the future, you must add the tool to HP SIM again using the following
command from the path /var/opt/mx/tools on Linux or HP-UX and \ProgramFiles\HP\Systems
Insight Manager\tools on Windows:
mxtool -a -f sgmw-web-tools.xml
NOTE: If there is a task that utilizes the Serviceguard Manager tool and the tool is removed and then
added again, the tasks might no longer work because the GUID has changed by adding the tool again.
These tasks must be deleted and added again. This condition does not apply to HP Serviceguard 5.0 being
integrated with HP SIM 5.0.
-------------------------------------------------------------
HP Serviceguard WBEM Provider 1.0 does not provide roll-up status for HP SIM.
-------------------------------------------------------------
When you install a Serviceguard cluster, there is a default name Serviceguard cluster defined as its cluster
name. The cluster node (not the member node) is a non-addressable node.
Therefore, if the you install multiple Serviceguard clusters in your subnets and use HP SIM to discover those
clusters without renaming the clusters to be unique, associations of members to their respective clusters will
not be accurate. To solve this issue, HP SIM will always append cluster ID defined by Serviceguard cluster
to the cluster name.
-------------------------------------------------------------
When renaming a Serviceguard cluster and re-identifying it, HP SIM might create a new non-addressable
Serviceguard cluster node instead of renaming the old cluster node. This can happen when Serviceguard
SNMP and WBEM agents report different cluster ID values then what was found when HP SIM originally
queried the same cluster node before it was renamed. However, all of the Serviceguard cluster's member
nodes will be correctly associated to the cluster after renaming and re-identification have occurred.
HP SIM
HP SIM is not compatible with version 2.0.1 of the Pegasus WMI Mapper. HP SIM 5.3 ships with version
2.6.5.2 of the Pegasus WMI Mapper, and HP recommends that you use this version with HP SIM. Indications
should be enabled when installing this mapper, which is the default when installed along with HP SIM.
-------------------------------------------------------------
On Red Hat Linux, if mxstop runs before HP SIM is stopped and rebooted, the HP SIM daemons do not
auto-start. However, if HP SIM is running when a reboot command is issued, the auto-start works as expected.
If the daemons do not auto-start, they can be started by running the mxstart command.
-------------------------------------------------------------
The Help→About HP Systems Insight Manager window displays the operating system name as Windows
Vista on Microsoft Vista and Microsoft Windows 2008 CMS.
HP SIM 25