* Re: eth3 becoming /sys/class/net/dev22358
2007-01-31 13:00 eth3 becoming /sys/class/net/dev22358 Jan-Frode Myklebust
@ 2007-01-31 15:25 ` Jan-Frode Myklebust
2007-01-31 16:24 ` Bill Nottingham
` (4 subsequent siblings)
5 siblings, 0 replies; 7+ messages in thread
From: Jan-Frode Myklebust @ 2007-01-31 15:25 UTC (permalink / raw)
To: linux-hotplug
On 2007-01-31, Jan-Frode Myklebust <mykleb@no.ibm.com> wrote:
>
> I could probably fix it by a simple rule looking at SYSFS{address}
> for these two interfaces,
Actually I wasn't able to.. Tried both:
KERNEL="eth*", SYSFS{address}="00:14:5e:4b:5a:17", NAME="eth2"
and simply:
SYSFS{address}="00:14:5e:4b:5a:17", NAME="eth2"
but neither gave me the expected eth2 name after a boot. Just some
seemingly random "dev19887"..
-jf
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CIDÞVDEV
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
^ permalink raw reply [flat|nested] 7+ messages in thread* Re: eth3 becoming /sys/class/net/dev22358
2007-01-31 13:00 eth3 becoming /sys/class/net/dev22358 Jan-Frode Myklebust
2007-01-31 15:25 ` Jan-Frode Myklebust
@ 2007-01-31 16:24 ` Bill Nottingham
2007-01-31 16:36 ` Linas Vepstas
` (3 subsequent siblings)
5 siblings, 0 replies; 7+ messages in thread
From: Bill Nottingham @ 2007-01-31 16:24 UTC (permalink / raw)
To: linux-hotplug
Jan-Frode Myklebust (mykleb@no.ibm.com) said:
> I'm working with a fairly new machine running rhel4u3,
> and for some reason only 2 out of 4 broadcom nics are
> named correctly. I.e. during boot it shows them all named
> correctly:
>
> eth0: Tigon3 [partno(BCM95704A41) rev 2100 PHY(serdes)] (PCIX:133MHz:64-bit) 10/100/1000BaseT Ethernet 00:14:5e:4b:5a:16
> eth1: Tigon3 [partno(BCM95704A41) rev 2100 PHY(serdes)] (PCIX:133MHz:64-bit) 10/100/1000BaseT Ethernet 00:14:5e:4b:5a:17
> eth2: Tigon3 [partno(BCM95704s) rev 2100 PHY(serdes)] (PCIX:133MHz:64-bit) 10/100/1000BaseT Ethernet 00:14:5e:3f:56:04
> eth3: Tigon3 [partno(BCM95704s) rev 2100 PHY(serdes)] (PCIX:133MHz:64-bit) 10/100/1000BaseT Ethernet 00:14:5e:3f:56:05
>
> but for some reason eth2 and eth3 are named dev22358 and
> dev6737. Any ideas why this might be?
Make sure you have ifcfg-ethX files with the correct HWADDR in
them.
Bill
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CIDÞVDEV
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
^ permalink raw reply [flat|nested] 7+ messages in thread* Re: eth3 becoming /sys/class/net/dev22358
2007-01-31 13:00 eth3 becoming /sys/class/net/dev22358 Jan-Frode Myklebust
2007-01-31 15:25 ` Jan-Frode Myklebust
2007-01-31 16:24 ` Bill Nottingham
@ 2007-01-31 16:36 ` Linas Vepstas
2007-01-31 16:37 ` Jan Frode Myklebust
` (2 subsequent siblings)
5 siblings, 0 replies; 7+ messages in thread
From: Linas Vepstas @ 2007-01-31 16:36 UTC (permalink / raw)
To: linux-hotplug
On Wed, Jan 31, 2007 at 02:00:42PM +0100, Jan-Frode Myklebust wrote:
> I'm working with a fairly new machine running rhel4u3,
> and for some reason only 2 out of 4 broadcom nics are
> named correctly. I.e. during boot it shows them all named
> correctly:
>
> but for some reason eth2 and eth3 are named dev22358 and
> dev6737. Any ideas why this might be?
You should crawl through the redhat updates. This problem was
seen on a large variety of machines and situations, and was
eventually fixed. I don't know what the fix was.
--linas
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CIDÞVDEV
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
^ permalink raw reply [flat|nested] 7+ messages in thread* Re: eth3 becoming /sys/class/net/dev22358
2007-01-31 13:00 eth3 becoming /sys/class/net/dev22358 Jan-Frode Myklebust
` (2 preceding siblings ...)
2007-01-31 16:36 ` Linas Vepstas
@ 2007-01-31 16:37 ` Jan Frode Myklebust
2007-01-31 16:57 ` Jan Frode Myklebust
2007-01-31 16:58 ` Bill Nottingham
5 siblings, 0 replies; 7+ messages in thread
From: Jan Frode Myklebust @ 2007-01-31 16:37 UTC (permalink / raw)
To: linux-hotplug
Bill Nottingham <notting@redhat.com> wrote on 31.01.2007 17:24:17:
>
> Make sure you have ifcfg-ethX files with the correct HWADDR in
> them.
Yes, that was it! I removed all HWADDR's from these, and now I see all
nics.
Thanks!
____________________________________________
Med vennlig hilsen / Kind Regards
Jan-Frode Myklebust
IT Specialist
IBM
P.O. Box 75, 4064 Stavanger
Visiting address: Strandsvingen 14, 4032 Stavanger
Tel: +47-519-57142 Mob: +47-908-87424
E-mail: mykleb@no.ibm.com
Jabber: janfrode@tanso.net
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CIDÞVDEV
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
^ permalink raw reply [flat|nested] 7+ messages in thread* Re: eth3 becoming /sys/class/net/dev22358
2007-01-31 13:00 eth3 becoming /sys/class/net/dev22358 Jan-Frode Myklebust
` (3 preceding siblings ...)
2007-01-31 16:37 ` Jan Frode Myklebust
@ 2007-01-31 16:57 ` Jan Frode Myklebust
2007-01-31 16:58 ` Bill Nottingham
5 siblings, 0 replies; 7+ messages in thread
From: Jan Frode Myklebust @ 2007-01-31 16:57 UTC (permalink / raw)
To: linux-hotplug
As HWADDR in ifcfg-eth* seems to be more of a safety-net, what's the
recommended way of getting stable eth* names on RHEL4? Creating udev-rules
for all servers seems too much... It would be nice if there were a simple
"save-current eth*-mac mapping" function that would be restored upon boot.
-jf
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CIDÞVDEV
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
^ permalink raw reply [flat|nested] 7+ messages in thread* Re: eth3 becoming /sys/class/net/dev22358
2007-01-31 13:00 eth3 becoming /sys/class/net/dev22358 Jan-Frode Myklebust
` (4 preceding siblings ...)
2007-01-31 16:57 ` Jan Frode Myklebust
@ 2007-01-31 16:58 ` Bill Nottingham
5 siblings, 0 replies; 7+ messages in thread
From: Bill Nottingham @ 2007-01-31 16:58 UTC (permalink / raw)
To: linux-hotplug
Jan Frode Myklebust (MYKLEB@no.ibm.com) said:
> As HWADDR in ifcfg-eth* seems to be more of a safety-net, what's the
> recommended way of getting stable eth* names on RHEL4? Creating udev-rules
> for all servers seems too much... It would be nice if there were a simple
> "save-current eth*-mac mapping" function that would be restored upon boot.
The answer *is* to add HWADDR to the config files.
Bill
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CIDÞVDEV
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
^ permalink raw reply [flat|nested] 7+ messages in thread