<?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: PIX FAILOVER ACTIVE-STANDBY in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/pix-failover-active-standby/m-p/163171#M608199</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi G&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;That goes for all failover devices such as PIX'es, LocalDirectors etc.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Every time a unit goes from standby to active there is a short time with no connection to whatever users are trying to reach. All connections are also dropped, which can result in timeouts for users.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Since the primary and secondary unit are only selected by the end of the failover cable and only can work on 2 identical units, there is no need to switch back. The performance is exactly the same on both units, so why risk losing maybe important sessions? As I see it, there is no need for such a "switchback" mechanism and I am sure that Cisco feels the same way about this.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Best regards&lt;/P&gt;&lt;P&gt;Jan&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 14 Mar 2003 11:04:55 GMT</pubDate>
    <dc:creator>jbeining</dc:creator>
    <dc:date>2003-03-14T11:04:55Z</dc:date>
    <item>
      <title>PIX FAILOVER ACTIVE-STANDBY</title>
      <link>https://community.cisco.com/t5/network-security/pix-failover-active-standby/m-p/163170#M608198</link>
      <description>&lt;P&gt;Hi all.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Reading the docs, when 2 pix are in LAN FAILOVER situation (without stateful link), primary unit is active and secondary unit is standby.&lt;/P&gt;&lt;P&gt;When primary goes down, secondary get the active status and start to&lt;/P&gt;&lt;P&gt;accept traffic.&lt;/P&gt;&lt;P&gt;When primary goes up after a failure, it shuold reclaim the active status, but&lt;/P&gt;&lt;P&gt;in my situation the secondary remain active and the primary is standby.&lt;/P&gt;&lt;P&gt;To force primary to return active i shuold issue "failover actvie".&lt;/P&gt;&lt;P&gt;Why this?&lt;/P&gt;&lt;P&gt;I miss somethings?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks.&lt;/P&gt;&lt;P&gt;G.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 21 Feb 2020 06:37:25 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-failover-active-standby/m-p/163170#M608198</guid>
      <dc:creator>giuliano</dc:creator>
      <dc:date>2020-02-21T06:37:25Z</dc:date>
    </item>
    <item>
      <title>Re: PIX FAILOVER ACTIVE-STANDBY</title>
      <link>https://community.cisco.com/t5/network-security/pix-failover-active-standby/m-p/163171#M608199</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi G&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;That goes for all failover devices such as PIX'es, LocalDirectors etc.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Every time a unit goes from standby to active there is a short time with no connection to whatever users are trying to reach. All connections are also dropped, which can result in timeouts for users.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Since the primary and secondary unit are only selected by the end of the failover cable and only can work on 2 identical units, there is no need to switch back. The performance is exactly the same on both units, so why risk losing maybe important sessions? As I see it, there is no need for such a "switchback" mechanism and I am sure that Cisco feels the same way about this.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Best regards&lt;/P&gt;&lt;P&gt;Jan&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 14 Mar 2003 11:04:55 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-failover-active-standby/m-p/163171#M608199</guid>
      <dc:creator>jbeining</dc:creator>
      <dc:date>2003-03-14T11:04:55Z</dc:date>
    </item>
    <item>
      <title>Re: PIX FAILOVER ACTIVE-STANDBY</title>
      <link>https://community.cisco.com/t5/network-security/pix-failover-active-standby/m-p/163172#M608200</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Yes, it sounds logic ....&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 14 Mar 2003 16:03:12 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-failover-active-standby/m-p/163172#M608200</guid>
      <dc:creator>giuliano</dc:creator>
      <dc:date>2003-03-14T16:03:12Z</dc:date>
    </item>
    <item>
      <title>Re: PIX FAILOVER ACTIVE-STANDBY</title>
      <link>https://community.cisco.com/t5/network-security/pix-failover-active-standby/m-p/163173#M608201</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Just to confirm what the previous poster said, after the primary or failed PIX comes back up, the currently active PIX does NOT automatically fail over.  Why should it.  If you want to force the primary to become the active again then you can either do a "failover active" on the primary, or a "no failover active" on the secondary.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This is noted here:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-custom" href="http://www.cisco.com/warp/public/110/failover.html#failback" target="_blank"&gt;http://www.cisco.com/warp/public/110/failover.html#failback&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Also, the previous poster mentioned that during failover all sessions are lost.  This is NOT true if you're doing stateful failover, which I would recommend.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 17 Mar 2003 03:08:17 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-failover-active-standby/m-p/163173#M608201</guid>
      <dc:creator>gfullage</dc:creator>
      <dc:date>2003-03-17T03:08:17Z</dc:date>
    </item>
  </channel>
</rss>

