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


To have a better experience, please upgrade your IE browser.


eSight V300R009C00 Operation Guide 10

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).
FAQ and Troubleshooting

FAQ and Troubleshooting

Unable to access eSight application from external Nodes using FloatIP


After installation of eSight application using HA mode in redhat VM, float ip is unable to access from external systems. IP whitelist is neded to be configured for the float IP in both HA VMs.


Below is Procedure to configure the floatIP whitelist in redhat VM. Below procedure need to be followed for both active and standby eSight server VMs

  1. Using "SSH" connect to undercloud, using root user.
  2. Switch to stack user.

    # su - stack

  3. Source to set the environment variables usign below command.

    > source stackrc

  4. Check all the node information using below command.

    > nova list

  5. Identify one controller node and switch to the controller node using below command.

    > ssh heat-admin@<Controller IP>

  6. Source to set the environment variables usign below command.

    > source overcloudrc

  7. Find the instance id of the eSight server usign below command.

    > nova list --all-t |grep <instance name>

  8. Find the interface ID of the instance using below command.

    > nova interface-list vmid

    vmid is the ID of the eSight server VM

  9. Check the whitelist configuration using below command.

    > neutron port-show portid

  10. Update the IP whitelist for the VM using below command.

    > neutron port-update portid --allowed_address_pairs list=true type=dict ip_address=<float IP>

    <float IP> is the IP which need to allow from external systems

Follow up Procedure

  1. Using the below command in controller node,check the whitelisted IP is shown in dict ip_address field.

    neutron port-show portid

  2. Ping the float IP from external system and ping should give result.
  3. If ping result fails, contact RedHat engineer.

How to configure mapping relationship between RedHat OpenStack Doman Name and IP Address


How do I configure the mapping relationship between the RedHat OpenStack domain name and the IP address?


To enable eSight to manage the RedHat OpenStack, you need to correctly configure the mapping relationship between the RedHat OpenStack domain name and the IP address. Perform the following steps:


In the two-node cluster scenario, configure both the active and standby servers.

  1. Log in to the eSight server as user ossuser in SSH mode.
  2. Switch to user root.

    # su - root
    Password: root password 

    After you switch to user root, "root@Host name:~#" is displayed.

  3. Run the following command to go to /etc .

    # cd /etc

  4. Run the following command to modify the hosts file.

    # vi hosts

  5. Press i to enter the edit mode. Add the mapping relationship between the domain name and the IP address to the hosts file, For details, see the following example.

    Press Esc and run the :wq! command to save the settings and quit the editing mode.

    Example overcloud.localdomain

    overcloud.localdomain is keystone domain name

Slow installation Sensu client plugin due to Invalid DNS Configuration


During installation sensu client plugin on all overcloud and ceph node, it was taking more time. this is due to DNS service running in over cloud, but the configured DNS server is not valid.


There are 2 solutions for the servers

  1. Set the correct DNS server configuration for all overcloud and ceph Nodes
  2. Disable the DNS service in all ceph and overcloud nodes

Below procedure explains how to disable the DNS service in all overcloud and controller nodes

  • Disabling DNS service in overcloud and ceph node will have impact on other functionality of OpenStack. Kindly confirm below procedure, Review and approval with OpenStack and Customer before performing implementation.
  • Step involves the restart of sshd service. Consider the impact of restart in other application related to the ssh service before performing the operation

Below procedure to disable the the DNS Service must be performed in all overcloud and ceph nodes

  1. Login to overcloud/ceph node
  2. set UseDNS as no in sshd_config file

    # vi /etc/ssh/sshd_config

  3. Restart the sshd service using below command

    # systemctl restart sshd

Updated: 2019-09-07

Document ID: EDOC1100011877

Views: 311288

Downloads: 635

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