Method and system of connecting to a multipath hub in a cluster
In one aspect, a computerized method useful for connecting to a multipath hub in a cluster includes the step of, with a gateway in a same network as the cluster, receiving, from a branch edge, a request to connect to a logical identifier (ID) of the multipath hub. The gateway recognizes a logical ID representing a cluster. The gateway determines a least-loaded edge in the cluster to be the multipath hub. The gateway returns a connectivity information for the multipath hub. The branch edge configures a tunnel to the multipath hub.
1. A method for forwarding traffic from a first edge device at a first branch office to a second edge device at a second branch office, the method comprising:
at the first edge device of the first branch office:
sending a connection request to connect to a hub in a hub cluster of a datacenter;
receiving selection of a particular hub from the cluster along with a set of connectivity data for the first edge device to use to establish tunnel connectivity to the particular hub;
forwarding traffic from the first branch office to a second branch office through the particular hub.
2. The method of claim 1 , wherein the connection request is sent to, and the selection of the particular hub is received from, a gateway.
3. The method of claim 2 , wherein the particular hub is selected based on an assessment of load on the hubs in the hub cluster.
4. The method of claim 3 , wherein the gateway receives statistics from the datacenter regarding usage of each hub in the hub cluster.
5. The method of claim 4 , wherein the statistics comprise at least one of a tunnel usage count percentage, a processor usage percentage, and a memory usage percentage.
6. The method of claim 3 , wherein the datacenter is an enterprise datacenter.
7. The method of claim 1 , wherein sending the connection request comprises sending the request with a logical identifier (ID) associated with the hub cluster.
8. The method of claim 1 further comprising after using the particular hub to forward traffic from the first branch office to the second branch office, receiving connectivity information from the gateway to establish a tunnel between the first and second edge devices.
9. The method of claim 8 further comprising:
using the received connectivity information to establish the tunnel between the first and second edge devices;
using the tunnel to forward directly traffic from the first edge device to the second edge device without traversing the particular hub.
10. The method of claim 1 , wherein the particular hub is a first hub of the hub cluster, the second edge device connects to a second hub of the hub cluster, and the datacenter comprises a switch that forwards traffic sent from the first edge device through the first hub to the second hub to forward to the second edge device.
11. A non-transitory machine readable medium storing a program which when executed by at least one processing unit forwards traffic from a first edge device at a first branch office to a second edge device at a second branch office, the program comprising sets of instructions for:
at the first edge device of the first branch office:
sending a connection request to connect to a hub in a hub cluster of a datacenter;
receiving selection of a particular hub from the cluster along with a set of connectivity data for the first edge device to use to establish tunnel connectivity to the particular hub;
forwarding traffic from the first branch office to a second branch office through the particular hub.
12. The non-transitory machine readable medium of claim 11 , wherein the connection request is sent to, and the selection of the particular hub is received from, a gateway.
13. The non-transitory machine readable medium of claim 12 , wherein the particular hub is selected based on an assessment of load on the hubs in the hub cluster.
14. The non-transitory machine readable medium of claim 13 , wherein the gateway receives statistics from the datacenter regarding usage of each hub in the hub cluster.
15. The non-transitory machine readable medium of claim 14 , wherein the statistics comprise at least one of a tunnel usage count percentage, a processor usage percentage, and a memory usage percentage.
16. The non-transitory machine readable medium of claim 13 , wherein the datacenter is an enterprise datacenter.
17. The non-transitory machine readable medium of claim 11 , wherein the set of instructions for sending the connection request comprises a set of instructions for sending the request with a logical identifier (ID) associated with the hub cluster.
18. The non-transitory machine readable medium of claim 11 , wherein the program further comprises a set of instructions for receiving, after using the particular hub to forward traffic from the first branch office to the second branch office, connectivity information from the gateway to establish a tunnel between the first and second edge devices.
19. The non-transitory machine readable medium of claim 18 , wherein the program further comprises sets of instructions for:
using the received connectivity information to establish the tunnel between the first and second edge devices;
using the tunnel to forward directly traffic from the first edge device to the second edge device without traversing the particular hub.
20. The non-transitory machine readable medium of claim 11 , wherein the particular hub is a first hub of the hub cluster, the second edge device connects to a second hub of the hub cluster, and the datacenter comprises a switch that forwards traffic sent from the first edge device through the first hub to the second hub to forward to the second edge device.