Networking
![]()
Linux® on IBM® Z includes several network device drivers that are specific to z/Architecture®.
Example

In the example there are six Linux instances; two of them run as z/VM® guests in one LPAR and a third Linux instance runs in another LPAR. Within z/VM, Linux instances can be connected directly by IUCV, virtual-CTC, or through a guest LAN or VSWITCH. Within and between LPARs, you can connect Linux instances through HiperSockets™. OSA-Express cards running in QDIO mode can connect the mainframe to an external network.
Linux instance 4 and 5 are guests of a KVM host and are connected through an Open vSwitch, which in turn is connected to the LAN through a Network Express adapter. Linux instance 6 runs in an LPAR and is connected over a Network Express adapter to the LAN.
Table 1 lists which control units and device type combinations are supported by the network device drivers.
| Device type | Control unit | Device driver | Comment |
|---|---|---|---|
| 1732/01 | 1731/01 | qeth | OSA configured as OSD |
| 1732/02 | 1731/02 | qeth | OSA configured as OSX |
| 1732/03 | 1731/02 | qeth | OSA configured as OSM |
| 1732/05 | 1731/05 | qeth | HiperSockets |
| 0000/00 | 3088/08 | ctcm | Virtual CTC under z/VM |
| 0000/00 | 3088/1e | ctcm | FICON® channel |
| 0000/00 | 3088/1f | ctcm | ESCON® channel |
| Device type | Device driver | Comment |
|---|---|---|
| RoCE | mlx5_core | See RoCE Express for more details. |
| ROC2 | mlx5_core | See RoCE Express for more details. |
| NETH | mlx5_core | See Network Express in hybrid mode for more details. |
| NETD | mlx5_core | See Network Express in direct mode for more details. |