Hi, a cisco firewall SA 520 W restarted unexpected, it have firmware 2.1.18 version. what's the possible reason?
This equipment have several problems, web interface not loading several times too.
I have experienced the same issue but noticed mine from a change in the "Remote Log Identifier" that shows up in the outputted Sylogs via Kiwi Syslog
As you can see from the screenshot my "Remote Log Identifier" is set to SA527W
Sample output logs
Jan 13 23:56:47 SA527W
Jan 14 23:58:36 SA527W
Jan 15 23:58:52 SA527W
Jan 16 08:46:14 SA527W
All Appears ok
Then at 08:47:42 on 16-01-2011 last entry with SA527W as the identifier is seen.
The next entries at 08:51:38 show a change to Identifier in syslogs to TEAMF1
So it appears there has been almost a 5 minute reboot period.
The next set of syslog entries show a change in "Remote Log Identifier" and the system time / date has gone back to Jan 01 00:00:00
16-01-2011 08:51:30 Cron.Notice xx.xx.xx.xx crond: USER root pid 7260697 cmd /sbin/decodeSel.sh #Every 10 minutes, translate the latest IPMI SEL data
16-01-2011 08:51:38 Daemon.Debug xx.xx.xx.xx Jan 01 00:03:36 TeamF1 [System][PLATFORM] platformHandleDBUpdate:upnp op=18 row=1<000>
16-01-2011 08:51:38 Daemon.Debug xx.xx.xx.xx Jan 01 00:03:36 TeamF1 [System][PLATFORM] upnpMgmtDBUpdateHandler:DBUpdate event: Table: upnp opCode:18 rowId:1<000>
16-01-2011 08:51:38 Daemon.Debug xx.xx.xx.xx Jan 01 00:03:36 TeamF1 [System][PLATFORM] upnpMgmtTblHandler<000>
16-01-2011 08:51:38 Daemon.Error xx.xx.xx.xx Jan 01 00:03:37 TeamF1 [System][PLATFORM] IP: xx.xx.xx.xx <000>
16-01-2011 08:51:38 Daemon.Error xx.xx.xx.xx Jan 01 00:03:37 TeamF1 [System][PLATFORM] BCAST: xx.xx.xx.xx <000>
NTP update kicks in and sets the clock to the correct time
16-01-2011 08:56:15 User.Emerg xx.xx.xx.xx Jan 16 08:54:47 TeamF1 [Kernel] *******The above log repeated 1 times *******<000>
16-01-2011 08:56:15 Daemon.Info xx.xx.xx.xx Jan 16 08:54:47 TeamF1 [System][NTP] Synchronized time with 0.us.pool.ntp.org<000>
16-01-2011 08:56:15 Daemon.Info xx.xx.xx.xx Jan 16 08:54:47 TeamF1 [System][NTP] Current timezone is :GMT<000>
16-01-2011 08:56:15 Daemon.Info xx.xx.xx.xx Jan 16 08:54:47 TeamF1 [System][NTP] Date and Time Before Synchronization: Sat Jan 01 00:08:13 GMT 2000 <000>
16-01-2011 08:56:15 Daemon.Info xx.xx.xx.xx Jan 16 08:54:47 TeamF1 [System][NTP] Date and Time After Synchronization : Sun Jan 16 08:54:47 GMT 2011 <000>
System up time GUI interface indicates a reboot (see screenshot)
External Modem – shows no downtime in the last four days (see screenshot) up
So why was there an unexpected reboot, the firewall and external modem are both on a UPS so there has been no power loss?
Firmware 2.1.18 on the firewall.
I have the same problen, the router and switch is connected to the same UPS and both didn't restarted, that confirm that there is not a power failure. At this time and because the web interface are unstable my client is requesting to me a refund and he is plannig to put his old Dlink firewall to work
I take issue with generic comments whenever people say things are "very bad" and they fail to provide sound technical details of the problem. I suggest trying to be more specific when you describe a problem avoid generic statements like this. As a community of users we sometimes fail to recognize the power of our many voices.
As a collective we can make Cisco to fix problems by identifying the true root cause, or at least the reoccurance of specific errors by sharing them.
If your customers are unhappy I would get on the phone with Cisco support since your losses are ultimately their losses. Don't settle for the first tier of support if they give an unsatisfactory answer.
As a community we have a powerful voice if we accurately document issues. Identifying the root cause is beneficial to everyone, and it may help to actually improve software. Generic problem descriptions are useless and they provide ZERO benefit to the software developers that write the code fixes.
With that said, I clearly understand a customer complaining, so leverage that problem with support and make them help you make the customer happy. I am 100% positive Cisco does not want that customer using other gear.
NOTE: As for DLINK, I suspect the SA520 is a rebranded item but cannot prove it. I saw another DLINK model that look almost EXACTLY like the SA520W.
http://www.gdrc.org/decision/problem-solve.html - might be helpful to some
Did either of you open a support case?
I've been having similar issues with my SA520w...same firmware version. I've looked at the logs and can't seem to find anything that is causing the reboot. Has anyone spoken to tech support directly or solved this issue?
Please ugrade your box to the latest Release4, candidate 1.
Let me know if your issue is fixed.