You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After working with an end-user on an issue that arose from manual virtual IP configuration, I am changing the recommendation for SUSE. Cloud-users should use the fully-supported cloud-netconfig plugin to manage IPs instead of manually setting them in YaST or ifcfg-* files to avoid IP ordering (primary/secondary) issues.
Copy file name to clipboardExpand all lines: includes/virtual-network-multiple-ip-addresses-os-config.md
+4-50Lines changed: 4 additions & 50 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -53,60 +53,14 @@ ping -S 10.0.0.7 outlook.com
53
53
</details>
54
54
55
55
### SUSE Linux Enterprise and openSUSE
56
-
57
-
<details>
58
-
<summary>Expand</summary>
59
-
60
-
##### YaST Method
61
-
62
-
1. For a graphical (GTK) interface, open YaST in a VNC or RDP session and go to the "System" > "Network Settings" module. For command-line (ncurses) interface, run <code>yast2 lan</code> from a terminal window or Azure Serial Console.
63
-
64
-
> [!TIP]
65
-
> The ncurses YaST interface highlights a letter of each selectable YaST option which can be selected with Alt + letter.
66
-
> The GTK interface provides a similar feature but uses an underline for this letter instead.
67
-
68
-
2. In the "Overview" tab, highlight the interface and select the "Edit" option to open a NIC-specific dialog.
69
-
70
-
3. In the "Address" tab, select "Add" on the "Additional IPs" box.
71
-
72
-
4. Add a Label for the IP alias, IP Address and Subnet Mask. Select "OK" then "Next" and finally "OK".
73
-
74
-
##### Manual Method
75
-
76
-
Add the IPADDR_0 and LABEL_0 entries to the respective `/etc/sysconfig/network/ifcfg-*` interface file.
77
-
78
-
For example, to add "10.0.0.128" as an IP alias with the label "eth0a" to an existing `eth0` interface on a "/24" network.
79
-
80
-
[A]. Use VIM to edit the file in place
81
56
82
-
```bash
83
-
vim /etc/sysconfig/network/ifcfg-eth0
84
-
```
85
-
86
-
Insert <code>i</code> the following lines at the end of the ifcfg file.
57
+
<details>
58
+
<summary>Expand</summary>
87
59
88
-
```vim
89
-
IPADDR_0='10.0.0.128/24'
90
-
LABEL_0='eth0a'
91
-
```
92
-
Use the "Esc" key to exit insert mode and run the write and quit vim commands:
93
-
94
-
```vim
95
-
:wq
96
-
```
60
+
SUSE-based distributions use the <code>cloud-netconfig</code> plugin from the <code>cloud-netconfig-azure</code> package to manage additional IP addresses. No manual configuration is required on the part of the administrator. The first IP address of an interface set on the platform is assigned via DHCP. The cloud-netconfig plugin then probes the Azure Instance Metadata Service API continuously (once per minute) for additional IP addresses assigned to the interface and adds/removes them as secondary IP addresses automatically.
97
61
98
-
[B]. Use bash to append these values in a single command
Instruct wicked network service to reload the interface:
62
+
This plugin should be installed and enabled on new images by default. Configuration steps for old workloads can be found here: https://www.suse.com/c/multi-nic-cloud-netconfig-ec2-azure/
0 commit comments