<?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  Hi MArvin, I was curious to in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/debug-fover-in-active-active/m-p/2492467#M238796</link>
    <description>&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Hi MArvin,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I was curious to learn about output of debug commands but as per your reply leave&lt;/P&gt;&lt;P&gt;it for now untill we have some issues.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;MAhesh&lt;/P&gt;</description>
    <pubDate>Thu, 01 May 2014 17:35:50 GMT</pubDate>
    <dc:creator>mahesh18</dc:creator>
    <dc:date>2014-05-01T17:35:50Z</dc:date>
    <item>
      <title>debug fover in active/active</title>
      <link>https://community.cisco.com/t5/network-security/debug-fover-in-active-active/m-p/2492465#M238782</link>
      <description>&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Hi Everyone,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Need to know if ASA is in active/active state.&lt;/P&gt;&lt;P&gt;I check the command&lt;/P&gt;&lt;P&gt;debug&amp;nbsp; fover ?&lt;/P&gt;&lt;P&gt;&amp;nbsp; cable&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Failover LAN status&lt;BR /&gt;&amp;nbsp; cmd-exec&amp;nbsp; Failover EXEC command execution&lt;BR /&gt;&amp;nbsp; fail&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Failover internal exception&lt;BR /&gt;&amp;nbsp; fmsg&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Failover message&lt;BR /&gt;&amp;nbsp; ifc&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Network interface status trace&lt;BR /&gt;&amp;nbsp; open&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Failover device open&lt;BR /&gt;&amp;nbsp; rx&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Failover Message receive&lt;BR /&gt;&amp;nbsp; rxdmp&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Failover recv message dump (serial console only)&lt;BR /&gt;&amp;nbsp; rxip&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; IP network failover packet recv&lt;BR /&gt;&amp;nbsp; switch&amp;nbsp;&amp;nbsp;&amp;nbsp; Failover Switching status&lt;BR /&gt;&amp;nbsp; sync&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Failover config/command replication&lt;BR /&gt;&amp;nbsp; tx&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Failover Message xmit&lt;BR /&gt;&amp;nbsp; txdmp&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Failover xmit message dump (serial console only)&lt;BR /&gt;&amp;nbsp; txip&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; IP network failover packet xmit&lt;BR /&gt;&amp;nbsp; verify&amp;nbsp;&amp;nbsp;&amp;nbsp; Failover message verify&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;this is available both in system and admin context.&lt;/P&gt;&lt;P&gt;is there any reason for this that it is available in both contexts?&lt;/P&gt;&lt;P&gt;if i run debug fover will that run debug for both contexts?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Also if failover is working fine and i run command&lt;/P&gt;&lt;P&gt;debug fover cable will this cause any outage?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Mahesh&lt;/P&gt;</description>
      <pubDate>Tue, 12 Mar 2019 04:08:53 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/debug-fover-in-active-active/m-p/2492465#M238782</guid>
      <dc:creator>mahesh18</dc:creator>
      <dc:date>2019-03-12T04:08:53Z</dc:date>
    </item>
    <item>
      <title>Mahesh,"show failover" will</title>
      <link>https://community.cisco.com/t5/network-security/debug-fover-in-active-active/m-p/2492466#M238793</link>
      <description>&lt;P&gt;Mahesh,&lt;/P&gt;&lt;P&gt;"show failover" will give you the status. "show failover history" will show you the last several events.&lt;/P&gt;&lt;P&gt;Any debug should always be used very sparingly on a production device (even more so if a lot of people depend on it working reliably). We typically debug on production devices only when working with TAC on a device that's already having issues.&lt;/P&gt;</description>
      <pubDate>Thu, 01 May 2014 17:31:30 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/debug-fover-in-active-active/m-p/2492466#M238793</guid>
      <dc:creator>Marvin Rhoads</dc:creator>
      <dc:date>2014-05-01T17:31:30Z</dc:date>
    </item>
    <item>
      <title> Hi MArvin, I was curious to</title>
      <link>https://community.cisco.com/t5/network-security/debug-fover-in-active-active/m-p/2492467#M238796</link>
      <description>&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Hi MArvin,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I was curious to learn about output of debug commands but as per your reply leave&lt;/P&gt;&lt;P&gt;it for now untill we have some issues.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;MAhesh&lt;/P&gt;</description>
      <pubDate>Thu, 01 May 2014 17:35:50 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/debug-fover-in-active-active/m-p/2492467#M238796</guid>
      <dc:creator>mahesh18</dc:creator>
      <dc:date>2014-05-01T17:35:50Z</dc:date>
    </item>
  </channel>
</rss>

