Lines Matching full:fabric
48 discovered during a fabric login or scan, and they persist until the
77 Virtualization (NPIV) mechanism, a point-to-point connection to a Fabric
79 separate port to other endpoints on the fabric, even though it shares one
81 unique view of the fabric based on fabric zoning and array lun-masking
82 (just like a normal non-NPIV adapter). Using the Virtual Fabric (VF)
83 mechanism, adding a fabric header to each frame allows the port to
84 interact with the Fabric Port to join multiple fabrics. The port will
85 obtain an N_Port_ID on each fabric it joins. Each fabric will have its
88 on each virtual fabric.
95 distinct N_Port_ID and view of fabric endpoints and storage entities.
282 FC_VPORT_NO_FABRIC_SUPP - No Fabric Support
290 FC_VPORT_NO_FABRIC_RSCS - No Fabric Resources
291 The vport is not operational. The Fabric failed FDISC with a status
295 FC_VPORT_FABRIC_LOGOUT - Fabric Logout
296 The vport is not operational. The Fabric has LOGO'd the N_Port_ID
299 FC_VPORT_FABRIC_REJ_WWN - Fabric Rejected WWN
300 The vport is not operational. The Fabric failed FDISC with a status
317 | | Link Up & Loop | No Fabric Support |
319 | | Link Up & no Fabric | No Fabric Support |
321 | | Link Up & FLOGI response | No Fabric Support |
332 | | FDISC LS_RJT w/ no resources | No Fabric Resources |
334 | | FDISC LS_RJT w/ invalid | Fabric Rejected WWN |
346 | Active: | LOGO received from fabric | Fabric Logout |
352 | Fabric Logout: | Link still up | Unknown |
357 No Fabric Support:
358 No Fabric Resources:
359 Fabric Rejected WWN:
436 - If the driver detects the topology is loop, non-fabric, or the
524 topology type and existence of the fabric. As this is not applicable to