- Community Home
- >
- Servers and Operating Systems
- >
- HPE BladeSystem
- >
- BladeSystem - General
- >
- Re: All c-Class enclosures not populating after di...
BladeSystem - General
1752392
Members
6064
Online
108788
Solutions
Forums
Categories
Company
Local Language
юдл
back
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
юдл
back
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
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- 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
тАО01-14-2009 09:21 AM
тАО01-14-2009 09:21 AM
All c-Class enclosures not populating after discovery
I have many c-Class enclosures and none are showing up in SIM under "All c-Class Enclosures" after discovery. The system type shows up as unknown.
Product Number 412133-B21
System Type Unknown
Hardware Description HP Onboard Administrator
OS Name Embedded
OS Type Embedded
Management Protocols SNMP:1.0
I've spent a fair amount of time making sure all the firmware and login credentials are current and correct. I've also perfomed a different installation of SIM on my laptop which is on the same network, and ran the first time setup and it found all the enclosures within the inclusion range entered and listed them correctly under "All c-Class Enclosures"
So I've narrowed this issue down to some config or misconfig issue on this particlular SIM installation.
Anyone have some suggestions on what needs to happen to get these enclosures to show up properly?
Thanks,
Jason
Product Number 412133-B21
System Type Unknown
Hardware Description HP Onboard Administrator
OS Name Embedded
OS Type Embedded
Management Protocols SNMP:1.0
I've spent a fair amount of time making sure all the firmware and login credentials are current and correct. I've also perfomed a different installation of SIM on my laptop which is on the same network, and ran the first time setup and it found all the enclosures within the inclusion range entered and listed them correctly under "All c-Class Enclosures"
So I've narrowed this issue down to some config or misconfig issue on this particlular SIM installation.
Anyone have some suggestions on what needs to happen to get these enclosures to show up properly?
Thanks,
Jason
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-14-2009 09:37 AM
тАО01-14-2009 09:37 AM
Re: All c-Class enclosures not populating after discovery
Below is an enclosure identification log:
David Claypool noticed the desktop agents were showing as being installed.
One red flag in your identification log is the comment "System has the SNMP ProLiant *desktop* agents installed, adding system type." which shouldn't be happening.
Anyone know where it might be pulling this from?
Starting identification process...
Checking for known running web servers.
Checking for System Management Home Page and other HP web agents.
The System Management Homepage is not supported on this system.
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 VMware ESX 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 responded to a SNMP request, it supports SNMP.
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
\\System has the SNMP ProLiant desktop agents installed, adding system type.
Running HP NetServer identification.
System supports the NetServer SNMP agent, adding system type
Running HP-UX SNMP identification.
System does not have the HPUX SNMP agents installed.
Running SNMP System Type Manager identification.
No matching SNMP System Type Manager rule was found.
Checking for DMI protocol support.
The Windows CMS cannot communicate with HP-UX or other DMI, skipping.
Running DMI System Type Manager identification.
The system does not have Windows DMI support.
Running HP-UX DMI identification.
The system does not have HP-UX DMI support.
Running HP/Compaq Desktop identification.
The system does not have Windows DMI support.
Running HP DMI Desktop identification.
The system does not have HP DMI Desktop support.
Running Generic DMI identification.
The system does not have Generic DMI support.
Checking for SSH protocol support.
The system supports SSH protocol
The SSH protocol is not supported on this system
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.
The system is not part of HP Service Guard cluster
Checking if this system is supported by Insight Power Manager.
Insight Power Manager is not supported.
Running VM identification.
Building system relationships.
Running limited data collection for common attribute.
Done with limited data collection, checking retrieved data.
The system does not have SMH or SSO support.
Running node communication diagnosis
System identification done with this system.
Thanks Again,
Jason
David Claypool noticed the desktop agents were showing as being installed.
One red flag in your identification log is the comment "System has the SNMP ProLiant *desktop* agents installed, adding system type." which shouldn't be happening.
Anyone know where it might be pulling this from?
Starting identification process...
Checking for known running web servers.
Checking for System Management Home Page and other HP web agents.
The System Management Homepage is not supported on this system.
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 VMware ESX 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 responded to a SNMP request, it supports SNMP.
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
\\System has the SNMP ProLiant desktop agents installed, adding system type.
Running HP NetServer identification.
System supports the NetServer SNMP agent, adding system type
Running HP-UX SNMP identification.
System does not have the HPUX SNMP agents installed.
Running SNMP System Type Manager identification.
No matching SNMP System Type Manager rule was found.
Checking for DMI protocol support.
The Windows CMS cannot communicate with HP-UX or other DMI, skipping.
Running DMI System Type Manager identification.
The system does not have Windows DMI support.
Running HP-UX DMI identification.
The system does not have HP-UX DMI support.
Running HP/Compaq Desktop identification.
The system does not have Windows DMI support.
Running HP DMI Desktop identification.
The system does not have HP DMI Desktop support.
Running Generic DMI identification.
The system does not have Generic DMI support.
Checking for SSH protocol support.
The system supports SSH protocol
The SSH protocol is not supported on this system
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.
The system is not part of HP Service Guard cluster
Checking if this system is supported by Insight Power Manager.
Insight Power Manager is not supported.
Running VM identification.
Building system relationships.
Running limited data collection for common attribute.
Done with limited data collection, checking retrieved data.
The system does not have SMH or SSO support.
Running node communication diagnosis
System identification done with this system.
Thanks Again,
Jason
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-14-2009 10:38 PM
тАО01-14-2009 10:38 PM
Re: All c-Class enclosures not populating after discovery
hi Jason,
The c-class enclosures will appear properly iff Onboard Administrators (OA) get properly discovered. Please check if you have put in any restricitions on SNMP in the Onboard Administrator SNMP settings. Also, try to enable and disable SNMP once on OA.
Whats the SIM version? and OA firmware?
The c-class enclosures will appear properly iff Onboard Administrators (OA) get properly discovered. Please check if you have put in any restricitions on SNMP in the Onboard Administrator SNMP settings. Also, try to enable and disable SNMP once on OA.
Whats the SIM version? and OA firmware?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-16-2009 08:18 AM
тАО01-16-2009 08:18 AM
Re: All c-Class enclosures not populating after discovery
No restrictions on SNMP. I tried disabling and reenabling with no success.
OA 2.32
SIM 5.2 w SP2
HP BladeSystem Integrated Manager 3.4
HP Insight Power Manager 1.40
HP Performance Management Pack 4.7.1
HP Server Migration Pack 2.0.2
HP Virtual Machine Management Pack 2.0.2
Rapid Deployment Pack 3.81
-We have over 10 of these an none show up under Class C enclosures in SIM
-You may have missed this, but I installed a separate copy of SIM 5.2 on my laptop and it discovered and listed the enclosures properly on the first try, so I'm sure its not anything on the OA/Enclosure side.
Does anyone know this process well enough to give me some further troubleshooting steps?
I need someone to break out the Big Guns as this seems to be a code level issue. :-)
screen shot of sim discovery attached
Thanks
Jason
OA 2.32
SIM 5.2 w SP2
HP BladeSystem Integrated Manager 3.4
HP Insight Power Manager 1.40
HP Performance Management Pack 4.7.1
HP Server Migration Pack 2.0.2
HP Virtual Machine Management Pack 2.0.2
Rapid Deployment Pack 3.81
-We have over 10 of these an none show up under Class C enclosures in SIM
-You may have missed this, but I installed a separate copy of SIM 5.2 on my laptop and it discovered and listed the enclosures properly on the first try, so I'm sure its not anything on the OA/Enclosure side.
Does anyone know this process well enough to give me some further troubleshooting steps?
I need someone to break out the Big Guns as this seems to be a code level issue. :-)
screen shot of sim discovery attached
Thanks
Jason
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP