WLC with many of clients associated but most do not respond to the ping and people lose connectivity...

jjalonsom · ‎05-13-2019

Hi, I have a big problem with the wireless network for a long time. The company I work in is dedicated to the repair of cell phones, tablets, etc and all day these devices are connecting to the wireless to download certain things and then they must be disconnected so that the access points are not saturated (in theory the user must do it).

One of the biggest problems is that the access points are filled with customers and there are connection problems.

I have noticed that many of the clients that appear associated in the controller do not respond to the ping that I send them, even though they appear as "associated".
I go to production and ask how many devices are they using and they tell me 20, and in the controller I see there are 150 (this is an example taking an area where there are 2 access points).

In the Controller I have between 800 and 1100 associated clients daily, but reviewing the areas of the company and talking with the supervisors this number should be much lower.

Currently I have an open case with the Cisco TAC due to a bug in our model access points "AIR-AP1572EAC-A-K9" but this happens with so many connections this before the bug.

WLC: 5520

Code: 8.5.135.0

19 x AIR-AP1572EAC-A-K9

2 x AIR-AP3802I-A-K9

1 x AIR-AP3802E-B-K9

Actually we have an open project to replace "AIR-AP1572EAC-A-K9" for "AIR-AP3802P-A-K9 with directional antennas AIR-ANT2513P4MN= to work with a high density environment.

"

This is an example of a client that appears associated from an hour and a half and has an assigned IP but does not respond.

(Cisco Controller) >debug client 10:f1:f2:83:74:76

(Cisco Controller) >
(Cisco Controller) >
(Cisco Controller) >*DHCP Socket Task: May 13 08:50:40.821: [PA] 10:f1:f2:83:74:76 DHCP successfully bridged packet to STA
*DHCP Socket Task: May 13 09:10:41.647: [PA] 10:f1:f2:83:74:76 DHCP received op BOOTREQUEST (1) (len 324,vlan 1, port 1, encap 0xec03, xid 0xe34e29e1)
*DHCP Socket Task: May 13 09:15:42.114: [PA] 10:f1:f2:83:74:76 DHCP received op BOOTREQUEST (1) (len 324,vlan 1, port 1, encap 0xec03, xid 0xd86fc793)
*DHCP Socket Task: May 13 09:15:42.114: [PA] 10:f1:f2:83:74:76 DHCP (encap type 0xec03) mstype 000:21:9b:8d:e1:e0
*DHCP Socket Task: May 13 09:15:42.114: [PA] 10:f1:f2:83:74:76 DHCP processing DHCP REQUEST (3)
*DHCP Socket Task: May 13 09:15:42.114: [PA] 10:f1:f2:83:74:76 DHCP op: BOOTREQUEST, htype: Ethernet, hlen: 6, hops: 0
*DHCP Socket Task: May 13 09:15:42.114: [PA] 10:f1:f2:83:74:76 DHCP xid: 0x93c76fd8 (2479321048), secs: 0, flags: 0
*DHCP Socket Task: May 13 09:15:42.114: [PA] 10:f1:f2:83:74:76 DHCP chaddr: 10:f1:f2:83:74:76
*DHCP Socket Task: May 13 09:15:42.114: [PA] 10:f1:f2:83:74:76 DHCP ciaddr: 172.18.1.176, yiaddr: 0.0.0.0
*DHCP Socket Task: May 13 09:15:42.114: [PA] 10:f1:f2:83:74:76 DHCP siaddr: 0.0.0.0, giaddr: 0.0.0.0
*DHCP Socket Task: May 13 09:15:42.114: [PA] 10:f1:f2:83:74:76 DHCP Opt82 bridge mode insertion enabled, inserts opt82 if opt82 is enabled vlan=19, datalen =18, optlen=79
*DHCP Socket Task: May 13 09:15:42.114: [PA] 10:f1:f2:83:74:76 DHCP successfully bridged packet to DS
*DHCP Socket Task: May 13 09:15:42.115: [PA] 10:f1:f2:83:74:76 DHCP received op BOOTREPLY (2) (len 312,vlan 19, port 1, encap 0xec00, xid 0xd86fc793)
*DHCP Socket Task: May 13 09:15:42.115: [PA] 10:f1:f2:83:74:76 DHCP processing DHCP ACK (5)
*DHCP Socket Task: May 13 09:15:42.115: [PA] 10:f1:f2:83:74:76 DHCP op: BOOTREPLY, htype: Ethernet, hlen: 6, hops: 0
*DHCP Socket Task: May 13 09:15:42.115: [PA] 10:f1:f2:83:74:76 DHCP xid: 0x93c76fd8 (2479321048), secs: 0, flags: 0
*DHCP Socket Task: May 13 09:15:42.115: [PA] 10:f1:f2:83:74:76 DHCP chaddr: 10:f1:f2:83:74:76
*DHCP Socket Task: May 13 09:15:42.115: [PA] 10:f1:f2:83:74:76 DHCP ciaddr: 0.0.0.0, yiaddr: 172.18.1.176
*DHCP Socket Task: May 13 09:15:42.115: [PA] 10:f1:f2:83:74:76 DHCP server id: 172.18.0.3 rcvd server id: 172.18.0.3
*DHCP Socket Task: May 13 09:15:42.115: [PA] 10:f1:f2:83:74:76 DHCP successfully bridged packet to STA
*DHCP Socket Task: May 13 09:20:42.602: [PA] 10:f1:f2:83:74:76 DHCP received op BOOTREQUEST (1) (len 324,vlan 1, port 1, encap 0xec03, xid 0x4e2e6a6)
*DHCP Socket Task: May 13 09:20:42.602: [PA] 10:f1:f2:83:74:76 DHCP (encap type 0xec03) mstype 000:21:9b:8d:e1:e0
*DHCP Socket Task: May 13 09:20:42.602: [PA] 10:f1:f2:83:74:76 DHCP processing DHCP REQUEST (3)
*DHCP Socket Task: May 13 09:20:42.602: [PA] 10:f1:f2:83:74:76 DHCP op: BOOTREQUEST, htype: Ethernet, hlen: 6, hops: 0
*DHCP Socket Task: May 13 09:20:42.602: [PA] 10:f1:f2:83:74:76 DHCP xid: 0xa6e6e204 (2800148996), secs: 0, flags: 0
*DHCP Socket Task: May 13 09:20:42.602: [PA] 10:f1:f2:83:74:76 DHCP chaddr: 10:f1:f2:83:74:76
*DHCP Socket Task: May 13 09:20:42.602: [PA] 10:f1:f2:83:74:76 DHCP ciaddr: 172.18.1.176, yiaddr: 0.0.0.0
*DHCP Socket Task: May 13 09:20:42.602: [PA] 10:f1:f2:83:74:76 DHCP siaddr: 0.0.0.0, giaddr: 0.0.0.0
*DHCP Socket Task: May 13 09:20:42.602: [PA] 10:f1:f2:83:74:76 DHCP Opt82 bridge mode insertion enabled, inserts opt82 if opt82 is enabled vlan=19, datalen =18, optlen=79
*DHCP Socket Task: May 13 09:20:42.602: [PA] 10:f1:f2:83:74:76 DHCP successfully bridged packet to DS
*DHCP Socket Task: May 13 09:20:42.603: [PA] 10:f1:f2:83:74:76 DHCP received op BOOTREPLY (2) (len 312,vlan 19, port 1, encap 0xec00, xid 0x4e2e6a6)
*DHCP Socket Task: May 13 09:20:42.603: [PA] 10:f1:f2:83:74:76 DHCP processing DHCP ACK (5)
*DHCP Socket Task: May 13 09:20:42.603: [PA] 10:f1:f2:83:74:76 DHCP op: BOOTREPLY, htype: Ethernet, hlen: 6, hops: 0
*DHCP Socket Task: May 13 09:20:42.603: [PA] 10:f1:f2:83:74:76 DHCP xid: 0xa6e6e204 (2800148996), secs: 0, flags: 0
*DHCP Socket Task: May 13 09:20:42.603: [PA] 10:f1:f2:83:74:76 DHCP chaddr: 10:f1:f2:83:74:76
*DHCP Socket Task: May 13 09:20:42.603: [PA] 10:f1:f2:83:74:76 DHCP ciaddr: 0.0.0.0, yiaddr: 172.18.1.176
*DHCP Socket Task: May 13 09:20:42.603: [PA] 10:f1:f2:83:74:76 DHCP siaddr: 0.0.0.0, giaddr: 0.0.0.0
*DHCP Socket Task: May 13 09:20:42.603: [PA] 10:f1:f2:83:74:76 DHCP server id: 172.18.0.3 rcvd server id: 172.18.0.3
*DHCP Socket Task: May 13 09:20:42.603: [PA] 10:f1:f2:83:74:76 DHCP successfully bridged packet to STA
*DHCP Socket Task: May 13 09:25:43.104: [PA] 10:f1:f2:83:74:76 DHCP received op BOOTREQUEST (1) (len 324,vlan 1, port 1, encap 0xec03, xid 0x5ec8a6e1)
*DHCP Socket Task: May 13 09:25:43.104: [PA] 10:f1:f2:83:74:76 DHCP (encap type 0xec03) mstype 000:21:9b:8d:e1:e0
*DHCP Socket Task: May 13 09:25:43.104: [PA] 10:f1:f2:83:74:76 DHCP processing DHCP REQUEST (3)
*DHCP Socket Task: May 13 09:25:43.104: [PA] 10:f1:f2:83:74:76 DHCP xid: 0xe1a6c85e (3785803870), secs: 0, flags: 0
*DHCP Socket Task: May 13 09:25:43.104: [PA] 10:f1:f2:83:74:76 DHCP chaddr: 10:f1:f2:83:74:76
*DHCP Socket Task: May 13 09:25:43.104: [PA] 10:f1:f2:83:74:76 DHCP ciaddr: 172.18.1.176, yiaddr: 0.0.0.0
*DHCP Socket Task: May 13 09:25:43.104: [PA] 10:f1:f2:83:74:76 DHCP siaddr: 0.0.0.0, giaddr: 0.0.0.0
*DHCP Socket Task: May 13 09:25:43.104: [PA] 10:f1:f2:83:74:76 DHCP Opt82 bridge mode insertion enabled, inserts opt82 if opt82 is enabled vlan=19, datalen =18, optlen=79
*DHCP Socket Task: May 13 09:25:43.104: [PA] 10:f1:f2:83:74:76 DHCP successfully bridged packet to DS
*DHCP Socket Task: May 13 09:25:43.105: [PA] 10:f1:f2:83:74:76 DHCP received op BOOTREPLY (2) (len 312,vlan 19, port 1, encap 0xec00, xid 0x5ec8a6e1)
*DHCP Socket Task: May 13 09:25:43.105: [PA] 10:f1:f2:83:74:76 DHCP processing DHCP ACK (5)
*DHCP Socket Task: May 13 09:25:43.105: [PA] 10:f1:f2:83:74:76 DHCP op: BOOTREPLY, htype: Ethernet, hlen: 6, hops: 0
*DHCP Socket Task: May 13 09:25:43.105: [PA] 10:f1:f2:83:74:76 DHCP xid: 0xe1a6c85e (3785803870), secs: 0, flags: 0
*DHCP Socket Task: May 13 09:25:43.105: [PA] 10:f1:f2:83:74:76 DHCP chaddr: 10:f1:f2:83:74:76
*DHCP Socket Task: May 13 09:25:43.105: [PA] 10:f1:f2:83:74:76 DHCP ciaddr: 0.0.0.0, yiaddr: 172.18.1.176
*DHCP Socket Task: May 13 09:25:43.105: [PA] 10:f1:f2:83:74:76 DHCP siaddr: 0.0.0.0, giaddr: 0.0.0.0
*DHCP Socket Task: May 13 09:25:43.105: [PA] 10:f1:f2:83:74:76 DHCP server id: 172.18.0.3 rcvd server id: 172.18.0.3
*DHCP Socket Task: May 13 09:25:43.105: [PA] 10:f1:f2:83:74:76 DHCP successfully bridged packet to STA
*dot1xMsgTask: May 13 09:30:12.264: [PA] 10:f1:f2:83:74:76 key Desc Version FT - 0

*dot1xMsgTask: May 13 09:30:12.264: [PA] 10:f1:f2:83:74:76 Key exchange done, data packets from mobile 10:f1:f2:83:74:76 should be forwarded shortly
*dot1xMsgTask: May 13 09:30:12.264: [PA] 10:f1:f2:83:74:76 key Desc Version FT - 0

*dot1xMsgTask: May 13 09:30:12.264: [PA] 10:f1:f2:83:74:76 Sending EAPOL-Key Message to mobile 10:f1:f2:83:74:76
state PTKINITDONE (message 5 - group), replay counter 00.00.00.00.00.00.00.03
*dot1xMsgTask: May 13 09:30:12.264: [PA] 10:f1:f2:83:74:76 Allocating EAP Pkt for retransmission to mobile 10:f1:f2:83:74:76
*dot1xMsgTask: May 13 09:30:12.264: [PA] 10:f1:f2:83:74:76 Updated broadcast key sent to mobile 10:F1:F2:83:74:76
*dot1xSocketTask: May 13 09:30:12.573: [PA] 10:f1:f2:83:74:76 validating eapol pkt: key version = 2
*Dot1x_NW_MsgTask_6: May 13 09:30:12.573: [PA] 10:f1:f2:83:74:76 Received EAPOL-Key from mobile 10:f1:f2:83:74:76
*Dot1x_NW_MsgTask_6: May 13 09:30:12.573: [PA] 10:f1:f2:83:74:76 Ignoring invalid EAPOL version (1) in EAPOL-key message from mobile 10:f1:f2:83:74:76
*Dot1x_NW_MsgTask_6: May 13 09:30:12.573: [PA] 10:f1:f2:83:74:76 key Desc Version FT - 0

*Dot1x_NW_MsgTask_6: May 13 09:30:12.573: [PA] 10:f1:f2:83:74:76 Received EAPOL-key in REKEYNEGOTIATING state (message 6) from mobile 10:f1:f2:83:74:76
*Dot1x_NW_MsgTask_6: May 13 09:30:12.573: [PA] 10:f1:f2:83:74:76 Freeing EAP Retransmit Bufer for mobile 10:f1:f2:83:74:76
*Dot1x_NW_MsgTask_6: May 13 09:30:12.573: [PA] 10:f1:f2:83:74:76 Stopping retransmission timer for mobile 10:f1:f2:83:74:76
*DHCP Socket Task: May 13 09:30:43.721: [PA] 10:f1:f2:83:74:76 DHCP received op BOOTREQUEST (1) (len 324,vlan 1, port 1, encap 0xec03, xid 0xcf5325be)
*DHCP Socket Task: May 13 09:30:43.721: [PA] 10:f1:f2:83:74:76 DHCP (encap type 0xec03) mstype 000:21:9b:8d:e1:e0
*DHCP Socket Task: May 13 09:30:43.721: [PA] 10:f1:f2:83:74:76 DHCP processing DHCP REQUEST (3)
*DHCP Socket Task: May 13 09:30:43.721: [PA] 10:f1:f2:83:74:76 DHCP op: BOOTREQUEST, htype: Ethernet, hlen: 6, hops: 0
*DHCP Socket Task: May 13 09:30:43.721: [PA] 10:f1:f2:83:74:76 DHCP xid: 0xbe2553cf (3190117327), secs: 0, flags: 0
*DHCP Socket Task: May 13 09:30:43.721: [PA] 10:f1:f2:83:74:76 DHCP chaddr: 10:f1:f2:83:74:76
*DHCP Socket Task: May 13 09:30:43.721: [PA] 10:f1:f2:83:74:76 DHCP ciaddr: 172.18.1.176, yiaddr: 0.0.0.0
*DHCP Socket Task: May 13 09:30:43.721: [PA] 10:f1:f2:83:74:76 DHCP siaddr: 0.0.0.0, giaddr: 0.0.0.0
*DHCP Socket Task: May 13 09:30:43.721: [PA] 10:f1:f2:83:74:76 DHCP Opt82 bridge mode insertion enabled, inserts opt82 if opt82 is enabled vlan=19, datalen =18, optlen=79
*DHCP Socket Task: May 13 09:30:43.721: [PA] 10:f1:f2:83:74:76 DHCP successfully bridged packet to DS
*DHCP Socket Task: May 13 09:30:43.722: [PA] 10:f1:f2:83:74:76 DHCP received op BOOTREPLY (2) (len 312,vlan 19, port 1, encap 0xec00, xid 0xcf5325be)
*DHCP Socket Task: May 13 09:30:43.722: [PA] 10:f1:f2:83:74:76 DHCP processing DHCP ACK (5)
*DHCP Socket Task: May 13 09:30:43.722: [PA] 10:f1:f2:83:74:76 DHCP op: BOOTREPLY, htype: Ethernet, hlen: 6, hops: 0
*DHCP Socket Task: May 13 09:30:43.722: [PA] 10:f1:f2:83:74:76 DHCP xid: 0xbe2553cf (3190117327), secs: 0, flags: 0
*DHCP Socket Task: May 13 09:30:43.722: [PA] 10:f1:f2:83:74:76 DHCP chaddr: 10:f1:f2:83:74:76
*DHCP Socket Task: May 13 09:30:43.722: [PA] 10:f1:f2:83:74:76 DHCP ciaddr: 0.0.0.0, yiaddr: 172.18.1.176
*DHCP Socket Task: May 13 09:30:43.722: [PA] 10:f1:f2:83:74:76 DHCP siaddr: 0.0.0.0, giaddr: 0.0.0.0
*DHCP Socket Task: May 13 09:30:43.722: [PA] 10:f1:f2:83:74:76 DHCP server id: 172.18.0.3 rcvd server id: 172.18.0.3
*DHCP Socket Task: May 13 09:30:43.722: [PA] 10:f1:f2:83:74:76 DHCP successfully bridged packet to STA
*DHCP Socket Task: May 13 09:35:44.258: [PA] 10:f1:f2:83:74:76 DHCP received op BOOTREQUEST (1) (len 324,vlan 1, port 1, encap 0xec03, xid 0x9b56943d)
*DHCP Socket Task: May 13 09:35:44.258: [PA] 10:f1:f2:83:74:76 DHCP (encap type 0xec03) mstype 000:21:9b:8d:e1:e0
*DHCP Socket Task: May 13 09:35:44.258: [PA] 10:f1:f2:83:74:76 DHCP processing DHCP REQUEST (3)
*DHCP Socket Task: May 13 09:35:44.258: [PA] 10:f1:f2:83:74:76 DHCP op: BOOTREQUEST, htype: Ethernet, hlen: 6, hops: 0
*DHCP Socket Task: May 13 09:35:44.258: [PA] 10:f1:f2:83:74:76 DHCP xid: 0x3d94569b (1033131675), secs: 0, flags: 0
*DHCP Socket Task: May 13 09:35:44.258: [PA] 10:f1:f2:83:74:76 DHCP chaddr: 10:f1:f2:83:74:76
*DHCP Socket Task: May 13 09:35:44.258: [PA] 10:f1:f2:83:74:76 DHCP ciaddr: 172.18.1.176, yiaddr: 0.0.0.0
*DHCP Socket Task: May 13 09:35:44.258: [PA] 10:f1:f2:83:74:76 DHCP Opt82 bridge mode insertion enabled, inserts opt82 if opt82 is enabled vlan=19, datalen =18, optlen=79
*DHCP Socket Task: May 13 09:35:44.258: [PA] 10:f1:f2:83:74:76 DHCP successfully bridged packet to DS
*DHCP Socket Task: May 13 09:35:44.259: [PA] 10:f1:f2:83:74:76 DHCP received op BOOTREPLY (2) (len 312,vlan 19, port 1, encap 0xec00, xid 0x9b56943d)
*DHCP Socket Task: May 13 09:35:44.259: [PA] 10:f1:f2:83:74:76 DHCP processing DHCP ACK (5)
*DHCP Socket Task: May 13 09:35:44.259: [PA] 10:f1:f2:83:74:76 DHCP op: BOOTREPLY, htype: Ethernet, hlen: 6, hops: 0
*DHCP Socket Task: May 13 09:35:44.259: [PA] 10:f1:f2:83:74:76 DHCP xid: 0x3d94569b (1033131675), secs: 0, flags: 0
*DHCP Socket Task: May 13 09:35:44.259: [PA] 10:f1:f2:83:74:76 DHCP chaddr: 10:f1:f2:83:74:76
*DHCP Socket Task: May 13 09:35:44.259: [PA] 10:f1:f2:83:74:76 DHCP ciaddr: 0.0.0.0, yiaddr: 172.18.1.176
*DHCP Socket Task: May 13 09:35:44.259: [PA] 10:f1:f2:83:74:76 DHCP siaddr: 0.0.0.0, giaddr: 0.0.0.0
*DHCP Socket Task: May 13 09:35:44.259: [PA] 10:f1:f2:83:74:76 DHCP server id: 172.18.0.3 rcvd server id: 172.18.0.3
*DHCP Socket Task: May 13 09:35:44.259: [PA] 10:f1:f2:83:74:76 DHCP successfully bridged packet to STA
*DHCP Socket Task: May 13 09:40:44.780: [PA] 10:f1:f2:83:74:76 DHCP received op BOOTREQUEST (1) (len 324,vlan 1, port 1, encap 0xec03, xid 0x92ea174d)
*DHCP Socket Task: May 13 09:40:44.780: [PA] 10:f1:f2:83:74:76 DHCP processing DHCP REQUEST (3)
*DHCP Socket Task: May 13 09:40:44.780: [PA] 10:f1:f2:83:74:76 DHCP op: BOOTREQUEST, htype: Ethernet, hlen: 6, hops: 0
*DHCP Socket Task: May 13 09:40:44.780: [PA] 10:f1:f2:83:74:76 DHCP xid: 0x4d17ea92 (1293413010), secs: 0, flags: 0
*DHCP Socket Task: May 13 09:40:44.780: [PA] 10:f1:f2:83:74:76 DHCP chaddr: 10:f1:f2:83:74:76
*DHCP Socket Task: May 13 09:40:44.780: [PA] 10:f1:f2:83:74:76 DHCP ciaddr: 172.18.1.176, yiaddr: 0.0.0.0
*DHCP Socket Task: May 13 09:40:44.780: [PA] 10:f1:f2:83:74:76 DHCP siaddr: 0.0.0.0, giaddr: 0.0.0.0
*DHCP Socket Task: May 13 09:40:44.780: [PA] 10:f1:f2:83:74:76 DHCP Opt82 bridge mode insertion enabled, inserts opt82 if opt82 is enabled vlan=19, datalen =18, optlen=79
*DHCP Socket Task: May 13 09:40:44.780: [PA] 10:f1:f2:83:74:76 DHCP successfully bridged packet to DS
*DHCP Socket Task: May 13 09:40:44.781: [PA] 10:f1:f2:83:74:76 DHCP received op BOOTREPLY (2) (len 312,vlan 19, port 1, encap 0xec00, xid 0x92ea174d)
*DHCP Socket Task: May 13 09:40:44.781: [PA] 10:f1:f2:83:74:76 DHCP processing DHCP ACK (5)
*DHCP Socket Task: May 13 09:40:44.781: [PA] 10:f1:f2:83:74:76 DHCP op: BOOTREPLY, htype: Ethernet, hlen: 6, hops: 0
*DHCP Socket Task: May 13 09:40:44.781: [PA] 10:f1:f2:83:74:76 DHCP xid: 0x4d17ea92 (1293413010), secs: 0, flags: 0
*DHCP Socket Task: May 13 09:40:44.781: [PA] 10:f1:f2:83:74:76 DHCP chaddr: 10:f1:f2:83:74:76
*DHCP Socket Task: May 13 09:40:44.781: [PA] 10:f1:f2:83:74:76 DHCP ciaddr: 0.0.0.0, yiaddr: 172.18.1.176
*DHCP Socket Task: May 13 09:40:44.781: [PA] 10:f1:f2:83:74:76 DHCP siaddr: 0.0.0.0, giaddr: 0.0.0.0
*DHCP Socket Task: May 13 09:40:44.781: [PA] 10:f1:f2:83:74:76 DHCP server id: 172.18.0.3 rcvd server id: 172.18.0.3
*DHCP Socket Task: May 13 09:40:44.781: [PA] 10:f1:f2:83:74:76 DHCP successfully bridged packet to STA
*DHCP Socket Task: May 13 09:45:45.276: [PA] 10:f1:f2:83:74:76 DHCP received op BOOTREQUEST (1) (len 324,vlan 1, port 1, encap 0xec03, xid 0x107c2200)
*DHCP Socket Task: May 13 09:45:45.276: [PA] 10:f1:f2:83:74:76 DHCP (encap type 0xec03) mstype 000:21:9b:8d:e1:e0
*DHCP Socket Task: May 13 09:45:45.276: [PA] 10:f1:f2:83:74:76 DHCP op: BOOTREQUEST, htype: Ethernet, hlen: 6, hops: 0
*DHCP Socket Task: May 13 09:45:45.276: [PA] 10:f1:f2:83:74:76 DHCP xid: 0x227c10 (2259984), secs: 0, flags: 0
*DHCP Socket Task: May 13 09:45:45.276: [PA] 10:f1:f2:83:74:76 DHCP chaddr: 10:f1:f2:83:74:76
*DHCP Socket Task: May 13 09:45:45.276: [PA] 10:f1:f2:83:74:76 DHCP ciaddr: 172.18.1.176, yiaddr: 0.0.0.0
*DHCP Socket Task: May 13 09:45:45.276: [PA] 10:f1:f2:83:74:76 DHCP siaddr: 0.0.0.0, giaddr: 0.0.0.0
*DHCP Socket Task: May 13 09:45:45.276: [PA] 10:f1:f2:83:74:76 DHCP Opt82 bridge mode insertion enabled, inserts opt82 if opt82 is enabled vlan=19, datalen =18, optlen=79
*DHCP Socket Task: May 13 09:45:45.276: [PA] 10:f1:f2:83:74:76 DHCP successfully bridged packet to DS
*DHCP Socket Task: May 13 09:45:45.277: [PA] 10:f1:f2:83:74:76 DHCP received op BOOTREPLY (2) (len 312,vlan 19, port 1, encap 0xec00, xid 0x107c2200)
*DHCP Socket Task: May 13 09:45:45.277: [PA] 10:f1:f2:83:74:76 DHCP processing DHCP ACK (5)
*DHCP Socket Task: May 13 09:45:45.277: [PA] 10:f1:f2:83:74:76 DHCP op: BOOTREPLY, htype: Ethernet, hlen: 6, hops: 0
*DHCP Socket Task: May 13 09:45:45.277: [PA] 10:f1:f2:83:74:76 DHCP xid: 0x227c10 (2259984), secs: 0, flags: 0
*DHCP Socket Task: May 13 09:45:45.277: [PA] 10:f1:f2:83:74:76 DHCP chaddr: 10:f1:f2:83:74:76
*DHCP Socket Task: May 13 09:45:45.277: [PA] 10:f1:f2:83:74:76 DHCP ciaddr: 0.0.0.0, yiaddr: 172.18.1.176
*DHCP Socket Task: May 13 09:45:45.277: [PA] 10:f1:f2:83:74:76 DHCP siaddr: 0.0.0.0, giaddr: 0.0.0.0
*DHCP Socket Task: May 13 09:45:45.277: [PA] 10:f1:f2:83:74:76 DHCP server id: 172.18.0.3 rcvd server id: 172.18.0.3
*DHCP Socket Task: May 13 09:45:45.277: [PA] 10:f1:f2:83:74:76 DHCP successfully bridged packet to STA
*DHCP Socket Task: May 13 09:50:45.741: [PA] 10:f1:f2:83:74:76 DHCP received op BOOTREQUEST (1) (len 324,vlan 1, port 1, encap 0xec03, xid 0x82f0f32)
*DHCP Socket Task: May 13 09:50:45.741: [PA] 10:f1:f2:83:74:76 DHCP (encap type 0xec03) mstype 000:21:9b:8d:e1:e0
*DHCP Socket Task: May 13 09:50:45.741: [PA] 10:f1:f2:83:74:76 DHCP processing DHCP REQUEST (3)
*DHCP Socket Task: May 13 09:50:45.741: [PA] 10:f1:f2:83:74:76 DHCP op: BOOTREQUEST, htype: Ethernet, hlen: 6, hops: 0
*DHCP Socket Task: May 13 09:50:45.741: [PA] 10:f1:f2:83:74:76 DHCP xid: 0x320f2f08 (839855880), secs: 0, flags: 0
*DHCP Socket Task: May 13 09:50:45.741: [PA] 10:f1:f2:83:74:76 DHCP chaddr: 10:f1:f2:83:74:76
*DHCP Socket Task: May 13 09:50:45.741: [PA] 10:f1:f2:83:74:76 DHCP ciaddr: 172.18.1.176, yiaddr: 0.0.0.0
*DHCP Socket Task: May 13 09:50:45.741: [PA] 10:f1:f2:83:74:76 DHCP siaddr: 0.0.0.0, giaddr: 0.0.0.0
*DHCP Socket Task: May 13 09:50:45.741: [PA] 10:f1:f2:83:74:76 DHCP Opt82 bridge mode insertion enabled, inserts opt82 if opt82 is enabled vlan=19, datalen =18, optlen=79
*DHCP Socket Task: May 13 09:50:45.741: [PA] 10:f1:f2:83:74:76 DHCP successfully bridged packet to DS
*DHCP Socket Task: May 13 09:50:45.742: [PA] 10:f1:f2:83:74:76 DHCP received op BOOTREPLY (2) (len 312,vlan 19, port 1, encap 0xec00, xid 0x82f0f32)
*DHCP Socket Task: May 13 09:50:45.742: [PA] 10:f1:f2:83:74:76 DHCP processing DHCP ACK (5)
*DHCP Socket Task: May 13 09:50:45.742: [PA] 10:f1:f2:83:74:76 DHCP op: BOOTREPLY, htype: Ethernet, hlen: 6, hops: 0
*DHCP Socket Task: May 13 09:50:45.742: [PA] 10:f1:f2:83:74:76 DHCP xid: 0x320f2f08 (839855880), secs: 0, flags: 0
*DHCP Socket Task: May 13 09:50:45.742: [PA] 10:f1:f2:83:74:76 DHCP chaddr: 10:f1:f2:83:74:76
*DHCP Socket Task: May 13 09:50:45.742: [PA] 10:f1:f2:83:74:76 DHCP ciaddr: 0.0.0.0, yiaddr: 172.18.1.176
*DHCP Socket Task: May 13 09:50:45.742: [PA] 10:f1:f2:83:74:76 DHCP siaddr: 0.0.0.0, giaddr: 0.0.0.0
*DHCP Socket Task: May 13 09:55:46.239: [PA] 10:f1:f2:83:74:76 DHCP received op BOOTREQUEST (1) (len 324,vlan 1, port 1, encap 0xec03, xid 0xbb08b47b)
*DHCP Socket Task: May 13 09:55:46.239: [PA] 10:f1:f2:83:74:76 DHCP (encap type 0xec03) mstype 000:21:9b:8d:e1:e0
*DHCP Socket Task: May 13 09:55:46.239: [PA] 10:f1:f2:83:74:76 DHCP op: BOOTREQUEST, htype: Ethernet, hlen: 6, hops: 0
*DHCP Socket Task: May 13 09:55:46.239: [PA] 10:f1:f2:83:74:76 DHCP xid: 0x7bb408bb (2075396283), secs: 0, flags: 0
*DHCP Socket Task: May 13 09:55:46.239: [PA] 10:f1:f2:83:74:76 DHCP chaddr: 10:f1:f2:83:74:76
*DHCP Socket Task: May 13 09:55:46.239: [PA] 10:f1:f2:83:74:76 DHCP ciaddr: 172.18.1.176, yiaddr: 0.0.0.0
*DHCP Socket Task: May 13 09:55:46.239: [PA] 10:f1:f2:83:74:76 DHCP siaddr: 0.0.0.0, giaddr: 0.0.0.0
*DHCP Socket Task: May 13 09:55:46.239: [PA] 10:f1:f2:83:74:76 DHCP Opt82 bridge mode insertion enabled, inserts opt82 if opt82 is enabled vlan=19, datalen =18, optlen=79
*DHCP Socket Task: May 13 09:55:46.239: [PA] 10:f1:f2:83:74:76 DHCP successfully bridged packet to DS
*DHCP Socket Task: May 13 09:55:46.240: [PA] 10:f1:f2:83:74:76 DHCP received op BOOTREPLY (2) (len 312,vlan 19, port 1, encap 0xec00, xid 0xbb08b47b)
*DHCP Socket Task: May 13 09:55:46.240: [PA] 10:f1:f2:83:74:76 DHCP processing DHCP ACK (5)
*DHCP Socket Task: May 13 09:55:46.240: [PA] 10:f1:f2:83:74:76 DHCP op: BOOTREPLY, htype: Ethernet, hlen: 6, hops: 0
*DHCP Socket Task: May 13 09:55:46.240: [PA] 10:f1:f2:83:74:76 DHCP xid: 0x7bb408bb (2075396283), secs: 0, flags: 0
*DHCP Socket Task: May 13 09:55:46.240: [PA] 10:f1:f2:83:74:76 DHCP chaddr: 10:f1:f2:83:74:76
*DHCP Socket Task: May 13 09:55:46.240: [PA] 10:f1:f2:83:74:76 DHCP ciaddr: 0.0.0.0, yiaddr: 172.18.1.176
*DHCP Socket Task: May 13 09:55:46.240: [PA] 10:f1:f2:83:74:76 DHCP siaddr: 0.0.0.0, giaddr: 0.0.0.0
*DHCP Socket Task: May 13 09:55:46.240: [PA] 10:f1:f2:83:74:76 DHCP server id: 172.18.0.3 rcvd server id: 172.18.0.3
*DHCP Socket Task: May 13 09:55:46.240: [PA] 10:f1:f2:83:74:76 DHCP successfully bridged packet to STA
*DHCP Socket Task: May 13 10:00:46.730: [PA] 10:f1:f2:83:74:76 DHCP received op BOOTREQUEST (1) (len 324,vlan 1, port 1, encap 0xec03, xid 0xc7df2166)
*DHCP Socket Task: May 13 10:00:46.730: [PA] 10:f1:f2:83:74:76 DHCP (encap type 0xec03) mstype 000:21:9b:8d:e1:e0
*DHCP Socket Task: May 13 10:00:46.730: [PA] 10:f1:f2:83:74:76 DHCP processing DHCP REQUEST (3)
*DHCP Socket Task: May 13 10:00:46.730: [PA] 10:f1:f2:83:74:76 DHCP op: BOOTREQUEST, htype: Ethernet, hlen: 6, hops: 0
*DHCP Socket Task: May 13 10:00:46.730: [PA] 10:f1:f2:83:74:76 DHCP xid: 0x6621dfc7 (1713496007), secs: 0, flags: 0
*DHCP Socket Task: May 13 10:00:46.730: [PA] 10:f1:f2:83:74:76 DHCP chaddr: 10:f1:f2:83:74:76
*DHCP Socket Task: May 13 10:00:46.730: [PA] 10:f1:f2:83:74:76 DHCP ciaddr: 172.18.1.176, yiaddr: 0.0.0.0
*DHCP Socket Task: May 13 10:00:46.730: [PA] 10:f1:f2:83:74:76 DHCP siaddr: 0.0.0.0, giaddr: 0.0.0.0
*DHCP Socket Task: May 13 10:00:46.730: [PA] 10:f1:f2:83:74:76 DHCP Opt82 bridge mode insertion enabled, inserts opt82 if opt82 is enabled vlan=19, datalen =18, optlen=79
*DHCP Socket Task: May 13 10:00:46.730: [PA] 10:f1:f2:83:74:76 DHCP successfully bridged packet to DS
*DHCP Socket Task: May 13 10:00:46.731: [PA] 10:f1:f2:83:74:76 DHCP received op BOOTREPLY (2) (len 312,vlan 19, port 1, encap 0xec00, xid 0xc7df2166)
*DHCP Socket Task: May 13 10:00:46.731: [PA] 10:f1:f2:83:74:76 DHCP processing DHCP ACK (5)
*DHCP Socket Task: May 13 10:00:46.731: [PA] 10:f1:f2:83:74:76 DHCP op: BOOTREPLY, htype: Ethernet, hlen: 6, hops: 0
*DHCP Socket Task: May 13 10:00:46.731: [PA] 10:f1:f2:83:74:76 DHCP xid: 0x6621dfc7 (1713496007), secs: 0, flags: 0
*DHCP Socket Task: May 13 10:00:46.731: [PA] 10:f1:f2:83:74:76 DHCP ciaddr: 0.0.0.0, yiaddr: 172.18.1.176
*DHCP Socket Task: May 13 10:00:46.731: [PA] 10:f1:f2:83:74:76 DHCP siaddr: 0.0.0.0, giaddr: 0.0.0.0
*DHCP Socket Task: May 13 10:00:46.731: [PA] 10:f1:f2:83:74:76 DHCP server id: 172.18.0.3 rcvd server id: 172.18.0.3
*DHCP Socket Task: May 13 10:00:46.731: [PA] 10:f1:f2:83:74:76 DHCP successfully bridged packet to STA

luis_cordova · ‎05-13-2019

Hi @jjalonsom ,

I told you that there is an event related to WLC:

https://community.cisco.com/t5/wireless/pregunte-al-experto-mejores-pr%C3%A1cticas-y-tips-para-configurar/td-p/3847983

This is an event in Spanish, but, I know that the expert can help you in English if you need it.
I am sure that it will guide you with your doubt.

Regards

jjalonsom · ‎05-14-2019

thank you

patoberli · ‎05-15-2019

Honestly I believe the users aren't deleting the profile on the mobile phone and thus stay connected if they are close to the company.
I would create a captive portal for those users, which doesn't allow network access if they don't authenticate themselves every day. So on the second day, those clients connect to the old, not deleted, network and can't login anymore. That means those clients can't receive anymore any messages and use the internet and thus will probably delete the network :)

WLC with many of clients associated but most do not respond to the ping and people lose connectivity from devices...