OOOOOOOKKKKKKK this is kinda weird. I have had this WS-8-250-AC-white up on the new version for maybe 8 hours today. As you can see from some previous posts, I was trying to get the details for the simplest case of Discovery not working, so I reset to factory defaults from the WebUI and when it came back, applied the change for ubiDiscovery and did the testing I described above. Then just left it there while I posted my results.
I came back and figured, hey, I should test ssh. Got in just fine. typed a "?" Wanted to see what the CLI configuration might look like. Typed "con" enter, followed by ? and read the list of commands in that mode. Typed exit, enter. Back to main prompt.
But then on my WebUI session window got the message:
"The configuration has changed on the device. You will not be able to save any configuration changes.
Click here to reload the configuration." (Unexpected since I had not made any changes)
Well I remembered that I wanted to set the IP to 192.168.1.21 (what I had before setting to defaults) . So I exited the ssh session. Then "Clicked here".
Seemed to reload the config. So I updated the IP and save applied. It took a few seconds to come back on the new IP. I clicked the Ports tab so I could turn POE back on port 6.
It displayed that page, then locked up and would no longer reply (no https, ssh, or ping) on 192.168.1.21 nor .20 . Traffic passed through it just fine. POReboot did not help. PC had no problems getting to the airRouter I was testing with on .110 off of the same 8 port 10/100 dumb switch they shared. Clearing PC ARP cache did not help. unplugging AirRouter did not help.
Tried everything except a console cable (which my partner had borrowed). So I finally tried the 10sec Reset switch on POReboot. That worked.
Since then I went back through the same steps, but could not reproduce.
There are a few hundred hours of uptime on this switch and it has gone through several firmware upgrades, this is the first time having to resort to the reset button.
