<?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 Problem with Failover ASA5506X version 9.5.2 in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/problem-with-failover-asa5506x-version-9-5-2/m-p/2829388#M174136</link>
    <description>&lt;P&gt;I have a problem with ASA5506X version 9.5.2.&amp;nbsp; Active/Standby falover is configured but it seems that the outside interface status is not monitored correctly.&lt;/P&gt;
&lt;P&gt;Failure of the inside interface activate the standby normaly, but a failure of the outside interface link does nothing.&amp;nbsp; Even more.&amp;nbsp; On the serial console of the "active" ASA5506, the show interface GigabitEthernet1/1 show the interface as "up" even tough there is no network cable connected to it.&lt;/P&gt;
&lt;P&gt;So it's probably why the failover is not activated by failure of the outside interface&lt;/P&gt;
&lt;P&gt;a "show failover" also reports the outside interface as normal even though no network cable is connected to it&lt;/P&gt;
&lt;P&gt;If the failover is forced from the "secondary" now active, seems like both becomes active and no traffic id forwarded.&amp;nbsp; A reboot of the secondary unit, brings back communication as it returned to it's standby state.&amp;nbsp; I have done these setup many times with the ASA5505 without any problems.&lt;/P&gt;
&lt;P&gt;Error message at boot process saying "Failed to start admin listener"&amp;nbsp; Can't say it's related to the problem but I think it's&amp;nbsp;very likely&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;</description>
    <pubDate>Tue, 12 Mar 2019 07:01:20 GMT</pubDate>
    <dc:creator>alain.chagnon</dc:creator>
    <dc:date>2019-03-12T07:01:20Z</dc:date>
    <item>
      <title>Problem with Failover ASA5506X version 9.5.2</title>
      <link>https://community.cisco.com/t5/network-security/problem-with-failover-asa5506x-version-9-5-2/m-p/2829388#M174136</link>
      <description>&lt;P&gt;I have a problem with ASA5506X version 9.5.2.&amp;nbsp; Active/Standby falover is configured but it seems that the outside interface status is not monitored correctly.&lt;/P&gt;
&lt;P&gt;Failure of the inside interface activate the standby normaly, but a failure of the outside interface link does nothing.&amp;nbsp; Even more.&amp;nbsp; On the serial console of the "active" ASA5506, the show interface GigabitEthernet1/1 show the interface as "up" even tough there is no network cable connected to it.&lt;/P&gt;
&lt;P&gt;So it's probably why the failover is not activated by failure of the outside interface&lt;/P&gt;
&lt;P&gt;a "show failover" also reports the outside interface as normal even though no network cable is connected to it&lt;/P&gt;
&lt;P&gt;If the failover is forced from the "secondary" now active, seems like both becomes active and no traffic id forwarded.&amp;nbsp; A reboot of the secondary unit, brings back communication as it returned to it's standby state.&amp;nbsp; I have done these setup many times with the ASA5505 without any problems.&lt;/P&gt;
&lt;P&gt;Error message at boot process saying "Failed to start admin listener"&amp;nbsp; Can't say it's related to the problem but I think it's&amp;nbsp;very likely&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 12 Mar 2019 07:01:20 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/problem-with-failover-asa5506x-version-9-5-2/m-p/2829388#M174136</guid>
      <dc:creator>alain.chagnon</dc:creator>
      <dc:date>2019-03-12T07:01:20Z</dc:date>
    </item>
    <item>
      <title>have you try with failover</title>
      <link>https://community.cisco.com/t5/network-security/problem-with-failover-asa5506x-version-9-5-2/m-p/2829389#M174138</link>
      <description>&lt;P&gt;have you try with failover history?&lt;/P&gt;
&lt;P&gt;outside interface is up and running on both ASA? (Primary and Standby)&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Regards.&lt;/P&gt;
&lt;P&gt;Rolando Valenzuela&lt;/P&gt;</description>
      <pubDate>Thu, 10 Dec 2015 20:49:25 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/problem-with-failover-asa5506x-version-9-5-2/m-p/2829389#M174138</guid>
      <dc:creator>Rolando Valenzuela</dc:creator>
      <dc:date>2015-12-10T20:49:25Z</dc:date>
    </item>
    <item>
      <title>I had the same problem, my</title>
      <link>https://community.cisco.com/t5/network-security/problem-with-failover-asa5506x-version-9-5-2/m-p/2829390#M174139</link>
      <description>&lt;P&gt;I had the same problem, my issue was that the outside interface https was NATted, changed the ASDM port (duh). Only one result with the phrase&amp;nbsp;&lt;SPAN&gt;"Failed to start admin listener" so I guess I'll leave this here.&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 05 Oct 2016 15:29:41 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/problem-with-failover-asa5506x-version-9-5-2/m-p/2829390#M174139</guid>
      <dc:creator>Zachary Bovard</dc:creator>
      <dc:date>2016-10-05T15:29:41Z</dc:date>
    </item>
  </channel>
</rss>

