Changes to VNS settings require devices to "Forget This Network" before they will connect to same network, same credentials - C5210

  • 0
  • 1
  • Problem
  • Updated 2 years ago
  • Solved
Seems that any changes to topology (i.e. to multicast filters) or associated VLAN tag cause clients to not be able to connect.  Turning off WiFi and turning it back on doesn't help.  Same SSID, same credentials, the only thing that seems to work is "Forget This Network" then re-add.  Has anyone else seen this and maybe have a work-around?
Photo of ITS Tech

ITS Tech

  • 70 Points

Posted 2 years ago

  • 0
  • 1
Photo of Ronald Dvorak

Ronald Dvorak, Embassador

  • 51,164 Points 50k badge 2x thumb
Have you tried to disassociate the client in the client per VNS report ?

With "connect" do you mean "connect to the SSID" or do you mean to get an IP from the new subnet bacause you've changed the VLAN = other subnet.
Photo of Ty Kolff

Ty Kolff

  • 1,098 Points 1k badge 2x thumb
I have noticed this when the AP's and VNS's belong to a site it will boot users off when any changes are made to any of the networks belonging to that site. 

I haven't noticed the problem when the AP's are NOT members of a site.
Photo of Umut Aydin

Umut Aydin, Escalation Support Engineer

  • 2,300 Points 2k badge 2x thumb
If this issue happen on different end-clients then I would open a case with GTAC.This need to be worked with Engineering if this behaviour is expected within the site config.
But from my feeling and sounding I wouldn't expect this because this would cause everywhere that the clients need to be re-enabled again.
Please open a case by GTAC