Hi all, (please disregard my previous mail, some things where wrong, sorry.) I am trying to rename and bond two eth with AY while installing over NFS. It fails in the second configure step because it can't setup networking. SLES11 on a HP DL385 G5 with two internal NICs and one additional PCI dual-port NIC. These are the relevant parts of my networking section: <networking> <net-udev config:type="list"> <rule> <name>eth0</name> <rule>ATTR{address}</rule> <value>00:23:7d:25:5f:e4</value> </rule> <rule> <name>eth1</name> <rule>ATTR{address}</rule> <value>00:23:7d:25:5f:e6</value> </rule> </net-udev> <interfaces config:type="list"> <interface> <bonding_master>yes</bonding_master> <bonding_module_opts>mode=1 miimon=100</bonding_module_opts> <bonding_slave0>eth0</bonding_slave0> <bonding_slave1>eth1</bonding_slave1> <bootproto>static</bootproto> <device>bond0</device> <ipaddr>1.2.3.4</ipaddr> <netmask>255.255.255.0</netmask> <prefixlen>24</prefixlen> <startmode>auto</startmode> </interface> <interface> <bootproto>none</bootproto> <device>eth0</device> <startmode>off</startmode> </interface> <interface> <bootproto>none</bootproto> <device>eth1</device> <startmode>off</startmode> </interface> [... snip ...] </networking> Now what happens after the reboot is: Broadcom NetXtreme II Gigabit Ethernet Driver bnx2 v1.8.0 (Aug 14, 2008) vendor=1166 device=0142 bnx2 0000:0c:04.0: PCI INT A -> GSI 40 (level, low) -> IRQ 40 eth0: Broadcom NetXtreme II BCM5706 1000Base-T (A2) PCI-X 64-bit 100MHz found at mem f6000000, IRQ 40, node addr 00:1e:0b:d8:68:68 vendor=1166 device=0142 bnx2 0000:0d:05.0: PCI INT A -> GSI 39 (level, low) -> IRQ 39 eth1: Broadcom NetXtreme II BCM5706 1000Base-T (A2) PCI-X 64-bit 100MHz found at mem f8000000, IRQ 39, node addr 00:1e:0b:d8:68:6a vendor=1166 device=0144 bnx2 0000:04:00.0: PCI INT A -> GSI 41 (level, low) -> IRQ 41 eth2: Broadcom NetXtreme II BCM5708 1000Base-T (B2) PCI-X 64-bit 133MHz found at mem f2000000, IRQ 41, node addr 00:23:7d:25:5f:e6 vendor=1166 device=0142 bnx2 0000:42:00.0: PCI INT A -> GSI 34 (level, low) -> IRQ 34 scsi2 : qla2xxx eth3: Broadcom NetXtreme II BCM5708 1000Base-T (B2) PCI-X 64-bit 133MHz found at mem fa000000, IRQ 34, node addr 00:23:7d:25:5f:e4 eth3 renamed to eth3_rename by udevd [2213] eth2 renamed to eth2_rename by udevd [2214] eth1 renamed to eth2 by udevd [2212] eth2_rename renamed to eth1 by udevd [2214] udev: renamed network interface eth1 to eth2 udev: renamed network interface eth2_rename to eth1 eth0 renamed to eth3 by udevd [2211] udev: renamed network interface eth0 to eth3 eth3_rename renamed to eth0 by udevd [2213] udev: renamed network interface eth3_rename to eth0 All looks good. But later it goes: Setting up (localfs) network interfaces: lo lo IP address: 127.0.0.1/8 IP address: 127.0.0.2/8 done eth0 device: Broadcom Corporation NetXtreme II BCM5708 Gigabit Ethernet (rev 12) No configuration found for eth0 unused eth1 device: Broadcom Corporation NetXtreme II BCM5708 Gigabit Ethernet (rev 12) No configuration found for eth1 unused eth2 device: Broadcom Corporation NetXtreme II BCM5706 Gigabit Ethernet (rev 02) eth2 Starting DHCP4 client. . . . . . . . eth2 DHCP4 continues in background waiting eth3 device: Broadcom Corporation NetXtreme II BCM5706 Gigabit Ethernet (rev 02) No configuration found for eth3 unused Waiting for mandatory devices: eth2 __NSC__ 11 10 8 7 6 5 3 2 1 eth2 device: Broadcom Corporation NetXtreme II BCM5706 Gigabit Ethernet (rev 02) eth2 DHCP4 client (dhcpcd) is running eth2 . . . but is still waiting for data waiting eth2 interface could not be set up until now failed Setting up service (localfs) network . . . . . . . . . . failed *** Starting YaST2 *** So network cannot be setup for the second stage because 1) eth0/1 are disabled for bonding 2) eth2 is in another VLAN And the final configuration step fails with: Cannot access installation media SUSE-Linux-Enterprise-Server-11 11-0 (Medium 1). Check whether the server is accessible. Am I doing something totally wrong? Or should I open a bugreport with Novell? Thanks, Michael ps: Why bother with renaming? Because not all our servers have additional NICs and for consistency I want the internal ones to always be eth0/1. -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-autoinstall+help@opensuse.org