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