Configuring Trap Notification Logs

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:

1. Configure the notification log.

   host1(config)snmp-server notificationlog log 10.10.4.4 adminStatus includeVarbinds

2. (Optional) Specify when the notification log ages out.

   host1(config)#snmp-server notificationlog ageout 5

3. (Optional) Specify the maximum number of entries kept in the notification log.

   host1(config)#snmp-server notificationlog entrylimit 210

4. (Optional) Enable the snmpTrap log to severity level info.

   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.

log severity

• Use to set the severity level for a selected category or for systemwide logs.

  Note: For more information about this command, see the JUNOSe System Event Logging Reference Guide.

• Example

  host1(config)#log severity info snmptrap

• Use the no version to return to the default severity value (error) for the selected category. To return all logs to their default severity setting, include an * (asterisk) with the no version.
• See log severity.

snmp-server notificationLog ageOut

• Use to set the ageout for traps in the notification log tables. The range is 0–214748364 minutes.
• Example

  host1(config)#snmp-server notificationLog ageout 5

• Use the no version to return the ageout limit to the default value, 1440 minutes.
• See snmp-server notificationLog ageOut.

snmp-server notificationLog entryLimit

• Use to set the maximum number of notifications kept in all notification log tables.
• The range is 1–500, which means that you can allocate up to 500 notifications across all virtual routers on the router. As you allocate the entry limits for virtual routers, the available range changes to reflect the number of notifications that you have allocated.
• Example

  host1(config)#snmp-server notificationLog entrylimit 210

• Use the no version to return the limit to the default value, 500.
• See snmp-server notificationLog entryLimit.

snmp-server notificationLog log

• Use to configure SNMP notification log tables.
• Use the adminStatus keyword to enable administrative status.
• Use the includeVarbinds keyword to include log names and log indexes in the trap’s variable bindings.
• Example

  host1(config)snmp-server notificationLog log 10.10.4.4 adminStatus includeVarbinds

• Use the no version to remove the notification log configuration.
• See snmp-server notificationLog log.

Copyright © 2008, Juniper Networks, Inc. All rights reserved. Trademark Notice.