Change the scripts under /etc/sysconfig/network-scr
Main Topics
Browse All TopicsHi All,
I have Suse linux 9.3 installed on HP DL585 server.
There are 2 on-board NICs, and initially they are shown as eth0 and eth1.
After putting a quad-port NIC card, the on-board NIC names changed to eth4 and eth5. Add-on NICs got eth0 through eth3 names.
I want to change the NIC name from eth4 to eth0, I tried by adding PERSISTENT_NAME='eth0' to scripts in /etc/sysconfig/network/.
When I rebooted or /etc/init.d/network restart, it says
rename from eth4 to eth0 failed, file already exists. something like this.
I tried some other options but in vain.
Please let me know how can I fix this.
Thanks in advance.
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
Business Accounts
Answer for Membership
by: qualipsoftPosted on 2009-06-26 at 23:33:31ID: 24726564
1. check the udev rules under /etc/udev/rules.d/70-persi stent-net. rules (file name may differ in your distribution). These rules are used to automatically rename interfaces too.
2. It is a known issue with the current Linux kernels that interface name collisions occur, for the persistent names, use either higher numbers (e.g.: eth10, eth11, ...) or even a different prefix (e.g.: peth1, peth2, ... for "persistent"-eth) although this *may* cause issues with programs that rely on this prefix, but these are few.
There has been various discussions over a new set of kernel-supported naming rules in the linux net mailing list... change is coming.
In the mean time, good luck!