<?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: Adding switch stack to the SDA fabric using Autolan in Software-Defined Access (SD-Access)</title>
    <link>https://community.cisco.com/t5/software-defined-access-sd-access/adding-switch-stack-to-the-sda-fabric-using-autolan/m-p/3888023#M209</link>
    <description>&lt;P&gt;If your data cabling at the back of the switch stack is done correctly, then you do not need to configure anything. Assuming this is day 0 bring up and the switches (licensing and OS versions are same) are coming up for the first time out of the factory with PnP agent, the platform/system will decide who will become Active based on the lowest MAC address. When it calls home the PnP server/DNA Center,&amp;nbsp; PnP will set the priority of that switch to 10 to make it as Active member and to ensure that after further reloads the same switch becomes Active&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Example output below:&lt;/P&gt;
&lt;P&gt;na-poc-11#show switch detail &lt;BR /&gt;Switch/Stack Mac Address : 2c86.d239.ef00 - Local Mac Address&lt;BR /&gt;Mac persistency wait time: Indefinite&lt;BR /&gt;H/W Current&lt;BR /&gt;Switch# Role Mac Address Priority Version State &lt;BR /&gt;-------------------------------------------------------------------------------------&lt;BR /&gt;*1 Active 2c86.d239.ef00 &lt;STRONG&gt;10&lt;/STRONG&gt; V08 Ready &lt;BR /&gt;2 Standby 2c86.d245.ef00 1 V08 Ready &lt;BR /&gt;3 Member 2c86.d2be.fc80 1 V08 Ready&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Stack Port Status Neighbors &lt;BR /&gt;Switch# Port 1 Port 2 Port 1 Port 2 &lt;BR /&gt;--------------------------------------------------------&lt;BR /&gt;1 OK OK 2 3 &lt;BR /&gt;2 OK OK 3 1 &lt;BR /&gt;3 OK OK 1 2&lt;/P&gt;
&lt;P&gt;dna-poc-11#&lt;/P&gt;
&lt;P&gt;For details on the complete workflow not just the above refer to the below link&lt;/P&gt;
&lt;P&gt;Search for&amp;nbsp;(Stack Considerations)&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;A href="https://www.cisco.com/c/en/us/td/docs/cloud-systems-management/network-automation-and-management/dna-center/tech_notes/b_dnac_sda_lan_automation_deployment.html" target="_blank" rel="noopener"&gt;https://www.cisco.com/c/en/us/td/docs/cloud-systems-management/network-automation-and-management/dna-center/tech_notes/b_dnac_sda_lan_automation_deployment.html&lt;/A&gt;&lt;/P&gt;</description>
    <pubDate>Wed, 10 Jul 2019 22:51:21 GMT</pubDate>
    <dc:creator>Karthik Kumar Thatikonda</dc:creator>
    <dc:date>2019-07-10T22:51:21Z</dc:date>
    <item>
      <title>Adding switch stack to the SDA fabric using Autolan</title>
      <link>https://community.cisco.com/t5/software-defined-access-sd-access/adding-switch-stack-to-the-sda-fabric-using-autolan/m-p/3887556#M208</link>
      <description>&lt;P&gt;Hello&amp;nbsp;&lt;/P&gt;&lt;P&gt;Need to know the right order when using&amp;nbsp; DNA Autolan to build the underlay .&lt;/P&gt;&lt;P&gt;Is it to build the switch stack completely and then it will be discovered as a single entity during autolan process ? or do I need to connect one switch to the fabric and then after I build the underlay come back to switch and start adding to it the other stack members ?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;Hassan&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 10 Jul 2019 08:16:43 GMT</pubDate>
      <guid>https://community.cisco.com/t5/software-defined-access-sd-access/adding-switch-stack-to-the-sda-fabric-using-autolan/m-p/3887556#M208</guid>
      <dc:creator>hassan_yousif2005</dc:creator>
      <dc:date>2019-07-10T08:16:43Z</dc:date>
    </item>
    <item>
      <title>Re: Adding switch stack to the SDA fabric using Autolan</title>
      <link>https://community.cisco.com/t5/software-defined-access-sd-access/adding-switch-stack-to-the-sda-fabric-using-autolan/m-p/3888023#M209</link>
      <description>&lt;P&gt;If your data cabling at the back of the switch stack is done correctly, then you do not need to configure anything. Assuming this is day 0 bring up and the switches (licensing and OS versions are same) are coming up for the first time out of the factory with PnP agent, the platform/system will decide who will become Active based on the lowest MAC address. When it calls home the PnP server/DNA Center,&amp;nbsp; PnP will set the priority of that switch to 10 to make it as Active member and to ensure that after further reloads the same switch becomes Active&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Example output below:&lt;/P&gt;
&lt;P&gt;na-poc-11#show switch detail &lt;BR /&gt;Switch/Stack Mac Address : 2c86.d239.ef00 - Local Mac Address&lt;BR /&gt;Mac persistency wait time: Indefinite&lt;BR /&gt;H/W Current&lt;BR /&gt;Switch# Role Mac Address Priority Version State &lt;BR /&gt;-------------------------------------------------------------------------------------&lt;BR /&gt;*1 Active 2c86.d239.ef00 &lt;STRONG&gt;10&lt;/STRONG&gt; V08 Ready &lt;BR /&gt;2 Standby 2c86.d245.ef00 1 V08 Ready &lt;BR /&gt;3 Member 2c86.d2be.fc80 1 V08 Ready&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Stack Port Status Neighbors &lt;BR /&gt;Switch# Port 1 Port 2 Port 1 Port 2 &lt;BR /&gt;--------------------------------------------------------&lt;BR /&gt;1 OK OK 2 3 &lt;BR /&gt;2 OK OK 3 1 &lt;BR /&gt;3 OK OK 1 2&lt;/P&gt;
&lt;P&gt;dna-poc-11#&lt;/P&gt;
&lt;P&gt;For details on the complete workflow not just the above refer to the below link&lt;/P&gt;
&lt;P&gt;Search for&amp;nbsp;(Stack Considerations)&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;A href="https://www.cisco.com/c/en/us/td/docs/cloud-systems-management/network-automation-and-management/dna-center/tech_notes/b_dnac_sda_lan_automation_deployment.html" target="_blank" rel="noopener"&gt;https://www.cisco.com/c/en/us/td/docs/cloud-systems-management/network-automation-and-management/dna-center/tech_notes/b_dnac_sda_lan_automation_deployment.html&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 10 Jul 2019 22:51:21 GMT</pubDate>
      <guid>https://community.cisco.com/t5/software-defined-access-sd-access/adding-switch-stack-to-the-sda-fabric-using-autolan/m-p/3888023#M209</guid>
      <dc:creator>Karthik Kumar Thatikonda</dc:creator>
      <dc:date>2019-07-10T22:51:21Z</dc:date>
    </item>
    <item>
      <title>Re: Adding switch stack to the SDA fabric using Autolan</title>
      <link>https://community.cisco.com/t5/software-defined-access-sd-access/adding-switch-stack-to-the-sda-fabric-using-autolan/m-p/3889455#M212</link>
      <description>&lt;P&gt;Many thanks.&lt;/P&gt;</description>
      <pubDate>Fri, 12 Jul 2019 18:44:14 GMT</pubDate>
      <guid>https://community.cisco.com/t5/software-defined-access-sd-access/adding-switch-stack-to-the-sda-fabric-using-autolan/m-p/3889455#M212</guid>
      <dc:creator>hassan_yousif2005</dc:creator>
      <dc:date>2019-07-12T18:44:14Z</dc:date>
    </item>
  </channel>
</rss>

