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.

Similar Messages

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

5508 WLC Upgrade from 7.0.116 to 7.2.111.3

I am planing to upgrade 2 of my 5508 series WLC from 7.0.116 to version 7.2.111.3. I understand that legacy AP's are no longer supported. Is there any other issues I should be aware of that others have experienced? Is the upgrade straight-forward just like other code upgrades? Thank you.

Thanks so much for all the information. Afterr reading throught this, it makes sense now. I do have one more question. After doing a show sysinfo on these controllers, it does look like the FUS does need to be updated. Should I perform this before I upgrade to version 7.2 code, or after I have peformed the upgrade to 7.2, or does it matter?
(Cisco Controller) >show sysinfo
Manufacturer's Name.............................. Cisco Systems Inc.
Product Name..................................... Cisco Controller
Product Version.................................. 7.0.116.0
Bootloader Version............................... 1.0.1
Field Recovery Image Version..................... 6.0.182.0
Firmware Version................................. FPGA 1.3, Env 1.6, USB console 1.27
Build Type....................................... DATA + WPS

WLC 5508 Fus upgrade

Hi,
I have few 5508 controlers with 7.0.116.0 version and i decided to upgrade to 7.4. I did an upgrade of software and FUS (
AIR-CT5500-K9-1-7-0-0-FUS.aes) on three of them without any problems. But on the last one i cannot upgrade fus image.. I dowload code from tftp server, wlc checks image and ask for reload for changes to take effects. After reboot it still has old fus installed :/ I have no access to console to see if there are any errors during the reboot. Is there any way of troubleshooting?
Thanks

Hi Ad,
same exact image is being used for all WLCs upgrade? or this is a different one (downloaded separately)?
Rating useful replies is more useful than saying "Thank you"

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.

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

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 Upgrade - FUS Upgrade

Greetings,
I am planning on upgrading our redundant 5508 WLC’s from v.7.3.112.0 to v.7.4.110.0 this weekend. One thing I noticed in the release notes of 7.4 is the guideline to update the Field Upgrade Software to v. 1.7.0.0-FUS.
My question is should this FUS be upgraded before or after I upgrade the WLC to 7.4? On the release notes it does state a FPGA error on the does occur on the 5500 series controllers.
http://www.cisco.com/en/US/docs/wireless/controller/release/notes/fus_rn_1_7_0_0.html#wp45499
On a Cisco 5500 Series Controller, it is observed that the controller sporadically reboots (due to a defect CSCtr39523) and displays the following FPGA error message:
fpga: Lost heartbeat from Environment controller, system will reboot in 5 seconds!!!
A crash file is not created to debug or troubleshoot the error.
You can resolve this issue by installing the FUS image. Please see Resolved Caveats for more details.
Thanks,
Robert

Honestly, it doesn't really matter the ordr you upgrade in.
Though, I tend to update the FUS before the image.
HTH,
Steve
Please remember to rate useful posts, and mark questions as answered

WLC upgrade due to Advisory

Hi,
We have a 5508 WLC running 7.2.110.0 and need to upgrade according to the advisory released today.
It seems we have three upgrade choices:
7.2.110.0 to 7.2.111.3
7.2.110.0 to 7.3.110.0
7.2.110.0 to 7.4.x
I've not upgraded one of these 5508's before, but if they are anything like ASAs then I need to be careful.
Can anyone advise if upgrading from our current version to 7.4 requires planning. Same for 7.3.
How will the WLC upgrades affect the APs (3502i) ?
How does one recover from a failed upgrade on these WLCs?
Thanks.

WLC version 7.4.100 will need Prime Infrastructure Version 1.3 to be managed, but Version 1.3 is not yet available to download at this time.
Huh? What is Prime Infrastructure and why do I need it?

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

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

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

Similar Messages

Maybe you are looking for