SLES11: static network setup not possible with active Hyper-V Linux Integration Components 2.0
This document (7005461) is provided subject to the disclaimer at the end of this document.
Environment
SUSE Linux Enterprise Server 11
Windows Server 2008 R2
Hyper-V Manager 6.1.7600.16385
Windows Server 2008 R2
Hyper-V Manager 6.1.7600.16385
Situation
With installed Linux Integration Components 2.0 YaST2 is not able to configure the synthetic network adapter with a static IP address. Once the values for IP address and netmask were entered and the changes applied, the main network settings window does not show the changes.
In case the adapter was previously configured with DHCP, it will remain to show up as such if one tries to change the values into a static setup.
In case the adapter was previously configured with DHCP, it will remain to show up as such if one tries to change the values into a static setup.
Resolution
Solution:
Please update the package yast2-network to version
Please note: In order for the updated package to work, the old configuration file /etc/sysconfig/network/ifcfg-seth0 needs to be deleted first.
Quick Workaround:
Edit /etc/sysconfig/network/ifcfg-seth0 manually and set the values for IP address and netmask in this file, like in the following example:
Please update the package yast2-network to version
yast2-network-2.17.128 via online update.
Please note: In order for the updated package to work, the old configuration file /etc/sysconfig/network/ifcfg-seth0 needs to be deleted first.
Quick Workaround:
Edit /etc/sysconfig/network/ifcfg-seth0 manually and set the values for IP address and netmask in this file, like in the following example:
BOOTPROTO='static'
BROADCAST=''
ETHTOOL_OPTIONS=''
IPADDR='192.168.66.10/24'
MTU=''
NAME=""
NETMASK=''
NETWORK=''
REMOTE_IPADDR=''
STARTMODE='auto'
USERCONTROL='no'
BROADCAST=''
ETHTOOL_OPTIONS=''
IPADDR='192.168.66.10/24'
MTU=''
NAME=""
NETMASK=''
NETWORK=''
REMOTE_IPADDR=''
STARTMODE='auto'
USERCONTROL='no'
Additional Information
If only one synthetic adapter was added to the virtual machine, delete /etc/sysconfig/network/ifcfg-seth1.
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:7005461
- Creation Date: 09-Mar-2010
- Modified Date:14-Oct-2022
-
- SUSE Linux Enterprise Server
For questions or concerns with the SUSE Knowledgebase please contact: tidfeedback[at]suse.com
