snmpd.trap(4snmp)
snmpd.trap --
SNMP trap communities file
Synopsis
/etc/netmgt/snmpd.trap
Description
The snmpd.trap file contains the definitions for the hosts which
will be sent a TRAP PDU by the SNMP
agent/server daemon,
snmpd(1Msnmp).
When a trap occurs, the SNMP agent sends a packet containing the
trap information to each of the host addresses listed in this file.
The snmpd.trap file contains lines which consist of four items:
- ``protocol''
-
a protocol name (either ``ip'' or ``ipx'')
- ``community_string''
-
a session or community string that can be used by the system receiving
the trap to filter out trap messages that it wants to monitor (in this
case, the community string is not used for authentication purposes)
- ``address''
-
an IP address in dot notation or an IPX
address
depending on the protocol used:
-
IP notation is in decimal
-
IPX notation is 4 bytes of network address followed by a colon
(:), then 6 bytes of node address, all in hexadecimal
- ``socket/port''
-
the port number for IP must be in decimal; according to
RFC 1157, the port number for IP should always be 162;
the socket number for IPX must be in hexadecimal; according to
RFC 1420, the socket number for IPX should always
be 9010
Lines which begin with a hash sign (#) are ignored.
Currently, two TRAP PDUs are generated by
snmpd. They are the coldStart and
authenticationFailure trap types. The coldStart trap
is generated when snmpd is started. The
authenticationFailure trap is generated when an authentication
error occurs.
Warnings
The IP address 0.0.0.0 and the IPX address
00000000:000000000000 are used as wildcards, meaning that the trap packet
is broadcast over the indicated transport.
Examples
The following is a sample snmpd.trap file:
ip test1 192.9.200.99 162
ip test1 192.9.200.15 162
ip test2 123.45.67.89 162
ip public 0.0.0.0 162
ipx public 00000000:000000000000 9010
As noted in the ``Description'', the community strings shown are used by
the network management software receiving trap packets as a means of
filtering out specific traps. For example, a particular network management
station might be interested only in traps sent with the test1 or test2
community strings, and might ignore all of the traps sent with the public
community string.
References
snmpd(1Msnmp)
RFC 1155, RFC 1157, RFC 1213, RFC 1420
30 January 1998
© 1998 The Santa Cruz Operation, Inc. All rights reserved.