---Problem Description---
qeth on a DPM-managed IBM Z machine does not obtain its MAC Address for L2 OSD interfaces from the OSA Network Adapter. Instead it uses a random MAC Address.
This causes connectivity issues in setups where a reliable & pre-determined MAC Address is required - ie. when doing network configuration via DHCP.
---Steps to Reproduce---
- Bring up a qeth L2 OSD interface in DPM-managed LPAR.
- Inspect the interface's MAC Address. It should be the same as displayed in the DPM Panels.
Stack trace output:
no
Oops output:
no
System Dump Info:
The system is not configured to capture a system dump.
-Attach sysctl -a output output to the bug.
Backport of "s390/qeth: improve fallback to random MAC address"
Backport of "s390/qeth: utilize virtual MAC for Layer2 OSD devices"
This ticket is for 18.04 only. Already available with 20.04
---Problem Description---
qeth on a DPM-managed IBM Z machine does not obtain its MAC Address for L2 OSD interfaces from the OSA Network Adapter. Instead it uses a random MAC Address.
This causes connectivity issues in setups where a reliable & pre-determined MAC Address is required - ie. when doing network configuration via DHCP.
---uname output--- 4.15.0- 101-generic
Ubuntu 18.04 / vmlinuz-
Machine Type = IBM z14 GA2
---Debugger---
A debugger is not configured
---Steps to Reproduce---
- Bring up a qeth L2 OSD interface in DPM-managed LPAR.
- Inspect the interface's MAC Address. It should be the same as displayed in the DPM Panels.
Stack trace output:
no
Oops output:
no
System Dump Info:
The system is not configured to capture a system dump.
-Attach sysctl -a output output to the bug.
Backport of "s390/qeth: improve fallback to random MAC address"
Backport of "s390/qeth: utilize virtual MAC for Layer2 OSD devices"
This ticket is for 18.04 only. Already available with 20.04