Business Community > All Threads > The issues of ER605 V2.20 before joining to Omada Cloud Essentials and after joined
< All Threads

The issues of ER605 V2.20 before joining to Omada Cloud Essentials and after joined

The issues of ER605 V2.20 before joining to Omada Cloud Essentials and after joined

The issues of ER605 V2.20 before joining to Omada Cloud Essentials and after joined
The issues of ER605 V2.20 before joining to Omada Cloud Essentials and after joined
3 weeks ago - last edited 3 weeks ago
Tags: #DHCP Service #Controller Related
Model: ER605 (TL-R605)  
Hardware Version: V2
Firmware Version: 2.2.6 Build 20240718 Rel.82712

The issues of ER605 V2.20 before joining to Omada Cloud Essentials and after joined

 

Model : ER605

Firmware Version : 2.2.6 Build 20240718 Rel.82712

 

Before Joined to Omada Cloud Essentials

1. Booting Device, It's take very very long times more than 5-10 Minutes and didn't have any LED status blink. (This issue is a Critical Case because if ER605 lost the power or rebooting. The end devices has been boot completed but the Gateway still booting. That's mean end devices cannot get the IP Address)

2. Any WAN using the static IP but didn't assigned DNS IP, WAN status will offline.

 

After Joined to Omada Cloud Essentials

1. LAN Setting has been changed to default IP (192.168.0.1) but WAN Setting not back to default. That's mean all network devices has been down. Why LAN setting didn't sync to Cloud.

2. I cannot find the menu for Address Reservation on Gateway and also the Configuration of Address Reservation before joined cloud has been lost.

3. After forget ER605 on Cloud, It has been factory to default. That's mean any configuration has been done on cloud is lost. That's mean I need to start configuration again. (My suggestion, The WAN and LAN setting should be have the latest configuration. Any customer can factory reset by themselves.

 

If anyone know how to fix these issues please let me know and thank you for anyone suggestion.

  0      
 
  0      
 
#1
Options
2 Accepted Solutions
Re:The issues of ER605 V2.20 before joining to Omada Cloud Essentials and after joined-Solution
3 weeks ago - last edited 3 weeks ago

  @DukDig 

 

Hi,

 

As far as I know, any migration from Stand Alone management to OC200/300 or Software/Cloud management will restore all settings to default.

 

The only way you can do to "prevent" that, is to prepare the configuration in Controller tool in advance, and after it is done, Adopt the devices (routers, switches, APs).

I've done that 3 times already and that's how it is.

 

Keep in mind, that when you are setting up a Controller, it is asking you if you would like to Overwrite WAN (or leave as it is on device). This can save your local WAN configuration instead of overwriting it.

 

 

In terms of booting - as I worked with ER605, ER706 and ER707-m2 - all of those are booting really slow and can take up to 5min to get online. The ER605 is the slowest on since it's hardware is the poorest one.

 

Cheers :)

Recommended Solution
  1  
  1  
#2
Options
Re:The issues of ER605 V2.20 before joining to Omada Cloud Essentials and after joined-Solution
3 weeks ago - last edited 3 weeks ago

  @DukDig 

 

no, you cannot set a fixed IP on the client, there is not much you can do with cloud esseitial. if you need something more advanced go for Omada

 

 

Recommended Solution
  1  
  1  
#4
Options
3 Reply
Re:The issues of ER605 V2.20 before joining to Omada Cloud Essentials and after joined-Solution
3 weeks ago - last edited 3 weeks ago

  @DukDig 

 

Hi,

 

As far as I know, any migration from Stand Alone management to OC200/300 or Software/Cloud management will restore all settings to default.

 

The only way you can do to "prevent" that, is to prepare the configuration in Controller tool in advance, and after it is done, Adopt the devices (routers, switches, APs).

I've done that 3 times already and that's how it is.

 

Keep in mind, that when you are setting up a Controller, it is asking you if you would like to Overwrite WAN (or leave as it is on device). This can save your local WAN configuration instead of overwriting it.

 

 

In terms of booting - as I worked with ER605, ER706 and ER707-m2 - all of those are booting really slow and can take up to 5min to get online. The ER605 is the slowest on since it's hardware is the poorest one.

 

Cheers :)

Recommended Solution
  1  
  1  
#2
Options
Re:The issues of ER605 V2.20 before joining to Omada Cloud Essentials and after joined
3 weeks ago

  @RaRu 

 

Thank you for your reqly.

 

How about the DHCP Address Reservation on ER605? Is that possible to do it on Omada Cloud Essentials?

 

  0  
  0  
#3
Options
Re:The issues of ER605 V2.20 before joining to Omada Cloud Essentials and after joined-Solution
3 weeks ago - last edited 3 weeks ago

  @DukDig 

 

no, you cannot set a fixed IP on the client, there is not much you can do with cloud esseitial. if you need something more advanced go for Omada

 

 

Recommended Solution
  1  
  1  
#4
Options

Information

Helpful: 0

Views: 153

Replies: 3

Tags

DHCP Service Controller Related
Related Articles
Er605 V2.20 and Er605 V2.0 Firmware
1196 0
ER605 Configuration Issues
929 0
OMADA CONTROLLER - ADD THE ER605
139 0
ER605 v2 2.1.1 DHCP issues
1301 0
ER605 device add to omada cloud (without controller)
1136 0
is it possible to set up a second ER605 in Omada?
1754 0
About Us
Press
Copyright © TP-Link Systems Inc. All rights reserved.