<?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 Rebooting the standby ASA in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/rebooting-the-standby-asa/m-p/2417734#M270501</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt; Hi Julio,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Active ASA had following symptons during that time&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1&amp;gt;not assigning DHCP IP to users.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;2&amp;gt;&lt;/P&gt;&lt;P&gt;sh run on Active ASA&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;it gives error&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;ERROR: Command Ignored, Configuration in progress...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;MAhesh&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Sun, 02 Feb 2014 05:11:39 GMT</pubDate>
    <dc:creator>mahesh18</dc:creator>
    <dc:date>2014-02-02T05:11:39Z</dc:date>
    <item>
      <title>Rebooting the standby ASA</title>
      <link>https://community.cisco.com/t5/network-security/rebooting-the-standby-asa/m-p/2417726#M270493</link>
      <description>&lt;P&gt;Hi Everyone,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If ASA is in active / standby failover.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;And for some reason if you need to reboot standby ASA is it good practice just to reboot standby?&lt;/P&gt;&lt;P&gt;If standby is rebooted should it syn all the config over failover link from active ASA?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Mahesh&lt;/P&gt;</description>
      <pubDate>Tue, 12 Mar 2019 03:39:03 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/rebooting-the-standby-asa/m-p/2417726#M270493</guid>
      <dc:creator>mahesh18</dc:creator>
      <dc:date>2019-03-12T03:39:03Z</dc:date>
    </item>
    <item>
      <title>Rebooting the standby ASA</title>
      <link>https://community.cisco.com/t5/network-security/rebooting-the-standby-asa/m-p/2417727#M270494</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;To reload the standby unit, on the primary unit issue the command&lt;STRONG&gt; failover reload-standby&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Once the standby unit is back online&amp;nbsp; a full running config synch will take place from the active ASA to the standby ASA.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-- &lt;BR /&gt;Please remember to rate and select a correct answer&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 01 Feb 2014 20:26:04 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/rebooting-the-standby-asa/m-p/2417727#M270494</guid>
      <dc:creator>Marius Gunnerud</dc:creator>
      <dc:date>2014-02-01T20:26:04Z</dc:date>
    </item>
    <item>
      <title>Rebooting the standby ASA</title>
      <link>https://community.cisco.com/t5/network-security/rebooting-the-standby-asa/m-p/2417728#M270495</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt; Hi Marius,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We did the reboot of standby ASA and log shows&lt;/P&gt;&lt;P&gt;(Secondary) Beginning configuration replication: Receiving from mate.&lt;/P&gt;&lt;P&gt;******REPLICATION OF CONFIGURATION FROM ACTIVE TO STANDBY UNIT IS INCOMPLETE,&lt;BR /&gt; TO PREVENT THE STANDBY UNIT TAKING OVER AS ACTIVE WITH A PARTIAL CONFIGURATION,&lt;BR /&gt; THE STANDBY UNIT WILL NOW REBOOT*******&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So now ASA is in booting loop and it boots up gives the above message and again reboot.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Can you tell why this is happening?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For now we have turned off standby asa.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;MAhesh&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 02 Feb 2014 01:23:44 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/rebooting-the-standby-asa/m-p/2417728#M270495</guid>
      <dc:creator>mahesh18</dc:creator>
      <dc:date>2014-02-02T01:23:44Z</dc:date>
    </item>
    <item>
      <title>Rebooting the standby ASA</title>
      <link>https://community.cisco.com/t5/network-security/rebooting-the-standby-asa/m-p/2417729#M270496</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Mahesh &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This can happen sometimes when the standby firewall does not accept one or more of the commands in the configuration coming from the active firewall. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Have there been any configuration changes made to the active firewall recently ? &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is that all you see in the log or do you see the standby complaining about certain lines in the configuration ? &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Jon&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 02 Feb 2014 01:57:16 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/rebooting-the-standby-asa/m-p/2417729#M270496</guid>
      <dc:creator>Jon Marshall</dc:creator>
      <dc:date>2014-02-02T01:57:16Z</dc:date>
    </item>
    <item>
      <title>Rebooting the standby ASA</title>
      <link>https://community.cisco.com/t5/network-security/rebooting-the-standby-asa/m-p/2417730#M270497</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt; Hi John,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thats all we see in logs from standby ASA.&lt;/P&gt;&lt;P&gt;Its not complaining about any lines in the config.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Standby ASA boots up fine when it is not connected to Active ASA.&lt;/P&gt;&lt;P&gt;As soon as we connect the standby to active ASA it gives above log message and reboot&amp;nbsp; also then active ASA is not&lt;/P&gt;&lt;P&gt;reachable over the network.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Currently standby ASA is powered down.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;About recent changes to ASA i am checking on that.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;MAhesh&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 02 Feb 2014 02:15:09 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/rebooting-the-standby-asa/m-p/2417730#M270497</guid>
      <dc:creator>mahesh18</dc:creator>
      <dc:date>2014-02-02T02:15:09Z</dc:date>
    </item>
    <item>
      <title>Rebooting the standby ASA</title>
      <link>https://community.cisco.com/t5/network-security/rebooting-the-standby-asa/m-p/2417731#M270498</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello Mahesh,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You sure that is the only log you see when the issue arises?? Get a console connection to the firewall and make sure you are logging everything.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The mismatch configuration should be shown to you by the ASA.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;As soon as you see the lines posted back to us and we will analize them.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Looking for some Networking Assistance?&amp;nbsp; &lt;BR /&gt;&lt;SPAN&gt;Contact me directly at &lt;/SPAN&gt;&lt;A class="jive-link-email-small" href="mailto:jcarvaja@laguiadelnetworking.com"&gt;jcarvaja@laguiadelnetworking.com&lt;/A&gt;&lt;SPAN&gt; &lt;/SPAN&gt;&lt;BR /&gt; &lt;BR /&gt;I will fix your problem ASAP. &lt;BR /&gt; &lt;BR /&gt;Cheers, &lt;BR /&gt; &lt;BR /&gt;Julio Carvajal Segura &lt;BR /&gt;&lt;A class="jive-link-external-small" href="http://laguiadelnetworking.com"&gt;http://laguiadelnetworking.com&lt;/A&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 02 Feb 2014 03:12:47 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/rebooting-the-standby-asa/m-p/2417731#M270498</guid>
      <dc:creator>Julio Carvajal</dc:creator>
      <dc:date>2014-02-02T03:12:47Z</dc:date>
    </item>
    <item>
      <title>Rebooting the standby ASA</title>
      <link>https://community.cisco.com/t5/network-security/rebooting-the-standby-asa/m-p/2417732#M270499</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt; Hi Julio,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;After above logs it shows&lt;/P&gt;&lt;P&gt;%ASA-1-105020: (Secondary) Incomplete/slow config replication&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; ***&lt;BR /&gt;*** --- SHUTDOWN NOW ---&lt;BR /&gt;***&lt;BR /&gt;*** Message to all terminals:&lt;BR /&gt;***&lt;BR /&gt;***&amp;nbsp;&amp;nbsp; failover reset&lt;BR /&gt;Process shutdown finished&lt;BR /&gt;Rebooting.....&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;Booting system, please wait...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;That was happening again and again.&lt;/P&gt;&lt;P&gt;Currently standby ASA is powered off .&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;There were no errors for config changes in the logs of standby ASA.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;MAhesh&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 02 Feb 2014 03:33:42 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/rebooting-the-standby-asa/m-p/2417732#M270499</guid>
      <dc:creator>mahesh18</dc:creator>
      <dc:date>2014-02-02T03:33:42Z</dc:date>
    </item>
    <item>
      <title>Rebooting the standby ASA</title>
      <link>https://community.cisco.com/t5/network-security/rebooting-the-standby-asa/m-p/2417733#M270500</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Okey and what about on the Active firewall at the time of the issue?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Looking for some Networking Assistance?&amp;nbsp; &lt;BR /&gt;&lt;SPAN&gt;Contact me directly at &lt;/SPAN&gt;&lt;A class="jive-link-email-small" href="mailto:jcarvaja@laguiadelnetworking.com"&gt;jcarvaja@laguiadelnetworking.com&lt;/A&gt;&lt;SPAN&gt; &lt;/SPAN&gt;&lt;BR /&gt; &lt;BR /&gt;I will fix your problem ASAP. &lt;BR /&gt; &lt;BR /&gt;Cheers, &lt;BR /&gt; &lt;BR /&gt;Julio Carvajal Segura &lt;BR /&gt;&lt;A class="jive-link-external-small" href="http://laguiadelnetworking.com"&gt;http://laguiadelnetworking.com&lt;/A&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 02 Feb 2014 03:41:41 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/rebooting-the-standby-asa/m-p/2417733#M270500</guid>
      <dc:creator>Julio Carvajal</dc:creator>
      <dc:date>2014-02-02T03:41:41Z</dc:date>
    </item>
    <item>
      <title>Rebooting the standby ASA</title>
      <link>https://community.cisco.com/t5/network-security/rebooting-the-standby-asa/m-p/2417734#M270501</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt; Hi Julio,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Active ASA had following symptons during that time&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1&amp;gt;not assigning DHCP IP to users.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;2&amp;gt;&lt;/P&gt;&lt;P&gt;sh run on Active ASA&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;it gives error&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;ERROR: Command Ignored, Configuration in progress...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;MAhesh&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 02 Feb 2014 05:11:39 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/rebooting-the-standby-asa/m-p/2417734#M270501</guid>
      <dc:creator>mahesh18</dc:creator>
      <dc:date>2014-02-02T05:11:39Z</dc:date>
    </item>
    <item>
      <title>Rebooting the standby ASA</title>
      <link>https://community.cisco.com/t5/network-security/rebooting-the-standby-asa/m-p/2417735#M270502</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello Mahesh,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Okey but do you see any logs in the console session?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Did you really console in to the box to see all the logs?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;console logging 7&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It's because I have seen this behavior before and on all the cases I worked I saw a configuration command not properly written&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Looking for some Networking Assistance?&amp;nbsp; &lt;BR /&gt;&lt;SPAN&gt;Contact me directly at &lt;/SPAN&gt;&lt;A class="jive-link-email-small" href="mailto:jcarvaja@laguiadelnetworking.com"&gt;jcarvaja@laguiadelnetworking.com&lt;/A&gt;&lt;SPAN&gt; &lt;/SPAN&gt;&lt;BR /&gt; &lt;BR /&gt;I will fix your problem ASAP. &lt;BR /&gt; &lt;BR /&gt;Cheers, &lt;BR /&gt; &lt;BR /&gt;Julio Carvajal Segura &lt;BR /&gt;&lt;A class="jive-link-external-small" href="http://laguiadelnetworking.com"&gt;http://laguiadelnetworking.com&lt;/A&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 02 Feb 2014 05:35:41 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/rebooting-the-standby-asa/m-p/2417735#M270502</guid>
      <dc:creator>Julio Carvajal</dc:creator>
      <dc:date>2014-02-02T05:35:41Z</dc:date>
    </item>
    <item>
      <title>Rebooting the standby ASA</title>
      <link>https://community.cisco.com/t5/network-security/rebooting-the-standby-asa/m-p/2417736#M270503</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Which ASA model are you using for both of the ASAs?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is this the first time you are trying to setup Active/Standby failover for these two units?&amp;nbsp; If not is this the first time you are seeing this type of issue?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What ASA version are the ASAs running?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;As Julio has mentioned, this is most likely the cause of the standby not accepting one or more of the configurations the Active unit is trying to sync across.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-- &lt;BR /&gt;Please remember to rate and select a correct answer&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 02 Feb 2014 19:26:50 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/rebooting-the-standby-asa/m-p/2417736#M270503</guid>
      <dc:creator>Marius Gunnerud</dc:creator>
      <dc:date>2014-02-02T19:26:50Z</dc:date>
    </item>
    <item>
      <title>Rebooting the standby ASA</title>
      <link>https://community.cisco.com/t5/network-security/rebooting-the-standby-asa/m-p/2417737#M270504</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt; Hi MArius,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Active/standby failover was working fine from last few years.&lt;/P&gt;&lt;P&gt;This issue occur first time.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Model is&amp;nbsp; ASA5520.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Version is&amp;nbsp; 8.0(5)28.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;MAhesh&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 05 Feb 2014 22:11:40 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/rebooting-the-standby-asa/m-p/2417737#M270504</guid>
      <dc:creator>mahesh18</dc:creator>
      <dc:date>2014-02-05T22:11:40Z</dc:date>
    </item>
    <item>
      <title>Rebooting the standby ASA</title>
      <link>https://community.cisco.com/t5/network-security/rebooting-the-standby-asa/m-p/2417738#M270505</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;What you could try doing is remove the failover configuration from the standby unit, make a copy of the Active ASA config (copy paste into notepad) and then copy the configuration to the standby unit approx. 10 lines at a time and see where the configuration is failing to be accepted.&amp;nbsp; Just remember to add the failover commands last.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Are both ASA's running the same version?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-- &lt;BR /&gt;Please remember to rate and select a correct answer&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 06 Feb 2014 07:17:47 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/rebooting-the-standby-asa/m-p/2417738#M270505</guid>
      <dc:creator>Marius Gunnerud</dc:creator>
      <dc:date>2014-02-06T07:17:47Z</dc:date>
    </item>
    <item>
      <title>Rebooting the standby ASA</title>
      <link>https://community.cisco.com/t5/network-security/rebooting-the-standby-asa/m-p/2417739#M270506</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt; Hi Marius,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;YEs both ASA have same version.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Seems we will add only failover cable from active to standby first and see how it behaves.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;MAhesh&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 06 Feb 2014 13:04:46 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/rebooting-the-standby-asa/m-p/2417739#M270506</guid>
      <dc:creator>mahesh18</dc:creator>
      <dc:date>2014-02-06T13:04:46Z</dc:date>
    </item>
    <item>
      <title>Rebooting the standby ASA</title>
      <link>https://community.cisco.com/t5/network-security/rebooting-the-standby-asa/m-p/2417740#M270507</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt; Hi Marius,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I added the standby firewall with failovcer cable first and it worked fine.&lt;/P&gt;&lt;P&gt;After that i added all the other cables.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;All is good now.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 07 Feb 2014 19:26:12 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/rebooting-the-standby-asa/m-p/2417740#M270507</guid>
      <dc:creator>mahesh18</dc:creator>
      <dc:date>2014-02-07T19:26:12Z</dc:date>
    </item>
    <item>
      <title>Re: Rebooting the standby ASA</title>
      <link>https://community.cisco.com/t5/network-security/rebooting-the-standby-asa/m-p/3778910#M270508</link>
      <description>&lt;P&gt;&lt;STRONG&gt;"This active FWSM was sending its configuration to the standby FWSM and wouldn't accept configuration changes."&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;I received this error&amp;nbsp;message after I&amp;nbsp;created&amp;nbsp; some new ACL rules on my FWSM and tried to apply the change. I&amp;nbsp;used&amp;nbsp;the '&lt;STRONG&gt;failover suspend-config-sync&lt;/STRONG&gt;'&amp;nbsp;&amp;nbsp;and saved the running-config to flash, then&amp;nbsp; '&lt;STRONG&gt;no&amp;nbsp;failover suspend-config-sync&lt;/STRONG&gt;' but the problem is still there. I appreciate your help to fix this issue, thank you.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="FWSM faileover-status.JPG" style="width: 999px;"&gt;&lt;img src="https://community.cisco.com/t5/image/serverpage/image-id/27705i3573FB36CBFD5EEA/image-size/large?v=v2&amp;amp;px=999" role="button" title="FWSM faileover-status.JPG" alt="FWSM faileover-status.JPG" /&gt;&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 14 Jan 2019 09:16:50 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/rebooting-the-standby-asa/m-p/3778910#M270508</guid>
      <dc:creator>Elshaday G</dc:creator>
      <dc:date>2019-01-14T09:16:50Z</dc:date>
    </item>
  </channel>
</rss>

