Bug 2083077
| Summary: | Add support in multipathd to listen for FPIN-Li events and mark effected paths as marginal | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 8 | Reporter: | MUNEENDRA (Broadcom) <muneendra.kumar> |
| Component: | device-mapper-multipath | Assignee: | Ben Marzinski <bmarzins> |
| Status: | CLOSED ERRATA | QA Contact: | Lin Li <lilin> |
| Severity: | medium | Docs Contact: | Kristina Slaveykova <kslaveyk> |
| Priority: | high | ||
| Version: | 8.7 | CC: | agk, bmarzins, gfialova, heinzm, kslaveyk, lilin, msnitzer, prajnoha, zkabelac |
| Target Milestone: | rc | Keywords: | Triaged |
| Target Release: | --- | Flags: | pm-rhel:
mirror+
|
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | device-mapper-multipath-0.8.4-25.el8 | Doc Type: | Enhancement |
| Doc Text: |
.`multipathd` now supports detecting FPIN-Li events
When you add a new value `fpin` for the `marginal_pathgroups` config option, you enable `multipathd` to monitor the Link Integrity Fabric Performance Impact Notification (PFIN-Li) events and move paths with link integrity issues to a marginal pathgroup. With the `fpin` value set, `multipathd` overrides its existing marginal path detection methods and relies on the Fibre Channel fabric to identify link integrity issues.
With this enhancement, the `multipathd` method becomes more robust in detecting marginal paths on Fibre Channel fabrics that can issue PFIN-Li events.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2022-11-08 10:47:39 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
MUNEENDRA (Broadcom)
2022-05-09 09:07:20 UTC
Backported. Muneedra, would you be able to test these RHEL-8 rpms? https://people.redhat.com/bmarzins/device-mapper-multipath/rpms/RHEL8/2083077/ (In reply to Ben Marzinski from comment #2) > Muneedra, would you be able to test these RHEL-8 rpms? > > https://people.redhat.com/bmarzins/device-mapper-multipath/rpms/RHEL8/ > 2083077/ Benjamin, we will do the testing and let you know the same. (In reply to MUNEENDRA (Broadcom) from comment #3) > (In reply to Ben Marzinski from comment #2) > > Muneedra, would you be able to test these RHEL-8 rpms? > > > > https://people.redhat.com/bmarzins/device-mapper-multipath/rpms/RHEL8/ > > 2083077/ > > Benjamin, > we will do the testing and let you know the same. Any update? Will update in a day or two (In reply to MUNEENDRA (Broadcom) from comment #9) > Will update in a day or two Any update? (In reply to Lin Li from comment #10) > (In reply to MUNEENDRA (Broadcom) from comment #9) > > Will update in a day or two > > Any update? The functionality is not working as expected with the initial rpm's provided by Benjamin. Benjamin is providing the additional rpm's to debug the issue further. The latest rpm's provided by Benjamin is working as expected. Thanks for all the help Benjamin. Move to verified according to comment 7 and comment 12. 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 |