Autoyast installation fails when multiple NICs are installed on the target server
This document (7008631) is provided subject to the disclaimer at the end of this document.
Environment
SUSE Linux Enterprise Server 11 SP1
SUSE Linux Enterprise Server 11
SUSE Linux Enterprise Server 11
Situation
Automated installation via Autoyast profile
Using a network installation source
Installation loses network connection to installation source after second boot and stops with message "Cannot access installation media... Check whether the server is accessible"
Prior to losing connection to installation source the message "No configuration found for eth0" can be seen.
The installation continues and finishes successfully if an interface is manually activated with "yast lan" or "dhcpcd eth0" via a different virtual console.
Autoyast xml file contains a udev rule correctly mapping interface name with an existing NIC mac address.
<net-udev config:type="list">
<rule>
<name>eth0</name>
<rule>ATTR{address}</rule>
<value>00:50:56:bb:52:3f</value>
</rule>
</net-udev>
This problem applies to virtual (VMware ESX) or physical installations
Using a network installation source
Installation loses network connection to installation source after second boot and stops with message "Cannot access installation media... Check whether the server is accessible"
Prior to losing connection to installation source the message "No configuration found for eth0" can be seen.
The installation continues and finishes successfully if an interface is manually activated with "yast lan" or "dhcpcd eth0" via a different virtual console.
Autoyast xml file contains a udev rule correctly mapping interface name with an existing NIC mac address.
<net-udev config:type="list">
<rule>
<name>eth0</name>
<rule>ATTR{address}</rule>
<value>00:50:56:bb:52:3f</value>
</rule>
</net-udev>
This problem applies to virtual (VMware ESX) or physical installations
Resolution
Workaround
Map the interface name with its mac address via boot parameter:
If PXE is being used, the above boot parameter can be added to pxe file. For example:
Map the interface name with its mac address via boot parameter:
udev.rule="mac=<mac address>, name=<interface>"
For example:
udev.rule="mac=00:50:56:00:be:ef,name=eth1"
If PXE is being used, the above boot parameter can be added to pxe file. For example:
label install
kernel linux
append initrd=initrd splash=verbose showopts install=nfs://<servername>/path/to/source/ autoyast=nfs://<servername>/path/to/xmlfile.xml udev.rule="mac=00:50:56:01:02:03,name=eth0"
Disclaimer
This Support Knowledgebase provides a valuable tool for SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented "AS IS" WITHOUT WARRANTY OF ANY KIND.
- Document ID:7008631
- Creation Date: 23-May-2011
- Modified Date:13-Mar-2021
-
- SUSE Linux Enterprise Server
For questions or concerns with the SUSE Knowledgebase please contact: tidfeedback[at]suse.com
