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

Similar Messages

WLC 5508 HA license

Hi,
We have 2 WLC and each WLC have 100 wap license. If we make them into a High availability pair do we get 200 wap licences?
Thanks,

Sorry I didn't understand "In your case 5508 would max out to 500".
We have 2 WLC each have license for 100 LWAP and they are not in HA pair now. When I will join the 2 WLC as a HA WLC, then I will have license for 100 LWAP or both WLC licences will add up and we will have 200 LWAP license in HA WLC
Now if suppose WLC-1 primary fails and we have 200 LWAP attached with it, in this scenario, do the WLC-2 can support the 200 LWAPs?
Thanks

Redundant WLC-5508 Deployment Licensing

I am deploying a redundant WLC-5508. We purchased 2, each with the base license of 50 AP's. After the survey, we determined that we need an additional 9 access points. Do we have to purchase 2 upgrade licenses? If so, can we get them in increments of 5, similar to the 2500 series WLC's?

After the survey, we determined that we need an additional 9 access points. Do we have to purchase 2 upgrade licenses?
Yes. You need to purchase TWO (2) licenses.
Here's the difficulty with your scenario:
For unknown reason, someone in Cisco has determine that, in your case, you have an appliance with 50 bases license and you need to add 9 WAPs. Logic dictates that you could potentially get a 25-base license right? Not in this case. Your minimum license you can get is 100-base license.
Because of this, I would recommend that you raise a TAC Case and potentially get both of the WLC RMA-ed. Tell TAC that you want to get a 25-base license ADDED to both units. (Bringing the total to 75.)
Message was edited by: Leo Laohoo

Updating Evaluation License for WLCS 3.5

Hi,
I am still evaluating WLCS 3.5 and would like to obtain a new evaluation
license (my existing one ran out today). According to the docs this should
just involve downloading another license and running UpdateLicense.cmd from
the BEA_HOME directory where both the new and old license files reside.
However, doing this has not had any noticeable effect (ie I can't start the
server). The license.bea file still has today as the expiration date. Also
do I need to upgrade my WLS6.0 license separately as well? A quick response
would be appreciated.
Regards
Laura Allen

Incidently, I can start the underlying WLS6.0 ok - I thought they used the
same license file? The error I get when attempting to start WLCS is as
follows:
<14-Aug-01 15:48:44 BST> <Error> <COMMERCE_SERVER_FRAMEWORK> <LOG_FATAL:
WebLogi
c Personalization Server: Core Server: 3.5 license error.>
Press any key to continue . . .
"Laura Allen" <[email protected]> wrote in message
news:3b793430$[email protected]..
Hi,
I am still evaluating WLCS 3.5 and would like to obtain a new evaluation
license (my existing one ran out today). According to the docs thisshould
just involve downloading another license and running UpdateLicense.cmdfrom
the BEA_HOME directory where both the new and old license files reside.
However, doing this has not had any noticeable effect (ie I can't startthe
server). The license.bea file still has today as the expiration date.Also
do I need to upgrade my WLS6.0 license separately as well? A quickresponse
would be appreciated.
Regards
Laura Allen

WLC 5508 Base-Ap-Count License Inactive

Hello,
I have two licenses on a WLC 5508 "base-ap-count permenant 100 Count medium Inactive" and "base-ap-count permanent 150 count medium In Use". Should both the 100 and 150 be added up to make 250? Why is the 100 license inactive? There is no option to make it active.

Here is my status:
show license summary
License Store: Primary License Storage
StoreIndex: 0 Feature: base-ap-count Version: 1.0
License Type: Permanent
License State: Inactive
License Count: 5 / 0 (Active/In-use)
License Priority: Medium
License Store: Primary License Storage
StoreIndex: 1 Feature: wlc-virtual Version: 1.0
License Type: Permanent
License State: Active, In Use
License Count: 1 /1 (Active/In-use)
License Priority: Medium
License Store: Primary License Storage
StoreIndex: 2 Feature: base-ap-count Version: 1.0
License Type: Permanent
License State: Inactive
License Count: 10 / 0 (Active/In-use)
License Priority: Medium
License Store: Primary License Storage
StoreIndex: 3 Feature: base-ap-count Version: 1.0
License Type: Permanent
License State: Active, In Use
License Count: 15 /15 (Active/In-use)
License Priority: Medium
Both 5 license and 10 license have the dropdown arrow available to delete. Is it ok to delete them?
vWLC came with 5 AP then I added two 5 AP licenses.

Format WLC-5508 Flash and IOS recovery guide

Dear Support Cummunity,
i have a WLC-5508 where by i am unable to join any kind of AIR-LAP1x00 Access-Points.
They can't join in the local management ip of the controller within same L2 or via routed network thereby using the APs CLi by
"lwapp ap controller ip addr xx.xx.xx.xx".
I upgraded from: 6.0.188.0 to
AIR-CT5500-K9-6-0-199-0.aes
AIR-CT5500-K9-7-0-98-0.aes
thereby catching the same logs every time.
The main error message from the WLCs log i catched first is:
"maximum number of downloads (0) exceeded"
*sntpReceiveTask: Jul 16 07:40:58.827: %LOG-3-Q_IND: capwap_ac_sm.c:1683 Ignoring discovery request from AP 00:26:99:86:c9:b9 - maximum number of downloads (0) exceeded
*spamApTask1: Jul 16 07:40:58.343: %CAPWAP-3-DISC_MAX_DOWNLOAD: capwap_ac_sm.c:1683 Ignoring discovery request from AP 00:26:99:86:c9:b9 - maximum number of downloads (0) exceeded
*sntpReceiveTask: Jul 16 07:40:48.822: %LOG-3-Q_IND: capwap_ac_sm.c:1683 Ignoring discovery request from AP 00:26:99:86:c9:b9 - maximum number of downloads (0) exceeded
*spamApTask1: Jul 16 07:40:48.342: %CAPWAP-3-DISC_MAX_DOWNLOAD: capwap_ac_sm.c:1683 Ignoring discovery request from AP 00:26:99:86:c9:b9 - maximum number of downloads (0) exceeded
Later on i found some more logging infos:
*Aug 16 04:12:07.188: %SYSTEM-3-FILE_READ_FAIL: nvstore.c:422 Failed to read configuration file 'cliWebInitParms.cfg'
*Aug 16 04:12:07.188: %CNFGR-3-INV_COMP_ID: cnfgr.c:2080 Invalid Component Id : Unrecognized (81) in cfgConfiguratorInit.
*Aug 16 04:12:07.139: %SYSTEM-3-FILE_READ_FAIL: nvstore.c:422 Failed to read configuration file 'rfidInitParms.cfg'
*Aug 16 04:12:07.126: %SYSTEM-3-FILE_READ_FAIL: nvstore.c:422 Failed to read configuration file 'dhcpParms.cfg'
*Aug 16 04:12:07.113: %SYSTEM-3-FILE_READ_FAIL: nvstore.c:422 Failed to read configuration file 'bcastInitParms.cfg'
*Aug 16 04:12:07.047: %SYSTEM-3-FILE_READ_FAIL: nvstore.c:422 Failed to read configuration file 'rrmInitParms.cfg'
*Aug 16 04:12:06.906: %SYSTEM-3-FILE_READ_FAIL: nvstore.c:422 Failed to read configuration file 'apfInitParms.cfg'
*Aug 16 04:12:06.801: %MM-3-MEMBER_ADD_FAILED: mm_dir.c:860 Could not add Mobility Member. Reason: IP already assigned, Member-Count:1,MAC: 00:00:00:00:00:00, IP: 0.0.0.0
*Aug 16 04:12:06.599: %SYSTEM-3-FILE_READ_FAIL: nvstore.c:422 Failed to read configuration file 'mmInitParms.cfg'
*Aug 16 04:12:06.589: %SYSTEM-3-FILE_READ_FAIL: nvstore.c:422 Failed to read configuration file 'aaaapiInitParms.cfg'
*Aug 16 04:12:06.587: %SYSTEM-3-FILE_READ_FAIL: nvstore.c:422 Failed to read configuration file 'pemInitParms.cfg'
*Aug 16 04:12:06.474: %SYSTEM-3-FILE_READ_FAIL: nvstore.c:422 Failed to read configuration file 'dot1xInitParms.cfg'
*Aug 16 04:12:06.446: %SYSTEM-3-FILE_READ_FAIL: nvstore.c:422 Failed to read configuration file 'capwapInitParms.cfg'
*Aug 16 04:12:06.301: %SYSTEM-3-FILE_READ_FAIL: nvstore.c:422 Failed to read configuration file 'spamInitParms.cfg'
*Aug 16 04:12:06.298: %LICENSE-1-REQUEST_FAILED: license_syslog_notify:564 License request for feature base-ap-count 1.0 failed in this device, UDI=AIR-CT5508-K9:FCW1341L530
*Aug 16 04:12:05.221: %SSHPM-3-FREAD_FAILED: sshpmlscscep.c:1268 Error reading file /mnt/application/lscca_pem.crt
*Aug 16 04:11:46.121: %SYSTEM-3-FILE_READ_FAIL: nvstore.c:422 Failed to read configuration file 'sshpmInitParms.cfg'
as for me it looks like my filesystem is kind of corrupted since several files can not be read.
now at power up one can choose 5 in order to format flash/disk. unfortuanitly i have not found some documentation about formatting flash procedures.
please guide me to the appropriate documentation.
============================================================
Boot Loader Menu
============================================================
1. Run primary image (7.0.98.0) - Active
2. Run backup image (6.0.199.0)
3. Change active boot image
4. Clear configuration
5. Format FLASH Drive
6. Manually update images
Enter selection: 5
Launching...
WARNING! Choose this option may render the device warranty invalid
and/or make the device unusable.
what are my next steps going to be from here in order to format/restore?
thank you
colin

(Cisco Controller) >show sys
Incorrect usage. Use the '?' or key to list commands.
(Cisco Controller) >show sysinfo
Manufacturer's Name.............................. Cisco Systems Inc.
Product Name..................................... Cisco Controller
Product Version.................................. 7.0.98.0
Bootloader Version............................... 1.0.1
Field Recovery Image Version..................... N/A
Firmware Version................................. FPGA 1.3, Env 1.6, USB console 1.27
Build Type....................................... DATA + WPS
System Name...................................... WLC
System Location..................................
System Contact...................................
System ObjectID.................................. 1.3.6.1.4.1.9.1.1069
IP Address....................................... 192.168.11.16
Last Reset....................................... Software reset
System Up Time................................... 0 days 0 hrs 4 mins 41 secs
System Timezone Location......................... (GMT +1:00) Amsterdam, Berlin, Rome, Vienna
Current Boot License Level....................... base
Current Boot License Type........................ Permanent
Next Boot License Level.......................... base
Next Boot License Type........................... Permanent
Configured Country............................... CH - Switzerland
--More-- or (q)uit
Operating Environment............................ Commercial (0 to 40 C)
Internal Temp Alarm Limits....................... 0 to 65 C
Internal Temperature............................. +39 C
External Temperature............................. +25 C
Fan Status....................................... OK
State of 802.11b Network......................... Enabled
State of 802.11a Network......................... Enabled
Number of WLANs.................................. 1
Number of Active Clients......................... 0
Burned-in MAC Address............................ 00:24:97:CE:E0:40
Power Supply 1................................... Present, OK
Power Supply 2................................... Absent
Maximum number of APs supported.................. 0 ç ???
why is it that it tells me i've got 0 APs supported on a permanent base license witch ships per default?
i tried to install a evaluation License but without success..

Converged Access Design Help (Catalyst 3850 and WLC 5508...Mobility Oracle)

Hello,
I am an engineer working with a Cisco Gold Partner in Saudi Arabia. We have a large university as our client where they are constructing a new
building and require our services to build the network infrastructure. Therefore, we are to implement the routing and switching infrastructure as
well as the Wireless solution.
At present, I have no issues in implementing the R&S infrastructure as it is very straight forward but it has implications on the deployment of
the wireless solution which I explain further below. The R&S infrastructure comprises of the typical Core, Distribution, and Access layers and we
are focusing on the local distribution and access switches with regards to the new building. The client has a converged Layer 3 network spanning
from distribution layer to core layer and they are running EIGRP for this convergence. This is not a problem and has already been implemented.
Yet, the challenge arises in deploying the WLAN infrastructure. The client already has a Cisco WLAN infrastructure in place where they have a
large number of LAPs that are registered with their controllers in the Data Center. They have two WLC 5508 where one is the Primary and the other
the Secondary. The local distribution switch to which the WLC are connected also is the gateway for the SVIs for the SSIDs that are configured on
the controllers. This means that once the packets from the AP come in to the WLC, they are tagged with the correct VLAN and sent to the directly
connected distribution switch which then routes it into the rest of the Layer 3 network. Interestingly, the WLC 5508 are running AireOS 7.6 and
support the "New Mobility" feature. The two controllers have formed a Mobility Group (MG) between each other.
Now, the new building will have two Catalyst 3850 switches installed where each one has a total of 40 AP licenses pre-installed and activated
i.e. a total of 80 APs can be supported by the two switches. A total of 67 LAPs will be deployed in the new building which can be accommodated
between the two switches and their integrated controller.
Yet, based on my understanding and research about Converged Access is that, ideally, the Catalyst 3850 will only run the Mobility Agent (MA)
feature while a central controller would provide the Mobility Controller (MC) service. unfortunately, there are not enough licenses on the
existing WLC 5508 nor can we migrate the new licenses that will facilitate such a split deployment.
This means that I would need to configure the two Catalyst 3850 as independent MC and form a MG between them. I have done this and tested this
already and the mobility is working fine. But my concern is not about getting the Catalyst 3850 to work as this is simple but rather it is
focused on creating a common Mobility Domain (MD) so that clients can roam from this new building to the rest of the campus while maintaining the
state of their connections to the WLAN infrastructure.
To make things more complicated, since the new building will have its own Layer 3 distribution switch and the Catalyst 3850 switches will connect
to this distribution switch, it means that new VLANs and SVIs need to be created for the SSIDs broadcast in the new building. This means that new
subnets need to be assigned to the SSIDs.
As such, I have the following questions:
Q1) If we create new SVIs for the SSIDs (same SSIDs names will be used in the new building as in the rest of the university campus) this means
that new subnets will be assigned to these SSIDs. Now, I believe I have two options...one is to make the new Catalyst 3850s to be in the same MG
as the existing WLC 5508 which then cater for Layer 3 client roaming or I have to treat this as a totally seperate WLAN network and follow on to
the solution as per the next question. Please advise which is a better option?
Q2) I could create separate MG i.e. the new building Catalyst 3850s can be in one MG and the existing controllers can be in another MG. I can
then have one of the existing WLC 5508 (the primary one) to run the Mobility Oracle (MO) feature so as to create a single Mobility Domain (MD).
Would this facilitate in Layer 3 client roaming and RRM for all the controllers in the same MD?
Q3) If I do create a MD, how is this accomplished in such an environment since the documentation is severely limited in this regard?
Please advise at your earliest. To assist further, I have attached a topology diagram which may aid in explaining the situation with more
clarity. If these things are clarified, I will be better able to wrap my head around the technology and in turn service my clients better.
Regards,
Amir

Hi Amir,
Q1) If we create new SVIs for the SSIDs (same SSIDs names will be used in the new building as in the rest of the university campus) this means that new subnets will be assigned to these SSIDs. Now, I believe I have two options...one is to make the new Catalyst 3850s to be in the same MG as the existing WLC 5508 which then cater for Layer 3 client roaming or I have to treat this as a totally seperate WLAN network and follow on to the solution as per the next question. Please advise which is a better option?
I would configure them in the same mobility group. Also configure same SPG for those two 3850 stacks if users are frequently roaming within these two buildings.
Q2) I could create separate MG i.e. the new building Catalyst 3850s can be in one MG and the existing controllers can be in another MG. I can then have one of the existing WLC 5508 (the primary one) to run the Mobility Oracle (MO) feature so as to create a single Mobility Domain (MD). Would this facilitate in Layer 3 client roaming and RRM for all the controllers in the same MD?
MO is not required (it is only for very large scale deployments)
Q3) If I do create a MD, how is this accomplished in such an environment since the documentation is severely limited in this regard?
Yes, documents are hard to find :(
These notes may be useful to you based on my experience. I am running IOS-XE 3.6.1 in my production.
http://mrncciew.com/2014/05/06/configuring-new-mobility/
http://mrncciew.com/2013/12/14/3850ma-with-5760mc/
HTH
Rasika
*** Pls rate all useful responses ****

WLC 5508 running 7.4.110.0 unable to tftp upload config from controller

Hi,
Two WLC 5508 running identical code version. One is 50 license Primary, the second is HA. Identical config on both. HA WLC can upload its config to the TFTP or FTP server but Primary cannot. The operation fails for both CLI and GUI and for different protocols i.e. TFTP, FTP.
#### Primary Controller
(Cisco Controller) >show sysinfo
Manufacturer's Name.............................. Cisco Systems Inc.
Product Name..................................... Cisco Controller
Product Version.................................. 7.4.110.0
Bootloader Version............................... 1.0.20
Field Recovery Image Version..................... 7.6.95.16
Firmware Version................................. FPGA 1.7, Env 1.8, USB console 2.2
Build Type....................................... DATA + WPS
System Name...................................... PRODWC7309
System Location..................................
System Contact...................................
System ObjectID.................................. 1.3.6.1.4.1.9.1.1069
Redundancy Mode.................................. Disabled
IP Address....................................... 10.1.30.210
Last Reset....................................... Power on reset
System Up Time................................... 18 days 18 hrs 51 mins 35 secs
System Timezone Location......................... (GMT+10:00) Sydney, Melbourne, Canberra
System Stats Realtime Interval................... 5
System Stats Normal Interval..................... 180
Configured Country............................... AU - Australia
Operating Environment............................ Commercial (0 to 40 C)
--More-- or (q)uit
Internal Temp Alarm Limits....................... 0 to 65 C
Internal Temperature............................. +34 C
External Temperature............................. +17 C
Fan Status....................................... OK
State of 802.11b Network......................... Enabled
State of 802.11a Network......................... Enabled
Number of WLANs.................................. 8
Number of Active Clients......................... 138
Memory Current Usage............................. Unknown
Memory Average Usage............................. Unknown
CPU Current Usage................................ Unknown
CPU Average Usage................................ Unknown
Burned-in MAC Address............................ 3C:08:F6:CA:52:20
Power Supply 1................................... Present, OK
Power Supply 2................................... Present, OK
Maximum number of APs supported.................. 50
(Cisco Controller) >debug transfer trace enable
(Cisco Controller) >transfer upload start
Mode............................................. TFTP
TFTP Server IP................................... 10.1.22.2
TFTP Path........................................ /
TFTP Filename.................................... PRODWC7309-tmp.cfg
Data Type........................................ Config File
Encryption....................................... Disabled
*** WARNING: Config File Encryption Disabled ***
Are you sure you want to start? (y/N) Y
*TransferTask: Jun 02 10:41:15.183: Memory overcommit policy changed from 0 to 1
*TransferTask: Jun 02 10:41:15.183: RESULT_STRING: TFTP Config transfer starting.
TFTP Config transfer starting.
*TransferTask: Jun 02 10:41:15.183: RESULT_CODE:1
*TransferTask: Jun 02 10:41:24.309: Locking tftp semaphore, pHost=10.1.22.2 pFilename=/PRODWC7309-tmp.cfg
*TransferTask: Jun 02 10:41:24.393: Semaphore locked, now unlocking, pHost=10.1.22.2 pFilename=/PRODWC7309-tmp.cfg
*TransferTask: Jun 02 10:41:24.393: Semaphore successfully unlocked, pHost=10.1.22.2 pFilename=/PRODWC7309-tmp.cfg
*TransferTask: Jun 02 10:41:24.394: tftp rc=-1, pHost=10.1.22.2 pFilename=/PRODWC7309-tmp.cfg
pLocalFilename=/mnt/application/xml/clis/clifile
*TransferTask: Jun 02 10:41:24.394: RESULT_STRING: % Error: Config file transfer failed - Unknown error - refer to log
*TransferTask: Jun 02 10:41:24.394: RESULT_CODE:12
*TransferTask: Jun 02 10:41:24.394: Memory overcommit policy restored from 1 to 0
% Error: Config file transfer failed - Unknown error - refer to log
(Cisco Controller) >show logging
*TransferTask: Jun 02 10:41:24.393: #UPDATE-3-FILE_OPEN_FAIL: updcode.c:4579 Failed to open file /mnt/application/xml/clis/clifile.
*sshpmReceiveTask: Jun 02 10:41:24.315: #OSAPI-3-MUTEX_FREE_INFO: osapi_sem.c:1087 Sema 0x2b32def8 time=142 ulk=1621944 lk=1621802 Locker(sshpmReceiveTask sshpmrecv.c:1662 pc=0x10b07938) unLocker(sshpmReceiveTask sshpmReceiveTaskEntry:1647 pc=0x10b07938)
-Traceback: 0x10af9500 0x1072517c 0x10b07938 0x12020250 0x12080bfc
*TransferTask: Jun 02 10:39:01.789: #UPDATE-3-FILE_OPEN_FAIL: updcode.c:4579 Failed to open file /mnt/application/xml/clis/clifile.
*sshpmReceiveTask: Jun 02 10:39:01.713: #OSAPI-3-MUTEX_FREE_INFO: osapi_sem.c:1087 Sema 0x2b32def8 time=5598 ulk=1621801 lk=1616203 Locker(sshpmReceiveTask sshpmrecv.c:1662 pc=0x10b07938) unLocker(sshpmReceiveTask sshpmReceiveTaskEntry:1647 pc=0x10b07938)
-Traceback: 0x10af9500 0x1072517c 0x10b07938 0x12020250 0x12080bfc
#### HA Controller
(Cisco Controller) >show sysinfo
Manufacturer's Name.............................. Cisco Systems Inc.
Product Name..................................... Cisco Controller
Product Version.................................. 7.4.110.0
Bootloader Version............................... 1.0.20
Field Recovery Image Version..................... 7.6.95.16
Firmware Version................................. FPGA 1.7, Env 1.8, USB console 2.2
Build Type....................................... DATA + WPS
System Name...................................... PRODWC7310
System Location..................................
System Contact...................................
System ObjectID.................................. 1.3.6.1.4.1.9.1.1069
Redundancy Mode.................................. Disabled
IP Address....................................... 10.1.31.210
Last Reset....................................... Software reset
System Up Time................................... 18 days 19 hrs 1 mins 27 secs
System Timezone Location......................... (GMT+10:00) Sydney, Melbourne, Canberra
System Stats Realtime Interval................... 5
System Stats Normal Interval..................... 180
Configured Country............................... AU - Australia
Operating Environment............................ Commercial (0 to 40 C)
--More-- or (q)uit
Internal Temp Alarm Limits....................... 0 to 65 C
Internal Temperature............................. +34 C
External Temperature............................. +17 C
Fan Status....................................... OK
State of 802.11b Network......................... Enabled
State of 802.11a Network......................... Enabled
Number of WLANs.................................. 4
Number of Active Clients......................... 0
Memory Current Usage............................. Unknown
Memory Average Usage............................. Unknown
CPU Current Usage................................ Unknown
CPU Average Usage................................ Unknown
Burned-in MAC Address............................ 3C:08:F6:CA:53:C0
Power Supply 1................................... Present, OK
Power Supply 2................................... Present, OK
Maximum number of APs supported.................. 500
(Cisco Controller) >debug transfer trace enable
(Cisco Controller) >transfer upload start
Mode............................................. FTP
FTP Server IP.................................... 10.1.22.2
FTP Server Port.................................. 21
FTP Path......................................... /
FTP Filename..................................... 10_1_31_210_140602_1050.cfg
FTP Username..................................... ftpuser
FTP Password..................................... *********
Data Type........................................ Config File
Encryption....................................... Disabled
*** WARNING: Config File Encryption Disabled ***
Are you sure you want to start? (y/N) y
*TransferTask: Jun 02 10:51:31.278: Memory overcommit policy changed from 0 to 1
*TransferTask: Jun 02 10:51:31.278: RESULT_STRING: FTP Config transfer starting.
FTP Config transfer starting.
*TransferTask: Jun 02 10:51:31.278: RESULT_CODE:1
*TransferTask: Jun 02 10:52:05.468: ftp operation returns 0
*TransferTask: Jun 02 10:52:05.477: RESULT_STRING: File transfer operation completed successfully.
*TransferTask: Jun 02 10:52:05.477: RESULT_CODE:11
File transfer operation completed successfully.
Not upgrading to 7.4.121.0 because of bug CSCuo63103. Have not restarted the controller yet.
Any one else had this issue ? Is there a workaround ?
Thanks,
Rick.

Thanks Stephen, In my deployments of 7.4.110.0 version I have not seen this issue so may be controller reboot will fix it (we do have HA to minimize the impact). I will keep the thread updated with findings and may request TAC for the special release 7.4.121.0 if the still not happy with 7.4.110.0
Rick.

WLC 5508 7.4.X - N+1

Hi,
I don't undestand this document
http://www.cisco.com/c/en/us/td/docs/wireless/technology/hi_avail/N1_High_Availability_Deployment_Guide/N1_HA_Overview.html
How can the third 5508 (suport max 500 AP) backup all other WLC ? n+1 how ?
With secondary wlc configured in HA-SKU (without AP SSO) the 500 licenze are permanent ?
who can explain me.. this is a document bug ??

What they're describing is HA N+1, not HA 1:1 AP SSO. This option, which is "NON-AP-SSO", allows you to use an HA-SKU or > -50-k9 SKU coverted, to operate as a dedicated +1 WLC in HA. When using this configuration, this WLC allows the use of the "hardware maximum" of the device: Thus 500 APs for WLC 5508, or 1000APs for a WISM2 (as an example). Since this WLC can wait as a backup to multiple WLCs, that's why it's not capable of the AP SSO, which requires a 1:1 pairing of the HA WLC with an Active HA WLC.
When using the HA N+1 the WLC acts the same as the pre AP-SSO "HA" concept; where you had Primary, Secondary Tertiary configs on your APs (which you may still have). All it is saying is that the N+1 HA WLC can act as one of these Secondary/Tertiary WLCs, much like a WLC you had licenesed for 250 or 500 APs could do previously.
In the past you would use, lets say a 250 WLC AP as this backup WLC. Many people were frustrated that they had to have a $60,000 WLC just sitting there "waiting for something to fail". But that's what it did. If a WLC failed, lets say one with 100 APs, this backup WLC would take on the APs and use 100 of it's 250 AP license count. If additional WLCs failed, the process continued until this backup WLC was filled.
The idea of using the HA-SKU in an N+1 is that while yes, you don't get the 1:1 AP SSO configuration, you are getting more bang for your buck in that this WLC can sit as a backup (as it did in the past) but it can accept up to the maximum it's hardware can handle in terms of AP count, not only what it was permanently licensed for. Rather than spending $100,00 on a 500 AP count WLC to backup your 2x250 AP count WLCs, why not look at a $50,000 HA-SKU that can "handle" up to 500 APs.
So given this scenario, this WLC is "backuping up all other WLCs" for whom it is a Secondary/Tertiary WLC backup.
As far as the HA-SKU "licenese", it's not "permanent" per se. With an HA SKU in N+1 you have a 90 day timer which will then "nag you" (via console) that this HA WLC is not truly intended to permanently house these APs. The idea is that if the Primary WLC failed, you would get it back online and then move your APs back to where they belong and return the HA N+1 WLC back to 0 APs.

WLC 5508 HA Problem Soft.ver 7.4.100

Dear Support,
we are using two WLC 5508 software ver.7.4.100 with first 50AP license and in the next day we add 50AP license again to the primary WLC. when we activate HA base in the following guiden http://www.cisco.com/c/en/us/td/docs/wireless/controller/technotes/7-5/High_Availability_DG.html but when we doing test the failover we found a couple log message on the Secondary WLC like below and not for long time all AP on the Secondary WLC was drop off.
1. DP Critical Error
2. *RRM-DCLNT-2_4: May 23 07:43:53.204: #RRM-3-RRM_LOGMSG: rrmTables.c:682 RRM LOG: Could not retrieve RRM Coverage Measurement DataKey BSSID:34:db:fd:dd:3e:20,Key SlotId:0
*RRM-DCLNT-2_4: May 23 07:43:53.164: #RRM-3-RRM_LOGMSG: rrmTables.c:682 RRM LOG: Could not retrieve RRM Coverage Measurement DataKey BSSID:34:db:fd:dd:3e:20,Key SlotId:0
*RRM-DCLNT-2_4: May 23 07:43:52.854: #RRM-3-RRM_LOGMSG: rrmTables.c:682 RRM LOG: Could not retrieve RRM Coverage Measurement DataKey BSSID:2c:36:f8:72:fc:c0,Key SlotId:0
I also send a complete log for both problem above and enclose it with pdf file. need you advice and assistance,
regard, afriansyah

I agree go to version 7.4.121.0 I has some strange issues on prior releases. Personally I am running 7.6.120.0 right now but that's mainly due to support for the 3702 access points.
http://www.cisco.com/c/en/us/td/docs/wireless/controller/technotes/7-5/High_Availability_DG.html#pgfId-74573
that's a good guide just to double check yourself just in case. -

Upgrade WLC 5508 Ver. 7.0.98.0 to Ver 7.6.110.0

i will upgrade WLC 5508 Ver 7.0.98.0 with License 50 AP. to Ver 7.6.110.0 will it ask to install license ?

No, It will not ask for again.
Just upgrade the software.
Regards
Dont forget to rate helpful posts

WLC 5508 in HA pair (7.4.121.0) sudden reload

I have a pair of WLC 5508 in HA pair running version 7.4.121.0, last week I have two sudden reload on my active WLC. Here's the error from my syslog server on the first sudden reload. The second reload has almost the same logs.
10.x.x.234 - active
10.x.x.237 - standby
2014-01-30 17:52:20 Local0.Error 10.x.x.237 WLC-HA01: *rmgrMain: Jan 30 17:52:24.498: #RMGR-3-RED_HEARTBEAT_TMOUT: rmgr_main.c:242 rmgrTmoHeartbeat: Recved GW ping count 6 phyMgr ping count 0.
2014-01-30 17:52:20 Local0.Emerg 10.x.x.237 WLC-HA01: *rmgrMain: Jan 30 17:52:24.555: #RMGR-0-RED_HA_RELOAD: rmgr_utils.c:198 System reboot: reason: category Sanity check object Self
2014-01-30 17:52:21 Local0.Emerg 10.x.x.234 WLC-HA01: *rmgrMain: Jan 30 17:52:24.989: #RMGR-0-RED_HA_RELOAD: rmgr_utils.c:188 System reboot: reason: category Peer reload req object Peer
2014-01-30 17:52:21 Local0.Alert 10.x.x.234 WLC-HA01: *dtlArpTask: Jan 30 17:52:25.106: #DTL-1-IP_CONFLICT_DETECTED: dtl_net.c:4857 Network device with mac addr 7c:ad:74:8d:6b:0f using IP address of local interface
Cisco TAC recommends to disable monitoring the default gateway.
--> config redundancy management-gateway-failover disable
I was wondering if someone has the issue with what I have.
Second issue I have is when it fails over to the standby WLC, I do get a web-auth certificate error from the WLC when clients login. This only happens after a sudden reload. If I do a redundancy force-switchover during maintenance window, the certificate error doesn't show up. To fix the certificate error I have to bounce both WLCs one after the other.
Thanks in advance.

Hi,
I exeprienced a reload problem in standby WLC, with HA in release 7.6.100.0.
I use a dedicated VLAN to transport the redundancy sync and info, 'cause the two WLCs are in different buildings.
The standby WLC reload continuously 'cause it doesn,t find the default gateway.
(Cisco Controller-Standby) >show redundancy summary
            Redundancy Mode = SSO ENABLED
                Local State = STANDBY HOT
                 Peer State = ACTIVE
                       Unit = Secondary - HA SKU (Inherited AP License Count = 500)
                    Unit ID = 00:06:F6:DB:E3:E0
           Redundancy State = SSO (Both AP and Client SSO)
               Mobility MAC = 58:8D:09:CD:81:C0
Management Gateway Failover = ENABLED (Management GW failover would be operational in few moments)
Average Redundancy Peer Reachability Latency = 621 usecs
Average Management Gateway Reachability Latency = 0 usecs
Redundancy Management IP Address................. 40.231.36.6
Peer Redundancy Management IP Address............ 40.231.36.5
Redundancy Port IP Address....................... 169.254.36.6
Peer Redundancy Port IP Address.................. 169.254.36.5
Rebooting as default GW is not reachable from Standby Controller
Restarting system. Reason: Default Gateway is not reachable ..
The problem is that the WLC tries to ping the DGW using the primary IP management address belonging to the active WLC, so we have duplicated IP problem, ARP problem and so on .....
The standby WLC should use the redundancy managemet address to ping the default gateway, instead the primary IP management address!!!!!!
So the workaround is the CLI command :
config redundancy management-gateway-failover disable
on the primary WLC, via console or in SSH.
When the standby will reload it will inherit the config from the active primary WLC
(Cisco Controller-Standby) >show redundancy summary
            Redundancy Mode = SSO ENABLED
                Local State = STANDBY HOT
                 Peer State = ACTIVE
                       Unit = Secondary - HA SKU (Inherited AP License Count = 500)
                    Unit ID = 00:06:F6:DB:E3:E0
           Redundancy State = SSO (Both AP and Client SSO)
               Mobility MAC = 58:8D:09:CD:81:C0
Management Gateway Failover = ENABLED (Management GW failover is disabled as it is DISABLED on the Peer)
Average Redundancy Peer Reachability Latency = 666 usecs
Average Management Gateway Reachability Latency = 0 usecs
Redundancy Management IP Address................. 40.231.36.6
Peer Redundancy Management IP Address............ 40.231.36.5
Redundancy Port IP Address....................... 169.254.36.6
Peer Redundancy Port IP Address.................. 169.254.36.5
The workaround works in my experience.

WLC 5508 LOAD BALANCING APs to HA-SSO

Do somebody knows what´s going to happen about configuration when you migrate 2-WLC 5508 giving wireless services correctly, using load balancing with the APs to HA-SSO mode???
At this time we have some AP groups in WLC1 and in WLC2 we don´t have the AP groups, what´s going to happen with the configuration of both WLCs, both configuration are going to be merged??
REGARDS

When you covert the pair into SSO, all the APs will go to the ACTIVE unit. No unit will "live" in the standby unit because this unit will "share" the AP-support license between the two.
This is the first step you need to get sorted. Send an email to [email protected] and give them the exact details of what you want to do (i. e. AP SSO) and then provide the serial number of your nominated active WLC and the serial number of your nominated standby WLC.

WLC 5508 rebooted but still showing high uptime

Hi all,
I had to reboot our production WLC 5508 last night to apply a new adder license, which increased our AP count by 25.
We run a DMZ mobility controller alongside the primary controller, which handles our mobile/guest WLANs using a Mobility Anchor. Normally we would reboot both of these due to issues with the anchor after the primary is rebooted.
So last night I rebooted the primary after installing the new adder license. Once it came back up, I checked the license count and it had increased as per the new license. After that I rebooted the mobility controller, and waited to ensure that this came back up.
Almost straight away, all the AP's had re-associated with the primary (all 96 of them), and clients were starting to show up. I checked the same on the mobility controller (although this does not manage any AP's) and I could see mobility clients associating with this also.
The problem came this morning, when none of the mobility clients that were connected to the mobiltiy WLANs were able to get to the Internet, or any kind of outside connection. This is the typical issue we see when our core switch gets rebooted, or the primary on its own, without rebooting the secondary.
So to troubleshoot this morning the first thing I suddenly noticed was the uptime on the primary controller. It showed 298 days!!
Anyone seen this behaviour before? The WLC DID reboot - I watched it go down and POST again. Why would the uptime counter not reset?
We're on firmware 7.2.111.3 - which I realise is pretty old, but due to CIsco screwing us over with a limited upgrade path, we are not able to upgrade it yet (AP hardware not supported on any of the newer code above this version).
Any help appreciated!

In response to Sandeep, here's the sh sysinfo output:
Manufacturer's Name.............................. Cisco Systems Inc.
Product Name..................................... Cisco Controller
Product Version.................................. 7.2.111.3
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
System Name...................................... UK***********
System Location.................................. Slough CoLo
System Contact................................... Greg Dent
System ObjectID.................................. 1.3.6.1.4.1.9.1.1069
IP Address....................................... 172.17.1.40
Last Reset....................................... Software reset
System Up Time................................... 0 days 3 hrs 42 mins 23 secs
System Timezone Location.........................
Configured Country............................... Multiple Countries:GB,RU,US
Operating Environment............................ Commercial (0 to 40 C)
Internal Temp Alarm Limits....................... 0 to 65 C
Internal Temperature............................. +44 C
External Temperature............................. +26 C
--More-- or (q)uit
Fan Status....................................... OK
State of 802.11b Network......................... Enabled
State of 802.11a Network......................... Enabled
Number of WLANs.................................. 7
Number of Active Clients......................... 794
Burned-in MAC Address............................ **************
Power Supply 1................................... Present, OK
Power Supply 2................................... Present, OK
Maximum number of APs supported.................. 125
As you may notice, the uptime has now reset, but thats because I had to reboot it again this morning. I didnt grab the output before the second reboot. It seems whatever issue caused the uptime counter not to reset didnt occur this time.
Very odd.

WLC 5508 AP-Manager interface

Hi, I own a WLC 5508 and I (probably) do not understand AP-Manager interfaces. I have a lab with 2x 1242AG and 1x 1252AG connected to c2960. APs are in vlan 10 (192.168.10.0/24, configured via DHCP), APs are connected to "switchport mode access" interface. c2960 is connected via a trunk to c4506, and WLC is plugged in gi1/3 and gi1/4 (both through twingig). Both ports are configured as "switchport mode trunk". Management interface on WLC is on WLC port 8 (connected to gi1/4), and AP-Manager is on WLC port 1 (connected to gi1/3). Management interface on WLC has "Dynamic AP management" set to disabled, and AP-Manager has it set to enabled. Both, Management and AP-Manager interfaces are tagged, vlan id 12 and 13 (subnets 192.168.12.0/24, 192.168.13.0/24) respectively. APs receive their IP configuration via DHCP (server located in vlan 20, 192.168.20.0, ip helper-address in use), and try to discover WLC by DNS resolution (CISCO-CAPWAP-CONTROLLER.some.domain resolves to AP-Manager IP correctly). But APs do not join to controller, WLC says "Ignoring discovery request received on non-management interface", AP has "not joined" status in Monitor/Statistics/AP Join.
But if I set management interface as "Dynamic AP enabled", and change DNS to resolve CISCO-CAPWAP-... to it's IP everything works fine - AP joins at once. Please help, how to join LAP to AP-Manager interface? Join to WLC manager is simple, but my design requires at least 2 AP-Manager interfaces.

Hello,
I just wanted to mention foremost; a split LAG configuration is not supported on the WLCs. This "can" be achieved if you are splitting your LAG ports amongst VSS configuration on your two capable devices, but is not a recommended or supported configuration. I would highly suggest a LAG configuration over your individual port. As far as the "ap-manager" concern you have of managing more than 48 APs, you are correct in that the AP-manager cannot handle more than 48 APs, however only when in an individual port configuration. The LAG will overcome this limitation.
George was correct about your DNS entry, this needs to point to the WLC's management interface. This is why the AP joined when you pointed the DNS entry back to the management address-- as intended.
This link is anchored to the mgmt, ap-manager, and dynamic interface creation for the 7.0.116.0 Config Guide: http://www.cisco.com/en/US/docs/wireless/controller/7.0MR1/configuration/guide/cg_ports_interfaces.html#wp1286790
"If" you want to keep an individual port configuration, and need more than 60 APs connected, you will need to create more than one "ap-manager" interface. You will just make a new dyanamic intreface and place it on the same network as the current ap manager (ie, management interface) and mark it for dynamic ap management. All APs will still need to only see the management interface for joining; the WLC will assign to the appropriate AP manager as needed. The WLC will fill up the first AP manager before joining building tunnels through the next AP-manager interface, so in your lab you will not really be able to test this behavior, assuming the 3-4 APs you were using.
1. You can keep your management interface with "dynamic ap management" enabled so this serves as the first AP manager; if you desire.
2. You will need to create another dynamic interface mapped to the next port. enabled "dynamic ap management" again here, and place this new "ap-manager" interface on the same vlan as the mgmt. Keep in mind creating a dynamic interface and designating it as an AP manager prevents mapping that interface to a WLAN, see note below.
*NOTE (from config guide): When you enable this feature, this dynamic interface is configured as an AP-manager interface (only one AP-manager interface is allowed per physical port). A dynamic interface that is marked as an AP-manager interface cannot be used as a WLAN interface.
I would highly suggest the LAG configuration so there is no need to worry about the ap manager interfaces, regardless of the number of APs communicating. This also allows for growth if WLC needs to be licensed for more and more APs.

WLC 5508 Evaluation License Expiry

Similar Messages

Maybe you are looking for