<?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: SDAccess address planning for underlay, onboarding, loopbacks, etc. in Software-Defined Access (SD-Access)</title>
    <link>https://community.cisco.com/t5/software-defined-access-sd-access/sdaccess-address-planning-for-underlay-onboarding-loopbacks-etc/m-p/4136836#M760</link>
    <description>&lt;P&gt;Please read through the following:&lt;/P&gt;
&lt;P&gt;&lt;A href="https://www.cisco.com/c/en/us/td/docs/solutions/CVD/Campus/cisco-sda-design-guide.html#SDAccessDesignConsiderations" target="_blank"&gt;https://www.cisco.com/c/en/us/td/docs/solutions/CVD/Campus/cisco-sda-design-guide.html#SDAccessDesignConsiderations&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;Look at the LAN Design Principles, I believe it would answer your doubts.&lt;/P&gt;</description>
    <pubDate>Mon, 17 Aug 2020 12:20:38 GMT</pubDate>
    <dc:creator>sandjose</dc:creator>
    <dc:date>2020-08-17T12:20:38Z</dc:date>
    <item>
      <title>SDAccess address planning for underlay, onboarding, loopbacks, etc.</title>
      <link>https://community.cisco.com/t5/software-defined-access-sd-access/sdaccess-address-planning-for-underlay-onboarding-loopbacks-etc/m-p/4136381#M759</link>
      <description>&lt;P&gt;Hello all,&lt;/P&gt;&lt;P&gt;The company I work for uses SDAccess and I am trying to figure out how it has been setup, since I inherited the management of the whole infra.&lt;/P&gt;&lt;P&gt;The deployment consists of several fabrics controlled by a single DNAC. The fabrics are connected by "IP Transits" in SDA parlance. Cisco ASAs are used in each fabric (or branch) as fusion routers, with IPsec tunnels connecting to the main HQ where dnac resides.&lt;/P&gt;&lt;P&gt;I cannot get my head around the criteria used to assign the prefixes. I see for example an "onboarding" vlan assigned in each branch. Then there's the loopback0, with its own address. Then again the underlay, with yet another prefix.&lt;/P&gt;&lt;P&gt;I see a lot of dense documentation is available on the Cisco website, yet I cannot seem to find a document that guides the user through proper address planning for such a distributed setup.&lt;/P&gt;&lt;P&gt;Could you please point me to such document? Thanks!&lt;/P&gt;</description>
      <pubDate>Sat, 15 Aug 2020 21:07:44 GMT</pubDate>
      <guid>https://community.cisco.com/t5/software-defined-access-sd-access/sdaccess-address-planning-for-underlay-onboarding-loopbacks-etc/m-p/4136381#M759</guid>
      <dc:creator>nicov84</dc:creator>
      <dc:date>2020-08-15T21:07:44Z</dc:date>
    </item>
    <item>
      <title>Re: SDAccess address planning for underlay, onboarding, loopbacks, etc.</title>
      <link>https://community.cisco.com/t5/software-defined-access-sd-access/sdaccess-address-planning-for-underlay-onboarding-loopbacks-etc/m-p/4136836#M760</link>
      <description>&lt;P&gt;Please read through the following:&lt;/P&gt;
&lt;P&gt;&lt;A href="https://www.cisco.com/c/en/us/td/docs/solutions/CVD/Campus/cisco-sda-design-guide.html#SDAccessDesignConsiderations" target="_blank"&gt;https://www.cisco.com/c/en/us/td/docs/solutions/CVD/Campus/cisco-sda-design-guide.html#SDAccessDesignConsiderations&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;Look at the LAN Design Principles, I believe it would answer your doubts.&lt;/P&gt;</description>
      <pubDate>Mon, 17 Aug 2020 12:20:38 GMT</pubDate>
      <guid>https://community.cisco.com/t5/software-defined-access-sd-access/sdaccess-address-planning-for-underlay-onboarding-loopbacks-etc/m-p/4136836#M760</guid>
      <dc:creator>sandjose</dc:creator>
      <dc:date>2020-08-17T12:20:38Z</dc:date>
    </item>
  </channel>
</rss>

