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

FusionCloud 6.3.1.1 Troubleshooting Guide 02

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).
Domain Names on the Management VMs Cannot Be Resolved

Domain Names on the Management VMs Cannot Be Resolved

Symptom

Domain names on the management VMs cannot be resolved.

Possible Causes

  • An incorrect DNS server address is configured in the /etc/resolv.conf file on the management VMs.
  • Networks between the management VMs and the DNS-OM nodes are disconnected.
  • The DNS process is abnormal.

Troubleshooting Process

Locate the fault based on the possible causes and troubleshoot the fault.

Procedure

  1. Check whether you can log in to the OM-SRV01 and OM-SRV02 VMs where DNS is located.

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

  2. Restore the VM. For details, see Cloud Service Management Plane Fault Diagnosis.
  3. Contact technical support to reinstall DNS. No further action is required.
  1. Check whether the /etc/resolv.conf file is correctly configured.
  2. Use PuTTY to log in to the faulty node using the IP address and the service account of the node.

    The default username is udns, and the default password is Huawei12#$.

  3. Run the following command to open the configuration file /etc/resolv.conf:

    vi /etc/resolv.conf

  4. Check whether the two IP addresses in the configuration file are the IP addresses of the DNS-OM nodes.

    • If yes, go to 8.
    • If no, correct the IP addresses and perform the test again. If the domain name can be resolved, the fault is rectified. Otherwise, go to 8.

  1. Run the following command on the faulty node to check whether the network connection between the faulty node and the DNS-OM node is normal:

    ping DNS-IP

    • If yes, go to 9.
    • If no, contact technical support for assistance, and then rectify the fault.

  2. Use PuTTY to log in to a DNS-OM node as the udns user. Run the following command, and enter the password of the root user to switch to the root user (the default password is Cloud12#$):

    sudo su - root

  3. Run the following command to check the named process status:

    systemctl status named

    If information similar to the following is displayed, the named process stops accidentally.

  4. Run the following command to restart the named process:

    systemctl restart named

    • If no command output is displayed, the named process is successfully restarted. Run the following command to check the status of the named process:

      systemctl status named

      If information similar to the following is displayed, the named process is restored.

    • If the following information is displayed, the named process fails to be restart:
      Job for named.service failed because the control process exited with error code. See "systemctl status named.service" and "journalctl -xe" for details.

      Run the following commands to restore the named process based on the error message:

      systemctl status named

      journalctl -xe

      After the fault is rectified, restart the named process again. If the fault persists, contact technical support for assistance.

Translation
Download
Updated: 2019-06-10

Document ID: EDOC1100063248

Views: 23012

Downloads: 37

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