- Community Home
- >
- Servers and Operating Systems
- >
- HPE ProLiant
- >
- Server Management - Systems Insight Manager
- >
- HP Blade ILO4 using only SNMP V3, Traps not receiv...
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
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
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
09-24-2013 09:53 PM
09-24-2013 09:53 PM
HP Blade ILO4 using only SNMP V3, Traps not received in HP SIM
Hi,
We have a requirement to use only snmpv3 (for security reasons) to monitor HP blade center C7000 Chassis. I have all the blades with ILO4 which supports snmpv3 and installed SIM 7.2 with latest hotfix. I have configured all the blades to use snmpv3 and it works fine when discovering the blades, log shows snmpv3 was found and successfully authenticated.
However issue here is no traps are received if I disable snmpv1 on the iLO. if I enabel snmpv1 on iLO traps/events are getting generated and displayed properly but not when snmpv1 is disabled. I also did wireshark and alerts sent from iLO however HP SIM does not display the events. Also enabled snmp authentication failure MIB to show failure events in SIM, but there are no failure events. I m confused here.. The requirement is to use only snmpv3 for this environment.
Any suggessions will be appreciated.
Thanks
Xeon
- Tags:
- snmp
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-26-2013 01:40 AM
09-26-2013 01:40 AM
Re: HP Blade ILO4 using only SNMP V3, Traps not received in HP SIM
Hi,
i've not configured this myself so I cannot give conclusive answer.
However, I would recommend to make sure both SIM as the ILO firmware are up-to-date. I've seens many 'resolved' issues regarding snmpv3 both in ILO as SIM change logs.
If that does not resolve the issue, it might be worth creatign a support call at HP.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-27-2014 09:02 PM
11-27-2014 09:02 PM
HP Blade ILO4 using only SNMP V3, Traps not received in HP SIM
Hi Xeon,
Can you please tell me how you configured SNMP V3 in HP blade center C7000.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-24-2015 10:58 PM
03-24-2015 10:58 PM
Re: HP Blade ILO4 using only SNMP V3, Traps not received in HP SIM
Hi,
I'm having trouble getting HPSIM to discover my new G9 blade.
Although SNMPv3 parameters are configured on both ilo & SIM, SIM is still saying "The system did not respond to SNMPv3".
It also mentions "The system is unable to connect via HTTPS" although I can login to the ilo using HTTPS.
Can you let me know how I can go about troubleshooting this?
Log from the discovery is below.
********* Significant issues and overall target discovery/identification
status:
Minor: The name of the system could not be resolved to a fully qualified
domain name. For a Windows CMS, make sure that the domain name of
the managed system is included in the DNS suffixes in the Windows
Advanced TCP/IP Settings page.
Minor: The reverse DNS lookup using the IP address: x.x.x.x failed.
It might be that the nslookup timed out or DNS server cannot find
this address, or that the domain does not exist.
Minor: Verify that your name resolution service or the host file
configuration is configured properly so that your system's hostname
can be resolved to the fully qualified domain name.
Normal: The system has valid hardware data (model, serial number, and
unique identifier) and has been identified properly for SIM to
manage.
********* Additional results (listed for information only):
* Starting identification process...
* Checking for known running web servers...
Minor: The system is unable to connect via HTTPS
* Could not generate DH keypair
* 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: Identification can get the system information from the ProLiant
SNMP Foundation agents for servers.
* Running SNMP base cluster identification using common cluster
MIB...
Normal: The system is identified as management processor, skipping SNMP
cluster identification.
* Checking for WBEM protocol support on system...
Normal: The system is not a server so skipping WBEM identification.
* Running WBEM rules based identification...
Normal: The system is not a server so skipping WBEM identification.
* 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 does does not have the NetServer SNMP agents installed.
* 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: Skipping IPMI discovery. System is logical device.
* 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: 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...
* 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.
Sanjay Mundhra
I am a HPE Employee