WLAN Controller - reg

Unanswered Question

Hi, I have been working with WLAN controller 4402 for a while now however some strange thing happened this morning. all registered LWAP APs disappeared. upon rebooting, all of the APs came back (registered) but started disapperaring one by one after a few seconds. anyone knows whts happening?

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
dennischolmes Mon, 06/09/2008 - 06:52

Check the WLC date and time. It sounds like the certificates are out of synch. THe AP's have a certificate on them that allows for the encrypted LWAPP tunnel to be established between them and the controller. If the time on the controller is wrong then the APs will not join permanantly. The APs also will reboot several times if there has been a code update done on the WLC. This occurs as the APs look for the version of code they are running as compared to the one on the controller. If different, then the APs will download the version of code on the WLC, later version or earlier.

Hi, I checked the time on the controller and adjusted it accordingly but the same thing keeps happening. the debugs show the controller receiving LWAPP Discovery Requests and responding succefully yet nothing else happens.

below is some logs

P Disassociated. Base Radio MAC:00:1b:2a:12:71:50

2 Tue Jun 10 08:11:16 2008 AP's Interface:1(802.11a) Operation State Down: Base Radio MAC:00:1b:2a:12:71:50 Cause=Max Retrasmission

3 Tue Jun 10 08:11:16 2008 AP's Interface:0(802.11b) Operation State Down: Base Radio MAC:00:1b:2a:12:71:50 Cause=Max Retrasmission

4 Tue Jun 10 08:11:04 2008 AP with Base Radio MAC 00:1b:2a:12:71:50 (NSSF-BLKA08thfloor-AP08B) is unable to associate. The regulatory domain configured on it '-E' does not match the controller's country code: Argentina

5 Tue Jun 10 08:11:02 2008 AP Associated. Base Radio MAC: 00:1b:2a:12:71:50

6 Tue Jun 10 08:10:59 2008 AP Disassociated. Base Radio MAC:00:1b:2a:12:71:f0

7 Tue Jun 10 08:10:59 2008 AP's Interface:1(802.11a) Operation State Down: Base Radio MAC:00:1b:2a:12:71:f0 Cause=Max Retrasmission

8 Tue Jun 10 08:10:59 2008 AP's Interface:0(802.11b) Operation State Down: Base Radio MAC:00:1b:2a:12:71:f0 Cause=Max Retrasmission

9 Tue Jun 10 08:10:58 2008 AP Disassociated. Base Radio MAC:00:1b:2a:12:70:a0

10 Tue Jun 10 08:10:58 2008 AP's Interface:1(802.11a) Operation State Down: Base Radio MAC:00:1b:2a:12:70:a0 Cause=Max Retrasmission

11 Tue Jun 10 08:10:58 2008 AP's Interface:0(802.11b) Operation State Down: Base Radio MAC:00:1b:2a:12:70:a0 Cause=Max Retrasmission

12 Tue Jun 10 08:10:58 2008 AP Disassociated. Base Radio MAC:00:1e:7a:3a:a9:90

13 Tue Jun 10 08:10:58 2008 AP's Interface:1(802.11a) Operation State Down: Base Radio MAC:00:1e:7a:3a:a9:90 Cause=Max Retrasmission

14 Tue Jun 10 08:10:58 2008 AP's Interface:0(802.11b) Operation State Down: Base Radio MAC:00:1e:7a:3a:a9:90 Cause=Max Retrasmission

15 Tue Jun 10 08:10:56 2008 AP Disassociated. Base Radio MAC:00:1b:2a:12:71:20

16 Tue Jun 10 08:10:56 2008 AP's Interface:1(802.11a) Operation State Down: Base Radio MAC:00:1b:2a:12:71:20 Cause=Max Retrasmission

17 Tue Jun 10 08:10:56 2008 AP's Interface:0(802.11b) Operation State Down: Base Radio MAC:00:1b:2a:12:71:20 Cause=Max Retrasmission

18 Tue Jun 10 08:10:56 2008 AP Disassociated. Base Radio MAC:00:1b:2a:12:72:50

19 Tue Jun 10 08:10:56 2008 AP's Interface:1(802.11a) Operation State Down: Base Radio MAC:00:1b:2a:12:72:50 Cause=Max Retrasmission

20 Tue Jun 10 08:10:56 2008 AP's Interface:0(802.11b) Operation State Down: Base Radio MAC:00:1b:2a:12:72:50 Cause=Max Retrasmission

21 Tue Jun 10 08:10:53 2008 AP Disassociated. Base Radio MAC:00:1b:2a:12:70:20

22 Tue Jun 10 08:10:53 2008 AP's Interface:1(802.11a) Operation State Down: Base Radio MAC:00:1b:2a:12:70:20 Cause=Max Retrasmission

23 Tue Jun 10 08:10:53 2008 AP's Interface:0(802.11b) Operation State Down: Base Radio MAC:00:1b:2a:12:70:20 Cause=Max Retrasmission

24 Tue Jun 10 08:10:48 2008 AP with Base Radio MAC 00:1b:2a:12:71:f0 (NSSF-BLKA05thfloor-AP05B) is unable to associate. The regulatory domain configured on it '-E' does not match the controller's country code: Argentina

25 Tue Jun 10 08:10:47 2008 AP with Base Radio MAC 00:1b:2a:12:70:a0 (NSSF-BLKA06thfloor-AP06B) is unable to associate. The re

pradeepk_123 Tue, 06/10/2008 - 00:51

Hi,

Could you pl check the country codes/ regulatory domain on the controller. I think there is a mismatch between -E and -A..

dennischolmes Wed, 06/11/2008 - 04:20

As stated in my post below, you still have to have a regulatory domain issue. The AP mentioned in the log states the "E" series AP. I would check all APs and verify you have the ones for the proper regulatory domain to insure that you have local RF compliancy.

bbxie Mon, 06/09/2008 - 22:01

you can run some debug commands in WLC CLI:

debug mac addr ap-mac-address

debug lwapp events enable

it will tell you what happend for those APs.

dennischolmes Tue, 06/10/2008 - 02:37

You do have a mismatch on regulatory domains. The APs with E in them are for European (ETSI)usage. The A is for US and an N would mean they were for North America excluding the US. You have either changed your regulatory domain on the controller or received APs for the wrong regulatory domain.

Actions

This Discussion

 

 

Trending Topics: Other Wireless Mobility

client could not be authenticated
Network Analysis Module (NAM) Products
Cisco 6500 nam
reason 440 driver failure
Cisco password cracker
Cisco Wireless mode