how common is it to see input pause on interfaces connected to an AP

Hello,

​

We have a number of Meraki AP's connectioned to 2960x switches. All pretty standard - 1gbps trunk ports on the switches, couple of SSIDs broadcasting on the AP's and not many (currently 0) clients connected to the AP.

I've read that the input pause counter is the interface sending pause messages to the connected devices to wait before transmitting to allow the switch to clear its queue/buffer. Given that this interface is not likely to be oversubscribed, why would the input pause counter be increasing?

I cant see anything else of concern on the interface but we get complaints about WiFi now and then and I'd like to ensure that any underlying issues are ironed out

​

Is it normal to see input pause counters increment on trunk ports connected to access points? i reset the counters shortly before posting this

​

thanks

Description: Link to Meraki AP

MTU 1500 bytes, BW 1000000 Kbit/sec, DLY 10 usec,

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

Encapsulation ARPA, loopback not set

Keepalive set (10 sec)

Full-duplex, 1000Mb/s, media type is 10/100/1000BaseTX

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

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

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

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

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 7.0 kilobits , 3 pps

5 minute output rate 73.0 kilobits , 39 pps

2,970 packets input, 1,514,845 bytes, 0 no buffer

Received 370 broadcasts (332 multicasts)

0 runts, 0 giants, 0 throttles

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

0 watchdog, 332 multicast, 13,502 pause input

0 input packets with dribble condition detected

62,076 packets output, 25,874,223 bytes, 0 underruns

0 output errors, 0 collisions, 0 interface resets

0 unknown protocol drops

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