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 2084365 - [RFE] enable device configuration selection to include the transport protocol.
Summary: [RFE] enable device configuration selection to include the transport protocol.
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: device-mapper-multipath
Version: 9.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: rc
: 9.1
Assignee: Ben Marzinski
QA Contact: Lin Li
Kristina Slaveykova
URL:
Whiteboard:
Depends On: 2065477
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-05-12 00:30 UTC by Ben Marzinski
Modified: 2022-11-15 13:04 UTC (History)
12 users (show)

Fixed In Version: device-mapper-multipath-0.8.7-9.el9
Doc Type: Enhancement
Doc Text:
.Enabled protocol specific configuration of multipath device paths Previously due to different optimal configurations for the different protocols, it was impossible to set the configuration correctly without setting an option for each individual protocol. With this enhancement, users can now configure multipath device paths based on their path transport protocol. Use the `protocol` subsection of the `overrides` section in the `/etc/multipath.conf` file to correctly configure multipath device paths, based on their protocol.
Clone Of: 2065477
Environment:
Last Closed: 2022-11-15 11:16:24 UTC
Type: Bug
Target Upstream Version:
Embargoed:
pm-rhel: mirror+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-121785 0 None None None 2022-10-03 14:01:51 UTC
Red Hat Product Errata RHBA-2022:8313 0 None None None 2022-11-15 11:16:41 UTC

Comment 1 Ben Marzinski 2022-05-17 17:30:43 UTC 
The final solution to to is to add a protocol subsection to the overrides section of multipath.conf, which can contain multiple protocol subsections. Path devices are matched against the protocol subsection using the mandatory "type" attribute.  Attributes in a matching protocol subsection take precedence over attributes in the rest
of the overrides section, which like always take precedence of attributes in the devices and defaults sections. If there are multiple matching protocol subsections, later entries take precedence. The "type" attribute can be one of scsi:fcp, scsi:spi, scsi:ssa, scsi:sbp, scsi:srp, scsi:iscsi, scsi:sas, scsi:adt, scsi:ata, scsi:unspec, ccw, cciss, nvme, and undef. The protocol that a path is using can be viewed by running:

multipathd show paths format "%d %P"

The only attributes that can be set in the protocol subsection are "type", "dev_loss_tmo", "fast_io_fail_tmo", and "eh_deadline". Here is an example of a overrides sections with protocol subsections:

overrides {
        protocol {
                type "scsi:fcp"
                dev_loss_tmo 70
                fast_io_fail_tmo 10
                eh_deadline 360
        }
        protocol {
                type "scsi:iscsi"
                fast_io_fail 120
        }
}
Comment 4 Lin Li 2022-06-01 10:23:36 UTC 
[root@storageqe-05 ~]# rpm -qa | grep multipath
device-mapper-multipath-libs-0.8.7-9.el9.x86_64
device-mapper-multipath-0.8.7-9.el9.x86_64

[root@storageqe-05 ~]# man multipath.conf
       protocol subsection
              The protocol subsection recognizes the following mandatory attribute:

              type   The protocol string of the  path  device.  The  possible  values  are  scsi:fcp,  scsi:spi,  scsi:ssa,  scsi:sbp,  scsi:srp,
                     scsi:iscsi,  scsi:sas,  scsi:adt,  scsi:ata, scsi:unspec, ccw, cciss, nvme, and undef. This is not a regular expression. the
                     path device protcol string must match exactly. The protocol that a path is using can be viewed by  running  multipathd  show
                     paths format "%d %P"

              The following attributes are optional; if not set, the default values are taken from the overrides, devices, or defaults section:

                     fast_io_fail_tmo
                     dev_loss_tmo
                     eh_deadline


[root@storageqe-05 ~]# multipathd show paths format "%d %P"
dev protocol   
sda scsi:unspec
sdj scsi:fcp   
sdk scsi:fcp   
sdl scsi:fcp   
sdm scsi:fcp   
sdn scsi:fcp   
sdo scsi:fcp   
sdp scsi:fcp   
sdq scsi:fcp   
sdb scsi:fcp   
sdc scsi:fcp   
sdd scsi:fcp   
sde scsi:fcp   
sdf scsi:fcp   
sdg scsi:fcp   
sdh scsi:fcp   
sdi scsi:fcp
Comment 10 errata-xmlrpc 2022-11-15 11:16:24 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 (device-mapper-multipath 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-2022:8313
Note You need to log in before you can comment on or make changes to this bug.