Enabling Load Balancing in a Network Virtualization Overlay Architecture
Abstract
A load balancing function is integrated into a Network Virtualization Edge, NVE, function. This load balancing function is configured by a Network Virtualization Authority, NVA, using a new protocol. The can thus enable or disable the LB function for a given VN in a specific NVE. According to one example method, the NVA receives ( 210 ) Virtual Machine, VM, configuration information from a VM orchestration system. Based on this information, the NVA configures ( 220 ) an attached NVE to enable load balancing by sending an enable message to the NVE. The NVA subsequently receives ( 230 ) a confirmation message from the NVE, indicating that the load balancing function is enabled. The NVA then updates ( 240 ) remote NVEs, allowing load balancing traffic to be sent to the first NVE.
Claims
exact text as granted — not AI-modifiedWhat is claimed is:
1 . A method in an Network Virtualization Authority, NVA, node that provides reachability and forwarding information to one or more Network Virtualization Edge, NVE, nodes in a network employing a Network Virtualization Overlay, NVO, wherein each NVE node implements Layer 2 and/or Layer 3 network virtualization functions for one or more tenant system elements, the method comprising:
receiving virtual machine, VM, configuration information for one or more VMs; configuring at least a first NVE to enable load balancing, LB, by sending a LB enable message to the first NVE node; and updating configuration information for one or more remote NVEs to allow load balancing traffic for the one or more VMs to be sent to the first NVE node.
2 . The method of claim 1 , wherein the method further comprises receiving confirmation, from the first NVE node, that a load balancing function is enabled.
3 . The method of claim 1 , further comprising:
determining that LB should be disabled in the first NVE node; sending a LB disable message to the first NVE node; and updating configuration information for one or more remote NVEs to prevent load balancing traffic for the one or more VMs from being sent to the first NVE node.
4 . The method of claim 3 , wherein the method further comprises receiving confirmation, from the first NVE node, that the load balancing function has been disabled.
5 . The method of claim 3 , wherein the method further comprises:
configuring second NVE node to enable load balancing, LB, by sending a LB enable message to the second NVE node; and updating configuration information for one or more remote NVEs to allow load balancing traffic for the one or more VMs to be sent to the second NVE node.
6 . The method of claim 5 , wherein the method further comprises receiving confirmation, from the second NVE node, that a load balancing function is enabled.
7 . A method in a Network Virtualization Edge, NVE, node in a network employing a Network Virtualization Overlay, NVO, where the NVE node implements Layer 2 and/or Layer 3 network virtualization functions for one or more tenant system elements, the method comprising:
receiving a load balancing, LB, enable message from a Network Virtualization Authority, NVA, node that provides reachability and forwarding information to the NVE node; enabling a load balancing function, in response to the LB enable message; and forwarding subsequent load balancing traffic to one or more virtual machines, VMs, using the enabled load balancing function.
8 . The method of claim 7 , further comprising sending a confirmation message to the NVA node, in response to receiving the LB enable message.
9 . The method of claim 7 , further comprising:
receiving a load balancing, LB, disable message from the NVA node; and disabling the load balancing function, in response to the LB disable message.
10 . The method of claim 9 , wherein the method further comprises sending confirmation, to the NVA node, that the load balancing function has been disabled.
11 . The method of claim 7 , wherein forwarding the subsequent load balancing traffic to one or more VMs comprises:
retrieving an LB address from each of one or more incoming packets; determining a virtual network context for each of the one or more incoming packets, using the LB address; obtaining a VM MAC address for each of the one or more incoming packets, based on a load balancing algorithm and the virtual network context; and forwarding the one or more incoming packets according to the obtained VM MAC addresses.
12 . The method of claim 11 , wherein the NVE node supports Layer 3 service and wherein the LB address retrieved from each of the one or more incoming packets is an IP destination address.
13 . The method of claim 11 , wherein the NVE node supports Layer 2 service and wherein the LB address retrieved from each of the one or more incoming packets is a MAC destination address.
14 . (canceled)
15 . (canceled)
16 . (canceled)
17 . (canceled)
18 . (canceled)
19 . A Network Virtualization Authority, NVA, node adapted to provide reachability and forwarding information to one or more Network Virtualization Edge, NVE nodes in a network employing a Network Virtualization Overlay, NVO, wherein each NVE node implements Layer 2 and/or Layer 3 network virtualization functions for one or more tenant system elements, the NVA node comprising a network interface circuit and further comprising a processing circuit adapted to:
receive virtual machine, VM, configuration information for one or more VMs, via the network interface circuit; configure at least a first NVE to enable load balancing, LB, by sending a LB enable message to the first NVE node via the network interface circuit; and update configuration information for one or more remote NVEs to allow load balancing traffic for the one or more VMs to be sent to the first NVE node.
20 . The NVA node of claim 19 , wherein the processing circuit is adapted to carry out the method of any of claims 2 - 6 .
21 . A Network Virtualization Edge, NVE, node adapted for use in a network employing a Network Virtualization Overlay, NVO, and further adapted to implement Layer 2 and/or Layer 3 network virtualization functions for one or more tenant system elements, the NVE node comprising a network interface circuit and further comprising a processing circuit adapted to:
receive, via the network interface circuit, a load balancing LB enable message from a Network Virtualization Authority, NVA, node that provides reachability and forwarding information to the NVE node; enable a load balancing function, in response to the LB enable message; and forward subsequent load balancing traffic to one or more virtual machines, VMs, using the enabled load balancing function.
22 . The NVE node of claim 21 , wherein the processing circuit is adapted to carry out the method of any of claims 8 - 13 and claims 29 - 33 .
23 . (canceled)
24 . (canceled)
25 . (canceled)
26 . (canceled)
27 . (canceled)
28 . (canceled)
29 . The method of claim 7 , wherein the LB enable message comprises a Virtual Network (VN) identifier for a VN to which the load balancing traffic belongs.
30 . The method of claim 7 , wherein the LB enable message comprises one or more QoS requirements, one or more security policies, or one or more of both.
31 . The method of claim 7 , wherein the LB enable message comprises an LB address to be used as a destination address for any incoming traffic to which load balancing shall be applied.
32 . The method of claim 7 , wherein the LB enable message comprises one or more addresses for VMs to which load balancing traffic should be forwarded.
33 . The method of claim 7 , wherein the LB enable message identifies a load balancing algorithm to be applied to load balancing traffic.Join the waitlist — get patent alerts
Track US2016285769A1 — get alerts on status changes and closely related new filings.
We store only your email — no account needed. See our privacy policy.