Hi Dave,
* Thanks for your valuable feedback.*
*
*
As per your suggestion, i created* snmpd.con*f file and it looks like
following
###########################################################################
# SECTION: Access Control Setup
#
# This section defines who is allowed to talk to your running
# snmp agent.
# rwcommunity: a SNMPv1/SNMPv2c read-write access community name
# arguments: community [default|hostname|network/bits] [oid]
rwcommunity private
###########################################################################
# SECTION: Trap Destinations
#
# Here we define who the agent will send traps to.
# trapcommunity: Default trap sink community to use
# arguments: community-string
trapcommunity private
# trap2sink: A SNMPv2c trap receiver
# arguments: host [community] [portnum]
trap2sink 127.0.0.1
# authtrapenable: Should we send traps when authentication failures occur
# arguments: 1 | 2 (1 = yes, 2 = no)
authtrapenable 1
*and also i created snmptrapd.conf file* which contains only single line as
below
authCommunity log,execute,net private
I moved these two configuration files to location : /usr/local/share/snmp/
I am able to run the SNMP agent using command : sudo /usr/local/sbin/snmpd
-f -L -d -p 9999
and i started snmptrapd demon on other terminal using command : snmptrapd
-f -Le *as a root*
*
*
*When i started SNMP agent i got following coldStart(Trap) on Manager side(
i,e on other terminal) :*
2011-11-25 19:37:42 localhost [UDP: [127.0.0.1]:37800->[127.0.0.1]:162]:
DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (4) 0:00:00.04
SNMPv2-MIB::snmpTrapOID.0
= OID: SNMPv2-MIB::coldStart SNMPv2-MIB::snmpTrapEnterprise.0 = OID:
NET-SNMP-MIB::netSnmpAgentOIDs.10
*When i stopped SNMP agent i got following Shutdown(Trap) on Manager side(
i,e on other terminal) :*
2011-11-25 19:47:29 localhost [UDP: [127.0.0.1]:37800->[127.0.0.1]:162]:
DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (58699) 0:09:46.99
SNMPv2-MIB::snmpTrapOID.0
= OID: NET-SNMP-AGENT-MIB::nsNotifyShutdown SNMPv2-MIB::snmpTrapEnterprise.0
= OID: NET-SNMP-MIB::netSnmpNotificationPrefix
*and i tried for authentication failure trap by sending GET request with
invalid community string, the following authentication failure trap i got*
2011-11-25 19:49:53 localhost [UDP: [127.0.0.1]:58778->[127.0.0.1]:162]:
DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (4825) 0:00:48.25
SNMPv2-MIB::snmpTrapOID.0
= OID: SNMPv2-MIB::authenticationFailure SNMPv2-MIB::snmpTrapEnterprise.0 =
OID: NET-SNMP-MIB::netSnmpAgentOIDs.10
So finally i am quite satisfied with it...
I have gone through man pages for snmpd.conf and snmptrapd.conf and FAQ's
as you mentioned earlier.
*Now please suggest me on following things*
*
*
1) How to monitor scalar object(That i defined in MIB and able to access
using GET request) using DisMan Event MIB?
2) Can you guide me the exact flow for monitoring scalar object for sending
SNMPv2 traps using DisMan Event MIB?
*Thanks in Advance*
*Prashant Nirni*
On 25 November 2011 06:30, prashant n <[email protected]> wrote:
> Please suggest me on following things
> 1) I want to send SNMP v2 traps by the SNMP agent.
See the 'snmpd.conf(5)' man page - in particular
"trap2sink" and "informsink"
> So in the previous mail you told some thing like
> "The second pre-requisite is familiarity with SNMPv3.
> DisMan Event monitoring relies on internal "loopback" queries,
> which are implemented using SNMPv3.
>
> Have you tried using SNMPv3 yet?
> If not, then I'd suggest you give this a go first"
> I did not get this. So how to send SNMP v2 traps?
To send SNMPv2 traps - simply use the two directives above.
Try that first, and make sure the standard coldStart &
nsShutdown traps are received and processed successfully.
The DisMan Event MIB is concerned with triggering
*when* traps should be sent - not the SNMP version used.
Please make sure that the basic notification infrastructure
is in place and working before thinking about DisMan monitoring.
That's the first pre-requisite.
Do that first - make sure it's working.
Then get back to us.
Dave
------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure
contains a definitive record of customers, application performance,
security threats, fraudulent activity, and more. Splunk takes this
data and makes sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-novd2d
_______________________________________________
Net-snmp-coders mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
