Problem with the AP[AIR-CAP3502I-C-K9] or WLC

[vidiya]

Hi Team ,

We have installed Ap's accross the region and have associated them with WLC but wen the Ap gets rebooted , it is getting Ip from DHCP instead of Static IP[DHCP is not enabled]. we need to manually assign the proper IP.

could you please tell me on how to avoid this problem.

regards,
Vidiya.

 

[RadiclDreamer]

Is your dhcp server handing out these IP addresses? If so can you use a reservation?

 

[vidiya]

Hi Radicl,

Ip addresses are assigined statically and DHCP option is not enbaled in the Ap's.

These AP's are connected to the switches and DHCP is enabled for LAN users and wifi users on Core switch.

After AP gets rebooted i dont understand why is taking IP from DHCP instead of its own Ip address.

Note the Ip address which are given to AP are also excluded from DHCP range.

Regards,
vidiya.

 

[RadiclDreamer]

Im guessing these are lightweight versions? What code are you running on your controller?

 

[imagoon]

All of ours are statically assigned with DHCP disabled. However when communications fails they will fall back to DHCP and pop up as an AP with problems. They do that by design. If you are assigning statics, it likely means there is a communications issue causing them to fall back to DHCP to reach the controller to send the alarm.

 

[vidiya]

AIR-CT5508-K9 is controller version

 

[vidiya]

Hi imagoon ,

Do you mean that this is default behaviour of LWAPP AP's or WLC's?

 

[RadiclDreamer]

How are you adding them to the controller? DNS entry or dhcp option?

 

[imagoon]

Hi imagoon ,

Do you mean that this is default behaviour of LWAPP AP's or WLC's?

I believe the default is DHCP -> DNS name. We switch the LWWAP to static and if they can't connect as a static address, it reverts to DHCP.

 

[vidiya]

Hi Radicl ,

We will configure the static Ip , default gateway and controller Ip manually in all AP's in order to associate with the WLC.

Regards,
Vidiya.