--- Comment From mario.alberto.gali...@ibm.com 2021-07-28 17:41 EDT---
Sound good for me, lets close it
--
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
--- Comment From mario.alberto.gali...@ibm.com 2021-07-27 11:33 EDT---
Enable udev monitor:
udevadm --debug monitor --property >> udevadm_reload.txt
Steeps followed to retrieve logs:
- Checking actual status of the vLan:
root@ilabg13:~# date
Tue Jul 27 08:23:47 MST 2021
root@ilabg13:~# ip
--- Comment From mario.alberto.gali...@ibm.com 2021-07-27 10:40 EDT---
Since the file /etc/systemd/network/10-enP53p0s0.link was removed it wasn't get
generated again.
Is there a way to get it generated again?
--
You received this bug notification because you are a member of Ubuntu
Bugs
--- Comment From mario.alberto.gali...@ibm.com 2021-06-24 11:53 EDT---
Giving it a try without the /etc/systemd/network/ files
- Checking that it is empty
root@ilabg13:~# ll /etc/systemd/network/
total 8
drwxr-xr-x 2 root root 4096 Jun 24 08:41 ./
drwxr-xr-x 5 root root 4096 Jun 17 06:18 .
--- Comment From mario.alberto.gali...@ibm.com 2021-06-23 18:19 EDT---
Files content:
root@ilabg13:~# cat /etc/systemd/network/10-enP53p0s0.link
[Match]
MACAddress=82:0c:9b:c9:78:f8
[Link]
Name=enP53p0s0
root@ilabg13:~# cat /usr/lib/systemd/network/99-default.link
# SPDX-License-Identifie
--- Comment From mario.alberto.gali...@ibm.com 2021-06-17 12:14 EDT---
Right now the system is at kernel version:
root@ilabg13:~# uname -a
Linux ilabg13.tuc.stglabs.ibm.com 5.4.0-73-generic #82-Ubuntu SMP Wed Apr 14
17:29:32 UTC 2021 s390x s390x s390x GNU/Linux
And it is a new version ava
--- Comment From mario.alberto.gali...@ibm.com 2021-06-15 11:18 EDT---
Enable udev monitor:
udevadm --debug monitor --property >> udevadm_monitor.txt
Steeps followed to retrieve logs:
- Manually remove the IP
ip addr del 192.168.171.53/24 dev enP53p0s0.171
- Try to assign ip via netplan
r
--- Comment From mario.alberto.gali...@ibm.com 2021-06-14 11:18 EDT---
Enable udev debug mode:
root@ilabg13:~# cat /etc/systemd/system/systemd-udevd.service.d/override.conf
[Service]
Environment=SYSTEMD_LOG_LEVEL=debug
root@ilabg13:~# systemctl daemon-reload && sudo systemctl restart system
--- Comment From stefan.ra...@de.ibm.com 2021-06-11 10:04 EDT---
Talked to Viktor - he didn't think there's much indication that the skewed
interface name has any effect. Especially since the interface gets a LL address
assigned just fine.
--
You received this bug notification because y
--- Comment From stefan.ra...@de.ibm.com 2021-06-10 03:55 EDT---
Makes me wonder if what we're seeing is a side-effect of
--- Comment From stefan.ra...@de.ibm.com 2021-06-10 03:58 EDT---
Makes me wonder whether this could be a side-effect of the interface name,
indeed.
@Viktor/Nik
--- Comment From mario.alberto.gali...@ibm.com 2021-06-09 17:17 EDT---
Attaching output of 'journalctl -b -u systemd-networkd --no-pager' after
'systemctl daemon-reload && systemctl restart systemd-networkd' execution
File -> journalctl_deamon-reload
--
You received this bug notificatio
--- Comment From mario.alberto.gali...@ibm.com 2021-06-09 15:04 EDT---
Steeps followed...
Updated systemd-networkd loglevel:
root@ilabg13:~# cat /etc/systemd/system/systemd-networkd.service.d/override.conf
[Service]
Environment=SYSTEMD_LOG_LEVEL=debug
root@ilabg13:~# systemctl restart syst
--- Comment From mario.alberto.gali...@ibm.com 2021-06-09 11:50 EDT---
Did another experiment and removed the IP assigned to both RoCE adapters vLans
using ip command and ran the netplan apply.
The issue was recreated only one of the vLans gets the ip assigned the
other one didn't.
--
Y
--- Comment From mario.alberto.gali...@ibm.com 2021-06-09 11:37 EDT---
Adding another journalctl to trace the setup with ip command
I proceded to execute:
root@ilabg13:~# ip addr add 192.168.171.53/24 dev enP53p0s0.171
And that get the ip assigned:
root@ilabg13:~# ip a
1: lo: mtu 65536
--- Comment From mario.alberto.gali...@ibm.com 2021-06-09 11:27 EDT---
Attached the output of journalctl -o verbose
Also did some changes int he netplan config file and the result was the
same:
config file:
network:
version: 2
ethernets:
encdb0:
addresses:
- 11.111.114.213/22
macaddress:
--- Comment From stefan.ra...@de.ibm.com 2021-06-09 05:41 EDT---
Hi Frank,
Do we know which component is supposed to set the IP address in Mario's case?
Probably netplan...?! It's debug log doesn't say anything about IP addresses
being set, which is unfortunate.
So here's a couple of oddi
--- Comment From mario.alberto.gali...@ibm.com 2021-06-07 16:13 EDT---
Just executed netplan try and netplan apply and take snapshot of journalctl.
It is attached now!
- The configuration has not being touched for long time
- Correct is the only one presenting this problem
- Correct all of
--- Comment From mario.alberto.gali...@ibm.com 2021-06-07 14:49 EDT---
Compressed and attached system.journal.
Frank,
I have other systems with similar configurations but not exactly the same. It
is another ubuntu host but Native linux installed in its own Lpar, and have
some other hosts
--- Comment From mario.alberto.gali...@ibm.com 2021-06-07 13:56 EDT---
Could you provide a place to upload the system.journal file? it pass the limit
of 51200 KB
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.lau
--- Comment From mario.alberto.gali...@ibm.com 2021-06-01 13:57 EDT---
This is the actual configuration of HBA assigned to the Host:
root@ilabg13:~# znetconf -c
Device IDs TypeCard Type CHPID Drv. Name
State
20 matches
Mail list logo
