On Tue, Dec 11, 2012 at 5:53 PM, Balasubramaniam Natarajan <[email protected]> wrote: > On Wed, Dec 5, 2012 at 11:33 AM, Arun Khan <[email protected]> wrote: > >> >> > The trouble is I did not pull out the nic card on this server and replace >> > the nic after installation for me to face this problem. >> >> I don't understand what you are saying above. >> > > I ment that if I had replaced the NIC card on the server then it is okay > for the OS to have named my nic card in that increasing order, however it > this case all I did was to reboot the machine and eth0 became eth5.
I don't have your persistent rules file handy. I have not seen the contents change *unless* there is some hardware change - removal does not delete it's respective entry and addition creates an new entry with the eth number bumped up. > Please state your problem clearly. What you kind of hardware you are >> dealing with, what are you doing with that hardware. >> >> > I am using Dell Rack based server, which has four ethernet card. While > installing the system I configure eth0 to be my mgmt interface. Then I ran > apt-get update and apt-get upgrade, then rebooted the system when I faced > this problem of eth0 never came up :-( > > >> Brute force solution - empty the persistent net rules file and reboot. >> udev will recreate the entries in the file and assign device eth* >> names in the order it sees them. Edit the file to your liking i.e. >> which NIC (aka mac address) you want to assign to respective eth* >> names. >> > What Linux distro and version number? > This worked on an instance, thanks. However how do I make sure that the OS > does not rename the interface automatically and cause this confusion ? > See above - entries in the persistent rules file should not change mapping of eth name to mac address. You can make a backup copy of the persistent rules file for reference. -- Arun Khan _______________________________________________ ILUGC Mailing List: http://www.ae.iitm.ac.in/mailman/listinfo/ilugc
