Tavve zoneranger User Manual page 76

a. The Ranger Gateway through which the ZoneRanger will access the NTP server. Note
b. The IP address or hostname of the NTP Server.
3. Optionally, the Validate Authentication option may be enabled. If this option is enabled, a set
of ( index , key ) pairs must be configured in the Keys table. These values must match the
corresponding values configured on the NTP servers that were specified in the previous step. In
the case of NTP proxy, the managed device acting as an NTP client does not have any control
over which NTP server will be chosen to handle each request. As such, the table of ( index,
) values in the specified NTP servers must be identical, at least for the set of indexes that
key
the managed devices may use.
4. By default, when the ZoneRanger proxies a NTP proxy request through the joined Ranger
Gateway to the NTP server, the source of the NTP request will appear to the NTP server as if
the NTP client is the Ranger Gateway server and not the actual ZoneRanger managed device. It
is possible to configure the Ranger Gateway to spoof the source address in the NTP proxy
request to be that of the ZoneRanger managed device instead of the address of the Ranger
Gateway. To configure NTP proxy spoofing, either use the Ranger Gateway Viewer Configure
> Gateway Settings menu, NTP Proxy area or the
Gateway.
Additional Note
If the Ranger Gateway is communicating with an NTP server installed on the same server using
GVI or on a different server using RGVI, it may be necessary to restart the NTP server after the
GVI service or RGVI client on that server are enabled. The startup procedure of some NTP servers
is to enumerate the IP addresses on a given server, and then to specifically bind a listener for each of
these addresses. Enabling GVI or starting an RGVI client effectively creates a new IP address,
associated with an underlying virtual point-to-point interface, and if this interface was not
configured at the point when the NTP server was started, the NTP server will be unaware of the
additional interface, and will not be able to receive NTP traffic from that interface. Where the
Ranger Gateway and an NTP server are co-located on the same server, it is recommended that the
server be configured to start the Ranger Gateway before starting the NTP server when the server
starts up. Similarly, where an RGVI client and an NTP server are co-located on the same server, it
is recommended that the server be configured to start the RGVI client before starting the NTP
server.
ZoneRanger 5.5 User's Guide
that the option for the ZoneRanger to access an NTP server directly is not supported in
this case.
command on the Ranger
configGateway
76