Configuring NTP Authentication Using the System Configuration Page (CTPView)

date_range 20-Jan-22

NTP authentication enables the CTP device, which functions as the NTP client, to verify that servers are known and trusted. Symmetric key authentication will be used to authenticate the packets. It is assumed that the shared secret key is already being communicated between client and server and it is the responsibility of the server to have the shared secret keys already configured in their configuration and keys files. The client then adds the required key ID and shared secret key to their configuration and keys files through CTPView or through syscfg commands. The Key ID and Key Value fields must be left blank in CTPView to disable NTP authentication.

To configure NTP authentication using CTPView:

In the side pane, select System > Configuration.

Tip
Alternatively, you can specify the key ID and key value for NTP authentication from the System Query page by selecting System > Query in the side pane.
Click Node Settings tab.
The NTP Settings page is displayed. The hostname and IP address of the CTP device are displayed under the Device table, which is shown to the left of the NTP Settings table.
Configure the parameters described in Table 14 and click Submit Settings.
(Optional) Click System > Configuration > Node Settings to verify the NTP configuration details.

Table 14: NTP Server Authentication Settings on the System Configuration Page in CTPView

Field	Function	Your Action
Server IP	Specifies the IPv4 or IPV6 address of the NTP server. Adds NTP servers to the server list (IP addresses or hostnames). You can configure a maximum of two NTP servers. NTP authentication is started from the first server in the list and if the first server fails or becomes unavailable, the second server in the list is used.	Enter the IPv4 or IPv6 address of the NTP server to be used for authentication.
Key ID	Specifies the key ID to authenticate the NTP packets received from the server by the NTP client. The servers and clients involved must agree on the key and key identifier to authenticate NTP packets. Keys and related information are specified in a key file. Key ID is used to prove authenticity of data received over the network. During the synchronization of time, the client requests the key ID with the “NTP Client” packet and server sends the response with the “NTP Server” packet. If the key ID differs in both the packets, then the time does not synchronize. The time is synchronized and modified for the client only when the two key IDs are the same. The IP address with the secret key is configured in the “/etc/ntp.conf” NTP configuration file on the CTP device. The following is the example for the ntp.conf file: ‘server x.x.x.x key 123’ where: x.x.x.x is the NTP server IP address Key is the secret key id which is shared by both the client and server.	Enter a 32-bit integer in the range of 1 through 65534.
Key Value	Specifies the value of the NTP key used for NTP authentication between the NTP server and the NTP client. NTP uses keys to implement authentication. This key is used while exchanging data between the client and server. The following three key types are present: An A key is just a sequence of up to eight ASCII characters. An M key is a sequence of up to 31 ASCII characters. An S key is a 64 bit value with the low order bit of each byte being odd parity. CTP devices support the M key (MD5) for NTP authentication. All the keys must be defined in the “/etc/ntp/keys” file. The following is an example for the keys file: ‘123 M pass’ where: 123 is the key id (range 1 to 65534) M designates the key type (M means MD5 encryption) Pass denotes the key itself	Enter the key value as a sequence of up to 31 ASCII characters.
Status	Specifies whether you want to enable or disable the NTP process on the CTP device.	Select one: Enabled—Enables the NTP process on the CTP device. Disabled—Disables the NTP process on the CTP device.

You can also configure the RADIUS and TACACS+ settings from the System Configuration page.

To configure TACACS+ from the CTPView web interface:

In the side pane, select System > Configuration.
Click Node Settings > TACACS+ Settings tab.
The TACACS+ Settings page is displayed.
Configure the parameters described in Table 15 and click Submit Settings.

(Optional) Click System > Query > Node Settings to verify the TACACS+ configuration details.

Table 15: TACACS+ Settings for the CTPView Web Interface

Field	Function	Your Action
Status	Specifies whether TACACS+ is enabled or disabled. TACACS+ is disabled by default.	Select one. Enabled Disabled
Dest Port	TACACS+ uses the TCP port for sending and receiving data. Port 49 is reserved for TACACS+ and is the default port.	Enter the destination port number.
Timeout	Time in seconds that the TACACS+ client should wait for a response from the TACACS+ server after sending the authentication and authorization request. Timeout value applies to all the TACACS+ servers that are configured. The default timeout value is 5 seconds.	Specify a value.
Off-Line-Failover	You can use the local authentication credentials if the configured TACACS+ servers are unavailable or no response is received from the TACACS+ servers. The default option is `Allowed to Loc Acct`.	Select one. Not Allowed Allowed to Loc Acct
Reject-Failover	You can use the local authentication credentials if the TACACS+ server rejects the attempt to authenticate. The default option is `Allowed to Loc Acct`.	Select one. Not Allowed Allowed to Loc Acct
Servers	You can configure up to 10 TACACS+ servers each for CTPOS and CTPView users for authentication and authorization. CTP tries to authenticate the user from the first server in the list. If the first server is unavailable or fails to authenticate, then it tries to authenticate from the second server in the list, and so on. Authorization is done on the server that successfully authenticates the user.	Enter the IP address of the server, and specify a shared secret.
Shared Secret	Shared secret is the secret key that TACACS+ servers use to encrypt and decrypt packets that are sent and received from the server. TACACS+ clients use the same secret key to encrypt and decrypt packets.	Specify the shared secret.

To configure RADIUS from the CTPView web interface:

In the side pane, select System > Configuration.
Click Node Settings > RADIUS Settings tab.
The RADIUS Settings page is displayed.
Configure the parameters described in Table 16 and click Submit Settings.

(Optional) Click System > Query > Node Settings to verify the RADIUS configuration details.

Table 16: RADIUS Settings for the CTPView Web Interface

Field	Function	Your Action
Status	Specifies whether RADIUS is enabled or disabled. RADIUS is disabled by default.	Select one. Enabled Disabled
Dest Port	RADIUS uses the TCP port for sending and receiving data. Port 49 is reserved for RADIUS and is the default port.	Enter the destination port number.
Timeout	Time in seconds that the RADIUS client should wait for a response from the RADIUS server after sending the authentication and authorization request. Timeout value applies to all the RADIUS servers that are configured. The default timeout value is 5 seconds.	Specify a value.
Off-Line-Failover	You can use the local authentication credentials if the configured RADIUS servers are unavailable or no response is received from the RADIUS servers. The default option is `Allowed to Loc Acct`.	Select one. Not Allowed Allowed to Loc Acct
Reject-Failover	You can use the local authentication credentials if the RADIUS server rejects the attempt to authenticate. The default option is `Allowed to Loc Acct`.	Select one. Not Allowed Allowed to Loc Acct
Servers	You can configure up to 10 RADIUS servers each for CTPOS and CTPView users for authentication and authorization. CTP tries to authenticate the user from the first server in the list. If the first server is unavailable or fails to authenticate, then it tries to authenticate from the second server in the list, and so on. Authorization is done on the server that successfully authenticates the user.	Enter the IP address of the server, and specify a shared secret.
Shared Secret	Shared secret is the secret key that RADIUS servers use to encrypt and decrypt packets that are sent and received from the server. RADIUS clients use the same secret key to encrypt and decrypt packets.	Specify the shared secret.

arrow_backward PREVIOUS

NEXT arrow_forward CTPView Network Management System Administration

Helped me install or use the product
Accelerated my deployment

Discuss the product with a co-worker
Make a purchase inquiry

CTPView Network Management System Administration

Configuring NTP Authentication Using the System Configuration Page (CTPView)

Stay in touch