Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Guide That Contains This Content
[+] Expand All
[-] Collapse All

    Configuring the SNMP 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. You can use the adminStatus keyword to enable administrative status. You can use the includeVarbinds keyword to include log names and log indexes in the trap’s variable bindings.
      host1(config)snmp-server notificationlog log adminStatus includeVarbinds
    2. (Optional) Specify when the notification log ages out. The value range is 0 through 214,748,364 minutes.
      host1(config)#snmp-server notificationlog ageout 5
    3. (Optional) Specify the maximum number of entries kept in the notification log. The value range is 1 through 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.
      host1(config)#snmp-server notificationlog entrylimit 210
    4. (Optional) Enable the snmpTrap log to severity level info.


      • 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.
      • For more information about the log severity command, see the JunosE System Event Logging Reference Guide.
      host1(config)#log severity info snmpTrap

    Published: 2014-08-12