Hewlett Packard Enterprise Development LP

Hewlett-Packard Development Company, L.p.

Rupin Tashi Mohan

Krishna Babu Puttagunta

Vivek Agarwal

Asutosh Satapathy

Curtis C Ballard

Komateswar Dhanadevan

Alice Terumi Clark

Dheeraj Sharma

Govind Chandru Rathod

Charles J Newfell, Jr

Kumar Rahul

George Shin

Unnikrishnan Ponnan Katangot

Christopher Robert Nichols

Travis Pascoe

Ayyanar Perumal

Sudheer Vanapalli

Andrew E S MacKay

Radhakrishnan Velchamy

Aithal Basrur Girish

Kasthurirengan Karthigeyan

Julio Valladares

Satyaprakash Rao

Shrinivas B Kulkarni

Y Ravindra Paramashivappa

Daniel Shea

Barry A Maskas

Andrew ES Mackay

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.

Storage system port information management

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.

Determining path information in a computing network

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.

Fabric driven non-volatile memory express subsystem zoning

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

Universal host and non-volatile memory express storage domain discovery for non-volatile memory express over fabrics

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.

Managing distribution of I/O queue pairs of a target among hosts

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.

Network bandwidth configuration

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.

Group zoning and access control over a network

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.

Determining non-TDP zones in a storage area network

Examples include distribution of I/O Q-connections of an NVMe&#x2122; subsystem among hosts that are to communicate with the NVMe&#x2122; subsystem in an NVMe&#x2122; zone of a system. Some examples receive information including a number of I/O Q-connections available at the NVMe&#x2122; subsystem, register the number of available I/O Q-connections of the NVMe&#x2122; subsystem with an NVMe&#x2122; fabric controller, determine a number of I/O Q-connections of the NVMe&#x2122; 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&#x2122; subsystem to be used by the host.

Distributing I/O Q-connections of subsytems among hosts

In one example, provide a plurality of initial switch configuration templates associated with network switches, establishing a link with a network switch comprising a connection with a principal port of the network switch, select from the plurality of initial switch configuration templates an initial switch configuration template associated with the network switch device, and transmit to the network switch device, through the principal port, an in-band command with the selected initial switch configuration template.

Switch configuration

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.

Server network interface level failover

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.

Target driven peer-zoning synchronization

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.

Growing community of inventors

Andover, MA, United States of America

Rupin Tashi Mohan