10-08-2008 12:01 AM - edited 07-03-2021 04:34 PM
We currently have a campus with 4 WISM on 4 6509 .
After a reload of one of these WISM, all the AP ( AIR-AP1231 ) disappear from this WISM :
(WiSM-slot1-2) >show ap summary
Number of APs.................................... 1
Before the reload this WISM has 80 AP .
The other 79 AP are now registered with another WISM .
Is this normal or ( load balancing ) or what ?
Any help is apreciated
Solved! Go to Solution.
10-08-2008 05:27 AM
You have to check the primary/secondary/tertiary settings on the WLC, but for each access point. Go to the Wireless tab and click on an access point for this setting.
AP Fallback mode is on the WLC under the Controller tab. It forces an access point to join its primary controller if possible. If it's disabled, the access point will be happy to stay on a non-primary controller until it reboots. If it's enabled, then as soon as its primary becomes available (either because it comes up or because you specify a new primary), it will join that controller.
AP Fallback is convenient for load-balancing, but it can cause significant downtime if a controller goes down and comes back up immediately. All your APs will fail over to another controller at the initial drop, but they'll all switch back over once the original controller comes back. Each time will cause clients to drop. If a controller starts flapping for any reason, your wireless network will be seriously disrupted. Of course, if you leave it disabled and a controller goes down, all access points will hop over to their secondary controller and never go back. This isn't so bad, though, because you can just manually set it for AP fallback at a convenient time, let them all switch back, and then disable fallback again.
If you do not active AP fallback mode, be sure to reset each AP after you give it a primary/secondary/tertiary controller. Otherwise it will sit tight on the current controller.
Also, make sure that the Master Controller mode is disabled. This forces all access points to join it if you have no primary controller listed. It's under the Controller tab, under Advanced.
10-08-2008 01:47 AM
One solution can be the Configuring Auto-Anchor Mobility ?
10-08-2008 03:48 AM
Make sure you have your mobility groups setup on each wlc. Also make sure you have set the primary, secondary and or tertiary wlc on the ap. Last but not least, verify that you have ap fallback enabled on the wlc's. This option will forces the ap to go back to the primary wlc that is is configured for.... as long as everything is configured correctly.
10-08-2008 04:11 AM
Make sure you have your mobility groups setup on each wlc.
YES I HAVE
Also make sure you have set the primary, secondary and or tertiary wlc on the ap
I HAVE TO CHECK IT ON THE AP ?
you have ap fallback enabled on the wlc's
ON THE WLC ? OR ON THE AP ?
thanks a lot
10-08-2008 05:27 AM
You have to check the primary/secondary/tertiary settings on the WLC, but for each access point. Go to the Wireless tab and click on an access point for this setting.
AP Fallback mode is on the WLC under the Controller tab. It forces an access point to join its primary controller if possible. If it's disabled, the access point will be happy to stay on a non-primary controller until it reboots. If it's enabled, then as soon as its primary becomes available (either because it comes up or because you specify a new primary), it will join that controller.
AP Fallback is convenient for load-balancing, but it can cause significant downtime if a controller goes down and comes back up immediately. All your APs will fail over to another controller at the initial drop, but they'll all switch back over once the original controller comes back. Each time will cause clients to drop. If a controller starts flapping for any reason, your wireless network will be seriously disrupted. Of course, if you leave it disabled and a controller goes down, all access points will hop over to their secondary controller and never go back. This isn't so bad, though, because you can just manually set it for AP fallback at a convenient time, let them all switch back, and then disable fallback again.
If you do not active AP fallback mode, be sure to reset each AP after you give it a primary/secondary/tertiary controller. Otherwise it will sit tight on the current controller.
Also, make sure that the Master Controller mode is disabled. This forces all access points to join it if you have no primary controller listed. It's under the Controller tab, under Advanced.
10-08-2008 05:30 AM
Jeff explained it perfectly.... test it with one ap first just in case. If that ap works, then you can go a head and make the changes to the rest of the ap's.
10-08-2008 05:35 AM
Thank you very much
i think was also explained here :
10-08-2008 06:45 AM
To make my AP come back up to the previous position I have to place the FALLBACK and then RESET the AP ....or just place the FALLBACK and wait ?
10-08-2008 06:50 AM
Just enable fallback. If that doesn't work, then you have some configuration issue.
10-08-2008 08:22 AM
Correct. And if AP fallback is not enabled, simply reset the access point to have it join its primary again.
10-13-2008 04:23 AM
Hello
just check with my client the WISM configuration and the FALLBACK is enable on the PRIMARY SECONDARY etc..
When reload the APs ( 80 AIRONET ) the NEVER come back on the PRIMARY or SECONDARY but they register with other CONTROLLERS
Do I have to create different MOBILITY GROUP for each zone ?
Now I have only one mobility Group ( with 6 WISM MODULE )
ThanKS
10-13-2008 05:00 AM
Just to clarify, have they configure primary, secondary, and tertiary controllers on each access point individually (through the WLC)?
Be sure that they're using WLC names and not IP addresses.
10-13-2008 05:13 AM
They have configured PRIMARY , SECONDARY etc..
They use IP address ...Can cause a problem ?
10-13-2008 10:45 AM
Yes, you should configure it with the controller name, not IP address. Try that and let us know what happens.
10-15-2008 02:36 AM
Hello
we are very unlucky becasue our host-name is too long for the field in the GUI of WLC
gobbi-wism-a-manager.sw.unibocconi.it
I see also that is not possible to insert via CLI...
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