H04L49/35

Device-aware dynamic protocol adaptation in a software-defined network

An example consistent with this disclosure includes a controller that is communicatively coupled to dataflow devices in a network. The controller receives device information from a dataflow device and determines features supported by the dataflow device based, in part, on the device information received from the dataflow device. Using a driver configured to use the features supported by the dataflow device, the controller transmits a command to the dataflow device. The controller then receives a response to the command from the dataflow device. The response to the command may include information that indicates different features are supported by the dataflow device than previously determined. The controller updates its determination of the features supported by the dataflow device and updates the driver used to transmit the command to the dataflow device.

Efficient highly connected deployment units

Efficient and highly-scalable network solutions are provided that each utilize deployment units based on Clos networks, but in an environment such as a data center of Internet Protocol-based network. Each of the deployment units can include multiple stages of devices, where connections between devices are only made between stages and the deployment units are highly connected. In some embodiments, the level of connectivity between two stages can be reduced, providing available connections to add edge switches and additional host connections while keeping the same number of between-tier connections. In some embodiments, where deployment units (or other network groups) can be used at different levels to connect other deployment units, the edges of the deployment units can be fused to reduce the number of devices per host connection.

POWER-OVER-ETHERNET (POE) BREAKOUT MODULE

Presented herein are embodiments of a power-over-Ethernet (PoE) breakout system that may be used to breakout a PoE port from a PoE information handling system into a number of breakout ports. In one or more embodiments, a PoE breakout system comprises: a PoE port for connecting to a PoE information handling system, such as a PoE switch; a plurality of breakout ports for connecting to powered devices, wherein each breakout port is configured to supply power to a powered device; and a power management module electrically coupled to the PoE port and configured to supply power to each breakout port according to a configuration that sets a power level for that breakout port. In one or more embodiments. the PoE breakout system comprises a data communications module that switches data traffic to a correct PoE breakout port according to its intended powered device.

IP aliases in logical networks with hardware switches
11196682 · 2021-12-07 · ·

Some embodiments provide a novel method of configuring a managed hardware forwarding element (MHFE) that implements a logical forwarding element (LFE) of a logical network to handle address resolution requests (e.g., Address Resolution Protocol (ARP) requests) for multiple addresses (e.g., IP addresses) associated with a single network interface of the logical network. The method identifies a physical port of the MHFE with which the multiple addresses are to be associated. The physical port is coupled to an end machine (e.g., a virtual machine, server, container, etc.) of the logical network. The method then modifies associations stored at the MHFE to associate the physical port with the multiple addresses.

TECHNOLOGIES FOR SWITCHING NETWORK TRAFFIC IN A DATA CENTER

Technologies for switching network traffic include a network switch. The network switch includes one or more processors and communication circuitry coupled to the one or more processors. The communication circuity is capable of switching network traffic of multiple link layer protocols. Additionally, the network switch includes one or more memory devices storing instructions that, when executed, cause the network switch to receive, with the communication circuitry through an optical connection, network traffic to be forwarded, and determine a link layer protocol of the received network traffic. The instructions additionally cause the network switch to forward the network traffic as a function of the determined link layer protocol. Other embodiments are also described and claimed.

Method and system of a cloud-based multipath routing protocol

In one aspect, a computerized system useful for implementing a cloud-based multipath routing protocol to an Internet endpoint includes an edge device that provides an entry point into an entity's core network. The entity's core network includes a set of resources to be reliably accessed. The computerized system includes a cloud-edge device instantiated in a public-cloud computing platform. The cloud-edge device joins a same virtual routing and forwarding table as the edge device. The cloud-edge device receives a set of sources and destinations of network traffic that are permitted to access the edge device and the set of resources.

Method and system of a cloud-based multipath routing protocol

In one aspect, a computerized system useful for implementing a cloud-based multipath routing protocol to an Internet endpoint includes an edge device that provides an entry point into an entity's core network. The entity's core network includes a set of resources to be reliably accessed. The computerized system includes a cloud-edge device instantiated in a public-cloud computing platform. The cloud-edge device joins a same virtual routing and forwarding table as the edge device. The cloud-edge device receives a set of sources and destinations of network traffic that are permitted to access the edge device and the set of resources.

Runtime schema for services in a switch

One embodiment of the present invention provides a switch. During operation, the switch parses a first schema of the switch. The first schema indicates initialization information for one or more services of the switch expressed based on one or more tags. The switch then identifies a tag of the one or more tags in the first schema based on the parsing and identifies information corresponding to the tag from a profile of the switch. Subsequently, the switch generates a second schema from the first schema based on the identified information.

Runtime schema for services in a switch

One embodiment of the present invention provides a switch. During operation, the switch parses a first schema of the switch. The first schema indicates initialization information for one or more services of the switch expressed based on one or more tags. The switch then identifies a tag of the one or more tags in the first schema based on the parsing and identifies information corresponding to the tag from a profile of the switch. Subsequently, the switch generates a second schema from the first schema based on the identified information.

Switch with network services packet processing by service software instances

Virtual machine environments are provided in the switches that form a network, with the virtual machines executing network services previously performed by dedicated appliances. The virtual machines can be executed on a single multi-core processor in combination with normal switch functions or on dedicated services processor boards. Packet processors analyze incoming packets and add a services tag containing services entries to any packets. Each switch reviews the services tag and performs any network services resident on that switch. This allows services to be deployed at the optimal locations in the network. The network services may be deployed by use of drag and drop operations. A topology view is presented, along with network services that may be deployed. Services may be selected and dragged to a single switch or multiple switches. The management tool deploys the network services software, with virtual machines being instantiated on the switches as needed.