WLC 6.0.188.0 bug

I recently deployed 2100 4 with the code above, series controllers each controller force the port speed to 10 half which is obviously a nightmare. Reset the speed via the GUI or CLI to 100 full and goes down to 10 in the second half. Roll back to the image of emergency 5.1 fixes the problem but its inconveenient.

Anyone else seen this, I'm waiting for TAC to get back to me I don't think it's the same as CSCta49183 hjb speed/duplex configuration is not available through the CLI for the WLC indicating orders are not available.

Anyone else seen this?

A Cisco person broke the code. He he he...

Tags: Cisco Wireless

Similar Questions

Lose the CDP features in upgrade WLC

Hi all

Recently, we have a consultant to come in and upgrade our 5508 WLC to new version 8.0.133.0.

ALL good until recently, we need to check where an AP connected to that through goto COP under the monitor and the field is empty.

is there a setting somewhere we can turn on? and how back us the COP? as this is a good feature to see where APs connect to

This pass?

All advice is appreciated.

ThanksPeter

Then you have to deal with this bug:CSCuv33255

https://BST.cloudapps.Cisco.com/bugsearch/bug/CSCuz89453/?referring_site...

Concerning

Remember messages useful rates

customers on flexconnect AP cannot get dhcp address after upgrade wlc

Hi community support.

I have a WLC 2504, with 30 APs 1130 flexconnect mode. The WLC runs the code version 7.0.240.0. In order to register new models of ap, we need upgrade to a recent code.

In the last attempt to upgrade to version 7.4.121.0, the AP has joined the WLC, mappings of vlan in flexconnect have been checked and were very good. However, customers were unable to get an address DHCP (169.254.x.x). The DHCP server is local to each location, is usually a 3750 x that serves as a master switch.

connection via cable, clients received address dhcp. so the dhcp server isn't the problem. Updated for the 7.6.100.0 code, but got the same behavior.

Finally, we decided to downgrade the wlc code 7.0.240.0 once again, and everything started working again, but I need upgrade we buy access to new models of points.

Someone else had a similar problem?

Thank you

Hello

What is the vlan native you are using? If it's the number of vlan 2, then it is known bug CSCui73764

Symptom:

Flex series APs 1130 & 1240 mode, won't see traffic, for example, DHCP, ARP. on some wireless LANs.

Conditions:
(1) flex connect local switching
(2) AP 1240 or 1130
(3) any version before 7.4.121.7
(4) native vlan x, not work y vlan.
(5) failed to get the ip address of the user.

Workaround solution:
change the vlan native to a surprisingly high number, so no wlan will never be are mapped to a very high bridge group number.

Other Description of the problem:
Telnet on the flex AP. here is an example. VLAN 3 is the vlan native Flex ap, it is correctly mapped to group 1. now WiFi is not working is the one that is mapped to vlan2. below, carefully, the vlan 2 is mapped to fill the 3 group. It is the forum where we hit the bug. Therefore, it can be any combination of wlan-vlan-native vlan.

HTH

Rasika

Pls note all useful responses *.

Problem with WLC and a 3rd-party NMS SNMP AP Assoc/cancellation interruption

Hello

I'm troubleshooting an issue, why our NMS is not able to automatically clear an alarm generated trap of an AP that has been separated and is associated with again.

When debugging on the WLC snmp trap generation, I discovered that when the AP disassociates the WLC sends the trap of bsnAPDisassociated , which is perfectly defined and I can also find in the SNMP Object Navigator. However when the AP reassociates again the WLC sends the ciscoLwappApAssociatedtrap.

Part 3 NMS is not able to understand it, but our WCS system does, that's why I then took a peek in the MIB file installed.

I discovered that ciscoLwappApAssociated is a sheet of ciscoLwappApMIBNotifs (1.3.6.1.4.1.9.9.513.0. 4), which I have neither

Cannot be found in the Cisco SNMP Object Navigator or the downloadable MIB.

As the MIB in the WCS is a XML file I didn't how to get information in the 3rd-party NMS.

Anyone have any idea on how to solve this problem or there at - it update CISCO-LWAPP-AP-MIB available somewhere?

Our WLCs are running the latest version of the software (7.0.116.0) as well as our WCS (7.0.172.0)

Thanks in advance!

Kind regards

Patrick

Such discrepancies sometimes occur. Best is a matter of TAC in order to tackle the problem through a bug or have a new MIB published on cisco.com if necessary

WLC v4.2.112.0 - IDS Signatures - Deauth/Auth and flooding of the Assoc

Hi all

My apologies if this has already asked. There seems to be several posts with people getting critical alarms and they are due to bugs in Cisco?

Couple of points.

I am under the above version and I'm getting a lot of IDS Deauth Auth and Assoc alarms on WLCs/WCS.

How can I find out if these are some releated bug or not?

Also, does anyone know how these three and the other signature attack work? IE, a deauth is a number of deauth messages sent to an access point, but how much is sent before the WLC reports on them? That is to say, what are the criteria to generate the IDS alarms. Also for other signature attacks?

It doesn't seem to be too docs on the web?

Many thx and sincere friendships,

Ken

Ken:

It is a region that has been a bit murky documentation. There have been a number of requests for better documentation, but we are still waiting to see.

Surprisingly, one of the best forms of

"documentation" is by examining the signature file wireless IDS which has a few comments and explains how settings work. You can see what a little enlightening.

In addition, when it comes to false alarms, we have seen a number of them in various flavors. Here are a few thoughts:

If you run "containment" or rogue APs, wireless ID system currently interprets its own messages of containment as a false-positive/attack. This is a known bug ( CSCsj06015 ) that says: it is fixed, but to my knowledge continues to be a problem.

Here is a link to the bug:

http://Tools.Cisco.com/support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&bugId=CSCsj06015

Also, when some brands of customers go out of scope, a string of messages disassociation is sent via the Russia Federation to ensure that the RF connection is broken. However, the number of these legitimate trusts sometimes exceeds the allowed value in the signature CODES of Cisco Wireless file and the WLC erroneously interprets as a false positive / attack, whereas in fact, it's a normal approval. The number of detections per second value can be adjusted (in fact, the proposed TAC make some changes here - but this really needs to be better set at the factory to prevent them to ancestral). One of the links below explains the methodology to change wireless IDs. The most recent versions of the WCS/WLC are supposed to allow a change of parameter/GUI based these parameters vs export/edition/download the signature file wireless IDS on/in each WLC.

For your reading pleasure, here are some links that you might find useful who discuss various wrinkles in wireless IDs:

http://forums.Cisco.com/eForum/servlet/NetProf?page=NetProf&CommCmd=MB%3Fcmd%3Dpass_through%26location%3Doutline%40%5E1%40.1ddf672c/0#selected_message

http://forums.cisco.com/eforum/servlet/NetProf?page=netprof&forum=Expert%20Archive&topic=Wireless%20-%20Mobility&topicID=.ee7f999&CommCmd=MB%3Fcmd%3Dpass_through%26location%3Doutline%40%5E1%40%40.2cbf522e/16#selected_message

http://forums.Cisco.com/eForum/servlet/NetProf?page=NetProf&CommCmd=MB%3Fcmd%3Dpass_through%26location%3Doutline%40%5E1%40.2cbf520e/1#selected_message

http://forums.Cisco.com/eForum/servlet/NetProf?page=NetProf&CommCmd=MB%3Fcmd%3Dpass_through%26location%3Doutline%40%5E1%40.2cbeccbc/0#selected_message

http://forums.Cisco.com/eForum/servlet/NetProf?page=NetProf&CommCmd=MB%3Fcmd%3Dpass_through%26location%3Doutline%40%5E1%40.1ddfaecb/1#selected_message

Thank you

John

(Don't forget to rate helpful messages)

Microsoft Mouse and keyboard Center 2.3.188.0 is not Exchange buttons of the mouse correctly with Windows Remote Desktop

I use Microsoft Mouse and keyboard Center for years with no problems. For example, version 2.2.173.0 worked well. I use Windows 7 Professional 64 bit.

I swapped the buttons on my Comfort Optical Mouse 3000 (so that the right button's "click" and the left button displays a context menu, for example). When I connect to a remote computer, traded buttons continue to operate as programmed.

Just set Windows Update to update my mouse and keyboard Center to the 2.3.188.0 version. Now when I use the Windows Remote Desktop to connect to another computer that is running Windows 7 Professional 64 bit, my button is not honored. In other words, on the local computer, the right button of the mouse is 'click '. On the remote computer, the left mouse button is 'click '. The keys are reversed on the local computer, as I have it configured, but not on the remote computer.

I called Microsoft and was transferred to various departments. I would like to report this bug, although I have to pay out of pocket, but there seems to be no way to report this bug.

Is there a way to report this bug to Microsoft? Is there a solution? How can I revert to a previous version of Microsoft Mouse and keyboard Center?

I suggest to perform a restore of the system to a restore point before the update.

You can also uninstall the keyboard and the mouse Center programs and features.

Then, go to this site and download the previous version.

(I couldn't find any previous version on Microsoft sites, but I checked the file hash values, I downloaded Microsoft previously).

MD5: 4a2fb26c01d96b25487735da2925f89a

SHA1: a68199c29a840dc8719c7f644ae14a4b138f65e7

http://www.userdrivers.com/keyboard-mouse/Microsoft-mouse-and-keyboard-Center-2-2-173-0-for-Windows-7-8-x86-x64/download/

WCS & WLC version compatibility

Are there compatibility issues between the 7.0.164.0 of the WCS and WLC version 7.0.116.0 version?

Hi Jason,

Table 1-WCS Versions

WCS version	Controller supported versions	Rental Server Versions supported	Versions supported for MSE	Release date	Upgrade took in charge of	Operating system requirement
7.0.172.0	7.0.116.0 7.0.98.218 7.0.98.0 6.0.202.0 6.0.199.4 6.0.196.0 6.0.188.0 6.0.182.0 6.0.108.0 5.2.193.0 5.2.178.0 5.2.157.0 4.2.209.0 4.2.207.0 4.2.205.0 4.2.176.0 4.2.173.0 4.2.130.0 4.2.112.0 4.2.99.0 4.2.61.0	6.0.202.0	7.0.201.0	April 2011	7.0.164.3 7.0.164.0 6.0.202.0 6.0.196.0 6.0.181.0 6.0.170.0 6.0.132.0 5.2.148.0 5.2.130.0 5.2.125.0 5.2.110.0	Windows 2003 SP2 32-bit RHEL 5.x Windows / RHEL on ESX 3.0.1 and above No support for 64-bit
7.0.164.3	7.0.98.0 6.0.202.0 6.0.199.4 6.0.196.0 6.0.188.0 6.0.182.0 6.0.108.0 5.2.193.0 5.2.178.0 5.2.157.0 4.2.209.0 4.2.207.0 4.2.205.0 4.2.176.0 4.2.173.0 4.2.130.0 4.2.112.0 4.2.99.0 4.2.61.0	6.0.103.0	7.0.105.0	December 2010	7.0.164.0 6.0.196.0 6.0.181.0 6.0.170.0 6.0.132.0 5.2.148.0 5.2.130.0 5.2.125.0 5.2.110.0	Windows 2003 SP2 32-bit RHEL 5.x Windows / RHEL on ESX 3.0.1 and above No support for 64-bit
7.0.164.0	7.0.98.0 6.0.202.0 6.0.199.4 6.0.196.0 6.0.188.0 6.0.182.0 6.0.108.0 5.2.193.0 5.2.178.0 5.2.157.0 4.2.209.0 4.2.207.0 4.2.205.0 4.2.176.0 4.2.173.0 4.2.130.0 4.2.112.0 4.2.99.0 4.2.61.0	6.0.103.0	7.0.105.0	June 2010	6.0.181.0 6.0.170.0 6.0.132.0 5.2.148.0 5.2.130.0 5.2.125.0 5.2.110.0	Windows 2003 SP2 32-bit RHEL 5.x Windows / RHEL on ESX 3.0.1 and above No support for 64-bit
6.0.202.0	6.0.202.0 6.0.199.4 6.0.199.0 (taken from EAC) 6.0.196.0 6.0.188.0 6.0.182.0 6.0.108.0

5.2.193.0
5.2.178.0
5.2.157.0
5.1.163.0
5.1.151.0
4.2.209.0
4.2.207.0
4.2.205.0
4.2.176.0
4.2.173.0
4.2.130.0
4.2.112.0
4.2.99.0
4.2.61.0

6.0.202.0

April 2011

6.0.196.0
6.0.181.0
6.0.170.0
6.0.132.0
5.2.148.0
5.2.130.0
5.2.125.0
5.2.110.0
5.1.65.4
5.1.64.0
4.2.128.0
4.2.110.0
4.2.97.0
4.2.81.0
4.2.62.11
4.2.62.0

Windows 2003 SP2 32-bit

RHEL 5.x

Windows / RHEL on ESX 3.0.1 and above

No support for 64-bit

6.0.196.0

6.0.199.4
6.0.199.0 (taken from EAC)
6.0.196.0
6.0.188.0
6.0.182.0
6.0.108.0
5.2.193.0
5.2.178.0
5.2.157.0
5.1.163.0
5.1.151.0
4.2.209.0
4.2.207.0
4.2.205.0
4.2.176.0
4.2.173.0
4.2.130.0
4.2.112.0
4.2.99.0
4.2.61.0

6.0.102.0

6.0.105.0

July 15, 2010

6.0.181.0
6.0.170.0
6.0.132.0
5.2.148.0
5.2.130.0
5.2.125.0
5.2.110.0
5.1.65.4
5.1.64.0
4.2.128.0
4.2.110.0
4.2.97.0
4.2.81.0
4.2.62.11
4.2.62.0

Windows 2003 SP2 32-bit

RHEL 5.x

Windows / RHEL on ESX 3.0.1 and above

No support for 64-bit

6.0.181.0

6.0.196.0
6.0.188.0
6.0.182.0
6.0.108.0
5.2.193.0
5.2.178.0
5.2.157.0
5.1.163.0
5.1.151.0
4.2.207.0
4.2.205.0
4.2.176.0
4.2.173.0
4.2.130.0
4.2.112.0
4.2.99.0
4.2.61.0

6.0.101.0

6.0.103.0

February 17, 2010

6.0.170.0
6.0.132.0
5.2.148.0
5.2.130.0
5.2.125.0
5.2.110.0
5.1.65.4
5.1.64.0
4.2.128.0
4.2.110.0
4.2.97.0
4.2.81.0
4.2.62.11
4.2.62.0

Windows 2003 SP2 32-bit

RHEL 5.x

Windows / RHEL on ESX 3.0.1 and above

No support for 64-bit

6.0.170.0

6.0.188.0
6.0.182.0
6.0.108.0
5.2.193.0
5.2.178.0
5.2.157.0
5.1.163.0
5.1.151.0
4.2.207.0
4.2.205.0
4.2.176.0
4.2.173.0
4.2.130.0
4.2.112.0
4.2.99.0
4.2.61.0

6.0.97.0

November 8, 2009

6.0.132.0
5.2.148.0
5.2.130.0
5.2.125.0
5.2.110.0
5.1.65.4
5.1.64.0
4.2.128.0
4.2.110.0
4.2.97.0
4.2.81.0
4.2.62.11
4.2.62.0

Windows 2003 SP2 32-bit

RHEL 5.x

Windows / RHEL on ESX 3.0.1 and above

No support for 64-bit

6.0.132.0

6.0.182.0
6.0.108.0
5.2.178.0
5.2.157.0
5.1.163.0
5.1.151.0
4.2.205.0
4.2.176.0
4.2.173.0
4.2.130.0
4.2.112.0
4.2.99.0
4.2.61.0

6.0.85.0

June 11, 2009

5.2.130.0
5.2.125.0
5.2.110.0
5.1.65.4
5.1.64.0
4.2.128.0
4.2.110.0
4.2.97.0
4.2.81.0
4.2.62.11
4.2.62.0

Windows 2003 SP2 32-bit

RHEL 5.x

Windows / RHEL on ESX 3.0.1 and above

No support for 64-bit

5.2.148.0

5.2.193.0
5.2.178.0
5.2.157.0
5.1.151.0
5.0.148.2
5.0.148.0
4.2.207.0
4.2.205.0
4.2.176.0
4.2.173.0
4.2.130.0
4.2.112.0
4.2.99.0
4.2.61.0

5.2.100.0

June 25, 2009

5.2.130.0
5.2.125.0
5.2.110.0
5.1.65.4
5.1.64.0
5.0.72.0
5.0.56.2
5.0.56.0
4.2.128.0
4.2.110.0
4.2.97.0
4.2.81.0
4.2.62.11
4.2.62.0

Windows 2003 SP2 32-bit

RHEL 5.x

Windows / RHEL on ESX 3.0.1 and above

No support for 64-bit

5.2.130.0

5.2.178.0
5.2.157.0
5.1.151.0
5.0.148.2
5.0.148.0
4.2.176.0
4.2.173.0
4.2.130.0
4.2.112.0
4.2.99.0
4.2.61.0

5.2.91.0

February 21, 2009

5.2.125.0
5.2.110.0
5.1.65.4
5.1.64.0
5.0.72.0
5.0.56.2
5.0.56.0
4.2.110.0
4.2.97.0
4.2.81.0
4.2.62.11
4.2.62.0

Windows 2003 SP2 32-bit

RHEL 5.x

Windows / RHEL on ESX 3.0.1 and above

No support for 64-bit

5.2.125.0

5.2.178.0
5.2.157.0
5.1.151.0
5.0.148.2
5.0.148.0
4.2.176.0
4.2.173.0
4.2.130.0
4.2.112.0
4.2.99.0
4.2.61.0

5.2.91.0

February 10, 2009

5.2.110.0
5.1.65.4
5.1.64.0
5.0.72.0
5.0.56.2
5.0.56.0
4.2.110.0
4.2.97.0
4.2.81.0
4.2.62.11
4.2.62.0

Windows 2003 SP2 32-bit

RHEL 5.x

Windows / RHEL on ESX 3.0.1 and above

No support for 64-bit

5.2.110.0

5.2.157.0
5.1.151.0
5.0.148.2
5.0.148.0
4.2.176.0
4.2.173.0
4.2.130.0
4.2.112.0
4.2.99.0
4.2.61.0

5.2.91.0

November 24, 2008

5.1.64.0
5.0.72.0
5.0.56.2
5.0.56.0
4.2.110.0
4.2.97.0
4.2.81.0
4.2.62.11
4.2.62.0

Windows 2003 SP2 32-bit

RHEL 5.1

RHEL 5.0

Windows / RHEL on ESX 3.0.1 and above

No support for 64-bit

5.1.65.4

5.1.163.0
5.1.151.0
5.0.148.2
5.0.148.0
4.2.176.0
4.2.173.0
4.2.130.0
4.2.112.0
4.2.99.0
4.2.61.0

5.1.35.0

January 9, 2009

5.1.64.0
5.0.72.0
5.0.56.2
5.0.56.0
4.2.110.0
4.2.97.0
4.2.81.0
4.2.62.11
4.2.62.0

Windows 2003 SP2 32-bit

RHEL 5.x

Windows / RHEL on ESX 3.0.1 and above

No support for 64-bit

5.1.64.0

5.1.151.0
5.0.148.2
5.0.148.0
4.2.176.0
4.2.173.0
4.2.130.0
4.2.112.0
4.2.99.0
4.2.61.0

5.1.30.0

July 21, 2008

5.0.56.2
5.0.56.0
4.2.97.0
4.2.81.0
4.2.62.11
4.2.62.0

Windows 2003 SP2 32-bit

RHEL 5.1

RHEL 5.0

Windows / RHEL on ESX 3.0.1 and above

No support for 64-bit

5.0.72.0

5.0.148.2
5.0.148.0
4.2.130.0
4.2.112.0
4.2.99.0
4.2.61.0
4.1.185.0
4.1.171.0

4.0.38.0

Does not apply

August 5, 2008

5.0.56.2
5.0.56.0
4.2.62.11
4.2.62.0
4.1.91.0
4.1.83.0

Windows 2003 SP2 32-bit

RHEL 5.1

RHEL 5.0

Windows / RHEL on ESX 3.0.1 and above

No support for 64-bit

5.0.56.2

5.0.148.0
4.2.61.0
4.1.x.x

4.0.33.0

Does not apply

April 14, 2008

5.0.56.0
4.2.62.11
4.2.62.0
4.1.91.0
4.1.83.0

Windows 2003 SP2 32-bit

RHEL 5.0

Windows / RHEL on ESX 3.0.1 and above

No support for 64-bit

5.0.56.0

5.0.148.0
4.2.61.0
4.1.x.x

4.0.32.0

Does not apply

February 16, 2008

4.2.62.11
4.2.62.0
4.1.91.0
4.1.83.0

Windows 2003 SP2 32-bit

RHEL 5.0

Windows / RHEL on ESX 3.0.1 and above

No support for 64-bit

4.2.128.0

4.2.207.0
4.2.205.0
4.2.176.0
4.2.130.0
4.2.112.0
4.2.99.0
4.2.61.0
4.1.185.0
4.1.171.0
4.0.216.0
4.0.206.0
4.0.179.11
4.0.179.8
4.0.155.0

3.1.43.0

Does not apply

May 13, 2009

4.2.110.0
4.2.97.0
4.2.81.0
4.2.62.11
4.2.62.0
4.1.91.0
4.1.83.0
4.0.100.0
4.0.97.0
4.0.96.0
4.0.87.0
4.0.81.0
4.0.66.0

Windows 2003 SP2 32-bit

RHEL 4.0

RHEL 5.0 (No. 5.1 and later supported)

Windows / RHEL on ESX 3.0.1 and above

No support for 64-bit

4.2.110.0

4.2.176.0
4.2.130.0
4.2.112.0
4.2.99.0
4.2.61.0
4.1.185.0
4.1.171.0
4.0.216.0
4.0.206.0
4.0.179.11
4.0.179.8
4.0.155.0

3.1.42.0

Does not apply

29 sep 2008

4.2.97.0
4.2.81.0
4.2.62.11
4.2.62.0
4.1.91.0
4.1.83.0
4.0.100.0
4.0.97.0
4.0.96.0
4.0.87.0
4.0.81.0
4.0.66.0

Windows 2003 SP2 32-bit

RHEL 4.0

RHEL 5.0

Windows / RHEL on ESX 3.0.1 and above

No support for 64-bit

4.2.97.0

4.2.176.0
4.2.130.0
4.2.112.0
4.2.99.0
4.2.61.0
4.1.185.0
4.1.171.0
4.0.216.0
4.0.206.0
4.0.179.11
4.0.179.8
4.0.155.0

3.1.38.0

Does not apply

June 3, 2008

4.2.81.0
4.2.62.11
4.2.62.0
4.1.91.0
4.1.83.0
4.0.100.0
4.0.97.0
4.0.96.0
4.0.87.0
4.0.81.0
4.0.66.0

Windows 2003 SP2 32-bit

RHEL 4.0

RHEL 5.0

Windows/RHEL on ESX 3.0.1 and above

No support for 64-bit

4.2.81.0

4.2.99.0
4.2.61.0
4.1.185.0
4.1.171.0
4.0.216.0
4.0.206.0
4.0.179.11
4.0.179.8
4.0.155.0

3.1.36.0

Does not apply

March 17, 2008

4.2.62.11
4.2.62.0
4.1.91.0
4.1.83.0
4.0.100.0
4.0.97.0
4.0.96.0
4.0.87.0
4.0.81.0
4.0.66.0

Windows 2003 SP2 32-bit

RHEL 4.0

RHEL 5.0

Windows / RHEL on ESX 3.0.1 and above

No support for 64-bit

4.2.62.11

4.2.61.0
4.1.185.0
4.1.171.0
4.0.216.0
4.0.206.0
4.0.179.11
4.0.179.8
4.0.155.0

3.1.35.0

Does not apply

January 25, 2008

4.2.62.0
4.1.91.0
4.1.83.0
4.0.100.0
4.0.97.0
4.0.96.0
4.0.87.0
4.0.81.0
4.0.66.0

Windows 2003 SP2 32-bit

RHEL 4.0 update 5

Windows / RHEL on ESX 3.0.1 and above

No support for 64-bit

4.2.62.0

4.2.61.0
4.1.185.0
4.1.171.0
4.0.216.0
4.0.206.0
4.0.179.11
4.0.179.8
4.0.155.0

3.1.35.0

Does not apply

November 9, 2007

4.1.91.0
4.1.83.0
4.0.100.0
4.0.97.0
4.0.96.0
4.0.87.0
4.0.81.0
4.0.66.0

Windows 2003 SP2 32-bit

RHEL 4.0 update 5

Windows / RHEL on ESX 3.0.1 and above

No support for 64-bit

http://www.Cisco.com/en/us/docs/wireless/WCS/release/notes/WCS_RN7_0_172.html

See you soon!

Rob

PS: + 5 to my friend Leo with the invisible stars

WISN upgrade to 6.0.188

I will move my WISMs to 6.0.188 from the GUI. In the installation notes it say to close the port-channel controller.

When I do so I can't get controllers to start the download. If I download the new IOS will be the controller

restart automatically? If if do not know how it would happen. You stop the port channel after the start to recharge?

Thanks for the help!

Pete

What you need to do is to move out of one of the WLC access point and then move this WLC to 6.0.188. Then move the access point

Return to WLC to ensure that everything works. then all that you move the ap for the upgrade

WLC and upgrade your other WLC on the WISN. You need to restart the WLC after the upgrade, however.

WLC displays a different IP address for LAP in GUI

Hello

I have the following problem with a single AIR-WLC2112-K9 controller with 2 KNEES. When I ask the news by GUI for the towers wireless---> name AP (click)---> General Info displayed in the "IP Configuration" not corresponding to the address field appears static IP 172.18.98.2 IP address, but the line above "IP address" shows 156.70.30.5. Controller has IP 156.70.30.3

I checked the console with the command show ip config lwapp and the IP address is correct. 172.18.98.2.

any idea?

It is a hill and well documented issue of the WLC that you can set static IP address to a LWAP. I use 6.0.188.0 and it's random. What firmware version do you use?

Backup the IOS on a WLC 5508

Hello

Hope someone can help me, I have a Cisco 5508 WLC and wanted to backup the IOS.

Is there an easy way to do it? or a Cisco restrict this function with the new IOS licensing model?

Second question, with WLC 5508 IOS version 7.0.98 I see that there is no field recovery Image, is that correct?

See you soon,.

Ron

I guess that you Q #1 has been addressed above.

For your Q n ° 2 'the second question, with WLC 5508 IOS version 7.0.98 I see that there is no field recovery Image, is this correct?"

Yes that is correct

-->

(w-5508-1) > show sysinfo

Name of the manufacturer... Cisco Systems Inc..
Product name... Cisco controller
Version of the product... 7.0.98.0
Bootloader Version... 1.0.1
Retrieving Image Version field... N/A

And it's a CSCth43373 bug

5508 7.0 running shows the version of field recovery images by n/a
```
Symptom:

5508 shows Field Recovery Image version as N/A.
Conditions:
Upgrade 5508 to version 7.0.98.0
Workaround:
None
```
--

You will have to wait for the new 7.0 code to appear on Cisco.com

Be sure to mark the thread as solved if you feel that your issue has been addressed.

Thank you

Serge

HOWTO to Setup wpa2 + aes + psk with mac-filter WLC 4402 (RADIUS)

Hello

I'm trying to Setup wpa2 + aes + psk with mac-filter (RADIUS) on WLC 4402 (6.0.182), with Lap - 1142

on security, the value L2 security wpa + wpa2 and make sure MAC filtering

Uncheck the WPA

check the WPA2, AES, TKIP to unckeck

Mgmt PSK auth key

PSK ASCII marker

L3 no

Uncheck the political web

AAA servers

Select enable accounting radius server server

It's work fine, when I use WEP with mac-filter (radius)

but when I select WPA2 is it fail and no newspaper both WLC server and RADIUS

Is this limitation or bug...

Thanks in advance for your help

This sounds like it should work. Maybe your client likes not wpa2/aes or does not match the PSK. I would try to associate with this same configuration, but without enabled mac filtering to try to identify the problem.

-John

Impossible to 2504 WLC with new operating system

Hello

I got a cisco WLC 2504 with the version of the OS - 7.0.112.56. When I tried to upgrade to the new operating system, it gives below error.

(Cisco Controller) > transfer download starts

Mode............................................. TFTP
Data Type........................................ Code
TFTP Server IP... 192.168.1.1
TFTP package Timeout... 6
Attempts to TFTP Max... 10
TFTP Path........................................ /
Name of the TFTP file. Air-CT2500-K9-8-3-102-0.AES

This can take some time.
Are you sure you want to start? y (y/N)

Transfer of TFTP boot Code.

TFTP receive full... extraction of components.

Failed version of image control. Version 8.3.102.2 not supported.

Transfer failed: incompatibility of Version - the version of the image is not for this model

TFTP failed while storing it in flash!

Please help in this case if someone knows the question.

Thanks in advance

Version of the product... 7.0.112.56

It could be a bug. This is a special version of technology.

Try to upgrade to, say, 7.0.252.0 and see if it works. If so, then go directly to 8.3.X.

Version of the IOS WLC 2125 for L3 ap-mode?

Hello

I tried to search for this topic, but always without success. can someone please tell me if that fix the version of IOS for wlc can I use to support L3 ap-mode?

Here's my current version;

NAME: "Chassis", DESCR: "Cisco wireless controller.
PID: AIR-WLC2125-K9, VID: V05, SN:

Built-in MAC address... 68:EF:BD:04:55:2 A

Press Enter to continue or to abort.

Information System
Name of the manufacturer... Cisco Systems Inc..
Product name... Cisco controller
Version of the product... 6.0.188.0
RTOS Version... 6.0.188.0
Bootloader Version... 4.0.191.0
Version of the Image of emergency... N/A
Build Type....................................... DATA + WPS

Thanks in advance!

see you soon,

Dayve

Hi stephane,

The link below will answer your question...

http://www.Cisco.com/en/us/docs/wireless/controller/5.2/configuration/guide/c52ovrv.html#wp1069102

It's...

Version 5.2 or a later version of the controller software support only mode Layer 3 CAPWAP, versions 5.0 and 5.1 of the controller software load only Layer 3 LWAPP mode and controller software versions prior to 5.0 supports 2 layer or Layer 3 LWAPP mode.

Concerning

Surendra

Cisco ISE 1.2 & Cisco WLC 5508 v7.6

Hi all

We intend to upgrade our WLC to 7.6 to fix a bug with FlexConnect customer ACL but I just saw on the ISE Cisco compatibility table which it recommended only up to the WLC 5508 v7.5...

Cisco told me to avoid 7.5 as it is in a State of defferred if anyone know or are running in a laboratory or production, ISE1.2 with a WLC v7.6 n 5508?

I wish I knew rather questions of people know before hand than to have to go through a software update, and then restore.

Thank you all

Mario Rosa

Definitely stay away from 7.5. I've done several deployments with the WLCs 7.6 running. The two main issues that I touched were:

CSCue68065 - in this bug FlexConnect ACL does not work unless you have a regular (non FlexConnect) ACL created with exactly the same name

CSCuo39416 - CWA does not not on FlexConnect APs. It would apply to you if you have older models APs

I hope this helps!

Thank you for evaluating useful messages!

ACS 5.0 - WLC could not authenticate

Salvation of the Forumers

My script is

1 using the microsoft AD running on window 2008, use ad server to perform authentication of identity

2. I let successfully the ACS 5.0 device link and join the domain created on the AD server.

3. I have also set up on WLC 2100 series with the right key on pre-shared, server IP RADIUS (which is my ACS appliance IP)

Problem statement:

1. try to access the network Journal ACS showing the error log 'Unknow CA, a no authentication'. (I know I'm missing to place certificate for EAP protocol somehow...)

Question:

1. to solve this problem, I can generate self-signed certificate ACS, then let the WLC import the certificate self-signed GBA?

(so EAPoW challenge can happen as ACS and WLC are reciprocal trust, which, in my view, ACS simply use the user of the AD, so in this cse ACS database is the authentication server and WLC is the authenticator and my AP / user's begging him, am I rite?)

can I not like it? Appreciate all feedback and response!

2. If we are not my thought, can you please suggest me a solution (my requirement, it is not using any third party trusted agent certificate)

Thank you

Noel

Hi Noel,

If I can update your list, the components must be the following:

-ACS authentication server =

-WLC = authenticator

-wireless client = client

Use of certificates for EAP authentication between client wireless and ACS (devices performing the EAP authentication): the WLC check all ACS certificate.

You can certainly create a self-signed certificate on ACS for PEAP for example working.

On the client, you must then either not to validate a server certificate or to import GBA self-signed certificate as a CA certificate root to trust the self-signed certificate ACS itself when sent by ACS during the configuration of the PEAP TLS tunnel.

One final note, for WLC working with ACS 5.0, please make sure you are on the patch
5.0.0.21.6 or later

http://www.Cisco.com/cgi-bin/tablebuild.pl/acs5_patches

in order to avoid the known bug CSCsy17858

http://Tools.Cisco.com/support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&bugId=CSCsy17858

Kind regards

Fede

--

If this helps you or answers to your question if it you please mark it as 'responded' or write it down, if other users can easily find it.

WLC 6.0.188.0 bug

Similar Questions

Maybe you are looking for