Re: network devices changing ...

Thanks,

it's very helpfull. It should fix all topics.

Bye, Peer

On 31.07.2013 18:02, Hans-Joachim Ehlers wrote:
> 1) Driver Update Disk:
> DUD for SLES 11 SP1 - See http://www.novell.com/support/kb/doc.php?id=7009981 ( Its for multipathing but its the same logic )
>
> - Create DUD structure
> - and/or apply driverupdate=1 kernel command line option
>
>
> Or to load the driver during boot:
>
> Add an option to your pxe boot env. like:
>
> ...
> append initrd= .....  insmod=tg3 insmod=megariad_sas
> ...
>
> Keep in mind that the modules MUST have been build for the kernel provided by the initrd.
>
> 2) Persistent network device names
>
>  From Uwe Gansert http://users.suse.com/~ug/AutoYaST_FAQ.html#a9
> ...
> 1.10 Is there a way for persistent network device names?
> ...
> <networking>
>    <net-udev config:type="list">
>        <rule>
>          <name>eth0</name>
>          <rule>ATTR{address}</rule>
>          <value>00:50:56:bb:52:3f</value>
>        </rule>
>    </net-udev>
> ...
> </networking>
> for linuxrc you can use udev.rule="mac=de:ad:00:00:be:ef,name=eth1"
> and you can pass multiple of those like udev.rule="...,name=eth0" udev.rule="...,name=eth1" udev.rule="...,name=eth2"
> ...
>
>
> Hth
> Hajo
>
> -----Original Message-----
> From: Dr.Peer-Joachim Koch [mailto:[email protected]]
> Sent: Wednesday, July 31, 2013 9:12 AM
> To: [email protected]
> Subject: [opensuse-autoinstall] network devices changing ...
>
> Hi,
>
> on new DELL R820 I'm currently trying to install SLES11SP1.
> A newer version is not possible (software reasons ...).
> I used some older autoinstall file, which works for old nodes. On the
> new node
> the installations fails.
> 1) The initrd was modified (new tg3 and megariad_sas module. But both
> modules
>    are not loaded automatically. I have to do this by hand.
>
> 2) When I start the installation process after loading the modules,
> everything seems to be fine, but after the first boot the network devices
> have changed. In in the udev rules file the eth{0,1} switched to eth{2,3}
> and eth{2,3} switched to eth{0,1}. So after the first boot, no network
> is available and I have to switch the udev rules (doing a rescue boot).
> Therefore not everything of the autoinstall script is executed.
>
> *) How can I check, why the modules are *not* loaded ?
>
> *) Can I force in the autoinstall file to create the udev rules according
> to the mac addresses (lowest mac adr. -> eth0; lowest mac adr.+1 ->eth1,...)
> N�����r��y隊Z)z{.�殶���֥�맲��r��z�^�ˬz��N�(�֜��^�	ޭ隊Z)z{.�殶���֥��0�����Ǩrg==


-- 
Mit freundlichem Gruß
     Peer-Joachim Koch
_________________________________________________________
Max-Planck-Institut fuer Biogeochemie
Dr. Peer-Joachim Koch
Hans-Knöll Str.10            Telefon: ++49 3641 57-6705
D-07745 Jena                 Telefax: ++49 3641 57-7705

begin:vcard
fn:Dr. Peer-Joachim Koch
n:Koch;Peer-Joachim
org;quoted-printable:MPI f=C3=BCr Biogeochemie;DVA
adr:;;Hans-Knoell-Str. 10;Jena;;07745;Germany
email;internet:[email protected]
title:Dr. 
tel;work:+49 3641 576705
tel;fax:+49 3641 577705
tel;cell:+49 177 387 5780
x-mozilla-html:FALSE
version:2.1
end:vcard