HP Insight Foundation Software for ProLiant - Manual (Page 45)

by a search that compares ProLiant Support Packs only if every component in the ProLiant Support Pack
is present on the targeted system.
It is unlikely that all of the components in a ProLiant Support Pack will be installed on any system. This causes
most searches that include Support Pack software criteria to return no systems.
After downloading the 6.40 ProLiant Support Pack into my existing VCRM 1.0 directory, the catalog does
not display the ProLiant and Integrity Support Pack Why doesn't this ProLiant Support Pack display?
Solution: The 6.40 ProLiant Support Pack does not work with VCRM 1.0. HP recommends that you install
VCRM 2.0 or later.
Note: The installation of the VCRM 2.0 does not require a reboot.
I have the VCRM Auto Update feature configured to automatically download ProLiant and Integrity Support
Packs and the VCRM states the updates have completed successfully. However, no files have been downloaded.
Solution: A log entry appears in the VCRM Log indicating Automatic update downloaded 0 files. No VCAs
have provided operating systems information to use as a download selection criteria.
HP recommends the following actions:
•
If the VCA is not installed on any system within the network, you must install the VCA on a system and
configure the VCA to use the VCRM.
•
If the VCA is installed on a system within the network, you must configure the VCA to use the VCRM.
Miscellaneous problems
Should the VCRM be installed before running Discovery in HP SIM, and if so, why?
Solution: While it is not essential, it is a good idea to install a VCRM before running Discovery. Be sure that
this repository trusts HP SIM. Refer to
Setting up Trust Relationships in the HP SIM User Guide for more
information on trust relationships. It is a good idea to install a 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 Agents for Windows in HP SIM, 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 Agents 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 Agents for Windows from the
Windows 2000 and Windows NT branch.
What capabilities do I get from the VCA alone?
Solution: The VCA provides a list of the HP Web-enabled System Management Software and firmware
installed on the local server. For the VCA to provide version control and software distribution functionality,
it must be configured to refer to a VCRM.
Does HP have any intention of disabling the Install icon on those components that do not install silently or
without user intervention in future releases?
Solution: Yes.
The VCA or VCRM display as links under the Integrated Agents list on the SMH, but the application is
missing from the version control category on the SMH's Home tab, or the category does not display at all.
When I click the link under the Integrated Agents, a page displays indicating The application is
not available
.
Solution: On Windows, the associated Win32 service is stopped. You must restart the HP Version Control
Agent or HP Version Control Repository Manager's Win32 service on the server. If the service is not set for
automatic startup, then configure the service to start automatically. If the service stopped unexpectedly, check
the Windows NT Event Log as well as the application's log for additional information.
On Linux, the associated VCA daemon process is stopped, and the VCA daemon can be restarted by the
root
user running /etc/init.d/hpvca restart.
Miscellaneous problems 45