Method and system for load balancing in a software-defined networking (sdn) system upon server reconfiguration
US-2016182378-A1 · Jun 23, 2016 · US
US9634940B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-9634940-B2 |
| Application number | US-201514662259-A |
| Country | US |
| Kind code | B2 |
| Filing date | Mar 19, 2015 |
| Priority date | Jan 31, 2013 |
| Publication date | Apr 25, 2017 |
| Grant date | Apr 25, 2017 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
A method includes receiving in a network switch of a communication network communication traffic that originates from a source node and arrives over a route through the communication network traversing one or more preceding network switches, for forwarding to a destination node. In response to detecting in the network switch a compromised ability to forward the communication traffic to the destination node, a notification is sent to the preceding network switches. The notification is to be consumed by the preceding network switches and requests the preceding network switches to modify the route so as not to traverse the network switch.
Opening claim text (preview).
The invention claimed is: 1. A method, comprising: in a network switch of a communication network, receiving communication traffic that originates from a source node and arrives over a route through the communication network traversing one or more preceding network switches, for forwarding to a destination node; in response to detecting in the network switch a compromised ability to forward the communication traffic to the destination node, sending to the preceding network switches a notification, which is to be consumed by the preceding network switches and requests the preceding network switches to modify the route so as not to traverse the network switch, receiving the notification in a preceding network switch, evaluating in the preceding network switch a rule which checks whether the preceding network switch is in a position to modify the route, modifying the route between the preceding network switch and the destination node in response to the notification if the rule is met and when the rule is not met, forwarding the notification to another of the preceding switches, wherein detecting the compromised ability comprises identifying the compromised ability with respect to an originating packet, and wherein forwarding the notification comprises extracting from the notification a flow identifier of the originating packet, caching the extracted flow identifier of the originating packet, forwarding the notification in response to receiving a subsequent packet that is destined to the cached flow identifier of the originating packet, and removing the cached flow identifier after forwarding the notification in response to N subsequent packets arriving over N different ports, N≧1. 2. The method according to claim 1 , wherein detecting the compromised ability comprises detecting one of a congestion on a network link leaving the network switch en-route to the destination node, a failure in the network link, and a head-of-line time-out at an input to the network link. 3. The method according to claim 1 , wherein sending the notification comprises forwarding the notification in accordance with a forwarding rule that depends on a topology of the communication network. 4. The method according to claim 1 , wherein detecting the compromised ability comprises identifying the compromised ability with respect to an originating packet, and wherein sending the notification comprises specifying a flow identifier of the originating packet in the notification. 5. The method according to claim 4 , wherein sending the notification comprises generating a signature that depends on the originating packet and indicates which of the preceding switches is to consume the notification, and sending the signature in the notification. 6. The method according to claim 4 , wherein specifying the flow identifier of the originating packet comprises one of: reporting the flow identifier of the originating packet in a payload field of the notification; and substituting a destination address of the originating packet to serve as a source address of the notification. 7. The method according to claim 1 , wherein sending the notification comprises indicating a cause of the compromised ability in the notification. 8. The method according to claim 1 , wherein evaluating the rule ensures that, per packet flow, only one of the preceding network switches modifies the route. 9. The method according to claim 8 , wherein evaluating the rule comprises assessing the rule with respect to a signature that is provided in the notification. 10. The method according to claim 8 , wherein the rule depends on a topology of the communication network. 11. The method according to claim 8 , wherein the communication network has a Fat-Tree (FT) topology, and wherein evaluating the rule comprises comparing a level of the preceding network switch in the FT topology to the level of the network switch that sent the notification. 12. The method according to claim 1 , wherein forwarding the notification comprises sending the notification using multicast. 13. The method according to claim 1 , wherein receiving the notification comprises extracting from the notification a flow identifier of an originating packet that caused the notification, and wherein modifying the route comprises re-routing all the packets addressed to the extracted flow identifier regardless of whether they are configured for adaptive routing. 14. The method according to claim 1 , wherein sending the notification comprises routing the notification over an alternative route that differs from the route traversed by the communication traffic that caused the notification. 15. The method according to claim 1 , wherein sending the notification comprises including in the notification a signature for checking by the preceding switches. 16. The method according to claim 1 , wherein sending the notification comprises preempting processing of another packet in order to give precedence to the notification. 17. The method according to claim 1 , and comprising, as the communication traffic traverses the preceding network switches, inserting into the communication traffic one or more identities of one or more of the preceding switches that are capable of modifying the route. 18. The method according to claim 17 , wherein sending the notification comprises addressing the notification to one or more of the preceding network switches whose identities are inserted into the communication traffic. 19. A network switch, comprising: multiple ports, which are configured to communicate with a communication network; and switching circuitry, which is configured to receive communication traffic that originates from a source node and arrives over a route through the communication network, to forward the traffic to a destination node via a downstream network switch, to receive from the downstream network switch a notification that indicates a compromised ability of the downstream network switch to forward the communication traffic to the destination node, and, in response to the notification, to evaluate a rule, which checks whether the network switch is in a position to modify the route, and to modify the route when the rule is met, so as not to traverse the downstream network switch, and to forward the notification to another of the preceding switches when the rule is not met, wherein the switching circuitry is configured to extract from the notification a flow identifier of an originating packet that caused the notification, to cache the extracted flow identifier of the originating packet, and to forward the notification in response to receiving a subsequent packet that is destined to the cached flow identifier of the originating packet, wherein the switching circuitry is configured to remove the cached flow identifier after forwarding the notification in response to N subsequent packets arriving over N different ports, N≧1. 20. The switch according to claim 19 , wherein the compromised ability is caused by one of a congestion on a network link leaving the downstream network switch en-route to the destination node, a failure in the network link, and a head-of-line time-out at an input to the network link. 21. The switch according to claim 19 , wherein the rule ensures that only one of multiple preceding network switches between the source node and the downstream network switch will modify the route. 22. The switch according to claim 21 , wherein the switching circuitry is configured to evaluate the rule wit
by diverting traffic away from congested entities · CPC title
using route fault recovery · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.