SNMP Traps

The router generates SNMP traps and system log messages as follows:

• If the first RADIUS server fails to respond to the RADIUS request, the E-series RADIUS client issues a system log message and, if configured, an SNMP trap indicating that the RADIUS server timed out. The E-series RADIUS client will not issue another system log message or SNMP trap regarding this RADIUS server until the deadtime expires, if configured, or for 3 minutes if deadtime is not configured.
• The E-series RADIUS client then sends the RADIUS request to the second configured RADIUS server. If the second RADIUS server fails to respond to the RADIUS request, the E-series RADIUS client again issues a system log message and, if configured, an SNMP trap indicating that the RADIUS server timed out.
• This process continues until either the E-series RADIUS client receives a valid response from a RADIUS server or the list of configured RADIUS servers is exhausted. If the list of RADIUS servers is exhausted, the E-series RADIUS client issues a system log message and, if configured, an SNMP trap indicating that all RADIUS servers have timed out.

If the E-series RADIUS client receives a RADIUS response from a “dead” RADIUS server during the deadtime period, the RADIUS server is restored to active status.

If the router receives a valid RADIUS response to an outstanding RADIUS request, the E-series client issues a system log message and, if configured, an SNMP trap indicating that the RADIUS server is now available.

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