ProCurve / ProVision-Based
cancel
Showing results for 
Search instead for 
Did you mean: 

RMON SNMP not working on 16.02.0022m code

SOLVED
Go to solution
OidNinja
Occasional Contributor

RMON SNMP not working on 16.02.0022m code

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."

1 REPLY
OidNinja
Occasional Contributor
Solution

Re: RMON SNMP not working on 16.02.0022m code

So 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.