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
        }
}

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:7714