Network Time Protocol configuration is to be done on the SDM-FT first and on
the DMS after. NTP Configuration and start-up on SDM-FT: 1. The time zone variable TZ on the SDM needs to be set in the environment file /etc/environment, for SDM TOD to operate on specific time zone. The time, date and time zone of the SDM-FT can be changed by using the “smit system”. 2. Edit the xntpd configuration file, /etc/ntp.conf, and make sure that it contains the following lines: driftfile /etc/ntp.drift tracefile /etc/ntp.trace 3. Add a line for each NTP server that you want the SDM to synchronize with as follows: server <ntp server ip address> Only one server is required for synchronization, but more may be desirable to increase reliability. If the SDM cannot contact one server to synchronize, it may be able to contact another. 4. Before starting the NTP server on the SDM, its TOD clock must be synchronized with the NTP master server: ntpdate <ntp server IP address> 5. Access the xntpd control menu by typing: >smit xntpd 7. Select "Start Using the xntpd Subsystem" to enter the xntpd daemon start- up menu and select option “BOTH” (to start the process now and after reboot of the SDM). 8. Check to see that the xntpd process is running: >ps -ef | grep xntpd root 12032 10949 1 13:57:16 pts/1 0:00 grep xntpd root 29936 8776 0 Jun 23- 0:03 /usr/sbin/xntpd The process should be started under /usr/sbin/xntpd. If not, kill the process and restart it. 9. Confirm that the daemon is communicating with the NTP server by executing the following command: >ntpq -p remote refid st t when poll reach delay offset disp *47.128.128.59 47.128.0.137 3 u 725 1024 377 9.63 -0.004 2.47 The "*" before the NTP server IP address indicates that the server is being used for synchronization. Note that it may take some time for the "*" to appear. However, as long as the value in the “when” field is less than the value of the “poll” field, the daemon is successfully communicating with the server.
NTP Configuration and start-up on the DMS:
1. In OFCENG, office parameter SNTP_CLIENT is set to “Y”. 2. Execute the DATE command to verify that the date displayed is that of the present day date or else set the present date properly by SETDATE command. > DATE > SETDATE <DD> <MM> <YYYY> 3. Go to the NTPCI level and execute the command STARTNTP with proper time zone value in minutes. NTPCI> STARTNTP <TZ> 4. Execute the QUERYNTPTIME command to query the present Core TOD clock offset with the ntp time. NTPCI> QUERYNTPTIME 5. Execute the SETTIMETONTP command at the NTPCI level to set the Core TOD clock with ntp time. NTPCI> SETTIMETONTP 6. Verify the status of the process: > QUERY PROCESS SNTPCLNT 433E8340: 6508 6046 SNTPCLNT class=GTERM slice=1 lock=3 unprot=0 queued on mailbox Make sure that the process has been started in option “queued on mailbox”. If not, kill the SNTPCLNT process and restart the procedure. If it does not work, try to change the office parameter controlling the SNTP client in OFCENG.
Kali Linux - An Ethical Hacker's Cookbook - Second Edition: Practical recipes that combine strategies, attacks, and tools for advanced penetration testing, 2nd Edition
Windows Server 2019 Administration Fundamentals - Second Edition: A beginner's guide to managing and administering Windows Server environments, 2nd Edition
React.js for A Beginners Guide : From Basics to Advanced - A Comprehensive Guide to Effortless Web Development for Beginners, Intermediates, and Experts
The Apple Watch Ultra 2 And Series 9 Update: Your Rich Book to the complete Mastery of Apple Watch Ultra 2 and Series 9 with WatchOS 10, Tips, Tricks, Features, and Pictures