I managed to bork a SG350-10P and running Release 2.5.5.47. It was fine running Release 2.5.0.92 and when I upgraded it to 2.5.5.47, it went into a reboot loop. I consoled into the switch to tell it load 2.5.0.92, but was unsuccessful. I also reload 2.5.0.92 via Xmodem download and it was also unsuccessful.
I get this message "%HAL_config_poe-F-POEInitError: HALP_config_poe_692xx_check_master_reset: HALP_config_poe_number_of_poe_devices is Zero. Failed on init."
-----------------------------------
-- Unit Number 1 Master Enabled --
-----------------------------------
26-Nov-2019 01:27:33 %Entity-I-SEND-ENT-CONF-CHANGE-TRAP: entity configuration change trap.
26-Nov-2019 01:27:34 %MLDP-I-MASTER: Switching to the Master Mode.
26-Nov-2019 01:27:37 %SNMP-I-CDBITEMSNUM: Number of running configuration items loaded: 0
26-Nov-2019 01:27:37 %SNMP-I-CDBITEMSNUM: Number of startup configuration items loaded: 0
The SSH Server is generating a default RSA key.
This may take a few minutes, depending on the key size.
26-Nov-2019 01:27:38 %HAL_config_poe-F-POEInitError: HALP_config_poe_692xx_check_master_reset: HALP_config_poe_number_of_poe_devices is Zero. Failed on init.
***** FATAL ERROR *****
Reporting Task: HCPT.
Software Version: 2.5.0.92 (date Nov 26 2019 time 13:25:31)
base_address=0xb46c3000
ros(+0x78aed8)[0xb4e4ded8]
ros(HOSTG_fatal_error+0x10)[0xb4e504dc]
ros(OSSYSG_fatal_error+0x2a0)[0xb541b854]
ros(+0xb5a320)[0xb521d320]
ros(HALP_config_poe_692xx_dev_op_set_periodic+0xa80)[0xb57d4004]
ros(+0x1101a98)[0xb57c4a98]
ros(HALP_config_poe_691xx_692xx_poe_dev_operation+0x3c)[0xb57c4b78]
ros(HALC_config_poe_dev_operation+0x44)[0xb57d7a40]
ros(+0x10b1bd8)[0xb5774bd8]
ros(HALC_config_device_dispatch+0x1a8)[0xb5775b58]
ros(+0x10cf208)[0xb5792208]
ros(+0x10cf418)[0xb5792418]
ros(+0x10cf4a0)[0xb57924a0]
/lib/libp2linux.so.1(task_run+0xf4)[0xb4653818]
***** END OF FATAL ERROR *****
**************************************************
***************** SYSTEM RESET *****************
**************************************************
Restarting system.
This bug is documented here -
The workaround is RMA
Is this covered under under the Cisco Small Business Product Limited Hardware Warranty Terms?
If so, how does one file a claim?
Thanks
Dan
