<?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: Fusion Router in Software-Defined Access (SD-Access)</title>
    <link>https://community.cisco.com/t5/software-defined-access-sd-access/fusion-router/m-p/3830926#M69</link>
    <description>&lt;P&gt;Hi Scott,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;That make sense. Appreciate you taking the time to respond to my query.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Many thanks&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Tue, 02 Apr 2019 19:56:16 GMT</pubDate>
    <dc:creator>dm2020</dc:creator>
    <dc:date>2019-04-02T19:56:16Z</dc:date>
    <item>
      <title>Fusion Router</title>
      <link>https://community.cisco.com/t5/software-defined-access-sd-access/fusion-router/m-p/3830419#M67</link>
      <description>&lt;P&gt;Hi All,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I'm currently deploying a small pilot SDA fabric for a company. A question has been raised about the need for the fusion router. Now I know what the purpose of the fusion router is, however, is it mandatory in every deployment as we can achieve the same route leaking between VRFs on the border nodes which I have tested without any issues. What are the reasons that we should use a dedicated router for this?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;</description>
      <pubDate>Tue, 02 Apr 2019 08:11:08 GMT</pubDate>
      <guid>https://community.cisco.com/t5/software-defined-access-sd-access/fusion-router/m-p/3830419#M67</guid>
      <dc:creator>dm2020</dc:creator>
      <dc:date>2019-04-02T08:11:08Z</dc:date>
    </item>
    <item>
      <title>Re: Fusion Router</title>
      <link>https://community.cisco.com/t5/software-defined-access-sd-access/fusion-router/m-p/3830873#M68</link>
      <description>&lt;P&gt;The Fusion is a Best Practice recommendation to move VRF route leaking and / or VRF combining off the Fabric Border to avoid unintended redistributions (especially 0.0.0.0/0 routes) into the LISP Control Plane that could be harmful to the SD-Access fabric. That said, it is not a requirement to have a Fusion device, and an SD-Access fabric without a Fusion is TAC supported.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;If your production SD-Access fabric will have a Fusion device, then it is my experience that the pilot should also have a Fusion device. This is so that the Pilot can mimick the production environment as closely as possible so that testing will be most applicable to what is ultimately deployed.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Remember that Fusion device can also be a firewall, if that fits into your design.&lt;/P&gt;</description>
      <pubDate>Tue, 02 Apr 2019 18:16:06 GMT</pubDate>
      <guid>https://community.cisco.com/t5/software-defined-access-sd-access/fusion-router/m-p/3830873#M68</guid>
      <dc:creator>Scott Hodgdon</dc:creator>
      <dc:date>2019-04-02T18:16:06Z</dc:date>
    </item>
    <item>
      <title>Re: Fusion Router</title>
      <link>https://community.cisco.com/t5/software-defined-access-sd-access/fusion-router/m-p/3830926#M69</link>
      <description>&lt;P&gt;Hi Scott,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;That make sense. Appreciate you taking the time to respond to my query.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Many thanks&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 02 Apr 2019 19:56:16 GMT</pubDate>
      <guid>https://community.cisco.com/t5/software-defined-access-sd-access/fusion-router/m-p/3830926#M69</guid>
      <dc:creator>dm2020</dc:creator>
      <dc:date>2019-04-02T19:56:16Z</dc:date>
    </item>
    <item>
      <title>Re: Fusion Router</title>
      <link>https://community.cisco.com/t5/software-defined-access-sd-access/fusion-router/m-p/3831130#M70</link>
      <description>&lt;P&gt;Not required, it is only needed to reach specific destinations outside the SD-Fabric, for example, a DC or Enteprise network out of the LISP/Fabric domain, with an eBGP session between a Border and a Fusion which has route information of the enterprise network, you can redistribute IGP routes to a LISP MS/MR.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;To leak between VRFs on the fabric, a border node running MPBGP and Route target imports is good enough.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;In a future, this feature should be addressed by LISP Extranet.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 03 Apr 2019 05:24:23 GMT</pubDate>
      <guid>https://community.cisco.com/t5/software-defined-access-sd-access/fusion-router/m-p/3831130#M70</guid>
      <dc:creator>jalejand</dc:creator>
      <dc:date>2019-04-03T05:24:23Z</dc:date>
    </item>
    <item>
      <title>Re: Fusion Router</title>
      <link>https://community.cisco.com/t5/software-defined-access-sd-access/fusion-router/m-p/4146272#M835</link>
      <description>&lt;P&gt;Hi, am also facing the same issue, where fusion router is being mentioned mandatory by the vendor.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Could you please share the topology or assets you use for the SD-access fabric and device which you used for interconnecting SDA fabric and traditional network?&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I have attached underlay setup diagram.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;THanks in advance.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 04 Sep 2020 09:24:13 GMT</pubDate>
      <guid>https://community.cisco.com/t5/software-defined-access-sd-access/fusion-router/m-p/4146272#M835</guid>
      <dc:creator>vk00455130</dc:creator>
      <dc:date>2020-09-04T09:24:13Z</dc:date>
    </item>
  </channel>
</rss>

