I've just been tasked with setting up 19 AIR-CT2504 WLCs with AIR-CAP3502E APs. The primary objective is to maximize throughput from clients uploading LARGE files over the air.
I need to make sure I config HT 802.11n properly with no support for legacy clients in the 5Ghz band.
I have the below BoQ implemented
AIR-CAP3502E-N-K9
I am trying to deploy several AIR-CAP3502E-E-K9 access points from a cisco 5508 wire lan contoller running ver 7 code. However iam having difficulty registering the access points with the WLC. The wlc is connect to a 3650 switch, and each access point is connected to a 2960 switch. A bad update was not allowing the access points to get their correct firmware.
View 7 Replies View Relatedhave concern regarding the faiolver of 2 WLCs.
1. One Active_WLC(2504) have a full licence of 15 Access points.
2. 2nd Seconday_WLCs(2504) have a normal licenece (Without any AP licenece-Zero AP Count License).
Now my questions are:
1. If first WLCs goes down due to any kind of problem then can secondary WLCs comes up and takover of all APs.
2. if Yes, then How may days or hours...These APs will connect to the WLC.
3.If first WLCs comes up after some days, then can this WLC automaticall tak over the situation??
I'm using two 5500 WLCs with the version 7.2.110.0 When some AP with the part number AIR-CAP1552E-N-K9 associate with them, the 802.11g stays up and the 802.11a stays down.I saw the AP interfaces in Wireless --> All APs and the 802.11a is down and the regulatory domain show me not supported but the 802.11g is working normally.I follow this document from Cisco [URL] and i just have BR - Brazil to support this part number.
View 5 Replies View RelatedPossible to assign reslient WLCs to an OEAP 600?
The web GUI of the OEAP itself only has a single field to enter the address of a single controller.
But, I wonder if once the OEAP is talking to your WLC across the Internet, you can allocate HA settings to the OEAP so that it can fall back to a secondary WLC if your main WLC fails.
This is sort of hinted at in the docs I have read, but I have not been able to find it explicitly stated anywhere.
It would be nice to have 2 DMZ-based WLCs at two different data centres to allow remote users to have a fail-over solution, but I need to be sure that this is supported before implementing.
I have been installing Light Weight AP's and these make LMS device discovery take much longer because they are found via CDP but do not run SNMP. So you suffer the SNMP retry and wait time for each one which adds up with several hundred AP's. I added the CDP platform description they announce via CDP to system-config.xml but this didn't do the trick. I have updated system-config.xml successfully in the past to add ATA's and 7936 conference phones and this stopped discovery from processing these devices. So I was surprised when this didn't work for LW AP's. The CDP platform of the AP's looks like this (from show cdp n):
Platform: cisco AIR-CAP3502E-A-K9 , Capabilities: Trans-Bridge
So you can see cisco is all lower case and there appears to be spaces at the end before the comma. I thought the spaces might be the problem so I added them in system-config.xml but this didn't work. When I display system-config.xml with the XML editor in IE it does not show spaces at the end even though they are their when I look at the file with notepad. When I enable debug for discovery it shows these being added to the bypass table for CDP discovery but it still tries to process them. This is LMS 3.2 on Windows Server 2003. I use the CDP module for discovery.
Does the AP is able to configure 2 public ip address of the DMZ-WLCs?
like ip 1.1.1.1 in my US data center, whereas a second ip 2.2.2.2 in my EU data center?
I have wlc AIR-CT2504-K9. After save config and power down, wlc cannot start. In console I see:
WLCNG Boot Loader Version 1.0.16 (Built on Feb 28 2011 at 13:14:54 by cisco)
Board Revision 0.0 (SN: PSZ163201YR, Type: AIR-CT2504-K9) (P)
Verifying boot loader integrity... OK.
OCTEON CN5230C-SCP pass 2.0, Core clock: 750 MHz, DDR clock: 330 MHz (660 Mhz da ta rate)
CPU Cores: 4
[Code].....
I have 8 2504 controllers and each needs to have a minimum of 20 MAC addresses added. I would rather not add them one at a time but I don't see any features that allow for an import. Any way to do the import?
View 2 Replies View RelatedWe have 1 WLC + 17 AP's on our main site and thats working fine... we just buyed a new AP for a new site of us. Its the same domain, same ip range nothing special at all... Somehow the AP on the site keeps rebooting and the users getting nervous of it there
Specs:
WLC: AIR-CT2504-K9
Software Version: 7.2.110.0
AP:AIR-LAP1042N-E-K9
Software version: 7.2.110.0
[code]....
AIR-CT2504-25-K9 will support AIR LAP1142N-E-K9
View 3 Replies View RelatedWe have existing AP 1132 with WLC 4404 controller implemented in a site. We started add on new AP 3502 with WLC 5508.Our customer has existing 10 of 4404 controllers and configured in the same mobility group, and the roaming is working fine(ap are 1131).
Curently we deployed 2 new 5508 controllers and replaced some 1131 AP to 3500 AP. And the controller created new IP scheme for the wireless client. But after migrate 2 APs, we found that the roaming is not working when the wireless client move from new AP to old AP.
When moving from new AP to old AP, the ip address for the client is unchange, but the ping will be droped, and will never come back. Until we do a ipconfig flush, and reconnect, the connection can back to normal, but the ip address als changed to the old IP scheme.
I configured a 2504 controller with two LWAPP Access Points, and I'm using two SSID's on the same controller, the problem is when the user tries to switch between SSID's he gets an error message saying that the other network is unavailable but if he disconnects from the first network and then connects to the other it works fine !.
View 5 Replies View Relatedsome computers is connecting to AP that is farthest, But there are two APS closer and the signal gets too low, the computer only connects to the closest AP if I disconnect and reconnect.I have 2 controllers series 2500 model AIR-CT2504-K9.
View 5 Replies View RelatedOn the WLC I've set DHCP address pool, everything seems fine after ap download image -> reboot -> hit "Enter" to start blar blar blar... however, after a few second the WLC will initial upgrade image again and again. it's like a non-stop process.
Attached is the start up message, as you can see, i captured it after the ap successfully boot up, and WLC initial another cycle of image upgrade.
btw, my network is flat, WLC & AP all in the same network.
*Nov 3 06:28:30.788: %CAPWAP-5-CHANGED: CAPWAP changed state to JOIN
examining image...!
extracting info (292 bytes)
[Code].....
I have bought 2504 LAN Controller and my old 1142 wants to configure to accept that Controller instead of old controller. These APs and controllers in far away site and before I go there I want to figure out how can I do following.
1. How can I configure old 1142(Previously connected with another LAN Controller) to accept New 2504 Controller instead of old controller ?
2. What are the concerns do I need to consider?
City A is the data center with 2 WLC (CT2504-K9) and a number of AP. City B is a branch with MPLS between A and B. Right now the APs at City B has joined the controller. Users at B is getting ip's assigned from DHCP at City A. How do I configure the WLC so users can get ip's assigned from DHCP server present at B. Option 43 is enabled.
View 2 Replies View Relatedtell me when is available for order the High Availability for AIR-CT2504, like:
AIR-CT7510-HA-K9 Cisco 7500 Series High Availability Wireless Controller
AIR-CT5508-HA-K9 Cisco 5508 Series Wireless Controller for High Availability
I have three 5508 WLCs, running code 7.0.98.0 supporting 100+ LWAPs in H-REAP mode. The LWAPs are servicing 2-3 WLANs each. Some are using central authentication and local switching, some are configured for central authentication and central switching. When the LWAPs fail from one WLC to another WLC, the LWAP's lose all of their VLAN mappings and pick up the VLAN of the management interface on the new WLC.
All WLANs are configured to use the management interface on the WLC and the VLAN mappings are configured per LWAP on the H-REAP properties tab. The WLAN ID numbers and all the WLAN settings are the same across all 3 WLC's. I have created AP groups on all 3 WLC's and the AP group config matches across the 3 WLCs.
I can get the LWAPs to keep their VLAN mapping by creating an interface on the WLC with the VLAN ID of the locally switched/remote site VLAN and then setting the interface for the WLAN to the new interface. However, then the WLAN doesn't work, because the centrally located WLC doesn't have the remote site VLAN. It also seems to keep the VLAN mapping if I create the locally switched/remote site VLAN interface on the WLC , and point the WLAN to the management interface. This shouldn't be a necessary step though... In H-REAP with local switching, the LWAPs aren't using the interface on the WLC.
I found a note in the 7.0 WLC config guide that explains why the VLANs are picking up the management interface VLAN, but that same note says the VLAN mappings can be changed per LWAP/WLAN!
From config guide: For hybrid-REAP access points, the interface mapping at the controller for WLANs that is configured for H-REAP Local Switching is inherited at the access point as the default VLAN tagging. This mapping can be easily changed per SSID, per hybrid-REAP access point
Using H-REAP and been able to get the LWAPs to keep the VLAN mapping when failing from one WLC to another?
I have inherited a site where the builders have installed a 2504 controller with 8 access points. Unfortunately they have not created an ap-manager interface when they did the set up. Is there any way I can do this via GUI or command line without going back to defaults?
View 7 Replies View RelatedI have AIR-CT2504-5-K9, with 5 access point license support. I buy capacity adder license LIC-CT2504-5A for add 5 access points more. When i try download licence file from tftp server on WLC system i see message "License 1 Failed 1" on WLC. TFTP server message downloading OK.
View 4 Replies View Relatedi have AIR-CT2504-5-K9, with 5 access point license support. I buy capacity adder license LIC-CT2504-5A for add 5 access points more. When i try download licence file from tftp server on WLC system i see message "License 1 Failed 1" on WLC. TFTP server message downloading OK.
View 7 Replies View RelatedI am using two AIR-CT2504-K9 controllers
Product Version.................................. 7.4.100.0
Bootloader Version............................... 1.0.16
Field Recovery Image Version..................... 1.0.0
Firmware Version................................. PIC 16.0
and 20 access points AIR-CAP2602I-E-K9 Cisco IOS Software, C2600 Software Version 15.2(2)JA, RELEASE SOFTWARE (fc1) LWAPP image version 7.4.100.0
I created 3 SSID:
1. [WPA2][Auth(PSK)]
2. Web-Passthrough
3. [WPA2][Auth(PSK)]
Configuration on controllers is identical. High Availability is configured on all APs. First controller controls only those APs witch have SSIDs with [WPA2][Auth(PSK)], second controller is basically for APs with Web-Passthrough SSID. From the start I have problem, some clients who try to connect to SSID with PSK are dropped or can’t connect entirely, but when they go to the next AP they connect successfully. For example I have Android smartphone and Lenovo laptop, smartphone connects successfully but laptop fails connection to the same AP, but when I take it to other AP it connects successfully. Sometimes smartphones can’t connect too. When devise can’t connect to one SSID it can’t connect to other SSID either. Sometimes there are up to 20 clients tying to connect to the same AP.
When I look into logs, I get these two messages:
Jun 3 08:58:58 192.168.224.1 WLC1: *dot1xMsgTask: Jun 03 08:58:51.176: #DOT1X-4-MAX_EAPOL_KEY_RETRANS: 1x_ptsm.c:456 Max EAPOL-key M1 retransmissions exceeded for client 7c:e9:d3:f4:74:4d
[Code].....
I've got a new CT2504 controller with software version 7.0.220.0 Regarding to [URL]I've tried to configure the internal DHCP on a dynamic-interface, but this is not possible:(Cisco Controller) >config interface dhcp dynamic-interface vlan401 primary 172.16.x.3 vlan401 Interface IP can not be used as internal DHCP server IP It works, if I use another IP (aka DHCP server) in the same subnet or in another subnet. It works also for the management interface.
(Cisco Controller) >show interface detailed management
Interface Name................................... management
MAC Address...................................... d0:c2:82:xx:xx:xx
IP Address....................................... 10.2.x.135
IP Netmask....................................... 255.255.255.240
IP Gateway....................................... 10.2.x.129
[code].....
We have just installed our first CT2504.After install I have found a dramatic drop in signal strength compared to the wireless survey result obtained.All of our site surveys include real world testing using an AP, in this case a AP1041N.In doubt I retested a section using an AP1041N in the same location as one of the recently deployed LAP1041N.
In the same location a LAP1041N has between -10 and -20dbi difference in SNR compared to the test AP1041N.For example locations that tested with -60dbi using an AP1041N have little to no coverage using the LAP1041N installed.This applies irrespective of the WLC automatic control over Tx power or manually setting the LAP TX to the highest level.
I have a CT2504 at a customer site which does not load the captive portal page correctly nor will it load via HTTP as opposed to HTTPS.So for starters I did what I do with all my CT2504's (which work fine), I configured my Guest network to authenticate via the default captive portal. I then disabled HTTPS and SSH and enabled HTTP managment followed by rebooting the controller. On boot, logging into the WLC management GUI is automatically presented via HTTP as expected.However when clients access the Guest network they are redirected to the Web Authorisation via HTTPS instead of HTTP?In addtion to the above the captive portal page does not display correctly.The preview via the controller works fine, but the client is presented with a page with broken links to the images i.e. the blue strip at the top and the Cisco logo on the right.
View 3 Replies View RelatedI´m trying to connect them to my WLAN, for throubleshoot I create a new WLAN with WPA2-TKIP and a PSK, the devices didin´t connect to the WLAN.I also change the security to WPA2-AES with TKIP, it didn´t work too.
My best choice was to disable every security configuration in order to began the throubleshooting from zero, but even with no Layer 2 and 3 security, the devices didn´t connect to my Test WLAN.
I´m using a AIR-CT2504-K9 WLC with two AIR-CAP3502I-A-K9 AP, all the PCs and other brand cellphones and tablets work well.
Also I have a SOHO router on the office, and the IPad connect without a problem with that WLAN, but I need them to connect to my Cisco AP.
We've been upgrading our WLCs to 7.0.230.0 but I've notifced after they have been upgraded they no longer appear in the controller section in License Center on the WCS. They still exist in the WCS and the audit the configuration jobs are working. I've also tried manually triggering the Controller License Status background tasks and this runs without reporting any errors.I thought it may be because the WCS was at a lower version but I've now upgraded this to 7.0.230.0 also but the WLCs are still missing.
View 1 Replies View RelatedI would like to discuss another method of a bulk controller upgrade and see what other engineers take on this upgrade path would be.Say I have an instance of 84404s with 50 APs each, In this case I have N+1 redundancy where I can follow the normal procedure.Normal Procedure.Move all APs to controllers 1-4Preload all APs with the new code versionUpgrade and reboot empty controllers 5-8 to new code versionMove all APs to 5-8 with new code versoinUpgrade empty 1-4Move all APs back home.Now take the same scenario only chage it to 80 APs per controller. I've now lost my N+1 and cannot do it quite as smoothly. As opposed to trying to follow the normal proceedure and have an extended window of "brown outs" How about doing it all at once.Black-out accelerated proceedure:Preload new code on all controllersPreload new image on all APs on all controllersReboot all 8 controllers at the same time.Allow time for APs to connect back and load the new image.I assume with this proceedure that I might see around 15-30 minutes of actual downtime to the site but it seems like that could be preferable to two-three hours of brown outs.
View 6 Replies View RelatedWe are currently running WCS but have built a new Prime Infrastructure 1.3 system from scratch on a brand new server, we have sucessfully migrated the old WCS database on to the new Prime server and as a test I have pointed 1 anchor controller to it. Possible to point the WLC's to both WCS and Prime Infrastructure concurrently - I was thinking that it would be a quick fallback if we has any problems with Prime (I know there have been some!) We are not running MSE but we do have mobility groups, the WLC's are 5508 running 7.0.235.3 .
View 0 Replies View RelatedIs it possible for the wlc (5500) block wireless users attempting to login to the network more than 3 times?I have several devices trying to connect to the network automatically using rhe old password, after 3 attempts the account will lock out! Im running peap mschapv2 with radius and active directory.
View 1 Replies View RelatedWe are in a warehouse type setting and have data centers on each side of warehouse with 5508 WLC's in each data center. Each side is on its own subnet with routing in between and a different set of SSID's for each set of WLC’s. Are goal is to have the ability to failover in the event that if one data center goes down AP’s will move to the controllers in the other DC and the clients will still be able to operate.
Our thought was to implement mobility groups between the controllers. While I saw documentation on setting this up when the controllers are on the same vlan, I didnt see any setup config when controllers are in different vlans. So I am wondering if mobility groups are even an option for what we want to accomplish. For the most part clients stay on their respected sides of the warehouse and so we are not necessarily needing roaming for clients between controllers in DC1 and DC2. But that does raise another question in that we do have a planned voice wlan that we would like to have the ability to roam between each side of the warehouse. But we have seen ip issues with this. In the past we have had both SSID's setup on each side and ran to issues with clients not renewing their IP address when moving to the controllers on the different subnets.
Can we setup mobility groups between controllers on different vlans/subnets? For failover purposes will mobility groups assist in our setup with 2 DC’s and different subnets/vlans? If the answer is yes we can setup mobility groups between different subnets, is there a way to setup the SSID's on all controllers and have the ability for clients to roam and renew their IP’s when moving to a different controller on a different subnet?