Abstract: Control plane policing (CoPP) is a mechanism to police incoming traffic to the control plane for control plane protection and routing stability. Currently, networking switches are statically configured for CoPP limits in hardware/firmware. Such an approach of using a static CoPP limit does not work well in dynamic scenarios where one protocol load could be more than the other. The present patent document discloses embodiments of dynamic CoPP limit derivation. CoPP limits are initially estimated based on protocol configuration and are dynamically updated based on application load. A congestion notification may be sent to a sender to limit a transmission rate. Use of dynamic CoPP limit embodiments have advantages of faster protocol convergence, efficient slow packet processing notification to peer, and effective CoPP drop setting based on application load.

Abstract: Described herein are methods and a system for placing a network and devices in life support when it is determined that a network event necessitates such. Interconnected devices on the network are monitored, devices providing status such as temperature. Based on status, a life support event is determined. If it is determined that life support is needed, devices and services are prioritized. Monitoring is performed as to changes in the network and devices. The network and devices are returned to normal operation if the monitoring determines a normal status.

Abstract: An apparatus comprises at least one processing device configured to determine whether an information technology asset in an information technology infrastructure environment is equipped with a cellular modem and, responsive to determining that the information technology asset is equipped with the cellular modem, to determine whether a cellular operational profile for a cellular-based management network associated with the information technology infrastructure environment is provisioned for the cellular modem. The processing device is also configured, responsive to determining that the cellular operational profile is provisioned, to establish a connection with the cellular-based management network.

Abstract: The technology described herein is directed towards intelligently controlling the power consumed by light emitting diodes (LEDs) of network devices, such as present in a datacenter. An internal device agent, application and/or centralized monitoring system can determine when to activate and deactivate LEDs, such as to activate when a group of devices is likely being observed, and deactivate otherwise. Devices can be grouped for collective control, such as a group per rack of network devices with their LEDs activated and deactivated together. Sensors, such as rack cabinet door sensors, motion sensors and so on can be used to detect whether a group of devices is likely being observed; an action such as closing the door or walking away can be sensed to deactivate the LEDs. After LED activation, expiration of a configurable timer can be used to deactivate the LEDs. Significant power savings are thus achievable in various network scenarios.

Abstract: A Layer 2 (L2) domain hierarchical address communication system includes a first computing device that provides a first host, and a second computing device that provides a second host. A first leaf switch device is connected to the first computing device, and a second leaf switch device that is connected to the second computing device and coupled to the first leaf switch device. The first leaf switch device receives a first data communication from the first host that includes a second hierarchical MAC address of the second host. The first leaf switch device identifies a hierarchical MAC prefix in the second hierarchical MAC address, and uses the hierarchical MAC prefix to forward the first data communication to the second leaf switch device.

Abstract: A networking device credential information reset system includes credential information reset authorization devices coupled to a networking device. At least one of the credential information reset authorization devices receives a networking device credential information reset request from the networking device and, in response, generates a networking device credential information reset alert and provides it for display on an administrator device. Following the networking device credential information reset alert being provided for display on the administrator device, a first credential information reset authorization device receives first credential information for the first credential information reset authorization device from the administrator device, validates the first credential information and, in response, provides a credential information reset authorization to the networking device that is configured to cause the networking device to reset second credential information for the networking device.

Abstract: A Data Processing Unit (DPU) control/management offload system includes a first networking device that is coupled to a DPU. The first networking device identifies the DPU, and generates a first virtual networking device in the first networking device for the DPU. The first networking device then offloads control protocol(s) and/or management operation(s) from the DPU using the first virtual networking device, which may include receiving a control communication that is directed to the DPU, determining that the control communication utilizes the control protocol(s) and, in response, redirecting the control communication to the first virtual networking device and processing the control communication using the first virtual networking device.

Abstract: Described herein are methods and a system for placing a network and devices in life support when it is determined that a network event necessitates such. Interconnected devices on the network are monitored, devices providing status such as temperature. Based on status, a life support event is determined. If it is determined that life support is needed, devices and services are prioritized. Monitoring is performed as to changes in the network and devices. The network and devices are returned to normal operation if the monitoring determines a normal status.

Abstract: Current data center deployments, particularly layer 2 (L2) deployments that use multi-chassis link aggregation group (MC-LAG) implementations, have limitations. Such deployments use a link, known as an inter-node link (INL)/inter-chassis link (ICL), to connect peer information handling system nodes. Because the peer nodes are coupled together via one or more INL connections, there are fewer ports available for each peer node to connect to end nodes. This configuration creates limitations to bandwidth and scaling, and also increase costs. Embodiments herein allow for the elimination of INLs by moving forwarding decisions to the spine node level. In one or more embodiments, a spine node determines ports to reach dual-homed, single-homed, and orphaned node that are connected to leaf node(s) based on information learned from the leaf nodes. For a leaf node, a sub-LAG (link aggregation group) may be created to reach single-homed/orphaned nodes connected to the leaf node.

Abstract: The technology described herein is directed towards intelligently controlling the power consumed by light emitting diodes (LEDs) of network devices, such as present in a datacenter. An internal device agent, application and/or centralized monitoring system can determine when to activate and deactivate LEDs, such as to activate when a group of devices is likely being observed, and deactivate otherwise. Devices can be grouped for collective control, such as a group per rack of network devices with their LEDs activated and deactivated together. Sensors, such as rack cabinet door sensors, motion sensors and so on can be used to detect whether a group of devices is likely being observed; an action such as closing the door or walking away can be sensed to deactivate the LEDs. After LED activation, expiration of a configurable timer can be used to deactivate the LEDs. Significant power savings are thus achievable in various network scenarios.

Abstract: A Layer 2 (L2) domain hierarchical address communication system includes a first computing device that provides a first host, and a second computing device that provides a second host. A first leaf switch device is connected to the first computing device, and a second leaf switch device that is connected to the second computing device and coupled to the first leaf switch device. The first leaf switch device receives a first data communication from the first host that includes a second hierarchical MAC address of the second host. The first leaf switch device identifies a hierarchical MAC prefix in the second hierarchical MAC address, and uses the hierarchical MAC prefix to forward the first data communication to the second leaf switch device.

Abstract: When an event occurs in the network that affects an information handling system in the network, a topology change notice (TCN) may be propagated so that the network topology can be regenerated. However, currently, there is no mechanism to readily identify the source information handling system of the TCN. To address issues, in one or more embodiments, when an information handling system (such as a network switch) initiates a TCN, it sends a specialized message to keep track of the source of the TCN. In one or more embodiments, information handling systems that receive the specialized message may record information about the source and forward it to other information handling system in the network.

Abstract: Systems and methods communicate to a primary peer node a message that indicates that a secondary peer node does not comprise an orphan port or a link that is operationally down. In various embodiments, this causes the primary node to not send broadcast, unknown unicast, or multicast (BUM) traffic to the secondary peer node such as to prevent that traffic from being unnecessarily dropped at the peer node, thus, conserving computing resources, such as an internode link bandwidth, and significantly improving overall network performance.

Abstract: A networking device credential information reset system includes credential information reset authorization devices coupled to a networking device. At least one of the credential information reset authorization devices receives a networking device credential information reset request from the networking device and, in response, generates a networking device credential information reset alert and provides it for display on an administrator device. Following the networking device credential information reset alert being provided for display on the administrator device, a first credential information reset authorization device receives first credential information for the first credential information reset authorization device from the administrator device, validates the first credential information and, in response, provides a credential information reset authorization to the networking device that is configured to cause the networking device to reset second credential information for the networking device.

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: Methods, systems, and devices for providing computer implemented services using managed systems are disclosed. To provide the computer implemented services, the managed systems and/or communication devices may need to operate in a predetermined manner conducive to, for example, execution of applications that provide the computer implemented services. To manage communications in such systems, a highly available service may, upon changes in topology of a deployment including managed system and communication devices, initiate a cooperative process for determining how to communicate in the deployment. The process may be performed to select a new global maximum transmission unit (MTU). Once selected, the deployment may be reconfigured based on the selected global MTU to limit the size of network data units. The global MTU may be selected to limit network data unit fragmentation, network data unit dropping, and unused space in data transmissions.

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: A system and method of managing virtual local area network (VLAN) associations with network ports includes receiving a first packet on a first port of a network switching device, extracting first VLAN identification information from the first packet, determining one or more first VLANs associated with the first port based on the first VLAN identification information, associating the first port with each of the one or more the first VLANs, and transmitting a second packet on the first port when a second VLAN associated with the second packet is included in the one or more first VLANs. In some embodiments, the first packet is received from an end station. In some embodiments, the first packet includes a VLAN identification field selected from a group consisting of a VLAN list field, a VLAN bitmap field, a Port VLAN ID type-length-value (TLV), and a Port Protocol VLAN ID TLV.

Abstract: A system and method of configuration of link aggregation groups includes a control unit and a port coupled to the control unit and configured to couple the network switching device to a neighboring switch. The control unit is configured to transmit a probe message to the neighboring switch, receive a remote switch identifier and link aggregation group (LAG) identifier from the neighboring switch, determine whether the remote switch identifier matches a previously received remote switch identifier and the remote LAG identifier matches a previously received remote LAG identifier. When both match, determine a first LAG associated with the previously received remote switch identifier and the previously received remote LAG identifier and assign the port to the first LAG. When both do not match, to create a second LAG, assign the port to the second LAG, and associate the remote switch identifier and the remote LAG identifier with the second LAG.

Abstract: A system and method of automated Data Center Bridging (DCB) configuration of an access switch includes a control unit, a memory, and a port configured to couple the access switch to a peer device. The control unit is configured to operate the port according to a state machine including a DCB disabled state, a DCB downstream state, and a DCB upstream state. When the port is in the DCB disabled state, the control unit exchanges network traffic on the port without any DCB extensions. When the port is in the DCB upstream state, the control unit exchanges network traffic on the port using DCB extensions based on the DCB configuration and receives the DCB configuration from the peer device. When the port is in the DCB downstream state, the control unit exchanges network traffic on the port using the DCB extensions and transmits the DCB configuration to the peer device.