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>

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

Can't ping the slave NIC IP after binding

Publication Date:  2014-06-30 Views:  105 Downloads:  0
Issue Description
Server Model: RH2288 V2
OS: Suse Linux 11

Problem description:
In suse linux,the eth0 and eth1 were bond to bond0.
After changing the IP address of eth0 using yast2,the IP is not reachable for both eth0 and eth1.
Alarm Information
None.
Handling Process
1: Add the slave NIC configuration to the bond0 configuration file:

VMM:/etc/sysconfig/network # vi ifcfg-bond0
BOOTPROTO='static'
STARTMODE='auto'
device='bond0'
IPADDR='192.168.2.222'
NETMASK='255.255.255.0'
BONDING_MASTER='yes'
BONDING_MODULE_OPTS='mode=1 miimon=200'
BONDING_SLAVE0='eth0'
BONDING_SLAVE1='eth1'
2: Save the configuration file and restart the network service
VMM:/etc/init.d/network restart 
Root Cause
Check the configuration file of the bond0 NIC:

VMM:/etc/sysconfig/network # more ifcfg-bond0
BOOTPROTO='static'
STARTMODE='auto'
device='bond0'
IPADDR=192.168.2.222 '
NETMASK='255.255.255.0'
BONDING_MASTER='yes'
BONDING_MODULE_OPTS='mode=1 miimon=200'
BROADCAST=''
ETHTOOL_OPTIONS=''
MTU=''
NAME=''
NETWORK=''
REMOTE_IPADDR=''
USERCONTROL='no'

We find the slave NIC configuration was lost.
Suggestions
After making NIC binding,don't use yast2 tool to change the slave NIC physical IP.
If we need to change the physical IP,we should modify the configuration file directly.

END