Clearing An Ip Dhcp Local Server Binding; Using Snmp Traps To Monitor Dhcp Local Server Events; Using Dhcp Local Server Event Logs - Juniper JUNOSE SOFTWARE FOR E SERIES 11.3.X - BROADBAND ACCESS CONFIGURATION GUIDE 2010-10-12 Configuration Manual

JunosE 11.3.x Broadband Access Configuration Guide

Clearing an IP DHCP Local Server Binding

Using SNMP Traps to Monitor DHCP Local Server Events

Using DHCP Local Server Event Logs

478
NOTE: This command is deprecated and might be removed completely in a
future release. The function provided by this command has been replaced
by the dhcp delete-binding command.
You can use the clear ip dhcp-local binding command to force the removal of a connected
user's IP address lease and associated route configuration. Using this command enables
you to:
Recover functional resources from a user who has not explicitly terminated connectivity
and whose lease is unexpired.
Discontinue connectivity to a user, prompting or forcing the user to request a new lease
in order to reestablish network connectivity.
The DHCP local server supports configurable global SNMP traps that monitor events
related to the DHCP local server and local SNMP traps that are related to address pool
utilization.You use the ip dhcp-local snmpTraps command to enable the global SNMP
traps for DHCP local server.
The DHCP local server's global SNMP trap generates severity level 1 (alert), 2 (critical),
and 3 (error) events. This trap helps administrators monitor DHCP local server general
health, error statistics, address lease status, and protocol events. The global SNMP trap
generates a severity level 4 (warning) event when a duplicate MAC address is detected.
The global SNMP trap information is captured in the dhcpLocalGeneral logging category.
SNMP also traps events related to address pool utilization. You use the warning command
to define the maximum and minimum threshold values and the snmpTrap command to
generate traps when utilization occurs above or below the defined values.
For linked or shared pools, SNMP treats the members of the pool as a group, and uses
the values configured for the first pool in the chain as the group's threshold.
The address pool utilization SNMP trap information is captured in the dhcpLocalPool
logging category.
NOTE: You must configure your SNMP management client to read the MIB
objects, and your SNMP trap collector must be capable of decoding the new
traps. For information about setting up SNMP, see the Configuring SNMP
chapter in JunosE System Basics Configuration Guide.
To troubleshoot and monitor your DHCP local server, use the following system event
logs:
Copyright © 2010, Juniper Networks, Inc.