1. Introduction, Setting

1-24

Because there is no NTP server that can be accessed from within the intranet, the sensor's clock and the manager's clock cannot be synchronized.

NetSkateKoban manages the terminal detection time based on the "terminal detection timestamp" included in the terminal detection information sent from the sensors.

If the clocks of the sensor and the manager become unsynchronized, issues may occur such as reduced reliability of the history information, terminals not appearing on the network map even when detected, or appearing only briefly before disappearing.

To prevent such issues, the standard configuration is to use an NTP service to synchronize the clocks of the manager and the sensors. However, if using an NTP service is absolutely not possible, starting from Ver.3.1, it has become possible to manage terminal detection timestamps using only the manager's clock instead of the sensor's clocks.

As for the specific configuration procedure, set the DETECTED_TIMESTAMP entry in the manager's configuration file config/manager/terminalDetection.conf to MANAGER. ("NetSkateKoban v5.3 Reference Manual Administration Guide" "13.2.15 config/manager/terminalDetection.conf")

With this setting, the terminal detection timestamp sent from the sensors will be ignored, and the manager will instead use its own clock at the moment the notification is received to manage the terminal detection time.

[When Using the Manager’s Clock]

DETECTED_TIMESTAMP=MANAGER

[When Using the Sensor’s Clock (Default Setting)]

DETECTED_TIMESTAMP=SENSOR