Configuring NTP Server Parameters on Multiple Network Elements
Use this procedure to configure the same NTP server parameters on multiple network elements. It is highly recommended that PSM and all NEs in the network use NTP servers for obtaining the time in order to avoid time discrepancies.
The PSM server treats each network element separately, launching individual tasks to communicate with and configure each NE. A task failure for one NE does not affect tasks for the other NEs.
PSM connects to each NE using the login credentials that you supplied when you connected to the PSM server. Therefore each NE must be configured with these same login credentials for this procedure to be successful.
PSM connects to each
NE using the applicable protocol for that NE type. When connecting
to an NE over SSH (e.g. BTI7800), the SSH key provided
by the NE must match the expected key (if the key was previously stored).
If the key supplied by the NE does not match the expected key, the
task times out and fails. Under normal situations, the supplied key
matches the expected key. However, if the NE operating system has
been re-installed, the keys might not match. In this situation, you
will need to remove the expected key from the PSM server
~/.ssh/known_hosts file. One method of doing this is to issue the following Linux
command from a Linux shell on the PSM server machine:
# sed -i '/NE_IP_address/d' ~/.ssh/known_hosts
NE_IP_address is the IP address of the NE.
This procedure is supported for the BTI7000 Series, the BTI7800 Series, and the BTI800 Series NEs.
- To configure NTP server parameters, select one or more network elements from the main topology window or from the tree view.
- Right-click and select Scripts>Network Elements>Configure
The "Configure NTP" dialog appears with the list of selected network elements at the top:
The "Selected Network Element(s)" box has limited space to display network elements. In some situations where the number of selected network elements is large, some network elements might not be displayed. This is normal behavior and does not affect script execution, which runs for all selected network elements, regardless of whether they appear in the list or not.
- Configure the IP address of the Primary NTP Server and the Secondary NTP Server as desired.
Not all network elements under management use the concept of primary and secondary NTP servers.
The BTI7000 Series network element keeps a list of up to five NTP servers to use. This procedure appends the new NTP servers to the existing list, with the specified Primary NTP Server added ahead of the specified Secondary NTP Server. From this list, the NE uses the server with the best stratum value. If you try to add an NTP server when the number of NTP servers is at the maximum number, the task will fail.
The BTI7800 Series network element manages a list of NTP servers with no arbitrary limit. This procedure appends the new NTP servers to the existing list, with the specified Primary NTP Server added ahead of the specified Secondary NTP Server. The NE tries to use the NTP server at the beginning of this list first. If it fails, then the next NTP server in the list is tried, and so on.
The BTI800 Series network element keeps a list of up to three NTP servers to use. This procedure appends the new NTP servers to the existing list, with the specified Primary NTP Server added ahead of the specified Secondary NTP Server. The NE tries to use the NTP server that is specified as the Preferred Server. The Preferred Server is designated in the System Information panel. If you try to add an NTP server when the number of NTP servers is at the maximum number, the task will fail.
- When you are finished, click OK.
The PSM server launches a task for each NE being configured.
- Look at the Tasks window to verify that each task has
completed successfully. A "Configure NTP" task might fail if the NTP
server being added is already on the NE list of servers to use.
In this example, the "Configure NTP" task was successful for
A task might fail if the primary or secondary NTP server being added already exists in the NTP server list on that NE. No configuration changes take effect on any failed NE.
This procedure is now complete.