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 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).
Adding a Single Virtual Resources Device

Adding a Single Virtual Resources Device

You can manually add a small number of virtual resources devices to the eSight if you have obtained the virtual resources device Internet Protocol (IP) address and protocol information.

Adding a Single FusionSphere

Configuring the Mapping Between FusionSphere OpenStack Domain Names and IP Addresses

Before eSight manages the FusionSphere OpenStack, correctly configure the mapping between the FusionSphere OpenStack domain name and IP address.

Procedure

Windows operating system

  1. Log in to the eSight server as the administrator user.
  2. Access the C:/Windows/System32/drivers/etc directory.
  3. Use the text editor to modify the hosts file.

    Add the mapping between the domain name and IP address in the file. For details, see the example.

SUSE Linux operating system

  1. Log in to the eSight server as the ossuser user using PuTTY.
  2. Run the following commands to switch to the root user:

    # su - root

    Password: root password

  3. Run the following command to access the /etc directory:

    cd /etc

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

    vi hosts

    Press i to enter the editing mode and add the mapping between the domain name and IP address in the file. For details, see the example.

  5. Press Esc and run the :wq! command to save the settings and exit the editing mode.
  6. For a two-node cluster, repeat Step 1 to Step 5 to configure the standby server.

Example

Three scenarios are involved in the configuration of the mapping between the FusionSphere OpenStack domain name and IP address: single-DC scenario, scenario where multiple DCs share the same KeyStone, and scenario with multiple DCs and multiple KeyStones. Refer to the following examples based on the requirements.

  • Single-DC scenario:
    10.38.136.2 az1.dc1.domainname.com
    10.38.136.2 identity.az1.dc1.domainname.com 
    10.38.136.2 image.az1.dc1.domainname.com 
    10.38.136.2 compute.az1.dc1.domainname.com 
    10.38.136.2 backup.az1.dc1.domainname.com 
    10.38.136.2 upgrade.az1.dc1domainname.com 
    10.38.136.2 log.az1.dc1domainname.com 
    10.38.136.2 ntp.az1.dc1.domainname.com 
    10.38.136.2 oam.az1.dc1.domainname.com 
    10.38.136.2 cps.az1.dc1.domainname.com 
    10.38.136.2 info-collect.az1.dc1.domainname.com 
    10.38.136.2 orchestration.az1.dc1.domainname.com 
    10.38.136.2 metering.az1.dc1.domainname.com 
    10.38.136.2 mtc.az1.dc1.domainname.com 
    10.38.136.2 volume.az1.dc1.domainname.com 
    10.38.136.2 object-store.az1.dc1.domainname.com 
    10.38.136.2 baremetal.az1.dc1.domainname.com 
    10.38.136.2 drextend.az1.dc1.domainname.com 
    10.38.136.2 nova-novncproxy.az1.dc1.domainname.com 
    10.38.136.2 network.az1.dc1.domainname.com 
    10.38.136.2 alarming.az1.dc1.domainname.com 
    10.38.136.2 compute-ext.az1.dc1.domainname.com
    NOTE:
    • 10.38.136.2: reverse proxy IP address of the FusionSphere OpenStack in the DC.(An IPv4 address is used as an example.)
    • az1.dc1.domainname.com: local domain name of the DC.

    For details about how to obtain the parameters, see the FusionSphere Product Documentation.

  • Scenario where multiple DCs share the same KeyStone:
    10.38.136.2 az1.dc1.h-multi-dc.com
    10.38.136.2 identity.az1.dc1.h-multi-dc.com 
    10.38.136.2 image.az1.dc1.h-multi-dc.com 
    10.38.136.2 compute.az1.dc1.h-multi-dc.com 
    10.38.136.2 backup.az1.dc1.h-multi-dc.com 
    10.38.136.2 upgrade.az1.dc1.h-multi-dc.com 
    10.38.136.2 log.az1.dc1.h-multi-dc.com 
    10.38.136.2 ntp.az1.dc1.h-multi-dc.com 
    10.38.136.2 oam.az1.dc1.h-multi-dc.com 
    10.38.136.2 cps.az1.dc1.h-multi-dc.com 
    10.38.136.2 info-collect.az1.dc1.h-multi-dc.com 
    10.38.136.2 orchestration.az1.dc1.h-multi-dc.com 
    10.38.136.2 metering.az1.dc1.h-multi-dc.com 
    10.38.136.2 mtc.az1.dc1.h-multi-dc.com 
    10.38.136.2 volume.az1.dc1.h-multi-dc.com 
    10.38.136.2 object-store.az1.dc1.h-multi-dc.com 
    10.38.136.2 baremetal.az1.dc1.h-multi-dc.com 
    10.38.136.2 drextend.az1.dc1.h-multi-dc.com 
    10.38.136.2 nova-novncproxy.az1.dc1.h-multi-dc.com 
    10.38.136.2 network.az1.dc1.h-multi-dc.com 
    10.38.136.2 alarming.az1.dc1.h-multi-dc.com 
    10.38.136.2 compute-ext.az1.dc1.h-multi-dc.com  
    10.38.144.2 image.az1.dc2.h-multi-dc.com 
    10.38.144.2 compute.az1.dc2.h-multi-dc.com 
    10.38.144.2 backup.az1.dc2.h-multi-dc.com 
    10.38.144.2 upgrade.az1.dc2.h-multi-dc.com 
    10.38.144.2 log.az1.dc2.h-multi-dc.com 
    10.38.144.2 ntp.az1.dc2.h-multi-dc.com 
    10.38.144.2 oam.az1.dc2.h-multi-dc.com 
    10.38.144.2 cps.az1.dc2.h-multi-dc.com 
    10.38.144.2 info-collect.az1.dc2.h-multi-dc.com 
    10.38.144.2 orchestration.az1.dc2.h-multi-dc.com 
    10.38.144.2 metering.az1.dc2.h-multi-dc.com 
    10.38.144.2 mtc.az1.dc2.h-multi-dc.com 
    10.38.144.2 volume.az1.dc2.h-multi-dc.com 
    10.38.144.2 object-store.az1.dc2.h-multi-dc.com 
    10.38.144.2 drextend.az1.dc2.h-multi-dc.com 
    10.38.144.2 baremetal.az1.dc2.h-multi-dc.com 
    10.38.144.2 nova-novncproxy.az1.dc2.h-multi-dc.com 
    10.38.144.2 network.az1.dc2.h-multi-dc.com 
    10.38.144.2 alarming.az1.dc2.h-multi-dc.com 
    10.38.144.2 compute-ext.az1.dc2.h-multi-dc.com
    NOTE:
    • 10.38.136.2: reverse proxy IP address of the FusionSphere OpenStack in DC1.(An IPv4 address is used as an example.)
    • az1.dc1.h-multi-dc.com: local domain name of DC1.
    • 10.38.144.2: reverse proxy IP address of the FusionSphere OpenStack in DC2.(An IPv4 address is used as an example.)
    • az1.dc2.h-multi-dc.com: local domain name of DC2.

    For details about how to obtain the parameters, see the FusionSphere Product Documentation.

  • Scenario with multiple DCs and multiple KeyStones:
    10.38.136.2 az1.dc1.h-multi-dc.com
    10.38.136.2 identity.az1.dc1.h-multi-dc.com 
    10.38.136.2 image.az1.dc1.h-multi-dc.com 
    10.38.136.2 compute.az1.dc1.h-multi-dc.com 
    10.38.136.2 backup.az1.dc1.h-multi-dc.com 
    10.38.136.2 upgrade.az1.dc1.h-multi-dc.com 
    10.38.136.2 log.az1.dc1.h-multi-dc.com 
    10.38.136.2 ntp.az1.dc1.h-multi-dc.com 
    10.38.136.2 oam.az1.dc1.h-multi-dc.com 
    10.38.136.2 cps.az1.dc1.h-multi-dc.com 
    10.38.136.2 info-collect.az1.dc1.h-multi-dc.com 
    10.38.136.2 orchestration.az1.dc1.h-multi-dc.com 
    10.38.136.2 metering.az1.dc1.h-multi-dc.com 
    10.38.136.2 mtc.az1.dc1.h-multi-dc.com 
    10.38.136.2 volume.az1.dc1.h-multi-dc.com 
    10.38.136.2 object-store.az1.dc1.h-multi-dc.com 
    10.38.136.2 baremetal.az1.dc1.h-multi-dc.com 
    10.38.136.2 drextend.az1.dc1.h-multi-dc.com 
    10.38.136.2 nova-novncproxy.az1.dc1.h-multi-dc.com 
    10.38.136.2 network.az1.dc1.h-multi-dc.com 
    10.38.136.2 alarming.az1.dc1.h-multi-dc.com 
    10.38.136.2 compute-ext.az1.dc1.h-multi-dc.com 
    10.38.144.2 az1.dc1.h-multi-dc.com
    10.38.144.2 identity.az1.dc1.h-multi-dc.com
    10.38.144.2 image.az1.dc2.h-multi-dc.com 
    10.38.144.2 compute.az1.dc2.h-multi-dc.com 
    10.38.144.2 backup.az1.dc2.h-multi-dc.com 
    10.38.144.2 upgrade.az1.dc2.h-multi-dc.com 
    10.38.144.2 log.az1.dc2.h-multi-dc.com 
    10.38.144.2 ntp.az1.dc2.h-multi-dc.com 
    10.38.144.2 oam.az1.dc2.h-multi-dc.com 
    10.38.144.2 cps.az1.dc2.h-multi-dc.com 
    10.38.144.2 info-collect.az1.dc2.h-multi-dc.com 
    10.38.144.2 orchestration.az1.dc2.h-multi-dc.com 
    10.38.144.2 metering.az1.dc2.h-multi-dc.com 
    10.38.144.2 mtc.az1.dc2.h-multi-dc.com 
    10.38.144.2 volume.az1.dc2.h-multi-dc.com 
    10.38.144.2 object-store.az1.dc2.h-multi-dc.com 
    10.38.144.2 drextend.az1.dc2.h-multi-dc.com 
    10.38.144.2 baremetal.az1.dc2.h-multi-dc.com 
    10.38.144.2 nova-novncproxy.az1.dc2.h-multi-dc.com 
    10.38.144.2 network.az1.dc2.h-multi-dc.com 
    10.38.144.2 alarming.az1.dc2.h-multi-dc.com 
    10.38.144.2 compute-ext.az1.dc2.h-multi-dc.com
    NOTE:
    • 10.38.136.2: reverse proxy IP address of the FusionSphere OpenStack in DC1.(An IPv4 address is used as an example.)
    • az1.dc1.h-multi-dc.com: local domain name of DC1.
    • 10.38.144.2: reverse proxy IP address of the FusionSphere OpenStack in DC2.(An IPv4 address is used as an example.)
    • az1.dc2.h-multi-dc.com: local domain name of DC2.

    For details about how to obtain the parameters, see the FusionSphere Product Documentation.

Adding new FusionSphere

eSight allows users to add a single FusionSphere via HTTPS.

Prerequisite

  • You have the resource access right.
  • You have obtained FusionSphere KeyStone Domain, user names, and passwords.
  • Virtual Manager (FS/FC/vCenter/ESX) has been installed.
  • eSight can communicate with the External_API and External_OM network planes.

Procedure

  1. In the main menu, choose Resource > Common.
  2. Choose Add Resource > Add Resource in the navigation area on the left.
  3. On the top of the right pane, choose Virtual Resource > FusionSphere.
  4. Enter basic information.
  5. Set HTTPS parameters.

    NOTE:

    The default password of the system_admin user is FusionSphere123.To ensure account security, it is recommended that you change your password upon first login.

  6. Set OpenStack OM login information.

    NOTE:

    The default password of the OmmRest user is Omm@1234. To ensure account security, it is recommended that you change your password upon first login. For details about how to change a password, see the FusionSphere Product Documentation.

  7. Set SNMP parameters.

    The SNMP parameter settings should be the same as the settings of the SNMP management station of the FusionSphere system. If you forget the settings of the SNMP management station of the FusionSphere system, set SNMP parameters as preferred here and select Synchronize SNMP Trap Settings to OpenStack OM.

  8. Click OK.

Follow-up Procedure

  • After the FusionSphere is added, if a message prompts that the user name and password of the OpenStack OM is not correct or the SNMP management station fails to be allocated, create an SNMP management station on the FusionSphere Open Stack OM again. For details, see Creating an SNMP management station.
  • on the FusionSphere list page, you can perform the operations described in the following table .

    Operation

    Description

    Modifying basic information

    • Click next to a FusionSphere.
    • Select FusionSpheres you want to modify and click above the FusionSphere list.

    Modifying the protocol

    Select FusionSpheres you want to modify and click above the FusionSphere list. In the drop-down list, select the parameters to be modified and access the editing page.

Adding a Single FusionCompute

eSight allows users to add a single FusionCompute via HTTPS.

Prerequisite

  • You have the resource access right.
  • You have obtained FusionCompute IP addresses, user names, and passwords.
  • Virtual Manager (FS/FC/vCenter/ESX) has been installed.

Procedure

  1. In the main menu, choose Resource > Common.
  2. Choose Add Resource > Add Resource in the navigation area on the left.
  3. On the top of the right pane, choose Virtual Resource > FusionCompute.
  4. Enter basic information.
  5. Set HTTPS parameters.
  6. Set SNMP parameters.

    The settings of SNMP parameters must be the same as those specified in the FusionCompute system. If you forget the settings of SNMP parameters in the FusionCompute system, set SNMP parameters as preferred here and select Synchronize SNMP TRAP Settings to FusionCompute.

    NOTE:

    The SNMP v3 protocol does not support alarm reporting. Therefore, when adding resources, it is recommended to select the SNMP v2c protocol.

  7. Optional: If FusionCompute is deployed in a two-node cluster, associate the deployment parameters of the FusionCompute VRM server.

    1. Select Start Two-Node Deployment.
    2. Enter the IP addresses of the active and standby VRMs.

  8. Click OK.

Follow-up Procedure

On the FusionCompute list page, you can perform the operations described in the following table .

Operation

Description

Modifying basic information

  • Click next to a FusionCompute.
  • Select FusionComputes you want to modify and click above the FusionCompute list.

Modifying the protocol

Select FusionComputes you want to modify and click above the FusionComputes list. In the drop-down list, select the parameters to be modified and access the editing page.

Adding a Single vCenter Server

eSight allows users to add a single vCenter server via SOAP.

Prerequisite

  • You have the resource access right.
  • You have obtained vCenter server IP addresses, user names, and passwords.
  • Virtual Manager (FS/FC/vCenter/ESX) has been installed.

Procedure

  1. In the main menu, choose Resource > Common.
  2. Choose Add Resource > Add Resource in the navigation area on the left.
  3. On the top of the right pane, choose Virtual Resource > vCenter Server.
  4. Enter basic information.
  5. Set SOAP parameters.
  6. Click OK.

Follow-up Procedure

On the vCenter server list page, you can perform the operations described in the following table.

Operation

Description

Modifying basic information

  • Click next to a vCenter server.
  • Select vCenter servers you want to modify and click above the vCenter server list.

Modifying the protocol

Select vCenter servers you want to modify and click above the vCenter server list. In the drop-down list box, click Modify SOAP parameters to access the editing page.

Adding a Single ESX Server

If you want a few ESX servers to access the eSight, you can add an ESX server one by one.

Prerequisite

  • You have obtained the IP address, user name, and password of the device.
  • eSight has been started.

    Virtual Manager (FS/FC/vCenter/ESX) has been installed.

Context

The ESX server is added to eSight through the SOAP protocol.

Procedure

  1. Choose Resource > Common from the main menu.
  2. Choose Add Resource > Add Resource in the navigation area on the left.
  3. Choose Virtual Resources > ESX Server in the information display area on the right.
  4. Enter the basic parameters for the ESX server that you want to discover in Basic Information.
  5. Set the SOAP Protocol parameters.
  6. Click OK.

    NOTE:

    Click Apply to create more NEs.

    • If the NE is created successfully, the NE is displayed in the list.
    • If the NE cannot be created, the Error dialog box is displayed. Click OK to set the parameters again.

Follow-up Procedure

  • Protocol parameters are required to implement communication between NEs and eSight. When protocol parameters are changed on the NEs, synchronize the parameters on eSight. For details, see 5.7 Configuring Protocol Parameters.
  • After an ESX server is added to eSight, you can delete it from the ESX server list.

    Operation

    Description

    Deleting ESX servers

    • Click next to an ESX server.
    • Select ESX servers you want to delete and click above the ESX server list.

Adding a Single Redhat OpenStack

Steps to add New Redhat OpenStack in eSight Monitoring.

NOTE:

Currently, you have access to a set of Red Hat OpenStack. If you need to access multiple sets, you need to create a new Vhost on RabbitMQ for each new set of Red Hat OpenStack. see <eSight V300R009C00 Maintenance Guide> Maintenance Reference -> Command Reference -> 3rd Party OpenStack Command Reference -> RabbitMQ Command ->Add RabbitMQ Connection Vhost to creat a new Vhost.

Figure 1-1 Connection for adding new Redhat.

Managing Virtual Resources (3rd Party Openstack)

eSight can manage Redhat OpenStack, allowing users to obtain information about the alarms and performance of Redhat OpenStack. eSight allows you to add Redhat OpenStack one by one.

Understanding Various Protocols

Protocol

Description

SOAP

Simple Object Access Protocol, a type of protocol that is lightweight, simple, and XML-based. It is designed to exchange structured information at web.

HTTPS

Hypertext Transfer Protocol Secure, an HTTP protocol that runs on top of transport layer security (TLS) and Secure Sockets Layer (SSL). It is used to establish a reliable channel for encrypted communication and secure identification of a network web server. For details, see RFC2818.

Rabbit MQ configuration

RabbitMQ is a message broker: it accepts and forwards messages. You can think about it as a post office: when you put the mail that you want posting in a post box, you can be sure that Mr. Postman will eventually deliver the mail to your recipient. In this analogy, RabbitMQ is a post box, a post office and a postman.

Methods and Protocols

Device Name

Can Be Automatically Discovered or Not (Y/N)HTTPS Protocol

Can Be Automatically Discovered or Not (Y/N)SOAP Protocol

Can Be Added in Batches or Not (Y/N)

Can Be Added One by One or Not (Y/N)

Redhat Open Stack

N

N

N

Y

Procedure

  1. Login to eSight GUI with valid user. Go to Resource > Virtual Resource > Redhat OpenStack
  2. Click on Create (as shown below in image)

  3. Define the Basic Information, type value will be by default Redhat OpenStack.

  4. Configure HTTPS Protocol information. Configure Keystone Domain/IP Address , Port, Username, Password. Click on Get Region it will automatically collecct the region name from Redhat OpenStack.

    NOTE:

    Login to dashboard GUI with admin user. Go to Admin> System > System Information.View the suffix of Public under the "Endpoints" whose name is keystone .

    • Parameter Description
      Table 11-1 Parameter Description

      Parameter

      Description

      Setting

      Keystone Domain/IP Address

      keystone Domain or IP Address

      Fill in according to the actual content.

      if it is Keystone Domain,see How to configure mapping relationship between Redhat OpenStack Domian Name and IP Address to configure mapping relationship between Redhat OpenStack Domian Name and IP Address.

      Port

      keystone's Port

      Fill in according to the actual content.

      Username

      admin user

      Value: admin

      Password

      admin user's password

      admin user's password

      Project(Tenant Name)

      Project Name or Tenant Name

      Value: admin

      Keystone Version

      Keystone Version

      v2.0 or v3

      If the Keystone Version of the Red Hat OpenStack is different from the eSight interface,see Modifying Keystone Version of OpenStack at eSight to modifying Keystone Version.

  5. Configure RabbitMQ with necessary parameters like RabbitMQ IP1, RabbitMQ IP2 (leave blank incase only one RabbitMQ), Vhost Name, Port,Username, Password, Certificate File Name and Certificate Password.

    Finally Apply and select OK button.

    NOTE:
    • Proper RabbitMQ certificate must be placed before adding the Redhat according to commissioning guide to ensuring the successful RabbitMQ connection. For different Redhat OpenStack, different RabbitMQ Vhost Name, Username and Password configurations are required.
    • Default Vhost Name for RabbitMQ is sensu

Translation
Download
Updated: 2019-09-07

Document ID: EDOC1100011877

Views: 336849

Downloads: 680

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