Data center wan aggregation to optimize hybrid cloud connectivity
US-2017063673-A1 · Mar 2, 2017 · US
US11843547B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-11843547-B2 |
| Application number | US-202217839336-A |
| Country | US |
| Kind code | B2 |
| Filing date | Jun 13, 2022 |
| Priority date | Sep 21, 2020 |
| Publication date | Dec 12, 2023 |
| Grant date | Dec 12, 2023 |
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.
Some embodiments provide a method for deploying edge forwarding elements in a public or private software defined datacenter (SDDC). For an entity, the method deploys a default first edge forwarding element to process data message flows between machines of the entity in a first network of the SDDC and machines external to the first network of the SDDC. The method subsequently receives a request to allocate more bandwidth to a first set of the data message flows entering or exiting the first network of the SDDC. In response, the method deploys a second edge forwarding element to process the first set of data message flows of the entity in order to allocate more bandwidth to the first set of the data message flows, while continuing to process a second set of data message flows of the entity through the default first edge node. The method in some embodiments receives the request for more bandwidth by first receiving a request to create a traffic group and then receiving a list of network addresses that are associated with the traffic group. In some embodiments, the method receives the list of network addresses associated with the traffic group by receiving a prefix of network addresses and receiving a request to associate the prefix of network addresses with the traffic group. Based on this request, the method then creates an association between the traffic group and the received prefix of network addresses.
Opening claim text (preview).
We claim: 1. A non-transitory machine readable medium storing a program for deploying edge forwarding elements in a software defined datacenter (SDDC), the program for execution by at least one processing unit, the program comprising sets of instructions for: deploying, for an entity, a default first edge forwarding element to process data message flows between machines in a first network of the SDDC and machines external to the first network of the SDDC; receiving a request to allocate more bandwidth to a first set of the data message flows entering or exiting the first network of the SDDC; and deploying, for the entity, a second edge forwarding element to process the first set of data message flows in order to allocate more bandwidth to the first set of the data message flows, while continuing to process a second set of data message flows through the default first edge forwarding element. 2. The non-transitory machine readable medium of claim 1 , wherein the set of instructions for receiving the request comprises sets of instructions for: receiving a request to create a traffic group; and receiving a list of network addresses associated with traffic group, the list of network addresses identifying the subset of the data message flows to be processed by the second edge forwarding element. 3. The non-transitory machine readable medium of claim 2 , wherein the set of instructions for receiving the list of network addresses associated with the traffic group comprises sets of instructions for: receiving a prefix of network addresses; and receiving a request to associate the prefix of network addresses with the traffic group. 4. The non-transitory machine readable medium of claim 3 , wherein the program further comprises a set of instructions for creating an association between the traffic group and the received prefix of network addresses. 5. The non-transitory machine readable medium of claim 2 , wherein the network addresses are network addresses associated with interfaces for connecting the machines in the first network to forwarding elements of the first network. 6. The non-transitory machine readable medium of claim 1 , wherein the set of instructions for deploying the second edge forwarding element comprises sets of instructions for: configuring the second edge forwarding element to forward data messages of the first set to forwarding elements in the external network; and configuring a set of forwarding elements in the first network to forward data messages of the first set from a set of machines of the first network to the second edge forwarding element. 7. The non-transitory machine readable medium of claim 6 , wherein the edge forwarding elements are edge routers, and the set of instructions for configuring the second edge forwarding element comprises a set of instructions for configuring the second edge forwarding element to advertise to forwarding elements in the external network routes to the set of machines. 8. The non-transitory machine readable medium of claim 6 , wherein the set of forwarding elements comprises a set of intervening routers, and the set of instructions for configuring the set of forwarding elements comprises a set of instructions for providing next-hop forwarding rules to the set of intervening routers. 9. The non-transitory machine readable medium of claim 6 , wherein the set of forwarding elements comprises a set of intervening switches that implement a logical switch, and the set of instructions for configuring the set of forwarding elements comprises a set of instructions for providing forwarding rules to the set of intervening switches to direct the switches to forward data messages of the first set to the second edge forwarding element through a set of tunnels that connect the set of intervening switches to the second edge forwarding element. 10. The non-transitory machine readable medium of claim 6 , wherein the set of instructions for configuring the set of forwarding elements in the first network comprises a set of instructions for configuring the set of forwarding elements to forward to the second edge forwarding element data message flows with (i) destination IP addresses that are associated with second edge forwarding element and (ii) source IP addresses associated with the set of machines. 11. The non-transitory machine readable medium of claim 6 , wherein the program further comprises a set of instructions for configuring a gateway of the SDDC to forward data message flows with destination IP addresses associated with the set of machines to the second edge forwarding element. 12. The non-transitory machine readable medium of claim 1 , wherein the SDDC is a public cloud datacenter having a second network, the first network is a private network that is defined in the second network to implement a virtual private cloud (VPC) for the entity in the public cloud datacenter, and the set of instructions for deploying the second edge forwarding element comprises sets of instructions for: deploying a gateway in the public cloud datacenter; and configuring a set of forwarding elements in the second network to forward the first set of data message flows to the deployed gateway. 13. The non-transitory machine readable medium of claim 1 , wherein the set of instructions for deploying the first and second edge forwarding elements comprises a set of instructions for deploying the first and second edge forwarding elements as different devices in the SDDC. 14. The non-transitory machine readable medium of claim 13 , wherein the different devices are first and second host computers on which the first and second edge forwarding elements execute. 15. The non-transitory machine readable medium of claim 1 , wherein the program further comprises sets of instructions for: receiving a request to allocate more bandwidth to a third set of the data message flows entering or exiting the first network of the SDDC; and deploying, for the entity, a third edge forwarding element to process the third set of data message flows in order to allocate more bandwidth to the third set of the data message flows, while continuing to process the second set of data message flows through the default first edge forwarding element and to process the first set of data message flows through the second edge forwarding element. 16. The non-transitory machine readable medium of claim 15 , wherein the set of instructions for deploying the second and third edge forwarding elements comprises a set of instructions for deploying the second and third edge forwarding elements to execute on different devices in the SDDC. 17. The non-transitory machine readable medium of claim 16 , wherein the different devices are first and second host computers on which the first and third edge forwarding elements execute, said different host computers allowing different physical network interface cards (PNICs) to be used for the first and third sets of data message flows. 18. The non-transitory machine readable medium of claim 16 , wherein the different devices are first and second gateway appliances.
Distributed allocation of resources, e.g. bandwidth brokers · CPC title
Interconnection of networks using encapsulation techniques, e.g. tunneling · CPC title
Arrangements for connecting between networks having differing types of switching systems, e.g. gateways · CPC title
Address processing for routing · CPC title
between local and global IP addresses · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.