Abstract: In some examples, a management system receives, from a first storage system, first port information of ports in the first storage system, and receives, from a second storage system, second port information of ports in a second storage system. The management system merges the first port information from the first storage system and the second port information from the second storage system into merged port information. The management system receives, from the first storage system, a request for port information of ports in the second storage system, and sends, to the first storage system, the second port information for use in path selection from hosts to the first and second storage systems.

Abstract: In one implementation, a non-transitory machine-readable storage medium may store instructions that upon execution cause a processor to: determine, by a network device, path information for a plurality of paths in a computing fabric, the path information identifying alternative paths to access namespaces; determine, by the network device, a first portion of the path information that is associated with a first host; and provide, by the network device the first portion of the path information to the first host.

Abstract: In some examples, fabric driven NVMe subsystem zoning may include receiving, from a non-volatile memory express (NVMe) Name Server (NNS), a zoning specification that includes an indication of a host that is to communicate with a given NVMe subsystem of an NVMe storage domain. Based on the zoning specification, the host may be designated as being permitted to connect to the given NVMe subsystem of the NVMe storage domain. An NVMe connect command may be received from the host. Based on the designation and an analysis of the NVMe connect command, a connection may be established between the given NVMe subsystem of the NVMe storage domain and the host.

Abstract: In some examples, universal host and NVMe™ storage domain discovery for NVM Express™ over Fabrics (NVMe-oF™) may include broadcasting location parameters to a host and a plurality of NVMe™ storage domains for discovery of a NVM Express™ over Fabrics (NVMe-oF™) service. Based on host parameters and NVMe™ storage domain parameters received in response to the broadcast location parameters, the host and the NVMe™ storage domains may be respectively registered with the NVMe-oF™ service. A mapping that indicates a specified NVMe™ storage domain that is to communicate with the host may be obtained. Communication may be implemented between the host and the specified NVMe™ storage domain by forwarding the mapping and associated discovery target parameters to the host to implement discovery of the specified NVMe™ storage domain by the host, and connection of the specified NVMe™ storage domain to the host.

Abstract: Examples relate to managing distribution of a total number of I/O queue pairs of an NVMe target among a plurality of NVM subsystems of the NVMe target and a plurality of hosts connected to the NVMe target. A target controller of the NVMe target defines a number of I/O queue pairs for a dedicated pool and a number of I/O queue pairs for a reserved pool based on the total number of I/O queue pairs. The target controller distributes a number of I/O queue pairs to each of the hosts from the number of I/O queue pairs of the dedicated pool and utilizes the number of I/O queue pairs of the reserved pool to balance out the number of I/O queue pairs on each of the hosts by selectively changing the number of I/O queue pairs of the reserved pool.

Abstract: In some examples, universal host and NVMe™ storage domain discovery for NVM Express™ over Fabrics (NVMe-oF™) may include broadcasting location parameters to a host and a plurality of NVMe™ storage domains for discovery of a NVM Express™ over Fabrics (NVMe-oF™) service. Based on host parameters and NVMe™ storage domain parameters received in response to the broadcast location parameters, the host and the NVMe™ storage domains may be respectively registered with the NVMe-oF™ service. A mapping that indicates a specified NVMe™ storage domain that is to communicate with the host may be obtained. Communication may be implemented between the host and the specified NVMe™ storage domain by forwarding the mapping and associated discovery target parameters to the host to implement discovery of the specified NVMe™ storage domain by the host, and connection of the specified NVMe™ storage domain to the host.

Abstract: Examples include determination of non-TDP zones in a storage area network. Some examples use a member zone list request to request identification of each zone of which a target port of a target device is a member, identify each TDP zone among identified zones of which a target port is a member and determine whether the identified zones include one or more non-TDP zones.

Abstract: Examples include determination of non-TDP zones in a storage area network. Some examples use a member zone list request to request identification of each zone of which a target port of a target device is a member, identify each TDP zone among identified zones of which a target port is a member and determine whether the identified zones include one or more non-TDP zones.

Abstract: In some examples, fabric driven NVMe subsystem zoning may include receiving, from a non-volatile memory express (NVMe) Name Server (NNS), a zoning specification that includes an indication of a host that is to communicate with a given NVMe subsystem of an NVMe storage domain. Based on the zoning specification, the host may be designated as being permitted to connect to the given NVMe subsystem of the NVMe storage domain. An NVMe connect command may be received from the host. Based on the designation and an analysis of the NVMe connect command, a connection may be established between the given NVMe subsystem of the NVMe storage domain and the host.

Abstract: In some examples, fabric driven NVMe subsystem zoning may include receiving, from a non-volatile memory express (NVMe) Name Server (NNS), a zoning specification that includes an indication of a host that is to communicate with a given NVMe subsystem of an NVMe storage domain. Based on the zoning specification, the host may be designated as being permitted to connect to the given NVMe subsystem of the NVMe storage domain. An NVMe connect command may be received from the host. Based on the designation and an analysis of the NVMe connect command, a connection may be established between the given NVMe subsystem of the NVMe storage domain and the host.

Abstract: Examples include distribution of I/O Q-connections of an NVMe™ subsystem among hosts that are to communicate with the NVMe™ subsystem in an NVMe™ zone of a system. Some examples receive information including a number of I/O Q-connections available at the NVMe™ subsystem, register the number of available I/O Q-connections of the NVMe™ subsystem with an NVMe™ fabric controller, determine a number of I/O Q-connections of the NVMe™ subsystem allowed to be used by each host and send to, each host, a first notification including the number of allowed I/O Q-connections of the NVMe™ subsystem to be used by the host.

Abstract: In one implementation, a non-transitory machine-readable storage medium may store instructions that upon execution cause a processor to: determine, by a network device, path information for a plurality of paths in a computing fabric, the path information identifying alternative paths to access namespaces; determine, by the network device, a first portion of the path information that is associated with a first host; and provide, by the network device the first portion of the path information to the first host.

Abstract: In some examples, universal host and NVMe™ storage domain discovery for NVM Express™ over Fabrics (NVMe-oF™) may include broadcasting location parameters to a host and a plurality of NVMe™ storage domains for discovery of a NVM Express™ over Fabrics (NVMe-oF™) service. Based on host parameters and NVMe™ storage domain parameters received in response to the broadcast location parameters, the host and the NVMe™ storage domains may be respectively registered with the NVMe-oF™ service. A mapping that indicates a specified NVMe™ storage domain that is to communicate with the host may be obtained. Communication may be implemented between the host and the specified NVMe™ storage domain by forwarding the mapping and associated discovery target parameters to the host to implement discovery of the specified NVMe™ storage domain by the host, and connection of the specified NVMe™ storage domain to the host.

Abstract: In one implementation, a non-transitory machine-readable storage medium may store instructions that upon execution cause a processor to: determine, by a network device, path information for a plurality of paths in a computing fabric, the path information identifying alternative paths to access namespaces; determine, by the network device, a first portion of the path information that is associated with a first host; and provide, by the network device the first portion of the path information to the first host.

Abstract: A technique includes hosting an Internet Storage Name Service (iSNS) server on a network switch to provide access to a plurality of subnets; and configuring the iSNS server to be an active server for a first subnet of a plurality of subnets and to be a backup server for a second subnet of the plurality of subnets.

Abstract: In some examples, to define a connection path of an initiator to target ports of a plurality of controller nodes that manage access of data in a storage system, a provisioning system determines loads of respective sets of target ports, and selects a selected set of target ports from among the sets of target ports for inclusion in the connection path based on the determined loads.

Abstract: In some examples, to define a connection path of an initiator to target ports of a plurality of controller nodes that manage access of data in a storage system, a provisioning system determines loads of respective sets of target ports, and selects a selected set of target ports from among the sets of target ports for inclusion in the connection path based on the determined loads.

Abstract: A technique includes hosting an Internet Storage Name Service (iSNS) server on a network switch to provide access to a plurality of subnets; and configuring the iSNS server to be an active server for a first subnet of a plurality of subnets and to be a backup server for a second subnet of the plurality of subnets.

Abstract: Described herein are exemplary storage network architectures and methods for diagnosing a path in a storage network. Devices and nodes in the storage network have ports. Port metrics for the ports may be ascertained and used to detect link problems in paths. In an exemplary described implementation, the following actions are effectuated in a storage network: ascertaining one or more port metrics for at least one device at a first time; ascertaining the one or more port metrics for the at least one device at a second time; analyzing the one or more port metrics from the first and second times; and determining if the analysis indicates a link problem in a path of the storage network.