AIR-CAP3702I-D-K9 disassociating intermittently

[shyamradhe]

Hello All

I am having some Wireless issue in my network with one AP- AIR-CAP3702I-D-K9-

It is disassociating 2-3 times in one day on regular basis, and i want to know why it is happening.

I just did some troubleshooting from my side and i want to share the output with you guys .

>My WLC module is -5508, SW version- 8.0.133.0

>checked logs on WLC and found 

"ap disassociated. base radio mac xxxx"

"some deauth pkts"

"IDS signature attack"

>AP never rebooted it's just for 2-3 seconds and every thing comes back normal.

>Cable test.

show cable-diagnostic tdt interface <gi>   -which is noraml

>Date ,Time, Zone all is okay on WLC and AP.

>checked country code which is India in my case - Okay.

>checked Power status of AP which is like below.

PoE/full Power.

>checked PoE status on switch interface which is.

16.8 Watts - I am not sure if it is okay for my ap module!!

>Also schedule an activity for NIC driver update for users.

Not sure for this too if will it resolve the issue or not ?! 

So Guys is there any thing else where i need to look at ? kindly check my observation above and let me know if any thing noticeable.

Also one thing I need to know that if these APs automatically selects the channels to run for, or we can hard code any AP to run on specific channel only.

If yes then "what would be the best practice to do that" you can share any link for this .

[Leo Laohoo]

show cable-diagnostic tdt interface <gi>   -which is noraml

I want to see the complete result.  

>checked logs on WLC and found 

Post the complete switchport output to the command "sh interface <BLAH> cont".

[shyamradhe]

Hi Leo

1- CINSUR01FINSW03#show cable-diagnostics tdr interface gigabitEthernet 1/0/45
TDR test last run on: April 21 09:35:05

Interface Speed Local pair Pair length Remote pair Pair status
--------- ----- ---------- ------------------ ----------- --------------------
Gi1/0/45 1000M Pair A 75 +/- 0 meters Pair A Normal
                           Pair B 71 +/- 0 meters Pair B Normal
                           Pair C 77 +/- 0 meters Pair C Normal
                           Pair D 71 +/- 0 meters Pair D Normal

2-

CINSUR01FINSW03#show interfaces gigabitEthernet 1/0/45 controller
GigabitEthernet1/0/45 is up, line protocol is up (connected)
Hardware is Gigabit Ethernet, address is f025.7207.78ad (bia f025.7207.78ad)
Description: "Fiat_Conf_IP_Ph"
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:09, output 00:00:00, output hang never
Last clearing of "show interface" counters never
Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 3396
Queueing strategy: fifo
Output queue: 0/40 (size/max)
5 minute input rate 82000 bits/sec, 33 packets/sec
5 minute output rate 164000 bits/sec, 34 packets/sec
240430629 packets input, 81874759716 bytes, 0 no buffer
Received 497163 broadcasts (323197 multicasts)
0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
0 watchdog, 323197 multicast, 0 pause input
0 input packets with dribble condition detected
368161127 packets output, 227257668156 bytes, 0 underruns
0 output errors, 0 collisions, 1 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

Transmit GigabitEthernet1/0/45                             Receive
3919368764 Bytes                                         270381092 Bytes
358158666 Unicast frames                            239933466 Unicast frames
6499542 Multicast frames                              323197 Multicast frames
3502919 Broadcast frames                            173966 Broadcast frames
0 Too old frames                                             133586610 Unicast bytes
0 Deferred frames                                           111388646 Multicast bytes
0 MTU exceeded frames                                 25405836 Broadcast bytes
0 1 collision frames                                         0 Alignment errors
0 2 collision frames                                         0 FCS errors
0 3 collision frames                                         0 Oversize frames
0 4 collision frames                                          0 Undersize frames
0 5 collision frames                                          0 Collision fragments
0 6 collision frames
0 7 collision frames                                          625803 Minimum size frames
0 8 collision frames                                          2572010 65 to 127 byte frames
0 9 collision frames                                           177094417 128 to 255 byte frames
0 10 collision frames                                        22868130 256 to 511 byte frames
0 11 collision frames                                        10228123 512 to 1023 byte frames
0 12 collision frames                                        27042146 1024 to 1518 byte frames
0 13 collision frames                                        0 Overrun frames
0 14 collision frames                                        0 Pause frames
0 15 collision frames
0 Excessive collisions                                      0 Symbol error frames
0 Late collisions                                               0 Invalid frames, too large
0 VLAN discard frames                                    0 Valid frames, too large
0 Excess defer frames                                     0 Invalid frames, too small
2633134 64 byte frames                                  0 Valid frames, too small
64851487 127 byte frames
144307953 255 byte frames                             0 Too old frames
21695576 511 byte frames                                 0 Valid oversize frames
12359233 1023 byte frames                             0 System FCS error frames
122313744 1518 byte frames                           0 RxPortFifoFull drop frame
0 Too large frames
0 Good (1 coll) frames
0 Good (>1 coll) frames

[Leo Laohoo]

What is the uptime of the switch?

[shyamradhe]

CINSUR01FINSW03 uptime is 8 weeks, 6 days, 2 hours, 2 minutes

[Leo Laohoo]

Mea culpa!  I meant what's the uptime of the AP.  

[shyamradhe]

Fiat_conf_WAP01 uptime is 1 week, 1 day, 13 hours, 5 minutes

[shyamradhe]

one more observation i want to add here that since last day i am not getting disassociation logs, nor any user complaints so just checked and found that the number of clients connected to this AP is only 17 , this is less than the previous days when i countered this issue, clients counts was 25-30 that time... Is this also could be a reason of disconnection ? I am not sure !

[Scott Fella]

What you need to look at is if the AP is detecting radar events. This can take down the service on the 5ghz for up to 30 seconds if an event is triggered.  Is the issue only with one AP and not any of the others?  Have you scrubbed the WLC logs to check for radar events?  Is your DCA set to 24 hours and not default at 10 minutes?  Channel changes also can drop clients, so baseline the channel and power levels over a week, maybe couple times a day and see if channels and or power changes.

-Scott 

*** Please rate helpful posts *** 

[George Stefanick]

The best way is to be onsite pick a few vocal users and run debugs on their macs and bridges dog it. You can also look at the windows event logs and see if you see any codes that show WLAN disconnects. 

[shyamradhe]

Sorry for delayed reply, as i was busy to resolve this issue but no luck :( 

one more thing i want to share here, today i also faced complete network outage 

when i checked my core(not redundant-single core) i found below TCN logs...

CINSUR01CORESW01#show spanning-tree detail | i ieee|occurr|from|is exec
VLAN0001 is executing the rstp compatible Spanning Tree protocol
Number of topology changes 5257 last change occurred 00:00:18 ago
from GigabitEthernet1/2
VLAN0010 is executing the rstp compatible Spanning Tree protocol
Number of topology changes 662 last change occurred 00:00:49 ago
from GigabitEthernet1/1
VLAN0020 is executing the rstp compatible Spanning Tree protocol
Number of topology changes 643 last change occurred 00:00:49 ago
from GigabitEthernet1/1
VLAN0025 is executing the rstp compatible Spanning Tree protocol
Number of topology changes 645 last change occurred 00:00:49 ago
from GigabitEthernet1/1
VLAN0040 is executing the rstp compatible Spanning Tree protocol
Number of topology changes 645 last change occurred 00:00:49 ago
from GigabitEthernet1/1
VLAN0041 is executing the rstp compatible Spanning Tree protocol
Number of topology changes 644 last change occurred 00:00:49 ago
from GigabitEthernet1/1
VLAN0042 is executing the rstp compatible Spanning Tree protocol
Number of topology changes 645 last change occurred 00:00:49 ago
from GigabitEthernet1/1
VLAN0043 is executing the rstp compatible Spanning Tree protocol
Number of topology changes 645 last change occurred 00:00:49 ago
from GigabitEthernet1/1
VLAN0044 is executing the rstp compatible Spanning Tree protocol
Number of topology changes 645 last change occurred 00:00:49 ago
from GigabitEthernet1/1
VLAN0045 is executing the rstp compatible Spanning Tree protocol
Number of topology changes 645 last change occurred 00:00:49 ago
from GigabitEthernet1/1
VLAN0050 is executing the rstp compatible Spanning Tree protocol
Number of topology changes 649 last change occurred 00:00:49 ago
from GigabitEthernet1/1
VLAN0055 is executing the rstp compatible Spanning Tree protocol
Number of topology changes 645 last change occurred 00:00:49 ago
from GigabitEthernet1/1

is this mean that i have loop in my network ?, and can this also be the cause of clients disconnection over Wireless  ?.

[Leo Laohoo]

Hmmmm ... Gi 1/1.  This means the appliance is a chassis-based system, like a 6500 or 4500, without VSS enabled.  

Is Gi 1/1 the downlink to the switch where the AP in question is?  If so, post the complete output to the command "sh run interface Gi1/1" as well as "sh interface Gi 1/1".

I forgot to ask what is the Association time of the AP to the controller?  Is the AP powered using PoE, injector or a power brick?

[shyamradhe]

Hi Leo

AP is powered using PoE /full power.

AP never rebooted. Although there is some log which says. "AP disassociate due to link failure". (users disconnected only for 1-2 seconds and connects automatically).

Now i am stuck with Core too :( , don't know if these two incedents are related to each other or not .

i am still can see TCN incresaing as i mentioned on my previous reply.

@Leo - as per my previous TCN logs, is that thing really serious ?

or that is common.?

GigabitEthernet1/1 is up, line protocol is up (connected)
Hardware is Gigabit Ethernet Port, address is 58ac.785f.2654 (bia 58ac.785f.2654)
MTU 1500 bytes, BW 1000000 Kbit/sec, DLY 10 usec,
reliability 255/255, txload 14/255, rxload 1/255
Encapsulation ARPA, loopback not set
Keepalive set (10 sec)
Full-duplex, 1000Mb/s, link type is auto, media type is 1000BaseSX
input flow-control is off, output flow-control is off
ARP type: ARPA, ARP Timeout 04:00:00
Last input 00:00:00, output never, output hang never
Last clearing of "show interface" counters 5d00h
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 3993000 bits/sec, 4194 packets/sec
5 minute output rate 55816000 bits/sec, 5581 packets/sec
132990464 packets input, 27390769699 bytes, 0 no buffer
Received 3402818 broadcasts (3058266 multicasts)
0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
0 input packets with dribble condition detected
233685813 packets output, 203105977020 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 output buffer failures, 0 output buffers swapped out

CINSUR01CORESW01#show running-config interface gigabitEthernet 1/1
Building configuration...

Current configuration : 59 bytes
!
interface GigabitEthernet1/1
switchport mode trunk
end

[Leo Laohoo]

Last clearing of "show interface" counters 5d00h

Why was the "sh interface" counters for Gi 1/1 cleared 5 days ago?

[shyamradhe]

As I said earlier due to network outage 5 days ago, we cleared the current interfaces counters for troubleshooting purpose.