Omada Controller OC200 v1 SDN crash after latest firmware upgrade
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.Omada Controller OC200 v1 SDN crash after latest firmware upgrade
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
I need advice for those immediately done the upgrade of firmware. I have omada sdn controller v1 with version 4.2.8 in process of upgrading to the latest release 4.2.11 crash after the reboot process if an upgrade. Tried already to remove the poe supplied cable then reconnect. Seem it's crash during the reboot process. I have s backup USB always connected to this controller while I performed as well to have my system configuration and full 365 downloads back up of data from my controller before performing the upgrade. Its noticeable light for power is steady on notice can't see my static IP assigned to this controller from my router. Need to advise on how to restore first before resetting(pressing) manually the pinhole reset button from the controller. I have a voucher system set up to maintain. 4 units out of 16 AP 225 outdoor can't link in mesh other EAP's. To mentioned online backup for my oc200 v1 backup controller is successful. Thank you.
Up to Date after several days hours of trial restoration remotely with my relatives (while I'm abroad) is a journey :)
Procedure Done in restoration from some advice read and share by @Fae
1. Factory reset performed from recovery page of OC200 v1. The steps as follow.
a. Do the initial reset button procedure from a pinhole of oc200 while connected to the live network.
b. Disconnect the crash OC200 from the working network.
c. Take the laptop offline from the live network and in Network Card IPv4 set the static ip 192.168.0.10 / Subnet Mask 255.255.255.0 / Default Gateway 192.168.0.253 (which is the default fallback IP Address of OC200)
d. connect the lan cable (cat6) to eth2 of oc200 controller and lan of laptop.
e. Power on the OC200 (with iPad charger 2.1A also tried to use 1A iPhone charger in the process) while button steady press in pinhole reset for about 15 seconds and release.
f. From Laptop browser type 192.168.0.253 to come to access the recovery page of OC200 with 3 option menu, reboot, factory reset (default) and upgrade firmware.
g. I select factory reset and seen the controller rebooted with the blank page, not display. (Process again steps e and f for recovery page) I observe the oc200 doesn't factory reset since still shows the same recent firmware version with the latest build upgraded before it not totally lost in the network.
2. Downgrade / Upgrade Firmware from failed oc200 controller in the network.
a. From procedure 1 do the steps a up to f to come upon the recovery page.
b. First tried the downgrade by uploading the 4.2.8 Firmware and restart after the successful upgrade it reboots itself and pages no display.
c. Disconnect from local machine connection and connected it back to live network using the original PO Cable connected to my POE+ Switch TL-SG1008MP still not detected in-network and tried to manually add the device to account associating the device key which is 20 character key at the backside of your controller, display device is not available or offline.
d. I do as well the reset pinhole button while connected to network and still nothing happen I do check possibility of new mac device on live network but failed to see this. And performed once the default fallback address192.168.0.253 in browser while the oc200 is connected on poe switch live network still failed.
e. removed oc200 in live network and conenct it back to local pc setup with ethernet to lan port of machine Procedure 1 steps a-f).
f. I noticed the successful downgrade seem not happen while device performed the recovery sequence without the glitch or error message performing procedure 2 from a-
b. it's kind weird after downgrade its reboot itself without any noticed of failure in the profcess while expectation device successfully downgraded.
g. Do the factory reset from recovery page and restart boot again to recovery page surprising nothing reset still got the latest frimware in oc200 v4.2.11 (which failed to work operate and seen in live network from my initial upgrade before i performed this long procedural process)
h. Knowing now the oc200 can't downgrade of factory reset from the stage of recovery. I do the same upgrade of firmware which already loaded from the crashed to operate unit after first original upgrade of controller (before this long escalation trials performed).
i. I downloaded the latest firmware v4.2.11 from tplink twice procedure performed from the unit to ensure i do have a corrupted firmware in process. to make it short both seems usually upgraded in process since normal steps followed without any error appear in the process.
j. Connected back the OC200 in live network and add device key in the process and to the last attempt still failed to see the device in the network while there's a power led light up and blinking network (seems normal activity blink) in poe lan port.
Out of several trials of reset, hardreset, soft reset (recovery page), and recovery upgrade/factory rest. NON of them works for me. I already contacted the technical support of vendor and agreed to send it back the device for the warranty claim and they will replicate I believe the same process performed in recovery or might they have a magic tricks out of my procedure and steps performed to fix or might a total replacement.
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
Dear @JhonneL,
now i noticed every client in voucher authentication seem 8hrs back shows time first used of their activated voucher vs the actual time of controller/router and pc where i manage the local access remotely to oc200. where If i visit the Insights> pas portal authentication it shows the actual voucher time activation correct from all system in the network. Only the weird part is from hotspot manager start activation of voucher shows 8 hrs backward it's kind weird
Sorry that I didn't understand the problem, do you mean that the voucher time is incorrect?
It may be helpful if you could describe the problem with some screenshots.
Please feel free to tell your discovery and actual experience with your scenario here, glad to listen.
- Copy Link
- Report Inappropriate Content
@Fae Please find my screenshot presentation of big difference in time generated from omada controller during clien voucher activation. It seems hot spot manager page shows 8 hrs backward while the Insight page menu past portal authorization got the actual time activation synchorinize with OC200 / Router. Additional info this time diff is always happening every new voucher activation on system and now I'm confuse which one will be followed by controller as an expiration, is it the time validtiy in pas portal authentication which is most realtime or the 8rs hrs backward time of Hot Spot Manager? :)
and my remote laptop use to monitor the voucher system at home.
- Copy Link
- Report Inappropriate Content
Dear @JhonneL,
Please find my screenshot presentation of big difference in time generated from omada controller during clien voucher activation. It seems hot spot manager page shows 8 hrs backward while the Insight page menu past portal authorization got the actual time activation synchorinize with OC200 / Router. Additional info this time diff is always happening every new voucher activation on system and now I'm confuse which one will be followed by controller as an expiration, is it the time validtiy in pas portal authentication which is most realtime or the 8rs hrs backward time of Hot Spot Manager? :) and my remote laptop use to monitor the voucher system at home.
Thank you for your detailed information, it's very helpful.
Just to let you know that I've reported the problem to the R&D team who is investigating the problem.
One thing we can confirm is that the Created Time showing under the Vouchers tab is showing in a wrong way, the issue will be fixed in the subsequent updates. At present, please refer to the Authorized Clients tab or navigate to Insight > Passed Portal Authorization menu to check the time validity. Thank you!
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
@Fae / @R1D2 Hello just to update you after almost a month of waiting for the replacement of bricked OC200 after the release online update for OC200 v1 firmware 4.2.11 1.7.4 Build 20210118 Rel.72627 I received the warranty replacement from my vendor after technical discussion as well with the TP-Link Distributor support in my home country.
Remotely with my relative on-site, we manage to deploy the replacement OC200 v1 and make it online for 15 minutes :).
Base on the technical engineer I have spoken on my overseas call, most issues they received happen from failed firmware upgrade experience from their client for OC200, very seldom the hardware it a self fault in parts or component but most firmware bricked issue.
I hope my experienced and other community contributor and member here can address this concern to the development team to seek way on how to program and recover the operating system of OC200 since I tried several method from your shared sequence and procedure non of them fix the issue, where I understand from technical staff its more on firmware issue not component or IC level parts inside the unit.
Might develop a fail-safe recovery program for this controller for actual user DO IT Yourself procedure can recover it without much downtime on their existing network infrastructure deployment with OMADA Systems Deployment. I have short experience knowledge in CISCO switches and router configuration from their CI I seen more stable and well program their Cisco IOS (Internetwork Operating System). I hope TP-Link can develop not the same at least recovery industrial system for recovery of failed update firmware on the devices.
I'm looking forward you can advise and give feedback on my concern and suggestion.
Appreciate and Best Regards,
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 5523
Replies: 15
Voters 0
No one has voted for it yet.