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
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@centos.org [mailto:centos-bounces@centos.org] On Behalf Of gene.poole@macys.com Sent: Wednesday, April 14, 2010 10:59 AM To: centos@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
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.
On 4/14/2010 9:58 AM, gene.poole@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?
The eth? names are assigned in more or less random order at bootup
Not exactly "random" but not always as expected:) http://linux.dell.com/files/whitepapers/nic-enum-whitepaper-v3.pdf
On Wed, 2010-04-14 at 15:12 +0000, Joseph L. Casale wrote:
The eth? names are assigned in more or less random order at bootup
Not exactly "random" but not always as expected:) http://linux.dell.com/files/whitepapers/nic-enum-whitepaper-v3.pdf
--- Nice paper by Michael.. What I do is disable all the nics in the bios via console rdir of drac 3 -5. Enable one at a time to install then enable the other integrated nics. Then have the the other nic hardware installed. Can also be done remote or local. It eases the frustration. Then you have them in the order you want.
John
Nice paper by Michael.. What I do is disable all the nics in the bios via console rdir of drac 3 -5. Enable one at a time to install then enable the other integrated nics. Then have the the other nic hardware installed. Can also be done remote or local. It eases the frustration. Then you have them in the order you want.
Or use HP's :)
On 14 Apr 2010, at 17:05, "Joseph L. Casale" jcasale@activenetwerx.com wrote:
Or use HP's :)
I had the same issue (admittedly with RedHat 5.3) with an HP server with the on board NICs detected last.
Just edit the ifcfg-ethX files so that MAC refers to the NIC you want it to be.
Ben
Am Mittwoch, den 14.04.2010, 17:58 +0200 schrieb JohnS:
On Wed, 2010-04-14 at 15:12 +0000, Joseph L. Casale wrote:
The eth? names are assigned in more or less random order at bootup
Not exactly "random" but not always as expected:) http://linux.dell.com/files/whitepapers/nic-enum-whitepaper-v3.pdf
Nice paper by Michael.. What I do is disable all the nics in the bios via console rdir of drac 3 -5. Enable one at a time to install then enable the other integrated nics. Then have the the other nic hardware installed. Can also be done remote or local. It eases the frustration. Then you have them in the order you want.
John
We use spacewalk integraed cobbler for installation it takes the mac addresses as input for nic configuration and cares about that problem in a nice way.
Chris
financial.com AG
Munich head office/Hauptsitz München: Maria-Probst-Str. 19 | 80939 München | Germany Frankfurt branch office/Niederlassung Frankfurt: Messeturm | Friedrich-Ebert-Anlage 49 | 60327 Frankfurt | Germany Management board/Vorstand: Dr. Steffen Boehnert | Dr. Alexis Eisenhofer | Dr. Yann Samson | Matthias Wiederwach Supervisory board/Aufsichtsrat: Dr. Dr. Ernst zur Linden (chairman/Vorsitzender) Register court/Handelsregister: Munich – HRB 128 972 | Sales tax ID number/St.Nr.: DE205 370 553
On 4/14/2010 11:16 AM, Christoph Maser wrote:
Nice paper by Michael.. What I do is disable all the nics in the bios via console rdir of drac 3 -5. Enable one at a time to install then enable the other integrated nics. Then have the the other nic hardware installed. Can also be done remote or local. It eases the frustration. Then you have them in the order you want.
John
We use spacewalk integraed cobbler for installation it takes the mac addresses as input for nic configuration and cares about that problem in a nice way.
I usually build disk images to be installed in other locations in as-yet-unknown machines - so the guy installing ends up plugging in one cable at a time, using mii-tool to see which link came up, and assigning the IP for that subnet, then going to the next. Not handy, but it works and doesn't take that much more time than dealing with MAC addresses would.
From: "gene.poole@macys.com" gene.poole@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@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@macys.com (gene.poole@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@centos.org http://lists.centos.org/mailman/listinfo/centos
----- Original Message ----
From: Jobst Schmalenbach jobst@barrett.com.au To: centos@centos.org Sent: Thu, April 15, 2010 1:20:45 AM Subject: Re: [CentOS] How Do I ...
;-)
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! ;-)
Then came blade servers with built-in nics you can't unplug because they're plugged to the blade center enclosure's internal switches :)
I had an awful time trying to install a bunch of servers via PXE, the server booted from one nic, then tried to configure eth0 which was ANOTHER nic which was (of course) connected to a different built in switch and the installation failed because it couldn't access the kickstart file.
We had to trunk the 4 internal switches for the install, then we had to look into the switch's management to see which card was in what port, then modify the ifcfg-ethX to configure each one of the NICs with the right IP
Fer
On 4/15/2010 10:32 AM, Fernando Gleiser wrote:
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! ;-)
Then came blade servers with built-in nics you can't unplug because they're plugged to the blade center enclosure's internal switches :)
Worse, and probably more to the point of non-deterministic hardware detection, you can plug in a USB->ethernet adapter anytime or several in any order.
Yeah, but that has an advantage!
After you plug in the USB-nic you can do an ifconfig and immediately know the HW address ... make up an "ifcfg-ethX" for that ... plug in the next one ... ifconfig ... make up an "ifcfg-ethx" for that one and so on.
I use this method to tap into bridged adsl connections, VOIP interfaces etc ...
jobst
On Thu, Apr 15, 2010 at 11:10:18AM -0500, Les Mikesell (lesmikesell@gmail.com) wrote:
On 4/15/2010 10:32 AM, Fernando Gleiser wrote:
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! ;-)
Then came blade servers with built-in nics you can't unplug because they're plugged to the blade center enclosure's internal switches :)
Worse, and probably more to the point of non-deterministic hardware detection, you can plug in a USB->ethernet adapter anytime or several in any order.
-- Les Mikesell lesmikesell@gmail.com _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Then came blade servers with built-in nics you can't unplug because they're plugged to the blade center enclosure's internal switches :)
ok, granted:
2 (OUCH)
Jobst
On Thu, Apr 15, 2010 at 08:32:06AM -0700, Fernando Gleiser (fergleiser@yahoo.com) wrote:
----- Original Message ----
From: Jobst Schmalenbach jobst@barrett.com.au To: centos@centos.org Sent: Thu, April 15, 2010 1:20:45 AM Subject: Re: [CentOS] How Do I ...
;-)
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! ;-)
I had an awful time trying to install a bunch of servers via PXE, the server booted from one nic, then tried to configure eth0 which was ANOTHER nic which was (of course) connected to a different built in switch and the installation failed because it couldn't access the kickstart file.
We had to trunk the 4 internal switches for the install, then we had to look into the switch's management to see which card was in what port, then modify the ifcfg-ethX to configure each one of the NICs with the right IP
Fer
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
-
Benjamin Donnachie -
Christoph Maser -
Fernando Gleiser -
Gabriel Rosca -
gene.poole＠macys.com -
Jobst Schmalenbach -
John Doe -
JohnS -
Joseph L. Casale -
Kahlil Hodgson -
Les Mikesell