Last updated on DECEMBER 01, 2016
Applies to:Oracle FS1-2 Flash Storage System - Version All Versions to All Versions [Release All Releases]
Information in this document applies to any platform.
If the timezone in the FS1 Pilot is set to anything but UTC, the time stamps for events, alerts, and log collections in both the GUI and the system logs will vary depending on which software component in the system generates the event or the log collection. The amount of time variation will depend on the difference between UTC and the configured timezone. This can result in Events appearing out of order in the Event Log and screen, Alerts appearing out of order, and log collection timestamps and file names being out of order.
Later log collections such as manual logs may appear to have been taken hours before or after an event driven log collection that they are related to. Event driven log collection times may appear out of sequence depending on whether the initiating event comes from a Controller or the Pilot software. A typical symptom is that times in the Event Log will be outside the boundaries of the log collection file name.
For example a log collection AK00999999-151119221311-151119223713-COLD_START_FAILED-e-02-02.tar which begins at 2015-Nov-19-22:13:11 and ends at 2015-Nov-19-22:37:13 may have event time stamps that occur before or after those boundaries. This makes problem determination extremely difficult as the times for system events and log collections cannot be used to determine a sequence of issues and recoveries without checking for operating system times in log filenames and reorganizing all logs to provide the correct sequence.
On the Pilot shell, a date command must indicate that the time is in UTC. If it does not, the timezone is wrong and must be corrected.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms