This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.Port speed in TL-SX3008F settings when adopted to controller
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
I uploaded the beta version of the software to OC200
Currently, my situation is that the controller is trying to readopt the device
But we have a new problem 
The SX3008F switch requires a password, and in the case of automatic adoption, we do not have a login and password window, unless it can be disabled somewhere in the CLI or web switch?
Ok, it worked.
The solution was quite strange.
I used everything I found and what you told me.
In fact, the beta version of the controller software managed to remember the device.
But, the automatic login remembered by the controller did not work and he kept trying to connect but could not log in.
The solution was to disconnect the SFP cable from the switch to force the controller to display the reconnect button, click it, enter the password, connect the SFP again and confirm OK in the controller window.
And this is how the switch was correctly adapted to the controller.
I think I will write a long instruction on how to deal with it 
Solution
A solution to the problem for everyone who may have a similar problem to me.
Devices:
- OC200 v1 controller with firmware 5.12.9 or lower
- any 1G switch with SFP
- any 10G switch with SFP+ (this will probably happen on others)
What you need:
USB/RJ45 COM cable to connect to the CLI of the 10G switch
Steps:
- Connect to our 10G switch via CLI
- Set a new password for admin
- We follow the instructions:
- Type "enable" without the quotes, hit enter,
- Type "configure" without quotes, hit enter,
- Type "interface ten-gigabitEthernet 1/0/1" without quotes, hit enter
- Type "speed 1000" without quotes, hit enter
- Type "end" without quotes, hit enter
- Type "copy running-config startup-config", hit enter.
- Now we have access via the 1G port to the web for our switch
- Log in to our OC200 and see that the device has appeared and check the software version. If it is 5.12.9, we need to manually upload the beta version: https://community.tp-link.com/en/business/forum/topic/628384
- Log in to our 10G switch and upgrade the version of our switch to the latest version available manually via the web
- We adapt the switch in the controller. Most likely, if there is no good update, the current standard situation will occur along the way. This means that adaptation will begin and during it the controller will reset the port settings of our 10G switch to standard settings and at the same time block the possibility of changing them using the CLI
- Now, when it crashes, wait for the disconnected status in the devices tab.
- Go to our 10G switch --> configuration -> general -> if we already have a beta version of our software for the controller, in the first tab at the very end we have a checkbox with "Remembered device:" and we select it and save it
- We enter the port settings and manually set the connection speed to 1000 full duplex for our SFP+ port
- Now the gymnastics - enter the Switch 10G via CLI and reset it, thanks to the latest software we have immediate access to it, you do not need to enter any bootmen
- Repeat steps 2-9
- Refresh the list of devices in the Omada controller
- The controller gets dizzy when trying to adopt again - there are lots of logs that it cannot automatically connect
- Unplug the SFP or SFP+ cable from one of the switches - we must lose the connection, thanks to which Omada will display a window for logging in to this Switch
- Enter our login details from point 19.1 and do not click anything
- Connect the SFP/SFP+ cable and click OK from point 21
- After this long fight, we are happy with the switch connected to our Omada system
