Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. If you'd prefer to explore, try our test area to get started. And see here for current known issues.

New Member

New 5508 in network

We have an existing WLAN with 2 WISM's that support 100 AP's. We just completed a resurvey and have installed 4 5508's WLC's and 500 new 1142 AP's. The new 5508's are online but when we bring one of the new 1142 aps online it joins the WISM instead of the new 5508. We are able to move the AP from the WISM to the 5508 but this is too time consuming. What we would like to have happen is for all of the new 1142's be bring up we would like them to join the 5508. We have option 43 configured on the new controllers but the AP's still join the old. The dns record for CAPWAP is still pointing to the WISM so we are wondering if we changed it to point to the management interface of the 5508 would that cause all of the new aps to join the new controllers. Also if one of the old aps drops off net, reboots, etc will it now try to joon the new controller or if the manual proccess is NOT completed to totally clear the config on the old ap will it still join back to the old controller.

Everyone's tags (2)
11 REPLIES
VIP Purple

New 5508 in network

You can configure HA (Primary, Secondary, tertiary) for APs in order to get them register to required WLC. If you ensure you configure 5508 as primary controller for all your AP, it will go & join that controller.

If you have Prime/WCS you can push a template to do this very easily, rather going through each AP & configure it

HTH

Rasika

**** Pls rate all useful responses ****

New Member

New 5508 in network

Not sure how HA is going to help here unless the AP has already joined the new controller. After it has joined the WISM wecan go in and configure HA to point to the new 5508's and they will move to it. This deployment is more than 700 AP's and we don't want that manual effort for every AP.

We do run a Prime/WCS enviroment but the customer made the decision to deploy the new network on their side so they will not have the use of our WCS.

Bronze

New 5508 in network

Use master controller option, since this is a new deployment.

"

Q.   When should I use the master controller mode on a WLC?

A. When there is a master controller enabled, all newly added access       points with no primary, secondary, or tertiary controllers assigned associate       with the master controller on the same subnet. This allows the operator to       verify the access point configuration and assign primary, secondary, and       tertiary controllers to the access point using the All APs >       Details page.

The master controller is normally used only when adding new access       points to the Cisco Wireless LAN solution. When no more access points are being       added to the network, Cisco WLAN solution recommends that you disable the       master controller.

http://www.cisco.com/en/US/products/ps6366/products_qanda_item09186a008064a991.shtml

New Member

New 5508 in network

We attempted that but the new AP's still preferred to join the WISM instead of the new 5508's

Bronze

New 5508 in network

Hi,

the AP you are testing with has never joined a WLC before?

remove that DNS entry temporary, and check for the master controller option on the old WLC.

can you post a console output from the AP while its trying to join?

New Member

New 5508 in network

Our next step actually is going to be to change dns to point to the new 5508's instead of the 4400's/wisms. We fully expect that this will resolve the issue withe the new AP's joining the new 5508's. Will update after testing is completed next week.

VIP Purple

Re: New 5508 in network

This won't help much to resolve your issue. Even though you send 5508 IP via DNS as long as 5508 & WiSM are in the same mobility group your APs will learn all of those controller IPs. Therefore you have to configure HA (Primary, Secondary) feature if you want certain APs to  go & register for a given controller as Primary/Secondary/Tertiary WLC. Without that feature it is upto WLCs to decide which AP will register to which WLC (depend on the load of each WLC).

If you do not have Prime or WCS option then you can try CLI method to configure HA, once AP registered to a particular controller.This will avoid go to each AP like in GUI method.Here is the CLI command syntax to do this.

(WLC) >config ap primary-base < Primary WLC IP address>

(WLC) >config ap secondary-base

For example your primary 5508 name is 5508-1 with Mgt IP 192.168.10.10 & AP names are LAP1-LAP100. Assuming those will be registerd to WiSM, then you can configure HA for those AP using WiSM CLI like below

(WISM) >config ap primary-base 5508-1 LAP1 192.168.10.10

(WISM) >config ap primary-base 5508-1 LAP2 192.168.10.10

(WISM) >config ap primary-base 5508-1 LAP3 192.168.10.10

.

.

.

(WISM) >config ap primary-base 5508-1 LAP100 192.168.10.10

Read this post for more information about AP failover

http://mrncciew.com/2013/04/07/ap-failover/

HTH

Rasika

**** Pls rate all useful responses ****

New Member

Re: New 5508 in network

I understand what you are saying but it does not resolve the customers issue. He does not want to have to manually configure aftereach AP has joined the WLC. I can tell you that the WISM and the 5508's had different mobility groups defined. Below is how we generally define. This the template I used for the inital config on the 5508's The customers WISM's are similar but not exactly the same.

Name

MKT-XXXX-WLC##

802.3x Flow Control Mode

Disabled

LWAPP Transport Mode

Layer 3

LAG Mode on next reboot

Disabled

Broadcast Forwarding

Disabled

AP Multicast Mode

Multicast

Multicast Group Address

232.10.0.11 (WLC1)

232.10.0.12 (WLC2)

232.10.0.13 (WLC3) 232.10.0.14 (WLC4)

etc..

Aggressive Load Balancing

Disabled

Peer to Peer Blocking Mode

Disabled

Over the Air Provisioning of AP

Disabled

AP Fallback

Enabled

Apple Talk Bridging

Disabled

Fast SSID change

Disabled

Default Mobility Domain

MKT-XXXX-mg

RF-Network Name

MKT-XXXX-rf

User Idle Timeout (seconds)

300

ARP Timeout (seconds)

300

Web Radius Authentication

PAP

WebAuth Proxy Redirection Mode

Disabled

WebAuth Proxy Redirection Port

0

802.3 Bridging

Disabled

Mobility Management

Mobility Groups

MAC Address

all WLCs

IP Address

all WLCs

Group Name

MKT-XXXX-mg

Mobility Anchor Config

Keep Alive Count

3

Keep Alive Interval

10

Symmetric Mobility Tunneling mode

Enabled

DSCP Value

0

Hall of Fame Super Silver

Re: New 5508 in network

Is the new wlc's on the same subnet as the WiSM? Also, with 500 new AP's, I would think that you would still need to properly place AP's on the new wlc's.

If I were you, I would not use option 43 and only have one DNS entry to point to maybe your 4th new 5508. I would also make sure the master controller is enabled on that WLC. Let the AP's join that WLC and then write a script to configure the primary, secondary and tertiary WLC.

If you for some reason still have AP's joining the old WiSM, then enable AAA AP authorization to prevent AP's from joining the WiSM's. Just remember this will also prevent current access point from rejoining that WiSM if the AP bounces.

Sent from Cisco Technical Support iPhone App

Sent from Cisco Technical Support iPhone App

-Scott
*** Please rate helpful posts ***
New Member

Re: New 5508 in network

I suggested that option 43 not be used but the site engineer insisted that it was the solution and he is the customer. He is going to make the dns change to point to one of the new WLC's and we will see how it goes. As far as the WISM's and the new WLC subnets go they are NOT on the same subnet forthe  Manager or AP-Manager IP's.

Hall of Fame Super Silver

Re: New 5508 in network

Well not really knowing how everything is setup makes it a bit difficult to tell you what you should do. If they want to use option 43, make sure it is setup right and is only pointing to one if the new 5508's. Console into a new AP, connect it to the network and see if the AP gets an IP address and option 43 is providing the WLC management IP. If option 43 is setup wrong, you will see this from the console. You will also see how the ap is discovering the WLC and if it's still the WiSM, you will know why.

Sent from Cisco Technical Support iPhone App

-Scott
*** Please rate helpful posts ***
330
Views
0
Helpful
11
Replies