HELP NEEDED - Misconfigured SG2008 L2 swtich for 802.1x, had to factory reset switch, readopt Mess

HELP NEEDED - Misconfigured SG2008 L2 swtich for 802.1x, had to factory reset switch, readopt Mess

HELP NEEDED - Misconfigured SG2008 L2 swtich for 802.1x, had to factory reset switch, readopt Mess
HELP NEEDED - Misconfigured SG2008 L2 swtich for 802.1x, had to factory reset switch, readopt Mess
2025-07-08 02:53:44 - last edited 2025-07-13 18:15:22
Hardware Version: V4
Firmware Version: 4.20.9

While attempting to "try new things" because I am out of options with my FreeRADIUS goat-toss (separate though related issue and aging series of tickets, also still un-resolved),... I misconfigured my SG2008 switch by enabling 802.1x on the port which was configured for and connected to my SDC. No other ports were configured such that the SDC could be reconnected on a different port ... So as you might have guessed, I had to factory reset the SG2008 switch.

 

Now, I remember thinking ... hey, no big deal. The SDC has the devices configuration saved right? So i simply undo my mistake within the Controller for the switch port, factory reset the switch, wait for it to boot, force provision from SDC and viola .... back to golden! Right?   Nope!

 

Imagine the needle of a panic meter slamming all the way to "freak out" so hard that it actually begins spinning on the gauge, breaking the glass, flying off its spindle and embedding itself into the nearby wall only inches from the receptionists head .... yep, that's me right now.

 

The SDC did in fact see the switch device as it finished rebooting after having performed a factory reset .... but the SDC sees the switch as a BRAND NEW device, never before connected .... its as if the SDC magically wiped any knowledge of its previous existence from all of its data stores... 

 

Except ..... 

 

the switches MAC address hasn't changed, Hmmmmmm....  nor has its IP to MAC binding both still present within the SDC. And hold on a minute, on closer inspection I still have all of my switch and vlan profiles right there in the SDC ... but the reset switch is somehow strange to the SDC now. Force Provisioning doesnt do squat, I have to go in and RECONFIGURE THE ENTIRE SWITCH FROM SCRATCH?! Clearly I'm missing something here....

 

I mean, ARE YOU KIDDING ME? Where in the virtually non-existent switch documentation does it state in HUGE BOLD RED LETTERS that factory resetting the device will LOSE ALL CONFIGURED SETTINGS? I must be blind, because I keep looking and I still haven't been abe to find anything like that documented anywhere. Getting past that, though I am nowhere near past it believe that .... Is there nothing that can be done to recover the switches pre-factory-reset configuration such that something can be salvaged and reapplied to the device post-disaster?

 

I realize, the hardware is relatively inexpensive when compared to other "business class" options and I also realize that a customer with expectations sometimes looks a lot like an entitled millennial throwing a tantrum ... but I am not a millennial, I'm not throwing a tantrum (yes I am), and this is a very REAL and show stopping problem which I still can't believe anyone should ever have to suffer through. I mean Hello?! the SDC has all of the configurable information about the devices it controls within it.... Right? Doesn't it?!

 

But if not, then why on EARTH would a vendor take away the customers ability as an administrator to connect directly to the device post-adoption to SDC? That right there signals complete lunacy should anyone ever consider adopting any device ever again, I think Id rather just use them stand alone than to endure this nightmare again. Quite literally every single aspect of my network is down right now because of this. And at present, the only solution or way forward appears to be to reconfigure the switch from scratch and PRAY that it never happens again. Because if it should, there will be no way to recover without repeating this .... HELLSCAPE of a nightmare all over again.

 

So please enlighten me .... and anyone else who has had or will someday have this happen to them.... please tell us that there is a hope. That we don't actually have to manually reinvent the wheel from scratch every time we need to reset a switch.

 

 What is the general concensis on "best practices" with regard to recovering a factory reset switches pre-reset / disaster configuration?

 

 

SPOILER ALERT

 

Something other than "reconfigure from scratch" would be needed in the way of a response in order to be considered minimally acceptable.

 

 

And Thank You!, once again, for both your valuable time and kind consideration toward helping to one day perhaps resolving this enduring calamity.

 

 

It doesn't really matter whether you think that you can or whether you think that you can't .... either way .... you're always going to be correct.
  0      
  0      
#1
Options
1 Accepted Solution
Re:HELP NEEDED - Misconfigured SG2008 L2 swtich for 802.1x, had to factory reset switch, readopt Mess-Solution
2025-07-12 03:31:51 - last edited 2025-07-13 18:15:22

  @GRL 

 

I don't know what to tell you...

 

I didn't choose to "Forget Device" for the switch until after it failed to re-adopt for the ninth or tenth time and then only after having sat dead in the water for two days with no support.

 

What I finally did, what I should have done immediately after the incident occurred, and what I will certainly be doing at any point in the future should something like this ever happen again:

 

  • Correct any misconfigurations via the controller
  • Factory reset the misconfigured device
  • Login to the newly reset device (stand alone - pre-adoption), to provide admin credentials, IP info, and the controller info.
  • Restore controller from a recent backup taken before the misconfiguration occurred
  • Ensure all physical connections are correct and in place
  • Manually re-adopt the device via Controller
  • Review all settings to ensure any needed changes which occurred after the backup used for restoration was taken to the time of restore were re-applied / made and tested to ensure intended operation.

 

For some reason my pre-restore controller would not re-adopt the factory reset switch with its configuration in tact, it repeatedly saw the reset switch as a completely new device. That switch is my core switch and has a metric - TON of configuration the entirety of which I simply was not ready to re-design and then re implement again from square 0 ... I understand what it was supposed to do ... I also know what it did in this (albiet possibly isolated and 1 in a million) instance. Two very different pictures. 

 

Now I am back to a stable configuration with every device working as expected. Except for the WPA2-Enterprise EAP-TLS via FreeRADIUS problem that I was working on when I accidentally misconfigured the wrong switch port, thus taking us all full circle. Watch your step when exiting the ride, sensations of dizziness and nausea may be experienced and are not uncommon ... 

It doesn't really matter whether you think that you can or whether you think that you can't .... either way .... you're always going to be correct.
Recommended Solution
  0  
  0  
#3
Options
3 Reply
Re:HELP NEEDED - Misconfigured SG2008 L2 swtich for 802.1x, had to factory reset switch, readopt Mess
2025-07-11 08:08:37 - last edited 2025-07-11 08:08:51

  @Net-Moose 

 

I have pin-hole / terminal factory reset tons of my switches after failed experiments or goof-ups and they are always readopted with whatever settings the controller has for them (once the config is corrected before adoption)

 

The only time the controller totally forgets a device is if you "forget device" from inside the controller and/or you dont have "remember this device" ticked in its config

Main: ER8411 x1, SG3428X x1, SG3452 x1, SG2428LP x1, SG3210 x1, SG2218P x1, SG2008P x3, ES208G x1, EAP650 x6 Remote: ER7206 v2 x1, ER605 v2 x3, SG2008P x2, EAP650 x2, ES205G x1 Controller: OC300
  0  
  0  
#2
Options
Re:HELP NEEDED - Misconfigured SG2008 L2 swtich for 802.1x, had to factory reset switch, readopt Mess-Solution
2025-07-12 03:31:51 - last edited 2025-07-13 18:15:22

  @GRL 

 

I don't know what to tell you...

 

I didn't choose to "Forget Device" for the switch until after it failed to re-adopt for the ninth or tenth time and then only after having sat dead in the water for two days with no support.

 

What I finally did, what I should have done immediately after the incident occurred, and what I will certainly be doing at any point in the future should something like this ever happen again:

 

  • Correct any misconfigurations via the controller
  • Factory reset the misconfigured device
  • Login to the newly reset device (stand alone - pre-adoption), to provide admin credentials, IP info, and the controller info.
  • Restore controller from a recent backup taken before the misconfiguration occurred
  • Ensure all physical connections are correct and in place
  • Manually re-adopt the device via Controller
  • Review all settings to ensure any needed changes which occurred after the backup used for restoration was taken to the time of restore were re-applied / made and tested to ensure intended operation.

 

For some reason my pre-restore controller would not re-adopt the factory reset switch with its configuration in tact, it repeatedly saw the reset switch as a completely new device. That switch is my core switch and has a metric - TON of configuration the entirety of which I simply was not ready to re-design and then re implement again from square 0 ... I understand what it was supposed to do ... I also know what it did in this (albiet possibly isolated and 1 in a million) instance. Two very different pictures. 

 

Now I am back to a stable configuration with every device working as expected. Except for the WPA2-Enterprise EAP-TLS via FreeRADIUS problem that I was working on when I accidentally misconfigured the wrong switch port, thus taking us all full circle. Watch your step when exiting the ride, sensations of dizziness and nausea may be experienced and are not uncommon ... 

It doesn't really matter whether you think that you can or whether you think that you can't .... either way .... you're always going to be correct.
Recommended Solution
  0  
  0  
#3
Options
Re:HELP NEEDED - Misconfigured SG2008 L2 swtich for 802.1x, had to factory reset switch, readopt Mess
2025-07-13 18:24:03 - last edited 2025-07-13 18:26:55

Problem is now a non-issue ... self-resolved. If interested see last entry for what I ended up doing to return my factory reset switch to a readopted status fully configured from the software controller. Note, as the official documentation states (and as other experienced community members have echoed) this should not be your typical experience with performing a factory reset of an omada switch. This was simply what I had to do in my non-standard case. I recommend following the official documentation and guidance in the hopes it works for you ... and if it doesn't, then this is what worked for me, so maybe it could work for you too. Again, I am not a SME (Subject Matter Expert) so use your best judgment when deciding whether or not to adopt any of these steps into your recovery effort.

It doesn't really matter whether you think that you can or whether you think that you can't .... either way .... you're always going to be correct.
  0  
  0  
#4
Options