1841017 – RFE: Allow IP over InfiniBand (IPoIB) device to be configured

RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 1841017 - RFE: Allow IP over InfiniBand (IPoIB) device to be configured

Summary: RFE: Allow IP over InfiniBand (IPoIB) device to be configured

Keywords:
Status:	CLOSED ERRATA
Alias:	None
Product:	Red Hat Enterprise Linux 8
Classification:	Red Hat
Component:	nmstate
Sub Component:
Version:	8.3
Hardware:	Unspecified
OS:	Unspecified
Priority:	high
Severity:	high
Target Milestone:	rc
Target Release:	8.4
Assignee:	Gris Ge
QA Contact:	Mingyu Shi
Docs Contact:
URL:
Whiteboard:
Depends On:
Blocks:	1856279 1875967 1894575
TreeView+	depends on / blocked

Reported:	2020-05-28 07:12 UTC by Dominik Holler
Modified:	2022-05-07 13:47 UTC (History)
CC List:	8 users (show)
Fixed In Version:
Doc Type:	If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:	2021-05-18 15:16:54 UTC
Type:	Bug
Target Upstream Version:
Embargoed:
Dependent Products:
Flags:	pm-rhel: mirror+

Attachments	(Terms of Use)
verification (15.20 KB, text/plain) 2020-11-11 10:55 UTC, Mingyu Shi	no flags	Details
View All

Links
System	ID	Private	Priority	Status	Summary	Last Updated
Github	nmstate nmstate pull 1345	0	None	closed	InfiniBand: Add support of IP over InfiniBand	2020-11-16 03:29:39 UTC

Internal Links: 1785800

Description Dominik Holler 2020-05-28 07:12:41 UTC

nmstate should be able to configure an NetworkManager connection on an IP over InfiniBand (IPoIB) device for IP networking.
The nmstate configuration should be similar like an Ethernet interface.


The related configuration in NetwrokManager is documented in
https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html-single/configuring_infiniband_and_rdma_networks/index#configuring-an-ipoib-connection-using-nmcli-commands_configuring-ipoib

Comment 4 Dominik Holler 2020-07-28 17:28:39 UTC

Andrei, can you please share a verbal description of the Infiniband scenario you like to configure?

Comment 5 Andrei 2020-07-28 20:24:07 UTC

Hi Dominik,

Currently we are using oVirt 4.3 in our PROD.
1 or 10G is DATA network and IB is Storage network (iSCSI and NFS).
This part is working fine in 4.3 and 4.4

We are using IB network as VM migration network - it is working perfectly in 4.3. 4.4 - not wokring as we can't add oVirt network to IB adapter/bond.

IB VM migration is critical as we have some servers with 1G, and VM migration (for example in case of host software upgrade) can bу a huge problem (with VM 32Gb+ is close to impossible).

And still we are dreaming about oVirt IB pkey support for Vms (cheap low latency VM connection ...)

Comment 6 Dominik Holler 2020-07-29 06:42:09 UTC

Thanks Andrei, you feedback helps to push things in a good direction.

(In reply to Andrei from comment #5)
> Hi Dominik,
> 
> Currently we are using oVirt 4.3 in our PROD.
> 1 or 10G is DATA network and IB is Storage network (iSCSI and NFS).
> This part is working fine in 4.3 and 4.4
> 
> We are using IB network as VM migration network - it is working perfectly in
> 4.3. 4.4 - not wokring as we can't add oVirt network to IB adapter/bond.
> 
> IB VM migration is critical as we have some servers with 1G, and VM
> migration (for example in case of host software upgrade) can bу a huge
> problem (with VM 32Gb+ is close to impossible).

Which network configuration requires this for your example?
Do you use a bond of IB devices, maybe even in combination with SR-IOV?
Do you want to assign an IP address to infininband  devices (IPoIB)?
Do you want to set MTU explicitly? Are you using datagram mode only, or are other modes relevant, too?


> 
> And still we are dreaming about oVirt IB pkey support for Vms (cheap low
> latency VM connection ...)

Is there a way wo work around this by assigning a SR-IOV VF to a VM?

Comment 7 Andrei 2020-07-29 11:08:51 UTC

Hi Dominik,

> Which network configuration requires this for your example? 
Sorry, didn't get this.

SR-IOV / VF can be a solution but with huge drawback - RDMA is getting up to 4G per instance, and for small VM it can be critical.
So we don't use them.

We use Bond (single device 2 ports connected to to switches) in connected mode and IPoIB (usually we assign IP before adding bond to oVirt network).

Regurding MTU - we set it during oVirt netwrok creation - 65520. But there is a small problem - as default IB mode is datagram - the resul MTU is 1500 (the workaround is to adjust bond config file).
It will be greate to add IB mode (datagram / connect) selection to GUI.

Comment 8 Gris Ge 2020-09-27 14:35:57 UTC

For nmstate, the feature patch has been posted to upstream.

The desire state will be:

```yml
- name: mlx5_ib1.8013
  type: infiniband
  state: up
  infiniband:
    base-iface: mlx5_ib1
    mode: datagram
    pkey: '0x8013'
```


The IP over InfiniBand interface cannot be a bridge port as they don't have ethernet layer.
The IP over InfiniBand interface can only be bond port when bond is in active-backup mode which is limited by linux kernel.

The RoCE(RDMA over Converged Ethernet) does not have above restriction. The nmstate will treat the RoCE interfaces as normal ethernet interface, no code need to be amended.

Comment 9 Gris Ge 2020-09-27 14:39:01 UTC

The SR-IOV of InfiniBand require vendor specific tool, for example `mstconfig -d 83:00.0 set SRIOV_EN=1 NUM_OF_VFS=5`.

Hence nmstate cannot support configuring the SR-IOV of InfiniBand yet.

Comment 11 Dominik Holler 2020-10-09 13:26:23 UTC

(In reply to Gris Ge from comment #9)
> The SR-IOV of InfiniBand require vendor specific tool, for example
> `mstconfig -d 83:00.0 set SRIOV_EN=1 NUM_OF_VFS=5`.
> 
> Hence nmstate cannot support configuring the SR-IOV of InfiniBand yet.

Please handle SR-IOV the same way like Ethernet,
because this would enable Infiniband NICs to be supported, e.g.
https://docs.mellanox.com/pages/viewpage.action?pageId=12013542#SingleRootIOVirtualization(SRIOV)-ConfiguringSR-IOVforConnectX-4/Connect-IB/ConnectX-5(InfiniBand)

Comment 12 Gris Ge 2020-10-15 12:27:13 UTC

Upstream has merged the patch.

The infiniband over IP is supported including pkey, SR-IOV interfaces and bond.

Comment 17 Mingyu Shi 2020-11-11 10:55:10 UTC

Created attachment 1728293 [details]
verification

Verified with versions:
nmstate-0.4.1-2.el8.noarch
nispor-0.6.1-2.el8.x86_64
NetworkManager-1.28.0-0.1.el8.x86_64
DISTRO=RHEL-8.4.0-20201103.d.0
Linux rdma05.rhts.eng.pek2.redhat.com 4.18.0-241.el8.dt1.x86_64 #1 SMP Mon Nov 2 08:24:31 EST 2020 x86_64 x86_64 x86_64 GNU/Linux

Comment 19 errata-xmlrpc 2021-05-18 15:16:54 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (nmstate bug fix and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2021:1748

Note You need to log in before you can comment on or make changes to this bug.