<?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 question in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/pix-failover-question/m-p/547477#M526244</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thank you so much for your reply. &lt;/P&gt;&lt;P&gt;In fact, since it failover to the secondary unit for some reason, I am fine with just running on the secondary unit as an active unit. However, I got the following message when I try to configure something on the secondary unit. Is there a way to fix this without using the "failover" command you have suggested? &lt;/P&gt;&lt;P&gt;________________________________________&lt;/P&gt;&lt;P&gt;PRSPIX1# conf t&lt;/P&gt;&lt;P&gt;**** WARNING *** &lt;/P&gt;&lt;P&gt;        Configuration Replication is NOT performed from Standby unit to Active unit.&lt;/P&gt;&lt;P&gt;        Configurations are no longer synchronized.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 22 Mar 2006 02:11:41 GMT</pubDate>
    <dc:creator>kope</dc:creator>
    <dc:date>2006-03-22T02:11:41Z</dc:date>
    <item>
      <title>PIX Failover question</title>
      <link>https://community.cisco.com/t5/network-security/pix-failover-question/m-p/547474#M526234</link>
      <description>&lt;P&gt;I got the following message when the primary PIX fail over to the secondary. My question is just how do I fail back to the primary PIX as an active unit?&lt;/P&gt;&lt;P&gt;# sh failover&lt;/P&gt;&lt;P&gt;Failover On&lt;/P&gt;&lt;P&gt;Cable status: Normal&lt;/P&gt;&lt;P&gt;Reconnect timeout 0:00:00&lt;/P&gt;&lt;P&gt;Poll frequency 15 seconds&lt;/P&gt;&lt;P&gt;Last Failover at: 09:53:43 cst Sun Mar 19 2006&lt;/P&gt;&lt;P&gt;        This host: Primary - Standby &lt;/P&gt;&lt;P&gt;                Active time: 8750355 (sec)&lt;/P&gt;&lt;P&gt;                Interface outside (18.18.46.5): Normal &lt;/P&gt;&lt;P&gt;                Interface inside (18.18.46.130): Normal &lt;/P&gt;&lt;P&gt;                Interface dmz (18.18.45.2): Normal &lt;/P&gt;&lt;P&gt;                Interface failover (10.10.10.3): Normal &lt;/P&gt;&lt;P&gt;        Other host: Secondary - Active &lt;/P&gt;&lt;P&gt;                Active time: 181080 (sec)&lt;/P&gt;&lt;P&gt;                Interface outside (18.18.46.4): Normal &lt;/P&gt;&lt;P&gt;                Interface inside (18.18.46.129): Normal &lt;/P&gt;&lt;P&gt;                Interface dmz (18.18.45.1): Normal &lt;/P&gt;&lt;P&gt;                Interface failover (10.10.10.1): Normal &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks.&lt;/P&gt;</description>
      <pubDate>Fri, 21 Feb 2020 08:47:25 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-failover-question/m-p/547474#M526234</guid>
      <dc:creator>kope</dc:creator>
      <dc:date>2020-02-21T08:47:25Z</dc:date>
    </item>
    <item>
      <title>Re: PIX Failover question</title>
      <link>https://community.cisco.com/t5/network-security/pix-failover-question/m-p/547475#M526236</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;To fail back to the primary unit you can either do:&lt;/P&gt;&lt;P&gt;&lt;B&gt;&lt;/B&gt;&lt;/P&gt;&lt;P&gt;failover active&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;on the primary, or do:&lt;/P&gt;&lt;P&gt;&lt;B&gt;&lt;/B&gt;&lt;/P&gt;&lt;P&gt;no failover active&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;on the secondary.  Keep in mind that because a failover pair are always the same hardware, there theoretically is no advantage to running on the primary unit, and so if the units do fail over to the secondary for some reason, they will NOT fail back automatically.  If for whatever reason you prefer running on the primary unit, then you have to manually fail them back using either of the above two commands.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 21 Mar 2006 23:30:36 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-failover-question/m-p/547475#M526236</guid>
      <dc:creator>gfullage</dc:creator>
      <dc:date>2006-03-21T23:30:36Z</dc:date>
    </item>
    <item>
      <title>Re: PIX Failover question</title>
      <link>https://community.cisco.com/t5/network-security/pix-failover-question/m-p/547476#M526242</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;hi glen how are u . sebastan remember. good to see u in the forum adn helping us out. hey glen i have a serious doubt regarding the interface testing procedure in the pix failover process. if possible kind help me out . in the topic "stateful failover with cross-over cable between pix firewalls".if possible.pls help me out.waiting for ur reply. see ya and bye &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;sebastan&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 22 Mar 2006 01:45:55 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-failover-question/m-p/547476#M526242</guid>
      <dc:creator>sebastan_bach</dc:creator>
      <dc:date>2006-03-22T01:45:55Z</dc:date>
    </item>
    <item>
      <title>Re: PIX Failover question</title>
      <link>https://community.cisco.com/t5/network-security/pix-failover-question/m-p/547477#M526244</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thank you so much for your reply. &lt;/P&gt;&lt;P&gt;In fact, since it failover to the secondary unit for some reason, I am fine with just running on the secondary unit as an active unit. However, I got the following message when I try to configure something on the secondary unit. Is there a way to fix this without using the "failover" command you have suggested? &lt;/P&gt;&lt;P&gt;________________________________________&lt;/P&gt;&lt;P&gt;PRSPIX1# conf t&lt;/P&gt;&lt;P&gt;**** WARNING *** &lt;/P&gt;&lt;P&gt;        Configuration Replication is NOT performed from Standby unit to Active unit.&lt;/P&gt;&lt;P&gt;        Configurations are no longer synchronized.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 22 Mar 2006 02:11:41 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-failover-question/m-p/547477#M526244</guid>
      <dc:creator>kope</dc:creator>
      <dc:date>2006-03-22T02:11:41Z</dc:date>
    </item>
    <item>
      <title>Re: PIX Failover question</title>
      <link>https://community.cisco.com/t5/network-security/pix-failover-question/m-p/547478#M526248</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Pix will not replicate the config from standby to active unit,so make sure when ever you make any config changes it has to be on the Active unit.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Simply Check which Pix is Active then make the config changes on that.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Tanveer&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 22 Mar 2006 09:07:22 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-failover-question/m-p/547478#M526248</guid>
      <dc:creator>thamdani</dc:creator>
      <dc:date>2006-03-22T09:07:22Z</dc:date>
    </item>
    <item>
      <title>Re: PIX Failover question</title>
      <link>https://community.cisco.com/t5/network-security/pix-failover-question/m-p/547479#M526252</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;And check to see why the actice PIX failed in the first place. You don't want to leave behind a lingering problem....&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 28 Mar 2006 16:35:43 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-failover-question/m-p/547479#M526252</guid>
      <dc:creator>mloring</dc:creator>
      <dc:date>2006-03-28T16:35:43Z</dc:date>
    </item>
  </channel>
</rss>

