
ND-CLK User Manual- Rev 1.0.1 - Sep-08
36
Symmetricom
®
, Inc
[Note: Devices which have been assigned a fallback IP address of 169.254.xxx.xxx
will be displayed in the main WinDiscovery window with
RED
text, indicating a
problem with the configuration.]
When the Ethernet interface is initialized the NTD clock will verify that the IP address
(either static or assigned by DHCP) is not being used by another device on the network.
If a conflict is found the NTD clock will default to a 169.254.xxx.xxx address. The IP
address that caused the error is saved and returned as an error to WinDiscovery. This
error status is available to the user via the Status window on WinDiscovery.
•
If static IP addressing is being used the original conflicting static IP
address can be restored by doing a soft restart of the NTD clock using
either WinDiscovery or telnet prior to changing any other configuration
parameters.
[IMPORTANT NOTE: if the configuration of the network clock is changed
while a 169.254.xxx.xxx is being used (for example: changing the Time Zone
offset), then the current 169.254.xxx.xxx address will become the permanent
static address and the original conflicting static address is lost. At this point,
it is necessary to manually change the static IP address to one that does not
conflict, or you may do a “Reset Configuration” to restore the system to
factory default settings.]
•
If DHCP was selected and the NTD fell back to a 169.254.xxx.xxx
address approximately every 10 [depending upon the “Advanced Settings”
values] minutes the Ethernet interface will be reinitialized and the NTD
clock will attempt to get an IP address from the DHCP server. If the NTD
is successful, the error will be cleared and the new address from the DHCP
server will be used. If a discovery was done using WinDiscovery or telnet
was used this initialization will be delayed by 2 hours.
Problem: Clock is unable to find NTP reference, either Primary or Secondary Source.
Problem: Status LED is ON.
Problem: Status in WinDiscovery says ‘Unsynchronized’
Possible reasons/solutions:
1. Verify that the NTP server(s) specified are reachable, communicating, and are not
flagging their reported time as invalid. Use a PC-based SNTP client application
to verify the server(s) if necessary.
2. Verify that a gateway/router/firewall has been configured that allows the clock to
communicate outside of its local network.
3. Verify that the IP address configured for the clock is correct. If you manually
enter (or DHCP assigns) an IP address that already exists on the network, this will
create an IP address conflict. The clock will reset its address (fallback) to one
within the link-local address space (169.254.xxx.xxx). If you see that the IP
address starts with 169.254, obtain a new IP address for the clock or resolve the