ā03-22-2011 01:24 PM - edited ā03-16-2019 04:05 AM
Hi,
Hope I can get some helps here.
Environment: CUCM 7.15, C2921 15.0(1)M4 with T1 PRI
T1 PRI "Path Code Violation" errors have been observered during business hours. The customer brought in the telco (Bell Canada) to do the on-site stress test, but didn't see any errors.
"The Telco created loopback 50kms away at main CO, this tested the line from 2921, which is via copper to remote CO ( 3kms), then to main CO via their fiber."
A TAC case has been opened for a while, still no clues.
Below is the errors:
Data in Interval 15:
0 Line Code Violations, 12535 Path Code Violations
0 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 9 Degraded Mins
301 Errored Secs, 271 Bursty Err Secs, 0 Severely Err Secs, 0 Unavail Secs
Data in Interval 16:
0 Line Code Violations, 3000 Path Code Violations
0 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 10 Degraded Mins
307 Errored Secs, 236 Bursty Err Secs, 0 Severely Err Secs, 0 Unavail Secs
Data in Interval 17:
0 Line Code Violations, 4864 Path Code Violations
0 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 10 Degraded Mins
282 Errored Secs, 236 Bursty Err Secs, 0 Severely Err Secs, 0 Unavail Secs
Data in Interval 18:
0 Line Code Violations, 15043 Path Code Violations
0 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 14 Degraded Mins
480 Errored Secs, 416 Bursty Err Secs, 0 Severely Err Secs, 0 Unavail Secs
Data in Interval 19:
0 Line Code Violations, 7677 Path Code Violations
0 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 11 Degraded Mins
307 Errored Secs, 238 Bursty Err Secs, 0 Severely Err Secs, 0 Unavail Secs
Data in Interval 20:
0 Line Code Violations, 2288 Path Code Violations
0 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 8 Degraded Mins
152 Errored Secs, 113 Bursty Err Secs, 0 Severely Err Secs, 0 Unavail Secs
Data in Interval 21:
0 Line Code Violations, 4258 Path Code Violations
0 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 11 Degraded Mins
251 Errored Secs, 208 Bursty Err Secs, 0 Severely Err Secs, 0 Unavail Secs
ā03-22-2011 02:11 PM
verify line coding with TELCO is correct
"A Path code violation error event is a frame synchronization bit error in the D4 (SF) format, or a CRC error in the ESF format. Path code violations and line code violations are typically present simultaneously. Always verify that your line coding is correct."
http://www.cisco.com/en/US/tech/tk713/tk628/technologies_tech_note09186a00801095a3.shtml
ā03-22-2011 02:17 PM
Thank you for your input, Andrian.
All configurations were verified with telco. It's odd as we see PCV only, no LCV.
ā03-22-2011 02:29 PM
Don't know if you went through this T1 PRI Troubleshooting Flowchart. Worth a try
http://www.cisco.com/en/US/tech/tk713/tk628/technologies_tech_note09186a00800a754a.shtml
ā03-23-2011 05:44 AM
Hi,
If the line coding and framing have already been verified, it could mean that you are having a layer 1 issue.
Can you please check the cabling and the card?
ā03-23-2011 06:53 AM
I had this same problem last week.
Here is an example of the issue I was having. After I contacted the Telco company and they ran some intrusive testing the T1 became clean again.
BAD
Total Data (last 24 hours)
2 Line Code Violations, 2218 Path Code Violations,
3 Slip Secs, 0 Fr Loss Secs, 2 Line Err Secs, 219 Degraded Mins,
1037 Errored Secs, 388 Bursty Err Secs, 0 Severely Err Secs, 29 Unavail Secs
GOOD
Total Data (last 24 hours)
0 Line Code Violations, 0 Path Code Violations,
0 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins,
0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 0 Unavail Secs
I hope this helps!!!
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: