<?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 problem in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/pix-failover-problem/m-p/328279#M550476</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;If possible log the error messages with which you can easily troubleshoot the problem.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 21 Mar 2005 22:38:43 GMT</pubDate>
    <dc:creator>thomas.chen</dc:creator>
    <dc:date>2005-03-21T22:38:43Z</dc:date>
    <item>
      <title>PIX Failover problem</title>
      <link>https://community.cisco.com/t5/network-security/pix-failover-problem/m-p/328278#M550475</link>
      <description>&lt;P&gt;Hello&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I’m having a problem regarding my Primary PIX and PIX Failover unit.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The primary (active) unit unusually getting standby status and consequently the PIX Failover unit unusually getting active status.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;No power interruption nor any configuration change takes place here.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I had this problem yesterday morning and then I gave the command reload to the Failover unit (which at that time was working as active unit) and soon the Primary PIX become active one.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Unfortunately, this morning ( at around 10.00 am) I discovered the same thing, that is the Primary PIX become standby unit without any cause and Secondary Failover become active unit without any cause.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In this regard, I’m here attaching two files – one for Primary PIX and another for Secondary Failover PIX,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;so that it would help you to pin point the actual reason for this problem and fix it up as early as possible accurately.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I’m expecting your prompt reply as you know.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;Tushar&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 21 Feb 2020 08:01:02 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-failover-problem/m-p/328278#M550475</guid>
      <dc:creator>tushar</dc:creator>
      <dc:date>2020-02-21T08:01:02Z</dc:date>
    </item>
    <item>
      <title>Re: PIX Failover problem</title>
      <link>https://community.cisco.com/t5/network-security/pix-failover-problem/m-p/328279#M550476</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;If possible log the error messages with which you can easily troubleshoot the problem.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 21 Mar 2005 22:38:43 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-failover-problem/m-p/328279#M550476</guid>
      <dc:creator>thomas.chen</dc:creator>
      <dc:date>2005-03-21T22:38:43Z</dc:date>
    </item>
  </channel>
</rss>

