Objective
Describe the configuration procedures recommended by OpServices for time synchronization between OpMon and the Network internal NTP server.
Target audience
Intended for OpMon administrators and IT teams, that needs to perform the time synchronization between OpMon and the NTP server.
1) Configuration for time synchronization between OpMon and the Network internal NTP server
After the installation, if necessary, you can proceed to the configuration for time synchronization between OpMon and the Network internal NTP server. This configuration is RECOMMENDED. For that, the next steps must be followed:
a) Login as root on the OpMon console.
b) Edit the file /etc/ntp.conf with the command:
[root@opmon /]# vim /etc/ntp.conf
c) Locate the corresponding lines to the servers (ntp servers), that follow the next standard.
server
d) The file must contain at least an entry with the name server. If you prefer, follow the configuration example, recommended by NTP.br.
# servidores publicos do projeto ntp.br server a.st1.ntp.br iburst server b.st1.ntp.br iburst server c.st1.ntp.br iburst server d.st1.ntp.br iburst server gps.ntp.br iburst server a.ntp.br iburst server b.ntp.br iburst server c.ntp.br iburst # configuracoes de restricao de acesso restrict default kod notrap nomodify nopeer noquery restrict -6 default kod notrap nomodify nopeer noquery # desabilitar comando monlist disable monitor
e) Now you can comment it, and insert the line referring to the internal NTP server (consult the network administrator).
f) Save when exit the file
g) Restart the ntpd service with the next command:
[root@opmon /]# service ntpd restart Shutting down ntpd: [ OK ] Starting ntpd: [ OK ]
h) To check the synchronization performance, type the next command:
[root@opmon /]# ntpq -c as ind assID status conf reach auth condition last_event cnt =========================================================== 1 18409 9614 yes yes none sys.peer reachable 1 2 18410 9414 yes yes none candidat reachable 1 3 18411 9014 yes yes none reject reachable 1 4 18412 9014 yes yes none reject reachable 1 [root@opmon /]# ntpq -c pe remote refid st t when poll reach delay offset jitter =============================================================== *a.ntp.br 200.160.7.186 2 u 44 64 17 40.266 1.235 0.058 +b.ntp.br 200.20.186.76 2 u 40 64 17 28.124 2.723 0.265 c.ntp.br 200.160.7.186 2 u 39 64 17 43.864 1.702 0.043 LOCAL(0) .LOCL. 10 l 39 64 17 0.000 0.000 0.001
i) If the word REJECT appears on the column CONDITION, the configuration must be evaluated, once the connection to the NTP server was rejected. If REJECT appears after the configuration, it’s normal. The updating process can take some minutes, wait a moment and try later. Otherwise the network administrator must be consulted.
2) Forcing the NTP update manually
You can force the NTP update manually, following the next instructions: a) Check if the server date is updated
[root@opmon /]# date Mon Jul 11 13:30:03 BRT 2011
b) If it’s outdated, run the next commands in order:
[root@opmon /]# ntpdate -u a.ntp.br 11 Jul 13:50:16 ntpdate[21855]: step time server 200.160.0.8 offset 1205.161757 sec