Operating System - Linux
1827819 Members
1635 Online
109969 Solutions
New Discussion

DL 385 G2 Network device name issue

 
Sudeesh
Respected Contributor

DL 385 G2 Network device name issue

Hi All,

I have installed RHEL 5.2 x86_64 on a proline DL 385 G2 and getting some issue with network interface device names.

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?

I have dowloaded latest driver from HP and installed them.

Your help will be much appreciated.

Thanks

Sudeesh
The most predictable thing in life is its unpredictability
8 REPLIES 8
Steven E. Protter
Exalted Contributor

Re: DL 385 G2 Network device name issue

Shalom Sudeesh,

This will probably be corrected by upgrading the firmware of the system.

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.

The OS could be a contributing to the problem.

SEP
Steven E Protter
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
Ivan Krastev
Honored Contributor

Re: DL 385 G2 Network device name issue

You can use udev to assign permanent names for network cards - http://reactivated.net/writing_udev_rules.html#example-netif

regards,
ivan
Sudeesh
Respected Contributor

Re: DL 385 G2 Network device name issue

Thanks for the replies.

Its a DL 385 G5 and not G2. im sorry for the typo.

I still have to test the udev procedure
The most predictable thing in life is its unpredictability
Steven E. Protter
Exalted Contributor

Re: DL 385 G2 Network device name issue

Check the firmware then and try Ivan's procedure.

SEP
Steven E Protter
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
Sudeesh
Respected Contributor

Re: DL 385 G2 Network device name issue

I could finally fix the issue with putting entries in /etc/modprobe.conf and specifying HWADDR in /etc/sysconfig/network-scripts/ifcfg-eth# files.

alias eth? bnx2 .. for each NIC
alias eth? e1000e


I have another issue trying to add VIP for the load balancer. The system becomes unreachable from network after adding the VIP lo:1.

Any idea what is causing this?

The most predictable thing in life is its unpredictability
Marco Wessel
Valued Contributor

Re: DL 385 G2 Network device name issue

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.

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...)
Sudeesh
Respected Contributor

Re: DL 385 G2 Network device name issue

Team,

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.


Thank you very much for your response.
The most predictable thing in life is its unpredictability
Sudeesh
Respected Contributor

Re: DL 385 G2 Network device name issue

Thank you
The most predictable thing in life is its unpredictability