T1600G-52TS stucks in "configuring" while adopting to Omada Controller

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.

T1600G-52TS stucks in "configuring" while adopting to Omada Controller

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
T1600G-52TS stucks in "configuring" while adopting to Omada Controller
T1600G-52TS stucks in "configuring" while adopting to Omada Controller
2023-01-03 20:28:53 - last edited 2023-01-03 21:05:56
Tags: #Omada
Hardware Version: V4
Firmware Version: 4.0.6

Hey guys,

 

I am using a T1600G-52TS with latest firmware, which is compatible with the Omada Controller. I used it multiple months without any problems in that combination. Some weeks ago I needed to restart my whole network devices and after that the switch wasn't readopting to the controller. It's now always stucking in the "configuring" state and switches to "disconnected" after some minutes.

 

Any ideas on how to fix or analyze this?

 

Edit: Controller is running as docker container on a local server (latest version). In complete there are 4 Omada Switches, a ER605 router and 5 access points (EAP245 and EAP 225 outdoor). Everything is up to date.

 

Thank you in advance

Konni

  0      
  0      
#1
Options
2 Reply
Re:T1600G-52TS stucks in "configuring" while adopting to Omada Controller
2023-01-03 21:33:02

I filtered the logs for lines containing the switch mac address. See the screenshot (logs cannot be inserted, log files cannot be attached).

File:
Screenshot 2023-01-03 223218.pngDownload
  0  
  0  
#2
Options
Re:T1600G-52TS stucks in "configuring" while adopting to Omada Controller
2023-01-04 05:47:43 - last edited 2023-01-04 05:51:52

  @Konni 

 

Have you tried to reset this T1600G before re-adopting?

 

Are you able to Ping or find the T1600G switch IP after adopting?

 

What I'm thinking: Although the switch shows disconnect on the controller, it may obtained another IP, and that IP is not able to communicate with the controller IP

  0  
  0  
#3
Options