Action | Take action based upon Reason code:
noNtpServerConfigured (1) - Create at least one NTP client object with an IP address of a known NTP server.
allNtpServersOutOfSync (2) - If all NTP entries suddenly transition from to OUTOFSYNC, do the following, as applicable:
View NTP SERVER ADMIN screen to verify the NTP clients are properly configured.
Check for connectivity by pinging the IP address of all configured NTP servers.
If you do not ping successfully, investigate possible causes: Network outage, disconnected cable, NTP servers are down.
Check DEBUG and SYSTEM logs for NTP messages which may indicate invalid NTP packets received.
If the above condition is not present and no error messages exist in the DEBUG and SYSTEM logs, a "glitch" in the network may have occurred, or NTP packets were discarded for some reason. Allow a reasonable amount of time to pass (depending upon how long the clients have been out of sync) for NTP clients to sync back up to NTP servers. If unsure, contact Sonus TAC for guidance. |
Impact | The impact is based upon the sonusNtpDownReasonCode:
noNtpServerConfigured(1)
No NTP client objects were created. If fault is present from boot-up, call admission is suspended - no calls are allowed since the NTP start time is incorrect.
allNtpServersOutOfSync(2) If one or more NTP servers were up and in sync prior to receiving this alarm, the node timing for this particular node may drift away from the NTP network timing at a rate based upon the accuracy of the internal clock.
During this fault condition, an NTP client may simply be synced up with its configured server and slowly drifting back toward the correct NTP time. |