Release Notes

Cause: Not available
Workaround: Use Dynamic Host Conguration Protocol (DHCP) address to the initiator.
Network ports are displayed as unknown in YaST2
network conguration
Description: While conguring a bonding interface, the congured bond-slaves are listed as Unknown Network Device
Cause: YaST installer is unable to write the device name in to the ifcfg les.
Workaround: Delete the existing conguration of previously congured network interfaces.
Unable to boot from iSCSI over iPV6 after successful
installation
Description: After the successful installation of SUSE Linux Enterprise Server 12 from iSCSI over IPv6, the system does not
boot and fails to provide a GUI login.
Cause: This issue occurs when rewall is enabled during installation.
Workaround: Disable rewall settings during install.
Unable to expose some ports of Emulex cards with
NPAR-EP enabled when system reboots
Description:
The Emulex OneConnect OCm14104-N1-D and Emulex OneConnect OCe14102-N1-D cards have totallty 32
interfaces, with NPAR-EP enabled, when the system reboots some ports of the cards are not exposed to the
operating system.
Cause: The OS has only 30 seconds to linkup with interfaces after it reboots.
Workaround: Edit /etc/wicked/common.xml and set use-nanny to true and reboot.
Invalid naming conventions for ports in Intel and NDC
cards
Description:
The naming conventions for Intel and NDC cards in SUSE Linux Enterprise Server 12 by biosdevname might not
be accurate for all the networking devices.
Cause: Limitation in the biosdevname.
Workaround: Add kernel boot parameter biosdevname=0 and the naming convention reverts to eth naming.
10 Issues and Resolutions