Issues Regarding The Timed Log; Shutdown Delay In N3400 Systems When Critical Thresholds Are Crossed - IBM N Series Manual

The following timed options have no effect in Data ONTAP 8.0 or later:
v The timed.log option
v The timed.max_skew option
v The timed.min_skew option
v The timed.sched option
v The timed.window option
v The rtc and the rdate values of the timed.proto option
If you attempt to set the these options when the system is running Data
ONTAP 8.0 or later, they have no effect. However, these settings do take effect
if the system is reverted back to a release prior to Data ONTAP 8.0.

Issues regarding the timed log

Starting with Data ONTAP 8.0, the NTP daemon automatically adjusts the
storage system time to keep the system clock synchronized with the specified
NTP server. However, time adjustments made by the NTP daemon are not
logged even when the timed.log option is set to on.

Shutdown delay in N3400 systems when critical thresholds are crossed

In N3400 systems running Data ONTAP 8.0.1 and later releases in the 8.0.x
family, after a critical temperature or voltage threshold has been crossed, there
is a two-minute delay before the system shuts down. The purpose of the
delay is to provide enough time for AutoSupport messages to be delivered.
There is no shutdown delay if three or more fans fail.
If the system is running a heavy load or if the network is slow, the
AutoSupport message might not be delivered. However, EMS messages report
that thresholds have been crossed, regardless of whether an AutoSupport
message is delivered.
90
IBM System Storage N series: Data ONTAP 8.0.4 7-Mode Release Notes