> The FC HBA driver put out by Qlogic works well but does a silly thing;
> it enumerates devices from 0, instead of by the actually loop ID.
> This makes it impossible to spec absolute paths to the device, as
> everything will shift when devices are moved on the FC loop.
There are several reasons why this is done:
Most modern SANs use soft loop ID which means that the ID is determined at
login time to the SAN, so changes as the SAN composition changes, therefore
the loop ID isn't really meaningful anyway.
FC drivers are coming around to the notion of persistent binding, which is
where you try to identify your devices by WWN instead of loop ID. This is
usually implemented as a mapping function which assigns a known SCSI pun to a
particular WWN regardless of the actual loop ID.
Version 5.x of the qla2x00 driver (in SuSE 7.3 and also on the IBM website but
not the qlogic website [yet]) does arbitrated loop. Now, since arbitrated
loop has two or more paths to the device through different ports with possibly
different loop IDs, which loop ID would you use as the "actual" one?
James Bottomley
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Sun Oct 07 2001 - 21:00:37 EST