Hi Mario, so did I got it right that this is the only one out of multiple
systems with a similar config that has this problem - on a ROcE interface with
vlan?
Did you modified expanded the device config of that system over time (with more
OSA or more RoCE devices) or was it untouched after initial installation?
(Well, I think at least regular updates were done ...)
Are all these systems with RoCE v2.x devices?
What happens if you try to set the IP via the ip command?
Well, I just configured all RoCE devices that I have on this LPAR for vlan
usage and assigned IP addresses to the base and vlan interface with the help of
the ip command, which worked:
ip a | grep "192.168.1.20"
inet 192.168.1.201/24 scope global enP1p0s0
inet 192.168.1.203/24 scope global enP1p0s0d1
inet 192.168.1.205/24 scope global enP2p0s0
inet 192.168.1.207/24 scope global enP2p0s0d1
inet 192.168.1.202/24 scope global enP1p0s0.1234
inet 192.168.1.204/24 scope global enP1p0s0d1.1234
inet 192.168.1.206/24 scope global enP2p0s0.1234
inet 192.168.1.208/24 scope global enP2p0s0d1.1234
Next: transfer this config to the netplan yaml ...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1929657
Title:
[Ubuntu 20.4.2] vLan not getting static IP assigned (on s390x)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1929657/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
