P1Fanatic

Seeing increasing CRC's on the serial interface:

sh int s11/1/1
Serial11/1/1 is up, line protocol is up
Hardware is cyBus PODS3 Serial
Description: 44736k link to xxxxx
Internet address is xxxxxx
MTU 4470 bytes, BW 44736 Kbit, DLY 200 usec, rely 255/255, load 12/255
Encapsulation HDLC, crc 16, loopback not set
Keepalive set (10 sec)
Last input 00:00:09, output 00:00:01, output hang never
Last clearing of "show interface" counters 00:23:23
Queueing strategy: fifo
Output queue 0/40, 0 drops; input queue 0/75, 0 drops
5 minute input rate 953000 bits/sec, 393 packets/sec
5 minute output rate 2260000 bits/sec, 402 packets/sec
563633 packets input, 201888897 bytes, 0 no buffer
Received 0 broadcasts, 0 runts, 0 giants, 0 throttles
0 parity
366 input errors, 363 CRC, 0 frame, 3 overrun, 0 ignored, 0 abort
593825 packets output, 425522179 bytes, 0 underruns
0 output errors, 0 applique, 0 interface resets
0 output buffer failures, 0 output buffers swapped out
0 carrier transitions
LC=up CA=down TM=down LB=down TA=down LA=down

Checking the controller we are seeing rising C-Bit and P-Bit violations. Does this look like an SDH clocking issue to you guys?

sh cont serial 11/1/1
Serial11/1/1 -
Mx T3(2) HW Revision 0x3, FW Revision 3.9
Framing is c-bit, Clock Source is Line
Bandwidth limit is 44210, DSU mode 0, Cable length is 50
rx FEBE since last clear counter 0, since reset 29825
Data in current interval (546 seconds elapsed):
170 Line Code Violations, 62 P-bit Coding Violation
62 C-bit Coding Violation
57 P-bit Err Secs, 0 P-bit Sev Err Secs
0 Sev Err Framing Secs, 0 Unavailable Secs
99 Line Errored Secs, 57 C-bit Errored Secs, 0 C-bit Sev Err Secs
Total Data (last 1 15 minute intervals):
377 Line Code Violations, 120 P-bit Coding Violation,
120 C-bit Coding Violation,
107 P-bit Err Secs, 0 P-bit Sev Err Secs,
0 Sev Err Framing Secs, 0 Unavailable Secs,
187 Line Errored Secs, 107 C-bit Errored Secs, 0 C-bit Sev Err Secs
No alarms detected.

P1Fanatic

All the Cisco bods out in the lovely sun then?

scoob_dood

you n00b

- Jon

P1Fanatic

stfu noob3r Some smart peeps on here, unlike at our gaff

carl

I'm afraid I don't know jack-**** about serial interfaces. There shouldn't be a clocking issue as your config indicated you're recovering the clock from the line. Have you tried clock-source internal?

Only other thing I can think of is possibly only relevant to POS or ATM, which is making sure the framing's right at both ends (SDH rather than SONET -- presuming you're in the UK) and that the flags are set right (s1s0=02).