Upgrade wlc 2106 for mesh

Hi,
I want to upgrade my WLC for meshing network. The last release is 4.1.192.22M but in the release note it's write 4.1.192.17M in the upgrade path ...
Another point is that the release 4.1.190.5 isn't present int the download section.
What's the path for the upgrade ?

You can follow the upgrade path in the release notes. 4.1.185.0 - 4.1.190.5 - 4.1.191.24M - 4.1.192.22M.
I just checked and 4.1.190.5 is located under the Mesh Code link for the controller, All Releases, 4.1

Similar Messages

Second WLC 5508 for HA N+1 with Mesh Network

Hi,
End user has a WLC 5508 and around 12 LAPs (an increasing un short time) configured and working for mesh network (some ROOTs and MAPs)
now is the way to deploy an additional 5508 in another site so that be the backup of the first controller.
Taking into account that is a mesh network what would be the options in WLC's config so that we can have the shortest time for LAPs to associate to
the backup controller?
I appreciate your comments
regards

yes, wlcs can be on different sites. be sure to configure primary, secondary wlc name and ip on those APs.

WLC 2106 and Linksys Bridge WET610N works with 7.0.116.0 release?

Hi all,
i'm having troubles with WLC 2106 controller and several wireless bridges, so i'd like to know if i can fix it in some way.
My environment is as follows:
1 WLC 2106 with 2 Aironet 1240G
I have a production appliance that needs an ethernet port to work, so i bought a Linksys Bridge WET610N to make it works via wireless.
The Linksys bridge connects to the 1240G as a client and works well, but the appliance connected to the ethernet port of the bridge is unreachable.
Searching for the problem, i found that the wlc act as a proxy arp for the wireless clients and being the ethernet appliance a "passive" client, the controller isn't aware of it.
My WLC is running the 7.0.98.0 firmware. In the release notes for the 7.0.116.0, in the "Non-Cisco WGB Support" seems to state that now also non cisco bridges can work using the passive client feature. I've already enabled it on my controller but this didn't solve my problem.
Can anyone tell me if the upgrade to the 7.0.116.0 can fix it?
Thanks in advance
Riccardo Coppola

I'm not sure what (cheap) devices can do the wgb feature that is inter-brand compatible.
The thing is that the WLC enforces the rule "1 wireless client = 1 client". Meaning you can't bridge multiple clients behind a wireless clients, that just screws up roaming mechanisms etc ...
Cisco WGBs have the IAPP protocol to tell the WLC "listen, I'm a WGB wireless client and those are the wired clients connected to me, allow them on the network".
What does "universal WGB" feature does is that the WGB forwards the traffic of the client (only 1 client supported in this case !) to the infrastructure AP but the WGB never sends anything with its own mac address. It uses the client mac address as source.
This means that the WLC has no way of knowing that there is more than 1 device. It just thinks that your wired client is a wireless client.
So it's more than mac cloning since the WgB has to be the one authenticating to the infrastructure (Wpa/wpa2 whatsoever) by spoofing the client mac. The WGB is still in charge of roaming decisions and so on and so on...
I hope it clarifies the situation ?

WLC-2106 and multiple interfaces on the same network

Hi there,
I recently created a TAC request to the Cisco support regarding our WLC-2106, but they could not help me. Basically I just learned that you can create new interfaces for the wireless LAN controller and then dedicate them to a given wireless network (SSID). This way I could more effectively utilize network bandwidth also. Problem is that all of the interfaces have to be in a different network segment in order to work, which is not what I want. I specifically want to have several interfaces on the same network segment.
Has anyone tried to accomplish the same?

Basically what I've misunderstood is that all the traffic generated by our wireless clients have been going through the single 100Mbit/s ethernet port on the wireless LAN controller (management interface), and to mitigate this I thought I could create new interfaces (ports) and dedicate those to given WLAN networks.. I see now that this is not supported. Not inside the same network at least.
So, by reading further and consulting my best friend Google I learned about a setting called "AP Mode". Changing that from Local (the default) to H-REAP the APs should not route their traffic anymore through the management interface on the wireless controller, but instead route all the client traffic directly to the local LAN. This way you effectively remove the 100Mbit/s bottle-neck when all the APs were using the management interface both for configuration and client data traffic.
It seems you also have to enable H-REAP Local switching from a given WLAN network in addition to changing the AP Mode of your access points to H-REAP. I'm still in the testing phase here so should anyone have any insight to this, I'd be greatful to hear more.

AP 1140 and WLC 2106

Does someone know if WLC 2106 support AP 1140 ? I read that AP 1140 is CAPWAP only and I don't know if WLC 2106 supports CAPWAP.
Thanks

Yes it does, you may have to upgrade your controller software to get 802.11n and CAPWAP, use the latest code 6.0.182.
CAPWAP was supported from code 5.2.157
The max throughput on the 2106 though is only 100mbps so yo wont see the highest speeds

DMZ Anchor WLC setup for Wireless Guest Access

I have the following setup.
A DMZ WLC 4402 connected to firewall DMZ interface in 10.10.73.0/24 network.
An Inside WLC 2106 connected to firewall Inside interface in 10.10.71.0/24 network.
Both WLCs are running the same 4.2.176 code.
DMZ WLC is anchor to itself and Inside WLC select the DMZ WLC as the anchor point.
I have setup EoIP between DMZ and Inside WLCs successfully with both the control and data path both show as UP status. >> "show mobility anchor"
The main issue: Clients cannot obtain IP addresses after connected to Guest SSID.
1. Inside WLC, the guest WLAN ingress is 802.11b/g radio and egress port is set to management interface (EoIP) of type WLAN.
What is the DMZ WLC setting? Is the ingress set to "802.11b/g" which does not make sense because the ingress is EoIP from Inside WLC?
Or I still set as 802.11b/g? Same config as Inside WLC? I read from other threads suggested by Terry that the config must be the same for both WLCs.
In the Inside WLC, I saw alot of pdu encapsulation errors for broadcast packets which is ffff.ffff.ffff xxxx which I think is the DHCP request from the connected Wireless clients not making through the EoIP tunnel. I have set static ip for the Wireless client but the packets cannot route through the EoIP tunnel to the far end.
2. DHCP server is provided by DMZ WLC with the scope 10.10.76.0/24. In the Inside WLC, which DHCP server IP adddress to set to? DMZ WLC mgmt ip address? DMZ WLC, the DHCP server is also set to DMZ WLC mgmt ip?
3. Layer 2 authentication. I read that DMZ WLC is supposed to be the DHCP server, Layer 2 or 3 authentication for Wireless Clients. However, it seems like Inside WLC is required to configure the Layer 2 authentication parameters and the DMZ WLC is set to providing the DHCP service?
4. Lastly, anyone has done DMZ WLC sending the Wireless clients traffic to Bluecoat proxy server before hitting the Internet?
Thanks.

One of the biggest things is to make sure the wlan is configured exactly the same. The DMZ WLC ingress is the management and also is the egress port. You can create a dynamic interface on the DMZ WLC, but this way makes thing easier. The DMZ WLC should provide the dhcp, so the dhcp scope of course will be on the same subnet as the management of the DMZ WLC. The DHCP Server will be the ip address of the management interface of the DMZ WLC. The authentication also has to be configured exactly the same on the inside wlc and the DMZ wlc. Since you are pushing clients through the tunnel to the DMZ WLC, that is where clients will need to get their ip address, since that DMZ WLC has a network interface to the guest network. I haven't had luck when a proxy is involved, but I know there was a post a while ago on how to setup the proxy to allow the wlc to bypass the users initial dns resolution.

WLC code for point to point bridging

What is the best WLC code for point to point and point to multipoint bridging on a 2504 with 2602 APs? 7.2-7.4 had transparent vlan issues and I'm not sure if they were fixed in 7.5-7.6. We have 5-6 vlans that we are needing to bridge between a large open area. Also, are there any bugs with wireless mesh and ISE?

You do not have many choices now, only 7.0.250.0, 7.4.121.0 & 7.6.110.0 codes are supported by Cisco. All other codes have been deferred by them.
I do not have configured those set-up to advise you specific to that. I would think 7.6.110.0 may have fixed whatever the known bugs in previous versions.
HTH
Rasika
**** Pls rate all useful responses ****

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

Want to configure wpa2 enterprise in wlc 2106

Hi,
I want to configure the wlc 2106 with wpa2 enterprise .... i reckon that iI need ACS server ( Radius Server ) with server certificate as well client certificate.
how do i configure the redius server to get access through wpa2 enterprise .. If i am wrong , what are all things required to enable wpa2 enterprise with AES encryption .
Is it possible to get the evalution copy of acs server with certificate ?
how to go ahead for the same .
It would be great help me to get the proper answer for configuration of wpa2 enterprise with AES ...

The below link may help you..
http://www.cisco.com/en/US/products/ps6366/products_configuration_example09186a008095382f.shtml
Regards
Surendra

WLC 2106 and iPhones

Just recently I am having issues with my WLC 2106 WiFi network and iPhones. For the past week, the iPhones have been locking up the network much like as it was described with the ARP issues with the exception that what I have been reading, this issue did not effect the 2100 series.
I've done searches but have not found anything applicable to what is happening now.
Any help will be GREATLY appreciated.

It's running on v. 4.0.217.0. Right now I'm controlling who is accessing the wifi via MAC filter to prevent anyone with an iphone to log on but that just doesn't cut it since there's a lot of visitors coming in to use the wifi.
I won't be able to go in and do more testing for a week or two to get that debug log.
But this seems to be a common issue with at least the 2106s. As soon as anyone logs in with an iphone, the controller locks up and the only thing to do is reboot. It only fairly recently started happening so maybe it's only with the newer iphones?

WLC 2106 question

Hello,
What is the recomended way to connect 5 APs 1242 to a wlc 2106?
Connect directly the 5 APs to the wlc and use one port for the management interface and connection to the switch or to connect the APs to a switch and use one connection for the wlc?
Thanks in advance.

Depends on the AP.
One FastEthernet connection to the switch doens't "really" create a bottleneck. Your AP might. If you, say, you have 1130 or older then I'd say no significant bottleneck because the APs are also FastEthernet.
If you use the newer ones, like the 1250 and newer, which has GigEthernet and/or higher throughput (if you enable 802.11n) the yes. The switch AND the WLC 2100 are both the bottleneck.

WLC 2106 Configuration steps

I have WLC 2106,And 5 LWAP, 3 Cat3560 Switches.and my 2851 CME router providing DHCP for Data VLAN 1 nad Voice VLAN 100
any one can please help me how to do the basic configuration
when i configure Managment and AP manager on WLC 2106 on untaged VLAN 0 i can able to ping but when i cahnged the VLAN to 1 im not able to communicate to WLC from switch or any port from WLC
please help me to configure the WLC
Thanks & Regards
PRajoth

The software guide states "A zero value for the VLAN identifier (on the Controller > Interfaces page) means that the interface is untagged.
The default (untagged) native VLAN on Cisco switches is VLAN 1. When controller interfaces are configured as tagged (meaning that the VLAN identifier is set to a non-zero value), the VLAN must be allowed on the 802.1Q trunk configuration on the neighbor switch and not be the native untagged VLAN.
Cisco recommends that only tagged VLANs be used on the controller. You should also allow only relevant VLANs on the neighbor switch's 802.1Q trunk connections to controller ports. All other VLANs should be disallowed or pruned in the switch port trunk configuration. This practice is extremely important for optimal performance of the controller.
Note Cisco recommends that you assign one set of VLANs for WLANs and a different set of VLANs for management interfaces to ensure that controllers properly route VLAN traffic"
Can you supply a screen shot of the interfaces page from your WLC and supply the WLC switch port configuration also? Just to sanity check what you have so far?

Upgrading WLC 4400

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

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

Microsoft Server 2003 / PEAP / WLC 2106

Has anyone ever had a certificate vanishing issue on an M$ Server 2003? For some strange reason the certificate under my IAS RAS policy keeps disappearing after an undetermined amount of time? The server is the only DC / CA root / IAS in the forest. I'm not sure why the self-signed cert. will not remain in the cert. store?
Current config.:
(2) WLC 2106 (both RADIUS clients on DC/IAS)
(5) 1141 LAPs
Authentication: PEAP/MS-CHAPv2
Encryption: TKIP/AES
Any ideas? Thanks.

In 4.1, disabling DHCP proxy did just that, it disabled the "proxy". If you ever look at your dhcp lease of a wireless client, it comes from a dhcp server of 1.1.1.1 (virtual IP of the controller). With proxy disabled, the address will no longer be masked.
In 4.2 and beyond, disabling dhcp proxy actually disables the DHCP Relay that is the process of the controller sending the dhcp requests to a specified server.
So if in 4.1, you had "dhcp proxy" disabled, in 4.2 and beyond, you are actually disabling the relay as well.
If this is indeed the case, enable dhcp proxy, or add an IP Helper adress to your router for this vlan, just like you would normally do for Wired clients.

Upgrade wlc 2106 for mesh

Similar Messages

Maybe you are looking for