Recovering Lost Traps - Juniper SYSTEM BASICS - CONFIGURATION GUIDE V 11.1.X Configuration Manual

JUNOSe 11.1.x System Basics Configuration Guide
snmp-server notificationLog ageOut
snmp-server notificationLog entryLimit
snmp-server notificationLog log

Recovering Lost Traps

SNMP traps can be lost during startup of the E Series router for one of the following
reasons:
176
Configuring Traps
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.
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.
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.
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.