Can Unleashed "hallucinate" SSID's, or is something darker going on?

[Woody]

I have two R510's running Unleashed V 200.15.6.212.20. They run fine, no issues at all.

As AP's they deliver one 2.4Ghz SSID and one 5Ghz SSID - without band steering (so that IOT devices connect to the separately named 2.4Ghz) and all other devices to 5Ghz.

I purchased an R710 on ebay. It was brand new in box and had the original FW. I did a hard factory reset (the one with the paperclip) and installed Unleashed V 200.15.6.212.20. When it booted up, it did the Master election and configured itself from the other two R510's.

Yesterday, I removed one of the R510's from the network and installed this "new" R710 in its place.

All worked perfectly, until approx 8 hours later, when I noticed that ALL the LED's were no longer lit (not even the red one) on the R710. In my confusion, I presumed that the R710 had crashed or, that somehow I had configured a setting to turn off the external LED's. So I did a WiFi scan, and could see that while all the LED's were off, the R710 was still live, but advertising a SSID of "Technical.Support-2331". This is not my SSID or anything like a SSID I have ever set.

Confused, I powered down the R710 and replaced it with the R510 that I had removed earlier.

This is where it gets really spooky..

Once the R510 had booted up, it too only offered (a 2.4GHz and 5Ghz) SSID of Technical.Support-2331 and NOT the previous SSID's that I had programmed and have been used by all the WiFi devices in the house since the year dot.

So I took my Android phone, connected to the Technical.Support-2331 SSID - and using the password for the old SSID that this had replaced, two things happened:

1. My phone connected to the Technical.Support-2331 SSID - but using the password from the previous SSID.

2. At the exact moment of connection (1.) the broadcast SSID changed from Technical.Support-2331 back to the correct legacy SSID.

12 hours later, all is well with the world and Technical.Support-2331 SSID has not re-appeared and just in case that you think I have been drinking, I pulled this out of the logs for the very moment that I successfully connected to the Technical.Support-2331 SSID, - at the point the SSID name changed back to the original:

2025/06/22 23:10:38 Low WLAN[Technical.Support/Technical.Support-2331] with BSSID[60:d0:2c:25:d6:48] has been removed from radio [11b/g/n] of AP[Ruckus-R510-Kitchen@60:d0:2c:25:d6:40]
2025/06/22 23:10:38 Low WLAN[Technical.Support/Technical.Support-2331] with BSSID[60:d0:2c:25:d6:4c] has been removed from radio [11a/n/ac] of AP[Ruckus-R510-Kitchen@60:d0:2c:25:d6:40]

Any bright ideas as to what is going on here?

The only thing that I can think, is a remote controller thinking this device belongs to them - and resetting the SSID, or is maybe, Technical.Support-2331 a kind of engineering default SSID, which gets used as a default if a config fails?

[declareguacamol]

@bitlife Sounds like a fallback or diagnostic SSID triggered by a sync glitch or failed config. Good call checking the logs — might be worth reporting to Ruckus in case it’s a hidden feature or bug.