GS1920 Switch not booting correctly

MarioR

Hello,

my GS1920-24HPv2 stopped working on x-mas….
Everything seemed to work until 12.00 am, then everything went offline. I checked the switch and pwr/sys were green. Cloud was blinking amber. I was a bit confused because I had disabled the Cloud Feature as I am not using it. So i rebooted the switch to see if it works after a reboot. The reboot made it even worse - Pwr green, sys blinking - nothing more. Switch doesn't boot. So I left it there alone.

After a few hours I came back and the switch showed the same combination of lights as before, so I tried to login to the gui. Everything looked good on the dashboard, so I tried to "erase running-config". Thought it might have lost it's config somehow…

After the reboot the same things happen again. I can only log in to gui after waiting for about 30min. Searched the forums and connected the serial cable to flash the firmware again. This wasn't working on first try, so I kept going. The firmware flash succeeded (.bin and .rom), so I tried rebooting again. No luck… Again stuck in boot process.

If I leave it like this, I can log in to the gui after some time. Still connected to the console, I can see the following lines at boot.
Copyright (c) 2023 Zyxel and/or its affiliates. All Rights Reserved.
initialize switch, ethernet address: bc:99:11:c9:9c:05
Initializing MSTP.............
Initializing VLAN Database...
Initializing IP Interface...
Initializing Advanced Applications...
Initializing Command Line Interface...
Initializing Web Interface...
81173f30: bcmPoePowerManagementModeSet(1107) ret=-3
81173f30: bcmPoePowerManagementModeSet(1107) ret=-3
PwrDepInit(646) error
81173f30: bcmPoePowerManagementModeSet(1107) ret=-3
81172828: bcmPoePortCommandAll(902) ret=-3
81172828: bcmPoePortCommandAll(902) ret=-3
81172828: bcmPoePortCommandAll(902) ret=-3
81172828: bcmPoePortCommandAll(902) ret=-3
81172828: bcmPoePortCommandAll(902) ret=-3
81172828: bcmPoePortCommandAll(902) ret=-3
81168e80: bcmPoePortCommandAll(902) ret=-3
81168e80: bcmPoePortCommandAll(902) ret=-3
81168e80: bcmPoePortCommandAll(902) ret=-3
81168e80: bcmPoePortCommandAll(902) ret=-3
81168e80: bcmPoePortCommandAll(902) ret=-3
81168e80: bcmPoePortCommandAll(902) ret=-3
bcmPoePowerSourceSet total=390 ret=-3, ack=1
28 e0 00 01 01 01 02 01-03 01 ff 11 (...........
00 00 00 00 86 66 a0 30-80 c0 41 dc .....f.0..A.

I collected the tech-support files from the gui in case I need them.

The switch boots from config image 2, nr.1 shows a checksum error:
Bootbase Version: V1.00 | 04/12/2018 10:50:50
DRAM calibration...PASSED
RAM: Size = 262144 Kbytes
DRAM POST: Testing: 262144K
OK
DRAM Test SUCCESS !
FLASH: 32M
check sum error! len = 5656640 checksum = 05dc calculated = 6303
change boot image to 2


There were about 15 devices (Dell Poweredge, connected before, 6 ot them POE (2x Zyxel Accesspoint, 2N IP Verso doorbell, 3x Reolink cameras). The switch never complaint about power-draw and everything worked for about 15 months. I did no changes to the config before it stopped working.

Any help would be appreciated. Whats wrong with it?

Zyxel_Kay

Hi @MarioR

Thank you for providing such a detailed description and the console logs.

The repeated PoE errors in your console log (bcmPoePowerManagementModeSet and PwrDepInit errors) indicate a hardware issue with the switch's PoE modules. Since you've already tried firmware reflash and configuration reset without success, this will require an RMA.

To initiate the RMA process:

• For the EMEA region, follow the guidelines to check the device warranty and submit an RMA.
  Submit an EMEA RMA request
• For the US region, use the link below to submit an RMA request.
  Submit a US RMA request

Please include your console logs and tech-support files with the RMA request.

====Update====

Have you had a console cable connected continuously during switch operation? In our experience, certain console cable connections can sometimes interfere with the switch's boot sequence. If you had a console cable connected when the issue first occurred, try disconnecting it and rebooting the switch to rule out any cable-related issues.