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

HUAWEI CLOUD Stack 6.5.0 Alarm and Event Reference 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).
ALM-12043 DNS Resolution Duration Exceeds the Threshold

ALM-12043 DNS Resolution Duration Exceeds the Threshold

Description

The system checks the DNS parsing duration every 30 seconds and compares the actual DNS parsing duration with the threshold (the default threshold is 20,000 ms). This alarm is generated when the system detects that the DNS parsing duration exceeds the threshold for several times (5 times by default) consecutively.

To change the threshold, choose System > Threshold Configuration > Device > Host > Network Status > DNS Name Resolution Duration > DNS Name Resolution Duration.

When the hit number is 1, this alarm is cleared when the DNS parsing duration is less than or equal to the threshold. When the hit number is greater than 1, this alarm is cleared when the DNS parsing duration is less than or equal to 90% of the threshold.

Attribute

Alarm ID

Alarm Severity

Auto Clear

12043

Major

Yes

Parameters

Name

Meaning

ServiceName

Identifies the service name for which the alarm is generated.

RoleName

Identifies the role name for which the alarm is generated.

HostName

Identifies the object (host ID) for which the alarm is generated.

Impact on the System

  • Kerberos-based secondary authentication is slow.
  • The ZooKeeper service is abnormal.
  • The node is faulty.

Possible Causes

  • The node is configured with the DNS client.
  • The node is equipped with the DNS server and the DNS server is started.

Procedure

Check whether the node is configured with the DNS client.

  1. Log in to the FusionInsight Manager.

    1. Log in to the ManageOne OM plane using a browser, then choose Alarms.
      • Login address: https://URL for the homepage of the ManageOne OM plane:31943. Example: https://oc.type.com:31943.
      • Default username: admin, default password: Huawei12#$.
    2. In the alarm list, locate and click the target alarm name in the Name column. The Alarm Details and Handling Recommendations dialog box is displayed.
    3. Locate the value in the IP Address/URL/Domain Name column, which is the float IP address of the FusionInsight Manager.
    4. Log in to the FusionInsight Manager using a browser.
      • Login address: https://float IP address of the FusionInsight Manager:28443/web. Example: https://10.10.192.100:28443/web.
      • Default username: admin, default password: obtain it from the system administrator.

  2. On the FusionInsight Manager portal, choose Alarms.
  3. Check the value of HostName in the detailed alarm information to obtain the name of the host involved in this alarm.
  4. Use PuTTY to log in to the node for which the alarm is generated as user root. The password is specified by users before the installation. Obtain it from the system administrator.
  5. Run the cat /etc/resolv.conf command to check whether the DNS client is installed.

    If information similar to the following is displayed, the DNS client is installed and started:

    namesever 10.2.3.4 
    namesever 10.2.3.4
    • If yes, go to 6.
    • If no, go to 8.

  6. Run the vi /etc/resolv.conf command to comment out the following content using the number signs (#) and save the file:

    # namesever 10.2.3.4  
    # namesever 10.2.3.4

  7. Check whether this alarm is cleared after 5 minutes.

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

Check whether the node is equipped with the DNS server and the DNS server is started.

  1. Run the service named status command to check whether the DNS server is installed on the node:

    If information similar to the following is displayed, the DNS server is installed and started:

    Checking for nameserver BIND  
    version: 9.6-ESV-R7-P4 
    CPUs found: 8 
    worker threads: 8 
    number of zones: 17 
    debug level: 0 
    xfers running: 0 
    xfers deferred: 0 
    soa queries in progress: 0 
    query logging is ON 
    recursive clients: 4/0/1000 
    tcp clients: 0/100 
    server is up and running
    • If yes, go to 9.
    • If no, go to 11.

  2. Run the service named stop command to stop the DNS server.
  3. Check whether this alarm is cleared after 5 minutes.

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

Collect fault information.

  1. On the FusionInsight Manager portal, choose System > Log Download.
  2. Select Manager from the Services drop-down list box and click OK.
  3. Set Host to the node for which the alarm is generated and the active OMS node.
  4. Set Start Time for log collection to 10 minutes ahead of the alarm generation time and End Time to 10 minutes behind the alarm generation time, and click Download.
  5. Contact Technical Support and send the collected logs.

Alarm Clearing

After the fault is rectified, the system automatically clears this alarm.

Related Information

None.

Translation
Download
Updated: 2019-08-30

Document ID: EDOC1100062365

Views: 45009

Downloads: 33

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