Begin Tab Sub Links

Storage

last updated on: 2008-06-13



Disk Products

  • Sun StorageTek 31xx, 33xx, 35xx
    • No customer actions required - arrays use only GMT
  • Sun StorageTek 52xx, 53xx
    • Customers on releases earlier than 4.12, must upgrade to 4.12 or later
    • Customers on release 4.12 or later, then need to download the DST schedule from ftp://elsie.nci.nih.gov/pub/ and run the zic command
      • This procedure is documented here
  • Sun Storagetek 5800
    • Uses UTC internally, no impact.
  • Sun StorageTek 6020, 6120
    • Customer action required - time should be manually updated through the CLI
  • Sun StorageTek 6130, 6140, 6540
  • Sun StorageTek FLX380, FLX280, FLX240, FLX210
  • Sun StorageTek D280, D240, B280, D178
    • Controller Firmware
      • The DST change will have no impact on the controller firmware or operation of the hardware. All time values that are stored by the controller or conveyed via the SYMbol interface are expressed in absolute GMT (Greenwich Mean Time). The time is obtained from the controller's real-time clock and provided in GMT format back to the management interface.
      • There is no notion of time zone in time stamps or preserved time values in the controller firmware. The management software is expected to translate between such values and the local time zone equivalents.
    • Management Software
      • Customers will be using either CAM or SANtricity as the Management Software for these arrays.
      • See the Storage Software section for information on CAM and SANtricity.
  • Sun StorageTek 6320
    • A patch is in development, but will not be available before March 11th 2007
    • The customer can manually change the time if needed
    • Impact of not upgrading - The associated event logs (generated on the Sun StorageTek 6320) will be off by one hour for the three week period from March 11 to April 1. Assuming that the servers attached to the Sun StorageTek 6320 have been properly updated, the user should see no visible problems because all end-user time-stamping (such as file date/time stamps) are generated by the host and are stored on the Sun StorageTek6320as simple data like everything else. On Sunday, April 1, the Sun StorageTek 6320 will self-correct, enabling DST.
  • Sun StorEdge 6910, 3910, 6960, 3960
    • No customer actions required
    • The StorEdge 6910, 3910, 6960, and 3960 all use GMT to record log events
    • The time on the service processor can be set manually if required
    • There is no impact if the time is not set
  • Sun StorageTek 6920
    • Customer actions are required - this issue will be addressed in the future release of Firmware version 3.0.1.26
      • Firmware version 3.0.1.26 (URB 26) is now available. This upgrade MUST be performed by Sun engineers. Please contact your local support center for further information.
    • There is no workaround currently available
    • See Sun Alert 102797
    • Impact of not upgrading - The associated event logs (generated on the Sun StorageTek 6920) will be off by one hour for the three week period from March 11 to April 1. Assuming that the servers attached to the Sun StorageTek 6920 have been properly updated, the user should see no visible problems because all end-user time-stamping (such as file date/time stamps) are generated by the host and are stored on the Sun StorageTek 6920 as simple data like everything else. On Sunday, April 1, the Sun StorageTek 6920 will self-correct, enabling DST.
  • Sun StorageTek 9xxx
    • The Sun StorageTek 9xxx systems include a Service Processor (SVP) that is used by the engineer during the installation, configuration and ongoing management of the system. The clock on the SVP is typically set by the engineer to Greenwich Mean Time (GMT) or to the customer's local time and must never be set to automatically adjust to DST or other similar changes. The change in start/end dates for DST will not affect the operation of these storage systems.
    • No customer actions required
  • Sun StorageTek 9900, 9985 NAS Blade
    • The NAS Blade for the 9990 and 9985 rely upon their NAS operating systems to calculate daylight saving time changes. The required changes are in the 03-07 NAS operating system version that is scheduled for release on February 19, 2007.
    • See InfoDoc 78884 for details on the Hitachi Software and Microcode order process.
    • Note that this upgrade must be performed by Sun trained personnel.
    • See http://www.hds.com/pdf/hds_dst_impact.pdf for further information
  • Sun StorEdge A1000, A3000, A3500, A5x00, RM6, RSM2000, SSA arrays
  • Sun StorEdge D130, D2, D240, D1000, S1 JBODs
    • No customer actions required
  • Shared Virtual Array (SVA) disk products - V2X4f, V2X2, V2X, V960 and related products
  • Virtual Storage Manager (VSM) platforms - VSM2, VSM3, VSM4, VSM4e, VSM5
    • These products maintain an internal time of day clock completely independent of any Host based clock. The internal time of day clock of these products must be manually synchronized to local time. This is accomplished via the local or detached operator panel. Keeping the product's internal time of day clock synchronized to the actual local time is a convenience and does not positively or negatively affect the operation of the product.
    • No customer actions required unless the product is set to local time
    • Check with your OS vendor to determine if OS patches are required
  • Sun StorEdge T3, T3+
    • No customer actions required
    • The time can be changed manually if required
    • Impact of not changing the time is that the the time recorded in the logs will be 1 hour off for 3 weeks
  • HBAs
    • Apply OS patches



Tape Products

  • StorageTek SL8500, SL500
    • No customer actions required
    • Check with your OS vendor to determine if OS patches are required
  • Key Management Station
    • The clock can be reset manually. Customers will be contacted and assisted through the process.
  • Tape Drives (all models)
    • No customer actions required
    • Check with your OS vendor to determine if OS patches are required
  • StorageTek L1400, L700, L180, L80, L40, L20
    • These products maintain an internal time of day clock independent of any Host based clock. The internal time of day clock of these products must be manually synchronized to local time. Keeping the product's internal time of day clock synchronized to the actual local time is a convenience and does not affect the operation of the product.
    • No customer actions required unless the product is set to local time
    • Check with your OS vendor to determine if OS patches are required
  • StorageTek 9310, 97xx
    • These products maintain an internal time of day clock independent of any Host based clock. The internal time of day clock of these products must be manually synchronized to local time. Keeping the product's internal time of day clock synchronized to the actual local time is a convenience and does not affect the operation of the product.
    • No customer actions required unless the product is set to local time
    • Check with your OS vendor to determine if OS patches are required
  • StorageTek C2, C4
    • Customer must reset the time via the operator control panel. See User Manual for instructions
    • An incorrect time can affect the timing of data backups
    • Also check with your OS vendor to determine if OS patches are required
  • StorageTek StorageNet 6000 Storage Domain Manager (SN6000)
    • Product runs on UTC
    • No customer actions required
    • Check with your OS vendor to determine if OS patches are required



Storage Software


See also the Software section for other software product information.
  • ACSLS
    • No customer actions required
    • Check with your OS vendor to determine if OS patches are required
  • Backbone
    • Gets time from the OS
    • Check with your OS vendor to determine if OS patches are required
  • Business Analytics
    • Gets time from the OS
    • Check with your OS vendor to determine if OS patches are required
  • CAM (Common Array Manager)
    Customer actions required:
    • Customers currently using CAM 5.0, 5.0.1 or 5.0.2 will need to apply Java fixes and update the OS.
    • Application of Java fixes is required and requires the JVM to be restarted. This will cause CAM to restart.

    OS patches are also required:
    For reference:
    • Sun StorEdge 6130 Array Host Installation Software for Solaris V1.2 (Original 6130 release)
      • Runs on Solaris/SPARC Version 8, 9, 10
      • Uses J2SDK 1.4.2_08 (Java SDK)
    • Sun StorageTek 6140 Array Management Software 2.1 (Original 6140 release)
      • Runs on Solaris/SPARC Versions 8, 9, 10
      • Uses J2SDK 1.4.2_08
    • Sun StorageTek Common Array Manager (CAM) 5.0, 5.0.1, 5.0.2 (Original 6540 release)
      • Runs on Solaris/SPARC Versions 8, 9, 10, Solaris/X86 Version 10, Windows
      • Uses J2SDK 1.4.2_08

    CAM 5.1 will ship in February 2007 with the latest Java SDK which fixes this issue.

    Customer impacts if changes not applied:
    • If the customer does not apply the Java fixes to CAM 5.0, 5.0.1 or 5.0.2 or upgrade to CAM 5.1, the time reported by CAM will not change for DST at the right time. This could cause time stamps on logs and/or alarm entries to be off by an hour.
  • CBEM
    • Require an update to Java 1.4.2_13
    • Refer to Java DST Information to update from the Java 1.4.2 image that this product is using.
  • Data Replication Manager 1.0
    • Requires an update to Java 1.4.2_13. It is not compatible with Java 5.0. During installation, Java 1.4.2_08 may have been installed depending on the Customer actions during installation.
    • Customer impacts if changes not applied:
      • Timestamps may not be displayed correctly.
  • EBS (EMC)
    • Gets time from the OS
    • Check with your OS vendor to determine if OS patches are required
  • ExLM
    • No customer actions required
    • Check with your OS vendor to determine if OS patches are required
  • Expert High Performance Data Mover
    • Gets time from the OS
    • Check with your OS vendor to determine if OS patches are required
  • Expert Performance Reporter
    • Gets time from the OS
    • Check with your OS vendor to determine if OS patches are required
  • Hitrack
    • Gets time from the OS
    • Check with your OS vendor to determine if OS patches are required
  • Host Software Component
    • Gets time from the OS
    • Check with your OS vendor to determine if OS patches are required
  • Intellistore
    • Gets time from the OS
    • Check with your OS vendor to determine if OS patches are required
  • Lib Attach
    • Gets time from the OS
    • Check with your OS vendor to determine if OS patches are required
  • Library Station
    • Gets time from the OS
    • Check with your OS vendor to determine if OS patches are required
  • Management Portal 1.0
    • Portal 1.0 is highly dependent on Java Enterprise System Release 3 (Web Server, Portal Server, Directory Server, Access Manager), and Postgresql 7.x.
      • Refer to the Java Enterprise System Release 3 products on this issue.
    • Customer impacts if changes not applied:
      • Several portlets within the product may display an incorrect timestamp.
    • See Sun Alert 102760 for Java versions, refer to Java DST Information to bring Java versions to latest versions.
  • MVS-Client System Component (MVS/CSC)
    • Gets time from the OS
    • Check with your OS vendor to determine if OS patches are required
  • Removable Media, Library Software/Client System Component (RMLS/CSC)
    • Gets time from the OS
    • Check with your OS vendor to determine if OS patches are required
  • SANtricity
    The SANtricity management software relies on the Java Runtime Engine (JRE) to translate GMT into the appropriate time. This calculation involves both the time zone and daylight saving translations. So in order to fix this in SANtricity a new build of host software with the appropriate JRE included must be distributed. This issue is addressed in 1.4 JRE version 1.4.2.11 as well as the 1.5 JRE.

    Customer actions required:
    • Upgrade to SANtricty the latest build of 9.12 or SANtricity 9.19.
    • The required JRE update has been incorporated into the latest 9.12 and all 9.19 SANtricity builds. If a customer is running either of these builds they will not see any impact of the DST change for any firmware levels they are managing.

    Customer impacts if changes not applied:
    • If the customer is not running one of these builds there should be no material impact. The impact is cosemtic in that email alerts and Major Event Log entries will be off by 1 hour for 3 weeks in the spring and 1 week in the fall. This is due to the fact that the time will be translated improperly by the Java Runtime Engine that is currently in use.
    • This should not be a material impact; as noted above, all times within the controller firmware are stored in an absolute form. Such values will be incorrect for the three-week period when viewed from SANtricity or other Java-based management software. Additional incorrect timestamps may be seen in diagnostics reports, various component display dialog boxes, and performance monitor.
  • SDP Appliance
    • JRE and RedHat Linux upgrade patches to SDP site units are required
    • Updates will be implemented by SDP engineering over the remote connection
  • SDS/SVM/SLVM
    • Gets time from the OS
    • Check with your OS vendor to determine if OS patches are required
  • Storage Foundation
    • Gets time from the OS
    • Check with your OS vendor to determine if OS patches are required
  • Storage Management Component
    • Gets time from the OS
    • Check with your OS vendor to determine if OS patches are required
  • Storagetek Traffic Manager, SAN (Leadville) and SAN Foundation Kit
    • These products are components of the Solaris consolidation and require the application of the Solaris OS patches.
  • Unicsys-Client System Component (Unisys/CSC)
    • Gets time from the OS
    • Check with your OS vendor to determine if OS patches are required
  • Veritas Cluster Server (VCS)
    • Uses Java Run Time Environment (VRTSjre (Java 1.4) and VRTSjre15 (Java 1.5)
    • Refer to Java DST Information.
  • Veritas Volume Manager
  • Virtual Tape Control System
    • Gets time from the OS
    • Check with your OS vendor to determine if OS patches are required
  • Virtualization
    • StorageTek VTL
    • StorageTek MirrorStore
    • FalconStor IPStor
      • The VTL, Mirrorstore, and IPStor management software relies on the Java Runtime Engine (JRE). The RedHat v7.3 patch and the SUSE v9.3 patch are updates to the JRE. Running the patches will ensure that local time is correctly calculated.
      • Customer impacts if changes not applied:
        • If the customer does not install these updates, FalconStor IPStor, Mirrorstor and VirtualTape Library systems will not accurately reflect the correct local time for replication schedules, TimeMark snapshots, log files, reports, and client/server synchronizations. The impact dates will be from March 11th to April 1st and again from October 28th to November 4th. Using Network Time Protocol (NTP) will not resolve these issues. Without the patches, local time values will be incorrect for a three-week period. The values will be corrected once the original DST date of April 1st passes.
      • For customer actions see Sun Alert 102811
    • VSM (all models)
    • VSM SW VTCS, VTSS, NCS
      • Gets time from the OS
      • Check with your OS vendor to determine if OS patches are required




Change Log

Note: This Change Log only reflects changes made to this web page. Please refer to product specific information for details of product updates.
  • [2008-06-13] Updated references to Sun Alert 103044 to refer to the new SunAlert 234461.
  • [2007-08-22] Updated US specific links for Solaris to refer to DST Sun Alert 103044.
  • [2007-08-22] Updated US specific links for Java to refer to main Java DST main information page.
  • [2007-03-09] Sun StorageTek 52xx, 53xx - revised instructions and added update procedure
  • [2007-03-07] Qlogic switch firmware release 5.0.1.10 available
  • [2007-03-07] ST6920 - Firmware version 3.0.1.26 is now available
  • [2007-03-05] Updated Sun StorageTek 6920 firmware release information
  • [2007-03-02] Switches - added Sun Alert 102788
  • [2007-03-02] Added RMLS/CSC
  • [2007-02-26] VTL, Mirrorstore, IPstor - replaced customer actions by reference to Sun Alert 102881
  • [2007-02-26] Added StorageTek L180, L80, L40, L20, 9310, 97xx
  • [2007-02-21] Added link to Hitachi Data System external site for Sun StorageTek 9900
  • [2007-02-21] Updated impact for Sun StorageTek 6320, 6920
  • [2007-02-20] Sun StorageTek 6320 - updated status and impact
  • [2007-02-16] Added SL500
  • [2007-02-16] Added ExLM and Unisys/CSC
  • [2007-02-16] Removed L500, SL1400
  • [2007-02-16] StorEdge 6910, 3910, 6960, 3960, T3, T3+ added
  • [2007-02-14] StorageTek C2, C4 - customer action updated
  • [2007-02-14] Sun StorageTek 6920 - release date for firmware 3.0.1.26 added
  • [2007-02-14] Sun StorageTek 9900, 9985 NAS Blade - NAS OS 03-07 update requirement added
  • [2007-02-14] Added reminder to look at Software list
  • [2007-02-14] Added link to StorADE information under Software
  • [2007-02-14] VTL, Mirrorstore, and IPStor - added installation procedures
  • [2007-02-12] Sun StorageTek 6920 - updated information and added Sun Alert number
  • [2007-02-12] Sun StrorageTek 9xxx - added more detail on time configuration
  • [2007-02-12] Customer impact and actions added to VTL, MirrorStore and IPStor
  • [2007-02-08] StorageTek SN6000 added