US 12,254,340 B2
Providing services with guest VM mobility
Fenil Kavathia, Sunnyvale, CA (US); Anuprem Chalvadi, Sunnyvale, CA (US); Yang Ping, San Jose, CA (US); Akhila Naveen, Palo Alto, CA (US); Yong Feng, Sunnyvale, CA (US); Kantesh Mundaragi, Bangalore (IN); Rahul Mishra, Mountain View, CA (US); Pierluigi Rolando, Santa Clara, CA (US); Jayant Jain, Cupertino, CA (US); and Raju Koganty, San Jose, CA (US)
Assigned to VMWare LLC, Palo Alto, CA (US)
Filed by VMware LLC, Palo Alto, CA (US)
Filed on Jan. 31, 2023, as Appl. No. 18/103,516.
Application 18/103,516 is a continuation of application No. 17/352,298, filed on Jun. 19, 2021, granted, now 11,609,781.
Application 17/352,298 is a continuation of application No. 16/444,826, filed on Jun. 18, 2019, granted, now 11,042,397, issued on Jun. 22, 2021.
Claims priority of provisional application 62/809,464, filed on Feb. 22, 2019.
Claims priority of application No. 201941007860 (IN), filed on Feb. 28, 2019.
Prior Publication US 2023/0168917 A1, Jun. 1, 2023
Int. Cl. G06F 9/455 (2018.01); G06F 9/54 (2006.01); H04L 12/46 (2006.01); H04L 41/0803 (2022.01); H04L 41/0816 (2022.01); H04L 41/5003 (2022.01); H04L 41/5054 (2022.01); H04L 45/00 (2022.01); H04L 45/302 (2022.01); H04L 45/586 (2022.01); H04L 45/74 (2022.01); H04L 45/745 (2022.01); H04L 47/125 (2022.01); H04L 47/17 (2022.01); H04L 47/19 (2022.01); H04L 47/2425 (2022.01); H04L 49/00 (2022.01); H04L 49/25 (2022.01); H04L 61/2592 (2022.01); H04L 67/10 (2022.01); H04L 67/1001 (2022.01); H04L 67/101 (2022.01); H04L 67/51 (2022.01); H04L 67/56 (2022.01); H04L 67/563 (2022.01); H04L 67/60 (2022.01); H04L 69/321 (2022.01); H04L 69/324 (2022.01); H04L 69/325 (2022.01); H04L 41/0806 (2022.01); H04L 41/0893 (2022.01); H04L 101/622 (2022.01)
CPC G06F 9/45558 (2013.01) [G06F 9/546 (2013.01); H04L 12/4633 (2013.01); H04L 41/0803 (2013.01); H04L 41/0816 (2013.01); H04L 41/5003 (2013.01); H04L 41/5054 (2013.01); H04L 45/26 (2013.01); H04L 45/308 (2013.01); H04L 45/38 (2013.01); H04L 45/586 (2013.01); H04L 45/66 (2013.01); H04L 45/74 (2013.01); H04L 45/745 (2013.01); H04L 47/125 (2013.01); H04L 47/17 (2013.01); H04L 47/19 (2013.01); H04L 47/2425 (2013.01); H04L 49/252 (2013.01); H04L 49/3009 (2013.01); H04L 61/2592 (2013.01); H04L 67/10 (2013.01); H04L 67/1001 (2022.05); H04L 67/101 (2013.01); H04L 67/51 (2022.05); H04L 67/56 (2022.05); H04L 67/563 (2022.05); H04L 67/60 (2022.05); H04L 69/321 (2013.01); H04L 69/324 (2013.01); H04L 69/325 (2013.01); G06F 2009/4557 (2013.01); G06F 2009/45595 (2013.01); H04L 41/0806 (2013.01); H04L 41/0893 (2013.01); H04L 2101/622 (2022.05); H04L 2212/00 (2013.01)] 20 Claims
OG exemplary drawing
 
1. A method of specifying a sequence of services, the method comprising:
identifying, for a data message associated with a source machine executing on a source host computer, a plurality of service nodes to perform a plurality of service operations on the data message, the plurality of service nodes defining a service path in a network, the service path comprising the plurality of service nodes;
distributing to the source host computer a service insertion rule to use to identify the plurality of service nodes as the data message traverses along an egress path from the source host computer to a destination host computer; and
distributing, to each of a plurality of host computers that each executes at least one service node, at least one next-hop forwarding rule that comprises a network address of a next-hop service node in a service path, each host computer using each next-hop forwarding rule to retrieve the network address of a next-hop service node to forward the data message after a service node on the host computer performs a service operation on the data message.