WLC 7.5 Release

Do you recommend this version given that it is still fairly new?

As Leo said, it is depend on your requirement. If you looking for a feature which is not available in 7.4.x or earliear then you have to go with it. Refer below post to see few new features introduced in this code
http://mrncciew.com/2013/09/02/why-i-want-to-go-for-wlc-7-5/
I am running this code in my Guest Anchor WLC (5508) & primararly due to a feature requirement with OEAP600 (Split tunneling for printing).
Here are some important bugs (I have already encounted) that you should be aware if you are going with 7.5.102.0 code.
1. CSCui69732 - 802.1p tagging value changed, Platinum 6 to5, Gold 5 to 4, Silver 3 to 2
2. CSCui87814 - Cannot open WLC GUI in Chrome-29 with 'https. {Also impact guest wireless with android devices}
Workaround:
Configure this, save/reboot controller:
config network secureweb cipher-option rc4-preference enable
3. CSCuj18674 - captive portal/wispr support for apple ios7
Below release note will listed all other un-resolved bugs & you need to read & see those are applicable to your environment.
http://www.cisco.com/en/US/docs/wireless/controller/release/notes/crn75.html
Below link should provide information about Wireless Hot Issues based on the reported TAC cases. I normally keep an eye on this & see software version I am running having those crtical bugs.
http://www.cisco.com/warp/public/146/news_cisco/data/syndication/ext/tachi/ExternalWireless.xml
HTH
Rasika
**** Pls rate all useful responses ****

Similar Messages

WLC 7.4 release date?

Do we know when the 7.4x software will be released? It was rumoured it was going to contain the bonjour gateway implementation and I am keen to try.

That would be a frivolous case. Anything you can say on a TAC case, you can mention here Van.
@Codflanglers no matter what they say as to the release date, don't believe it until you see it on cisco.com in the available downloads section.
HTH,
Steve
Please remember to rate useful posts, and mark questions as answered

5508 WLC not releasing DHCP addresses

Have a WLC 5508 running 7.0.230 with internal DHCP server. Timeout is 3600 seconds. The IP addresses never seem to be released.
The controller will show 70 clients but 254 addresses will be assigned. Has anyone else experienced this problem?

#Check "Lease remaining time" change in this value on the WLC for the clients that are not currently connected and already connected to it. Watch if its getting removed/refreshed once the lease time is expired.
#Cross reference with cli as well.
#If its an open wlan, client pass by will get an ip, so what admin seeing could be new client keep coming in and its an expected behavior.
#Find if time is static or client's dhcp entry doesn't remove once lease time expired.
#Per design, WLC doesn't release the internal dhcp ip when the client sends deauth to WLC, however, it should when the timer gets expired for clients that were currently not connected.

Does WLC release 7.6 support internal DHCP when AP and client SSO is configured?

Hi,
I currently have 5508 WLCs running on release 7.6 and they are to be configured in 1:1 HA mode. Would like to know if internal DHCP is supported if AP and client SSO is to be configured.
Thanks in advance.

Unfortunately, till date no AirOS release supports Internal DHCP when AP SSO is configured.
For details, check HA Deployment Guide. It says following :
"Internal DHCP is not supported when SSO is enabled."
-Thanks
Vinod

WCS WLC support

Hi,
We are running version 4.2.62 of Cisco WCS.
I'd like to upgrade to 4.2.128. We run version 4.2.209.0 on our WLCs.
The release notes for WCS version 4.2.128 does not list WLC version 4.2.209 as a supported version.
I would think it would be OK but can anyone confirm if this will actually work?
Also, is it worth upgrading the WCS to the more recent 7x versions?
thanks.

Hi,
The release notes mention with which version the WCS has been tested. So since 4.2.62 WCS came at the same time as 4.2.61 WLC it doesn't state it supports other 4.2 versions since it could not have been tested with those. However, since they are the same major release, all should be ok but you'll maybe face minor bugs here and there.
So just upgrade your WCS to the last 4.2 version of WCS and you'll be good to go :-)
Regards,
Nicolas
===
Don't forget to rate answers that you find useful

EAP-FAST - WLC 7.4 Roaming between different FlexConnect (FC) Group

Dear all,
WLC 7.4 Release Notes states that with both Local/Central Switching:
- Mobility in the same Flex Group with CCKM is Fast Roaming if WLAN is mapped to same VLAN
- Mobility between different Flex Group with CCKM cause a Full Auth
Using CCK with EAP-Fast during a call with Cisco IP Phone 7921G and 7925G we notice a gap when roaming from an AP belonging to FC GroupA to an AP belonging to FC Group B...so the only solution to do Fast Romaing is to use PMK(OKC) since CCKM will do a complete authentication each time moving from FC Group.
Where do we enable OKC for a specific WLAN? In the FlexConnect Group Menu?
Thanks a lot for sharing answer and suggestion
BR
O.G.

Hello Scott,
thanks for the explanation...
So if in 7.4.121 OKC is enabled by default I don't understand why I'm having a full Authentication when roaming from AP of FC Group A to AP to FC Group B instead of Fast-Roaming...and this is happening in all FC Group configured (6x).
Should I disable CCKM flag in the WLAN definition?!?!
FC Groups and Mobility
http://www.cisco.com/c/en/us/support/docs/wireless/5500-series-wireless-controllers/112042-technote-product-00.html#anc13
O.G

TX Power Levels are low after WLC upgrade to 7.0.98.0

I recently upgraded our WLC 4404 to release 7.0.98.0. The process was very smooth with no
issues. The controller manages access points in two buildings. Prior to the upgrade the access points were maintaining high TX power levels...typically between 1 and 3. After the upgrade the power levels all droped to 6 and 8. I have confirmed that the correct external antenas have been set for each access point. I have not done a site survey to see if the lower power levels are acceptable. But the environment has been very consistent for the past year with regards to TX power levels. For the time being I have manually set a power level of 2 to prevent any service outages. Is there any explanation as to why the power levels have changed so drastically?

My customer is having a simlar problem with 2106 controller and 1131 AG access point.
After I upgrade the controller for 7.0.98.218, the access points was setting automaticly by controller with power level "0".
When its happening I see the follwing logs
Thu Dec 15 12:19:15 2011 AP's Interface:1(802.11a) Operation State Down: Base Radio MAC:00:3a:98:19:e7:c0 Cause=Heartbeat Timeout Status:NA
70 Thu Dec 15 12:19:15 2011 AP's Interface:0(802.11b) Operation State Down: Base Radio MAC:00:3a:98:19:e7:c0 Cause=Heartbeat Timeout Status:NA
Can You help me?
thanks, Murilo

Wlc 5508 - ap 1141N

/* Style Definitions */
table.MsoNormalTable
{mso-style-name:"Tabella normale";
mso-tstyle-rowband-size:0;
mso-tstyle-colband-size:0;
mso-style-noshow:yes;
mso-style-priority:99;
mso-style-qformat:yes;
mso-style-parent:"";
mso-padding-alt:0cm 5.4pt 0cm 5.4pt;
mso-para-margin:0cm;
mso-para-margin-bottom:.0001pt;
mso-pagination:widow-orphan;
font-size:11.0pt;
font-family:"Calibri","sans-serif";
mso-ascii-font-family:Calibri;
mso-ascii-theme-font:minor-latin;
mso-fareast-font-family:"Times New Roman";
mso-fareast-theme-font:minor-fareast;
mso-hansi-font-family:Calibri;
mso-hansi-theme-font:minor-latin;
mso-bidi-font-family:"Times New Roman";
mso-bidi-theme-font:minor-bidi;}
hello guys, I would like to know if anyone of you ever had problems related to the n-channel on the access-point and how did you solve it?
I have placed 20 AP1141N with WLC 5508 latest release 7.0.1
but when I activate the function N I have a performance degradation.
I need to use the n-channel to enable for greater throughput.
thanks for the help me.

Hello Leo, I indicated that the degradation, and that users who connect to the access-point not only travel at a slower speed not remain connected all the time you drop.
thenks for help me

WLPS/WLCS 3.5 and Campaign Mananger 1.1 Ships!

All,
We recently put WLPS and WLCS 3.5 on the web. These new releases add new
features and run on WLS 6.0 allowing you to use new WLS features, such as
two-phase commit across different databases.
http://www.bea.com/products/weblogic/commerce/whatsnew.shtml
In addition we have completed a new product offering - the Campaign Manager.
Campaign Manager is a Swing application that allows business users to create
targeted, personalized campaigns for sites running WLPS or WLCS. You can
define discounts, send emails, select personalized content, track
advertisements, perform dynamic user segmentation etc. etc.
http://www.bea.com/products/weblogic/campaign/index.shtml
All without a single line of Java or JSP code. Just start up the WLPS or
WLCS templates, boot-up the Campaign Manager and start clicking!
There cool! Check 'em out - you can download all three here:
http://commerce.beasys.com/downloads/commerce_servers.jsp#wlcs
Sincerely,
Daniel Selman

We were using WLCS 3.2 and WLS 5.1 SP8 so far, we got a patch
(patch_CR043462) from BEA in response to some bugs we reported ( BEA Support
Case: 222714). This patch had some new classes (e.g.
CommerceInputProcessorExtended, PipelineSessionExtended) and to use them we
changed the code. The site is live now. I'm now trying to find the
effort/feasibility of migrating to WLS 6 and WLCS3.5. But during the
migration I found that the above patch is not shipped with WLCS 3.5. So my
question is, can we use the old patch given to us with WLCS 3.5 or shouldn't
it be part of the new WLCS 3.5 release ? What BEA suggests about this.
Regards,
Ajay Upadhyaya
"Daniel Selman" <[email protected]> wrote in message
news:3adf2542$[email protected]..
All,
We recently put WLPS and WLCS 3.5 on the web. These new releases add new
features and run on WLS 6.0 allowing you to use new WLS features, such as
two-phase commit across different databases.
http://www.bea.com/products/weblogic/commerce/whatsnew.shtml
In addition we have completed a new product offering - the CampaignManager.
Campaign Manager is a Swing application that allows business users tocreate
targeted, personalized campaigns for sites running WLPS or WLCS. You can
define discounts, send emails, select personalized content, track
advertisements, perform dynamic user segmentation etc. etc.
http://www.bea.com/products/weblogic/campaign/index.shtml
All without a single line of Java or JSP code. Just start up the WLPS or
WLCS templates, boot-up the Campaign Manager and start clicking!
There cool! Check 'em out - you can download all three here:
http://commerce.beasys.com/downloads/commerce_servers.jsp#wlcs
Sincerely,
Daniel Selman

Wlc ha question

hi all ,
our primary wlc has failed and we received a new one from rma.
Now If I set ha between the new wlc and existing one.will existing wlc push up configuration to new wlc (primary)?
release 7.4
thanks in advance

High Availability in Release 7.3 and 7.4
The new architecture for HA is for box-to-box redundancy. In other words, 1:1 where one WLC will be in an Active state and the second WLC will be in a Hot Standby state continuously monitoring the health of the Active WLC via a Redundant Port. Both the WLCs will share the same set of configurations including the IP address of the Management interface. The WLC in the Standby state does not need to be configured independently as the entire configuration (Bulk Configuration while boot up and Incremental Configuration in runtime) will be synced from the Active WLC to the Standby WLC via a Redundant Port. The AP's CAPWAP State (only APs which are in a run state) is also synced, and a mirror copy of the AP database is maintained on the Standby WLC. The APs do not go into the Discovery state when the Active WLC fails and the Standby WLC takes over the network's Active WLC.
There is no preempt functionality. When the previous Active WLC comes back, it will not take the role of the Active WLC, but will negotiate its state with the current Active WLC and transition to a Standby state. The Active and Standby decision is not an automated election process. The Active/Standby WLC is decided based on HA SKU (Manufacturing Ordered UDI) from release 7.3 onwards. A WLC with HA SKU UDI will always be the Standby WLC for the first time when it boots and pairs up with a WLC running a permanent count license. For existing WLCs having a permanent count license, the Active/Standby decision can be made based on manual configuration.
http://www.cisco.com/c/en/us/td/docs/wireless/controller/technotes/7-5/High_Availability_DG.html#pgfId-74573

How to create a custom DACL in ISE

Hello once again,
I'm puzzled over the note that I found at
http://www.cisco.com/en/US/docs/security/ise/1.0/user_guide/ise10_authz_polprfls.html#wp1136540
Namely the one that says:
The Name and DACL Content fields require that values be entered and are marked with an asterisk (*).
How would I interpret it? What's the proper syntax to create an DACL?
I created my own one the way I would do it in ACS, i.e.
ip:inacl#1=permit udp any host 192.168.1.100 eq 53
ip:inacl#1=deny ip any 192.168.1.0 255.255.255.0
ip:inacl#2=permit ip any any
But it doesn't work when I apply it to the authorization profile

Sorry about that, WLC do not support the dacl feature, this for switches and ASAs that support DACL feature. I assumed you were wanting this for wired.
http://www.cisco.com/en/US/docs/security/ise/1.1.1/compatibility/ise_sdt.html
Here is the note that metions this in the release notes:
4
Wireless LAN Controllers (WLCs) do not support downloadable ACLs (dACLs), but support named ACLs. WLCs prior to release 7.0.116.0 do not support CoA and require deployment of an ISE Inline Posture Node to support posture services. Use of Inline Posture Node requires WLC version 7.0.98 or later. Autonomous AP deployments (no WLC) also require deployment of an Inline Posture Node for posture support. Profiling services are currently supported for 802.1X-authenticated WLANs only on the WLC with CoA support. HREAP is not supported. WLCs do not currently support MAC Authentication Bypass (MAB).
thanks,
Tarik Admani
*Please rate helpful posts*

Anchor Controller with 8021.x

Hello,
I would like to know if the Anchor controller is compatible with 802.1x.
For my guest Wireless I would like to authentification with WPA2 AES on Layer 2 and a second authentification in Layer 3 with web authentification.
I have tested it with my controller and it's working but when I apply my anchor mobiltity group it don't work.
Could you please help me.
Best Regards

The process? The foreign elf and the anchor has to have the same configuration on the WLAN. The only exception is really the profile name and the interface. If the layer 3 is using radius to authenticate, then your guest anchor has to communicate to the radius. If your using local username and password, then that has to be defined in the anchor.
Mid you haven't setup anchoring before, create a new open ssid and make sure anchoring works.
https://supportforums.cisco.com/document/11936816/cisco-guest-access-using-wlc-anchor-setup-–-release-70
-Scott

ISE vs Packet Fence

Hello,
I'm currently studying a solution for AAA in my company. Since I've got an almost full Cisco network architecture, I've read a lot about ISE.
But recently I hear about Packet Fence, an open source project which seems to offer the same features.
So I'd like to get some of your advices about this software against ISE : is it worth it to get it ? What are advantages and drawbacks of this one ?
Since we're on a Cisco forum i'm not expecting you to tell me that Packet Fence is better, but I'd just like to get objective reviews.
Thankfully,
Yoshipower.

Hi Ravi,
I am also looking at the same options and I was heading entirely in the ISE direction until I realised that there is not full support for non-WLC WiFi systems. So since I have an AP1141 this seems to mean that I would be as well to go with Packet Fence as the best I will get from either solution is basic 802.1x authentication?
Footnote number 4 on Table 1 of this document seems to cover most of the limitations:-
http://www.cisco.com/en/US/docs/security/ise/1.0.4/compatibility/ise104_sdt.html
"Wireless LAN Controllers (WLCs) do not support downloadable ACLs (dACLs), but support named ACLs. WLCs prior to release 7.0.116.0 do not support CoA and require deployment of an ISE Inline Posture Node to support posture services. Use of Inline Posture Node requires WLC version 7.0.98 or later. Autonomous AP deployments (no WLC) also require deployment of an Inline Posture Node for posture support. Profiling services are currently supported for 802.1X-authenticated WLANs only on the WLC with CoA support. HREAP is not supported. WLCs do not currently support MAC Authentication Bypass (MAB)."
So based on the above the ISE is not able to offer me profiling services or CoA. And I can only get posture support if I have an inline node everywhere that I have an AP?
Thanks
David

Radius request source interface

HI !
I have controllers WLC 5508 and release 7.4.
If I, in the WLAN configurations about AAA and radius servers, use the possibillty to change the radius request source interface by "Radius Server Overwrite Interface" it will, use the interface that the SSID is configured to, as a source address.
If my SSID is configured to a interface group, what will happend then??
Will only the first configured vlan be used as a source or will he vary the source address between the vlan included inte the interface group?
(It, of cource, need to be the the same every the time, every request and predictable)
/mats

Hi,
Yes, I did get an answer on my tac-case on this. It will use the first configured vlan in the group.
I have had it configured and use "radius server overwrite" on the interface group right now. It working this way since these months. It seems to work well. :-)
/mats

Wireless Controller 4402 Crash

Hi,
I will make an abbreviation report about my case. My WLC 4402 was running 4.0.217.0 version. There are 18 access point work with local. It's work fine.
To a new project, we will add a access point 1522 and others 1242 to extend the range to a small building using mesh indoor (enterprise mesh).
To make this I read that I need use 5.2 version on WLC. So, I upgrade the WLC (locally) to release 4-2-176-0 and It's work fine (I don't install the new access points yet).
After, I upgrade the WLC to release 5-2-157-0 and install a 5-2-157-0-ER, according to document release. After reboot of new release 5.2, the WLC begin crash and reboot.
I make a downgrade to 4-2-176-0 because my client needed to work, and it's work fine.
In attached is the âtech-supportâ of Controller.
More one information! I too have a WCS that was with release 5.0.56.2 and I upgrade to 5.2.110, before upgrade the controller.
Sorry, because my English is not so good.
thanks
Claudio

If you downgrade from one release to another, you may lose the configuration from your current release. The workaround is to reload the previous controller configuration files saved on the backup server or to reconfigure the controller.
Before upgrading your controller to software release 5.2 in a mesh network, check the boot variable setting before updating the boot. If the boot system image is visible, then no boot variable update is required. If the boot system image is missing, then you must update the boot variable. Refer the below URL for more information on how to check boot variable setting.
http://www.cisco.com/en/US/docs/wireless/controller/5.2/configuration/guide/c52mfw.html#wp1101710

WLC 7.5 Release

Similar Messages

Maybe you are looking for