<?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 PIX debug problem in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/pix-debug-problem/m-p/22447#M696645</link>
    <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I has three different debugs installed on the PIX 515, e.g. debug crypto ipsec 4, debug crypto isakmp 4 and a IP packet debug on the inside interface. Afte about 15 min crashes the PIX with the follow message&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;                                                                                         &lt;/P&gt;&lt;P&gt;Watchdog timeout failure! Please contact customer support.                               &lt;/P&gt;&lt;P&gt;                                                                                         &lt;/P&gt;&lt;P&gt;                                                                                         &lt;/P&gt;&lt;P&gt;    PC       SP       STATE       Runtime    SBASE     Stack Process                     &lt;/P&gt;&lt;P&gt;Lrd 80078bd6 80a5d7a8 8046a470         40 80a5c7e8 3712/4096 arp_timer                   &lt;/P&gt;&lt;P&gt;Lsi 8007c157 80ac08bc 80469fc8         40 80abf900 3872/4096 FragDBGC                    &lt;/P&gt;&lt;P&gt;Lwe 8000be20 80ac8850 8046d6e8     775010 80ac7990 3616/4096 dbgtrace                    &lt;/P&gt;&lt;P&gt;Lwe 8015cb5a 80aca9cc 804476c8       3480 80ac8a20 6624/8192 Logger                      &lt;/P&gt;&lt;P&gt;Hwe 8015feeb 80bb1a78 80447978          0 80bafab8 8092/8192 tcp_fast                    &lt;/P&gt;&lt;P&gt;Hwe 8015fe72 80bb3b04 80447978          0 80bb1b48 8088/8192 tcp_slow                    &lt;/P&gt;&lt;P&gt;Lsi 800c7e3a 80c29cb8 80469fc8          0 80c28cf8 4008/4096 xlate clean                 &lt;/P&gt;&lt;P&gt;Lsi 800c7d60 80c2ad44 80469fc8          0 80c29d88 3672/4096 uxlate clean                &lt;/P&gt;&lt;P&gt;Mrd 800c5561 80d7b030 80469ff0          0 80d79078 8004/8192 tcp_intercept_timer_process &lt;/P&gt;&lt;P&gt;Lsi 8019a4aa 80e206d0 80469fc8         10 80e1f710 3956/4096 route_process               &lt;/P&gt;&lt;P&gt;Hsi 800b80e1 80e2175c 80469fc8       5740 80e207a0 2880/4096 Hosts conn cleaner          &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Someone knows the problem with the debugs!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;</description>
    <pubDate>Fri, 21 Feb 2020 05:59:20 GMT</pubDate>
    <dc:creator>imeissner</dc:creator>
    <dc:date>2020-02-21T05:59:20Z</dc:date>
    <item>
      <title>PIX debug problem</title>
      <link>https://community.cisco.com/t5/network-security/pix-debug-problem/m-p/22447#M696645</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I has three different debugs installed on the PIX 515, e.g. debug crypto ipsec 4, debug crypto isakmp 4 and a IP packet debug on the inside interface. Afte about 15 min crashes the PIX with the follow message&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;                                                                                         &lt;/P&gt;&lt;P&gt;Watchdog timeout failure! Please contact customer support.                               &lt;/P&gt;&lt;P&gt;                                                                                         &lt;/P&gt;&lt;P&gt;                                                                                         &lt;/P&gt;&lt;P&gt;    PC       SP       STATE       Runtime    SBASE     Stack Process                     &lt;/P&gt;&lt;P&gt;Lrd 80078bd6 80a5d7a8 8046a470         40 80a5c7e8 3712/4096 arp_timer                   &lt;/P&gt;&lt;P&gt;Lsi 8007c157 80ac08bc 80469fc8         40 80abf900 3872/4096 FragDBGC                    &lt;/P&gt;&lt;P&gt;Lwe 8000be20 80ac8850 8046d6e8     775010 80ac7990 3616/4096 dbgtrace                    &lt;/P&gt;&lt;P&gt;Lwe 8015cb5a 80aca9cc 804476c8       3480 80ac8a20 6624/8192 Logger                      &lt;/P&gt;&lt;P&gt;Hwe 8015feeb 80bb1a78 80447978          0 80bafab8 8092/8192 tcp_fast                    &lt;/P&gt;&lt;P&gt;Hwe 8015fe72 80bb3b04 80447978          0 80bb1b48 8088/8192 tcp_slow                    &lt;/P&gt;&lt;P&gt;Lsi 800c7e3a 80c29cb8 80469fc8          0 80c28cf8 4008/4096 xlate clean                 &lt;/P&gt;&lt;P&gt;Lsi 800c7d60 80c2ad44 80469fc8          0 80c29d88 3672/4096 uxlate clean                &lt;/P&gt;&lt;P&gt;Mrd 800c5561 80d7b030 80469ff0          0 80d79078 8004/8192 tcp_intercept_timer_process &lt;/P&gt;&lt;P&gt;Lsi 8019a4aa 80e206d0 80469fc8         10 80e1f710 3956/4096 route_process               &lt;/P&gt;&lt;P&gt;Hsi 800b80e1 80e2175c 80469fc8       5740 80e207a0 2880/4096 Hosts conn cleaner          &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Someone knows the problem with the debugs!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 21 Feb 2020 05:59:20 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-debug-problem/m-p/22447#M696645</guid>
      <dc:creator>imeissner</dc:creator>
      <dc:date>2020-02-21T05:59:20Z</dc:date>
    </item>
    <item>
      <title>Re: PIX debug problem</title>
      <link>https://community.cisco.com/t5/network-security/pix-debug-problem/m-p/22448#M696646</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;"debug packet" can easily overwhelm a pix in &lt;/P&gt;&lt;P&gt;production. You don't want to run it unless this&lt;/P&gt;&lt;P&gt;is for debugging purposes with minimal traffic. &lt;/P&gt;&lt;P&gt;Yes, I've seen it crash the pix.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 27 Feb 2002 15:40:46 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-debug-problem/m-p/22448#M696646</guid>
      <dc:creator>wzhang</dc:creator>
      <dc:date>2002-02-27T15:40:46Z</dc:date>
    </item>
    <item>
      <title>Re: PIX debug problem</title>
      <link>https://community.cisco.com/t5/network-security/pix-debug-problem/m-p/22449#M696647</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Wen,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;i's like that, that the debug each package is analyzed and only the installed IP-packet ar displayed.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Ingolf&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 27 Feb 2002 16:16:00 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-debug-problem/m-p/22449#M696647</guid>
      <dc:creator>imeissner</dc:creator>
      <dc:date>2002-02-27T16:16:00Z</dc:date>
    </item>
    <item>
      <title>Re: PIX debug problem</title>
      <link>https://community.cisco.com/t5/network-security/pix-debug-problem/m-p/22450#M696648</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Once you  give the debug commands to the pix, the pix will continue to generate the debug messages on the console.so it would be impossible to work with the console .One must telnet to the pix from a PC and give "undebugg all" command.I think this wiuld stop the pix from crash. &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 05 Mar 2002 08:54:20 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-debug-problem/m-p/22450#M696648</guid>
      <dc:creator>sudhakar.joseph</dc:creator>
      <dc:date>2002-03-05T08:54:20Z</dc:date>
    </item>
  </channel>
</rss>

