Making debugging persistent (DHCP)

Unanswered Question
Jul 10th, 2007

By running "debug ip dhcp server events" at enable mode - the DHCPD binding information was able to be sent to the syslog server. That's exactly when I wanted to have happen. But the problem is that if the DHCP router reboots I would need to execute that same debugging line else lose my DHCP assignment/binding logging. Is there any way to make such debugging persistent (still in effect even after reboot?) Or is there another means of having a DHCP enabled router send bindings out via syslog?

Jul 10 16:26:37 10.1.6.5 36: 35w3d: DHCPD: assigned IP address 10.1.6.253 to

client 0100.1128.aff4.77.

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (2 ratings)
Loading.
Paolo Bevilacqua Tue, 07/10/2007 - 16:04

Hi,

I think what you want can be done with "database agent":

ip dhcp database url [timeout seconds | write-delay seconds]

This way you will have always your bindings in a text file into an host.

If that's not enough, you can use Radius accounting for all DHCP transactions:

http://www.cisco.com/en/US/products/ps6441/products_configuration_guide_chapter09186a008071c33f.html

I don't think there is an easy way to enable debug commands automatically at boot.

Hope this helps, please rate post if it does!

Actions

This Discussion