<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 12 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]-->
<title>EAPS - Fail-timer-exp flag set. Domain state: Complete</title>
<style>
<!--
/* Font Definitions */
@font-face
{font-family:"MS Mincho";
panose-1:2 2 6 9 4 2 5 8 3 4;}
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:"\@MS Mincho";
panose-1:2 2 6 9 4 2 5 8 3 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
{mso-style-link:"Plain Text Char";
margin:0cm;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0cm;
margin-right:0cm;
margin-bottom:0cm;
margin-left:36.0pt;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
span.EmailStyle19
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle20
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.PlainTextChar
{mso-style-name:"Plain Text Char";
mso-style-link:"Plain Text";
font-family:"Courier New";}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:70.85pt 70.85pt 70.85pt 70.85pt;}
div.WordSection1
{page:WordSection1;}
-->
</style>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=EN-US link=blue vlink=purple>
<div class=WordSection1>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Not sure that the counter is linked to the EAPS issue :<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoPlainText><b>Rx-Invalid-Vlan-Intf –<o:p></o:p></b></p>
<p class=MsoPlainText><span style='font-family:"Arial","sans-serif"'>Vlan
interface for incoming vlan cannot be found.<o:p></o:p></span></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText><b>Rx-Undersize-Pkt –<o:p></o:p></b></p>
<p class=MsoPlainText><span style='font-family:"Arial","sans-serif"'>Packet
length is less than the length of the header.<o:p></o:p></span></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText><b>Rx-Invalid-8021Q-Tag –<o:p></o:p></b></p>
<p class=MsoPlainText><span style='font-family:"Arial","sans-serif"'>VlanTypeLength
field in Ethernet header does not match the default Ethernet value for 8021Q
Tag.<o:p></o:p></span></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText><b>Rx-Invalid-SNAP-Type –<o:p></o:p></b></p>
<p class=MsoPlainText><span style='font-family:"Arial","sans-serif"'>SNAP value
in Ethernet header is invalid.<o:p></o:p></span></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText><b>Rx-Invalid-OUI –<o:p></o:p></b></p>
<p class=MsoPlainText><span style='font-family:"Arial","sans-serif"'>OUI value
in Ethernet header does not match 00:E0:2B.<o:p></o:p></span></p>
<p class=MsoPlainText> <o:p></o:p></p>
<p class=MsoPlainText><b>Rx-EEP-Unsupported-Version – <o:p></o:p></b></p>
<p class=MsoPlainText><span style='font-family:"Arial","sans-serif"'>Unsupported
EEP version. EEP version should be 1<o:p></o:p></span></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText><b>Rx-EEP-Invalid-Length –<o:p></o:p></b></p>
<p class=MsoPlainText><span style='font-family:"Arial","sans-serif"'>Length in
EEP header is greater than the packet length. <o:p></o:p></span></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText><b>Rx-EEP-Checksum-Invalid -<o:p></o:p></b></p>
<p class=MsoPlainText><span style='font-family:"Arial","sans-serif"'>EEP
checksum is invalid.<o:p></o:p></span></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText><b>Rx-Domain-Invalid –<o:p></o:p></b></p>
<p class=MsoPlainText><span style='font-family:"Arial","sans-serif"'>Control
vlan of incoming PDU does not have any EAPS domain associated with it.<o:p></o:p></span></p>
<p class=MsoPlainText><span style='font-family:"Arial","sans-serif"'><o:p> </o:p></span></p>
<p class=MsoPlainText><b>Rx-Lif-Invalid –<o:p></o:p></b></p>
<p class=MsoPlainText><span style='font-family:"Arial","sans-serif"'>LIF for
ingress port cannot be found.<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>I would suggest to open a case at TAC.<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>You can also use the command : debug eaps check config (on EXOS)
on each EAPS switch to check if there is some configuration anomaly.<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Regards, Fabian.<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<div>
<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm'>
<p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> Dudek, Michael
[mailto:michael.dudek@warema.de] <br>
<b>Sent:</b> mercredi 29 septembre 2010 13:17<br>
<b>To:</b> Fabian<br>
<b>Cc:</b> extreme-nsp@puck.nether.net<br>
<b>Subject:</b> AW: [e-nsp] EAPS - Fail-timer-exp flag set. Domain state:
Complete<o:p></o:p></span></p>
</div>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:blue'>Hello Fabian,</span><o:p></o:p></p>
<div>
<p class=MsoNormal><br>
<span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:blue'>first
of all I checked whether there are rx or tx errors on the common links (2
BD8810), result: no errors</span><o:p></o:p></p>
</div>
<div>
<p class=MsoNormal> <o:p></o:p></p>
</div>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:blue'>Then I checked the common links with all possible commands like
"sh eaps counters shared-port 4:8". Result: <br>
On all EAPS-Domains are only Rx-Seg-Health and tX-Seg-Health packets. </span><o:p></o:p></p>
<div>
<p class=MsoNormal> <o:p></o:p></p>
</div>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:blue'>In addition the global counters for EAPS Shared-Ports are all null.</span><o:p></o:p></p>
<div>
<p class=MsoNormal> <o:p></o:p></p>
</div>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:blue'>The command "sh eaps counters global" shows maybe some
interesting things:</span><o:p></o:p></p>
<div>
<p class=MsoNormal> <o:p></o:p></p>
</div>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:blue'>"Rx-Invalid-Vlan-Intf : 73" and "Rx-Lif-Invalid
: 5" <br>
"Rx-Invalid-Vlan-Intf : 150" and
"Rx-Lif-Invalid : 88"</span><o:p></o:p></p>
<div>
<p class=MsoNormal> <o:p></o:p></p>
</div>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:blue'>But I don't know how to interpret these counters.</span><o:p></o:p></p>
<div>
<p class=MsoNormal> <o:p></o:p></p>
</div>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:blue'>Furthermore I compared again the eaps configurations but there
seems to be no misconfiguration. Also EpiCenter <br>
reports only that some vlans are not protected, but they are! It has something
to do with case-sensitve, how you are writing the names of the vlans, like
"PB4" or "pb".</span><o:p></o:p></p>
<div>
<p class=MsoNormal> <o:p></o:p></p>
</div>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:blue'>It seems more that something is teasing or targeting the cpu on the
masters. But there are 3 EAPS-Rings that doesn't have that problem.<br>
Two of them have nothing to do with the investigated common links, and there is
not the named vlan "stammhaus" on them.<br>
But 1 EAPS-Master doesn't report any problems, he seems to be unimpressed even
though the vlan "stammhaus" is configured on that switch, too.</span><o:p></o:p></p>
<div>
<p class=MsoNormal> <o:p></o:p></p>
</div>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:blue'>Any further ideas, suggestions.</span><o:p></o:p></p>
<div>
<p class=MsoNormal> <o:p></o:p></p>
</div>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:blue'>Regards, mikeld</span><o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<div class=MsoNormal align=center style='text-align:center'><span lang=DE>
<hr size=2 width="100%" align=center>
</span></div>
<p class=MsoNormal style='margin-bottom:12.0pt'><b><span lang=DE
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>Von:</span></b><span
lang=DE style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> Fabian
[mailto:fabian.extr@gmail.com] <br>
<b>Gesendet:</b> Dienstag, 28. September 2010 23:53<br>
<b>An:</b> Dudek, Michael<br>
<b>Cc:</b> extreme-nsp@puck.nether.net<br>
<b>Betreff:</b> RE: [e-nsp] EAPS - Fail-timer-exp flag set. Domain state:
Complete</span><span lang=DE><o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Hi Mikeld,<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>This message should appear when the EAPS Master is losing EAPS
PDU that it has sent over the ring.<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Loss of EAPS Health-Check Packets could happen:<o:p></o:p></span></p>
<p class=MsoListParagraph style='text-indent:-18.0pt'><span style='font-size:
11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>-</span><span
style='font-size:7.0pt;color:#1F497D'>
</span><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Frames in error in the ring<o:p></o:p></span></p>
<p class=MsoListParagraph style='text-indent:-18.0pt'><span style='font-size:
11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>-</span><span
style='font-size:7.0pt;color:#1F497D'>
</span><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>A switch in the ring that is having some trouble and loosing
frames<o:p></o:p></span></p>
<p class=MsoListParagraph style='text-indent:-18.0pt'><span style='font-size:
11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>-</span><span
style='font-size:7.0pt;color:#1F497D'>
</span><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Lot of frames going to CPU on the Master<o:p></o:p></span></p>
<p class=MsoListParagraph style='text-indent:-18.0pt'><span style='font-size:
11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>-</span><span
style='font-size:7.0pt;color:#1F497D'>
</span><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>..<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Wireshark will not really help because EAPS PDU are isolated in
the Control VLAN.<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>If this happened on all rings, I will check the Common Link (or
EAPS Shared-Link) status/statistics.<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Fabian.<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<div>
<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm'>
<p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>
extreme-nsp-bounces@puck.nether.net
[mailto:extreme-nsp-bounces@puck.nether.net] <b>On Behalf Of </b>Dudek, Michael<br>
<b>Sent:</b> mardi 28 septembre 2010 09:08<br>
<b>To:</b> extreme-nsp@puck.nether.net<br>
<b>Subject:</b> [e-nsp] EAPS - Fail-timer-exp flag set. Domain state: Complete<o:p></o:p></span></p>
</div>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<p><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>No matter
whether it is XOS Version 12.4.1.7 v1241b7-patch1-7 nor EW-Version 7.8e.2.1, at
a certain time, mainly between 12.00 to 01.00 pm I get hundreds of
messages in the syslogs like</span><o:p></o:p></p>
<p><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>09/27/2010
12:47:32.81 <Info:EAPS.DmnInfo> EAPSD DSK33 - Fail-timer-exp flag
cleared. Domain state: Complete</span> <br>
<span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>09/27/2010
12:47:32.81 <Info:EAPS.DmnInfo> EAPSD DSK33 - Fail-timer-exp flag set.
Domain state: Complete</span> <br>
<span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>09/27/2010
12:47:28.86 <Info:EAPS.DmnInfo> EAPSD DSK33 - Fail-timer-exp flag
cleared. Domain state: Complete</span> <br>
<span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>09/27/2010
12:47:24.82 <Info:EAPS.DmnInfo> EAPSD DSK33 - Fail-timer-exp flag set.
Domain state: Complete</span> <br>
<span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>09/27/2010
12:47:17.81 <Info:EAPS.DmnInfo> EAPSD DSK33 - Fail-timer-exp flag
cleared. Domain state: Complete</span> <br>
<span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>09/27/2010
12:47:17.81 <Info:EAPS.DmnInfo> EAPSD DSK33 - Fail-timer-exp flag set.
Domain state: Complete</span> <o:p></o:p></p>
<p><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>There are
nearly all EAPS-Master from 24 EAPS-Rings affected. My investigations shows the
following:</span> <o:p></o:p></p>
<p><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>All the
eaps-rings have no configuration errors. </span><br>
<span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>There are no
rx- or tx-errors on the uplinks. </span><br>
<span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>Network
performance is not affected. </span><br>
<span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>It must be a
certain vlan from which the interference comes, this vlan is known. </span><br>
<span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>It happens only
on weekdays and during office hours </span><br>
<span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>I have no
details found with wireshark, but I'm not an expert with wireshark </span><br>
<span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>I found some
references about IPv6 neighbor discovery protocol, there are some W7 PCs in
that vlan. </span><o:p></o:p></p>
<p><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>My guess is
that something teases the cpu of the eaps-masters but how can I catch that
thing?</span> <br>
<span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>Does anyone
have a suggestion how I can get this under control with EW or XOS or wireshark
or anything else?</span> <o:p></o:p></p>
<p><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>Thanks a
lot, Mikeld</span> <o:p></o:p></p>
</div>
</body>
</html>