NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Reboot events in logs?
Does the switch log all reboots after either a soft reboot or a hard reboot? Over the last week, the switch was rebooted several times and power was removed a couple times. However, I see only one ...
I verified and it's working as designed:
For time storing, it is normal if we don’t write synced time to a persistent storage. For such system, usually it will boot up with date 1970 (Jan 1st) and sync to the current time after software is brought up fully.
Default should be OK, the severity is:
- Behavior: Wrap
- Severity filter: Notice
If you don't anything since October, it would mean "no reboot since then"
Just thought of something. The switch defaults to SNTP for time. You've been working with us offline about issues with our Management VLAN not being connected (only OOB). If the Management VLAN isn't connected, I'm assuming SNTP wouldn't have worked over OOB. Might that explain the issue? I see many logging statements from Jan 1 (assuming these are logs before SNTP was connected)?
Management VLAN has been up for a couple of days and the SNTP time currently is accurate.
Also, should I be looking at the memory log? Does this equate to the log in the AV UI?
I rebooted again, I see a bunch of log messages from Jan 1, then a cold start message on Oct 31 and then finally two SSL cert logging statements with the correct date/time (I'm assuming this is when the unit was able to sync w/SNTP).
It appears like the local time is logged incorrectly until the unit reboots. Do I need to manually set the system time and then switch back to SNTP to prevent this?
I see in your log lots of Jan 1 times also.To close on this (any other questions, please email ProAVDesign@netgear.com) and one of the SEs will schedule a call with you to address any other concern! We're here to support you.
- If there is internet on the OOB side, then the time is synchronized with NTP too from there (all my switches in my lab are managed through OOB, and they all sync to the right time with OOB right)
- When there is a reboot, during the boot there is no time sync yet, the switch lost his time. That's why you see Jan 1st until all services are up, eventually the correct time comes back again when NTP was reached
- If you set up a time manually, I don't think it would change anything as during the first 60 seconds of the boot, there is no time yet anyway, either
- On the other hand, ignoring the Jan 1st you know that logs are coming "incremental", so any log entry with Jan 1st would also indicate a reboot somehow in the history of logs
- The show logging (logs entries in Engage or in AV UI\Maintenance or IT GUI Monitoring) is the same as Memory log (just the presentation is different) - Traps are reflecting the logs too - the severity is the same too
NETGEAR Academy
Master AV-over-IP networking, multicast protocols, and troubleshooting to confidently deploy and manage AV networks.
Join Us!
