Bug 2218741

Summary:	Add support in multipathd for NVMe 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 MIGRATED	QA Contact:	Lin Li <lilin>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	8.10	CC:	agk, bmarzins, heinzm, lilin, msnitzer, prajnoha, zkabelac
Target Milestone:	rc	Keywords:	MigratedToJIRA
Target Release:	---	Flags:	pm-rhel: mirror+
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-09-21 19:42:31 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) 2023-06-30 05:33:33 UTC

Description of problem:
Needs to add a support to Handle FPIN-li events for NVMe in multipathd.
At present we have the support for only scsi devices(EP).

When link integrity issues are detected on a Fibre Channel fabric,
A Link Integrity Fabric Performance Impact Notification (FPIN-Li) can be send to a node. 
If multipathd listens for these events, it can use them to control a path's marginal status, 
instead of trying to detect marginal paths internally. 
The path will remain marginal until a registered state change notification (RSCN) or Link Up event is received.


Version-Release number of selected component (if applicable):
RHEL8.10



Actual results:
Multipathd has a more robust method of detecting marginal paths on Fibre Channel fabrics that can issue PFIN-Li events.


Additional info:
This feature which support scsi  is already part of RHEL9.0  and RHEL8.7

Comment 1 RHEL Program Management 2023-09-21 19:39:29 UTC

Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.