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 2091653 - [DDF] Section misses Predictable Names information for RoCE adapters, introduced with RHEL 9.0
Summary: [DDF] Section misses Predictable Names information for RoCE adapters, introdu...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: Documentation
Version: unspecified
Hardware: All
OS: All
medium
unspecified
Target Milestone: rc
: 9.0
Assignee: Mayur Patil
QA Contact: smitterl
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-05-30 16:02 UTC by Direct Docs Feedback
Modified: 2022-10-11 15:37 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
.RoCE Express Adapters now use an improved interface naming scheme With this enhancement, RDMA over Converged Ethernet (RoCE) Express adapters use the predictable interface naming scheme and the Peripheral Communication Interface on z-system (zPCI) connector. In this naming scheme, RHEL uses user identifier (UID) or function identifier (FID) to generate unique names. In case that no unique UID is available, RHEL uses FID to set the naming scheme.
Clone Of:
Environment:
Last Closed: 2022-10-11 12:07:37 UTC
Type: ---
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1939914 1 None None None 2023-05-06 08:33:36 UTC
Red Hat Bugzilla 1939916 1 None None None 2023-05-06 08:33:21 UTC
Red Hat Bugzilla 1940049 1 None None None 2022-05-30 16:06:37 UTC
Red Hat Bugzilla 1940050 1 None None None 2022-05-30 16:07:01 UTC
Red Hat Issue Tracker RHELPLAN-123682 0 None None None 2022-05-30 16:16:03 UTC

Description Direct Docs Feedback 2022-05-30 16:02:09 UTC
IIUC, this section currently only documents OSA/OSD adapters.
For RoCE Express adapters, we have Predictable Names with their own scheme. More info in IBM docs [1].

In short RoCE Express uses zPCI.
They can be given unique names through their FID or UID. Usage of UID is recommended by IBM.
These new Predictable Interface Name schemes are only available in the current 9.0 release, not any RHEL 8 release.

[1]https://www.ibm.com/docs/en/linux-on-systems?topic=identifiers-interface-names

Reported by: smitterl

https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/9/html/configuring_and_managing_networking/consistent-network-interface-device-naming_configuring-and-managing-networking#annotations:d5a84e5d-0e4e-46f6-8ecc-1abdcee4dbc6

Comment 1 smitterl 2022-05-30 16:03:58 UTC
Section 1.4. Predictable network interface device names on the System z platform explained


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