How PowerVC assigns Fibre Channel ports
When creating virtual Fibre Channel adapters for a new virtual server, IBM® Power® Virtualization Center first selects a Virtual I/O Server on the chosen host, and then selects physical Fibre Channel ports within that Virtual I/O Server. By default, every Virtual I/O Server on the chosen host is used, but custom storage connectivity groups can be used to constrain that selection.
- There is a direct cable connection from the Fibre Channel port to the storage controller.
- The port has a Fibre Channel loopback test plug attached.
- Does the port have a port tag? If so, does that port tag allow connectivity with this storage connectivity group? If it does not allow connectivity, the port is rejected.
- Does the port allow connectivity? If not, the port is rejected.
- Is the port's status OK, or if it has an error, is it an error that is not related to NPIV? If not, the port is rejected.
- Do the ports connect to the required fabrics, as specified in the NPIV Fabric Access Requirement setting? If not the VIOS cannot be used.
- For each fabric required, are there enough ports to meet the For each VIOS, number of ports to connect per fabric setting? If not, the VIOS cannot be used.
- The resulting ports are sorted by Fibre Channel adapter and then are further sorted by those that are the least utilized, when considering all active NPIV connections.
- The first n ports are chosen and mapped to virtual Fibre Channel adapters, where n is the value specified for For each VIOS, number of ports to connect per fabric.