{"id":11,"date":"2011-08-28T23:28:26","date_gmt":"2011-08-28T23:28:26","guid":{"rendered":"http:\/\/www.linuxauthority.com\/wordpress\/?p=11"},"modified":"2012-10-30T23:37:08","modified_gmt":"2012-10-30T23:37:08","slug":"network-channel-bonding-teaming-rhel-6-0","status":"publish","type":"post","link":"https:\/\/www.linuxauthority.com\/wordpress\/?p=11","title":{"rendered":"Network Channel Bonding (teaming) RHEL 6.0"},"content":{"rendered":"\n<!-- ALL ADSENSE ADS DISABLED -->\n<p>This procedure did not actually change very much from RHEL 5.0. Knowing the changes however are pretty critical to getting it right.<\/p>\n<p>Gone is the Administrator&#8217;s friend and potential cestpool, \/etc\/modpprobe.conf<\/p>\n<p>Its replaced by anything you want to load in \/etc\/modprobe.d<\/p>\n<p>Naming guidelines? Who needs them. Name the file anything you want.<\/p>\n<p>Procedure: Still pretty darned easy.<\/p>\n<p>Pre-requisite: You need two network connections to the same network subnet. Unlike HP-UX APA (Auto port aggregation) you don&#8217;t normally need special switch configuration. Though it is possible for Cisco switches to mess this up.<\/p>\n<p>I&#8217;m recommending use of a standard naming convention in your shop. I, in a fit of creativity have chosen the name, bonding.conf<\/p>\n<p>All you do is rip the bonding configuration you used from modeprobe.conf on RHEL 5 and put it in the fil:<\/p>\n<p><span style=\"color: #0000ff;\"><strong>\/etc\/modprobe.d\/bonding.conf<\/strong><\/span><br \/>\n<strong>options bond0 miimon=200 mode=5<\/strong><br \/>\n<strong>alias eth0 e1000<\/strong><br \/>\n<strong>alias eth1 e1000<\/strong><\/p>\n<p>This system has two Intel 1 GB cards in it, plugged into the same network and subnet.<\/p>\n<p><strong>[root@viper ~]# cat <span style=\"color: #0000ff;\">\/etc\/sysconfig\/network-scripts\/ifcfg-eth0<\/span><\/strong><br \/>\n<strong># Intel Corporation 82541GI Gigabit Ethernet Controller<\/strong><br \/>\n<strong>DEVICE=eth0<\/strong><br \/>\n<strong>MASTER=bond0<\/strong><br \/>\n<strong>SLAVE=yes<\/strong><br \/>\n<strong>BOOTPROTO=none<\/strong><br \/>\n<strong>USERCTL=no<\/strong><\/p>\n<p><strong>[root@viper ~]# cat <span style=\"color: #0000ff;\">\/etc\/sysconfig\/network-scripts\/ifcfg-eth1<\/span><\/strong><br \/>\n<strong># Intel Corporation 82540EM Gigabit Ethernet Controller<\/strong><br \/>\n<strong>DEVICE=eth1<\/strong><br \/>\n<strong>ONBOOT=yes<\/strong><br \/>\n<strong>MASTER=bond0<\/strong><br \/>\n<strong>SLAVE=yes<\/strong><br \/>\n<strong>BOOTPROTO=none<\/strong><br \/>\n<strong>USERCTL=no<\/strong><\/p>\n<p>Now the all critical bond0 configuration which has not changed.<\/p>\n<p><strong>[root@viper ~]# cat \/etc\/sysconfig\/network-scripts\/ifcfg-bond0<\/strong><br \/>\n<strong>DEVICE=bond0<\/strong><br \/>\n<strong>BOOTPROT=static<\/strong><br \/>\n<strong>IPADDR=192.168.0.200<\/strong><br \/>\n<strong>NETMASK=255.255.255.0<\/strong><\/p>\n<p><strong>GATEWAY=192.168.0.1<\/strong><\/p>\n<p><strong>BROADCAST=192.168.0.255<\/strong><br \/>\n<strong>ONBOOT=yes<\/strong><br \/>\n<strong>TYPE=Bonding<\/strong><br \/>\n<strong>USERCTL=no<\/strong><\/p>\n<p>To implement:<\/p>\n<p><strong>\/sbin\/service network restart<\/strong><\/p>\n<p><strong>[root@viper ~]# service network restart<\/strong><br \/>\n<strong>Shutting down interface bond0:\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 [\u00a0 OK\u00a0 ]<\/strong><br \/>\n<strong>Shutting down loopback interface:\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 [\u00a0 OK\u00a0 ]<\/strong><br \/>\n<strong>Bringing up loopback interface:\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 [\u00a0 OK\u00a0 ]<\/strong><br \/>\n<strong>Bringing up interface bond0:\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 [\u00a0 OK\u00a0 ]<\/strong><\/p>\n<p>One little warning. Red Has put a little tool in the OS called Network manager. It thinks it owns the network configuration.<\/p>\n<p>If you for example copy in the configuration from another system with the intent of changing the IP address on a new one, be quick about it. Copy in ifcfg-bond0 without ifcfg-eth0\/1 and you lose network access to the system.<\/p>\n<p>It is highly recommended you do this with some form of console access.<\/p>\n<p>&nbsp;<\/p>\n<p>&nbsp;<\/p>\n","protected":false},"excerpt":{"rendered":"<p>This procedure did not actually change very much from RHEL 5.0. Knowing the changes however are pretty critical to getting it right. Gone is the Administrator&#8217;s friend and potential cestpool, \/etc\/modpprobe.conf Its replaced by anything you want to load in \/etc\/modprobe.d Naming guidelines? Who needs them. Name the file anything you want. Procedure: Still pretty [&hellip;]<\/p>\n<a role=\"link\" class=\"rtp-readmore\" title=\"Read more on Network Channel Bonding (teaming) RHEL 6.0\" href=\"https:\/\/www.linuxauthority.com\/wordpress\/?p=11\" rel=\"nofollow\">Read More &rarr;<\/a>","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[8],"tags":[],"class_list":["post-11","post","type-post","status-publish","format-standard","hentry","category-networking"],"_links":{"self":[{"href":"https:\/\/www.linuxauthority.com\/wordpress\/index.php?rest_route=\/wp\/v2\/posts\/11"}],"collection":[{"href":"https:\/\/www.linuxauthority.com\/wordpress\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.linuxauthority.com\/wordpress\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.linuxauthority.com\/wordpress\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.linuxauthority.com\/wordpress\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=11"}],"version-history":[{"count":5,"href":"https:\/\/www.linuxauthority.com\/wordpress\/index.php?rest_route=\/wp\/v2\/posts\/11\/revisions"}],"predecessor-version":[{"id":13,"href":"https:\/\/www.linuxauthority.com\/wordpress\/index.php?rest_route=\/wp\/v2\/posts\/11\/revisions\/13"}],"wp:attachment":[{"href":"https:\/\/www.linuxauthority.com\/wordpress\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=11"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.linuxauthority.com\/wordpress\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=11"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.linuxauthority.com\/wordpress\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=11"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}