<?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: BGP issue in Extreme X770 switch in Network Architecture &amp; Design</title>
    <link>https://community.extremenetworks.com/t5/network-architecture-design/bgp-issue-in-extreme-x770-switch/m-p/13254#M658</link>
    <description>Hi Paul&lt;BR /&gt;
&lt;BR /&gt;
Thanks for your reply. I have OSPF and BGP running, but for different purpose. The issue happens with the 2nd switch rebooting. When the first switch reboots, it doesn't impact the BGP peering on the 2nd one. But when the reverse happens, the 2nd switch is rebooted, all BGP peering on the other switch is also impacted.&lt;BR /&gt;
&lt;BR /&gt;
I have a maintenance window planned, will do some more detailed investigation first for collecting more information.&lt;BR /&gt;
&lt;BR /&gt;
Regards,&lt;BR /&gt;
Sumanta.&lt;BR /&gt;</description>
    <pubDate>Tue, 01 Nov 2016 16:52:00 GMT</pubDate>
    <dc:creator>Sumanta_Ghosh</dc:creator>
    <dc:date>2016-11-01T16:52:00Z</dc:date>
    <item>
      <title>BGP issue in Extreme X770 switch</title>
      <link>https://community.extremenetworks.com/t5/network-architecture-design/bgp-issue-in-extreme-x770-switch/m-p/13250#M654</link>
      <description>What do the CLI mean? "configure bgp restart both" and "configure bgp as-display-format asplain"? &lt;BR /&gt;
&lt;BR /&gt;
There is a switch related issue in live network where we see fail-over from primary to secondary switch and back is not as working expected. Both switches are in ISC MLAG cluster and run BGP peering with other adjacent nodes. The fail-over works when first switch reboots but when  the second switch comes back up after reboot, all the iBGP sessions  reset/re-establish.  &lt;BR /&gt;
&lt;BR /&gt;</description>
      <pubDate>Thu, 27 Oct 2016 21:50:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/network-architecture-design/bgp-issue-in-extreme-x770-switch/m-p/13250#M654</guid>
      <dc:creator>Sumanta_Ghosh</dc:creator>
      <dc:date>2016-10-27T21:50:00Z</dc:date>
    </item>
    <item>
      <title>RE: BGP issue in Extreme X770 switch</title>
      <link>https://community.extremenetworks.com/t5/network-architecture-design/bgp-issue-in-extreme-x770-switch/m-p/13251#M655</link>
      <description>Hello Sumanta&lt;BR /&gt;
&lt;BR /&gt;
Are you using OSPF IGP for your iBGP?&lt;BR /&gt;
&lt;BR /&gt;
Thanks&lt;BR /&gt;
P&lt;BR /&gt;</description>
      <pubDate>Thu, 27 Oct 2016 22:31:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/network-architecture-design/bgp-issue-in-extreme-x770-switch/m-p/13251#M655</guid>
      <dc:creator>Paul_Russo</dc:creator>
      <dc:date>2016-10-27T22:31:00Z</dc:date>
    </item>
    <item>
      <title>RE: BGP issue in Extreme X770 switch</title>
      <link>https://community.extremenetworks.com/t5/network-architecture-design/bgp-issue-in-extreme-x770-switch/m-p/13252#M656</link>
      <description>Hi Sumanta, regarding the commands:&lt;BR /&gt;
&lt;BR /&gt;
&lt;I&gt;&lt;B&gt;configure bgp restart both&lt;/B&gt;&lt;/I&gt; is used for BGP Graceful Restart (&lt;B&gt;both&lt;/B&gt; means planned and unplanned). "Act as a graceful BGP restart router for both planned and unplanned restarts."&lt;BR /&gt;
&lt;BR /&gt;
&lt;B&gt;configure bgp as-display-format asplain "&lt;/B&gt;Configures the AS number format displayed in show commands"&lt;BR /&gt;
&lt;B&gt;&lt;/B&gt;&lt;BR /&gt;
  &lt;B&gt;asdot&lt;/B&gt;           Display AS numbers in dot notation e.g. 1.10    &lt;B&gt;asplain&lt;/B&gt;         Display AS numbers as plain numbers e.g. 65546&lt;BR /&gt;
&lt;BR /&gt;</description>
      <pubDate>Thu, 27 Oct 2016 22:38:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/network-architecture-design/bgp-issue-in-extreme-x770-switch/m-p/13252#M656</guid>
      <dc:creator>Henrique</dc:creator>
      <dc:date>2016-10-27T22:38:00Z</dc:date>
    </item>
    <item>
      <title>RE: BGP issue in Extreme X770 switch</title>
      <link>https://community.extremenetworks.com/t5/network-architecture-design/bgp-issue-in-extreme-x770-switch/m-p/13253#M657</link>
      <description>Hello Sumanta.&lt;BR /&gt;
&lt;BR /&gt;
Henrigue pointed out what I was fishing for.  If you are using OSPF and the router goes down the failover will be fast however when a OSPF router comes back online it needs to join its adjacency with its neighbors will go down then back up to redo the link.  We do support Graceful OSPF which takes care of that.  Essentially it tells the neighbor router that I am going down and when I come back don't redo the connection.  Simplified &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;BR /&gt;
&lt;BR /&gt;
That may be what you are seeing the drop in the iBGP may be an issue if you are not using graceful restart on the OSPF protocol.&lt;BR /&gt;
&lt;BR /&gt;
Thanks&lt;BR /&gt;
P&lt;BR /&gt;</description>
      <pubDate>Thu, 27 Oct 2016 22:52:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/network-architecture-design/bgp-issue-in-extreme-x770-switch/m-p/13253#M657</guid>
      <dc:creator>Paul_Russo</dc:creator>
      <dc:date>2016-10-27T22:52:00Z</dc:date>
    </item>
    <item>
      <title>RE: BGP issue in Extreme X770 switch</title>
      <link>https://community.extremenetworks.com/t5/network-architecture-design/bgp-issue-in-extreme-x770-switch/m-p/13254#M658</link>
      <description>Hi Paul&lt;BR /&gt;
&lt;BR /&gt;
Thanks for your reply. I have OSPF and BGP running, but for different purpose. The issue happens with the 2nd switch rebooting. When the first switch reboots, it doesn't impact the BGP peering on the 2nd one. But when the reverse happens, the 2nd switch is rebooted, all BGP peering on the other switch is also impacted.&lt;BR /&gt;
&lt;BR /&gt;
I have a maintenance window planned, will do some more detailed investigation first for collecting more information.&lt;BR /&gt;
&lt;BR /&gt;
Regards,&lt;BR /&gt;
Sumanta.&lt;BR /&gt;</description>
      <pubDate>Tue, 01 Nov 2016 16:52:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/network-architecture-design/bgp-issue-in-extreme-x770-switch/m-p/13254#M658</guid>
      <dc:creator>Sumanta_Ghosh</dc:creator>
      <dc:date>2016-11-01T16:52:00Z</dc:date>
    </item>
    <item>
      <title>RE: BGP issue in Extreme X770 switch</title>
      <link>https://community.extremenetworks.com/t5/network-architecture-design/bgp-issue-in-extreme-x770-switch/m-p/13255#M659</link>
      <description>Hi Paul&lt;BR /&gt;
&lt;BR /&gt;
OSPF is not running here, we have direct adjacent i-BGP peering on /30 uplinks. I get this message during reboot, anything to worry about?&lt;BR /&gt;
&lt;BR /&gt;
Warn:BGP.RIBMgr.ProcStubMsgDataLost&lt;BR /&gt;
&lt;BR /&gt;
An attempt to process an ATG_I3_INET_ADDR_IND has failed due to local&lt;BR /&gt;
                                                             resource shortages or indication that the I3 join has lost some&lt;BR /&gt;
                                                             information for the request&lt;BR /&gt;
                                                             VR = 0x00000005&lt;BR /&gt;
                                                             I3 join index = 1&lt;BR /&gt;
                                                             Data lost flag value = 1&lt;BR /&gt;
                                                             Local resource ret code = 0  &lt;BR /&gt;
&lt;BR /&gt;
Regards,&lt;BR /&gt;
Sumanta.&lt;BR /&gt;
&lt;BR /&gt;</description>
      <pubDate>Fri, 04 Nov 2016 19:05:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/network-architecture-design/bgp-issue-in-extreme-x770-switch/m-p/13255#M659</guid>
      <dc:creator>Sumanta_Ghosh</dc:creator>
      <dc:date>2016-11-04T19:05:00Z</dc:date>
    </item>
  </channel>
</rss>

