1131 LWAP not join WLC 4402

Unanswered Question
Nov 17th, 2007

I am deploying WLC 4402 with LWAP 1131 but AP fail to join the WLC .The resone that I dont have DNS server.The error message in the AP is :

###########################

AP001d.451f.8582>

*Mar 1 00:00:38.005: %DHCP-6-ADDRESS_ASSIGN: Interface FastEthernet0 assigned D

HCP address 172.26.5.12, mask 255.255.255.0, hostname AP001d.451f.8582

Translating "CISCO-LWAPP-CONTROLLER"...domain server (255.255.255.255)

*Mar 1 00:00:49.371: LWAPP_CLIENT_ERROR: lwapp_name_lookup - Could Not resolve

#############################

I tried to configure the Controller address in LAP but I fail ,The error when I tried to configure AP is below:

####################

AP001d.451f.8582#lwapp ap controller ip address 172.26.5.10

ERROR!!! Command is disabled.

######################

my question is :

is it possible to make LAP join WLC with out DNS,if yes how ?

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
rob.huffman Sun, 11/18/2007 - 07:55

Hi Yhab,

There are other ways besides DNS to help in the AP and WLC Discovery process. Have a look in this good doc;

Lightweight AP (LAP) Registration to a Wireless LAN Controller (WLC)

http://www.cisco.com/en/US/tech/tk722/tk809/technologies_tech_note09186a00806c9e51.shtml#topic2

For the Static entry problem;

If this AP was ever registered you can use this command from the LAP CLI to clear the LWAPP configuration on the LAP:

clear lwapp private-config

This allows you to use the AP LWAPP static configuration commands again.

Here is an example:

Enable (enter password)

AP1240#clear lwapp private-config

AP1240#lwapp ap hostname AP1240

AP1240#lwapp ap ip address 10.77.244.199 255.255.255.224

AP1240#lwapp ap ip default-gateway 10.77.244.220

AP1240#lwapp ap controller ip address 172.16.1.50

Note: You cannot use the clear lwapp private-config command when the LAP is registered with the controller.

http://www.cisco.com/en/US/products/hw/wireless/ps430/products_tech_note09186a00808e2d27.shtml#t2

Hope this helps!

Rob

dennischolmes Sun, 11/18/2007 - 08:21

Since you are having problems with manual configuration you can try a couple of more things. Enable option 43 on your dhcp server. Option 43 is a vsa that allows you to designate the address of the controller. The other way is to attach the AP to a switch port that exists on the vlan with the controller's mgt interface. This will allow for LWAPP discovery and remember the location of the WLC. It's commonly referred to as "Priming" the AP. The exact steps fpr each of these methods are listed on the Cisco website. Just do a search for option 43 or LWAPP discovery.

Richard Atkin Wed, 11/21/2007 - 12:54

Another option is that providing you have other Access Points in the area, and the AP has been associated to a controller before, you can enable Over The Air Provisioning (OTAP) which will allow the AP to learn the WLC IP address over the air, from your other Access Points.

This is enabled from the 'Controller' tab on the WLC GUI.

Regards,

Richard

Scott Fella Wed, 11/21/2007 - 18:28

I see your AP is getting an address on the same subnet as the WLC you are trying to assign the ap to. If your ap is on the same subnet as the management and ap-manager interface, then you have a configuration issue on the WLC. Make sure you set the time on the WLC via ntp or manually. What does the rest of the log show on the AP?

yhab_dataconsult Fri, 11/23/2007 - 12:22

Hello all,

Thank for help,It was a "native vlan " issue ,I forget to add this lin when I configuerd the Trunk .

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