<?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 Re: Anyconnect dual ISP in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/anyconnect-dual-isp/m-p/3922048#M24593</link>
    <description>&lt;P&gt;True, but our second connection (which is really our 3rd connection has bandwidth limit (1GB)) and we need to keep our monthly bandwidth for a real disaster.&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;</description>
    <pubDate>Tue, 10 Sep 2019 19:31:51 GMT</pubDate>
    <dc:creator>eandcciscoadmin</dc:creator>
    <dc:date>2019-09-10T19:31:51Z</dc:date>
    <item>
      <title>Anyconnect dual ISP</title>
      <link>https://community.cisco.com/t5/network-security/anyconnect-dual-isp/m-p/3921825#M24591</link>
      <description>&lt;P&gt;Hello everyone,&lt;/P&gt;&lt;P&gt;I have a Cisco ASA configured with Dual ISP failover. The failover and failback after first ISP port shutdown and turning back on, works fine. I have a concern about Anyconnect connections after failover. Is there a way for&amp;nbsp; ASA to disconnect all Anyconnect users after failback to main ISP automatically?&lt;/P&gt;&lt;P&gt;By "automatically" I mean that I don't have to intervene and kill all the connections by myslef but ASA detects that main ISP is back on line and kills all second ISP Anyconnect connections.&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Ramin&lt;/P&gt;</description>
      <pubDate>Tue, 10 Sep 2019 14:45:03 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/anyconnect-dual-isp/m-p/3921825#M24591</guid>
      <dc:creator>eandcciscoadmin</dc:creator>
      <dc:date>2019-09-10T14:45:03Z</dc:date>
    </item>
    <item>
      <title>Re: Anyconnect dual ISP</title>
      <link>https://community.cisco.com/t5/network-security/anyconnect-dual-isp/m-p/3921917#M24592</link>
      <description>&lt;P&gt;When you clear the AnyConnect sessions, you also disturb your users work. I prefer in these scenarios to let the users continue their work on the secondary ISP connection and when they connect the next time they'll again use the primary connection.&lt;/P&gt;
&lt;P&gt;All in all, it seems to me more user-friendly.&lt;/P&gt;</description>
      <pubDate>Tue, 10 Sep 2019 16:26:43 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/anyconnect-dual-isp/m-p/3921917#M24592</guid>
      <dc:creator>Karsten Iwen</dc:creator>
      <dc:date>2019-09-10T16:26:43Z</dc:date>
    </item>
    <item>
      <title>Re: Anyconnect dual ISP</title>
      <link>https://community.cisco.com/t5/network-security/anyconnect-dual-isp/m-p/3922048#M24593</link>
      <description>&lt;P&gt;True, but our second connection (which is really our 3rd connection has bandwidth limit (1GB)) and we need to keep our monthly bandwidth for a real disaster.&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;</description>
      <pubDate>Tue, 10 Sep 2019 19:31:51 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/anyconnect-dual-isp/m-p/3922048#M24593</guid>
      <dc:creator>eandcciscoadmin</dc:creator>
      <dc:date>2019-09-10T19:31:51Z</dc:date>
    </item>
    <item>
      <title>Re: Anyconnect dual ISP</title>
      <link>https://community.cisco.com/t5/network-security/anyconnect-dual-isp/m-p/3922066#M24594</link>
      <description>&lt;P&gt;I think you could automate that with an Embedded Event Manager script.&lt;/P&gt;</description>
      <pubDate>Tue, 10 Sep 2019 20:04:58 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/anyconnect-dual-isp/m-p/3922066#M24594</guid>
      <dc:creator>Karsten Iwen</dc:creator>
      <dc:date>2019-09-10T20:04:58Z</dc:date>
    </item>
    <item>
      <title>Re: Anyconnect dual ISP</title>
      <link>https://community.cisco.com/t5/network-security/anyconnect-dual-isp/m-p/3942816#M24595</link>
      <description>&lt;P&gt;Thanks Karsten, I tied the event manager to interface status change from up to down Syslog (411002) with "noconfirm" option which immediately kills all Anyconnect connections.&lt;/P&gt;&lt;P&gt;Thanks for the hint.&lt;/P&gt;&lt;P&gt;Ramin&lt;/P&gt;</description>
      <pubDate>Thu, 17 Oct 2019 20:04:38 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/anyconnect-dual-isp/m-p/3942816#M24595</guid>
      <dc:creator>eandcciscoadmin</dc:creator>
      <dc:date>2019-10-17T20:04:38Z</dc:date>
    </item>
  </channel>
</rss>

