<?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: Failover issue. in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/failover-issue/m-p/1398238#M857128</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;Even i too faced this issue some time back.In this scenario just need to apply two command.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1.Apply "failover active" command in primary unit.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;2.Apply "no failover active " command in seconday,then immediatey it will go standby mode.then connect the failover utp cable.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;3.In your secondary firewall failover configuration, make sure the below command should be available &lt;STRONG&gt;"failover lan unit secondary"&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;regards&lt;/P&gt;&lt;P&gt;karuppu&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 02 Mar 2010 05:43:23 GMT</pubDate>
    <dc:creator>KARUPPUCHAMY MALAIYANDI</dc:creator>
    <dc:date>2010-03-02T05:43:23Z</dc:date>
    <item>
      <title>Failover issue.</title>
      <link>https://community.cisco.com/t5/network-security/failover-issue/m-p/1398235#M857125</link>
      <description>&lt;P&gt;Hi All,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am facing a issue in ASA failover.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Scenario:-&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;2 ASA 5520 box.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Version 8.2(1).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;2 box is connecting with utp cable back to back failover.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When we connecting the failover cable, the configuration is replicating from the secondary box to Primary.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Why it is behaving like this firewall any bug in this IOS?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Rgds,&lt;/P&gt;&lt;P&gt;Subash&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 17:15:51 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/failover-issue/m-p/1398235#M857125</guid>
      <dc:creator>subashmbi</dc:creator>
      <dc:date>2019-03-11T17:15:51Z</dc:date>
    </item>
    <item>
      <title>Re: Failover issue.</title>
      <link>https://community.cisco.com/t5/network-security/failover-issue/m-p/1398236#M857126</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I am not sure of the problem.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Do they keep failing over or the blank config from the standby unit gets written to the active unit?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You need to collect&lt;/P&gt;&lt;P&gt;sh run fail&lt;/P&gt;&lt;P&gt;sh fail&lt;/P&gt;&lt;P&gt;sh fail history&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;from both units and see what might be going on. Do both units think they are active?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-KS&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 01 Mar 2010 18:05:36 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/failover-issue/m-p/1398236#M857126</guid>
      <dc:creator>Kureli Sankar</dc:creator>
      <dc:date>2010-03-01T18:05:36Z</dc:date>
    </item>
    <item>
      <title>Re: Failover issue.</title>
      <link>https://community.cisco.com/t5/network-security/failover-issue/m-p/1398237#M857127</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;I am sending the logs of my Primary unit.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Rgds&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Sub&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 02 Mar 2010 04:53:46 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/failover-issue/m-p/1398237#M857127</guid>
      <dc:creator>subashmbi</dc:creator>
      <dc:date>2010-03-02T04:53:46Z</dc:date>
    </item>
    <item>
      <title>Re: Failover issue.</title>
      <link>https://community.cisco.com/t5/network-security/failover-issue/m-p/1398238#M857128</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;Even i too faced this issue some time back.In this scenario just need to apply two command.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1.Apply "failover active" command in primary unit.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;2.Apply "no failover active " command in seconday,then immediatey it will go standby mode.then connect the failover utp cable.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;3.In your secondary firewall failover configuration, make sure the below command should be available &lt;STRONG&gt;"failover lan unit secondary"&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;regards&lt;/P&gt;&lt;P&gt;karuppu&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 02 Mar 2010 05:43:23 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/failover-issue/m-p/1398238#M857128</guid>
      <dc:creator>KARUPPUCHAMY MALAIYANDI</dc:creator>
      <dc:date>2010-03-02T05:43:23Z</dc:date>
    </item>
    <item>
      <title>Re: Failover issue.</title>
      <link>https://community.cisco.com/t5/network-security/failover-issue/m-p/1398239#M857129</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks...&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 02 Mar 2010 12:24:22 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/failover-issue/m-p/1398239#M857129</guid>
      <dc:creator>subashmbi</dc:creator>
      <dc:date>2010-03-02T12:24:22Z</dc:date>
    </item>
  </channel>
</rss>

