- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: WBEM Problem
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
тАО08-30-2010 03:39 AM
тАО08-30-2010 03:39 AM
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
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-30-2010 03:42 AM
тАО08-30-2010 03:42 AM
Re: WBEM Problem
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-01-2010 07:32 PM
тАО09-01-2010 07:32 PM
Re: WBEM Problem
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-02-2010 03:33 AM
тАО09-02-2010 03:33 AM
Re: WBEM Problem
The output of the command you gave me in tha attachment. Would you please explain further?
Thanks in advance..
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-02-2010 04:01 AM
тАО09-02-2010 04:01 AM
Re: WBEM Problem
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-02-2010 04:20 AM
тАО09-02-2010 04:20 AM
Re: WBEM Problem
# 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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-02-2010 04:39 AM
тАО09-02-2010 04:39 AM
Re: WBEM Problem
http://forums11.itrc.hp.com/service/forums/questionanswer.do?threadId=1385867
Verify port requirements
rgs,
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-02-2010 04:45 AM
тАО09-02-2010 04:45 AM
Re: WBEM Problem
And reverify system credentials (user and password) are the same.
rgs,
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-02-2010 05:00 AM
тАО09-02-2010 05:00 AM
Re: WBEM Problem
Verify messages from cimserver in syslog.
# grep -i cimserver /var/adm/syslog/syslog.log
Put output from command:
# cimserver -l -s
rgs,
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-02-2010 05:00 AM
тАО09-02-2010 05:00 AM
Re: WBEM Problem
# cimprovider -l -s
rgs,