topic Re: WBEM Problem in Operating System - HP-UX

WBEM Problem

Mustafa Al Ahmad — Mon, 30 Aug 2010 10:39:50 GMT

Dears,
when i tried to identify my server in cim i got the following errors:

Starting identification process...
Checking for known running web servers.
Checking for System Management Home Page and other HP web agents.
Received a response from the system management homepage, this system supports SMH.
Checking for WBEM support on system.
This system does not have any SMI-S CIMOM installed
This system doesn't have a server CIMOM installed locally, or cannot connect to it using all credentials specified
Running WBEM rules based identification.
Cannot get ComputerSystem WBEM/WMI data from the system
Running VM Identification.
The system is not a VM Host, or WBEM credentials may not be specified, skipping VM Identification
Running WS-Man identification.
The system did not respond to WS-Management, verify credentials.
Checking for SNMP support on system.
The system did not respond to SNMP, verify security settings and community strings.
Running SNMP base Cluster identification using common cluster MIB.
This was not a system with the common cluster MIBs supported.
Running HP ProLiant management agent identification
The system does not support SNMP.
Running HP NetServer identification.
The system does not support SNMP.
Running HP-UX SNMP identification.
The system does not support SNMP.
Running SNMP System Type Manager identification.
The system does not support SNMP.
Checking for DMI protocol support.
DMI is globally disabled, skipping DMI identification.
Running DMI System Type Manager identification.
The non Windows CMS cannot communicate with Windows DMI, skipping.
Running HP-UX DMI identification.
DMI is globally disabled, skipping DMI identification.
Running HP/Compaq Desktop identification.
The non Windows CMS cannot communicate with Windows DMI, skipping.
Running HP DMI Desktop identification.
DMI is globally disabled, skipping DMI identification.
Running Generic DMI identification.
The non Windows CMS cannot communicate with Windows DMI, skipping.
Running SSH Protocol identification.
The system supports SSH protocol
Running SSH Identification.
This system passed the ssh authentication; it has a valid ssh credential
OS Name is identified by other identifier; continue to run other commands
Running Storage identification.
Did not detect WBEM support on this system. Will not attempt storage identification. If this is a storage host, check WBEM credentials and make sure the providers and CIMOM are operational on the host.
Storage identification completed.
Running HP Service Guard Identification.
Running SNMP Subtypes identification
Create bare-metal device nodes if OA is discovered with "Automatic Device discovery" option enabled.
Create bare-metal server node if ILO is discovered with "Automatic Server discovery" option enabled.
Building system relationships.
Running limited data collection for common attribute.
The SSH is not configured on this system
SMH trust status is true.
Running node communication diagnosis
System identification done with this system.

Here is the output for cimauth -l

mgmnt, root/cimv2, "rw"
mgmnt, root/PG_InterOp, "rw"
mgmnt, root/PG_Internal, "rw"
mgmnt, root/cimv2/npar, "rw"
mgmnt, root/cimv2/vpar, "rw"
mgmnt, root/cimv2/hpvm, "rw"
mgmnt, root/cimv2/hpvm/pending, "rw"

The system credential & the Global credential are the same.

Please help in soloving the above wbem problem.

Apreciated your help.

Best regards,
Mustafa

Re: WBEM Problem

Mustafa Al Ahmad — Mon, 30 Aug 2010 10:42:16 GMT

The above server is HP-UX 11.31

Re: WBEM Problem

Matt (A) Speroni — Thu, 02 Sep 2010 02:32:27 GMT

Hi Mustafa,

Try the following:

# evweb subscribe -L -b external

The handler name used to be the CIM server, moreover the destination url also is the CIM server CIMXML listener.

Kind regards
Matt

Re: WBEM Problem

Mustafa Al Ahmad — Thu, 02 Sep 2010 10:33:38 GMT

Hi matt,
The output of the command you gave me in tha attachment. Would you please explain further?

Thanks in advance..

Re: WBEM Problem

rariasn — Thu, 02 Sep 2010 11:01:59 GMT

Hi Mustafa:

Verify:

# cimconfig -l -c
...
enableSubscriptionsForNonprivilegedUsers=true
enableNamespaceAuthorization=true
..

and restart cimserver

# cimserver -s
# ps -ef | grep cimserver | grep -v grep
# kill nnnn

# cimserver

# cimserver -l -s

Re: WBEM Problem

Mustafa Al Ahmad — Thu, 02 Sep 2010 11:20:57 GMT

Hi Rariasn,

# cimconfig -l -c
enableAuditLog=false
sslClientVerificationMode=disabled
idleConnectionTimeout=0
enableSubscriptionsForNonprivilegedUsers=true
socketWriteTimeout=20
shutdownTimeout=30
authorizedUserGroups=
enableRemotePrivilegedUserAccess=true
enableHttpsConnection=true
enableNamespaceAuthorization=true
enableHttpConnection=false

I have also restarted the cim server & still the problem exist.

Thank You

Best Regards,
Mustafa

Re: WBEM Problem

rariasn — Thu, 02 Sep 2010 11:39:31 GMT

Hi,

http://forums11.itrc.hp.com/service/forums/questionanswer.do?threadId=1385867

Verify port requirements

rgs,

Re: WBEM Problem

rariasn — Thu, 02 Sep 2010 11:45:43 GMT

Mustafa:

And reverify system credentials (user and password) are the same.

rgs,

Re: WBEM Problem

rariasn — Thu, 02 Sep 2010 12:00:12 GMT

Mustafa:

Verify messages from cimserver in syslog.

# grep -i cimserver /var/adm/syslog/syslog.log

Put output from command:

# cimserver -l -s

rgs,

Re: WBEM Problem

rariasn — Thu, 02 Sep 2010 12:00:36 GMT

Sorry:

# cimprovider -l -s

rgs,

Re: WBEM Problem

Mustafa Al Ahmad — Thu, 02 Sep 2010 20:30:56 GMT

Hi Rariasn,

-I have verified the system credential.

-I found a repitive error messeges in syslog.log. Here is a sample

Sep 2 05:57:24 web1prod cimserver[11756]: PGS17200: Authentication failed for u
ser mgmnt.
Sep 2 06:01:00 web1prod cimserver[11755]: fork failed.

- Here is the output of cimprovider -l -s

$ cimprovider -l -s
MODULE STATUS
OperatingSystemModule OK
ComputerSystemModule OK
ProcessModule OK
IPProviderModule OK
DNSProviderModule OK
NTPProviderModule OK
NISProviderModule OK
SDProviderModule OK
IOTreeModule OK
HPUXLVMProviderModule OK
AmgrAgentProviderModule OK
EMSHAProviderModule OK
HPUX_ProviderModule OK
HP_NParProviderModule OK
HP_ResParProviderModule OK
HPUXRAIDSAProviderModule OK
HPUXSASProviderModule OK
HPUXSCSIProviderModule OK
HPUXSCSICSProviderModule OK
HP_VParProviderModule OK
HPUXFCProviderModule OK
HPUXFCCSProviderModule OK
HPUXFCIndicationProviderModule OK
FSProviderModule OK
HPUXIOTreeIndicationProviderModule OK
HPUXLANProviderModule OK
HPUXLANCSProviderModule OK
HP_iCODProviderModule OK
HP_iCAPProviderModule OK
HP_GiCAPProviderModule OK
HP_OLOSProviderModule OK
HP_UtilizationProviderModule OK
HPVMProviderModule OK
Hewlett-Packard:CDM-ProvidersModule OK
SFMProviderModule OK
HPUXStorageIndicationProviderModule OK
HPUXStorageProviderModule OK
SGProvidersModule OK

Re: WBEM Problem

rariasn — Fri, 03 Sep 2010 07:23:27 GMT

Hi Mustafa:

>>>> Sep 2 06:01:00 web1prod cimserver[11755]: fork failed

# cimserver -s
# ps -ef | grep -i cimserver | grep -vE "cimserverd|grep"|awk '{print $2}'|xargs kill

# rm /var/opt/wbem/socket/cimxml.socket

# cimserver

# grep -i cimserver /var/adm/syslog/syslog.log

From cms server: do system identification.

rgs,

Re: WBEM Problem

Mustafa Al Ahmad — Sat, 18 Sep 2010 07:03:52 GMT

Hi Rariasn,

Sorry for late reply since i was in vacation.

The good news is that the problem has been re-solved after restarting the cimserver agent on the server.

Thank you very much & appreciated you help.

Best Regards,
Mustafa

Re: WBEM Problem

Mustafa Al Ahmad — Sat, 18 Sep 2010 07:08:30 GMT

The problem has been re-solved after restarting the cimserver agent on the server.