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.
Hello,
This is a bit of a mess because I can't quite figure out how to configure the switch for Omada.
I followed the instructions from related forum posts:
TL-SX3008F First Time Omada Setup
and
Port speed settings when adopted to controller
Namely, the equipment set looks like this:
- ER605 router firmware ER605(UN)_V2_2.2.3 Build 20231201
- OC200 controller firmware OC200(UN)_V2_2.11.3 Build 20230906
- switch TL-SG2218 firmware TL-SG2218(UN)_V1_1.1.8 Build 20230602
- switch TL-SX3008F firmware TL-SX3008F(UN)_V1_1.0.5 Build 20230702
- AP EAP110
- AP EAP650-wall
Everything works, but I can't connect the TL-SX3008F to the controller correctly.
On the switch TL-SG2218 I manually set the speed to 1g and full duplex on ports 17 and 18 (SFP ports).
Configuring looks like this:
Connecting TL-SX3008F (SFP+ port) with TL-SG2218 (SFP port) using Ubiquiti DUACC-DAC-10G-0.5
Then, using the COM and Putty connection, I change the port settings from 10G to 1G, the switch gets the network and I can see it in Omada.
I do the adoption, the adoption continues, configuration takes place and Omada resets the switch so that all ports are on 10G again.
I can't change the port settings from the console because Omada blocks it.
I tested the firmware versions for the switch:
TL-SX3008F(UN)_V1_1.0.1 Build 20220623
TL-SX3008F_v1_Build 20210827(Beta)
TL-SX3008F(UN)_V1_1.0.4 Build 20230131
TL-SX3008F(UN)_V1_1.0.5 Build 20230702
In no case does the software autonegotiate the port speed in the switch TL-SX3008F
Now the question is, if I insert the TP-Link TL-SM331T module into the TL-SX3008F, will it finally be forced to work on a given port on 1G?
Do I need to play around with another JetStream switch that has its own 10G ports?
Or maybe someone has another idea and solution 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
Let's try this solution
After adoption:
After few minutes we got red status:
Changed port to 1G full duplex when its offline:
After reset from CLI we got this
It seems that after resetting it still loses everything :/
Quickly clicking through the settings right after clicking adopt and setting the port does not help.
Each time (I checked 3 times) after unsuccessfully sending the configuration to the switch by the controller, setting the port to 1G in offline mode, resetting the device to the initial state, setting its port to 1G in the controller, I have a new device to adopt.
Unless I don't see something that causes a device that is not fully configured to be remembered?
