Abstract: In various examples, one or more network links for transmitting data in a network may be selected based at least in part on a quality associated with the one or more network links. Link quality information associated with a plurality of links may be accessed and analyzed to determine which links to use for transmitting data. Link quality may be evaluated in combination with other link attributes to proactively select network links to minimize network disruption in the event of network equipment failure.

Abstract: Methods, systems, and devices are provided herein for a mechanism to identify link down reasons. As described herein, a first port of a first peer device may be determined to have unexpectedly changed to a port down state. Subsequently, a topology file may be referenced to identify a second port of a second peer device with which the first peer device is intended to have a link if not for the first port being in a port down state. In some examples, port settings of the first port may be compared with port settings of the second port. If a port setting for the first port mismatches an associated port setting for the second port, an alert message may be transmitted to a network administrator indicating this mismatch as a possible reason for the first port being in the port down state.

Abstract: Embodiments herein facilitate the modification of data traffic load balancing on information handling systems affected by a networking information handling system having the status of one or more of its uplinks changed from operable to inoperable or from inoperable to operable. In one or more embodiments, an agent operating on or in conjunction with a networking information handling system (e.g., a TOR) detects a change in one its links. The agent sends a message to information handling system(s) (e.g., hosts) that are communicatively coupled to the TOR regarding the change in status. Based upon the TOR's message, a host may adjust its traffic load balancing to compensate for the status change. Embodiments, therefore, help efficiently utilize network pathways.

Abstract: Methods, systems, and devices are provided herein for providing a visually guided topology wiring scheme. As described herein, after determining that a first end of a cable has been inserted at a first port of a first peer device, a wiring application may reference a topology file to identify a second port of a second peer device with which the first peer device is intended to have a link. Subsequently, the wiring application may activate an indicator associated with the second port to mimic an indicator associated with the first port. For example, the wiring application may cause both indicators associated with each port to flash according to a same or similar flashing pattern, to produce or illuminate at a similar or identical color (e.g., approximately the same color), to flash at approximately a same rate, or by substantially synchronizing a flashing of each indicator.

Abstract: A network device including a first data structure storing a set of buffer profile types. Each buffer profile type is associated with one or more configuration parameters. The network device further includes a second data structure storing a set of peer device identifiers, wherein each peer device identifier of the set of peer device identifiers is associated with a buffer profile type. The network device includes a buffer management application to receive first data associated with a first peer network device coupled via a first link to an interface component of the network device, determine the first data matches a first peer device identifier stored in the second data structure, and assign a first buffer profile type to the interface component of the network device, wherein the first buffer profile type is associated with the first peer device identifier in the second data structure.

Abstract: Methods, systems, and devices are provided herein for providing a visually guided topology wiring scheme. As described herein, after determining that a first end of a cable has been inserted at a first port of a first peer device, a wiring application may reference a topology file to identify a second port of a second peer device with which the first peer device is intended to have a link. Subsequently, the wiring application may activate an indicator associated with the second port to mimic an indicator associated with the first port. For example, the wiring application may cause both indicators associated with each port to flash according to a same or similar flashing pattern, to produce or illuminate at a similar or identical color (e.g., approximately the same color), to flash at approximately a same rate, or by substantially synchronizing a flashing of each indicator.

Abstract: Methods, systems, and devices are provided herein for a mechanism to identify link down reasons. As described herein, a first port of a first peer device may be determined to have unexpectedly changed to a port down state. Subsequently, a topology file may be referenced to identify a second port of a second peer device with which the first peer device is intended to have a link if not for the first port being in a port down state. In some examples, port settings of the first port may be compared with port settings of the second port. If a port setting for the first port mismatches an associated port setting for the second port, an alert message may be transmitted to a network administrator indicating this mismatch as a possible reason for the first port being in the port down state.

Abstract: A network device including a first data structure storing a set of buffer profile types. Each buffer profile type is associated with one or more configuration parameters. The network device further includes a second data structure storing a set of peer device identifiers, wherein each peer device identifier of the set of peer device identifiers is associated with a buffer profile type. The network device includes a buffer management application to receive first data associated with a first peer network device coupled via a first link to an interface component of the network device, determine the first data matches a first peer device identifier stored in the second data structure, and assign a first buffer profile type to the interface component of the network device, wherein the first buffer profile type is associated with the first peer device identifier in the second data structure.

Abstract: Access control systems and methods herein successfully overcome ACL (access control list) group width limitations of existing designs by splitting an ACL group across different units, e.g., to create two ACL groups that each has a relatively smaller width. In one or more embodiments, availability of ACL space is increased by hierarchically splitting an ACL table to fit into different two networked devices and modifying certain fields carrying metadata in packets that are exchanged between the devices, such that one chipset may carry information about the lookup of another. In one or more embodiments, an ACL group for a port extender is created by selectively creating a sub-group with qualifiers that fit within an available group width, and moving the remaining qualifiers to a controlling bridge to achieve the desired functionality/action.

Abstract: A loop prevention system includes a plurality of networking devices that are coupled together to form a Layer Two (L2) domain and at least a portion of the plurality of networking devices are coupled together in a physical loop configuration. A networking device included in the plurality of networking devices may include at least one L2 domain connection that couples the networking device to at least one of the plurality of networking devices in the L2 domain, and an edge connection that connects the networking device to a computing device that is outside of the L2 domain. The networking device may receive a data frame via the edge connection. The networking device then generates a loop breaker data frame by tagging the data frame with a loop breaker tag and forwards the loop breaker data frame via the at least one L2 domain connection.

Abstract: Access control systems and methods herein successfully overcome ACL group width limitations of existing designs by splitting an ACL group across different units, e.g., to create two ACL groups that each has a relatively smaller width. In embodiments, availability of ACL space is increased by hierarchically splitting an ACL table to fit into different two coupled devices and modifying certain fields carrying metadata in packets that are exchanged between the devices, such that one chipset may carry information about the lookup of another. In embodiments, an ACL group for a port extender is created by selectively creating a sub-group with qualifiers that fit within an available group width, and moving the remaining qualifiers to a controlling bridge to achieve the desired functionality.

Abstract: Methods, systems, and devices are provided herein for a mechanism to identify link down reasons. As described herein, a first port of a first peer device may be determined to have unexpectedly changed to a port down state. Subsequently, a topology file may be referenced to identify a second port of a second peer device with which the first peer device is intended to have a link if not for the first port being in a port down state. In some examples, port settings of the first port may be compared with port settings of the second port. If a port setting for the first port mismatches an associated port setting for the second port, an alert message may be transmitted to a network administrator indicating this mismatch as a possible reason for the first port being in the port down state.

Abstract: A loop prevention system includes a plurality of networking devices that are coupled together to form a Layer Two (L2) domain and at least a portion of the plurality of networking devices are coupled together in a physical loop configuration. A networking device included in the plurality of networking devices may include at least one L2 domain connection that couples the networking device to at least one of the plurality of networking devices in the L2 domain, and an edge connection that connects the networking device to a computing device that is outside of the L2 domain. The networking device may receive a data frame via the edge connection. The networking device then generates a loop breaker data frame by tagging the data frame with a loop breaker tag and forwards the loop breaker data frame via the at least one L2 domain connection.

Abstract: Hash collision in a highly scaled configuration cannot be prevented. However, the impact of the hash collision may be reduced based on a priority. Currently, there are no priorities assigned to virtual ports (VP) in a VXLAN environment. Thus, any VP may be impacted by not being added to a hash table that facilitates network data traffic processing. The probability of not being added to a hash table for network VPs is higher given that they tend to be programmed at a later stage than access VP. With priority-based hash table programming embodiments, hash table programming is better controlled, and the impact to higher priority VPs is reduced.

Abstract: Embodiments herein facilitate the modification of data traffic load balancing on information handling systems affected by a networking information handling system having the status of one or more of its uplinks changed from operable to inoperable or from inoperable to operable. In one or more embodiments, an agent operating on or in conjunction with a networking information handling system (e.g., a TOR) detects a change in one its links. The agent sends a message to information handling system(s) (e.g., hosts) that are communicatively coupled to the TOR regarding the change in status. Based upon the TOR's message, a host may adjust its traffic load balancing to compensate for the status change. Embodiments, therefore, help efficiently utilize network pathways.

Abstract: An optical transceiver monitoring system includes an optical transceiver device that includes a non-volatile memory system, and a computing device that includes a computing device port that is coupled to the optical transceiver device. The computing device monitors the computing device port and, in response, detects one or more interactions between the optical transceiver device and the computing device. The computing device determines that the one or more interactions satisfy an event condition, and in response to the one or more interactions satisfying the event condition, provides first event information that corresponds to the one or more interactions to the optical transceiver device for storage in the non-volatile memory system.

Abstract: A port unavailability remediation system includes a management device and a networking device including a plurality of physical ports. Following the unavailability of a first physical port that is included in the plurality of physical ports and that is linked to a first port identifier, the networking device receives a port identifier link change request from the management device that requests the linking of the first port identifier to a second physical port that is included in the plurality of physical ports and, in response, links the first port identifier to the second physical port. Subsequent to linking the first port identifier to the second physical port, the networking device prevents modification of the second physical port.

Abstract: A multi-port queue group system an Network Processing Unit coupled to ingress port(s) and an egress port group having a first egress port and a second egress port. The NPU includes an egress queue group having a first egress queue associated with the first egress port and a second egress queue associated with the second egress port. The NPU receives data packets that are each directed to the egress port group via the ingress port(s), and buffers a first subset of the data packets in the first egress queue included in the egress queue group, and a second subset of the data packets in the second egress queue included in the egress queue group. The NPU then transmits at least one of the data packets via at least one of the first egress port and the second egress port included in the egress port group.

Abstract: An optical transceiver monitoring system includes an optical transceiver device that includes a non-volatile memory system, and a computing device that includes a computing device port that is coupled to the optical transceiver device. The computing device monitors the computing device port and, in response, detects one or more interactions between the optical transceiver device and the computing device. The computing device determines that the one or more interactions satisfy an event condition, and in response to the one or more interactions satisfying the event condition, provides first event information that corresponds to the one or more interactions to the optical transceiver device for storage in the non-volatile memory system.

Abstract: A link validation system includes a first device and a second device. The first device identifies that a first link to the second device has become available via a first port on the first device, and determines that the first link to the second device is not a valid link. In response to determining that the first link to the second device is not a valid link, the first device configures the first port in an auto-negotiation error state. Subsequent to configuring the first port in the auto-negotiation error state, the first device detects a port connection cycling operation associated with the first port and, in response, clears the auto-negotiation error state for the first port.