<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
Yes the JNP DOM MIB is what you are looking for.<br>
<br>
It also the traps for warnings and alarms thresholds you can use
which is driven by the optic own parameters.<br>
( Human Interface: show interfaces diagnostics optics
<interface> ] )<br>
<br>
TLDR:<br>
<br>
Realtime: Traps;<br>
Monitoring: DOM MIB;<br>
<br>
PS: I suggest you join [ <a class="moz-txt-link-abbreviated" href="mailto:juniper-nsp@puck.nether.net">juniper-nsp@puck.nether.net</a> ] mailing
list.<br>
<pre class="moz-signature" cols="72">-----
Alain Hebert <a class="moz-txt-link-abbreviated" href="mailto:ahebert@pubnix.net">ahebert@pubnix.net</a>
PubNIX Inc.
50 boul. St-Charles
P.O. Box 26770 Beaconsfield, Quebec H9W 6G7
Tel: 514-990-5911 <a class="moz-txt-link-freetext" href="http://www.pubnix.net">http://www.pubnix.net</a> Fax: 514-990-9443
</pre>
<div class="moz-cite-prefix">On 4/29/21 5:32 PM, Eric Kuhnke wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAB69EHh8WZFAMiGKeMJsX-5FraJGWC0ZhCmtdUvjK=6xGhoqnQ@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="ltr">
<div>The Junipers on both sides should have discrete SNMP OIDs
that respond with a FEC stress value, or FEC error value. See
blue highlighted part here about FEC. Depending on what
version of JunOS you're running the MIB for it may or may not
exist.</div>
<div><br>
</div>
<div><a
href="https://kb.juniper.net/InfoCenter/index?page=content&id=KB36074&cat=MX2008&actp=LIST"
moz-do-not-send="true">https://kb.juniper.net/InfoCenter/index?page=content&id=KB36074&cat=MX2008&actp=LIST</a></div>
<br>
<div>In other equipment sometimes it's found in a sub-tree of
SNMP adjacent to optical DOM values. Once you can acquire and
poll that value, set it up as a custom thing to graph and
alert upon certain threshold values in your choice of NMS. <br>
</div>
<div><br>
</div>
<div>Additionally signs of a failing optic may show up in some
of the optical DOM MIB items you can poll: <a
href="https://mibs.observium.org/mib/JUNIPER-DOM-MIB/"
moz-do-not-send="true">https://mibs.observium.org/mib/JUNIPER-DOM-MIB/</a></div>
<div><br>
</div>
<div>It helps if you have some non-misbehaving similar linecards
and optics which can be polled during custom graph/OID
configuration, to establish a baseline 'no problem' value,
which if exceeded will trigger whatever threshold value you
set in your monitoring system. </div>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Thu, Apr 29, 2021 at 1:40
PM Baldur Norddahl <<a
href="mailto:baldur.norddahl@gmail.com"
moz-do-not-send="true">baldur.norddahl@gmail.com</a>>
wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div dir="ltr">Hello
<div><br>
</div>
<div>We had a 100G link that started to misbehave and caused
the customers to notice bad packet loss. The optical
values are just fine but we had packet loss and latency.
Interface shows FEC errors on one end and carrier
transitions on the other end. But otherwise the link would
stay up and our monitor system completely failed to warn
about the failure. Had to find the bad link by traceroute
(mtr) and observe where packet loss started.</div>
<div><br>
</div>
<div>
<div>The link was between a Juniper MX204 and Juniper
ACX5448. Link length 2 meters using 2 km single mode SFP
modules.</div>
</div>
<div><br>
</div>
<div>What is the best practice to monitor links to avoid
this scenarium? What options do we have to do link
monitoring? I am investigating BFD but I am unsure if that
would have helped the situation.</div>
<div><br>
</div>
<div>Thanks,</div>
<div><br>
</div>
<div>Baldur</div>
<div><br>
</div>
<div><br>
</div>
</div>
</blockquote>
</div>
</blockquote>
<br>
</body>
</html>