SG2005P-PD not booting up properly

SG2005P-PD not booting up properly

SG2005P-PD not booting up properly
SG2005P-PD not booting up properly
Wednesday - last edited Thursday
Model: SG2005P-PD  
Hardware Version: V1
Firmware Version: 1.0.14

Hi,

 

I was performing regular maintenance and one thing was to upgrade the Firmware for SG2005P-PD. A new version was available (1.0.15). During the upgrade an unexpected loss of power occurred in my network (including PoE power for the SG2005P-PD).
After the power was restored, the SG2005P-PD failed to come up. Omada Controllor (OC200) showed it as disconnected. Multiple restarts and eventually resets, didn't help. The SG2005P-PD starts, but only the PoE Status LED is ON with an amber color. No other LED's are on.
I removed it from my Omada Controller and no new devices is found. I added it manually using the Device Key and now it stays in "Preconfigured" status. If I connect a PC to either of it's out ports, the PC has internet access. So it's strange that the SG2005P-PD itself is not getting it's configuration. I'd guess reseting the SG2005P-PD should allow me to access the WebUI, but no. I manually configured an IP for my PC to 192.168.0.10, but 192.168.0.254 is not responding. Using an IP scanner on the PC I discovered a 192.168.0.30, but that also didn't respond.
Have tried Force Provisioning, Custom Upgrade, none work.

Is there anything else for me to try or is this device bricked for good? It's not an old device and has been working in my network flawlessly for a bit over a year. 

Kind regards,
Alder

  0      
  0      
#1
Options
1 Accepted Solution
Re:SG2005P-PD not booting up properly-Solution
Thursday - last edited Thursday

  @aldets 

Thank you for your post. Please check whether the SYS LED is on. After a reset, if the switch cannot obtain an IP from the upstream DHCP server, its fallback IP will be 192.168.0.1.Please check whether you can still ping the switch’s IP address—use a PC directly connected to the switch for this test. If the switch responds to pings and you can log in, try to export its log file; note that any logs will be lost if you have already rebooted the device.
If you can access the CLI, please run the following commands to collect diagnostic information for us:
enable
debug show dump-info
Our official FAQ explains how to connect via SSH/Telnet—please refer to that document.Typical CLI Configuration Examples for TP-Link JetStream Switch
If none of the above steps work, the switch may have suffered a hardware failure. In that case, you can contact your retailer or our official support team to arrange a warranty replacemen

Recommended Solution
  0  
  0  
#2
Options
2 Reply
Re:SG2005P-PD not booting up properly-Solution
Thursday - last edited Thursday

  @aldets 

Thank you for your post. Please check whether the SYS LED is on. After a reset, if the switch cannot obtain an IP from the upstream DHCP server, its fallback IP will be 192.168.0.1.Please check whether you can still ping the switch’s IP address—use a PC directly connected to the switch for this test. If the switch responds to pings and you can log in, try to export its log file; note that any logs will be lost if you have already rebooted the device.
If you can access the CLI, please run the following commands to collect diagnostic information for us:
enable
debug show dump-info
Our official FAQ explains how to connect via SSH/Telnet—please refer to that document.Typical CLI Configuration Examples for TP-Link JetStream Switch
If none of the above steps work, the switch may have suffered a hardware failure. In that case, you can contact your retailer or our official support team to arrange a warranty replacemen

Recommended Solution
  0  
  0  
#2
Options
Re:SG2005P-PD not booting up properly
Thursday

  @Ethan-TP 

Hei,

 

The reset is not working, Only the PoE Status LED is ON with an amber color. No other LED's are on. Performing the reset has no effect, no LED blinking.

So the Switch won't fallback to the default IP of 192.168.0.1. 

I had a ES206GP v1.0 in my network which I isolated from the network, so that the devices would not be connected to any DHCP servers. Connected the switch to one of the PoE ports from the ES206GP, it got PoE power. Connected a PC to the switch SG2005P.

Situation is basicly the same, had to manually configure IP 192.168.0.10 to the PC and ran a host scan. Only 192.168.0.30 was detected which is the SG2005P. Confirmed it by using PING towards the IP and for a brief moment disconnected the cable between the PC and the SG2005P - PING was interrupted. Connected the cable and the PING resumed.

Also performed a nmap scan for open ports with the following result:


nmap -sS -p 1-1024 192.168.0.30
Starting Nmap 7.98 (  ) at 2025-11-19 15:43 +0200
Nmap scan report for 192.168.0.30
Host is up (0.00s latency).
All 1024 scanned ports on 192.168.0.30 are in ignored states.

 

PING against 192.168.0.1 had no response.

  0  
  0  
#3
Options