Documentation/scsi/scsi_fc_transport.rst

44   Virtualization (NPIV) mechanism, a point-to-point connection to a Fabric
46   separate port to other endpoints on the fabric, even though it shares one
48   unique view of the fabric based on fabric zoning and array lun-masking
49   (just like a normal non-NPIV adapter).  Using the Virtual Fabric (VF)
50   mechanism, adding a fabric header to each frame allows the port to
51   interact with the Fabric Port to join multiple fabrics. The port will
52   obtain an N_Port_ID on each fabric it joins. Each fabric will have its
55   on each virtual fabric.
62   distinct N_Port_ID and view of fabric endpoints and storage entities.
249     FC_VPORT_NO_FABRIC_SUPP     - No Fabric Support
257     FC_VPORT_NO_FABRIC_RSCS     - No Fabric Resources
258       The vport is not operational. The Fabric failed FDISC with a status
262     FC_VPORT_FABRIC_LOGOUT      - Fabric Logout
263       The vport is not operational. The Fabric has LOGO'd the N_Port_ID
266     FC_VPORT_FABRIC_REJ_WWN     - Fabric Rejected WWN
267       The vport is not operational. The Fabric failed FDISC with a status
284    |                  | Link Up & Loop                 | No Fabric Support   |
286    |                  | Link Up & no Fabric            | No Fabric Support   |
288    |                  | Link Up & FLOGI response       | No Fabric Support   |
299    |                  | FDISC LS_RJT w/ no resources   | No Fabric Resources |
301    |                  | FDISC LS_RJT w/ invalid        | Fabric Rejected WWN |
313    | Active:          | LOGO received from fabric      | Fabric Logout       |
319    | Fabric Logout:   | Link still up                  | Unknown             |
324     No Fabric Support:
325     No Fabric Resources:
326     Fabric Rejected WWN:
403         - If the driver detects the topology is loop, non-fabric, or the
491     topology type and existence of the fabric. As this is not applicable to