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 ***

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

Upgrade WLC 5508 IOS 8.0.100

Hi
I wan to upgrade the IOS version on WLC 5508, but I do not is recommended,
Can you help me is recommended upgrade for this version?.
The apple devices have a problem with retry authentication constantly
regards

After WLC upgrade to 8.0.100 [ not in HA mode], the AP seem to be dropping out and reconnect using the fallback to IP- inspite of the statically configured IP on the AP
Running Outdoor mesh AIR-CAP1552E-N-K9 on WLC 5508
(Cisco Controller) >show boot
Primary Boot Image............................... 8.0.100.0 (default) (active)
Backup Boot Image................................ 7.6.101.2
=========
Last AP disconnect details
- Reason for last AP connection failure.................... The AP has been reset by the controller
- Last AP disconnect reason................................ Unknown failure reason
Last join error summary
- Type of error that occurred last......................... Lwapp join request rejected
- Reason for error that occurred last...................... No Mwar payload found in join request
- Time at which the last join error occurred............... Dec 03 00:05:26.114
AP disconnect details
- Reason for last AP connection failure.................... The AP has been reset by the controller

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 ****

WLC 5508 7.0.98.0 problem with locpRxServerTask missed software watchdog

Hi
today my wlc 5508 crash. after trying to get access via sp. i doesnt reponds. so i rebooted. in the sh tech i saw this message which i gues indicates the RC of the failure.    ANY IDEAS...
*             Start Cisco Crash Handler Serv               *
Sys Name:       usa-5354-wlc-02
Model:          AIR-CT5508-K9
Version:        7.0.98.0
Timestamp:      Thu Jan 5 05:43:13 2012
SystemUpTime:   254 days 4 hrs 46 mins 24 secs
pid:            1225
TID:            944042816
Task Name:      locpRxServerTask
Reason:         Reaper Reset
timer tcb:      0x2572
timer cb:       0x10354e28 ('rrmTimerInit+600')
timer arg1:     0x19b11010
timer arg2:     0x0
Long time taken timer call back inforamtion:
--More-- or (q)uit
Time Stamp:     Thu Sep 22 15:56:24 2011
timer cb:       0x100d6f48 ('apfRldpScheduleSet+656')
Duration : 103753 usecs, cbCount= 15
Analysis of Failure:
Software was stopped by the reaper for the following reason:
     Reaper Reset: Task "locpRxServerTask" missed software watchdog

May be here is the bug that u r hitting..
http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&bugId=CSCti21343
Upgrade the image to the latest that we have (7.0.220)
Please dont forget to rate the useful posts!!
Regards
Surendra

Upgrade WLC 5508 to ver 7.5

hi,
I need upgrade a WLC 5508 to ver 7.5. we have aironet 1242 AG y 1131 AG and I dont see any ver AP to join
please, are there IOS to do these?
thanks
RAHA
[email protected]

Below AP models supported by WLC 7.5.x software. (see the below release note for detail)
Cisco 1040, 1130, 1140, 1240, 1250, 1260, 1600, 2600, 3500, 3500p, 3600, Cisco 600 Series OfficeExtend Access Points, 700 Series, AP801, and AP802
http://www.cisco.com/en/US/docs/wireless/controller/release/notes/crn75.html
AP will get updated image from WLC once you upgrade controller software to 7.5.x
HTH
Rasika
**** Pls rate all useful responses ****

Questions for upgrade WLC 5508

I need to update a 5508 WLC 7.2.103 to a version that supports the Access Point 2600 model, but the WLC administer it with a WCS version 7.0.230, which is the next version of software that supports the Access Point 2600 model and if that version is compatible with the WCS that I have?

Depending on what code version you require on the WLC, here is a matrix that will explain wht versions are compatible.
http://www.cisco.com/en/US/docs/wireless/controller/5500/tech_notes/Wireless_Software_Compatibility_Matrix.html
If you stay with v7.2.103.0, then you need NCS 1.1.0.58. Prime Infrastructure replaces both WCS and NCS so you might look at the upgrade from WCS to Prime Infrastructure.
Thanks,
Scott
Help out other by using the rating system and marking answered questions as "Answered"

Upgrade WLC 5508 to 7.3x or 7.4x?

Hi Community,
In order to enbale HA SSO on our two 5008 WLC's, I plan to upgrade them to 7.3 / 7.4 (currently 7.2)
Right now 7.3.112.0 is the latest release. We do not have any 1600 series AP's, which requires 7.4.
So here's my question..any reason going for 7.4 directly..or not going for it?
Thanks for your thoughts/input,
Stefan

There are a lot of open bugs in both versions which is the problem. We have had customers go from the 7.3 to 7.4 then to the latest 7.3 and they still have HA issues. We have had a few just get rid of the HA and go with the normal two WLCs with license model. Since many have hit different bugs, I can't really tell you which one pisses them off more.
Sent from Cisco Technical Support iPhone App

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

Wlc 5508 inaccessible after upgrade to version 8

dear all,
I have a problem after upgrading wlc 5508,
at first after upgrade everything works fine, but while waiting for APs to rejoin, wlc suddenly inaccessible either via SSH, telnet or console
I have restart the wlc with no luck
LED indicator for SYS and ALR are off
any suggestion will be highly appreciated
thanks
regards

If the appliance failed in the first month after delivery, you might be able to squeeze off an RMA.
If the appliance failed in the first year after delivery, I don't care what is written in the "warranty", you can't do anything until you have a valid Service Contract.

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.

WLC 5508 Problem with #DOT1X-3-INVALID_REPLAY_CTR

Hi all,
I have WLC 5508 with version 7.4.110.0 and with 13 AccessPoints.So 12 of this AP are AIR-LAP1142N-E-K9 and 1 is AIR-CAP3602I-E-K9.
Logs of my WLC are:
*Dot1x_NW_MsgTask_1: Jan 11 01:15:05.167: #DOT1X-3-INVALID_REPLAY_CTR: 1x_eapkey.c:360 Invalid replay counter from client 90:c1:15:c6:c3:49 - got 00 00 00 00 00 00 00 01, expected 00 00 00 00 00 00 00 02
*Dot1x_NW_MsgTask_4: Jan 11 01:09:41.015: #DOT1X-3-INVALID_REPLAY_CTR: 1x_eapkey.c:360 Invalid replay counter from client 5c:0a:5b:c1:16:34 - got 00 00 00 00 00 00 00 01, expected 00 00 00 00 00 00 00 02
*Dot1x_NW_MsgTask_3: Jan 11 01:03:32.269: #DOT1X-3-INVALID_REPLAY_CTR: 1x_eapkey.c:360 Invalid replay counter from client 40:b3:95:13:da:cb - got 00 00 00 00 00 00 00 03, expected 00 00 00 00 00 00 00 04
*Dot1x_NW_MsgTask_3: Jan 11 01:03:32.266: #DOT1X-3-INVALID_REPLAY_CTR: 1x_eapkey.c:360 Invalid replay counter from client 40:b3:95:13:da:cb - got 00 00 00 00 00 00 00 02, expected 00 00 00 00 00 00 00 04
*Dot1x_NW_MsgTask_0: Jan 11 01:03:31.648: #DOT1X-3-INVALID_REPLAY_CTR: 1x_eapkey.c:360 Invalid replay counter from client 24:77:03:67:01:48 - got 00 00 00 00 00 00 00 02, expected 00 00 00 00 00 00 00 03
*Dot1x_NW_MsgTask_5: Jan 11 01:03:31.638: #DOT1X-3-INVALID_REPLAY_CTR: 1x_eapkey.c:360 Invalid replay counter from client 14:10:9f:da:c1:cd - got 00 00 00 00 00 00 00 02, expected 00 00 00 00 00 00 00 03
*Dot1x_NW_MsgTask_2: Jan 11 01:03:31.638: #DOT1X-3-INVALID_REPLAY_CTR: 1x_eapkey.c:360 Invalid replay counter from client cc:78:5f:29:cc:82 - got 00 00 00 00 00 00 00 02, expected 00 00 00 00 00 00 00 03
*Dot1x_NW_MsgTask_4: Jan 11 01:03:31.633: #DOT1X-3-INVALID_REPLAY_CTR: 1x_eapkey.c:360 Invalid replay counter from client 08:11:96:55:81:c4 - got 00 00 00 00 00 00 00 02, expected 00 00 00 00 00 00 00 03
*Dot1x_NW_MsgTask_0: Jan 11 01:03:31.631: #DOT1X-3-INVALID_REPLAY_CTR: 1x_eapkey.c:360 Invalid replay counter from client 84:3a:4b:56:36:50 - got 00 00 00 00 00 00 00 02, expected 00 00 00 00 00 00 00 03
*Dot1x_NW_MsgTask_1: Jan 11 01:03:31.630: #DOT1X-3-INVALID_REPLAY_CTR: 1x_eapkey.c:360 Invalid replay counter from client 14:10:9f:e2:d4:91 - got 00 00 00 00 00 00 00 02, expected 00 00 00 00 00 00 00 03
*Dot1x_NW_MsgTask_0: Jan 11 00:59:52.593: #DOT1X-3-INVALID_REPLAY_CTR: 1x_eapkey.c:360 Invalid replay counter from client a0:88:b4:60:20:f8 - got 00 00 00 00 00 00 00 01, expected 00 00 00 00 00 00 00 02
*apfRogueTask_3: Jan 11 00:59:32.168: #APF-1-UNABLE_TO_CONTAIN_ROGUE: apf_rogue.c:4414 Unable to contain rogue 40:01:C6:11:F9:F1 - Not enough Container AP(s). Number of Container AP(s) 2, Requested containment level 4
*apfRogueTask_3: Jan 11 00:58:38.635: #APF-1-UNABLE_TO_CONTAIN_ROGUE: apf_rogue.c:4414 Unable to contain rogue 40:01:C6:11:F9:F1 - Not enough Container AP(s). Number of Container AP(s) 1, Requested containment level 4
*Dot1x_NW_MsgTask_0: Jan 11 00:50:06.885: #DOT1X-3-INVALID_REPLAY_CTR: 1x_eapkey.c:360 Invalid replay counter from client 10:68:3f:46:4e:e8 - got 00 00 00 00 00 00 00 01, expected 00 00 00 00 00 00 00 02
*Dot1x_NW_MsgTask_0: Jan 11 00:50:06.883: #DOT1X-3-INVALID_REPLAY_CTR: 1x_eapkey.c:360 Invalid replay counter from client 10:68:3f:46:4e:e8 - got 00 00 00 00 00 00 00 00, expected 00 00 00 00 00 00 00 02
*dot1xMsgTask: Jan 11 00:49:05.842: #DOT1X-3-PSK_CONFIG_ERR: 1x_ptsm.c:618 Client c8:e0:eb:19:2a:97 may be using an incorrect PSK
*apfRogueTask_3: Jan 11 00:40:42.576: #APF-1-UNABLE_TO_CONTAIN_ROGUE: apf_rogue.c:4414 Unable to contain rogue 40:01:C6:11:F9:F1 - Not enough Container AP(s). Number of Container AP(s) 3, Requested containment level 4
*Dot1x_NW_MsgTask_3: Jan 11 00:40:17.471: #DOT1X-3-INVALID_REPLAY_CTR: 1x_eapkey.c:360 Invalid replay counter from client c4:43:8f:f1:8c:8b - got 00 00 00 00 00 00 00 01, expected 00 00 00 00 00 00 00 02
*Dot1x_NW_MsgTask_4: Jan 11 00:40:03.368: #DOT1X-3-INVALID_REPLAY_CTR: 1x_eapkey.c:360 Invalid replay counter from client f0:d1:a9:8e:1a:dc - got 00 00 00 00 00 00 00 02, expected 00 00 00 00 00 00 00 03
*Dot1x_NW_MsgTask_1: Jan 11 00:39:30.528: #DOT1X-3-INVALID_REPLAY_CTR: 1x_eapkey.c:360 Invalid replay counter from client 14:10:9f:d8:84:09 - got 00 00 00 00 00 00 00 01, expected 00 00 00 00 00 00 00 02
I already go to this link to check the Description of errors-
http://www.cisco.com/en/US/docs/wireless/controller/message/guide/msgs4.html#wp1000139
Appreciate all feedback. Thank you.

Hi Ruben,
a) After successful dot1x authentication, session keys are derived from pairwise master key.
b) When the AP transmits a key to a station by default, it expects a response back within a set timeframe.
c) If the station does not respond, the AP increments the counter and retransmits the key.
d) If the AP receives a response to first message just after the retransmission of the key, a mismatch occurs in the counter.
This in most of the cases will be a client driver problem.
Solution :
1) try to increase the EAPOL-Key Timeout ( config advanced eap ).
2) Upgrade the client driver.
*****Help out other by using the rating system and marking answered questions as "Answered"*****

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. -

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 Firmware Upgradation

Hi All,
WLC 5508 - current firmware 7.0.116.0 is running on it. we need add couple of 2700 series AP. From the release notes i got know 2700 series supported on the 7.6.120.x and later.
http://www.cisco.com/c/en/us/td/docs/wireless/access_point/2700/quick/guide/ap2700getstart.html
- whereas 7.6.120.x is the latest one in the train. can we have this firmware on the controller as its latest??
- from the release notes - we can have a direct upgrade to 7.6.120.0., upgrading from 7.0.x.x to 7.6.120.x missing so many version in between. any potential problems i may get ??
- FUS (Field upgrade software is necessary) which version and how it can be installed ??
Regards,
Channa

Hi Channa,
Go for the 7.6.130.0 (7.6MR3) when it is available to public. To be released within next couple of weeks.If you need to do this before 7.6MR3 comes then you can get pre-release of that code via TAC. Refer below for that.
https://supportforums.cisco.com/document/12245186/76mr3-beta-availability
Yes, you have to upgrade your FUS, It is recommended to go for v 1.9.0.0. Below will give you the upgrade procedure. Better to do it via CLI & allocate 30-45min downtime for this upgrade
http://www.cisco.com/c/en/us/td/docs/wireless/controller/release/notes/fus_rn_OL-31390-01.html
Feature wise there are lots of feature available in 7.6.x compare to 7.0.x. But I do not expect any problem going from 7.0.x to 7.6.x as long as you upgrade your FUS first.
Also read these compatibility matrix to see all your AP models are supporting by this 7.6.x code & any other PI or MSE compatibility if you have those.
http://www.cisco.com/c/en/us/td/docs/wireless/compatibility/matrix/compatibility-matrix.html
HTH
Rasika
**** Pls rate all useful responses ****

Upgrade WLC 5508 to 7.4.121.0 problem

Similar Messages

Maybe you are looking for