WLC 5508 / 2602e LAP / Dropped Connections

                  We are starting to experience some dropped connections while utilizing a 5508 WLC (SW: 7.4.100.0) with 2602e LAP's.  The connections seem to drop for 1-2 seconds and then reconnect on their own.  Machines and cards are varied.  Any thoughts?

Just adding to Leo, and Rasika..
Just check these features
The User Idle Timeout: When a user is idle without any communication with the LAP for the amount of time set as User Idle Timeout, the client is deauthenticated by the WLC. The client has to reauthenticate and       reassociate to the WLC. It is used in situations where a client can drop out from its associated LAP without notifying the LAP.
The Session Timeout is the maximum time for a client session with the WLC. After this time, WLC de-authenticates the client, and the client goes through the whole authentication (re-authentication) process again.
This parameter can be accessed from the WLANs > Edit menu.
Hope it helps.
Regards

Similar Messages

  • WLC 5508 with LAP-1142n - Several Errors

    Hello all,
    I had installed a WLC 5508 with 7 LAP 1142n and 2 converted AP 1131abg.
    I am seeing some errors relating 2 issues.
    1st- One particular AP 1142 is disassociating and reseting the radios.
    /* Style Definitions */
    table.MsoNormalTable
    {mso-style-name:"Table Normal";
    mso-tstyle-rowband-size:0;
    mso-tstyle-colband-size:0;
    mso-style-noshow:yes;
    mso-style-priority:99;
    mso-style-qformat:yes;
    mso-style-parent:"";
    mso-padding-alt:0cm 5.4pt 0cm 5.4pt;
    mso-para-margin:0cm;
    mso-para-margin-bottom:.0001pt;
    mso-pagination:widow-orphan;
    font-size:10.0pt;
    font-family:"Times New Roman","serif";}
    Thu Oct 28 11:50:49 2010
    AP's Interface:0(802.11b)   Operation State Up: Base Radio MAC:e8:04:62:23:ac:e0 Cause=Radio interface   reset. Status:NA
    Thu Oct 28 11:50:49 2010
    AP's Interface:0(802.11b)   Operation State Down: Base Radio MAC:e8:04:62:23:ac:e0 Cause=Radio interface   reset. Status:NA
    Thu Oct 28 11:50:49 2010
    AP's Interface:1(802.11a)   Operation State Up: Base Radio MAC:e8:04:62:23:ac:e0 Cause=Radio interface   reset. Status:NA
    Thu Oct 28 11:50:49 2010
    AP's Interface:1(802.11a)   Operation State Down: Base Radio MAC:e8:04:62:23:ac:e0 Cause=Radio interface   reset. Status:NA
    Thu Oct 28 11:50:46 2010
    AP's Interface:1(802.11a) Operation   State Up: Base Radio MAC:e8:04:62:23:ac:e0 Cause=Radio reset due to Init.   Status:NA
    Thu Oct 28 11:50:46 2010
    AP's Interface:0(802.11b)   Operation State Up: Base Radio MAC:e8:04:62:23:ac:e0 Cause=Radio reset due to   Init. Status:NA
    Thu Oct 28 11:50:46 2010
    AP 'AP3', MAC:   e8:04:62:23:ac:e0 disassociated previously due to AP Reset. Uptime: 1 days,   10 h 24 m 23 s . Last reset reason: operator changed 11g mode.
    Thu Oct 28 11:50:35 2010
    AP Disassociated. Base Radio   MAC:e8:04:62:23:ac:e0
    Thu Oct 28 11:50:35 2010
    AP's Interface:1(802.11a)   Operation State Down: Base Radio MAC:e8:04:62:23:ac:e0 Cause=New Discovery Status:NA
    Thu Oct 28 11:50:35 2010
    AP's Interface:0(802.11b) Operation   State Down: Base Radio MAC:e8:04:62:23:ac:e0 Cause=New Discovery Status:NA
    I had some search, and the new discovery cause, might be that the AP didnt know what WLC do associate, in a multi-controller environment. This is not the case. I only have one WLC in the same management vlan.
    2st-The Radius server is beeing related in the logs as been deactivated. I raise the server time-out on Radius configuration option, but it still continues to do it.
    /* Style Definitions */
    table.MsoNormalTable
    {mso-style-name:"Table Normal";
    mso-tstyle-rowband-size:0;
    mso-tstyle-colband-size:0;
    mso-style-noshow:yes;
    mso-style-priority:99;
    mso-style-qformat:yes;
    mso-style-parent:"";
    mso-padding-alt:0cm 5.4pt 0cm 5.4pt;
    mso-para-margin:0cm;
    mso-para-margin-bottom:.0001pt;
    mso-pagination:widow-orphan;
    font-size:10.0pt;
    font-family:"Times New Roman","serif";}
    Thu Oct 28 10:24:41 2010
    RADIUS server 10.67.128.36:1812 deactivated in global list
    Thu Oct 28 10:24:41 2010
    RADIUS server 10.67.128.36:1812 failed to respond to request (ID 172)   for client e8:06:88:51:c0:2b / user 'unknown'
    Is this meaning the WLC stop sending request to the Radius Server ? We dont have BackUp Radius.
    As far as i know, its always the same mac-address client that is associated to that error, maybe a iphone.
    I had so many clients in that SSID and they are all working good.
    The Radius server is a NPS from windows Server 2008
    /* Style Definitions */
    table.MsoNormalTable
    {mso-style-name:"Table Normal";
    mso-tstyle-rowband-size:0;
    mso-tstyle-colband-size:0;
    mso-style-noshow:yes;
    mso-style-priority:99;
    mso-style-qformat:yes;
    mso-style-parent:"";
    mso-padding-alt:0cm 5.4pt 0cm 5.4pt;
    mso-para-margin:0cm;
    mso-para-margin-bottom:.0001pt;
    mso-pagination:widow-orphan;
    font-size:10.0pt;
    font-family:"Times New Roman","serif";}
    , and the client says that the medium response time is 0,02 sec, so im wondering why the controller is not getting response from Radius for a particular client?! My client also says, that didnt found any log related to that mac-address client ... what is weird...
    WLC with last software available 7.0.164
    Hope some one help me here.
    Best Regards,
    Bruno Petrónio

    Thanks Scott,
    I understand what you are mentioning, and i really didnt do it yet.
    I realize that the primary controller was not configured on the
    /* Style Definitions */
    table.MsoNormalTable
    {mso-style-name:"Table Normal";
    mso-tstyle-rowband-size:0;
    mso-tstyle-colband-size:0;
    mso-style-noshow:yes;
    mso-style-priority:99;
    mso-style-qformat:yes;
    mso-style-parent:"";
    mso-padding-alt:0cm 5.4pt 0cm 5.4pt;
    mso-para-margin:0cm;
    mso-para-margin-bottom:.0001pt;
    mso-pagination:widow-orphan;
    font-size:10.0pt;
    font-family:"Times New Roman","serif";}
    Wireless –> All APs –> High Availability tab, and did it only to the AP that is taking this beahviour.
    Is this mandatory for a 1 controller only ?
    No mather what the manual say, after that the AP is rebooting 2 mins in 2 mins... with the same kind of messages.
    The interface on the switch is getting a few input errors and the same numbers of crc... but are so few...
    Next step ... i will change it to another one's place/pathing cable.
    Regarding the Radius messages... any ideas ?
    I'm already on 30 sec's of server timeout.
    Best Regards,
    Bruno Petrónio

  • WLC 5508 intermittent loss of connectivity

    Hi.
    I have a WLC 5508 connecting directly to a distribution switch (3850) via a layer 2 etherchannel trunk fibre link with LAG enabled on the WLC.
    Whenever there is a loss of power to the server room where both devices are hosted & power later gets restored, the distribution switch & WLC lose Layer 2 & 3 connectivity. Connectivity only gets restored when the WLC is power cycled or the fibre cables connecting to its SFP ports are removed & plugged back in. When this is done connectivity is restored between them, APs associate etc. Once there is a loss of power to the room for whatsoever reason again, the loss of connectivity issue re-occurs.
    Disabled the etherchannel at some point, using only a single fibre trunk link between them, but the issue persists.
    Also check for interface errors, CRCs, etc on both ends but there are none.
    Can anyone please advice me on what the issue is & what can be done to permanently resolve this?
    Thanks in anticipation.
    Ope.

    Software version is 7.4.100.0
    int gig1/0/5
      switchport mode trunk
      switchport trunk encapsulation dot1q
      channel-group 1 mode on
    int gig1/0/6
    switchport mode trunk
    switchport trunk encapsulation dot1q
    channel-group 1 mode on
    Port setting on the switch is set to auto-negotiate. Port setting on the controller is "auto". The link has been negotiated (& always negotiates) to 1000Mbps full duplex on both ends.
    Presently in transit with no way of connecting to the device, but I checked the duplex & speed settings on both devices which was appropriately negotiated. Also checked for interface error counters on the switch, there was none. Checked the WLC logs too, there were no logs on issues with the interfaces or auto-negotiation.

  • Low Bandwith, WLC 5508 and LAP 1142N, please help !

    Hello Everyone
    For the Environment:
    - I have a WLC 5508 With a license up to 100 AP, at the Point there are 39 AP connected.
    - The WLC is connected with 8x 1Gbit/s, as a Trunk ==> 2 Members of 3750 Switches Stack ( 4gig and 4 gig)
    - The AP are connected to diferent 2960s with an Uplink ( 3 Gbit/s)  to the 3750 Switches
    - There are max. 12 AP on each 2960s
    - The AP are powered over Ethernet
    The AP:
    - it runs a/b/g/n and on 2,4 Ghz i schould have 300 mbit/s as for the 5 Ghz it schould also run 300mbit /s
    - the Ap has an uplink of 1 Gbit/s
    The clients:
    - have a intel Wifi link 5300 AGN Card
    To the Problem:
    - if i connect to one AP, and the Signal strength is High, i get an upload rate of max. 6-8Mbyte/s.
      and i am the only Person uploading.
      if i upload from 3 clients the same data from the same spot to the same target i get 2-3 Mbyte/s per client.
      if connect to the same target and run over ethernet cable fom the same spot, i get an upload of 70 -85 Mbyte/s.
    Question:
    - Why am i having these Bandwith problems ??

    Thanks Scott,
    I understand what you are mentioning, and i really didnt do it yet.
    I realize that the primary controller was not configured on the
    /* Style Definitions */
    table.MsoNormalTable
    {mso-style-name:"Table Normal";
    mso-tstyle-rowband-size:0;
    mso-tstyle-colband-size:0;
    mso-style-noshow:yes;
    mso-style-priority:99;
    mso-style-qformat:yes;
    mso-style-parent:"";
    mso-padding-alt:0cm 5.4pt 0cm 5.4pt;
    mso-para-margin:0cm;
    mso-para-margin-bottom:.0001pt;
    mso-pagination:widow-orphan;
    font-size:10.0pt;
    font-family:"Times New Roman","serif";}
    Wireless –> All APs –> High Availability tab, and did it only to the AP that is taking this beahviour.
    Is this mandatory for a 1 controller only ?
    No mather what the manual say, after that the AP is rebooting 2 mins in 2 mins... with the same kind of messages.
    The interface on the switch is getting a few input errors and the same numbers of crc... but are so few...
    Next step ... i will change it to another one's place/pathing cable.
    Regarding the Radius messages... any ideas ?
    I'm already on 30 sec's of server timeout.
    Best Regards,
    Bruno Petrónio

  • WLC 5508 - Client Intermittent Drop Out

    We have an intermittent issue where clients seeem to drop their connectivity intermittently and I wondered if anyone else have seen this.
    When the client drops out it is associated to the AP at good signal strength -45 -> -49 dbm. All our clients are running Win7. Once the issue occurs a yellow exclamation mark appear across the system tray wireless icon and a message appears in the "Network and Sharing Centre" that either says “no internet connection” or “DNS server not responding". The association with the AP appears to be intact. This seems to be confirmed as the client can ping its default gateway and can be pinged from another device but no connectivity above layer 3 appear to be working. Really the best way to describe it is that all communication above layer 3 stops. This behaviour is extremely intermittent.
    The wireless clients are a small cross section of HP business laptops. HP8460p, HP6930p and a few other models. The laptops are all running the latest wireless drivers available (that was the first thing we tried). We have two 5508 wireless controllers operating 60 APs between them. Most of the APs in the area where we are seeing the issue are AIR-LAP1242 we do run the AIR-CAP3502 also but not in this area. We only have 2.4GHz enabled but with the extended data rates (to 130mbps). We have multiple WLANs but the one that seems to be causing the issue is the only one running WPA2.
    The only way to restore full connectivity to the client is to hard reset the wireless adapter.
    We have run debugs on the client and ran a sniffer trace between the controller and the authentication server but so far this has not turned up anything. The wireless controller is showing the client still associated but a link test from the controller to the client failed.
    Any ideas would be welcome. I can provide further information if required.

    Hi
    What EAP type do you have deployed, as I guess you are using 802.1X?
    Does this problem occur during client roaming?
    Is the problem specific to only HP devices or are other laptop vendors in the mix?
    I would suggest that you perform a packet capture on one of the wireless clients when the problem happens. You could use wireshark. Perform the following tests during the capture:
    1. Ping a remote device on a different subnet.
    2. Perform a layer 4 and above activity such as opening a web page or FTP.
    In the interim, you could try the following:
    1. Disable Aironet IE on the WLAN SSID Advanced tab
    2. Increase the packet max-retries timeout value on the dot11radio interface.

  • LAP drops client connections

    Hello! we have WLC 5508 (6.0.188.0) and some converted APs   AIR-AP1141N-E-K9. Everything works fine except one moment:
    1 of this converted APs is located beyond the office building, but it is still connected to our local network as if it was located within the office (there is a fiber channel between our cisco core switch and a switch, to which that 1 LAP is connected)
    The trouble is that users can't have the normal wi-fi on that beyond LAP. I see few successful pings to the "associated" client then drops, again a little success, than long drops.
    Logs from the WLC:
    Feb 15 10:04:53 172.22.90.20 Wi-Fi_Controller: *Feb 15 10:11:17.702: %DOT1X-3-MAX_EAPOL_KEY_RETRANS: 1x_ptsm.c:407 Max EAPOL-key M1 retransmissions exceeded for client xx:xx:xx:xx:xx:xx
    Feb 15 10:04:57 172.22.90.20 Wi-Fi_Controller: *Feb 15 10:11:22.104: %DOT1X-3-MAX_EAPOL_KEY_RETRANS: 1x_ptsm.c:407 Max EAPOL-key M1 retransmissions exceeded for client xx:xx:xx:xx:xx:xx
    Feb 15 10:36:14 172.22.90.20 Wi-Fi_Controller: *Feb 15 10:42:38.859: %DOT1X-3-INVALID_REPLAY_CTR: 1x_eapkey.c:354 Invalid replay counter from client xx:xx:xx:xx:xx:xx - got 00 00 00 00 00 00 00 00, expected 00 00 00 00 00 00 00 01
    Feb 15 10:37:07 172.22.90.20 Wi-Fi_Controller: *Feb 15 10:43:32.061: %DOT1X-3-MAX_EAPOL_KEY_RETRANS: 1x_ptsm.c:407 Max EAPOL-key M3 retransmissions exceeded for client xx:xx:xx:xx:xx:xx
    Feb 15 10:37:12 172.22.90.20 Wi-Fi_Controller: *Feb 15 10:43:37.061: %DOT1X-3-MAX_EAPOL_KEY_RETRANS: 1x_ptsm.c:407 Max EAPOL-key M1 retransmissions exceeded for client xx:xx:xx:xx:xx:xx
    Feb 15 10:37:16 172.22.90.20 Wi-Fi_Controller: *Feb 15 10:43:40.888: %DOT1X-1-INVALID_WPA_KEY_STATE: 1x_eapkey.c:1638 Received EAPOL-key message while in invalid state (0) - version 1, type 3, descriptor 2, client xx:xx:xx:xx:xx:xx
    Feb 15 10:37:21 172.22.90.20 Wi-Fi_Controller: *Feb 15 10:43:45.661: %DOT1X-3-MAX_EAPOL_KEY_RETRANS: 1x_ptsm.c:407 Max EAPOL-key M1 retransmissions exceeded for client xx:xx:xx:xx:xx:xx
    Feb 15 10:37:23 172.22.90.20 Wi-Fi_Controller: *Feb 15 10:43:47.540: %DOT1X-1-INVALID_WPA_KEY_STATE: 1x_eapkey.c:1638 Received EAPOL-key message while in invalid state (0) - version 1, type 3, descriptor 2, client xx:xx:xx:xx:xx:xx
    Feb 15 10:37:26 172.22.90.20 Wi-Fi_Controller: *Feb 15 10:43:50.461: %DOT1X-3-MAX_EAPOL_KEY_RETRANS: 1x_ptsm.c:407 Max EAPOL-key M1 retransmissions exceeded for client xx:xx:xx:xx:xx:xx
    What could it be? Is it possible that some noises or whatever could cause it? The building with this problematic LAP is a kind of film studio...

    oh, I badly explained what I need again(((
    I don't need only 2.4 Ghz now. I cited just to remind why I was doing this:
    "  I was making an experiment of changing Radio Policy on a WLAN for SSID, to which only Apple users are connecting. I had chosen "802.11a only", then "802.11a/g" only, but finally I left "All" as it was before.   "
    And now I am faced this problem :
    "  But now Apple devices choose only radio 802.11g or 802.11a to connect to, although they could choose 802.11n before my experiments! " Now all that devices have only 54 Mbps as a Current Tx RateSet. They need 144 Mbps, which they had before, while connecting with radio 802.11n
    Any ideas?

  • WLC 5508, SW 6.0.199.4, 1142 AP: Clients getting dropped intermittently

    We have deployed a WLC 5508 w/ SW version 6.0.199.4, 1142 AP's & open authentication w/ MAC filtering. Clients are randomly getting dropped with "Limited Access" shown in Win 7. In this state, the client machine is unable to ping the gateway and sometimes lose their DHCP assigned IP as well. A manual disconnect/re-connect to the SSID is required everytime.
    I ran a debug on one the clients stuck in the "Limited Access" state (debug client xx:xx:xx:xx):
    *Apr 15 16:59:23.205: e0:91:53:60:1f:e4 Adding mobile on LWAPP AP 3c:ce:73:c5:1e:b0(0)
    *Apr 15 16:59:23.205: e0:91:53:60:1f:e4 Scheduling deletion of Mobile Station:  (callerId: 23) in 5 seconds
    *Apr 15 16:59:23.205: e0:91:53:60:1f:e4 apfProcessProbeReq (apf_80211.c:4722) Changing state for mobile e0:91:53:60:1f:e4 on AP 3c:ce:73:c5:1e:b0 from Idle to Probe
    *Apr 15 16:59:23.205: e0:91:53:60:1f:e4 Scheduling deletion of Mobile Station:  (callerId: 24) in 5 seconds
    *Apr 15 16:59:23.225: e0:91:53:60:1f:e4 Scheduling deletion of Mobile Station:  (callerId: 24) in 5 seconds
    *Apr 15 16:59:23.225: e0:91:53:60:1f:e4 Scheduling deletion of Mobile Station:  (callerId: 24) in 5 seconds
    *Apr 15 16:59:23.646: e0:91:53:60:1f:e4 Scheduling deletion of Mobile Station:  (callerId: 24) in 5 seconds
    *Apr 15 16:59:23.646: e0:91:53:60:1f:e4 Scheduling deletion of Mobile Station:  (callerId: 24) in 5 seconds
    *Apr 15 16:59:23.666: e0:91:53:60:1f:e4 Scheduling deletion of Mobile Station:  (callerId: 24) in 5 seconds
    *Apr 15 16:59:23.666: e0:91:53:60:1f:e4 Scheduling deletion of Mobile Station:  (callerId: 24) in 5 seconds
    *Apr 15 16:59:28.553: e0:91:53:60:1f:e4 apfMsExpireCallback (apf_ms.c:418) Expiring Mobile!
    *Apr 15 16:59:28.554: e0:91:53:60:1f:e4 0.0.0.0 START (0) Deleted mobile LWAPP rule on AP [3c:ce:73:c5:1e:b0]
    *Apr 15 16:59:28.554: e0:91:53:60:1f:e4 Deleting mobile on AP 3c:ce:73:c5:1e:b0(0)
    On doing a manual re-connect, got the following logs:
    *Apr 15 17:01:38.143: e0:91:53:60:1f:e4 Association received from mobile on AP b8:62:1f:e9:9f:30
    *Apr 15 17:01:38.143: e0:91:53:60:1f:e4 Applying site-specific IPv6 override for station e0:91:53:60:1f:e4 - vapId 7, site 'Academy', interface 'students'
    *Apr 15 17:01:38.143: e0:91:53:60:1f:e4 Applying IPv6 Interface Policy for station e0:91:53:60:1f:e4 - vlan 15, interface id 14, interface 'students'
    *Apr 15 17:01:38.143: e0:91:53:60:1f:e4 Applying site-specific override for station e0:91:53:60:1f:e4 - vapId 7, site 'Academy', interface 'students'
    *Apr 15 17:01:38.143: e0:91:53:60:1f:e4 0.0.0.0 START (0) Changing ACL 'none' (ACL ID 255) ===> 'none' (ACL ID 255) --- (caller apf_policy.c:1276)
    *Apr 15 17:01:38.143: e0:91:53:60:1f:e4 STA - rates (8): 130 132 139 150 12 18 24 36 0 0 0 0 0 0 0 0
    *Apr 15 17:01:38.143: e0:91:53:60:1f:e4 STA - rates (12): 130 132 139 150 12 18 24 36 48 72 96 108 0 0 0 0
    *Apr 15 17:01:38.143: e0:91:53:60:1f:e4 0.0.0.0 START (0) Deleted mobile LWAPP rule on AP [b8:62:1f:e5:6a:90]
    *Apr 15 17:01:38.144: e0:91:53:60:1f:e4 Updated location for station old AP b8:62:1f:e5:6a:90-0, new AP b8:62:1f:e9:9f:30-0
    *Apr 15 17:01:38.144: e0:91:53:60:1f:e4 apfProcessAssocReq (apf_80211.c:4268) Changing state for mobile e0:91:53:60:1f:e4 on AP b8:62:1f:e9:9f:30 from Probe to AAA Pending
    *Apr 15 17:01:38.144: e0:91:53:60:1f:e4 Scheduling deletion of Mobile Station:  (callerId: 20) in 10 seconds
    *Apr 15 17:01:38.144: e0:91:53:60:1f:e4 0.0.0.0 START (0) Initializing policy
    *Apr 15 17:01:38.144: e0:91:53:60:1f:e4 0.0.0.0 START (0) Change state to AUTHCHECK (2) last state AUTHCHECK (2)
    *Apr 15 17:01:38.144: e0:91:53:60:1f:e4 0.0.0.0 AUTHCHECK (2) Change state to L2AUTHCOMPLETE (4) last state L2AUTHCOMPLETE (4)
    *Apr 15 17:01:38.144: e0:91:53:60:1f:e4 0.0.0.0 L2AUTHCOMPLETE (4) Plumbed mobile LWAPP rule on AP b8:62:1f:e9:9f:30 vapId 7 apVapId 2
    *Apr 15 17:01:38.144: e0:91:53:60:1f:e4 0.0.0.0 L2AUTHCOMPLETE (4) Change state to DHCP_REQD (7) last state DHCP_REQD (7)
    *Apr 15 17:01:38.144: e0:91:53:60:1f:e4 apfPemAddUser2 (apf_policy.c:213) Changing state for mobile e0:91:53:60:1f:e4 on AP b8:62:1f:e9:9f:30 from AAA Pending to Associated
    *Apr 15 17:01:38.145: e0:91:53:60:1f:e4 Scheduling deletion of Mobile Station:  (callerId: 49) in 65535 seconds
    *Apr 15 17:01:38.145: e0:91:53:60:1f:e4 Including FT Mobility Domain IE (length 5) in Initial assoc Resp to mobile
    *Apr 15 17:01:38.145: e0:91:53:60:1f:e4 Sending Assoc Response to station on BSSID b8:62:1f:e9:9f:30 (status 0) Vap Id 2 Slot 0
    *Apr 15 17:01:38.145: e0:91:53:60:1f:e4 apfProcessRadiusAssocResp (apf_80211.c:1957) Changing state for mobile e0:91:53:60:1f:e4 on AP b8:62:1f:e9:9f:30 from Associated to Associated
    *Apr 15 17:01:38.189: e0:91:53:60:1f:e4 DHCP received op BOOTREQUEST (1) (len 308, port 13, encap 0xec03)
    *Apr 15 17:01:38.189: e0:91:53:60:1f:e4 DHCP dropping packet due to ongoing mobility handshake exchange, (siaddr 0.0.0.0,  mobility state = 'apfMsMmQueryRequested'
    *Apr 15 17:01:39.953: e0:91:53:60:1f:e4 0.0.0.0 DHCP_REQD (7) State Update from Mobility-Incomplete to Mobility-Complete, mobility role=Local, client state=APF_MS_STATE_ASSOCIATED
    *Apr 15 17:01:39.954: e0:91:53:60:1f:e4 0.0.0.0 DHCP_REQD (7) pemAdvanceState2 4166, Adding TMP rule
    *Apr 15 17:01:39.954: e0:91:53:60:1f:e4 0.0.0.0 DHCP_REQD (7) Adding Fast Path rule
      type = Airespace AP - Learn IP address
      on AP b8:62:1f:e9:9f:30, slot 0, interface = 13, QOS = 0
      ACL Id = 255, Jumbo F
    *Apr 15 17:01:39.954: e0:91:53:60:1f:e4 0.0.0.0 DHCP_REQD (7) Successfully plumbed mobile rule (ACL ID 255)
    *Apr 15 17:01:39.954: e0:91:53:60:1f:e4 0.0.0.0 Added NPU entry of type 9, dtlFlags 0x0
    *Apr 15 17:01:39.954: e0:91:53:60:1f:e4 Sent an XID frame
    *Apr 15 17:01:40.807: e0:91:53:60:1f:e4 Orphan Packet from STA - IP 169.254.201.128
    *Apr 15 17:01:43.234: e0:91:53:60:1f:e4 DHCP received op BOOTREQUEST (1) (len 308, port 13, encap 0xec03)
    *Apr 15 17:01:43.234: e0:91:53:60:1f:e4 DHCP processing DHCP DISCOVER (1)
    *Apr 15 17:01:43.234: e0:91:53:60:1f:e4 DHCP   op: BOOTREQUEST, htype: Ethernet, hlen: 6, hops: 0
    *Apr 15 17:01:43.234: e0:91:53:60:1f:e4 DHCP   xid: 0x9b24c896 (2602879126), secs: 1280, flags: 0
    *Apr 15 17:01:43.234: e0:91:53:60:1f:e4 DHCP   chaddr: e0:91:53:60:1f:e4
    *Apr 15 17:01:43.234: e0:91:53:60:1f:e4 DHCP   ciaddr: 0.0.0.0,  yiaddr: 0.0.0.0
    *Apr 15 17:01:43.234: e0:91:53:60:1f:e4 DHCP   siaddr: 0.0.0.0,  giaddr: 0.0.0.0
    *Apr 15 17:01:43.234: e0:91:53:60:1f:e4 DHCP successfully bridged packet to DS
    *Apr 15 17:01:43.234: e0:91:53:60:1f:e4 DHCP received op BOOTREPLY (2) (len 308, port 13, encap 0xec00)
    *Apr 15 17:01:43.234: e0:91:53:60:1f:e4 DHCP processing DHCP OFFER (2)
    *Apr 15 17:01:43.234: e0:91:53:60:1f:e4 DHCP   op: BOOTREPLY, htype: Ethernet, hlen: 6, hops: 0
    *Apr 15 17:01:43.234: e0:91:53:60:1f:e4 DHCP   xid: 0x9b24c896 (2602879126), secs: 0, flags: 0
    *Apr 15 17:01:43.234: e0:91:53:60:1f:e4 DHCP   chaddr: e0:91:53:60:1f:e4
    *Apr 15 17:01:43.235: e0:91:53:60:1f:e4 DHCP   ciaddr: 0.0.0.0,  yiaddr: 10.6.2.160
    *Apr 15 17:01:43.235: e0:91:53:60:1f:e4 DHCP   siaddr: 0.0.0.0,  giaddr: 0.0.0.0
    *Apr 15 17:01:43.235: e0:91:53:60:1f:e4 DHCP   server id: 10.6.15.254  rcvd server id: 10.6.15.254
    *Apr 15 17:01:43.235: e0:91:53:60:1f:e4 DHCP successfully bridged packet to STA
    *Apr 15 17:01:43.240: e0:91:53:60:1f:e4 DHCP received op BOOTREQUEST (1) (len 316, port 13, encap 0xec03)
    *Apr 15 17:01:43.241: e0:91:53:60:1f:e4 DHCP processing DHCP REQUEST (3)
    *Apr 15 17:01:43.241: e0:91:53:60:1f:e4 DHCP   op: BOOTREQUEST, htype: Ethernet, hlen: 6, hops: 0
    *Apr 15 17:01:43.241: e0:91:53:60:1f:e4 DHCP   xid: 0x9b24c896 (2602879126), secs: 1280, flags: 0
    *Apr 15 17:01:43.241: e0:91:53:60:1f:e4 DHCP   chaddr: e0:91:53:60:1f:e4
    *Apr 15 17:01:43.241: e0:91:53:60:1f:e4 DHCP   ciaddr: 0.0.0.0,  yiaddr: 0.0.0.0
    *Apr 15 17:01:43.241: e0:91:53:60:1f:e4 DHCP   siaddr: 0.0.0.0,  giaddr: 0.0.0.0
    *Apr 15 17:01:43.241: e0:91:53:60:1f:e4 DHCP   requested ip: 10.6.2.160
    *Apr 15 17:01:43.241: e0:91:53:60:1f:e4 DHCP   server id: 10.6.15.254  rcvd server id: 10.6.15.254
    *Apr 15 17:01:43.241: e0:91:53:60:1f:e4 DHCP successfully bridged packet to DS
    *Apr 15 17:01:43.241: e0:91:53:60:1f:e4 DHCP received op BOOTREPLY (2) (len 308, port 13, encap 0xec00)
    *Apr 15 17:01:43.241: e0:91:53:60:1f:e4 DHCP processing DHCP ACK (5)
    *Apr 15 17:01:43.241: e0:91:53:60:1f:e4 DHCP   op: BOOTREPLY, htype: Ethernet, hlen: 6, hops: 0
    *Apr 15 17:01:43.241: e0:91:53:60:1f:e4 DHCP   xid: 0x9b24c896 (2602879126), secs: 0, flags: 0
    *Apr 15 17:01:43.241: e0:91:53:60:1f:e4 DHCP   chaddr: e0:91:53:60:1f:e4
    *Apr 15 17:01:43.241: e0:91:53:60:1f:e4 DHCP   ciaddr: 0.0.0.0,  yiaddr: 10.6.2.160
    *Apr 15 17:01:43.241: e0:91:53:60:1f:e4 DHCP   siaddr: 0.0.0.0,  giaddr: 0.0.0.0
    *Apr 15 17:01:43.241: e0:91:53:60:1f:e4 DHCP   server id: 10.6.15.254  rcvd server id: 10.6.15.254
    *Apr 15 17:01:43.242: e0:91:53:60:1f:e4 10.6.2.160 DHCP_REQD (7) Change state to RUN (20) last state RUN (20)
    *Apr 15 17:01:43.242: e0:91:53:60:1f:e4 10.6.2.160 RUN (20) Reached PLUMBFASTPATH: from line 4972
    *Apr 15 17:01:43.242: e0:91:53:60:1f:e4 10.6.2.160 RUN (20) Replacing Fast Path rule
      type = Airespace AP Client
      on AP b8:62:1f:e9:9f:30, slot 0, interface = 13, QOS = 0
      ACL Id = 255, Jumbo Frames = NO,
    *Apr 15 17:01:43.242: e0:91:53:60:1f:e4 10.6.2.160 RUN (20) Successfully plumbed mobile rule (ACL ID 255)
    *Apr 15 17:01:43.242: e0:91:53:60:1f:e4 Assigning Address 10.6.2.160 to mobile
    *Apr 15 17:01:43.242: e0:91:53:60:1f:e4 DHCP successfully bridged packet to STA
    *Apr 15 17:01:43.242: e0:91:53:60:1f:e4 10.6.2.160 Added NPU entry of type 1, dtlFlags 0x0
    *Apr 15 17:01:43.242: e0:91:53:60:1f:e4 Sending a gratuitous ARP for 10.6.2.160, VLAN Id 15
    *Apr 15 17:01:46.428: e0:91:53:60:1f:e4 DHCP received op BOOTREQUEST (1) (len 308, port 13, encap 0xec03)
    *Apr 15 17:01:46.428: e0:91:53:60:1f:e4 DHCP processing DHCP INFORM (8)
    *Apr 15 17:01:46.429: e0:91:53:60:1f:e4 DHCP   op: BOOTREQUEST, htype: Ethernet, hlen: 6, hops: 0
    *Apr 15 17:01:46.429: e0:91:53:60:1f:e4 DHCP   xid: 0xbb0d5d87 (3138215303), secs: 0, flags: 0
    *Apr 15 17:01:46.429: e0:91:53:60:1f:e4 DHCP   chaddr: e0:91:53:60:1f:e4
    *Apr 15 17:01:46.429: e0:91:53:60:1f:e4 DHCP   ciaddr: 10.6.2.160,  yiaddr: 0.0.0.0
    *Apr 15 17:01:46.429: e0:91:53:60:1f:e4 DHCP   siaddr: 0.0.0.0,  giaddr: 0.0.0.0
    *Apr 15 17:01:46.429: e0:91:53:60:1f:e4 DHCP successfully bridged packet to DS
    *Apr 15 17:01:46.429: e0:91:53:60:1f:e4 DHCP received op BOOTREPLY (2) (len 308, port 13, encap 0xec00)
    *Apr 15 17:01:46.429: e0:91:53:60:1f:e4 DHCP processing DHCP ACK (5)
    *Apr 15 17:01:46.429: e0:91:53:60:1f:e4 DHCP   op: BOOTREPLY, htype: Ethernet, hlen: 6, hops: 0
    *Apr 15 17:01:46.429: e0:91:53:60:1f:e4 DHCP   xid: 0xbb0d5d87 (3138215303), secs: 0, flags: 0
    *Apr 15 17:01:46.429: e0:91:53:60:1f:e4 DHCP   chaddr: e0:91:53:60:1f:e4
    *Apr 15 17:01:46.429: e0:91:53:60:1f:e4 DHCP   ciaddr: 10.6.2.160,  yiaddr: 0.0.0.0
    *Apr 15 17:01:46.429: e0:91:53:60:1f:e4 DHCP   siaddr: 0.0.0.0,  giaddr: 0.0.0.0
    *Apr 15 17:01:46.429: e0:91:53:60:1f:e4 DHCP   server id: 10.6.15.254  rcvd server id: 10.6.15.254
    show client e0:91:53:60:1f:e4 (after re-connect)
    (Cisco Controller) >show client detail e0:91:53:60:1f:e4
    Client MAC Address............................... e0:91:53:60:1f:e4
    Client Username ................................. N/A
    AP MAC Address................................... b8:62:1f:e9:9f:30
    Client State..................................... Associated    
    Client NAC OOB State............................. Access
    Wireless LAN Id.................................. 7 
    BSSID............................................ b8:62:1f:e9:9f:31 
    Connected For ................................... 105 secs
    Channel.......................................... 11
    IP Address....................................... 10.6.2.160
    Association Id................................... 8 
    Authentication Algorithm......................... Open System
    Reason Code...................................... 1 
    Status Code...................................... 0 
    Session Timeout.................................. 65535
    Client CCX version............................... No CCX support
    QoS Level........................................ Silver
    Diff Serv Code Point (DSCP)...................... disabled
    802.1P Priority Tag.............................. disabled
    WMM Support...................................... Enabled
    U-APSD Support................................... Disabled
    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
    ACL Name......................................... none
    ACL Applied Status............................... Unavailable
    Policy Type...................................... N/A
    Encryption Cipher................................ None
    Management Frame Protection...................... No
    EAP Type......................................... Unknown
    Interface........................................ students
    VLAN............................................. 15
    Quarantine VLAN.................................. 0
    Access VLAN...................................... 15
    Client Capabilities:
          CF Pollable................................ Not implemented
          CF Poll Request............................ Not implemented
          Short Preamble............................. Implemented
          PBCC....................................... Not implemented
          Channel Agility............................ Not implemented
          Listen Interval............................ 1
          Fast BSS Transition........................ Not implemented
    Fast BSS Transition Details:
    Client Statistics:
          Number of Bytes Received................... 36509
          Number of Bytes Sent....................... 32902
          Number of Packets Received................. 300
          Number of Packets Sent..................... 66
          Number of EAP Id Request Msg Timeouts...... 0
          Number of EAP Request Msg Timeouts......... 0
          Number of EAP Key Msg Timeouts............. 0
          Number of Data Retries..................... 95
          Number of RTS Retries...................... 0
          Number of Duplicate Received Packets....... 1
          Number of Decrypt Failed Packets........... 0
          Number of Mic Failured Packets............. 0
          Number of Mic Missing Packets.............. 0
          Number of Policy Errors.................... 0
          Radio Signal Strength Indicator............ -66 dBm
          Signal to Noise Ratio...................... 29 dB
    Nearby AP Statistics:
          APSOEBFF_COR3(slot 0) .....................
    antenna0: 50 seconds ago -91 dBm................. antenna1: 50 seconds ago -76 dBm
          APSOEAFF_FAC(slot 0) ......................
    antenna0: 108 seconds ago -89 dBm................ antenna1: 108 seconds ago -87 dBm
          APSOEBGF_FAC(slot 0) ......................
    antenna0: 50 seconds ago -82 dBm................. antenna1: 50 seconds ago -71 dBm
          APSOEBGF_STAFF(slot 0) ....................
    antenna0: 49 seconds ago -74 dBm................. antenna1: 49 seconds ago -58 dBm
    WLAN config
    WLAN Identifier.................................. 9
    Profile Name..................................... STAFF
    Network Name (SSID).............................. STAFF
    Status........................................... Enabled
    MAC Filtering.................................... Enabled
    Broadcast SSID................................... Enabled
    AAA Policy Override.............................. Disabled
    Network Admission Control
      NAC-State...................................... Disabled
      Quarantine VLAN................................ 0
    Number of Active Clients......................... 32
    Exclusionlist.................................... Disabled
    Session Timeout.................................. Infinity
    CHD per WLAN..................................... Disabled
    Webauth DHCP exclusion........................... Disabled
    Interface........................................ staff
    WLAN ACL......................................... unconfigured
    DHCP Server...................................... Default
    DHCP Address Assignment Required................. Disabled
    Quality of Service............................... Silver (best effort)
    Scan Defer Priority.............................. 5,6
    Scan Defer Time.................................. 100 milliseconds
    WMM.............................................. Allowed
    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
    IPv6 Support..................................... 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................................ Disabled
       Accounting.................................... Disabled
       Dynamic Interface............................. Disabled
    Local EAP Authentication......................... Disabled
    Security
       802.11 Authentication:........................ Open System
       Static WEP Keys............................... Disabled
       802.1X........................................ Disabled
       Wi-Fi Protected Access (WPA/WPA2)............. Disabled
       CKIP ......................................... Disabled
       Web Based Authentication...................... Disabled
       Web-Passthrough............................... Disabled
       Conditional Web Redirect...................... Disabled
       Splash-Page Web Redirect...................... Disabled
       Auto Anchor................................... Disabled
       H-REAP Local Switching........................ Disabled
       H-REAP Learn IP Address....................... Enabled
       Infrastructure MFP protection................. Enabled (Global Infrastructure MFP Disabled)
       Client MFP.................................... Optional but inactive (WPA2 not configured)
       Tkip MIC Countermeasure Hold-down Timer....... 60
    Call Snooping.................................... Disabled
    Band Select...................................... Disabled
    Load Balancing................................... Disabled
    HELPPPP!

    We have 75 evenly distributed AP's servicing the 500 odd users. Found the below traps on WLC. I was making some changes in the WLAN settings at the time:
    Tue Apr 16 00:03:45 2013          Client Excluded: MACAddress:8c:a9:82:5d:d2:dc Base Radio MAC :3c:ce:73:c6:fe:00 Slot: 0 User Name: unknown Ip Address: unknown Reason:802.11 Association failed repeatedly. ReasonCode: 2
    106          Tue Apr 16 00:03:45 2013          Client Excluded: MACAddress:58:94:6b:f2:24:c8 Base Radio MAC :c8:f9:f9:4c:01:30 Slot: 1 User Name: unknown Ip Address: unknown Reason:802.11 Association failed repeatedly. ReasonCode: 2
    107          Tue Apr 16 00:03:45 2013          Client Excluded: MACAddress:bc:77:37:72:dc:0b Base Radio MAC :3c:ce:73:c6:53:10 Slot: 0 User Name: unknown Ip Address: unknown Reason:802.11 Association failed repeatedly. ReasonCode: 2
    108          Tue Apr 16 00:03:45 2013          Client Excluded: MACAddress:00:26:c7:7d:12:76 Base Radio MAC :3c:ce:73:c4:79:80 Slot: 0 User Name: unknown Ip Address: unknown Reason:802.11 Association failed repeatedly. ReasonCode: 2
    109          Tue Apr 16 00:03:45 2013          Client Excluded: MACAddress:bc:77:37:75:1f:93 Base Radio MAC :c8:f9:f9:2b:85:30 Slot: 0 User Name: unknown Ip Address: unknown Reason:802.11 Association failed repeatedly. ReasonCode: 2
    110          Tue Apr 16 00:03:45 2013          Client Excluded: MACAddress:ac:72:89:58:8e:b9 Base Radio MAC :3c:ce:73:c6:53:10 Slot: 0 User Name: unknown Ip Address: unknown Reason:802.11 Association failed repeatedly. ReasonCode: 2
    111          Tue Apr 16 00:03:44 2013          Client Excluded: MACAddress:bc:77:37:26:cd:e3 Base Radio MAC :3c:ce:73:c5:1f:10 Slot: 0 User Name: unknown Ip Address: unknown Reason:802.11 Association failed repeatedly. ReasonCode: 2
    112          Tue Apr 16 00:03:44 2013          Client Excluded: MACAddress:ac:72:89:25:ea:e0 Base Radio MAC :3c:ce:73:c6:77:70 Slot: 0 User Name: unknown Ip Address: unknown Reason:802.11 Association failed repeatedly. ReasonCode: 2
    113          Tue Apr 16 00:03:44 2013          Client Excluded: MACAddress:00:24:2c:6a:85:3d Base Radio MAC :3c:ce:73:c6:6a:50 Slot: 0 User Name: unknown Ip Address: unknown Reason:802.11 Association failed repeatedly. ReasonCode: 2
    114          Tue Apr 16 00:03:44 2013          Client Excluded: MACAddress:68:5d:43:61:16:51 Base Radio MAC :3c:ce:73:f6:0c:20 Slot: 0 User Name: unknown Ip Address: unknown Reason:802.11 Association failed repeatedly. ReasonCode: 2
    115          Tue Apr 16 00:03:44 2013          Client Excluded: MACAddress:7c:d1:c3:8a:64:f6 Base Radio MAC :3c:ce:73:c4:74:20 Slot: 1 User Name: unknown Ip Address: unknown Reason:802.11 Association failed repeatedly. ReasonCode: 2

  • Wlc 5508: windows 8 can't connect using wpa+wpa2

    Dear All,
    I need your help.
    My customer have Cisco WLC 5508 (cisco wlc 7.0.116.0) .
    We create ssid with layer 2 security wpa+wpa2.
    Using Windows 8, it's can't connect to the wireless lan.
    But if I change, the ssid, with layer 2 security wep.
    It can connect / connected.
    Please help.
    Thanks,
    Jerri

    This is a known issue with Windows 8.  You need to upgrade your firmware to 7.0.250.X for wireless clients running Win8. 
    Another thing, choose one:  Either WPA or WPA2.  Don't enable one and "hope" the wireless client will make the choice because most of the time, they won't.

  • WLC 5508 - Failed to connect from LMS 3.2

    Hello.
    I am trying to include a WLC 5508 in our LMS 3.2.
    I have defined the device and credentials, but the LMS server cannot get access to it.
    If I try to check de device credentials from the Device Center I get a "failed to connect", but if I a try a telnet session, also from Device Center, I get a connection.
    I checked the credentails are OK.
    Thank you.

    Hi,
    You need to download and install the last package : WLC.RME431.v2-1.zip : http://www.cisco.com/cisco/software/cart.html?imageGuId=E3A42793DA29A1B6AC3024C088F9FBC2B324EC8B&i=rs
    You must install : MDF 1.37
    You must install packages before WLC.RME431.v2-1.zip:
    SharedSwimWLC.RME431.v1-2.zip
    SharedDcmaWLC.RME431.v1-1.zip
    SharedSwimIOS.RME431.v2-5-4.zip
    LibSwim.RME431.v2-5-3.zip
    LibCommon.RME431.v2-4-2.zip
    Elisabeth
    WLC.RME431.v2-1.readme:
    Supported Devices
    =================
    Device Type : Cisco 5500 Series Wireless LAN Controllers
           Cisco 3750 Switch with Wireless LAN Controller
    Devices/Modules Supported :
    Cisco 5508 Wireless LAN Controller : 1.3.6.1.4.1.9.1.1069
    Cisco 3750 24+2 port 10/100/1000 Switch with integrated Cisco 4402 Wireless Controller: 1.3.6.1.4.1.9.1.747
    Features Supported:
    Inventory Manager : Yes
    Syslog Analyzer : Yes
    Config.Mgmt  : Yes
    Software Mgmt : Yes
    Minimum Software : 6.0.188.0
    Hardware and Software Requirements
    ==================================
    Hardware and software requirements are the same as those needed for Resource Manager
    Essentials 4.3.1 installation.
    You must install Resource Manager Essentials 4.3.1 and MDF 1.37 before installing the
    device package.
    For a detailed list of requirements, as well as instructions for installing Resource
    Manager Essentials 4.3.1, go to Cisco.com.
    For documentation on Resource Manager Essentials, see:
    http://www.cisco.com/en/US/products/sw/cscowork/ps2073/tsd_products_support_series_home.html
    Package Dependencies
    ====================
    To install the WLC Package, you must install the
    following dependent packages:
    SharedSwimWLC.RME431.v1-2.zip
    SharedDcmaWLC.RME431.v1-1.zip
    SharedSwimIOS.RME431.v2-5-4.zip
    LibSwim.RME431.v2-5-3.zip
    LibCommon.RME431.v2-4-2.zip

  • WLC 5508 disable wlan client still connected

    I have one wlc 5508 running on latest IOS 7.116, there is one wlan abc which i have disable status and disable broadcast, but randomly still i can see from wlc dashboard there is one client connected to this wlan abc. The moment i check on the client details, there is no client connected to that wlan and when return to dashboard, no more client connected to that wlan abc. This happened in randomly, it is bug or something else?

    I would guess that the client entry also indicates "probing" as status. It means that the client is not connected. It is actually probing, so it"s looking for that SSID that it probably associated to in the past (so it remembers about it)

  • 1310 LAP unable to join WLC 5508

    Hi All,
    Hope to you a very happy new year,
    I have an (AIR-LAP1310G-E-K9R) and I tried to join it to WLC 5508 but I'm facing an error,
    I get this error from the LAP 1310 console as below:
    Compiled Mon 17-Jul-06 11:45 by alnguyen
    *Mar  1 00:00:05.289: %LINK-3-UPDOWN: Interface FastEthernet0, changed state to up
    *Mar  1 00:00:06.289: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0, changed state to up
    *Mar  1 00:00:23.337: %LWAPP-5-CHANGED: LWAPP changed state to DISCOVERY
    *Mar  1 00:00:33.477: %DHCP-6-ADDRESS_ASSIGN: Interface FastEthernet0 assigned DHCP address 10.114.36.25, mask 255.255.255.0, hostname APe4d3.f1c2.8882
    examining image...
    *Mar  1 00:00:44.781: %LWAPP-5-CHANGED: LWAPP changed state to JOIN
    *Jan 11 15:21:37.178: %LWAPP-5-CHANGED: LWAPP changed state to IMAGE
    %Error opening  (Protocol error)archive download: takes 6 seconds
    *Jan 11 15:21:43.178: LWAPP_CLIENT_ERROR_DEBUG:  Retransmission count for packet exceeded more than max(IMAGE_DATA
    , 1)
    *Jan 11 15:21:43.178: %LWAPP-5-CHANGED: LWAPP changed state to DISCOVERY
    *Jan 11 15:21:43.179: %LWAPP-5-CHANGED: LWAPP changed state to DISCOVERY
    *Jan 11 15:21:43.181: LWAPP_CLIENT_ERROR: not receive read response(3)
    *Jan 11 15:21:43.185: lwapp_image_proc: unable to open tar file
    *Jan 11 15:21:43.200: %SYS-5-RELOAD: Reload requested by lwapp image download proc. Reload Reason: Reason unspecified.
    *Jan 11 15:21:43.201: %LWAPP-5-CHANGED: LWAPP changed state to DOWN
    *Jan 11 15:21:43.207: %LWAPP-5-CHANGED: LWAPP changed state to DISCOVERYXmodem file system is available.
    flashfs[0]: 3 files, 2 directories
    flashfs[0]: 0 orphaned files, 0 orphaned directories
    flashfs[0]: Total bytes: 7741440
    flashfs[0]: Bytes used: 1861632
    flashfs[0]: Bytes available: 5879808
    flashfs[0]: flashfs fsck took 14 seconds.
    Base ethernet MAC Address: e4:d3:f1:c2:88:82
    Initializing ethernet port 0...
    Reset ethernet port 0...
    Reset done!
    ethernet link up, 100 mbps, full-duplex
    Ethernet port 0 initialized: link is up
    Loading "flash:/c1310-rcvk9w8-mx/c1310-rcvk9w8-mx"...#######################################################################################################################################################################
    File "flash:/c1310-rcvk9w8-mx/c1310-rcvk9w8-mx" uncompressed and installed, entry point: 0x3000
    executing...
                  Restricted Rights Legend
    Use, duplication, or disclosure by the Government is
    subject to restrictions as set forth in subparagraph
    (c) of the Commercial Computer Software - Restricted
    Rights clause at FAR sec. 52.227-19 and subparagraph
    (c) (1) (ii) of the Rights in Technical Data and Computer
    Software clause at DFARS sec. 252.227-7013.
               cisco Systems, Inc.
               170 West Tasman Drive
               San Jose, California 95134-1706
    Cisco IOS Software, C1310 Software (C1310-RCVK9W8-M), Version 12.3(11)JX1, RELEASE SOFTWARE (fc1)
    Technical Support: http://www.cisco.com/techsupport
    Copyright (c) 1986-2006 by Cisco Systems, Inc.
    Compiled Mon 17-Jul-06 11:45 by alnguyen
    Image text-base: 0x00003000, data-base: 0x00359EA0
    Initializing flashfs...
    flashfs[1]: 3 files, 2 directories
    flashfs[1]: 0 orphaned files, 0 orphaned directories
    flashfs[1]: Total bytes: 7741440
    flashfs[1]: Bytes used: 1861632
    flashfs[1]: Bytes available: 5879808
    flashfs[1]: flashfs fsck took 2 seconds.
    flashfs[1]: Initialization complete....done Initializing flashfs.
    cisco AIR-LAP1310G-E-K9R   (PowerPCElvis) processor (revision B0) with 24566K/8192K bytes of memory.
    Processor board ID FGL1649T00U
    PowerPCElvis CPU at 262Mhz, revision number 0x0950
    Last reset from reload
    LWAPP image version 3.0.51.0
    1 FastEthernet interface
    32K bytes of flash-simulated non-volatile configuration memory.
    Base ethernet MAC Address: E4:D3:F1:C2:88:82
    Part Number                          : 73-8960-09
    PCA Assembly Number                  : 800-24963-06
    PCA Revision Number                  : B0
    PCB Serial Number                    : FOC16447J1K
    Top Assembly Part Number             : 800-28479-05
    Top Assembly Serial Number           : FGL1649T00U
    Top Revision Number                  : D0
    Product/Model Number                 : AIR-LAP1310G-E-K9R
    Press RETURN to get started!
    *Mar  1 00:00:04.329: %SYS-5-RESTART: System restarted --
    Cisco IOS Software, C1310 Software (C1310-RCVK9W8-M), Version 12.3(11)JX1, RELEASE SOFTWARE (fc1)
    Technical Support: http://www.cisco.com/techsupport
    Copyright (c) 1986-2006 by Cisco Systems, Inc.
    Compiled Mon 17-Jul-06 11:45 by alnguyen
    *Mar  1 00:00:05.289: %LINK-3-UPDOWN: Interface FastEthernet0, changed state to up
    *Mar  1 00:00:06.289: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0, changed state to up
    *Mar  1 00:00:23.337: %LWAPP-5-CHANGED: LWAPP changed state to DISCOVERY
    *Mar  1 00:00:33.352: %DHCP-6-ADDRESS_ASSIGN: Interface FastEthernet0 assigned DHCP address 10.114.36.28, mask 255.255.255.0, hostname APe4d3.f1c2.8882
    examining image...
    *Mar  1 00:00:44.783: %LWAPP-5-CHANGED: LWAPP changed state to JOIN
    *Jan 11 15:21:37.189: %LWAPP-5-CHANGED: LWAPP changed state to IMAGE
    %Error opening  (Protocol error)archive download: takes 6 seconds
    *Jan 11 15:21:43.189: LWAPP_CLIENT_ERROR_DEBUG:  Retransmission count for packet exceeded more than max(IMAGE_DATA
    , 1)
    *Jan 11 15:21:43.189: %LWAPP-5-CHANGED: LWAPP changed state to DISCOVERY
    *Jan 11 15:21:43.189: %LWAPP-5-CHANGED: LWAPP changed state to DISCOVERY
    *Jan 11 15:21:43.192: LWAPP_CLIENT_ERROR: not receive read response(3)
    *Jan 11 15:21:43.195: lwapp_image_proc: unable to open tar file
    *Jan 11 15:21:43.210: %SYS-5-RELOAD: Reload requested by lwapp image download proc. Reload Reason: Reason unspecified.
    *Jan 11 15:21:43.210: %LWAPP-5-CHANGED: LWAPP changed state to DOWN
    *Jan 11 15:21:43.216: %LWAPP-5-CHANGED: LWAPP changed state to DISCOVERYXmodem file system is available.
    flashfs[0]: 3 files, 2 directories
    flashfs[0]: 0 orphaned files, 0 orphaned directories
    flashfs[0]: Total bytes: 7741440
    flashfs[0]: Bytes used: 1861632
    flashfs[0]: Bytes available: 5879808
    flashfs[0]: flashfs fsck took 14 seconds.
    Base ethernet MAC Address: e4:d3:f1:c2:88:82
    Initializing ethernet port 0...
    Reset ethernet port 0...
    Reset done!
    ethernet link up, 100 mbps, full-duplex
    Ethernet port 0 initialized: link is up
    Please Advise,
    Thanks in advanced,
    Ahmed,

    Dear Stefan,
    Many thanks for your kind reply,
    Please find the information below:
    Controller Summary
    Management IP Address
    10.114.44.131
    Service Port IP Address
    10.114.23.20
    Software Version
    7.2.111.3
    Field Recovery Image Version
    6.0.182.0
    System Name
    CIR906.WLC.5508
    Please Advise,
    Thanks,
    Ahmed,

  • Can anybody tell me how to connect aironet 1400 to wlc 5508 ??

    I try to deploy cisco wlc 5508 to wireless network that based on cisco aironet bridge 1400 seirese , but it dose not work !
    when i read the data sheet of the wlc 5508 i found that it is not support that type of bridges , is there anyway to connect aironet 1400 to wlc 5505 ?
    thanx 

    Duplicate posts. :P
    Go here: https://supportforums.cisco.com/discussion/12136581/can-anybody-tell-me-how-connect-aironet-1400-wlc-5508

  • WLC 5508 Flex connect

    Is there any separate licencse require for centralized WLC 5508 deployment?

    agree with Stephan.
    No need for addition license. just need to have number of AP license on WLC.
    Just for reference:
    H-Reap Design and Deployment Guide
    http://www.cisco.com/c/en/us/support/docs/wireless/5500-series-wireless-controllers/71250-h-reap-design-deploy.html
    H-REAP Modes of Operation Configuration Example
    http://www.cisco.com/c/en/us/support/docs/wireless-mobility/wireless-lan-wlan/81680-hreap-modes.html
    Regards

  • Converted 1140 AP can't join the WLC 5508

    Hello! Please, help me to sort my problem out.
    We have bought autonomous APs   AIR-AP1141N-E-K9 and converted them to the lightweight mode, but they cannot join the WLC 5508. The errors are below. There were NO problems with the LAPs that were bought before, together with the WLC.
    AP's IP: 172.22.90.27   IOS version  12.4
    WLC's IP: 172.22.90.20   IOS version 6.0.188.0
    ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
    This Discussion has been converted into document:- https://supportforums.cisco.com/docs/DOC-23054
    +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
    logs from the AP:
    Translating "CISCO-LWAPP-CONTROLLER"...domain server (255.255.255.255)
    *Oct 13 21:37:06.044: %CAPWAP-5-CHANGED: CAPWAP changed state to DISCOVERY
    *Oct 13 21:37:06.045: %CAPWAP-5-CHANGED: CAPWAP changed state to DISCOVERY
    *Oct 13 21:37:06.046: bsnInitRcbSlot: slot 1 has NO radio
    *Oct 13 21:37:06.056: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to a
    dministratively down
    *Oct 13 21:37:06.066: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to r
    eset
    *Oct 13 21:37:06.098: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to up
    Translating "CISCO-CAPWAP-CONTROLLER"...domain server (255.255.255.255)
    *Oct 13 21:37:15.060: %CAPWAP-3-ERRORLOG: Could Not resolve CISCO-LWAPP-CONTROLL
    ER
    *Oct 13 21:37:24.060: %CAPWAP-3-ERRORLOG: Could Not resolve CISCO-CAPWAP-CONTROL
    LER
    *Oct 13 21:37:34.060: %CAPWAP-3-ERRORLOG: Go join a capwap controller
    *Oct 13 21:38:34.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_i
    p: 172.22.90.20 peer_port: 5246
    *Oct 13 21:38:34.000: %CAPWAP-5-CHANGED: CAPWAP changed state to
    *Oct 13 21:38:34.822: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully
    peer_ip: 172.22.90.20 peer_port: 5246
    *Oct 13 21:38:34.823: %CAPWAP-5-SENDJOIN: sending Join Request to 172.22.90.20
    *Oct 13 21:38:34.823: %CAPWAP-5-CHANGED: CAPWAP changed state to JOIN
    *Oct 13 21:38:34.825: %CAPWAP-3-ERRORLOG: Unencrypted non-discovery CAPWAP Contr
    ol Message from 172.22.90.20
    *Oct 13 21:38:34.825: %CAPWAP-3-ERRORLOG: Invalid AC Message Type 4.
    *Oct 13 21:38:34.825: %CAPWAP-3-ERRORLOG: Failed to handle capwap control messag
    e from controller
    *Oct 13 21:38:39.823: %CAPWAP-5-SENDJOIN: sending Join Request to 172.22.90.20
    *Oct 13 21:38:39.823: %CAPWAP-3-ERRORLOG: Unencrypted non-discovery CAPWAP Contr
    ol Message from 172.22.90.20
    *Oct 13 21:38:39.823: %CAPWAP-3-ERRORLOG: Invalid AC Message Type 4.
    *Oct 13 21:38:39.823: %CAPWAP-3-ERRORLOG: Failed to handle capwap control messag
    e from controller
    *Oct 13 21:38:39.824: %CAPWAP-3-ERRORLOG: Failed to process unencrypted capwap p
    acket from 172.22.90.20
    *Oct 13 21:39:33.999: %DTLS-5-SEND_ALERT: Send WARNING : Close notify Alert to 1
    72.22.90.20:5246
    *Oct 13 21:39:34.000: %CAPWAP-3-ERRORLOG: Go join a capwap controller
    *Oct 13 21:38:34.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_i
    p: 172.22.90.20 peer_port: 5246
    *Oct 13 21:38:34.000: %CAPWAP-5-CHANGED: CAPWAP changed state to
    *Oct 13 21:38:34.001: %DTLS-5-PEER_DISCONNECT: Peer 172.22.90.20 has closed conn
    ection.
    *Oct 13 21:38:34.001: %DTLS-5-SEND_ALERT: Send WARNING : Close notify Alert to 1
    72.22.90.20:5246
    *Oct 13 21:38:34.001: %CAPWAP-3-ERRORLOG: Invalid event 38 & state 3 combination
    *Oct 13 21:38:34.125: %CAPWAP-3-ERRORLOG: Dropping dtls packet since session is
    not established.
    logs from the WLC:
    debug capwap events enable
    *Dec 21 15:02:06.244: 68:bc:0c:63:3d:a0 DTLS keys for Control Plane deleted successfully for AP 172.22.90.27
      *Dec 21 15:02:06.246: 68:bc:0c:63:3d:a0 DTLS connection closed event receivedserver (172:22:90:20/5246) client (172:22:90:27/21077)
    *Dec 21 15:02:06.246: 68:bc:0c:63:3d:a0 Entry exists for AP (172:22:90:27/21077)
    *Dec 21 15:02:06.246: 68:bc:0c:63:3d:a0 apfSpamProcessStateChangeInSpamContext: Deregister LWAPP event for AP 68:bc:0c:63:3d:a0 slot 0
    *Dec 21 15:02:06.246: 68:bc:0c:63:3d:a0 Deregister LWAPP event for AP 68:bc:0c:63:3d:a0 slot 0
    *Dec 21 15:02:06.246: 68:bc:0c:63:3d:a0 apfSpamProcessStateChangeInSpamContext: Deregister LWAPP event for AP 68:bc:0c:63:3d:a0 slot 1
    *Dec 21 15:02:06.246: 68:bc:0c:63:3d:a0 Deregister LWAPP event for AP 68:bc:0c:63:3d:a0 slot 1
    Ble
    *Dec 21 15:04:03.194: 68:bc:0c:63:3d:a0 capwap_ac_platform.c:1223 - Operation State 0 ===> 4
    *Dec 21 15:04:03.194: 68:bc:0c:63:3d:a0 Register LWAPP event for AP 68:bc:0c:63:3d:a0 slot 0
      *Dec 21 15:05:36.253: 68:bc:0c:63:3d:a0 Join Version: = 100711424
    *Dec 21 15:05:36.253: 68:bc:0c:63:3d:a0 Join resp: CAPWAP Maximum Msg element len = 93
    debug capwap errors enable
    *Dec 21 16:16:51.879: 68:bc:0c:63:3d:a0 DTLS connection was closed
    *Dec 21 16:17:09.940: 68:bc:0c:63:3d:a0 Join Priority Processing status = 0, Incoming Ap's Priority 1, MaxLrads = 12, joined Aps =5
    debug capwap detail enable
    *Dec 21 16:21:49.961: 68:bc:0c:63:3d:a0 CAPWAP Control Msg Received from 172.22.90.27:21078
    *Dec 21 16:21:49.961: 68:bc:0c:63:3d:a0 packet received of length 281 from 172.22.90.27:21078
    *Dec 21 16:21:49.961: 68:bc:0c:63:3d:a0 Msg Type = 3 Capwap state = 5
    *Dec 21 16:21:49.961: 68:bc:0c:63:3d:a0 Join resp: Result Code message element len = 8
    *Dec 21 16:21:49.961: 68:bc:0c:63:3d:a0 1. 47 0
    *Dec 21 16:21:49.961: 68:bc:0c:63:3d:a0 2. 232 3
    *Dec 21 16:21:49.961: 68:bc:0c:63:3d:a0 3. 6 0
    *Dec 21 16:21:49.961: 68:bc:0c:63:3d:a0 4. 12 0
    *Dec 21 16:21:49.961: 68:bc:0c:63:3d:a0 Join resp: AC Descriptor message element len = 48
    *Dec 21 16:21:49.961: 68:bc:0c:63:3d:a0 acName = Wi-Fi_Controller
    *Dec 21 16:21:49.961: 68:bc:0c:63:3d:a0 Join resp: AC Name message element len = 68
    *Dec 21 16:21:49.961: 68:bc:0c:63:3d:a0 Join resp: WTP Radio Information message element len = 77
    *Dec 21 16:21:49.961: 68:bc:0c:63:3d:a0 Join resp: CAPWAP Control IPV4 Address len = 87
    *Dec 21 16:21:49.961: 68:bc:0c:63:3d:a0 Sending encrypted packet to AP 172:22:90:27 (21078)
    *Dec 21 16:21:49.961: 68:bc:0c:63:3d:a0 Releasing WTP
    *Dec 21 16:24:12.212: 68:bc:0c:63:3d:a0 CAPWAP Control Msg Received from 172.22.90.27:21077
    *Dec 21 16:24:12.212: 68:bc:0c:63:3d:a0 DTLS connection 0x167c8b20 closed by controller
    *Dec 21 16:24:12.212: DTL Deleting AP 9 - 0.0.0.0
    *Dec 21 16:24:12.214: CAPWAP DTLS connection closed msg
    *Dec 21 16:24:12.216: 68:bc:0c:63:3d:a0 Sending LWAPP Event DeReg to 'mfpSendEventReport+168' for AP 68:bc:0c:63:3d:a0(0)
    *Dec 21 16:24:12.216: Received SPAM_MFP_RADIO_DOWN message
    *Dec 21 16:24:12.218: 68:bc:0c:63:3d:a0 Sending LWAPP Event DeReg to 'l2roamInit+560' for AP 68:bc:0c:63:3d:a0(0)
    *Dec 21 16:24:12.220: 68:bc:0c:63:3d:a0 Sending LWAPP Event DeReg to 'apfSpamCallbackInSpamContext+1224' for AP 68:bc:0c:63:3d:a0(0)
    *Dec 21 16:24:12.222: 68:bc:0c:63:3d:a0 Sending LWAPP Event DeReg to 'apfSpamSendBlackListTable+376' for AP 68:bc:0c:63:3d:a0(0)
    *Dec 21 16:24:12.224: 68:bc:0c:63:3d:a0 Sending LWAPP Event DeReg to 'rrmIappSendChdPacket+2320' for AP 68:bc:0c:63:3d:a0(0)
    *Dec 21 16:24:12.226: 68:bc:0c:63:3d:a0 Sending LWAPP Event DeReg to 'asTrackInitTask+19360' for AP 68:bc:0c:63:3d:a0(0)
    *Dec 21 16:24:12.228: 68:bc:0c:63:3d:a0 Sending LWAPP Event DeReg to 'mfpSendEventReport+168' for AP 68:bc:0c:63:3d:a0(1)
    *Dec 21 16:24:12.228: Received SPAM_MFP_RADIO_DOWN message
    *Dec 21 16:24:12.230: 68:bc:0c:63:3d:a0 Sending LWAPP Event DeReg to 'l2roamInit+560' for AP 68:bc:0c:63:3d:a0(1)
    *Dec 21 16:24:12.232: 68:bc:0c:63:3d:a0 Sending LWAPP Event DeReg to 'apfSpamCallbackInSpamContext+1224' for AP 68:bc:0c:63:3d:a0(1)
    *Dec 21 16:24:12.234: 68:bc:0c:63:3d:a0 Sending LWAPP Event DeReg to 'apfSpamSendBlackListTable+376' for AP 68:bc:0c:63:3d:a0(1)
    *Dec 21 16:24:12.236: 68:bc:0c:63:3d:a0 Sending LWAPP Event DeReg to 'rrmIappSendChdPacket+2320' for AP 68:bc:0c:63:3d:a0(1)
    *Dec 21 16:24:12.238: 68:bc:0c:63:3d:a0 Sending LWAPP Event DeReg to 'asTrackInitTask+19360' for AP 68:bc:0c:63:3d:a0(1)
    *Dec 21 16:24:12.238: 68:bc:0c:63:3d:a0 Deleting and removing AP 68:bc:0c:63:3d:a0 from fast path
    P.S. The time is set to the WLC with the NTP
    P.P.S. Don't lookup at the time the logs were made - they were made not during the same day/time

    I have solved this as soon as published my problem!!!
    the answer is published here:
    https://supportforums.cisco.com/thread/2004491
    especially in the post of Matthew Fowler
    Hi,
    Please take a look at CSCte01087.
    I see that your WLC is 10.0.13.5 and your AP is 10.0.13.28/24 so they are on the same subnet. I also see your AP MAC address does not begin with 00. This is why I believe it is relevant.
    Please try the workaround or open a TAC case if you need a fix.
    -Matt
    Symptom:
    An access point running 6.0.188.0 code may be unable to join a WLC5508.
    Messages similar to the following will be seen on the AP.
       %CAPWAP-3-ERRORLOG: Invalid AC Message Type 4.
       %CAPWAP-3-ERRORLOG: Unencrypted non-discovery CAPWAP Control Message
    Conditions:
    At least one of the following conditions pertains:
    - The high order byte of the AP's MAC address is nonzero, and the AP is in
    the same subnet as the WLC5508's management (or AP manager) interface
    - The WLC's management (or AP manager) interface's default gateway's
    MAC address' high order byte is nonzero.
    Workaround:
    If the MAC address of the WLC's default gateway does not begin with 00,
    and if all of the APs' MAC addresses begin with 00, then: you can put
    the APs into the same subnet as the WLC's management (or AP manager)
    interface.
    In the general case, for the situation where the WLC's default gateway's
    MAC does not begin with 00, you can address this by changing it to begin
    with 00. Some methods for doing this include:
    -- use the "mac-address" command on the gateway, to set a MAC address
    that begins with 00
    -- then enable HSRP on the gateway (standby ip ww.xx.yy.zz) and use this
    IP as the WLC's gateway.
    For the case where the APs' MAC addresses do not begin with 00, then make
    sure that they are *not* in the same subnet as the WLC's management
    (AP manager) interface, but are behind a router.
    Another workaround is to downgrade to 6.0.182.0.  However, after
    downgrading the WLC to 6.0.182.0, any APs that have 6.0.188.0 IOS
    (i.e. 12.4(21a)JA2) still installed on them will be unable to join.
    Therefore, after downgrading the WLC, the APs will need to have a
    pre-12.4(21a)JA2 rcvk9w8 or k9w8 image installed on them.
    different vlan!!!! yes! thank you Matthew Fowler sooooo much!!!!

  • Anchor mobility configuration getting lost in wlc 5508 ios code 7.4.100.0

    It is observed that in WLC 5508 , ios 7.4.100.0 ,  mobility anchor configuration on wlan  is getting lost .  we configure anchor ip address on  guest wlan > mobility anchor >  Switch IP Address (Anchor).
    We have configured the template on NCS 2.0 to push the anchor mobility ip address on all WLC
    Has anyone oberved this behavoiur. We have more than 100 WLC  , and  everyweek  mobility anchor configuration is lost on some WLC having code  7.4.100.0.

    I am having this exact same problem.  I am running 7.3 on 5508 WLC.   My remote site LAP's are using Flex (HREAP).  The initial access point that my laptop associates to connects with no problem, as soon as I wander out of range of the initial LAP and into the area of another access point, I lose data connectivity.   The was validated like the original post as I start a constant ping on the LAN and watch as the ping latency increases and then ping replies stop.  The only way to correct the problem is resetting of the wireless adapter on the laptop.  Side note my DroidX has no problem wandering from AP to AP.
    Laptop: Windows 7 32bit
    I then returned to my home site and test where I have a secondary controller and the LAP's are configured for local mode, no problems roaming from access point to access point.   Validated with constant ping test.  The pings drop for a second and re-
    continues as the laptop reconnects.
    **Edit: I am going to try the removing the DHCP Addr. Assignment required option, and report that back to the TAC engineer.
    Message was edited by: Michael Dunki-Jacobs
    **Edit Solved:***
    The problem is in deed solved by turning the "DHCP Address Required" but why?

Maybe you are looking for