<?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: IPv6 IBGP Loopback peering in ExtremeSwitching (EXOS/Switch Engine)</title>
    <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/ipv6-ibgp-loopback-peering/m-p/16687#M411</link>
    <description>The problem was caused by ipv6-unicast capability was not enabled on both ibgp switches.&lt;BR /&gt;
&lt;A href="https://gtacknowledge.extremenetworks.com/articles/Solution/Bgp-ipv6-networks-not-transmitted-to-bgp-neighbor" target="_blank" rel="nofollow noreferrer noopener"&gt;https://gtacknowledge.extremenetworks.com/articles/Solution/Bgp-ipv6-networks-not-transmitted-to-bgp...&lt;/A&gt;&lt;BR /&gt;
&lt;BR /&gt;</description>
    <pubDate>Thu, 24 Aug 2017 12:20:00 GMT</pubDate>
    <dc:creator>OscarK</dc:creator>
    <dc:date>2017-08-24T12:20:00Z</dc:date>
    <item>
      <title>IPv6 IBGP Loopback peering</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/ipv6-ibgp-loopback-peering/m-p/16685#M409</link>
      <description>I'm trying to setup ibgp ipv6 between two x460-g2 running version 22.2.1.5-patch1-4 &lt;BR /&gt;
&lt;BR /&gt;
I have two ebgpipv6 neigh on one router and one ibgp ipv6 neigh on the other router.&lt;BR /&gt;
&lt;BR /&gt;
The router with ebgp receives  a default :./0 from the upstream provider. &lt;BR /&gt;
&lt;BR /&gt;
I annononce the default route route thru ebgp to a customer just fine.&lt;BR /&gt;
&lt;BR /&gt;
&lt;B&gt;Ex &lt;/B&gt;&lt;BR /&gt;
enable bgp neighbor X address-family ipv6-unicast originate-default&lt;BR /&gt;
&lt;BR /&gt;
However between the ibgp speakers nothing is announced. &lt;BR /&gt;
Since it's ibgp I have a igp ( ospv3) that has full connectivity between the ibgp routers I can ping and have reachability between the ipv6 loopback interfaces ( that I have assigned) &lt;BR /&gt;
&lt;BR /&gt;
&lt;B&gt;Below is the snippet of the bgp config &lt;/B&gt;&lt;BR /&gt;
create bgp neighbor X remote-AS-number 12345&lt;BR /&gt;
enable bgp neighbor X&lt;BR /&gt;
disable bgp neighbor X capability ipv4-unicast&lt;BR /&gt;
disable bgp neighbor X capability ipv4-multicast&lt;BR /&gt;
configure bgp neighbor X address-family ipv6-unicast send-community both&lt;BR /&gt;
enable bgp neighbor X address-family ipv6-unicast soft-in-reset&lt;BR /&gt;
configure bgp neighbor X source-interface ipaddress X&lt;BR /&gt;
&lt;BR /&gt;
I can mention that the exact same thing works like a charm with ipv4. &lt;BR /&gt;
The default I get from the upstream is announced to my ibgp peer and I peer over the loopbacks. &lt;BR /&gt;
&lt;BR /&gt;
Can you see any errors or mistakes ?&lt;BR /&gt;
If not I will open a case. &lt;BR /&gt;
&lt;BR /&gt;</description>
      <pubDate>Thu, 17 Aug 2017 19:39:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/ipv6-ibgp-loopback-peering/m-p/16685#M409</guid>
      <dc:creator>andreas1</dc:creator>
      <dc:date>2017-08-17T19:39:00Z</dc:date>
    </item>
    <item>
      <title>RE: IPv6 IBGP Loopback peering</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/ipv6-ibgp-loopback-peering/m-p/16686#M410</link>
      <description>Hi,&lt;BR /&gt;
&lt;BR /&gt;
I usually like to check what one peer is sending and what the other is receiving, but you may want to check your next-hop first (next-hop self).&lt;BR /&gt;</description>
      <pubDate>Fri, 18 Aug 2017 00:30:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/ipv6-ibgp-loopback-peering/m-p/16686#M410</guid>
      <dc:creator>Stephane_Grosj1</dc:creator>
      <dc:date>2017-08-18T00:30:00Z</dc:date>
    </item>
    <item>
      <title>RE: IPv6 IBGP Loopback peering</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/ipv6-ibgp-loopback-peering/m-p/16687#M411</link>
      <description>The problem was caused by ipv6-unicast capability was not enabled on both ibgp switches.&lt;BR /&gt;
&lt;A href="https://gtacknowledge.extremenetworks.com/articles/Solution/Bgp-ipv6-networks-not-transmitted-to-bgp-neighbor" target="_blank" rel="nofollow noreferrer noopener"&gt;https://gtacknowledge.extremenetworks.com/articles/Solution/Bgp-ipv6-networks-not-transmitted-to-bgp...&lt;/A&gt;&lt;BR /&gt;
&lt;BR /&gt;</description>
      <pubDate>Thu, 24 Aug 2017 12:20:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/ipv6-ibgp-loopback-peering/m-p/16687#M411</guid>
      <dc:creator>OscarK</dc:creator>
      <dc:date>2017-08-24T12:20:00Z</dc:date>
    </item>
  </channel>
</rss>

