Sun Microsystems, Inc.  Sun System Handbook - ISO 3.4 June 2011 Internal/Partner Edition
   Home | Current Systems | Former STK Products | EOL Systems | Components | General Info | Search | Feedback

Asset ID: 1-72-1009954.1
Update Date:2010-07-06
Keywords:

Solution Type  Problem Resolution Sure

Solution  1009954.1 :   Sun Fire[TM] Midrange Server: Time Jumps When SC Accumulates Extended Uptime  


Related Items
  • Sun Fire E6900 Server
  •  
  • Sun Fire 3800 Server
  •  
  • Sun Fire 6800 Server
  •  
  • Sun Fire E4900 Server
  •  
  • Sun Fire 4800 Server
  •  
  • Sun Fire V1280 Server
  •  
  • Sun Fire E2900 Server
  •  
  • Sun Fire 4810 Server
  •  
Related Categories
  • GCS>Sun Microsystems>Servers>Midrange V and Netra Servers
  •  
  • GCS>Sun Microsystems>Servers>Midrange Servers
  •  

PreviouslyPublishedAs
213638


Symptoms
On certain Sun Fire[TM] systems, a System Controller (SC) running ScApp versions 5.18.X, 5.19.X or 5.20.X. with extended uptime may experience an abrupt clock change.

The changes have been seen where the clock jumps forward to 828 days, or where the clock becomes unstable upon reaching 828 days. The forward jump has been seen jumping 60 days forward to 828 days. This clock change can affect the domain time, database applications, customer data, or any other clock related operations.



Resolution
See the following:

Resolution is in Patch ID: 114527-12 ScApp 5.20.7 or higher



Relief/Workaround

1. Add these lines to the /etc/system file for all domains to disable the domains from getting their time from the SC:

   set tod_broken=1
set dosynctodr=0

2. Enable NTP on the domain, and SNTP on the system controller. Refer to the appropriate Solaris Systems Administration Guide for your Solaris Release, and the appropriate Platform Administration Guide for your ScApp Release.

3. Reboot the system controllers.

4. Reboot the domain at next available maintenance window prior to reaching 575 Days uptime on the system controller.

If uptime is greater than 575 days:

1. Add these lines to the /etc/system file for all domains to disable the domains from getting their time from the SC:

   set tod_broken=1
set dosynctodr=0

2. Manually disable the running domain from getting it's time from the SC. Either reboot the domain with the /etc/system changes listed in step 1, or run the script below. The following script can be invoked as "root" on the running domain to change the value of "tod_broken" and "dosynctodr" in the running domain's kernel:

   #!/bin/sh
#
# Set tod_broken and dosynctodr
#
echo "tod_broken ?W 1" | adb -w -k /dev/ksyms /dev/mem
echo "dosynctodr ?W 0" | adb -w -k /dev/ksyms /dev/mem
#
# exit 0

3. Enable NTP on the domain, and SNTP on the system controller. Refer to the appropriate Solaris Systems Administration Guide for your Solaris Release, and the appropriate Platform Administration Guide for your ScApp Release.

4. Reboot the system Controllers

(see "Additional Information" for determination of uptime on the SC).

Note: The domain will still get it's initial time from the SC on boot even with the /etc/system setting. This functionality cannot be fully disabled.

If the domain experiences this issue and the domain time has already changed, a reboot of the SC will be necessary. The time will also need to be adjusted manually on both the domain and SC. A reboot of the affected domain may also be necessary.



Additional Information
To see how long the SC has been up, and what version of ScApp it is running use the 'showsc' command:


f6800b-ssc0:SC> showsc
SC: SSC0
Main System Controller
SC Failover: enabled and active.
Clock failover enabled.
SC date: Tue Jun 26 09:28:36 EST 2007
SC uptime: 828 days 18 hours 44 minutes 53 seconds
ScApp version: 5.19.3 Build_01
RTOS version: 45

Technical Instruction <Document: 1004720.1> Sun Fire[TM] 3800-6800: How do the clocks work?



Product
Sun Fire V1280 Server
Sun Fire E6900 Server
Sun Fire E4900 Server
Sun Fire E2900 Server
Sun Fire 6800 Server
Sun Fire 4810 Server
Sun Fire 4800 Server
Sun Fire 3800 Server

Internal Comments
Audited/updated 11/17/09 - roberto.morandi@Sun.COM, ESG Content Team


The following is strictly for the use of Sun employees:

See Bug ID: 6567546 or Bug ID: 6585200


Technical Instruction <Document: 1006119.1>

Title: Sun Fire[TM]: Enabling SNTP on Sun Fire 3800-6800 SC Disrupts Domain Clock


scapp, vxworks, drift, jump, time jump, SC, domain, 828 days, 828, 575, 575 days
Previously Published As
89943

Change History
Date: 2007-09-23
User Name: 97961
Action: Approved
Comment: Publishing. No further edits required.
Version: 13
Date: 2007-09-23
User Name: 97961

Attachments
This solution has no attachment
  Copyright © 2011 Sun Microsystems, Inc.  All rights reserved.
 Feedback