Abstract: Systems and methods utilize discovery log entry identifiers (DLEIDs) to identify individual discovery log page entries (DLPEs) in a discovery log page, for example, to allow a name server to manipulate DLPEs and perform specific operations, including zoning operations. Thus, DLEIDs advantageously reduce data flow and repetitive full discovery log page requests and responses and associated processing times; especially, in scenarios where changes to data are minimal. Further, a DLEID-based get log page command may be used to perform push and pull registrations, e.g., to query a specific set of end devices. Advantageously, this reduces messages size and, thus, the number of messages that need to be exchanged, e.g., during an addition or deletion of end devices, especially in larger environments.

Abstract: Systems and methods utilize discovery log entry identifiers (DLEIDs) to identify individual discovery log page entries (DLPEs) in a discovery log page, for example, to allow a name server to manipulate DLPEs and perform specific operations, including zoning operations. Thus, DLEIDs advantageously reduce data flow and repetitive full discovery log page requests and responses and associated processing times; especially, in scenarios where changes to data are minimal. Further, a DLEID-based get log page command may be used to perform push and pull registrations, e.g., to query a specific set of end devices. Advantageously, this reduces messages size and, thus, the number of messages that need to be exchanged, e.g., during an addition or deletion of end devices, especially in larger environments.

Abstract: Systems and methods use zoning configuration to construct border gateway protocol (BGP) route maps. The constructed route maps may then be used to selectively advertise routes between BGP peer devices without having to advertise all available routes to all entities or subsystems in a network. Advantageously, this significantly reduces potential security risks to the network and improves scalability of services in non-volatile memory express over Fabric and other systems.

Abstract: Border gateway protocol (BGP) configuration systems and methods automatically establish a BGP peering relationship between a BGP peer device and a centralized discovery controller (CDC) that allow the CDC to advertise routes to the BGP peer device. Various embodiments accomplish this by exchanging BGP information between the CDC, the BGP peer device, and a BGP auto-configuration service, which configures BGP parameters that establish the BGP peering relationship.

Abstract: Systems and methods provide modern storage networks, such as those utilizing a non-volatile memory express over Fabric (NVMe-oF) system, with connectivity options that meet low-latency and high-throughput demands. In certain embodiments, this is accomplished by enabling network entities to acquire and utilize network information, including discovery information, to dynamically manage routing tables and build routes, e.g., to allow a host to send out frames through desired interfaces to reach target destinations. An automated IP routing update service allows for dynamically creating, reading, updating, and deleting functions of otherwise static IP routing table entries to streamline functions in the storage fabric.

Abstract: A congestion and failure detector and localizer running on a storage array locally monitors ports of the storage array for IO failures and local link errors and remotely monitors ports of host initiators and host-side and storage array-side switches for link errors. Based on whether the local link error rate is increasing at any ports, whether IO failures are associated with a single host initiator port, and whether link error rate is increasing on both the host initiator and initiator-side switch, the congestion and failure detector and localizer generates a flag indicating either a physical link problem between the storage array and adjacent switch, ISL physical issue or spreading congestion, host initiator-side physical link problem, or path congestion. The flag identifies the storage array port, issue type, link, fabric name, and host initiator.

Abstract: Systems and methods provide zero-configuration provisioning for modern storage networks such as those utilizing a non-volatile memory express over Fabric (NVMe-oF) system. In various embodiments, this is accomplished by leveraging discovery information, such as multicast Domain Name System (mDNS) information, to locate subsystems in a network and to explicitly and dynamically specify target destinations without a Centralized Discovery Controller (CDC) client having to modify its routing table.

Abstract: Centralized quality-of-service (QoS) policies administration in a storage area network (SAN) is a problem without meaningful solutions. Current implementations require explicit administration of end points, which is error-prone and not scalable. Zoning for NVMe-oF is defined as a method to specify connectivity access control information on the Discovery Controller (DC) of an NVMe-oF fabric, not as a way to specify QoS policies. Embodiments comprise centrally specifying one or more QoS parameters as part of NVMe-oF zoning definitions maintained at an NVMe-oF DC to centrally controlled QoS parameters property in an NVMe-oF Zone. Accordingly, embodiments provide mechanisms to specify QoS parameters in a centralized manner to eliminate requiring a system administrator having to perform per-connection QoS provisioning.

Abstract: Systems and methods for detecting cybersecurity attacks comprise monitoring switches in a Fibre Channel (FC) fabric to obtain and examine network information to identify indicators of compromise (IoC), such as an attempt of a compromise or an actual compromise of the FC fabric by an unauthorized device. Exemplary IoCs comprise changes in zoning and/or the number of switches in the fabric.

Abstract: A traditional storage platform performs many basic functions, such as storage partitions allocation (i.e., namespace masking) and many advanced functions, such as deduplication or dynamic storage allocation. These functions need to be managed and this results in a multiple management system paradigm, in which a fabric management application manages the fabric connectivity policies (i.e., Zoning), while a storage management application manages the storage namespace mappings and advanced functions. Embodiments herein provide for centralized management for both connectivity and storage namespace mapping, among other advanced features. Namespace zoning information may comprise Namespace ZoneGroups, Namespace Zones, Namespace Zone Members, Namespace ZoneAlias, and Namespace ZoneAlias Members, which expand the NVMe-oF zoning framework from just connectivity control to full Namespaces allocation.

Abstract: A Centralized Discovery Controller (CDC) uses built-in intelligence to determine or estimate whether a connection with a non-volatile memory express (NVMe) entity has been discontinued intentionally or whether a connection loss is rather transient, e.g., due to a temporary network issue. In the former case, the CDC sends out asynchronous event notifications (AENs) and communicates the absence of the NVMe entity in a get log page to indicate an administrative access control action, e.g., a user intervention due to a zoning change or the removal of an entity due to a hardware failure. In the latter case, the CDC creates an “unreachable” entry in the name server database that indicates a CDC connectivity failure but maintains the entity in the name server database despite the connection loss, refraining from sending out notifications to relevant (or impacted) entities to increase bandwidth, traffic stability, and network availability.

Abstract: Provided is a distribution platform and method for physician-owned Durable Medical Equipment (DMEs). In the platform, the system and method authenticate a physician and select a patient. The system and method then select a product, in the form of a HCPCS code, general description, or brand model number, from a displayed set of possible products that match the service being provided. The system and method then select or confirm auto-population of the effective date of the prescription, select the frequency at which the selected products can be dispensed to the patient, and electronically sign, by the physician, a recap of the prescription which is auto-populated with the validated patient's name or other unique identifier, product, date of prescription, frequency, and the physician's NPI (“National Provider Identifier Standard”).

Abstract: Embodiments herein comprise a centralized NVMe-oF namespace masking and configuration repository, which may be referenced for convenience herein as a distributed configuration service (DCS). By centralizing the functionality, there is no longer a requirement that each host, network element, and subsystem have its own user interface (UI). DCS embodiments provide a single UI for a number of features, including but not limited to: (1) viewing the list of Host interfaces that are attached to the network and are registered; (2) viewing the list of Subsystem interfaces that are attached to the IP Network and are registered with the DCS; (3) viewing the storage capacity available behind each subsystem interface; and (4) allowing a user to define the Host to Subsystem interface relationships as well as define how much storage should be allocated to each Host.

Abstract: System and methods for using a discovery controller to establish network connections in a network that comprises Non-Volatile Memory Express™ over fabrics (NVMe-oF™) entities that support multicast change notifications comprise: in response to a change that affects at an NVMe-oF™ entity that has not yet established a connection with the discovery controller, generating a multicast change notification (MCN) that notifies the unconnected entity of the change and automatically communicating the MCN to the unconnected entity without requiring an explicit persistent connection to the discovery controller, e.g., to access storage ports in the network.

Abstract: A current technique to enforce a Zoning configuration is referred to as “Hard Zoning”. Hard Zoning is a technique in which network switches in a fabric inspect packets to ascertain if a packet should be forwarded or discarded, according to the communication between nodes allowed by the Zoning configuration. For the network switches to be able to perform this packet-by-packet filtering, Zoning information needs to be supplied to the network switches. However, current approaches involve sending duplicate data to switches. These approaches are very inefficient and cumbersome. Accordingly, embodiments comprise a Centralized Discovery Controller (CDC) that collects network information, generates, for a switch, its appropriate zoning information, and sends the switch-specific zoning information to that switch.

Abstract: Provided is a distribution platform for physician-owned Durable Medical Equipment (DMEs). In the platform, the system authenticates a physician and selects or creates a patient, and determines a set of possible diagnosis code combinations that match a service being provided. The system selects a product from a displayed set of products that match the service being provided, dynamically generates a set of medical necessities, and confirms the generated set of medical necessities. The system selects a product SKU based on the determined set of possible diagnosis code combinations, the selected product, and the confirmed set of medical necessities. The system dynamically generates confirmations based on DMEPOS standards, and confirms the generated confirmations by electronical signature of the physician, where the confirmation with signature is recorded with a time stamp.

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: 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: Solutions to configure congestion reaction behavior of end devices of a Fibre Channel (FC) fabric, to the extent that any such solutions exist, are inefficient, cumbersome, and unscalable. The present document discloses embodiments of a distributed Congestion Control Service that may use FC services and communication paths to distribute congestion control actions (e.g., during login or at other times such as configuration parameters change). Embodiments also allow for congestion configuration parameters to be provided to end devices in a transport-agnostic way. Furthermore, congestion control actions may be delivered on-demand or at other times, such as after a change.

Abstract: To address concerns with administration of zones in storage area network (SAN) environments, presented are embodiments of a “zone group,” including systems and methods for configuring, implementing, and managing such. While zone group embodiments may comprise one or more zones, unlike traditional zone sets, a zone group includes additional features. For example, a zone group includes an “Owner” and also allows for multiple zone groups to be active on a fabric at one time. By adding the concept of an owner to a zone group, changes made by a user or entity impact the zone group to which the owner has rights to access or modify. Also, by allowing multiple zone groups to be active at the same time, embodiments enable multiple administrators or entities to make unrelated modifications to connectivity and dramatically reduce the impact of unintentional changes. Additional features and benefits are described herein.