Defining A Ntp Neighbor Configuration - Extreme Networks Summit WM3000 Series Reference Manual

6 Enter a Key ID between 1-65534. The Key ID is a Key abbreviation allowing the controller to
reference multiple passwords.
This makes password migration easier and more secure between the controller and its NTP resource.
7 Enter an authentication Key Value used to secure the credentials of the NTP server providing system
time to the controller.
8 Select the Trusted Key checkbox to use a trusted key.
A trusted key should be used when a public key is known, but cannot be securely obtained. Adding
a trusted key allows data to be considered secure between the controller and its SNTP resource.
9 Refer to the Status field.
The Status is the current state of the requests made from the applet. Requests are any "SET/GET"
operation from the applet. The Status field displays error messages if something goes wrong in the
transaction between the applet and the controller.
10 Click OK to save and add the changes to the running configuration and close the dialog.
11 Click Cancel to close the dialog without committing updates to the running configuration.

Defining a NTP Neighbor Configuration

The controller's NTP association can be either a neighboring peer (the controller synchronizes to
another associated device) or a neighboring server (the controller synchronizes to a dedicated SNTP
server resource). Refer to the NTP Neighbor tab to assess the controller's existing configurations (both
peer and server) and, if necessary, modify the attributes of an existing peer or server configuration or
create a new neighbor peer or server SNTP configuration.
To review the controller's existing NTP neighbor configurations:
1 Select Services > Secure NTP from the main menu tree.
2 Select the NTP Neighbor tab.
Summit WM3000 Series Controller System Reference Guide
263