Use this screen to specify the time source that the Avaya media server uses to set the time of day. You can synchronize the system clock used on server 1 and server 2 to Coordinated Universal Time (UTC) via a connection to a network time server. If you do not have access to a network time server, you can synchronize server 1 and server 2 to use the local clock on server 1.
This topic covers:
Specifying the time source for the Avaya call-processing system
Providing a keys.install file if needed
To specify the time source for the Avaya media server:
This
computer synchronizes with a duplicated server.
This configuration uses its local clock as its time source and server
1 synchronizes with server 2.
Note: The
time on server 2 must be set within five minutes to server 1 to ensure
synchronization. When local synchronization is used between servers, you
can set the date command on server 1 to adjust for time drift (varying
from the original setting), and as a result time server 2 automatically
updates to the time on server 1 within about 15 minutes after this change.
It is not necessary for you to again complete the Configuration screens
to restart the NTP
service unless the time adjustment exceeds the 15-minute limit.
Use
these Network Time Servers.
Caution: You should
have already set the media server's time within five minutes to NTS
time, date and time zone. If you need to set the time source after the
configuration has been submitted, then set the time configuration without
changing any values to ensure the NTP
service restarts.
Complete the following fields with the appropriate information if you select Use Network Time Servers
Specify up to three network time servers by IP address or DNS name in the order in which you want the Avaya media server to check them. You should always specify at least two.
If any of the specified servers requires a trusted key, enter the valid key number. Only 1 key is allowed in each field for the Primary, Secondary, or Tertiary NTS. When you enter a key for the server, it is automatically added to the list of trusted keys in the Trusted key field.
Specify whether the Avaya media server is to support multicast timing messages:
Typically, multicast is not used when network time servers are specified.
Select Yes if the NTS routinely broadcasts its timing messages to multiple clients.
Select No if the Avaya media server is to poll (directly request the time from) the specified Network Time Servers.
Additional keys (optional): To encrypt the messages between an NTS and the Avaya media server, valid key numbers must be provided by your LAN administrator.
Trusted keys: function like a checksum to make sure the time packets are valid. Trusted keys that are entered with the entries for network time servers or as a Request key or Control key are automatically added to the list of trusted keys in the Trusted Key field. Typically, the only time an additional entry is added occurs when the Trusted key list is used with multicast authentication. Such is the case because no explicit trusted key entry is associated with the multicast option.
Specify additional trusted keys that this media server can use to authenticate time messages, if required by any of the other servers.
Use a blank space as a delimiter if there is more than one key (for example, 2 3 6 to specify valid keys 2, 3, and 6). These numbers are associated with encryption codes in a "keys" file (see step 5).
Request key: allows an administrator to send a remote query request. Only 1 key is allowed in this field.
Control key: allows an administrator to query and request changes to an NTS. Only 1 key is allowed in this field.
Provide a keys file: If you specify keys in steps 2 or 3, you must provide a file named keys.install to allow the media server to communicate with the NTS.
If a new keys.install file is to be used, upload or create it now if possible. See Providing the keys.install file below.
Note: If you upload the keys file later, you have to run the Configure Server wizard again to have the system recognize it. Click Continue to page through the wizard until you come to this screen. Specify the keys file location, then Continue through the end of the wizard to update the system files.
After the keys.install file is uploaded, select the location where it resides.
Files you upload reside in the /var/home/ftp subdirectory.
If a keys file is not used, or if the correct keys.install file is already installed, select the option to not install a new keys file.
Note: After NTP is enabled, time changes greater than 15 minutes will disrupt the synchronization with the NTS and NTP will shut down. You need to set the server's clock now so that synchronization can work.
If you do not install a key file, click Continue.
If encryption between the NTS and Avaya media server is to be used for additional security, you must provide a keys.install file that specifies for each key:
the key number
the encryption type
the key code
The keys file can be installed in several ways:
Upload the keys file: If a keys.install file was previously created on or downloaded to the services laptop or another computer on the network, it can be installed as follows:
In the main menu under Miscellaneous, click the Upload Files to Server link.
Locate the keys.install file on your computer or network, then click Load File. The file is uploaded to the media server's FTP directory.
Create the keys file: If the keys file is short, the network administrator can create one now during configuration if needed:
On a directly connected laptop or other computer, create a flat-text file named keys.install with the correct keys information using any ASCII application.
Next, upload it using the Upload Files to Server screen as described above.
Download or copy the keys file: Longer files may be transferred from the network time server to the Avaya media server as follows:
Using either the Download Files to Server screen or the Transfer files using FTP procedure to access the keys file listed on your preinstallation worksheet.
In both cases, the file is transferred to the media server's FTP directory.