No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

FusionAccess 6.5 Alarm Handling 04

Rate and give feedback:
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
1000050 Time of the System Is Inconsistent with That of the Domain Controller

1000050 Time of the System Is Inconsistent with That of the Domain Controller

Description

The alarm module checks the time of the ITA server and the time mapping to the domain name, IP address of the primary domain controller, and IP address of the secondary domain controller every 2 minutes by default. This alarm is generated when the time interval between the ITA server and any of the preceding addresses is more than 4 minutes for three consecutive times. This alarm is cleared when the time interval between the ITA server and any of the preceding addresses is less than 4 minutes.

Attribute

Alarm ID

Alarm Severity

Auto Clear

1000050

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.

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

  • If the time of the ITA server is different from that of the domain controller, the system may fail to provision and allocate VMs.
  • The clock source of the WI server is the same as that of the ITA server. When the time of the WI server is different from that of the domain controller, users may fail to log in to the desktops.

Possible Causes

  • The NTP service of the domain controller in the first domain is faulty.
  • The clock synchronization between the infrastructure VM and the first domain configured in the system is faulty.
  • The time of the domain involved in the alarm is different from that of the first domain configured in the system.

Procedure

  1. Log in to an ITA server as user gandalf and run the following command to switch to user root:

    su

  2. Run the following command to query the clock source configured for the ITA server, that is, the domain name of the first domain configured in the system:

    cat /opt/HA/module/harm/plugin/script/ntpinfo

  3. Check whether the domain involved in this alarm is the first domain configured in the system.

    • If yes, go to 4.
    • If no, go to 17.

  4. Check the OS of the domain controller in the domain involved in this alarm.

    • If the OS is Windows, go to Step 5.
    • If the OS is Linux, go to Step 10.

  5. Log in to the domain controller using the domain account and choose Start > Administrative Tools > Services to open the service list.
  6. Right-click Windows Time and choose Restart from the shortcut menu.
  7. Choose FusionAccess > Alarm Monitoring 2 minutes later to check whether the alarm still exists.

    • If yes, go to Step 8.
    • If no, no further action is required.

  8. Restart the domain controller of the domain.
  9. Choose FusionAccess > Alarm Monitoring 2 minutes later to check whether the alarm still exists.

    • If yes, go to 12.
    • If no, no further action is required.

  10. Log in to the LiteAD server as user gandalf and run the following command to restart the NTP service:

    sudo service ntp restart

  11. Choose FusionAccess > Alarm Monitoring 2 minutes later to check whether the alarm still exists.

    • If yes, go to 12.
    • If no, no further action is required.

  12. Log in to two ITA servers as user gandalf and run the following command to switch to user root:

    su

  13. Run the following command to query the time of the ITA server:

    date

  14. Check whether the time of the ITA server is consistent with that of the domain controller involved in this alarm.

    Note: If the time zones are different, convert the time zones to the same ones and compare the time.
    • If yes, contact technical support engineers.
    • If no, go to Step 15.

  15. Run the following command to forcibly synchronize the time between the ITA server and the clock source:

    ntpdate -u domain name of the first domain configured in the system

    If the time fails to be synchronized, run the following commands to retry the synchronization:

    ntpdate -u IP address of the active domain controller in the first domain configured in the system

    ntpdate -u IP address of the standby domain controller in the first domain configured in the system

  16. Choose FusionAccess > Alarm Monitoring 2 minutes later to check whether the alarm still exists.

    • If yes, contact technical support engineers.
    • If no, no further action is required.

  17. Contact the administrator to configure the clock source for the domain involved in this alarm. Ensure that the clock source of the domain is the same as that of the first domain configured in the system.
  18. Choose FusionAccess > Alarm Monitoring 2 minutes later to check whether the alarm still exists.

    • If yes, contact technical support engineers.
    • If no, no further action is required.

Translation
Download
Updated: 2019-10-11

Document ID: EDOC1100061083

Views: 4033

Downloads: 14

Average rating:
This Document Applies to these Products
Related Documents
Related Version
Share
Previous Next