Time synchronization mode between WDM products and standard NTP servers

5

It is a synchronization mode between NMS time and NE time.

With the time synchronization function, the NE time is kept consistent with the NMS time. This allows the NMS to record the correct time at which alarms occur and the correct time at which abnormal events are reported by NEs.

When NEs report alarms and abnormal events to the NMS, the NMS records the time of alarms and events based on the NE time. If the NE time is incorrect, the generation time of alarms recorded on the NMS is also incorrect, which may cause troubles in fault locating. The same case happens to the generation time of abnormal events that are recorded in the NE security log. To ensure the accuracy of NE time, the NMS provides two time synchronization modes with the following servers: the NMS server and the standard NTP server.

Note:

The Web LCT improves the accuracy of NE time by synchronizing the NE time with the NMS time.

If synchronization with the NMS server is applied, all NEs use the NMS server time as the standard time, and can be synchronized with the NMS server manually or automatically. The NMS time refers to the time of the workstation where the NMS server resides or system time of the NMS server. This synchronization mode is easy and applies to a network with relatively low requirement on time accuracy.

If synchronization with the standard NTP server is applied, all NEs and the NMS are synchronized with the standard NTP server automatically. The standard NTP server can be the NMS server or a dedicated time server. This synchronization mode makes the NE time and NMS time accurate to 1/1000,000,000 seconds and applies to a network that has a high requirement on time accuracy.

Other related questions:
Synchronization modes between NMS time and NE time on WDM products
Synchronization modes between NMS time and NE time: With the time synchronization function, the NE time is kept consistent with the NMS time. This allows the NMS to record the correct time at which alarms occur and the correct time at which abnormal events are reported by NEs. When NEs report alarms and abnormal events to the NMS, the NMS records the time of alarms and events based on the NE time. If the NE time is incorrect, the generation time of alarms recorded on the NMS is also incorrect, which may cause troubles in fault locating. The same case happens to the generation time of abnormal events that are recorded in the NE security log. To ensure the accuracy of NE time, the NMS provides two time synchronization modes with the following servers: the NMS server and the standard NTP server. Note: The Web LCT improves the accuracy of NE time by synchronizing the NE time with the NMS time. If synchronization with the NMS server is applied, all NEs use the NMS server time as the standard time, and can be synchronized with the NMS server manually or automatically. The NMS time refers to the time of the workstation where the NMS server resides or system time of the NMS server. This synchronization mode is easy and applies to a network with relatively low requirement on time accuracy. If synchronization with the standard NTP server is applied, all NEs and the NMS are synchronized with the standard NTP server automatically. The standard NTP server can be the NMS server or a dedicated time server. This synchronization mode makes the NE time and NMS time accurate to 1/1000,000,000 seconds and applies to a network that has a high requirement on time accuracy.

Method used to synchronize the time between an NE and the standard NTP server.
The standard NTP service can automatically synchronize the NE time with the standard NTP server time.

How can I set NTP time synchronization for a camera?
After NTP is enabled for a camera, the camera will automatically time-synchronize with the NTP server. VCN3000 V100R002C00 For DHSDK-, GB/T 28181-, and AXISSDK-compliant cameras, you need to set NTP parameters on camera web pages. For HWSDK-, ONVIF-, and HIKSDK-compliant cameras, you need to enable the NTP time synchronization function on the OMU portal of the access server. After the NTP time synchronization function is enabled, the cameras will automatically time-synchronize with the server. The procedure is as follows: 1. Log in to the OMU portal of the MPU server as the Admin user. 2. Choose Maintenance > Unified Configuration and select the serve to which the camera mounts. 3. Set Module name to SCU and Parameter type to System property, and click Search. 4. In the search results, click Edit in the row where Parameter Name is NTPIPC and set Value to 1. 5. Click Save to enable the camera NTP time synchronization function. VCN3000 V100R001C01: 1. Log in to the server with which the camera synchronizes time as the root user. Note: The default password of the root user is Change_Me. 2. Run the chkconfig ntp command to check whether the NTP service is enabled on the server. If the following information is displayed, the NTP service has been enabled: ntp on Note: If a VMU two-node cluster is deployed, verify that the NTP service is enabled on both the active and standby nodes. If the NTP service has been enabled, go to step 3. If the NTP service is disabled, run the /etc/init.d/ntp restart command to enable the NTP service and go to the next step. 3. Change the NTP server IP address of the camera. If the Driver parameter of the camera is set to TEYES, skip this step. If the Driver parameter of the camera is set to T28181, DHSDK, or AXISSDK, log in to the camera web page and change the NTP server IP address to the server IP address. If the Driver parameter of the camera is set to HWSDK, HIKSDK, or ONVIF, perform the following steps: a. Log in to the C/S client. b. Choose Devices > Local Domain. c. Double-click the camera. The Configuration window is displayed. d. Choose System Settings > Time Settings. e. Enable the NTP and enter the NTP server IP address. f. Click OK.

Why is the time of the NTP client greatly different from that on a CE series switch that serves as an NTP server after the NTP clock is synchronized
An NTP client or NTP server sets the time zone, which cannot be synchronized by NTP. For example, the time on an NTP server is set to Beijing time (UTC+8), but an NTP client uses the system default UTC time zone. Therefore, the clock between the NTP client and NTP server is 8 hours apart after clock synchronization. You are advised to set the same time zone for the NTP server and NTP client during NTP clock synchronization. Otherwise, the clock between them is greatly different after the synchronization.

Time and time zone policy of the server BMC
The default time zone of iMana/iBMC is the GMT time zone. The time zone and time synchronization policy is as follows: iMana and iBMC of rack servers synchronize time with the BIOS every minute but does not synchronize the time zone. Therefore, if the iMana/iBMC time is different from the OS time, the difference is caused by different time zone settings. iMana/iBMC of blade servers (E9000 and E6000) synchronize time with the management module every hour. The management module supports NTP settings for time synchronization.

If you have more questions, you can seek help from following ways:
To iKnow To Live Chat
Scroll to top