9b8f5c9c9a
Added configuration to use Loopback ip if a switch doesn't have MGMT_PORT.
77 lines
2.7 KiB
Django/Jinja
77 lines
2.7 KiB
Django/Jinja
###############################################################################
|
|
# Managed by Ansible
|
|
# file: ansible/roles/acs/templates/ntp.conf.j2
|
|
###############################################################################
|
|
|
|
# /etc/ntp.conf, configuration for ntpd; see ntp.conf(5) for help
|
|
|
|
driftfile /var/lib/ntp/ntp.drift
|
|
|
|
|
|
# Enable this if you want statistics to be logged.
|
|
#statsdir /var/log/ntpstats/
|
|
|
|
statistics loopstats peerstats clockstats
|
|
filegen loopstats file loopstats type day enable
|
|
filegen peerstats file peerstats type day enable
|
|
filegen clockstats file clockstats type day enable
|
|
|
|
|
|
# You do need to talk to an NTP server or two (or three).
|
|
#server ntp.your-provider.example
|
|
|
|
# pool.ntp.org maps to about 1000 low-stratum NTP servers. Your server will
|
|
# pick a different set every time it starts up. Please consider joining the
|
|
# pool: <http://www.pool.ntp.org/join.html>
|
|
{% for ntp_server in NTP_SERVER %}
|
|
server {{ ntp_server }} iburst
|
|
{% endfor %}
|
|
|
|
#only listen on MGMT_INTERFACE, LOOPBACK_INTERFACE ip when MGMT_INTERFACE is not defined, or eth0
|
|
# if we don't have both of them (default is to listen on all ip addresses)
|
|
interface ignore wildcard
|
|
{% if MGMT_INTERFACE %}
|
|
{% for (mgmt_intf, mgmt_prefix) in MGMT_INTERFACE|pfx_filter %}
|
|
interface listen {{ mgmt_prefix | ip }}
|
|
{% endfor %}
|
|
{% elif LOOPBACK_INTERFACE %}
|
|
{% for (name, prefix) in LOOPBACK_INTERFACE|pfx_filter %}
|
|
{% if prefix | ipv4 and name == 'Loopback0' %}
|
|
interface listen {{ prefix | ip }}
|
|
{% endif %}
|
|
{% endfor %}
|
|
{% else %}
|
|
interface listen eth0
|
|
{% endif %}
|
|
interface listen 127.0.0.1
|
|
|
|
# Access control configuration; see /usr/share/doc/ntp-doc/html/accopt.html for
|
|
# details. The web page <http://support.ntp.org/bin/view/Support/AccessRestrictions>
|
|
# might also be helpful.
|
|
#
|
|
# Note that "restrict" applies to both servers and clients, so a configuration
|
|
# that might be intended to block requests from certain clients could also end
|
|
# up blocking replies from your own upstream servers.
|
|
|
|
# By default, exchange time with everybody, but don't allow configuration.
|
|
restrict -4 default kod notrap nomodify nopeer noquery
|
|
restrict -6 default kod notrap nomodify nopeer noquery
|
|
|
|
# Local users may interrogate the ntp server more closely.
|
|
restrict 127.0.0.1
|
|
restrict ::1
|
|
|
|
# Clients from this (example!) subnet have unlimited access, but only if
|
|
# cryptographically authenticated.
|
|
#restrict 192.168.123.0 mask 255.255.255.0 notrust
|
|
|
|
|
|
# If you want to provide time to your local subnet, change the next line.
|
|
# (Again, the address is an example only.)
|
|
#broadcast 192.168.123.255
|
|
|
|
# If you want to listen to time broadcasts on your local subnet, de-comment the
|
|
# next lines. Please do this only if you trust everybody on the network!
|
|
#disable auth
|
|
#broadcastclient
|