<?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 Transmitting Received BGP routes with AS in tact in ExtremeSwitching (EXOS/Switch Engine)</title>
    <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/transmitting-received-bgp-routes-with-as-in-tact/m-p/44923#M11108</link>
    <description>I am having an issue with what appears to be two networks that are advertised to me via BGP..one is pretty standard and the other one is maybe a little less typical. I receive the route from an EBGP peer for a /24 and it goes into our routing table. When I advertise these upstream, there is no record of the source ASN. To complicate things further, one of the peers is using a SWIP'd range which is fine but it is part of an aggregate network that we advertise. I have an advertisement policy that removes that from the summary but so far that doesn't seem to be working.&lt;BR /&gt;
&lt;BR /&gt;
To recap, networks that I receive via an EBGP customer are not being transmitted to other EBGP peers even when permitted and I am hoping to retain the ASN so that when it gets further upstream it has the full AS-path.&lt;BR /&gt;
&lt;BR /&gt;
Let me know what details I can share but so far I'm not finding any gtac guides or any similar requests on the community site. Thank you!</description>
    <pubDate>Mon, 19 Nov 2018 23:43:00 GMT</pubDate>
    <dc:creator>nesuser2</dc:creator>
    <dc:date>2018-11-19T23:43:00Z</dc:date>
    <item>
      <title>Transmitting Received BGP routes with AS in tact</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/transmitting-received-bgp-routes-with-as-in-tact/m-p/44923#M11108</link>
      <description>I am having an issue with what appears to be two networks that are advertised to me via BGP..one is pretty standard and the other one is maybe a little less typical. I receive the route from an EBGP peer for a /24 and it goes into our routing table. When I advertise these upstream, there is no record of the source ASN. To complicate things further, one of the peers is using a SWIP'd range which is fine but it is part of an aggregate network that we advertise. I have an advertisement policy that removes that from the summary but so far that doesn't seem to be working.&lt;BR /&gt;
&lt;BR /&gt;
To recap, networks that I receive via an EBGP customer are not being transmitted to other EBGP peers even when permitted and I am hoping to retain the ASN so that when it gets further upstream it has the full AS-path.&lt;BR /&gt;
&lt;BR /&gt;
Let me know what details I can share but so far I'm not finding any gtac guides or any similar requests on the community site. Thank you!</description>
      <pubDate>Mon, 19 Nov 2018 23:43:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/transmitting-received-bgp-routes-with-as-in-tact/m-p/44923#M11108</guid>
      <dc:creator>nesuser2</dc:creator>
      <dc:date>2018-11-19T23:43:00Z</dc:date>
    </item>
    <item>
      <title>RE: Transmitting Received BGP routes with AS in tact</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/transmitting-received-bgp-routes-with-as-in-tact/m-p/44924#M11109</link>
      <description>Can you post the running configuration of bgp</description>
      <pubDate>Tue, 27 Nov 2018 04:46:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/transmitting-received-bgp-routes-with-as-in-tact/m-p/44924#M11109</guid>
      <dc:creator>Padmashree_Naga</dc:creator>
      <dc:date>2018-11-27T04:46:00Z</dc:date>
    </item>
    <item>
      <title>RE: Transmitting Received BGP routes with AS in tact</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/transmitting-received-bgp-routes-with-as-in-tact/m-p/44925#M11110</link>
      <description>Padmashree, Thanks for your reply. I think I found a few things out which might help the community...some might not.&lt;BR /&gt;
&lt;BR /&gt;
The ultimate cure was to add:&lt;BR /&gt;
configure bgp add network SMALLERSUB/NET&lt;BR /&gt;
&lt;BR /&gt;
modify aggregate address to remove SMALLERSUB/NET from aggregation:&lt;BR /&gt;
configure bgp add aggregate-address LARGERSUB/NET summary-only advertise-policy RemoveSummary&lt;BR /&gt;
&lt;BR /&gt;
edit RemoveSummary.pol&lt;BR /&gt;
entry removefromsummary {&lt;BR /&gt;
        if match any {&lt;BR /&gt;
                nlri SMALLERSUB/NET exact;&lt;BR /&gt;
        } then {&lt;BR /&gt;
                deny;&lt;BR /&gt;
        }&lt;BR /&gt;
}&lt;BR /&gt;
&lt;BR /&gt;
entry accept_others {&lt;BR /&gt;
        if { } then {&lt;BR /&gt;
                permit;&lt;BR /&gt;
        }&lt;BR /&gt;
}&lt;BR /&gt;
&lt;BR /&gt;
Last but not least, one of my routers was routers was kicking out the route received from an ebgp peer..haven't had the time to look at release notes but I suspect it is a previously addressed bug. &lt;BR /&gt;
&lt;BR /&gt;
Hope this info helps somebody!&lt;BR /&gt;
&lt;BR /&gt;</description>
      <pubDate>Tue, 27 Nov 2018 04:55:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/transmitting-received-bgp-routes-with-as-in-tact/m-p/44925#M11110</guid>
      <dc:creator>nesuser2</dc:creator>
      <dc:date>2018-11-27T04:55:00Z</dc:date>
    </item>
  </channel>
</rss>

