Abstract:
Systems and methods are provided for a multicast based solution to solving the slow-start problem that ensures both optimal (1-hop) and in-sequence delivery of packets to the destination. Packets are hardware switched thereby completely eliminating the slow software switching path.
Abstract:
Systems and methods are provided for a multicast based solution to solving the slow-start problem that ensures both optimal (1-hop) and in-sequence delivery of packets to the destination. Packets are hardware switched thereby completely eliminating the slow software switching path.
Abstract:
Systems and methods are provided for a multicast based solution to solving the slow-start problem that ensures both optimal (1-hop) and in-sequence delivery of packets to the destination. Packets are hardware switched thereby completely eliminating the slow software switching path.
Abstract:
Techniques are provided for updating routing tables of switch devices. At a first switch device of a first rack unit in a network, information is received about addresses of host devices in the network. The addresses are stored in a software cache. A packet is received from a first host device assigned to a first subnet and housed in the first rack unit. The packet is destined for a second host device assigned to a second subnet and housed in a second rack unit in the network. The packet is forwarded using the subnet entry and it may remain sub-optimal during a period before which an entry can be installed form a software cache. The software cache is evaluated to determine the address of the second host device. The packet is then forwarded optimally. This will ensure any-to-any communications in the network initially sub-optimally and subsequently optimally.
Abstract:
A user application may provide a hint which may be used by a compute device to select a tag to be inserted into the packets generated by the user application. Upon some event, the application transmits a hint associated with a network flow generated by the user application to a stack associated with the computing device. One of the layers of the stack—e.g., the operating system in the computing device—may include a hint database that contains rules for selecting tags using a received hint as input. The layer may then insert the tag into one or more packets of the network flow. When processing the packet, network devices in the SDN enabled network recognize the tag and perform an action corresponding to the tag.
Abstract:
A multi-protocol software-defined networking (SDN) controller receives receiving from one or more applications one or more requests for services to be performed by one or more of a plurality of network devices that communicate with the SDN controller by a plurality of different of SDN protocols. The requests are mapped to appropriate ones of the plurality of different SDN protocols to fulfill the services of the requests. The SDN controller sends to the respective one or more of the plurality of network devices, control messages according to appropriate ones of the plurality of different SDN protocols. Responses are received at the SDN controller from the one or more of the plurality of network devices, each response indicating a failure or a success for a corresponding request. Failures and successes of the responses are associated with appropriate ones of the requests.
Abstract:
Systems and methods are provided for a multicast based solution to solving the slow-start problem that ensures both optimal (1-hop) and in-sequence delivery of packets to the destination. Packets are hardware switched thereby completely eliminating the slow software switching path.
Abstract:
A Service Abstraction Layer (SAL) provides network level abstraction enabling applications to interface via multiple software-defined networking (SDN) protocols with network devices in a heterogeneous network (devices in the network support a variety of SDN protocols) and in an opaque fashion in order to fulfill desired services by one or more of the protocols. Abstraction is not limited or mapped to any particular protocol. Protocols can change and applications can vary. Support for new protocols can be added later as plug-ins.
Abstract:
A user application may provide a hint which may be used by a compute device to select a tag to be inserted into the packets generated by the user application. Upon some event, the application transmits a hint associated with a network flow generated by the user application to a stack associated with the computing device. One of the layers of the stack—e.g., the operating system in the computing device—may include a hint database that contains rules for selecting tags using a received hint as input. The layer may then insert the tag into one or more packets of the network flow. When processing the packet, network devices in the SDN enabled network recognize the tag and perform an action corresponding to the tag.
Abstract:
Techniques are provided for updating routing tables of switch devices. At a first switch device of a first rack unit in a network, information is received about addresses of host devices in the network. The addresses are stored in a software cache. A packet is received from a first host device assigned to a first subnet and housed in the first rack unit. The packet is destined for a second host device assigned to a second subnet and housed in a second rack unit in the network. The packet is forwarded using the subnet entry and it may remain sub-optimal during a period before which an entry can be installed form a software cache. The software cache is evaluated to determine the address of the second host device. The packet is then forwarded optimally. This will ensure any-to-any communications in the network initially sub-optimally and subsequently optimally.