WAN - Hssi-B-Port high errors

Unanswered Question
Jan 30th, 2009
User Badges:

Should the invent txclock command help eliminate some of the high errors seen on these Hssi point to point connections? I'm looking for a solution that will eliminate these high errors seen. Of course the provider always says no trouble found. The core router is a 7204VXR (NPR400). The config looks like this:

interface Hssi3/0

service-policy output PTC-TO-HAN-P2P-POLICY

load-interval 30

serial restart-delay 0


Then the other side is a cisco 3845 with the same type of module:


Mx HSSI-B Port adapter, 1 port. Config looks like this:


interface Hssi2/0

load-interval 30

serial restart-delay 0

service-policy output HAN-P2P-POLICY


4896 input errors, 4783 CRC, 0 frame, 96 overrun, 0 ignored, 17 abort









  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
Paolo Bevilacqua Fri, 01/30/2009 - 07:40
User Badges:
  • Super Gold, 25000 points or more
  • Hall of Fame,

    Founding Member

How many input packets ?


tedreese Fri, 01/30/2009 - 07:52
User Badges:

this is one 7204VXR side:


MTU 4470 bytes, BW 45045 Kbit, DLY 200 usec,

reliability 255/255, txload 83/255, rxload 19/255

Encapsulation HDLC, crc 16, loopback not set

Keepalive set (10 sec)

Restart-Delay is 0 secs

Last input 00:00:01, output 00:00:00, output hang never

Last clearing of "show interface" counters 01:21:46

Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 91

Queueing strategy: weighted fair

Output queue: 0/1000/64/91 (size/max total/threshold/drops)

Conversations 0/179/256 (active/max active/max total)

Reserved Conversations 1/1 (allocated/max allocated)

Available Bandwidth 18018 kilobits/sec

30 second input rate 3526000 bits/sec, 2147 packets/sec

30 second output rate 14702000 bits/sec, 2564 packets/sec

9858536 packets input, 2323315924 bytes, 0 no buffer

Received 573 broadcasts, 0 runts, 0 giants, 0 throttles

0 parity

0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort

11329375 packets output, 3422481842 bytes, 0 underruns

0 output errors, 0 applique, 0 interface resets

0 output buffer failures, 0 output buffers swapped out

0 carrier transitions LC=down CA=up TM=down LB=down TA=up LA=down


This is the 3845 side:


MTU 4470 bytes, BW 45045 Kbit, DLY 200 usec,

reliability 255/255, txload 24/255, rxload 77/255

Encapsulation HDLC, crc 16, loopback not set

Keepalive set (10 sec)

Restart-Delay is 0 secs

Last input 00:00:00, output 00:00:00, output hang never

Last clearing of "show interface" counters 1w1d

Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0

Queueing strategy: Class-based queueing

Output queue: 0/1000/64/0 (size/max total/threshold/drops)

Conversations 0/73/256 (active/max active/max total)

Reserved Conversations 1/1 (allocated/max allocated)

Available Bandwidth 18018 kilobits/sec

30 second input rate 13760000 bits/sec, 2422 packets/sec

30 second output rate 4416000 bits/sec, 2165 packets/sec

514107407 packets input, 2894366978 bytes, 0 no buffer

Received 89136 broadcasts, 0 runts, 0 giants, 0 throttles

0 parity

4923 input errors, 4809 CRC, 0 frame, 97 overrun, 0 ignored, 17 abort

521028387 packets output, 521951278 bytes, 0 underruns

0 output errors, 0 applique, 0 interface resets

0 output buffer failures, 0 output buffers swapped out

0 carrier transitions LC=down CA=up TM=down LB=down TA=up LA=down




Paolo Bevilacqua Fri, 01/30/2009 - 08:24
User Badges:
  • Super Gold, 25000 points or more
  • Hall of Fame,

    Founding Member

Hi, you are fine. Cannot use the byet counter because it has rolled over, but


514107407 * 800 B/pft * 8 =



Paolo Bevilacqua Fri, 01/30/2009 - 09:31
User Badges:
  • Super Gold, 25000 points or more
  • Hall of Fame,

    Founding Member

Excuse the garbage in other answer. Seems like you have a BER better that 1/10^8. Usually circuits are deemed acceptable in that area.


514107407 * 800 B/pkt * 8 bits in byte / 4923 =


668350072

tedreese Fri, 01/30/2009 - 09:34
User Badges:

Ok, my question is would the invent txclock config assist in clearing up these errors?


Thanks,

Ted

Actions

This Discussion