Business Community > Controllers > ER605 : Device Adoption Failed Because the Device does not Respond to Adopt Commands
< Controllers

ER605 : Device Adoption Failed Because the Device does not Respond to Adopt Commands

ER605 : Device Adoption Failed Because the Device does not Respond to Adopt Commands

ER605 : Device Adoption Failed Because the Device does not Respond to Adopt Commands
ER605 : Device Adoption Failed Because the Device does not Respond to Adopt Commands
Saturday
Tags: #Adoption
Model: ER605 (TL-R605)  
Hardware Version: V2
Firmware Version: 2.2.5

Hi everyone,

 

I've installed a whole omada setup at a house in the countryside : OC200, ER605, SG2210MP and 7 APs. After setting everything up I had an error adopting the ER605. I think it's a subnet problem but I am now offsite so my options are limited and I won't be back for a time and I was wondering if there was a way to solve this from a distance safely without rendering the site unreachable and forcing me to make the trip again just solve this issue.

 

I've got Starlink in Bypass mode on WAN1 and an old MR600 4G router on LAN2 of the ER605 and the idea was to set it up as WAN 2 after adoption of ER605 in the Omada Network. Main switch is plugged into LAN3 and OC200 on Port 1 of the main switch for PoE.  

 

Could the MR600 be the problem here ? Also when I go to LAN settings in my Site settings, on VLAN1 the DHCP Overide is set to manual so it feels that there maybe a conflict there as well with the ER605 

 

Thanks for your help.

  0      
 
  0      
 
#1
Options
2 Reply
Re:ER605 : Device Adoption Failed Because the Device does not Respond to Adopt Commands
Yesterday

Hi  @commandeurbrin 

 

Thanks for posting here.

 

What's the LAN IP address of the ER605? What's the IP address of the OC200?

By default, both ER605 and the MR600 use the same IP address, 192.168.0.1.

Connecting two DHCP servers with the same IP address to the same network may cause such an issue. It is recommended that you first remove the MR600, restart the ER605 and OC200, and try again. After successfully managing the ER605, set WAN/LAN2 as a WAN port, then change the LAN IP of the ER605 to a different subnet, such as 192.168.1.1. Once configured successfully, reconnect the MR600.

 

 

Wish you a happy life and smooth network usage!  >Omada US Enterprise Beta Program Launch< >Get the Latest Omada SDN Controller Releases Here< >Experience the Latest Omada EAP Firmware<
  0  
  0  
#2
Options
Re:ER605 : Device Adoption Failed Because the Device does not Respond to Adopt Commands
22 hours ago

@commandeurbrin

This will not solve your issue, but I recommend to power the OC200 controller via a dedicated PoE injector instead of a PoE-port on the switch that is managed by this controller. A switch reboots much faster than the OC200 controller which may result in adoption issues when it reboots. By having it on a dedicated PoE injector you don't have this issue that the controller reboots when the switch reboots.

ER707-M2, SG3218XP-M2, EAP772's & EAP245's
  0  
  0  
#3
Options

Information

Helpful: 0

Views: 60

Replies: 2

Tags

Adoption
About Us
Press
Copyright © TP-Link Systems Inc. All rights reserved.