Symmetricom ND-SERIES User Manual page 35

1. The WinDiscovery application has been open for too long and the clock configuration(s)
has(have) changed. For example, this can occur if the DHCP server has issued new/refreshed
addresses. Close the WinDiscovery application and restart.
2. The discovery process was not complete before selecting clock(s). After selecting "Discover"
button, wait until the discovery status indicates 100% completion.
3. Verify that the physical network cables and equipment and configuration for UDP have not
changed.
4. Verify that you are currently the only user accessing the clock via WinDiscovery or telnet.
5. The network may currently be experiencing heavy traffic which is reducing bandwidth and/or
causing collisions with the UDP messages/packets between the clock(s) and WinDiscovery.
Since delivery of UDP messages are not guaranteed, this can cause WinDiscovery to not receive
the latest configuration or status packets, and thus show outdated or garbled information. In
some cases, the clock may not be discovered and displayed in the WinDiscovery device tree. In
others, previously discovered clocks may no longer be accessible or responding.
• Press the "Discover" button again and wait until the discovery process completes.
• Close the current WinDiscovery session and restart the WinDiscovery application.
• Take steps to increase the bandwidth and reduce network traffic.
• If this is an ongoing problem, consider the Telnet configuration method or remove the clock
system to an isolated LAN.
Problem: Clock appears in RED text under WinDiscovery device tree.
Problem: Clock is being assigned an IP address of 169.254.xxx.xxx
Problem: Clock not maintaining its assigned IP address.
Problem: Clock function is erratic. Clock periodically resets itself.
Problem: Clock is showing an "Error" field under the status window in WinDiscovery.
Possible reasons/solutions:
1. Incorrect network configuration may be causing the clock to receive a fallback IP address and or
perform soft restarts. 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. Determine the cause of fallback IP address and resolve issue. View the
error status field under the status window to help determine the cause of why the clock received
a 169.254.xxx.xxx. Near the bottom of the Status window the error will be displayed. (If there is
no error the text box will not be displayed.)
[Note: Devices which have been assigned a fallback IP address of 169.254.xxx.xxx will be
displayed in the main WinDiscovery window with
configuration.]
When the Ethernet interface is initialized the ND 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 ND 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.
ND Clocks User Manual - Rev 2.0.1 Sep-08
RED text, indicating a problem with the
31
®
Symmetricom , Inc.