<?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: DL 385 G2 Network device name issue in Operating System - Linux</title>
    <link>https://community.hpe.com/t5/operating-system-linux/dl-385-g2-network-device-name-issue/m-p/5146256#M81817</link>
    <description>Shalom Sudeesh,&lt;BR /&gt;&lt;BR /&gt;This will probably be corrected by upgrading the firmware of the system.&lt;BR /&gt;&lt;BR /&gt;I thought the DL385 G2 would not take a 64 bit OS. You might want to check the support matrix on this. I know the G2 DL360 won't take 64 bit OS. &lt;BR /&gt;&lt;BR /&gt;The OS could be a contributing to the problem.&lt;BR /&gt;&lt;BR /&gt;SEP</description>
    <pubDate>Sun, 14 Dec 2008 18:03:50 GMT</pubDate>
    <dc:creator>Steven E. Protter</dc:creator>
    <dc:date>2008-12-14T18:03:50Z</dc:date>
    <item>
      <title>DL 385 G2 Network device name issue</title>
      <link>https://community.hpe.com/t5/operating-system-linux/dl-385-g2-network-device-name-issue/m-p/5146255#M81816</link>
      <description>Hi All,&lt;BR /&gt;&lt;BR /&gt;I have installed RHEL 5.2 x86_64 on a proline DL 385 G2 and getting some issue with network interface device names.&lt;BR /&gt;&lt;BR /&gt;System got both Intel and Broadcom NICs. In each reboot they get diffrent device names assigned. How to set the driver to assign a fixed device name every time?&lt;BR /&gt;&lt;BR /&gt;I have dowloaded latest driver from HP and installed them.&lt;BR /&gt;&lt;BR /&gt;Your help will be much appreciated.&lt;BR /&gt;&lt;BR /&gt;Thanks&lt;BR /&gt;&lt;BR /&gt;Sudeesh</description>
      <pubDate>Sun, 14 Dec 2008 06:34:53 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/dl-385-g2-network-device-name-issue/m-p/5146255#M81816</guid>
      <dc:creator>Sudeesh</dc:creator>
      <dc:date>2008-12-14T06:34:53Z</dc:date>
    </item>
    <item>
      <title>Re: DL 385 G2 Network device name issue</title>
      <link>https://community.hpe.com/t5/operating-system-linux/dl-385-g2-network-device-name-issue/m-p/5146256#M81817</link>
      <description>Shalom Sudeesh,&lt;BR /&gt;&lt;BR /&gt;This will probably be corrected by upgrading the firmware of the system.&lt;BR /&gt;&lt;BR /&gt;I thought the DL385 G2 would not take a 64 bit OS. You might want to check the support matrix on this. I know the G2 DL360 won't take 64 bit OS. &lt;BR /&gt;&lt;BR /&gt;The OS could be a contributing to the problem.&lt;BR /&gt;&lt;BR /&gt;SEP</description>
      <pubDate>Sun, 14 Dec 2008 18:03:50 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/dl-385-g2-network-device-name-issue/m-p/5146256#M81817</guid>
      <dc:creator>Steven E. Protter</dc:creator>
      <dc:date>2008-12-14T18:03:50Z</dc:date>
    </item>
    <item>
      <title>Re: DL 385 G2 Network device name issue</title>
      <link>https://community.hpe.com/t5/operating-system-linux/dl-385-g2-network-device-name-issue/m-p/5146257#M81818</link>
      <description>You can use udev to assign permanent names for network cards - &lt;A href="http://reactivated.net/writing_udev_rules.html#example-netif" target="_blank"&gt;http://reactivated.net/writing_udev_rules.html#example-netif&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;regards,&lt;BR /&gt;ivan</description>
      <pubDate>Sun, 14 Dec 2008 20:46:17 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/dl-385-g2-network-device-name-issue/m-p/5146257#M81818</guid>
      <dc:creator>Ivan Krastev</dc:creator>
      <dc:date>2008-12-14T20:46:17Z</dc:date>
    </item>
    <item>
      <title>Re: DL 385 G2 Network device name issue</title>
      <link>https://community.hpe.com/t5/operating-system-linux/dl-385-g2-network-device-name-issue/m-p/5146258#M81819</link>
      <description>Thanks for the replies.&lt;BR /&gt;&lt;BR /&gt;Its a DL 385 G5 and not G2. im sorry for the typo.&lt;BR /&gt;&lt;BR /&gt;I still have to test the udev procedure</description>
      <pubDate>Mon, 15 Dec 2008 16:25:56 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/dl-385-g2-network-device-name-issue/m-p/5146258#M81819</guid>
      <dc:creator>Sudeesh</dc:creator>
      <dc:date>2008-12-15T16:25:56Z</dc:date>
    </item>
    <item>
      <title>Re: DL 385 G2 Network device name issue</title>
      <link>https://community.hpe.com/t5/operating-system-linux/dl-385-g2-network-device-name-issue/m-p/5146259#M81820</link>
      <description>Check the firmware then and try Ivan's procedure.&lt;BR /&gt;&lt;BR /&gt;SEP</description>
      <pubDate>Mon, 15 Dec 2008 18:06:13 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/dl-385-g2-network-device-name-issue/m-p/5146259#M81820</guid>
      <dc:creator>Steven E. Protter</dc:creator>
      <dc:date>2008-12-15T18:06:13Z</dc:date>
    </item>
    <item>
      <title>Re: DL 385 G2 Network device name issue</title>
      <link>https://community.hpe.com/t5/operating-system-linux/dl-385-g2-network-device-name-issue/m-p/5146260#M81821</link>
      <description>I could finally fix the issue with putting entries in /etc/modprobe.conf and specifying HWADDR in /etc/sysconfig/network-scripts/ifcfg-eth# files. &lt;BR /&gt;&lt;BR /&gt;alias eth? bnx2 .. for each NIC&lt;BR /&gt;alias eth? e1000e &lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;I have another issue trying to add VIP for the load balancer. The system becomes unreachable from network after adding the VIP lo:1.&lt;BR /&gt;&lt;BR /&gt;Any idea what is causing this?&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Tue, 16 Dec 2008 13:58:40 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/dl-385-g2-network-device-name-issue/m-p/5146260#M81821</guid>
      <dc:creator>Sudeesh</dc:creator>
      <dc:date>2008-12-16T13:58:40Z</dc:date>
    </item>
    <item>
      <title>Re: DL 385 G2 Network device name issue</title>
      <link>https://community.hpe.com/t5/operating-system-linux/dl-385-g2-network-device-name-issue/m-p/5146261#M81822</link>
      <description>Even the DL385 (original, so G1) is an opteron box thus taking a 64-bit OS which won't even boot unless the box can run it. I have one running debian-amd64 doing my database work.&lt;BR /&gt;&lt;BR /&gt;Anyhoo, is udev installed? It will keep nic assignments constant based on their MAC address. (Which is very interesting if you have autogenerated MAC addresses in a VM...)&lt;BR /&gt;</description>
      <pubDate>Fri, 19 Dec 2008 08:39:53 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/dl-385-g2-network-device-name-issue/m-p/5146261#M81822</guid>
      <dc:creator>Marco Wessel</dc:creator>
      <dc:date>2008-12-19T08:39:53Z</dc:date>
    </item>
    <item>
      <title>Re: DL 385 G2 Network device name issue</title>
      <link>https://community.hpe.com/t5/operating-system-linux/dl-385-g2-network-device-name-issue/m-p/5146262#M81823</link>
      <description>Team,&lt;BR /&gt;&lt;BR /&gt;All issues solved. I got a doc from net on how to set the VIPS for load balancer and disabling arp ... n all those stuff.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Thank you very much for your response.&lt;BR /&gt;</description>
      <pubDate>Fri, 19 Dec 2008 16:31:30 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/dl-385-g2-network-device-name-issue/m-p/5146262#M81823</guid>
      <dc:creator>Sudeesh</dc:creator>
      <dc:date>2008-12-19T16:31:30Z</dc:date>
    </item>
    <item>
      <title>Re: DL 385 G2 Network device name issue</title>
      <link>https://community.hpe.com/t5/operating-system-linux/dl-385-g2-network-device-name-issue/m-p/5146263#M81824</link>
      <description>Thank you</description>
      <pubDate>Fri, 19 Dec 2008 16:32:40 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/dl-385-g2-network-device-name-issue/m-p/5146263#M81824</guid>
      <dc:creator>Sudeesh</dc:creator>
      <dc:date>2008-12-19T16:32:40Z</dc:date>
    </item>
  </channel>
</rss>

