IP Library Granted Patent US 11,258,713
Granted Patent B2
US 11,258,713 · App. 16/886,540 · Granted Feb 22, 2022

Policy-based proximity routing

Inventors: Hongwei Zhu (Mountain View, CA); Dileep Devireddy (San Jose, CA); Ganesan Chandrashekhar (Campbell, CA); Feng Gu (Mountain View, CA); Sreenivas Duvvuri (San Ramon, CA); Chidambareswaran Raman (Sunnyvale, CA); Nithin Bangalore Raju (Santa Clara, CA)
Assignee: VMWARE, INC.
H04L47/20H04L45/021H04L45/44H04L45/54H04L45/74H04L61/6022H04L63/0236H04L63/18H04L63/20H04L67/1008H04L67/148
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 11,258,713
App. No.
16/886,540
Granted
Feb 22, 2022
Kind
B2
Abstract

In some embodiments, a first network device in a first site sets a first IP address for an interface of the first network device to a value of a second IP address of a second network device in a second site. Policies are added in a policy table to cover IP addresses used in the second site and a specific route for a third IP address associated with a first workload migrated from the second site to the first site is added into a routing table. The first workload is on a stretched network that is coupled via a layer 2 channel. The policy table configures the first network device to send a second packet from the first workload to a third workload in the second site via the layer 2 channel when an IP address for the third workload does not match an eligible route in the routing table.

Claims (59)

1. A method comprising:

setting, by a first network device in a first site, a first Internet Protocol (IP) address for an interface of the first network device to a value of a second IP address of a second network device in a second site;

adding a set of policies in a policy table to cover a set of IP addresses used in the second site;

adding a specific route into a routing table for the first network device for a third IP address associated with a first workload when it is detected that the first workload is migrated from the second site to the first site, wherein the first workload is on a stretched network between the first site and the second site that is coupled via a layer 2 channel, wherein:

the specific route in the routing table configures the first network device to send a first packet from a second workload local to the first site to the first workload without sending the first packet to the second site, and

the policy table configures the first network device to send a second packet from the first workload to a third workload in the second site via the layer 2 channel between the first site when an IP address for the third workload does not match an eligible route in the routing table.

2. The method of claim 1 , wherein:

the first network device is configured to review the policy table after not finding the eligible route in the routing table.

3. The method of claim 1 , wherein:

the first network device includes a first Media Access Control (MAC) address and the second network device includes a second MAC address, and

the second packet is sent to the IP address of the third workload and a MAC address associated with the first MAC address of the first network device.

4. The method of claim 1 , wherein the set of IP addresses found in the second site are for networks connected to the second network device in the second site.

5. The method of claim 1 , wherein the first network device keeps a MAC address for the first workload as a source MAC address for the second packet and keeps a same time to live value for the second packet when sending the second packet via the layer 2 channel.

6. The method of claim 1 , wherein:

the second packet is sent to the second network device, and

the second network device sends the packet to the third workload in the second site.

7. The method of claim 1 , wherein:

the third workload sends a third packet for the first workload,

the second network device sends the third packet to the first workload via the layer 2 channel, and

paths for the second packet and the third packet are symmetric in that the paths go through the layer 2 channel.

8. A non-transitory computer-readable storage medium containing instructions, that when executed, control a computer system to be operable for:

setting, by a first network device in a first site, a first Internet Protocol (IP) address for an interface of the first network device to a value of a second IP address of a second network device in a second site;

adding a set of policies in a policy table to cover a set of IP addresses used in the second site;

adding a specific route into a routing table for the first network device for a third IP address associated with a first workload when it is detected that the first workload is migrated from the second site to the first site, wherein the first workload is on a stretched network between the first site and the second site that is coupled via a layer 2 channel, wherein:

the specific route in the routing table configures the first network device to send a first packet from a second workload local to the first site to the first workload without sending the first packet to the second site, and

the policy table configures the first network device to send a second packet from the first workload to a third workload in the second site via the layer 2 channel between the first site when an IP address for the third workload does not match an eligible route in the routing table.

9. The non-transitory computer-readable storage medium of claim 8 , wherein:

the first network device is configured to review the policy table after not finding the eligible route in the routing table.

10. The non-transitory computer-readable storage medium of claim 8 , wherein:

the first network device includes a first Media Access Control (MAC) address and the second network device includes a second MAC address, and

the second packet is sent to the IP address of the third workload and a MAC address associated with the first MAC address of the first network device.

11. The non-transitory computer-readable storage medium of claim 8 , wherein the set of IP addresses found in the second site are for networks connected to the second network device in the second site.

12. The non-transitory computer-readable storage medium of claim 8 , wherein the first network device keeps a MAC address for the first workload as a source MAC address for the second packet and keeps a same time to live value for the second packet when sending the second packet via the layer 2 channel.

13. The non-transitory computer-readable storage medium of claim 8 , wherein:

the second packet is sent to the second network device, and

the second network device sends the packet to the third workload in the second site.

14. The non-transitory computer-readable storage medium of claim 8 , wherein:

the third workload sends a third packet for the first workload,

the second network device sends the third packet to the first workload via the layer 2 channel, and

paths for the second packet and the third packet are symmetric in that the paths go through the layer 2 channel.

15. A method comprising:

receiving, by a first network device, a packet, wherein a first workload is located in a network that is stretched across a first site and a second site, wherein the first network device includes an interface associated with an Internet Protocol (IP) address that is a same IP address as a second network device in the second site, and the packet includes a destination IP address;

determining whether the destination IP address of the packet matches an eligible route in a routing table for the first network device;

when the destination IP address of the packet does not match the eligible route, performing:

reviewing a policy table to determine that the destination IP address matches a route for a policy in the policy table, wherein the policy table includes routes to cover a set of IP addresses used in the second site; and

based on the determining the route in the policy table, sending the packet through a layer 2 channel to the second network device in the second site based on the policy, wherein the second network device sends the packet to a device;

when the destination IP address of the packet does match the eligible route, sending the packet to the first workload without sending the packet to the second site when the destination IP address is for the first workload.

16. The method of claim 15 , wherein when the destination IP address of the packet does not match the eligible route:

the packet comprises a first packet,

the device sends a second packet to the first workload, and

the second network device sends the second packet to the first workload via the layer 2 channel.

17. The method of claim 15 , wherein when the destination IP address of the packet does not match the eligible route, the first network device keeps a MAC address for the second packet as a source MAC address for the first workload and keeps a same time to live value for the packet when sending the packet via the layer 2 channel.

18. The method of claim 15 , wherein the packet comprises a first packet, and the device comprises a first device, the method further comprising:

receiving a second packet from the first workload for a second device, wherein the second device is on a non-stretched network in the first site; and

sending the second packet locally to the second device.

19. The method of claim 18 , wherein:

the eligible route in the routing table is a specific route for the IP address associated with the first workload.

20. The method of claim 18 , further comprising:

when the first workload migrates to the first site, adding a specific route for the IP address associated with the first workload in the routing table.

Assignments (2)
CHANGE OF NAME Recorded Apr 15, 2024
From: VMWARE, INC.
To: VMWARE LLC
Reel/Frame 067102/0395 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded May 28, 2020
From: ZHU, HONGWEI; DILEEP, DILEEP; CHANDRASHEKHAR, GANESAN; GU, FENG; DUVVURI, SREENIVAS; RAMAN, CHIDAMBARESWARAN; RAJU, NITHIN BANGALORE
To: VMWARE, INC.
Reel/Frame 052781/0301 →
Continuity (2)
Provisional Application 63005982 · Apr 6, 2020
Related Publication 20210314265A1 · Oct 7, 2021