<?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 Question in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/asa-failover-question/m-p/1344976#M839065</link>
    <description>&lt;P&gt;I have 2 5540 ASA in an Active / Standy setup. The Active firewall has a packet shaper sitting between it and the inside LAN. When I reboot the Packet shaper the FWs failover. I have the default timeings for failover 1 second hello 15 seconds keepalive. I would assume this emans that as long as the Active firewall sends a hello packet within 15 seconds the standby will not assume the active role. The Packet Shaper reboot takes only a couple of seconds (typically 1 or 2 lost ping packets) Am I missing something simple here?&lt;/P&gt;</description>
    <pubDate>Mon, 11 Mar 2019 15:55:29 GMT</pubDate>
    <dc:creator>ricey</dc:creator>
    <dc:date>2019-03-11T15:55:29Z</dc:date>
    <item>
      <title>ASA Failover Question</title>
      <link>https://community.cisco.com/t5/network-security/asa-failover-question/m-p/1344976#M839065</link>
      <description>&lt;P&gt;I have 2 5540 ASA in an Active / Standy setup. The Active firewall has a packet shaper sitting between it and the inside LAN. When I reboot the Packet shaper the FWs failover. I have the default timeings for failover 1 second hello 15 seconds keepalive. I would assume this emans that as long as the Active firewall sends a hello packet within 15 seconds the standby will not assume the active role. The Packet Shaper reboot takes only a couple of seconds (typically 1 or 2 lost ping packets) Am I missing something simple here?&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 15:55:29 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-failover-question/m-p/1344976#M839065</guid>
      <dc:creator>ricey</dc:creator>
      <dc:date>2019-03-11T15:55:29Z</dc:date>
    </item>
    <item>
      <title>Re: ASA Failover Question</title>
      <link>https://community.cisco.com/t5/network-security/asa-failover-question/m-p/1344977#M839066</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;The packetshaper takes only a few seconds to reboot. However, the interface link will be down for approximately 40 seconds during the reboot as I tested in a lab.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;All systems are like this, it doesn't mean that once they booted successfully, their network link will be up at the same time.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 15 Jul 2009 14:23:32 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-failover-question/m-p/1344977#M839066</guid>
      <dc:creator>Danilo Dy</dc:creator>
      <dc:date>2009-07-15T14:23:32Z</dc:date>
    </item>
    <item>
      <title>Re: ASA Failover Question</title>
      <link>https://community.cisco.com/t5/network-security/asa-failover-question/m-p/1344978#M839067</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Danilo,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;thanks for your quick response. What is the reason for this? &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;By the way, the packet shaper does not really take only a few seconds to boot, buts "fails open" whenever it is rebooted. &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 15 Jul 2009 14:31:48 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-failover-question/m-p/1344978#M839067</guid>
      <dc:creator>ricey</dc:creator>
      <dc:date>2009-07-15T14:31:48Z</dc:date>
    </item>
    <item>
      <title>Re: ASA Failover Question</title>
      <link>https://community.cisco.com/t5/network-security/asa-failover-question/m-p/1344979#M839068</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;This is probably because of interface health checks. The primary device sees the interface go down and is now "less healthy" than the secondary and fails over.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 15 Jul 2009 17:54:30 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-failover-question/m-p/1344979#M839068</guid>
      <dc:creator>plumbis</dc:creator>
      <dc:date>2009-07-15T17:54:30Z</dc:date>
    </item>
    <item>
      <title>Re: ASA Failover Question</title>
      <link>https://community.cisco.com/t5/network-security/asa-failover-question/m-p/1344980#M839069</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Pete,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks very much for your respose. Do you know how I can override this default behaviour and ensure the primary stays active unless the secondary does not receive a hello packet within the 15 seconds?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks again,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Rich&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 16 Jul 2009 07:01:14 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-failover-question/m-p/1344980#M839069</guid>
      <dc:creator>ricey</dc:creator>
      <dc:date>2009-07-16T07:01:14Z</dc:date>
    </item>
  </channel>
</rss>

