Scribd
Upload
34 views

Combining Multiple Network Interface Into Single Interface

This document provides instructions for configuring network interface bonding in Linux. Bonding allows combining multiple network interfaces into a single interface to improve performance. The steps shown configure bonding for two interfaces (eth0 and eth1) under the bond0 interface. This involves loading the bonding kernel module, configuring the bond0 and interface files, and restarting the network. Verification with ifconfig confirms the new bond0 interface and associated slave interfaces eth0 and eth1.

Uploaded by

maczmail5190
Copyright
© Attribution Non-Commercial (BY-NC)
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
34 views

Combining Multiple Network Interface Into Single Interface

This document provides instructions for configuring network interface bonding in Linux. Bonding allows combining multiple network interfaces into a single interface to improve performance. The steps shown configure bonding for two interfaces (eth0 and eth1) under the bond0 interface. This involves loading the bonding kernel module, configuring the bond0 and interface files, and restarting the network. Verification with ifconfig confirms the new bond0 interface and associated slave interfaces eth0 and eth1.

Uploaded by

maczmail5190
Copyright
© Attribution Non-Commercial (BY-NC)
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 2

8.

Append below details and save


Combining multiple network alias bond0 bonding
interface into single interface options bond0 mode=balance-alb miimon=100

(bond) 9. Load the bonding module


# modprobe bonding
Bonding is a process of combining more multiple 10. Restart network
network interfaces as one interface. The main # /etc/init.d/network restart
objective of bonding is to improve the performance
of both network interfaces. Using this way, more load 11. You can check whether your bonding is ok by
and data can be handled by the bonded network using ifconfig command
interface rather than using single network interface. # ifconfig
In this how to, I will use only two interfaces as
example. The output should be something like below
1. Create bond configuration file (example bond0) bond0 Link encap:Ethernet HWaddr
# vim /etc/sysconfig/network-scripts/ifcfg-bond0 00:0C:29:C6:BE:59
inet addr:192.168.1.20 Bcast:192.168.1.255
Mask:255.255.255.0
2. Put below configuration inside the bond0 inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link
configuration file UP BROADCAST RUNNING MASTER MULTICAST
DEVICE=bond0 MTU:1500 Metric:1
IPADDR=192.168.1.20 RX packets:2804 errors:0 dropped:0 overruns:0
NETWORK=192.168.1.0 frame:0
NETMASK=255.255.255.0 TX packets:1879 errors:0 dropped:0 overruns:0
USERCTL=no carrier:0
BOOTPROTO=none collisions:0 txqueuelen:0
ONBOOT=yes RX bytes:250825 (244.9 KiB) TX bytes:244683
(238.9 KiB)
Replace above ip address, network and netmask with
actual details and save the configuration file eth0 Link encap:Ethernet HWaddr
00:0C:29:C6:BE:59
inet addr:192.168.1.20 Bcast:192.168.1.255
3. Open the first network interface configuration file Mask:255.255.255.0
# vim /etc/sysconfig/network-scripts/ifcfg-eth0 inet6 addr: fe80::20c:29ff:fec6:be59/64
Scope:Link
UP BROADCAST RUNNING SLAVE MULTICAST
4. Append with the below details and save MTU:1500 Metric:1
DEVICE=eth0 RX packets:2809 errors:0 dropped:0 overruns:0
USERCTL=no frame:0
ONBOOT=yes TX packets:1390 errors:0 dropped:0 overruns:0
MASTER=bond0 carrier:0
SLAVE=yes collisions:0 txqueuelen:1000
BOOTPROTO=none RX bytes:251161 (245.2 KiB) TX bytes:180289
(176.0 KiB)
5. Open the second network interface configuration Interrupt:11 Base address:0x1400
file
eth1 Link encap:Ethernet HWaddr
# vim /etc/sysconfig/network-scripts/ifcfg-eth1 00:0C:29:C6:BE:59
inet addr:192.168.1.20 Bcast:192.168.1.255
6. Edit the file to become like below and save Mask:255.255.255.0
DEVICE=eth1 inet6 addr: fe80::20c:29ff:fec6:be59/64
USERCTL=no Scope:Link
ONBOOT=yes UP BROADCAST RUNNING SLAVE MULTICAST
MASTER=bond0 MTU:1500 Metric:1
SLAVE=yes RX packets:4 errors:0 dropped:0 overruns:0
BOOTPROTO=none frame:0
TX packets:502 errors:0 dropped:0 overruns:0
7. Load bond module carrier:0
collisions:0 txqueuelen:1000
# vim /etc/modprobe.d/bonding.conf RX bytes:258 (258.0 b) TX bytes:66516 (64.9
KiB)
Interrupt:10 Base address:0x1480
Installing a DNS for host
lookups
Digital Reef requires that both the Fully Qualified
Domain Name (FQDN) and the short host name be
able to be found in the DNS. In the event a DNS
cannot be configured with the host names and IP
addresses of the Digital Reef nodes, one of the nodes
can be used as a DNS

1. On Fedora 9, use yum to install bind


# yum install bind
2.

You might also like