README - HP Systems Insight Manager 5.3 with Update 1

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

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

have applied Internet Explorer patch Q313675 or any patch that supersedes or includes that patch, such

as Q316059 and Q319182.

Therefore, do not use underscores in any system name for systems being managed by HP SIM.

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

If you receive the Warning HTTPS Hostname Mismatch when accessing HP SIM and you click No, you will

continue to receive the error until you click Yes. You will then be taken to the Sign in page.

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

You will not be able to sign into HP SIM if you install HP SIM on a standalone/workstation system and then

promote that same system to a Windows Domain Controller.

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

On 64-bit Linux, if no user can log in to the browser interface, then verify there is also a 32-bit PAM interface

installed.

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

On an HP-UX or Linux system, you must sign in as root the first time you sign in to HP SIM, even if you

installed with another superuser account. Authorizations can then be added for superuser or other accounts.

SNMP

Windows 2003 installations do not have SNMP installed by default, so you must install SNMP manually.

After SNMP is installed, the security settings have the local host enabled only. The default configuration for

Search 37