Miscellaneous problems – HP Systems Insight Manager User Manual

Page 44

Advertising
background image

Solution: Generally, HP Service Pack for ProLiant cannot be used for comparison when developing
a software update search. However, if you must compare ProLiant Support Packs, use the following
guidelines when selecting HP Service Pack for ProLiant to compare:

The only comparison you can use with a HP Service Pack for ProLiant is Equal To.

Systems Insight Manage cannot determine whether a HP Service Pack for ProLiant was installed
on a system, only whether all of the components in a HP Service Pack for ProLiant are installed
on a system. A targeted system is returned by a search that compares HP Service Pack for
ProLiant only if every component in the HP Service Pack for ProLiant is present on the targeted
system.

It is unlikely that all of the components in a HP Service Pack for ProLiant will be installed on any
system. This causes most searches that include HP Service Pack for ProLiant software criteria to
return no systems.

After downloading the 6.40 HP Service Pack for ProLiant into my existing HP VCRM 1.0 directory,
the catalog does not display the HP Service Pack for ProLiant, ProLiant and Integrity Support Packs
Why doesn't this HP Service Pack for ProLiant display?

Solution: The 6.40 HP Service Pack for ProLiant does not work with HP VCRM 1.0. HP recommends
that you install HP VCRM 2.0 or later.

Note: The installation of the HP VCRM 2.0 does not require a reboot.

I have the HP VCRM Auto Update feature configured to automatically download HP Service Pack
for ProLiant, ProLiant and Integrity Support Packs and the HP VCRM states the updates have
completed successfully. However, no files have been downloaded.

Solution: A log entry appears in the HP VCRM Log indicating Automatic update downloaded 0
files. No HP VCAs have provided operating systems information to use as a download selection
criteria
.

HP recommends the following actions:

Configure HP VCRM and select operating system to download PSP.

If the HP VCA is not installed on any system within the network, you must install the HP VCA
on a system and configure the HP VCA to use the HP VCRM.

If the HP VCA is installed on a system within the network, you must configure the HP VCA to
use the HP VCRM.

Miscellaneous problems

Should the HP VCRM be installed before running Discovery in Systems Insight Manage, and if so,
why?

Solution: While it is not essential, it is a good idea to install a HP VCRM before running Discovery.
Be sure that this repository trusts Systems Insight Manage. Refer to Setting up Trust Relationships
in the Systems Insight Manage User Guide for more information on trust relationships. It is a good
idea to install a HP VCRM is so that the Software Version Status Polling task can properly sort the
versions of software retrieved from systems. If you do not set up a repository before running
Discovery, then the versions are sorted when a software criteria search is set up for the first time.

Why is it that when I search for systems with Foundation Agent's for Windows in Systems Insight
Manage, I get only the Windows 2000 systems back and not Windows NT?

Solution: Even though you choose a component that is supported for both Windows NT and
Windows 2000, the search only returns the systems that match the operating system tree from
which you chose the component when you created the search. In this example, if you chose the
Foundation Agent's for Windows from the Windows 2000 branch of the criteria tree, then only
Windows 2000 systems are returned. If you want systems from both Windows 2000 and Windows
NT, choose the Foundation Agent's for Windows from the Windows 2000 and Windows NT
branch.

44

Troubleshooting

Advertising
This manual is related to the following products: