In a message dated 9/3/00 11:48:21 PM Eastern Daylight Time,
[EMAIL PROTECTED] writes:
<< Hssi4/0 is up, line protocol is up
Hardware is M2T-HSSI-B
MTU 4470 bytes, BW 45045 Kbit, DLY 200 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation HDLC, crc 16, loopback not set
Keepalive set (10 sec)
Last input 00:00:00, output 00:00:00, output hang never
Last clearing of "show interface" counters 1w4d
Queueing strategy: fifo
Output queue 0/40, 94 drops; input queue 0/75, 7 drops
30 second input rate 152000 bits/sec, 26 packets/sec
30 second output rate 14000 bits/sec, 18 packets/sec
4392773 packets input, 2649138142 bytes, 0 no buffer
Received 0 broadcasts, 0 runts, 7 giants, 2 throttles
0 parity
6492 input errors, 6026 CRC, 0 frame, 261 overrun, 2 ignored, 205 abort
5518158 packets output, 917289728 bytes, 0 underruns
0 output errors, 0 applique, 46 interface resets
0 output buffer failures, 0 output buffers swapped out
60 carrier transitions LC=down CA=up TM=down LB=down TA=up
LA=down
>>
You've definately got errors on this line...If this is a line with the telco
you should call them and set up a test window when the net is not in use so
that they can run some tests. What you should do to get a better
understanding of the amount of errors is do a "Clear counters Hssi4/0"
command. This will clear the interface and you can monitor how many errors
you get over a certain period of time... Try that for now...Hope it helps...
;)
Mark Zabludovsky ~ CCNA, CCDA
<A HREF="mailto: [EMAIL PROTECTED]">[EMAIL PROTECTED]</A>
If the automobile had followed the same development as the computer, a
Rolls-Royce would today cost $100, get a million miles per gallon, and
explode once a year killing everyone inside.
~Robert Cringely, InfoWorld~
___________________________________
UPDATED Posting Guidelines: http://www.groupstudy.com/list/guide.html
FAQ, list archives, and subscription info: http://www.groupstudy.com
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
