Sponsored Content
Top Forums UNIX for Advanced & Expert Users Configuring snmpd.conf and snmptrapd.conf Post 302133002 by jagdish.machhi@ on Tuesday 21st of August 2007 11:33:05 AM
Old 08-21-2007
Configuring snmpd.conf and snmptrapd.conf

HI,

I want a help for Configuring snmpd.conf and snmptrapd.conf (i.e Configuring SNMP)

for receiving

TRAPS in my networks. I am using RHEL4.0 OS.

Please tell me How I can configure above two files in a proper way and at an

advanced level.

Especially I am getting stuck on configuring "snmptrapd.conf" file for

getting OID's from the Remote machine when I am giving following command

#snmptrap -v2c -c public <dest. IP> 256 <trap-oid> <object-oid> <type> value

Please help me ?

Regards
JAGDISH
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

snmptrapd.conf

Hi All Can anybody tell me how to configure snmptrapd.conf ? Thanx (0 Replies)
Discussion started by: jeenat
0 Replies

2. UNIX for Dummies Questions & Answers

Configuring syslog.conf in a TRU64 UNIX machine

Dear all I want to redirect the logs of the syslog of a tru64 unix machine in a log and event monitoring tool installed in another server. In the syslog.conf i have appended *.*@<server_name> at the end, where <server_name> is the name of the machine on which the reporting tool is running. I... (0 Replies)
Discussion started by: adak2010
0 Replies

3. UNIX for Dummies Questions & Answers

snmptrapd.conf

i tried this to get snmptrapd.conf bt unable... # snmpconf The following installed configuration files were found: 1: /etc/snmp/snmp.conf 2: /etc/snmp/snmpd.conf 3: /usr/share/snmp/snmp.conf 4: /usr/share/snmp/snmpd.conf Would you like me to read them in? Their... (0 Replies)
Discussion started by: jeenat
0 Replies

4. Red Hat

SD.conf and LPFC.conf

What would be Redhat RHEL 4.0 equivalent for Solaris sd.conf and lpfc.conf? What are the files called and where are the files located? (1 Reply)
Discussion started by: soupbone38
1 Replies

5. Solaris

basic question on sd.conf and lpc.conf file

Hello Guys, Do we need to configure this file only if we add SAN disk or even if we add local disk, do we need to modify? (4 Replies)
Discussion started by: mokkan
4 Replies

6. Infrastructure Monitoring

Proper permission /etc/snmp/snmpd.conf

Hi All, I'm hardening my linux. And I came across with this file. /etc/snmp/snmpd.conf It's current mod is 644 with root:root ownership and group. Can I make this 640 without hurting the OS? Meaning no public read access. Does other resources need to read to it? Thanks and more... (1 Reply)
Discussion started by: itik
1 Replies

7. UNIX for Advanced & Expert Users

logOption warning in snmptrapd.conf

Hi, trying to get snmp traps logged in /var/log/messages. I put this option in snmptrapd.conf: logOption Ls d then restarting the snmptrad daemon I got this warning: Unknown token: logoption. and server is not logging traps. Starting snmptrapd manually works, traps are logged.... (0 Replies)
Discussion started by: neutrino
0 Replies

8. Red Hat

Configuring syslog.conf

Hi, I would like to configure syslog linux client, syslog server is windows server. so adding on linux client in /etc/syslog.conf @hostname will work in the place of directory location. example of /etc/syslog.conf # Log all kernel messages to the console. # Logging much else clutters up... (2 Replies)
Discussion started by: manoj.solaris
2 Replies

9. Shell Programming and Scripting

Script to update rsyslog.conf and auditd.conf

Hello all, Newbie here. I'm currently tasked with updating rsyslog.conf and auditd.conf on a large set of servers. I know the exact logging configurations that I want to enable. I have updated both files on on a server and hope to use the updated files as a template for the rest of the... (3 Replies)
Discussion started by: Mide
3 Replies

10. Solaris

Configure resolv.conf and nsswitch.conf

Hi, I've installed Solaris 11.3(live media) and configured DNS. Everytime I reboot the server, resolv.conf got deleted and it created a new nsswitch.conf. I used below to configure both settings: # svccfg -s dns/client svc:/network/dns/client> setprop config/nameserver = (xx.xx.xx.aa... (1 Reply)
Discussion started by: flexihopper18
1 Replies
TrapReceiver(3) 					User Contributed Perl Documentation					   TrapReceiver(3)

NAME
NetSNMP::TrapReceiver - Embedded perl trap handling for Net-SNMP's snmptrapd SYNOPSIS
Put the following lines in your snmptrapd.conf file: perl NetSNMP::TrapReceiver::register("trapOID", &myfunc); ABSTRACT
The NetSNMP::TrapReceiver module is used to register perl subroutines into the Net-SNMP snmptrapd process. Net-SNMP MUST have been configured using --enable-embedded-perl. Registration of functions is then done through the snmptrapd.conf configuration file. This module can NOT be used in a normal perl script to receive traps. It is intended solely for embedded use within the snmptrapd demon. DESCRIPTION
Within the snmptrapd.conf file, the keyword "perl" may be used to call any perl expression and using this ability, you can use the NetSNMP::TrapReceiver module to register functions which will be called every time a given notification (a trap or an inform) is received. Registered functions are called with 2 arguments. The first is a reference to a hash containing information about how the trap was received (what version of the SNMP protocol was used, where it came from, what SNMP user name or community name it was sent under, etc). The second argument is a reference to an array containing the variable bindings (OID and value information) that define the noification itself. Each variable is itself a reference to an array containing three values: a NetSNMP::OID object, the value that came associated with it, and the value's numeric type (see NetSNMP::ASN for further details on SNMP typing information). Registered functions should return one of the following values: NETSNMPTRAPD_HANDLER_OK Handling the trap succeeded, but lets the snmptrapd demon check for further appropriate handlers. NETSNMPTRAPD_HANDLER_FAIL Handling the trap failed, but lets the snmptrapd demon check for further appropriate handlers. NETSNMPTRAPD_HANDLER_BREAK Stops evaluating the list of handlers for this specific trap, but lets the snmptrapd demon apply global handlers. NETSNMPTRAPD_HANDLER_FINISH Stops searching for further appropriate handlers. If a handler function does not return anything appropriate or even nothing at all, a return value of NETSNMPTRAPD_HANDLER_OK is assumed. Subroutines are registered using the NetSNMP::TrapReceiver::register function, which takes two arguments. The first is a string describing the notification you want to register for (such as "linkUp" or "MyMIB::MyTrap" or ".1.3.6.1.4.1.2021...."). Two special keywords can be used in place of an OID: "default" and "all". The "default" keyword indicates you want your handler to be called in the case where no other handlers are called. The "all" keyword indicates that the handler should ALWAYS be called for every notification. EXAMPLE
As an example, put the following code into a file (say "/usr/local/share/snmp/mytrapd.pl"): #!/usr/bin/perl sub my_receiver { print "********** PERL RECEIVED A NOTIFICATION: "; # print the PDU info (a hash reference) print "PDU INFO: "; foreach my $k(keys(%{$_[0]})) { if ($k eq "securityEngineID" || $k eq "contextEngineID") { printf " %-30s 0x%s ", $k, unpack('h*', $_[0]{$k}); } else { printf " %-30s %s ", $k, $_[0]{$k}; } } # print the variable bindings: print "VARBINDS: "; foreach my $x (@{$_[1]}) { printf " %-30s type=%-2d value=%s ", $x->[0], $x->[2], $x->[1]; } } NetSNMP::TrapReceiver::register("all", &my_receiver) || warn "failed to register our perl trap handler "; print STDERR "Loaded the example perl snmptrapd handler "; Then, put the following line in your snmprapd.conf file: perl do "/usr/local/share/snmp/mytrapd.pl"; Start snmptrapd (as root, and the following other opions make it stay in the foreground and log to stderr): snmptrapd -f -Le You should see it start up and display the final message from the end of the above perl script: Loaded the perl snmptrapd handler 2004-02-11 10:08:45 NET-SNMP version 5.2 Started. Then, if you send yourself a fake trap using the following example command: snmptrap -v 2c -c mycommunity localhost 0 linkUp ifIndex.1 i 1 ifAdminStatus.1 i up ifOperStatus.1 i up ifDescr s eth0 You should see the following output appear from snmptrapd as your perl code gets executed: ********** PERL RECEIVED A NOTIFICATION: PDU INFO: notificationtype TRAP receivedfrom 127.0.0.1 version 1 errorstatus 0 messageid 0 community mycommunity transactionid 2 errorindex 0 requestid 765160220 VARBINDS: sysUpTimeInstance type=67 value=0:0:00:00.00 snmpTrapOID.0 type=6 value=linkUp ifIndex.1 type=2 value=1 ifAdminStatus.1 type=2 value=1 ifOperStatus.1 type=2 value=1 ifDescr type=4 value="eth0" EXPORT
None by default. # =head2 Exportable constants # NETSNMPTRAPD_AUTH_HANDLER # NETSNMPTRAPD_HANDLER_BREAK # NETSNMPTRAPD_HANDLER_FAIL # NETSNMPTRAPD_HANDLER_FINISH # NETSNMPTRAPD_HANDLER_OK # NETSNMPTRAPD_POST_HANDLER # NETSNMPTRAPD_PRE_HANDLER SEE ALSO
NetSNMP::OID, NetSNMP::ASN snmptrapd.conf(5) for configuring the Net-SNMP trap receiver. snmpd.conf(5) for configuring the Net-SNMP snmp agent for sending traps. http://www.Net-SNMP.org/ AUTHOR
W. Hardaker, <hardaker@users.sourceforge.net> COPYRIGHT AND LICENSE
Copyright 2004 by W. Hardaker This library is free software; you can redistribute it and/or modify it under the same terms as Perl itself. perl v5.16.3 2012-10-09 TrapReceiver(3)
All times are GMT -4. The time now is 01:57 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy