[Bug 1914740] Comment bridged from LTC Bugzilla
--- Comment From heinz-werner_se...@de.ibm.com 2021-03-17 08:12 EDT--- IBM bugzilla status-> closed, workaround available, upstream activitiy by Canonical. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1914740 Title: IPs are not assigned for Hipersockets in DHCP mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1914740/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1914740] Comment bridged from LTC Bugzilla
--- Comment From wint...@de.ibm.com 2021-03-01 12:00 EDT--- Works like a charm, thank you xnox! I tested L2 and L3 HiperSockets during reboot. L2 got the IP@ via unicast reply L3 got its IP@ via broadcast reply. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1914740 Title: IPs are not assigned for Hipersockets in DHCP mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1914740/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1914740] Comment bridged from LTC Bugzilla
--- Comment From wint...@de.ibm.com 2021-03-01 02:53 EDT--- This is the setup I use as DHCP client: root@s83lp72:~# cat /etc/os-release NAME="Ubuntu" VERSION="20.04.2 LTS (Focal Fossa)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 20.04.2 LTS" VERSION_ID="20.04" HOME_URL="https://www.ubuntu.com/; SUPPORT_URL="https://help.ubuntu.com/; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy; VERSION_CODENAME=focal UBUNTU_CODENAME=focal So if you can provide a fix for focal fossa (plus instructions how to install it), I can give it a try. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1914740 Title: IPs are not assigned for Hipersockets in DHCP mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1914740/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1914740] Comment bridged from LTC Bugzilla
--- Comment From wint...@de.ibm.com 2021-02-25 10:28 EDT--- (In reply to comment #25) > For netplan yaml of: > > network: > version: 2 > ethernets: > enc8f00: > dhcp4: yes > > It would be interesting to see if L3 dhcp starts to work if one does: > > $ sudo mkdir -p /etc/systemd/network/10-netplan-enc8f00.network.d > $ cat < /etc/systemd/network/10-netplan-enc8f00.network.d/30-request-broadcast.conf > [DHCPv4] > RequestBroadcast=yes > EOF > > $ sudo networkctl reconfigure enc8f00 > > (or chzdev -d 0.0.8f00; chzdev -e 0.0.8f00 or reboot, whatever is easier to > make networkd force renew). Thank you xnox. I confirm that this works with chzdev -d/-e and with reboot. @Asha, this is a better solution for you. --- Comment From wint...@de.ibm.com 2021-02-25 10:36 EDT--- (In reply to comment #26) > My preference would be to fix networkd, if that fails netplan, and isc-dhcp > only if there is syntax to online the device in the right l2/l3 state via > kernel cmdline and that one needs to complete install over it. > > For example, does automatic chzdev device enablement provides > autoconfiguration for hipersockets in l3? in that case it would be neat for > ip=dhcp to just do the right thing. > Yes, 'chzdev -e' defaults to Layer3 unless you explicitely specify 'chzdev -e layer2=1'. Note that chzdev creates a udev rule to make this setting persistent. > Would turning on RequestBroadcast=yes for ID_NET_DRIVER=qeth_l3 interfaces > be good enough in networkd? Yes, that sounds good. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1914740 Title: IPs are not assigned for Hipersockets in DHCP mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1914740/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1914740] Comment bridged from LTC Bugzilla
--- Comment From wint...@de.ibm.com 2021-02-18 02:54 EDT--- (In reply to comment #18) > Thx Alexandra and Asha for digging deeply into that issue with the > hipersocket environment. > So the initial reason was to use L3 because of potentially connecting to > z/OS instances? > Yes, that is the one scenario where L3 HiperSockets with DHCP would be neccessary. The other thing is that HiperSockets Linux interfaces default to L3, so they can potentially connect to z/OS. So even if no z/OS is around, people may use L3 HiperSockets just because it is the default. @Asha, do you have a need to use L3 in your scenario? Will you ever connect to z/OS? > > And I totally agree to use interfaces in L2 mode whereever possible, > especially when it comes to DHCP. And so far I only saw DHCP environments on > Z in L2 mode, hence my surprise at the very beginning about the combination > of DHCP / Hipersockets / L3. Note that OSA L3 interfaces do have the same issue with DHCP. But there is no reason to use OSA L3 interfaces at all and they default to L2. So hopefully nobody cares about that. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1914740 Title: IPs are not assigned for Hipersockets in DHCP mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1914740/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1914740] Comment bridged from LTC Bugzilla
--- Comment From stefan.ra...@de.ibm.com 2021-02-18 02:39 EDT--- Hi Frank, As for dhclient: Fedora33 ships isc-dhclient-4.4.2b1, and that has the option as part of the binary and described in the man page. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1914740 Title: IPs are not assigned for Hipersockets in DHCP mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1914740/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1914740] Comment bridged from LTC Bugzilla
--- Comment From wint...@de.ibm.com 2021-02-17 03:43 EDT--- For documentation: 'dhclient -B' is a way to turn on the required flag for Layer3 DHCP at the client side. My Ubuntu 20.04.2 contains only isc-dhclient-4.4.1 Seems that isc-dhclient-4.4.2 is required for this option. Using 'bootp-broadcast-always;' in a dhclient.conf file may be another option. However: as mentioned above, I strongly recommend to use Layer2 interfaces for DHCP, if possible. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1914740 Title: IPs are not assigned for Hipersockets in DHCP mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1914740/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1914740] Comment bridged from LTC Bugzilla
--- Comment From sankar...@in.ibm.com 2021-02-17 01:19 EDT--- Comment on attachment 148055 DHCP client debug information Yesterday SSC team had a debug session with Alexandra. I have attached the debug info of both server and client here. Each file contains the debug information from M96 and S209B machines. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1914740 Title: IPs are not assigned for Hipersockets in DHCP mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1914740/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1914740] Comment bridged from LTC Bugzilla
--- Comment From wint...@de.ibm.com 2021-02-16 11:49 EDT--- This morning we had a debug session with Asha and team. The first issues were configuration problems. For documentation purposes: - By default HiperSockets channels (CHPIDs) are isolated network segments, you cannot communicate between devices on different CHPIDs - By default HiperSockets cannot be used for communications between different CECs Network planning needs to be done accordingly, a simple way is e.g. : 1 IP subnet <-> 1 HiperSockets channel Then we reproduced the following issue: DHCP server and DHCP client both connected to the same HS channel via Layer 3 interfaces. Requests are sent out via broadcast (tcpdump on client), server sends responses (seen in journalctl on server) responses never reach the client (tcpdump on client). Sankar will attach detailed debug information. As mentioned, last Friday I was successfully running DHCP between Ubunut 20.04 server and client via Layer 2 HiperSockets. Today I reproduced with Layer3 HiperSockets and it failed. Remember that for HiperSockets Layer3 needs to be used on all participating interfaces!! (OSA is different) Analysis: See the "Device Drivers, Features, and Commands" https://www.ibm.com/developerworks/linux/linux390/documentation_dev.html Chapter "Required options for using dhcpcd with layer3" There it states "Run the DHCP client with an option that instructs the DHCP server to broadcast its response to the client." Unfortunately I did not find such an option for netplan dhcp. Deprecated workaround: add "always-broadcast on;" to /etc/dhcp/dhcpd.conf on the server side (I tried this with my LPARs and it worked.) Recommended solution: Use layer2 HiperSockets, if you want to use DHCP on HiperSockets and have only Linux'es connected. (By default z/OS only supports layer3 HiperSockets, so all endpoints need to be Layer 3 HiperSockets, if a z/OS is attached to this network segment) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1914740 Title: IPs are not assigned for Hipersockets in DHCP mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1914740/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1914740] Comment bridged from LTC Bugzilla
--- Comment From wint...@de.ibm.com 2021-02-12 07:04 EDT--- I have set up an DHCP server and DHCP client over HiperSockets, both on Ubuntu 20.04.1 and it works just fine. Please provide your config files for dhcp and netplan on server and client side. Is the dhcp server also running on Ubuntu? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1914740 Title: IPs are not assigned for Hipersockets in DHCP mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1914740/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1914740] Comment bridged from LTC Bugzilla
--- Comment From wint...@de.ibm.com 2021-02-11 08:44 EDT--- Thanks for the information Asha. Can you append any logs? dmesg, journalctl or any DHCP related logs? Do you have any information from the DHCP server? Logs? Network setup? Do you have tcpdump data? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1914740 Title: IPs are not assigned for Hipersockets in DHCP mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1914740/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
