Packet-Optical Technologies
Packet-Optical Technologies
Don't Go Over that Cliff
01.19.16

I don't know about you, but I spent many hours (way too many hours) as a kid glued to the TV screen watching Saturday morning cartoons. Looney Tunes were always a favorite, especially The Road Runner.  If you've watched more than one episode you know it'd only be a matter of time before the hapless Wile E. Coyote would end up running off the edge of a cliff. Always funny, but he's seriously bummed.
 

 

RoadRunner Coyote.png

 
Why bring this up here? Well, in the packet-optical transport world we sometimes live in fear of falling off cliffs: FEC cliffs, to be specific. If the link BER exceeds the correction capability of the receiver's FEC decoder, uncorrected codewords result. Uncorrected code words -> corrupted Ethernet frames -> dropped packets -> you are bummed.
 
To avoid that cliff you need watch where you're going and know what to look for. Heres an example for a PTX 100G DWDM PIC:  
 
Step 1 - Clear the Stats
 
When looking at FEC stats, it's important that your readings are not stale. If you bring a link up or down, you'll likely see some residual errors that have been accumulated by the FEC PM counters. While this is completely normal and expected, you'll want to make sure you clear the counters once the link is stable to ensure you're looking at meaningful data. Here's how:
 

> clear interface statistics et-1/0/0

 
Step 2 - Read the Stats
 
Once you have clean stats ready, you'll want to look at some numbers. The longer your collect stats, the more meaningful they will be. Here is a CLI excerpt on how to read them (see more about the parameters here):

 

> show interfaces et-1/1/0 extensive

 

...

 

OTN FEC statistics:

    Corrected Errors                                13032402

    Uncorrected Words                                      0

    Corrected Error Ratio (        53 sec average)  3.42e-05

...

 
Step 3 - Look for the Cliff
 
Once you have valid stats, you should compare them against the FEC cliff for your specific interface type. Looking at Table 1 from the TechLibrary article Understanding Pre-FEC BER Monitoring and BER Thresholds, we can see that the FEC cliff for the PTX 100G DWDM PIC is 1.5E-2. 
 
Putting all this together for this specific example, we can see that we're in good shape: there are no uncorrected words (UCWs) and the current pre-FEC BER (aka Corrected Error Ratio) has about 3 orders of magnitude margin vs. the FEC cliff for this PIC.
 
Don't be that Coyote
 
Knowing your link performance and equipment limits are fundamental to turning up and maintaining a stable and reliable packet-optical link. Going over the FEC cliff is no laughing matter... if you do, you might wind up with an anvil on your head.
 
Coyote.png

01.19.16
Juniper Employee

I had no TV till I was 22 yrs (not months) old.. I caught wih road runner in my adult life... Smiley Happy

 

Top Kudoed Authors
User Kudos Count
14
11
4
2
2