Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Attention: The Cisco Support Community site will be in read only mode on Dec14, 2017 from 12:01am PST to 11:30am for standard maintenance. Sorry for the inconvenience.

New Member

WLC2504 disconnecting a client

Hello,

I am working on a Cisco Wireless network where a particular Axis network camera device is disconnected from an SSID after 6 to 10 minutes.  The last three tests showed the device disconnecting after 6, 8 and 10 minutes.

There are 2 other devices connected to the same SSID, also Axis network cameras.  They remain connected to the SSID for days on end.

Troubleshooting steps carried out so far:

Adjusted user idle timeout on SSID -

Client user idle timeout (15-100000) Seconds

Added two AP groups to only allow the CAM SSID to be present on one access point

Adjusted user idle timeout on controller -

User Idle Timeout (seconds)

I was hoping there was a controller or SSID timeout setting that could be used to workaround the problem but this does not appear to be the case.

Based on the fact this is only affecting one device, after 6-10 minutes, and there are other SSIDs and devices which do not disconnect I am not convinced this is either the controller or APs.

However to put this to bed once and for all I would be grateful of any input from this forum.

Network device disconnecting debug dialogue:

*spamApTask1: Jan 04 15:55:51.599: 00:40:8c:xx:xx:xx Received Idle-Timeout from AP a4:0c:c3:xx:xx:xx, slot 0 for STA 00:40:8c:xx:xx:xx

*spamApTask1: Jan 04 15:55:51.599: 00:40:8c:xx:xx:xx apfMsDeleteByMscb Scheduling mobile for deletion with deleteReason 4, reasonCode 4

*spamApTask1: Jan 04 15:55:51.599: 00:40:8c:xx:xx:xx Scheduling deletion of Mobile Station:  (callerId: 30) in 1 seconds

*osapiBsnTimer: Jan 04 15:55:52.412: 00:40:8c:xx:xx:xx apfMsExpireCallback (apf_ms.c:615) Expiring Mobile!

*apfReceiveTask: Jan 04 15:55:52.412: 00:40:8c:xx:xx:xx apfMsExpireMobileStation (apf_ms.c:5827) Changing state for mobile 00:40:8c:xx:xx:xx on AP a4:0c:c3:xx:xx:xx from Associated to Disassociated

*apfReceiveTask: Jan 04 15:55:52.412: 00:40:8c:xx:xx:xx Sent Deauthenticate to mobile on BSSID a4:0c:c3:xx:xx:xx slot 0(caller apf_ms.c:5921)

*apfReceiveTask: Jan 04 15:55:52.413: 00:40:8c:xx:xx:xx apfMsAssoStateDec

*apfReceiveTask: Jan 04 15:55:52.413: 00:40:8c:xx:xx:xx apfMsExpireMobileStation (apf_ms.c:5959) Changing state for mobile 00:40:8c:xx:xx:xx on AP a4:0c:c3:xx:xx:xx from Disassociated to Idle

*apfReceiveTask: Jan 04 15:55:52.413: 00:40:8c:xx:xx:xx pemApfDeleteMobileStation2: APF_MS_PEM_WAIT_L2_AUTH_COMPLETE = 0.

*apfReceiveTask: Jan 04 15:55:52.413: 00:40:8c:xx:xx:xx 172.16.xx.9 RUN (20) Deleted mobile LWAPP rule on AP [a4:0c:c3:xx:xx:xx]

*apfReceiveTask: Jan 04 15:55:52.413: 00:40:8c:xx:xx:xx apfMsRunStateDec

*apfReceiveTask: Jan 04 15:55:52.413: 00:40:8c:xx:xx:xx apfMs1xStateDec

*apfReceiveTask: Jan 04 15:55:52.413: 00:40:8c:xx:xx:xx Deleting mobile on AP a4:0c:c3:xx:xx:xx(0)

*pemReceiveTask: Jan 04 15:55:52.414: 00:40:8c:xx:xx:xx 172.16.xx.9 Removed NPU entry.

Details of the SSID:

WLAN Identifier.................................. 6

Profile Name..................................... CAM

Network Name (SSID).............................. CAM

Status........................................... Enabled

MAC Filtering.................................... Disabled

Broadcast SSID................................... Enabled

AAA Policy Override.............................. Disabled

Network Admission Control

  Client Profiling Status ....................... Disabled

   DHCP ......................................... Disabled

   HTTP ......................................... Disabled

  Radius-NAC State............................... Disabled

  SNMP-NAC State................................. Disabled

  Quarantine VLAN................................ 0

Maximum number of Associated Clients............. 0

Maximum number of Clients per AP Radio........... 200

Number of Active Clients......................... 2

Exclusionlist Timeout............................ 60 seconds

Session Timeout.................................. 86400 seconds

User Idle Timeout................................ 300 seconds

--More-- or (q)uit

User Idle Threshold.............................. 0 Bytes

NAS-identifier................................... wes-wlc2504-core1

CHD per WLAN..................................... Enabled

Webauth DHCP exclusion........................... Disabled

Interface........................................ cam

Multicast Interface.............................. Not Configured

WLAN IPv4 ACL.................................... unconfigured

WLAN IPv6 ACL.................................... unconfigured

mDNS Status...................................... Enabled

mDNS Profile Name................................ default-mdns-profile

DHCP Server...................................... Default

DHCP Address Assignment Required................. Disabled

Static IP client tunneling....................... Disabled

Quality of Service............................... Silver

Per-SSID Rate Limits............................. Upstream      Downstream

Average Data Rate................................   0             0

Average Realtime Data Rate.......................   0             0

Burst Data Rate..................................   0             0

Burst Realtime Data Rate.........................   0             0

Per-Client Rate Limits........................... Upstream      Downstream

Average Data Rate................................   0             0

Average Realtime Data Rate.......................   0             0

Burst Data Rate..................................   0             0

--More-- or (q)uit

Burst Realtime Data Rate.........................   0             0

Scan Defer Priority.............................. 4,5,6

Scan Defer Time.................................. 100 milliseconds

WMM.............................................. Allowed

WMM UAPSD Compliant Client Support............... Disabled

Media Stream Multicast-direct.................... Disabled

CCX - AironetIe Support.......................... Enabled

CCX - Gratuitous ProbeResponse (GPR)............. Disabled

CCX - Diagnostics Channel Capability............. Disabled

Dot11-Phone Mode (7920).......................... Disabled

Wired Protocol................................... None

Passive Client Feature........................... Disabled

Peer-to-Peer Blocking Action..................... Disabled

Radio Policy..................................... All

DTIM period for 802.11a radio.................... 1

DTIM period for 802.11b radio.................... 1

Radius Servers

   Authentication................................ Global Servers

   Accounting.................................... Global Servers

      Interim Update............................. Disabled

   Dynamic Interface............................. Disabled

   Dynamic Interface Priority.................... wlan

Local EAP Authentication......................... Disabled

--More-- or (q)uit

Security

   802.11 Authentication:........................ Open System

   FT Support.................................... Disabled

   Static WEP Keys............................... Disabled

   802.1X........................................ Disabled

   Wi-Fi Protected Access (WPA/WPA2)............. Enabled

      WPA (SSN IE)............................... Disabled

      WPA2 (RSN IE).............................. Enabled

         TKIP Cipher............................. Enabled

         AES Cipher.............................. Disabled

                                                                Auth Key Management

         802.1x.................................. Disabled

         PSK..................................... Enabled

         CCKM.................................... Disabled

         FT-1X(802.11r).......................... Disabled

         FT-PSK(802.11r)......................... Disabled

         PMF-1X(802.11w)......................... Disabled

         PMF-PSK(802.11w)........................ Disabled

      FT Reassociation Timeout................... 20

      FT Over-The-DS mode........................ Enabled

      GTK Randomization.......................... Disabled

      SKC Cache Support.......................... Disabled

--More-- or (q)uit

      CCKM TSF Tolerance......................... 1000

   WAPI.......................................... Disabled

   Wi-Fi Direct policy configured................ Disabled

   EAP-Passthrough............................... Disabled

   CKIP ......................................... Disabled

   Web Based Authentication...................... Disabled

   Web-Passthrough............................... Disabled

   Conditional Web Redirect...................... Disabled

   Splash-Page Web Redirect...................... Disabled

   Auto Anchor................................... Disabled

   FlexConnect Local Switching................... Disabled

   flexconnect Central Dhcp Flag................. Disabled

   flexconnect nat-pat Flag...................... Disabled

   flexconnect Dns Override Flag................. Disabled

   FlexConnect Vlan based Central Switching ..... Disabled

   FlexConnect Local Authentication.............. Disabled

   FlexConnect Learn IP Address.................. Enabled

   Client MFP.................................... Optional

   PMF........................................... Disabled

   PMF Association Comeback Time................. 1

   PMF SA Query RetryTimeout..................... 200

   Tkip MIC Countermeasure Hold-down Timer....... 60

AVC Visibilty.................................... Disabled

--More-- or (q)uit

AVC Profile Name................................. None

Flow Monitor Name................................ None

Call Snooping.................................... Disabled

Roamed Call Re-Anchor Policy..................... Disabled

SIP CAC Fail Send-486-Busy Policy................ Enabled

SIP CAC Fail Send Dis-Association Policy......... Disabled

KTS based CAC Policy............................. Disabled

Assisted Roaming Prediction Optimization......... Disabled

802.11k Neighbor List............................ Disabled

802.11k Neighbor List Dual Band.................. Disabled

Band Select...................................... Disabled

Load Balancing................................... Disabled

Multicast Buffer................................. Disabled

Mobility Anchor List

WLAN ID     IP Address            Status

-------     ---------------       ------

802.11u........................................ Disabled

MSAP Services.................................. Disabled

Controller:

Manufacturer's Name.............................. Cisco Systems Inc.

Product Name..................................... Cisco Controller

Product Version.................................. 7.4.110.0

Bootloader Version............................... 1.0.16

Field Recovery Image Version..................... 1.0.0

Firmware Version................................. PIC 16.0

Network device boot up debug dialogue:

(Cisco Controller) >*apfMsConnTask_4: Jan 04 16:17:53.890: 00:40:8c:xx:xx:xx Adding mobile on LWAPP AP a4:0c:c3:xx:xx:xx(0)

*apfMsConnTask_4: Jan 04 16:17:53.890: 00:40:8c:xx:xx:xx Association received from mobile on BSSID a4:0c:c3:yy:yy:yy

*apfMsConnTask_4: Jan 04 16:17:53.890: 00:40:8c:xx:xx:xx Global 200 Clients are allowed to AP radio

*apfMsConnTask_4: Jan 04 16:17:53.890: 00:40:8c:xx:xx:xx Max Client Trap Threshold: 0  cur: 2

*apfMsConnTask_4: Jan 04 16:17:53.890: 00:40:8c:xx:xx:xx Rf profile 600 Clients are allowed to AP wlan

*apfMsConnTask_4: Jan 04 16:17:53.890: 00:40:8c:xx:xx:xx Applying Interface policy on Mobile, role Unassociated. Ms NAC State 0 Quarantine Vlan 0 Access Vlan 0

*apfMsConnTask_4: Jan 04 16:17:53.890: 00:40:8c:xx:xx:xx Re-applying interface policy for client

*apfMsConnTask_4: Jan 04 16:17:53.890: 00:40:8c:xx:xx:xx 0.0.0.0 START (0) Changing IPv4 ACL 'none' (ACL ID 255) ===> 'none' (ACL ID 255) --- (caller apf_policy.c:2018)

*apfMsConnTask_4: Jan 04 16:17:53.890: 00:40:8c:xx:xx:xx 0.0.0.0 START (0) Changing IPv6 ACL 'none' (ACL ID 255) ===> 'none' (ACL ID 255) --- (caller apf_policy.c:2246)

*apfMsConnTask_4: Jan 04 16:17:53.890: 00:40:8c:xx:xx:xx In processSsidIE:4210 setting Central switched to TRUE

*apfMsConnTask_4: Jan 04 16:17:53.890: 00:40:8c:xx:xx:xx In processSsidIE:4213 apVapId = 1 and Split Acl Id = 65535

*apfMsConnTask_4: Jan 04 16:17:53.890: 00:40:8c:xx:xx:xx Applying site-specific Local Bridging override for station 00:40:8c:xx:xx:xx - vapId 6, site 'CCTV', interface 'cam'

*apfMsConnTask_4: Jan 04 16:17:53.890: 00:40:8c:xx:xx:xx Applying Local Bridging Interface Policy for station 00:40:8c:xx:xx:xx - vlan 88, interface id 16, interface 'cam'

*apfMsConnTask_4: Jan 04 16:17:53.890: 00:40:8c:xx:xx:xx Applying site-specific override for station 00:40:8c:xx:xx:xx - vapId 6, site 'CCTV', interface 'cam'

*apfMsConnTask_4: Jan 04 16:17:53.891: 00:40:8c:xx:xx:xx Applying Interface policy on Mobile, role Unassociated. Ms NAC State 2 Quarantine Vlan 0 Access Vlan 88

*apfMsConnTask_4: Jan 04 16:17:53.891: 00:40:8c:xx:xx:xx Re-applying interface policy for client

*apfMsConnTask_4: Jan 04 16:17:53.891: 00:40:8c:xx:xx:xx 0.0.0.0 START (0) Changing IPv4 ACL 'none' (ACL ID 255) ===> 'none' (ACL ID 255) --- (caller apf_policy.c:2018)

*apfMsConnTask_4: Jan 04 16:17:53.891: 00:40:8c:xx:xx:xx 0.0.0.0 START (0) Changing IPv6 ACL 'none' (ACL ID 255) ===> 'none' (ACL ID 255) --- (caller apf_policy.c:2246)

*apfMsConnTask_4: Jan 04 16:17:53.891: 00:40:8c:xx:xx:xx processSsidIE  statusCode is 0 and status is 0

*apfMsConnTask_4: Jan 04 16:17:53.891: 00:40:8c:xx:xx:xx processSsidIE  ssid_done_flag is 0 finish_flag is 0

*apfMsConnTask_4: Jan 04 16:17:53.891: 00:40:8c:xx:xx:xx STA - rates (8): 2 4 11 12 18 22 152 36 0 0 0 0 0 0 0 0

*apfMsConnTask_4: Jan 04 16:17:53.891: 00:40:8c:xx:xx:xx suppRates  statusCode is 0 and gotSuppRatesElement is 1

*apfMsConnTask_4: Jan 04 16:17:53.891: 00:40:8c:xx:xx:xx STA - rates (12): 2 4 11 12 18 22 152 36 48 72 96 108 0 0 0 0

*apfMsConnTask_4: Jan 04 16:17:53.891: 00:40:8c:xx:xx:xx extSuppRates  statusCode is 0 and gotExtSuppRatesElement is 1

*apfMsConnTask_4: Jan 04 16:17:53.891: 00:40:8c:xx:xx:xx Processing RSN IE type 48, length 20 for mobile 00:40:8c:xx:xx:xx

*apfMsConnTask_4: Jan 04 16:17:53.891: 00:40:8c:xx:xx:xx 0.0.0.0 START (0) Initializing policy

*apfMsConnTask_4: Jan 04 16:17:53.891: 00:40:8c:xx:xx:xx 0.0.0.0 START (0) Change state to AUTHCHECK (2) last state START (0)

*apfMsConnTask_4: Jan 04 16:17:53.891: 00:40:8c:xx:xx:xx 0.0.0.0 AUTHCHECK (2) Change state to 8021X_REQD (3) last state AUTHCHECK (2)

*apfMsConnTask_4: Jan 04 16:17:53.891: 00:40:8c:xx:xx:xx Not Using WMM Compliance code qosCap 00

*apfMsConnTask_4: Jan 04 16:17:53.891: 00:40:8c:xx:xx:xx 0.0.0.0 8021X_REQD (3) Plumbed mobile LWAPP rule on AP a4:0c:c3:xx:xx:xx vapId 6 apVapId 1 flex-acl-name:

*apfMsConnTask_4: Jan 04 16:17:53.891: 00:40:8c:xx:xx:xx apfMsAssoStateInc

*apfMsConnTask_4: Jan 04 16:17:53.891: 00:40:8c:xx:xx:xx apfPemAddUser2 (apf_policy.c:276) Changing state for mobile 00:40:8c:xx:xx:xx on AP a4:0c:c3:xx:xx:xx from Idle to Associated

*apfMsConnTask_4: Jan 04 16:17:53.891: 00:40:8c:xx:xx:xx apfPemAddUser2:session timeout forstation 00:40:8c:xx:xx:xx - Session Tout 0, apfMsTimeOut '0' and sessionTimerRunning flag is  0

*apfMsConnTask_4: Jan 04 16:17:53.891: 00:40:8c:xx:xx:xx Stopping deletion of Mobile Station: (callerId: 48)

*apfMsConnTask_4: Jan 04 16:17:53.891: 00:40:8c:xx:xx:xx Func: apfPemAddUser2, Ms Timeout = 0, Session Timeout = 0

*apfMsConnTask_4: Jan 04 16:17:53.892: 00:40:8c:xx:xx:xx Sending Assoc Response to station on BSSID a4:0c:c3:xx:xx:xx (status 0) ApVapId 1 Slot 0

*apfMsConnTask_4: Jan 04 16:17:53.892: 00:40:8c:xx:xx:xx apfProcessAssocReq (apf_80211.c:7399) Changing state for mobile 00:40:8c:xx:xx:xx on AP a4:0c:c3:xx:xx:xx from Associated to Associated

*dot1xMsgTask: Jan 04 16:17:53.895: 00:40:8c:xx:xx:xx Creating a PKC PMKID Cache entry for station 00:40:8c:xx:xx:xx (RSN 2)

*dot1xMsgTask: Jan 04 16:17:53.895: 00:40:8c:xx:xx:xx Resetting MSCB PMK Cache Entry 0 for station 00:40:8c:xx:xx:xx

*dot1xMsgTask: Jan 04 16:17:53.895: 00:40:8c:xx:xx:xx Setting active key cache index 8 ---> 8

*dot1xMsgTask: Jan 04 16:17:53.895: 00:40:8c:xx:xx:xx Setting active key cache index 8 ---> 0

*dot1xMsgTask: Jan 04 16:17:53.895: 00:40:8c:xx:xx:xx Adding BSSID a4:0c:c3:xx:xx:xx to PMKID cache at index 0 for station 00:40:8c:xx:xx:xx

*dot1xMsgTask: Jan 04 16:17:53.895: New PMKID: (16)

*dot1xMsgTask: Jan 04 16:17:53.895:      [0000] aa 28 26 73 f2 af e7 a5 41 88 77 db 2e 4a 1f ae

*dot1xMsgTask: Jan 04 16:17:53.896: 00:40:8c:xx:xx:xx Initiating RSN PSK to mobile 00:40:8c:xx:xx:xx

*dot1xMsgTask: Jan 04 16:17:53.896: 00:40:8c:xx:xx:xx dot1x - moving mobile 00:40:8c:xx:xx:xx into Force Auth state

*dot1xMsgTask: Jan 04 16:17:53.896: 00:40:8c:xx:xx:xx Found an cache entry for BSSID a4:0c:c3:xx:xx:xx in PMKID cache at index 0 of station 00:40:8c:xx:xx:xx

*dot1xMsgTask: Jan 04 16:17:53.896: 00:40:8c:xx:xx:xx Found an cache entry for BSSID a4:0c:c3:xx:xx:xx in PMKID cache at index 0 of station 00:40:8c:xx:xx:xx

*dot1xMsgTask: Jan 04 16:17:53.896: Including PMKID in M1  (16)

*dot1xMsgTask: Jan 04 16:17:53.896:      [0000] aa 28 26 73 f2 af e7 a5 41 88 77 db 2e 4a 1f ae

*dot1xMsgTask: Jan 04 16:17:53.896: 00:40:8c:xx:xx:xx Starting key exchange to mobile 00:40:8c:xx:xx:xx, data packets will be dropped

*dot1xMsgTask: Jan 04 16:17:53.896: 00:40:8c:xx:xx:xx Sending EAPOL-Key Message to mobile 00:40:8c:xx:xx:xx

                                                                                                              state INITPMK (message 1), replay counter 00.00.00.00.00.00.00.00

*Dot1x_NW_MsgTask_2: Jan 04 16:17:53.921: 00:40:8c:xx:xx:xx Received EAPOL-Key from mobile 00:40:8c:xx:xx:xx

*Dot1x_NW_MsgTask_2: Jan 04 16:17:53.921: 00:40:8c:xx:xx:xx Ignoring invalid EAPOL version (1) in EAPOL-key message from mobile 00:40:8c:xx:xx:xx

*Dot1x_NW_MsgTask_2: Jan 04 16:17:53.921: 00:40:8c:xx:xx:xx Received EAPOL-key in PTK_START state (message 2) from mobile 00:40:8c:xx:xx:xx

*Dot1x_NW_MsgTask_2: Jan 04 16:17:53.921: 00:40:8c:xx:xx:xx Stopping retransmission timer for mobile 00:40:8c:xx:xx:xx

*Dot1x_NW_MsgTask_2: Jan 04 16:17:53.921: 00:40:8c:xx:xx:xx Sending EAPOL-Key Message to mobile 00:40:8c:xx:xx:xx

                                                                                                                    state PTKINITNEGOTIATING (message 3), replay counter 00.00.00.00.00.00.00.01

*Dot1x_NW_MsgTask_2: Jan 04 16:17:53.938: 00:40:8c:xx:xx:xx Received EAPOL-Key from mobile 00:40:8c:xx:xx:xx

*Dot1x_NW_MsgTask_2: Jan 04 16:17:53.938: 00:40:8c:xx:xx:xx Ignoring invalid EAPOL version (1) in EAPOL-key message from mobile 00:40:8c:xx:xx:xx

*Dot1x_NW_MsgTask_2: Jan 04 16:17:53.938: 00:40:8c:xx:xx:xx Received EAPOL-key in PTKINITNEGOTIATING state (message 4) from mobile 00:40:8c:xx:xx:xx

*Dot1x_NW_MsgTask_2: Jan 04 16:17:53.938: 00:40:8c:xx:xx:xx Stopping retransmission timer for mobile 00:40:8c:xx:xx:xx

*Dot1x_NW_MsgTask_2: Jan 04 16:17:53.938: 00:40:8c:xx:xx:xx apfMs1xStateInc

*Dot1x_NW_MsgTask_2: Jan 04 16:17:53.938: 00:40:8c:xx:xx:xx 0.0.0.0 8021X_REQD (3) Change state to L2AUTHCOMPLETE (4) last state 8021X_REQD (3)

*Dot1x_NW_MsgTask_2: Jan 04 16:17:53.938: 00:40:8c:xx:xx:xx Not Using WMM Compliance code qosCap 00

*Dot1x_NW_MsgTask_2: Jan 04 16:17:53.938: 00:40:8c:xx:xx:xx 0.0.0.0 L2AUTHCOMPLETE (4) Plumbed mobile LWAPP rule on AP a4:0c:c3:xx:xx:xx vapId 6 apVapId 1 flex-acl-name:

*Dot1x_NW_MsgTask_2: Jan 04 16:17:53.938: 00:40:8c:xx:xx:xx 0.0.0.0 L2AUTHCOMPLETE (4) Change state to DHCP_REQD (7) last state L2AUTHCOMPLETE (4)

*Dot1x_NW_MsgTask_2: Jan 04 16:17:53.938: 00:40:8c:xx:xx:xx 0.0.0.0 DHCP_REQD (7) pemAdvanceState2 5952, Adding TMP rule

*Dot1x_NW_MsgTask_2: Jan 04 16:17:53.938: 00:40:8c:xx:xx:xx 0.0.0.0 DHCP_REQD (7) Adding Fast Path rule

  type = Airespace AP - Learn IP address

  on AP a4:0c:c3:xx:xx:xx, slot 0, interface = 1, QOS = 0

  IPv4 ACL ID = 255, IPv

*Dot1x_NW_MsgTask_2: Jan 04 16:17:53.938: 00:40:8c:xx:xx:xx 0.0.0.0 DHCP_REQD (7) Fast Path rule (contd...) 802.1P = 0, DSCP = 0, TokenID = 15206  Local Bridging Vlan = 88, Local Bridging intf id = 16

*Dot1x_NW_MsgTask_2: Jan 04 16:17:53.938: 00:40:8c:xx:xx:xx 0.0.0.0 DHCP_REQD (7) Successfully plumbed mobile rule (IPv4 ACL ID 255, IPv6 ACL ID 255)

*apfReceiveTask: Jan 04 16:17:53.939: 00:40:8c:xx:xx:xx 0.0.0.0 DHCP_REQD (7) State Update from Mobility-Incomplete to Mobility-Complete, mobility role=Local, client state=APF_MS_STATE_ASSOCIATED

*apfReceiveTask: Jan 04 16:17:53.939: 00:40:8c:xx:xx:xx 0.0.0.0 DHCP_REQD (7) pemAdvanceState2 5576, Adding TMP rule

*apfReceiveTask: Jan 04 16:17:53.939: 00:40:8c:xx:xx:xx 0.0.0.0 DHCP_REQD (7) Replacing Fast Path rule

  type = Airespace AP - Learn IP address

  on AP a4:0c:c3:xx:xx:xx, slot 0, interface = 1, QOS = 0

  IPv4 ACL ID = 255,

*apfReceiveTask: Jan 04 16:17:53.940: 00:40:8c:xx:xx:xx 0.0.0.0 DHCP_REQD (7) Fast Path rule (contd...) 802.1P = 0, DSCP = 0, TokenID = 15206  Local Bridging Vlan = 88, Local Bridging intf id = 16

*apfReceiveTask: Jan 04 16:17:53.940: 00:40:8c:xx:xx:xx 0.0.0.0 DHCP_REQD (7) Successfully plumbed mobile rule (IPv4 ACL ID 255, IPv6 ACL ID 255)

*pemReceiveTask: Jan 04 16:17:53.940: 00:40:8c:xx:xx:xx 0.0.0.0 Added NPU entry of type 9, dtlFlags 0x0

*pemReceiveTask: Jan 04 16:17:53.940: 00:40:8c:xx:xx:xx Sent an XID frame

*pemReceiveTask: Jan 04 16:17:53.940: 00:40:8c:xx:xx:xx 0.0.0.0 Added NPU entry of type 9, dtlFlags 0x0

*pemReceiveTask: Jan 04 16:17:53.940: 00:40:8c:xx:xx:xx Sent an XID frame

*IPv6_Msg_Task: Jan 04 16:17:55.100: 00:40:8c:xx:xx:xx Pushing IPv6: fe80:0000:0000:0000: 0240:8cff:fef2:d2ea , and MAC: 00:40:8c:xx:xx:xx , Binding to Data Plane. SUCCESS !!

*IPv6_Msg_Task: Jan 04 16:17:55.100: 00:40:8c:xx:xx:xx Calling pemAdvanceState from ipv6 addr learn, with pem session state 7

*IPv6_Msg_Task: Jan 04 16:17:55.100: 00:40:8c:xx:xx:xx apfMsRunStateInc

*IPv6_Msg_Task: Jan 04 16:17:55.100: 00:40:8c:xx:xx:xx 0.0.0.0 DHCP_REQD (7) Change state to RUN (20) last state DHCP_REQD (7)

*IPv6_Msg_Task: Jan 04 16:17:55.100: 00:40:8c:xx:xx:xx 0.0.0.0 RUN (20) Reached PLUMBFASTPATH: from line 6556

*IPv6_Msg_Task: Jan 04 16:17:55.100: 00:40:8c:xx:xx:xx 0.0.0.0 RUN (20) Replacing Fast Path rule

  type = Airespace AP Client

  on AP a4:0c:c3:xx:xx:xx, slot 0, interface = 1, QOS = 0

  IPv4 ACL ID = 255, IPv6 ACL ID = 255

*IPv6_Msg_Task: Jan 04 16:17:55.100: 00:40:8c:xx:xx:xx 0.0.0.0 RUN (20) Fast Path rule (contd...) 802.1P = 0, DSCP = 0, TokenID = 15206  Local Bridging Vlan = 88, Local Bridging intf id = 16

*IPv6_Msg_Task: Jan 04 16:17:55.100: 00:40:8c:xx:xx:xx 0.0.0.0 RUN (20) Successfully plumbed mobile rule (IPv4 ACL ID 255, IPv6 ACL ID 255)

*pemReceiveTask: Jan 04 16:17:55.102: 00:40:8c:xx:xx:xx 0.0.0.0 Added NPU entry of type 1, dtlFlags 0x0

*pemReceiveTask: Jan 04 16:17:55.102: 00:40:8c:xx:xx:xx Pushing IPv6: fe80:0000:0000:0000: 0240:8cff:fef2:d2ea , and MAC: 00:40:8c:xx:xx:xx , Binding to Data Plane. SUCCESS !!

*pemReceiveTask: Jan 04 16:17:55.102: 00:40:8c:xx:xx:xx 0.0.0.0, VLAN Id 88 Not sending gratuitous ARP

*DHCP Socket Task: Jan 04 16:18:03.382: 00:40:8c:xx:xx:xx DHCP received op BOOTREQUEST (1) (len 556,vlan 5, port 1, encap 0xec03)

*DHCP Socket Task: Jan 04 16:18:03.382: 00:40:8c:xx:xx:xx DHCP processing DHCP DISCOVER (1)

*DHCP Socket Task: Jan 04 16:18:03.382: 00:40:8c:xx:xx:xx DHCP   op: BOOTREQUEST, htype: Ethernet, hlen: 6, hops: 0

*DHCP Socket Task: Jan 04 16:18:03.382: 00:40:8c:xx:xx:xx DHCP   xid: 0x9f211f21 (2669748001), secs: 0, flags: 0

*DHCP Socket Task: Jan 04 16:18:03.382: 00:40:8c:xx:xx:xx DHCP   chaddr: 00:40:8c:xx:xx:xx

*DHCP Socket Task: Jan 04 16:18:03.382: 00:40:8c:xx:xx:xx DHCP   ciaddr: 0.0.0.0,  yiaddr: 0.0.0.0

*DHCP Socket Task: Jan 04 16:18:03.382: 00:40:8c:xx:xx:xx DHCP   siaddr: 0.0.0.0,  giaddr: 0.0.0.0

*DHCP Socket Task: Jan 04 16:18:03.382: 00:40:8c:xx:xx:xx DHCP successfully bridged packet to DS

*DHCP Socket Task: Jan 04 16:18:03.386: 00:40:8c:xx:xx:xx DHCP received op BOOTREPLY (2) (len 322,vlan 88, port 1, encap 0xec00)

*DHCP Socket Task: Jan 04 16:18:03.386: 00:40:8c:xx:xx:xx DHCP processing DHCP OFFER (2)

*DHCP Socket Task: Jan 04 16:18:03.386: 00:40:8c:xx:xx:xx DHCP   op: BOOTREPLY, htype: Ethernet, hlen: 6, hops: 0

*DHCP Socket Task: Jan 04 16:18:03.386: 00:40:8c:xx:xx:xx DHCP   xid: 0x9f211f21 (2669748001), secs: 0, flags: 0

*DHCP Socket Task: Jan 04 16:18:03.386: 00:40:8c:xx:xx:xx DHCP   chaddr: 00:40:8c:xx:xx:xx

*DHCP Socket Task: Jan 04 16:18:03.386: 00:40:8c:xx:xx:xx DHCP   ciaddr: 0.0.0.0,  yiaddr: 172.16.xx.9

*DHCP Socket Task: Jan 04 16:18:03.386: 00:40:8c:xx:xx:xx DHCP   siaddr: 172.16.yy.9,  giaddr: 172.16.xx.254

*DHCP Socket Task: Jan 04 16:18:03.386: 00:40:8c:xx:xx:xx DHCP   server id: 172.16.yy.9  rcvd server id: 172.16.yy.9

*DHCP Socket Task: Jan 04 16:18:03.386: 00:40:8c:xx:xx:xx DHCP successfully bridged packet to STA

*dtlArpTask: Jan 04 16:18:04.463: 00:40:8c:xx:xx:xx 172.16.xx.9 RUN (20) DHCP Address Re-established

*dtlArpTask: Jan 04 16:18:04.463: 00:40:8c:xx:xx:xx 172.16.xx.9 RUN (20) Reached PLUMBFASTPATH: from line 6873

*dtlArpTask: Jan 04 16:18:04.463: 00:40:8c:xx:xx:xx 172.16.xx.9 RUN (20) Replacing Fast Path rule

  type = Airespace AP Client

  on AP a4:0c:c3:xx:xx:xx, slot 0, interface = 1, QOS = 0

  IPv4 ACL ID = 255, IPv6 ACL ID =

*dtlArpTask: Jan 04 16:18:04.463: 00:40:8c:xx:xx:xx 172.16.xx.9 RUN (20) Fast Path rule (contd...) 802.1P = 0, DSCP = 0, TokenID = 15206  Local Bridging Vlan = 88, Local Bridging intf id = 16

*dtlArpTask: Jan 04 16:18:04.463: 00:40:8c:xx:xx:xx 172.16.xx.9 RUN (20) Successfully plumbed mobile rule (IPv4 ACL ID 255, IPv6 ACL ID 255)

*dtlArpTask: Jan 04 16:18:04.463: 00:40:8c:xx:xx:xx Assigning Address 172.16.xx.9 to mobile

*pemReceiveTask: Jan 04 16:18:04.464: 00:40:8c:xx:xx:xx 172.16.xx.9 Added NPU entry of type 1, dtlFlags 0x0

*pemReceiveTask: Jan 04 16:18:04.464: 00:40:8c:xx:xx:xx Pushing IPv6: fe80:0000:0000:0000: 0240:8cff:fef2:d2ea , and MAC: 00:40:8c:xx:xx:xx , Binding to Data Plane. SUCCESS !!

*DHCP Socket Task: Jan 04 16:18:05.764: 00:40:8c:xx:xx:xx DHCP received op BOOTREQUEST (1) (len 556,vlan 5, port 1, encap 0xec03)

*DHCP Socket Task: Jan 04 16:18:05.764: 00:40:8c:xx:xx:xx DHCP processing DHCP DISCOVER (1)

*DHCP Socket Task: Jan 04 16:18:05.764: 00:40:8c:xx:xx:xx DHCP   op: BOOTREQUEST, htype: Ethernet, hlen: 6, hops: 0

*DHCP Socket Task: Jan 04 16:18:05.764: 00:40:8c:xx:xx:xx DHCP   xid: 0xca23fb44 (3391355716), secs: 0, flags: 0

*DHCP Socket Task: Jan 04 16:18:05.764: 00:40:8c:xx:xx:xx DHCP   chaddr: 00:40:8c:xx:xx:xx

*DHCP Socket Task: Jan 04 16:18:05.764: 00:40:8c:xx:xx:xx DHCP   ciaddr: 0.0.0.0,  yiaddr: 0.0.0.0

*DHCP Socket Task: Jan 04 16:18:05.764: 00:40:8c:xx:xx:xx DHCP   siaddr: 0.0.0.0,  giaddr: 0.0.0.0

*DHCP Socket Task: Jan 04 16:18:05.764: 00:40:8c:xx:xx:xx DHCP successfully bridged packet to DS

*DHCP Socket Task: Jan 04 16:18:05.772: 00:40:8c:xx:xx:xx DHCP received op BOOTREPLY (2) (len 322,vlan 88, port 1, encap 0xec00)

*DHCP Socket Task: Jan 04 16:18:05.772: 00:40:8c:xx:xx:xx DHCP processing DHCP OFFER (2)

*DHCP Socket Task: Jan 04 16:18:05.772: 00:40:8c:xx:xx:xx DHCP   op: BOOTREPLY, htype: Ethernet, hlen: 6, hops: 0

*DHCP Socket Task: Jan 04 16:18:05.772: 00:40:8c:xx:xx:xx DHCP   xid: 0xca23fb44 (3391355716), secs: 0, flags: 0

*DHCP Socket Task: Jan 04 16:18:05.772: 00:40:8c:xx:xx:xx DHCP   chaddr: 00:40:8c:xx:xx:xx

*DHCP Socket Task: Jan 04 16:18:05.772: 00:40:8c:xx:xx:xx DHCP   ciaddr: 0.0.0.0,  yiaddr: 172.16.xx.9

*DHCP Socket Task: Jan 04 16:18:05.772: 00:40:8c:xx:xx:xx DHCP   siaddr: 172.16.yy.9,  giaddr: 172.16.xx.254

*DHCP Socket Task: Jan 04 16:18:05.772: 00:40:8c:xx:xx:xx DHCP   server id: 172.16.yy.9  rcvd server id: 172.16.yy.9

*DHCP Socket Task: Jan 04 16:18:05.772: 00:40:8c:xx:xx:xx DHCP successfully bridged packet to STA

*DHCP Socket Task: Jan 04 16:18:05.867: 00:40:8c:xx:xx:xx DHCP received op BOOTREQUEST (1) (len 556,vlan 5, port 1, encap 0xec03)

*DHCP Socket Task: Jan 04 16:18:05.867: 00:40:8c:xx:xx:xx DHCP processing DHCP REQUEST (3)

*DHCP Socket Task: Jan 04 16:18:05.867: 00:40:8c:xx:xx:xx DHCP   op: BOOTREQUEST, htype: Ethernet, hlen: 6, hops: 0

*DHCP Socket Task: Jan 04 16:18:05.867: 00:40:8c:xx:xx:xx DHCP   xid: 0xca23fb44 (3391355716), secs: 0, flags: 0

*DHCP Socket Task: Jan 04 16:18:05.867: 00:40:8c:xx:xx:xx DHCP   chaddr: 00:40:8c:xx:xx:xx

*DHCP Socket Task: Jan 04 16:18:05.867: 00:40:8c:xx:xx:xx DHCP   ciaddr: 0.0.0.0,  yiaddr: 0.0.0.0

*DHCP Socket Task: Jan 04 16:18:05.867: 00:40:8c:xx:xx:xx DHCP   siaddr: 0.0.0.0,  giaddr: 0.0.0.0

*DHCP Socket Task: Jan 04 16:18:05.867: 00:40:8c:xx:xx:xx DHCP   requested ip: 172.16.xx.9

*DHCP Socket Task: Jan 04 16:18:05.867: 00:40:8c:xx:xx:xx DHCP   server id: 172.16.yy.9  rcvd server id: 172.16.yy.9

*DHCP Socket Task: Jan 04 16:18:05.867: 00:40:8c:xx:xx:xx DHCP successfully bridged packet to DS

*DHCP Socket Task: Jan 04 16:18:05.874: 00:40:8c:xx:xx:xx DHCP received op BOOTREPLY (2) (len 322,vlan 88, port 1, encap 0xec00)

*DHCP Socket Task: Jan 04 16:18:05.874: 00:40:8c:xx:xx:xx DHCP processing DHCP ACK (5)

*DHCP Socket Task: Jan 04 16:18:05.874: 00:40:8c:xx:xx:xx DHCP   op: BOOTREPLY, htype: Ethernet, hlen: 6, hops: 0

*DHCP Socket Task: Jan 04 16:18:05.874: 00:40:8c:xx:xx:xx DHCP   xid: 0xca23fb44 (3391355716), secs: 0, flags: 0

*DHCP Socket Task: Jan 04 16:18:05.874: 00:40:8c:xx:xx:xx DHCP   chaddr: 00:40:8c:xx:xx:xx

*DHCP Socket Task: Jan 04 16:18:05.874: 00:40:8c:xx:xx:xx DHCP   ciaddr: 0.0.0.0,  yiaddr: 172.16.xx.9

*DHCP Socket Task: Jan 04 16:18:05.874: 00:40:8c:xx:xx:xx DHCP   siaddr: 0.0.0.0,  giaddr: 172.16.xx.254

*DHCP Socket Task: Jan 04 16:18:05.874: 00:40:8c:xx:xx:xx DHCP   server id: 172.16.yy.9  rcvd server id: 172.16.yy.9

Everyone's tags (5)
9 REPLIES
Hall of Fame Super Silver

Re: WLC2504 disconnecting a client

You need to use WPA2 with AES not TKIP. Also the session timer has to be higher than the user idle timer just to note. So I would either try to increase the idle timer to 7200 and see if that helps or maybe even enable passive client.

Sent from Cisco Technical Support iPhone App

-Scott
*** Please rate helpful posts ***
Hall of Fame Super Silver

Re: WLC2504 disconnecting a client

Just to add, I would just change the encryption to WPA2/AES and leave the rest at default and see if that helps. The standard for WPA2 is AES not TKIP, WPA uses TKIP.

Sent from Cisco Technical Support iPhone App

-Scott
*** Please rate helpful posts ***
New Member

WLC2504 disconnecting a client

Thank you Scott,

I have changed the encryption.  The device still disconnected but this time the debug did not log anything. I power cycled the device and the debug picked up the association.  I will continue to monitor connectivity.

Security

   802.11 Authentication:........................ Open System

   FT Support.................................... Disabled

   Static WEP Keys............................... Disabled

   802.1X........................................ Disabled

   Wi-Fi Protected Access (WPA/WPA2)............. Enabled

      WPA (SSN IE)............................... Disabled

      WPA2 (RSN IE).............................. Enabled

         TKIP Cipher............................. Disabled

         AES Cipher.............................. Enabled

                                                               Auth Key Management

         802.1x.................................. Disabled

         PSK..................................... Enabled

         CCKM.................................... Disabled

         FT-1X(802.11r).......................... Disabled

         FT-PSK(802.11r)......................... Disabled

         PMF-1X(802.11w)......................... Disabled

         PMF-PSK(802.11w)........................ Disabled

      FT Reassociation Timeout................... 20

      FT Over-The-DS mode........................ Enabled

      GTK Randomization.......................... Disabled

      SKC Cache Support.......................... Disabled

Hall of Fame Super Silver

Re: WLC2504 disconnecting a client

Okay... The logs you were seeing was most likely because you had WPA2/TKIP and the device was re-associating using the standards for WPA2 which is AES.

What you need to look at is what state the client is in when it looses connection. The client should still be in the RUN state. Also take a look at the arp table in the router to see of the device entry is still there.

You can try to enable passive mode and see if that helps.

Sent from Cisco Technical Support iPhone App

-Scott
*** Please rate helpful posts ***
New Member

Re: WLC2504 disconnecting a client

Understood Scott,

As soon as the client is no longer connected to the network "show client summary" shows the client as disassociated.

"show arp switch" on the WLC does not show an entry for the client.

"show client detail MAC address" reports MAC not found.

During testing, with all WLC parameters unchanged, the client did remain associated for 70 minutes before disassociating.

I will investigate testing passive mode.

New Member

Re: WLC2504 disconnecting a client

Another test - the only variable being the reboot of the client device.

Approximately 10 minutes after the client is rebooted the WLC client debug was empty but there is loss of IP connectivity.  Hhowever, as you mentioned the client is still showing "Policy Manager state" as RUN.

(Cisco Controller) >show client detail 00:40:8C:xx:xx:xx

Client MAC Address............................... 00:40:8C:xx:xx:xx

Client Username ................................. N/A

AP MAC Address................................... a4:0c:c3:yy:yy:yy

AP Name.......................................... wes-ap-2

Client State..................................... Associated

Client NAC OOB State............................. Access

Wireless LAN Id.................................. 6

Hotspot (802.11u)................................ Not Supported

BSSID............................................ a4:0c:c3:yy:yy:yy

Connected For ................................... 1721 secs

Channel.......................................... 11

IP Address....................................... 172.16.xx.9

Gateway Address.................................. Unknown

Netmask.......................................... Unknown

IPv6 Address..................................... fe80::240:8cff:fef2:d2ea

Association Id................................... 7

Authentication Algorithm......................... Open System

Reason Code...................................... 1

Status Code...................................... 0

Session Timeout.................................. 0

Client CCX version............................... 4

Client E2E version............................... No E2E support

--More-- or (q)uit

QoS Level........................................ Silver

802.1P Priority Tag.............................. disabled

CTS Security Group Tag........................... Not Applicable

KTS CAC Capability............................... No

WMM Support...................................... Enabled

  APSD ACs.......................................  BK  BE  VI  VO

Power Save....................................... OFF

Current Rate..................................... m7

Supported Rates.................................. 1.0,2.0,5.5,11.0,6.0,9.0,

    ............................................. 12.0,18.0,24.0,36.0,48.0,

    ............................................. 54.0

Mobility State................................... Local

Mobility Move Count.............................. 0

Security Policy Completed........................ Yes

Policy Manager State............................. RUN

Policy Manager Rule Created...................... Yes

Audit Session ID................................. none

IPv4 ACL Name.................................... none

IPv4 ACL Applied Status.......................... Unavailable

IPv6 ACL Name.................................... none

IPv6 ACL Applied Status.......................... Unavailable

mDNS Status...................................... Enabled

mDNS Profile Name................................ default-mdns-profile

--More-- or (q)uit

No. of mDNS Services Advertised.................. 0

Policy Type...................................... WPA2

Authentication Key Management.................... PSK

Encryption Cipher................................ CCMP (AES)

Protected Management Frame ...................... No

Management Frame Protection...................... No

EAP Type......................................... Unknown

Interface........................................ cam

VLAN............................................. 88

Quarantine VLAN.................................. 0

Access VLAN...................................... 88

Client Capabilities:

      CF Pollable................................ Not implemented

      CF Poll Request............................ Not implemented

      Short Preamble............................. Implemented

      PBCC....................................... Not implemented

      Channel Agility............................ Not implemented

      Listen Interval............................ 3

      Fast BSS Transition........................ Not implemented

Client Wifi Direct Capabilities:

      WFD capable................................ No

      Manged WFD capable......................... No

      Cross Connection Capable................... No

--More-- or (q)uit

      Support Concurrent Operation............... No

Fast BSS Transition Details:

Client Statistics:

      Number of Bytes Received................... 253107304

      Number of Bytes Sent....................... 5365674

      Number of Packets Received................. 186204

      Number of Packets Sent..................... 91711

      Number of Interim-Update Sent.............. 0

      Number of EAP Id Request Msg Timeouts...... 0

      Number of EAP Id Request Msg Failures...... 0

      Number of EAP Request Msg Timeouts......... 0

      Number of EAP Request Msg Failures......... 0

      Number of EAP Key Msg Timeouts............. 0

      Number of EAP Key Msg Failures............. 0

      Number of Data Retries..................... 11217

      Number of RTS Retries...................... 0

      Number of Duplicate Received Packets....... 2665

      Number of Decrypt Failed Packets........... 0

      Number of Mic Failured Packets............. 0

      Number of Mic Missing Packets.............. 0

      Number of RA Packets Dropped............... 0

      Number of Policy Errors.................... 0

      Radio Signal Strength Indicator............ -54 dBm

--More-- or (q)uit

      Signal to Noise Ratio...................... 38 dB

Client Rate Limiting Statistics:

      Number of Data Packets Recieved............ 0

      Number of Data Rx Packets Dropped.......... 0

      Number of Data Bytes Recieved.............. 0

      Number of Data Rx Bytes Dropped............ 0

      Number of Realtime Packets Recieved........ 0

      Number of Realtime Rx Packets Dropped...... 0

      Number of Realtime Bytes Recieved.......... 0

      Number of Realtime Rx Bytes Dropped........ 0

      Number of Data Packets Sent................ 0

      Number of Data Tx Packets Dropped.......... 0

      Number of Data Bytes Sent.................. 0

      Number of Data Tx Bytes Dropped............ 0

      Number of Realtime Packets Sent............ 0

      Number of Realtime Tx Packets Dropped...... 0

      Number of Realtime Bytes Sent.............. 0

      Number of Realtime Tx Bytes Dropped........ 0

Nearby AP Statistics:

      wes-ap-2(slot 0)

        antenna0: 91 secs ago.................... -50 dBm

        antenna1: 91 secs ago.................... -62 dBm

DNS Server details:

--More-- or (q)uit

      DNS server IP ............................. 0.0.0.0

      DNS server IP ............................. 0.0.0.0

Assisted Roaming Prediction List details:

Client Dhcp Required:     False

Approximately 5 minutes after the loss of IP connectivity the debug then logs an idle-timeout, at which point "show client detail" reports invalid client MAC address provided.

(Cisco Controller) >*spamApTask1: Jan 05 17:15:28.780: 00:40:8c:xx:xx:xx Received Idle-Timeout from AP a4:0c:c3:yy:yy:yy, slot 0 for STA 00:40:8c:xx:xx:xx

*spamApTask1: Jan 05 17:15:28.781: 00:40:8c:xx:xx:xx apfMsDeleteByMscb Scheduling mobile for deletion with deleteReason 4, reasonCode 4

*spamApTask1: Jan 05 17:15:28.781: 00:40:8c:xx:xx:xx Scheduling deletion of Mobile Station:  (callerId: 30) in 1 seconds

*osapiBsnTimer: Jan 05 17:15:29.712: 00:40:8c:xx:xx:xx apfMsExpireCallback (apf_ms.c:615) Expiring Mobile!

*apfReceiveTask: Jan 05 17:15:29.713: 00:40:8c:xx:xx:xx apfMsExpireMobileStation (apf_ms.c:5827) Changing state for mobile 00:40:8c:xx:xx:xx on AP a4:0c:c3:yy:yy:yy from Associated to Disassociated

*apfReceiveTask: Jan 05 17:15:29.713: 00:40:8c:xx:xx:xx Sent Deauthenticate to mobile on BSSID a4:0c:c3:yy:yy:yy slot 0(caller apf_ms.c:5921)

*apfReceiveTask: Jan 05 17:15:29.713: 00:40:8c:xx:xx:xx apfMsAssoStateDec

*apfReceiveTask: Jan 05 17:15:29.713: 00:40:8c:xx:xx:xx apfMsExpireMobileStation (apf_ms.c:5959) Changing state for mobile 00:40:8c:xx:xx:xx on AP a4:0c:c3:yy:yy:yy from Disassociated to Idle

*apfReceiveTask: Jan 05 17:15:29.713: 00:40:8c:xx:xx:xx pemApfDeleteMobileStation2: APF_MS_PEM_WAIT_L2_AUTH_COMPLETE = 0.

*apfReceiveTask: Jan 05 17:15:29.713: 00:40:8c:xx:xx:xx 172.16.xx.9 RUN (20) Deleted mobile LWAPP rule on AP [a4:0c:c3:yy:yy:yy]

*apfReceiveTask: Jan 05 17:15:29.713: 00:40:8c:xx:xx:xx apfMsRunStateDec

*apfReceiveTask: Jan 05 17:15:29.713: 00:40:8c:xx:xx:xx apfMs1xStateDec

*apfReceiveTask: Jan 05 17:15:29.713: 00:40:8c:xx:xx:xx Deleting mobile on AP a4:0c:c3:yy:yy:yy(0)

*pemReceiveTask: Jan 05 17:15:29.715: 00:40:8c:xx:xx:xx 172.16.xx.9 Removed NPU entry.

Hall of Fame Super Gold

Re: WLC2504 disconnecting a client

Out of curiosity, how many cameras do you have that is connected via wireless?

If you have more than one, I would like to know if this is affecting ALL your cameras or not.

Can you also verify with the wireless camera manufacturer for any new firmware release? Bascially, can you ensure the firmware of the camera are up-to-date?

Sent from Cisco Technical Support Nintendo App

New Member

Re: WLC2504 disconnecting a client

Thanks Leo,

There are 3x cameras in total.

1x Axis 207W

1x Axis 207MW

1x Axis M1034-W

All cameras have the latest firmware and have done since installation and the 207 cameras do not disconnect.

Axis have been providing technical support on the M1034-W.

I am going to compare how the M1034-W behaves with an isolated wireless router.

New Member

I experienced a similar

I experienced a similar situation with an Axis 211W.

 

When I would connect the device to my secured camera network with a static IP address, it would never show an IP in the client connection on the WLC. I got messages related to "Not sending gratuitous ARP" from the WLC console.

When I would check in the core router, no ARP entry for the camera's MAC address existed.

I left the Axis camera off over night, and when I got in the office this morning, I turned it back on.

Connected right up. When I checked the core ARP table, it was there.

What's going on here? Why did waiting overnight fix it? Is there some sort of periodic ARP flush that happens? I am continuing to test, and it seems to be working (about 30 minutes now) but I am still confused and trying to understand why doing what I did had any positive impact.

1108
Views
0
Helpful
9
Replies
CreatePlease to create content