You are advised to use the bond port mode for the service network of the HDFS service. bond4 is supported. After being created, this port applies to Global Zone and NameNode Zone. Global Zone and NameNode Zone can use the same bond port, but their IP addresses must be planned separately.
If the bond port mode is not used, skip this step. The following uses eth0 and eth1 of a node as an example to describe how to create bond ports for the HDFS service network.
The port for which bond ports are created must be a port without configuring an IP address.
The following uses the 25GE TCP networking as an example to describe how to create bond4 for the eth1 and eth2 ports of a node (management IP address: 192.168.239.56). Table 1 describes more parameters.
create bond_port general transfer_protocol=TCP bond_name=bond_test1 bond_mode=bond4 port1_name=eth1 port2_name=eth2 node_ip=192.168.239.56
Parameter |
Description |
Value |
|---|---|---|
transfer_protocol |
Transport protocol |
The value is TCP.
NOTE:
The HDFS service network supports only the TCP protocol. |
bond_name |
Bond port name The port name of the HDFS service network can contain only digits, letters, periods (.), hyphens (-), and underscores (_), and must start with a letter and end with a digit or letter. A maximum of 13 characters are allowed. |
hdfs_bond |
bond_mode |
Bond mode |
bond4: mode 4, that is, dynamic link aggregation mode.
NOTE:
The HDFS service network supports only the bond4 mode. |
port1_name |
Name of port 1 |
eth1 |
port2_name |
Name of port 2 |
eth2 |
node_ip |
Management IP address of a node |
192.168.239.56 |
The command output is as follows:
admin:/>create bond_port general transfer_protocol=TCP bond_name=bond_test1 bond_mode=bond4 port1_name=eth1 port2_name=eth2 node_ip=192.168.239.56 Command executed successfully.