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

2008-08-05 Thread Amos Rosenboim
Hello Chris, If I remember correctly then B3 errors are associated with clocking alignment along the circuit. This also correlate to what you are saying about passing through 7 carriers. Regards Amos Rosenboim [EMAIL PROTECTED] On Aug 4, 2008, at 9:54 PM, Chris Adams wrote: I have an

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

2008-08-05 Thread Kevin Oberman
Date: Mon, 4 Aug 2008 13:54:27 -0500 From: Chris Adams [EMAIL PROTECTED] Sender: [EMAIL PROTECTED] 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

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

2008-08-05 Thread Clinton Work
If the errors are occurring frequently enough (once an hour), you could ask for a hard loopback on one end and ask the service provider to run a bert test from the other side towards the hard loopback. The bert will see the path errors in the middle of the circuit which will prove the

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

2008-08-04 Thread Chris Adams
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