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).
1009002 UNS Data Synchronization Exception

1009002 UNS Data Synchronization Exception

Description

The alarm module checks the UNS server every 2 minutes. This alarm is generated when the alarm module detects that the UNS server is abnormal or unavailable for three consecutive times. This alarm is cleared when the alarm module detects that the UNS server becomes normal.

Attribute

Alarm ID

Alarm Severity

Auto Clear

1009002

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 type 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

Users cannot log in to VMs from thin clients (TCs) or software clients (SCs).

Possible Causes

  • The IP address has been changed. The alarms generated by the IP address must be manually cleared.
  • The UNS server is not running properly.
  • The NBI account of the ITA server that interconnect with the UNS server is locked.
  • The password of the ITA communication account is incorrect.
  • The network is faulty.

Procedure

  1. Check whether the NBI account for the UNS server to connect to the ITA server is locked. If the NBI account is locked, unlock it. If the ITA version is V100R005C30, see FusionAccess Software Installation > FusionAccess Initial Configuration > (Optional) Unlock NBI User and Reset the Password in the FusionAccess Desktop Solution V100R005C30 Software Installation Guide. If the ITA version is ProductVersion-XXXX, see Installation and Commission > Software Installation > FusionAccess Initial Configuration > (Optional) Unlock NBI User and Reset the Password in the FusionAccess Desktop Solution V100R006C20 Product Documentation.

    • If yes, unlock the NBI account.
    • If no, go to Step 2.

  2. Log in to the ITA server as user gandalf, and check whether the UNS server network is normal. Runping -c 3 IP address of the UNS server to check whether the communication is normal. Check if the WI name if right. WI name must be the wi cluster name configured in the ITA. If ITA of version V100R02C01 is configured, DESKTOPID is required.

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

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

  3. If the ITA version is V100R005C30 or ProductVersion-XXXX, check whether the ITA communication account password is set correctly.

    • If yes, go to Step 6.
    • If no, please login to FusionAccess and reconfigure the password of ITA account in UNS Information to ensure it is correct, and go to Step 5.

  4. Locate and rectify the network fault based on the actual situation on site.
  5. Choose FusionManager > Monitoring or FusionAccess > Alarm to check whether the alarm still exists.

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

  6. Check whether the UNS service status is normal.

    Open your browser, enter http://Service plan IP address of the UNS server/services/monitor/monitorStatus in the address box, and press Enter to check whether the UNS service status is normal.

    • If yes, go to Step 10.
    • If no, go to Step 7.

      If the output result which contains the following data is displayed on the browser or in the file that the browser asks you to download, the UNS service is normal:

      {"resultCode":0}

  7. Log in to the UNS server using an administrator account and run the shell command service WIService restart to restart the UNS service.
  8. Repeat Step 6 to check whether the UNS service is normal.

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

  9. Choose FusionManager > Monitoring or FusionAccessAlarm to check whether the alarm still exists.

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

  10. Run the shell command netstat -an | grep 4477 to check whether the status of port 4477 is listening.

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

  11. The firewall of the operating system where the ITA server is installed is disabled by default. The firewall may intercept messages returned by the UNS server. Check whether the firewall is disabled.

    • If yes, contact Huawei technical support.
    • If no, disable the firewall.

  12. Choose FusionManager > Monitoring or FusionAccess > Alarm to check whether the alarm still exists.

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

  13. Check whether the NBI certificates and passwords for the UNS server to connect to ITA servers are consistent. If the ITA version is V100R005C30, see FusionAccess Software Installation > (Optional) Deploying the UNS > Configuring the UNS in the FusionAccess Desktop Solution V100R005C30 Software Installation Guide. If the ITA version is ProductVersion-XXXX, see Installation and Commission > Software Installation > (Optional) Deploying the UNS > Configuring the UNS in the FusionAccess Desktop Solution V100R006C20 Product Documentation.

    • If yes, contact Huawei technical support.
    • If no, configure the certificate according to the documentation.

  14. Manually Synchronize Data, then 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.

Related Information

None

Download
Updated: 2019-03-01

Document ID: EDOC1100010511

Views: 20443

Downloads: 12

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