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

Failed to Deploy the MPPDB Service on FusionInsight MPPDB V100R002C70

Publication Date:  2019-04-12 Views:  33 Downloads:  0
Issue Description

The binding mode of the FusionInsight MPPDB V100R002C70 NIC is as follows:

ifcfg-bond0 configuration:

DEVICE=bond0

BOOTPROTO=none

ONBOOT=yes

IPADDR=20.78.2.89

NETMASK=255.255.255.128

GATEWAY=20.78.2.1

 

ifcfg-bond1 configuration:

DEVICE=bond1

BOOTPROTO=none

ONBOOT=yes

IPADDR=20.78.1.89

NETMASK=255.255.255.128

GATEWAY=20.78.1.1

 

Create the bonding.conf file in the /etc/modprobe.d directory. The configuration is as follows:

 

allias bond0 bonding

 

allias bond1 bonding

 

options bonding max_bonds=2 miimon=200 mode=1

 

As a result, the MPPDB service fails to be deployed.
Handling Process

FusionInsight MPPDB V100R002C70 on the live network has 12 nodes, of which two are management nodes and 10 are data nodes used to deploy the MPPDB service. The management plane and service plane are separated.


Each node provides two 10GE cables for active/standby binding to function as the management plane and two 10GE cables for active/standby binding to function as the service plane. The binding mode is as follows:


ifcfg-bond0 configuration:

DEVICE=bond0

BOOTPROTO=none

ONBOOT=yes

IPADDR=20.78.2.89

NETMASK=255.255.255.128

GATEWAY=20.78.2.1


ifcfg-bond1 configuration:

DEVICE=bond1

BOOTPROTO=none

ONBOOT=yes

IPADDR=20.78.1.89

NETMASK=255.255.255.128

GATEWAY=20.78.1.1


Create the bonding.conf file in the /etc/modprobe.d directory. The configuration is as follows:


allias bond0 bonding


allias bond1 bonding


options bonding max_bonds=2 miimon=200 mode=1


Restart the NIC.


service network restart


An error is reported during the installation and deployment of the MPPDB Server.




After log analysis, it is found that an error is printed in the gs_checkos file.




 


The error message indicates that the NIC RX fails to be obtained. The R&D personnel point out that the logic for determining whether the NIC is bound in the preinstall phase based on the options bonding character string detected in the ifcfg-bond0.


However, in this case, the binding is confirmed by creating the options bonding specified in bonding.conf file under the /etc/modprobe.d directory. As a result, an error occurs in the logic for checking whether the NIC is bound in the preinstall phase is incorrect. As a result, the NIC RX fails to be obtained.

Root Cause

In the preinstall phase, the logic for determining whether a network adapter is bound is incorrect and the NIC RX fails to be obtained.

Solution

Measures:

 

Modify the NIC binding mode.

 

 

ifcfg-bond0 configuration:

DEVICE=bond0

BOOTPROTO=none

ONBOOT=yes

IPADDR=20.78.2.89

NETMASK=255.255.255.128

GATEWAY=20.78.2.1

 

BONDING_OPTS='mode=1 miimon=100 use_carrier=1 primary=eth0'

 

ifcfg-bond1 configuration:

DEVICE=bond1

BOOTPROTO=none

ONBOOT=yes

IPADDR=20.78.1.89

NETMASK=255.255.255.128

GATEWAY=20.78.1.1

 

BONDING_OPTS='mode=1 miimon=100 use_carrier=1 primary=eth2'

 

 

Restart the NIC.

 

service network restart

 

Deploy the MPPDB Server service again. The fault is rectified.

Suggestions

You are advised to modify the preinstall script when configuring the MPPDB service to change the logic that determines whether the NIC is bound. Create a bonding.conf file under the /etc/modprobe.d directory, and then specify the options bonding in the bonding.conf file.

END