Are multiple trunks possible on a 5508 WLC version 7.0.116.0

To date I have only ever deployed guest WLCs with one bundled channel to a neigboring switch. With tunneled guest traffic flow via one vlan on the trunk (management) and leaving on the guest VLAN going physcily back to the same switch. Everything I have read indicated this is all that is supported.
However we have a requirement where the client would like to have two trunks connected to two different switches. So that tunneled guest traffic flow can come via one trunk and leave on the guest VLAN via another trunk going to another switch. Is this possible or are there any other methods I should try that may achieve a similar outcome with physical segragation?

This is not possible ... if you LAG the links. But if you un-LAG it maybe you can. I haven't tried it.
So that tunneled guest traffic flow can come via one trunk and leave on the guest VLAN via another trunk going to another switch. This sounds "awful" (for the lack of a better PG-13 word).

Similar Messages

Disabling 802.11 b clients on a 5508 WLC version 7.0.116.0

Hi,
We have a rquirment to disable WLAN access to B clients. I believe the best way to do this is to change data rates in -
Wireless >802.11b/g/n > network > Data Rates
diable 1,2,5.5 and 11.
Mandatory 6
Supported 9,12,18,24,36,48,54
A suggestion made to me was to untick the box in -
Wireless >802.11b/g/n > network > 802.11b/g Network Status
But I believe doing this from my testing disables the 2.4 B/G radio globally all together. Is there any other method for diabling B clients while leaving G clients ont he 2.4 radio intact?

You could set 12Mb to Mandatory, I think that would prevent B clients from associating globally.
But if it is only a specific WLAN that you never want to support B Clients, you could always set that WLAN Radio policy to 802.11G/A only.... (I think that is still an option). It should allow G/N and A/N clients, but disallow B clients. I read somewhere that band select wont work if the radio policy is not ALL, so maybe not viable for you if you use band select (or perhaps this has been fixed).
Either way I think you have several options at your disposal, not just disabling all B rates..... (this this is the easiest approach if you want all B clients gone, and you have coverage to support non 1,2,5.5,11 rates.
-Wesley Terry

Are multiple colors possible on a published calendar?

Hi, on my desktop I easily see multiple colors, with each on for a different calendar. we have a published calendar for a group, that would be great if it were possible either to publish both with the same URL, or at least allow color changes for some of the items on the calendar again with just one url. Is this possible in iCal?
Thanks.
-wayne

Wayne,
Unfortunately, published calendars are not capable of displaying individual calendar colors.
Consider providing iCal Feedback.
;~)

5508 WLC version 7.6 maximum RADIUS Servers

Hi All,
Is there a maximum limit for RADIUS Servers that we can configure for Authentication under Security TAB in WLC 5508/8500 with version 7.6?
We have 6 RADIUS Servers that needs to be configured for WLAN Client Authentication.
Thanks,
CJ

IIRC the limit is 16 servers on the WLC. but you can only call up to three under the WLAN itself.
If you need to be able to failover to anything beyond 3, than check the network user box in the AAA server configuration to make it globally available.
HTH,
Steve

New Cisco 1552AP Mesh with 5508 controller version 7.0.116.0

New to working with Wireless and the Cisco Meshing concept so have a few questions to ask.
I currently have the majority of the mesh setup and configured. I have a setup with two RAPs with 9 MAPS connecting to each RAP.
First question is how many MAPS can connect to a RAP generally?
Secondly how can I block other cisco AP's that are not in my mesh network from trying to connect to my AP's
The below is constantly hammering the logs for 6 devices that are Cisco close to my mesh that are not mine.
8
Sat Nov 12 23:31:53 2011
Mesh child node '58:35:d9:aa:db:4f' has changed its parent to mesh node '88:f0:77:b7:c6:e0' from mesh node '88:f0:77:b7:c6:c0'.
Mesh Node '58:35:d9:aa:db:4f' failed to join controller, MAC address not in MAC filter list.
I have only added the MAC addresses of my AP's in to my AP Policy under security. Would these other AP's affect the mesh in any way?
What I am seeing is the AP's constantly changing the child to parent relationship. I have inherited this network and they have about 20 AP's all within a square mile which is absolutely overkill. Would this close proximity of AP's together be the cause for the constant child parent changes?
How close should I have RAP's together. The network was setup so two raps are about 20 metres apart and the AP's on one side connect to RAP1 and the other to RAP2?
How do you deal with Radar? The install is pretty much next to an airfield with radar running and a few times I have seen all the AP's disconnect and change channels.
These are a few questions to start. As I go through my logs I will continue to ask additional questions. Cheers.

Out of order answers here.
Don't use the UNI-II band, this should help with the radar, for the most part. Generally I only recommend 4-6 MAP to a RAP. Othewise you can over saturate the backhaul, and of course the further out you go, the smaller the backhaul.
You could set a bridge-group name (BGN), for the RAP-MAP sectors. This can help you limit the number of MAP to RAP, it also will help keep MAPs that aren't your off your network as they do look at the BGN. However, this is not an end all method. a MAP can still try to join a MESH using 'default' as it's BGN.
If the mac address isn't in your filter, the MAP won't be able to join, and the message it sends to try, is low bandwidth.
HTH,
Steve
Please remember to rate helpful posts or to mark the question as answered so that it can be found later.

Clients unable to connect and get DHCP - LAP1142N AP and 5508 WLC

Hi,
I have 19 locations, each with 1 or more LAP1142N AP's in FlexConnect mode, AP's are primed using CAPWAP to my 5508 WLC at the datacenter. The AP's join the WLC without issue every time. I have two WLAN's, one guest and one staff, the guest network is open and obtains DHCP from a WatchGuard XTM33 firewall at each of the remote locations. The staff side is WPA2/RADIUS and DHCP is assigned from the WLC. Each AP is assigned a static IP that is not in the DHCP scope. For example: DHCP scope on the branch firewall is 192.168.1.10-250 the AP will be assigned static IP of 192.168.1.1.. The AP's are connected to a HP procurve switch that has a untagged VLAN, the firewall is using the native vlan 1 and so is the AP.
I have been running this network for over a year and it has not had a single issue until the last two weeks. Nothing on the network has changed or has been upgraded.
Now for the issue: The issue I am seeing is that clients are no longer able to connect to the AP and do not get DHCP assigned to them. I am able to get it working, if I remove the static IP from the AP, the AP will reboot, join the controller, then begin working, users can connect and DHCP is assigned from the firewall as it should. However, If the AP then reboots, the AP will join back to the controller but no clients can connect nor do they get a DHCP address. So, I then reassign a static IP to the AP again and it reboots, connects to the controller and clients then can connect and get DHCP.
Attached is a running config from one of the APs
I've found several posts on this topic, in fact the patch of unassigning or reassigning static IP is one that I found. However, I wanted to post this to see if there is any further assistance I can get on this. I am also waiting on my SmartNet to start up and will be contacting Cisco support as well.
Thanks for any help.

Alright, so I finally figured out the issue with this. I had a Mobility Anchor set on the guest WLAN and once I removed that all started working again.
What is Mobility Anchor?
A. Mobility Anchor, also referred to as Guest tunneling or Auto Anchor Mobility, is a feature where all the client traffic that belongs to a WLAN (Specially Guest WLAN) is tunneled to a predefined WLC or set of controllers that are configured as Anchor for that specific WLAN. This feature helps to restrict clients to a specific subnet and have more control over the user traffic. Refer to the Configuring Auto-Anchor Mobility section of Cisco Wireless LAN Controller Configuration Guide, Release 7.0 for more information on this feature.

Cisco 5508-WLC using MS NPS as RADIUS Server for EAP-TLS

Has anyone experienced a problem getting a Cisco WLC to work with MS NPS server? We've done it before albeit with differnt code versions.
I have a Cisco 5508 WLC running 7.0.116.0 code hosting a WLAN configured for WPA2 with 802.1x for authentication. I have two Windows NPS servers configured as the RADIUS servers for EAP-TLS authentication. Via debug info on the WLC I can see the 802.1x handshake take place with the wireless client and the WLC as well as a successful transmission of an Authentication Packet from the WLC to one of the RADIUS servers. However on the WLC I see repeated RADIUS server x.x.x.x:1812 deactivated in global list and on the NPS server I'm seeing event log errors indicating "The Network Policy Server discarded the request for a user" along with the pertinent auth request info that I would expect the NPS server to receive from the WLC.
Based on the WLC debug info I'm never actually getting to the EAP-TLS certificate authentication part. It seems the NPS servers don't like the format of the initial RADIUS authentication request coming from the WLC and so don't respond whcih in turn casues to WLC to switch to the other NPS server which produces the same issue.
Any ideas of what might be the issue or misconfiguration?

Jim,
I wanted to know if you can setup wireshark on both of the boxes and see if your are hitting the following bug:
http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&bugId=CSCti91044
It looks as if the WLC is retransmitting the client traffic from one radius session with primary over to the secondary in which the radius state attribute that was assigned from the primary server is probably hitting the secondary server. Therefore if the state attribute isnt assigned from the secondary server it will discard the packet.
May need to open a TAC case to see if this issue is on the 550x controllers also.
Thanks,
Tarik

WCS & WLC version compatibility

Are there any compatibility issues between WCS version 7.0.164.0 and WLC version 7.0.116.0?

Hi Jason,
Table 1 WCS Versions
WCS Version Supported Controller Versions Supported Location Server Versions Supported MSE Versions Release Date Upgrade Supported From Operating System Requirement
7.0.172.0
7.0.116.0
7.0.98.218
7.0.98.0
6.0.202.0
6.0.199.4
6.0.196.0
6.0.188.0
6.0.182.0
6.0.108.0
5.2.193.0
5.2.178.0
5.2.157.0
4.2.209.0
4.2.207.0
4.2.205.0
4.2.176.0
4.2.173.0
4.2.130.0
4.2.112.0
4.2.99.0
4.2.61.0
6.0.202.0
7.0.201.0
April 2011
7.0.164.3
7.0.164.0
6.0.202.0
6.0.196.0
6.0.181.0
6.0.170.0
6.0.132.0
5.2.148.0
5.2.130.0
5.2.125.0
5.2.110.0
Windows 2003 SP2 32-bit
RHEL 5.x
Windows/ RHEL on ESX 3.0.1 and above
No support for 64 bit
7.0.164.3
7.0.98.0
6.0.202.0
6.0.199.4
6.0.196.0
6.0.188.0
6.0.182.0
6.0.108.0
5.2.193.0
5.2.178.0
5.2.157.0
4.2.209.0
4.2.207.0
4.2.205.0
4.2.176.0
4.2.173.0
4.2.130.0
4.2.112.0
4.2.99.0
4.2.61.0
6.0.103.0
7.0.105.0
December 2010
7.0.164.0
6.0.196.0
6.0.181.0
6.0.170.0
6.0.132.0
5.2.148.0
5.2.130.0
5.2.125.0
5.2.110.0
Windows 2003 SP2 32-bit
RHEL 5.x
Windows/ RHEL on ESX 3.0.1 and above
No support for 64 bit
7.0.164.0
7.0.98.0
6.0.202.0
6.0.199.4
6.0.196.0
6.0.188.0
6.0.182.0
6.0.108.0
5.2.193.0
5.2.178.0
5.2.157.0
4.2.209.0
4.2.207.0
4.2.205.0
4.2.176.0
4.2.173.0
4.2.130.0
4.2.112.0
4.2.99.0
4.2.61.0
6.0.103.0
7.0.105.0
June 2010
6.0.181.0
6.0.170.0
6.0.132.0
5.2.148.0
5.2.130.0
5.2.125.0
5.2.110.0
Windows 2003 SP2 32-bit
RHEL 5.x
Windows/ RHEL on ESX 3.0.1 and above
No support for 64 bit
6.0.202.0
6.0.202.0
6.0.199.4
6.0.199.0 (pulled from CCO)
6.0.196.0
6.0.188.0
6.0.182.0
6.0.108.0
5.2.193.0
5.2.178.0
5.2.157.0
5.1.163.0
5.1.151.0
4.2.209.0
4.2.207.0
4.2.205.0
4.2.176.0
4.2.173.0
4.2.130.0
4.2.112.0
4.2.99.0
4.2.61.0
6.0.202.0
6.0.202.0
April 2011
6.0.196.0
6.0.181.0
6.0.170.0
6.0.132.0
5.2.148.0
5.2.130.0
5.2.125.0
5.2.110.0
5.1.65.4
5.1.64.0
4.2.128.0
4.2.110.0
4.2.97.0
4.2.81.0
4.2.62.11
4.2.62.0
Windows 2003 SP2 32-bit
RHEL 5.x
Windows/ RHEL on ESX 3.0.1 and above
No support for 64 bit
6.0.196.0
6.0.199.4
6.0.199.0 (pulled from CCO)
6.0.196.0
6.0.188.0
6.0.182.0
6.0.108.0
5.2.193.0
5.2.178.0
5.2.157.0
5.1.163.0
5.1.151.0
4.2.209.0
4.2.207.0
4.2.205.0
4.2.176.0
4.2.173.0
4.2.130.0
4.2.112.0
4.2.99.0
4.2.61.0
6.0.102.0
6.0.105.0
15 July 2010
6.0.181.0
6.0.170.0
6.0.132.0
5.2.148.0
5.2.130.0
5.2.125.0
5.2.110.0
5.1.65.4
5.1.64.0
4.2.128.0
4.2.110.0
4.2.97.0
4.2.81.0
4.2.62.11
4.2.62.0
Windows 2003 SP2 32-bit
RHEL 5.x
Windows/ RHEL on ESX 3.0.1 and above
No support for 64 bit
6.0.181.0
6.0.196.0
6.0.188.0
6.0.182.0
6.0.108.0
5.2.193.0
5.2.178.0
5.2.157.0
5.1.163.0
5.1.151.0
4.2.207.0
4.2.205.0
4.2.176.0
4.2.173.0
4.2.130.0
4.2.112.0
4.2.99.0
4.2.61.0
6.0.101.0
6.0.103.0
17 Feb 2010
6.0.170.0
6.0.132.0
5.2.148.0
5.2.130.0
5.2.125.0
5.2.110.0
5.1.65.4
5.1.64.0
4.2.128.0
4.2.110.0
4.2.97.0
4.2.81.0
4.2.62.11
4.2.62.0
Windows 2003 SP2 32-bit
RHEL 5.x
Windows/ RHEL on ESX 3.0.1 and above
No support for 64 bit
6.0.170.0
6.0.188.0
6.0.182.0
6.0.108.0
5.2.193.0
5.2.178.0
5.2.157.0
5.1.163.0
5.1.151.0
4.2.207.0
4.2.205.0
4.2.176.0
4.2.173.0
4.2.130.0
4.2.112.0
4.2.99.0
4.2.61.0
6.0.97.0
6.0.97.0
8 Nov 2009
6.0.132.0
5.2.148.0
5.2.130.0
5.2.125.0
5.2.110.0
5.1.65.4
5.1.64.0
4.2.128.0
4.2.110.0
4.2.97.0
4.2.81.0
4.2.62.11
4.2.62.0
Windows 2003 SP2 32-bit
RHEL 5.x
Windows/ RHEL on ESX 3.0.1 and above
No support for 64 bit
6.0.132.0
6.0.182.0
6.0.108.0
5.2.178.0
5.2.157.0
5.1.163.0
5.1.151.0
4.2.205.0
4.2.176.0
4.2.173.0
4.2.130.0
4.2.112.0
4.2.99.0
4.2.61.0
6.0.85.0
6.0.85.0
11 June 2009
5.2.130.0
5.2.125.0
5.2.110.0
5.1.65.4
5.1.64.0
4.2.128.0
4.2.110.0
4.2.97.0
4.2.81.0
4.2.62.11
4.2.62.0
Windows 2003 SP2 32-bit
RHEL 5.x
Windows/ RHEL on ESX 3.0.1 and above
No support for 64 bit
5.2.148.0
5.2.193.0
5.2.178.0
5.2.157.0
5.1.151.0
5.0.148.2
5.0.148.0
4.2.207.0
4.2.205.0
4.2.176.0
4.2.173.0
4.2.130.0
4.2.112.0
4.2.99.0
4.2.61.0
5.2.100.0
5.2.100.0
25 June 2009
5.2.130.0
5.2.125.0
5.2.110.0
5.1.65.4
5.1.64.0
5.0.72.0
5.0.56.2
5.0.56.0
4.2.128.0
4.2.110.0
4.2.97.0
4.2.81.0
4.2.62.11
4.2.62.0
Windows 2003 SP2 32-bit
RHEL 5.x
Windows/ RHEL on ESX 3.0.1 and above
No support for 64 bit
5.2.130.0
5.2.178.0
5.2.157.0
5.1.151.0
5.0.148.2
5.0.148.0
4.2.176.0
4.2.173.0
4.2.130.0
4.2.112.0
4.2.99.0
4.2.61.0
5.2.91.0
5.2.91.0
21 Feb 2009
5.2.125.0
5.2.110.0
5.1.65.4
5.1.64.0
5.0.72.0
5.0.56.2
5.0.56.0
4.2.110.0
4.2.97.0
4.2.81.0
4.2.62.11
4.2.62.0
Windows 2003 SP2 32-bit
RHEL 5.x
Windows/ RHEL on ESX 3.0.1 and above
No support for 64 bit
5.2.125.0
5.2.178.0
5.2.157.0
5.1.151.0
5.0.148.2
5.0.148.0
4.2.176.0
4.2.173.0
4.2.130.0
4.2.112.0
4.2.99.0
4.2.61.0
5.2.91.0
5.2.91.0
10 Feb 2009
5.2.110.0
5.1.65.4
5.1.64.0
5.0.72.0
5.0.56.2
5.0.56.0
4.2.110.0
4.2.97.0
4.2.81.0
4.2.62.11
4.2.62.0
Windows 2003 SP2 32-bit
RHEL 5.x
Windows/ RHEL on ESX 3.0.1 and above
No support for 64 bit
5.2.110.0
5.2.157.0
5.1.151.0
5.0.148.2
5.0.148.0
4.2.176.0
4.2.173.0
4.2.130.0
4.2.112.0
4.2.99.0
4.2.61.0
5.2.91.0
5.2.91.0
24 Nov 2008
5.1.64.0
5.0.72.0
5.0.56.2
5.0.56.0
4.2.110.0
4.2.97.0
4.2.81.0
4.2.62.11
4.2.62.0
Windows 2003 SP2 32-bit
RHEL 5.1
RHEL 5.0
Windows/ RHEL on ESX 3.0.1 and above
No support for 64 bit
5.1.65.4
5.1.163.0
5.1.151.0
5.0.148.2
5.0.148.0
4.2.176.0
4.2.173.0
4.2.130.0
4.2.112.0
4.2.99.0
4.2.61.0
5.1.35.0
5.1.35.0
9 Jan 2009
5.1.64.0
5.0.72.0
5.0.56.2
5.0.56.0
4.2.110.0
4.2.97.0
4.2.81.0
4.2.62.11
4.2.62.0
Windows 2003 SP2 32-bit
RHEL 5.x
RHEL 5.x
Windows/ RHEL on ESX 3.0.1 and above
No support for 64 bit
5.1.64.0
5.1.151.0
5.0.148.2
5.0.148.0
4.2.176.0
4.2.173.0
4.2.130.0
4.2.112.0
4.2.99.0
4.2.61.0
5.1.30.0
5.1.30.0
21 July 2008
5.0.56.2
5.0.56.0
4.2.97.0
4.2.81.0
4.2.62.11
4.2.62.0
Windows 2003 SP2 32-bit
RHEL 5.1
RHEL 5.0
Windows/ RHEL on ESX 3.0.1 and above
No support for 64 bit
5.0.72.0
5.0.148.2
5.0.148.0
4.2.130.0
4.2.112.0
4.2.99.0
4.2.61.0
4.1.185.0
4.1.171.0
4.0.38.0
Not Applicable
5 Aug 2008
5.0.56.2
5.0.56.0
4.2.62.11
4.2.62.0
4.1.91.0
4.1.83.0
Windows 2003 SP2 32-bit
RHEL 5.1
RHEL 5.0
Windows/ RHEL on ESX 3.0.1 and above
No support for 64 bit
5.0.56.2
5.0.148.0
4.2.61.0
4.1.x.x
4.0.33.0
Not Applicable
14 Apr 2008
5.0.56.0
4.2.62.11
4.2.62.0
4.1.91.0
4.1.83.0
Windows 2003 SP2 32-bit
RHEL 5.0
Windows/ RHEL on ESX 3.0.1 and above
No support for 64 bit
5.0.56.0
5.0.148.0
4.2.61.0
4.1.x.x
4.0.32.0
Not Applicable
16 Feb 2008
4.2.62.11
4.2.62.0
4.1.91.0
4.1.83.0
Windows 2003 SP2 32-bit
RHEL 5.0
Windows/ RHEL on ESX 3.0.1 and above
No support for 64 bit
4.2.128.0
4.2.207.0
4.2.205.0
4.2.176.0
4.2.130.0
4.2.112.0
4.2.99.0
4.2.61.0
4.1.185.0
4.1.171.0
4.0.216.0
4.0.206.0
4.0.179.11
4.0.179.8
4.0.155.0
3.1.43.0
Not Applicable
13 May 2009
4.2.110.0
4.2.97.0
4.2.81.0
4.2.62.11
4.2.62.0
4.1.91.0
4.1.83.0
4.0.100.0
4.0.97.0
4.0.96.0
4.0.87.0
4.0.81.0
4.0.66.0
Windows 2003 SP2 32-bit
RHEL 4.0
RHEL 5.0 (5.1 and later no supported)
Windows/ RHEL on ESX 3.0.1 and above
No support for 64 bit
4.2.110.0
4.2.176.0
4.2.130.0
4.2.112.0
4.2.99.0
4.2.61.0
4.1.185.0
4.1.171.0
4.0.216.0
4.0.206.0
4.0.179.11
4.0.179.8
4.0.155.0
3.1.42.0
Not Applicable
29 Sep 2008
4.2.97.0
4.2.81.0
4.2.62.11
4.2.62.0
4.1.91.0
4.1.83.0
4.0.100.0
4.0.97.0
4.0.96.0
4.0.87.0
4.0.81.0
4.0.66.0
Windows 2003 SP2 32-bit
RHEL 4.0
RHEL 5.0
Windows/ RHEL on ESX 3.0.1 and above
No support for 64 bit
4.2.97.0
4.2.176.0
4.2.130.0
4.2.112.0
4.2.99.0
4.2.61.0
4.1.185.0
4.1.171.0
4.0.216.0
4.0.206.0
4.0.179.11
4.0.179.8
4.0.155.0
3.1.38.0
Not Applicable
3 Jun 2008
4.2.81.0
4.2.62.11
4.2.62.0
4.1.91.0
4.1.83.0
4.0.100.0
4.0.97.0
4.0.96.0
4.0.87.0
4.0.81.0
4.0.66.0
Windows 2003 SP2 32-bit
RHEL 4.0
RHEL 5.0
Windows/RHEL on ESX 3.0.1 and above
No support for 64 bit
4.2.81.0
4.2.99.0
4.2.61.0
4.1.185.0
4.1.171.0
4.0.216.0
4.0.206.0
4.0.179.11
4.0.179.8
4.0.155.0
3.1.36.0
Not Applicable
17 Mar 2008
4.2.62.11
4.2.62.0
4.1.91.0
4.1.83.0
4.0.100.0
4.0.97.0
4.0.96.0
4.0.87.0
4.0.81.0
4.0.66.0
Windows 2003 SP2 32-bit
RHEL 4.0
RHEL 5.0
Windows/ RHEL on ESX 3.0.1 and above
No support for 64 bit
4.2.62.11
4.2.61.0
4.1.185.0
4.1.171.0
4.0.216.0
4.0.206.0
4.0.179.11
4.0.179.8
4.0.155.0
3.1.35.0
Not Applicable
25 Jan 2008
4.2.62.0
4.1.91.0
4.1.83.0
4.0.100.0
4.0.97.0
4.0.96.0
4.0.87.0
4.0.81.0
4.0.66.0
Windows 2003 SP2 32-bit
RHEL 4.0 Update 5
Windows/ RHEL on ESX 3.0.1 and above
No support for 64 bit
4.2.62.0
4.2.61.0
4.1.185.0
4.1.171.0
4.0.216.0
4.0.206.0
4.0.179.11
4.0.179.8
4.0.155.0
3.1.35.0
Not Applicable
9 Nov 2007
4.1.91.0
4.1.83.0
4.0.100.0
4.0.97.0
4.0.96.0
4.0.87.0
4.0.81.0
4.0.66.0
Windows 2003 SP2 32-bit
RHEL 4.0 Update 5
Windows/ RHEL on ESX 3.0.1 and above
No support for 64 bit
http://www.cisco.com/en/US/docs/wireless/wcs/release/notes/WCS_RN7_0_172.html
Cheers!
Rob
PS: +5 to my friend Leo using the invisible Stars

How can I add the new AP license to HA 5508 WLC?

Hi,
My customer has two 5508 WLC in HA mode and these devices have 250 AP license. Customer bought 50 AP and 50 AP license. But I could not add the license to WLC! When I check the Management>Software Activation> tab there are only two options under the tab these are "Licenses" "License Usage". There is no "Command" option in there. Also I tried add on CLI but this error log appeared " !!!! Blocked: Changing License configurations on Secondary unit is blocked !!!! "
I think this is possible when disable the HA but is there anybody know this how can I add the new 50 AP license to HA WLC without disable the HA?
Thanks,
Burhan

Hi,
Thank you for your reply.
Yes I know the controllers synchronize with the enabled license and the 250 AP license bundled with two device there is no problem.
I want to add new 50 AP license in addition 250 AP license. Because customer has 300 AP's.
As I said, When I check the Management>Software Activation> tab there are only two options under the tab these are "Licenses" "License Usage". There is no "Command" option in there.
Thanks,

Can we use a 5508 WLC in Hong Kong and join 3602 APs in Vietnam to it? Any regulatory contraints?

Hi friends,
I am looking for some wisdom here!
Just wondering if I can use a 5508 WLC in Hong Kong and join 3602 APs in Vietnam to it?
Any regulatory contsraints / guidelines that would prohibit from doing so?
- Regards,
Tarun.

You have two differnt regulations... here is a link:
http://www.cisco.com/en/US/prod/collateral/wireless/ps5679/ps5861/product_data_sheet0900aecd80537b6a_ps10981_Products_Data_Sheet.html
You need to make sure you are not breaking any rules and it is best to have an AP that is specific to that country. Also if you add multiple country codes on a WLC, the AP's will only be able to use the most common channels and TX power setting allowed on both. Here is a link explaining that.
http://nostringsattachedshow.com/2012/02/02/multiple-country-codes-with-the-cisco-wlc/
Thanks,
Scott
Help out other by using the rating system and marking answered questions as "Answered"

5508 WLC HA pair - change management interface settings

Hi,
We have a pair of 5508 WLC's in a HA configuration that is working well at the moment, however I have noticed that the management interface is configured as untagged. I would like to change this to tagged and change the attached switch to trunk for these devices but if I try and edit the management interface through the GUI the VLAN and IP address section is greyed out and cannot be changed. While I could attempt it through the CLI and am comfortable doing that, the fact that it cannot be changed through the GUI implies that this should not be changed and so I am after further information. I don't have any lab equipment other than the HA pair in production so I cannot try changing it through the CLI at the moment.
The WLC's are in LAG mode if that makes any difference. I realise there may be downtime required for making this change but I am trying to work out the steps to get this done without having to drastically reconfigure things.
Any assistance would be appreciated.

Introduction of New Interfaces for HA Interaction
Redundancy Management Interface
The IP address on this interface should be configured in the same subnet as the management interface. This interface will check the health of the Active WLC via network infrastructure once the Active WLC does not respond to Keepalive messages on the Redundant Port. This provides an additional health check of the network and Active WLC, and confirms if switchover should or should not be executed. Also, the Standby WLC uses this interface in order to source ICMP ping packets to check gateway reachability. This interface is also used in order to send notifications from the Active WLC to the Standby WLC in the event of Box failure or Manual Reset. The Standby WLC will use this interface in order to communicate to Syslog, the NTP server, and the TFTP server for any configuration upload.
Redundancy Port
This interface has a very important role in the new HA architecture. Bulk configuration during boot up and incremental configuration are synced from the Active WLC to the Standby WLC using the Redundant Port. WLCs in a HA setup will use this port to perform HA role negotiation. The Redundancy Port is also used in order to check peer reachability sending UDP keep-alive messages every 100 msec (default timer) from the Standby WLC to the Active WLC. Also, in the event of a box failure, the Active WLC will send notification to the Standby WLC via the Redundant Port. If the NTP server is not configured, a manual time sync is performed from the Active WLC to the Standby WLC on the Redundant Port. This port in case of standalone controller and redundancy VLAN in case of WISM-2 will be assigned an auto generated IP Address where last 2 octets are picked from the last 2 octets of Redundancy Management Interface (the first 2 octets are always 169.254).

5508 WLC HA pair and layer 3 roaming

Hey,
We have a pair of 5508 WLC's configured in HA (primary/standby). We have a single SSID that we're broadcasting across each floor of our head office. The AP's are in flexconnect mode so users pickup an IP address from the DHCP range for that building level and that's all working well.
The problem I have is that users cannot roam between floors without losing access to the network. They roam to the AP's on the different floors, and maintain wireless connection throughout the building, but they cannot connect to anything on the network when outside of the floor that contains an IP range that matches the client's IP. I was told by a number of technical consultants that this sort of layer 3 roaming should work in this configuration. When users go to a different floor, they retain their original IP and the traffic is tunneled (EOIP) back to the controller to maintain network connectivity, however this does not appear to be happening.
Firstly I'm wondering if this is possible with a HA pair configured in active/standby. All of the documentation around layer 3 roaming seems to involve at least 2 controllers, the foreign and the anchor. In this case as they're a HA pair their is technically only a single controller.
If it is possible to do layer 3 roaming on a single controller (intra-controller), if anyone can provide some guidance on things I should be checking or looking out for that would be appreciated.
Thanks.

Still though, I had a number of technical consultants from a very large system integrator design this setup and despite my asking a number of times how this roaming could work I was simply told it would.
ROFL!
We contracted a consulting company/implementors to do a wireless job (back in 2011) for a particular project (politics dictate I keep stay away from it). They had one "wireless expert".
Then one day, I got a call from the "wireless expert" and the phone conversation went like this, "It's me. I am doing another wireless project for another agency. But I would like to know how do you convert an autonomous AP to controller-based IOS". <FACEPALM>
Long story short: They won't know. Not all of them know. Their main concern is YOUR MONEY in their hands. That's all. But I can tell you this: I am the end user. I configure stuff. Roaming works if you get the basics correct. Roaming works if you know what you want and you get it done right. Scott Fella and Steve Rodriguez, two regular in this forum, (and works for CDW) and they are good. There's another "mad Texan" by the name of George Stefanick is another one. An Aussie by the name of Rasika is also around.
The most basic item is roaming is how you space your APs. Unless you've got wireless antennas coming out of your ears, you need to organize a wireless site survey. And when you want to do the a "good" wireless site survey, you "future proof" your requirements. Right now, my wireless site survey is aimed at "wireless VoIP" requirement.

5508 wlc with 1142 wap

I am wanting to know about methods of getting a wap to join a wlc. I’ve got 5508 wlc’s and the wap’s are the 1142’s. Are there other methods of getting wap’s to join wlc’s other than option 43 of dhcp? Also, is it possible to get a wap to automatically join a secondary controller if the first one it is trying to join is full?

The wap’s do not seem to be finding the other controller when being added. They just look for one controller only and do not attempt to find the other. Also, on the wap’s, when you enter the primary and secondary controller on the controller admin site. It does not move the wap’s to the other controller as primary. The secondary controller has 11 wap’s to go before full. The primary controller is full

Can't put two 5508 WLCs in the same RF group

Hi experts,
I have two 5508 WLCs and I want them to be backup to each other. I put in the same "RF Group Name" and even the same "Default Mobility Domain Name" however under Wireless -> 802.11b/g/n -> RRM -> RF Grouping each controller still only have themselves as the only memter to the group.
Two controllers are having management IPs on the same subnet 192.168.161.x/24. AP-manager interfaces are in the same network as well. They can ping each other fine. The following screen shots show the current relavent config on the controller:
I do have two controllers in the same mobility group and they are both showing up...
Does anyone know why they can't add each other to the RF group? All other settings are pretty much default...
Thanks!

Hi,
is there a chance that one of the 2 WLC doesn't contain any access point ? Or that the APs from one WLC are not physically close to the APs of the second WLC ?
The point of RF grouping is to exchange RF information, to make RRM decisions together and to know what ap is a rogue and which is not. RF group information travels over the air from AP to AP.
So if a wlc has no ap of if its APs are not close to those of the other WLC there is both no point in grouping with the other WLC in rf group and also no technical way of doing so.
Regards,
Nicolas
===
Don't forget to rate answers that you find useful

Can't get 1532i to associate to 5508 WLC running 7.6.130.0

Greetings,
I've got 20 or so APs on a 5508 WLC. Most of the APs are 1242, one is 3602. I'm now trying to get a 1532i to associate to the 5508 and it's not happening. This is the first 1532 on this controller.
Also, I got this 1532 AP from a sister site and they had it configured as Autonomous in wgb mode, so I had to do the Autonomous to Unified Conversion. This conversion appeared to go successfully. But now the AP won't associate to my controller.
Thanks
Following is what happens from the AP's console :
AP78da.6e59.e58a#reload
Proceed with reload? [confirm]
Writing out the event log to flash:/event.log ...
Write of event.log done
*Oct 28 20:27:37.151: %SYS-5-RELOAD: Reload requested by Cisco on console. Reload Reason: Reload.
*Oct 28 20:27:37.155: %LWAPP-5-CHANGED: CAPWAP changed state to DOWN
*Oct 28 20:27:39.999: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to 10.132.249.5:5246
*Oct 28 20:27:40.039: %LWAPP-3-CLIENTERRORLOG: LWAPP LED Init: incorrect led state 255
System Bootstrap, Version U-Boot 1.1.4-gf5ee82b1-dirty Corfu , RELEASE SOFTWARE
Build Date: Oct 17 2013 - 18:08:55
corfu - Scorpion 1.0
DRAM: 256 MB
Now running in RAM - U-Boot at: 8ffbc000
Flash Manuf Id 0xc2, DeviceId0 0x20, DeviceId1 0x14
flash size 1MB, sector count = 256
Atheros on-chip NAND FLash Controller Driver, Version 0.1 (c) 2010 Atheros Communications, Ltd.
Ath Nand ID[8ffee17c]: 2c:f1:80:95:02
ONFI MICRON MT29F1G08ABADAWP
Micron NAND 128MiB 3,3V 8-bit [128MB]
size = 128MB
Hit any key to stop autoboot: 0
boot_method is set to IOS_BOOT, boot IOS bootloader in NOR flash
Loading .text @ 0x84000000 (207840 bytes)
Loading .rodata @ 0x84032be0 (39008 bytes)
Loading .data @ 0x8403c440 (3264 bytes)
Loading .data.rel.local @ 0x8403d100 (1084 bytes)
Loading .data.rel @ 0x8403d53c (124 bytes)
Loading .data.rel.ro @ 0x8403d5b8 (960 bytes)
Clearing .bss @ 0x8403d980 (161116 bytes)
Clearing .scommon @ 0x84064edc (56 bytes)
## Starting application at 0x84000000 ...
IOS Secondary Bootloader - Starting system.HW Test Status(0)
Ath Nand ID: 95:80:f1:2c:00
Using driver version 1 for media type 2
Valid buffers 146
total146 146
success found all blocks
start end 65 85
found in range
high low end 2728 2089 85
Xmodem file system is available.
mifs[0]: 15 files, 5 directories
mifs[0]: Total bytes : 131334144
mifs[0]: Bytes used : 7966720
mifs[0]: Bytes available : 123367424
mifs[0]: mifs fsck took 0 seconds.
Base Ethernet MAC address: 78:da:6e:59:e5:8a
Setup MAC....
Waiting for PHY auto negotiation to complete...Port 0 Negogiation success.
Ethernet speed is 100 Mb - FULL duplex
Scorpion ----> F1 PHY *
: cfg1 0xf cfg2 0x7115
Loading "flash:/ap1g3-k9w8-mx.152-4.JB6/ap1g3-k9w8-mx.152-4.JB6"...##########################################################################################################################################################################################################################################################################################################################################################################
File "flash:/ap1g3-k9w8-mx.152-4.JB6/ap1g3-k9w8-mx.152-4.JB6" uncompressed and installed, entry point: 0x60080000
executing...
Stop MAC.
Starting IOS...
cp0 timer begin value is set as 1000
prid= 19750
Starts main.
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, C1530 Software (ap1g3-K9W8-M), Version 15.2(4)JB6, RELEASE SOFTWARE (fc1)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2014 by Cisco Systems, Inc.
Compiled Fri 22-Aug-14 11:03 by prod_rel_team
Initializing flashfs...
Ath Nand ID: 95:80:F1:2C:00
Using driver version 1 for media type 2
Valid buffers 146
total146 146
success found all blocks
start end 65 85
found in range
high low end 2728 2089 85
mifs[4]: 15 files, 5 directories
mifs[4]: Total bytes : 131334144
mifs[4]: Bytes used : 7966720
mifs[4]: Bytes available : 123367424
mifs[4]: mifs fsck took 2 seconds.
mifs[4]: Initialization complete.
...done Initializing flashfs.
:pci_init_board:521 *** Warning *** : PCIe1 WLAN Module not found !!!
pci_rc2_init_board:570 PCIE Controller Init Bus Master Enable
:pci_rc2_init_board:593 PCIe2 WLAN Module Found !!!
soap_pci_subsys_init:706 Bus Master/Mem Enable on pci_write side
soap_pci_subsys_init(713): PCI vendor ID: 0x168C ret:0
soap_pci_subsys_init(715): PCI device ID: 0x33 ret:0
Scorpion ----> F1 PHY *
Waiting for PHY auto negotiation to complete...Port 0 Negogiation success.
Disabling 802.3az feature on port 0
sgmii cal value = 0xE
Disabling 802.3az feature on port 1.
SGMII setup done, status is 0x2
Radio0 present 9550 9000 0 0 0 0
Rate table has 282 entries (12 legacy/96 11n/174 11ac)
Radio1 present 9590 9000 0 0 B2000000 1
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-CAP1532I-A-K9 (MIPS74k) processor (revision 27) with 204800K/57344K bytes of memory.
Processor board ID FTX1813201L
MIPS74k CPU at 700MHz, revision number 0x0000
Last reset from power-on
LWAPP image version 7.6.100.0
2 Gigabit Ethernet interfaces
2 802.11 Radios
32K bytes of flash-simulated non-volatile configuration memory.
Base ethernet MAC Address: 78:DA:6E:59:E5:8A
Part Number : 74-11942-01
PCA Assembly Number : 000-00000-00
PCA Revision Number :
PCB Serial Number : FOC180951ZR
Top Assembly Part Number : 000-00000-00
Top Assembly Serial Number : FTX1813201L
Top Revision Number : 23
Product/Model Number : AIR-CAP1532I-A-K9
% Please define a domain-name first.
Press RETURN to get started!
*Mar 1 00:00:09.895: %SOAP_FIPS-2-SELF_TEST_IOS_SUCCESS: IOS crypto FIPS self test passed (11)mips74k_config_radio_pci(302): PCI CMD write: 0x356
*Mar 1 00:00:14.391: %LINK-6-UPDOWN: Interface GigabitEthernet0, changed state to upEnterprise mode: 0x44000000
*Mar 1 00:00:14.895: %SOAP_FIPS-2-SELF_TEST_RAD_SUCCESS: RADIO crypto FIPS self test passed on interface Dot11Radio 0 (2)
*Mar 1 00:00:14.971: ath_load_ctl_pwr_tbl() dot11radio 2G loading CTL binary flash:/ap1g3-k9w8-mx.152-4.JB6/CO2.bin version# 3.0
*Mar 1 00:00:15.419: %SOAP_FIPS-2-SELF_TEST_RAD_SUCCESS: RADIO crypto FIPS self test passed on interface Dot11Radio 1 (2)
*Mar 1 00:00:15.419: ath_load_ctl_pwr_tbl() dot11radio 5G loading CTL binary flash:/ap1g3-k9w8-mx.152-4.JB6/CO5.bin version# 3.4
*Mar 1 00:00:15.699: CDP_PD: Power Source: 4-pair Power Injector
*Mar 1 00:00:15.723: AP Mesh platform identified (backhaul config:0x2, access:0xF)
*Mar 1 00:00:15.735: Starting Ethernet promiscuous mode
*Mar 1 00:00:15.735: Skipping Ethernet bridge initializaion
*Mar 1 00:00:16.431: %LINK-6-UPDOWN: Interface GigabitEthernet1, changed state to up
*Mar 1 00:00:18.363: %SYS-5-RESTART: System restarted --
Cisco IOS Software, C1530 Software (ap1g3-K9W8-M), Version 15.2(4)JB6, RELEASE SOFTWARE (fc1)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2014 by Cisco Systems, Inc.
Compiled Fri 22-Aug-14 11:03 by prod_rel_team
*Mar 1 00:00:18.363: %SNMP-5-COLDSTART: SNMP agent on host AP78da.6e59.e58a is undergoing a cold start
*Mar 1 00:00:18.399: %MESH-6-BVI_CREATED: Mesh BVI1 interface created
*Mar 1 00:00:18.399: ath_ACIF_set_distance: Retrieved existing timeout value: 25us for distance: 0km
*Mar 1 00:00:18.399: ath_ACIF_set_distance: Setting new timeout value: 45us for distance: 3km
*Mar 1 00:00:18.399: %CDP_PD-4-POWER_OK: Full power - HIGH_POWER inline power source
*Mar 1 00:00:18.619: %SSH-5-ENABLED: SSH 2.0 has been enabled
*Mar 1 00:00:18.619: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to up
*Mar 1 00:00:18.619: %LINK-6-UPDOWN: Interface Dot11Radio1, changed state to uplwapp_crypto_init: MIC Present and Parsed Successfully
*Mar 1 00:00:18.811: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0, changed state to up
*Mar 1 00:00:20.399: %LINK-6-UPDOWN: Interface BVI1, changed state to down
*Mar 1 00:00:37.015: Logging LWAPP message to 255.255.255.255.
*Mar 1 00:00:37.027: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset
*Mar 1 00:00:38.027: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to up
*Mar 1 00:00:38.035: %LINK-5-CHANGED: Interface Dot11Radio1, changed state to reset
*Mar 1 00:00:39.027: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to up
*Mar 1 00:00:39.067: %LINK-6-UPDOWN: Interface Dot11Radio1, changed state to up
*Mar 1 00:00:40.023: %MESH-6-ADJACENCY_STATE_MACHINE_STARTED: Mesh adjacency state machine started
*Mar 1 00:00:40.067: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio1, changed state to up
*Mar 1 00:01:13.531: Mesh setting the ethernet port 0 state to 2
*Mar 1 00:01:13.531: %MESH-6-CAPWAP_RESTART: Mesh Capwap re-started
*Mar 1 00:01:15.531: %LINK-6-UPDOWN: Interface BVI1, changed state to up
*Mar 1 00:01:16.531: %LINEPROTO-5-UPDOWN: Line protocol on Interface BVI1, changed state to up
*Mar 1 00:01:18.639: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to down
*Mar 1 00:01:18.651: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset
*Mar 1 00:01:19.639: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to down
*Mar 1 00:01:19.671: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to up
*Mar 1 00:01:20.671: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to up
*Mar 1 00:01:28.643: %MESH-6-CAPWAP_RESTART: Mesh Capwap re-started
*Mar 1 00:01:28.759: %DHCP-6-ADDRESS_ASSIGN: Interface BVI1 assigned DHCP address 10.132.120.85, mask 255.255.255.0, hostname AP78da.6e59.e58a
*Mar 1 00:01:28.759: %MESH-6-CAPWAP_RESTART: Mesh Capwap re-started
*Mar 1 00:01:33.791: %LWAPP-3-CLIENTERRORLOG: LWAPP LED Init: incorrect led state 255
*Mar 1 00:01:33.855: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to down
Translating "CISCO-CAPWAP-CONTROLLER.americas.mittalco.com"...domain server (10.132.250.250) [OK]
*Mar 1 00:01:33.867: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset
*Mar 1 00:01:34.855: %CAPWAP-3-ERRORLOG: Did not get log server settings from DHCP.
*Mar 1 00:01:34.855: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to down
*Mar 1 00:01:34.915: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to up
*Mar 1 00:01:35.915: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to up
*Mar 1 00:01:44.855: %CAPWAP-3-ERRORLOG: Go join a capwap controller
*Oct 28 20:29:44.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 10.132.249.5 peer_port: 5246
*Oct 28 20:29:44.495: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully peer_ip: 10.132.249.5 peer_port: 5246
*Oct 28 20:29:44.495: %CAPWAP-5-SENDJOIN: sending Join Request to 10.132.249.5
*Oct 28 20:29:44.499: %CAPWAP-3-ERRORLOG: Invalid event 10 & state 5 combination.
*Oct 28 20:29:44.499: %CAPWAP-3-ERRORLOG: CAPWAP SM handler: Failed to process message type 10 state 5.
*Oct 28 20:29:44.499: %CAPWAP-3-ERRORLOG: Failed to handle capwap control message from controller
*Oct 28 20:29:44.499: %CAPWAP-3-ERRORLOG: Failed to process encrypted capwap packet from 10.132.249.5
*Oct 28 20:29:49.495: %CAPWAP-5-SENDJOIN: sending Join Request to 10.132.249.5
*Oct 28 20:30:43.999: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to 10.132.249.5:5246
*Oct 28 20:30:44.031: %LWAPP-3-CLIENTERRORLOG: LWAPP LED Init: incorrect led state 255
*Oct 28 20:30:44.095: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to down
*Oct 28 20:30:44.135: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset
*Oct 28 20:30:45.095: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to down
*Oct 28 20:30:45.155: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to up
*Oct 28 20:30:46.155: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to up
*Oct 28 20:30:54.095: %CAPWAP-3-ERRORLOG: Go join a capwap controller
*Oct 28 20:30:52.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 10.132.249.5 peer_port: 5246
*Oct 28 20:30:52.499: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully peer_ip: 10.132.249.5 peer_port: 5246
*Oct 28 20:30:52.499: %CAPWAP-5-SENDJOIN: sending Join Request to 10.132.249.5
*Oct 28 20:30:52.499: %CAPWAP-3-ERRORLOG: Invalid event 10 & state 5 combination.
*Oct 28 20:30:52.503: %CAPWAP-3-ERRORLOG: CAPWAP SM handler: Failed to process message type 10 state 5.
*Oct 28 20:30:52.503: %CAPWAP-3-ERRORLOG: Failed to handle capwap control message from controller
*Oct 28 20:30:52.503: %CAPWAP-3-ERRORLOG: Failed to process encrypted capwap packet from 10.132.249.5
*Oct 28 20:30:57.499: %CAPWAP-5-SENDJOIN: sending Join Request to 10.132.249.5

You have to add the MAC address of the 1530 to the WLC mac filter list before the AP will join. Here is a link that explains it.
http://www.cisco.com/c/en/us/td/docs/wireless/access_point/1530/quick/guide/ap1532qsg.html#pgfId-45801
Scott

Are multiple trunks possible on a 5508 WLC version 7.0.116.0

Similar Messages

Maybe you are looking for