Wireless/Redundant Edge Services xl Module Management and Configuration Guide WS.02.xx and greater

2-145
Configuring the ProCurve Wireless Edge Services xl Module
Enabling Secure Network Time Protocol (NTP)
If you enable your module to act as the master clock, it can serve the time
whether or not it receives the time from another server or peer.
4. If you checked the Act as NTP Master Clock box (in step 3), in the Clock
Stratum field enter how many hops (from 1 to 15) the Wireless Edge
Services xl Module is from an NTP time source.
Valid values are from 1 to 15, although your clock stratum value should
be at least 2 (because you are not actually connected to a stratum 0
device). Typically, you should set the stratum somewhat higher (for
example, to 10): the Wireless Edge Services xl Module automatically
chooses the NTP resource with the lowest stratum number, and its
internal clock should not take precedence over a more robust clock.
The NTP-enabled module compares the time reported by several sources
and does not synchronize to a time source whose time is significantly
different than others, even if its stratum is lower. You do not need to worry
that your module will synchronize to an NTP server that is not synchro-
nized itself.
5. Check the Listen to NTP Broadcasts box to allow the Wireless Edge Services
xl Module to receive the time from an NTP broadcast server.
The module and the NTP broadcast server must be on the same subnet-
work.
6. If you check the Listen to NTP Broadcasts box, you have the option of setting
the broadcast delay in the Broadcast Delay field.
By default, the Wireless Edge Services xl Module exchanges a series of
packets with the broadcast server to estimate the average delay to the
server. With this information, the module knows by how much to offset
the time it receives from the server.
Alternatively, you can manually specify the estimated delay to the server
by entering a value between 1 and 999999 microseconds in the Broadcast
Delay field.
7. Click the Apply button.
You can now set up optional security mechanisms (see “Applying ACLs
to NTP Services” on page 2-146 and “Configuring Authentication for
Secure NTP” on page 2-148) and add neighbors (see “Configuring NTP
Neighbors” on page 2-152).