Problem: Network Configuration Is never Saved

Problem:

The configuration for an interface (ie “ens192/”) through UMC does not save the settings. After a reboot the server still does not use the configured IP and UMC shows unconfigured fields for IP and gateway.

Environment

On the command line the configured settings were as shown:

root@ucs:~# ucr dump | grep -E "^interfaces"
interfaces/br0/address: 169.254.77.10
interfaces/br0/broadcast: 169.254.255.255
interfaces/br0/ipv6/acceptRA: false
interfaces/br0/netmask: 24
interfaces/br0/network: 169.254.0.0
interfaces/br0/start: true
interfaces/br0/type: dhcp
interfaces/ens192/address: 192.168.9.11
interfaces/ens192/broadcast: 192.168.9.255
interfaces/ens192/ipv6/acceptRA: false
interfaces/ens192/order: 1
interfaces/ens192/start: true
interfaces/ens192/type: static
interfaces/handler: ifplugd
interfaces/primary: ens192

A bridge interface is configured (“br0”) which usually uses the underlying interfaces for failover oder performance reasons.

Solution

A bridge interface wipes out the IP settings of the underlying interfaces. To configure the “ens192” interface remove the “br0” settings. Then reboot the server and the configuration of the ens192 will be possible and stable.

root@ucs:~# ucr unset interfaces/br0/address interfaces/br0/start interfaces/br0/type

Mastodon