Yes. The DHCTs receive their time from the QPSK via the “siManager” process on the DNCS. As such, it is the time that is on the DNCS that must be correct. The DNCS uses the NTP process to ensure time is correct. NTP can be configured to either a GPS or an NTP Time Server.
•1) To determine what the DNCS is using for time sync, open an xterm window an run:
$cd /export/home/dncs/doctor (if you are running SR 4.2 or lower)
Or
$cd /dvs/dncs/Utilities/doctor (if you are running SR 4.3 or higher)
•2) Run the “doctor” report to examine Time only:
$doctor –tv
DNCS/App Server Time Sync
============================================================
OK: DNCS and App Server time difference = 0 seconds.
DNCS NTP process : ntpd
DNCS NTP synchronization source : *timeserver2
App Server NTP process : ntpd
App Server NTP synchronization source : *dncsatm
Timezone and Daylight Savings Time Check
============================================================
= Hub Summary =
Timezone Offset DST Observed No. of Hubs Site Name
--------------- ------------ ----------- ------------
-300 minutes Yes 3 DNCS
Hub names which observe daylight savings time
---------------------------------------------
TAC LAB HUB1
TAC LAB HUB2
Virtual_Hub1
= DHCT Summary =
Timezone Offset DST Observed No. of DHCTs Site Name
--------------- ------------ ------------ -----------
Follow hub Follow hub 9 DNCS
Values for the DNCS NTP synchronization source:
LOCAL – the DNCS is not synced to any time source and is using local time, which can drift
GENERIC – the DNCS is synced to the GPS as its time source
TimeServer or IP Address – the DNCS is synced to an NTP Server
•3) If the DNCS is synced to LOCAL, ensure your Time Source values are correct in the NTP configuration file:
$cd /etc/inet
$cat ntp.conf
[12:34:52]$ cat ntp.conf
server timeserver1 prefer
server timeserver2
server timeserver3
server 127.127.8.1 mode 10 prefer # GPS connected to serial port
server 127.127.1.0 #local clock will engage if GPS fails
server 127.0.0.1 # UNIX clock if all else fails
fudge 127.127.1.0 stratum 10
driftfile /etc/ntp.drift
•4) The “server” entry can be a name, like the one in our example, or can be the IP Address of the NTP Server. If no name or IP is present, you are still configured to use a GPS. Verify your GPS is still connected correctly to the DNCS.
If the name or IP is present, attempt to ping name or IP specified:
$ ping -s timeserver1
PING timeserver1: 56 data bytes
64 bytes from timeserver1 (10.90.128.142): icmp_seq=0. time=2.99 ms
64 bytes from timeserver1 (10.90.128.142): icmp_seq=1. time=0.936 ms
•- In our example the IP is pingable. If you are unable to ping the IP, this is probably the issue.
•- Restore network connectivity between the DNCS and the NTP Server and processed.
•5) Once the network connection to the NTP Server is working, as root user:
# cd /etc/rc2.d
# ./S99xntpd stop
•- This will stop NTP on the DNCS
# ps -ef | grep ntp
•- Ensure the process stops as expected
# ./S99xntpd start
•- This will restart NTP on the DNCS
# ps -ef | grep ntp
root 18473 1 0 13:00:00 ? 0:00 /usr/local/xntpd/ntpd -c /etc/inet/ntp.conf -p /etc/ntp.pid -l /var/adm/log/ntp
•- Ensure the process restarts correctly
•6) After 10 minutes, run the $doctor –tv command from step 2
•- Verify the DNCS is now synced to the correct time source
•- Verify the DHCTs now have the correct time
