cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
548
Views
0
Helpful
5
Replies

Switch port bandwidth problem

branfarm1
Enthusiast
Enthusiast

Hi there,

I have a Cisco 3020 bladeswitch that is only reporting interface bandwidth of 10000Kbit when the link is actually a gigabit interface:

GigabitEthernet0/9 is up, line protocol is up (connected)

Hardware is Gigabit Ethernet, address is 001b.0c06.4909 (bia 001b.0c06.4909)

MTU 1500 bytes, BW 10000 Kbit, DLY 1000 usec,

reliability 255/255, txload 1/255, rxload 21/255

Encapsulation ARPA, loopback not set

Keepalive set (10 sec)

Auto-duplex, Auto-speed, link type is auto, media type is 1000BaseX

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

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

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

Last clearing of "show interface" counters 00:29:44

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

Queueing strategy: fifo

Output queue: 0/40 (size/max)

5 minute input rate 844000 bits/sec, 54 packets/sec

5 minute output rate 13000 bits/sec, 37 packets/sec

179197 packets input, 243202451 bytes, 0 no buffer

Received 42 broadcasts (0 multicast)

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

134878 packets output, 9565053 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

Here's the interface configuration:

Current configuration : 60 bytes

!

interface GigabitEthernet0/9

spanning-tree portfast

end

I've tried having both sides as Auto, and both sides set manually, with no luck. Has anyone seen this issue before? Any ideas?

Thanks in advance

1 Accepted Solution

Accepted Solutions

garytayl
Participant
Participant

If you are running 12.2(25)SEF2, There is an internal cosmetic bug for that. It is first fixed in 12.2(35)SE.

View solution in original post