NTP Server (NPP1)

Description

This probe verifies that the Network Time Protocol (NTP) server process is running. It simply checks that the process appears in the process table, no application level test is done to see if the server is actually working.

Release notes

Resource configuration interface

Resource parameters

This probe has no configurable parameters.

Performance graphs

This probe does not generate any performance graphs.

Alarms

This probe can report following alarm states:

• CRITICAL: Cannot connect to NTP process, probably not running
• WARNING: INIT: Initial synchronization ongoing
• WARNING: STEP: System time changed, trying to resynchronize
• WARNING: LOCL: Using local clock as fallback to provide time, not synchronized with any remote server

Possible causes

• NTP process is not running
• No remote NTP servers configured or available

Possible consequences

If the NTP server is not working:

• phones will not be able to synchronize their time/date, so the time shown on the phones may start to deviate or be entirely incorrect on newly installed phones.

During INIT and STEP warning state, no time is served to the phones. These states can resolve themselves after some time.

During LOCL warning state, the time served to the phones comes from the local clock of the SOP so it will be less accurate. This will be solved when the SOP can reach remote time servers again.

Possible actions

Use the SOP Shell to resync the NTP server (see FAQ: Time Problems).

This will also restart the NTP server if it is not running.