<?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 asa failover issue - secondary gets No Failover command in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/asa-failover-issue-secondary-gets-no-failover-command/m-p/1698483#M417199</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Karien,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What does 'show failover history' on both units show when the problem occurs? Are there any syslogs generated when the problem happens? These should give you an idea of why failover is getting disabled.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-Mike&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 10 Jun 2011 16:27:04 GMT</pubDate>
    <dc:creator>mirober2</dc:creator>
    <dc:date>2011-06-10T16:27:04Z</dc:date>
    <item>
      <title>asa failover issue - secondary gets No Failover command</title>
      <link>https://community.cisco.com/t5/network-security/asa-failover-issue-secondary-gets-no-failover-command/m-p/1698482#M417198</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;Anybody has seen this issue, or even better, solved it &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;&lt;P&gt;We have 2 failover clusters&amp;nbsp; that works fine for some time &lt;BR /&gt;but after a random time (6 to 50 days seen), for an unknow reason, the 'no failover' command shows up in the secondary firewall configuration and it has also the NoFailover prompt.&lt;BR /&gt;After that we have 2 active firewalls with the known consequences &lt;span class="lia-unicode-emoji" title=":disappointed_face:"&gt;😞&lt;/span&gt;&lt;BR /&gt;We have 2 cisco cases, but Cisco doens't find anything and we are currently waiting for the issue to happen again to take logs.&lt;/P&gt;&lt;P&gt;extra info:&lt;BR /&gt;1 cluster&amp;nbsp; with 8.2.4 soft&lt;BR /&gt;1 cluster with 8.0.5.23 soft&lt;/P&gt;&lt;P&gt;thx Karien&lt;/P&gt;</description>
      <pubDate>Fri, 21 Feb 2020 12:22:28 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-failover-issue-secondary-gets-no-failover-command/m-p/1698482#M417198</guid>
      <dc:creator>karien.depyper</dc:creator>
      <dc:date>2020-02-21T12:22:28Z</dc:date>
    </item>
    <item>
      <title>asa failover issue - secondary gets No Failover command</title>
      <link>https://community.cisco.com/t5/network-security/asa-failover-issue-secondary-gets-no-failover-command/m-p/1698483#M417199</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Karien,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What does 'show failover history' on both units show when the problem occurs? Are there any syslogs generated when the problem happens? These should give you an idea of why failover is getting disabled.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-Mike&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 10 Jun 2011 16:27:04 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-failover-issue-secondary-gets-no-failover-command/m-p/1698483#M417199</guid>
      <dc:creator>mirober2</dc:creator>
      <dc:date>2011-06-10T16:27:04Z</dc:date>
    </item>
    <item>
      <title>asa failover issue - secondary gets No Failover command</title>
      <link>https://community.cisco.com/t5/network-security/asa-failover-issue-secondary-gets-no-failover-command/m-p/1698484#M417200</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello again,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Root cause found:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1/ Versions higher then 8.0.4 and 8.2.4 have a change in code, by which low failover timers (msec) and redundant interfaces can cause this issue. I changed failover timers, and it seems solved now.&lt;/P&gt;&lt;P&gt;Before:&lt;/P&gt;&lt;P&gt;failover polltime unit msec 200 holdtime msec 800&lt;/P&gt;&lt;P&gt;failover polltime interface msec 500 holdtime 5&lt;/P&gt;&lt;P&gt;Now:&lt;/P&gt;&lt;P&gt;failover polltime unit 1 holdtime 5&lt;/P&gt;&lt;P&gt;failover polltime interface 1 holdtime 5&lt;/P&gt;&lt;P&gt;2/ failover over management interface is not supported.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Good luck!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 01 Aug 2011 08:29:10 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-failover-issue-secondary-gets-no-failover-command/m-p/1698484#M417200</guid>
      <dc:creator>karien.depyper</dc:creator>
      <dc:date>2011-08-01T08:29:10Z</dc:date>
    </item>
  </channel>
</rss>

