You have to aggregate two network interfaces, eth0 and eth1, into a single logical interface such
as bond0. Which option shows the four configuration files that need to be configured to set up this
bonding?
A.
/etc/sysconfig/network-scripts/ifcfg-bond0
/etc/sysconfig/network-scripts/ifcfg-eth0
/etc/sysconfig/network-scripts/idfg-eth1
/proc/bonding.conf
B.
/etc/sysconfig/network-scripts/ifcfg-bond0
/etc/sysconfig/network-scripts/ifcfg-eth0
/etc/sysconfig/network-scripts/idfg-eth1
/etc/modeprobe.d/bonding.cfg
C.
/etc/sysconfig/network/ifcfg-bond0
/etc/sysconfig/network-scripts/ifcfg-eth0
/etc/sysconfig/network-scripts/ifcfg-eth1
/etc/modprobe.d/bonding.conf
D.
/etc/sysconfig/network-scripts/ifcfg-bond0
/etc/sysconfig/network-scripts/eth0
/etc/sysconfig/network-scripts/eth1
/etc/bonding.conf
Explanation:
*Step #1: Create a Bond0 Configuration File
Red Hat Enterprise Linux (and its clone such as CentOS) stores network configuration in
/etc/sysconfig/network-scripts/ directory. First, you need to create a bond0 config file as follows:
# vi /etc/sysconfig/network-scripts/ifcfg-bond0
*Step #2: Modify eth0 and eth1 config files
Open both configuration using a text editor such as vi/vim, and make sure file read as follows for
eth0 interface# vi /etc/sysconfig/network-scripts/ifcfg-eth0
*Step # 3: Load bond driver/module
Make sure bonding module is loaded when the channel-bonding interface (bond0) is brought up.
You need to modify kernel modules configuration file:
For each configured channel bonding interface, there must be a corresponding entry in your new
/etc/modprobe.d/bonding.conf file.
None of the answers are correct. If C was this then it would be right
/etc/sysconfig/network-scripts/ifcfg-bond0
/etc/sysconfig/network-scripts/ifcfg-eth0
/etc/sysconfig/network-scripts/ifcfg-eth1
/etc/modprobe.d/bonding.conf
Matt is right. also you can use the following command to aggregate two nic into one logical nic:
# modprobe bonding
# ifconfig bond0 192.168.0.1 netmask 255.255.255.0
# ifenslave bond0 eth0 eth1
B is OK