Dell Products Inc.

Nvidia Corporation

Sudharsan Dhamal Gopalarathnam

Vamshidhar Varre

Senthil Kumar Ganesan

Karthik Krishnamurthy

Vinoth Kumar Arumugam

Anbalagan Natchimuthu

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.

Prioritized hash table

Approaches in accordance with various illustrative embodiments provide for the management of active connections in a network environment. In particular, various embodiments implement keep alive functionality in components such as network processing units (NPUs) of network devices such as routers and switches, instead of host processors for those devices. When a status message is received, such as a hello message, the NPU can set or refresh a hit bit in a table entry for a given connection with a peer device. If a subsequent status message is not received within a keep alive interval of the last received status message, then the NPU can determine that the connection with the peer device is stale and can inform the host processor that the connection is no longer available for routing network traffic. The status messages are terminated in the NPU and prevented from being received and processed by the host processor.

Offloading connection management for network resources

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.

Mechanism to identify link down reasons

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.

Uplink failure rebalancing

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.

Visually guided topology wiring

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.

Buffer profile assignment management based on peer network device data

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.

Loop prevention system

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.

Optical transceiver monitoring system

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.

Growing community of inventors

Bothell, WA, United States of America

Sudharsan Dhamal Gopalarathnam