Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
This bz is for implementing more intelligent scsi_dh attachment. Today, it is based on which scsi_dh module is loaded first.
For Clarrions we want to do below. We will want to do something similar for other boxes that support vendor specific methods and ALUA.
In the standard inquiry return, byte 5 bits 4 and 5 (zero-relative) contain the
TPGS status. They'll be 00 on a PNR array and 11 on an ALUA box. The lun_state
information can be ambiguous as 0x01 and 0x02 are returned in both ALUA and PNR
modes but means different things;
0x01 (PNR) LUN bound and assigned to the OTHER SP
0x01 (ALUA) LUN bound and using the non-optimized path
0x02 (PNR) LUN bound and assigned to THIS SP
0x02 (ALUA) LUN bound and using the optimized path
So I'd say we check TPGS first and then we can interpret the lun_state
accordingly based on that info...
Comment 2RHEL Program Management
2011-05-13 15:26:07 UTC
This request was evaluated by Red Hat Product Management for inclusion
in a Red Hat Enterprise Linux maintenance release. Product Management has
requested further review of this request by Red Hat Engineering, for potential
inclusion in a Red Hat Enterprise Linux Update release for currently deployed
products. This request is not yet committed for inclusion in an Update release.