<?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 Rohan,&amp;quot;state&amp;quot; refers to the in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/failover-link/m-p/2673725#M190871</link>
    <description>&lt;P&gt;Rohan,&lt;/P&gt;&lt;P&gt;"state" refers to the status of certain elements in the active&amp;nbsp;ASA's memory that&amp;nbsp;represent, generally speaking, connections through it and resources currently allocated. Most commonly we think of things like the NAT table, TCP connections and UDP flow "state". A complete list of the things that are included is in the configuration guide (&lt;A href="http://www.cisco.com/c/en/us/td/docs/security/asa/asa94/configuration/general/asa-general-cli/ha-failover.html#pgfId-1495008"&gt;link&lt;/A&gt;).&lt;/P&gt;&lt;P&gt;When we replicate those elements from the active to the standby unit, that is considered stateful. The link used to do so can be the same one as is used for "basic" (stateless) failover or it can be a dedicated one.&amp;nbsp;&lt;/P&gt;&lt;P&gt;By using stateful failover we minimize the impact to data flows when a failover occurs. The goal&amp;nbsp;is to not lose any and not even cause a TCP session&amp;nbsp;to be reset or UDP packet to be lost.&lt;/P&gt;</description>
    <pubDate>Mon, 08 Jun 2015 05:50:35 GMT</pubDate>
    <dc:creator>Marvin Rhoads</dc:creator>
    <dc:date>2015-06-08T05:50:35Z</dc:date>
    <item>
      <title>failover link</title>
      <link>https://community.cisco.com/t5/network-security/failover-link/m-p/2673724#M190869</link>
      <description>&lt;P&gt;what is the differnce between failover link and stateful failover link&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;and also between stateful and stateless&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 12 Mar 2019 06:04:07 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/failover-link/m-p/2673724#M190869</guid>
      <dc:creator>rohan jadhav</dc:creator>
      <dc:date>2019-03-12T06:04:07Z</dc:date>
    </item>
    <item>
      <title>Rohan,"state" refers to the</title>
      <link>https://community.cisco.com/t5/network-security/failover-link/m-p/2673725#M190871</link>
      <description>&lt;P&gt;Rohan,&lt;/P&gt;&lt;P&gt;"state" refers to the status of certain elements in the active&amp;nbsp;ASA's memory that&amp;nbsp;represent, generally speaking, connections through it and resources currently allocated. Most commonly we think of things like the NAT table, TCP connections and UDP flow "state". A complete list of the things that are included is in the configuration guide (&lt;A href="http://www.cisco.com/c/en/us/td/docs/security/asa/asa94/configuration/general/asa-general-cli/ha-failover.html#pgfId-1495008"&gt;link&lt;/A&gt;).&lt;/P&gt;&lt;P&gt;When we replicate those elements from the active to the standby unit, that is considered stateful. The link used to do so can be the same one as is used for "basic" (stateless) failover or it can be a dedicated one.&amp;nbsp;&lt;/P&gt;&lt;P&gt;By using stateful failover we minimize the impact to data flows when a failover occurs. The goal&amp;nbsp;is to not lose any and not even cause a TCP session&amp;nbsp;to be reset or UDP packet to be lost.&lt;/P&gt;</description>
      <pubDate>Mon, 08 Jun 2015 05:50:35 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/failover-link/m-p/2673725#M190871</guid>
      <dc:creator>Marvin Rhoads</dc:creator>
      <dc:date>2015-06-08T05:50:35Z</dc:date>
    </item>
  </channel>
</rss>

