Comment 4 for bug 1541544
Revision history for this message
| bugproxy (bugproxy) wrote Comment bridged from LTC Bugzilla | #4 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
------- Comment From <email address hidden> 2016-02-05 11:40 EDT-------
We have to distinguish between the different device types supported by the qeth driver:
1. OSA-cards: the qeth default is layer2. The OSA-card is able to convert between layer2 and layer3. Thus no lack of connectivity here. Nevertheless a customer may want to select layer3, especially if he wants to make use of TCP Segmentation Offload.
2. HiperSockets: the qeth default is layer3 to allow smooth communication with zOS. HiperSockets LANs are either layer2 or layer3; there is no connectivity between a layer2 participant and a layer3 participant.
3.virtual NICs attached to a z/VM VSWITCH or GuestLAN when Linux is running as a z/VM guest: Here the Linux definition has to follow the layer definition of the VSWITCH or GuestLAN in z/VM, otherwise connectivity is broken. Up to now there is no automatic detection of the layer defined in z/VM.