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

eSight V300R010C00SPC200, 300, and 500 Operation Guide 09

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 Floating IP

This topic explain how to solve the problem that unable to access eSight application from external Nodes using Floating IP.

Context

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

Procedure

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

  1. Log in to the Director as the stack user and run the following command to set the environment variables:

    > source stackrc

  2. Run the following command to check the information of all nodes:

    > nova list

  3. Select a controller node and run the following command to log in to it:

    > ssh heat-admin@<Controller IP>

  4. Run the following command to set the environment variables:

    > source overcloudrc

    NOTE:

    Ensure that the file exists on the node. If the file does not exist, copy it from the Director node.

  5. Run the following command to check the VMIDs of the eSight servers:

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

  6. Run the following command with the VMIDs you obtained in the previous step to check the port IDs of the eSight instances:

    > nova interface-list <VMID>
    NOTE:

    <VMID> is the ID of the eSight server VM

  7. Run the following command to check the IP address whitelist configuration based on the Port ID obtained in the previous step:

    > neutron port-show <Port ID>

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

    > neutron port-update <Port ID> --allowed_address_pairs list=true type=dict ip_address=<Floating IP>
    NOTE:

    <Floating 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 <Port ID>

  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

This topic explain how to configure mapping relationship between RedHat OpenStack Doman Name and IP Address.

Context

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

Procedure

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:

NOTE:

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 
    NOTE:

    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

    10.38.136.2 overcloud.localdomain
    NOTE:

    overcloud.localdomain is keystone domain name

Slow installation Sensu client plugin due to Invalid DNS Configuration

This topic explain how to solve the problem that slow installation Sensu client plugin due to Invalid DNS Configuration.

Context

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.

Procedure

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

Translation
Download
Updated: 2019-09-12

Document ID: EDOC1100044378

Views: 70170

Downloads: 373

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