I have an environment of Cisco 5508 Wireless Controller and 1142N Access Points. I have a problem with the ratio of concentration of clients connecting to Access points in floors.
Recently I have been turning off 802.11a on the access points and I am seeing increase in client count in a few of acces points.What is the maximum client count supported by these access points and how do i ensure they are distributed evenly on access points?
I have an AIR-AP1242AG-E-K9 which had c1240-k9w8-mx.124-21a.JA loaded, I followed the link below and upgraded with Cisco’s upgrade tool to c1240-rcvk9w8-mx with no problems at all, after the upgrade I could then see the LWAP on the 4402 controller and had it working a treat.Now the problems begin, I brought it into the office where we have 5508 controllers, plug in the LWAP into our management switch and boot it up I get an IP assigned from the DHCP server and the AP goes into discovery mode but never finds the controller.I have logged the boot process but this does not give much away, our other 1100 series AP’s boot fine,
[URL]
Console Boot Log. Xmodem file system is available. flashfs[0]: 9 files, 3 directories flashfs[0]: 0 orphaned files, 0 orphaned directories flashfs[0]: Total bytes: 15998976
[code]....
And that is where she sits and does nothing more, I have noticed the DNS problems but the other 1100 series LWAP’s boot up after show that same issue.
I am installing a small wireless network (for the firs time). The WLAN is connected to a router/firewall and consists of a Cisco 2960-C Series 8-Port Compact Ethernet Switch, a Cisco Aironet 2500 Series Wireless LAN Controller for Lightweight Access Points and a Cisco Aironet 1140 Series g/n Lightweight Access Points (five AP if I get it to work).
My problem is that when a client connects to the access point it does not get an IP-address.
In the WLC DHCP proxy is enabled and Internal DHCP server is used.
The scope is from 192.168.104.65 - 192.168.104.99 The WLC IP is 192.168.104.60 The DHCP server is given as 192.168.104.60
When starting the system I can see the the AP have the IP 192.168.104.66 so it seems the DHCP gives out IP-addresses. I can ping the AP.
When a client connects to the APit is asked for the security key and the client can be seen in the WLC monitor section. The client never gets an IP-address; in the WLC monitor 0.0.0.0 is shown.
we are running WCS 7.0.164.3 and wonder whether is there any reporting option availabel that can give us daily report on Top 50 or Top 100 APs by client count.
I know that I can look at the client tab under WCS home page and see the top 5 APs by client count on real time.In our environment we have around 700 APs and would like to know by having this kind of report which APs are mostly hit ?
We have few sites with old 1232 ag AUTONOMOUS existing AP's , They are connected through 1 mbps link to main office .Now we are planing to upgrade with WLC 5508 and few 1140 ap . but we want to use these same 1232ag ap on some sites.So we need to upgrade it to LWAP .
1>Is it possible to upgrade this model of AP 2>Which is the ios i should download , is it avaliable in cisco site (as this ap is end of sale now ) 3>How the step to upgrade this autonomous ap
I'd like to know your experience regarding how client count affects performance.
What I have seen in a university network, with a very high client densiity, using 3500 APs, is that around 55 clients ping reply time gets over 200 ms; around 60 users there's packet loss; then, as CC increases, somewhere between 60 - 70 the service gets totally lost. Off course, this depends on bandwidth consumption per user, interference, etc.
Also, I'd like to know what we could expect from 802.11ac regarding this topic. Is there any information on tests, or some estimation already published?
*Mar 1 01:28:21.018: %CAPWAP-5-CHANGED: CAPWAP changed state to DISCOVERY *Mar 1 01:28:21.022: %LWAPP-3-CLIENTERRORLOG: bsnSetCurrentBHRate : fail to set radio control and data rate
*Mar 1 01:28:21.179: %CDP_PD-2-POWER_LOW: All radios disabled - AC_ADAPTOR (00 00.0000.0000) *Mar 1 01:28:21.984: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEth ernet0, changed state to up *Mar 1 01:28:34.341: %DHCP-6-ADDRESS_ASSIGN: Interface GigabitEthernet0 assigne d DHCP address 192.168.10.244, mask 255.255.255.0, hostname AP2c54.2d0d.c3c4
I have two number of WLC model 5508 running IOS version 7.0.98.0. And One WLC in DMZ with the same model and IOS version. AP model is 1141. The Two WLCs are integrated with ACS. I have a SSID named EMployee. The DHCP for the users are configured in a seperate DHCP server and i have mapped this DHCP server IP to the interaface Employee.And this interface is mapped to the SSID as well.. But my client is not receiving the DHCP IP. Attached are the debug logs from the client.
I am using 2 anchor controllers 5508 as DHCP server. Anchor controller A is primary and anchor controller B is secondary. From time to time, client will complain "duplicate IP address error" when they try to connect guest wireless.First question: both anchor controller should have a recorder of IP address which is assigned to each PC, right?Second question: is there any way this type of issue can be avoided?
I am having some troubles with client roaming on a 5508 controller running firmware 7.3.101.0. As soon as a client roams outside the range of an AP they lose data flow and do not seem to transition to another AP for about 1 minute.This is a small network with 6 x AIRCAP3502E-N-K9 AP's (running in H-REAP mode) on the same floor and clients are a mix of HP notebooks, Mac Books, iMacs, iPads and iPhones. There are several seperate SSID's setup and the problem occurs on all. All are WPA2/AES with either a PSK or 802.1X. Both 2.4GHz and 5GHz radios are enabled with auto power and channel selection.
I have tried changing the roaming settings from default and also playing with the AP power settings to no avail.Is this normal behaviour or is there something I can do to improve the reconnection speed?
I have one 5508 with Product version 6.0.199.4 and about 7 Cisco 1140 APs.We have a next problems. Go out of the connection on the clients PC, while physically a wireless connection to the workstations is not broken, but access to network resources is lost and restored after some time (up to about one minute).The logs on the controller at the same time see the following message.
I've just installed a standard Cisco wireless install (5508, 3502i, local and flexconnect setups) all working swimmingly.
The customer has asked for a new WLAN for a particular group of staff that will route to a different gateway than the general wireless staff.
The 5508 is connected to a older Avaya L3 switch that is the customers core swtich, but it isn't capable of PBR so it routes on desitnation only and its default route is not where I need the new WLAN traffic to route to. An ASA will be connected to the Avaya switch (which is the alternate gateway I need to get the new WLAN users to). So my question is probably routing 101, but if the ASA interface, the Avaya swtich and the WLAN interface all reside in the same VLAN, can I give the wireless clients the ASA as their gateway via DHCP and successfully get their traffic to the ASA?
Is it possible to rename the default webauthentication URL from [URL] to something like [URL]. We are running on 7.0.98.0, is it possible to do http for web authentication and https for Mgmt access if we upgrade the controller software?
We configured our guest wireless with no layer 2 authetication so users can associate with an AP and get an ip adress but they can't go anywhere unless they have a valid username and password(web authentication) - does this affect the performance of an AP since there will be many people associated with each AP, is there any setting in the WLC to de associate a client from an AP if its idle for certain time.
I have had several complaints from around the firm where by mobile devices are being bumped off the PSK secured network (All other SSID networks are operating A-OK). Both Android and iPhone devices are being affected, the device will just loop until it reconnects, sometimes up to 20 minutes of trying to establish a connection. It will eventually connect so the key is not the issue.I've attached a debug of a device which fails to connect and then shortly after is successful.
Controller 5508 v7.0.116.0 AP 3502i IOS 12.4(23c)JA2
Since two months they work full time with the new Dutch Electronic Patient Dossier.We installed 3 Cisco 5508 controllers, version 7.0.230.0 last year on a HP-switched network on a layer 2 mobility domain.Cisco 1041 AP are
The personnel works woth thin clients url... The one with the double antenna.This client has a Broadcom BCM943228HM4L 802.11 a.b.g.n (2x2) adapter.
On the client they have a connected RDP session to a server with the documents.Now they are walking from one patient to another patient. The problem they experience is a very late roaming. At the beginning of the corridor, the client will associate, but is going to roam at the end of the corridor. We installed 4 AP's on each corridor, so they signal is very well, maybe to well?
I disabled client loadbalancing and band select.The lowest data rates are also disabled. Mandatory begins at 12 Mbps. I can increase this to 18 Mbps.These clients work with PSK, with both methods (WPA-TKIP and WPA2-AES) enabled.We did this because of many old and new clients.
The customer tried to find out the problem with a smartphone, same issue. Very late roaming.I can upgrade the WLC to 7.0.240.0. The only problem I have is the WCS. When upgrading to 7.2 and higher I need to have NCS.
recently I installed WLC 5508 en the central office and installed a network mesh in a remote office; central and remote office is connected with serial link as WAN, and I have dhcp server in the remote office for give ip address to all users and devices in the remote office. Additional I have 5 LAP1552 (mesh) and 2 LAP1260 in the remote office, all clients that connect to LAP1260(this don't belong to the mesh) receive ip address from dhcp server, but neither client that try to connect to the mesh (LAP1552) receive ip address from dhcp server. I don't have if I doing some thing bad. The range IP that receive the all ap's belong to the network of devices and the range ip for the users belong to network of users.
I am having trouble with a newly configured install. Basically it seems that my centrally switched guest SSID is not functioning. As you change AP groups, which should change the interface associated with the SSID and also the dhcp client address, the client is retaining the original dhcp address from whichever AP group they first associated with.
I also have a locally switch WPA2 SSID at each location which is working fine. Clients are able to change dhcp address correctly as they move between AP groups. It just doesn't seem to be working on the guest network, which is odd because it was working earlier in the install. It has only started having issues yesterday afternoon.
The interface above is assigned to the guest SSID in one of the AP group. I assume this has something to do with it but I've been over my DHCP assignments on the core switch, local switch, controller, and dhcp server and can find no issue with the configuration..
I am not sure why as I am not using DOT1X at all. The guest is a pass-thru and the WPA2 network is just WPA + WPA2 with TKIP and AES. No DOT1X anywhere on the controller...
Background: Wireless credit card machines can't stay connected to the 5508 controller 7.0.116 / 1142 ap wireless system. MAC address of one of the wireless hosts is 00:12:0e:ec:ce:97. AP servicing them is d4:a0:2a:99:34:60. Hosts are able to connect to the network after a reboot and stay connected for random periods of time but then don't come back unless you manually reload them. I have 3 in total in the same room services by the same ap.
I have the output of debug client 00:12:0e:ec:ce:97. Output showed 802.1x 'timeoutEvt' Timer expired for station 00:12:0e:ec:ce:97 so I increased the value to 4000ms on the controller but am still having the issue.
Note that the output below is the state the client stays in after receiving the timeout (802.1x 'timeoutEvt') showing subsequent attampts. The only way to get them back on is a reload of the credit card machine.
I have been noticing in my trap logs that there are an excessive amount of Client Association/Authentication Failures. I cannot figure out why. I have a Cisco 5508 WLC with 81 AP's (1131ag, 1142abgn, 1262N) models. The wireless devices are on a Windows Domain and use 802.1x EAP authentication, authenticating the user and computer info with a RADIUS Server. I look at the logs and all it can tell me is Reason:Unspecified ReasonCode:1. I read that the Reason Code is due to "Client associated but no longer authorized" but to be honest I am not sure what that means.
Installed a new 5508 WLC last week, and finished bringing 68 new 3602i access points online in our College Dorms. We are seeing a lot of "Client De-authenticated" errors "Reason: Unspecified Reason: Code 1. Years ago I asked about error code 1. The reply from Cisco was: "The programers put the code in. It basically means we don't know what the problem is."Got a call from one of the dorms stating that students were getting knocked off the network while going to sites. If a student is wired, network is solid.Walked the dorm in question and was getting full bars of signals at all times, and was able to stream a movie from my Ultraviolet account without any break or slowdown as I moved from access point to access point. So.. my device, an iPad, was fully mobile and did not experience any disconnects.Did observe one student using a MacBook Pro. This student was constantly loosing connection to the access point. Checked the controller for the MAC of the student's computer. I did find deauthentication errors. BUT... this student's error was the computer was receiving an IP address from the DHCP that was already in use. At the computer the error message was a timeout issue.I am just learning the ropes on the 5508. Have used 3 4404s for the past six years.
User is connecting to 5508, running 7.0.116.0. Previously worked on another AP. TV (client) is set to use dhcp. As other posts have mentioned, "DHCP Addr. Assignment" checkbox is not checked for this wlan, but I also switched it to Required for this wlan but it did not make any difference. Seems to be a problem with just this client as many other clients are on this AP with no problems.
Users have to register their MAC to get on our wireless system, but there is no encyption or security enabled once the device has been registered.
I have setup the WLC to authenticate to a MS Server2008 NPS for a WPA2/AES SSID. The connection is successful, but client authentication fails for wrong EAP-type. I believe this indicates a Windows7 client issue. What is the required client setup to satisfy the MS NPS?
WLC 5508 v7.0.98 6-7 Autonomous upgraded to lightweight APs - 2 * 1231G while the rest are 1242AG 3 dynamic interfaces, 2 to Corp (diff VLANs) and 1 to Guest 4 WLANs binded to different interfaces 2 to the Corp interface Vlan X 1 to Guest 1 to Corp Vlan Y
DHCP for Corp is provided by their own Win DHCP server while controller is the DHCP server for Guest. Lease time is 1 day.
My problem now is, some clients, at random, loses their IP after being connected to the network. They get a 169.254.x.x. They connect to the Corp network OK, no browsing issues but after a while, they lose their IP address.
They can either wait for a while before getting an IP back or just simple renew their IP on their machine.
I've tried increasing the threshold values in the Local EAP to double its default values and also setting the WLAN session time out values to infinite. However, these 2 didn't work. I'm still having clients that occasionally lose their IPs at random.
I've also noted that this affects clients with WZC wireless drivers and not others e.g. Intel Proset.
I would like to be able to allow a specific client to only associate at 6mbit/s -is this possible using the wlc controller 5508? Another option would be to limit a whole w lan ssid to 6mbit/s but i can't find a way to do that either.
Other w lan ssid's on the same access points/controller need full data rates, so i guess i can't use the RF-profiling for this.
I have 2 units Cisco WLC 5508 running software version 7.0.220 with 70 over units Cisco AP 1262N and 1242AG. Some of wireless clients having problem to get the correct IP address from the DHCP server. There are 2 units of Microsoft DHCP. Both DHCP server ip have been configured on the Interface at the WLC. The core switch also being configured with ip helper. I've attached the debug output of one of the wireless client during the problem.
I have a strange issue with clients connected to a WiFi network.I have configured AP in FlexConnect mode and 2 SSID's. After a reboot of the AP the network is stable for almost 45 mins. Then each client will go UP and Down, mostly with a delay of 5 mins.
What could be the source of this. The clients are Windows CE handheld with fixed IP adres. I already configure persitent client and have play arround with APR timers as well. Thereby an Windows desktop or an iPad has less connectivity issues but even they expert pakcteloss once in severall minutes.
Session timer is turned off
The iPad for example can play music, but each 5 mins you hear a little hickup and 2 subsecond ping are loss.
I am using guest solution with two WLCs , one inside and one as anchor in DMZ.we have also NAC guest server to authenticate the guest users. inside WLC is 5508 and had been updated to latest version 7.2.103.0 last Thursday.
now we facing problem with the guest SSID , after the user authenticate, immediately disconnected and to access again he has to authenticate again and so on.
Is there any Bug with the new version because the setup was working fine before upgrading.
We're in the process of upgrading our Wireless AP's from autonomus to LWAP. We're doing the upgrades remotely (we have 100's of sites to do, and it's not possible to be there to console on to each one), using a local computer to upgrade them to LWAP's with the Cisco Upgrade Tool.Having some inconsistent bugs pop up though from time to time.The most common one is that it basically buggers up the IP address after applying the recovery firmware image. It's supposed to keep the IP it had according to the IPFile.txt (for example 172.25.25.4), but it does something very weird... it keeps the last two octets (so 25.4 from the e.g) but replaces the first two octets with a 192.168 address. So the final address in this example after the UpgradeTool has done its work, is 192.168.25.4 - which is compeltely wrong.
This causes it to be unable to talk to the WLC (obviously, with bogus IP information it will struggle), and gives us big problems in that it wont ever come up unless someone can console to the AP and fix it. We can usually resolve the issue by munging about on the switch - switching the port it's connected to between access and trunk and doing some shut/noshut cycles seems to do the trick mostly.
I have WLC 2504 with 7.2.103.0 software version , & 2 different LWAP 1262n & 1231G with "c1200-rcvk9w8-mx.124-21a.JA" Image.The 1262n is joined to the to the controller and working fine but the 1231G it can't join the controller , the controller says "Join request received from an unsupported AP" !!i will attaches the logs for this AP.
Is it possible to Change IOS of 1252 LWAP AP to Autonomous AP? I have seen some documents for changing Autonomous AP to LWAP and change back procedures.
I have a 1121 autonomous AP which I switched to the lightweight mode by copying the LWAPP ios to its flash and issuing the command boot system flash IOS_file_Name. After that I was unable to associate the AP to my wireless controller because it was continiously rebooting. Unfortunately this AP does not have a console port so I can access the debug and see what is happening. And I was not able to switch it back to the autonmous mode becaus the AP won't accept the Autonomous mode IOS anymore.
