<?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 Re: Any way to have ASA &amp;quot;debug&amp;quot; commands stay on? in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/any-way-to-have-asa-quot-debug-quot-commands-stay-on/m-p/4126974#M1072384</link>
    <description>We have to use the command "logging debug-trace persistent" and then input the debugs we want to run, because if we had the debugs applied before that command, those debugs will not persist after ending the session.&lt;BR /&gt;&lt;BR /&gt;To confirm that you debugs will remain after ending the session , use the command "show debug" and look for the "persistent" keyword , as the below example :&lt;BR /&gt;&lt;BR /&gt;debug aaa shim enabled at level 255&lt;BR /&gt;debug aaa shim enabled at level 255 (persistent)&lt;BR /&gt;debug webvpn  enabled at level 255&lt;BR /&gt;debug webvpn  enabled at level 255 (persistent)&lt;BR /&gt;debug webvpn xml enabled at level 255&lt;BR /&gt;debug webvpn xml enabled at level 255 (persistent)&lt;BR /&gt;debug webvpn anyconnect enabled at level 255&lt;BR /&gt;debug webvpn anyconnect enabled at level 255 (persistent)&lt;BR /&gt;&lt;BR /&gt;</description>
    <pubDate>Tue, 28 Jul 2020 22:07:08 GMT</pubDate>
    <dc:creator>malkhati</dc:creator>
    <dc:date>2020-07-28T22:07:08Z</dc:date>
    <item>
      <title>Any way to have ASA "debug" commands stay on?</title>
      <link>https://community.cisco.com/t5/network-security/any-way-to-have-asa-quot-debug-quot-commands-stay-on/m-p/981474#M940739</link>
      <description>&lt;P&gt;ASA v8.03: I've noticed that if I turn on various debug commands (eg: "debug crypto isakmp sa"), they seem to be automatically turned off when I exit my SSH session.  Is there any way to keep them persistent between sessions?  Cisco routers (IOS) keep debug settings after I exit.&lt;/P&gt;&lt;P&gt;Basically I'm looking for a rare occurrence in my debug logs, but I don't want to stay logged in all the time.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 12:19:22 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/any-way-to-have-asa-quot-debug-quot-commands-stay-on/m-p/981474#M940739</guid>
      <dc:creator>thomasdzubin</dc:creator>
      <dc:date>2019-03-11T12:19:22Z</dc:date>
    </item>
    <item>
      <title>Re: Any way to have ASA "debug" commands stay on?</title>
      <link>https://community.cisco.com/t5/network-security/any-way-to-have-asa-quot-debug-quot-commands-stay-on/m-p/981475#M940741</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;This is not possible since a command is run for that specific instance of the SSH session. When the session is terminated the command is also terminated.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 24 Mar 2008 21:24:29 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/any-way-to-have-asa-quot-debug-quot-commands-stay-on/m-p/981475#M940741</guid>
      <dc:creator>tstanik</dc:creator>
      <dc:date>2008-03-24T21:24:29Z</dc:date>
    </item>
    <item>
      <title>Re: Any way to have ASA "debug" commands stay on?</title>
      <link>https://community.cisco.com/t5/network-security/any-way-to-have-asa-quot-debug-quot-commands-stay-on/m-p/981476#M940742</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;send them to your log server&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;log debug-trace &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 24 Mar 2008 21:29:18 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/any-way-to-have-asa-quot-debug-quot-commands-stay-on/m-p/981476#M940742</guid>
      <dc:creator>abinjola</dc:creator>
      <dc:date>2008-03-24T21:29:18Z</dc:date>
    </item>
    <item>
      <title>Re: Any way to have ASA "debug" commands stay on?</title>
      <link>https://community.cisco.com/t5/network-security/any-way-to-have-asa-quot-debug-quot-commands-stay-on/m-p/981477#M940743</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I just find it odd that I can SSH into a *router* (IOS) and the debug stays on even when I terminate the SSH session.  Yeah, I know the PIX/ASA firewalls and IOS routers are different products that work different, but it would be nice to have debug consistency&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 24 Mar 2008 21:44:51 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/any-way-to-have-asa-quot-debug-quot-commands-stay-on/m-p/981477#M940743</guid>
      <dc:creator>thomasdzubin</dc:creator>
      <dc:date>2008-03-24T21:44:51Z</dc:date>
    </item>
    <item>
      <title>Re: Any way to have ASA "debug" commands stay on?</title>
      <link>https://community.cisco.com/t5/network-security/any-way-to-have-asa-quot-debug-quot-commands-stay-on/m-p/981478#M940744</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Yes, that's what I finally ended up doing.  Thanks&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 24 Mar 2008 21:45:28 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/any-way-to-have-asa-quot-debug-quot-commands-stay-on/m-p/981478#M940744</guid>
      <dc:creator>thomasdzubin</dc:creator>
      <dc:date>2008-03-24T21:45:28Z</dc:date>
    </item>
    <item>
      <title>Re: Any way to have ASA "debug" commands stay on?</title>
      <link>https://community.cisco.com/t5/network-security/any-way-to-have-asa-quot-debug-quot-commands-stay-on/m-p/4126974#M1072384</link>
      <description>We have to use the command "logging debug-trace persistent" and then input the debugs we want to run, because if we had the debugs applied before that command, those debugs will not persist after ending the session.&lt;BR /&gt;&lt;BR /&gt;To confirm that you debugs will remain after ending the session , use the command "show debug" and look for the "persistent" keyword , as the below example :&lt;BR /&gt;&lt;BR /&gt;debug aaa shim enabled at level 255&lt;BR /&gt;debug aaa shim enabled at level 255 (persistent)&lt;BR /&gt;debug webvpn  enabled at level 255&lt;BR /&gt;debug webvpn  enabled at level 255 (persistent)&lt;BR /&gt;debug webvpn xml enabled at level 255&lt;BR /&gt;debug webvpn xml enabled at level 255 (persistent)&lt;BR /&gt;debug webvpn anyconnect enabled at level 255&lt;BR /&gt;debug webvpn anyconnect enabled at level 255 (persistent)&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Tue, 28 Jul 2020 22:07:08 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/any-way-to-have-asa-quot-debug-quot-commands-stay-on/m-p/4126974#M1072384</guid>
      <dc:creator>malkhati</dc:creator>
      <dc:date>2020-07-28T22:07:08Z</dc:date>
    </item>
    <item>
      <title>Re: Any way to have ASA "debug" commands stay on?</title>
      <link>https://community.cisco.com/t5/network-security/any-way-to-have-asa-quot-debug-quot-commands-stay-on/m-p/5029961#M1109533</link>
      <description>&lt;P&gt;&lt;SPAN class="HwtZe"&gt;&lt;SPAN class="jCAhz ChMk0b"&gt;&lt;SPAN class="ryNqvb"&gt;Unfortunately, the persistent debug doesn't work in 9.9(2)80 anymore. logging debug-trace persistent is quite useless when all debuggers won't. Do you have information on that?&lt;BR /&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 29 Feb 2024 15:29:46 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/any-way-to-have-asa-quot-debug-quot-commands-stay-on/m-p/5029961#M1109533</guid>
      <dc:creator>lukasl1991</dc:creator>
      <dc:date>2024-02-29T15:29:46Z</dc:date>
    </item>
    <item>
      <title>Re: Any way to have ASA "debug" commands stay on?</title>
      <link>https://community.cisco.com/t5/network-security/any-way-to-have-asa-quot-debug-quot-commands-stay-on/m-p/5029998#M1109534</link>
      <description>&lt;P&gt;This old post&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Make new one it is better&amp;nbsp;&lt;/P&gt;
&lt;P&gt;MHM&lt;/P&gt;</description>
      <pubDate>Thu, 29 Feb 2024 16:05:26 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/any-way-to-have-asa-quot-debug-quot-commands-stay-on/m-p/5029998#M1109534</guid>
      <dc:creator>MHM Cisco World</dc:creator>
      <dc:date>2024-02-29T16:05:26Z</dc:date>
    </item>
  </channel>
</rss>

