HOW WISM LOAD BALANCING WORKS ?

[abelleli71]

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

[jeff.kish]

Fortunately, you don't need the domain name. Just give the hostname for the WLC, which I guess is "gobbi-wism-a-manager". Try that and see if it works!

[abelleli71]

Unfortuantely happen this:

1. First time the AP register with the PRIMARY

2. Second time ( 2nd reboot of the AP ) the AP registe with a WLC that is not present neither in PRIMARY nor SECONDARY .

That's very a strange case

q: the show run-config ( not show running config ) of the WISM is like a show tech ?

thanks

[jeff.kish]

The show run-config is like a show tech because it provides a lot of info, but it doesn't show all the exact same info.

Are all WiSM controllers configured for the same mobility group? How are the access points supposed to find the controllers? Through broadcast, DNS, or DHCP?

Also, ensure that "Master mode" is disabled on all controllers. You can find this under the "Controller" tab in the controller GUI.

[abelleli71]

Here the answer :

1.Are all WiSM controllers configured for the same mobility group?

YES the same for all

2.

How are the access points supposed to find the controllers? Through broadcast, DNS, or DHCP?

How to check it ?

3. Master mode" is disabled

YES

We make other test and try to reload the WLC and will let you know

Alberto

[abelleli71]

This is an AP configuration catch from show-run (WLC)

I suppose the DHCP is not enable

I suppose that the controller find the AP's through BROADCAST ( IGMP snooping is disabled )

The test fail another time :

3 reload = 2 times follow the hyerarchy 1 time go to another WLC ( not listed in the GUI )

Interface Name................................... wifi-guest-lwapp

MAC Address...................................... 00:18:ba:df:ef:8b

IP Address....................................... 10.6.191.253

IP Netmask....................................... 255.255.224.0

IP Gateway....................................... 10.6.191.254

VLAN............................................. 623

Quarantine-vlan.................................. no

Active Physical Port............................. LAG (29)

Primary Physical Port............................ LAG (29)

Backup Physical Port............................. Unconfigured

Primary DHCP Server.............................. 10.6.191.250

Secondary DHCP Server............................ Unconfigured

DHCP Option 82................................... Disabled

ACL.............................................. Unconfigured

AP Manager....................................... No

Guest Interface.................................. No

[abelleli71]

We can consider this sentence by Cisco . That the AP join the WLC if setup in the primary , secondary etc... and ( important ) he consider the LESS LOADED ( and our WLC has got 9 AP the other 3 WLC has got 90 AP )

The AP then attempts to join the least loaded WLC, which is the WLC with the greatest available AP capacity. After an AP joins a WLC, the AP learns the IP addresses of the other WLCs in the mobility group from its joined WLC.

Here the Cisco sentence :

Subsequently, the AP sends LWAPP primary discovery requests to each of the WLCs in the mobility group. The WLCs respond with a primary discovery response to the AP. The primary discovery response includes information about the WLC type, total capacity, and current AP load. As long as the WLC has the AP Fallback parameter enabled, the AP can decide to change over to a less loaded WLC

[jeff.kish]

Make sure to set all controllers to use AP Fallback mode.

Also, under Controller -> Mobility Management (on the left) -> Mobility Groups, have you added each controller management IP address to this list?

Also, are all controller management interfaces in the same subnet?

[abelleli71]

PROBLEM SOLVED

We do not put IP ADDRESS inside the PRIMARY FIELD neither the DNS NAME but the SYSTEM NAME ( case sensitive )

So :

IP 10.0.0.11 ( NOT CORRECT )

gobbi-wism-a.sw.unibocconi.it ( NOT CORRECT )

WiSM-A-Gobbi ( correct ! )

THANKS FOR YOUR TIME

[jeff.kish]

Haha, whew! Glad this nightmare is over for you :)