WLC 2006 Support LAG?

Does the 2006 WLC support LAG (i.e., logically connecting its 4 100 Mb/s ethernet ports together like EtherChannel)?
Thanks

Hi Friend,
Unfortunately this feature is not available on 2006 controller.
Only 4404, 4402 supports lag.
HTH
Ankur
*Pls rate all helpfull post

Similar Messages

Wlc 2006 mac filtering

I would like to allow client to access wireless lan based on the client mac-address.
How I config it on WLC 2006 locally (not using radius server)? If yes, How mnay mac-address can be configured on the wlc2006?
Thanks.
Douglas

Hi Douglas,
Just wanted to add a note to Ankurs good info;
Maximum MAC Filter Entries
The controller database can contain up to 2048 MAC filter entries for local netusers. The default value is 512. To support up to 2048 entries, you must enter this command in the controller CLI:
config database size MAC_filter_entry
where MAC_filter_entry is a value from 512 to 2048.
From this good doc;
http://www.cisco.com/en/US/products/ps6366/prod_release_note09186a0080813b1c.html#wp42756
MAC Filtering
http://www.cisco.com/en/US/products/ps6366/products_user_guide_chapter09186a00805a6ad0.html#wp1040588
Hope this helps!
Rob

WLC 2006 LWAPP issue?

Hi, I am setting up a WLC2006 with 2 AP1010's. I cannot get the controller to see either AP. When I place the AP's on a network with a WLC 4400, they are recogized immediately by the 4400 at Layer-2 LWAPP.
Since the WLC2006 only works at Layer-3 LWAPP, do I have an AP icompatibility issue with the AP1010's(since I can only get them to work at Layer-2 LWAPP)?
Any advice is greatly appreciated.
Chris

According to Cisco doc., L2 mode is supported by WLC 44xx & 41xx and not supported by WLC 2006. And the 1010 supports L2 mode only, so the 1010 cannot works w/ 2006. You have to upgrade the AP to 1200, 1130 or 1240 or the WLC to 4xxx. And, don't know is there any future IOS / firmware can support it. Hopes this help.

Querry on Cisco WLC 2006

Hi ,
Need one help from you.Please let me know Cisco WLC 2006 ( Running version 4.2.207) will support Access Point 1242AG ?
Thanks in advance.
Thanks & Regds,
Lalit

Hi Sabastian,
Thanks for your reply.My question was I have a Wireless Lan Controller 2006 with 1030 Access Points registered to that and i wants to add AP1242AG.The Current version running on WLC 2006 is 4.2.207.I wants to add 1242AG Access Point to the 2006 WLC.Will my current WLC with current running version of image will support AP1242AG ?
Please reply.
Thanks & Regds,
Lalit

WLC 2006 EEPROM

I'm a teatcher in the Technical High-School of Geneva.
We have a project in the laboratory with a CISCO AIR-WLC2006-K9 V1. Due a bug (CISCO Field Notice: FN-62555; http://www.cisco.com/en/US/ts/fn/620/fn62555.html) Bug in CISCO IOS, the EEPROM (contain MAC address, serial Number, …) was erased and now the device can't boot.
It's a never used equipment and CISCO won't repair this (don't support this, End of Live ?)
Does someone could copy the EEPROM of its controller and send me the file ?
Many thanks in advance !

It's true, I must find an EEPROM but on the side of the Cisco product is no longer supported ! But we do not have money to buy a new WLC for Student's laboratory
Do you still have a wlc 2006 ?
if yes, would it be possible to have a copy of the contents of the EEPROM ?

Issues upgrading WLC-2006

I cannot seem to get past the "transfer download start" (CLI) or "download" (GUI) phase of the upgrade on a WLC-2006 -- from 3.2.171.5 to 4.2.209.0. The transfer consistently times out at about 76% complete and I receive an error message, either "error writing to flash" or "error writing output file" (or something similar). Any suggestions/recommendations would be greatly appreciated.

You can't upgrade from 3.X to 4.2.209 direct. You need to upgrade to 4.0.206.0 first before going anyware. It's specified in the Release Notes.
http://www.cisco.com/en/US/docs/wireless/controller/release/notes/crn422090.html#wp233853

WLC 2006 DHCP locking up

We have a WLC 2006 that is setup to distribute IPs to wireless clients using the internal DHCP server. Occasionally, wireless clients can connect to the APs (four 1131AGs) but do not get IP addresses assigned.
Rebooting the WLC temporarily fixes the problem.
software version is 4.0.155.0
anyone experiencing this or know of a solution?
thanks!

Apparently, others have observed similar DHCP behavior.
You may want to read a related thread ("Wireless Clients eventually not issued DHCP through WLC4404") in the "General" conversation section.
LINK:
http://forums.cisco.com/eforum/servlet/NetProf?page=netprof&forum=Wireless%20-%20Mobility&topic=General&CommCmd=MB%3Fcmd%3Ddisplay_location%26location%3D.1ddc63fc

High CPU on WLC 2006

I'm wondering if there are any options I can try for the following situation:
Professional sports arena has a small wireless deployment intended for use by media during games for research and submitting updates. Currently four APs on a WLC2006 (4.2.61) with a dedicated DSL connection for internet access. Only about 20-30 users typically and other than game time very stable. WLAN setup with an open SSID using web-auth to keep from needing to deal with support for encryption for visiting people. But during games with all the spectators the associations go way up due to iphones, driods, etc.. Eventually the performance starts dropping to the point where web-auth stops working. On the console (web unresponsive) I got CPU utilization staying at 80-98% and client counts of up to 180.. Too much for a 2006 I'm going to assume?
A couple options off the top of my head:
Turn on some form of encyption to reduce the number of associations, but this possibly opens up a requirement for additional support that may be needed to get non-technical users connected that need to.
More powerful controller? I haven't really been able to find anything yet on scalability expectations for the WLCs for this situation. Also don't believe there is a budget for any serious upgrade right now.
Any other thoughts or ideas anyone has that might help?

Hi David, 4.2.61 is one of the worst release to chose. In general the first release of a branch is not the best one.
4.2.209 is still the same code branch and is the most stable software out there. There has been a couple of bugs with web authentication not working under load.
Now you have another good point, that many clients on only 6 APs and a 2006 is a undersized network. 30 clients per AP is over recommendations. And the fact that some might stay in "web auth required" state means they have a special ACL applied and consume a lot of CPU on the WLC ...
The encryption is done by the AP, so WLAN encryption will not change anything to WLC CPU usage.
Regards,
Nicolas

WLC 2006 INTERNAL DHCP FOR GUESTS CLIENTS

I would like to use the internal DHCP to issue ipaddress to the guest wireless clients.
However; when i setup the wlc internal DCHP scope and try to connect to the wireless guest vlan the WLC debug DHCP reads ...forwarding to 192.168.255.2 which i have listed as the gateway to the pix
any examples on how to do this would be great.
here is what i have for the dhcp scope:
Dhcp Scope Info
Scope: Guest.Data.DHCP
Enabled.......................................... Yes
Lease Time....................................... 86400 (1 day )
Pool Start....................................... 192.168.255.17
Pool End......................................... 192.168.255.30
Network.......................................... 192.168.255.0
Netmask.......................................... 255.255.255.0
Default Routers.................................. 192.168.255.2 0.0.0.0 0.0.0.0
DNS Domain.......................................
DNS.............................................. 0.0.0.0 0.0.0.0 0.0.0.0
Netbios Name Servers............................. 0.0.0.0 0.0.0.0 0.0.0.0
Here is what i have for the wlan
WLAN Identifier.................................. 2
Network Name (SSID).............................. Guest.Data
Status........................................... Disabled
MAC Filtering.................................... Disabled
Broadcast SSID................................... Enabled
AAA Policy Override.............................. Disabled
Number of Active Clients......................... 0
Exclusionlist Timeout............................ 60 seconds
Session Timeout.................................. Infinity
Interface........................................ guest.data
WLAN ACL......................................... unconfigured
DHCP Server...................................... Default
DHCP Address Assignment Required................. Enabled
Quality of Service............................... Silver (best effort)
WMM.............................................. Disabled
CCX - AironetIe Support.......................... Enabled
CCX - Gratuitous ProbeResponse (GPR)............. Disabled
Dot11-Phone Mode (7920).......................... Disabled
Wired Protocol................................... None
IPv6 Support..................................... Disabled
--More-- or (q)uit
Radio Policy..................................... All
Security
802.11 Authentication:........................ Open System
Static WEP Keys............................... Disabled
802.1X........................................ Disabled
Wi-Fi Protected Access (WPA/WPA2)............. Disabled
CKIP ......................................... Disabled
IP Security Passthru.......................... Disabled
Web Based Authentication...................... Disabled
Web-Passthrough............................... Disabled
Auto Anchor................................... Disabled
H-REAP Local Switching........................ Disabled
Management Frame Protection................... E

when i try to assocate the dhcp scope to wireless.guest.data interface using 192.168.255.1 which is the ip of the that interface it will not let me. I would have thought since i was using the interal dhcp that the .1 address would be the dhcp scope address also. i can assign 192.168.255.0 or 192.168.255.2(gateway)if i use .0 or .2 the dhcp request (discovery) process starts and then will forward to .2 (gateway) and never assign an address. the only thing that happens is that the client wireless interface will get 255.255.255.255 for a few seconds then go away.
what i am trying to accomplish is to connect the wlc port 2 directly to a pix 506 which goes to the internet so the guest traffice is not on our vlan.
any other suggestions on guest vlans would be appricated....
Tom
Interface Name................................... wireless.guest.data
IP Address....................................... 192.168.255.1
IP Netmask....................................... 255.255.255.0
IP Gateway....................................... 192.168.255.2
VLAN............................................. 150
Quarantine-vlan.................................. no
Physical Port.................................... 2
Primary DHCP Server.............................. Unconfigured
Secondary DHCP Server............................ Unconfigured
DHCP Option 82................................... Disabled
ACL.............................................. Unconfigured
AP Manager....................................... No
Scope: wireless.guest.data.dhcp.server
Enabled.......................................... Yes
Lease Time....................................... 86400 (1 day )
Pool Start....................................... 192.168.255.17
Pool End......................................... 192.168.255.30
Network.......................................... 192.168.255.0
Netmask.......................................... 255.255.255.0
Default Routers.................................. 192.168.255.2 0.0.0.0 0.0.0.0
DNS Domain.......................................
DNS.............................................. 0.0.0.0 0.0.0.0 0.0.0.0
Netbios Name Servers............................. 0.0.0.0 0.0.0.0 0.0.0.0

WLC 5500 support for Diameter protocol?

We have been having issues with wireless user authentication (sessions start/die). Multiple authentications are sometimes needed for end users to connect. We use 802.1x to Microsoft Radius in server 2008 R2, and it's flaky. I've read up on the Diameter protocol, and it looks like it would be very good to use. However, our WLC 5508's only support the normal (and very old UDP version) of Radius.
Does Cisco plan on enhancing the software to be able to support Diameter in the future?

That is something you would need to ask your Cisco SE about. I haven't heard anything regarding future support for that, but that doesn't mean it will not happen.
Mad far as your current deployment, I have many customers who are using Microsoft IAS and NPS for radius with no issues like what you are having. It's something you need to understand why they are not connecting right away. Many times it can be how the WLAN is configured or driver related issues.
-Scott

WLC 4404 and LAG

We are trying to setup the four ports on our 4404 wireless lan controller to use LAG connected to a 3560G switch. If we connect distribution port 1 to a switch trunked port the unit works as expected. However, if we create an etherchannel containing four gigabit ports we cannot connect to the unit and all the port status LED's remain orange on the switch. They pickup the physical connection but are unable to communicate with the 4404.
We have enabled LAG on the 4404 and have rebooted several times but to no avail. We are using copper SFP's, not fibre to connect to the switch. The 4404 is on software release 5.1.151. Can anyone suggest where we are going wrong?

How do you have the trunk ports and port channel setup?
On the switch run:
show etherchannel load-balance
Make sure it is set to src-dst-ip, if not then.
port-channel load-balance src-dst-ip
You Port Channel should look like this:
interface Port-channel2
description WLC
switchport
switchport access vlan 10
switchport trunk encapsulation dot1q
switchport trunk native vlan 10
switchport trunk allowed vlan 12,10,25
switchport mode trunk
Your trunk should look like this
interface GigabitEthernet1/45
description WLC
switchport
switchport access vlan 10
switchport trunk encapsulation dot1q
switchport trunk native vlan 10
switchport trunk allowed vlan 12,10,25
switchport mode trunk
no cdp enable
channel-group 3 mode on
spanning-tree portfast

WLC 5508 support of Secure LDAP using TLS

Hi,
I have seen that the current WLC software release, 7.0.116.0, does not support secure LDAP using TLS. Are there any plans to incorporate this feature? (I've read that it was supported in previous releases to version 4.2). Is it in the roadmap of the product?
Thank you very much for your help.
Kind regards,

I too am desiring this functionality.,,

Does WLC 5508 Support LDAPS - Port 636

We have 2 5508 WLC's and @ 35 AirCap Radios.
We're running latest S/W release 8.0.110.
We presently use LDAP to authenticate to the wireless.
We would like to move to LDAPS on port 636.
Configuration Guide says you can select other port numbers for LDAP but
only port 389 is supported.
Is this true?
I read some old posts that said on releases year ago LDAPS and port 636 was supported.

Config guide says below & it is default to 389. It does not say only 389 supported.
http://www.cisco.com/c/en/us/td/docs/wireless/controller/8-0/configuration-guide/b_cg80/b_cg80_chapter_0101110.html
"If you are adding a new server, enter the LDAP server’s TCP port number in the Port Number text box. The valid range is 1 to 65535, and the default value is 389."
Anyway give it a try & see
Rasika

Prime Infrastructure 1.3 + WLC 2504 - Enable LAG?

Hi everybody,
I'm facing a little issue using Prime Infrastructure 1.3 configuration templates to manage a couple of 2504 WLCs.
I'm using a Configuration -> General template to enable LAG on a couple of controller and when I try to apply it I get the error: "LAG mode cannot be enabled for 2500 series of controllers."
Obviously I can enable LAG locally on controllers, but then each time I try to apply the configuration template from Prime Infrastructure LAG gets disabled again.
Is this a known issues? Does anybody known how it can be worked around?
Thanks,
L

There is a defect in PI 1.4 that you can't enable LAG for the 2504. It's possible that 1.3 also affected
https://tools.cisco.com/bugsearch/bug/CSCui37076
HTH,
Steve
Please remember to rate useful posts, and mark questions as answered

WLC version support on 6509 WiSM

Anyone know what WLC version is supported on a WiSM running in a 6509?
Currently we are running 4.2.61.0 and i have noticed on the Cisco website that its up to verison 6.x.x.
How can i find out what version our 6509 will support?

The WiSM is supported with a sup720 running 12.2(18)SXF2 or higher, any SXH, or any SXI version. As long as the sup720 is running any of these versions you can run any of the WiSM images posted in the software download page. Any specific interoperabiltiy issues would be listed in the release notes for the controllers.

WLC 2006 Support LAG?

Similar Messages

Maybe you are looking for