Backup wireless controller fail somtimes for some SSID


Userlevel 2
Hi all,

I have setup of 2 wireless controllers, 5 SSID and 200 APs. 4 Topologies are bridged at EWC and one at AP. Everything is going and working well as all access points are active in the main wireless controller. But when some APs move to be active on the backup controller some SSIDs (bridged at EWC) don't work well sometimes for some users while other SSIDs keep working well.

I checked the path between two wireless controllers and all Topologies are reachable and synchronized.

I am using C5210 and software 09.21.06.0006 for both controllers

Anyone have an idea what could be wrong?!

Thanks in advance,
Husam

12 replies

Userlevel 7
Do all the topologies match on both controllers, or are you trying to move users to different vlans/networks during the fail-over? This is kind of hard to troubleshoot on the Hub, I would suggest that you contact GTAC and start a case so both configs can be reviewed.
Userlevel 7
Doug wrote:

Do all the topologies match on both controllers, or are you trying to move users to different vlans/networks during the fail-over? This is kind of hard to troubleshoot on the Hub, I would suggest that you contact GTAC and start a case so both configs can be reviewed.

Also make sure the time between controllers is synced (even if you have NTP configured)
Userlevel 2
Doug wrote:

Do all the topologies match on both controllers, or are you trying to move users to different vlans/networks during the fail-over? This is kind of hard to troubleshoot on the Hub, I would suggest that you contact GTAC and start a case so both configs can be reviewed.

Hi,
It is same topology and same configuration as I made and synchronized it from man controller.

The problem come up when some APs moved to be active on the backup controller and that result in some users can connect to wireless network but they can not have access to to any resources in the network even the default getaway, but some other users keep working normally.

regards,
Husam
Userlevel 2
Doug wrote:

Do all the topologies match on both controllers, or are you trying to move users to different vlans/networks during the fail-over? This is kind of hard to troubleshoot on the Hub, I would suggest that you contact GTAC and start a case so both configs can be reviewed.

for time as well they are going at same min!
Userlevel 7
Is mobility configured and is the mobility tunnel up.

Please also decribe in more detail what "don't work well" mean.

-Ron
Userlevel 2
Ron wrote:

Is mobility configured and is the mobility tunnel up.

Please also decribe in more detail what "don't work well" mean.

-Ron

Hi

I mean that some users can connect to wireless network but they can not have access to to any resources in the network even the default getaway, but some other users keep working normally.

Regards,
Husam
Userlevel 2
Ron wrote:

Is mobility configured and is the mobility tunnel up.

Please also decribe in more detail what "don't work well" mean.

-Ron

For mobility is up!
Userlevel 7
Pretty sure that this is related to mobility but we'd need a network diagram to unterstand the setup and to give you some advise.
Userlevel 7
Ron wrote:

Pretty sure that this is related to mobility but we'd need a network diagram to unterstand the setup and to give you some advise.

A screenshot of the affected topology from both controllers would also help.
Userlevel 2
Ron wrote:

Pretty sure that this is related to mobility but we'd need a network diagram to unterstand the setup and to give you some advise.

Hi
I thought that the mobility is related roaming the user between two APs each one is connected to different EWC. But my case is that if one AP moved to be active on the Backup controller, sometimes some user already connected or new connected to this AP can not reach the gateway and nothing else in the network. This case for some user not for all of them.

attached is screenshot of home page, mobility config and affected topology.



Userlevel 7
Hi Husam, Do you still need help with this issue?
Userlevel 2
Hi,

Thank you. It is solved. it was miss-configuration related to default gateway of some topology.

Best regards

Reply