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: Data Center Bridge (DCB)-based path selection methods and systems reduce packet loss in a network system comprising a Link Aggregation Group (LAG) topology. In embodiments, once traffic received at a LAG node and identified as DCB traffic, links whose DCB status are identified as “up” are assigned to a LAG sub-trunk that may be used to forward the DCB traffic on the LAG trunk, while non-DCB traffic is forwarded to any member of the LAG, irrespective of DCB status. In addition, DCB traffic received from a LAG peer node, which sends traffic on an inter-node link (INL) when no DCB-enabled links to a downstream device are present, is identified as DCB traffic and forwarded on a LAG sub-trunk that comprises DCB-enabled links. An egress mask that indicates to not forward the traffic received at the LAG node on the INL may be overridden, such that DCB traffic may be forwarded.

Abstract: Data Center Bridge (DCB)-based path selection methods and systems reduce packet loss in a network system comprising a Link Aggregation Group (LAG) topology. In embodiments, once traffic received at a LAG node and identified as DCB traffic, links whose DCB status are identified as “up” are assigned to a LAG sub-trunk that may be used to forward the DCB traffic on the LAG trunk, while non-DCB traffic is forwarded to any member of the LAG, irrespective of DCB status. In addition, DCB traffic received from a LAG peer node, which sends traffic on an inter-node link (INL) when no DCB-enabled links to a downstream device are present, is identified as DCB traffic and forwarded on a LAG sub-trunk that comprises DCB-enabled links. An egress mask that indicates to not forward the traffic received at the LAG node on the INL may be overridden, such that DCB traffic may be forwarded.

Abstract: Data Center Bridge (DCB)-based path selection methods and systems reduce packet loss in a network system comprising a Link Aggregation Group (LAG) topology. In embodiments, once traffic received at a LAG node and identified as DCB traffic, links whose DCB status are identified as “up” are assigned to a LAG sub-trunk that may be used to forward the DCB traffic on the LAG trunk, while non-DCB traffic is forwarded to any member of the LAG, irrespective of DCB status. In addition, DCB traffic received from a LAG peer node, which sends traffic on an inter-node link (INL) when no DCB-enabled links to a downstream device are present, is identified as DCB traffic and forwarded on a LAG sub-trunk that comprises DCB-enabled links. An egress mask that indicates to not forward the traffic received at the LAG node on the INL may be overridden, such that DCB traffic may be forwarded.

Abstract: Data Center Bridge (DCB)-based path selection methods and systems reduce packet loss in a network system comprising a Link Aggregation Group (LAG) topology. In embodiments, once traffic received at a LAG node and identified as DCB traffic, links whose DCB status are identified as “up” are assigned to a LAG sub-trunk that may be used to forward the DCB traffic on the LAG trunk, while non-DCB traffic is forwarded to any member of the LAG, irrespective of DCB status. In addition, DCB traffic received from a LAG peer node, which sends traffic on an inter-node link (INL) when no DCB-enabled links to a downstream device are present, is identified as DCB traffic and forwarded on a LAG sub-trunk that comprises DCB-enabled links. An egress mask that indicates to not forward the traffic received at the LAG node on the INL may be overridden, such that DCB traffic may be forwarded.

Abstract: A link aggregated FCoE system includes a target device, a first FCF device coupled to the target device and a LAG, and a second FCF device coupled to the LAG and to the first FCF device by an ICL. The first and second FCF devices are each associated with a common FCF MAC address. The first FCF device receives, through the LAG, first FCoE data traffic directed to the common FCF MAC address and including a target device destination identifier and, in response, forwards the first FCoE data traffic to the target. The second FCF device receives, through the LAG, second FCoE data traffic directed to the common FCF MAC address and including the target device destination identifier and, in response, forwards the second FCoE data traffic to the first FCF device so that the first FCF device may forward the second FCoE data traffic to the target device.

Abstract: A registered state change notification system includes a switch device that is coupled to a plurality of end devices to provide a fabric. An application executing on the switch device detects a change that is associated with a zone in the fabric that includes a plurality of end devices and, in response, generates a multicast Registered State Change Notification (RSCN) that includes a Zone Fiber Channel Identifier (FCID) that is associated with the zone. Subsequently and without the use of the application, multicast hardware included in the switch device sends the multicast RSCN including the Zone FCID to at least a subset of the plurality of end devices.

Abstract: A registered state change notification system includes a switch device that is coupled to a plurality of end devices to provide a fabric. An application executing on the switch device detects a change that is associated with a zone in the fabric that includes a plurality of end devices and, in response, generates a multicast Registered State Change Notification (RSCN) that includes a Zone Fibre Channel Identifier (FCID) that is associated with the zone. Subsequently and without the use of the application, multicast hardware included in the switch device sends the multicast RSCN including the Zone FCID to at least a subset of the plurality of end devices.

Abstract: Embodiments for connecting a host device to target devices in a network through a switch of a plurality of switches, by: defining a special zone for targets that are not directly connected to the switch having the host; directly through the switch; discovering all targets connected to all ports of switch and other switches through a device discovery process; creating a switch-to-target mapping table for all discovered targets; sending a virtual discovery command to all the discovered host-target pairs using the switch-to-target mapping table; creating a virtual address translation table that maps an ID and address of the host to virtual IDs and addresses assigned for network ports of each host-target pairs; and transmitting network traffic between the host and target using the virtual address translation table.

Abstract: Embodiments for connecting a host device to target devices in a network through a switch of a plurality of switches, by: defining a special zone for targets that are not directly connected to the switch having the host; directly through the switch; discovering all targets connected to all ports of switch and other switches through a device discovery process; creating a switch-to-target mapping table for all discovered targets; sending a virtual discovery command to all the discovered host-target pairs using the switch-to-target mapping table; creating a virtual address translation table that maps an ID and address of the host to virtual IDs and addresses assigned for network ports of each host-target pairs; and transmitting network traffic between the host and target using the virtual address translation table.

Abstract: A link aggregated FCoE system includes a target device, a first FCF device coupled to the target device and a LAG, and a second FCF device coupled to the LAG and to the first FCF device by an ICL. The first and second FCF devices are each associated with a common FCF MAC address. The first FCF device receives, through the LAG, first FCoE data traffic directed to the common FCF MAC address and including a target device destination identifier and, in response, forwards the first FCoE data traffic to the target. The second FCF device receives, through the LAG, second FCoE data traffic directed to the common FCF MAC address and including the target device destination identifier and, in response, forwards the second FCoE data traffic to the first FCF device so that the first FCF device may forward the second FCoE data traffic to the target device.