ER605 V2.0 Adoption to Azure hosted Cloud

ER605 V2.0 Adoption to Azure hosted Cloud
ER605 V2.0 Adoption to Azure hosted Cloud
2022-06-24 17:17:01
Model: ER605 (TL-R605)  
Hardware Version: V2
Firmware Version: Build 20220223 Rel.68551

Frustrating!

We set this up before taking it to the customer and yes this was a bit of a pain to adopt but eventually it did.. 

 

Took this to the customers site after having to reset and now this will not (after following everying) adopt in a Cloud controler that is hosted in Azure.. All the Switches and AP have come online but not the gateway

 

Originally logged in with the 192.168.0.1 address and registered to the cloud portal so that it appeared and clicking adopt... It failed

Then set the IP address on the 192.168.2.x range which the rest of the network is .. clicked adopt... failed

 

Looked through the logs on the controller and really vague.. 

 

All I get is 

timeout-pool-0] [] c.t.s.o.m.d.d.m.a.a(175): timeout wait adopt watch result of OmadacId(fc02b8e93074478f4fd4b56e59447085) DeviceMac() BusinessId(topic=smb_omada_business_fe6e7a70-bbe4-4edb-ace9-2743d17b0b3a, id=45613377-92e2-4f40-b257-2eafcfb25f2c), response:OperationResponse(errorCode=-39002, msg=Device adoption failed because the device does not respond to adopt commands., result=AdoptOneDeviceStatusResult(mac=, status=22, statusCategory=2))

 

Any thoughts

  0      
  0      
#1
Options
4 Reply
Re:ER605 V2.0 Adoption to Azure hosted Cloud
2022-06-24 19:23:39

  @Safetnet did you open required ports on customer's network?

  0  
  0  
#2
Options
Re:ER605 V2.0 Adoption to Azure hosted Cloud
2022-06-24 19:29:41

  @btx Hi

 

The ports are open on the Azure VM... and this worked when testing prior to going onsite... 

 

The gateway is the firewall and shouldn't need ports open ... ?

 

The Switch has registered OK and so has the AP to the controller

 

 

 

  0  
  0  
#3
Options
Re:ER605 V2.0 Adoption to Azure hosted Cloud
2022-06-24 20:28:32 - last edited 2022-06-24 20:31:00

  @Safetnet according to log it says, failed because the device does not respond to adopt commands. I would assume that controller can not reach the gateway for some reason, if it is managed by omada, I assume you already tried resetting and readapting, but ensure first that controller can communicate with the gateway.

 

Can you write which cloud controller version is in use?

  0  
  0  
#4
Options
Re:ER605 V2.0 Adoption to Azure hosted Cloud
2022-06-25 09:35:00

  @btx

 

This was originally setup before taking to site but was removed as the connection details we different, which reset the device.

 

The controller has ports 29811-29814 TCP and 29810 UDP and is running version 5.3.1...

 

 The gateway appears in the controller waiting to adopt OK... just wished that there was more info in the logs..

 

Thanks

  1  
  1  
#5
Options