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).
1010001 AUS Server Abnormal

1010001 AUS Server Abnormal

Description

After startup, the AccessAgent Update Server (AUS) sends a heartbeat message to the IT adapter (ITA) every 2 minutes. The heartbeat message contains CPU usage and memory usage. This alarm is generated when the ITA does not receive the AUS heartbeat message for three consecutive times. This alarm is cleared when the ITA receives the AUS heartbeat message again.

Attribute

Alarm ID

Alarm Severity

Auto Clear

1010001(1009005)

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 alarms needs to be observed or handled if necessary.
  • Warning: indicates a fault that may affect service quality. This type of alarms 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 Name

(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.

Impact on the System

  • The AccessAgents of user VMs cannot be upgraded using the AUS server.

Possible Causes

  • IP address conflict.
  • The IP address has been changed. The alarms generated by the IP address must be manually cleared.
  • The AUS server is not running properly.
  • The network is faulty.

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 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, 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 FusionManager > Monitoring or FusionAccess > Alarm to check whether the alarm still exists.

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

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

    • If yes, go to Step 7.
    • 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. Choose FusionManager > Monitoring or FusionAccess > Alarm and check whether the alarm exists.

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

  7. Log in to the AUS server as an administrator and run the shell command service AUSService status to check whether the AUS service is normal.

  8. Run the shell command service AUSService restart to restart the AUS server.

    Repeat Step 7 to check whether the AUS service is normal.

    • If yes, go to Step 9.
    • If no, contact Technical Support.

  9. Choose FusionManager > Monitoring or FusionAccess > Alarm and check whether the alarm exists.

    • If yes, contact Technical Support.
    • If no, no further action is required.

Related Information

None

Download
Updated: 2019-03-01

Document ID: EDOC1100010511

Views: 19985

Downloads: 12

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