APPENDIX A:
Asktime Output:
asktime: INFO: [asktime version 19.7.0-82 (1.26)]
asktime: INFO: Logging to /usr/local/avamar/var/asktime.log
--------------------------------------------------------
Use these previously specified external time servers?
111.x.x.xxx host.domain.com
22.xx.xx.xx host2.domain.com
y(es), n(o), q(uit/exit): n
asktime: INFO: The name "ntp" did not resolve to any DNS "IN A"
resource records.
If you wish asktime to suggest a list of internal time servers
automatically, then ask your hostmaster to create one
or more "IN A" resource records for the name "ntp"
in the "x.x.com" zone.
For example:
ntp IN A xx.x.xxx.xx
ntp IN A xxx.xxx.xxx.x
ntp IN A xxx.xxx.xxx.x
Creating DNS resource records for "ntp" is optional; you
will have other opportunities to enter time server information.
Continue?
y(es), n(o), q(uit/exit): y
--------------------------------------------------------
Do you wish to use U.S. public Internet time servers such as
those offered by NIST or the U.S. Naval Observatory?
Please note the following issues with public time servers:
1. NETWORK CONFIGURATION: In order to use public Internet time
servers your site must allow port 123/udp traffic to and
from the selected Internet time servers.
2. SECURITY: Your site security policy might forbid the use
of Internet time servers. Consider setting up two or
more internal NTP time servers instead.
3. APPROPRIATE USE: Some of the U.S. public time servers known
to asktime are intended to be used only by clients within
specific U.S. time zones. If you use one of these time
servers, then asktime infers that you are using the
corresponding local time zone.
(Your previous answer was: "n".)
y(es), n(o), q(uit/exit): n
--------------------------------------------------------
Are there other external time servers that you
would like to use?
(Your previous answer was: "y".)
y(es), n(o), q(uit/exit): y
--------------------------------------------------------
Please enter the IP addresses of the external
time servers, one per line, in the form
A.B.C.D, e.g. xxx.xxx.xxx.x.
Time servers may also be specified as host names,
provided that those names will resolve.
Press Enter or Return after each response.
An empty response (a blank line) ends the list.
[00] 333.x.x.x
[01] 444.x.x.x
[02]
This is the list that you entered:
333.x.x.x
444.x.x.x
Is this list correct?
y(es), n(o), q(uit/exit): y
--------------------------------------------------------
Use this previously specified local time zone?
Australia/Sydney
y(es), n(o), q(uit/exit): y
--------------------------------------------------------
Generating time configuration files...
[mktime.custom version 1.2]
--------------------------------------------------------
The time configuration files have been created
in the following directory:
/usr/local/avamar/var/time-config-files
Do you wish to proceed with installation of these
files on the selected node?
Answering y(es) will proceed with installation.
Answering n(o) will not proceed, but will leave
available for future use the answers you have
made to the preceding configuration questions.
Answering q(uit) will exit WITHOUT saving your
answers.
y(es), n(o), q(uit/exit): y
--------------------------------------------------------
We need an approximately correct initial date and time.
Here is the current date and time from NTP, but
with year and time zone from this host:
Sat Jan 27 14:12:49 EST 2024
Please pay close attention to the MONTH, DAY, and YEAR
as well as the time.
Is this approximately correct (within a minute or two)?
y(es), n(o), q(uit/exit): y
--------------------------------
Distributing and installing time configuration files.
Please allow a minimum of 3 minutes. More time may
be required, depending on the number of nodes in the
Axion system and how busy those nodes are.
If you wish to watch this process, apply this command
in another window:
tail -f /usr/local/avamar/var/timedist.log
You may also find it helpful to monitor the following
file on each node (starting with 0.s):
/usr/local/avamar/var/timesyncmon.log
Time now: Sat Jan 27 14:14:15 EST 2024
Please wait...
--------------------------------------------------------
Do you wish to wait and watch for time synchronization?
y(es), n(o), q(uit/exit): y
asktime: INFO: Status monitoring key:
x ntpd not running on one or more nodes (should auto-correct quickly)
o no clock selected yet on one or more nodes
. unsatisfactory clock selections on one or more nodes
< insufficient time server contacts on one or more nodes
> offset still greater than 2 s on one or more nodes
) offset still greater than 1 s on one or more nodes
} offset still greater than 500 ms on one or more nodes
" offset still greater than 250 ms on one or more nodes
* possible convergence seen (offset <= 250 ms on all nodes)
Notes:
- Ideally you will see something like this: "ooxxooooooooooooooo........***"
- If you interrupt monitoring with control-C, there may be a delay
of a few seconds before monitoring stops.
Commencing 60 monitoring passes, with 10-second intervals
between passes. Time now: Sat Jan 27 14:16:48 EST 2024
APPENDIX B:
Example output for ntpq -pn
remote refid st t when poll reach delay offset jitter
==============================================================================
*333.x.x.x INIT. 16 u - 64 0 0.000 0.000 4000.00
444.x.x.x INIT. 16 u - 64 0 0.000 0.000 4000.00
xxx.xxx.x.x LOCAL(0) 8 l 5 64 1 0.000 0.000 0.001