EP3991368A1 - Zone démilitarisée transparente fournissant un service à états entre des réseaux physiques et logiques - Google Patents

Zone démilitarisée transparente fournissant un service à états entre des réseaux physiques et logiques

Info

Publication number
EP3991368A1
EP3991368A1 EP20812203.6A EP20812203A EP3991368A1 EP 3991368 A1 EP3991368 A1 EP 3991368A1 EP 20812203 A EP20812203 A EP 20812203A EP 3991368 A1 EP3991368 A1 EP 3991368A1
Authority
EP
European Patent Office
Prior art keywords
network
edge device
logical
network edge
data message
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
EP20812203.6A
Other languages
German (de)
English (en)
Inventor
Jayant Jain
Mike PARSA
Xinhua Hong
Subrahmanyam Manuguri
Anirban Sengupta
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
VMware LLC
Original Assignee
VMware LLC
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Priority claimed from US16/742,663 external-priority patent/US11588682B2/en
Priority claimed from US16/742,633 external-priority patent/US11411777B2/en
Priority claimed from US16/742,685 external-priority patent/US10938594B1/en
Application filed by VMware LLC filed Critical VMware LLC
Publication of EP3991368A1 publication Critical patent/EP3991368A1/fr
Pending legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/24—Multipath
    • H04L45/245—Link aggregation, e.g. trunking
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/02—Topology update or discovery
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/58—Association of routers
    • H04L45/586—Association of routers of virtual routers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/74—Address processing for routing
    • H04L45/745—Address table lookup; Address filtering

Definitions

  • Providing a stateful service across two or more equal cost multipathing (ECMP) paths presents certain challenges. If different paths are selected for forward and return data messages of a data message flow, a service engine providing the stateful service on one path may not be able to track a state of the data message flow as the service engine will not receive all the data messages of the data message flow (i.e., will not receive data messages for which an alternative path is selected). If the different paths are combined to pass through a same service engine, the path selection is not respected as the combined paths will redistribute incoming data messages among the combined outgoing interfaces such that a particular data message will be forwarded along a different path than the path selected by the ECMP operation. Accordingly, a solution that respects ECMP path selection and maintains correct state information at a stateful service engine is required.
  • Some embodiments of the invention provide novel methods for providing a stateful service at a network edge device (e.g., an NSX edge) that has a plurality of north-facing interfaces (e.g., interfaces to an external network) and a plurality of corresponding south-facing interfaces (e.g., interfaces to an internal logical network). North-facing interfaces of the network edge device are associated with south-facing interfaces. In some embodiments, the association is one-to-one, while in other embodiments some interfaces are grouped (e.g., aggregated) and the groups are associated in a one-to-one fashion.
  • the network edge device receives data messages at the interfaces from forwarding elements that select particular paths (e.g., interfaces of forwarding elements on the other side of the network edge device) for the data messages.
  • the selection of paths in some embodiments, is based on equal cost multipathing (ECMP) or a similar selection mechanism.
  • ECMP equal cost multipathing
  • the network edge device is transparent to the north and south forwarding elements such that they are not aware that the network edge device is interposed between north and south forwarding elements in some embodiments.
  • a set of interfaces on the north (south) side of the network edge device for a set of equal cost paths are bonded together in the network edge device to correspond to a single interface on the north (south) side of a logical bridge including at least one logical switch providing a stateful service implemented by the network edge device.
  • the bond is implemented, in some embodiments, using a bonding module executing on the network edge device that maintains a mapping between ingress and egress interfaces (in addition to standard bonding techniques) to allow deterministic forwarding through the network edge device in the presence of bonded interfaces.
  • a bonding module on the ingress side for a particular data message associates an identifier of an ingress interface on which a data message is received with the data message.
  • the association is stored in metadata of the data message and is removed after a bonding module on the egress side determines the egress interface based on the mapping between ingress and egress interfaces.
  • the at least one logical switch calls a service engine to provide the stateful service.
  • the bonded interfaces force all traffic for the ECMP group to go through the same set of logical switches and call the same service engine to provide the stateful service and maintain state information for each flow crossing the logical switches. If the interfaces were not bonded and separate logical switches (and service engines) processed data messages on the separate paths, a return data message could use a different path than an original message and state information would not be kept by the service engine and the stateful service would not function properly.
  • the network edge device receives a data message at a first interface and provides the data message to the logical switch interface associated with the bonding module.
  • the bonding module associates the data message with an identifier of the ingress interface. In some embodiments, the association is inserted in the data message, while in other embodiments the identifier is appended to the data message.
  • a service engine is called by a logical switch, in some embodiments, to provide a stateful service.
  • the service engine provides the stateful service and provides the data message to an egress interface associated with a second bonding module.
  • the second bonding module uses a mapping table, in some embodiments, to determine an egress interface associated with the ingress interface.
  • the logical processing removes the ingress interface identifier and provides the data message to the egress module.
  • the network edge device in some embodiments, is a primary network edge device and a secondary network edge device is implemented as a standby network edge device.
  • the secondary network edge device replicates the interfaces and associations of the primary network edge device and is available to assume the functions of the primary network edge device in the case of a failure of the primary network edge device.
  • failure of the primary network edge device is defined by a user.
  • the definition of failure in some embodiments, is defined by a user-supplied policy (e.g., a threshold for a given metric).
  • failover occurs when all paths through the primary network edge device fail.
  • each interface associated with a different bridge calls a service engine based on identifiers included in data messages received at the interface.
  • Each data message flow is associated with a particular identifier that is associated with a particular service engine instance that provides the stateful service.
  • the interface that receives a data message identifies a service engine to provide the stateful service and provides the data message to the identified service engine.
  • the service engine After processing the data message, the service engine provides the data message to the egress interface associated with the ingress interface.
  • Figure 1 illustrates an exemplary network topology of a system implementing an embodiment of the invention.
  • Figure 2 illustrates a particular embodiment of a system topology that includes a north edge device implementing a logical router and a logical switch (and DMZ).
  • Figure 3 illustrates a particular embodiment of a network topology of a system implementing an embodiment of the invention using a common connection tracker.
  • Figure 4 illustrates a particular embodiment of a network topology of a system implementing an embodiment of the invention using different service engines for different logical networks.
  • Figure 5 conceptually illustrates a process for configuring a network edge device to process data messages using a set of bonded interfaces with deterministic mapping between bonded interfaces.
  • Figure 6 conceptually illustrates a process for configuring a network edge device to implement the bonded interfaces and bonding modules that, in some embodiments, maintain the mapping tables generated.
  • Figure 7 illustrates two sets of mapping tables that are used in different embodiments of the invention.
  • Figure 8 conceptually illustrates a process for using the configured network edge device to provide a stateful service.
  • Figure 9 illustrates a particular network edge device in a set of network edge devices connecting a first north edge routing element and a south edge routing element.
  • Figure 10 illustrates a second embodiment of a network in which the invention is carried out.
  • Figure 11 illustrates an embodiment including active and standby network edge devices.
  • Figure 12 conceptually illustrates a process for failure handling.
  • Figure 13 conceptually illustrates a process for configuring a network edge device to implement an embodiment of the invention that allows for separate logical switches for different equal cost paths.
  • Figure 14 conceptually illustrates a process for processing data messages at a network edge device configured according to an embodiment in which a set of shared service engines are implemented for the set of logical switches.
  • Figure 15 illustrates an embodiment in which the process of Figure 14 is carried out.
  • Figure 16 conceptually illustrates a process for processing data messages at a network edge device configured according to an embodiment in which a common connection tracker is shared by each logical switch and the service engine associated with each logical switch.
  • Figure 17 illustrates an embodiment in which the process of Figure 16 is carried out.
  • Figure 18 illustrates the system of some embodiments.
  • Figure 19 conceptually illustrates a computer system with which some embodiments of the invention are implemented.
  • data packet, packet, data message, or message refers to a collection of bits in a particular format sent across a network. It should be understood that the term data packet, packet, data message, or message may be used herein to refer to various formatted collections of bits that may be sent across a network, such as Ethernet frames, IP packets, TCP segments, UDP datagrams, etc.
  • references to L2, L3, L4, and L7 layers are references to the second data link layer, the third network layer, the fourth transport layer, and the seventh application layer of the OSI (Open System Interconnection) layer model, respectively.
  • OSI Open System Interconnection
  • Data messages are organized into data message flows based on being part of a same communication session between a source and destination compute node.
  • a unidirectional data message flow is often defined by a set of header values (e.g., a 5-tuple for a TCP flow, or, more generally, an n-tuple) of a data message.
  • a bidirectional data message flow includes both the forward unidirectional flow and the return unidirectional data message flow (e.g., a return flow that has a set of source and destination addresses reversed in relation to the forward flow).
  • a data message flow will refer to the bidirectional data message flow unless otherwise indicated.
  • a user-defined logical network refers to a particular logical abstraction of a network.
  • the logical abstraction includes logical counterparts to network elements of a physical network such as forwarding elements (e.g., switches, hubs, routers, bridges, etc.), load balancers, and firewalls.
  • the logical forwarding elements e.g., a logical switch or logical router
  • MFEs e.g., physical or virtual/software switches, or routers
  • a particular host machine may host data compute nodes (DCNs) (e.g., containers or virtual machines (VMs)) connected to multiple different logical networks and the set of MFEs implements all the logical networks to which the DCNs logically connect. Additional details of the structure and function of logical networks are described in U S. Patent Publication 2016/0226754, which is hereby incorporated by reference.
  • DCNs data compute nodes
  • VMs virtual machines
  • a network edge device is implemented in some logical networks.
  • a network edge device connects a first set of forwarding elements on a first side of the network edge device to a second set of forwarding elements on a second side of the network edge device.
  • the network edge device executes in a ‘bare-metal’ environment (i.e., directly on a physical device).
  • the first set of forwarding elements are MFEs implementing a distributed logical router in a particular logical network and the second set of forwarding elements is a service router in the logical network that provides connectivity to an external network.
  • the first set of forwarding elements is a set of logical forwarding elements (e.g., routers, switches, etc.) in a logical network and the second set of forwarding elements is a set of forwarding elements external to the logical network.
  • logical forwarding elements e.g., routers, switches, etc.
  • the network edge device operates between two networks
  • the two gateway devices e.g., network edge routers
  • the two gateway devices e.g., network edge routers
  • the network edge device implements a set of logical switches in some embodiments.
  • Logical switches in some embodiments, are distributed logical switches implemented by a plurality of network edge devices.
  • the logical switches are associated with a distributed stateful service, or set of stateful services, in some embodiments.
  • Some embodiments of the invention provide novel methods for providing a stateful service at a network edge device (e.g., an NSX edge) that has a plurality of north-facing interfaces (e.g., interfaces to an external network) and a plurality of corresponding south-facing interfaces (e.g., interfaces to a logical network). North-facing interfaces of the network edge device are associated with south-facing interfaces. In some embodiments, the association is one-to-one, while in other embodiments some interfaces are grouped (e.g., aggregated) and the groups are associated in a one-to-one fashion.
  • the network edge device receives data messages at the interfaces from forwarding elements that select particular paths (e.g., interfaces of forwarding elements on the other side of the network edge device) for the data messages.
  • the selection of paths in some embodiments, is based on equal cost multipathing (ECMP) or a similar selection mechanism.
  • ECMP equal cost multipathing
  • the network edge device is transparent to the north and south forwarding elements such that they are not aware that the network edge device is interposed between north and south forwarding elements in some embodiments. For example, a time to live parameter is not decremented, and, conjunctively or alternatively, a source IP address is not changed.
  • FIG. 1 illustrates an exemplary network topology of a system 100 implementing an embodiment of the invention.
  • System 100 includes a set of network forwarding elements connecting external network 105 and internal network 110.
  • External network 105 and internal network 110 connect to a set of edge routers, i.e., north edge routers 120 and south edge routers 140 respectively, that connect the networks 105 and 110.
  • the edge routers 120 and 140 are any combination of physical routers and software routers implemented on a physical network edge device.
  • the software routers in some embodiments, are implemented as a plurality of forwarding elements such as a distributed router, a transit logical switch, and a service router as described in U.S. Patent Publication 2016/0226754.
  • the edge routers 120 and 140 are specifically the service routers of an edge device.
  • the south edge routers 140 in some embodiments, are active-active edge devices for a same logical network (or set of logical networks) in internal network 110. In some other embodiments, the south edge routers 140 are in an active- standby configuration.
  • a network edge device 101 Interposed between north edge routers 120 and south edge routers 140 is a set of network edge devices 101 that each execute a set of logical switches 130 and a set of service engines 131 that provide a set of gateway services in a transparent bridge between interfaces of the north and south edge routers.
  • a network edge device 101 in some embodiments, is a bare metal edge device. The provision of gateway services will be described in further detail below in relation to Figures 5-17.
  • the set of network edge devices 101 implements a demilitarized zone (DMZ) 155 that provides an extra layer of protection between the external and internal networks 105 and 110.
  • each network edge device provides a connection between a specific internal (e.g., logical network) and the external network.
  • Figure 2 illustrates a particular embodiment of a system topology that includes a set of north edge devices 225 each implementing logical router 220 (corresponding to a service router of north edge router 120) and the logical switch 130 (and DMZ 155).
  • the external network is an external logical network 205.
  • the logical router 220 in some embodiments, is a component of external logical network 205.
  • Figure 2 illustrates a set of connections for a single north edge device 225 with a set of edge routers (e.g., in an active-active or active-standby configuration) of an internal network (e g., a logical network) 110.
  • additional similar devices are employed in the system 200 for connecting to additional internal elements (e.g., edge routers of additional logical networks in the internal network 110).
  • Figure 3 illustrates a particular embodiment of a network topology of a system 300 implementing an embodiment of the invention using a common connection tracker.
  • Figure 3 includes a set of logical switches 330 in place of the single logical switch 130.
  • One embodiment using a set of logical switches 330 is described in Figure 17.
  • the multiple logical switches 330 are each implemented by a set of network edge devices making up the DMZ 155.
  • Each logical switch in some embodiments includes an associated service engine 331 to provide a service for data messages traversing the DMZ 155.
  • each of a set of network edge devices implements a subset of logical switches (e.g., anywhere from one to all of the logical switches) in the set of logical switches 330.
  • the service engines 33 in some embodiments, share a connection tracker 346 that maintains connection states for data flows passing through the DMZ using any of the logical switches 330.
  • Figure 3 also includes a set of south edge routers 340 and a set of north edge routers
  • each set of edge routers 120 and 340 represents a set of edge devices in one of an active-active or active- standby configuration.
  • some embodiments implement the south edge router as a component of an edge device that also includes a transit logical switch and a distributed router for a logical network (e.g., a logical network in internal network 110).
  • a single physical device implements multiple south (north) edge routers in the set of south (north) edge routers 340 (120).
  • each edge router in the set of edge routers 120 and 340 are implemented by a different edge device.
  • FIG. 4 illustrates a particular embodiment of a network topology of a system 400 implementing an embodiment of the invention using different service engines for different logical networks.
  • Figure 4 includes a set of logical switches 430 as described in Figure 15.
  • the multiple logical switches 430 are each implemented by a set of network edge devices making up the DMZ 155.
  • Each network edge device in some embodiments, also executes a set of service engines associated with different tenants or logical networks (e.g., logical networks 450A and 450B) for which it provides stateful services.
  • Each logical switch in some embodiments, can call any service engine 431 executing on the same network edge device to provide a service for data messages traversing the DMZ 155.
  • the service engine called in some embodiments, depends on the logical network associated with the data message to be provided the service.
  • Figure 4 also includes a set of south edge routers 440 and a set of north edge routers
  • each set of edge routers 120 and 440 represents a set of edge devices in one of an active-active or active- standby configuration.
  • some embodiments implement the south edge router as a component of an edge device that also includes a transit logical switch and a distributed router for a logical network (e g., a logical network in internal network 110).
  • the south edge routers 440 include south edge routers for both logical networks 450 that execute on a same edge device.
  • each logical network’s south edge routers 440 execute on a different set of edge devices.
  • a single physical device implements multiple south (north) edge routers in the set of south (north) edge routers 440 (120).
  • each edge router in the set of edge routers 120 and 440 are implemented by a different edge device.
  • Some embodiments using an active-active configuration assign different traffic to different edge devices (e g., using a sharding technique) to ensure that each data message in a particular data message flow (e.g., a bidirectional data message flow between a compute node in the internal network 110 and a compute node in the external network 105) is processed at a same edge device so as to maintain accurate state information without having to synchronize data-message-flow state information across edge devices.
  • a set of interfaces on the north (south) side of the network edge device for a set of equal cost paths are bonded together in the network edge device to correspond to a single interface on the north (south) side of a logical bridge including at least one logical switch providing a stateful service implemented by the network edge device.
  • the bond is implemented, in some embodiments, using a bonding module executing on the network edge device that maintains a mapping between ingress and egress interfaces to allow deterministic forwarding through the network edge device in the presence of bonded interfaces (in addition to standard bonding techniques).
  • a bonding module on the ingress side for a particular data message associates an identifier of an ingress interface on which a data message is received with the data message.
  • the association is stored in metadata of the data message and is removed after a bonding module on the egress side determines the egress interface based on the mapping between ingress and egress interfaces.
  • the at least one logical switch calls a service engine to provide the stateful service.
  • the bonded interfaces force all traffic for the ECMP group to go through the same set of logical switches and call the same service engine to provide the stateful service and maintain state information for each flow crossing the logical switches. If the interfaces were not bonded and separate logical switches (and service engines) processed data messages on the separate paths, a return data message could use a different path than an original message and state information would not be kept by the service engine and the stateful service would not function properly.
  • Figures 8-7 illustrate aspects of configuring and using an exemplary embodiment using bonded interfaces depicted in Figure 9.
  • FIG. 5 conceptually illustrates a process 500 for configuring a network edge device to process data messages using a set of bonded interfaces with deterministic mapping between bonded interfaces.
  • Process 500 in some embodiments, is performed by a network manager computer (e.g., a virtualization controller, a network manager, etc.).
  • Process 500 begins (at 510) by determining a mapping between interfaces of the network edge device.
  • the network edge device is a transparent (e.g., bump-in-the-wire) device that provides a service without changing the data message in a way that is apparent to the forwarding elements.
  • each source forwarding element expects that a data message sent from a first interface of the source forwarding element/network edge device will arrive at a second interface of the network edge device/destination forwarding element and not at a third interface of the network edge device/destination forwarding element. Because of this expectation, the normal function of a set of bonded interfaces (e.g., selecting an egress interface through a round robin, or other algorithm) would break the transparency of the network edge device (and, in some embodiments, would result in a forwarding failure) if a data message received at the first interface was received at the third interface.
  • the configuration information includes an identification of sets of interfaces to bond into a single interface of a set of logical switches that bridge networks on either side of the network edge device.
  • the identified sets of interfaces include all the interfaces of the network edge device.
  • the sets of interfaces include all the interfaces that are not management interfaces.
  • the configuration information includes configuration for a service engine that provides a stateful service (e.g., firewall, network address translation, virtual private network, etc.) associated with the set of logical switches.
  • the configuration information includes a set of mapping information (e.g., a mapping table or tables) to maintain deterministic forwarding between interfaces of the network edge device.
  • the set of mapping tables includes separate mapping tables for a north- and south-side bonding module.
  • the generated configuration data is then provided (at 530) to the network edge device (or devices) to be used by the network edge device to configure the bonded interfaces and bonding modules executing on the network edge device and the process ends.
  • FIG. 6 conceptually illustrates a process 600 for configuring a network edge device to implement the bonded interfaces and bonding modules that, in some embodiments, maintain the mapping tables generated (at 520).
  • the process 600 begins (at 610) by receiving configuration information for configuring the bonded interfaces and bonding modules of the network edge device.
  • the configuration data in some embodiments, is received from a network manager computer.
  • the configuration information identifies interfaces that are to be bonded into a single interface of a logical switch
  • the configuration information identifies a first set of interfaces that are bonded into an interface of a south-side logical switch and a second set of interfaces that are bonded into an interface of a north-side logical switch.
  • the configuration information also includes, in some embodiments, a set of mapping tables that include mappings between individual interfaces of the network edge device.
  • the process 600 configures
  • Configuring the interface bonding includes configuring the set of logical switches that make up a bridge between the networks on either side of the network edge device (through the bonded interfaces).
  • a single logical switch is implemented with each bonded interface corresponding to a different interface of the implemented logical switch.
  • a pair of logical switches i.e., a north-side logical switch and south side logical switch
  • the logical switch configuration data includes configuration information for a service engine that provides a stateful service.
  • the network edge device also configures the bonding modules to store the received mapping table(s).
  • the network edge device stores a single mapping table that is accessible to each bonding module, while in other embodiments, each bonding module stores a separate mapping table.
  • the mapping table in some embodiments, is received as a single mapping table that is split into the two separate tables at the network edge device. Two exemplary sets of mapping tables are depicted in Figure 7. One of ordinary skill in the art will appreciate that there are many ways to store the mapping tables that are excluded by the description of the specific examples.
  • FIG. 7 illustrates two sets of mapping tables 710 and 720 that are used in different embodiments of the invention.
  • Mapping table 710 is a single mapping table that includes an association between every possible ingress interface of the network edge device and an egress interface of the network edge device.
  • Each bonding module uses table 710 to identify an egress interface for a data message associated with a particular ingress interface.
  • Mapping table set 720 includes two different mapping tables (e.g., 720A and 720B) stored by different bonding modules.
  • Mapping table 720A is for a first bonding module bonding interfaces fp-ethO and fp-ethl and mapping table 720B is for a second bonding module bonding interfaces fp-eth2 and fp-eth3.
  • Each individual table 720A and 720B stored by a bonding module only stores entries 721 for interfaces that it is not bonding, as data messages received from the interfaces it bonds are provided to the logical switch and the other bonding module to determine an egress interface based on the ingress interface.
  • the network edge device receives a data message at a first interface and provides the data message to the logical switch interface associated with the bonding module.
  • the bonding module associates the data message with an identifier of the ingress interface. In some embodiments, the association is inserted in the data message, while in other embodiments the identifier is appended to the data message.
  • the ingress interface is stored as metadata associated with the data message.
  • a service engine is called by a logical switch, in some embodiments, to provide a stateful service. The service engine provides the stateful service and provides the data message to an egress interface associated with a second bonding module.
  • the second bonding module uses a mapping table, in some embodiments, to determine an egress interface associated with the ingress interface.
  • the logical processing removes the ingress interface identifier and provides the data message to the egress module.
  • FIG. 8 conceptually illustrates a process 800 for using the configured network edge device to provide a stateful service.
  • the process 800 is performed by the network edge device, but one of ordinary skill in the art will understand that different modules of the network edge device may be responsible for different operations of process 800.
  • the process 800 begins (at 810) by receiving a data message at a first, ingress interface of the network edge device.
  • the data message is received, in some embodiments, based on a selection of the interface from a plurality of possible interfaces (e.g., paths) by an upstream forwarding element (e g., a router performing an ECMP operation).
  • an upstream forwarding element e g., a router performing an ECMP operation.
  • the process 800 determines (at 820) an ingress interface associated with the data message and stores an identifier of the ingress interface for the data message.
  • the identified ingress interface is stored in metadata associated with the data message.
  • the identifier in some embodiments, is stored in the data packet itself (e.g., in an encapsulation header or other unused portion of the data message).
  • the data message associated with the identifier for the ingress interface is then provided to the logical switch interface associated with the bonded interfaces.
  • the logical switch (or service engine associated with the logical switch) provides
  • the stateful service calls the service engine associated with the logical switch.
  • the stateful service in some embodiments, is at least one of a firewall, network address translation, and a VPN. If the stateful service is a firewall, providing the stateful service can lead to a data message being dropped. However, for the purposes of illustration, the description of Figure 8 assumes that the data message is allowed. One of ordinary skill in the art will understand that if a data message is dropped the process 800 does not proceed to the next operation.
  • the service engine has provided the stateful service the data message, in some embodiments, is returned to the logical switch interface from where it was called, while in other embodiments it is provided to an interface (e.g., the interface associated with the bonded interfaces) of the next logical switch on the egress side (for the particular data message) of the network edge device.
  • an interface e.g., the interface associated with the bonded interfaces
  • the bonding module then identifies (at 840) an egress interface for the data message based on the stored ingress interface identifier using the mapping table.
  • the ingress interface identifier is associated with a particular egress interface in the mapping table.
  • different associations between interfaces can exist for different flows.
  • a separate mapping table is stored for each flow and is identified by a flow identifier such as a five tuple or a hash of header values of the data messages in the data message flow.
  • the bonding module then removes (at 850) the ingress interface identifier and provides the data message to the egress interface to forward to the next hop of the data message.
  • the removal of the identifier is optional. For example, if the identifier is stored in an unused portion of a data message header, such that it will not affect the subsequent forwarding operations or the content of the data message, there is no need to remove the identifier and operation 850 will merely provide the data message to the identified egress interface. Once the data message is provided to the egress interface and forwarded to the next hop, the process ends.
  • Figure 9 illustrates a particular network edge device 910 in a set of network edge devices connecting a first north edge routing element 920 (in a set of north edge routing elements) connected to interfaces 905A (e.g., fp-ethO) and 905B (e.g., fp-ethl) and a south edge routing element 930 (in a set of south edge routing elements) connected to interfaces 905C (e.g., fp-eth2) and 905D (e.g., fp-eth3).
  • a first north edge routing element 920 in a set of north edge routing elements
  • interfaces 905A e.g., fp-ethO
  • 905B e.g., fp-ethl
  • south edge routing element 930 in a set of south edge routing elements
  • the paths between routing elements 920 and 930 are equal cost in the illustrated embodiment and either can be selected for transmitting data messages between the routing (e.g., forwarding) elements 920 and 930.
  • the network edge device 910 includes bonded interfaces indicated by the dotted ellipse 960 and bonding modules 912A and 912B that support the bonded interfaces on the north and south sides of the network edge device 910, respectively.
  • the bonding modules 912 are implemented, in some embodiments, as part of a set of logical switches 914 that (1) provide a bridge between the north and south networks and (2) provide a stateful service for data messages crossing the bridge.
  • the bridge in Figure 9 is depicted as two logical switches 914A and 914B, however, in some other embodiments, the bridge is implemented using a single logical switch with separate interfaces (e.g., ports) connecting to the north and south side bonded interfaces.
  • the logical switches 914 provide a stateful service to data messages passing through the set of logical switches 914 between the two networks.
  • the stateful service in some embodiments is provided by a service engine 913 that provides a firewall service, network address translation, virtual private network, etc. that may require processing all the data messages in a data message flow for proper performance. Additional services, in some embodiments, are provided by additional service engines (not shown for clarity). By bonding the two equal cost paths at the logical switch interface, the invention ensures that all data messages that are sent along either path are processed by the same service engine 913 to ensure that state information maintained at the service engine is complete.
  • the bonding modules store a mapping table that ensures that traffic received at any particular interface are forwarded to the destination using the corresponding interface.
  • Figure 10 illustrates a second embodiment of a network in which the invention is carried out.
  • Figure 10 illustrates a particular network edge device 1010 connecting a first set of north edge routing elements 1020 connected to interfaces 1005A-C and a second set of south edge routing elements 1030 connected to interfaces 1005D-F.
  • the sets of routing elements 1020 and 1030 help to connect other routing elements 1025 in the networks on either side of the network edge device 1010.
  • the paths between routing (e.g., forwarding) elements in the sets of routing elements 1020 and 1030 i.e., 1005A to 1005D and 1005B to 1005E and 1005C to 1005F) are equal cost in the illustrated embodiment and any of them can be selected for transmitting data messages between the routing elements 1025.
  • the network edge device 1010 includes bonding module 1012 that supports the bonded interfaces on the north and south sides of the network edge device 1010, respectively.
  • the bonding module is a function of the logical switch that implements the interface bonding and stores the mapping tables or otherwise maintains the connections between specific interfaces.
  • the bonding module 1012 supports different interfaces of a single logical switch 1014 that (1) provides a bridge between the north and south networks and (2) provides a stateful service for data messages crossing the bridge using service engine 1013.
  • the bridge in Figure 10 is depicted as one logical switch 1014, however, in some other embodiments, the bridge is implemented using multiple logical switches as in Figure 9.
  • the logical switch 1014 provides a stateful service to data messages passing through the logical switch 1014 between the two networks.
  • the stateful service in some embodiments is provided by the service engine 1013 that provides a firewall service, network address translation, virtual private network, etc. that may require processing all the data messages in a data message flow for proper performance. Additional services, in some embodiments, are provided by additional service engines (not shown for clarity). By bonding the two equal cost paths, the invention ensures that all data messages that are sent along either path are processed by the same service engine 1013 to ensure that state information maintained at the service engine is complete.
  • path 1040A connects interfaces 1005 A and 1005D
  • path 1040B connects interfaces 1005B and 1005E
  • path 1040C connects interfaces 1005C and 1005F
  • the bonding modules store a mapping table that ensures that traffic received at any particular interface are forwarded to the destination using the corresponding interface.
  • mapping table that ensures that traffic received at any particular interface are forwarded to the destination using the corresponding interface.
  • the network edge device in some embodiments, is a primary network edge device and a secondary network edge device is implemented as a standby network edge device.
  • the secondary network edge device replicates the interfaces and associations of the primary network edge device and is available to assume the functions of the primary network edge device in the case of a failure of the primary network edge device.
  • failure of the primary network edge device is defined by a user.
  • the definition of failure in some embodiments, is defined by a user-supplied policy (e.g., a threshold for a given metric). In other embodiments, failover occurs when all paths through the primary network edge device fail.
  • Figure 11 illustrates an embodiment including active and standby network edge devices 1110A and 1110B.
  • Figure 11 illustrates pairs of edge routing (forwarding) elements 1120 and 1130 connected by three paths through each of an active network edge device 1110A and a standby network edge device 1110B.
  • the bonding is indicated by 1160 which, in some embodiments, represents a standard bonding operation by each logical switch 1114 for the logical interfaces associated with the bonded interfaces of edge devices 1110.
  • the network edge devices 1110 provide a set of bonded interfaces 1105A-C (on the north side) and 1105D-F (on the south side) and a set of logical switches 1114 that connect the pairs of edge routing (forwarding) elements 1120 and 1130.
  • a service engine that provides stateful services is omitted from the illustrated embodiment for clarity but is understood to be present as in Figure 9 and 10.
  • the interfaces of the network edge devices 1110 are deterministically paired such that data messages entering interface 1105 A exits from 1105D (bonding modules supporting the deterministic mapping are not shown).
  • the standby edge device 1110B in some embodiments, has an equivalent set of interfaces (1105A-C on the north side and 1105D-F on the south side) and advertises the cost of the path through the interfaces of the standby edge device 1110B as having a higher cost than the paths through the equivalent interfaces of the active edge device 1110A such that all data messages destined for the pair of edge routers 1130 passes through active edge device 1110A.
  • An active- standby configuration is often used when stateful services are provided at the edge device. The failover process of similar embodiments employing active and standby network edge devices is described in Figure 12.
  • edge device 1110 is transparent to the routing elements, in some embodiments, when a particular connection to the edge device fails (e.g., a connection between the north edge routing element 1120B and interface 1105B on edge device 1110A) the edge device 1110 is responsible for bringing down a corresponding connection on the other side of the edge device 1110 (e.g., the connection between the south edge routing element 1130A and interface 1105E on edge device 1110A). In the case of a failure of either interface 1105B or 1105E, traffic from within the network on the north side can still reach destinations in the network on the south side and vice versa using edge routing element 1130B.
  • a particular connection to the edge device fails (e.g., a connection between the north edge routing element 1120B and interface 1105B on edge device 1110A) the edge device 1110 is responsible for bringing down a corresponding connection on the other side of the edge device 1110 (e.g., the connection between the south edge routing element 1130A and interface 1105E on edge device 11
  • FIG. 12 conceptually illustrates a process 1200 for failure handling (i.e., failover).
  • the process 1200 is performed by a network edge device, or network manager computer that monitors the health of an active network edge device (e.g., network edge device 1110A).
  • the process 1200 begins by receiving (at 1210) a failover policy that defines how different failures are to be handled.
  • the failover policy is received from a user and specifies threshold values for a set of connection (link) metrics (e.g., dropped data messages, bandwidth, a current load metric, a reliability metric, and a capacity metric) that trigger the standby network edge device to become the active network edge device.
  • link connection
  • the change in active network edge devices applies only to new data message flows with existing data message flows directed to the previously active network edge device. In other embodiments, all data message flows are directed to the new active network edge device upon failover.
  • link failure is determined at the level of the logical switch
  • the network edge device e.g., at the level of a logical switch port or interface.
  • failure detection required separate monitoring and failover which introduced additional complexity.
  • monitoring a single logical switch failure is simpler and does not require failover until all paths have failed.
  • a user can set a policy for failover other than complete failure by setting up conditional failover based on connection metrics of the combined multiple links between the networks. The network topology is therefore maintained for longer periods than would be the case if a single link failure out of multiple links could trigger a failover event.
  • the process 1200 then proceeds to monitor (at 1220) the link (representing the combined links over all the bonded interfaces).
  • the link monitoring includes monitoring the metrics specified in a default or user-specified policy. Monitoring, in some embodiments, is performed by a network manager computer that initiates a failover process when the conditions for failover are met. In some embodiments, monitoring is performed by the standby network edge device to determine if it needs to initiate a failover process and become the new active network edge device.
  • the process 1200 determines (at 1230) whether a failover process has been triggered based on the monitored metrics and the received failover policy. If the policy has not been met, i.e., the metrics have not crossed the specified threshold from an acceptable to an unacceptable value, the process returns to monitor (at 1220) the link.
  • the policy specifies a plurality of thresholds such that a first threshold may be crossed for a specified period before triggering a failover process, while a second threshold is specified such that any crossing of the second threshold triggers a failover process.
  • a failover process causes a formerly-standby network edge device to advertise its availability with a lower cost and a formerly-active network edge device to advertise its availability with a higher cost such that all traffic is now directed to new active (formerly-standby) device.
  • a failover process causes a formerly-standby network edge device to advertise its availability with a lower cost and a formerly-active network edge device to advertise its availability with a higher cost such that all traffic is now directed to new active (formerly-standby) device.
  • each interface associated with a different bridge calls a service engine based on identifiers included in data messages received at the interface.
  • Each data message flow is associated with a particular identifier that is associated with a particular service engine instance that provides the stateful service.
  • the interface that receives a data message identifies a service engine to provide the stateful service and provides the data message to the identified service engine. After processing the data message, the service engine provides the data message to the egress interface associated with the ingress interface.
  • each logical switch has an associated service engine and uses a single connection tracker to maintain state information accessible to each service engine to ensure that all data messages of a data message flow are processed using current state information.
  • the connection tracker in some embodiments, is implemented as a lightweight database in the network edge device that is queried by each service engine in the network edge device. In some embodiments, the connection tracker is implemented as a simple table. One of ordinary skill in the art will appreciate that these are just two examples of many ways that a connection tracker may be implemented.
  • each service engine is programmed for rules associated with different logical networks and the set of rules associated with a particular data message is identified using an identifier stored in, or associated with, the data message (e.g., a VLAN tag).
  • the service engine uses the identified set of rules and the information in the connection tracker to provide the stateful service.
  • the service engine After processing the data message, the service engine provides the data message to the logical switch (e.g., to the egress interface of the logical switch) with which the service engine is associated.
  • FIG. 13 conceptually illustrates a process 1300 for configuring a network edge device to implement an embodiment of the invention that allows for separate logical switches for different equal cost paths.
  • the process 1300 is described from the perspective of a single network edge device that is being configured, but one of ordinary skill in the art will appreciate that, similarly to the process 500 described in Figure 5, a network manager computer, in some embodiments, generates the configuration data and sends it to the network edge device. Additionally, in some embodiments, the process 1300 is performed by each network edge device in a set of multiple edge devices implementing the DMZ.
  • a network edge device may perform different parts of the process 1300 (e.g., an agent for receiving the configuration data and a local controller for configuring the network edge device to configure the network edge device according to the received configuration data).
  • the process 1300 begins by receiving (at 1310) configuration information for configuring (implementing) a set of service engine instances that each provide a set of stateful services on the network edge device.
  • each service engine instance is associated with a different identifier.
  • the identifier in some embodiments, is an identifier associated with data message flows such that each data message in a particular data message flow will have a same identifier and be associated with a same service engine instance.
  • the identifier is associated with a network from which the data message flow is received (e.g., a VLAN or VXLAN tag, an IP address prefix, etc.).
  • a connection tracker of the service engine associated with a particular identifier will process all data messages of a data message flow and maintain current and correct state information.
  • each service engine is associated with a particular logical switch and includes multiple sets of rules for multiple different logical networks serviced by the network edge device.
  • the configuration information also includes, in some embodiments, configuration information for a shared connection tracker that maintains state information for data message flows processed by all the service engines and logical switches implemented on the network edge device.
  • the state information is maintained for each data message flow and includes a network identifier (e g., a VLAN or VXLAN tag an IP address prefix, etc. associated with the network) along with flow identifiers (e.g., an n- tuple) that uniquely identifies the data message flow.
  • a network identifier e.g., a VLAN or VXLAN tag an IP address prefix, etc. associated with the network
  • flow identifiers e.g., an n- tuple
  • the network edge device then receives (at 1320) configuration information to configure a plurality of bridges between particular sets of interfaces of the network edge device.
  • the configuration information includes a set of logical switches to implement, the identity of the bridged interfaces, and linked interfaces (e.g., linked into a link aggregation group (LAG) using a link aggregation control protocol (LACP)).
  • the configuration information received also includes configuration information to configure the interfaces (e.g., the physical interfaces of the network edge device or the logical interfaces of the logical switches) to call particular service engine instances based on identifiers included in received data messages.
  • the configuration information for a particular interface includes a particular service engine called by the interface and the identifier of a received data message is used by the service engine to determine the set of service rules that apply to the received data message.
  • the order of receiving the configuration information may be reversed or combined into a single operation in some embodiments.
  • the network edge device then configures (at 1330) the bridges and service engine instances specified by the configuration information.
  • the network edge device in some embodiments, now includes a set of bridged interfaces and a set of service engine instances that can be called from any interface. In other embodiments, the network edge device now includes a common connection tracker shared by the set of bridged interfaces (i.e., by the logical switches) and the set of service engine instances associated with the set of bridged interfaces. As will be described in relation to Figures 14-17, the network edge device is now ready to implement the invention and the process ends.
  • FIG 14 conceptually illustrates a process 1400 for processing data messages at a network edge device configured according to an embodiment of process 1300 in which a set of shared service engines are implemented for the set of logical switches.
  • the process 1400 is performed by the network edge device, in some embodiments, and one of ordinary skill in the art will appreciate that different modules or components of the network edge device perform different operations of process 1400.
  • the process 1400 begins by receiving (at 1410) a data message of a data message flow at a particular interface of the network edge device.
  • the data message includes a particular identifier, e.g., a VLAN tag, that is associated with every data message in the data message flow.
  • the process 1400 then identifies (at 1420) the service engine instance that is associated with the particular identifier.
  • the service engine instances are associated with particular identifiers in a table accessible by the interfaces.
  • the association in some embodiments, is between a VLAN tag and service engine. In other embodiments, the association is based on other data message flow attributes that do not change for a particular flow.
  • the process 1400 calls (at 1430) the identified service engine.
  • the identified service engine instance is called from the interface of the network edge device.
  • the identified service engine is called from a logical switch interface of a set of logical switches that bridges (connects) two interfaces of the network edge device.
  • the identified service engine provides (at 1440) the stateful service to the data message and forwards the data message to its destination.
  • the data message is returned to the ingress interface to be sent across the bridge to the egress interface.
  • the data message is forwarded through the logical switch interface to the egress interface and ultimately to the destination.
  • the process 1400 ends.
  • Figure 15 illustrates an embodiment in which the process 1400 is carried out.
  • Figure 15 illustrates a network edge device 1510 providing a set of paths between a first set of north edge routing elements 1520 connected to interfaces 1505A-E and a second set of south edge routing elements 1530 connected to interfaces 1505F-J.
  • Each set of associated interfaces e.g., 1505 A and 1505F
  • Each set of associated interfaces is connected by a single logical switch and includes, in the depicted embodiment, sets of interfaces (i.e., 1505D / 1505E and 15051 / 1505J) configured as a link aggregation group 1540 with the aggregated interfaces also connecting through a single logical switch 1514.
  • Figure 15 also illustrates a set of service engine instances 1545 that execute on the network edge device and can be called from any interface (e g., any interface configured to call a service engine) to provide a stateful service for data messages received at the interface.
  • Figure 15 also illustrates exemplary routing elements 1525A and 1525B in the external (north-side) and internal (south-side) networks.
  • external routing element 1525 A considers each north edge routing element 1520 to be an equal cost path to a destination behind (or below) the internal routing element 1525B. Accordingly, in trying to reach the destination, external routing element 1525 A may select either of north edge routers 1520 as a next hop and the decision may change over the life of a flow based on factors not having to do with any of the illustrated system components.
  • the north edge routing elements 1520 see each path to the internal routing element 1525B to be equal cost and may select either of south edge routers 1530 as a next hop and the decision may change in the middle of a flow based on factors not having to do with any of the illustrated system components.
  • the change in path selection does not affect the provision of the stateful service as the same service engine is called by each logical switch based on the flow identifiers that do not change over the life of the flow.
  • each logical switch has an associated service engine and uses a single connection tracker to maintain state information accessible to each service engine to ensure that all data messages of a data message flow are processed using current state information.
  • each service engine is programmed for rules associated with different logical networks and the set of rules associated with a particular data message is identified using an identifier stored in, or associated with, the data message (e.g., a VLAN tag). The service engine uses the identified set of rules and the information in the connection tracker to provide the stateful service. After processing the data message, the service engine provides the data message to the logical switch (e.g., to the egress interface of the logical switch) with which the service engine is associated.
  • the logical switch e.g., to the egress interface of the logical switch
  • FIG. 16 conceptually illustrates a process 1600 for processing data messages at a network edge device configured according to an embodiment of process 1300 in which a common connection tracker is shared by each logical switch and the service engine associated with each logical switch.
  • the process 1600 is performed by the network edge device, in some embodiments, and one of ordinary skill in the art will appreciate that different modules or components of the network edge device perform different operations of process 1600.
  • the process 1600 begins by receiving (at 1610) a data message of a data message flow at a particular interface of the network edge device.
  • the data message includes a particular identifier, e.g., a VLAN tag, that is associated with every data message in the data message flow.
  • the process 1600 then records (at 1620) the data message state information in the shared connection tracker.
  • the state information includes a set of identifiers of the data message (e.g., an n-tuple) and an identifier of the network associated with the data message (e.g., a VLAN or VXLAN tag, an IP address source or destination subnet, etc.) that are used to unambiguously identify the data message flow in the shared connection tracker.
  • One example of state information recorded by the process 1600 occurs upon receiving an ACK data message for a TCP connection.
  • the process 1600 updates an entry in the connection tracker to identify that the TCP connection has been established.
  • the process calls (at 1630) the service engine instance that is associated with the particular interface (i.e., logical switch) on which the data message was received.
  • the identified service engine instance is called from the interface of the network edge device.
  • the identified service engine is called from a logical switch interface of a set of logical switches that bridges (connects) two interfaces of the network edge device.
  • the service engine instances store multiple sets of service rules that apply to different networks (e.g., logical networks, or subnets) that are associated with particular identifiers.
  • connection tracker information is accessed (and updated) by the service engine as a part of providing the service.
  • the process 1600 identifies (at 1640) the set of service rules applicable to data message based on an identifier associated with the data message.
  • the identifier in some embodiments, is a network identifier (e.g., a VLAN or VXLAN tag, an IP address prefix, etc.) that is associated with each data message in a data message flow and with a set of service rules stored by the service engine.
  • the association is based on other data message flow attributes that do not change for a particular flow.
  • connection tracker is used to identify a specific rule or action previously applied to the data message flow based on the identifier associated with the data message (e.g., an n-tuple, or an n-tuple and network identifier).
  • the service engine provides (at 1650) the stateful service to the data message based on the identified set of applicable rules and forwards the data message to its destination.
  • the data message is returned to the ingress interface to be sent across the bridge to the egress interface.
  • the data message is forwarded through the logical switch interface to the egress interface and ultimately to the destination.
  • Figure 17 illustrates an embodiment in which the process 1600 is carried out.
  • Figure 17 illustrates a network edge device 1710 providing a set of paths between a first set of north edge routing elements 1720 connected to interfaces 1705A-E and a second set of south edge routing elements 1730 connected to interfaces 1705F-J.
  • the north and south edge routing elements are centralized logical routers implemented by edge devices (e.g., NSX edge) that, in some embodiments, also implement transit logical switches and distributed routers as described in U.S. Patent Publication 2016/0226754.
  • the edge routing elements in some embodiments, are configured in an active-active configuration, while in other embodiments, they are configured in and active-standby configuration.
  • Each set of associated interfaces (e.g., 1705A and 1705F) is connected by a single logical switch and includes, in the depicted embodiment, sets of interfaces (i.e., 1705D / 1705E and 17051 / 1705J) configured as a link aggregation group 1740 with the aggregated interfaces also connecting through a single logical switch 1714.
  • Figure 17 also illustrates a set of identical service engine instances 1745 that execute on the network edge device and are associated with interfaces of different logical switches to provide a stateful service for data messages received at the interface.
  • Figure 17 also depicts a shared connection tracker 1746 used by each logical switch to maintain the state of the data message flows traversing network edge device 1710.
  • the service engines 1745 are replaced by a set of service engines for providing different stateful or stateless services and only one service engine is shown for clarity.
  • the service engines providing different services all use the connection tracker 1746.
  • each service engine providing a particular stateful service is associated with (e.g., calls or queries) a particular connection tracker common to the service engines providing the particular stateful service.
  • Figure 17 also illustrates exemplary routing elements 1725A and 1725B in the external (north-side) and internal (south-side) networks.
  • external routing element 1725 A considers each north edge routing element 1720 to be an equal cost path to a destination behind (or below) the internal routing element 1725B. Accordingly, in trying to reach the destination, external routing element 1725 A may select either of north edge routers 1720 as a next hop and the decision may change over the life of a flow based on factors not having to do with any of the illustrated system components.
  • the north edge routing elements 1720 see each path to the internal routing element 1725B to be equal cost and may select either of south edge routers 1730 as a next hop and the decision may change in the middle of a flow based on factors not having to do with any of the illustrated system components.
  • the change in path selection does not affect the provision of the stateful service because using the shared connection tracker 1746 ensures that correct state data is maintained for data messages of a same data message flow that arrive on different interfaces.
  • Figure 17 illustrates only one network edge device 1710 forming a connection between two sets of edge routing elements
  • each of the depicted elements represents a set of multiple similar elements forming multiple connections between multiple different networks through multiple edge devices.
  • Figure 18 illustrates the system 1800 of some embodiments. As shown, this system includes multiple virtualized hosts 1805 and 1810 (hosting guest virtual machines 1850 and software forwarding elements (SFEs) 1852), a set of network manager computers 1820, and a network edge device 1815.
  • SFEs software forwarding elements
  • the virtualized hosts 1805 and 1810 host compute nodes that can be sources and destinations of data messages sent through network 1875 and network edge device 1815 to or from a compute node in network 1885
  • the network edge device 1815 is shown executing a software forwarding element (SFE) implementing a logical edge router for the managed network including hosts 1805-1815 connected by network 1875.
  • the edge device 1840 executes a set of logical switches 1814 and a set of service engines (e.g., service engine instances) 1845 as described above.
  • the hosts 1805 and 1810, the controller set 1820, and the network edge device 1815 communicatively couple through a network 1875, which can include a local area network (LAN), a wide area network (WAN) or a network of networks (e.g., Internet).
  • Network 1885 in some embodiments, is one of a second managed network in a same datacenter, a managed network in a second datacenter, and an external network.
  • the set of network manager computers 1820 provide control and management functionality for defining and managing the instantiation of one or more GVMs on each host (for the purposes of this discussion, network controllers 1820 includes both management plane and control plane controllers). These controllers are also responsible, in some embodiments, for configuring the edge device to provide the functionality described above. These controllers, in some embodiments, also provide control and management functionality for defining and managing multiple logical networks that are defined on the common software forwarding elements of the hosts.
  • the term “software” is meant to include firmware residing in read-only memory or applications stored in magnetic storage, which can be read into memory for processing by a processor.
  • multiple software inventions can be implemented as sub-parts of a larger program while remaining distinct software inventions.
  • multiple software inventions can also be implemented as separate programs.
  • any combination of separate programs that together implement a software invention described here is within the scope of the invention.
  • the software programs when installed to operate on one or more electronic systems, define one or more specific machine implementations that execute and perform the operations of the software programs.
  • FIG. 19 conceptually illustrates a computer system 1900 with which some embodiments of the invention are implemented.
  • the computer system 1900 can be used to implement any of the above-described hosts, controllers, and managers. As such, it can be used to execute any of the above described processes.
  • This computer system includes various types of non-transitory machine readable media and interfaces for various other types of machine readable media.
  • Computer system 1900 includes a bus 1905, processing unit(s) 1910, a system memory 1925, a read-only memory 1930, a permanent storage device 1935, input devices 1940, and output devices 1945.
  • the bus 1905 collectively represents all system, peripheral, and chipset buses that communicatively connect the numerous internal devices of the computer system 1900.
  • the bus 1905 communicatively connects the processing unit(s) 1910 with the read-only memory 1930, the system memory 1925, and the permanent storage device 1935.
  • the processing unit(s) 1910 retrieve instructions to execute and data to process in order to execute the processes of the invention.
  • the processing unit(s) may be a single processor or a multi-core processor in different embodiments.
  • the read only-memory (ROM) 1930 stores static data and instructions that are needed by the processing unit(s) 1910 and other modules of the computer system.
  • the permanent storage device 1935 is a read-and-write memory device. This device is a non-volatile memory unit that stores instructions and data even when the computer system 1900 is off. Some embodiments of the invention use a mass-storage device (such as a magnetic or optical disk and its corresponding disk drive) as the permanent storage device 1935.
  • the system memory 1925 is a read-and-write memory device. However, unlike storage device 1935, the system memory is a volatile read-and-write memory, such a random access memory.
  • the system memory stores some of the instructions and data that the processor needs at runtime.
  • the invention processes are stored in the system memory 1925, the permanent storage device 1935, and/or the read-only memory 1930. From these various memory units, the processing unit(s) 1910 retrieve instructions to execute and data to process in order to execute the processes of some embodiments.
  • the bus 1905 also connects to the input and output devices 1940 and 1945.
  • the input devices enable the user to communicate information and select commands to the computer system.
  • the input devices 1940 include alphanumeric keyboards and pointing devices (also called “cursor control devices”).
  • the output devices 1945 display images generated by the computer system.
  • the output devices include printers and display devices, such as cathode ray tubes (CRT) or liquid crystal displays (LCD). Some embodiments include devices such as a touchscreen that function as both input and output devices.
  • bus 1905 also couples computer system 1900 to a network 1965 through a network adapter (not shown).
  • the computer can be a part of a network of computers (such as a local area network (“LAN”), a wide area network (“WAN”), or an Intranet, or a network of networks, such as the Internet. Any or all components of computer system 1900 may be used in conjunction with the invention.
  • Some embodiments include electronic components, such as microprocessors, storage and memory that store computer program instructions in a machine-readable or computer- readable medium (alternatively referred to as computer-readable storage media, machine-readable media, or machine-readable storage media).
  • electronic components such as microprocessors, storage and memory that store computer program instructions in a machine-readable or computer- readable medium (alternatively referred to as computer-readable storage media, machine-readable media, or machine-readable storage media).
  • Such computer-readable media include RAM, ROM, read-only compact discs (CD-ROM), recordable compact discs (CD-R), rewritable compact discs (CD-RW), read-only digital versatile discs (e.g., DVD-ROM, dual-layer DVD-ROM), a variety of recordable/rewritable DVDs (e.g., DVD-RAM, DVD-RW, DVD+RW, etc ), flash memory (e.g., SD cards, mini-SD cards, micro-SD cards, etc.), magnetic and/or solid state hard drives, read-only and recordable Blu-Ray® discs, ultra-density optical discs, any other optical or magnetic media, and floppy disks.
  • RAM random access memory
  • ROM read-only compact discs
  • CD-R recordable compact discs
  • CD-RW rewritable compact discs
  • read-only digital versatile discs e.g., DVD-ROM, dual-layer DVD-ROM
  • flash memory e.g., SD
  • the computer-readable media may store a computer program that is executable by at least one processing unit and includes sets of instructions for performing various operations.
  • Examples of computer programs or computer code include machine code, such as is produced by a compiler, and files including higher-level code that are executed by a computer, an electronic component, or a microprocessor using an interpreter.
  • ASICs application specific integrated circuits
  • FPGAs field programmable gate arrays
  • memory all refer to electronic or other technological devices. These terms exclude people or groups of people.
  • display or displaying means displaying on an electronic device.
  • computer readable medium As used in this specification, the terms “computer readable medium,” “computer readable media,” and “machine readable medium” are entirely restricted to tangible, physical objects that store information in a form that is readable by a computer. These terms exclude any wireless signals, wired download signals, and any other ephemeral or transitory signals.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

La présente invention concerne, selon certains modes de réalisation, des procédés nouveaux pour fournir un service à états au niveau d'un dispositif de périphérie de réseau (p.ex. un bord NSX) doté d'une pluralité d'interfaces ascendantes (p.ex. des interfaces à un réseau externe) et une pluralité d'interfaces correspondantes descendantes (p.ex. des interfaces vers un réseau logique). Dans certains modes de réalisation, le dispositif de périphérie de réseau reçoit des messages de données en provenance d'un premier dispositif de passerelle issu d'un réseau logique, assure le service de réseau à états sur le message de données, et transfère le message de données vers la destination via une interface correspondante connectée à un réseau physique.
EP20812203.6A 2020-01-14 2020-11-04 Zone démilitarisée transparente fournissant un service à états entre des réseaux physiques et logiques Pending EP3991368A1 (fr)

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
US16/742,663 US11588682B2 (en) 2020-01-14 2020-01-14 Common connection tracker across multiple logical switches
US16/742,633 US11411777B2 (en) 2020-01-14 2020-01-14 Port mapping for bonded interfaces of ECMP group
US16/742,685 US10938594B1 (en) 2020-01-14 2020-01-14 Transparent demilitarized zone providing stateful service between physical and logical networks
PCT/US2020/058896 WO2021145939A1 (fr) 2020-01-14 2020-11-04 Zone démilitarisée transparente fournissant un service à états entre des réseaux physiques et logiques

Publications (1)

Publication Number Publication Date
EP3991368A1 true EP3991368A1 (fr) 2022-05-04

Family

ID=73554532

Family Applications (1)

Application Number Title Priority Date Filing Date
EP20812203.6A Pending EP3991368A1 (fr) 2020-01-14 2020-11-04 Zone démilitarisée transparente fournissant un service à états entre des réseaux physiques et logiques

Country Status (3)

Country Link
EP (1) EP3991368A1 (fr)
CN (2) CN117221214A (fr)
WO (1) WO2021145939A1 (fr)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11411777B2 (en) 2020-01-14 2022-08-09 Vmware, Inc. Port mapping for bonded interfaces of ECMP group

Family Cites Families (22)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6879590B2 (en) * 2002-04-26 2005-04-12 Valo, Inc. Methods, apparatuses and systems facilitating aggregation of physical links into logical link
CN100531158C (zh) * 2006-06-29 2009-08-19 华为技术有限公司 一种无线接入网关支持透明代理的系统及方法
US9450859B2 (en) * 2012-06-15 2016-09-20 Citrix Systems, Inc. Systems and methods for deriving unique MAC address for a cluster
US8971323B2 (en) * 2012-06-15 2015-03-03 Citrix Systems, Inc. Systems and methods for dynamic routing in a cluster
CN104023091B (zh) * 2013-02-28 2018-10-30 华为终端有限公司 一种多链路融合方法及设备
US9413658B2 (en) * 2013-03-15 2016-08-09 Cisco Technology, Inc. System for conversational link aggregation resolution in a network switch
WO2015142404A1 (fr) * 2014-03-21 2015-09-24 Nicira, Inc. Routage dynamique pour des routeurs logiques
US10104166B2 (en) * 2014-05-20 2018-10-16 Citrix Systems, Inc. Systems and methods for providing load balancing as a service
EP3219058B1 (fr) * 2014-11-14 2020-11-18 Nicira Inc. Services à états sur bord en grappe sans état
US9787573B2 (en) * 2014-12-31 2017-10-10 Juniper Networks, Inc. Fast convergence on link failure in multi-homed Ethernet virtual private networks
US10129180B2 (en) * 2015-01-30 2018-11-13 Nicira, Inc. Transit logical switch within logical router
US10038628B2 (en) * 2015-04-04 2018-07-31 Nicira, Inc. Route server mode for dynamic routing between logical and physical networks
CN106330780B (zh) * 2015-06-24 2019-08-20 联想企业解决方案(新加坡)有限公司 用于构成聚合链路的交换机、设备和方法
US9967182B2 (en) * 2015-07-31 2018-05-08 Nicira, Inc. Enabling hardware switches to perform logical routing functionalities
US10785315B2 (en) * 2015-10-30 2020-09-22 Citrix Systems, Inc. Method for resumption of an application session with a very dynamic and very large state in a standby intermediary device when the primary device fails
WO2017082947A1 (fr) * 2015-11-12 2017-05-18 Hewlett Packard Enterprise Development Lp Agrégation ethernet entre un dispositif périphérique et un commutateur
US10972380B2 (en) * 2016-04-05 2021-04-06 Versa Networks, Inc. Method for configuring a connection using redundant service nodes
US10841273B2 (en) * 2016-04-29 2020-11-17 Nicira, Inc. Implementing logical DHCP servers in logical networks
CN108574583A (zh) * 2017-03-08 2018-09-25 华为技术有限公司 一种设备升级方法及接入设备
CN108259328B (zh) * 2017-08-30 2020-06-05 新华三技术有限公司 报文转发方法及装置
CN108259339B (zh) * 2017-08-31 2020-12-25 新华三技术有限公司 报文发送方法及装置
CN109547354B (zh) * 2018-11-21 2022-08-30 广州市百果园信息技术有限公司 负载均衡方法、装置、系统、核心层交换机及存储介质

Also Published As

Publication number Publication date
CN117221214A (zh) 2023-12-12
CN114342333A (zh) 2022-04-12
WO2021145939A1 (fr) 2021-07-22
CN114342333B (zh) 2023-10-20

Similar Documents

Publication Publication Date Title
US11588682B2 (en) Common connection tracker across multiple logical switches
US20240015086A1 (en) Detecting failure of layer 2 service using broadcast messages
US12074731B2 (en) Transitive routing in public cloud
US10938594B1 (en) Transparent demilitarized zone providing stateful service between physical and logical networks
US11375005B1 (en) High availability solutions for a secure access service edge application
US11223494B2 (en) Service insertion for multicast traffic at boundary
US11196591B2 (en) Centralized overlay gateway in public cloud
US20230179474A1 (en) Service insertion at logical network gateway
US20230025586A1 (en) Network management services in a secure access service edge application
US10944673B2 (en) Redirection of data messages at logical network gateway
US20230026330A1 (en) Network management services in a point-of-presence
US20220030058A1 (en) Distributed service chain across multiple clouds
US20230026865A1 (en) Network management services in a virtual network
CN114342342B (zh) 跨多个云的分布式服务链
US10491466B1 (en) Intelligent use of peering in public cloud
EP3815311B1 (fr) Utilisation intelligente d'appairage dans un nuage public
US11909558B2 (en) Port mapping for bonded interfaces of ECMP group
US20190306086A1 (en) Incorporating layer 2 service between two interfaces of gateway device
US10313205B2 (en) Context-sensitive command whitelisting for centralized troubleshooting tool
CA3180645A1 (fr) Decharge de traitement de flux a l'aide d'identifiants de port virtuel
WO2020046686A1 (fr) Insertion de service au niveau d'une passerelle de réseau logique
WO2021145939A1 (fr) Zone démilitarisée transparente fournissant un service à états entre des réseaux physiques et logiques

Legal Events

Date Code Title Description
STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: UNKNOWN

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE INTERNATIONAL PUBLICATION HAS BEEN MADE

PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: REQUEST FOR EXAMINATION WAS MADE

17P Request for examination filed

Effective date: 20220131

AK Designated contracting states

Kind code of ref document: A1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

DAV Request for validation of the european patent (deleted)
DAX Request for extension of the european patent (deleted)
RAP3 Party data changed (applicant data changed or rights of an application transferred)

Owner name: VMWARE LLC

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: EXAMINATION IS IN PROGRESS

17Q First examination report despatched

Effective date: 20240503