<?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: Border GW interface address configuration in Software-Defined Access (SD-Access)</title>
    <link>https://community.cisco.com/t5/software-defined-access-sd-access/border-gw-interface-address-configuration/m-p/4689251#M2000</link>
    <description>&lt;P&gt;Hi iores, it is used to seed a Border Node BGP route for the IP range within the SD-Access Fabric Site, this route is often advertised in EBGP from Border Node to external routing devices such as a fusion device. On the Border Node you'll see both a network statement for the loopback interface (which configured with the same IP address as an Anycast Gateway) and an BGP aggregate-address representing the whole Anycast Gateway IP range. Cheers, Jerome&lt;/P&gt;</description>
    <pubDate>Mon, 19 Sep 2022 00:04:39 GMT</pubDate>
    <dc:creator>jedolphi</dc:creator>
    <dc:date>2022-09-19T00:04:39Z</dc:date>
    <item>
      <title>Border GW interface address configuration</title>
      <link>https://community.cisco.com/t5/software-defined-access-sd-access/border-gw-interface-address-configuration/m-p/4684853#M1996</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;why border GW needs to have a loopback interface configured with the same IP address as anycast gateway?&lt;/P&gt;&lt;P&gt;As far as I understand, this is because the border GW needs to advertise this network to the external L3 network and by configuring loopback with the same IP address as anycast gateway tricks border GW to advertise the routes to endpoint subnets without really knowing the routes to them.&lt;/P&gt;&lt;P&gt;How border router doesn't know the routes to endpoints subnets although they are part of the same fabric?&lt;/P&gt;</description>
      <pubDate>Sun, 11 Sep 2022 11:19:08 GMT</pubDate>
      <guid>https://community.cisco.com/t5/software-defined-access-sd-access/border-gw-interface-address-configuration/m-p/4684853#M1996</guid>
      <dc:creator>iores</dc:creator>
      <dc:date>2022-09-11T11:19:08Z</dc:date>
    </item>
    <item>
      <title>Re: Border GW interface address configuration</title>
      <link>https://community.cisco.com/t5/software-defined-access-sd-access/border-gw-interface-address-configuration/m-p/4689251#M2000</link>
      <description>&lt;P&gt;Hi iores, it is used to seed a Border Node BGP route for the IP range within the SD-Access Fabric Site, this route is often advertised in EBGP from Border Node to external routing devices such as a fusion device. On the Border Node you'll see both a network statement for the loopback interface (which configured with the same IP address as an Anycast Gateway) and an BGP aggregate-address representing the whole Anycast Gateway IP range. Cheers, Jerome&lt;/P&gt;</description>
      <pubDate>Mon, 19 Sep 2022 00:04:39 GMT</pubDate>
      <guid>https://community.cisco.com/t5/software-defined-access-sd-access/border-gw-interface-address-configuration/m-p/4689251#M2000</guid>
      <dc:creator>jedolphi</dc:creator>
      <dc:date>2022-09-19T00:04:39Z</dc:date>
    </item>
  </channel>
</rss>

