- Community Home
- >
- Servers and Operating Systems
- >
- HPE ProLiant
- >
- Server Management - Systems Insight Manager
- >
- MIB's ignored
Server Management - Systems Insight Manager
1748195
Members
3875
Online
108759
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
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
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
03-10-2010 09:23 PM
03-10-2010 09:23 PM
MIB's ignored
We have implemented a CMS (V5.3SP1)/Windows.
We have hundreds of Linux servers trapping to the CMS as well as many other systems/devices. Everytime snmpd is restarted, we get a trap of 1.3.6.1.4.1.8072.4.6.2 (generic unregistered) followed by a "Cold Start" event.
We eventually worked out that the unregistered was snmpd sending out a shutdown trap. For whatever reason net-snmp says this should be 1.3.6.1.4.1.8072.4.0.2 yet every server bar none use 6 rather than 0 for the trap id.
To get around this we compiled the net-snmp-agent-mib adding trap id 6 then loaded it into SIM. A snmp broswer shows that 1.3.6.1.4.1.8072.4.6.2 maps to nsNotifyShutdownLocal and 1.3.6.1.4.1.8072.4.0.2 maps to nsNotifyShutdown. These are shown in the Options->Events->SNMP Trap Settings so I assume the mib loaded OK. However, when the traps come through, they get reported as generic unregistered as before.
We have checks and checked the MIB and cannot find anything wrong with it.
But the interesting thing is that the "Cold Start" is 1.3.6.1.4.1.8072.3.2.10 which is not defined in net-snmp (even though it has it's enterpise OID) and I can't find a mib where it is defined. So it looks like the CMS ignores our mib, ignore things with enterpise 8072 or processes 8072 internally.
Does anyone know what is going on here?
We have hundreds of Linux servers trapping to the CMS as well as many other systems/devices. Everytime snmpd is restarted, we get a trap of 1.3.6.1.4.1.8072.4.6.2 (generic unregistered) followed by a "Cold Start" event.
We eventually worked out that the unregistered was snmpd sending out a shutdown trap. For whatever reason net-snmp says this should be 1.3.6.1.4.1.8072.4.0.2 yet every server bar none use 6 rather than 0 for the trap id.
To get around this we compiled the net-snmp-agent-mib adding trap id 6 then loaded it into SIM. A snmp broswer shows that 1.3.6.1.4.1.8072.4.6.2 maps to nsNotifyShutdownLocal and 1.3.6.1.4.1.8072.4.0.2 maps to nsNotifyShutdown. These are shown in the Options->Events->SNMP Trap Settings so I assume the mib loaded OK. However, when the traps come through, they get reported as generic unregistered as before.
We have checks and checked the MIB and cannot find anything wrong with it.
But the interesting thing is that the "Cold Start" is 1.3.6.1.4.1.8072.3.2.10 which is not defined in net-snmp (even though it has it's enterpise OID) and I can't find a mib where it is defined. So it looks like the CMS ignores our mib, ignore things with enterpise 8072 or processes 8072 internally.
Does anyone know what is going on here?
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