ER605 no longer Adopter by OC200 after recent Firmware Update on OC200
After the recent OC200 (v1.0)
5.14.26.23 |
1.31.3 Build 20240620 Rel.80383 |
Update my ER605 is no longer adopted by the controler.
when looking at the OC200 i am presented with:
HOWEVER when connecting to the Routers IP i see:
Is anyone experiencing similar troubles at present?
Another interresting observation:
the DHCP Server seems to be running just fine, so is the DYNDS Service
My VPNs are however all unresponsive.
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
Such things unfortunately happen a little too often. there are very often problems when there is an update especially with routers.
but ok, I think your only option is to do a factory reset and readopt the router,
- Copy Link
- Report Inappropriate Content
@MR.S Thank you for your reply!
I have to unfortunately concur with you on the “little to often” part, especially in conjunction with the restrictive replacement policy I'll be tempted to start looking into alternatives if this will end up creating significant Downtime.
Regarding resetting the Router & Readopting:
The Site has a lot of incoming VPN Connections, some of which are older Open VPN Profiles, back I migrated the Site from a defective ER605 V1 to this V2 those were somehow bricked (I then assumed because of the different Hardware) will a Reset do the same?
- Copy Link
- Report Inappropriate Content
if you reset the router, you will not lose any configuration, but you must take a backup of the controller anyway, always take a backup :-)
reset the router with the reset button, then delete the router from the controller before adopting again, all the old settings will remain.
backup first :-)
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
hmm, that was weird. it shall not happen. I have re-adopted routers many times, very many times due to problems after updating, but everything has worked as it should afterwards. but I have used the Windows controller, there shouldn't be any difference.
- Copy Link
- Report Inappropriate Content
Thanks for posting in our business forum.
Would like to know what you did after the "firmware update".
Can you list a step note you took on your network after the firmware update? I would like to see each step you take to find out what might be the human error.
The controller log would be helpful as well if you could paste it along with your step note. Specifically targeting the time after the upgrade.
I think this problem should be posted on the controller page which seems to be a controller issue mainly. The router seems to be good to me.
And, you might try to reboot both of them to refresh the cache or any system error it might have. You know, it is not ECC memory on the devices. There might be errors after a long time it runs. Reboot would fix them sometimes.
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 380
Replies: 7
Voters 0
No one has voted for it yet.