Sponsored Content
Full Discussion: SNMP Traps
Special Forums UNIX and Linux Applications Infrastructure Monitoring SNMP Traps Post 302365882 by pupp on Wednesday 28th of October 2009 09:19:17 AM
Old 10-28-2009
you need several of the sun (depending on the hardware as well) mib files. these files will have sections for NOTIFICATIONS and TRAPS. in a NMS like opennms, these need to be parsed out into a xml file for opennms to be able to translate traps coming into the event bus. not sure how cacti works but it follows the same logic.
 

10 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

Sending SNMP Traps in AIX / Unix

Hi, Just wondering if anyone knows how can I send an SNMP Trap in Unix Environment(AIX) to another machine (NT/Ux) after having activated the SNMP in the AIX. Can this be done by using a single command line or do I have to write a script for it? Thanks in advance for your advices. :) (1 Reply)
Discussion started by: goliath
1 Replies

2. Solaris

SNMP traps

Hello I am trying to check that SNMP traps could be sent from one server to other . I am running this command from receiving server to see it can receive it /usr/sbin/snoop udp port 162 and on the sending end I am running this commad cst051 UDP D=162 S=1480 LEN=120 but i am... (1 Reply)
Discussion started by: Ajwat
1 Replies

3. Linux

How to configure linux to receive snmp traps from a windows server?

Can anybody please tell me how to configure linux to receive snmp traps from a windows server? I am not able to receieve snmp traps on unix machines specifically linux and solaris. I have tried starting snmptrapd service on linux but it didn't work. Is there anything special that I have to do on... (2 Replies)
Discussion started by: iamtulipin
2 Replies

4. Solaris

List of SNMP Traps supported by Solaris 10

Hi, I want the list of SNMP traps supported by Solaris 10. DO anyone has the list prepared. Regards, Rajesh (1 Reply)
Discussion started by: grrajeish
1 Replies

5. Infrastructure Monitoring

Shell Script - Generate SNMP Traps

Good morning to you all I´m kinda of a noob to scripting, and my knowledge is still very basic: anyway, I´ve developed a small .sh script with the following purpose: - it will check a result file, checking if it has any values, or if it´s empty - if it´s empty it will send an email What... (0 Replies)
Discussion started by: zarahel
0 Replies

6. Red Hat

Sending data from DELL OMSA SNMP and Custom SNMP MIB to same UDP port 161

Hi , Currently DELL OMSA SNMP sends data through default udp port 161.I want my custom SNMP MIB also to send data in the same udp port 161.Whether its possible.If yes where to configure .I tried starting my custom MIB in udp port 161,but it throws port already in use.Kindly guide. (1 Reply)
Discussion started by: prabakar4all
1 Replies

7. UNIX for Dummies Questions & Answers

Creating a virtual Interface to recieve snmp traps

All, I have a question regarding setting up a virtual interface to recieve snmp traps from network devices. My Solaris 10 server is running the HPOV-NNMi application. The network devices in our environment (many thousands) are all pre-configured to send their snmp traps to a specific IP... (4 Replies)
Discussion started by: turk22
4 Replies

8. UNIX for Dummies Questions & Answers

SNMP Traps

Hi, We are using Zyrion Traverse to monitor all the servers. I like to set the traps on all of the Linux servers to send the traps to that servers. So for on the /etc/snmp/snmp.conf file, this is what I have... ### SNMP Traps ### trap2sink x.x.x.x # Traverse server My... (4 Replies)
Discussion started by: samnyc
4 Replies

9. Infrastructure Monitoring

SNMP traps to SNMP server

Dear Champs, I am new to unix, and need to configure linux server to send below traps to a SNMP server. Monitoring TRAP Disk Space Low Monitoring TRAP Memory Low Monitoring TRAP CPU high Monitoring TRAP Admin login/Logoff Please help me how to send this information to my SNMP server... (2 Replies)
Discussion started by: stavar
2 Replies

10. UNIX for Dummies Questions & Answers

Need to transfer all kernel logs (var/log/messages) to the snmp listener as snmp trap

i am working with embedded system -Dell DCS management sub system. my question is as below: currently we are using linux kernel 2.6.30 build and we have a kernel logs stored to the /var/log/messages path. now we have to transfer all this logs to the specified SNMP target as a part of SNMP... (4 Replies)
Discussion started by: vipul_prajapati
4 Replies
snmpd.conf(5n)															    snmpd.conf(5n)

Name
       snmpd.conf - Simple Network Management Protocol (SNMP) daemon configuration file

Description
       The file is a configuration file that contains information used by the daemon to define the static variables whose values are not available
       in the kernel.  It is created for you when you run the command, or you can create it manually.  The system or network  manager  is  usually
       responsible for maintaining it.

       The following are the file variables and their significance:

       sysDescr ID-string
	    The variable describes the host.  The ID-string is the value of the variable The default entry is of the form:

	    hostname:machine-type:software id

	    For example, the entry for a MicroVAX II named that is running ULTRIX Version 4.0 might read:
	    sysDescr  host1:MicroVAXII:ULTRIX V4.0 (Rev 64) System #2

       interface speed name speed
	    The variable describes a value for the Management Information Base (MIB) variable defined as:

	    The  name  parameter must be an ULTRIX interface name, such as sl0.  The following interfaces have default interface speeds and types:
	    de, qe, ni, ln, se, scs, xna.  If your system has one of these interfaces, you do not need to specify this parameter.

	    The speed parameter is a decimal number that describes the speed of the link in bits per second.  If you  do  not  specify	the  speed
	    parameter, does not return this variable and marks it as unavailable.

       interface type name type
	    The variable describes a value for the MIB variable in the interface table defined as:

	    The name parameter must be an ULTRIX interface name, such as sl0.

	    See  the sample file in the Examples section for a complete listing of the possible type specifications.  If the type parameter is not
	    specified, marks it as unavailable.

       tcpRtoAlgorithm algorithm-type
	    The variable describes a value for the MIB variable in the tcp group defined as This  variable  defines  the  Retransmission  Time-Out
	    (RTO) algorithm your system uses.

	    The  algorithm-type parameter is a numeric code that represents the type of RTO algorithm you are using.  The default algorithm is Van
	    Jacobson's, which is algorithm number 4.  See the sample file in the Examples section for a listing of the other algorithms.

	    If you do not specify this parameter, does not return this variable, and marks it as unavailable.

       community name IP-address type
	    The variable describes an SNMP community for the agent.

	    The name parameter is a string that describes the name of the community.

	    The IP-address parameter is the dot-notation Internet Protocol (IP) address for the  server.   Only  SNMP  packets	coming	from  that
	    address are accepted.  If you specify 0.0.0.0 in the address field, the SNMP agent honors the request from any Network Management Sta-
	    tion (NMS) having the name community.

	    The type parameter can be one of the following:

	    read-only
	    Permits only monitoring of variables.

	    read-write
	    Permits both monitoring and setting of variables.

	    traps
	    Generates traps when appropriate and sends them to the specified address with the specified community name.

	    The possible traps currently generated are cold start and authentication failure.

	    If you do not specify any community, uses the default community with an address 0.0.0.0 and a read-only type.  Invalid uses of  commu-
	    nities  are  logged with the command.  To limit the use of a community to a finite group of machines, specify another community clause
	    with the same community parameter name and a different address.

       timeout value
	    The variable indicates the timeout value in seconds between the Agent and the Extended  Agent.   If  the  Agent  does  not	receive  a
	    response within the allotted time, it returns an error message to the NMS.	The default timeout value is 5 seconds.

       extension extended-agent p1 p2 p3 p4
	    The variable lists the pathname of the extended-agent that the Agent activates.

	    Variables  p1  through  p4	are  passed by the Agent to the Extended Agent; p1 is usually the process name to be given to the Extended
	    Agent.

Examples
       The default file contains only the following entry:
       community public 0.0.0.0    read-only
       The following is an example of an extensive file:
       #
       #    snmpd.conf file
       #
       sysDescr        host1:MicroVAXII:ULTRIX V4.0 System #2

       #
       #  Describe the TCP RTO algorithm you are using.  Values
       #  are listed in RFC 1066, under the TCP group variable:
       #  tcpRtoAlgorithm
       #  They are:
       #
       #  other(1)	-- None of the below
       #  constant(2)	-- constant RTO
       #  rsre(3)	-- MILSTD 1778, appendix B
       #  vanj(4)	-- Van Jacobson's algorithm
       #
       tcprtoalgorithm	   4

       #
       #  Describe who can use your SNMP daemon by
       #  defining "communities".    USAGE:
       #
       #  community <name><IP address><type>
       #
       #  This is a limited-use community; a finite number of
       #  hosts can use it.
       #  Can only query from this community.
       #
       community test1	   128.45.10.100 read-only
       community test1	   128.45.10.101 read-only

       #
       #  These are our wide-open, general-use communities.  Specifying
       #  0.0.0.0 means that any address can use this community only
       #  to monitor variables.
       #
       community public 0.0.0.0 read-only

       #
       #  This is our only management community.  You can set variables
       #  as well as monitor variables with this community.  It is a
       #  wide-open community as well.
       #
       community testwrite 0.0.0.0 read-write

       #
       #  This is a trap community.  We send traps to these addresses
       #  all from the same community name.  Note that a 0.0.0.0
       #  address in a trap session is illegal and snmpd will ignore
       #  that community definition.
       #
       community trap1	   128.45.10.100 traps
       community trap1	   128.45.10.101 traps

       #
       #  The interface speed is given in bits/sec.  USAGE:
       #
       #  interface speed <name> <speed>
       #
       interface speed sl0 9600

       #
       #  The <name> parameter for the interface type is the
       #  same as the <name> for the interface speed, sl0 for
       #  this example.  USAGE:
       #
       #  interface type <name> <type>
       #
       #  The code number for the proper interface hardware type
       #  is specified in RFC 1066 under the ifType object
       #  definition.
       #
       #  Some possible values:
       #
       #  other(1)
       #  regular1822(2)
       #  hdh1822(3)
       #  ddn-x25(4)
       #  rfc877-x25(5)
       #  ethernet-csmacd(6)
       #  iso88023-csmacd(7)
       #  iso88024-tokenBus(8)
       #  iso88025-tokenRing(9)
       #  iso88026-man(10)
       #  starLan(11)
       #  Proteon-10MBit(12)
       #  Proteon-80MBit(13)
       #  hyperchannel(14)
       #  fddi(15)
       #  lapb(16)
       #  sdlc(17)
       #  t1-carrier(18)
       #  cept(19) -- European equivalent of T-1
       #  basicIsdn(20)
       #  primaryIsdn(21)
       #  propPointToPointSerial(22) -- proprietary serial
       #
       interface type  sl0 1

       #
       # Timer value to time out requests to extended agents.
       #
       timeout	 6

       #
       # List of extended agents.
       #
       extension /etc/snmpextd	     snmpextd

       In this example, note the following:

       o  Community can be monitored by either 128.45.10.100 or 128.45.10.101.

       o  Community can be monitored by any NMS.

       o  Community can be monitored and managed by any NMS.

       o  When a trap is generated, it is sent to community at 128.45.10.100 or 128.45.10.101.	Destination addresses must  have  a  mechanism	in
       place to handle the traps.

See Also
       snmpext(3n), snmpd(8n), snmpsetup(8n)
       RFC 1066--Management Information Base for Network Management of TCP/IP- based Internets
       RFC 1067--A Simple Network Management Protocol
       Guide to Networking

																    snmpd.conf(5n)
All times are GMT -4. The time now is 07:02 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy