<?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 SDA Border Node design consideration with a stack in Software-Defined Access (SD-Access)</title>
    <link>https://community.cisco.com/t5/software-defined-access-sd-access/sda-border-node-design-consideration-with-a-stack/m-p/5545711#M4376</link>
    <description>&lt;P&gt;Hi Experts,&lt;/P&gt;&lt;P&gt;I am new to SD-Access solution. Is it a good practice to have stack of Border Node for a small site?&lt;/P&gt;&lt;P&gt;I came across a post stating -it is not good&amp;nbsp;&lt;SPAN&gt;to have BN stacked as you lose hitless SWIM for site (assuming u have single pair of BN &amp;amp; FN there).&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Can anyone clarify this? we have a single Fusion node and a stack of BN.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Thank you in advance!&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Thu, 16 Apr 2026 06:25:35 GMT</pubDate>
    <dc:creator>Rupesh Patil</dc:creator>
    <dc:date>2026-04-16T06:25:35Z</dc:date>
    <item>
      <title>SDA Border Node design consideration with a stack</title>
      <link>https://community.cisco.com/t5/software-defined-access-sd-access/sda-border-node-design-consideration-with-a-stack/m-p/5545711#M4376</link>
      <description>&lt;P&gt;Hi Experts,&lt;/P&gt;&lt;P&gt;I am new to SD-Access solution. Is it a good practice to have stack of Border Node for a small site?&lt;/P&gt;&lt;P&gt;I came across a post stating -it is not good&amp;nbsp;&lt;SPAN&gt;to have BN stacked as you lose hitless SWIM for site (assuming u have single pair of BN &amp;amp; FN there).&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Can anyone clarify this? we have a single Fusion node and a stack of BN.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Thank you in advance!&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 16 Apr 2026 06:25:35 GMT</pubDate>
      <guid>https://community.cisco.com/t5/software-defined-access-sd-access/sda-border-node-design-consideration-with-a-stack/m-p/5545711#M4376</guid>
      <dc:creator>Rupesh Patil</dc:creator>
      <dc:date>2026-04-16T06:25:35Z</dc:date>
    </item>
    <item>
      <title>Re: SDA Border Node design consideration with a stack</title>
      <link>https://community.cisco.com/t5/software-defined-access-sd-access/sda-border-node-design-consideration-with-a-stack/m-p/5545726#M4377</link>
      <description>&lt;P&gt;for a small (usually office only) sites single stackwised BN is pretty Ok (maintenance window is easy to schedule, right?).&lt;BR /&gt;but for business critical sites &amp;gt;1 BNs are of good practice. FN redundancy should be aligned as well.&lt;BR /&gt;there is also use-case with L2-BN deviating form this practice afaik - overlapping VLA&amp;lt;-&amp;gt;EID-space mapping will create disaster.&lt;/P&gt;</description>
      <pubDate>Thu, 16 Apr 2026 07:04:30 GMT</pubDate>
      <guid>https://community.cisco.com/t5/software-defined-access-sd-access/sda-border-node-design-consideration-with-a-stack/m-p/5545726#M4377</guid>
      <dc:creator>Andrii Oliinyk</dc:creator>
      <dc:date>2026-04-16T07:04:30Z</dc:date>
    </item>
    <item>
      <title>Re: SDA Border Node design consideration with a stack</title>
      <link>https://community.cisco.com/t5/software-defined-access-sd-access/sda-border-node-design-consideration-with-a-stack/m-p/5545731#M4378</link>
      <description>&lt;P&gt;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/293790"&gt;@Andrii Oliinyk&lt;/a&gt;&amp;nbsp;Thank you!&lt;/P&gt;</description>
      <pubDate>Thu, 16 Apr 2026 07:13:32 GMT</pubDate>
      <guid>https://community.cisco.com/t5/software-defined-access-sd-access/sda-border-node-design-consideration-with-a-stack/m-p/5545731#M4378</guid>
      <dc:creator>Rupesh Patil</dc:creator>
      <dc:date>2026-04-16T07:13:32Z</dc:date>
    </item>
  </channel>
</rss>

