All, I've got a machine running CentOS 5.3 and this machine has got 2 - built-in 1 Gig NICs and a expansion card with 4 - 100 Meg NICs. For whatever reason at install time, it made the expansion card eth0 through eth3 and the internal ports eth4 and eth5. And by default the 'machine' is known on the network by the eth0 NIC, so my throughput is limited to 100 Mb. How can I force the internal NICs to be eth0 and eth1? Thanks, Gene Poole -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.centos.org/pipermail/centos/attachments/20100414/879b7c11/attachment-0002.html>
>How can I force the internal NICs to be eth0 and eth1?Edit the hardware address in the ifcfg-ethx scripts and the ips of the nics in question to be on the subnet of choice and arrangement of choice. Add a route statement or I think placing your gateway line in the eth cfg script should do that.
You can go to /etc/sysconfig/network-scripts , edit and move around ifcfg-ethX files Gabe From: centos-bounces at centos.org [mailto:centos-bounces at centos.org] On Behalf Of gene.poole at macys.com Sent: Wednesday, April 14, 2010 10:59 AM To: centos at centos.org Subject: [CentOS] How Do I ... All, I've got a machine running CentOS 5.3 and this machine has got 2 - built-in 1 Gig NICs and a expansion card with 4 - 100 Meg NICs. For whatever reason at install time, it made the expansion card eth0 through eth3 and the internal ports eth4 and eth5. And by default the 'machine' is known on the network by the eth0 NIC, so my throughput is limited to 100 Mb. How can I force the internal NICs to be eth0 and eth1? Thanks, Gene Poole -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.centos.org/pipermail/centos/attachments/20100414/05c95567/attachment-0002.html>
On 4/14/2010 9:58 AM, gene.poole at macys.com wrote:> All, > > I've got a machine running CentOS 5.3 and this machine has got 2 - > built-in 1 Gig NICs and a expansion card with 4 - 100 Meg NICs. For > whatever reason at install time, it made the expansion card eth0 through > eth3 and the internal ports eth4 and eth5. And by default the 'machine' > is known on the network by the eth0 NIC, so my throughput is limited to > 100 Mb. How can I force the internal NICs to be eth0 and eth1?The eth? names are assigned in more or less random order at bootup, but once configured are tied to the NICs by the ethernet hardware addresses. The easy approach is to leave the names the same but change the IP addresses assigned to them. Do you have a GUI setup where you can run system-config-network? -- Les Mikesell lesmikesell at gmail.com
On 4/14/2010 10:04 AM, Gabriel Rosca wrote:> You can go to /etc/sysconfig/network-scripts , edit and move around > ifcfg-ethX files >But you can't just rename them. They have the device name inside the file also and are tied to the corresponding NIC by the hardware address. -- Les Mikesell lesmikesell at gmail.com
From: "gene.poole at macys.com" <gene.poole at macys.com>> I've got a machine running CentOS 5.3 > and this machine has got 2 - built-in 1 Gig NICs and a expansion card with > 4 - 100 Meg NICs. For whatever reason at install time, it made the > expansion card eth0 through eth3 and the internal ports eth4 and eth5. > And by default the 'machine' is known on the network by the eth0 NIC, so > my throughput is limited to 100 Mb. How can I force the internal > NICs to be eth0 and eth1?Maybe look at /etc/modprobe.conf Don't forget to change the MACs JD
On 04/15/2010 12:58 AM, gene.poole at macys.com wrote:> I've got a machine running CentOS 5.3 and this machine has got 2 - > built-in 1 Gig NICs and a expansion card with 4 - 100 Meg NICs. For > whatever reason at install time, it made the expansion card eth0 through > eth3 and the internal ports eth4 and eth5. And by default the 'machine' > is known on the network by the eth0 NIC, so my throughput is limited to > 100 Mb. How can I force the internal NICs to be eth0 and eth1?I had a similar problem when an onboard NIC died on me and I had to shuffle ports to keep things running while I went shopping for a new mainboard. Port numbers are assigned by udev during startup and assignment is initially somewhat arbitrary and udev may shuffle the ports around by calling /lib/udev/rename_device. That program looks at your ifcfg-ethX scripts in /etc/sysconfig/network-scripts for lines like DEVICE=eth4 HWADDR=00:e0:4c:50:19:95 Therein lies your solution. Use, say, 'ifconfig' to map out the current HWADDR lines, and edit (and/or rename) the ifcfg-ethX scripts to suite. Just be sure to keep the DEVICE setting in sync with the name of the file. Hope this helps, Kal
;-) in the olden days it was so easy, you had PCI cards and they were named by the slot number, starting with eth0 in PCI slot 1 and so on. Then came the inbuilt nics Then came the PCIx built nics Then came the PCI-e built nics OUCH! ;-) run ifconfig and get all hardware addresses first AND(!) look at the hardware, its written on them and for inbuilt nics its written on the plug (sometimes you can see it in the bios as well). If you not sure which hardware address belongs to which you can unplug and plug ONE cable at a time AND "tail -f /var/log/messages" and see what ethX number was unplugged ... write the details of THAT card down (one at a time). Name the ifcfg-ethX file in /etc/sysconfig/network-scripts/ in order (IMPORTANT), e.g.: -rw-r--r-- 1 root root 480 Apr 02 23:47 ifcfg-A_eth0 -rw-r--r-- 1 root root 245 Apr 02 23:48 ifcfg-B_eth1 -rw-r--r-- 1 root root 258 Apr 02 23:49 ifcfg-C_eth2 -rw-r--r-- 1 root root 258 Apr 02 23:50 ifcfg-D_eth3 make sure that the names of the config files begin with "ifcfg-" or it will not work. Then you edit these files and set the hardware addresses and other (ipaddresses etc) The reason why you do this: if for example the nics have the same driver, by naming them in order at boot time there are INITIALIZED IN THAT ORDER. This too makes sure that the kernel knows what **you** think is the order. I have a server that has 5 different nics in it, with 2 PCI, 1 PCI-e, 2 inbuilt. I have them working correctly every boot, in the same order, correct IP and everything. jobst On Wed, Apr 14, 2010 at 10:58:36AM -0400, gene.poole at macys.com (gene.poole at macys.com) wrote:> All, > > I've got a machine running CentOS 5.3 and this machine has got 2 - > built-in 1 Gig NICs and a expansion card with 4 - 100 Meg NICs. For > whatever reason at install time, it made the expansion card eth0 through > eth3 and the internal ports eth4 and eth5. And by default the 'machine' is > known on the network by the eth0 NIC, so my throughput is limited to 100 > Mb. How can I force the internal NICs to be eth0 and eth1? > > Thanks, > Gene Poole> _______________________________________________ > CentOS mailing list > CentOS at centos.org > http://lists.centos.org/mailman/listinfo/centos-- main(){for (;;) fputc(NULL,rand() % 2);) | |0| | Jobst Schmalenbach, jobst at barrett.com.au, General Manager | | |0| Barrett Consulting Group P/L & The Meditation Room P/L |0|0|0| +61 3 9532 7677, POBox 277, Caulfield South, 3162, Australia