Too much traffic on interface. Link L2 between SW4500-SW6500

mcystylo27 · ‎05-23-2013

Hi everyone, i hope anyone can help me with a problem of a LINK L2, Between SW4500 and SW6500.

I have experience too much traffic between the link L2 (Fastethernet - GigabitEthernet),, 90%. What can I do to fix that, any command? rate-limit or something?

Here is some outputs of the interfaces:

FastEthernet2/30 is up, line protocol is up (connected)

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

reliability 255/255, txload 247/255, rxload 27/255

Encapsulation ARPA, loopback not set

Keepalive set (10 sec)

Full-duplex, 100Mb/s

input flow-control is unsupported output flow-control is unsupported

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

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

Last clearing of "show interface" counters 4w0d

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

Queueing strategy: fifo

Output queue: 0/40 (size/max)

5 minute input rate 10824000 bits/sec, 3091 packets/sec

5 minute output rate 97251000 bits/sec, 8037 packets/sec

2689449777 packets input, 1208566367319 bytes, 0 no buffer

Received 102306260 broadcasts (48742487 multicast)

0 runts, 0 giants, 0 throttles

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

0 input packets with dribble condition detected

6488342448 packets output, 9556099159094 bytes, 0 underruns

0 output errors, 0 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

GigabitEthernet3/3 is up, line protocol is up (connected)

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

reliability 255/255, txload 29/255, rxload 248/255

Encapsulation ARPA, loopback not set

Keepalive set (10 sec)

Full-duplex, 100Mb/s

input flow-control is off, output flow-control is on

Clock mode is auto

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

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

Last clearing of "show interface" counters 16w1d

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

Queueing strategy: fifo

Output queue: 0/40 (size/max)

30 second input rate 97430000 bits/sec, 8086 packets/sec

30 second output rate 11558000 bits/sec, 3214 packets/sec

23652164256 packets input, 34716225186331 bytes, 0 no buffer

Received 393377785 broadcasts (391598650 multicasts)

0 runts, 0 giants, 0 throttles

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

0 watchdog, 0 multicast, 0 pause input

0 input packets with dribble condition detected

9618336659 packets output, 4777117555931 bytes, 0 underruns

0 output errors, 0 collisions, 0 interface resets

0 babbles, 0 late collision, 0 deferred

0 lost carrier, 0 no carrier, 0 PAUSE output

0 output buffer failures, 0 output buffers swapped out

Thanks for your comments

mfurnival · ‎05-29-2013

Hi Jose,

What is too much traffic? The switches are only forwarding the traffic that they need to forward. If performance is being impacted you can use QoS for prioritization but you need to decide what traffic should get priority.

I noticed that you have fastethernet on one side and gigabit ethernet on the other so the link is only going to run at 100Mb. If you have a gig interface on the other switch use that and your utilization will drop to 1/10 of what it is now.