Stack configuring my ER605 with Omada SDN

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
Stack configuring my ER605 with Omada SDN
Stack configuring my ER605 with Omada SDN
2021-03-15 19:20:57 - last edited 2021-03-16 07:35:25
Hardware Version: V1
Firmware Version: 1.0.1

Hello,

 

Please HELP

Just got my new ER605, changed the ip to be on my network subnet (10.0.0.220) and my Omada SDN imidiatley found it.
Run the ADOPT, it went trough adopting, than provisioning, that configuring and all the lithgs on the router went off.
It looks stack and Omada reports there is router with ip 192.168.0.1 ready to be adopted, but it fails if I try.

Omada versio- Software 4.2.11

 

 

Logs from Omada

 

"2021-03-16 08:35:23 [nioEventLoopGroup-9-5] [INFO]-[SourceFile:51] - success to send InitialSettingSync to 40-3F-8C-B2-61-2A
2021-03-16 08:38:12 [nioEventLoopGroup-5-1] [INFO]-[SourceFile:229] - 40-3F-8C-B2-61-2A reset to discovery status from CONNECTED, close old connection
2021-03-16 08:38:12 [discovery-handler-pool-0] [INFO]-[SourceFile:579] - Old connected device 40-3F-8C-B2-61-2A reconnect to controller
2021-03-16 08:39:23 [device-timeout-service-0] [WARN]-[SourceFile:94] - Adopting 40-3F-8C-B2-61-2A time out
2021-03-16 08:39:23 [net-event-handler-pool-9] [WARN]-[SourceFile:133] - adopt timeout for 40-3F-8C-B2-61-2A.
2021-03-16 08:40:02 [Thread-18] [INFO]-[SourceFile:146] - Close connection to service server.
2021-03-16 08:40:02 [Thread-92] [INFO]-[SourceFile:921] - Thread 'heartBeatThread' is stopped
2021-03-16 08:40:02 [Thread-91] [INFO]-[SourceFile:792] - expiredRequestCleanThread is interrupted.
2021-03-16 08:40:02 [Thread-91] [INFO]-[SourceFile:796] - Thread 'expiredRequestCleanThread' is stopped
2021-03-16 08:40:02 [Thread-90] [INFO]-[SourceFile:837] - javax.net.ssl.SSLException: Socket closed
javax.net.ssl.SSLException: Socket closed
        at sun.security.ssl.Alert.createSSLException(Alert.java:127) ~[?:1.8.0_282]
        at sun.security.ssl.TransportContext.fatal(TransportContext.java:324) ~[?:1.8.0_282]
        at sun.security.ssl.TransportContext.fatal(TransportContext.java:267) ~[?:1.8.0_282]
        at sun.security.ssl.TransportContext.fatal(TransportContext.java:262) ~[?:1.8.0_282]
        at sun.security.ssl.SSLSocketImpl.handleException(SSLSocketImpl.java:1303) ~[?:1.8.0_282]
        at sun.security.ssl.SSLSocketImpl.access$300(SSLSocketImpl.java:72) ~[?:1.8.0_282]
        at sun.security.ssl.SSLSocketImpl$AppInputStream.read(SSLSocketImpl.java:831) ~[?:1.8.0_282]
        at com.tplink.eap.cloudsdk.client.p.a(SourceFile:120) ~[cloudsdk-1.0.5.jar:?]
        at com.tplink.eap.cloudsdk.client.s.run(SourceFile:830) [cloudsdk-1.0.5.jar:?]
        at java.lang.Thread.run(Thread.java:748) [?:1.8.0_282]
Caused by: java.net.SocketException: Socket closed
        at java.net.SocketInputStream.socketRead0(Native Method) ~[?:1.8.0_282]
        at java.net.SocketInputStream.socketRead(SocketInputStream.java:116) ~[?:1.8.0_282]
        at java.net.SocketInputStream.read(SocketInputStream.java:171) ~[?:1.8.0_282]
        at java.net.SocketInputStream.read(SocketInputStream.java:141) ~[?:1.8.0_282]
        at sun.security.ssl.SSLSocketInputRecord.read(SSLSocketInputRecord.java:457) ~[?:1.8.0_282]
        at sun.security.ssl.SSLSocketInputRecord.bytesInCompletePacket(SSLSocketInputRecord.java:68) ~[?:1.8.0_282]
        at sun.security.ssl.SSLSocketImpl.readApplicationRecord(SSLSocketImpl.java:1095) ~[?:1.8.0_282]
        at sun.security.ssl.SSLSocketImpl.access$200(SSLSocketImpl.java:72) ~[?:1.8.0_282]
        at sun.security.ssl.SSLSocketImpl$AppInputStream.read(SSLSocketImpl.java:815) ~[?:1.8.0_282]
        ... 3 more
2021-03-16 08:40:02 [Thread-90] [INFO]-[SourceFile:839] - Thread 'recvThread' is stopped
2021-03-16 08:40:02 [Thread-18] [INFO]-[SourceFile:127] - Connect service server automatically, ConnectionType is PERSISTENT_CONNECTION.
2021-03-16 08:40:13 [Thread-18] [INFO]-[SourceFile:320] - Exception occurs when connecting service server:java.net.UnknownHostException: n-devs-smb.tplinkcloud.com: Temporary failure in name resolution
2021-03-16 08:40:43 [device-timeout-service-0] [WARN]-[SourceFile:94] - Adopting 40-3F-8C-B2-61-2A time out
2021-03-16 08:40:43 [net-event-handler-pool-4] [WARN]-[SourceFile:133] - adopt timeout for 40-3F-8C-B2-61-2A.
2021-03-16 08:42:03 [device-timeout-service-0] [WARN]-[SourceFile:94] - Adopting 40-3F-8C-B2-61-2A time out
2021-03-16 08:42:03 [net-event-handler-pool-10] [WARN]-[SourceFile:133] - adopt timeout for 40-3F-8C-B2-61-2A.
2021-03-16 08:42:26 [Thread-18] [INFO]-[SourceFile:320] - Exception occurs when connecting service server:java.net.UnknownHostException: n-devs-smb.tplinkcloud.com: Temporary failure in name resolution
2021-03-16 08:43:23 [device-timeout-service-0] [WARN]-[SourceFile:94] - Adopting 40-3F-8C-B2-61-2A time out
2021-03-16 08:43:23 [net-event-handler-pool-2] [WARN]-[SourceFile:133] - adopt timeout for 40-3F-8C-B2-61-2A.
2021-03-16 08:44:43 [device-timeout-service-0] [WARN]-[SourceFile:94] - Adopting 40-3F-8C-B2-61-2A time out
2021-03-16 08:44:43 [net-event-handler-pool-0] [WARN]-[SourceFile:133] - adopt timeout for 40-3F-8C-B2-61-2A.
2021-03-16 08:44:43 [net-event-handler-pool-0] [WARN]-[SourceFile:165] - Failed to auto adopt 40-3F-8C-B2-61-2A 5 times as timeout"

 

 

 

Unfortunately, I cannot see what is going on in the router, once addoption starts

0
0
#1
Options
1 Reply
Re:Stack configuring my ER605 with Omada SDN
2021-03-19 07:47:41

Dear @AlexKh,

 

Just got my new ER605, changed the ip to be on my network subnet (10.0.0.220) and my Omada SDN imidiatley found it.
Run the ADOPT, it went trough adopting, than provisioning, that configuring and all the lithgs on the router went off.
It looks stack and Omada reports there is router with ip 192.168.0.1 ready to be adopted, but it fails if I try.

 

Sorry for any trouble caused. Please refer to the guide below to adopt the ER605.

 

【FAQs Released】How to add an Omada Gateway to the network

New to the TP-Link Community? Getting Started from this thread: https://community.tp-link.com/en/business/forum/topic/551684
0
0
#2
Options