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 V100R006C20 Alarm Handling 05 (FusionSphere 6.3.1)

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).
1000018 System Time Changes

1000018 System Time Changes

Description

On Windows, the alarm module checks the system time once every 2 minutes by default. This alarm is generated when the alarm module detects that the system time changes.

On LiteAD servers, the alarm module checks the system time once every 2 minutes by default. When current system time is more than 5 minutes slow compared to the system time recorded on the last check, this alarm is generated. For example, the system time recorded on the last check is 9:05:00, but current system time is 9:00:00.

On Linux which are not LiteAD servers, the system time is synchronized from an AD server or another NTP server every 2 minutes by default. After the time synchronization is complete, comparison between the time before and after the synchronization is performed. This alarm is generated when the time after the synchronization is more than 3 minutes slow compared to the time before the synchronization. For example, the time before the synchronization is 9:05:00, but the time after the synchronization is 9:00:00. No alarm is generated if the time after the synchronization is fast because services are not affected. This alarm is cleared manually when the system time is correct.

Attribute

Alarm ID

Alarm Severity

Auto Clear

1000018

Major

No

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. When the system time changes, you have to manually clear the alarm.

Operation

Specifies the operation that can be performed on the alarm.

Value: Manually Clear Alarm

Impact on the System

The timer running, heartbeat signal reporting, and VM status information processing are affected.

Possible Causes

  • The time of the upper-layer clock source server changes.
  • Local system time changes.
  • The local system time zone changes.
  • The server is incorrectly changed.

Procedure

  1. For a Windows server, go to Step 2; for a LiteAD server, go to Step 5;for a Linux server which is not LiteAD, go to Step 8.
  2. Check whether the time of the upper-layer clock source server changes.

    • If yes, see Fault Management > Troubleshooting > Handling Critical Faults > System Time Errors to resolve the problem.
    • If no, go to Step 3.

  3. Check whether the local system time changes.

    • If yes, check whether the local server is the active directory (AD) server.

  4. If the local server is an AD server, see Fault Management > Troubleshooting > Handling Critical Faults > System Time Errors to resolve the problem.
  5. If no, restart the Windows Time service on the local server, and run the following commands on the command-line interface (CLI) to synchronize time:

    net stop w32time

    net start w32time

    w32tm /resync

    Then go to Step 11.

  6. On the Windows server, choose Start > Control Panel > Clock > Language and Region > Date and Time > Change the time zone. In the Date and Time window that is displayed, click the Date and Time tab and Change the time zone to check whether the time zone is correct. If the time zone is incorrect, change it to the correct one and go to Step 11. If the time zone is correct, go to Step 11.
  7. Use the administrator account to log in to the server, and check whether a time source is configured for the server.

    • If yes, run ntpdate -u IP address of the time source to synchronize the system time of the server to the time source, then go to Step 7.
    • If no, go to Step 6.

  8. Use the administrator account to log in to the server, and run cat /etc/samba/ad.conf to check whether the server is the active LiteAD server or the standby LiteAD server.

    • If the value of ispdc is "Yes", run date -s Current Time to configure the correct system time.
    • If the value of ispdc is not "Yes", run ntpdate -u IP address of the active LiteAD server to synchronize the system of the standby LiteAD server to the active LiteAD server.

  9. Check the additional alarm information of time change alarm. The format is as follows: "Additional information: Component name = 192.168.6.26, IP address = 192.168.6.26, time change = 495 (s)." If the time change is more than 1 day, run service ntp restart and rcsamba-ad restart in order.
  10. If the WI, HDC, or license service is abnormal, see the WI, HDC, or license service alarm handling to rectify the fault and restart the service.
  11. If no service exception alarm exists but the login to shared desktop fails or the user VM status on the FusionAccess Portal is incorrect, log in to the server on which time changes and run the shell command to restart the WI, HDC, and license services. The commands for restarting the WI, HDC, and license services are service WIService restart, service HDCService restart, and service LICService restart respectively.
  12. Check the additional alarm information of time change alarm. The format is as follows: "Additional information: Component name = 192.168.6.26, IP address = 192.168.6.26, time change = 495 (s)." The time change plus the alarm generation time is later than the current time. For example, if the alarm is generated on 8:00:00, the time change is 1 hour, the current time is later than 9:00, and only time change alarm exists in the system without other service exceptions, no processing is required. Otherwise, restart the WI, HDC, and license services on the server. For the restart commands, see the WI, HDC, and license service alarm handling.
  13. Choose FusionManager > Monitoring or FusionAccess > Alarm to manually clear the alarm.

Related Information

None

Download
Updated: 2019-03-01

Document ID: EDOC1100010511

Views: 20004

Downloads: 12

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