Hello,
I’ve already consulted several posts on this forum regarding a similar issue, but I haven’t found a solution.
I’ve updated the firmware to version 2.0.2.14 and performed a factory reset afterward. Version 2.0.2.14 is the active image on the switch.
As mentioned in the release notes for this version, a bug causing random reboots was addressed.
Release Notes: CBS220 Firmware Version 2.0.2.14
Bug Fixed:
CSCwh29387 CBS 220 keeps rebooting after 1 - 2 weeks of uptime.
However, despite this firmware update, my switch still reboots approximately every 50 days, with a margin of a few hours.
This makes me think that the issue might not have been entirely resolved.
I have no power supply issues—everything is connected to an uninterruptible power supply (UPS). I’ve also switched power outlets to rule out any power-related problems, and only the switch exhibits this strange behavior.
I don’t understand why I can’t open a support case even though I purchased this switch brand new. Therefore, I’m posting here in the hope that someone from Cisco will notice this message.
The uptime is currently 48 days and 9 hours. I’m attaching the tech support file for reference.
What can I do to gather more information during the next reboot?
There are some weird things in the log file: When generating the tech support file, I noticed that it reports an uptime of 147 days, which is much higher than the 48 days displayed by the switch interface. The tech support file also contains a lot of Python exceptions.
To clarify, the switch operates perfectly except for these reboots, which are inconvenient because they abruptly shut down my PoE-powered Raspberry Pis.
Setup details:
- The switch is connected to a Netgate XG-7100 firewall.
- It’s used for video surveillance (6 cameras running 24/7).
- It also powers a Wi-Fi access point and a cluster of 4 Raspberry Pi 4s.
- There are a few VLANs configured, but nothing complicated.
- Both temperature and CPU levels are normal.
In the logs, I noticed a reboot instruction, leading me to believe the reboot is software-triggered rather than caused by a hardware issue. There’s nothing unusual right before the reboot log entry.
Any assistance in troubleshooting this issue would be greatly appreciated.
