<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic How to enable DHCPD logging in ASA 5505 in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/how-to-enable-dhcpd-logging-in-asa-5505/m-p/1802299#M533679</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;DIV&gt;&lt;P&gt;Hi Wed,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I&amp;nbsp; am not sure if you we have any syslog for it, I&amp;nbsp; tried searching for it&amp;nbsp; but could not find any for it. You can check one&amp;nbsp; thing, enable logging&amp;nbsp; at debug level as well as debugs, when you see the&amp;nbsp; ip pool exhausted&amp;nbsp; debug in the syslog server, you can chcek if there&amp;nbsp; was any log as well&amp;nbsp; genarted for it, reference the timestamp. If you&amp;nbsp; find any then, you can&amp;nbsp; send only that syslog to the server by:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;logging message &lt;SYSLOG id=""&gt;&lt;/SYSLOG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope this helps you out.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Varun&lt;/P&gt;&lt;/DIV&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 12 Aug 2011 16:02:43 GMT</pubDate>
    <dc:creator>varrao</dc:creator>
    <dc:date>2011-08-12T16:02:43Z</dc:date>
    <item>
      <title>How to enable DHCPD logging in ASA 5505</title>
      <link>https://community.cisco.com/t5/network-security/how-to-enable-dhcpd-logging-in-asa-5505/m-p/1802296#M533676</link>
      <description>&lt;P&gt;Hi every one.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have configured dhcpd in an ASA 5505 and every thing is working. I am testing it to give me a warning when the address pool is about to be finished or it is empty. But don't konw how to do it. &lt;/P&gt;&lt;P&gt;If I run the "debug dhcpd packet", i get that the address pool is empty. Is ther any one there who can help me please.&lt;/P&gt;&lt;P&gt;Thanx, Wedzek&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 21:10:54 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/how-to-enable-dhcpd-logging-in-asa-5505/m-p/1802296#M533676</guid>
      <dc:creator>wedzek123</dc:creator>
      <dc:date>2019-03-11T21:10:54Z</dc:date>
    </item>
    <item>
      <title>How to enable DHCPD logging in ASA 5505</title>
      <link>https://community.cisco.com/t5/network-security/how-to-enable-dhcpd-logging-in-asa-5505/m-p/1802297#M533677</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Wed,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You can send those debugs to your syslog server as well, if that makes your job easy,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;logging debug-trace&lt;/P&gt;&lt;P&gt;logging trap debugging&lt;/P&gt;&lt;P&gt;logging host &lt;IP of="" the="" server=""&gt; &lt;INTERFACE name=""&gt;&lt;/INTERFACE&gt;&lt;/IP&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;HTH,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Varun&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 12 Aug 2011 13:09:31 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/how-to-enable-dhcpd-logging-in-asa-5505/m-p/1802297#M533677</guid>
      <dc:creator>varrao</dc:creator>
      <dc:date>2011-08-12T13:09:31Z</dc:date>
    </item>
    <item>
      <title>How to enable DHCPD logging in ASA 5505</title>
      <link>https://community.cisco.com/t5/network-security/how-to-enable-dhcpd-logging-in-asa-5505/m-p/1802298#M533678</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello Varun,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thank you very much for the reply. I tried that and it worked. The problem with that is it bombards the Syslog server with all the debug messages. In fact you get this warning ( 'logging debug-trace' is enabled. All debug messages are currently being redirected to syslog and will not appear in any monitor session). I also googled a bit in Cisco websites and it is not advisable 'coz debug wastes&amp;nbsp; lot of CPU. I am wondering if there is a better alternative! &lt;/P&gt;&lt;P&gt;Thanx again!&lt;/P&gt;&lt;P&gt;Wed&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 12 Aug 2011 13:18:00 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/how-to-enable-dhcpd-logging-in-asa-5505/m-p/1802298#M533678</guid>
      <dc:creator>wedzek123</dc:creator>
      <dc:date>2011-08-12T13:18:00Z</dc:date>
    </item>
    <item>
      <title>How to enable DHCPD logging in ASA 5505</title>
      <link>https://community.cisco.com/t5/network-security/how-to-enable-dhcpd-logging-in-asa-5505/m-p/1802299#M533679</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;DIV&gt;&lt;P&gt;Hi Wed,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I&amp;nbsp; am not sure if you we have any syslog for it, I&amp;nbsp; tried searching for it&amp;nbsp; but could not find any for it. You can check one&amp;nbsp; thing, enable logging&amp;nbsp; at debug level as well as debugs, when you see the&amp;nbsp; ip pool exhausted&amp;nbsp; debug in the syslog server, you can chcek if there&amp;nbsp; was any log as well&amp;nbsp; genarted for it, reference the timestamp. If you&amp;nbsp; find any then, you can&amp;nbsp; send only that syslog to the server by:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;logging message &lt;SYSLOG id=""&gt;&lt;/SYSLOG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope this helps you out.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Varun&lt;/P&gt;&lt;/DIV&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 12 Aug 2011 16:02:43 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/how-to-enable-dhcpd-logging-in-asa-5505/m-p/1802299#M533679</guid>
      <dc:creator>varrao</dc:creator>
      <dc:date>2011-08-12T16:02:43Z</dc:date>
    </item>
  </channel>
</rss>

