Configuring Trap Notification Logs - Juniper JUNOSE SOFTWARE FOR E SERIES 11.3.X - SYSTEM BASICS CONFIGURATION GUIDE 2010-10-04 Configuration Manual

JunosE 11.3.x System Basics Configuration Guide

Configuring Trap Notification Logs

log severity
164
drainRate—Specifies the maximum number of traps per second sent to the host
full—Specifies the method for handling the queue full condition
size—Specifies the maximum number of traps kept in the queue
Example
host1(config)#snmp-server host 10.10.10.10 trapqueue drainrate 600 full droplastin
size 50
Use the no version to remove the SNMP host.
See snmp-server host.
SNMP uses the User Datagram Protocol (UDP) to send traps. Because UDP does not
guarantee delivery or provide flow control, some traps can be lost in transit to a destination
address. The Notification Log MIB provides flow control support for UDP datagrams.
You should set up your management applications to periodically request the recorded
traps to ensure that the host is up and the management applications have received all
the generated traps.
To identify the location of traps logged in the notification log, the system assigns a
consecutive index number to each SNMP trap message transmitted from the E Series
router. Clients can use the index to detect missing traps.
To configure trap notification logs:
Configure the notification log.
1.
host1(config)snmp-server notificationlog log 10.10.4.4 adminStatus includeVarbinds
(Optional) Specify when the notification log ages out.
2.
host1(config)#snmp-server notificationlog ageout 5
(Optional) Specify the maximum number of entries kept in the notification log.
3.
host1(config)#snmp-server notificationlog entrylimit 210
(Optional) Enable the snmpTrap log to severity level info.
4.
host1(config)#log severity info snmpTrap
NOTE: Enabling the snmpTrap log provides the same information in the
router log as appears in the snmp-server notification log. However, long
trap strings may appear truncated.
Copyright © 2010, Juniper Networks, Inc.