10-31-2011 07:39 AM - edited 07-03-2021 09:00 PM
Hello All,
I currently have a WLC4402 in my HO with approx 20 AP, my AP's register with the WLC using a DNS lookup with CISCO-LWAPP-CONTROLLER static entry.
I would like to install a second WLC and 20 AP's in a Remote location, how can I configure the AP's in the remote location to register with the new local WLC. I do not want the AP's coming back across the wan to register with the HO WLC.
Hope this makes sense and any ideas would be much appreciated.
Cheers
Colin
Solved! Go to Solution.
10-31-2011 07:56 AM
Hi Colin,
Few options :
1) Change the DNS entry to reflect new WLC.
-DNS:The LAP attempts to resolve the DNS name
"CISCO-LWAPP-CONTROLLER.localdomain
CISCO-CAPWAP-CONTROLLER.locadomain
2)Option 43 :
http://cisco.com/en/US/tech/tk722/tk809/technologies_configuration_example09186a00808714fe.shtml#t2
Note: If you configure option 43 and DNS the AP would prefer DNS in later codes..{atleast what I tested }.. Not sure which software version this go changed..But what documentation says it will prefer option 43.
Link:
http://cisco.com/en/US/tech/tk722/tk809/technologies_tech_note09186a00806c9e51.shtml
2) IP helper address . { not recommeded but a dirty way to get APs joined to the WLC }.
switch#config t
switch(config)#int vlan x
switch(config-if)#ip helper-address
switch(config-if)#exit
switch(config)#ip forward-protocol udp 5246
switch(config)#ip forward-protocol udp 12222
switch(config)#ip forward-protocol udp 12223
switch(config)#ip forward-protocol udp 5247
{Please remove the above commands after AP joins }
3)Statically Assign the WLC IP on the AP by consoling in:
debug lwapp console cli
deb lwapp cli no-reload
lwapp ap controller ip address
Test lwapp controller ip
Default use/pass: cisco/Cisco
Replace lwapp with capwap if using 5.2 software or higher.
4) Leave the way it is and use Mobility configuration to move APs acorss right WLC.
http://www.cisco.com/en/US/tech/tk722/tk809/technologies_configuration_example09186a008064a294.shtml?
Note: Since your existing APs have joined the WLC, changing those values will not affect them .
Thanks.Salil
10-31-2011 07:58 AM
Hello Colin
as i understand
you have AP's in head office , say VLAN X
and in remote office they will be in new VLAN Y (subnet)
and vlan X and Y share the same DNS server.
- the suggestion would be on the DHCP scope of VLAN y ( remote the DNS server and DNS domain name),
and configure the DHCP option 43 to point to new WLC.
hope this answers your query
Best regards
Talal
===
Don't forget to rate answers that you find useful
please rate answers that you find useful , and mark as answered - when it is :-) - so others can find it easily
10-31-2011 07:56 AM
Hi Colin,
Few options :
1) Change the DNS entry to reflect new WLC.
-DNS:The LAP attempts to resolve the DNS name
"CISCO-LWAPP-CONTROLLER.localdomain
CISCO-CAPWAP-CONTROLLER.locadomain
2)Option 43 :
http://cisco.com/en/US/tech/tk722/tk809/technologies_configuration_example09186a00808714fe.shtml#t2
Note: If you configure option 43 and DNS the AP would prefer DNS in later codes..{atleast what I tested }.. Not sure which software version this go changed..But what documentation says it will prefer option 43.
Link:
http://cisco.com/en/US/tech/tk722/tk809/technologies_tech_note09186a00806c9e51.shtml
2) IP helper address . { not recommeded but a dirty way to get APs joined to the WLC }.
switch#config t
switch(config)#int vlan x
switch(config-if)#ip helper-address
switch(config-if)#exit
switch(config)#ip forward-protocol udp 5246
switch(config)#ip forward-protocol udp 12222
switch(config)#ip forward-protocol udp 12223
switch(config)#ip forward-protocol udp 5247
{Please remove the above commands after AP joins }
3)Statically Assign the WLC IP on the AP by consoling in:
debug lwapp console cli
deb lwapp cli no-reload
lwapp ap controller ip address
Test lwapp controller ip
Default use/pass: cisco/Cisco
Replace lwapp with capwap if using 5.2 software or higher.
4) Leave the way it is and use Mobility configuration to move APs acorss right WLC.
http://www.cisco.com/en/US/tech/tk722/tk809/technologies_configuration_example09186a008064a294.shtml?
Note: Since your existing APs have joined the WLC, changing those values will not affect them .
Thanks.Salil
10-31-2011 07:58 AM
Hello Colin
as i understand
you have AP's in head office , say VLAN X
and in remote office they will be in new VLAN Y (subnet)
and vlan X and Y share the same DNS server.
- the suggestion would be on the DHCP scope of VLAN y ( remote the DNS server and DNS domain name),
and configure the DHCP option 43 to point to new WLC.
hope this answers your query
Best regards
Talal
===
Don't forget to rate answers that you find useful
please rate answers that you find useful , and mark as answered - when it is :-) - so others can find it easily
10-31-2011 12:03 PM
Hey Guys,
I like the DHCP option 43 to make the connection, by looking at the other options its most likely the easiest to implement.
Thnaks Again.
Colin
10-31-2011 07:19 PM
Actually you only need to forward UDP 5246 for capwap and 12223 for lwapp. You dont need the those extra ports ...
11-01-2011 06:11 AM
Is this done at the switch port level ?
11-01-2011 06:54 AM
Layer 3 vlan for the AP vlan.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide