[NTLUG:Discuss] UDEV rules not working

[terry]

On 7/6/07, VanSchuyver, Shawn (Contractor) <Shawn.VanSchuyver at yum.com>
wrote:
>
> ¥-----Original Message-----
> ¥From: discuss-bounces at ntlug.org [mailto:discuss-bounces at ntlug.org] On
> Behalf Of Chris Cox
> ¥Sent: Friday, July 06, 2007 10:04
> ¥To: NTLUG Discussion List
> ¥Subject: Re: [NTLUG:Discuss] UDEV rules not working
> ¥
> ¥VanSchuyver, Shawn (Contractor) wrote:
> ¥> Hello everybody,
> ¥>    I hope everyone is staying dry. I have an issue I hope you will be
> ¥> able to help me with.
> ¥>
> ¥> I am running SUSE SLED 10. I have many servers of different ages,
> makes,
> ¥> and models that have multiple network cards: motherboard built-in plus
> ¥> extra NICs.  I have defined the following rules under
> /etc/udev/rules.d/
> ¥> in 10-local.rules to force the first 3Com network card to be eth0.  The
> ¥> rules only work about 80% of the time. I cannot figure out why the
> other
> ¥> 20% fails.
> ¥>
> ¥> Even if there are more than 2 NICs there will only be 1 3Com network
> ¥> card. The 3Com NIC has to be eth0.
> ¥>
> ¥> UDEV RULES: 10-local.rules
> ¥>
> ¥> KERNEL=="eth*", SYSFS{vendor}="3Com Corporation", Name:="eth0"
> ¥> KERNEL=="eth*", SYSFS{Vendor}="3Com Corporation", Name:="eth0"
> ¥> KERNEL=="eth*", SYSFS{VENDOR}="3Com Corporation", Name:="eth0"
> ¥>
> ¥>
> ¥> Suggestions? Comments?
> ¥
> ¥Just curious... did you try following the instructions at:
> ¥/usr/share/doc/packages/sysconfig/README.Persistent_Interface_Names
> ¥
> ¥Personally, I'd reset your local.rules back to the original and
> ¥follow the instructions mentioned above.
> ¥
>
>
> I have read the README docs, the man pages, and online documentation for
> UDEV.
>
>         The main issue is the fact that I have only remote access to
> servers in unknown locations. I'm remote imaging them to convert them from
> SCO to SUSE. The 3Com cards are the only NICS connected to the network. The
> company hard coded their software to use ONLY eth0 over a 3Com card. So, I
> have to figure out how to configure very many remote servers on initial
> imaging to make the 3Com card eth0 without fail. None of the servers are
> identical in any fashion except for using the same LINUX image and having a
> 3Com NIC.  The servers run the complete gamut of hardware configurations
> possible on a X86 based architecture.
>
>         Based on this information, I have been able to gather. All I know
> is that the images load correctly on the servers, but 20% of them do not
> define the 3Com NICS as eth0 no matter what is in the UDEV rule set.
> 30-net_persistent.rules is completely empty of all rules on the image. I
> have even deleted all defined NIC info in /etc/sysconfig except for IP
> configuration information on eth0. I have even accounted for the variance in
> SYSFS for reading the variables from the NICS differently depending on where
> they were made. That is why I have 3 lines in 10-local.rules.
>
> Any other suggestions?
>
>
> This communication is confidential and may be legally privileged.  If you
> are not the intended recipient, (i) please do not read or disclose to
> others, (ii) please notify the sender by reply mail, and (iii) please delete
> this communication from your system.  Failure to follow this process may be
> unlawful.  Thank you for your cooperation.
>
> _______________________________________________
> http://www.ntlug.org/mailman/listinfo/discuss
>

Not sure about Suse,  but debian uses /etc/iftab  [to assign consitant names
to NICs].
(I just encountered a similar issue; See:
http://www.ntlug.org/BP-trryhend/UdevGotMe?action=view )

If that's not it, it may be that you are editing the wrong file, you might
do a search, something like
grep network /etc/udev/rules.d/*

OR..., what about YaST?    Maybe it's a function of, or a utility in YaST.
I would try that first!

-- 
                  <><