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

FusionInsight HD 6.5.0 Software Installation 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).
Preparing Data

Preparing Data

Collect information or data in Table 2-21 and enter the information or data collected in the Configuration Planning Tool to generate configuration files.

Table 2-21 Planning data

Name

Description

Example Value

Node IP address

  • Specifies the management plane IP addresses of each node.
  • Specifies the service plane IP addresses of each node.
  • Specifies the external management network IP addresses of the active and standby management nodes. (Optional. Configure the node IP address when you need to access FusionInsight Manager from the external management network plane.)
  • 192.168.10.10, 192.168.10.11...
  • 192.168.20.10, 192.168.20.11...
  • 10.10.100.10, 10.10.100.11

Floating IP address

  • OMSServer floating IP address, port, subnet mask, and gateway (management plane)
  • OMWebService floating IP address, port, subnet mask, and gateway (External management network). This address is used to access FusionInsight Manager. The IP address of the management plane or service plane can also be used.
  • Hue floating IP address (service plane)
  • DBService floating IP address and gateway (service plane)
  • Loader floating IP address (service plane)
  • Solr floating IP address (service plane)
  • Mapreduce floating IP address (service plane)
  • GraphBase floating IP address and subnet mask (service plane)
NOTE:
  • If floating IP addresses of OMSServer and OMWebService are consistent, their ports, subnet masks, and gateways must be identical. If their floating IP addresses are inconsistent, their ports must be different.
  • Mapreduce does not need to configure floating IP when using single node deployment mode.
  • Floating IP address: The floating IP address must be the unique and unused IP address in the same network segment. You can run the ping command on nodes in the same network segment to check whether the IP address is unique.
  • Interface: Virtual NIC. The parameter value must be unique in the network segment. bond0 indicates the physical NIC that can provide services on the node. If this NIC is not enabled, change it to an enabled physical NIC on the node. You can run the ifconfig command on nodes in the same network segment to check.

    For the NIC interface bound to the interface of a floating IP address, ensure that the IDs of the bonds used to provide floating IP addresses of the active and standby management nodes are consistent. If no bond is used, make sure that the IDs of the physical NICs used to provide floating IP addresses of the active and management nodes are consistent.

  • Subnet mask: The subnet mask must be the same as that of the node where the service is located. You can run the route command on nodes in the same network segment to check.
  • Gateway: This IP address is used to check whether the service and the network segment are properly connected. You are advised to set the gateway to the gateway address or another fixed and available IP address. The gateway cannot be the IP address or the floating IP address of the node where the service is located. You can run the route command on nodes in the same network segment to check.
  • 192.168.10.200, bond1:OM, 255.255.255.0, 192.168.10.254
  • 10.10.100.201, bond0:WS, 255.255.0.0, 10.10.100.254
  • 192.168.20.202
  • 192.168.20.203, 192.168.20.254
  • 192.168.20.204
  • 192.168.20.205
  • 192.168.20.206
  • 192.168.20.207, 255.255.255.0

(Optional) Third-party server IP address

Network Time Protocol (NTP) server. If the NTP server is not specified, the active management node is specified as the NTP server by default. Use commas (,) to separate multiple IP addresses. A maximum of two NTP servers are supported.

10.10.100.100,10.10.100.101

CAS server and port (7444)

10.10.100.110, 7444

Username and password

Specifies the password of OS user root.

NOTE:

If you install the cluster as user omm, obtain the password of user omm in advance, generate user omm by following the steps provided in Configuring the Software Package, and assign rights.

  • Install the software as user root:

    The password is Huawei123!.

  • Install the user as omm user:

    The password is Bigdata123@ (default password).

Initial username and password of the FusionInsight HD system.

admin, Admin@123

Host name

The host name must start with a letter or digit and contains only digits (0 to 9), letters (a to z and A to Z), and hyphens (-). In addition, the host name cannot contain only digits and does not contain underscores (_), cannot end with hyphens (-), and it must be unique. A host name uniquely maps a service plane IP address and a service plane IP address uniquely maps a host name.

NOTICE:

After software installation, the host name cannot be modified.

Management-1

Rack name

During the cluster installation, rack names are set on different nodes to manage and maintain the nodes in the cluster.

NOTE:

According to reliability principles, it is recommended that the active and standby management nodes be deployed on different racks and the control nodes be deployed on different racks.

/sh/rack1

Port number

Specified ports are used for communication. The managed host listens to the system data over a specified port. If firewalls are deployed between services in the cluster and firewalls are used by the system, the firewall will be disabled during installation. For customized firewalls, the ports must be opened manually for the managed host to receive data.

For details about the default ports used for the communication between services in the cluster, see the FusionInsight_HD 6.5.0 Communication Matrix.

For details, see the FusionInsight_HD 6.5.0 Communication Matrix.

Download
Updated: 2019-05-17

Document ID: EDOC1100074555

Views: 5955

Downloads: 6

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