The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
Table A-1 describes issues that may arise with respect to time synchronization using when using the Network Time Protocol (NTP), how the issues can be addressed, and how they are reported in the Health Dashboard.
The following notes apply to NTP time synchronization and the Health Dashboard:
•On the Health Dashboard, a critical state can be set only if it is reported by VSMS. Any other reported conditions generate warnings.
•It is possible for warnings sent at startup to be lost, especially if VSOM and VSMS are co-resident on the same platform.
•The cron synchronization process runs every 10 minutes.
•The Health Dashboard reports event counts.
•You must delete events manually; they are not deleted automatically when the condition clears.
|
|
||||
---|---|---|---|---|---|
|
|
|
|
|
|
Startup |
NTP not configured, or not reachable |
Down |
none |
trap: mediaServerStateChange state: scJumpForward |
VSMS is down/critical. System clock appears to have jumped forward by more than four hours or server has been down for a long time. The VSMS server is not operational unless the clocks are synchronized. |
Startup |
NTP not configured, or not reachable SC > TLR (less than 4 hours) |
Up |
none |
No trap |
NA |
Startup |
NTP not configured, or not reachable SC < TLR |
Up, NTP daemon not started |
set to TLR+2 minutes |
trap: mediaServerStateChange state: scJumpBackward |
VSMV up, warning. System clock appears to have jumped backward. The system identified a recording with a future time stamp |
Startup |
NTP is configured but it is not reachable any |
Up |
none |
trap: mediaServerStateChange state: ntpUnreachable |
VSMS up, warning. NTP server is not reachable. (Other traps may also be reported.) |
Startup |
NTP configured and reachable NTP > TLR + 4 hours, and system time does not match NTP |
Down |
none |
trap: mediaServerStateChange state: scJumpForward |
VSMS down, critical. System clock appears to have jumped forward by more than four hours or server has been down for a long time. The VSMS server is not operational unless the clocks are synchronized. |
Startup |
NTP configured and reachable NTP > TLR (less than 4 hours) or few minutes behind, and system time does not match |
Up |
set to NTP |
trap: mediaServerStateChange state: scJumpForwardLimited If system time is in sync with NTP, then no adjustments are needed and no traps sent |
VSMS up, warning. System clock has jumped forward. NTP was greater than TLR by not more than 4 hours and system clock time was significantly different from NTP server time. |
Startup |
NTP configured and reachable NTP < TLR more than few minutes |
Up |
set to TLR+2 minutes |
trap: mediaServerStateChange state: scJumpBackward |
VSMS up, warning. System clock appears to have jumped backward. The system identified a recording with a future time stamp. |
Cron |
NTP reachable NTP different from HC3 2 minutes or more |
Up |
NTP |
trap: clockAdjustmentStatusChange state: hcAdjToNtp |
VSMS up, warning. NTP server is reachable. Hardware clock was more than a few minutes different from NTP. The hardware clock is adjusted to NTP. |
Cron |
NTP not configured SC different from HC 2 minutes or more |
Up |
SC -> HC |
trap: clockAdjustmentStatusChange state: hcAdjToSc |
VSMS up, warning. NTP server is not configured. System clock is few minutes more than the hardware clock. Hardware clock is adjusted to the system time |
Cron |
NTP configured NTP not reachable |
UP, NTP daemon is killed if it was running |
none |
trap: clockAdjustmentStatusChange state: ntpUnreachable |
VSMS up, warning. NTP server is not reachable. |
Cron |
NTP became reachable after it was not reachable NTP < SC (more than few minutes) |
Up, NTP daemon not started |
none |
trap: clockAdjustmentStatusChange state: scBehindNtp |
VSMS up, warning. NTP server is reachable (after it was inaccessible). System clock is behind NTP and NTP daemon is not running |
Cron |
NTP became reachable after it was not reachable NTP > SC (less than 4 hours but more than couple minutes) |
Up, NTP daemon started |
NTP |
trap: clockAdjustmentStatusChange state: scJumpForward |
VSMS up, warning. NTP is reachable (after it was inaccessible).NTP daemon has been started. System clock is about to jump forward |
Cron |
NTP became reachable after it was not reachable NTP > SC + 4 hours |
Up, NTP daemon not started |
none |
trap: clockAdjustmentStatusChange state: scOutOfSyncNtp |
VSMS up, warning. NTP server is reachable (after it was inaccessible). System clock is out of sync with NTP and NTPD daemon is not running |
Cron |
NTP became reachable after it was not reachable NTP, SC, HC are in synch - meaning that the difference between system and NTP is less than few minutes |
Up, NTP daemon started if not already running |
none |
trap: clockAdjustmentStatusChange state: ntpreachable |
VSMS up, warning. NTP server is reachable (after it was inaccessible). NTP daemon has been started. |
1 SC = system clock. 2 LTR = time of last recording. For example, NTP > TLR + 4 hours means that the system time may have jumped ahead more than four hours. Refer to the Health Dashboard Notification column for more information. 3 HC = hardware clock |