802.11 Client Device Interoperability

Reply
Occasional Contributor I

Windows 7 clients behaviour when local-master failover

Hi

We have a local-master deployment with one local controller and the master acting as the backup LMS.

We have found a problem when local controller fails with windows 7 clients that we don't see with windows XP clients, both using the WZC suplicant. We're using WPA2-ENTERPRISE, with machine authentication enforced and IAS server in the radius side. Both XP and W7 correctly log in then network.

When local fails APs correctly register with master controller, and both W7 and XP clients see the WLAN going down and up again, correctly authenticating in the network and asking for IP addresses.

When local controller comes back, APs preempt to it after the preemption time, XP clients see the WLAN going down and up and thus asking for IP addresses, but W7 clients seem to not be aware of the WLAN failure. So, W7 still have the same IP address that was taken during the local controller failure and therefore they lose connection to the network.
We have seen that during the master->local preemption, the SSID is still radiating all the time (as seen using Network Stumbler). When fail-over occurs, we do see the SSID stop radiating for some time.

Our first thoughts pointed to a WZC issue but the fact that we don't see the SSID stop radiating suggest that the controllers maybe have something to do. Any ideas?


Hi

We have a local-master deployment with one local controller and the master acting as the backup LMS.

We have found a problem when local controller fails with windows 7 clients that we don't see with windows XP clients, both using the WZC suplicant. We're using WPA2-ENTERPRISE, with machine authentication enforced and IAS server in the radius side. Both XP and W7 correctly log in then network.

When local fails APs correctly register with master controller, and both W7 and XP clients see the WLAN going down and up again, correctly authenticating in the network and asking for IP addresses.

When local controller comes back, APs preempt to it after the preemption time, XP clients see the WLAN going down and up and thus asking for IP addresses, but W7 clients seem to not be aware of the WLAN failure. So, W7 still have the same IP address that was taken during the local controller failure and therefore they lose connection to the network.
We have seen that during the master->local preemption, the SSID is still radiating all the time (as seen using Network Stumbler). When fail-over occurs, we do see the SSID stop radiating for some time.

Our first thoughts pointed to a WZC issue but the fact that we don't see the SSID stop radiating suggest that the controllers maybe have something to do. Any ideas?


Thanks,

Jose
Aruba Employee

Windows 7 clients behaviour when local-master failover

Are both controllers on the same subnet? Is the client in the same VLAN no matter which controller he is on?

Thanks,
Zach
Thanks,

Zach Jennings
Occasional Contributor I

Re: Windows 7 clients behaviour when local-master failover

The controllers are on different sites, so VLANs and IP addressing are different.

We're currently having a look at windows registry entries if there is something that could be done with it.

Thanks,

Jose
Search Airheads
cancel
Showing results for 
Search instead for 
Did you mean: