Index: [Article Count Order] [Thread]

Date:  Tue, 16 Jan 2007 11:29:17 -0500
From:  "Paul Aviles" <paul.aviles (at mark) nickelnetworks.com>
Subject:  [coba-e:08598] Re: Kernel 2.6.x ethernet port naming
To:  <coba-e (at mark) bluequartz.org>
Message-Id:  <200701161631.l0GGUuJr017106 (at mark) srv1.nickelnetworks.com>
In-Reply-To:  <093701c73972$ad3587d0$0301a8c0@Jerrycp>
X-Mail-Count: 08598

Gerald, I have been using GS10 and GS12 for over 3 years also using up to
2.6.18 most recently and have never seen this issue.

Paul Aviles
Nickel Networks

-----Original Message-----
From: Gerald Waugh [mailto:gwaugh (at mark) frontstreetnetworks.com] 
Sent: Tuesday, January 16, 2007 8:32 AM
To: coba-e (at mark) bluequartz.org
Subject: [coba-e:08592] Kernel 2.6.x ethernet port naming

Interesting...
Linux Kernel 2.6.x finds the ethernet ports in reverse order.
This wasn't a problem with 2.4.x kernels

i.e. on Tyan and MSI servers this is true, eth0 is Lan2 and eth1 is Lan1 I
first found this very confusing as I expected Lan1 to be eth0.
Also this may confuse people in a colo location.

Dell has a workaround... See
http://linux.dell.com/files/whitepapers/nic-enum-whitepaper-v3.pdf
I haven'tried this yet but looks like it should work.
As one 'manual' solution was to add the HWADDR="MAC address" in the Network
scripts /etc/sysconfig/network-scripts/ifcfg-eth0 and eth1

They have a script which will do this "name_eths"
I assume;
http://linux.dell.com/files/name_eths/name_eths-0.4.tar.gz
Anyway, read the whitepaper, and try on a test server.
I'll test later today, but don't have time at the moment.

Gerald


--
This message has been scanned for viruses and dangerous content by
MailScanner, and is believed to be clean.