<?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 Deployment and multicast in Software-Defined Access (SD-Access)</title>
    <link>https://community.cisco.com/t5/software-defined-access-sd-access/sda-deployment-and-multicast/m-p/3997850#M419</link>
    <description>&lt;P&gt;Hi all:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;One of our customer is thinking to implement SDA into their network but still some doubts for IoT (OT) deployments due to multicast/broadcst traffic.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Let me elaborate.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;These are the requirements from customer&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;1.- IOT PLC devices use broadcast traffic&lt;/P&gt;
&lt;P&gt;2.- These IoT devices use a WoL (Wake on LAN) mechanism for switch-on/switch-off from a server outside the fabric.&lt;/P&gt;
&lt;P&gt;3.- IP Static addressing and it can’t be changed for these PLC’s&lt;/P&gt;
&lt;P&gt;4.- PLC’s has just one IP and they talk to other PLC’s (depending on PLC type, these are assigned in a different VLAN, then One VLAN per type of PLC, BUT all them talk to each other) and the Application servers.&lt;/P&gt;
&lt;P&gt;5.- Default Gateway for PLC’s is an External Firewall.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Customer already know that SDA supports broadcast and multicast but he wants to be sure 100% that SDA met the requirements.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Are we fully compliant with these requirements?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Do we have any Case Study with SDA and Manufacturing with IOT PLC devices connected in FE’s and Extended Nodes?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks in advance.&lt;/P&gt;
&lt;P&gt;Jesus&lt;/P&gt;</description>
    <pubDate>Thu, 12 Dec 2019 11:16:28 GMT</pubDate>
    <dc:creator>jmoliner</dc:creator>
    <dc:date>2019-12-12T11:16:28Z</dc:date>
    <item>
      <title>SDA Deployment and multicast</title>
      <link>https://community.cisco.com/t5/software-defined-access-sd-access/sda-deployment-and-multicast/m-p/3997850#M419</link>
      <description>&lt;P&gt;Hi all:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;One of our customer is thinking to implement SDA into their network but still some doubts for IoT (OT) deployments due to multicast/broadcst traffic.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Let me elaborate.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;These are the requirements from customer&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;1.- IOT PLC devices use broadcast traffic&lt;/P&gt;
&lt;P&gt;2.- These IoT devices use a WoL (Wake on LAN) mechanism for switch-on/switch-off from a server outside the fabric.&lt;/P&gt;
&lt;P&gt;3.- IP Static addressing and it can’t be changed for these PLC’s&lt;/P&gt;
&lt;P&gt;4.- PLC’s has just one IP and they talk to other PLC’s (depending on PLC type, these are assigned in a different VLAN, then One VLAN per type of PLC, BUT all them talk to each other) and the Application servers.&lt;/P&gt;
&lt;P&gt;5.- Default Gateway for PLC’s is an External Firewall.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Customer already know that SDA supports broadcast and multicast but he wants to be sure 100% that SDA met the requirements.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Are we fully compliant with these requirements?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Do we have any Case Study with SDA and Manufacturing with IOT PLC devices connected in FE’s and Extended Nodes?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks in advance.&lt;/P&gt;
&lt;P&gt;Jesus&lt;/P&gt;</description>
      <pubDate>Thu, 12 Dec 2019 11:16:28 GMT</pubDate>
      <guid>https://community.cisco.com/t5/software-defined-access-sd-access/sda-deployment-and-multicast/m-p/3997850#M419</guid>
      <dc:creator>jmoliner</dc:creator>
      <dc:date>2019-12-12T11:16:28Z</dc:date>
    </item>
    <item>
      <title>Re: SDA Deployment and multicast</title>
      <link>https://community.cisco.com/t5/software-defined-access-sd-access/sda-deployment-and-multicast/m-p/4035274#M525</link>
      <description>&lt;P&gt;You are referring to what we call L2 Flooding in SD-Access.&lt;/P&gt;
&lt;P&gt;This is used to support numerous use cases as such the one you point out.&lt;/P&gt;
&lt;P&gt;See here for more information regarding this topic.&lt;BR /&gt;&lt;A href="https://community.cisco.com/t5/networking-documents/cisco-sd-access-layer2-flooding/ta-p/3943916" target="_blank"&gt;https://community.cisco.com/t5/networking-documents/cisco-sd-access-layer2-flooding/ta-p/3943916&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 25 Feb 2020 09:49:25 GMT</pubDate>
      <guid>https://community.cisco.com/t5/software-defined-access-sd-access/sda-deployment-and-multicast/m-p/4035274#M525</guid>
      <dc:creator>ldanny</dc:creator>
      <dc:date>2020-02-25T09:49:25Z</dc:date>
    </item>
  </channel>
</rss>

