<?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 Linux NIC config in Operating System - Linux</title>
    <link>https://community.hpe.com/t5/operating-system-linux/linux-nic-config/m-p/4516333#M82356</link>
    <description>Hi,&lt;BR /&gt;&lt;BR /&gt;Noticed something very unusual on a BL35p server that I have regarding NIC config. The server fell off the network so I rebooted. After reboot eth1 showed up as connected but the g/w would not respond, eth0 was not configured at /etc/sysconfig/network-scripts/ifcfg-eth0.&lt;BR /&gt;&lt;BR /&gt;I moved ifcfg-eth1 to ifcfg-eth0 and restarted the services but no effect. I then rolled back the change and the g/w responded.&lt;BR /&gt;&lt;BR /&gt;When i checked the server both interfaces (eth0 and eth1) are up and connected – but only ifcfg-eth1 is setup on the server.&lt;BR /&gt;&lt;BR /&gt;Any ideas how this might happen or why?&lt;BR /&gt;&lt;BR /&gt;Rgds,&lt;BR /&gt;D.&lt;BR /&gt;</description>
    <pubDate>Mon, 19 Oct 2009 08:03:00 GMT</pubDate>
    <dc:creator>Duffs</dc:creator>
    <dc:date>2009-10-19T08:03:00Z</dc:date>
    <item>
      <title>Linux NIC config</title>
      <link>https://community.hpe.com/t5/operating-system-linux/linux-nic-config/m-p/4516333#M82356</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;Noticed something very unusual on a BL35p server that I have regarding NIC config. The server fell off the network so I rebooted. After reboot eth1 showed up as connected but the g/w would not respond, eth0 was not configured at /etc/sysconfig/network-scripts/ifcfg-eth0.&lt;BR /&gt;&lt;BR /&gt;I moved ifcfg-eth1 to ifcfg-eth0 and restarted the services but no effect. I then rolled back the change and the g/w responded.&lt;BR /&gt;&lt;BR /&gt;When i checked the server both interfaces (eth0 and eth1) are up and connected – but only ifcfg-eth1 is setup on the server.&lt;BR /&gt;&lt;BR /&gt;Any ideas how this might happen or why?&lt;BR /&gt;&lt;BR /&gt;Rgds,&lt;BR /&gt;D.&lt;BR /&gt;</description>
      <pubDate>Mon, 19 Oct 2009 08:03:00 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/linux-nic-config/m-p/4516333#M82356</guid>
      <dc:creator>Duffs</dc:creator>
      <dc:date>2009-10-19T08:03:00Z</dc:date>
    </item>
    <item>
      <title>Re: Linux NIC config</title>
      <link>https://community.hpe.com/t5/operating-system-linux/linux-nic-config/m-p/4516334#M82357</link>
      <description>Shalom,&lt;BR /&gt;&lt;BR /&gt;First when you move ifcfg-eth1 to ifcfg-eth0 you need to change:&lt;BR /&gt;DEVICE=eth1&lt;BR /&gt;&lt;BR /&gt;to &lt;BR /&gt;&lt;BR /&gt;DEVICE=eth0&lt;BR /&gt;&lt;BR /&gt;This problem was brought about by either changes to the network configuration of the NIC on the blade complex, or a hardware failure.&lt;BR /&gt;&lt;BR /&gt;The cause of the problem needs to be investigated and corrected.&lt;BR /&gt;&lt;BR /&gt;Your blade complex comes with a bootable DVD that can be used to boot and run hardware diagnostics. I recommend you schedule downtime and do this.&lt;BR /&gt;&lt;BR /&gt;SEP</description>
      <pubDate>Mon, 19 Oct 2009 11:34:12 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/linux-nic-config/m-p/4516334#M82357</guid>
      <dc:creator>Steven E. Protter</dc:creator>
      <dc:date>2009-10-19T11:34:12Z</dc:date>
    </item>
    <item>
      <title>Re: Linux NIC config</title>
      <link>https://community.hpe.com/t5/operating-system-linux/linux-nic-config/m-p/4516335#M82358</link>
      <description>also check for hard coded MAC entry in the config file</description>
      <pubDate>Sun, 25 Oct 2009 09:59:22 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/linux-nic-config/m-p/4516335#M82358</guid>
      <dc:creator>skt_skt</dc:creator>
      <dc:date>2009-10-25T09:59:22Z</dc:date>
    </item>
  </channel>
</rss>

