The System clock on T3 and T4 Systems Will Jump Ahead 24hours Upon Cold Reset Following Leap Year Clock Adjustment

Asset ID:	1-77-1397124.1
Update Date:	2012-05-25
Keywords:

Solution Type Sun Alert Sure

Solution 1397124.1 : The System clock on T3 and T4 Systems Will Jump Ahead 24hours Upon Cold Reset Following Leap Year Clock Adjustment

Applies to:

Solaris SPARC Operating System - Version 10 10/09 U8 to 10 10/09 U8 [Release 10.0]
Netra SPARC T4-1 Server - Version Not Applicable to Not Applicable [Release N/A]
SPARC T3-1 - Version Not Applicable to Not Applicable [Release N/A]
SPARC T3-2 - Version Not Applicable to Not Applicable [Release N/A]
SPARC T3-4 - Version Not Applicable to Not Applicable [Release N/A]
Information in this document applies to any platform.
__________________

Date of Workaround Release: 19-Jan-2012

Date of Resolved Release: 04-May-2012
___________________________________

Description

The system clock on T3 and T4 systems that have been up since 2011 will jump ahead 24 hours upon the first cold reset (powered on, or power cycled).

Occurrence

This issue can occur on the following platforms:

SPARC Platform

SPARC T3-1 without patch 147315-05
SPARC T3-2 without patch 147316-05
SPARC T3-4 without patch 147317-05
SPARC T3-1B without patch 147318-04
Netra SPARC T3-1 without patch 147319-06
Netra SPARC T3-1B without patch 147320-03
Netra SPARC T3-1BA without patch 144609-07
SPARC T4-1 without patch 147284-03
SPARC T4-2 without patch 147285-03
SPARC T4-4 without patch 147286-04
SPARC T4-1B without patch 147287-03
Netra SPARC T4-1 without patch 147289-03
Netra SPARC T4-2 without patch 147290-03
Netra SPARC T4-1B without patch 147291-03
SPARC SuperCluster T4-4 without patch 147286-04

Notes:

1. This issue affects the above systems running all current system firmware versions.

2. The x86 Platform is not affected by this issue.

Symptoms

Should the described issue occur, the system clock will jump ahead 24 hours.

Workaround

If the described issue occurs, the date can be manually corrected using the Solaris date(1) command as root. It is highly recommended to boot the system to single-user mode when doing this to avoid any application conflicts resulting from the time jump.

Once the time is manually set, there are no time jumps on further resets (A/C power cycle, cold or warm reset). The time jump only occurs on the first reset in 2012 for systems with uptime since 2011.

Note 1: If the date has been manually corrected, it will need to be corrected again once the patch has been installed or upon first reset in 2013.

Note 2: If the date has been manually corrected, it will need to be corrected again if the SC has been reset to defaults. This will happen with "set /SP reset_to_defaults=all" or through not preserving the configuration during a firmware upgrade.

NTP, if configured, will automatically correct the clock by setting the time through ntpdate(1M). However, if ntpdate is unable to access the time source the offset will be greater than 1000 seconds resulting in xntpd(1M) terminating:

    Jan 2 00:04:00 T3-1-host xntpd[557]: time error -86344.729079 is way too large (set clock manually)


   Jan 2 00:04:00 T3-1-host svc.startd[7]: network/ntp:default transitioned to maintenance by request (see 'svcs -xv' for details)


   Jan 2 00:04:00 T3-1-host xntpd[557]: xntpd exiting on signal 15

Note 3: If the date was manually adjusted, after applying the fix, the date will jump back 24 hours and the time will have to be manually adjusted again.

This issue is addressed by Sun System Firmware 8.1.4.e on the following platforms:

SPARC Platform

SPARC T3-1 with patch 147315-05 or later
SPARC T3-2 with patch 147316-05 or later
SPARC T3-4 with patch 147317-05 or later
SPARC T3-1B with patch 147318-04 or later
Netra SPARC T3-1 with patch 147319-06 or later
Netra SPARC T3-1B with patch 147320-03 or later
Netra SPARC T3-1BA with patch 144609-07 or later
SPARC T4-1 with patch 147284-03 or later
SPARC T4-2 with patch 147285-03 or later
SPARC T4-4 with patch 147286-04 or later
SPARC T4-1B with patch 147287-03 or later
Netra SPARC T4-1 with patch 147289-03 or later
Netra SPARC T4-2 with patch 147290-03 or later
Netra SPARC T4-1B with patch 147291-03 or later
SPARC SuperCluster T4-4 with patch 147286-04 or later

Patches

<SUNPATCH:147315-05>
<SUNPATCH:147316-05>
<SUNPATCH:147317-05>
<SUNPATCH:147318-04>
<SUNPATCH:147319-06>
<SUNPATCH:147320-03>
<SUNPATCH:147284-03>
<SUNPATCH:147285-03>
<SUNPATCH:147286-04>
<SUNPATCH:147287-03>
<SUNPATCH:147289-03>
<SUNPATCH:147291-03>
<SUNPATCH:144609-07>

<SUNPATCH:147290-03>

History

19-Jan-2012: Document released
20-Jan-2012: Updated Product field and Workaround section.
21-Jan-2012: Updated Workaround section.
24-Jan-2012: Updated Workaround for additional instructions - boot to single-user mode
17-Feb-2012: Updated Occurrence and Workaround sections.
02-Mar-2012:Updated Occurrence and Workaround sections.

04-May-2012: Updated Occurrence and Workaround sections. Resolved.

25-May-2012: Updated Alert Title.

Internal Section: Comments:

This issue was introduced with the firmware support for T3 platforms. All SysFw8.x releases have the issue.
Patches might be available before the end of Feb.

Note: This Sun Alert will only be resolved when a patch for each of the hardware platforms is released. Each system requires a separate patch.

Please send technical questions to the following email:
[email protected]
and copy the Responsible Engineer/Contributor listed below:

Internal Contributor/Submitter: [email protected]
Internal Eng Responsible Engineer: [email protected]
Oracle Knowledge Analyst: [email protected]
Internal Eng Business Unit Group: Systems RPE
Internal Escalation ID: 3-5147776431
Internal Pending Patches:147290-03
Internal Resolution Patches:147315-05, 147316-05, 147317-05, 147318-04, 147319-06, 147320-03, 147284-03, 147285-03, 147286-04, 147287-03, 147289-03, 147291-03, 144609-07

Attachments

This solution has no attachment