FEBE and B3 Errors on both sides of an OC48

Unanswered Question
Jun 13th, 2007
User Badges:

Below illustrates the FEBE and B3 errors we're seeing on router A and router B of an OC48. Any thoughts?


PATH

AIS = 0 RDI = 0 FEBE = 480 BIP(B3) = 284881

PLM = 0 UNEQ = 0 TIM = 0 TIU = 0

LOP = 0 NEWPTR = 0 PSE = 0 NSE = 0


Active Defects: B3-TCA

Active Alarms: B3-TCA


Other tests:

router A#traceroute <IP Address> (router B)



Type escape sequence to abort.


Tracing the route to router B (<IP Address>)



1 router B (<IP Address>) 20 msec * 20 msec



PING


Type escape sequence to abort.


Sending 5, 100-byte ICMP Echos to <IP Address>, timeout is 2 seconds:


!!!!!


Success rate is 100 percent (5/5), round-trip min/avg/max = 16/19/20 ms


router A#ping <IP Address>



Type escape sequence to abort.


Sending 5, 100-byte ICMP Echos to <IP Address>, timeout is 2 seconds:


.!!!!


Success rate is 80 percent (4/5), round-trip min/avg/max = 16/19/20 ms


router A#ping <IP Address>



Type escape sequence to abort.


Sending 5, 100-byte ICMP Echos to <IP Address>, timeout is 2 seconds:


...!.


Success rate is 20 percent (1/5), round-trip min/avg/max = 16/16/16 ms






  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
pciaccio Thu, 06/14/2007 - 02:52
User Badges:
  • Silver, 250 points or more

The errors you are seeing are Path FEBE (Far End Bit Errors) and Path B-3 BIP-8 errors (Bit Interleaved Parity). These errors are showing up on the Path. That means that they are originating from anywhere down the whole Path of the circuit from end-to-end. If they were Line or Section errors then you could isolate them better. However the FEBE means that the remote end point is receiving errors from your transmit. The BIP errors mean that the in-band monitoring byte calculations are not correct. Each byte of data is observed and if the data byte has a total number of ones being odd then a one is placed in the first position of the B-3 byte. This happens for all the data bytes to form a B-3 byte. If you are getting errors then the data is getting corrupt. You may have timing issues on your Sonet, or you may have a mis-configured piece of equipment along the Path. or even a dirty Fiber or low Db signal along the Path. I suggest you get the carrier involved to help you isolate the trouble...Good Luck..Please rate....

Actions

This Discussion