| CPC G06F 9/45558 (2013.01) [G06F 9/455 (2013.01); G06F 9/45533 (2013.01); G06F 15/177 (2013.01); H04L 41/08 (2013.01); H04L 41/0803 (2013.01); H04L 41/0806 (2013.01); H04L 41/0813 (2013.01); H04L 41/0823 (2013.01); H04L 41/0889 (2013.01); H04L 41/0893 (2013.01); H04L 41/12 (2013.01); H04L 45/64 (2013.01); H04L 45/74 (2013.01); H04L 49/70 (2013.01); H04L 61/2503 (2013.01); H04L 61/2517 (2013.01); H04L 61/2521 (2013.01); H04L 61/256 (2013.01); H04L 63/0218 (2013.01); H04L 67/1008 (2013.01); G06F 2009/4557 (2013.01); G06F 2009/45595 (2013.01); H04L 45/02 (2013.01); H04L 49/15 (2013.01)] | 18 Claims |

|
1. A method of performing a middlebox service operation in a data center comprising a plurality of host computers that execute source and destination machines for data message flows, the method comprising:
deploying a set of two or more middlebox service modules to execute on a set of two or more host computers to implement a plurality of distributed logical middleboxes for performing the middlebox service operation for a plurality of logical networks, each distributed logical middlebox implemented by at least two middlebox modules executing on at least two host computers;
distributing at least one logical middlebox service for each logical network;
configuring each middlebox service module with a set of middlebox service rules for the middlebox service modules to use to perform the middlebox service operation; and
wherein each distributed logical middlebox service is identified by a particular identifier, each particular set of middlebox service rules for each particular logical network is associated with the particular identifier of the particular logical network, and each middlebox service module uses a particular tag of the particular logical network to identify the set of middlebox service rules for the particular logical network to use while processing data messages associated with the particular logical network.
|