Upgrade WLC HA pair 7.4.110.0 to 7.6.130.0

Hi
I'll be upgrading a HA pair of 5508's from 7.4.110.0 to 7.6.130.0. The documentation suggests that I just need to upgrade the active and this code is copied to the standby. Then simply reboot. After this verify that the active is not the standby HA WLC. Verify all AP's have rejoined and upgraded.
I also need to want to upgrade the FUS image after this.
Has anyone had any issues with upgrading HA pairs?
Or would it be better to break HA and upgrade each of them seperately then recreate the HA pair (not something I really want to have to do).
Any other suggestions\precautions to reduce the risk of issues?
I plan to create backups before and after.
I'll also use "show ap cdp nei all" to get a list of AP's and where they are connected to verify they all rejoin the WLC and upgrade.
Thanks in advance

Thanks Leo,
But according to this document its not required break HA do the FUS upgrade?
http://www.cisco.com/c/en/us/td/docs/wireless/controller/technotes/7-5/High_Availability_DG.html#pgfId-43571
"The FUS image can be upgraded while the controllers have HA enabled. The secondary controller will get upgraded just like it does when upgrading the regular code. However, when you initiate the reboot on the primary controller both controllers will be unreachable until the FUS upgrade completes on both the active and the standby in the HA pair. This process will take around 30 to 40 minutes to complete just like in a non-HA FUS upgrade."
I have a maintainence window for the activity so having both down during the FUS upgrade is not an issue. My only concern is that if something goes wrong to both WLC's during the FUS upgrade I might have 2 dead WLC's and no backup plan !
Thanks

Similar Messages

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

Migrating AP's from WLC 4400 v.4.0.179.11 to WLC 5508 v.7.2.110.0

Hi,
I am replacing an old 4400 series WLC running version 4.0.179.11 to a new 5508 WLC running version 7.2.110.0.
We currently have 70 x 1131 Access points on the 4400 WLC.
With this upgrade, do i need to upgrade the old 4400 to version 6.0 so the AP's get an up to date IOS or can i directly migrate all AP's over to the new 5508 without any version incompatabilities on the AP's?
I am abit worried that the AP's are running a very old IOS on the 4400 v.4.0.179.11 to go straight to the new 5508 v.7.2.110.0.
Thanks

Hi,
Check out this release note
http://www.cisco.com/en/US/docs/wireless/controller/release/notes/crn7_2_110_0.html#wp976667
You'll need to get up to a supported version of 6.0 first as per the release notes.
You'll need to check out the 6.0 release notes too to make sure there are no other intermediate upgrade steps required too.
Nigel
Sent from Cisco Technical Support iPad App

Upgrade WLC 5508 to 7.4.121.0 problem

After I upgraded WLC 5508 from 7.2.111.3 to 7.4.121.0, all 3602i APs don't associate with the controller. All APs were working/associating with controller on 7.2.111.3 at same setting. IP address of APs are setup as DHCP.
The error message is "AP couldn't get IP address".
Any one has this type of problem when you upgrade WLC 5508 from 7.2.111.3 to 7.4.121.0.
Thanks,

Hi,
This doesn't look like software issue.
You have to check why the APs are not able to get ip address. Try connecting a PC to a swtich port where one of these APs are connected and see if you are able to get IP on PC.
Also check if the DHCP server is reachable and if there are IP address in the pool assigned for APs.
HTH,
Thanks & Regards,
Ishant
*** Please rate the post if you find it useful ***

Upgrading WLC 4400

Hi,
How is the correct steps for the upgrade of the WLC4400 from a version 4.1 to 4.2 version?
I backup the configuration running in the version 4.1.
I download, and put the file of the Software 4.2 in the TFTP directory.
I start the transfer from the TFTP to WLC.
The copy was succesfull.
I restart the WLC and Save the config.
But, the WLC lost the configuration (running the version 4.2), I connect to the console port and this showed the Wizard to start the initial configuration :S
What is the correct steps to upgrade WLC.

Hi Ricardo,
This is a good doc with Step by Step info
Wireless LAN Controller (WLC) Software Upgrade
http://www.cisco.com/en/US/tech/tk722/tk809/technologies_configuration_example09186a00805f381f.shtml
Cheers!
Rob
Please support CSC Helps Haiti
https://supportforums.cisco.com/docs/DOC-8895
https://supportforums.cisco.com/docs/DOC-8727

Software upgrades on HA Pairs?

I am working on a plan to convert some of my existing 5508s to be HA pairs. I like the redundancy i have now with multiple controllers, but don't necessarily like buying two licenses for every AP. I am trying to determine the downside to the HA mode. I am trying to figure out what a code upgrade looks like for a redundant pair. Currently, because I have 2 licenses for each AP, I have this process:
1. Load new code onto both controllers (no reboot here)
2. move the APs from controller A to controller B,
3. Reboot controller A to new code
4. Predownload new code from controller B to APs
5. Slowly move APs back to controller A so that there is no real outage. Clients move to adjacent APs as each AP is individually rebooted.
Is there a way I can take an HA member out of service, upgrade it and move the APs to it before doing the other HA member? Or does the whole HA pair have to be down to facilitate a code upgrade? Curious to hear what others are doing.
Thanks

Before you convert the WLC to HA, make sure all the bootstrap have been upgraded. If you have any certificates and/or web-auth pages, make sure they are loaded to both before you tie them up into an HA.
Next, your license for the 2nd unit. Send an email to [email protected] and provide the HA serial number. Tell them you want to convert this unit to HA SSO. They'll send you further instructions.
Ok, now the HA bit. Choose a firmware, either 7.4.121.X or 7.6.110.X. Don't choose anything else.
Read through the High Availability (SSO) Deployment Guide and pay close attention to mandatory requirements especially the requirement that both 5508 must be physically connected via the RP port.
Let us know how you go.

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 and 7.4.110.0 and AP Blackhole?

So large customer had WLCs running 7.4.110.0 and it appears there was either a 3500/3600 AP memory leak or a CCKM roaming issue. The APs would occasionally blackhole traffic. You could see 2+ APs at -67dbm in 5GHz. Phones are locked to 5GHz, data rates matched. . Phone showed good strong signal, but 7925 users would report every couple days the phone dropping/DHCP timeout, re-registering, etc. We had a large CSE/TAC group onsite audit the 7925 Deployment Guide and setup, and we did a lot of cleanup but never hit the silver bullet.
After upgrading the 5508 to 7.4.121.4 (TAC special not on Cisco.com) they reported the 7925 problems have improved. Only been 1 day so far.
There is also a WPA2 with Preshared Key CCKM bug with the 7925s that roaming takes 2s. Use either strong WEP or buy 7926s, or use EAP/certificates, etc. https://tools.cisco.com/bugsearch/bug/CSCtt38270
7.4.121.0 Release Notes
http://www.cisco.com/c/en/us/td/docs/wireless/controller/release/notes/crn74mr02.html#wp1142453
We are running daily Traffic Stream Metrics (TSM) reports from Prime/WLC, and exporting the CallManager Diagnositc LQK records (export via CAR) to show if things are improving/etc.

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.

Unable to upgrade WLC on SRE to 7.4.121.0

Hi
I am unable to upgrade one of my WLC on SRE to 7.4.121.0. I keep getting TFTP or FTP failure while storing in flash. The WLC is currently running 7.2.110.0 and is running on a SRE 700 module in a 2951 router.
I have tried with both TFTP and FTP and I have redownloaded the file from Cisco. I am using tftpd32 on Windows XP and it is allowed from the firewall. When I perform the transfer it shows in the TFTPd32 log as successful.
Could someone please suggest how I can get this to work please?
I get this in the GUI message Log when I try the upgrade
*TransferTask: Apr 09 11:47:14.561: %OSAPI-6-FILE_DOES_NOT_EXIST: osapi_file.c:361 File : /mnt/images/vinitrd-secondary does not exist.(errno 2)
-Traceback: 086b7300 08048aad 08057585 086c7e19 09231700 09280c7e
*TransferTask: Apr 09 11:47:14.561: %OSAPI-6-FILE_DOES_NOT_EXIST: osapi_file.c:361 File : /mnt/images/vinitrd-primary does not exist.(errno 2)
-Traceback: 086b7300 08048a32 08057585 086c7e19 09231700 09280c7e
*TransferTask: Apr 09 11:47:10.513: %UPDATE-3-INIT_TLV_FAIL: installpkg.c:1773 Error -1 installing Temporal Logic Verifier (TLV). Failed to install downloaded s/w.
*TransferTask: Apr 09 11:47:10.513: %UPDATE-3-INCMPLT_WRITE: installpkg.c:752 Warning: Truncated write. Error writing chunk size 1270, len left = 1270, total len = 1270.
Thanks

According to the release notes for 7.4.121.0 it is
http://www.cisco.com/c/en/us/td/docs/wireless/controller/release/notes/crn74mr02.html#pgfId-1141671
Cisco Wireless Controller on Cisco Services-Ready Engine (SRE) (controllerM2) running on ISM 300, SM 700, SM 710, SM 900, and SM 910.
How do I determine the Controller M2 part

Upgrade WLC 5508

I'm trying to upgrade my Cisco WLC 5508 with 125 AP's from 7.0.116 to 7.4.110, so it can support the new AIR-CAP2602 and the old AIR-LAP1142 at the same time, but for some reasons the AP's will not accept the new software.
(Cisco Controller) >show boot
Primary Boot Image............................... 7.0.116.0 (default) (active)
Backup Boot Image................................ 7.4.110.0
I have tried to predownload the new image to all AP's from the WLC, and it sucses, but the predownloaded image was not copied into the Backup image.
(Cisco Controller) >show ap image all
Total number of APs..............................   125
Number of APs
        Initiated........................................... 0
        Predownloading................................ 125
        Completed predownloading................ 0
        Not Supported.................................. 0
        Failed to Predownload....................... 0
                                                 Predownload     Predownload
AP Name            Primary Image Backup Image   Status          Version        Next Retry Time Retry Count
AP-xx-01               7.0.116.0      7.0.116.0      Complete        7.4.110.0      NA               NA
When I then re-boot the WLC on the new software (7.4.110), the AP's just show up in the GUI as "downloadning" and the the AP's re-boot. This going on and on, so I had to force the WLC to reset on the old software (7.0.116).
I think my problem is, that the AP's have the same image atached to both Primary and Backup, so my question is:
How do I clear the information about the Backup image in the AP's and downlod the new image to the AP's?
Can I ftp/tftp the new image direct to the AP's and Then do any configurations at the AP's to make it the Backup image?
THX Frank

Hi Frank,
(Cisco Controller) >show bootPrimary Boot Image............................... 7.0.116.0 (default) (active)Backup Boot Image................................ 7.4.110.0
Since your controller backup image is 7.4.100.0, when you pre-download the image to AP use the following ("backup" keyword instead of "primary")
(Cisco Controller) >config ap image predownload backup all
Then check "show ap image all" to confirm that new image version shown as pre-downloaded image version in your APs.
Then you can go ahead & swap the image on all your APs using
(Cisco Controller) >config ap image swap all
Then you can change the boot image on WLC to pointing to 7.4.110.0 & reset your controller.
(Cisco Controller) >config boot backup
(Cisco Controller) >show boot
Primary Boot Image............................... Code 7.0.116.0 (active)
Backup Boot Image................................ Code 7.4.110.0 (default)
(Cisco Controller) >reset system
Let us know how it goes
HTH
Rasika
**** Pls rate all useful responses ****

ISE 1.3 not receiving Radius requests from WLC 5508 ver 8.0.110.0

Hello all. I just implemented ISE 1.3 at a customer site. added a WLC running 8.0.110.0 using its mgmt address with a RADIUS preshared key. On the WLC, I created to SSIDs, corp and guest.
For corp I configured WPA2 and AES and forwarded Radius requests to my 2 ISE node PSN interfaces
For the guest I configured MAC filter with advanced features AAA overide and Radius NAC - per Cisco's documents
The corp forwards Radius requests to ISE, the guest does not. I get nothing from the guest.
I configured the WLC step by step from the Cisco document. I have completed over 10 ISE implementations in the last year using ISE 1.2 and WLC 7.x and have never run into this issue before.
Any help will be much appreciated.

This issue has been resolved. The issue was that for the guest SSID MAC filtering was enabled as required, but they had the test PCs on a mac filter bypass list for that SSID in the WLC. This was automatically authenticating the PC, and therefore not forwarding the RADIUS to ISE.
Once we removed the PC from the MAC filter list in the WLC, the authentications were forwarded to ISE as desired.

Unable to upgrade WLC 5508 using 7.4 IOS

while trying to push the new Software to a WLC i am getting error as mentioned.
(Cisco Controller) >transfer download path .
(Cisco Controller) >transfer download filename AIR-CT5500-K9-7-4-110-0.aes
(Cisco Controller) >transfer download start
Mode............................................. TFTP
Data Type........................................ Code
TFTP Server IP................................... x.x.x.x
TFTP Packet Timeout.............................. 6
TFTP Max Retries................................. 10
TFTP Path........................................ ./
TFTP Filename.................................... AIR-CT5500-K9-7-4-110-0.aes
This may take some time.
Are you sure you want to start? (y/N) y
TFTP Code transfer starting.
TFTP receive complete... extracting components.
Sanity check failed on file. The file was not downloaded completely! --- > What does this mean
TFTP Failure while storing in flash! (0)
the Size of file matches with Cisco and i am not sure how to check the MD5 on this file.
ftp> put c:/Intel/AIR-CT5500-K9-7-4-110-0.aes
ftp: 119537036 bytes sent in 921.35Seconds 129.74Kbytes/sec.
MD5: 4f30835b2170487c77ac23362dc8587d
Can anyone suggest why we are getting this.

That error is usually because the file was corrupt when I have seen it in the past. Download an MD5 checker and verify the MD5 that is listed in the download when you hover your mouse over the file name.
http://m.download.cnet.com/MD5-Checker/3000-2092_4-10410639.html
Like Leo mentioned, make sure your tftp supports large files. I use 3cdeamon
Sent from Cisco Technical Support iPhone App

Wireless dhcp issue after upgrading WLC to 7.6.100

Hi All,
We have upgraded our controllers to version 7.6.100. After upgrading, the access points also upgraded their version to 15.2(4)JB3. But, the problem is that after this process the APs do not get IP. It stays on this state:
*Sep 26 03:55:36.334: %CAPWAP-3-DHCP_RENEW: Could not discover WLC using DHCP IP. Renewing DHCP IP.
Not in Bound state.
The DCHP configuration is OK, since it is working in other two controllers we have and that we are not upgrading untill this issue is solved.
If we connect the APs via console and configure a static IP and controller's IP, the AP registers and works fine. But, the access points are located in 20 remote sites, so we would like to avoid going site by site.
Has anyone suffered this issue and knows how to "recover" those access points?
Thank you very mucho for your help!

Hi,
Thank you for your answer conraddaniel.
But, our issue was an error on the DHCP. The DHCP server pool for the APs was configured with lease time infinite (on a Cisco 6500). After capturing the packets and debugging on the AP we realized that the AP were receiving wrong values:
DHCP: Scan: Renewal time: 2147483647
DHCP: Scan: Rebind time: 536870911
So, on the AP debugging we saw:
DHCP: Scan: Renewal time larger than Rebind time
On Cisco documentation:
T1 Timer(Renewal) After a certain portion of the lease time has expired, you attempt to contact the server that initially granted the lease in order to renew the lease so its IP address can still be used.
T2 Timer(Rebinding) If renewal with the original leasing server fails, because, for example, the server was taken offline, then you ideally try to rebind to any active DHCP server and try to extend its current lease with any server that allows it to do so.
These T1 and T2 timers can be any values, but must be less than the IP address lease duration. T1 Timer must be less than T2. Generally T1 is set to 50 percent of the lease duration and T2 is set to 87.5 percent of the lease duration. Use this rule to set T1 and T2 timers.
On the previous version of the WLC, the DHCP was configured in the same way and we confirmed that the APs received same times, but they ignored those wrong values.
The workaround was to modify the lease time of the DHCP pool (1 day). This way, both timers had valid values and the APs accepted the DHCP OFFER. We still do not know why with lease infinite these timers have wrong values (a bug?).

Upgrade wlc to 7.4.100.60 AP3600 crash

Hi,
I have in a LAB and wlc 5508 with V7.4.100.0 working with 3 lap 1242 and tow 3602, I made the upgrade to the new version 7.4.100.60 the wlc is OK, but the 3600 neve came up, I consol them and was in a "ROMMON"
AP:
I had to upload the image because the ap send an error with the image. then I tried to join the 3600 again with the wlc and when the wlc downloads the new image to the access point, the AP crash again.
Do you know why is this ??
thanks

Hi,
I do not have the crash info, I download the firmware into the wlc again, I try to join the AP and works OK, I think the upgrade in the wlc was kind of corrupt.
Now it is working good.
thanks

WLC 5508 / firmware 7.2.110.0 is restarting automatically ( COLD START )

Hi Experts ,
I am having weird issue with 5508 controller which is having firmware 7.2.110.0 . This controller is restarting automatically
Since this issue was occuring since long time with earlier version , I have upgraded to 7.2.110.0 , however still no luck ....
I do not have any logs related to controller crash info.

Hey Scott,
I'm about to upgrade a 5508 controller from 7.0.220.0 to 7.4.110.0 , and was just prepping myself on upgrading the FUS as it will be the first time. Latest for 5508 is 1.7 and I noticed for 2504 its 1.8.
I was just curious where you saw that its mandatory to upgrade the FUS ? I can't seem to locate any actual documentation specifying anything about upgrading the FUS when going from one version to another etc. I know one of my clients has a 5508 on 7.4 with the old FUS (see below).
Bootloader Version............................... 1.0.1Field Recovery Image Version..................... 6.0.182.0
Firmware Version................................. FPGA 1.3, Env 1.6, USB console 1.27
Build Type....................................... DATA + WPS
Looking forward to your reply
Thanks !

Upgrade WLC HA pair 7.4.110.0 to 7.6.130.0

Similar Messages

Maybe you are looking for