On Fri, 30 Apr 2021 at 00:35, Eric Kuhnke wrote:
> 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
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.
>>>
>>> The link was between a Juniper MX204 and Juniper ACX5448. Link length 2
>>> meters using 2 km single mode SFP modules.
>>>
>>> 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.
>>>
>>> Thanks,
>>>
>>> Baldur
>>>
>>>
>>>
>>
about the failure. Had to find the
>> bad link by traceroute (mtr) and observe where packet loss started.
>>
>> The link was between a Juniper MX204 and Juniper ACX5448. Link length 2
>> meters using 2 km single mode SFP modules.
>>
>> 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.
>>
>> Thanks,
>>
>> Baldur
>>
>>
>>
>
Link
length 2 meters using 2 km single mode SFP modules.
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.
Thanks,
Baldur
From: NANOG On Behalf Of
Baldur Norddahl
Sent: Thursday, April 29, 2021 3:39 PM
To: nanog@nanog.org
Subject: link monitoring
Hello
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
ink was between a Juniper MX204 and Juniper ACX5448. Link length 2
>> meters using 2 km single mode SFP modules.
>>
>> 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.
>>
>> Thanks,
>>
>> Baldur
>>
>>
>>
> meters using 2 km single mode SFP modules.
>>
>> 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.
>>
>> Thanks,
>>
>> Baldur
>>
>>
here packet loss started.
>
> The link was between a Juniper MX204 and Juniper ACX5448. Link length 2
> meters using 2 km single mode SFP modules.
>
> 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 b
.
The link was between a Juniper MX204 and Juniper ACX5448. Link length
2 meters using 2 km single mode SFP modules.
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
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.
Thanks,
Baldur
Gents,
We need to separate the context of fast reroute via control plane topology
map vs local link protection with OAM at mac/phy sub-layer and time frames
at which they are relevant.
There are efforts going on at the media level but then there are current
solutions that are media and
On Mon, Jan 19, 2015 at 22:55:04 +, Dave Bell wrote:
http://www.rvdp.org/presentations/SC11-SRS-8021ag.pdf;
The 802.1ag code used is open source and available on:
https://svn.surfnet.nl/trac/dot1ag-utils/
Of course if you want fast failover, you need to send packets very
rapidly. Every
On Wed, Jan 21, 2015 at 12:22 PM, Ronald van der Pol
ronald.vander...@rvdp.org wrote:
On Mon, Jan 19, 2015 at 22:55:04 +, Dave Bell wrote:
http://www.rvdp.org/presentations/SC11-SRS-8021ag.pdf;
The 802.1ag code used is open source and available on:
BFD etc aim to prove there is end-to-end connectivity between two
points, not just that all links are up along the path. All ports could
be up, but end-to-end connectivity broken, for example a misconfigured
VLAN across a L2 network. Sending some kind of packet across the
network is pretty much
Hi,
Routers connected back to back often rely on BFD for link failures. Its
certainly possible that there is a switch between two routers and hence a
link down event on one side is not visible to the other side. So, you run
some sort of an OAM protocol on the two routers so that they can detect
15 matches
Mail list logo
