1000017 Communication Between the System and the NTP Server Is Abnormal
Description
The alarm module checks the communication between the system and the Network Time Protocol (NTP) server every 2 minutes. This alarm is generated when the alarm module detects that the communication between the system and the NTP server is abnormal for three consecutive times. This alarm is cleared when the alarm module detects that the communication between the system and the NTP server is normal.
Attribute
Alarm ID Alarm Severity Auto Clear
1000017
Critical
Yes
Parameters
Name Meaning
Alarm ID
Identifies an alarm. Each alarm is uniquely identified by an alarm ID and an alarm name.
Alarm Severity
Indicates the severity of an alarm. Value:
Critical: indicates that a fault affecting services provided by the system occurs. You need to rectify the fault immediately. If a device or resource is faulty, rectify it immediately even if the fault occurs during non-working hours.
Major: indicates that a fault affecting the service quality of the system occurs. You need to rectify the fault immediately. If the service quality of a device or resource is degraded, rectify it immediately during working hours.
Minor: indicates a fault that does not affect service quality. To prevent more serious faults, this type of alarm needs to be observed or handled if necessary.
Warning: indicates a fault that may affect service quality. This type of alarm must be handled based on the error type.
Alarm Name
Identifies an alarm. Each alarm is uniquely identified by an alarm ID and an alarm name.
Object Type
Specifies the type of the object for which the alarm is generated.
Alarm Object Name Specifies the name of the object for which the alarm is generated.
Component Type
(This parameter exists only in FusionManager.)
Specifies the name of the component for which the alarm is generated.
Generation Time
Specifies the time when the alarm is generated.
Clear Time
Specifies the time when the alarm is cleared.
Clear Mode
Specifies whether the alarm is manually or automatically cleared.
Operation Specifies the operation that can be performed on the alarm.
Value: Manually Clear Alarm
Impact on the System
IT adapter (ITA) service provisioning is affected. Users cannot log in to VMs from thin clients (TCs) or software clients (SCs).
Users cannot log in to VMs from the web interface (WI).
Possible Causes
The network is faulty.
The NTP server is not running properly.
The NTP server is set incorrectly on a Linux server.
Procedure
Check the OS of the server on which the alarm is generated.
If the OS is Windows, go to Step 2.
If the OS is Linux, go to Step 7.
Log in to the Windows server using a domain account, and check whether communication between the Windows server and the NTP server is normal.
Choose Start > Run.
Enter cmd in the text box, and click OK to access the command-line interface (CLI).
Run ping NTP server IP address to check whether the communication is normal. (If the Windows server is not an AD server, the NTP server IP address is the IP address of the active AD server.)
If yes, go to Step 5.
If no, go to Step 3.
The communication is normal if the command output is as follows:
Pinging 192.168.90.102 with 32 bytes of data:
Reply from 192.168.90.102: bytes=32 time<1ms TTL=128
Reply from 192.168.90.102: bytes=32 time<1ms TTL=128
Reply from 192.168.90.102: bytes=32 time<1ms TTL=128
Reply from 192.168.90.102: bytes=32 time<1ms TTL=128
(Note: The IP addresses are only examples. Use the actual IP addresses.)
Locate and rectify the network fault based on the actual situation on site.
Choose FusionManager > Monitoring or FusionAccess > Alarm to check whether the alarm still exists.
If yes, go to Step 5.
If no, no further operation is required.
Restart the Windows Time service.
Choose FusionManager > Monitoring or FusionAccess > Alarm to check whether the alarm still exists.
If yes, contact Huawei technical support.
If no, no further operation is required.
Log in to the Linux server using a common account, and run ping AD server IP address to check whether communication between the Linux server and the AD server is normal.
If yes, go to Step 10.
If no, go to Step 8.
The communication is normal if the command output is as follows:
PING 192.168.90.102 (192.168.90.102) 56(84) bytes of data.
64 bytes from 192.168.90.102: icmp_seq=1 ttl=64 time=0.019 ms
64 bytes from 192.168.90.102: icmp_seq=2 ttl=64 time=0.016 ms
64 bytes from 192.168.90.102: icmp_seq=3 ttl=64 time=0.027 ms
64 bytes from 192.168.90.102: icmp_seq=4 ttl=64 time=0.035 ms
64 bytes from 192.168.90.102: icmp_seq=5 ttl=64 time=0.020 ms
64 bytes from 192.168.90.102: icmp_seq=6 ttl=64 time=0.025 ms
Locate and rectify the network fault based on the actual situation on site.
Choose FusionManager > Monitoring or FusionAccess > Alarm to check whether the alarm still exists.
If yes, go to Step 10.
If no, no further operation is required.
Check whether the NTP service on the Linux server is configured properly. Enter sh /opt/InstallTools/startTools to go to the Linux installation page, select Configuration, press Enter, select Network Time (NTP), and check whether the NTP server IP address on the right is the IP address of the active and standby AD servers.
If yes, contact Huawei technical support.
If no, set the NTP server IP address to the IP address of the activer and standby AD servers.
Choose FusionManager > Monitoring or FusionAccess > Alarm to check whether the alarm still exists.
If yes, contact Huawei technical support.
If no, no further operation is required.
