The Version Control Repository Manager (VCRM) was not found on any discovered systems.

[PhS-]

Hello,

I have the following setup :

Running on a single VM :

OS : Windows 2012R2

HP System Management Homepage v7.3.0.9

Version Control Repository Manager 7.3.4.0

Systems Insight Manager 7.3.0 - Windows (Build version: C.07.03.00.00) with all the patches

I'm trying to configure HPSIM, Options, Software/Firmware, Version Control Repository... and I get the following message :

"The Version Control Repository Manager (VCRM) was not found on any discovered systems. "

I have tried the sugested "Identify Systems" without success.

********* 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: Global SNMP Identification is disabled.

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

* Starting identification process...
* Checking for known running web servers...
* Checking for SNMP protocol support on system...
Major: Global SNMP Identification is disabled.
* Checking for SNMPv3 protocol support on system...
Minor: Global SNMPv3 Identification is disabled.
* Running HP ProLiant management agent identification...
Normal: SNMP is globally disabled, skipped SNMP identification.
* Running SNMP base cluster identification using common cluster
MIB...
Normal: SNMP is not supported or globally disabled, skipping SNMP cluster
identification.
* Checking for WBEM protocol support on system...
Normal: This system has WBEM protocol support.
Minor: This system does not have any SMI-S CIMOMs installed. No storage
systems will be found on this system.
Normal: This system has a server CIMOM installed.
* Running WBEM rules based identification...
Normal: Got the system information from the WBEM / WMI providers and it has
a valid WBEM credential.
* 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 Storage identification...
* Storage identification completed.
* Running HP NetServer identification...
Normal: SNMP is globally disabled, skipped SNMP identification.
* Running HP-UX SNMP identification...
Normal: SNMP is globally disabled, skipped SNMP identification.
* Running OA Identifier which will discover systems in an enclosure
if the automatic enclosure discovery option for OA is enabled...
Normal: A non-embedded operating system is detected so skipping the OA
identification.
* Running XMLReply Identifier which will discover systems in a
rack/enclosure if the automatic discovery option for the container
node is enabled...
Normal: A non-embedded operating system is detected so skipping the
Management processor identification.
* Running iLO Identifier which will discover the server if the
automatic server discovery option for iLO is enabled...
Normal: A non-embedded operating system is detected so skipping the ILO
identification.
* Running p-Class Identifier...
Normal: The system is not a p-Class so skipping p-Class identification.
* Running IPMI protocol identification...
Normal: Skipping IPMI discovery in favor of WBEM/SNMP discovery.
* Running SSH Protocol identification...
Normal: This system has SSH protocol support.
* Running SSH Identification...
Minor: The system cannot be logged in using SSH protocol; check
credentials or check the settings in the SSH configuration file
* Running WS-Man identification...
Normal: A non-embedded operating system is detected so skipping the WS-MAN
identification.
* Running Monarch OA Identification...
Normal: The system is not a monarch OA so skipping monarch OA
identification.
* Checking for System Management Homepage and other HP web agents...
Normal: The system is not a server, storage or desktop. Skipping the check
for System Management Homepage.
* Running HP Serviceguard Identification...
Normal: The system is not part of HP Serviceguard cluster.
* Running SNMP System Type manager ...
Major: Global SNMP Identification is disabled.
* Running SNMP subtypes identification...
* Resolving DNS names...
Normal: The fully qualified domain name was successfully resolved for the
system.
* Checking if the Node is a Virtual Center...
Normal: Node is not a Virtual Center Node
* Running Virtual Machine Management (VMM) Plug-in Identification...
* Building system relationships...
Minor: The Secure Shell key-based access authentication is not configured
on the system(s).
Minor: System Management Homepage (SMH) is not installed or is not
responding on the system(s).
* Running system Manage Communication diagnosis...
* System identification finished on system.

 Any help would be appreciate.

[CJPerez]

check that you have installed and configured SNMP service. You have to accept and send traps to the HPSIM server...

HP SIM "--> Security--> Credentials Options" menu--> trusted Systems adds the VCRM server certificate, even if it is the same as the server from HP SIM.

In HP SIM menu "Options--> Software/Firmware--> Version Control Repository ' you see your VCRM as Trusted Server?

[PhS-]

SNMP service is not installed ... why should I do so ? (is it mandatory even is running on the same machine)?

 You mean : 

HP SIM ->Options ->Security ->Credentials-> Trusted Systems ... ?

And there should I use the tab Single Sin-on Trusted Certificates ? or Trusted Certificates (there Always Accept is selected for the moment )

[CJPerez]

HP SIM ->Options ->Security ->Credentials-> Trusted Systems ... ? Is correct, a translator´s problem.

When I have had problems to discover a server I've solved with SNMP.

Discovery requirements are the same as for any other server. HP SIM attempts the discovery by SNMP, WBEM or SSH. One of the 3 options must be available or can not discovery the server.

The configuration of trusted systems will be necessary when you have discovered the server and configured as VCRM. If you don't put the VCRM certificate in trusted system, the server does not include as trust.

Regards