02-20-2018 08:08 AM - edited 07-05-2021 08:16 AM
1 of the 4 WiSMs here reboots itself when the web GUI is started. The other 3 do not do this.
sequence:
1. type in it's IP @ in a browser while you have a CLI session for it open
2. the CLI shows it go offline and then starts it reboot
3. obviously, it drops all WAPs and the attached clients and the WAP associate to one of the other 3 WiSMs
4. once the reboot is done, WAPs slowly begin to be moved to the bad boy WiSM
We are going to replace our entire WiFi, which will take months, since the WiSM is end-of-existence but I'm getting tired of this since my backup person does not know the WiSM CLI nor can I show co-workers anything concerning the WiSM configuration on the CLI. The GUI is more helpful for that.
TAC looked for a similar case but came up w/ nothing that applied.
They are all on the same v7.0.252.0 code.
Solved! Go to Solution.
02-23-2018 07:35 AM - edited 02-23-2018 07:36 AM
A reboot of the WiSM fixed this.
It seems not all reboots are equal. When it was crashing/rebooting, that reboot never fixed this but this plain old reboot did when not preceded by an invocation of the GUI in a browser. Thanks.
02-20-2018 07:40 PM
02-21-2018 07:08 AM
02-21-2018 12:28 PM
02-21-2018 12:51 PM
02-23-2018 07:35 AM - edited 02-23-2018 07:36 AM
A reboot of the WiSM fixed this.
It seems not all reboots are equal. When it was crashing/rebooting, that reboot never fixed this but this plain old reboot did when not preceded by an invocation of the GUI in a browser. Thanks.
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