Deploying 1131s and 3502s - Pre-configured APs

[TERRY HAHN]

We pre-configure our APs with IP address, subnet mask, default gateway and controller IP address.  Our APs are on separate subnets by themselves.  All of the 1131's found the controller and came up.  None of the 3502s found the controller.  We then had to use the ip helper-address command and the ip forward-protocol command on the router for the 3502s - that worked.  Why don't the 3502s come up like the 1131s without the router commands?

[Surendra BG]

Hi,

3502 AP needs 7.0 WLC code.. please make sure the WLC code is anything above 7.0 , lemme know if we are running 7.0

Please dont forget to rate the usefull posts!!

Regards

Surendra

[TERRY HAHN]

We are running WLC verson 7.0.98.

[Nicholas Darrow]

When you configured the controller ip address on the ap, did you also included the controller name? I usually configure the ip address of the controllers in the dhcp option 43 or as a dns name so lost aps will come up. When statically assigning an ap, you should set the ip address AND the controller name under capwap not lwap.

Sent from Cisco Technical Support iPad App

[TERRY HAHN]

We statically configure the APs with the controller IP address.  I guess I don't see the added advantage of adding the controller name - how will that help if the AP already has the controller IP address?

[Nicholas Darrow · Accepted solution]

Try it. Just the ip address the wap won't join.

Sent from Cisco Technical Support iPad App

[TERRY HAHN]

Well, it's been a long time but I finally checked this out and you're right - I put the controller IP AND name in the AP and the AP came up right away - thanks!