topic Re: Cannot configure server to use WBEM with HPSIM in Server Management - Systems Insight Manager

Cannot configure server to use WBEM with HPSIM

rthonsgard — Thu, 11 Aug 2011 19:31:29 GMT

I'm having trouble configuring a Proliant BL460c G7 with Windows Server 2008 R2 SP1 using WBEM 2.8 with HPSIM 6.03. Every time I try to configure the agents I get the follwing output:

WBEM protocol settings are not valid/enabled for this system in HP SIM. Check yo
ur HP SIM settings for identification via WBEM.
Subscribe to WBEM / WMI Indications ................................. [FAILED]

Setting SNMP trap destination .......................................[SUCCESS]
Set Trust relationship to "Trust by Certificate"
Set Trust relationship to "Trust by Certificate" ................... [SUCCESS]
Added this instance of HP SIM to the trusted certificate list for System Managem
ent Homepage 2.0 or later.

Successfully restarted necessary management applications to ensure that all succ
essful changes will be effective.

Re-identifying system to get updated information ...

Checking whether the HP SIM CMS can login to the SMH URL

I have no problem adding servers using SNMP, but cannot add any using WBEM. I have my system credentials set and WBEM is enabled on the SIM server.

Re: Cannot configure server to use WBEM with HPSIM

jim goodman — Fri, 12 Aug 2011 18:53:01 GMT

When you say 6.03 are you meaning SIM 6.3?

Not a lot of info to go off of, but here are something I'd do to try and isolate it.

Verify the WMI Mapper is configured properly and the service is running. Options --> Protocol Settings --> WMI Mapper Proxy

Input the credential in the target node's (Tools and Links tab) System Credentials, click Advanced Protocols and add the WBEM credential there.

Windows Firewall off on both CMS and Target?

Using local or domain acct?

Is it adminstrator priviledge?

on the cms from a cmd window try running mxwbemsub -a -n <nodename>

you should be prompted for credentials

If you are using a local acct to access the target server, for the WBEM credential typically add the hostname in place of a domain in the username ex. hostname\username and see if that works. I have run into this one a number of times in some 2k8R2 AD situations.

another thing you can do is download Microsoft WMI Object Browser to the CMS and make sure you can browse the CIMv2 hive on the target from the CMS outside of SIM - that'll help isolate it.

There's some troubleshooting ideas for you to try.

ESXI5.5 not discovered through HPSIM

satish0007 — Fri, 13 Nov 2015 15:14:43 GMT

Hello,

Could anyone of you please help me resolve this issue. I am new to the HPSIM and have setup new HPSIM7.4 and doing testing.

Trying to discover ESXi server but go. Here is the discovery report that shows WBEM credentials is not correct but I am 100% sure the credentials is ok.

Please check the logs and suggest correct steps that can solve me problem.

Regards,

Satish

********* Significant issues and overall target discovery/identification
status:
Major: There is no working sign-in credential for this system. Go to
Options -> Security -> Credentials -> System Credentials and either
enter the credentials there or be sure that the checkbox enabling
HP SIM to try other credentials is checked.
Minor: The discovered blade is not in an enclosure. For c-Class
enclosures, verify that the supported OA firmware version is
installed and verify that the OA has been discovered in HP SIM. For
p-Class enclosures, verify that the iLO firmware and the HP Insight
Management Agents on the server are installed and verify that the
iLO has been discovered in HP SIM.
Normal: The system has valid hardware data (model, serial number, and
unique identifier) and has been identified properly for SIM to
manage.
Critical: There are no valid WBEM / WMI credentials for the system(s).

********* 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 did not respond to SNMP. Verify security settings and
community strings in Options->Security->Credentials->System
Credentials
* 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 system does not support SNMP.
* 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...
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.
Critical: There are no valid WBEM / WMI credentials for the system(s).
* 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: The system does not support SNMP.
* Running HP-UX SNMP identification...
Normal: The system does not support 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 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...
Minor: Running an ipmiutil command failed and the IPMI protocol is not
supported.
* 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...
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: The system does not support SNMP.
* 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: 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.

Re: ESXI5.5 not discovered through HPSIM

Andrew_Haak — Fri, 13 Nov 2015 15:27:16 GMT

Hello there,

What is the hardware type ? Gen8 or lower ?

The credentials on a Gen7 or lower need to be the root user or an other user with root like rights. This is a system user not an ESX user. Is the server is a Gen8 or higher you need to discover the ILO and use Agentless Management Service software.

Re: ESXI5.5 not discovered through HPSIM

satish0007 — Mon, 16 Nov 2015 11:32:08 GMT

Hi Andrew,

Server Moderl is Gen7. When I tried with root, it's get discover servers now.

I have to provide root access to the domain account to discover ESX host, right ?

One more query, VM's rinning on hosts are also getting discovered along with ESX. how can I stop them.

I want only ESX host to be monitor.

Thanks for you help :) It's realy usefull for me.

Regards,

Satish