Strange traps

[Domenico Viggiani]

Hi,
I'm receiving a lot of traps like these from a Procurve 2824 switch:

(enterprise:.1.3.6.1.4.1.11.2.3.7.11.31 generic:6 specific:2). 1 args: .1.3.6.1.2.1.16.9.1.1.2.77="I 06/01/07 09:17:35 ports: port 24 is now off-line"

(enterprise:.1.3.6.1.4.1.11.2.3.7.11.31 generic:6 specific:2). 1 args: .1.3.6.1.2.1.16.9.1.1.2.413="I 01/16/07 04:14:02 SNTP: updated time by 4 seconds"

(enterprise:.1.3.6.1.4.1.11.2.3.7.11.31 generic:6 specific:2). 1 args: .1.3.6.1.2.1.16.9.1.1.2.179="I 01/26/07 13:55:56 mgr: SME TELNET from 193.227.66.207 - OPERATOR Mode"

They are all the same (enterprise:.1.3.6.1.4.1.11.2.3.7.11.31 generic:6 specific:2), only args changes.

Are they RMON related?
Is there a way to receive 'normal' traps?

Thanks

[Ben Dehner]

My guess is that these are "normal" traps. The problem is probably with whatever network manager software is being used to receive the traps; it needs to have the proper MIBs loaded to interpret the traps correctly.

[daniel wright_1]

use 'critical' on the trap entry, this will give you thinks like excessive broadcasts crc errors etc, although it does still give you the port online, port offline messages but you should be able to filter these out.

[Domenico Viggiani]

I understand but why are all these traps almost the same, except for args?
Usually, traps are different for the first part or am I wrong?

Thanks

[Matt Hobbs]

This is just the way ProCurve do traps. There is no way to change this. It's not incorrect, it's just how it was chosen to be done.

[Domenico Viggiani]

Strange... there is something of strange.
People of OpenNMS don't understand my problems...