HP Systems Insight Manager 7.3 Release Notes

3 Issues and workarounds
The HP SIM undergoes rigorous testing before any given version of the product is released. From
HP test activities to date, the following items have been uncovered that you must keep in mind.
HP SIM
• Issue: Timeout issue observed while performing restore operation on OA.
Description: Timeout issue is observed while performing restore operation on OA. When OA
restore configuration fails on HP SIM, you can try increasing the timeout value and then try
restoring the configuration.
Workaround: To resolve the issue, change the OAConfigTimeOut property in the
globalsettings.props file by increasing the timeout value and then restore the
configuration.
• Issue: The Enclosure Manager Firmware version 1.20 and version 1.30 have issues in returning
Serial Number and Unique Identifier of IO Module in XML Response.
Description: IO Module nodes are discovered automatically when Enclosure Manager is
discovered. Because of issue with Enclosure Manager Firmware, IO Module nodes are not
discovered automatically in SIM when Enclosure Manager is discovered.
• Issue: Discovery issue with Debian OS
Description: When a system with Debian OS is discovered, SIM does not set OS name and
OS version on the node. This can be verified from system page of the node.
Workaround: OS Version can be set manually from Edit System Properties. OS name can be
found from Hardware Description displayed in system page of the node.
Follow below steps to set the OS version:
1. Click on the node. The system page of the node gets loaded.
2. Click on Tools & Links Edit System Properties.
3. Supply value for OS version in Operating System Version field.
4. Click on OK.
• Issue: WBEM subscription service fails on 3PAR OS 3.1.2 MU3. Core Discovery, inventory
and SNMP traps are not impacted.
• Issue: Installation of WBEM providers might fail on the target when the user tries to install an
entire baseline.
Description: The WBEM component dependencies are getting installed after the WBEM
component installation. The installation order of the components is not correctly followed by
HPSUM for WBEM component.
Workaround: Subsequent trial of baseline installation through 'Software Firmware Baseline
Installation' or individual component installation through 'CRA' resolves the issue.
• Issue: Deployment on agents not working consistently on windows targets
Description: For Windows based Servers, to communicate with remote node servers , HPSUM uses
admin$ share which is an automatic share provided by Windows Server. This share is used by
HPSUM to copy files and perform required operations. While, trying to access admin$ share if
HPSUM detects multiple connections to the remote Windows server, it may fail with an error
message as Multiple connections to a server or shared resource by the
same user, using more than one user name, are not allowed. Disconnect
all previous connections to the server or shared resource and try again.
10 Issues and workarounds