<?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: ospf log error in ExtremeSwitching (EXOS/Switch Engine)</title>
    <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/ospf-log-error/m-p/43499#M10508</link>
    <description>Hi Jasheer, &lt;BR /&gt;
&lt;BR /&gt;
I have seen this before and believe this  translates to the OSPF   neighbor changing state from FULL to EXSTART because of the receipt of a   Database Description (DBD) packet from the neighbor with an unexpected sequence   number.&lt;BR /&gt;
&lt;BR /&gt;
SeqNumberMismatch   means that a DBD packet during OSPF neighborship negotiation has been received   that either:&lt;BR /&gt;
&lt;BR /&gt;
&lt;UL&gt; 
&lt;LI&gt;has   an unexpected DBD sequence number 
&lt;/LI&gt;&lt;LI&gt;unexpectedly   has the Iimit bit set 
&lt;/LI&gt;&lt;LI&gt;has   an Options field differing from the last Options field received in a Database   Description packet. 
&lt;/LI&gt;&lt;/UL&gt;This   can be attributed to (Unidirectional) packet loss as a possible   cause.&lt;BR /&gt;
&lt;BR /&gt;
So I would take a look at the port that the neighbour is connecting through and check for any packet loss.&lt;BR /&gt;
&lt;BR /&gt;
Thanks.&lt;BR /&gt;
&lt;BR /&gt;</description>
    <pubDate>Mon, 28 Sep 2015 15:12:00 GMT</pubDate>
    <dc:creator>Anonymous</dc:creator>
    <dc:date>2015-09-28T15:12:00Z</dc:date>
    <item>
      <title>ospf log error</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/ospf-log-error/m-p/43498#M10507</link>
      <description>Hi,&lt;BR /&gt;
       My ospf link flopping continuously the  switch log is showing below mentioned. kindly help as to solve this issue.. &lt;BR /&gt;
&lt;BR /&gt;
09/28/2015 17:04:51.49 &lt;OSPF.NEIGHBOR.PROCDDFAIL&gt; Processing DD from neighbor 192.168.99.2 fails on NBR seqmismatch event,case else&lt;BR /&gt;&lt;/OSPF.NEIGHBOR.PROCDDFAIL&gt;</description>
      <pubDate>Mon, 28 Sep 2015 14:39:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/ospf-log-error/m-p/43498#M10507</guid>
      <dc:creator>Mohammed_Jashee</dc:creator>
      <dc:date>2015-09-28T14:39:00Z</dc:date>
    </item>
    <item>
      <title>RE: ospf log error</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/ospf-log-error/m-p/43499#M10508</link>
      <description>Hi Jasheer, &lt;BR /&gt;
&lt;BR /&gt;
I have seen this before and believe this  translates to the OSPF   neighbor changing state from FULL to EXSTART because of the receipt of a   Database Description (DBD) packet from the neighbor with an unexpected sequence   number.&lt;BR /&gt;
&lt;BR /&gt;
SeqNumberMismatch   means that a DBD packet during OSPF neighborship negotiation has been received   that either:&lt;BR /&gt;
&lt;BR /&gt;
&lt;UL&gt; 
&lt;LI&gt;has   an unexpected DBD sequence number 
&lt;/LI&gt;&lt;LI&gt;unexpectedly   has the Iimit bit set 
&lt;/LI&gt;&lt;LI&gt;has   an Options field differing from the last Options field received in a Database   Description packet. 
&lt;/LI&gt;&lt;/UL&gt;This   can be attributed to (Unidirectional) packet loss as a possible   cause.&lt;BR /&gt;
&lt;BR /&gt;
So I would take a look at the port that the neighbour is connecting through and check for any packet loss.&lt;BR /&gt;
&lt;BR /&gt;
Thanks.&lt;BR /&gt;
&lt;BR /&gt;</description>
      <pubDate>Mon, 28 Sep 2015 15:12:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/ospf-log-error/m-p/43499#M10508</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2015-09-28T15:12:00Z</dc:date>
    </item>
  </channel>
</rss>

