- Community Home
- >
- Networking
- >
- Switching and Routing
- >
- Aruba & ProVision-based
- >
- RMON SNMP not working on 16.02.0022m code
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
06-25-2018 01:07 PM
06-25-2018 01:07 PM
After upgrading from 15.17.0013 to 16.02.0022m the switches seem to be ignoring the RMON OID value as to how to handle a event type. Switches that we upgraded are starting to flood us with link up / down traps that were previously disabled. This particular switch is a J8698A (5412). In addition, the OIDs to monitor connected power supplies, fans, and temperature have apparently changed as well?!
Switch# getmib 1.3.6.1.2.1.16.9.1.1.3.10002
eventType.10002 = 1
Switch# getmib 1.3.6.1.2.1.16.9.1.1.3.10002
eventType.10002 = 1
10002 Link Down
10003 Link Up
eventType OBJECT-TYPE
SYNTAX INTEGER {
none(1),
log(2),
snmp-trap(3), -- send an SNMP trap
log-and-trap(4)
}
ACCESS read-write
STATUS mandatory
DESCRIPTION
"The type of notification that the probe will make
about this event. In the case of log, an entry is
made in the log table for each event. In the case of
snmp-trap, an SNMP trap is sent to one or more
management stations."
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-26-2018 06:42 AM
06-26-2018 06:42 AM
SolutionSo it probably has something to do with the front end command overriding the SNMP Set RMON OID. 'no snmp-server enable traps link-change all' accomplishes the same thing. I'll have to do some more testing if it affects all OIDS under RMON event table or just those that HP exposes with a front end CLI command.