Abstract: Presented herein are embodiments for providing and using a symbolic name for referencing an element of a non-volatile memory express (NVMe™) entity in an NVMe™-over-Fabric (NVMe-oF™) environment. In one or more embodiments, the symbolic name may be used to identify an element of an NVMe™ host or NVM subsystem in one or more processes. In one or more embodiments, a symbolic name may be provided as part of a registration process. Symbolic names may be used for identifying elements when performing other processes, such as masking and zoning for granting access rights. In one or more embodiments, a symbolic name may be shared by two or more elements.

Abstract: A port configuration migration system includes a primary I/O module connected to a server device via a secondary I/O module. A fabric manager system maps a virtual interface to a first downlink port on the primary I/O module that is connected to the secondary I/O module, with the virtual interface providing a virtual direct connection to the server device. The fabric manager system then configures the virtual interface with communication configuration information for the server device such that communications received via the first downlink port are transmitted using the virtual interface. The fabric manager system then receives a discovery communication from the server device via a second downlink port on the primary I/O module that is connected to the secondary I/O module, and remaps the virtual interface to the second downlink port such that communications received via the second downlink port are transmitted using the virtual interface.

Abstract: A multi-fabric VLAN configuration system includes a first fabric with server devices that are configured to communicate using VLANs, a primary I/O module coupled to the server devices, and a first fabric management system coupled to the server devices and the primary I/O module. The first fabric management system identifies VLAN information associated with the VLANs, automatically configures the primary I/O module using the VLAN information, and causes the VLAN information to be transmitted by the primary I/O module. A second fabric in the multi-fabric VLAN configuration system includes a leaf switch device that is coupled to the primary I/O module and that receives the VLAN information, and a second fabric management system that is coupled to the leaf switch device and that receives the VLAN information from the leaf switch device, and automatically configures the leaf switch device using the VLAN information.

Abstract: Presented herein are embodiments for implicitly or indirectly registering elements of a non-volatile memory express (NVMe™) entity in an NVMe-over-Fabric (NVMe-oF) environment. In one or more embodiments, one or more interactions between an NVMe™ entity and a centralized storage fabric service component, such as part of the Link Layer Discovery Protocol (LLDP) process or the Multicast Domain Name System (mDNS) process, may be used by the centralized storage fabric service to extract information about the NVMe™ entity and automatically register it with a centralized registration datastore. In one or more embodiments, the centralized registration datastore may be used to facilitate services in the NVMe-oF system, such as discovery of NVMe™ entities, provisioning, and access control. In one or more embodiments, an implicitly registered NVMe™ entity may also subsequently explicitly register, which may include supplying additional information about the NVMe™ entity.

Abstract: Presented herein are systems and methods for facilitating access control among elements of a non-volatile memory express (NVMe™) entity in an NVMe™-over-Fabric (NVMe-oF) environment. In one or more embodiments, NVMe™ entities, whether NVMe™ hosts or NVMe™ subsystems, can obtain information about elements of NVMe™ entities that have registered with a centralized storage fabric service component via a discovery controller of the centralize service. In one or more embodiments, based upon information received from requesting NVMe™ entities, the centralized storage fabric service creates and maintains a data store of zones, in which a zone comprises a listing of elements of NVMe™ entities that are members of that zone and have access rights relative to other members of that zone.

Abstract: A server-facing port activation system includes a core network system, a server device, and a networking device that includes at least one uplink port coupled to the core network system, and a first downlink port coupled to the server device. The networking device begin initialization operations and, in response, identifies that the first downlink port is coupled to the server device and prevents the first downlink port from being made available. While preventing the first downlink port from being made available, the networking device configures the at least one uplink port coupled to the core network system with server device information associated with the server device. The networking device then determines that the at least one uplink port coupled to the core network system is available and, in response, causes the first downlink port that is coupled to the server device to be made available.

Abstract: An automated multi-fabric link aggregation system includes leaf switch devices that have leaf switch device downlink ports, that are included in a first network fabric, and that are aggregated to provide a first aggregation fabric. Each leaf switch device generates discovery communications including a first network fabric identifier for the first network fabric, and a first aggregation fabric identifier for the first aggregation fabric. The leaf switch devices then transmit the discovery communications via the leaf switch device downlink ports. I/O modules that have I/O module uplink port are included in a second network fabric and are aggregated to provide a second aggregation fabric. The I/O modules receive the discovery communications via each of the I/O module uplink ports, determine that each received discovery communication includes the first network fabric identifier and the first aggregation fabric identifier and, in response, automatically configure the I/O module uplink ports in a LAG.

Abstract: A cluster deployment and management system includes a networking device that is coupled to a network and to each of a plurality of node devices in a cluster system. The networking device discovers then validates using a cluster profile each of the plurality of node devices in the cluster system. The networking device may then configure itself and any other networking devices according to the cluster profile. The networking device may then configure each of the plurality of node devices according to the cluster profile and deploy one or more applications and data to the node devices. The networking device may negotiate which of at least two networking devices present on the network and may perform lifecycle management operations on the at least one of the node. The networking device performs lifecycle management on at least one of the node devices during operation of the cluster system.

Abstract: A cluster deployment and management system includes a networking device that is coupled to a network and to each of a plurality of node devices in a cluster system. The networking device discovers then validates using a cluster profile each of the plurality of node devices in the cluster system. The networking device may then configure itself and any other networking devices according to the cluster profile. The networking device may then configure each of the plurality of node devices according to the cluster profile and deploy one or more applications and data to the node devices. The networking device may negotiate which of at least two networking devices present on the network and may perform lifecycle management operations on the at least one of the node. The networking device performs lifecycle management on at least one of the node devices during operation of the cluster system.

Abstract: A switching fabric role assignment system includes a plurality of switch devices coupled together in a switching fabric. A first switch device included in the plurality of switch devices receives an endhost device identification communication from an endhost device when the endhost device is connected to the first switch device. The first switch device uses the endhost device identification communication to identify an endhost device type of the endhost device and determines, based on the endhost device type, a first switch device role for the first switch device. The first switch device then transmits a first switch device role communication that identifies the first switch device role to a second switch device included in the plurality of switch devices and connected to the first switch device. The second switch device may then determine, based on the first switch device role, a second switch device role for the second switch device.

Abstract: Presented herein are embodiments for registering elements of a non-volatile memory express (NVMe) entity in an NVMe-over-Fabric (NVMe-oF) environment. In embodiments, a method for registering with a centralized storage fabric service component via a discovery controller (DC) of the centralize service comprises transmitting a DC registration command to the DC. In embodiments, the DC registration command includes a number of registration entries that the NVMe entity will be submitting for registration. In embodiments, the identified number of NVMe registration entries are transmitted to the centralized service and are stored in a registry. The NVMe registration entry may include an entry type for indicating an NVMe registration entry type, an NVMe qualified name (NQN) for identifying the NVMe entity, and a transport address for specifying an address of the element of the NVMe entity. Other NVMe entities may query the registry to obtain information about NVMe elements in the system.

Abstract: A multi-fabric VLAN configuration system includes a first fabric with server devices that are configured to communicate using VLANs, a primary I/O module coupled to the server devices, and a first fabric management system coupled to the server devices and the primary I/O module. The first fabric management system identifies VLAN information associated with the VLANs, automatically configures the primary I/O module using the VLAN information, and causes the VLAN information to be transmitted by the primary I/O module. A second fabric in the multi-fabric VLAN configuration system includes a leaf switch device that is coupled to the primary I/O module and that receives the VLAN information, and a second fabric management system that is coupled to the leaf switch device and that receives the VLAN information from the leaf switch device, and automatically configures the leaf switch device using the VLAN information.

Abstract: A port configuration migration system includes a primary I/O module connected to a server device via a secondary I/O module. A fabric manager system maps a virtual interface to a first downlink port on the primary I/O module that is connected to the secondary I/O module, with the virtual interface providing a virtual direct connection to the server device. The fabric manager system then configures the virtual interface with communication configuration information for the server device such that communications received via the first downlink port are transmitted using the virtual interface. The fabric manager system then receives a discovery communication from the server device via a second downlink port on the primary I/O module that is connected to the secondary I/O module, and remaps the virtual interface to the second downlink port such that communications received via the second downlink port are transmitted using the virtual interface.

Abstract: Presented herein are systems and methods for facilitating access control among elements of a non-volatile memory express (NVMe) entity in an NVMe-over-Fabric (NVMe-oF) environment. In one or more embodiments, NVMe entities, whether NVMe hosts or NVMe subsystems, can obtain information about elements of NVMe entities that have registered with a centralized storage fabric service component via a discovery controller of the centralize service. In one or more embodiments, based upon information received from requesting NVMe entities, the centralized storage fabric service creates and maintains a data store of zones, in which a zone comprises a listing of elements of NVMe entities that are members of that zone and have access rights relative to other members of that zone.

Abstract: Presented herein are embodiments for implicitly or indirectly registering elements of a non-volatile memory express (NVMe) entity in an NVMe-over-Fabric (NVMe-oF) environment. In one or more embodiments, one or more interactions between an NVMe entity and a centralized storage fabric service component, such as part of the Link Layer Discovery Protocol (LLDP) process or the Multicast Domain Name System (mDNS) process, may be used by the centralized storage fabric service to extract information about the NVMe entity and automatically register it with a centralized registration datastore. In one or more embodiments, the centralized registration datastore may be used to facilitate services in the NVMe-oF system, such as discovery of NVMe entities, provisioning, and access control. In one or more embodiments, an implicitly registered NVMe entity may also subsequently explicitly register, which may include supplying additional information about the NVMe entity.

Abstract: Presented herein are embodiments for registering elements of a non-volatile memory express (NVMe) entity in an NVMe-over-Fabric (NVMe-oF) environment. In embodiments, a method for registering with a centralized storage fabric service component via a discovery controller (DC) of the centralize service comprises transmitting a DC registration command to the DC. In embodiments, the DC registration command includes a number of registration entries that the NVMe entity will be submitting for registration. In embodiments, the identified number of NVMe registration entries are transmitted to the centralized service and are stored in a registry. The NVMe registration entry may include an entry type for indicating an NVMe registration entry type, an NVMe qualified name (NQN) for identifying the NVMe entity, and a transport address for specifying an address of the element of the NVMe entity. Other NVMe entities may query the registry to obtain information about NVMe elements in the system.

Abstract: Multicast Domain Name System (mDNS)-based pull registration systems and methods facilitate discovery in communication networks, such as Storage Area Networks (SANs) that operate in non-volatile memory express over Fabric (NVMe-oF) environments. In various embodiments, this is accomplished by allowing a network entity (e.g., a Centralized Discovery Controller (CDC)) to use a pull registration to exchange discovery information with a storage subsystem (e.g., a storage array), advantageously, without requiring storage subsystem to possess complex functionalities present in existing designs.

Abstract: Presented herein are embodiments for providing and using a symbolic name for referencing an element of a non-volatile memory express (NVMe) entity in an NVMe-over-Fabric (NVMe-oF) environment. In one or more embodiments, the symbolic name may be used to identify an element of an NVMe host or NVM subsystem in one or more processes. In one or more embodiments, a symbolic name may be provided as part of a registration process. Symbolic names may be used for identifying elements when performing other processes, such as masking and zoning for granting access rights. In one or more embodiments, a symbolic name may be shared by two or more elements.

Abstract: Multicast Domain Name System (mDNS)-based pull registration systems and methods facilitate discovery in communication networks, such as Storage Area Networks (SANs) that operate in non-volatile memory express over Fabric (NVMe-oF) environments. In various embodiments, this is accomplished by allowing a network entity (e.g., a Centralized Discovery Controller (CDC)) to use a pull registration to exchange discovery information with a storage subsystem (e.g., a storage array), advantageously, without requiring storage subsystem to possess complex functionalities present in existing designs.

Abstract: A switching fabric role assignment system includes a plurality of switch devices coupled together in a switching fabric. A first switch device included in the plurality of switch devices receives an endhost device identification communication from an endhost device when the endhost device is connected to the first switch device. The first switch device uses the endhost device identification communication to identify an endhost device type of the endhost device and determines, based on the endhost device type, a first switch device role for the first switch device. The first switch device then transmits a first switch device role communication that identifies the first switch device role to a second switch device included in the plurality of switch devices and connected to the first switch device. The second switch device may then determine, based on the first switch device role, a second switch device role for the second switch device.