cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
988
Views
0
Helpful
6
Replies

ignored error

mehrdad
Level 3
Level 3

Hi,

We're experiencing packet loss on our Cisco 7500 on its fastethernet.I see many packets are ignored on its interface ,pls see below :

30 second input rate 24196000 bits/sec, 13028 packets/sec

30 second output rate 16765000 bits/sec, 12792 packets/sec

14947291 packets input, 3482369644 bytes

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

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

0 watchdog

0 input packets with dribble condition detected

14598828 packets output, 2399689100 bytes, 0 underruns

0 output errors, 1905365178 collisions, 0 interface resets

Its avarage cpu usage is 40%, is there any solution to solve this problem?

any help will be appreciated

Thanks

Mehrdad

6 Replies 6

fabricio.monte
Level 1
Level 1

Hi,

The problem may be in the FEIP ou VIP Card that your PA fast is attached. It can be that the CPU usage in FEIP ou VIP Card was very high.

A question: do you have any rate-limit in this FastEthernet ?

Regards,

Fabricio

Network analyst

thank you for your reply.

yes, we have rate-limit on this interface, do you have any suggection?

Thanks

Mehrdad

scottmac
Level 10
Level 10

I believe that you are having problems, but the info you posted (especially the collisions rate) is fairly useless without knowing when the last Counter Reset occurred.

The fact that you have collisions at all on a (presumed) full duplex interface is a problem all by itself.

Check your duplex setting on both sides, hard code them, as possible, into agreement.

The ignored packets by be products of the collision frames.

Please reset your counters, and give us an idea of the rate at which the errors are accumulating.

Good Luck

Scott

Thank you for you reply, please see below :

FastEthernet5/1 is up, line protocol is up

Hardware is cyBus FastEthernet Interface, address is 0030.7bc4.90a1 (bia 0030.7bc4.90a1)

Description: OUT-LAN

MTU 1500 bytes, BW 100000 Kbit, DLY 100 usec,

reliability 255/255, txload 42/255, rxload 61/255

Encapsulation ARPA, loopback not set

Keepalive set (10 sec)

Full-duplex, 100Mb/s, 100BaseTX/FX

ARP type: ARPA, ARP Timeout 04:00:00

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

Last clearing of "show interface" counters 00:19:06

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

Queueing strategy: fifo

Output queue: 0/1000 (size/max)

30 second input rate 24196000 bits/sec, 13028 packets/sec

30 second output rate 16765000 bits/sec, 12792 packets/sec

14947291 packets input, 3482369644 bytes

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

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

0 watchdog

0 input packets with dribble condition detected

14598828 packets output, 2399689100 bytes, 0 underruns

0 output errors, 1905365178 collisions, 0 interface resets

0 babbles, 0 late collision, 0 deferred

0 lost carrier, 0 no carrier

0 output buffer failures, 0 output buffers swapped out

After ~15 seconds ->

FastEthernet5/1 is up, line protocol is up

Hardware is cyBus FastEthernet Interface, address is 0030.7bc4.90a1 (bia 0030.7bc4.90a1)

Description: OUT-LAN

MTU 1500 bytes, BW 100000 Kbit, DLY 100 usec,

reliability 255/255, txload 43/255, rxload 62/255

Encapsulation ARPA, loopback not set

Keepalive set (10 sec)

Full-duplex, 100Mb/s, 100BaseTX/FX

ARP type: ARPA, ARP Timeout 04:00:00

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

Last clearing of "show interface" counters 00:19:24

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

Queueing strategy: fifo

Output queue: 0/1000 (size/max)

30 second input rate 24586000 bits/sec, 13070 packets/sec

30 second output rate 16881000 bits/sec, 12860 packets/sec

15186674 packets input, 3539736336 bytes

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

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

0 watchdog

0 input packets with dribble condition detected

14834883 packets output, 2438576331 bytes, 0 underruns

0 output errors, 1901154422 collisions, 0 interface resets

0 babbles, 0 late collision, 0 deferred

0 lost carrier, 0 no carrier

0 output buffer failures, 0 output buffers swapped out

Suggest to identify what is connected to your f5/1 fastethernet port and also perform a cable test .. to make sure the connection to this port is OK and not breaking the 100 meters maximum distance rule.

So many collisions could be due to faulty NICs, broken cables or too many stations sharing that port.

Also please post the ouput of show buffers in case your buffers can be tuned up

Just in case..Have you done a 'shut' and 'no shut' on the fa interfaces?