Automatic Addition of Secondary IP Addresses in Azure fails
This document (000021188) is provided subject to the disclaimer at the end of this document.
Environment
SUSE Linux Enterprise Server 12 All Service Packs
Situation
Secondary TCPIP configurations based on Microsoft Azure IP settings are not automatically added after server reboots.
Failure to automatically add newly assigned secondary TCPIP addresses from Microsoft Azure IP configurations to SLES servers.
Resolution
Preferred Solution:
Alternative workaround:
If applying updates is not possible, a workaround exists:
1. Edit the network card configuration you wish to add the secondary IP address. For example, if your NIC is named "eth0" then the configuration file is /etc/sysconfig/network/ifcfg-eth0
2. Within that file, add the following contents:
CLOUD_NETCONFIG_MANAGE='yes'
IPADDR_1='10.0.0.99/24' # Replace with the desired secondary IP address and subnet mask BOOTPROTO='dhcp'
STARTMODE='auto'
LABEL_1='<label of your choice>'
Replace 10.0.0.99/24 with your desired secondary IP address and subnet mask. Choose a label for LABEL_1 that makes sense for your use case.
3. After making the changes, save the file and restart the network services by running the following command:
systemctl restart wicked.service
Keep in mind that restarting the network services may result in a temporary disconnection of clients.
Following these steps, you can successfully add a secondary IP address to your system.
Cause
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:000021188
- Creation Date: 01-Sep-2023
- Modified Date:17-Jan-2025
-
- SUSE Linux Enterprise Server
For questions or concerns with the SUSE Knowledgebase please contact: tidfeedback[at]suse.com