Cisco Wireless :: WLC 2100 Configured To Control Two AP
May 17, 2012
I have a fairly simple WLC 2100 configured to control two APs. We had a power outage a few days ago, and though the WLC was on a surge protector, it did not come back up properly after the outage. The STATUS light sticks at amber and I can't get any console response. At this point I'm not sure what to do except replace the WLC, though I'm loathed to do that as our budget was just cut substantially for next year and we're trying to turn nickels into pennies.
I am testing rogue on wire using 5508 WLC and , I have a dedicated AP configured as rogue detector and configured the switch port where the Rogue detector is connected as trunk. I have plugged in an autonomous AP with open authentication to the same switch so that it can act as a rogue. On the WLC, I can see that Autonomous AP as rogue on Wire. But along with that I am seeing another AP as rogue on wire, even though i have plugged in only one Autonomous AP to the switch.
I am trying to config my wireless lan controller (WLC) 2106 to discover my new 3500 access points.I followed the example Cisco configuration doc.69719.I am using a Cisco 3760 switch to interconnect the AP and WLC.I set up DHCP in the switch. [code]
Since few days the WLC 2100 series controller and 3x LAP1131AG are getting disconnected and the controller gets offline via the local ip address. At that point I have to reboot. To get anywhere and after I connect wirelessly to the AP before I know it it disconnects. It worked for 3 years straight no fuss. And now nothing. I reconfigured the WLC 10times and no diffference.
I have a cisco AIR-LAP1262N-A-K9 and AIR-LAP1142N-A-K9, and i would like to join to Cisco WLC2106 (software version 18.104.22.168)My ap 1262N have 3 antennas externals with 7dbi of ganancy,Is possible to do it?
I'd WLC 2100 series and 9 access point LAP1142N .8 LAP1142N can work fine and join a capwap controller is ok but only one LAP1142 is can not . Part of LAP is AIR-LAP1142N-A-K9
Apr 2 10:52:42.284: LWAPP_CLIENT_EVENT: spamResolveStaticGateway - gateway found *Apr 2 10:52:42.284: LWAPP_CLIENT_EVENT: spamResolveStaticGateway - gateway found *Apr 2 10:52:42.284: LWAPP_CLIENT_EVENT: Dropping discovery in LWAPP. This AP model is not supported by LWAPP WLC. *Apr 2 10:52:42.284: status of voice_diag_test from WLC is false *Apr 2 10:52:52.284: %CAPWAP-3-ERRORLOG: Go join a capwap controller
We have two 2100 WLC's that support 12 access points. One has been sitting in a box for some time, but we're at the point where we need to add additional access points that will put us in excess of the 12 limitation. What is the best way to go for installing the second WLC?
I have a problem with our WLC 2100 series (2125). Basycally internal DHCP server configured on WLC is not working. I have one AP connected to port no 7 (PoE) to bypass and eliminate problem with other equipment.
I am having trouble on setting up a WLC2100 ver 7. we need to implement a private and public network. private network authenticate to IAS - RADIUS (windows server 2003 server) while the public network is open but when a client connect to AP it will redirect to a 3rd party web athentication - HotSpot Server. the challenge is we want to broadcast a single SSID.
1. when a user/guest connect to the AP a radius server will authenticate thru IAS - Radius.
2. when a user is authenticate via radius a dhcp server will give an ip address of the private network.
3. if the user is not authenticate a dhcp server will give the public ip address and netowrk traffic must go to a different VLAN.
my question is, is it possible to broadcast a single SSID for the two network? is there a document which is related to our scenario?
The operating temperature for 2100 wireless lan controllers is up to a miximum of 40 degrees celsius according to the datasheet. We deployed some 2112 controllers all displaing a temperature above 50 degrees celsiun. This during normal operation and deployed proper enviromet (aroco ...)
One of our customers have one Cisco WLC 2100 (firmware 5.2) with 4 AP Mesh 1522, in a city deployment. In order to achieve local regulatory, has to implement bandwidth limitations per user.
I got screen captures of WLC QoS Profiles options, with Average Data Rate in Per-User Bandwidth Contracts. So my question is, do I need any other equipment to achieve per user bandwidth limitation? Can it be done with WLC QoS options?
We have a 2100 cisco Wireless LAN Controller which manages 3 APs and assign IP address to clients which connects via wifi. Currently, we are deploying dual stack IPv6 and our consultant stated that our current controller does not support IPv6.
This is rather odd statement because there is an option to enable IPv6 in the advance tab of WLAN. And sometimes clients (win7 and Mac OS X) are getting v6 addresses, able to ping v6 sites, and reach v6 sites successfully. And other times, clients do not..or getting the v6 address for 10-15minutes, then unable to ping/reach v6 sites.
Our consultant is sticking by his words saying it does not support. If this is true, then clients should not be able to get v6 at all....not sometimes and not other times; very inconsistent.
And what is ipv6 pass through? What is ipv6 bridging?
In the near future my company is looking into the option of adding a second network connection (exclusively for customers visiting our facility) to our pre existing WLAN network. We are currently using a Cisco 2100 series Wireless LAN Controller and probably 6-8 APs. Our main connection is made up of 4 T1 lines and the second connection will more than likely be a cheap DSL connection. I'm wondering if this technology supports two separate connections on one controller and APs. For example, is there a way within the controller web interface to separate what is currently our "Guest" connection from the main Internet line? I was thinking of just plugging from the DSL router directly to the controller and save the hassle of changing routing and VLANs.
We have 4 1142N LAPs that I want to divide between an internal wireless and a guest wireless network using the controller. Currently all of the APs are on an established internal network, but I want to migrate one over to a test guest network before buying more LAPs to augment the networks further. Currently the port connecting to the WCS from the 3560 switch is configured as an access port using VLAN 10. Whenever I make it a trunk port carrying VLAN 10 as well as the other ports we will be using for the guest and ap-manager networks, I lose connection with the controller. To me this implies that the port on the controller is configured as an access port as well. In the documentation I found for the controller it states that by default the ports are al configured to be trunks, but it appears as though something was changed by the previous tech. All of the APs are connected to other switches, not to the controller itself.
1) How can I get the port on the controller back to being a trunk port
2) Can I use the internal DHCP server for the guest network if the subnet is different than the management subnet, or will I have to use another external server and relay/proxy it through the controller to give guest clients IP addresses?
I have a cisco wlan controller (2100) running software 22.214.171.124. I have the internal private wlan running off of port 1 and that is working fine with an internal dhcp server.Is it possible to setup another ssid (guest) and have the interface directly linked to a static ip on the WAN and also use the built in cisco internal dhcp server?
Dell 8600 centrino intel pro wireless lan 2100 won't connect to netgear n150 wnr1000. Running 802.11b band it sees wireless network but won't connect. I have 2 other computers connected to network so it works.... I don't know if Netgear n150 is compatible with 802.11b band...
I'm trying to re-setup this EOL camera on a new router.I've been able to reset the cam to factory defaults and see it wired using dhcp. I then was able to change the address to a static address, still wired and still can see it with IE. However when I disconnect the rj-45 cable, power down and restart, I can't access the cam.
I'm new to the Cisco WLCs and recently implemented a wireless infrastructure using a WLC 2100 with 1262 LWAPs. I have two of the 1262s plugged into ports 7/8 using crossover cables. They're functioning correctly with the exception of the inability SSH and send pings to the LWAPs behind the WLC. Is there anyway to ping/shh through the WLCs to the LWAPs behind it? I use an NMS (Nagios) to monitor the status of the LWAPs and it can't monitor them if it cannot ping them. Also, is there anyway to configure the WLC to monitor the status of LWAPs?
A customer runs a 5508 WLC for quit a while. several dozens AP's are spread all over Europe an run just fine. All the AP's have a VPN based connection over an MPLS service provider, so we are using 10.x.x.x addresses only. We have upgraded to release 126.96.36.199 to support OEAP 600 and we have configured NAT in the Firewall as well a policy to support the home office AP. Everything works fine until the switch where the WLC was attached to crushed. From this moment on, all internal AP's ar no longer able to register at the WLC. A log at the console port on an AP shows that it tries to access the external (NAT) IP address. We had to remove the NAT flag to support the internal AP's.
I have a WLC 5008 running with 40 AIR-LAP1042N-E-K9 and country code BE (Belgium) configured.I also have some AIR-AP1142N-C-K9 which I converted to CAPWAP OS.Unfortunattely only 1 of the 2 radio interfaces is working because of regulatory reasons.(the AP's are -C models which stands for China - although they were bought in Belgium too).I tried to activate the country codes for BE and China, but the WLC won't accept both.Is there a way to get the 2nd radio interface working ?
I have a Killer Nic 2100 installed on an 1155 setup under Windows 8. I can upload large files to anywhere on my home network .. but when I pull large files off of my main computer with the Killer Nic in it .. the connection drops out on my main rig... no network connection of any kind on my main rig until I reboot ..
I don't have this problem with the onboard nic ..
sometimes the network will drop when the power flutters .. all the other computers I have will have internet connection .. but my rig won't ..