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

2-142
Configuring the ProCurve Wireless Edge Services xl Module
Enabling Secure Network Time Protocol (NTP)
By encrypting the cookie with the client’s public key, the server
ensures that only the client can use the cookie. The client, for its part,
must initially trust the server. After this initial trust, the client knows
that the same server is sending the time because only that server has
the cookie that generates the correct keys.
Configuring a Secure NTP Server
As an NTP server, the Wireless Edge Services xl Module sends the time to
stations and devices that request this information. To obtain the correct time,
it can use its internal clock, exchange messages with other servers in your
network (called its NTP neighbors), or both.
To configure secure NTP, first determine the module’s function in your net-
work’s NTP implementation:
1. If the Wireless Edge Services xl Module simply needs to accept the time
from an NTP server, complete one of the tasks below:
• Enable the module to listen for NTP broadcasts.
• Configure the module to request the time from NTP servers:
– Add up to three NTP neighbors in server mode.
– For additional security, require authentication.
When you require symmetric key authentication, first configure
a key that matches each server’s key.
When you require autokey authentication, make sure that your
module has the appropriate certificate.
■ If the module should act as an NTP server, complete these tasks:
• If you want the module to use its internal clock to serve the time,
configure it to act as the master clock.
• Or, apply ACLs to control access to the module’s NTP services.
• Optionally, require authentication for neighbors, configuring one of
the following options for keys:
– For auto-key, enable the feature and make sure that the module
has the necessary public and private keys (stored in a server
certificate in a trustpoint configuration).
– Manually create symmetric keys.