5508 WLC license upgrade ?

Looks like my 5508 WLC came with base license of 25 ap's and I need to exceed that.
Is this something I can purchase thru Cisco indirectly thru a vendor ?
Do I need a license to exceed the 25 ap's ?
Cheers
Dave

The part number for the adder license can be found in this doc.
http://www.cisco.com/en/US/prod/collateral/wireless/ps6302/ps8322/ps10315/data_sheet_c78-521631.html
Thanks,
Scott Fella
Sent from my iPhone

Similar Messages

5508 WLC License Transfer

I have four (4) 5508 wireless controllers that I would like to consolidate into one (1). I have 100 licenses on one (1) and 50 on the other three (3). Is there a way to pull the licenses off of the three (3) 50's and load them onto the 100 so I end up with one (1) controller with 250 licenses? Any help with this would be greatly appreciated. Thank you in advance.

you can go to: http://www.cisco.com/go/license
There you can attempt to 'rehost' the WLC licenses.
HTH,
Steve
Please remember to rate useful posts, and mark questions as answered

Cisco wlc license evaluation

I have a question
I have a wlc 5508 with license base to a capacity 100 AP. I have already registered 65 AP, and now I need to register in to wlc 57 AP more.
I would like to install a license of evaluation by 30 days. After that i'm going to purchase a new license to support all my APs.
Please could you tell me how many AP adder the capacity in the WLC the license of evaluation?
The license of evaluation are base or ap-count?
Regards
Ivan.

The controllers come with a 60 day license. Here is a link explaining licensing on the 5508
http://www.cisco.com/image/gif/paws/112926/5508-wlc-license.pdf
"Satisfaction does not come from knowing the solution, it comes from knowing why." - Rosalind Franklin
‎"I'm in a serious relationship with my Wi-Fi. You could say we have a connection."

How to Upgrade (legacy setup) 5508 wlc in HA

How to Upgrade 5508 wlc in HA (both the WLC with permanant AP license only, i.e, without HA license).
As per
http://www.cisco.com/c/en/us/td/docs/wireless/controller/technotes/7-5/High_Availability_DG.pdf
Both the WLCs have a valid AP Count license
• The CLI should be used to configure one WLC as the Standby WLC (as mentioned in the
configuration section) provided it satisfies the requirement of minimum permanent license count.
This condition is only valid for the 5500 WLC, where a minimum of 50 AP Permanent licenses are
needed to be converted to Standby. There is no restriction for other WLCs such as the WiSM2, 7500,
and 8500.
• AP-count license information will be pushed from Active to Standby.
• In the event of a switchover, the new Active WLC will operate with the license count of the previous
Active WLC and will start the 90-day countdown.
• The WLC configured as Secondary will not use its own installed license, and only the inherited
license from the active will be utilized.
• After 90-days, it starts nagging messages. It will not disconnect connected APs.
• With the new WLC coming up, HA SKU at the time of paring will get the AP Count:
– If the new WLC has a higher AP count than the previous, the 90-day counter is reset.
– If the new WLC has a lower AP count than the previous, the 90-day counter is not reset.
– After switchover to a lower AP count, the WLC offset timer will continue and nagging messages
will be displayed after time expiry.
My query is:
How can we upgrade the WLC version in this scenatio (where both the WLC have only permanent
AP License and not the HA license), Is it the same as done with HA controller or some othe procedure?
Pls comment.

Thanks Freerk for the comments,
But my query is, What would be the procedure for image upgradation after configuring HA between both the controllers (Primary-Secondary).
Will it be same as with the Primary-HA controller, or do i've to upgrade them individually and
re-configure HA again.

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,

5508 WLC upgrade

Looking to upgrade our 5508 WLC to the newest code AIR-CT5500-K9-7-2-103-0-FUS
We are currently running an older code 6.0.196.0
Are there any issues that I need to worry about with this upgrade ?
Do I need to upgrade the AP's at the same time ?
Any help would be appreciated.
Cheers
Dave

Looking to upgrade our 5508 WLC to the newest code AIR-CT5500-K9-7-2-103-0-FUS
Is the WLC going to be used in RUSSIA? That's what this code is for. If not, use the "AIR-CT5500-K9-7-2-103-0.aes" file instead.
Do I need to upgrade the AP's at the same time ?
The WLC will do it for you.

5508 WLC Upgrade steps

Single 5508 WLC with 8 x 1142 APs.
5508 is running FUS 1.3, software version 7.0.116.0, field recovery image 6.0.182.0.
I need to bring the software version up to at least 7.2.115 to support 2 new 2602 AP i need to install.
Question is; do I install FUS 1.9 then update my controller to 7.6.120 or do I need to do any intermediate steps?
This is my first time upgrading a WLC so I'm fresh and this is a production WLC.
Cheers

Hi Fisher.
Normally It doesn't matter as long as you get it done but make sure that you reboot the WLC before doing the next.
Here is the procedure for FUS upgrade:
http://www.cisco.com/c/en/us/td/docs/wireless/controller/release/notes/fus_rn_OL-31390-01.html
WLC Software upgrade Procedure:
http://www.cisco.com/c/en/us/support/docs/wireless-mobility/wireless-lan-wlan/68835-wlc-upgrade.html
Regards
Dont forget to rate helpful posts

WLC 5508 Evaluation License Expiry

Hi,
I have a customer who wants to do some WLC migration works. They have a spare 5508 (50 License) that they want to use to house their 100+ APs during the migration works as they are temporarily decommissioning the active 5508s. They have asked me whether they can get an extension to the evaluation license (I suggested the eval license may be the best option to get through this with minimal hassle) as they feel 60 days might not be long enough!
Thinking about it I read this in the WLC config guide regarding eval licenses:
"To prevent disruptions in operation, the controller does not switch licenses when an evaluation license expires. You must reboot the controller in order to return to a permanent license. Following a reboot, the controller defaults to the same feature set level as the expired evaluation license. If no permanent license at the same feature set level is installed, the controller uses a permanent license at another level or an unexpired evaluation license."
This suggests that the license will just continue to be active until a reboot? Is that correct, has anybody seen this in action. I have seen this sort of thing before with IOS-XE code where a feature is enabled as evaluation, and once it expires it doesn't stop the feature working, just sends loads of snmp traps complaining about not having the correct license level.
I would be interested if anyone knows what really happens once the eval expires and if the eval license count will remain active until WLC reboot.
Thanks
Rocky

Hi,
I have found another option for this unorthodox scenario. I just as an idea went to see if I could get a demo license for a 5508 I have in our lab (which currently has default eval license on it) from Cisco's license portal. Surprisingly it issued me a eval license, I installed it successfully onto the 5508! I now have 2x eval licenses, so in theory this will work for my customer as he can use this again for another 60 days!
I then thought I'd try again and see how far I can push it :) I then got a message saying:
We are unable to provide you with a license at this time.
You cannot obtain multiple trial licenses for the same UDI.
Ok, that makes sense, but I was able to add another eval on-top of the factory sent one.
What I will do is invoke it and see how it goes, and also I will then get to see what happens after 60 days.
Thoughts welcome.
Rocky

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.

AIR-CAP3702I booting up in mesh mode and not joining our 5508 WLC

I have a batch of 30+ AIR-CAP3702I-A-K9 APs that I need to setup but none of them are joining to the 5508 WLC and when I connect a console cable and view the output from the AP it shows that it is trying to initiate in mesh mode. I have read other forums that are showing that I need to put in the APs MAC address to a filter list on the WLC for it to show up and then I will be able to change it from mesh mode to local mode. The only issue I'm having with that solution is not knowing how it will affect my current production environment off of that 5508 WLC. I have 69 active production APs with clients working off them and there are no MAC filters currently in place on the WLC. By adding a MAC filter entry for the new APs would the WLC create an implicit deny for all other clients that don't have their MAC addresses entered?? If so is there another work around? Can the mode be changed via the CLI on the AP itself to make it local instead of mesh?

sh capwap client rcb
AdminState : ADMIN_ENABLED
SwVer : 7.6.1.118
NumFilledSlots : 2
Name : AP88f0.4290.7184
Location : default location
MwarName : xxxxx
MwarApMgrIp : x.x.x.x !<it has the correct name and IP of the WLC>
MwarHwVer : 0.0.0.0
ApMode : Bridge
ApSubMode : Not Configured
OperationState : JOIN
CAPWAP Path MTU : 576
LinkAuditing : disabled
ApRole : MeshAP
ApBackhaul : 802.11a
ApBackhaulChannel : 0
ApBackhaulSlot : 2
ApBackhaul11gEnabled : 0
ApBackhaulTxRate : 24000
Ethernet Bridging State : 0
Public Safety State : disabled
AP Rogue Detection Mode : Enabled
AP Tcp Mss Adjust : Disabled
AP IPv6 TCP MSS Adjust : Disabled
Predownload Status : None
Auto Immune Status : Disabled
RA Guard Status : Disabled
Efficient Upgrade State : Disabled
Efficient Upgrade Role : None
TFTP Server : Disabled
Antenna Band Mode : Unknown
802.11bg(0) Radio
ADMIN State = ENABLE [1]
OPER State = DOWN [1]
CONFIG State = UP [2]
HW State = UP [4]
Radio Mode : Bridge
GPR Period : 0
Beacon Period : 0
DTIM Period : 0
World Mode : 1
VoceraFix : 0
Dfs peakdetect : 1
Fragmentation Threshold : 2346
Current Tx Power Level : 0
Current Channel : 11
Current Bandwidth : 20
802.11a(1) Radio
ADMIN State = ENABLE [1]
OPER State = DOWN [1]
CONFIG State = UP [2]
HW State = UP [4]
Radio Mode : Bridge
GPR Period : 0
Beacon Period : 0
DTIM Period : 0
World Mode : 1
VoceraFix : 0
Dfs peakdetect : 1
Fragmentation Threshold : 2346
Current Tx Power Level : 1
Current Channel : 165
Current Bandwidth : 20
It is showing the following error on our WLC in the log file:
Tue Jul 15 14:01:26 2014
AAA Authentication Failure for UserName:88f042907184 User Type: WLAN USER
And here are some of the errors it's showing on the AP after bootup:
*Jul 15 17:47:30.471: %CAPWAP-5-SENDJOIN: sending Join Request to x.x.x.x
*Jul 15 17:47:31.003: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to down
*Jul 15 17:47:31.031: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to up
*Jul 15 17:47:31.039: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to down
*Jul 15 17:47:31.047: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset
*Jul 15 17:47:32.067: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to up
*Jul 15 17:47:33.067: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to up
*Jul 15 17:47:35.471: %CAPWAP-5-SENDJOIN: sending Join Request to x.x.x.x
*Jul 15 17:47:35.471: %DTLS-5-ALERT: Received WARNING : Close notify alert from x.x.x.x
*Jul 15 17:47:35.475: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to down
*Jul 15 17:47:35.483: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset
*Jul 15 17:47:36.475: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to down
*Jul 15 17:47:36.503: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to up
*Jul 15 17:47:37.503: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to up
*Jul 15 17:48:15.007: %MESH-3-TIMER_EXPIRED: Mesh Lwapp join timer expired
*Jul 15 17:48:15.007: %MESH-3-TIMER_EXPIRED: Mesh Lwapp join failed expired
*Jul 15 17:48:15.007: %MESH-6-LINK_UPDOWN: Mesh station 88f0.4290.7184 link Down
*Jul 15 17:48:17.007: %LINK-6-UPDOWN: Interface BVI1, changed state to down
*Jul 15 17:48:22.507: %LINEPROTO-5-UPDOWN: Line protocol on Interface BVI1, changed state to down
*Jul 15 17:59:10.099: %CAPWAP-3-ERRORLOG: Invalid event 31 & state 4 combination
*Jul 15 17:59:10.099: %CAPWAP-3-ERRORLOG: SM handler: Failed to process timer message. Event 31, state 4

WLC Firmware upgrade

I am working on a firmware upgrade on WLC 5508 and WLC 2100 from 7.2.111.3 to 7.4.121. I have 10 forign controllers and 2 anchor controllers. My question are:
(1) Should I upgrade the forign controllers first or anchor controllers first?
(2) Should I or do I need to upgrade Cisco NCS, 1.1.1.24, after the WLC firmware upgrade?
(3) SHould I or do I need to upgrade CIsco MSE to latest version?
Thanks,

(1) Should I upgrade the foreign controllers first or anchor controllers first?
Does not matter the order.
Make sure you upgrade the FUS to 1.9.0.0 version as well
http://www.cisco.com/en/US/docs/wireless/controller/release/notes/fus_rn_OL-31390-01.html
(2) Should I or do I need to upgrade Cisco NCS, 1.1.1.24, after the WLC firmware upgrade?
Refer the below link (table 4) compatibility matrix, you should have NCS/Prime 1.3.x
http://www.cisco.com/en/US/docs/wireless/controller/5500/tech_notes/Wireless_Software_Compatibility_Matrix.html#wp142297
(3) Should I or do I need to upgrade CIsco MSE to latest version?
Refer the table 7 of the above link, you should have MSE 7.4.121.0 as well for compatibility
http://www.cisco.com/en/US/docs/wireless/controller/5500/tech_notes/Wireless_Software_Compatibility_Matrix.html#wp142297
HTH
Rasika
**** Pls rate all useful responses ****

4500 R+E with sup 8 vs. (3850 stack + 5508 WLC)

I got into discussion about upgrade our 3750 stack, 4404 WLC, less than 50 APs (APs spread out over MPLS WAN). I'm planning to get 4510 R+ E with 2 sup 8, but another opinion talked me down to 3850 stack with 5508 WLC. Basically, his argument is 3850 stack can do everything 4500 R+E can do, plus it's not hulky as 4500. My argument is I like unify access since sup 8 built in WLC and we don't have to get 5508. I know there're more 4500 R+E and respect his argument. Does anyone has input on these setup giving pricing is not much different between setup.
Thanks
Kevin

In my honest opinion, if you are posted this solution here, you are smelling something is off. I hate to be a bearer of bad news. It is.
We went through the same exercise 2 years ago. We wanted to upgrade our legacy 3750/3750G to 3750X and we found out that if we were to get a stack of four (or more ) 3750X, it is cheaper (much, much cheaper) to get a 4510R+E bundle (with Sup7E included) and associated line cards on top. Just to note, the 3750X and 3850 have the same price. The Sup7E and Sup8E have the same price.
Don't ask me why your consultant wanted you to get 3850. I am refraining myself putting two theories in here.

Cisco ACS 5.5 with 5508 WLC.

Our current environment consists of 5508 WLCs authenticating to ACS 4.2.
I'm in a process of doing a clean build of ACS 5.5 (vmware) to replace the 4.2 installations. I do not want to migrate.
I have basic administration & Lobby Ambassador logins working. I now want to configure Layer 3 web auth for wireless access off Windows Domain accounts. I've found a document that discusses this, step by step, but it's for ACS 4.2 (which I know how to build), but nothing seems handy for ACS 5.5. Can anyone point me in that direction?
Thanks.

Are you using plain vanilla 5.0 or have any patches installed?
ACS 5.1 has new TACACS related functionaity including support for custom services and attributes. If these are needed for WLC support yo would need ti upgrade.
There may also have been relevant patch fixes since 5.0 timeframe but I can't find any specific relevant CDETS at this point

WLC code upgrade, WCS, ap_3600

i'm going to upgrade a 5508 wlc code from
7.0.116.0
to
7.1.91.0
to add 3600 series access points having it all manageable via WCS ver 7.0.230.0
it seems to be possible, as it is explained in the compatibility matrix found on
http://www.cisco.com/en/US/docs/wireless/controller/5500/tech_notes/Wireless_Software_Compatibility_Matrix.html
now I have to download the file to the controller...
AIR-CT5500-K9-SPECIAL-7-1-91-0.aes
(direct update possible)
before doing that I'd like to know if I will loose my configuration on the controller
i'm concerned about that because the release document is not clear:
- We highly recommend that you back up your controller's configuration files prior to upgrading the controller software. Otherwise, you must manually reconfigure the controller.
- For busy networks, controllers on high utilization, or small controller platforms it is advisable to disable the 802.11a/b/g networks as a precautionary measure.
- Step 5 Disable any WLANs on the controller.
- Step 19 Re-enable the WLANs......
- Step 22 If desired, reload your latest configuration file to the controller. (reload config after reenabling wlans????? why???)
so will I loose my configuration?
what is Field Upgrade Software? should i use that instead?
another controller another question .....: a cisco wlc 2100
found 2 update files
AIR-WLC2100-K9-7-0-230-0-ER.aes
AIR-WLC2100-K9-7-0-230-0.aes
why 2 update files this time? what file to update first?
thank you in advance for your answers

The 5508 has two files when you go to 7.2, which I would for the 3600. You'll also want to download and install the FUS image.
the 'legacy' WLC, like the 2100, have the .aes which is the OS for the WLC. The -ER is an Emergency Recovery image, it's waht you get when you break the boot cycle.
HTH,
Steve
Please remember to rate useful posts, and mark questions as answered

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

5508 WLC license upgrade ?

Similar Messages

Maybe you are looking for