- Community Home
- >
- Servers and Operating Systems
- >
- HPE ProLiant
- >
- Server Management - Systems Insight Manager
- >
- Re: VCRM no longer found in SIM
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-30-2015 06:52 AM - edited тАО07-30-2015 06:55 AM
тАО07-30-2015 06:52 AM - edited тАО07-30-2015 06:55 AM
VCRM no longer found in SIM
Hello,
I have the following servers:
- Linux (CentOS 7) Virtual machine (on ESXi 5.1) running SIM 7.4 with the May 2015 patches
- Windows (2012 R2) Virtual machine (on ESXi 5.1) running VCRM 7.4.2.0
Originally, the VCRM machine was a Windows 2008 R2 machine, and I could select this machine as a Version Control Repository in SIM. But after upgrading the machine from 2008R2 to 2012R2, SIM doesn't find the VCRM anymore. I've already imported the certificate of the SIM server as a trusted management machine in SMH on the VCRM machine, changed trust levels to all possible options, ran Pegasus WMI wrapper as Local System and a dedicated service account, disabled the firewall completely on the Windows machine, but none of this helps: SIM refuses to see the VCRM.
VCRM is showing up normally in SMH, and I can attach individual VCA's to this VCRM, so that works normally, just not the discovery in SIM.
Does anyone have an idea what else I can try, or is this combination not supposed to work? If that's the case, I'll just reinstall the VCRM machine with 2008R2.....
Joost
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-30-2015 07:23 AM
тАО07-30-2015 07:23 AM
Re: VCRM no longer found in SIM
So in the list of servers you can choose from the select VCRM server the VCRM server id not selectable?
If you install an empty VCRM on any other server does it show up as a VCRM server?
Andrew
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-30-2015 10:29 PM
тАО07-30-2015 10:29 PM
Re: VCRM no longer found in SIM
Hi,
I have installed VCRM (also 7.4.2.0) on the Linux SIM server and it's recognised normally. But I can't seem to attach Windows servers to the baseline in SIM, so I need a Windows VCRM to check the baseline of the Windows servers. And, as I said before, I had no problems with the 7.4.2.0 VCRM on a Windows 2008R2 machine, it's just the 2012R2 server that refuses to work.
Joost
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-31-2015 12:20 AM
тАО07-31-2015 12:20 AM
Re: VCRM no longer found in SIM
Andrew
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-31-2015 01:41 AM
тАО07-31-2015 01:41 AM
Re: VCRM no longer found in SIM
Hello Andrew,
SMH is available, and VCA's can connect to the VCRM on port 2381, so SMH/VCRM seem to work. It's just SIM that doesn't recognise the server.
Joost
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-31-2015 02:15 AM
тАО07-31-2015 02:15 AM
Re: VCRM no longer found in SIM
Andrew
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-31-2015 03:02 AM
тАО07-31-2015 03:02 AM
Re: VCRM no longer found in SIM
Hi Andrew,
No websites are visible in the second tab.
I ran a new identify job for the virtual server, and this is the output:
[quote]
********* Significant issues and overall target discovery/identification
status:
Minor: The discovered VM guest is not associated with the VM host. Verify
that the supported HP Insight Management Agents or WBEM providers
are installed on the host, and verify that the host has been
discovered. For an association between Citrix XenServer host and
its virtual machines, the HP Insight Control virtual machine
management (VMM) software must be installed and the VM Host must be
registered in VMM.
Normal: The system has valid hardware data (model, serial number, and
unique identifier) and has been identified properly for SIM to
manage.
Critical: HP SIM cannot communicate with these systems using the WBEM
protocol.
********* Additional results (listed for information only):
* Starting identification process...
* Checking for known running web servers...
* 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.
* Checking for SNMPv3 protocol support on system...
Normal: The system did not respond to SNMPv3. Verify security settings and
v3 credentials in Options->Security->Credentials->System
Credentials
* Running HP ProLiant management agent identification...
Normal: The ProLiant SNMP Foundation agents for servers are not installed
or are not configured.
* Running SNMP base cluster identification using common cluster
MIB...
Normal: This system does not have the common cluster MIBs support.
* Checking for WBEM protocol support on system...
Minor: This system does not have any SMI-S CIMOMs installed. No storage
systems will be found on this system.
Minor: The Central Management System (CMS) cannot communicate with the
CIMOM locally installed on the managed system using the WBEM
protocol, Identification will try to identify Windows systems using
the WMI Mapper as proxy; for Linux and HP-UX systems, check
credentials by going to Options->Security->Credentials->System
Credentials. For Linux systems also check if the HP WBEM provider
is installed.
* Running WBEM rules based identification...
Minor: Identification cannot get computer system hardware data from the
WBEM / WMI providers.
* 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...
* Did not detect the WBEM protocol support on this system. SMI
storage identification will be skipped.
* Storage identification completed.
* 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 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 XMLReply Identifier which will discover systems in a
rack/enclosure if the automatic discovery option for the container
node is enabled...
* 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.
Minor: If the http communication from CMS to target is working, but if it
is found to be slow then try increasing the Default connection
timeout parameter for http in global protocol settings.
* Running p-Class Identifier...
Normal: The system is not a p-Class so skipping p-Class identification.
* Running IPMI protocol identification...
Normal: IPMI protocol not detected so skipping IPMI Identification.
* Running SSH Protocol identification...
Normal: This system has SSH protocol support.
* Running SSH Identification...
Normal: The system can be logged in using SSH protocol; has a valid SSH
credential.
Normal: OS Name is identified by the SSH Identification.
* Running WS-Man identification...
Minor: The system did not respond to WS-Management (WS-Man) request.
* 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...
* Running SNMP System Type manager ...
Normal: No matching SNMP System Type Manager rule for sysObjID was found.
* Running SNMP subtypes identification...
* No additional subtype(s) found from SNMP.
* Resolving DNS names...
Normal: The fully qualified domain name was successfully resolved for the
system.
* Checking if the Node is a Virtual Center...
Normal: Skipping MxVirtualCenter Identifier.
* 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.
[/quote]
Only strange thing I see here is that SIM thinks there's no WBEM support, although the Pegasus WMI wrapper services are running on the Windows virtual machine.
Joost
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-31-2015 06:08 AM - edited тАО07-31-2015 01:24 PM
тАО07-31-2015 06:08 AM - edited тАО07-31-2015 01:24 PM
Re: VCRM no longer found in SIM
You could install these or add Windows credentials for the WBEM Discovery.
Because these protocols fail the discovery can't detect if the object is a server and will not run the SMH discovery.
Once the discovery works for either SNMP or WBEM i think the discovery will finish ok.
Andrew
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-03-2015 12:25 AM
тАО08-03-2015 12:25 AM
Re: VCRM no longer found in SIM
SNMP agents don't install on a VM, I thought? Also, I didn't need them when VCRM was running on Windows 2008R2.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-03-2015 12:53 AM
тАО08-03-2015 12:53 AM
Re: VCRM no longer found in SIM
Andrew