Linux - ServerThis forum is for the discussion of Linux Software used in a server related context.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I am a support technician for Atlas Networks.
I have a very strange CentOS issue.
I originally installed CentOS on a SuperMicro board, with the intent to move the drive to a different newer board.
After the move, the Intel network interface on the new board appears to not be seem by CentOS. lsmod shows the e1000e module loaded, and it makes no difference.
I have taken the new system and installed Centos, and verified that it will use the NIC natively, so this is not a 'missing module' issue.
The original board is a Super Micro X8STI-F
The newboard is an Intel DX79T0
The system this CentOS installation is running on is a Production server, so I am not open to just 'Try' things with out a definitive solution, or at least something that sounds very promising.
check the status or whether the nic is present or not
mii-tool -v
lspci -v "check the nic type, if "e1000e" something is showing then go to the Intel site & download the driver for the linux & install the gcc for compiler gcc compiler is required to install the driver
#yum install gcc*
then untar the pkg of the drive
tar zxf e1000e-<x.x.x>.tar.gz
Change to the driver src directory, where <x.x.x> is the version number for the driver tar:
Try typing "ifconfig -a" to see if the card has been given another name such as eth1 or eth2. I've noticed RHEL-based distros tend to hard-code the hardware address of the network adapters into their config files (for eth0 this config file is /etc/sysconfig/network-scripts/ifcfg-eth0). This is done so that interfaces do not change names when cards are added or removed. However, it means that if you move a drive to a new server, the network interface will not be called eth0 (since the system thinks eth0 should have a different hardware address). You'll need to edit the HWADDR line in the config file to change this or simply use the new interface name.
Try typing "ifconfig -a" to see if the card has been given another name such as eth1 or eth2. I've noticed RHEL-based distros tend to hard-code the hardware address of the network adapters into their config files (for eth0 this config file is /etc/sysconfig/network-scripts/ifcfg-eth0). This is done so that interfaces do not change names when cards are added or removed. However, it means that if you move a drive to a new server, the network interface will not be called eth0 (since the system thinks eth0 should have a different hardware address). You'll need to edit the HWADDR line in the config file to change this or simply use the new interface name.
This did it. It runs out it was assigned eth2. I am used to debian, so CentOS and RHEL is new for me.
Thanks for your help.
This did it. It runs out it was assigned eth2. I am used to debian, so CentOS and RHEL is new for me.
Thanks for your help.
If you look in /etc/udev/rules.d/70-persistent-net.rules (or maybe 60-net.rules) you should see your physical device and its alias to eth2. You may see other ethernet devices here as well. If you reorder the device names in the udev rules (as well as update the corresponding HWADDR lines in /etc/sysconfig/network-scripts/ifcfg-ethX), then reboot, it will map the devices in the desired manner.
It can be a bit annoying that devices that have been removed still occupy their ethX interface alias. If there are old devices (no longer on the system), you can delete the lines referring to these lines entirely.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.