Controller, 1522 and no IP connectivity

Answered Question
May 8th, 2008

Weirdest thing:


We are trying to register one 1522 Mesh AP (the one with a Cable Modem inside) to a controller using the lastest mesh image. Here is the thing:


For some reasong, the AP was previously associated to a different Controller, (lwapp commands disabled), despite being brand new and just got out of the box. So we are using some simple scenario where the AP is directly connected to a switch and the controller.


The controller is configured also as a DHCP server, and the AP does gets an IP.. BUT, it cannt ping neither the gateway (the switch) or the Controller. If it gets the DHCP info I guess there is connectivity between AP and WLC, but how come after gettint an IP address it cant ping and obivously it cant join the WLC.


Anyone with a tip or some orientation?


thanks in advance!

Correct Answer by dennischolmes about 8 years 9 months ago

Youre quite welcome. Make sure to close this post as "problem solved".

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (2 ratings)
Loading.
omarmontes Thu, 05/08/2008 - 18:02

I forgot, heres some more info:


We are using the Cable Modem just to energize the AP, the data conection is provided by an Ethernet cable (we just discconected the ethernet from the cable modem).


thanks

dennischolmes Fri, 05/09/2008 - 04:46

Have you entered the mac address of the AP to the controller? It is required to be added to the controller for the AP to fully register with the controller.

omarmontes Fri, 05/09/2008 - 05:30

Thanks, wea re gonna try that today.. but, i guess it should be able to ping the gateway no matter if its registered or not.. right?

dennischolmes Fri, 05/09/2008 - 09:26

Nope. All traffic is terminated at the cotroller until the unit is registered with the controller.

omarmontes Fri, 05/09/2008 - 09:34

But then what happens when the AP and the controller are in a different subnet? it should be able to reach the gateway so it can register with the controller, right?

dennischolmes Fri, 05/09/2008 - 09:42

In the LWAPP discovery process the machine state is as follows.

1. Get IP Address from DHCP scope (option 43 gives the location of controller if controller is on different subnet. DNS will work as well)

2. Register to controller. (In case of MESH APs, the AP mac address must be in the mac filter, if not, it will not join the controller)

3. Once registered, an LWAPP tunnel is opened that passes LWAPP control packets to the AP.

4. Once the LWAPP discovery process ends then clients can use the AP for network service.

5. Clients dhcp and authentication requests are passed by proxy to the dhcp scope and RADIUS servers defined in the interface servicing the SSID.

6. Clients allowed on network.


This is kind of a generalization but a decent overview of the process.

omarmontes Fri, 05/09/2008 - 16:34

you rock!



Adding the mac address did the trick. Thanks for the help!


Correct Answer
dennischolmes Fri, 05/09/2008 - 17:48

Youre quite welcome. Make sure to close this post as "problem solved".

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