WLC 5508 - Clients disconnecting

I am running WLC 5508 7.2.111.3 with some 2602i AP.
Last week one user reported his new macbook pro 2013 was encountering connectivity issues.His older macbook pro 2009 was working perfectly.
The user is sitting in the middle of 2nd floor having equal distance from second's floor access points.
The problem is that his Macbook pro 2013 was persistently trying to associate with 3rd's floor Access Points. Whatever i tried to do (deauthenticate user,rebooting 2nd & 3rd floor APs) the connection was persistent to 3rd floor Access Point. Even when i tried to install an Access Point in the user's office his Macbook Pro 2013 refused (!!!) to leave 3rd's floor Access Points.However his Macbook pro 2009 was always connected to the nearest Access Point (either to 2nd floor Access Points or to the newly installed access point in his office).
This week i had two visitors in 4th floor reporting that their Laptops (Sony Vaio) were doing very slow with the wireless.
When i tried to troubleshoot i found in the controller that their laptops were associating with 4th floor Access Points and after a minute they were disconnected and trying to associate to Ground Floor (!) Access Points. Of course they couldn't establish a connection and then associated again with 4th floor access points and after a while disconnected and trying to associate to Ground Floor Access Points
I tried to debug client with Sony Vaio and saw in the controller the following message
*apfMsConnTask_7: Mar 24 10:42:15.473: %APF-4-INVALID_ACTION_CATEGORY: apf_wme_utils.c:5481 Could not process 802.11 Action. Received Action frame with invalid category field(not supported by controller) from client. Mobile:*********, Category:7.
I also see a lot of these messages for other clients.
*apfMsConnTask_3: Mar 19 12:03:54.243: %APF-4-ASSOCREQ_PROC_FAILED: apf_80211.c:5275 Failed to process an association request from c8:6f:1d:24:0e:7d. WLAN:5, SSID:************. mobile in database timed out.
Am i hitting any bug similar or equal to CSCue53980?

have you tried with open authentication ( no security ) ? Check if client is able to associate then

Similar Messages

WLC 5508 : session disconnected when one lag-port is down.

Hello,
I have a WLC 5508 ( version 6.0.182).
When the port1 and port2 are connected ( The switch is configured with a etherchannel in forced mode) everything works fine: There is traffic on the 2 ports.
When I disconnect one of the 2 ports, I can still ping outside with my PC client, but all my tcp sesssions goes down and I even cannot restart my session. The only way I found is to do a "Disconnect / Reconnect" on my PC wireless connection.
Do you know this probleme ?
Is it a way to avoid it ?
Michel Misonne

CSCth12513 LAG fail-over does not work on CT5508
This bug is fixed in the special release available through TAC : 6.0.199.157 and 7.0.xxxx
Hope this helps.
Nicolas
===
Dont' forget to rate answers that you find useful

Repeated wlc 5508 client web authentication

I'm trying to troubleshoot a situation where many of our guest wireless users are repeatedly being prompted to reauthenticate via the web interface. the session timeout is set to 4 hours, however, many times a client is presented with a web authentication screen right in the middle of browsing at random times.
I do have several system log entries, but cannot find the specific entries in the Error code reference for the WLC. For example, I don't find anything on %AAA-3-VALIDATE_GUEST_SESSION_FAILED: file_db.c:4022 Guest user session validation failed for guest1. Index provided is out of range..
I'm running a WLC 5508 with 7.0.98.0 and have read through all of the release notes, error code references, etc., and don't see anything regarding this issue.
The WCS screenshot shows a good example of how often this occurs! Is the client actually re-associating with the AP (which in turn would require a web reauth)? Not sure if I'm barking up the wrong tree - focusing on web auth when I may actually need to be focusing on AP association...
I do have a TAC case opened up, but was wondering if anyone has experienced this before?
Sorry for the rambling...

Rene,
I did several things and at least one of them seemed to resolve the issue:
These notes are directly from my TAC case and I will try to provide a little more information [in brackets].
1.       Upgrade WLC to 7.0.98.218 [self explanatory]
2.       Upgrade WCS to 7.0.172.0 [current version, as of this note]
3.       Increase DHCP scope time on ASA from default (30 minutes) to 4
days [DHCP running external from the WLC]
4.       Remove TKIP from the WLAN - only allow AES [had both configured but tech advised to only use AES]
5.       Increased session timeout from 14400 seconds to 64800 seconds
(4 hours to 18 hours) [don't think this helped resolve the issue, but it certainly was more convenient for our longer-term guests]
I think that the TKIP and/or DHCP setting was integral as part of the resolution. I upgraded the WLC because the version that I was running didn't have the web-auth debug option, so I'm not sure that that actually contributed to the resolution.
Good Luck,
Rob.

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.

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 , AP client dhcp address different from WLAN interface VLAN subnet?

Hope the title makes sense, here's my situation: I have multiple businesses on 1 WLC 5508, there's a LAG to my core switch with seperate interfaces for each, broken up by vlans.
My question is: if i have a WLAN setup to use interface "Company A" which is vlan 10 with an ip of 10.0.1.5 which then points to 10.0.1.10 for dhcp.
Can the WLAN client connecting to the Company A WLAN use an IP in a different IP range?(192.168.1.10?) can the wlc route? from the perspective of the DHCP server where doers the request come from? (10.0.1.5?)
Can the DHCP server 10.0.10.10 on vlan 10 respond back with and ip on a different subnet to assign to the client to use and still be fully fonctioning? would the default gateway for the client need to be 10.0.1.5? So the clients ip would be 192.168.1.10 /24 with a gateway of 10.0.1.5 (ip adress fo vlan10 interface on WLC) And if multiple clients on the same subnet wanted to talk to each other woudl the WLC know how to route them to each other without passing through the default gateway?
Sorry if this is confusing I'm having a bit of a hard time explaining it in works, i can try and draw somethign up if it makes more sense.
thanks
Eric

I think if you want these clients to stick to a WLAN configured on a VLAN that has a different IP addressing you could configure your VLAN with the normal IP addressing then add on the SVI the 2nd IP_Class_default_gateway.
E.G.
Vlan 10
interface vlan 10
ip address 10.0.10.1 255.255.255.0
ip address 192.168.1.1 255.255.255.0 secondary
Clients that receive IP address from 192.168.1.0/24 network will be able to reach 192.168.1.1 and all traffic will pass right.

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)

AP disconnected from WLC 5508

Dear All,
Greetings!!!!!
We have WLC 5508 installed in our premises to which 80 1242AG APs are connected. Few days ago, all the APs all of a sudden disconnected from Controller and rejoined after 12 to 15 hours. when we try to investigate, there was regulatory domain conflict occur. But we didn't understand that those APs were configured with the same config before. How come they got diconnected and now rejoined without changing any configration in WLC?
Logs for both AP and WLC has been attahched here.
Kindly guide us!!!

Then the APs should of not of disassociated from the WLC. If all these APs are local to where the WLC resides, then I really don't know why the APs would of disassociated. Take a look at the monitor tab and then look at statistics and then ap join. There should be a history unless the WLC was rebooted or the log was cleared. The only other thing I could think of is if there was a duplicate address on a device that had the same IP address as the management interface of the WLC.
Sent from Cisco Technical Support iPhone App

Problem Concurent client WLC 5508

Hi All support,
i have running cisco wlc 5508 with software upgrade 7-4-100-0.aes and 24 cisco 1552 AP with mode mesh, concurent client only show 185 clients but if we using dual load wlc ( Whitout mobility group, if using mobility group clients still stuck concurent) clients can get online 150 on wlc01 and 130 on wlc02 ,total client we have is 300 client.for more information we using feature passive client on this network. any body can help ??
regards,
Sigit H.W

this is debug iapp :
*iappSocketTask: Mar 18 11:13:09.419:      [0480] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
*iappSocketTask: Mar 18 11:13:09.419:      [0496] 00 00 00 00 00 27 22 16 13 f9 00 00 00 00 00 00
*iappSocketTask: Mar 18 11:13:09.420:      [0512] 00 00 00 02 00 00 00 00 00 00 01 46 b8 17 01 00
*iappSocketTask: Mar 18 11:13:09.420:      [0528] 00 00 00 24 00 00 00 00 00 00 00 00 00 00 00 00
*iappSocketTask: Mar 18 11:13:09.420:      [0544] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
*iappSocketTask: Mar 18 11:13:09.420:      [0560] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
*iappSocketTask: Mar 18 11:13:09.420:      [0576] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
*iappSocketTask: Mar 18 11:13:09.420:      [0592] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
*iappSocketTask: Mar 18 11:13:09.420:      [0608] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
*iappSocketTask: Mar 18 11:13:09.420:      [0624] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
*iappSocketTask: Mar 18 11:13:09.420:      [0640] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
*iappSocketTask: Mar 18 11:13:09.420:      [0656] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
*iappSocketTask: Mar 18 11:13:09.420:      [0672] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
*iappSocketTask: Mar 18 11:13:09.420:      [0688] 00 00 27 22 40 a8 81 00 00 00 00 00 00 00 00 00
*iappSocketTask: Mar 18 11:13:09.420:      [0704] 01 00 00 00 00 00 00 00 a8 b9 19 01 00 00 00 00
*iappSocketTask: Mar 18 11:13:09.420:      [0720] 24 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
*iappSocketTask: Mar 18 11:13:09.420:      [0736] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
*iappSocketTask: Mar 18 11:13:09.420:      [0752] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
*iappSocketTask: Mar 18 11:13:09.420:      [0768] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
*iappSocketTask: Mar 18 11:13:10.785: IAPP Rx Frame (1633)
*iappSocketTask: Mar 18 11:13:10.785:      [0000] d0 c2 82 e3 ae c4 2c 36 f8 73 e6 80 81 00 00 0b
*iappSocketTask: Mar 18 11:13:10.785:      [0016] 08 00 45 00 05 cc d3 da 40 00 ff 11 28 8a 0a 9d
*iappSocketTask: Mar 18 11:13:10.785:      [0032] 32 6d 0a 9d 32 15 3e 69 14 7f 05 b8 00 00 00 20
*iappSocketTask: Mar 18 11:13:10.785:      [0048] 03 20 bb 9f 00 00 01 04 00 00 00 00 00 00 01 08
*iappSocketTask: Mar 18 11:13:10.785:      [0064] 00 00 2c 36 f8 73 e6 80 2c 36 f8 73 e6 80 2c 36
*iappSocketTask: Mar 18 11:13:10.785:      [0080] f8 73 e6 80 00 00 aa aa 03 00 40 96 00 00 06 03
*iappSocketTask: Mar 18 11:13:10.785:      [0096] 32 8b 2c 36 f8 73 e6 80 2c 36 f8 73 e6 80 00 00
*iappSocketTask: Mar 18 11:13:10.785:      [0112] 39 00 05 ed e1 cf 0a 30 08 00 00 27 22 40 a4 df
*iappSocketTask: Mar 18 11:13:10.785:      [0128] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
*iappSocketTask: Mar 18 11:13:10.786:      [0144] 00 00 a0 05 00 00 00 00 00 0c 00 00 00 00 00 00
*iappSocketTask: Mar 18 11:13:10.786:      [0160] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
*iappSocketTask: Mar 18 11:13:10.786:      [0176] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
*iappSocketTask: Mar 18 11:13:10.786:      [0192] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
*iappSocketTask: Mar 18 11:13:10.786:      [0208] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
*iappSocketTask: Mar 18 11:13:10.786:      [0224] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
*iappSocketTask: Mar 18 11:13:10.786:      [0240] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
*iappSocketTask: Mar 18 11:13:10.786:      [0256] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
*iappSocketTask: Mar 18 11:13:10.786:      [0272] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
*iappSocketTask: Mar 18 11:13:10.786:      [0288] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
*iappSocketTask: Mar 18 11:13:10.786:      [0304] 00 00 00 00 00 00 00 00 27 22 84 89 30 00 00 00
*iappSocketTask: Mar 18 11:13:10.786:      [0320] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 a3
*iappSocketTask: Mar 18 11:13:10.786:      [0336] 06 00 00 00 00 00 18 00 00 00 00 00 00 00 00 00
*iappSocketTask: Mar 18 11:13:10.786:      [0352] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
*iappSocketTask: Mar 18 11:13:10.786:      [0368] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
*iappSocketTask: Mar 18 11:13:10.786:      [0384] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
*iappSocketTask: Mar 18 11:13:10.786:      [0400] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
*iappSocketTask: Mar 18 11:13:10.786:      [0416] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
*iappSocketTask: Mar 18 11:13:10.786:      [0432] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
*iappSocketTask: Mar 18 11:13:10.786:      [0448] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
*iappSocketTask: Mar 18 11:13:10.786:      [0464] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
*iappSocketTask: Mar 18 11:13:10.786:      [0480] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
*iappSocketTask: Mar 18 11:13:10.786:      [0496] 00 00 00 00 00 27 22 40 a8 57 00 00 00 00 00 00
*iappSocketTask: Mar 18 11:13:10.786:      [0512] 00 00 00 00 00 00 00 00 00 00 00 00 aa 0d 01 00
*iappSocketTask: Mar 18 11:13:10.786:      [0528] 00 00 00 18 00 00 00 00 00 00 00 00 00 00 00 00
*iappSocketTask: Mar 18 11:13:10.786:      [0544] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
*iappSocketTask: Mar 18 11:13:10.786:      [0560] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
*iappSocketTask: Mar 18 11:13:10.786:      [0576] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
*iappSocketTask: Mar 18 11:13:10.786:      [0592] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
*iappSocketTask: Mar 18 11:13:10.786:      [0608] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
*iappSocketTask: Mar 18 11:13:10.786:      [0624] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
*iappSocketTask: Mar 18 11:13:10.786:      [0640] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
*iappSocketTask: Mar 18 11:13:10.786:      [0656] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
*iappSocketTask: Mar 18 11:13:10.786:      [0672] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
*iappSocketTask: Mar 18 11:13:10.786:      [0688] 00 00 27 22 2c a9 c6 00 00 00 00 00 00 00 00 00
*iappSocketTask: Mar 18 11:13:10.786:      [0704] 00 00 00 00 00 00 00 00 00 a2 06 00 00 00 00 00
*iappSocketTask: Mar 18 11:13:10.786:      [0720] 0c 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
*iappSocketTask: Mar 18 11:13:10.786:      [0736] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
*iappSocketTask: Mar 18 11:13:10.786:      [0752] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
*iappSocketTask: Mar 18 11:13:10.786:      [0768] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
*iappSocketTask: Mar 18 11:13:12.554: IAPP Rx Frame (1633)
*iappSocketTask: Mar 18 11:13:12.554:      [0000] d0 c2 82 e3 ae c4 2c 36 f8 73 04 20 81 00 00 0b
*iappSocketTask: Mar 18 11:13:12.554:      [0016] 08 00 45 00 05 cc 00 50 40 00 ff 11 fc 17 0a 9d
*iappSocketTask: Mar 18 11:13:12.554:      [0032] 32 6a 0a 9d 32 15 30 44 14 7f 05 b8 00 00 00 20
*iappSocketTask: Mar 18 11:13:12.554:      [0048] 03 20 bb fa 00 00 01 04 00 00 00 00 00 00 01 08
*iappSocketTask: Mar 18 11:13:12.554:      [0064] 00 00 2c 36 f8 73 04 20 2c 36 f8 73 04 20 2c 36
*iappSocketTask: Mar 18 11:13:12.554:      [0080] f8 73 04 20 00 00 aa aa 03 00 40 96 00 00 06 03
*iappSocketTask: Mar 18 11:13:12.554:      [0096] 32 8b 2c 36 f8 73 04 20 2c 36 f8 73 04 20 00 00
*iappSocketTask: Mar 18 11:13:12.554:      [0112] 39 00 05 ed 00 00 0a 30 08 00 00 27 22 40 a8 f0
*iappSocketTask: Mar 18 11:13:12.554:      [0128] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
*iappSocketTask: Mar 18 11:13:12.554:      [0144] 00 00 b0 14 01 00 00 00 00 12 00 00 00 00 00 00
*iappSocketTask: Mar 18 11:13:12.554:      [0160] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
*iappSocketTask: Mar 18 11:13:12.554:      [0176] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
*iappSocketTask: Mar 18 11:13:12.554:      [0192] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
*iappSocketTask: Mar 18 11:13:12.554:      [0208] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
*iappSocketTask: Mar 18 11:13:12.554:      [0224] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
*iappSocketTask: Mar 18 11:13:12.554:      [0240] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
*iappSocketTask: Mar 18 11:13:12.554:      [0256] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
*iappSocketTask: Mar 18 11:13:12.554:      [0272] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
*iappSocketTask: Mar 18 11:13:12.554:      [0288] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
*iappSocketTask: Mar 18 11:13:12.554:      [0304] 00 00 00 00 00 00 00 00 27 22 16 a3 f7 00 00 00
*iappSocketTask: Mar 18 11:13:12.554:      [0320] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ad
*iappSocketTask: Mar 18 11:13:12.554:      [0336] 10 01 00 00 00 00 24 00 00 00 00 00 00 00 00 00
*iappSocketTask: Mar 18 11:13:12.554:      [0352] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
*iappSocketTask: Mar 18 11:13:12.554:      [0368] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
*iappSocketTask: Mar 18 11:13:12.554:      [0384] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
*iappSocketTask: Mar 18 11:13:12.554:      [0400] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
*iappSocketTask: Mar 18 11:13:12.554:      [0416] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
*iappSocketTask: Mar 18 11:13:12.554:      [0432] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
*iappSocketTask: Mar 18 11:13:12.554:      [0448] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
*iappSocketTask: Mar 18 11:13:12.554:      [0464] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
*iappSocketTask: Mar 18 11:13:12.554:      [0480] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
*iappSocketTask: Mar 18 11:13:12.554:      [0496] 00 00 00 00 00 27 22 40 a9 37 00 00 00 00 00 00
*iappSocketTask: Mar 18 11:13:12.554:      [0512] 00 00 00 00 00 00 00 00 00 00 00 00 b1 13 01 00
*iappSocketTask: Mar 18 11:13:12.554:      [0528] 00 00 00 24 00 00 00 00 00 00 00 00 00 00 00 00
*iappSocketTask: Mar 18 11:13:12.554:      [0544] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
*iappSocketTask: Mar 18 11:13:12.554:      [0560] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
*iappSocketTask: Mar 18 11:13:12.554:      [0576] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
*iappSocketTask: Mar 18 11:13:12.554:      [0592] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
*iappSocketTask: Mar 18 11:13:12.554:      [0608] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
*iappSocketTask: Mar 18 11:13:12.554:      [0624] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
*iappSocketTask: Mar 18 11:13:12.554:      [0640] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
*iappSocketTask: Mar 18 11:13:12.554:      [0656] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
*iappSocketTask: Mar 18 11:13:12.554:      [0672] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
*iappSocketTask: Mar 18 11:13:12.554:      [0688] 00 00 27 22 40 a9 fd 00 00 00 00 00 00 00 00 00
*iappSocketTask: Mar 18 11:13:12.554:      [0704] 00 00 00 00 00 00 00 00 00 b2 16 01 00 00 00 00
*iappSocketTask: Mar 18 11:13:12.554:      [0720] 18 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
*iappSocketTask: Mar 18 11:13:12.554:      [0736] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
*iappSocketTask: Mar 18 11:13:12.554:      [0752] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
*iappSocketTask: Mar 18 11:13:12.554:      [0768] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
(Cisco Controller) >debug iapp all disable

WLC 5508 Internal DHCP server issues

Hi,
I am hoping to get your feedback around the dhcp issues I am facing with Two Centrally Switched Wireless LANs. I have tried to explain the setup and the problems below and would appreciate it if anyone can suggest a solution for the problems I am facing:
The setup is as follows:
- I have a WLC 5508 which has been configured with 4 SSIDs, out of which 2 are using Central Authentication and Switching.
- I have an LWAP connected to the WLC in HREAP mode.
- WLC is configured as the DHCP server for clients connecting to the SSID 'Guest'. For the rest, I am using external dhcp server.
- Only one scope for Guest Interface is setup on the WLC.
Problems:
1. As far as I know, for WLC to act as internal dhcp server, it is mandatory to have the proxy enabled, but the Clients connecting to SSID 'Internet' are
unable to get an ip address from the external dhcp server, if dhcp proxy is enabled on the WLC. If i disable the proxy, it all works fine.
2. DHCP does not release the ip addresses assigned to clients even after they are logged out.
3. If a machine which was earlier connected to 'Guest' SSID connects to the 'Internet' SSID, it requests the same ip it was assigned by the WLC which it was assigned under 'Guest', but gets tagged with the Vlan configured on the management interface.
************Output from the Controller********************
(Cisco Controller) >show sysinfo
Manufacturer's Name.............................. Cisco Systems Inc.
Product Name..................................... Cisco Controller
Product Version.................................. 7.0.116.0
Bootloader Version............................... 1.0.1
Field Recovery Image Version..................... 6.0.182.0
Firmware Version................................. FPGA 1.3, Env 1.6, USB console 1.27
Build Type....................................... DATA + WPS + LDPE
(Cisco Controller) >show interface summary
Interface Name                   Port Vlan Id IP Address         Type        Ap Mgr        Gu
est
guest                                        1    301      10.255.255.30    Dynamic   No              No
management                          1    100      172.17.1.30        Static          Yes            No
service-port                              N/A N/A      192.168.0.1       Static         No               No
virtual                                        N/A   N/A      10.0.0.1              Static         No               No
(Cisco Controller) >show wlan summary
Number of WLANs.................................. 4
WLAN ID WLAN Profile Name / SSID               Status    Interface Name
1        LAN                                    Enabled   management
2        Internet                               Enabled   management
3        Managment Assets          Enabled   management
4        Guest                                  Enabled   guest
(Cisco Controller) >show dhcp detailed guest
Scope: guest
Enabled.......................................... Yes
Lease Time....................................... 86400 (1 day )
Pool Start....................................... 10.255.255.31
Pool End......................................... 10.255.255.254
Network.......................................... 10.255.255.0
Netmask.......................................... 255.255.255.0
Default Routers.................................. 10.255.255.1 0.0.0.0 0.0.0.0
DNS Domain.......................................
DNS.............................................. 8.8.8.8 8.8.4.4 0.0.0.0
Netbios Name Servers............................. 0.0.0.0 0.0.0.0 0.0.0.0
(Cisco Controller) >show interface detailed management
Interface Name................................... management
MAC Address...................................... e8:b7:48:9b:84:20
IP Address....................................... 172.17.1.30
IP Netmask....................................... 255.255.255.0
IP Gateway....................................... 172.17.1.1
External NAT IP State............................ Disabled
External NAT IP Address.......................... 0.0.0.0
VLAN............................................. 100
Quarantine-vlan.................................. 0
Active Physical Port............................. 1
Primary Physical Port............................ 1
Backup Physical Port............................. Unconfigured
Primary DHCP Server.............................. 172.30.50.1
Secondary DHCP Server............................ Unconfigured
DHCP Option 82................................... Disabled
ACL.............................................. Unconfigured
AP Manager....................................... Yes
Guest Interface.................................. No
L2 Multicast..................................... Enabled
(Cisco Controller) >show interface detailed guest
Interface Name................................... guest
MAC Address...................................... e8:b7:48:9b:84:24
IP Address....................................... 10.255.255.30
IP Netmask....................................... 255.255.255.0
IP Gateway....................................... 10.255.255.1
External NAT IP State............................ Disabled
External NAT IP Address.......................... 0.0.0.0
VLAN............................................. 301
Quarantine-vlan.................................. 0
Active Physical Port............................. 1
Primary Physical Port............................ 1
Backup Physical Port............................. Unconfigured
Primary DHCP Server.............................. Unconfigured
Secondary DHCP Server............................ Unconfigured
DHCP Option 82................................... Disabled
ACL.............................................. Unconfigured
AP Manager....................................... No
Guest Interface.................................. No
L2 Multicast..................................... Enabled
(Cisco Controller) >show dhcp leases
       MAC                IP         Lease Time Remaining
00:21:6a:9c:03:04    10.255.255.46    23 hours 52 minutes 42 seconds        <<<<<<< lease remains even when the client is disconnected.
*********Example of Client connected to the right Vlan with an ip address from the incorrect interface. *************
(Cisco Controller) >show client detail 00:21:6a:9c:03:04
Client MAC Address............................... 00:21:6a:9c:03:04
Client Username ................................. N/A
AP MAC Address................................... a0:cf:5b:00:49:c0
AP Name.......................................... mel
Client State..................................... Associated
Client NAC OOB State............................. Access
Wireless LAN Id.................................. 2                 <<<<<<<<   'Internet' SSID
BSSID............................................ a0:cf:5b:00:49:ce
Connected For ................................... 319 secs
Channel.......................................... 36
IP Address....................................... 10.255.255.46      <<<<<<< IP address assigned from the 'Guest' Interface or dhcp scope on the WLC
Association Id................................... 1
Authentication Algorithm......................... Open System
Reason Code...................................... 1
Status Code...................................... 0
Session Timeout.................................. 1800
Client CCX version............................... 4
Client E2E version............................... 1
QoS Level........................................ Silver
802.1P Priority Tag.............................. disabled
WMM Support...................................... Enabled
Power Save....................................... OFF
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
H-REAP Data Switching............................ Central       <<<<<<<<<
H-REAP Authentication............................ Central       <<<<<<<<<<
Interface........................................ management
VLAN............................................. 100           <<<<<<<<<<< right Vlan
Quarantine VLAN.................................. 0
Access VLAN...................................... 100

Hi All,
I have a similar issue where Wireless clients are not receiving automatic addressing from an internal DHCP server. I have multiple interfaces configured on the WLC which are connected to separate VLANS. The manually specified DHCP primary server entry is the same on all interfaces. Some clients are able to authenticate and receive automatic IP configuration but some clients are failing the address assignment process. I have checked connectivity between the WLC and DHCP server, this is confirmed as working. When I carry out a "debug dhcp packet enable", I get the following outputs which seems as if the DHCP discover request from the client is skipped. Your thoughts and inputs on this are appreciated.
DHCP Socket Task: Nov 07 11:16:09.174: 00:22:fb:7b:37:32 DHCP option len (including the magic cookie) 76
*DHCP Socket Task: Nov 07 11:16:09.174: 00:22:fb:7b:37:32 DHCP option: message type = DHCP DISCOVER
*DHCP Socket Task: Nov 07 11:16:09.174: 00:22:fb:7b:37:32 DHCP option: 116 (len 1) - skipping
*DHCP Socket Task: Nov 07 11:16:09.174: 00:22:fb:7b:37:32 DHCP option: 61 (len 7) - skipping
*DHCP Socket Task: Nov 07 11:16:09.174: 00:22:fb:7b:37:32 DHCP option: requested ip = 169.254.223.5
*DHCP Socket Task: Nov 07 11:16:09.174: 00:22:fb:7b:37:32 DHCP option: 12 (len 13) - skipping
*DHCP Socket Task: Nov 07 11:16:09.174: 00:22:fb:7b:37:32 DHCP option: vendor class id = MSFT 5.0 (len 8)
*DHCP Socket Task: Nov 07 11:16:09.174: 00:22:fb:7b:37:32 DHCP option: 55 (len 11) - skipping
*DHCP Socket Task: Nov 07 11:16:09.174: 00:22:fb:7b:37:32 DHCP option: 43 (len 2) - skipping
*DHCP Socket Task: Nov 07 11:16:09.174: 00:22:fb:7b:37:32 DHCP options end, len 76, actual 68
*DHCP Socket Task: Nov 07 11:16:09.174: 00:22:fb:7b:37:32 DHCP Forwarding DHCP packet (332 octets) packet DHCP Socket Task: Nov 07 11:16:09.174: 00:22:fb:7b:37:32 DHCP option len (including the magic cookie) 76
Thanks,
Raj Sandhu

WLC 5508 8.0.100 AP dropout anf fallback issue

After WLC upgrade to 8.0.100 [ not in HA mode], the AP seem to be dropping out and reconnect using the fallback to IP- inspite of the statically configured IP on the AP
Running Outdoor mesh AIR-CAP1552E-N-K9 on WLC 5508
(Cisco Controller) >show boot
Primary Boot Image............................... 8.0.100.0 (default) (active)
Backup Boot Image................................ 7.6.101.2
=========
Last AP disconnect details
- Reason for last AP connection failure.................... The AP has been reset by the controller
- Last AP disconnect reason................................ Unknown failure reason
Last join error summary
- Type of error that occurred last......................... Lwapp join request rejected
- Reason for error that occurred last...................... No Mwar payload found in join request
- Time at which the last join error occurred............... Dec 03 00:05:26.114
AP disconnect details
- Reason for last AP connection failure.................... The AP has been reset by the controller

We downgraded the WLC to 7.4.121.0 and finally got rid of the DHCP problem
But encountered a new issue
The WGB once connected to the mesh AP does not reconnect to the network , auth failure- AIR-SAP1602E-Z-K9 running - ap1g2-k9w7-mx.152-2.JB2
Local EAP auth configured for WGB client on the WLC
Looks more like the WGB stuck in a state , unable to negotiate its credentials
Controller log
*dot1xMsgTask: Mar 24 10:33:52.737: #DOT1X-3-WPA_SEND_STATE_ERR: 1x_kxsm.c:1404 Unable to send EAPOL-key msg - invalid WPA state (0) - client f4:0f:1b:23:03:37
Attached is the debug and client status from WLC
Any idea what is going on
Thanks

An issue with WLC 5508 and 7921 phone

Hello all!
I have a system with WLC 5508 and some 1242 APs. And I use a lot of 7921 phones.
One of 7921 phones was in trouble. It loses registration, disconnect conversations...
I installed the trial WLC and run voice diagnostics.
I saw some of "Potentially degraded QoS in downlink direction because of incorrect packet classification" messages and one "Fair upstream packet loss ratio: 1,2%, which is less than threshold 2.5%"
As I understand all of 7921 phones in these area are affected.
what does it mean? I set up Platinum QoS for voice WLAN. I don't have any qos configuration string for AP and WLC ports on switches...
any ideas?
thanx in advance

Sergey:
There is one application called "WLC Config analyzer". You save your "show run-config" from your WLC in a text file and import it by this application. it will analyze the file for you and tell you what recommendations for voice are missing so you improve them.
When importing a config file you choose what voice clinets you are using, so you need to choose cisco 7921 to it tells you what config improvemetns is needed based on 7921 needs.
Here is the link to download the application:
https://supportforums.cisco.com/docs/DOC-1373
download the latest versoin.
BTW, how many voice/data clients are connected to one AP in that area? if I remember correctly if you are utilizing voice then the max number of clients connected to one AP should not exceed 17. If you have more than this number per AP try to minimize the number of users concurrently connected to the AP then try again.
Hope you'll find the config analyzer useful.
If useful please don't forget to rate.
Amjad

Wlc 5508 webauth subnet mask change issue

Recenly l changed the network subnet for a particular wlc interface and scope and also an upstream router and for some reason it would only allow me to use a /24 Host mask as my plan was to go to a /22 mask to allow for over 1000 hosts within this scope.
The Upstream Router which is a ( RV042 ) had the following original config :
     192.168.1.1
     255.255.255.0
I have noticed this device will not let me change the mask from a /24 to a /22 as you can only change from a pre-defined list of masks and you cannot manually add any either..
New Config
     10.10.0.10
     255.255.255.0
WLC 5508 Controller Interface
     Original Config
      192.168.1.25
     255.255.255.0
     192.168.1.1
     New Config
     10.10.0.25
     255.255.252.0
     Scope
     Range : 10.10.1.10 - 10.10.3.254
     Mask : 255.255.252.0
     Network : 10.0.0.0
     Router : 10.10.0.10
When l reconfigure to this addressing the wireless clients connect and get the new dhcp scope details but following this the webauth screen doesn't appear not allowing them to connect meaning there is no routing of traffic / internet access.
If l modify the above interface and scope masks back to a /24 - 255.255.255.0 the the wireless clients connect and webauth appears to prompt them to accept the terms and conditions and connect thus giving them internet access.
It looks like an issue with the mask ? The main reason l am trying to change the subnet addressing is because the standard /24 mask is not providing enough dhcp addresses and we have had times were the scope has been exhausted due to the public connecting and disconnecting as the lease perod of 2 hours holds onto the address before expiring meaning there is not enough available addresses for people to connect.
I would of thought that the upstream router ( RV042 ) even though it is only a /24 mask would still route the traffic coming from a WLC Controller interface with a /22 mask ?
Hopefully someone can suggest a solution ?
Thanks Simon

Hey Scott just getting back to this issue..   If for instance l can modify the wlc interface and Scope to have a /22 mask ( 1022 Hosts ) and my upstream Router ( Cisco RV042 ) can only provide a /24 or higher mask then does that mean l am still limited to a range of 254 hosts ( /24 Mask ) ? Would this mean l need to look into replacing my upstream Cisco RV042 VPN Router ?

IPad & 3502i WAP wlc 5508 H-REAP

I have a wierd situation occouring at a new remote location.
Here is my scheme.
At my phyiscal location =WHQ
wlc 5508 (7.0.98.0)
vlan 800
ssid KWD-Guest
open authentication
wep 48bit key
(ACL restricted to internet only access)
Remote physical location = 80NY
2821 router (12.4ios) - routes and dhcp for the locations networks.
3560-48 switch - user connections and WAP connections.
3502i WAP - H-REAP back to WHQ for management and configuration.
Remote physical location = 1441NY
3825 router (12.4ios) - routes and dhcp for the locations networks.
3560-48 switch - user connections and WAP connections.
1131AG WAP - H-REAP back to WHQ for management and configuration.
Here is the issue we are running into.
At 80NY the users want to connect to the guest vlan 800 ssid KWD-Guest with iPads and smart phones (model unknown).
They can see the ssid broadcasting. Try to connect to the ssid, input the wep key. wait, wait and time out on dhcp, giving themselves a 168.x.x.x addy
From the router side, I can see the dhcp request on the correct vlan hitting the correct dhcp pool.
The router hands out a valid ip address and associates it to the correct wireless devices Mac-Address
But as I said the client times out waiting for the dhcp address.
Now the kicker here is that the very same iPad and smart phone CAN connect to the guest ssid at 1441NY which is also hosted off the same 5508 at WHQ.
The only difference I see is the WAP model and the network addresses I hand out at each location.
To the best of my ability I have double checked my router/switch and controller/WAP configurations against each site to make sure there is a mirror in place.
Any ideas?
SR 617433573

dmantill,
Good morning and thank you for linking in the pdf.
I read it and hit several of the hyperlinks included in the pdf.
While I found the information useful and informative overall I did not really see anything that explained or covered the issue I am encountering.
I have a SR open now and the TAC engineer wants me to capture some debugs on the client mac. Once I can get the local tech onsite again we will perform the connection attempt with the debugging enabled.
FYI this is what the engineer wants to see.
Here is the information that I need to see when the problem occurs:
Disable/Disconnect the wireless client from the network – wait 1-2 mins
Open Telnet/SSH session to the WLC CLI - (Use Putty/SecureCRT with logging enabled)
type: Debug client
Turn the wireless device back on and let it authenticate/associate to the wireless network. Once the client experiences the problem, disable the debug process using the command:
debug disable-all
Filename: DebugClient.TXT

AIR-CAP1602I-E-K9 Not Talking to WLC 5508

hi all,
can't seem to get my APs to talk to WLC 5508.
can someone advise which WLC firmware to use and where can i get/download (link pls).
currently WLC is running 6.0.199.4.
Mar 1 00:00:47.839: %CDP_PD-4-POWER_OK: All radios disabled - NEGOTIATED inlin
e power source
*Mar 1 00:00:53.931: %CAPWAP-3-ERRORLOG: Not sending discovery request AP does
not have an Ip !!
*Mar 1 00:00:55.963: %DHCP-6-ADDRESS_ASSIGN: Interface BVI1 assigned DHCP addre
ss 172.28.159.15, mask 255.255.255.192, hostname APfc99.47a3.4d22
Translating "CISCO-CAPWAP-CONTROLLER"...domain server (255.255.255.255)
*Mar 1 00:01:06.899: %CAPWAP-3-ERRORLOG: Did not get log server settings from D
HCP.
*Mar 1 00:01:15.899: %CAPWAP-3-ERRORLOG: Could Not resolve CISCO-CAPWAP-CONTROL
LER
*Mar 1 00:01:15.899: %CAPWAP-3-ERRORLOG: Discovery response from MWAR 'Cisco_f8
:72:64'running version 6.0.199.4 is rejected.    <<<<
APfc99.47a3.4d22>sh ve
Cisco IOS Software, C1600 Software (AP1G2-RCVK9W8-M), Version 15.2(2)JB, RELEASE
SOFTWARE (fc1)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2012 by Cisco Systems, Inc.
Compiled Tue 11-Dec-12 04:52 by prod_rel_team
ROM: Bootstrap program is C1600 boot loader
BOOTLDR: C1600 Boot Loader (AP1G2-BOOT-M) LoaderVersion 15.2(2)JAX, RELEASE SOFT
WARE (fc1)
APfc99.47a3.4d22 uptime is 11 minutes
System returned to ROM by power-on
System image file is "flash:/ap1g2-rcvk9w8-mx/ap1g2-rcvk9w8-mx"
Last reload reason:
This product contains cryptographic features and is subject to United
States and local country laws governing import, export, transfer and
use. Delivery of Cisco cryptographic products does not imply
third-party authority to import, export, distribute or use encryption.
Importers, exporters, distributors and users are responsible for
compliance with U.S. and local country laws. By using this product you
agree to comply with applicable laws and regulations. If you are unable
to comply with U.S. and local laws, return this product immediately.
A summary of U.S. laws governing Cisco cryptographic products may be found at:
http://www.cisco.com/wwl/export/crypto/tool/stqrg.html
If you require further assistance please contact us by sending email to
[email protected].
cisco AIR-CAP1602I-E-K9    (PowerPC) processor (revision B0) with 98294K/32768K
bytes of memory.
Processor board ID FGL1726W6DQ
PowerPC CPU at 533Mhz, revision number 0x2151
Last reset from power-on
LWAPP image version 7.4.1.37
1 Gigabit Ethernet interface
32K bytes of flash-simulated non-volatile configuration memory.
Base ethernet MAC Address: FC:99:47:A3:4D:22
Part Number                          : 73-14671-04
PCA Assembly Number                  : 000-00000-00
PCA Revision Number                  :
PCB Serial Number                    : FOC17182J4J
Top Assembly Part Number             : 800-38552-01
Top Assembly Serial Number           : FGL1726W6DQ
Top Revision Number                  : A0
Product/Model Number                 : AIR-CAP1602I-E-K9
Configuration register is 0xF

Hi,
Date and time is ok on the WLC,
I configured Accept Self Signed Certificate (SSC) under Security / AP policy, once done the WLC recognized the AP, but output from the console of the AP power cycle the access point is:
IOS Bootloader - Starting system.
FLASH CHIP: Micronix MX25L256_35F
Xmodem file system is available.
flashfs[0]: 5 files, 2 directories
flashfs[0]: 0 orphaned files, 0 orphaned directories
flashfs[0]: Total bytes: 31936000
flashfs[0]: Bytes used: 6551040
flashfs[0]: Bytes available: 25384960
flashfs[0]: flashfs fsck took 9 seconds.
Reading cookie from SEEPROM
Base Ethernet MAC address: 4c:00:82:9a:47:a3
************* loopback_mode = 0
Loading "flash:/ap1g2-rcvk9w8-mx/ap1g2-rcvk9w8-mx"...####################
File "flash:/ap1g2-rcvk9w8-mx/ap1g2-rcvk9w8-mx" uncompressed and installed, entr
y point: 0x100000
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, C1600 Software (AP1G2-RCVK9W8-M), Version 15.2(2)JB, RELEASE
SOFTWARE (fc1)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2012 by Cisco Systems, Inc.
Compiled Tue 11-Dec-12 04:52 by prod_rel_team
Initializing flashfs...
FLASH CHIP: Micronix MX25L256_35F
flashfs[2]: 5 files, 2 directories
flashfs[2]: 0 orphaned files, 0 orphaned directories
flashfs[2]: Total bytes: 31808000
flashfs[2]: Bytes used: 6551040
flashfs[2]: Bytes available: 25256960
flashfs[2]: flashfs fsck took 9 seconds.
flashfs[2]: Initialization complete.
flashfs[3]: 0 files, 1 directories
flashfs[3]: 0 orphaned files, 0 orphaned directories
flashfs[3]: Total bytes: 11999232
flashfs[3]: Bytes used: 1024
flashfs[3]: Bytes available: 11998208
flashfs[3]: flashfs fsck took 1 seconds.
flashfs[3]: Initialization complete....done Initializing flashfs.
This product contains cryptographic features and is subject to United
States and local country laws governing import, export, transfer and
memory validate-checksum 30
^
% Invalid input detected at '^' marker.
no ip http server
       ^
% Invalid input detected at '^' marker.
use. Delivery of Cisco cryptographic products does not imply
third-party authority to import, export, distribute or use encryption.
Importers, exporters, distributors and users are responsible for
login authentication default
^
% Invalid input detected at '^' marker.
compliance with U.S. and local country laws. By using this product you
agree to comply with applicable laws and regulations. If you are unable
to comply with U.S. and local laws, return this product immediately.
A summary of U.S. laws governing Cisco cryptographic products may be found at:
http://www.cisco.com/wwl/export/crypto/tool/stqrg.html
If you require further assistance please contact us by sending email to
[email protected].
Warning: the compile-time code checksum does not appear to be present.
cisco AIR-CAP1602I-N-K9    (PowerPC) processor (revision B0) with 98294K/32768K
bytes of memory.
Processor board ID FGL1730S57A
PowerPC CPU at 533Mhz, revision number 0x2151
Last reset from power-on
LWAPP image version 7.4.1.37
1 Gigabit Ethernet interface
32K bytes of flash-simulated non-volatile configuration memory.
Base ethernet MAC Address: 4C:00:82:9A:47:A3
Part Number                          : 73-14671-04
PCA Assembly Number                  : 000-00000-00
PCA Revision Number                  :
PCB Serial Number                    : FOC17284HL9
Top Assembly Part Number             : 800-38552-01
Top Assembly Serial Number           : FGL1730S57A
Top Revision Number                  : A0
Product/Model Number                 : AIR-CAP1602I-N-K9
% Please define a domain-name first.
logging facility kern
        ^
% Invalid input detected at '^' marker.
logging trap emergencies
        ^
% Invalid input detected at '^' marker.
Press RETURN to get started!
*Mar 1 00:00:12.451: %LWAPP-3-CLIENTERRORLOG: Config load from flash failed. In
itialising Cfg
*Mar 1 00:00:13.683: %LINK-6-UPDOWN: Interface GigabitEthernet0, changed state
to up
*Mar 1 00:00:14.687: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEth
ernet0, changed state to up
*Mar 1 00:00:15.123: %SYS-5-RESTART: System restarted --
Cisco IOS Software, C1600 Software (AP1G2-RCVK9W8-M), Version 15.2(2)JB, RELEASE
SOFTWARE (fc1)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2012 by Cisco Systems, Inc.
Compiled Tue 11-Dec-12 04:52 by prod_rel_team
*Mar 1 00:00:15.151: %LWAPP-3-CLIENTERRORLOG: Config load from flash failed. In
itialising Cfg
*Mar 1 00:00:15.151: %CAPWAP-3-ERRORLOG: Failed to load configuration from flas
h. Resetting to default config
*Mar 1 00:00:16.195: %LINEPROTO-5-UPDOWN: Line protocol on Interface BVI1, chan
ged state to uplwapp_crypto_init: MIC Present and Parsed Successfully
no bridge-group 1 source-learning
                   ^
% Invalid input detected at '^' marker.
%Default route without gateway, if not a point-to-point interface, may impact pe
rformance
*Mar 1 00:00:48.695: %CDP_PD-4-POWER_OK: All radios disabled - INJECTOR_CONFIGU
RED_ON_SOURCE inline power source
*Mar 1 00:00:48.923: %DHCP-6-ADDRESS_ASSIGN: Interface BVI1 assigned DHCP addre
ss 10.2.3.100, mask 255.255.255.0, hostname AP4c00.829a.47a3
Translating "CISCO-CAPWAP-CONTROLLER.campeche.ecosur.mx"...domain server (10.2.3
.10) [OK]
*Mar 1 00:00:59.915: %CAPWAP-3-ERRORLOG: Did not get log server settings from D
HCP.
*Mar 1 00:00:59.919: %CAPWAP-3-ERRORLOG: Dropping dtls packet since session is
not established. A0203E6, 147E, A020364, A47B, 0
*Mar 1 00:01:09.915: %CAPWAP-3-ERRORLOG: Go join a capwap controller
*Jan 29 09:33:18.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_i
p: 10.2.3.230 peer_port: 5246
*Jan 29 09:33:18.535: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully
peer_ip: 10.2.3.230 peer_port: 5246
*Jan 29 09:33:18.535: %CAPWAP-5-SENDJOIN: sending Join Request to 10.2.3.230
*Jan 29 09:33:23.535: %CAPWAP-5-SENDJOIN: sending Join Request to 10.2.3.230
logging facility kern
        ^
% Invalid input detected at '^' marker.
logging trap emergencies
        ^
% Invalid input detected at '^' marker.
*Jan 29 09:34:17.999: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to 10.
2.3.230:5246
*Jan 29 09:34:17.999: %LWAPP-3-CLIENTERRORLOG: LWAPP LED Init: incorrect led sta
te 255
*Jan 29 09:34:17.999: %LWAPP-3-CLIENTERRORLOG: Config load from flash failed. In
itialising Cfg
*Jan 29 09:34:17.999: %CAPWAP-3-ERRORLOG: Failed to load configuration from flas
h. Resetting to default config
*Jan 29 09:34:28.015: %CAPWAP-3-ERRORLOG: Go join a capwap controller
*Jan 29 09:34:28.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_i
p: 10.2.3.230 peer_port: 5246
*Jan 29 09:34:28.535: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully
peer_ip: 10.2.3.230 peer_port: 5246
*Jan 29 09:34:28.535: %CAPWAP-5-SENDJOIN: sending Join Request to 10.2.3.230
*Jan 29 09:34:33.535: %CAPWAP-5-SENDJOIN: sending Join Request to 10.2.3.230
and debug command output enable CAPWAP events
(Cisco Controller) >debug capwap events enable
(Cisco Controller) >*spamApTask7: Jan 29 03:39:08.092: acDtlsPlumbControlPlaneKeys: lrad:10.2.3.100(42107) mwar:10.2.3.230(5246)
*spamApTask7: Jan 29 03:39:08.093: 4c:00:82:9a:47:a0 DTLS keys for Control Plane deleted successfully for AP 10.2.3.100
*spamApTask7: Jan 29 03:39:08.100: 4c:00:82:9a:47:a0 DTLS connection closed event receivedserver (10.2.3.230/5246) client (10.2.3.100/42107)
*spamApTask7: Jan 29 03:39:08.100: 4c:00:82:9a:47:a0 Entry exists for AP (10.2.3.100/42107)
*spamApTask7: Jan 29 03:39:08.100: 4c:00:82:9a:47:a0 No AP entry exist in temporary database for 10.2.3.100:42107
*spamApTask7: Jan 29 03:39:08.104: 4c:00:82:9a:47:a0 Discovery Request from 10.2.3.100:42107
*spamApTask7: Jan 29 03:39:08.104: 4c:00:82:9a:47:a0 Join Priority Processing status = 0, Incoming Ap's Priority 1, MaxLrads = 500, joined Aps =0
*spamApTask7: Jan 29 03:39:08.104: apModel:
*spamApTask7: Jan 29 03:39:08.104: apType = 38 apModel:
*spamApTask0: Jan 29 03:39:08.105: 4c:00:82:9a:47:a3 Received LWAPP DISCOVERY REQUEST to 6c:41:6a:5f:95:2f on port '13'
*spamApTask0: Jan 29 03:39:08.105: 4c:00:82:9a:47:a3 Discarding discovery request in LWAPP from AP supporting CAPWAP
*spamApTask7: Jan 29 03:39:08.105: 4c:00:82:9a:47:a0 Discovery Response sent to 10.2.3.100 port 42107
*spamApTask7: Jan 29 03:39:08.105: 4c:00:82:9a:47:a0 Discovery Response sent to 10.2.3.100:42107
*spamApTask7: Jan 29 03:39:08.105: 4c:00:82:9a:47:a0 Discovery Request from 10.2.3.100:42107
*spamApTask7: Jan 29 03:39:08.105: 4c:00:82:9a:47:a0 Join Priority Processing status = 0, Incoming Ap's Priority 1, MaxLrads = 500, joined Aps =0
*spamApTask7: Jan 29 03:39:08.105: apModel:
*spamApTask7: Jan 29 03:39:08.105: apType = 38 apModel:
*spamApTask7: Jan 29 03:39:08.105: 4c:00:82:9a:47:a0 Discovery Response sent to 10.2.3.100 port 42107
*spamApTask7: Jan 29 03:39:08.105: 4c:00:82:9a:47:a0 Discovery Response sent to 10.2.3.100:42107
*spamApTask7: Jan 29 03:39:08.105: 4c:00:82:9a:47:a0 Discovery Request from 10.2.3.100:42107
*spamApTask7: Jan 29 03:39:08.105: 4c:00:82:9a:47:a0 Join Priority Processing status = 0, Incoming Ap's Priority 1, MaxLrads = 500, joined Aps =0
*spamApTask7: Jan 29 03:39:08.105: apModel:
*spamApTask7: Jan 29 03:39:08.105: apType = 38 apModel:
*spamApTask7: Jan 29 03:39:08.106: 4c:00:82:9a:47:a0 Discovery Response sent to 10.2.3.100 port 42107
(Cisco Controller) >*spamApTask7: Jan 29 03:39:08.106: 4c:00:82:9a:47:a0 Discovery Response sent to 10.2.3.100:42107
*spamApTask7: Jan 29 03:39:18.104: 4c:00:82:9a:47:a3 DTLS connection not found, creating new connection for 10:2:3:100 (42107) 10:2:3:230 (5246)
*spamApTask7: Jan 29 03:39:18.638: acDtlsPlumbControlPlaneKeys: lrad:10.2.3.100(42107) mwar:10.2.3.230(5246)
*spamApTask7: Jan 29 03:39:18.638: 4c:00:82:9a:47:a3 Allocated index from main list, Index: 397
*spamApTask7: Jan 29 03:39:18.638: 4c:00:82:9a:47:a3 Using CipherSuite AES128-SHA
*spamApTask7: Jan 29 03:39:18.638: 4c:00:82:9a:47:a3 DTLS keys for Control Plane are plumbed successfully for AP 10.2.3.100. Index 398
*spamApTask6: Jan 29 03:39:18.638: 4c:00:82:9a:47:a3 DTLS Session established server (10.2.3.230:5246), client (10.2.3.100:42107)
*spamApTask6: Jan 29 03:39:18.638: 4c:00:82:9a:47:a3 Starting wait join timer for AP: 10.2.3.100:42107
*spamApTask7: Jan 29 03:39:23.636: 4c:00:82:9a:47:a0 Join Request from 10.2.3.100:42107
*spamApTask7: Jan 29 03:39:23.636: 4c:00:82:9a:47:a3 Deleting AP entry 10.2.3.100:42107 from temporary database.
*spamApTask7: Jan 29 03:39:23.637: 4c:00:82:9a:47:a0 MIC AP is not allowed to join by config
*spamApTask7: Jan 29 03:39:23.637: 4c:00:82:9a:47:a0 Join Request failed!

WLC 5508 - Clients disconnecting

Similar Messages

Maybe you are looking for