system clock problem over my hp superdome parisc 11iv1

[Cem Tugrul]

newhr:/#date
Tue Jan 18 17:39:44 EET 2011

[Cem Tugrul]

env command shows me;
TZ=EET-2EETDST
This is for Turkey and hp recommended it.

[donna hofmeister]

check the firmware on your system. there is a fix in one release that addresses 'domes that cannot correct the system clock regardless of ntp.

[Cem Tugrul]

@donna you are probably right and seems my superdome needs to be patched for last 3 yrs
Anyway,just a rapid solution what I done
that I set into cron sysntax as;(for every 5min)

00,05,10,15,20,25,30,35,40,45,50,55 * * * *
/usr/sbin/ntpdate -u ipadress_of_nrp_server >/dev/null

[Cem Tugrul]

patch&firmware needs

[Hakki Aydin Ucar]

You can check if it is working ;
# ntpq -p

[Cem Tugrul]

newhr:/#ntpq -p
remote refid st t when poll reach delay offset disp
==============================================================================
10.126.1.1 CHU(1) 8 u 707 1024 377 0.43 -10025. 4113.31

[Bill Hassell]

> ntpq -p
> 10.126.1.1 CHU(1) 8 u 707 1024 377 0.43 -10025. 4113.31

These are severe sync problems. While the ntpdate might seem to work, this is a 'jump' solution, that is, you may lose or gain seconds during the day, something that a properly setup ntp client will never do. So as long as you aren't running Oracle or Sybase or other big iron databases, it will be a cosmetic workaround (the date will be correct most of the time).

Oh wait, you said Oracle DB and application. Since most database transactions are timestamped to prevent problems with out of sync updates, if the clock keeps jumping forward or backward, you will likely see database corruption. Your machine is too unstable to be used for database work right now.

As Donna said, there is a firmware (hardware) update needed. This isn't a fix to HP-UX, it is a firmware change to the SuperDome hardware. Here is Donna's original problem:

http://h30499.www3.hp.com/t5/System-Administration/ntp-problem/m-p/2683866/highlight/true#M53674

You'll see all the symptoms that you are experiencing. Since there are several models of SuperDome (SX1000, SX2000, Integrity), you'll need to get the latest firmware 'recipe' for your model. Start with:

http://h20000.www2.hp.com/bizsupport/TechSupport/Product.jsp?lang=en&cc=us&taskId=135&prodTypeId=15351&prodCatId=321931

or

http://h20000.www2.hp.com/bizsupport/TechSupport/Product.jsp?lang=en&cc=us&taskId=135&prodTypeId=15351&prodCatId=321933

SuperDomes in the past have been managed by a small SMS server such as an rp2470. However, recently a patch was released for PDC code updates that provide the HP-UX program fwuu. This is for very old SuperDomes where the GSP does not have the "FW" command in the main menu. If you see the FW command, then you don't need the SMS for firmware updating.

If your machine is under hardware support with HP, let them do all this work. Otherwise, pay careful attention to all the steps in the README files.

[Cem Tugrul]

Bill,

Guardian Service Processor (GSP) - FW Revision 7.34, Aug 24 2004

You are right.My Super Dome also is using SMS
server rp2470 but had not been patched for 3 yrs because it was closed.

It would be better for me start patching the system instead of cron solution.

Thank you very Much...