WLC 7.4.100.0 Downgrade

Hello,
Some time ago I updated a WLC, model 2504, from version 7.3 to 7.4.100.0. I also update the FUS (Field Upgrade Software) to the latest release, 1.8.0.0.
Now I need to downgrade the WLC back to 7.3 version.
My doubt is: Can I just take the normal processes and downgrade the WLC back to 7.3, even with the FUS in version 1.8.0.0?
Tks guys,
Bartulihe

Leo,
I do it all the time especially when I beta test. So far I have not had any issues downgrading, but I always double check the config to make sure that the config hasn't changed. Now this could be because of issues I had in the past or when testing beta code, but even when I upgrade, I still check to make sure. There were a few code versions that did change some if my settings back to default.
Sent from Cisco Technical Support iPhone App

Similar Messages

WLC 7.6.100 traps

Hello Guyz,
I have recently upgraded to WLC 7.6.100 on WLC5508 and i am receiving the following trap messages often.
Cause=Indicates that while the radio state should be updated on controller, no reset should be reported. Status:NA
Any idea what would be the cause?
thanks in advance.

Might be an issue with the code... that version wasn't great. There is a new version which ifxes some major bugs.... v7.6.110.0.... this is what you should upgrade to.

SNMP OID for AssociatedAPs in Virtual WLC 7.4.100.0

Hello Guys!
I need you help for something that I need to do to monitor my Wi-FI network.
I'm using a Virtual WLC (SW Ver 7.4.100.0) where most that 30 APs are associated with, but I would like to monitor each disaciossiation of APs using SNMP. After some search, I have found this OID .1.3.6.1.4.1.14179.2.1.1.1.38 on some forums but it doesn't work, I see random number in my monitoring tool.
Do you know if there is any another OID to use with this software version or maybe if I have to upgrade to ver7.6 or ver8?
Thanks in advance,
Kevin

I'm assuming you don't own a license for Cisco Prime Infrastructure
One thing you can do is send SNMP traps to your monitoring software from the WLC (I've never used virtual WLC but my assumption is most options are the same. If your software doesn't support SNMP Traps consider a different monitoring software...
Go to Management > SNMP > Trap Receivers and set up your receiver
Then to to Management > SNMP > Trap ControlsHere is where you set what traps are sent via SNMP. If you see the "AP" tab you can set several things.
If you only want to see if an AP is dropping off the network and the above doesn't work, you could just put dhcp reservations on your APs and have your software ping it. This of course is only if its off network, not if it simply disassociates.

WLC 7.6.100 and PI 2.0

Today we are running software 7.5.102.0 on our 5508 controllers and software 1.3 on PI.
We now considering upgrade to 7.6.100 on the controllers and 2.0 on PI. In the release notes for 7.6.100 it says: "Cisco Prime Infrastructure 1.4.1 is needed to manage Cisco WLC software Release 7.6.100.0", but i guess that they mean 1.4.1 or higher?

HI,
As per this link 7.4.110.0 is the last support for 5508 WLC.
http://www.cisco.com/en/US/docs/net_mgmt/prime/infrastructure/2.0/release/notes/cpi_rn.html
confirmed through TAC that PI 2.1 is the only release that will support 7.6 WLC code.
It would be good to wait for 2.1 and then upgrade.
More about compatibilty matrix:
http://www.cisco.com/en/US/docs/wireless/controller/5500/tech_notes/Wireless_Software_Compatibility_Matrix.html
Regards

WLC 7.4.100 NAT IP Address field missing

Hi
I know that very few people have their wireless controllers on version 7.4.100. But has any one noticed that the NAT IP address field in the management interface configuration menu is missing?, although it is mentioned as being present in the WLC 7.4 configuration guide. This would definitely affect Office-Extend.
I just thought I ask before I raise the issue with Cisco TAC.

Hello Osita,
As per your query i can propose you the following solution-
Control which address(es) are sent in CAPWAP discovery responses when NAT is enabled on the Management Interface using the following command:
config network ap-discovery nat-ip-only {enable | disable}
where:
–enable— Enables use of NAT IP only in a discovery response. This is the default. Use this command if all APs are outside of the NAT gateway.
–disable—Enables use of both NAT IP and non-NAT IP in a discovery response. Use this command if APs are on the inside and outside of the NAT gateway; for example, Local Mode and OfficeExtend APs are on the same controller.
For more information refer to the link-
http://www.cisco.com/en/US/docs/wireless/controller/release/notes/crn74.html
Hope this will help.

WLC 7.4.100.60 and roaming problems on 8500

Hello,
After installing an 8500 controller on 7.4.100.60 and migrating 1000 APs do this controller, we have the following problems:
[1] clients get disconnected and loose sessions (note: client is mobile gun and is heavily mobile). I have the impression there are more coverage holes. This might be due to bug CSCue13108, but says fixed in 7.4.100.60, we wil be upgrading to 7.4.110.0 anyway shortly.
[2] we have lots of L3 roaming problems between clients, especially when clients roam between old WISM controller and new 8500 controller. They don't roam, they get disconnected and reconnected, resulting in ip address change, resulting in sessions loss. Old controller still runs 7.0.230.0 but compatibility matrix says these two versions are L3 roaming compatible.
However, the release notes of 8500 mention this: "Cisco 8500 Series Controller cannot be configured as a guest anchor controller. However, it can be configured as a foreign controller to tunnel guest traffic to a guest anchor controller in a DMZ"
Because Layer 3 roaming is similar to guest traffic tunneling, does this mean that the 8500 can be the initiator of a L3 roam tunnel, but cannot be the endpoint of a L3 roam tunnel ?
We have done a test that seems to confirm this: client starts on 8500 in state "local", goes to AP on old controller (7.0.230.0), but roam doesn't work. Client gets re-associated with ip address change. Then when moving back to the 8500 controller, the client does roam successfully, keeps its ip address in the 7.0.230.0 vlan and gets status "foreign" on 8500 controller. controllers are in same mobility group and mobility connections are all up.
In the 7.5 release notes, this limitation is not mentioned anymore. Does it mean it is solved and 8500 can be used as guest anchor controller in 7.5 ??
regards,
Geert

[2] we have lots of L3 roaming problems between clients, especially when clients roam between old WISM controller and new 8500 controller. They don't roam, they get disconnected and reconnected, resulting in ip address change, resulting in sessions loss. Old controller still runs 7.0.230.0 but compatibility matrix says these two versions are L3 roaming compatible.
Roaming from one AP to another that shares the same controller is totally different with inter-controller roaming, which you have now. I believe WiSM-1 has 180 ms compared to the 90 ms on a 5508. And this time difference means alot.
So when your client goes from one controller to another, they actually have to do a full re-authentication to the new controller.
I presume both the old and new controller are in the same Mobility Group?
However, the release notes of 8500 mention this: "Cisco 8500 Series Controller cannot be configured as a guest anchor controller. However, it can be configured as a foreign controller to tunnel guest traffic to a guest anchor controller in a DMZ"
Pffft! That'll be the most expensive Guest Anchor Controller if I follow this solution.

WLC 7.4.100.0 Mobility group control and data path down

Hi All,
Today i am facing issue with mobility group. i checked and found control and data path is down on foreign controller.I am able to ping anchor controller. Required ports are open on firewall but mping and eping fails. Any idea whats wrong. On Anchor controller, i have 7 foreign controller configured and among these 3 are working fine. Having problem with 4 foreign controller. Previously all are working fine and there is no changes made on network or firewall.

Post output of "show mobility summary" of your Anchor WLC & a non-working WLC. Also "show sysinfo" of those two controllers.
Regards
Rasika

ISE 1.2 and WLC 7.6.100.0 Flex Config

I've one SSID used for both Head Office users and branch users. The problem is that branch users are using flexconnect. All the branch users are using vlan 10 as pre authC and vlan 20 after authenctication. But H.O. users are using vlan 50 to connect. Now i've make the AuthZ policy to match wlan-id and wireless 802.1x.
The question is that how i'll make the H.O. users to match different AuthZ policy and branch users with other AuthZ policy since i need to return different vlan for them.
Thanks and Regards,
Zohaib

Hi Jan,
Thanks for the reply. I just want to know if there is any other way to identify the users in the policy since im using only default group and the network in operational. Shifting these AP to a new group will be difficult. Is there a way to put NAS-ID on flexconnect group?

Wireless controller ha between wlc5508 and wlc 4402

We have 2 wlc: a wlc 5508 ( license 100 AP ) and wlc 4402 ( license 12AP).
We try to setup when 5508 down, 12 identify AP (important AP -Group A) will join 4402 and all other AP (not improtan AP -Group B)
wont joint wlc 4402.
First, all AP join wlc 5508, 2 WLC have same mobility group.
After that, we config 12 APs belongto group A have primary and secondary wlc, group B only has primary wlc.
When wlc 5508 down, some of APs of GroupA and some of APs of GroupB join wlc 4402. We test many times and we have differnet result each times.
is theare any way to resolve our problem?
Thanks.

Just to add, make sure that the WLC is running the same code, if not, then make sure the ap is supported on the code that is running on the 5508. The issue with mixed code is the ap will upgrade and downgrade very time they switch to a different WLC.
http://www.cisco.com/en/US/docs/wireless/controller/5500/tech_notes/Wireless_Software_Compatibility_Matrix.html
Sent from Cisco Technical Support iPhone App

I Ask About WCS count Client not same WLC

WCS count Client not same WLC as on WLC count client = 100
on WCS count = 23-23
Wireless Control System Version 5.2.148.0
WLC 7.0.250.0
http://postimg.org/image/9boldeqd5/
http://postimg.org/image/l482i9poz/

Your WCS should have a higher (or not equal) version to your WLC.
I wouldn't even consider troubleshooting WCS problems if your WCS is running 5.X because WCS/WLC firmwares 5.X are very, very buggy.

Prime 2.0 patch or 2.1 beta to support WLC 7.6??

Will there be a beta run of 2.1 PI like there was for the latest 7.4 MR for WLC or even a patch to go on 2.0 that will allow us to finally manage WLC code above 7.4? These seperate PI software trains have been killing us trying to get to a more stable HA MSE (above 7.4.110) AND now to support the new 3702 APs.

Hi Toni
PI 2.0 & PI 1.4.x is incompatible to each other & you cannot resotre databases from one version to another.
To support 3700 you need to have PI 1.4.1 at the moment. See below for the 1.4.1 release notes
http://www.cisco.com/en/US/docs/net_mgmt/prime/infrastructure/1.4/release/notes/cpi_rn_141.html
This is a patch release for Cisco Prime Infrastructure1.4 (1.4.0.45). This patch must be installed on top of your existing Prime Infrastructure 1.4. This release supports two new AP platforms - Cisco 3700 and Cisco 1530 series access points (supported by WLC 7.6.100.0). This release also delivers a number of critical bug fixes. The update 1 for Prime Infrastructure 1.4 enables you to manage Cisco WLC 7.6.100.0 with the features of Cisco WLC 7.5.102.0 and earlier releases. This release does not support any new features of Cisco WLC 7.6.100.0
HTH
Rasika
**** Pls rate all useful responses ****

WLC/LDAP/WPA authentication solution

Hi Experts,
I have Cisco WLC 4404 with 100 LWAP access points. Currently I am using shared WEP authentication. I like to migrate it WPA. I want the clients to have authenticated using Individual username / password to get into the network. I am using LDAP for username password repository. I also have Cisco ACS (AAA) server kept unused.
I think it can be achieved using
1. web authentication configured in WLC itself. But i donot want this as WLC may be loaded unnecessarily. Is this correct.
2. Another option I read is 802.1x authentication with WPA. Since I am integrating with LDAP, I also learned that only EAP-FAST can be used.
The question is, whether windows XP supports EAP-FAST client by default (I didn't the option in win XP). Or otherwise should i load a third party clients in all the client laptops. Whether cisco aironet client is free to download and use?
Kindly help me
THANKS IN ADVANCE
sairam

Let me list your requirements, to better define them:
1) Clients must log in (each time?) with their username and password
2) You don't have, and don't want to implement, a certificate server
3) You are using a non-Windows AD LDAP directory for user authentication
4) You have a Cisco ACS (version ?) that you can use for RADIUS, to interact between the client and the LDAP server
5) You want to avoid web authentication if you can, because of concerns about overloading the WLC.
One thing - what is your supplicant? Are these standard Windows XP, SP2 machines? Also, what are your encryption requirements? Web authentication provides no encryption for the data after authentication.
And, without a certificate on at least the ACS server (plus appropriate Certificate Authority server), you're out of luck for EAP.
EAP-FAST generally requires a certificate on the server side (if you want it to be at least somewhat secure). And, it requires a Cisco supplicant, such as the Aironet Desktop Utility with the Cisco CB21AG PCMCIA card (or can potentially use the EAPHost supplicant in Windows Vista.)
If you don't need encryption, go with web authentication. The WLC should not have a problem handling the requests (how many simultaneous logins are you looking at?) If you do need encryption, you are going to need some additional components, whether supplicants or a certificate server.

Cisco WLC 5508 in HA mode error

Hai ,
I am Getting the below Error in Cisco WLC 5508, Version 7.4.100.0 in HAmode. The WLC contains Access Points having in local and Flex Connect Mode.
RF failure notification ErrorType: 32 Reason :Error: Config Sync failed on Standby for the usmdb:HA_send_usmDbApfMsDelete,
I sam a same bug in Cisco WLC 7.4.100.0 release notes similar to the error like
RF failure notification ErrorType: 32 Reason :Error: Config Sync failed on Standby for the usmdb:HA_send_usmDbSpamSetRadSlotAntennaType.
Any Ideas?

HI Mohamed,
its a open Caveats in 7.4.100.0
CSCud26632
Symptom: The following SNMP trap appears on the controller when you change the channel width number to 40-MHz:
RF failure notification ErrorType: 32 Reason :Error: Config Sync failed on Standby for the usmdb:HA_send_usmDbSpamSetRadSlotAntennaType.
Conditions: Controller is in an HA pair. Join the 802.11n access point to the controller and change the channel width to 40-MHz and channel number to 157.
Workaround: None
http://www.cisco.com/en/US/docs/wireless/controller/release/notes/crn74.html
Reagrds
Please rate helpful posts

Actualización WLC

Tengo WLC 5508 en versión 7.0,116 y lo quiero actualizar a la última versión. El esquema que tengo es el siguiente:
Son dos equipos en dos diferentes lugares en una misma ciudad y tengo una fibra oscura entre esos dos lugares, ósea están en la misma red LAN, los dos equipos están activos, pero el equipo A es el respaldo del B y el equipo B es el respaldo del A.
Cual sería la mejor forma de actualizar las WLC sin tener que dejar sin servicio a esos dos lugares.
La capacidad de cada WLC es de 100 access point y actualmente estoy usando 40 en cada uno de los lugares.
Sent from Cisco Technical Support iPad App

Scott otra pregunta al respecto.
Actualmente esta son las versiones disponibles para WLC.
------------version 7.0------------
20/Jun/2011     25/Oct/2011     01/Feb/2012    28/Apr/2012     06/Sep/2012    30/Jan/2013
7.0.116.0         7.0.220.0         7.0.230.0         7.0.235.0         7.0.235.3         7.0.240.0
------------version 7.1------------
08/Nov/2011
7.1.91.0
------------version 7.2------------
28/Jan/2012    29/May/2012    16/Sep/2012
7.2.103.0         7.2.110.0         7.2.111.3
------------version 7.3------------
20/Aug/2012    30/Jan/2013
7.3.101.0        7.3.112.0
------------version 7.4------------
16/Dec/2012
7.4.100.0
Cual seria la recomendable colocar y porque razon ?
Y si yo tengo la version 7.0 para subiar hasta la 7.1 o cualquiero superior a la 7.0 necesito algo de licenciamiento o no?
Gracias.
Jose Luis Diaz Ortega
Ing de Sistemas.
Administrador de redes.

Why LAP1131AG and LAP11412 cannot to join WLC 2504?

I have WLC 2504, Cisco LAP1131AG and then Cisco LAP1142N. Why LAP1131AG and LAP11412 cannot to join WLC 2504?
this is error code at the Cisco LAP1131AG
*Sep 12 19:30:27.730: %CAPWAP-3-ERRORLOG: Go join a capwap controller
*Sep 12 19:30:27.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 192.168.100.10 peer_port: 5246
*Sep 12 19:30:57.001: DTLS_CLIENT_ERROR: ../capwap/base_capwap/dtls/base_capwap_dtls_connection_db.c:2051 Max retransmission count reached!
*Sep 12 19:31:27.000: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to 192.168.100.10:5246
*Sep 12 19:31:32.083: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to administratively down
*Sep 12 19:31:32.083: %LINK-5-CHANGED: Interface Dot11Radio1, changed state to administratively down
*Sep 12 19:31:32.085: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to up
*Sep 12 19:31:32.117: %CAPWAP-3-ERRORLOG: Not sending discovery request AP does not have an Ip !!
*Sep 12 19:31:32.118: %LINK-6-UPDOWN: Interface Dot11Radio1, changed state to up
*Sep 12 19:31:33.083: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio1, changed state to down
*Sep 12 19:31:33.112: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to down
*Sep 12 19:31:33.117: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset
*Sep 12 19:31:34.104: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio1, changed state to up
*Sep 12 19:31:34.111: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to down
*Sep 12 19:31:34.142: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to up
*Sep 12 19:31:34.147: %LINK-6-UPDOWN: Interface Dot11Radio1, changed state to down
*Sep 12 19:31:34.152: %LINK-5-CHANGED: Interface Dot11Radio1, changed state to reset
*Sep 12 19:31:35.141: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to up
*Sep 12 19:31:35.146: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio1, changed state to down
*Sep 12 19:31:35.170: %LINK-6-UPDOWN: Interface Dot11Radio1, changed state to up
*Sep 12 19:31:36.171: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio1, changed state to up
this is version LAP1131AG
AP0018.18fc.fd58#sh version
Cisco IOS Software, C1130 Software (C1130-K9W8-M), Version 12.4(25e)JAO6, RELEASE SOFTWARE (fc1)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2014 by Cisco Systems, Inc.
Compiled Fri 22-Aug-14 10:07 by prod_rel_team
ROM: Bootstrap program is C1130 boot loader
BOOTLDR: C1130 Boot Loader (C1130-BOOT-M) Version 12.3(7)JA1, RELEASE SOFTWARE (fc1)
AP0018.18fc.fd58 uptime is 9 minutes
System returned to ROM by power-on
System image file is "flash:/c1130-k9w8-mx.124-25e.JAO6/c1130-k9w8-mx.124-25e.JAO6"
and then this is version WLC2504
(Cisco Controller) >show sysinfo
Manufacturer's Name.............................. Cisco Systems Inc.
Product Name..................................... Cisco Controller
Product Version.................................. 7.6.130.0
Bootloader Version............................... 1.0.20
Field Recovery Image Version..................... 7.6.101.1
Firmware Version................................. PIC 16.0
Build Type....................................... DATA + WPS
System Name...................................... Cisco_47:19:c4
System Location..................................
System Contact...................................
System ObjectID.................................. 1.3.6.1.4.1.9.1.1279
IP Address....................................... 192.168.100.10
Last Reset....................................... Software reset
System Up Time................................... 0 days 0 hrs 36 mins 45 secs
System Timezone Location.........................
System Stats Realtime Interval................... 5
System Stats Normal Interval..................... 180
--More-- or (q)uit
Configured Country............................... ID - Indonesia
Operating Environment............................ Commercial (0 to 40 C)
Internal Temp Alarm Limits....................... 0 to 65 C
Internal Temperature............................. +34 C
External Temperature............................. +40 C
Fan Status....................................... 4100 rpm
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............................ 24:E9:B3:47:19:C0
Maximum number of APs supported.................. 5
IP Address management WLC : 192.168.100.10/24
IP Address LAP1142N :192.168.100.102/24
IP Address LAP1131AG : 192.168.100.101/24
Can anyone help my problem?

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-LAP1142N-A-K9 (PowerPC405ex) processor (revision A0) with 90102K/40960K bytes of memory.
Processor board ID FGL1439S15W
PowerPC405ex CPU at 586MHz, revision number 0x147E
Last reset from reload
LWAPP image version 7.6.130.0
1 Gigabit Ethernet interface
2 802.11 Radios
32K bytes of flash-simulated non-volatile configuration memory.
Base ethernet MAC Address: C8:4C:75:79:EB:E9
Part Number : 73-12836-03
PCA Assembly Number : 800-33767-03
PCA Revision Number : A0
PCB Serial Number : FOC14234D8Z
Top Assembly Part Number : 800-33775-02
Top Assembly Serial Number : FGL1439S15W
Top Revision Number : A0
Product/Model Number : AIR-LAP1142N-A-K9
cisco AIR-LAP1131AG-A-K9 (PowerPCElvis) processor (revision A0) with 27638K/5120K bytes of memory.
Processor board ID FTX1026T46E
PowerPCElvis CPU at 262Mhz, revision number 0x0950
Last reset from power-on
LWAPP image version 7.6.130.0
1 FastEthernet interface
2 802.11 Radio(s)
32K bytes of flash-simulated non-volatile configuration memory.
Base ethernet MAC Address: 00:18:18:FC:FD:58
Part Number : 73-8962-09
PCA Assembly Number : 800-24818-08
PCA Revision Number : A0
PCB Serial Number : FOC102513DE
Top Assembly Part Number : 800-25544-06
Top Assembly Serial Number : FTX1026T46E
Top Revision Number : A0
Product/Model Number : AIR-LAP1131AG-A-K9
Configuration register is 0xF

WLC 7.4.100.0 Downgrade

Similar Messages

Maybe you are looking for