01-11-2012 04:07 PM
Hello, got a question I'm not getting terrific answers to. I have a customer who complains of packet loss on a T1. This is terminated on a Juniper M120's (JUNOS Base OS boot [9.3R4.4]) t1-5/0/0:5:23, parent card is ct3-5/0/0:5.
All that's ever seen are L2 channel errors. No CRCs, UAS, nothing else.
Errors: 0, Drops: 0, Framing errors: 0, Runts: 0, Giants: 0, Policed discards: 0, L3 incompletes: 0, L2 channel errors: 5767,
L2 mismatch timeouts: 0, HS link CRC errors: 0, SRAM errors: 0, Resource errors: 0
T1 media: Seconds Count State
SEF 0 0 OK
BEE 0 0 OK
AIS 0 0 OK
LOF 0 0 OK
LOS 0 0 OK
YELLOW 0 0 OK
CRC Major 0 0 OK
CRC Minor 0 0 OK
BPV 0 0
EXZ 0 0
LCV 0 0
PCV 0 0
CS 0 0
CRC 0 0
Juniper's KB returns "Output Fields L2 channel errors —Counter increments when the software could not find a valid logical interface for an incoming frame. L2 mismatch timeouts ".
Um .... ok. 'could not find a valid logical interface'.
I ask around and one fellow I respect mused that this is LCP/NCP interpreting, say, CDP (or other proprietary protocols) as unknown traffic, and it notes them as errors, incrementing the counter. Sounds possible. Yet, I can't find any dialogue/discussion on exactly how JUNOS qualifies L2 channel errors.
So that's my question. What causes these errors, and can their existence manifest as "packet-loss" experience from a customer's POV? Are they anything to be concerned with? I get conflicting answers.
01-12-2012 06:20 AM
Here is a discussion about those errors
I think you can try to use the error rate as a key... Can you measure (approximately)
the rate this error counter increasess (counts per minute, e.g.?)
If this number is stable, then it is likely something like CDP or other protocol Juniper is
Also what do the customers report about the interface? Are they seeing packet loss
all the time, or periodically? Does it correlate with the above errors? You should check
this, but as long as other units on this channelized card are all right, it does not seem
to me that the problem is on the Juniper side...
01-12-2012 09:06 AM
Most likely, this is not something to be concerned about. Is your encapsulation type frame-relay? It could be that you are receiving frames with an unconfigured dlci.
Could you send the entire output of 'show interface <interface> extensive', and 'show configuration <interface>'?