Sun ZFS Storage 7420
 
Oracle ZFS Storage ZS5-2
 
Oracle ZFS Storage ZS3-2
 
Sun Storage 7110 Unified Storage System
 
Oracle ZFS Storage ZS4-4
 
Sun Storage 7210 Unified Storage System
 
Oracle ZFS Storage ZS5-4
 
Sun Storage 7410 Unified Storage System
 
Oracle ZFS Storage ZS3-4
 
Sun ZFS Storage 7120
 
Sun Storage 7310 Unified Storage System
 
Oracle ZFS Storage Appliance Racked System ZS4-4
 
Sun ZFS Storage 7320
 
Oracle ZFS Storage ZS3-BA
 

PLA-Support>Sun Systems>DISK>ZFS Storage>SN-DK: 7xxx NAS
 

In this Document

Goal

Solution

References

Created from <SR 3-13684358664>

Applies to:

Goal

Leap second handling

Solution

Q1.  ZFS Storage is an NTP client, no need to handle the leap second issue, but in the case of ZFS, only STEP can be set.

         Then, in leap seconds, regardless of whether leap seconds (LI packet) is inserted or not , 1 second of reversal will occur,right ?
         If the answer is yes, how to avoid the leap second issue in storage side ?

Some variants of Unix may use a Timezone file to allow systems not running NTP, to report a time that is corrected for leap seconds.
This is *not* the case in Solaris.  Solaris Leap Second adjustment requires the use of NTP and Timezone file is not used.
In order to avoid any leap second issues , please use a NTP  server for time synchronization.

Q2.  Please tell me the OS version of ZFS7420 and Z3-2 and the version of NTP client.

Example:
  7420：Solaris11/NTP3
　Z3-2：Solaris11/NTP3

All ZFS storage appliances run Solaris 11.
The version of NTP delivered wwith Solaris 11 is NTP v4, while Solaris 10 ships with both.

References

This solution has no attachment