01-25-2018 12:36 AM - edited 03-08-2019 07:43 PM
Hi,
We had an unexpected restart in WSA. We check the system logs and we only see the RAID sync event, nothing about the cause for this restart. how can we get the root cause???
22 Jan 2018 13:52:04 (GMT +0100) Info: Begin Logfile 22 Jan 2018 13:52:04 (GMT +0100) Info: Version: 10.5.0-358 22 Jan 2018 13:52:04 (GMT +0100) Info: Time offset from UTC: 3600 seconds 22 Jan 2018 13:52:04 (GMT +0100) Info: System is coming up. 22 Jan 2018 13:52:10 (GMT +0100) Warning: The following update to the interface failed: setfib -1 route -n add default Reason: route: writing to routing socket: Invalid argument add net default fib 1: Invalid argument 22 Jan 2018 13:52:13 (GMT +0100) Warning: The following update to the interface failed: setfib -1 route -n add default Reason: route: writing to routing socket: Invalid argument add net default fib 1: Invalid argument 22 Jan 2018 13:53:04 (GMT +0100) Warning: A RAID-event has occurred: RAID states changed from "OPTIMAL" to "SUBOPTIMAL" 22 Jan 2018 13:53:05 (GMT +0100) Info: Internal SMTP system attempting to send a message to xxxxxxx with subject 'Warning <Hardware> ironportweb.xxxxxxxxx: RAID ALERT: RAID states changed from "OPTIMAL" to "SUBOPTIMAL"' (attempt #0).
REgards
02-05-2018 12:52 AM
Where in WSA can see the logs about a unexpected restart or corefile??????
This device ha reboot twice with no reason.
02-05-2018 01:01 AM
02 Feb 2018 01:01:10 (GMT +0100) Info: Internal SMTP system successfully sent a message to ccsadmin@consorseguros.es with subject 'Cisco Report: Dayly summary(ironportweb.xxx.xxx)'.
04 Feb 2018 12:54:28 (GMT +0100) Info: Begin Logfile
04 Feb 2018 12:54:28 (GMT +0100) Info: Version: 10.5.0-358 SN: 1xxxxxxxx-xxxxxxxx 04 Feb 2018 12:54:28 (GMT +0100) Info: Time offset from UTC: 3600 seconds 04 Feb 2018 12:54:27 (GMT +0100) Info: System is coming up. 04 Feb 2018 12:54:34 (GMT +0100) Warning: The following update to the interface failed: setfib -1 route -n add default Reason: route: writing to routing socket: Invalid argument add net default fib 1: Invalid argument 04 Feb 2018 12:54:36 (GMT +0100) Warning: The following update to the interface failed: setfib -1 route -n add default Reason: route: writing to routing socket: Invalid argument add net default fib 1: Invalid argument 04 Feb 2018 12:55:28 (GMT +0100) Warning: A RAID-event has occurred: RAID states changed from "OPTIMAL" to "SUBOPTIMAL"
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