[j-nsp] Debugging SONET (OC-3) errors

Chris Adams cmadams at hiwaay.net
Mon Aug 4 14:54:27 EDT 2008


I have an OC-3 (POS running PPP) between two POPs (an M10i at each end)
getting errors, and this is the first time I've had to debug errors on a
SONET link.

I am seeing BIP-B3 and REI-P incrementing in spurts on the Z end (e.g.
99 BIP-B3 and 45 REI-P, both showing 2 seconds), as well as ES-P and
ES-PFE matching the seconds (2 in since I cleared the counters).  No
other error counters are incrementing (no section or line errors at
all).  I have seen some errors at the A end as well, but not as many or
as often.

When I get a spurt of errors, both ends will show an interface flap (at
least most of the time; I'm not sure this is 100% of the time or not).

Reading various docs, this means there is a problem somewhere between
telco devices with the transmission from the Z end to the A end.  Is
that correct?

I opened a telco ticket, but they pretty much blew it off.  I know
little about SONET so I am having trouble telling them what to check.
I'd like to avoid intrusive testing if possible (since this is a major
circuit for us).

Part of the problem is that this circuit goes through 7 (yes 7!)
different carriers, and I am not sure that the telco that owns the whole
thing is looking at anything other than the loop on the Z end (the only
piece they actually own).

Any suggestions?
-- 
Chris Adams <cmadams at hiwaay.net>
Systems and Network Administrator - HiWAAY Internet Services
I don't speak for anybody but myself - that's enough trouble.


More information about the juniper-nsp mailing list