SG2008P disconnects from omada controller
Yesterday i updated my switch through omada controller to firmware 3.20.10, and since then, every 12~14 hours, the switch disconnects from my oc200, pings dont work, access thorugh the web interface also dont work, i had to disconnect and reconnect from the power to be able to reconnect, but with this i bring all my wlan network down because my ap's are connected to the poe ports, anyone with the same problem?
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
Thank you for your post. Could you please let me know:
- The hardware and software versions of your OC200, and whether they are running the latest firmware.
- The LED status on the switch when the issue occurs—for example, are the port LEDs and SYS LED lit normally?
- What devices are connected to the switch, and what does your network topology look like?
After the switch goes offline, do not restart it. Instead, access the switch CLI via console or SSH and collect the following information for us to analyze the cause of the disconnection:
show logging buffer
show running-config
This article provides guidance—please refer to it.Typical CLI Configuration Examples for TP-Link JetStream Switch
- Copy Link
- Report Inappropriate Content
@Ethan-TP
hi, this is the info you asked for
Model OC200 1.0 Firmware Version 1.36.7 Build 20250707 Rel.72474, its the last firmware version
the leds are normal, all blink the same as before
my topology is this
port 1, AP 620HD poe
port 2, OC200 poe
port 3, AP EAP245 poe
port 4, trunk port to proxmox
port 5, free
port 6, TL-SG1016 to my network
port 7, free
port 8, WAN hAP ac^2
my topology is normal, internet comes through port 8, 4vlans, 1 lan, 10 iot, 20 guest and 30 servers,
i can't log to my switch, ping, unless i power cycle the unit, all my lan, vlans, poe works but the switch its inaccesible, it doesnt show on my network
all started when i updated the switch to the latest firmware, 3.20.10, befora that i had like 2 years without any issues, updated firmware on all my equipment over time
- Copy Link
- Report Inappropriate Content
Besides the three items above, gathering CLI output while the issue is reproducible is critical for our analysis—please provide it.
When the problem occurs, access the device via SSH or console and collect the following:
show running-config
show logging buffer
show cpu-utilization
show memory-utilization
show system-time
show system-time ntp
debug show ecs log
debug show ecs controller-conf
debug show ecs set-cfg 1
debug show ecs set-cfg 2
debug show ecs set-cfg 3
debug show ecs set-cfg 4
debug show ecs set-cfg 5
You can also try pinging the Controller IP.
- Copy Link
- Report Inappropriate Content
@Ethan-TP
like i said, i cannot log to the router, it doesnt respond to pings, no ssh, no telnet, nothing, like it doesnt exists, but the communication are there, vlans works, lan works, just cant ping or log into, until i power cycle the unit
- Copy Link
- Report Inappropriate Content
It appears the switch has gone down. After rebooting the device, please run the CLI command show dump info and send us the output for analysis. Also, could you tell us the hardware and firmware version of your OC200?
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 442
Replies: 5
Voters 0
No one has voted for it yet.