<?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 Secondary ASA interface Flap when issue write Standby in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/secondary-asa-interface-flap-when-issue-write-standby/m-p/2246061#M357459</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello Ahmad,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Are you monitoring both units using syslogs? &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Do you get any message or syslog when the issue happens?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;- Eddy&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Sat, 25 May 2013 03:55:06 GMT</pubDate>
    <dc:creator>Eddy Duran</dc:creator>
    <dc:date>2013-05-25T03:55:06Z</dc:date>
    <item>
      <title>Secondary ASA interface Flap when issue write Standby</title>
      <link>https://community.cisco.com/t5/network-security/secondary-asa-interface-flap-when-issue-write-standby/m-p/2246060#M357457</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;i never see this before, but on newly purchased just configured firewall.&lt;/P&gt;&lt;P&gt;when i do wrtie standby.&lt;/P&gt;&lt;P&gt;All interfaces on standby unit flaps.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;is it some IOS bug? my firewalls are &lt;/P&gt;&lt;P&gt;Hardware:&amp;nbsp;&amp;nbsp; ASA5525, 8192 MB RAM, CPU Lynnfield 2394 MHz, 1 CPU (4 cores)&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; ASA: 4096 MB RAM, 1 CPU (1 core)&lt;/P&gt;&lt;P&gt;and image &lt;/P&gt;&lt;P&gt;asa861-2-smp-k8.bin&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;what could be the reason? FYI i am using lan base failover and not doing any statful failover.&lt;/P&gt;</description>
      <pubDate>Tue, 12 Mar 2019 01:49:03 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/secondary-asa-interface-flap-when-issue-write-standby/m-p/2246060#M357457</guid>
      <dc:creator>ahmad82pkn</dc:creator>
      <dc:date>2019-03-12T01:49:03Z</dc:date>
    </item>
    <item>
      <title>Secondary ASA interface Flap when issue write Standby</title>
      <link>https://community.cisco.com/t5/network-security/secondary-asa-interface-flap-when-issue-write-standby/m-p/2246061#M357459</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello Ahmad,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Are you monitoring both units using syslogs? &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Do you get any message or syslog when the issue happens?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;- Eddy&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 25 May 2013 03:55:06 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/secondary-asa-interface-flap-when-issue-write-standby/m-p/2246061#M357459</guid>
      <dc:creator>Eddy Duran</dc:creator>
      <dc:date>2013-05-25T03:55:06Z</dc:date>
    </item>
    <item>
      <title>Secondary ASA interface Flap when issue write Standby</title>
      <link>https://community.cisco.com/t5/network-security/secondary-asa-interface-flap-when-issue-write-standby/m-p/2246062#M357460</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt; Hi Ahmad,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This is expected behavior and when we issue the command "write standby", we see the device configuration getting erased and then re-configured from the active device. Device goes in the Sync config and Bulk Sync state in transition. Here is more info regarding the same : &lt;/P&gt;&lt;P&gt;&lt;A href="http://www.cisco.com/en/US/docs/security/asa/asa84/command/reference/uz.html#wp1668246"&gt;write standby&lt;/A&gt;&lt;/P&gt;&lt;P&gt;. This is a misleading message and a cosmetic issue is filed with this defect id : &lt;/P&gt;&lt;P&gt;&lt;A href="http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;amp;bugId=CSCuc63634"&gt;CSCuc63634&lt;/A&gt;&amp;nbsp; &lt;SPAN id="mce_marker"&gt; &lt;/SPAN&gt;&lt;SPAN style="font-family: &amp;quot;Calibri&amp;quot;,&amp;quot;sans-serif&amp;quot;; color: black; font-size: 10.5pt; mso-fareast-font-family: 'Times New Roman'; mso-bidi-font-family: 'Times New Roman'; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA;"&gt;This is expected behavior and when we issue the command "write standby", we see the device configuration getting erased and then re-configured from the active device. Device goes in the Sync config and Bulk Sync state in transition. Here is more info regarding the same : &lt;A href="http://www.cisco.com/en/US/docs/security/asa/asa84/command/reference/uz.html#wp1668246"&gt;write standby&lt;/A&gt;. This is a misleading message and a cosmetic issue is filed with this defect id : &lt;A href="http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;amp;bugId=CSCuc63634"&gt;&lt;SPAN style="color: #800080;"&gt;&lt;/SPAN&gt;&lt;/A&gt;&lt;A href="https://www.cisco.com/cisco/psn/bssprt/bss?searchType=bstbugidsearch&amp;amp;page=bstBugDetail&amp;amp;BugID=CSCuc63634" target="_blank"&gt;CSCuc63634&lt;/A&gt;&lt;/SPAN&gt;&amp;nbsp; &lt;SPAN style="font-family: &amp;quot;Calibri&amp;quot;,&amp;quot;sans-serif&amp;quot;; color: black; font-size: 11pt; mso-fareast-font-family: 'Times New Roman'; mso-bidi-font-family: 'Times New Roman'; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA;"&gt; &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: &amp;quot;Calibri&amp;quot;,&amp;quot;sans-serif&amp;quot;; color: black; font-size: 11pt; mso-fareast-font-family: 'Times New Roman'; mso-bidi-font-family: 'Times New Roman'; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA;"&gt; &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: &amp;quot;Calibri&amp;quot;,&amp;quot;sans-serif&amp;quot;; color: black; font-size: 11pt; mso-fareast-font-family: 'Times New Roman'; mso-bidi-font-family: 'Times New Roman'; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA;"&gt;Due to the configuration being removed and re-applied we saw the link flap on the standby devices.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: &amp;quot;Calibri&amp;quot;,&amp;quot;sans-serif&amp;quot;; color: black; font-size: 11pt; mso-fareast-font-family: 'Times New Roman'; mso-bidi-font-family: 'Times New Roman'; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA;"&gt; &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: &amp;quot;Calibri&amp;quot;,&amp;quot;sans-serif&amp;quot;; color: black; font-size: 11pt; mso-fareast-font-family: 'Times New Roman'; mso-bidi-font-family: 'Times New Roman'; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA;"&gt;Please rate this if helpful.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: &amp;quot;Calibri&amp;quot;,&amp;quot;sans-serif&amp;quot;; color: black; font-size: 11pt; mso-fareast-font-family: 'Times New Roman'; mso-bidi-font-family: 'Times New Roman'; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA;"&gt; &lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 25 May 2013 14:28:26 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/secondary-asa-interface-flap-when-issue-write-standby/m-p/2246062#M357460</guid>
      <dc:creator>Sanjay Shaw</dc:creator>
      <dc:date>2013-05-25T14:28:26Z</dc:date>
    </item>
    <item>
      <title>Secondary ASA interface Flap when issue write Standby</title>
      <link>https://community.cisco.com/t5/network-security/secondary-asa-interface-flap-when-issue-write-standby/m-p/2246063#M357462</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;thank you for the information, though this behavior would be new for me, since i never saw this on my dozen pair which are in production, May be something with new generation ASA series.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 27 May 2013 22:45:54 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/secondary-asa-interface-flap-when-issue-write-standby/m-p/2246063#M357462</guid>
      <dc:creator>ahmad82pkn</dc:creator>
      <dc:date>2013-05-27T22:45:54Z</dc:date>
    </item>
  </channel>
</rss>

