Problem WLAN controller 4400

There is a WLAN controller 4400 which controls the access points. There is a collapse of all access points from 00:00 to 00:12.
The link is working properly, no problems with the AC, the point is not restarted.
Logging
1. May 24 2010 00:01:08 CAPWAP 3 ECHO_ERR capwap_ac_sm.c:5116 Did not receive heartbeat reply; AP: 00:3a:98:5e:f7:80 *
2. May 24 2010 00:02:38 CAPWAP 3 ECHO_ERR capwap_ac_sm.c:5116 Did not receive heartbeat reply; AP: 00:26:ca:b7:ce:30 *
3. May 24 2010 00:02:49 DOT1X 3 ABORT_AUTH 1x_bauth_sm.c:447 Authentication aborted for client 00:15:70:f1:e4:b4 *
4. May 24 2010 00:03:07 APF 3 INVALID_RADIO_TYPE apf_api.c:27324 Invalid radio type 255 received. *
5. May 24 2010 00:06:50 APF 3 INVALID_RADIO_TYPE apf_api.c:27324 Invalid radio type 255 received. *
6. May 24 2010 00:06:50 APF 3 INVALID_RADIO_TYPE apf_api.c:27337 Invalid radio type 255 received. *
7. May 24 2010 00:06:50 APF 3 INVALID_RADIO_TYPE apf_api.c:27324 Invalid radio type 255 received. *
8. May 24 2010 00:06:50 APF 3 INVALID_RADIO_TYPE apf_api.c:27337 Invalid radio type 255 received. *
9. May 24 2010 00:07:03 APF 3 INVALID_RADIO_TYPE apf_api.c:27324 Invalid radio type 255 received. *
10. May 24 2010 00:07:03 APF 3 INVALID_RADIO_TYPE apf_api.c:27337 Invalid radio type 255 received. *
11. May 24 2010 00:07:10 APF 3 INVALID_RADIO_TYPE apf_api.c:27324 Invalid radio type 255 received. *
12. May 24 2010 00:07:10 APF 3 INVALID_RADIO_TYPE apf_api.c:27337 Invalid radio type 255 received.

If your WLC firmware is 5.X then I would like to recommend you upgrade to 6.X.

Similar Messages

Problem Wlan Controller 5508

Friends,
I have a problem authenticate with AP AIR-LAP1131AG-AK9 to Wlan Controller 5508 (software versión of the Wlan Controller6.0.202.0 ). This AP always tries to authenticate with Wlan Controller. Maybe it tries to download the ios version.
Could be a hardware problem.
I am going to attach the log file.
Thank.
Marco.

*Nov 23 20:28:50.348: %APF-3-AID_UPDATE_FAILED: apf_80211.c:5744 Error updating Association ID for REAP AP Client64:00:f1:12:b1:d0 - AID 4
*Nov 23 20:28:50.348: %LWAPP-3-MAX_AID2: spam_api.c:1045 Reached max limit on the association ID for AP (max association ID 256)
Looks like a great case for TAC.
This is an HREAP AP? It looks like it is associated fine with the WLC (no logs indicating it is trying) but instead it looks like Client Associations are breaking because it thinks it is up to 256 AIDs.....?
Maybe this is a common error, but it hasn't cross my path before...

WLAN Controller 4400 HA

I have a customer who has 1 x WLAN 4402 Controller. Everything is working perfectly until last week when we add another 4402 to act as HA.
After that, i can no longer ping the management IP of the 1st WLAN controller, nor getting into the web mgmt interface. However, everything on the 2nd new controller works perfectly.
Mgmt IP of 1st 4400: 10.120.16.2
Mgmt IP of 2nd 4400: 10.120.16.4
I have spent a lot of time on this but still couldn't figured out why.
More info on the attached files.
Cheers,
Hunt

Well, the only thing left to do is reset the wlc1 to factory default and configure wlc1 from scratch since your configuration seems okay. Don't try to do a restore, just in case the config is corrupted. I had to do this once and after a week, same thing happened. which was ap's wouldn't join the controller, but I was able to manage the device.

WLAN controller 4400 series, use service-port for initial configuration, IP address?

Hi, Everyone,
I just got a new Cisco Wlan controller 4402 from somebody else but I can't find a suitable console cable( DB-9 console on the controller) , I googled everywhere and I read I could use service port to do the initial configuration, the CISCO FAQ says initial IP for service port is 192.168.1.1, I tried use Cross-over cable to connect a PC to the service port directly and use a normal cable with a switch to connect the service port and a PC, both of the connections do not work out: from the PC, I can't ping 192.168.1.1 ( PC IP changed to 192.168.1.20) , nor can I go http://192.168.1.1 . The service port Link is solid GREEN and ACT is solid GREEN, the PC NIC says Connected with 100 Mbps , so I'm wondering the IP address of service port is not 192.168.1.1? Please help.
Any sussgestions and advices are greatly appreciated.

Hi,
plz connect service port to the switch port that should be configured as access.
connect a pc (ip address - as u mentioned) to the other port of the switch. both wlc and pc should be in same vlan (create a temperary vlan).
try https to access the wlc.
Thanks

Basic configuration for a WLAN Controller - 4400

I've been reading over the "Cisco Wireless LAN Controller Configuration Guide, Release 4.0".
So it looks like once you have the HTTPS enabled and the management IP set, the majority of the configuration is through the GUI - clicking your way through all the settings.
I've never used a wireless LAN controller -- so to make this quick and easy, is it possible to make a "quick and dirty cut and paste" CLI template to get it up and running with just minimal settings left to be done?
If so, could you post it? Thanks.

Well, first you will have to console into the wlc and go through the startup wizard. that is your minimum configuration to get it working. No way around this unless you build a script to automatically enter information on the startup wizard.

Cisco LWAP & WLAN Controller Flexconnect Across HP Switches

Hello All, I'm looking for a little guidance in making the needed routing and switching configuration changes on our Corporate Network to accomadate flex connect functionality for Cisco Lightweight Access Points (LWAPs). The LWAPs that are currently configured on our network only work when our WLAN Controller is up and running and I need for them to be disconnectable so that we can move the WLAN Controller to our virtual co-lo. It should be known that I inhereted this network from the previous admin and have been working hard to map everything out to the best of my ability. Also, the WLAN controller is already operating in our production network so it limits my ability to do much testing.
Just FYI, I'm a new Systems Admin promoted from a Desktop Support role and have my CCENT (Currently working on CCNA & MCITP Server Admin) so I have some knowledge but it is limited on the networking and switching side of things. Unfortunately, the Senior Systems Admin has even less knowledge of networking than me and I don't really have anyone to turn to which is why I'm posting here. I would have utilized GNS to help me simulate the configuration however there are HP switches in the mix and no means of emulating them.
-Relevant Device List-
(CONSA251) Sonicwall NSA 240 - 10.1.1.251
Interface Information
Interface    IP Address    Description
X0 -> LAN
10.1.1.251   LAN Interface
X1 -> WAN
*************   Time Warner WAN
X2 -> DMZ
*************   DMZ Interface
X3 -> WAN
*************   Sprint WAN
X0-V20 -> LAN
10.1.101.1   Corporate WLAN
X0-V30 -> LAN
192.168.1.1   Guest WLAN
(CORT250) Cisco 3845 - 10.1.1.250
(CO-WLAN-CTRLER) Cisco 5508 Wireless Controller - 10.1.1.2
(COSW240) HP Procurve 4108GL - 10.1.1.240
(COSW238) HP Procurve 2510B-24 - 10.1.20.238
(CORP-AP-MIS) AIR-LAP1131AG-A-K9 - 10.1.1.79
(COSW239) HP1810G-24 - No IP (Inaccesible but being replaced)
I will now go on to explain our network topology as it pertains to the WAPs and WLAN Controller and how I believe it needs to be configured in order to operate from my perspective.
Our Corporate and Guest Wireless Access is provided via the Sonicwall CONSA251 through a connection from the X0 interface to HP Switch COSW239 which is then connected to WLAN Controller CO-WLAN-CTRLER as detailed below:
Device - Interface Name/Port
CONSA251 - X0
COSW239 - 2
COSW239 - 18,19
CO-WLAN-CTRLER - 2,3
The WLAN Controller currently communicates with all the LWAPs via Layer 3 TCP\IP as I understand it and then routes all DHCP requests and traffic destine for the 10.1.101.1 (corporate WLAN) and 192.168.1.1 (Guest WLAN) to the Sonicwall and vice versa.
Now what I am trying to do is VLAN the LWAP CORP-AP-MIS across the HP Switches to the X0 interface on the Sonicwall NSA240 where it will be able to route traffic via VLAN 20 & 30. The problem lies in my inexperience with HP VLAN configurations and how the ports need to be configured on each device so it can route traffic to the Sonicwall when the WLAN Controller is shutdown.
The LWAP CORP-AP-MIS layer 2 trace to the WLAN Controller is as shown below:
Device - Interface Name/Port
CORP-AP-MIS - FA/0
COSW238     - 16
COSW238     - 25
COSW240     - B4
COSW240     - H6
CORT250     - GigabitEthernet0/0
CORT250     - Se1/0
CONSA251    - X0
Now for all intesive purposes the Corporate Router CORT250 should probably be handling the routing for our Corporate and Guest Wireless network however that was not the way it was originally setup and I have to work with what was inhereted. The Corporate Router CORT250 has a default route to the Sonicwall and the Sonicwall CONSA251 has all the routing already in place for the Corporate & Guest WLANs.
What I would like to do is VLAN off the X0-V20&V30 accross multiple switches and switchports to each LWAP in our building. I do have the LWAP I'm testing on configured with Flex Connect which I understand is required for it to be disconnectable.
Any guidance on how I would go about configuring this accross devices would be appreciated. I know there are some difference between HP and Cisco Switching terms and how tagging, untagging, and trunking works however I lack the experience to apply this in practice especially in a production environment.
I will be happy to provide any additional information or clarification that is needed. Thank you in advance for the help.

Just to add about the ISE... you can profile, but having only one ssid might or might not work in your situation. Also if you end up with remote sites or ap's in h-reap mode, currently ISE cant do any profiling. If you go with the 7500 or 5508/WiSM2, they don't really do an active-active or active backup. They are both up and you can split the load or put all ap's on one, its up to you. I usually split the load just to make sure both are working. I don't want to all of a sudden loose the primary and then find out my secondary/backup is not working.

1510 Mesh A.P with 5508 WLAN Controller

Hi everyone,
I got a situation. We had our wireless mesh network running with 4400 Controller and 1510 A.Ps. Now that we have bought new 5508 Controller (with SW: 7.2) and 3600 Indoor APs, we are unable to add legacy APs on our new controller. After a wild googling I have found that for 1510 APs i need to be on SW ver: 4.0. But that will lead into another situation i-e I wont be able to have my 3600 APs on WLAN Controller.
Any suggessions/wise words will be very very obliged....
Thanks,
Azhar...

You would have to keep those 440's up and have all the WLC in the same mobility group. That is the only way to keep those 1510's up and running. Cusco usually supports mobility between different version but only really as far back as 2 versions. Might work though.
Here is a compatibility guide that explains what devices work with what code.
http://www.cisco.com/en/US/docs/wireless/controller/5500/tech_notes/Wireless_Software_Compatibility_Matrix.html
Sent from Cisco Technical Support iPhone App

VoWLAN Roaming without WLAN Controller (WLC)

Hi,
Need some advice here. I am trying to implement VoWLAN in a company using Cisco WAP4410n Access Point. The problem is, I've downloaded all Cisco WLAN Controller (WLC) data sheets and can't find any compatible WLAN Controller for this type of Access Point.
Can I still implement VoWLAN without WLAN Controller? Is there any way to provide smooth intercell roaming without WLAN Controller?
Thanks
Regards

I have designed the cells so they have 20% cells overlap. I've also designed the channels so they won't interfere with each other (I use 2 GHz channel here)
But what could be used to replace WLC's role to manage these Access Points? maybe some kind of server?

WLAN CONTROLLER 2100

We have have three different locations on three different subnets 172.17.0.0/16, 172.20.0.0/24 and 172.21.0.0/24.
An MPLS connects all three offices together.
All three routers are doing DHCP server for their respective LAN
All internet traffic must pass through 172.17.0.0/16 where I have my sonic wall firewall.
My aim is to deploy the WLAN controller on the 172.17.0.0/16 network.
Then plug 1131LAP access points on each of the subnets.
Access points are able connect to the controller but my challenge is that when a client connects to an any of the APs, dhcp is assigned from the 172.17.0.0/16 LAN irrespective of which location the client is connecting from.
When I log in to the controller I can see that the APs are assigned ip address from the dhcp server at their location e.g AP at 172.21.0.0/24 gets an ip address of 172.21.0.42/24 from its local router but when a client connects to that same AP the client is given an ip from 172.17.0.0/16 network.

Thanks Scot. Yes I configured a guest WLAN and allowed tunnel to WLC but I had problem in dealing with access rule configuration.Here is what I did;
I created a "Guest" interface on physical port number 2,then assigned a completely different IP address of 192.168.0.2
Create a guest SSID and assigned it to the guest interface.
On the firewall device (NSA 2400) I configured a second physical interface (GUEST ZONE) 192.168.0.1 and defined a dhcp scope on this interface
Create access rule that
Denys traffic from GUEST > LAN and LAN > GUEST
Allows traffic from GUEST to WAN and WAN to GUEST
Then connect WLC port 2 to the guest interface port on NSA 2400 device.
When clients connects to the guest SSID,ip is assigned correctly from the Firewall device.
From windows connection icon I can that there is access to the Internet but it won't browse
Also a ping to the WLC interface 192.168.0.2 replies fine but
Ping to firewall 192.168.0.1 times out continuously.
Is it possible for me to define acl within the WLC that will block traffic from the guest LAN to our corporate LAN so that I can forget about the access rule within the NSA 2400 .?
Once again thank you so much your post has being very helpful
Sent from Cisco Technical Support iPad App

WLAN Controller not changing channels

We have a 2000 wireless controller with 4 1240 access points connected to it. The users would like to run their current non-cisco wireless network until all testing has been completed with the new cisco wireless installation. We have their old wireless on channel 11. It is my understanding that the WLAN Controller should see the old wireless gear and readjust itself so that there no interference. Well the problem is that the Cisco aps that can see the old wireless gear is setting itself with the same channel and not adjusting itself, it basically acts like it doesn't even care that the other wireless network is there. Is there a setting somewhere that I'm missing on the controller?? Any help would be greatly appreciated..

Is "Avoid non-802.11b noise" also checked?
On the controller if you go to management->trap logs, do you see any events that mention RF Manager changing channels? How about interference profile failed?
How about in monitor->rogue APs. Does it see the existing APs there?
In Wireless->802.11b/g radios, what channels and power levels do you see for your current ones?
Sorry for so many questions, I haven't see this as an issue before. One thing you could try is setting channel selection to manual and kicking it off. It shouldn't matter, but you never know.
-Eric

WLAN Controller Displays Interface IP in Web Authentication URL Instead of FQDN

Hi,
Can someone offer any help with the issue below please?
I have a guest wlan configured on a Cisco 2106 WLAN controller. Guest users are redirected to a Web Authenticaion page when they try to access the internet through a web browser, and can only proceed by succesfully authenticating with the controller.
The problem I have is that the guest users are presented with an SSL certficate error before they hit the web authentication page. I have installed an SSL certificate from Verisign on the controller, and have configured an FQDN for the interface that is used for the guest wlan. However, the certificate error still persists because when the user is re-redirected to the web auth page, the URL in the address bar is presented as the IP address of the interface instead of the FQDN, For example, when a user is redirected, the address bar in their web browser displays; https://1.1.1.5/ instead of https://guestwifi.domain.com/ The SSL certificate that is installed on the controller is securing the FQDN of the interface.
I'm not sure if i'm missing something here, but i'm struggling to find how to get the FQDN to display instead of the IP.
Thanks,
Paul

I'm not following what you mean when you sayd "FQDN for the interface that is used for the guest wlan"......
I assume you configured the Virtual Interface to have the dns entry as guestwifi.domain.com but clients are still being redirected to the virtual IP itself and not the dns name?
The only reason I can think of for that happening was if the WLC had not been rebooted since applying the DNS name to the Virtual Interface (it takes a reboot to modify client redirect stuff, the same goes for http vs https).
so guestwifi.domain.com should have a DNS entry resolving to 1.1.1.5, that entry should be on your virtual interface, and upon reboot you should always redirect to guestwifi.domain.com unless you manually type https://1.1.1.5 in the browser.

WLAN Controller CDP

CDP is a layer 2 protocol. Therefore, I have to assume that in a layer 3 routed architecture for a WLAN controller that the CDP information is tunneled back to the controller. What would cause the controller to NOT have accurate CDP information about all of its connected APs, assuming CDP is not globally and/or locally shut down?
Regards,
Scott

Not directly related to your problem, but a good reason to upgrade and move away from 4.2.61.0 is a nasty bug I just ran into. Local account that expire are not removed from the controller's database (so they're still in there but not visible in your management interface nor CLI). Once the database fills up to the maximum configured (512 is the default) you can no longer create local accounts.
CSCsm17944 :
WLC does not recognize the expired lifetime of guest user accounts, so
that the local user database is not cleared and can fill up with
non-active entries, preventing any other local net users from being created.
You can check the databse size and fill using the CLI command: Show database summary
Just my 2 cents.
Leo

WLAN Controller and Location appliance graceful shutdown?

Does anyone know if there is a supported graceful shutdown method/command for the
4400 series WLAN Controller and 2700 Location Appliances?
This weekend our server room will be undergoing maintenance and will experience a total power outage for a 4 hour period. It is our intent to manually bring all equipment down (hopefully in a graceful manner) and then back up once the maintenance is completed. As a result does anyone know if special precaution is needed to shutdown these 2 appliances, or can we simply bring down these devices hard which is the case with most other Cisco equipment?
Thanks in advance

Hi Mark,
Channel 1, 6, and 11 are just about as non-overlapping as 1, 7, and 13. There's an insignificant amount of overlap, so it's just as plausible of a solution, even in Europe. I honestly don't know why you wouldn't use the extra channels to eliminate the minor overlap - every bit helps.
The "channel blanket" or "virtual cell" WLAN design philosophy is rapidly spreading. Cisco maintains that it's a standards violation and I've heard no talk of them purchasing the not-to-be-named company or of them adopting the same design philosophy. I sincerely hope that they do one of the two soon, however, because it's very good design that's difficult for Cisco to compete against.

WLAN Controller on remote WAN?????

Hi Guys,
In the event of a WLAN controller, can the APs assosiate to a controller a thousand miles away?
The backup controller would be located in the DC where 100% of traffic is destined anyway so bandwidth is not of major concern.
Thanks

no problem - glad to help
if you read this:-
http://www.cisco.com/en/US/docs/wireless/controller/4.0/configuration/guide/c40hreap.html
it will give you alot of good information - but this is for WLC ver 4.0 - in 4.1/4.2 & 5.0 you get more functionality for H-REAP!

Wlan controller, can't bring up the gui, please advise

Hi,
I as configuring WLAN controller, I did following configuration but I still couldn't bring up the GUI and I wasn't able to ping WLAN controller interface ip addresses from other devices and visa versa.
Service Interface IP Address Configuration [none][DHCP]: none
Service Interface IP Address: 10.10.10.1
Service Interface Netmask: 255.255.255.0
Enable Link Aggregation (LAG) [yes][NO]: yes
Management Interface IP Address: 192.168.132.1
Management Interface Netmask: 255.255.255.0
Management Interface Default Router: 192.168.132.2
Management Interface VLAN Identifier (0 = untagged):
Management Interface DHCP Server IP Address: 192.168.132.111
AP Manager Interface IP Address: 192.168.132.4
AP-Manager is on Management subnet, using same values
AP Manager Interface DHCP Server (192.168.132.111):
Virtual Gateway IP Address: 10.42.1.230
Mobility/RF Group Name: NapNac
Network Name (SSID): test
Allow Static IP Addresses [YES][no]: yes
Configure a RADIUS Server now? [YES][no]: no
Warning! The default WLAN security policy requires a RADIUS server.
Please see documentation for more details.
Enter Country Code list (enter 'help' for a list of countries) [US]: US
Enable 802.11b Network [YES][no]: yes
Enable 802.11a Network [YES][no]: yes
Enable 802.11g Network [YES][no]: yes
Enable Auto-RF [YES][no]: yes
Configure a NTP server now? [YES][no]: yes
Enter the NTP server's IP address: 10.50.2.3
Enter a polling interval between 3600 and 604800 secs: 4000
Configuration correct? If yes, system will save it and reset. [yes][NO]: yes
>config network webmode enable
>config network secureweb enable
I did above config. but I still couldn't bring up the GUI.
Please advise how do I resolved this.
Thanks...

Hello
You can give your pc ip address 192.168.132.X and connect directly with the management interface (no lag configured)
Possible problems
->Management interface doesn't tag frames while switch does
Management Interface VLAN Identifier: xxx or put 0 and configure it as native vlan on the switch
--> LAG wrong configured on the switch --> ports down
Check if your etherchannel (LAG) on the switch is up
Still not ok
-> Default-gateway is wrong

Problem WLAN controller 4400

Similar Messages

Maybe you are looking for