HP SIM- Install the VCRM on a system

[aleks hdz]

I have already installed the HP SIM but how can I instal the VCRM?

[Bart_Heungens]

Hi,

Normally when you install SIM, VCRM is automatically installed with it.
You can verify this by going to the SMH Systems Management Hompeage of your server where SIM is installed and than check if the VCRM URL is present.

If not, VCRM can be downloaded seperately from the HP site and can also be found on the ICE download...

Kr,
Bart

[radek zima_1]

VCRM is installed with HPSIM or IC, check under services whether "HP Version Control Repository Manager" is running ... R.

[aleks hdz]

i've checked the services of the other servers and the HP VCRM appears enabled and loaded, but the client didn't appears

[Bart_Heungens]

Please rerun a discovery in HP SIM of the server where VCRM is installed...

[aleks hdz]

I've rediscovered the server and I get some errors:

********* Significant issues and overall target
discovery/identification status:
Major: The system cannot be identified properly for HP SIM to
manage; unable to get one or more of the following: model, serial
number or unique identifier (UUID). For management processors,
verify the system is running the latest firmware. For Linux based
operating systems, you must have dmidecode installed, enable the
PermitRootLogin and PasswordAuthentication in sshd, and use root sign-in
credential. For HP-UX, verify the sign-in credential. For Windows, check
if WMIMapper is configured correctly on the CMS and verify the
sign-in credential.
Major: WBEM is not enabled on the Central Management Server (CMS).

********* Additional results (listed for information only):

* Starting identification process...
* Checking for known running web servers...
* Checking for System Management Homepage and other HP web
agents...
Major: The HTTP or HTTPS is globally disabled so skipping web
service discovery.
* Checking for SNMP protocol support on system...
Normal: The system responded to an SNMP request; it supports SNMP
Protocol and has a valid read community string.
* Running SNMP System Type manager ...
Normal: No matching SNMP System Type Manager rule for sysObjID was
found.
* Running SNMP base cluster identification using common
cluster MIB...
Normal: This system does not have the common cluster MIBs support.
* Running IPMI protocol identification...
Normal: IPMI protocol not detected so skipping IPMI Identification.
* Checking for WBEM protocol support on system...
Major: WBEM is not enabled on the Central Management Server (CMS).
* Running WBEM rules based identification...
Major: WBEM is not enabled on the Central Management Server (CMS).
* Running Virtual Machine (VM) Host (non HP Integrity VM Host)
Identification...
Normal: The system is not a VM Host (non HP Integrity VM Host), or
WBEM credentials may not be specified so skipping VM
Identification.
* Running WS-Man identification...
Major: WS-Management(WS-Man) is globally disabled so skipping
WS-Man identification.
* Running HP ProLiant management agent identification...
Normal: Identification can get the system information from the
ProLiant SNMP Foundation agents for servers.
* Running HP NetServer identification...
Normal: System supports the NetServer SNMP agent, adding system
type.
* Running HP-UX SNMP identification...
Normal: System does not have the HP-UX SNMP agents installed.
* Running SSH Protocol identification...
Major: Using SSH Protocol in discovery is disabled on the Central
Management Server (CMS).
* Running SSH Identification...
Major: Using SSH Protocol in discovery is disabled on the Central
Management Server (CMS).
* Running Storage identification...
* Did not detect the WBEM protocol support on this system. SMI
storage identification will be skipped.
* Storage identification completed.
* Running HP Serviceguard Identification...
* Running SNMP subtypes identification...
* No additional subtype(s) found from SNMP.
* Running OA Identifier which will discover systems in an
enclosure if the automatic enclosure discovery option for OA is
enabled...
Normal: The system is not an Onboard Administrator, skipping
automatic discovery of systems in the enclosure.
* Running iLO Identifier which will discover the server if the
automatic server discovery option for iLO is enabled...
Minor: The system responds to the HTTP request but cannot get the
XML output. It is normal for servers not to get the XML data.
* Running p-Class Identifier...
Normal: The system is not a p-Class so skipping p-Class
identification.
* Resolving DNS names...
Normal: The DNS name was successfully resolved for the system.
* Running Virtual Machine Management (VMM) Plug-in
Identification...
Normal: Virtual Machine Management (VMM) Integration is not enabled
so skipping VMM VM Identification.
* Building system relationships...
Minor: The Secure Shell key-based access authentication is not
configured on the system(s).
Major: In order to access Secure Sockets Layer (SSL) based tools
such as System Management Homepage and Version Control Repository
Manager on remote systems without performing an additional sign-in,
you need to establish trust between the Central Management
Server (CMS) and the managed system(s).
* Running system Manage Communication diagnosis...
* System identification finished on system.

[Bart_Heungens]

In the global credentials page, do you have the appropriate accounts to be validated against the servers?

Do you have this on 1 server or on all discovered servers?

One error that I didn't see yet untill now is:
* Checking for System Management Homepage and other HP web
agents...
Major: The HTTP or HTTPS is globally disabled so skipping web
service discovery.
I should focus on that one since the discovery must start with the discovery of the SMH...
Is there anything specific changed on that server?

[aleks hdz]

I have the administrator credential, this happens on all discovered servers

[Bart_Heungens]

I am currently in Las Vegas at HP Discovery so I cannot test anything in my test environment... I will try to pick up next week, hopefully meanwhile someone else can help I hope?

But like I said, I would check that HTTP thing that seems to be disabled... This is not good...

Kr,
Bart

[aleks hdz]

I will do some tests, but rather wait to come back and you can help. Sorry for my English

Thanks