2009/6/23 Jansen, Mario <[email protected]>:
> It does not look as an varbind. I included an screenshot of our snmp
> application CA spectrum. It shows the trap 1.3.6.1.4.1.8072.3.2.3.6.1.
If you look at the first varbind, this shows:
.1.3.6.1.6.3.1.1.4.1.0 (snmpTrapOID.0)
with a value of .1.3.6.1.2.1.88.2.0.1 (mteTriggerFired)
So this is an mteTriggerFired notification.
(which fits with your use of "defaultMonitors)
I have no idea where this wierd 8072.3.2.3.6.1 OID is coming from,
nor why your trap receiver is regarding it as the trap OID.
But the varbind listed above identifies the trap.
> I had already imported
> the net-snmp-agent-mib already but it contains a very basic trap
> definition:
>
> nsNotifyStart NOTIFICATION-TYPE
> nsNotifyShutdown NOTIFICATION-TYPE
> nsNotifyRestart NOTIFICATION-TYPE
Yes - those are the only three notification we define.
Dave
------------------------------------------------------------------------------
Are you an open source citizen? Join us for the Open Source Bridge conference!
Portland, OR, June 17-19. Two days of sessions, one day of unconference: $250.
Need another reason to go? 24-hour hacker lounge. Register today!
http://ad.doubleclick.net/clk;215844324;13503038;v?http://opensourcebridge.org
_______________________________________________
Net-snmp-users mailing list
[email protected]
Please see the following page to unsubscribe or change other options:
https://lists.sourceforge.net/lists/listinfo/net-snmp-users
