Re: Trap SNMPv3

priya thangaraj <[email protected]>
Newsgroups gmane.network.net-snmp.user
Message-ID <[email protected]>
SNMP Variables:

newMIBNotify OBJECT IDENTIFIER ::= { newMIB 3 }

netSnmpExampleHeartbeatRate OBJECT-TYPE
    SYNTAX      Integer32
    MAX-ACCESS  accessible-for-notify
    STATUS      current
    DESCRIPTION
        "A simple integer object, to act as a payload for the
         netSnmpExampleHeartbeatNotification.  The value has
         no real meaning, but is nominally the interval (in
         seconds) between successive heartbeat notifications."
::= { carlsbadNotificationObjects 1 }

netSnmpExampleHeartbeatName OBJECT-TYPE
    SYNTAX      SnmpAdminString
    MAX-ACCESS  accessible-for-notify
    STATUS      current
    DESCRIPTION
        "A simple string object, to act as an optional payload
         for the netSnmpExampleHeartbeatNotification.  This varbind
         is not part of the notification definition, so is optional
         and need not be included in the notification payload.
         The value has no real meaning, but the romantically inclined
         may take it to be the object of the sender's affection,
         and hence the cause of the heart beating faster."
::= { carlsbadNotificationObjects 2 }


DeAuthFloodTrap  NOTIFICATION-TYPE
    OBJECTS     { netSnmpExampleHeartbeatRate, netSnmpExampleHeartbeatName}
    MAX-ACCESS  accessible-for-notify
    STATUS      current
    DESCRIPTION
        "A simple integer object, to act as a payload for the
         netSnmpExampleHeartbeatNotification.  The value has
         no real meaning, but is nominally the interval (in
         seconds) between successive heartbeat notifications."
::= { newMIBNotify 1 }

So I generated the template using mib2c.notify.conf, wherein all the trap
variable and its objects are added to the variable list. I also wrote the
code of registering these handlers through snmp_alarm_register.

Compilation was successful, when the code was executed, the handlers are
registered, but the trap is not being received by snmptrapd.

Successful sending of SNMPv3 traps was followed using the below sites,
http://www.net-snmp.org/tutorial/tutorial-5/commands/snmptrap-v3.html
http://net-snmp.sourceforge.net/wiki/index.php/TUT:Configuring_snmptrapd_to_receive_SNMPv3_notifications

These same traps I could do it in SNMPv2, but I face problems with SNMPv3.
Any guidance would be greatly appreciated.


On Thu, Jul 23, 2009 at 4:46 PM, Dave Shield <[email protected]>wrote:

> 2009/7/23 priya thangaraj <[email protected]>:
> > I was successful in sending a snmptrap which was logged by snmptrapd in
> > SNMPv3.
> >
> > The current issue is that, I have developed my own TRAP-Variables,
> sending
> > it through send_trapv2() via Agentx. But the trap sent is not being
> received
> > by snmptrapd.
> >
> > is there anything that I missed?
>
> What you have missed is providing _any_ details about exactly how
> you have set things up - both for the successful "sending a snmptrap"
> and for the unsuccessful "sending ... via AgentX".
>
>
> We cannot read your mind, so it's impossible to guess what might be going
> wrong.
>
> If you want us to help you, you *must* give us something to work with!
>
> Dave
>

------------------------------------------------------------------------------

_______________________________________________
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
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.