Cisco Wireless :: Using Two 5500 WLCs With The Version 7.2.110.0 / 802.11a Isn't Working
Feb 13, 2013
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.
Is 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.
ASDM access to 5500 using Java was just a frustrating experience. If you manage only one device you may not notice the pain. But if you are managing multiple devices with some device 'forbidden' to update ASA firmware,
I spend few days looking at the issue and came to a conclusion and decided to post to guide all newer VPN admins who will go through the same pain and hopefully we can reduce some combined wasted time.
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??
My understanding is that for fully WLC 5508 integration with ISE 1.1.2, it needs Version 7.2.103.0. Question is if customer has 5508 with either 7.0.230 or 7.0.98, and ISE 1.1.2, can AAA part work? what part will not work, any potential issue if they don't upgrade 5508 to 7.2.103?
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'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.
We 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 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?
Source--- Router 1 ( ip 1.1.1.1) --ACE---router---cloud---customer---router--destination( ip 99.99.99.99). Traceroute from client to destination shows the following: traceroute 99.99.99.99 traceroute to 99.99.99.99 (99.99.99.99), 30 hops max, 40 byte packets 1 1.1.1.1 (1.1.1.1) 1.10 ms 1.78 ms 2 99.99.99.99 (99.99.99.99) 1.01 ms 1.97 ms 2.511 ms 3 99.99.99.99 (99.99.99.99) 2.01 ms * 99.99.99.99 (99.99.99.99) 2.330 ms
[code]....
So on this, the destination is 99.99.99.99.The first hop is the default gateway, which is 1.1.1.1.After that, the next step is the Cisco ACE.After that there are several hops to the destination.Looks like for some reason the Cisco ACE is not recording his ip.( For any destination traceroute result is the saame.ICMP is allowed in the access list and also ther is ICMP inspect in my config. access-list ICMP line 10 extended permit icmp any
class-map type management match-any abc 201 match protocol ssh source-address X.X.0.0 x.x.0.0 class-map match-all ICMP_allow 2 match access-list ICMP
I have installed the new version of DCNM Prime (Version: 6.2(1) and all installation process went well without any error or warning, DCNM SAN client works well I can loggin and manage my MDS and UCS, but I have big issue to run DCNM LAN client after successful logging I have window that freezing and nothing is displayed (see printscreen attachment) I reinstalled several time Java, installed four version different of Java, tried this client from three different PC and still have the same issue.
McAffee scan of acs 1113 appliance running the 4.2 build 124 patch 12 version reports that a medium vulnerability exists because the system has SSH version 1. Any way to specify only version 2 or turn off SSH?
We have an issue with View db (Monitoring & Reports) backup on ACS, version 5.2.0.26. We have scheduled incremental backup daily and full backup monthly. Everything has been working well, but since yesterday following errors have appeared, and full and incremental backup stopped working:
Alarm Name System Alarm [Incremental Backup] Cause/Trigger On-demand Full Backup failed Alarm Details CARS_BR_BACKUP_CREATE : -405 : Internal error: couldn't create backup file Alarm Name
[code]....
We use same repository as always. Backup to the same repository works from CLI.
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.
I 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.
We 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 .
We 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?
We are looking to upgrade our WiSMs to version 7.0.230.0, but the Cisco compatibility matrix suggests we need to upgrade WCS to the same version (it is currently on 7.0.172.0). My question is can we upgrade the WiSMs and do the WCS at a later date with no issues or do we need to do them at the same time to keep visibility of everything?
The reason I ask is that some of my clients use lobby ambassador for some of their users and they will need wireless access on the day we are due to upgrade WCS (the WiSMs are due to be upgraded and rebooted earlier that morning.
I have a Cisco 5500 Software Version 6.0.199.4. Today I've been able to succesfully add a few newly purchased 1242G APs to my WC so I know everything is setup properly. They got the proper DHCP info and I was up and running in a few minutes.
I'm now trying the same thing with a newly purchased Air-Lap1262N-a-KP
I can read the bootup because I'm attached to it on the console.I see that it gets the proper IP#
But then I keep getting a "failed to decode the discovery response" error.
We have a WLC 5500 connected to a 2960 acting as core switch. there is a server attached to the switch , bearing all dhcp pools for lan and wireless users. Can the wlc or the switch be configured in such a way that the wireless users associating to the wlc get their ip addresses from the dhcp pool configured on the server. Can the configuration can be shared for such a setup.
i have a existing wireless network setup in my office existing wlc in 4402 and LAPs are 1130 & 1242 all are working fine but we are now planning to use new 5500 series controllers for the same access points,i want to ask that how i can done this job with very minore downtime and users disconnectivity + zero error results??
Our client have cisco 5500 Wireless lan controllers. They connect to core switch and other ports conenct to various switches on each floor. Then we have cisco AP 1300 series mounted on celing. I was reading that lightweight AP gets config from WLC as soon as they plug in. Need to know how the AP gets config from WLC switches?
I have a Cisco aironet 3502i access point which I am using with a 5500 Wireless Controller. I was configuring the AP for flexconnect and accidentally enabled PPPoE authentication - but never set configured login details for PPPoE. Now when the AP boots up it tries to use PPPoE but fails - it never even looks for an IP address. I have no way to get the AP connected to the controller again.I tried logging into the AP via console, the AP gives me output but I never get a login, even when I hold down the Mode button during startup.I also tried holding the Mode button and waiting for the AP to boot with its default IP (10.0.0.1) and connecting to the AP via telnet, but I was unable to connect or even ping with my PC on the same network configured as 10.0.0.2.What can I do to set this AP back to defaults, to become a normal DHCP client, and reconnect to the wireless controller where I can reconfigure it?
I've recently installed ssl certificates for our web auth guest interface on our WLC's. I discoverd the they required a Level 2 certificae to work properly. We are getting an untrusted certicate on our 802.1x ssids that authenicate against a 5500 ASA..A certificate was insatlled and has an error, show the certificate as untrusted, my questionis, does the 5500 ASA require a level 2 certifate as well?
The 5500 WLC would be the primary and 2500 WLC would be the secondary. The only need for the secondary would be in the event of failure of the primary, and support needs when doing maintenance such as code upgrades.
We would use the same version of code on each controller and apply the necessary amount of AP licenses on each. The controllers would have identical configurations and host multiple SSID's, including offering guest services. Does the 2500 support guest network services?
We have recently been given this unusual task. The setup is a series of CAP3502P access points, and a wireless controller (either 2500 Series or 5500 Series), as well as other standard network infrastructure.
In this network, the client (mobile/wireless) devices must be able to detect when they change what access point they are communicating through, while also requiring a seamless transition. Ie, if the client device is communicating via access point A, and displaying the application menus for A, when the user walks to the area services by access point B, it must detect that sot he application can display menus for B, without the user having to select "B".
Is there a way for the client device to detect which access point it is using and provide that to an application? Or alternatively a way for a host service residing on a server to get that information from the wireless controller?
