Time of Day TOD handling on V1280, N1280, E2900, and N1290 systems

Asset ID:	1-79-2054135.1
Update Date:	2015-09-28
Keywords:

Solution Type Predictive Self-Healing Sure

Solution 2054135.1 : Time of Day TOD handling on V1280, N1280, E2900, and N1290 systems

Applies to:

Sun Fire V1280 Server - Version All Versions and later
Sun Netra 1280 Server - Version All Versions and later
Sun Fire E2900 Server - Version All Versions and later
Sun Netra 1290 Server - Version All Versions and later
Information in this document applies to any platform.

Purpose

This document describes the interaction between Solaris and LOM Time of Day (TOD) clocks.

Details

Initially, Solaris gets its time from the TOD of the LOM.

If Solaris is set up as an NTP client of one or more NTP servers, the Solaris time will be slewed until it matches the time from the NTP server. If the time difference is large, Solaris time will be stepped rather than slewed. Then the Solaris time will be automatically fed back to the LOM and the LOM will reset its time.

Note that time here means the 32 bit value representing the number of seconds since the epoch. For unix systems, the epoch is January 1st, 1970 at UTC. Solaris and the LOM maintain their own unique timezone settings to provide local time.

If Solaris is not st up as an NTP client, it will retain the time it started with from the LOM TOD. Any changes to the Solaris TOD will be reflected in the LOM TOD.

References:

Serengeti clock: Sun Fire[TM] 3800, 4800, 4810, 6800, E4900, E6900: How do the clocks work? (Doc ID 1004720.1)
Known TOD issue on Serengeti and LW8: On Sun Fire 3800/4800/4810/6800, V1280, and Netra 1280 Domains, Time of Day (TOD) May Drift or Jump (Doc ID 1000616.1)

Attachments

This solution has no attachment