1522 not registering to the controller

Unanswered Question
Dec 14th, 2009

Some of the 1522 AP's are not joining to the controller. I have 2 WiSM's. that means 4 controllers. i added all the four controllers in a single mobility group. all the 1522 ap's are in a single vlan, some of them are gegustered in the controller and others are not registering. I added the mac address of the access points in all the four controllers. But its not regietring to the controller.

Other issue is that from the managemnt vlan i can access all the four controllers. But from any other vlan i can access only one controller, the second controller in the first wism. other controllers are not accessible from the other vlans.

i console to the 1522 AP and i tried to put the controller ip. but its showing that command disable. I am attaching the logs for your refrence.

*Dec 14 17:40:38.829: No entry exists for AP (10:175:168:141/43617)
*Dec 14 17:40:38.829: No entry exists in database

*Dec 14 17:42:13.447: 00:26:0a:38:db:00 Successful transmission of LWAPP Discovery Response to AP 00:26:0a:38:db:00 on port 29
*Dec 14 17:42:14.606: Discarding non-ClientHello Handshake OR DTLS encrypted packet from  10.175.168.141:43617)since DTLS session is not established

*Dec 14 17:42:14.667: 00:26:0a:38:a6:00 Discovery Request from 10.175.168.141:43616

*Dec 14 17:42:14.667: 00:26:0a:38:a6:00 Join Priority Processing status = 0, Incoming Ap's Priority 4, MaxLrads = 150, joined Aps =0
*Dec 14 17:42:14.667: 00:26:0a:38:a6:00 Discovery Response sent to 10.175.168.141:43616

*Dec 14 17:42:14.667: 00:26:0a:38:a6:00 Received LWAPP DISCOVERY REQUEST to 00:1e:4a:fa:8e:6b on port '29'
*Dec 14 17:42:14.667: Join Priority Processing status = 0, Incoming Ap's Priority 5, MaxLrads = 150,joined Aps =0
*Dec 14 17:42:14.668: 00:26:0a:38:a6:00 Successful transmission of LWAPP Discovery Response to AP 00:26:0a:38:a6:00 on port 29

Please advice

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.

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