Database Reference
In-Depth Information
Modify the individual network interface configuration files to reflect the bonding details:
[root@prddb3 network-scripts]# more ifcfg-eth24
# Linux NIC bonding between eth24 and eth25
# Murali Vallath
# December-21-2013
DEVICE=eth24
BOOTPROTO=none
ONBOOT=yes
USERCTL=no
MASTER=bond2
SLAVE=yes
TYPE=Ethernet
HWADDR=00:D0:B7:6A:39:85
Modify ifcfg-eth25 to make similar updates
In the preceding file, the
MASTER
clause indicates which logical interface this specific NIC belongs to, and the
SLAVE
clause indicates that it's one among other NICs that are bonded to the master and is only a slave to its master.
■
similar changes should be made to all network configuration files on node
prddb3
for
bond2
logical interface
described in this example.
Note
The next step is to restart the network interfaces, and this can be done by using the following commands:
[root@prddb3 root]# service network stop
Shutting down interface eth0: [ OK ]
Shutting down interface eth24: [ OK ]
Shutting down interface eth25: [ OK ]
Shutting down loopback interface: [ OK ]
[root@prddb3 root]#
[root@prddb3 root]# service network start
Setting network parameters: [ OK ]
Bringing up loopback interface: [ OK ]
Bringing up interface bond2: [ OK ]
[root@prddb3 root]#
The next step in the configuration process is to verify if the new logical interface is active. The following two
options will help verify the configuration:
1.
Verify from the messages generated during interface startup. This is found in the operating
system specific log files.
[root@prddb3 root]# tail -15 /var/log/messages
network: Setting network parameters: succeeded
kernel: ip_tables: (C) 2000-2002 Netfilter core team
network: Bringing up loopback interface: succeeded
kernel: ip_tables: (C) 2000-2002 Netfilter core team
ifup: Enslaving eth25 to bond2
kernel: bonding: bond0: enslaving eth24 as an active interface with a down link.
Search WWH ::
Custom Search