<?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 ASA 5512 Sync Problems in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/asa-5512-sync-problems/m-p/2617551#M197504</link>
    <description>&lt;P&gt;I am trying to configure an active/standby pair of ASA 5512's running version 8.6(1)2. The standby ASA will not sync with the active ASA. Is there a bug for this or is my configuration lacking?&lt;/P&gt;&lt;P&gt;#show running-config failover&lt;BR /&gt;failover&lt;BR /&gt;failover lan unit primary&lt;BR /&gt;failover lan interface fo GigabitEthernet0/3&lt;BR /&gt;failover key *****&lt;BR /&gt;failover replication http&lt;BR /&gt;failover link fo GigabitEthernet0/3&lt;BR /&gt;failover interface ip fo 192.168.255.1 255.255.255.252 standby 192.168.255.2&lt;BR /&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The secondary firewall is configured identically except for failover lan unit secondary.&lt;/P&gt;&lt;P&gt;The failover interfaces are using a dedicated switch.&lt;/P&gt;</description>
    <pubDate>Tue, 12 Mar 2019 05:24:47 GMT</pubDate>
    <dc:creator>cavazos.art</dc:creator>
    <dc:date>2019-03-12T05:24:47Z</dc:date>
    <item>
      <title>ASA 5512 Sync Problems</title>
      <link>https://community.cisco.com/t5/network-security/asa-5512-sync-problems/m-p/2617551#M197504</link>
      <description>&lt;P&gt;I am trying to configure an active/standby pair of ASA 5512's running version 8.6(1)2. The standby ASA will not sync with the active ASA. Is there a bug for this or is my configuration lacking?&lt;/P&gt;&lt;P&gt;#show running-config failover&lt;BR /&gt;failover&lt;BR /&gt;failover lan unit primary&lt;BR /&gt;failover lan interface fo GigabitEthernet0/3&lt;BR /&gt;failover key *****&lt;BR /&gt;failover replication http&lt;BR /&gt;failover link fo GigabitEthernet0/3&lt;BR /&gt;failover interface ip fo 192.168.255.1 255.255.255.252 standby 192.168.255.2&lt;BR /&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The secondary firewall is configured identically except for failover lan unit secondary.&lt;/P&gt;&lt;P&gt;The failover interfaces are using a dedicated switch.&lt;/P&gt;</description>
      <pubDate>Tue, 12 Mar 2019 05:24:47 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-5512-sync-problems/m-p/2617551#M197504</guid>
      <dc:creator>cavazos.art</dc:creator>
      <dc:date>2019-03-12T05:24:47Z</dc:date>
    </item>
    <item>
      <title>Does show inventory on both</title>
      <link>https://community.cisco.com/t5/network-security/asa-5512-sync-problems/m-p/2617552#M197506</link>
      <description>&lt;P&gt;Does show inventory on both indicate identical hardware?&lt;/P&gt;&lt;P&gt;I assume you've checked your failover key.&lt;/P&gt;&lt;P&gt;Also, are both the units' failover links confirmed up/up and in the same VLAN on the dedicated switch?&lt;/P&gt;</description>
      <pubDate>Thu, 29 Jan 2015 00:46:44 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-5512-sync-problems/m-p/2617552#M197506</guid>
      <dc:creator>Marvin Rhoads</dc:creator>
      <dc:date>2015-01-29T00:46:44Z</dc:date>
    </item>
    <item>
      <title>Hello Marvin,We have</title>
      <link>https://community.cisco.com/t5/network-security/asa-5512-sync-problems/m-p/2617553#M197508</link>
      <description>&lt;P&gt;Hello Marvin,&lt;/P&gt;&lt;P&gt;We have identical hardware. The failover key is identical, and we are up/up on the correct VLAN of the dedicated switch.&lt;/P&gt;&lt;P&gt;What I am seeing now as the backup syncs, it reboots and starts over again. I get the sync complete message, and then it boots. Fortunately, we only have 4 pairs of 5512's in our environment. And they all behave the same way.&lt;/P&gt;&lt;P&gt;Our 5510's run great.&lt;/P&gt;&lt;P&gt;And our version on the 5512's is 8.6(1)2&lt;/P&gt;</description>
      <pubDate>Fri, 30 Jan 2015 16:40:47 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-5512-sync-problems/m-p/2617553#M197508</guid>
      <dc:creator>cavazos.art</dc:creator>
      <dc:date>2015-01-30T16:40:47Z</dc:date>
    </item>
    <item>
      <title>Hmm it sounds like you're</title>
      <link>https://community.cisco.com/t5/network-security/asa-5512-sync-problems/m-p/2617554#M197509</link>
      <description>&lt;P&gt;Hmm it sounds like you're setting it up properly.&lt;/P&gt;&lt;P&gt;Although I don't see any published bug affecting you, you could be hitting a bug as 8.6(1)2 was very early code on that platform. If it's rebooting it should be creating a crashdump info file on disk0: that you could use to open a TAC case.&lt;/P&gt;&lt;P&gt;They will most likely advise upgrading to a more current release - 9.1(5) or 9.2(3). Either one would require you to first go via 9.1(2) as a prerequisite. &lt;A href="http://www.cisco.com/c/en/us/td/docs/security/asa/asa91/release/notes/asarn91.html#pgfId-763574"&gt;Reference&lt;/A&gt;.&lt;/P&gt;</description>
      <pubDate>Fri, 30 Jan 2015 16:51:48 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-5512-sync-problems/m-p/2617554#M197509</guid>
      <dc:creator>Marvin Rhoads</dc:creator>
      <dc:date>2015-01-30T16:51:48Z</dc:date>
    </item>
    <item>
      <title>Thanks! I need to send a</title>
      <link>https://community.cisco.com/t5/network-security/asa-5512-sync-problems/m-p/2617555#M197511</link>
      <description>&lt;P&gt;Thanks! I need to send a field tech to console into the device and get the crashdump from his laptop. We have them disabled for now as the reboots drive our NMS nuts.&lt;/P&gt;</description>
      <pubDate>Fri, 30 Jan 2015 16:56:20 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-5512-sync-problems/m-p/2617555#M197511</guid>
      <dc:creator>cavazos.art</dc:creator>
      <dc:date>2015-01-30T16:56:20Z</dc:date>
    </item>
  </channel>
</rss>

