Comment 10 for bug 1914740
Revision history for this message
| bugproxy (bugproxy) wrote Comment bridged from LTC Bugzilla | #10 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
------- Comment From <email address hidden> 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.