<?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 Failover link in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/failover-link/m-p/5351032#M1123672</link>
    <description>&lt;P&gt;Hi team,&lt;/P&gt;
&lt;P&gt;Is it failover and stateful link in Cisco Fw high availability configuration sufficient for configuration and connection synchronization between active and passive devices ?&lt;/P&gt;</description>
    <pubDate>Mon, 01 Dec 2025 07:02:08 GMT</pubDate>
    <dc:creator>Vishal6</dc:creator>
    <dc:date>2025-12-01T07:02:08Z</dc:date>
    <item>
      <title>Failover link</title>
      <link>https://community.cisco.com/t5/network-security/failover-link/m-p/5351032#M1123672</link>
      <description>&lt;P&gt;Hi team,&lt;/P&gt;
&lt;P&gt;Is it failover and stateful link in Cisco Fw high availability configuration sufficient for configuration and connection synchronization between active and passive devices ?&lt;/P&gt;</description>
      <pubDate>Mon, 01 Dec 2025 07:02:08 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/failover-link/m-p/5351032#M1123672</guid>
      <dc:creator>Vishal6</dc:creator>
      <dc:date>2025-12-01T07:02:08Z</dc:date>
    </item>
    <item>
      <title>Re: Failover link</title>
      <link>https://community.cisco.com/t5/network-security/failover-link/m-p/5351390#M1123683</link>
      <description>&lt;P&gt;What exactly is your question? What platform?&lt;/P&gt;</description>
      <pubDate>Mon, 01 Dec 2025 21:25:33 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/failover-link/m-p/5351390#M1123683</guid>
      <dc:creator>ahollifield</dc:creator>
      <dc:date>2025-12-01T21:25:33Z</dc:date>
    </item>
    <item>
      <title>Re: Failover link</title>
      <link>https://community.cisco.com/t5/network-security/failover-link/m-p/5352291#M1123732</link>
      <description>&lt;P&gt;Does stateful link performs connection synchronizaton between devices ?&amp;nbsp;&lt;/P&gt;
&lt;P&gt;We have failover and stateful link, does flapping or down link status of failover link impact our High availability between devices or it breaks ?&lt;/P&gt;</description>
      <pubDate>Thu, 04 Dec 2025 10:06:02 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/failover-link/m-p/5352291#M1123732</guid>
      <dc:creator>Vishal6</dc:creator>
      <dc:date>2025-12-04T10:06:02Z</dc:date>
    </item>
    <item>
      <title>Re: Failover link</title>
      <link>https://community.cisco.com/t5/network-security/failover-link/m-p/5352293#M1123733</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;&amp;nbsp; &amp;nbsp;Session synchronisation happens over "State link" while everything else happens over "High Availability link". Ideally use a port-channel and assign both roles (State Link and High Availability Link) to it, this way you have physical redundancy built-in for both roles.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;If "State Link" fails you'll loose session synchronisation. If "High Availability Link" fails and you don't have standby addresses configured on at last one data interface that is UP and monitored you'll end up in split-brain scenario, while if you do have standby addresses configured there'll be no split-brain. FTD's need to reach each other at layer 2 over monitored links where you have standby addresses configured.&lt;/P&gt;
&lt;P&gt;Thanks,&lt;/P&gt;
&lt;P&gt;Cristian.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 04 Dec 2025 10:17:29 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/failover-link/m-p/5352293#M1123733</guid>
      <dc:creator>Cristian Matei</dc:creator>
      <dc:date>2025-12-04T10:17:29Z</dc:date>
    </item>
    <item>
      <title>Re: Failover link</title>
      <link>https://community.cisco.com/t5/network-security/failover-link/m-p/5352330#M1123739</link>
      <description>&lt;P&gt;Yes, the stateful failover (state link) is responsible to synchronize all the sessions information of the supported features shown in the link below. On the other side, the failover link (control link) is responsible to share the failover information between the two peers. If you loose the state link nothing will be impacted as long as the active role doesn't move to the secondary device.&lt;/P&gt;
&lt;P&gt;&lt;A href="https://www.cisco.com/c/en/us/td/docs/security/asa/asa919/configuration/general/asa-919-general-config/ha-failover.html" target="_blank"&gt;CLI Book 1: Cisco Secure Firewall ASA Series General Operations CLI Configuration Guide, 9.19 - Failover for High Availability [Cisco Secure Firewall ASA] - Cisco&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;However, if you happen to have the state link down and at the same time a failover happens between the devices and the secondary device becomes the active, then all the sessions that were already established through the previous active firewall now need to be reinitiated.&lt;/P&gt;
&lt;P&gt;With regard to the control link, if that breaks between the two peers then both of them will be acting as the active device which will most likely cause an outage or at least an intermittent outage on your network.&lt;/P&gt;</description>
      <pubDate>Thu, 04 Dec 2025 11:41:29 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/failover-link/m-p/5352330#M1123739</guid>
      <dc:creator>Aref Alsouqi</dc:creator>
      <dc:date>2025-12-04T11:41:29Z</dc:date>
    </item>
    <item>
      <title>Re: Failover link</title>
      <link>https://community.cisco.com/t5/network-security/failover-link/m-p/5352359#M1123747</link>
      <description>&lt;P&gt;Do you mean to this way.&lt;/P&gt;
&lt;P&gt;interface GigabitEthernet0/4&lt;BR /&gt;description FO-ST&lt;BR /&gt;speed 1000&lt;BR /&gt;duplex full&lt;BR /&gt;channel-group 15 mode active&lt;/P&gt;
&lt;P&gt;interface GigabitEthernet0/5&lt;BR /&gt;description FO-ST&lt;BR /&gt;speed 1000&lt;BR /&gt;duplex full&lt;BR /&gt;channel-group 15 mode active&lt;/P&gt;
&lt;P&gt;interface Port-channel15&lt;BR /&gt;nameif HA&lt;BR /&gt;security-level 0&lt;BR /&gt;ip address 203.0.113.10 255.255.255.252 standby 203.0.113.11&lt;/P&gt;
&lt;P&gt;&lt;BR /&gt;failover link fa interface ip address 2.2.2.1 255.255.255.252 2.2.2.2&lt;BR /&gt;stateful link St interface ip address 1.1.1.1 255.255.255.252 1.1.1.2&lt;/P&gt;</description>
      <pubDate>Thu, 04 Dec 2025 13:15:44 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/failover-link/m-p/5352359#M1123747</guid>
      <dc:creator>Vishal6</dc:creator>
      <dc:date>2025-12-04T13:15:44Z</dc:date>
    </item>
    <item>
      <title>Re: Failover link</title>
      <link>https://community.cisco.com/t5/network-security/failover-link/m-p/5352360#M1123748</link>
      <description>&lt;P&gt;if stateful link fails? does Failover link performs job of stateful link ?&lt;/P&gt;</description>
      <pubDate>Thu, 04 Dec 2025 13:16:22 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/failover-link/m-p/5352360#M1123748</guid>
      <dc:creator>Vishal6</dc:creator>
      <dc:date>2025-12-04T13:16:22Z</dc:date>
    </item>
    <item>
      <title>Re: Failover link</title>
      <link>https://community.cisco.com/t5/network-security/failover-link/m-p/5352380#M1123751</link>
      <description>&lt;P&gt;No, each link is responsible for a different set of tasks. The state link is for sessions synchronization, and the control link is for the failover control traffic such as unite state, hello messages, etc.&lt;/P&gt;</description>
      <pubDate>Thu, 04 Dec 2025 14:00:07 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/failover-link/m-p/5352380#M1123751</guid>
      <dc:creator>Aref Alsouqi</dc:creator>
      <dc:date>2025-12-04T14:00:07Z</dc:date>
    </item>
    <item>
      <title>Re: Failover link</title>
      <link>https://community.cisco.com/t5/network-security/failover-link/m-p/5352385#M1123753</link>
      <description>&lt;P&gt;You would need to specify the port channel in the commands "failover lan interface fa" and "failover link st" to be port channel 15. Also, please keep in mind that you can't have any configs that aren't related to the HA on that port channel.&lt;/P&gt;</description>
      <pubDate>Thu, 04 Dec 2025 14:15:38 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/failover-link/m-p/5352385#M1123753</guid>
      <dc:creator>Aref Alsouqi</dc:creator>
      <dc:date>2025-12-04T14:15:38Z</dc:date>
    </item>
    <item>
      <title>Re: Failover link</title>
      <link>https://community.cisco.com/t5/network-security/failover-link/m-p/5352671#M1123767</link>
      <description>&lt;P&gt;Would&amp;nbsp; be port channel configuration without any ip?&lt;/P&gt;</description>
      <pubDate>Fri, 05 Dec 2025 12:48:20 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/failover-link/m-p/5352671#M1123767</guid>
      <dc:creator>Vishal6</dc:creator>
      <dc:date>2025-12-05T12:48:20Z</dc:date>
    </item>
    <item>
      <title>Re: Failover link</title>
      <link>https://community.cisco.com/t5/network-security/failover-link/m-p/5352675#M1123769</link>
      <description>&lt;P&gt;You don't need any IP configuration for the HA interface(s).&lt;/P&gt;</description>
      <pubDate>Fri, 05 Dec 2025 13:17:52 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/failover-link/m-p/5352675#M1123769</guid>
      <dc:creator>Aref Alsouqi</dc:creator>
      <dc:date>2025-12-05T13:17:52Z</dc:date>
    </item>
  </channel>
</rss>

