cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Announcements

Community Helping Community

274
Views
0
Helpful
2
Replies
Beginner

Random APs with Packet Loss and High Latency

Hello,

 

We have here only 1 Cisco 5508 WLC catering to 490+ APs (AIR-CAP702W and some AIR-CAP702I) running with software version of 8.0.140.0. These APs are connected to C2960X. I am monitoring these APs from my office. The issue is I am experiencing 1-3 APs a day experiencing VERY HIGH latency and packet loss at the same time. Due to this, it makes me unable to SSH to these APs to check what is going on. In addition, I am unable to check these AP physically since AP is located on a  guest room but being unable to SSH makes me think that something is really going on this AP.

 

1613.PNG

 

An example of an AP I rebooted as soon as I see the same issue. 

 

Reply from 172.17.16.13: bytes=32 time<1ms TTL=254
Reply from 172.17.16.13: bytes=32 time<1ms TTL=254
Reply from 172.17.16.13: bytes=32 time<1ms TTL=254
Reply from 172.17.16.13: bytes=32 time<1ms TTL=254
Reply from 172.17.16.13: bytes=32 time<1ms TTL=254
Reply from 172.17.16.13: bytes=32 time<1ms TTL=254
Reply from 172.17.16.13: bytes=32 time<1ms TTL=254
Reply from 172.17.16.13: bytes=32 time<1ms TTL=254
Reply from 172.17.16.13: bytes=32 time<1ms TTL=254
Reply from 172.17.16.13: bytes=32 time<1ms TTL=254
Reply from 172.17.16.13: bytes=32 time<1ms TTL=254
Reply from 172.17.16.13: bytes=32 time<1ms TTL=254
Reply from 172.17.16.13: bytes=32 time<1ms TTL=254
Reply from 172.17.16.13: bytes=32 time<1ms TTL=254
Reply from 172.17.16.13: bytes=32 time<1ms TTL=254
Reply from 172.17.16.13: bytes=32 time<1ms TTL=254
Reply from 172.17.16.13: bytes=32 time<1ms TTL=254
Reply from 172.17.16.13: bytes=32 time<1ms TTL=254
Reply from 172.17.16.13: bytes=32 time<1ms TTL=254
Reply from 172.17.16.13: bytes=32 time<1ms TTL=254
Reply from 172.17.16.13: bytes=32 time<1ms TTL=254
Reply from 172.17.16.13: bytes=32 time<1ms TTL=254
Reply from 172.17.16.13: bytes=32 time<1ms TTL=254
Reply from 172.17.16.13: bytes=32 time<1ms TTL=254
Reply from 172.17.16.13: bytes=32 time<1ms TTL=254
Reply from 172.17.16.13: bytes=32 time<1ms TTL=254
Reply from 172.17.16.13: bytes=32 time<1ms TTL=254
Reply from 172.17.16.13: bytes=32 time<1ms TTL=254
Reply from 172.17.16.13: bytes=32 time<1ms TTL=254
Reply from 172.17.16.13: bytes=32 time<1ms TTL=254
Reply from 172.17.16.13: bytes=32 time=1ms TTL=254
Reply from 172.17.16.13: bytes=32 time<1ms TTL=254
Reply from 172.17.16.13: bytes=32 time<1ms TTL=254
Reply from 172.17.16.13: bytes=32 time<1ms TTL=254
Reply from 172.17.16.13: bytes=32 time<1ms TTL=254
Reply from 172.17.16.13: bytes=32 time<1ms TTL=254
Reply from 172.17.16.13: bytes=32 time=180ms TTL=254
Reply from 172.17.16.13: bytes=32 time<1ms TTL=254
Reply from 172.17.16.13: bytes=32 time<1ms TTL=254
Reply from 172.17.16.13: bytes=32 time=22ms TTL=254
Reply from 172.17.16.13: bytes=32 time=5ms TTL=254
Reply from 172.17.16.13: bytes=32 time<1ms TTL=254
Reply from 172.17.16.13: bytes=32 time=841ms TTL=254
Reply from 172.17.16.13: bytes=32 time=559ms TTL=254
Reply from 172.17.16.13: bytes=32 time=246ms TTL=254
Reply from 172.17.16.13: bytes=32 time=220ms TTL=254
Request timed out.
Request timed out.
Reply from 172.17.16.13: bytes=32 time=540ms TTL=254
Reply from 172.17.16.13: bytes=32 time=1206ms TTL=254
Reply from 172.17.16.13: bytes=32 time=401ms TTL=254
Request timed out.
Request timed out.
Request timed out.
Reply from 172.17.16.13: bytes=32 time=146ms TTL=254
Request timed out.
Reply from 172.17.16.13: bytes=32 time=197ms TTL=254
Request timed out.
Request timed out.
Request timed out.
Reply from 172.17.16.13: bytes=32 time=286ms TTL=254
Request timed out.
Reply from 172.17.16.13: bytes=32 time=746ms TTL=254
Request timed out.
Request timed out.
Reply from 172.17.16.13: bytes=32 time=269ms TTL=254
Reply from 172.17.16.13: bytes=32 time=234ms TTL=254
Request timed out.
Request timed out.
Reply from 172.17.16.13: bytes=32 time=507ms TTL=254
Reply from 172.17.16.13: bytes=32 time=189ms TTL=254
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 172.17.16.13: bytes=32 time=743ms TTL=254
Request timed out.
Request timed out.
Request timed out.
Reply from 172.17.16.13: bytes=32 time=423ms TTL=254
Request timed out.
Reply from 172.17.16.13: bytes=32 time=200ms TTL=254

 

I checked for the switch port's current status and I do not see anything that might ignite this issue.

 

GigabitEthernet1/0/13 is up, line protocol is up (connected) 
  Hardware is Gigabit Ethernet, address is ac7e.8acd.3e8d (bia ac7e.8acd.3e8d)
  Description: [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:20, output 00:00:01, output hang never
  Last clearing of "show interface" counters never
  Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 1277
  Queueing strategy: fifo
  Output queue: 0/40 (size/max)
  30 second input rate 2000 bits/sec, 1 packets/sec
  30 second output rate 497000 bits/sec, 684 packets/sec
     48947055 packets input, 12246227826 bytes, 0 no buffer
     Received 881499 broadcasts (623645 multicasts)
     0 runts, 0 giants, 0 throttles
     0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
     0 watchdog, 623645 multicast, 0 pause input
     0 input packets with dribble condition detected
     3847557557 packets output, 421084438218 bytes, 0 underruns
     0 output errors, 0 collisions, 1 interface resets
     210933 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

Currently, my workaround for this issue is to reboot the AP, bounce the port connecting to AP and if these steps still do not work, I eventually lead to clearing the AP's config to its default config via WLC. It works. However, next day after, another AP is experiencing just the same issue I had yesterday. Sometimes, it's the same AP. I keep searching for this issue if this is a bug but I can't find any. Hoping for your insights. Thanks.

 

2 REPLIES 2
Hall of Fame Community Legend

Re: Random APs with Packet Loss and High Latency

IF rebooting the AP is workaround then I'd recommend upgrading the firmware of the WLC first and see if there are any improvements.
8.0.140.0 was released 3 years ago.
Highlighted
Beginner

Re: Random APs with Packet Loss and High Latency

Most of the time I clear the AP's configs to set it to its factory default as the main workaround for this reoccurring issue. But I will take note of this.

CreatePlease to create content
Content for Community-Ad

August's Community Spotlight Awards