some wireless clients, after a few hours, can only send traffic

[a.hamidreza]

After a few hours of connection to wireless, some wireless clients cannot receive any traffic, but they can send traffic. After disconnecting and reconnecting, everything is ok.

[MHM Cisco World]

follow

[marce1000]

 -  Describe your wireless-infrastructure , controller-model (?) , if applicable. What ap-models are being used ? What software version(s) are you on ?

 M.

[a.hamidreza]

There is a 3504 controller connected with one ethernet interface to the core switch, and the mixture of 30, 1832, and 1852 access points are connected to access switches. Connectivity between APs and WLC is layer 2, and APs configured local ap mode. Users connected with 802.1x to WLAN and radius server is cisco ISE.
the software version is: 8.10.162.0.

[marce1000]

 - Have a sanity check of the controller configuration with : https://cway.cisco.com/tools/WirelessAnalyzer/  - you can also do client debugging and have those debugging-outputs analyzed with : https://cway.cisco.com/tools/WirelessDebugAnalyzer/  a how to is provided in the following link : https://www.cisco.com/c/en/us/support/docs/wireless/aironet-1200-series/100260-wlc-debug-client.html

 M.

[a.hamidreza]

Thanks for your help.
I will check the configuration with the analyzer.

[MHM Cisco World]

Forward ARP Requests to Radio Interfaces When Not All Client IP Addresses Are Known

When a non-Cisco client device is associated to an access point and is not passing data, the access point might not know the client's IP address. If this situation occurs frequently on your wireless LAN, you can enable this check box. In this case, the access point responds on behalf of clients with IP addresses known to the access point but forwards out its radio port any ARP requests addressed to unknown clients. When the access point learns the IP addresses for all associated clients, it drops ARP requests not directed to its associated clients.

I think this is due to ARP missing.

[a.hamidreza]

Thanks for your help.
When disruption occurred, I checked the client. It can send traffic but cannot receive any traffic. I pinged another laptop with it, and with Wireshark saw the ping request received and sent the reply, but on the faulty laptop, I didn't receive any ping reply.
After that, I cleared the arp cache of the faulty laptop on the core switch, and It can learn the arp of that again.
The ARP cache on both laptops was correct.