{"id":457,"date":"2012-09-15T19:02:06","date_gmt":"2012-09-15T16:02:06","guid":{"rendered":"http:\/\/fatihacar.com\/blog\/?p=457"},"modified":"2012-09-26T13:17:57","modified_gmt":"2012-09-26T10:17:57","slug":"ethernet-bonding-on-oracle-linux-6","status":"publish","type":"post","link":"http:\/\/www.fatihacar.com\/blog\/ethernet-bonding-on-oracle-linux-6\/","title":{"rendered":"Ethernet Bonding on Oracle Linux 6"},"content":{"rendered":"<p>Bonding technology provides an additional benefit in that with multiple network interfaces effectively supporting the same communications channel, a fault within a single network interface in a bonded group does not stop communication. For example, you have a bonded setup with four network interfaces providing a single interface channel between two DRBD servers. If one network interface fails, communication can continue on the other three without interruption, although at a lower speed.<\/p>\n<p>I will give an example for bonding. I will use 4 ethernet interface for 2 different connection areas which are public and private connections. You can use these connections for cluster systems.<\/p>\n<p>You have to do below processes with root user. <\/p>\n<p><strong>Disable Network Manager<\/strong><\/p>\n<blockquote><p>\nservice NetworkManager stop<br \/>\nchkconfig NetworkManager off\n<\/p><\/blockquote>\n<p><strong>Create bond0 and bond1 Interface<\/strong><\/p>\n<blockquote><p>\nvi \/etc\/sysconfig\/network-scripts\/ifcfg-bond0<\/p>\n<blockquote><p>\nDEVICE=&#8221;bond0&#8243;<br \/>\nBROADCAST=&#8221;192.168.10.255&#8243;<br \/>\nGATEWAY=&#8221;192.168.10.1&#8243;<br \/>\nIPADDR=&#8221;192.168.10.10&#8243;<br \/>\nNETMASK=&#8221;255.255.255.0&#8243;<br \/>\nONBOOT=&#8221;yes&#8221;<br \/>\nUSERCTL=no<br \/>\nBONDING_OPTS=&#8221;mode=0 miimon=100 downdelay=300 updelay=300&#8243;\n<\/p><\/blockquote>\n<p>vi \/etc\/sysconfig\/network-scripts\/ifcfg-bond1<\/p>\n<blockquote><p>\nDEVICE=&#8221;bond1&#8243;<br \/>\nBROADCAST=&#8221;192.168.10.255&#8243;<br \/>\nGATEWAY=&#8221;192.168.10.1&#8243;<br \/>\nIPADDR=&#8221;192.168.10.12&#8243;<br \/>\nNETMASK=&#8221;255.255.255.0&#8243;<br \/>\nONBOOT=&#8221;yes&#8221;<br \/>\nUSERCTL=no<br \/>\nBONDING_OPTS=&#8221;mode=0 miimon=100 downdelay=300 updelay=300&#8243;\n<\/p><\/blockquote>\n<\/blockquote>\n<p>You can then configure additional parameters for the kernel module. Typical parameters are the mode option and the miimon option.<\/p>\n<p>The mode option specifies how the network interfaces are used. The default setting is 0, which means that each network interface is used in a round-robin fashion (this supports aggregation and fault tolerance). Using setting 1 sets the bonding mode to active-backup. This means that only one network interface is used as a time, but that the link automatically fails over to a new interface if the primary interface fails. This settings only supports fault-tolerance.<\/p>\n<p>The miimon option enables the MII link monitoring. A positive value greater than zero indicates the monitoring frequency in milliseconds for checking each slave network interface that is configured as part of the bonded interface. A typical value is 100.<br \/>\n<!--more--><br \/>\n<strong>Configure eth0 and eth1 Interfaces for bond0 (Add or Change Below Texts)<\/strong><\/p>\n<blockquote><p>\nvi \/etc\/sysconfig\/network-scripts\/ifcfg-eth0<\/p>\n<blockquote><p>\nDEVICE=eth0<br \/>\nBOOTPROTO=none<br \/>\nMASTER=bond0<br \/>\nHWADDR=00:01:02:03:04:05<br \/>\nONBOOT=yes<br \/>\nSLAVE=yes<br \/>\nUSERCTL=no\n<\/p><\/blockquote>\n<p>vi \/etc\/sysconfig\/network-scripts\/ifcfg-eth1<\/p>\n<blockquote><p>\nDEVICE=eth1<br \/>\nBOOTPROTO=none<br \/>\nMASTER=bond0<br \/>\nHWADDR=00:01:02:03:04:06<br \/>\nONBOOT=yes<br \/>\nSLAVE=yes<br \/>\nUSERCTL=no\n<\/p><\/blockquote>\n<\/blockquote>\n<p><strong>Change eth2 and eth3 Interfaces for bond1<\/strong><\/p>\n<blockquote><p>\nvi \/etc\/sysconfig\/network-scripts\/ifcfg-eth2<\/p>\n<blockquote><p>\nDEVICE=eth2<br \/>\nBOOTPROTO=none<br \/>\nMASTER=bond1<br \/>\nHWADDR=00:01:02:03:04:50<br \/>\nONBOOT=yes<br \/>\nSLAVE=yes<br \/>\nUSERCTL=no\n<\/p><\/blockquote>\n<p>vi \/etc\/sysconfig\/network-scripts\/ifcfg-eth3<\/p>\n<blockquote><p>\nDEVICE=eth3<br \/>\nBOOTPROTO=none<br \/>\nMASTER=bond1<br \/>\nHWADDR=00:01:02:03:04:60<br \/>\nONBOOT=yes<br \/>\nSLAVE=yes<br \/>\nUSERCTL=no\n<\/p><\/blockquote>\n<\/blockquote>\n<p><strong>Configure Modprobe<\/strong><\/p>\n<blockquote><p>\nvi \/etc\/modprobe.d\/bonding.conf<\/p>\n<blockquote><p>\nalias eth0 e1000e<br \/>\nalias eth1 e1000e<br \/>\nalias eth2 e1000e<br \/>\nalias eth3 e1000e<br \/>\nalias bond0 bonding<br \/>\nalias bond1 bonding\n<\/p><\/blockquote>\n<\/blockquote>\n<p><strong>Network Restart<\/strong><\/p>\n<blockquote><p>\nmodprobe bonding<br \/>\nservice network restart<\/p>\n<p><strong>Note :<\/strong> If you do not see below screen, you can reboot system.\n<\/p><\/blockquote>\n<p><img loading=\"lazy\" decoding=\"async\" src=\"http:\/\/fatihacar.com\/blog\/resimler\/bonding.jpg\" alt=\"\" title=\"bonding\" width=\"552\" height=\"123\" class=\"alignleft size-full wp-image-472\" srcset=\"http:\/\/www.fatihacar.com\/blog\/resimler\/bonding.jpg 552w, http:\/\/www.fatihacar.com\/blog\/resimler\/bonding-300x66.jpg 300w\" sizes=\"auto, (max-width: 552px) 100vw, 552px\" \/><\/p>\n<p>Finally, You can use these configurations on Oracle Linux 6.x, Redhat Linux 6.x, Centos 6.x.<\/p>\n<p>Source : Oracle Offical Documents<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Bonding technology provides an additional benefit in that with multiple network interfaces effectively supporting the same communications channel, a fault within a single network interface in a bonded group does not stop communication. For example, you have a bonded setup with four network interfaces providing a single interface channel between two DRBD servers. If one&#8230;<\/p>\n","protected":false},"author":37,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"jetpack_post_was_ever_published":false,"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_memberships_contains_paid_content":false,"footnotes":""},"categories":[18],"tags":[31,22],"class_list":["post-457","post","type-post","status-publish","format-standard","hentry","category-linux-unix","tag-linux-administration","tag-system-administration"],"jetpack_featured_media_url":"","jetpack_shortlink":"https:\/\/wp.me\/p39NFI-7n","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"http:\/\/www.fatihacar.com\/blog\/wp-json\/wp\/v2\/posts\/457","targetHints":{"allow":["GET"]}}],"collection":[{"href":"http:\/\/www.fatihacar.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/www.fatihacar.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/www.fatihacar.com\/blog\/wp-json\/wp\/v2\/users\/37"}],"replies":[{"embeddable":true,"href":"http:\/\/www.fatihacar.com\/blog\/wp-json\/wp\/v2\/comments?post=457"}],"version-history":[{"count":25,"href":"http:\/\/www.fatihacar.com\/blog\/wp-json\/wp\/v2\/posts\/457\/revisions"}],"predecessor-version":[{"id":484,"href":"http:\/\/www.fatihacar.com\/blog\/wp-json\/wp\/v2\/posts\/457\/revisions\/484"}],"wp:attachment":[{"href":"http:\/\/www.fatihacar.com\/blog\/wp-json\/wp\/v2\/media?parent=457"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/www.fatihacar.com\/blog\/wp-json\/wp\/v2\/categories?post=457"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/www.fatihacar.com\/blog\/wp-json\/wp\/v2\/tags?post=457"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}