<?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: Primary PIX failover interface stays in testing state in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/primary-pix-failover-interface-stays-in-testing-state/m-p/38545#M677591</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;In the event the "hello" packets are not received on an interface, or an interface waiting for "hello" more than 2.5 minutes after the other interface went into normal state, the interface is placed in "testing" mode (if the interface is not shutdown and link status is up). When this occurs, the other unit is informed through the failover cable that the interface is in testing mode. While an interface is in testing mode, normal traffic can flow, provided the interface is functioning properly. Testing is started only if an error condition has occurred and is therefore based on the idea that "if I'm okay, then you must be failed." &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope that answers your query.&lt;/P&gt;&lt;P&gt;R/Yusuf&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 04 Jul 2002 04:00:07 GMT</pubDate>
    <dc:creator>yusuff</dc:creator>
    <dc:date>2002-07-04T04:00:07Z</dc:date>
    <item>
      <title>Primary PIX failover interface stays in testing state</title>
      <link>https://community.cisco.com/t5/network-security/primary-pix-failover-interface-stays-in-testing-state/m-p/38544#M677583</link>
      <description>&lt;P&gt;I issued the show failover command on my primary pix box.  It showed two of the three interfaces in normal mode, but the third ( a vpn tunnel) was in test mode. I was able to ping, and send traffic successfully going through the third interface; but when the show failover was issued, the third interface was consistently in testing mode.  When the show failover command was issued on the secondary pix box, all three interfaces were in normal mode.  I finally reloaded the secondary pix box and this seemed to resolve the issue.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Has any body seen this, and is this a comman problem?&lt;/P&gt;&lt;P&gt;Version 6.1&lt;/P&gt;&lt;P&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 21 Feb 2020 06:08:42 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/primary-pix-failover-interface-stays-in-testing-state/m-p/38544#M677583</guid>
      <dc:creator>gresendiz</dc:creator>
      <dc:date>2020-02-21T06:08:42Z</dc:date>
    </item>
    <item>
      <title>Re: Primary PIX failover interface stays in testing state</title>
      <link>https://community.cisco.com/t5/network-security/primary-pix-failover-interface-stays-in-testing-state/m-p/38545#M677591</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;In the event the "hello" packets are not received on an interface, or an interface waiting for "hello" more than 2.5 minutes after the other interface went into normal state, the interface is placed in "testing" mode (if the interface is not shutdown and link status is up). When this occurs, the other unit is informed through the failover cable that the interface is in testing mode. While an interface is in testing mode, normal traffic can flow, provided the interface is functioning properly. Testing is started only if an error condition has occurred and is therefore based on the idea that "if I'm okay, then you must be failed." &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope that answers your query.&lt;/P&gt;&lt;P&gt;R/Yusuf&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 04 Jul 2002 04:00:07 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/primary-pix-failover-interface-stays-in-testing-state/m-p/38545#M677591</guid>
      <dc:creator>yusuff</dc:creator>
      <dc:date>2002-07-04T04:00:07Z</dc:date>
    </item>
  </channel>
</rss>

