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).
1007005 LiteAD Servers Are Inconsistent

1007005 LiteAD Servers Are Inconsistent

Description

The alarm module checks the system every 5 minutes. This alarm is generated when the alarm module detects data inconsistency between active and standby LiteAD servers for four consecutive times (about 20 minutes). The ITA automatically clears the alarm when the alarm module detects data consistency between active and standby LiteAD servers and reports recovery information.

Attribute

Alarm ID

Alarm Severity

Auto Clear

1007005

Major

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 data is inconsistent between active and standby LiteAD servers, login to the VMs that are newly created or restarted may fail.

Possible Causes

  • The network malfunctions.
  • The LiteAD server is abnormal.

Procedure

  1. Log in to the server where the alarm is generated using an administrator account and run the arping -c 3 -f -D -I eth0 IP address of the server where the alarm is generated command to check whether an IP conflict occurs.

    • If yes, go to Step 2.
    • If no, go to Step 4.

      If the information similar to the following is displayed, no IP conflict occurs:

      ARPING 192.168.162.11 from 0.0.0.0 eth0 
      Sent 3 probes (3 broadcast(s)) 
      Received 0 response(s) 
      (Note: The IP addresses are only examples. Use the actual IP addresses.)     

      If the information similar to the following is displayed, an IP conflict occurs:

      ARPING 192.168.162.11 from 0.0.0.0 eth0 
      Unicast reply from 192.168.162.11 [12:6E:D4:AB:CD:EF]  1.022ms 
      Sent 1 probes (1 broadcast(s)) 
      Received 1 response(s) 
      (Note: The preceding IP addresses and MAC addresses are only examples. Use the actual IP addresses and MAC addresses.)     

  2. Log in to the server that causes the IP conflict, shut down the server or change the server IP address, and run the arping -c 3 -f -D -I eth0 IP address of the server where the alarm is generated command again on the server where the alarm is generated to check whether the IP conflict persists.

    • If yes, contact Huawei technical support.
    • If no, go to Step 3.

  3. Choose FusionAccess > Alarm to check whether the alarm still exists after 10 minutes.

    • If yes, go to Step 4.
    • If no, no further operation is required.

  4. Log in to the LiteAD server as user gandalf, and check whether the peer server network is normal. Run ping -c 3 IP address of the peer server to check whether the communication is normal.

    • If yes, go to Step 6.
    • If no, go to Step 5.

      The communication is normal if the command output is as follows:

      PING 192.168.190.2 (192.168.190.2) 56(84) bytes of data. 
      64 bytes from 192.168.190.2: icmp_seq=1 ttl=64 time=0.047 ms 
      64 bytes from 192.168.190.2: icmp_seq=2 ttl=64 time=0.057 ms 
      64 bytes from 192.168.190.2: icmp_seq=3 ttl=64 time=0.058 ms 
      (Note: The IP addresses are only examples. Use the actual IP addresses.)     

  5. Locate and rectify the network fault based on the actual situation on site.
  6. Log in to the LiteAD server as user gandalf, and run date to check whether the time difference between the active and standby LiteAD servers is not greater than 5 minutes.

  7. Log in to the standby LiteAD server using an administrator account and run the date -s The system time of the active LiteAD server to synchronize the system of the standby LiteAD server to the active LiteAD server.

  8. Choose FusionAccess > Alarm to check whether the alarm still exists after 10 minutes.

    • If yes, go to Step 9.
    • If no, no further operation is required.

  9. Log in to the standby LiteAD server using an administrator account and run the rcsamba-ad restart to restart the LiteAD service.

  10. Choose FusionAccess > Alarm to check whether the alarm still exists after 10 minutes.

    • If yes, go to Step 11.
    • If no, no further operation is required.

  11. Log in to the active LiteAD server using an administrator account and run the rcsamba-ad restart to restart the LiteAD service.
  12. Choose FusionAccess > Alarm to check whether the alarm still exists after 10 minutes.

    • If yes, contact Huawei technical support.
    • If no, no further operation is required.

Related Information

None

Translation
Download
Updated: 2019-10-11

Document ID: EDOC1100061083

Views: 4031

Downloads: 14

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