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: 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 herein relate to managing data and network bandwidth. In an example implementation, a method includes monitoring a first location having a local volume and a local gateway and monitoring a second location having a first remote volume and a remote gateway. The method also includes determining a bandwidth requirement for a second remote volume at the second location and configuring the local gateway and the remote gateway for the bandwidth requirement. The method also includes adjusting the local gateway and the remote gateway when the bandwidth requirement changes.

Abstract: Example implementations relate to hard zoning capabilities for devices using Internet small computer system interface (iSCSI) protocol. For example, a method includes creating a virtual local area network (VLAN) at an Ethernet switch between an initiator and target adapter. The method includes assigning an access control list (ACL) to the VLAN, The method includes segregating a device of a plurality of devices connected to the SAN into a zone group. The method also includes controlling access of a zone group based on the ACL and frame filtering.

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: 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: 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: A system and method for target driven peer-zoning (TDPZ) synchronization can include a principal member device and a switch. The principal member device can include to send an active peer zone list request to a switch. In an example, the principal member device can store a first TDPZ database version number and a first TDPZ zone list. In an example, the switch may send a response based on the active peer zone list request. In an example, the response can include a second TDPZ database version number and a second TDPZ zone list. The principal member device may compare the first TDPZ database version number to the second TDPZ database version number.

Abstract: An example implementation may relate to a storage area network (SAN) switch and a SAN target device. For example, the SAN target device may issue an in-band diagnostic command to the SAN switch. The SAN target device may receive an in-band data message from the SAN switch in response to the in-band diagnostic command. The in-band data message may include diagnostic data about a port of the storage area network switch and a storage area network device connected to the port.

Abstract: Example embodiments relate to protocol agnostic storage access with a software defined network (SDN). A method may include receiving, at a SDN enabled switch, an initialization packet to access a storage volume. The method may include determining, at the SDN enabled switch, a storage protocol used by the initialization packet, adding a protocol tag indicative of the storage protocol to the initialization packet, and sending the initialization packet to a SDN controller. The method may include identifying, at the SDN controller, a storage application based on the protocol tag and sending the initialization packet to the storage application. The storage application may be one of a plurality of storage applications, each associated with a different storage protocol. The method may include performing, by the storage application, protocol-specific tasks.

Abstract: Examples include registration with a storage networking repository via a network interface device driver independent of a storage initiator. Some examples include registration with a storage networking repository, provision of a state change registration to the storage network device, and acquisition of login information for storage targets from the storage networking repository, each via a network interface device driver and independent of a storage initiator and a storage protocol driver.

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: Examples herein relate to managing data and network bandwidth. In an example implementation, a method includes monitoring a first location having a local volume and a local gateway and monitoring a second location having a first remote volume and a remote gateway. The method also includes determining a bandwidth requirement for a second remote volume at the second location and configuring the local gateway and the remote gateway for the bandwidth requirement. The method also includes adjusting the local gateway and the remote gateway when the bandwidth requirement changes.

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: Example implementations relate to hard zoning capabilities for devices using Internet small computer system interface (iSCSI) protocol. For example, a method includes creating a virtual local area network (VLAN) at an Ethernet switch between an initiator and target adapter. The method includes assigning an access control list (ACL) to the VLAN, The method includes segregating a device of a plurality of devices connected to the SAN into a zone group. The method also includes controlling access of a zone group based on the ACL and frame filtering.

Abstract: Examples include registration with a storage networking repository via a network interface device driver independent of a storage initiator. Some examples include registration with a storage networking repository, provision of a state change registration to the storage network device, and acquisition of login information for storage targets from the storage networking repository, each via a network interface device driver and independent of a storage initiator and a storage protocol driver.

Abstract: According to an example, coordination of adjustments to network frame hold time parameters between network devices in a network is initiated based on a trigger condition. Time data may be obtained from a plurality of network devices in the network, where the time data describes a network frame hold time parameter of each network device in the plurality and a network frame processing time of each network device. A set of affected network devices affected by network back pressure in the network, and a set of non-affected network devices in the plurality not included in the set of affected network devices, may be determined. Based on the time data, a pairing may be determined between a time-available network device from the set of non-affected network devices and a time-needed network devices, from the set of affected network devices, to receive an allocation of time credit from the time-available network device.