<?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: Multi site SDA transit and internet access in Software-Defined Access (SD-Access)</title>
    <link>https://community.cisco.com/t5/software-defined-access-sd-access/multi-site-sda-transit-and-internet-access/m-p/5315244#M4125</link>
    <description>&lt;P&gt;Hi Kev, if it's Pub/Sub SDA Transit then local internet is always preferred over remote internet, so it should 'just work'. Please see Cisco Live presentation &lt;A href="https://www.ciscolive.com/on-demand/on-demand-library.html#/session/1750271924574001zt2d" target="_self"&gt;BRKENS-2816&lt;/A&gt; for detailed explanation.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Tue, 29 Jul 2025 11:36:45 GMT</pubDate>
    <dc:creator>jedolphi</dc:creator>
    <dc:date>2025-07-29T11:36:45Z</dc:date>
    <item>
      <title>Multi site SDA transit and internet access</title>
      <link>https://community.cisco.com/t5/software-defined-access-sd-access/multi-site-sda-transit-and-internet-access/m-p/5315214#M4124</link>
      <description>&lt;P&gt;Hi&lt;/P&gt;&lt;P&gt;We have 2 SDA fabrics.&amp;nbsp; Site A and site B.&amp;nbsp; Site A provides internet access for both sites at the moment.&amp;nbsp; We want to introduce a second internet pipe and site B solely for that site.&amp;nbsp; However, we want site A to provide fallback internet access should site B's pipe fail.&lt;/P&gt;&lt;P&gt;We have an SDA transit between the sites.&lt;/P&gt;&lt;P&gt;So the problem is, in short, each site must use its own internet pipe but site B must be able to use site A's in a failure scenario.&amp;nbsp; We have no need for Site A to ever use site B's internet pipe.&amp;nbsp; All I can imagine is it has something to do with Border priority and/or affinity but I have never used these parameters before.&lt;/P&gt;&lt;P&gt;Thanks as always, Kev.&lt;/P&gt;</description>
      <pubDate>Tue, 29 Jul 2025 10:28:32 GMT</pubDate>
      <guid>https://community.cisco.com/t5/software-defined-access-sd-access/multi-site-sda-transit-and-internet-access/m-p/5315214#M4124</guid>
      <dc:creator>KevinR99</dc:creator>
      <dc:date>2025-07-29T10:28:32Z</dc:date>
    </item>
    <item>
      <title>Re: Multi site SDA transit and internet access</title>
      <link>https://community.cisco.com/t5/software-defined-access-sd-access/multi-site-sda-transit-and-internet-access/m-p/5315244#M4125</link>
      <description>&lt;P&gt;Hi Kev, if it's Pub/Sub SDA Transit then local internet is always preferred over remote internet, so it should 'just work'. Please see Cisco Live presentation &lt;A href="https://www.ciscolive.com/on-demand/on-demand-library.html#/session/1750271924574001zt2d" target="_self"&gt;BRKENS-2816&lt;/A&gt; for detailed explanation.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 29 Jul 2025 11:36:45 GMT</pubDate>
      <guid>https://community.cisco.com/t5/software-defined-access-sd-access/multi-site-sda-transit-and-internet-access/m-p/5315244#M4125</guid>
      <dc:creator>jedolphi</dc:creator>
      <dc:date>2025-07-29T11:36:45Z</dc:date>
    </item>
    <item>
      <title>Re: Multi site SDA transit and internet access</title>
      <link>https://community.cisco.com/t5/software-defined-access-sd-access/multi-site-sda-transit-and-internet-access/m-p/5315253#M4126</link>
      <description>&lt;P&gt;Thank you Jerome.&amp;nbsp; I kind of thought that might be the case but thanks for the confirmation.&lt;/P&gt;</description>
      <pubDate>Tue, 29 Jul 2025 12:03:57 GMT</pubDate>
      <guid>https://community.cisco.com/t5/software-defined-access-sd-access/multi-site-sda-transit-and-internet-access/m-p/5315253#M4126</guid>
      <dc:creator>KevinR99</dc:creator>
      <dc:date>2025-07-29T12:03:57Z</dc:date>
    </item>
  </channel>
</rss>

