01-28-2025 08:24 AM
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:
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.
01-28-2025 08:46 AM
- I would advise to configure a syslog server on the device to send all logs too, then when it reboots examine the last logs which could be send, sometimes this could provide insights (too) ,
M.
01-28-2025 02:06 PM
Syslog server is up. Update here in a few hours.
01-30-2025 12:30 AM
So, uptime restarted to zero but no REBOOT is visible in the logs.
As jason-g said in this thread:
https://community.cisco.com/t5/switches-small-business/cbs220-random-periodic-crash-and-or-reboot/td-p/5217491
It seems to be an error in the uptime display, as I have an uptime of zero day today, but tech support now displays 150 days. I used to lose connection and poe power when uptime dropped to zero before using the latest firmware but apparently the problem is fixed now.
So it would be nice to fix this display bug so it's perfect.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide