<?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 By default there is no reload in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/asa-failover-behaviour/m-p/3082018#M146115</link>
    <description>&lt;P&gt;By default there is no reload. The newly standby unit just monitors and is ready to again take over the active role if needed.&lt;/P&gt;</description>
    <pubDate>Thu, 02 Mar 2017 17:28:22 GMT</pubDate>
    <dc:creator>Karsten Iwen</dc:creator>
    <dc:date>2017-03-02T17:28:22Z</dc:date>
    <item>
      <title>ASA Failover behaviour</title>
      <link>https://community.cisco.com/t5/network-security/asa-failover-behaviour/m-p/3082017#M146114</link>
      <description>&lt;P&gt;quick question please.&lt;/P&gt;
&lt;P&gt;&lt;SPAN style="color: #1f497d;"&gt;When standby unit become active for &lt;SPAN style="text-decoration: underline;"&gt;any reason (of course except HW failure)&lt;/SPAN&gt;, does it force its mate to reload?&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN style="color: #1f497d;"&gt;&lt;/SPAN&gt;&lt;SPAN style="color: #1f497d;"&gt;more like when sec/stby becomes sec/act for any reason&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN style="color: #1f497d;"&gt;does the sec/act force pri/stby to reload?&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN style="color: #1f497d;"&gt;or the pri/stby remain working in monitor?&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN style="color: #1f497d;"&gt;Thanks,&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN style="color: #1f497d;"&gt;&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 12 Mar 2019 09:00:17 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-failover-behaviour/m-p/3082017#M146114</guid>
      <dc:creator>Hassan Chalabi</dc:creator>
      <dc:date>2019-03-12T09:00:17Z</dc:date>
    </item>
    <item>
      <title>By default there is no reload</title>
      <link>https://community.cisco.com/t5/network-security/asa-failover-behaviour/m-p/3082018#M146115</link>
      <description>&lt;P&gt;By default there is no reload. The newly standby unit just monitors and is ready to again take over the active role if needed.&lt;/P&gt;</description>
      <pubDate>Thu, 02 Mar 2017 17:28:22 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-failover-behaviour/m-p/3082018#M146115</guid>
      <dc:creator>Karsten Iwen</dc:creator>
      <dc:date>2017-03-02T17:28:22Z</dc:date>
    </item>
    <item>
      <title>Thank you very much, do you</title>
      <link>https://community.cisco.com/t5/network-security/asa-failover-behaviour/m-p/3082019#M146117</link>
      <description>&lt;P&gt;Thank you very much, do you have a reference?&lt;/P&gt;</description>
      <pubDate>Thu, 02 Mar 2017 17:45:21 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-failover-behaviour/m-p/3082019#M146117</guid>
      <dc:creator>Hassan Chalabi</dc:creator>
      <dc:date>2017-03-02T17:45:21Z</dc:date>
    </item>
    <item>
      <title>no reference for exactly this</title>
      <link>https://community.cisco.com/t5/network-security/asa-failover-behaviour/m-p/3082020#M146120</link>
      <description>&lt;P&gt;no reference for exactly this behavior. But the general documentation for FO:&lt;/P&gt;
&lt;P&gt;http://www.cisco.com/c/en/us/td/docs/security/asa/asa96/configuration/general/asa-96-general-config/ha-failover.html&lt;/P&gt;</description>
      <pubDate>Thu, 02 Mar 2017 17:57:45 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-failover-behaviour/m-p/3082020#M146120</guid>
      <dc:creator>Karsten Iwen</dc:creator>
      <dc:date>2017-03-02T17:57:45Z</dc:date>
    </item>
  </channel>
</rss>

