README - HP Systems Insight Manager 5.3

-------------------------------------------------------------

The Property pages for the VMWare ESX 3.5 operating system are not available due to limitations in the

WBEM agents

Reporting

Reports with one or more IP address or host name exported from HP SIM in XML format cannot be imported

into HP SIM. To create a report in XML format on specific systems, a collection of these systems must be

created and then this collection can be used to create a report.

-------------------------------------------------------------

When reports are too wide to print, even in Landscape mode, save the report in CSV format and print from

a tool such as Microsoft Excel, or select fewer data items for each category in the report. See the

HP Systems

Insight Manager Technical Reference Guide

for information on saving a report in CSV format.

NOTE: This recommendation applies to all reports except Snapshot Comparison reports.

-------------------------------------------------------------

Snapshot Comparison reports might not show accurate differences from different snapshots. This issue is a

known limitation with HP SIM that will be corrected in an upcoming release.

-------------------------------------------------------------

For information on Complex Reporting issues, see Complex issues.

-------------------------------------------------------------

After copying a report from an existing report that contains both system targets and an event filter, only the

event filter is displayed on the Manage Reports page. However, this is only a display problem. You can

select the newly copied report and generate the report correctly for the selected system targets with the event

filter. Then, the selected targets in that generated report displays a combination collection instead of the

system targets.

When running an advanced search on a PostgreSQL or SysMgmtDB database and using the IS NOT attribute

with the operating system criteria, the results are not correct. This issue includes creating a custom system

collection using attributes and creating an automatic event handling event using attributes. The operating

system criteria is made up of three parts, the operating system name, operating system description, and

operating system version. The operating system description is in parenthesis after the operating system name.

When the search runs using the operating system criteria and the IS NOT comparison, it ignores the operating

system description and operating version number part of the criteria and returns incorrect data.

For example, you might have HP-UX systems running HP-UX 11.11 and 11.23. The name for each of those

systems shown in the operating system criteria is HP-UX (HP-UX B.11.11 U) and HP-UX (HP-UX B.11.23 U)

respectively. For example, you only want to see systems that are not HP-UX 11.11 and therefore create an

operating system criteria where operating system IS NOT HP-UX (HP-UX B.11.11 U). However, because the

Operating System criteria using the IS NOT comparison does not work correctly when using the PostgreSQL

or SysMgmtDB database, what you then receive is all systems NOT having an operating system not equal

to HP-UX. Therefore, all HP-UX 11.11 and 11.23 systems are excluded from the list when in reality you only

wanted to exclude the HP-UX 11.11 systems.

Security

If HP SIM is installed after SMH is installed, the SMH 2048-bit key pair is replaced with the HP SIM 1,024-bit

key pair.

In specific instances, after entering your sign in credentials, you might be unable to sign into HP SIM or to

Some versions of Internet Explorer have a problem with underscores in the system name, preventing the

session cookie from working properly. This problem applies to Internet Explorer versions 5.5 and 6.0 that

36 Known Issues and Workarounds