Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements
Webcast-Catalyst9k
New Member

10 Gig Interface stats

Does anyone know what "throttles" mean on 10 interface stats. Is it a issue, whats causing this.

Thanks.

TenGigabitEthernet1/1 is up, line protocol is up (connected)

Hardware is C6k 10000Mb 802.3, address is 0015.c746.4800 (bia 0015.c746.4800)

Description: 10g Connection to LN-BSQ-0A-CER1-DDIST-1A

Internet address is 172.28.1.170/30

MTU 1500 bytes, BW 10000000 Kbit, DLY 10 usec,

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

Encapsulation ARPA, loopback not set

Keepalive set (10 sec)

Carrier delay is 0 msec

Full-duplex, 10Gb/s

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

ARP type: ARPA, ARP Timeout 00:25:00

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

Last clearing of "show interface" counters 1w1d

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

Queueing strategy: fifo

Output queue: 0/40 (size/max)

30 second input rate 123000 bits/sec, 182 packets/sec

30 second output rate 2702000 bits/sec, 322 packets/sec

L2 Switched: ucast: 4610837 pkt, 413638781 bytes - mcast: 763160 pkt, 90053981 bytes

L3 in Switched: ucast: 28297584 pkt, 12157030270 bytes - mcast: 0 pkt, 0 bytes mcast

L3 out Switched: ucast: 34006365 pkt, 27458288081 bytes mcast: 0 pkt, 0 bytes

34055244 packets input, 12692520423 bytes, 0 no buffer

Received 1145429 broadcasts (763120 IP multicast)

0 runts, 0 giants, 4967 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

39597225 packets output, 28007200104 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

1 REPLY
New Member

Re: 10 Gig Interface stats

Hi,

Throttles usually occurs when the interfaces input hold queue is full.

Probably packets are comming faster than interface can process them...

Check the nature of this. If it is simply short time bursts you can simply increase lenght of the input queue...

//Mikhail Galiulin

143
Views
0
Helpful
1
Replies
CreatePlease to create content