<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: RHL 6 Enterprise &amp;amp; Bonding NIcs in Operating System - Linux</title>
    <link>https://community.hpe.com/t5/operating-system-linux/rhl-6-enterprise-amp-bonding-nics/m-p/4750203#M81189</link>
    <description>Hi Darren,&lt;BR /&gt;&lt;BR /&gt;/etc/modprobe.conf can be read, if the user creates it.&lt;BR /&gt;The user can also create a file under /etc/modprobe.d&lt;BR /&gt;&lt;BR /&gt;Reference Materials:&lt;BR /&gt;&lt;A href="http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/6/html-single/Deployment_Guide/index.html" target="_blank"&gt;http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/6/html-single/Deployment_Guide/index.html&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;Refer to: 22.7.2. Using Channel Bonding&lt;BR /&gt;&lt;A href="http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/6/html-single/Deployment_Guide/index.html#sec-Using_Channel_Bonding" target="_blank"&gt;http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/6/html-single/Deployment_Guide/index.html#sec-Using_Channel_Bonding&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;Hope this works with your server.&lt;BR /&gt;&lt;BR /&gt;Thanks&lt;BR /&gt;</description>
    <pubDate>Wed, 09 Feb 2011 05:09:21 GMT</pubDate>
    <dc:creator>Suman_1978</dc:creator>
    <dc:date>2011-02-09T05:09:21Z</dc:date>
    <item>
      <title>RHL 6 Enterprise &amp; Bonding NIcs</title>
      <link>https://community.hpe.com/t5/operating-system-linux/rhl-6-enterprise-amp-bonding-nics/m-p/4750202#M81188</link>
      <description>Well I have moved to bonding the NICS on my new DL380 system, but have run into a problem.  I've created the bond0 interface &amp;amp; made the changes in the other nic configurations, but when I go to change the modprobe.conf, that file does not exist, neither does the modprobe.d directory.  Those files to exist in my RHL 5 system but not in the RHL6.  So how do I get them there correctly? (especially since the modprobe has the hardware configuration files.&lt;BR /&gt;&lt;BR /&gt;THanks&lt;BR /&gt;&lt;BR /&gt;Darren</description>
      <pubDate>Tue, 08 Feb 2011 19:40:52 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/rhl-6-enterprise-amp-bonding-nics/m-p/4750202#M81188</guid>
      <dc:creator>Darren Etheridge_2</dc:creator>
      <dc:date>2011-02-08T19:40:52Z</dc:date>
    </item>
    <item>
      <title>Re: RHL 6 Enterprise &amp; Bonding NIcs</title>
      <link>https://community.hpe.com/t5/operating-system-linux/rhl-6-enterprise-amp-bonding-nics/m-p/4750203#M81189</link>
      <description>Hi Darren,&lt;BR /&gt;&lt;BR /&gt;/etc/modprobe.conf can be read, if the user creates it.&lt;BR /&gt;The user can also create a file under /etc/modprobe.d&lt;BR /&gt;&lt;BR /&gt;Reference Materials:&lt;BR /&gt;&lt;A href="http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/6/html-single/Deployment_Guide/index.html" target="_blank"&gt;http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/6/html-single/Deployment_Guide/index.html&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;Refer to: 22.7.2. Using Channel Bonding&lt;BR /&gt;&lt;A href="http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/6/html-single/Deployment_Guide/index.html#sec-Using_Channel_Bonding" target="_blank"&gt;http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/6/html-single/Deployment_Guide/index.html#sec-Using_Channel_Bonding&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;Hope this works with your server.&lt;BR /&gt;&lt;BR /&gt;Thanks&lt;BR /&gt;</description>
      <pubDate>Wed, 09 Feb 2011 05:09:21 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/rhl-6-enterprise-amp-bonding-nics/m-p/4750203#M81189</guid>
      <dc:creator>Suman_1978</dc:creator>
      <dc:date>2011-02-09T05:09:21Z</dc:date>
    </item>
  </channel>
</rss>

