<?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 Failover pix become the permanent active? in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/failover-pix-become-the-permanent-active/m-p/615895#M497089</link>
    <description>&lt;P&gt;After the Primary failed the Standby has become the Active running over a month with new changes. Can the Standby force "write standby" to the old Primary pix before making the old Primary the Active?&lt;/P&gt;</description>
    <pubDate>Fri, 21 Feb 2020 09:14:37 GMT</pubDate>
    <dc:creator>carlos.hernandez</dc:creator>
    <dc:date>2020-02-21T09:14:37Z</dc:date>
    <item>
      <title>Failover pix become the permanent active?</title>
      <link>https://community.cisco.com/t5/network-security/failover-pix-become-the-permanent-active/m-p/615895#M497089</link>
      <description>&lt;P&gt;After the Primary failed the Standby has become the Active running over a month with new changes. Can the Standby force "write standby" to the old Primary pix before making the old Primary the Active?&lt;/P&gt;</description>
      <pubDate>Fri, 21 Feb 2020 09:14:37 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/failover-pix-become-the-permanent-active/m-p/615895#M497089</guid>
      <dc:creator>carlos.hernandez</dc:creator>
      <dc:date>2020-02-21T09:14:37Z</dc:date>
    </item>
    <item>
      <title>Re: Failover pix become the permanent active?</title>
      <link>https://community.cisco.com/t5/network-security/failover-pix-become-the-permanent-active/m-p/615896#M497090</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;if the above can't be done does anyone know how much time the Standby with FO license is allowed to run before bring up the Primary with UR license online and making it the Active?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Carlos&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 17 Oct 2006 16:29:27 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/failover-pix-become-the-permanent-active/m-p/615896#M497090</guid>
      <dc:creator>carlos.hernandez</dc:creator>
      <dc:date>2006-10-17T16:29:27Z</dc:date>
    </item>
    <item>
      <title>Re: Failover pix become the permanent active?</title>
      <link>https://community.cisco.com/t5/network-security/failover-pix-become-the-permanent-active/m-p/615897#M497091</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;You can write standby to push the config to the "primary" that is currently standby. The following link confirms this:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-custom" href="http://www.ciscotaccc.com/kaidara-advisor/security/showcase?case=K15656661" target="_blank"&gt;http://www.ciscotaccc.com/kaidara-advisor/security/showcase?case=K15656661&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;As it mentions, the main gotcha is you need to configure failover first on the replacement unit (makes sense).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;- Eric&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 18 Oct 2006 03:10:11 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/failover-pix-become-the-permanent-active/m-p/615897#M497091</guid>
      <dc:creator>ethiel</dc:creator>
      <dc:date>2006-10-18T03:10:11Z</dc:date>
    </item>
    <item>
      <title>Re: Failover pix become the permanent active?</title>
      <link>https://community.cisco.com/t5/network-security/failover-pix-become-the-permanent-active/m-p/615898#M497092</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;that is precisely what I was wondering. Thanks for confirming the process. The key thing is that the replication does not occur automatically when preempt is not configured.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;thanks very much for your response.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;regards,&lt;/P&gt;&lt;P&gt;carlos&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 18 Oct 2006 15:15:08 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/failover-pix-become-the-permanent-active/m-p/615898#M497092</guid>
      <dc:creator>carlos.hernandez</dc:creator>
      <dc:date>2006-10-18T15:15:08Z</dc:date>
    </item>
    <item>
      <title>Re: Failover pix become the permanent active?</title>
      <link>https://community.cisco.com/t5/network-security/failover-pix-become-the-permanent-active/m-p/615899#M497093</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Actually, to slightly revise my post, the link at the bottom of that page points out that if the new PIX is booted with the failover cable already connected, it will receive the config from the already running one. This is good in your situation, but bad if you have config on the new one that you want to keep.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-Eric&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Please remember to rate all helpful posts.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 18 Oct 2006 17:36:42 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/failover-pix-become-the-permanent-active/m-p/615899#M497093</guid>
      <dc:creator>ethiel</dc:creator>
      <dc:date>2006-10-18T17:36:42Z</dc:date>
    </item>
  </channel>
</rss>

