Patent Grant
10795716
Typical physical networks contain several physical routers to perform L3 forwarding (i.e., routing). When a first machine wants to send a packet to a second machine located on a different IP subnet, the packet is sent to a router that uses a destination IP address of the packet to determine through which of its physical interfaces the packet should be sent. Larger networks will contain multiple routers, such that if one of the routers fails, the packets can be routed along a different path between the first machine and the second machine.
In logical networks, user-defined data compute nodes (e.g., virtual machines) on different subnets may need to communicate with each other as well. In this case, tenants may define a network for virtualization that includes both logical switches and logical routers. Methods for implementing the logical routers to adequately serve such virtualized logical networks in datacenters are needed.
Some embodiments provide a method for implementing a logical router in a network (e.g., in a datacenter). In some embodiments, the method is performed by a management plane that receives configuration data from an administrator and converts that configuration data into a desired network state and/or a central control plane that performs additional processing on the network state and distributes the desired network state as configuration data to forwarding elements (or to local control planes that directly manage the forwarding elements) that implement the logical network (including the logical router). The management plane and central control plane, in some embodiments, may both operate within a centralized network controller.
The management plane, in some embodiments, receives a definition of a logical router (e.g., through an application programming interface (API) and defines multiple routing components for the logical router. Each of these routing components is separately assigned a set of routes (e.g., a routing information base) and a set of logical interfaces.
In some embodiments, the several routing components defined for a logical router includes one distributed routing component and several centralized routing components. In addition, the management plane of some embodiments defines a logical switch for handling communications between the components internal to the logical router (referred to as a transit logical switch). The distributed routing component and the transit logical switch are implemented in a distributed manner by numerous machines within the datacenter, while the centralized routing components are each implemented on a single machine. Some embodiments implement the distributed components in the datapath of managed forwarding elements on the various machines, while the centralized routing components are implemented in VMs (or other data compute nodes) on their single machines. Other embodiments also implement the centralized components in the datapath of their assigned machine (e.g., in a datapath of a bare metal machine).
The centralized components, in some embodiments, may be configured in active-active or active-standby modes. In active-active mode, all of the centralized components are fully functional at the same time, and traffic can ingress or egress from the logical network through the centralized components using equal-cost multi-path (ECMP) forwarding principles (balancing the traffic across the various centralized components), so long as the connectivity of the centralized components to the external networks is the same across the components.
In some embodiments, the logical router is part of a two-tier logical network structure. The two-tier structure of some embodiments includes a single logical router for connecting the logical network to a network external to the datacenter (referred to as a provider logical router (PLR) and administrated by, e.g., the owner of the datacenter), and multiple logical routers that connect to the single logical router and do not separately communicate with the external network (referred to as tenant logical routers (TLRs) and administrated by, e.g., different tenants of the datacenter). Some embodiments implement the centralized components of the PLR in active-active mode whenever possible, and only use active-standby mode when stateful services (e.g., NAT, firewall, load balancer, etc.) are configured for the logical router. When the logical router is a TLR, some embodiments either use no centralized components or two centralized components in active-standby mode when stateful services are configured for the logical router.
The management plane of some embodiments additionally configures the routing tables for each of the logical router constructs (e.g., for the distributed component as well as for each centralized component). The configuration received by the management plane may include specifications of routes (e.g., static routes) for the logical router as well as connections of the logical router to other logical routers (e.g., connections of the TLRs to a PLR). Some embodiments automatically identify to which routing components' routing tables the received routes should be pushed, as well as how to propagate routes based on the connections with other logical routers. In addition, each route added to the routing table of a routing component has a route type (e.g., static route, connected route, etc.) as well as an administrative distance value. Administrative distance values are used in determining priorities between routes for the same network address or range of addresses.
Some embodiments additionally define a sub-type field for static routes, with different sub-types having different administrative distance values. For instance, some embodiments include static routes based on administrator configured static routes as a first sub-type having a first administrative distance value. Additionally, the connection of a logical switch directly to the logical router by an administrator results in a connected route in the routing table of the distributed component, as well as routes for the various centralized components. These routes for the centralized components are assigned a second static route sub-type in some embodiments, with a smaller default administrative distance value than the administrator-configured static routes. Lastly, when a TLR is connected to a PLR, some embodiments identify any logical switch subnets that are connected to the TLR and which should be advertised (via dynamic routing protocols) to the external network. In this case, rather than running a dynamic routing protocol between the two logical routers, the management plane (which is aware of both logical router configurations) automatically performs the route exchange while handling the fact that the PLR actually has separate routing tables for each of its separate routing components. Thus, the management plane adds routes for these logical networks to both the distributed routing component and each of the centralized routing components. These routes are classified as static routes of a third sub-type, having a larger administrative distance value than the administrator-configured static routes.
In some embodiments, the management plane generates these routing tables for the various routing components of the logical router, and passes this data to the central control plane. The central control plane of some embodiments is responsible for generating a forwarding information base (i.e., a set of final routes to use for forwarding packets) for each of the routing components based on the routing tables received from the management plane. To generate this forwarding information base, the central control plane identifies the route for each prefix with the lowest administrative distance (preferring connected routes above all other routes), then traverses the routing table to identify an output interface (output logical port) for each route remaining in the table. The central control plane then distributes the routing component data to local controllers operating at the forwarding elements that implement the logical routing components (e.g., a single local controller for each of the centralized routing components and numerous forwarding elements for the distributed routing component, including the local controller to which the centralized routing component configuration information was distributed).
The preceding Summary is intended to serve as a brief introduction to some embodiments of the invention. It is not meant to be an introduction or overview of all inventive subject matter disclosed in this document. The Detailed Description that follows and the Drawings that are referred to in the Detailed Description will further describe the embodiments described in the Summary as well as other embodiments. Accordingly, to understand all the embodiments described by this document, a full review of the Summary, Detailed Description and the Drawings is needed. Moreover, the claimed subject matters are not to be limited by the illustrative details in the Summary, Detailed Description and the Drawing, but rather are to be defined by the appended claims, because the claimed subject matters can be embodied in other specific forms without departing from the spirit of the subject matters.
The novel features of the invention are set forth in the appended claims. However, for purpose of explanation, several embodiments of the invention are set forth in the following figures.
Some embodiments provide a method for implementing a logical router in a network (e.g., in a datacenter). In some embodiments, the method is performed by a management plane that receives configuration data from an administrator and converts that configuration data into a desired network state and/or a central control plane that performs additional processing on the network state and distributes the desired network state as configuration data to forwarding elements (or to local control planes that directly manage the forwarding elements) that implement the logical network (including the logical router). The management plane and central control plane, in some embodiments, may both operate within a centralized network controller.
The management plane, in some embodiments, receives a definition of a logical router (e.g., through an application programming interface (API) and defines multiple routing components for the logical router. Each of these routing components is separately assigned a set of routes (e.g., a routing information base) and a set of logical interfaces.
In some embodiments, the several routing components defined for a logical router includes one distributed routing component and several centralized routing components. In addition, the management plane of some embodiments defines a logical switch for handling communications between the components internal to the logical router (referred to as a transit logical switch). The distributed routing component and the transit logical switch are implemented in a distributed manner by numerous machines within the datacenter, while the centralized routing components are each implemented on a single machine. Some embodiments implement the distributed components in the datapath of managed forwarding elements on the various machines, while the centralized routing components are implemented in VMs (or other data compute nodes) on their single machines. Other embodiments also implement the centralized components in the datapath of their assigned machine (e.g., in a datapath of a bare metal machine).
The centralized components, in some embodiments, may be configured in active-active or active-standby modes. In active-active mode, all of the centralized components are fully functional at the same time, and traffic can ingress or egress from the logical network through the centralized components using equal-cost multi-path (ECMP) forwarding principles (balancing the traffic across the various centralized components), so long as the connectivity of the centralized components to the external networks is the same across the components.
In some embodiments, the logical router is part of a two-tier logical network structure. The two-tier structure of some embodiments includes a single logical router for connecting the logical network to a network external to the datacenter (referred to as a provider logical router (PLR) and administrated by, e.g., the owner of the datacenter), and multiple logical routers that connect to the single logical router and do not separately communicate with the external network (referred to as tenant logical routers (TLRs) and administrated by, e.g., different tenants of the datacenter). Some embodiments implement the centralized components of the PLR in active-active mode whenever possible, and only use active-standby mode when stateful services (e.g., NAT, firewall, load balancer, etc.) are configured for the logical router. When the logical router is a TLR, some embodiments either use no centralized components or two centralized components in active-standby mode when stateful services are configured for the logical router.
The management plane of some embodiments additionally configures the routing tables for each of the logical router constructs (e.g., for the distributed component as well as for each centralized component). The configuration received by the management plane may include specifications of routes (e.g., static routes) for the logical router as well as connections of the logical router to other logical routers (e.g., connections of the TLRs to a PLR). Some embodiments automatically identify to which routing components' routing tables the received routes should be pushed, as well as how to propagate routes based on the connections with other logical routers. In addition, each route added to the routing table of a routing component has a route type (e.g., static route, connected route, etc.) as well as an administrative distance value. Administrative distance values are used in determining priorities between routes for the same network address or range of addresses.
Some embodiments additionally define a sub-type field for static routes, with different sub-types having different administrative distance values. For instance, some embodiments include static routes based on administrator configured static routes as a first sub-type having a first administrative distance value. Additionally, the connection of a logical switch directly to the logical router by an administrator results in a connected route in the routing table of the distributed component, as well as routes for the various centralized components. These routes for the centralized components are assigned a second static route sub-type in some embodiments, with a smaller default administrative distance value than the administrator-configured static routes. Lastly, when a TLR is connected to a PLR, some embodiments identify any logical switch subnets that are connected to the TLR and which should be advertised (via dynamic routing protocols) to the external network. In this case, rather than running a dynamic routing protocol between the two logical routers, the management plane (which is aware of both logical router configurations) automatically performs the route exchange while handling the fact that the PLR actually has separate routing tables for each of its separate routing components. Thus, the management plane adds routes for these logical networks to both the distributed routing component and each of the centralized routing components. These routes are classified as static routes of a third sub-type, having a larger administrative distance value than the administrator-configured static routes.
In some embodiments, the management plane generates these routing tables for the various routing components of the logical router, and passes this data to the central control plane. The central control plane of some embodiments is responsible for generating a forwarding information base (i.e., a set of final routes to use for forwarding packets) for each of the routing components based on the routing tables received from the management plane. To generate this forwarding information base, the central control plane identifies the route for each prefix with the lowest administrative distance (preferring connected routes above all other routes), then traverses the routing table to identify an output interface (output logical port) for each route remaining in the table. The central control plane then distributes the routing component data to local controllers operating at the forwarding elements that implement the logical routing components (e.g., a single local controller for each of the centralized routing components and numerous forwarding elements for the distributed routing component, including the local controller to which the centralized routing component configuration information was distributed).
The above introduces the concept of a two-tiered logical router configuration as well as the management plane assignment of route types and sub-types and the central control plane routing information base generation. In the following, Section I focuses on the overall high-level design of the logical router of some embodiments, while Section II describes the configuration of the various logical router components and their respective routing information bases by the management plane. Section III then describes the conversion of the routing information bases to forwarding information bases for these logical router components. Finally, Section IV describes the electronic system with which some embodiments of the invention are implemented.
I. Logical Router and Physical Implementation
The following discussion describes the design of logical routers for some embodiments as well as the implementation of such logical routers by the network controllers of some embodiments. Logical routers, in some embodiments, exist in three different forms. The first of these forms is the API view, or configuration view, which is how the logical router is defined by a user (e.g., a datacenter provider or tenant). The second view is the control plane, or management plane, view, which is how the network controller internally defines the logical router. Finally, the third view is the physical realization, or implementation of the logical router, which is how the logical router is actually implemented in the datacenter. That is, the logical router is an abstraction describing a set of functionalities (e.g., routing, NAT, etc.) that a user configures for the logical router. The logical router is then implemented by various machines in the datacenter based on instructions distributed to those machines by a set of network controllers, with the instructions generated by the network controllers according to the configuration provided by the user.
In the management plane/control plane view (referred to herein as the management plane view), the logical router of some embodiments may include one or both of a single DR and one or more SRs. The DR, in some embodiments, spans managed forwarding elements (MFEs) that couple directly to VMs or other data compute nodes that are logically connected, directly or indirectly, to the logical router. The DR of some embodiments also spans the gateways to which the logical router is bound. The DR, in some embodiments, is responsible for first-hop distributed routing between logical switches and/or other logical routers that are logically connected to the logical router. The SRs of some embodiments are responsible for delivering services that are not implemented in a distributed fashion (e.g., some stateful services).
In some embodiments, the physical realization of a logical router always has a DR (i.e., for first-hop routing). A logical router will have SRs if either (i) the logical router is a PLR, and therefore connects to external physical networks or (ii) the logical router has services configured that do not have a distributed implementation (e.g., NAT, load balancing, DHCP in some embodiments). Even if there are no stateful services configured on a PLR, some embodiments use SRs in the implementation to centralized the connection to the external network.
A. Single-Tier Logical Router
The detailed configuration of the northbound and southbound interfaces of the various router constructs 205-215 and their connections with the transit logical switch 220 will be described in further detail below. In some embodiments, the management plane generates separate routing information bases (RIBs) for each of the router constructs 205-215, and the central control plane subsequently generates forwarding information bases (FIBs) for each of the router constructs 205-215. That is, in addition to having separate objects created in the management/control plane, each of the router constructs 205 is treated as a separate router with separate routes.
Finally,
The two SRs 205 and 210 each operate on a different gateway machine 315 and 320. The gateway machines 315 and 320 are host machines similar to the machines 305 in some embodiments, but host SRs rather than user VMs. In some embodiments, the gateway machines 315 and 320 each include an MFE as well as the SR, in order for the MFE to handle logical switching as well as routing for the DR 215. For instance, packets sent from the external network 120 may be routed by the SR routing table on one of the gateway machines and then subsequently switched and routed (according to the DR routing table) by the MFE on the same gateway.
The SRs may be implemented in a namespace, a virtual machine, or as a VRF in different embodiments. In some embodiments, the SRs are implemented within the datapath of the MFE rather than as a separate entity on the host machine with the MFE. The SRs may operate in an active-active or active-standby mode in some embodiments, depending on whether any stateful services (e.g., firewalls) are configured on the logical router. When stateful services are configured, some embodiments require only a single active SR. In some embodiments, the active and standby service routers are provided with the same configuration, but the MFEs 310 are configured to send packets via a tunnel to the active SR (or to the MFE on the gateway machine with the active SR). Only if the tunnel is down will the MFE send packets to the standby gateway.
B. Multi-Tier Topology
The previous example illustrates only a single tier of logical router. For logical networks with multiple tiers of logical routers, some embodiments may include both DRs and SRs at each level, or DRs and SRs at the upper level (the PLR tier) with only DRs at the lower level (the TLR tier).
In some embodiments, any number of TLRs may be attached to a PLR such as the PLR 405. Some datacenters may have only a single PLR to which all TLRs implemented in the datacenter attach, whereas other datacenters may have numerous PLRs. For instance, a large datacenter may want to use different PLR policies for different tenants, or may have too many different tenants to attach all of the TLRs to a single PLR (because, e.g., the routing table for the PLR might get too big, or only a certain number of interfaces are supported for the PLR, or too much traffic would be bottlenecked at the SRs of the PLR). Part of the routing table for a PLR includes routes for all of the logical switch domains of its TLRs, so attaching numerous TLRs to a PLR creates several routes for each TLR just based on the subnets attached to the TLR. The PLR 405, as shown in the figure, provides a connection to the external physical network 435; some embodiments only allow the PLR to provide such a connection, so that the datacenter provider can manage this connection. Each of the separate TLRs 410-420, though part of the logical network 400, are configured independently (although a single tenant could have multiple TLRs if they so chose).
Thus,
The partially centralized implementation of the TLR 410 includes a DR 605 to which the logical switches 425 and 430 attach, as well as two SRs 610 and 615. As in the PLR implementation, the DR and the two SRs each have interfaces to a transit logical switch 620. This transit logical switch serves the same purposes as the switch 525, in some embodiments. For TLRs, some embodiments implement the SRs in active-standby manner, with one of the SRs designated as active and the other designated as standby. Thus, so long as the active SR is operational, packets sent by a data compute node attached to one of the logical switches 425 and 430 will be sent to the active SR rather than the standby SR. In some embodiments, the transit logical switch 530 only includes a single port to connect to the TLR 410, and this port connects to the first SR 610, unless the SR fails and the connection moves to the second SR 615. As such, this connection is shown as a dashed line in the figure.
The above figures illustrate the management plane view of logical routers of some embodiments. In some embodiments, an administrator or other user provides the logical topology (as well as other configuration information) through an API. This data is provided to a management plane, which defines the implementation of the logical network topology (e.g., by defining the DRs, SRs, transit logical switches, etc.). In addition, in some embodiments a user associates each logical router (e.g., each PLR or TLR) with a set of physical machines (e.g., a pre-defined group of machines in the datacenter) for deployment. For purely distributed routers, such as the TLR 405 as implemented in
In some embodiments, the user definition of a logical router includes a particular number of uplinks. Described herein, an uplink is a northbound interface of a logical router in the logical topology. For a TLR, its uplinks connect to a PLR (all of the uplinks connect to the same PLR, generally). For a PLR, its uplinks connect to external routers. Some embodiments require all of the uplinks of a PLR to have the same external router connectivity, while other embodiments allow the uplinks to connect to different sets of external routers. Once the user selects a group of machines for the logical router, if SRs are required for the logical router, the management plane assigns each of the uplinks of the logical router to a physical machine in the selected group of machines. The management plane then creates an SR on each of the machines to which an uplink is assigned. Some embodiments allow multiple uplinks to be assigned to the same machine, in which case the SR on the machine has multiple northbound interfaces.
As mentioned above, in some embodiments the SR may be implemented as a virtual machine or other container, or within the datapath of the MFE of the host machine to which the SR is assigned (e.g., as a VRF context). In some embodiments, the choice for the implementation of an SR may be based on the services chosen for the logical router and which type of SR best provides those services.
In addition, the management plane of some embodiments creates the transit logical switches. For each transit logical switch, the management plane assigns a unique VNI to the logical switch, creates a port on each SR and DR that connects to the transit logical switch, and allocates an IP address for any SRs and the DR that connect to the logical switch. Some embodiments require that the subnet assigned to each transit logical switch is unique within a logical L3 network topology having numerous TLRs (e.g., the network topology 400), each of which may have its own transit logical switch. That is, in
Some embodiments place various restrictions on the connection of logical routers in a multi-tier configuration. For instance, while some embodiments allow any number of tiers of logical routers (e.g., a PLR tier that connects to the external network, along with numerous tiers of TLRs), other embodiments only allow a two-tier topology (one tier of TLRs that connect to the PLR). In addition, some embodiments allow each TLR to connect to only one PLR, and each logical switch created by a user (i.e., not a transit logical switch) is only allowed to connect to one PLR or one TLR. Some embodiments also add the restriction that southbound ports of a logical router must each be in different subnets. Thus, two logical switches may not have the same subnet if connecting to the same logical router. Lastly, some embodiments require that different uplinks of a PLR must be present on different gateway machines. It should be understood that some embodiments include none of these requirements, or may include various different combinations of the requirements.
II. Rib Configuration for SR and DR
When a user configures a logical router (e.g., by configuring its interfaces and provisioning routes), this configuration is used by the management plane to configure the SRs and DR for the logical router. For instance, the logical router 115 of
In addition, as part of the configuration, the management plane of some embodiments generates a routing information base (RIB) for each of the logical router components. That is, although the administrator defines only a single logical router, the management plane generates separate RIBs for the DR and for each of the SRs. As described below, the central control plane of some embodiments converts this RIB into a forwarding information base (FIB) for each of the components. For the SRs of a PLR, in some embodiments the management plane generates the RIB initially (and the central control plane generates the FIB), but the physical implementation of the SR also runs a dynamic routing protocol process (e.g., BGP, OSPF, etc.) to supplement the routing table locally and perform the additional RIB to FIB conversion. In other embodiments, the central control plane does not generate even the initial FIB. Instead, the entire RIB is pushed to the SR (e.g., to the gateway host machine that hosts the SR), and a separate process operating on that gateway host machine (e.g., a local controller or other process) performs the RIB to FIB conversion.
The management plane 705 of some embodiments is responsible for receiving a configuration 725 for a logical router (possibly with additional logical network configuration, such as the connection of other logical routers, logical switches, etc.) from an administrator and generating an internal configuration 730 for the logical router. In some embodiments, the management plane 705 receives the logical router configuration through an API accessible by administrators of the network managed by the network control system 700 (e.g., a datacenter administrator, a tenant network administrator, etc.).
As shown, the logical router configuration may include a set of interfaces for the logical router as well as administrator-defined static routes. For example, referring to
In addition to the interfaces of the logical router and its connections to other logical forwarding elements, the configuration 725 received by the management plane 705 may include static routes for the logical router. Static routes may be provided by the administrator, with the input including a prefix to be routed, a next hop, and in some cases an output interface. In use, any packet with a destination IP address that matches the prefix (and does not match a route with a longer prefix) will be output through the given interface to the given next hop address.
The management plane 705, as stated, converts this received configuration data 725 into a set of internal configuration data 730 for the logical router. As described below by reference to
The configuration 730 also includes routing tables (RIBs) for each of the routing components. For instance, some embodiments define a connected route for each interface of a routing component that connects to a logical switch. In addition, the management plane defines various types of static routes for the components, with different types of static routes having different administrative distances. All routes, in some embodiments, include administrative distance values, used to determine priority, with larger values indicating lower priority types of route (i.e., if two routes exist for the same prefix, the one with a lower distance value is used). If multiple routes for the same prefix are in the RIB with the same distance value, traffic to these prefixes is spread across the different routes (e.g., using ECMP principles to balance the traffic evenly). The following indicate the different types of routes, with default administrative distance values in parentheses:
The second route 810 has a route type of static and a sub-type of MP_static (management plane static). As such, the administrative distance for the route is 2. In this case, the prefix 10.0.1.0/28 is for an advertised route for a TLR that connects to the PLR. These routes are also added to the SR with the northbound IP address of the DR as the next hop. Similar routes with the type TLR-NAT would be added for NAT routes advertised by the TLR.
The third route 815 is a static route of sub-type static (i.e., a route added as a static route through the API by a user/administrator). This route has an administrative distance of 1, routes the prefix 12.0.0.0/28, and specifies a physical router IP address (outside the logical network) as its next hop. Finally, the last route 820 is a connected route. In general, each SR will have a connected route for its downlink interface that connects to a transit logical switch. In this case, the transit logical switch subnet is 192.168.100.0/24, and the route specifies an output interface (the downward-facing interface of the SR) rather than a next hop address.
In some embodiments, the administrative distances for each route are default values for the route type and sub-type. However, some embodiments allow the administrator to override these default values for specific routes, either for routes of sub-type static (when configuring the route initially) or for all static routes (including MP_static, TLR-NAT, PLR-NAT, and LR_connected routes).
Returning to
The routing table processor 735 of some embodiments converts the received RIBs (input routing tables) for the logical routing components into FIB data (output routing tables) that is used to configure the MFEs that implement the routing components. For a given routing component, the output routing table will have a maximum of one route for a particular network address prefix, using the administrative distances and route types to identify preference when a routing component has multiple routes for a particular prefix in its RIB. Some embodiments prefer connected routes, then select the static route for a prefix with the minimum administrative distance. Thus, LR-connected routes are preferred to all other types of static routes, with user-entered static routes preferred to MP_static, TLR-NAT, and PLR-NAT static routes (assuming default administrative distances).
In addition, the routing table processor 735 of some embodiments identifies a final action for each route, which is either a drop action (dropping packets sent to addresses matching the prefix) or an output interface. The routing table processor 735 performs recursive route traversal to identify these final actions. That is, the routing table processor 735, for each route that only has a next hop address, identifies the route in the routing table for that next hop address, and determines if an output interface or drop action is specified for that route. If such an action is specified, the action is applied to the original route. Otherwise, the process identifies another route in the table based on the next hop address of the second route, and continues on until it has identified an action to apply to the original route. The operations of the routing table processor will be described in greater detail below in Section III.
As shown, the routing table processor 735 outputs FIB data 755 for the logical routing components (SRs, DR), which is a routing table specifying actions for each route. This data, along with other logical network configuration data (e.g., logical switch configuration, ingress and egress ACL configurations for logical switches and routers, etc.), is sent to the local controllers 715 and 720 through the interface 750. The interface 750 with the local controllers, or a module separate from this interface, determines which MFEs need which configuration data using the machine ID information 745. The central control plane provides DR configuration information to local controllers 715 and 720 at both the appropriate host machines 760 (which host data compute nodes that send packets through the logical network to which this DR belongs) and the appropriate gateway host machines 765 at which the SRs are implemented. The SR configuration data, on the other hand, is only distributed to the local controllers 720 at the appropriate gateway host machines 765.
In should be noted that, in some embodiments, the local controllers at the SRs of the PLRs (that use dynamic routing protocols) merge the routing table configuration received from the central control plane with the routes learned from the physical routers (via the dynamic routing protocols). The SR locally calculates its FIB based on the incorporation of these dynamic routes in order to expedite route convergence, rather than sending the learned routes back to the centralized controller for recalculation.
A. DR Configuration
In some embodiments, the DR is always located on the southbound side (i.e., facing the data compute nodes of the logical network, rather than facing the external physical network) of the logical router implementation. Unless the logical router has no centralized component, the uplinks of the logical router will not be configured for the DR, whose northbound interfaces instead couple to the transit logical switch that is part of the logical router.
The northbound side of the logical router 915 has two uplinks, U1 and U2. The first uplink U1 has an IP address of 192.168.1.252 and connects to a first physical router 920 with an IP address of 192.168.1.252. The second uplink U2 has an IP address of 192.168.2.253 and connects to a second physical router 925 with an IP address of 192.168.2.252. The physical routers 920 and 925 are not actually part of the logical network, but rather connect the logical network to the external network. Though in the illustrated case each of the uplinks connects to a single, different physical router, in some cases each of the uplinks will connect to the same set of several physical routers. That is, both U1 and U2 might both connect to both of the physical routers 920 and 925. Some embodiments require that each of the external routers to which the uplinks connect provide the same connectivity, although this is not the case in the illustrated example. Instead, the first physical router 920 connects to the subnet 10.0.0.0/8, while the second router 925 connects to both the subnet 10.0.0.0/8 and 11.0.0.0/8.
For a logical router with a distributed component, some embodiments configure the DR as follows. The southbound interfaces are configured in the same way as the southbound interfaces of the logical router. These interfaces are those that connect to a logical switch in the logical topology, or to a lower-level logical router (e.g., the southbound interfaces of a PLR may connect to TLRs). The DR of some embodiments is allocated a single northbound interface, which is assigned an IP address and a MAC address. Assuming the logical router has one or more SRs, the northbound interface of the DR connects to a transit logical switch.
The RIB of the DR is assigned connected routes based on the subnets configured on its various southbound and northbound interfaces. These are the subnets configured for (i) the transit logical switch configured between the DR and SR components of the logical router, and (ii) any logical switches on its southbound interfaces. These logical switches on the southbound interfaces may be user-defined logical domains to which data compute nodes connect, or transit logical switches located between the DR of a PLR and any TLRs that connect to the PLR.
In addition, any static routes that egress from an uplink of the logical router are included in the RIB of the DR. In some embodiments, these routes are added to the DR as configured by the user, while in other embodiments these routes are modified such that the next-hop IP address is set to that of the uplink's SR. For example, a static route “a.b.c.0/24 via 192.168.1.252” (192.168.1.252 being an address of an external physical network router) is modified to be “a.b.c.0/24 via [IP of SR southbound interface]”. Static routes that egress from a southbound interface of the logical router, on the other hand, are included in the RIB of the DR unmodified. In some embodiments, for each SR of the logical router, a default route (i.e., a route for 0.0.0.0/0) is added to the RIB of the DR. In addition, in some embodiments, dynamic routes learned by a particular SR are added to the RIB of the DR. However, for TLRs, the SRs do not run a dynamic routing protocol in some embodiments.
Using the rules of some embodiments for generating the RIB, the RIB of the DR 1005 includes three connected routes, for the logical switch domains connected to the DR (1.1.1.0/24, 1.1.2.0/24, and 192.168.100.0/24). In addition, some embodiments include static connected routes for the subnets on which the uplinks are located, as well as any static routes configured by the administrator, and default routes pointing to both of the SR downlink IP addresses.
B. SR Configuration
As with the DR of a logical router, the management plane also configures each SR of the logical router with a separate RIB and interfaces. As described above, in some embodiments SRs of both PLRs and TLRs may deliver services (i.e., functionalities beyond simply routing, such as NAT, firewall, load balancing, etc.) and the SRs for PLRs also provide the connection between the logical network and external physical networks. In some embodiments, the implementation of the SRs is designed to meet several goals. First, the implementation ensures that the services can scale out—that is, the services assigned to a logical router may be delivered by any of the several SRs of the logical router. Second, some embodiments configure the SR in such a way that the service policies may depend on routing decisions (e.g., interface-based NAT). Third, the SRs of a logical router have the ability to handle failure (e.g., of the physical machine on which an SR operates, of the tunnels to that physical machine, etc.) among themselves without requiring the involvement of a centralized control plane or management plane (though some embodiments allow the SRs to operate at reduced capacity or in a suboptimal manner). Finally, the SRs ideally avoid unnecessary redirecting amongst themselves. That is, an SR should forward packets to the external physical network if it has the ability do so locally, only forwarding the packet to a different SR if necessary. Of course, the forwarding between SRs should avoid packet loops.
As shown in
The local northbound interfaces, in some embodiments, are those through which a packet can egress directly from the SR (e.g., directly to the physical network). An interface configured based on the uplink (or one of the uplinks) assigned to the SR is a local interface. On the other hand, an interface configured based on one of the other uplinks of the logical router assigned to a different SR is referred to as a dummy interface. Providing the SR with configuration for the dummy interfaces allows for the first-hop MFEs to send packets for any of the uplinks to any of the SRs, with that SR able to process the packets even if the packet is not destined for its local interface. Some embodiments, after processing a packet at one of the SRs for a dummy interface, forward the packet to the appropriate SR where that interface is local, in order for the other SR to forward the packet out to the external physical network. The use of dummy interfaces also allows the centralized controller (or set of controllers) that manages the network to push service policies that depend on routing decisions to all of the SRs, thereby allowing services to be delivered by any of the SRs. Some embodiments, however, do not use dummy interfaces, in which case only one northbound interface is assigned to each SR.
In some embodiments the SRs exchange routing information with the physical network (e.g., using a route advertisement protocol such as BGP or OSPF). One goal of this route exchange is that irrespective of which SR routes a packet towards the physical network, the routing decision should always point to either a local interface of the SR or a dummy interface that corresponds to an uplink of the logical router on a different SR. Thus, the policies associated with the logical router uplink can be applied by the SR even when the uplink is not assigned to that SR, enabling the scale out of stateful services. In some embodiments, when dummy interfaces are used, the routes received from a peer SR will have a larger administrative distance value than routes learned directly from a physical next-hop router, thereby ensuring that a SR will send a packet to its peer SR only when it cannot send the packet directly to a physical network router.
For a logical router that has one or more centralized components, some embodiments configure the SR as follows. For northbound interfaces, the SR has the same number of such interfaces as the logical router, and these interfaces each inherit the IP and MAC address of the corresponding logical router interfaces. A subset of these interfaces are marked as local interfaces (those for which the uplink is assigned to the SR), while the rest of the interfaces are marked as dummy interfaces. In some embodiments, the service policies defined for the logical router are pushed equivalently to all of the SRs, as these are configured in the same way from the network and interface perspective. The dynamic routing configuration for a particular logical router port/uplink are transferred to the local interface of the SR to which that particular uplink is assigned.
Each SR, as mentioned, is assigned a single southbound interface (also a local interface) that connects to a transit logical switch, with each SR's southbound interface connecting to the same transit logical switch. The IP addresses for each of these southbound interfaces is in the same subnet as the northbound interface assigned to the DR (that of the transit logical switch). Some embodiments differentiate the assignment of IP addresses between the SRs depending on whether the SRs are in active-active or active-standby mode. For active-active mode (i.e., when all of the SRs are treated as equals for routing purposes), different IP and MAC addresses are assigned to the southbound interfaces of all of the SRs. On the other hand, in active-standby mode, the same IP is used for both of the southbound interfaces of the two SRs, while each of the interfaces is assigned a different MAC address.
As indicated in the above subsection regarding DRs, users may configure static routes for the logical router. A static route (or a connected route) of the logical router that egresses from an uplink is copied to the RIB of the SR. The distance metric for such a route is unmodified if the uplink through which the route egresses is assigned to the SR; however, if the uplink is a dummy interface on the SR, then some embodiments add a value to this metric so that the SR will prefer a route that egresses from its local interface when the network can be reached without redirecting the packet to a different SR through a dummy interface. In other embodiments, the static routes are only propagated to the SRs to which they apply (e.g., if the SRs have different connectivity to the external network).
In addition, the SRs (of a top-level logical router) may learn dynamic routes and place these in their RIB (though some embodiments perform this locally, without involving the centralized control plane or management plane). In some embodiments, the dynamic routes learned from peer SRs are installed without this adjustment of the distance metric, because by default the metric for routes learned from IBGP (SR to SR peering) or OSPF are larger than the metric for routes learned from EBGP.
For each southbound interface of the logical router, some embodiments add a route for the corresponding network to the RIB of each SR. This route points to the northbound DR interface as its next-hop IP address. Furthermore, any other routes configured for the logical router that egress from the southbound interface are copied to the SR with the same northbound DR interface as the next-hop IP address.
Returning to the example of
Using the rules of some embodiments, the RIB for each SR will include a connected route for the subnet of the transit logical switch (192.168.100.0/24), static routes for any applicable user-entered static routes, and static connected routes for the two logical switches (for 1.1.1.0/24 and 1.1.2.0/24) that are attached to the DR 605.
C. Management Plane Processes
As shown, the process 1100 begins by receiving (at 1105) a specification of a PLR. The specification of a PLR is based on administrator input to define the PLR (e.g., an administrator employed by the owner of the datacenter). In some embodiments, this specification includes definitions of any services the PLR should provide, whether the PLR will be configured in active-active or active-standby mode (though some embodiments automatically use active-active mode unless stateful services are configured), how many uplinks are configured for the PLR, the IP and MAC addresses of the uplinks, the L2 and L3 connectivity of the uplinks, the subnets of any southbound interfaces of the PLR (one interface if the PLR is intended for a two-tier topology, and any number of interfaces if user logical switches will connect directly in a single-tier topology), any static routes for the RIB of the PLR, as well as other data. It should be understood that different embodiments may include different combinations of the listed data or other data in the configuration data for a PLR.
The process 1100 then defines (at 1110) a DR using this configuration data. This assumes that the PLR will not be completely centralized, in which case no DR is generated by the management plane. For the southbound interface of the DR, the management plane uses the southbound interface configuration of the PLR. That is, the IP address and MAC address for the DR are those specified for the logical router.
In addition, the process assigns (at 1115) each uplink specified for the PLR to a gateway machine. As described above, some embodiments allow (or require) the user to specify a particular set of physical gateway machines for the location of the SRs of the logical router. In some embodiments, the set of gateway machines might be together within a particular rack or group of racks of servers, or are otherwise related, with tunnels connecting all of the machines in a set. The management plane then assigns each of the uplinks to one of the gateway machines in the selected set. Some embodiments allow multiple uplinks to be assigned to the same gateway machine (so long as the logical router does not have only two uplinks configured in active-standby mode), while other embodiments only allow a single uplink per gateway machine for the PLR irrespective of whether in active-active or active-standby.
After assigning the uplinks to gateway machines, the process 1100 defines (at 1120) a SR on each of the selected gateway machines. For each SR, the process uses the configuration for the uplink assigned to that gateway machine as the configuration for the northbound interface of the SR. This configuration information includes the IP and MAC address of the uplink, as well as any uplink-specific policies. It should be understood that, for situations in which different policies and/or L3 connectivity are allowed and used between the different uplinks, some embodiments also configure dummy interfaces on the SRs in order to redirect packets if needed.
The process additionally defines (at 1125) a transit logical switch to connect the defined SRs and DR. In some embodiments, the management plane assigns a unique VNI (logical switch identifier) to the transit logical switch. In addition, some embodiments require that the subnet assigned to the transit logical switch be unique within the logical network topology. As such, the transit logical switch must use a subnet different from any user-defined logical switches that interface directly with the PLR, as well as all transit logical switches between the PLR and any TLRs that connect to the PLR, all transit logical switches within these TLRs, and any user-defined logical switches that connect to these TLRs.
Next, the process 1100 assigns (at 1130) a northbound interface to the DR. The northbound interface, in some embodiments, is assigned both a MAC address and an IP address (used for packets sent internally between the components of the PLR). In some embodiments, the IP address is in the subnet that was assigned to the transit logical switch defined at 1125. The configuration of the transit logical switch includes an association of this MAC address with one of its logical ports.
The process then determines (at 1135) whether the PLR is configured in active-active mode (or active-standby mode). As noted above, in some embodiments, this determination is made by the administrator as part of the configuration settings for the PLR. In other embodiments, the management plane automatically defines the SRs in active-active configuration for PLRs unless stateful services are set up, in which case the SRs are defined in active-standby mode.
When the PLR is configured in active-standby mode, the process assigns (at 1140) southbound interfaces of each of the two SRs (or more than two SRs, if there are multiple standbys). In the active-standby case, these southbound interfaces all have the same IP address, which is in the subnet of the transit logical switch defined at operation 1125. Although the two interfaces receive the same IP address, the MAC addresses assigned are different, so as to differentiate the two as destinations for northbound packets routed by the DR.
The process then assigns (at 1145) one of the SRs as active and one of the SRs as standby. Some embodiments make this determination randomly, while other embodiments attempt to balance the assignment of active and standby SRs across the gateway machines, as described in greater detail in U.S. Patent Publication 2015/0063364, which is incorporated herein by reference. The SR assigned as active will respond to ARP requests for the southbound interface, and will advertise prefixes to the external physical network from its northbound interface. The standby SR, on the other hand, will not respond to ARP requests (so as to avoid receiving northbound traffic), and will not advertise prefixes (but will maintain a BGP session in order to receive routes from the external network in case of failure of the active SR.
Lastly, the process 1100 generates (at 1150) separate RIBs for the DR and for each of the SRs. The separate RIBs are generated based on the configuration data in the manner described in the previous subsections, as well as below in Section III. The process then ends. In some embodiments, the central control plane also calculates the FIB centrally, while in other embodiments the local control planes (operating on the host and gateway machines) performs the RIB traversal to generate the FIB to use in actual forwarding of packets by the logical router components. In either case, the RIB is updated on the SRs based on the dynamic routes learned from the external network, and that data is propagated to the DR via central controllers.
On the other hand, when the PLR is configured in active-active (ECMP) mode, the process assigns (at 1155) southbound interfaces of each of the SRs. In the active-active cases, these southbound interfaces are each assigned different IP addresses in the subnet of the transit logical switch defined at operation 1125, as well as different MAC addresses. With different IP addresses, each of the SRs can handle northbound packets based on the IP address selected for a given packet by the DR pipeline in a host machine.
Next, the process assigns (at 1160) ranks to the SRs. As described in detail below, the SRs use the ranks in case of failover to determine which SR will take over responsibilities for a failed SR. In some embodiments, the next-highest ranked SR takes over for a failed SR by taking over its southbound interfaces so as to attract northbound traffic that would otherwise be sent to the IP address of the failed SR.
Finally, the process generates (at 1165) separate RIBs for the DR and for each of the SRs. The separate RIBs are generated based on the configuration data in the manner described in the previous subsections, as well as below in Section III. The process then ends. In some embodiments, the central control plane also calculates the FIB, while in other embodiments the local control planes (operating on the host and gateway machines) performs the RIB traversal to generate the FIB to use in actual forwarding of packets by the logical router components. In either case, the RIB is updated on the SRs based on the dynamic routes learned from the external network, and that data is propagated to the DR via central controllers.
The above description of
As shown, the process begins by receiving (at 1205) a specification of a TLR. The specification of a TLR is based on administrator input to define the TLR (e.g., an administrator employed by a tenant of the datacenter). In some embodiments, this specification includes definitions of any services the TLR should provide, which PLR the TLR should connect to through its uplink, any logical switches that connect to the TLR, IP and MAC addresses for the interfaces of the TLR, any static routes for the RIB of the TLR, as well as other data. It should be understood that different embodiments may include different combinations of the listed data or other data in the configuration data for the TLR.
The process 1200 then determines (at 1210) whether the TLR has a centralized component. In some embodiments, if the TLR does not provide stateful services, then no SRs are defined for the TLR, and it is implemented only in a distributed manner. On the other hand, some embodiments require SRs in active-standby mode when stateful services are provided, as shown in this figure.
When the TLR does not provide stateful services or otherwise require a centralized component, the process defines (at 1215) a DR using the specification of the logical router for both the southbound and northbound interfaces. The DR may have numerous southbound interfaces, depending on how many logical switches are defined to connect to the TLR. On the other hand, some embodiments restrict TLRs to a single northbound interface that sends packets to and receives packets from a PLR. The process also generates (at 1220) a RIB for the DR. The RIB for the DR will include all of the routes for the logical router, generated as described above.
On the other hand, when the TLR provides stateful services or requires a centralized component for other reasons, the process defines (at 1225) a DR using the received configuration data. For the southbound interfaces of the DR, the management plane uses the southbound interface configurations of the TLR. That is, the IP address and MAC address for each southbound interface are those specified for the ports of the logical router to which the various logical switches couple.
In addition, the process assigns (at 1230) the uplink specified for the TLR to two gateway machines. While some embodiments allow TLRs to operate in active-active mode with multiple uplinks, the process 1200 is for embodiments that restrict the TLRs to a single uplink (also referred to as a router link, as the link interconnects the TLR to another logical router) in active-standby mode. As described above, some embodiments allow (or require) the user to specify a particular set of physical gateway machines for the location of the SRs of the logical router. In some embodiments, the set of gateway machines might be together within a particular rack or group of racks of servers, or are otherwise related, with tunnels connecting all of the machines in a set. The management plane then assigns the uplink to two of the gateway machines in the selected set.
After assigning the uplinks to gateway machines, the process 1200 defines (at 1235) a SR on each of the two gateway machines. For each SR, the management plane uses the configuration for the single uplink as the configuration for the northbound interface of the SR. As there is only one northbound interface, the process applies the same configuration to both of the SRs. That is, not only is the same IP address used for both northbound interfaces, but the services on the interfaces are configured in the same manner as well. However, different MAC addresses are used for the northbound interfaces, so as to differentiate the active and standby SRs.
The process additionally defines (at 1240) a transit logical switch to connect the defined SRs and DR. In some embodiments, the management plane assigns a unique VNI (logical switch identifier) to the transit logical switch. In addition, some embodiments require that the subnet assigned to the transit logical switch be unique among the logical network topology. As such, the management plane must assign the transit logical switch a subnet different than any of the user-defined logical switches that interface with the TLR, as well as any transit logical switches between the TLR (or other TLRs) and the PLR, as well as all transit logical switches within other TLRs that connect to the same PLR, the transit logical switch within the PLR, and the user-defined logical switches that connect to the other TLRs.
Next, the process assigns (at 1245) a northbound interface to the DR. This interface, in some embodiments, is assigned both a MAC address and an IP address (used for packets sent internally between the components of the TLR). In some embodiments, the IP address is in the same subnet that was assigned to the transit logical switch at 1140. The process also assigns (at 1250) southbound interfaces of each of the two SRs. As this is an active-standby configuration, these southbound interfaces have the same IP address, which is in the subnet of the transit logical switch defined at operation 1140. Although the two interfaces receive the same IP address, the MAC addresses assigned are different, so as to differentiate the two as destinations for northbound packets routed by the DR.
The process 1200 then assigns (at 1255) one of the SRs as active and one of the SRs as standby. Some embodiments make this determination randomly, while other embodiments attempt to balance the assignment of active and standby SRs across the gateway machines. The SR assigned as active will respond to ARP requests for the southbound (from the DR of this TLR) and northbound (from the DR of the PLR) interfaces. The standby SR, on the other hand, will not respond to ARP requests (so as to avoid receiving northbound or southbound traffic).
Next, the process generates (at 1260) separate RIBs for the DR and for each of the SRs. The separate RIBs are generated based on the configuration data in the manner described in the previous subsections, as well as below in Section III. In some embodiments, the central control plane also calculates the FIB centrally, while in other embodiments the local control planes (operating on the host and gateway machines) perform the RIB traversal to generate the FIB to use in actual forwarding of packets by the logical router components. In either case, the RIB is updated on the SRs based on the dynamic routes learned from the external network, and that data is propagated to the DR via central controllers.
Irrespective of whether the TLR is generated with or without SRs, the process 1200 defines (at 1265) another transit logical between the TLR and the PLR to which it connects. This transit logical switch has a unique VNI, and a subnet to which the uplink IP address of the TLR belongs. In addition, an interface on the DR of the PLR is created in the same subnet to connect to the transit logical switch. The process then ends.
It should be understood that while the processes 1100 and 1200 illustrate a specific order for performing these various operations, these processes are merely conceptual. In various different embodiments, the management plane may perform the actual operations in various different orders, or even perform some of the operations in parallel. For instance, the management plane could define the transit logical switch first, prior to defining the SR or DR at all, could define all of the logical router components completely before assigning them to separate physical machines, etc.
III. RIB to FIB Conversion
As indicated above, in some embodiments the management plane receives a logical router configuration and generates (i) one or more logical router constructs for each logical router and (ii) a routing information base (RIB) for each logical router construct. In some embodiments, the calculation of a forwarding information base (FIB) from the RIB may be performed by the centralized control plane, as shown in
The central control plane processes will be described in part by reference to an example shown in
This data is received by the management plane, which defines logical routing components for the logical routers and generates routing tables (RIBs) for each component.
The management plane also defines the DR 1425 and two SRs 1430 and 1440 (one for each uplink) for the PLR 1305. The DR 1425 has the one south-facing interface for the TLR 1310, in addition to an interface P1 defined by the management plane. This interface P1 connects to a transit logical switch 1445 with a subnet 169.0.0.0/30, to which south-facing interfaces P2 and P3 of the three SRs 1430 and 1440 also connect. These three interfaces P1-P3 have, in turn, IP addresses of 169.0.0.1, 169.0.0.2, and 169.0.0.3. Each of the uplinks U1 and U2 is defined on one of the SRs (no dummy interfaces are defined in this example).
The management plane processes this configuration data 1505 as well as the input logical network configuration 1300 to generate RIB output 1500 for each of the routing components of the PLR (the RIB for the DR 1405 of the TLR 1310 is not shown). The RIB 1515 for the first SR 1430 includes eight routes in this simplified example. The first route (the order of the routes is not meaningful) is the default route 0.0.0.0/0 via 1.1.3.1, which is classified as a static route with the sub-type static, and therefore has an administrative distance of 1. The other static routes with next hop addresses of 1.1.3.1 are also added to the RIB 1515—the route for 172.16.0.0/16 has the default administrative distance, but the route for 1.1.5.0/24 has an administrative distance of 3 as the administrator specifies this value through the configuration data.
The RIB 1515 also includes static routes of sub-type MP_static for the advertised routes from the TLR, for 1.1.5.0/24 and 1.1.6.0/24. These routes are automatically propagated to the SRs with the northbound facing interface of the DR as the next hop, and have a default administrative distance of 2. In addition, a route for the transit logical switch 192.168.10.0/31 connected to the DR is added to the SR RIB 1515, as a static route of sub-type LR-connected, with an administrative distance of 0. Lastly, two connected routes are defined that specify output interfaces, with the uplink U1 connected to the subnet 1.1.3.0/30 and the internal southbound interface P2 connected to the transit logical switch subnet 169.0.0.0/30.
The RIB 1520 for the second SR 1440 includes seven routes, because there is one fewer user-entered static route with a next hop of 1.1.4.1. Specifically, the RIB 1520 includes a default route 0.0.0.0/0 via 1.1.4.1 and the other static route 10.0.0.0/8 via 1.1.4.1, with the latter having an administrative distance of 5. The same two static routes for 1.1.5.0/24 and 1.1.6.0/24 with sub-type MP_static as in the RIB 1515 are also present, as well as the static sub-type LR-connected route for 192.168.10.0/31. Lastly, two connected routes are defined that specify output interfaces, with the uplink U2 connected to the subnet 1.1.4.0/30 and the internal southbound interface P3 connected to the transit logical switch subnet 169.0.0.0/30.
For the RIB 1525 of the DR, all five of the user-entered static routes are present. Some embodiments add these routes as specified, with the user-entered next hop IP addresses (as shown in the figure). On the other hand, some embodiments automatically use the appropriate southbound SR interface (or interfaces, if multiple SRs have the same external connectivity) for the next hop IP addresses. The RIB 1525 also has static sub-type MP_static routes for each of the advertised prefixes 1.1.5.0/24 and 1.1.6.0/24, as well as static sub-type LR-connected routes for the external subnets 1.1.3.0/30 and 1.1.4.0/30. Lastly, the DR has two connected routes, for its internal interface P1 and its southbound interface with the TLR, D1.
The process 1700 then selects (at 1710) a prefix for which the RIB has at least one route. While the automatically-generated routes should not create multiple routes for the same prefix (so long as the various logical switch subnets of the logical network are assigned correctly), user-entered static routes may overlap with the automatically-generated routes. In the example, the RIB 1515 includes an automatically-generated MP_static route for 1.1.5.0/24 as well as a user-entered static route for this same prefix.
The process determines (at 1715) whether a connected route for the prefix exists in the RIB. In some embodiments, connected routes take precedence over all other routes. As such, when a connected route exists in the RIB for a prefix, the process adds (at 1720) this route to the FIB. The process also marks (at 1725) any static routes for the selected prefix as not in use. Such routes will not be added to the FIB. In the example of
When no connected route exists in the RIB for a selected prefix, the process adds (at 1730) the static route for the prefix with the lowest administrative distance to the FIB, and marks (at 1735) any other static routes for that prefix as not in use. Because this process is performed by the central control plane for an initial router configuration, only static and connected routes are possible. Some embodiments also incorporate dynamic routes learned by the SRs through route exchange protocols (e.g., BGP, OSPF, etc.) with external physical routers. In the example figure, the RIB 1515 has both a user-entered static route for 1.1.5.0/24 as well as an automatically-generated MP_static route for this prefix. Because the user-entered static route has a (non-default) administrative distance value of 3, the MP_static route with a next hop of 169.0.0.1 is preferred for the FIB 1615. The RIB 1525 for the DR also has two routes for 0.0.0.0/0 (i.e., two next hop IP addresses), which share the same administrative distance. In this case, both routes are added to the FIB and equal-cost multi-path (ECMP) routing will be used to select one of the next hop addresses.
In addition to identifying a single route for each prefix, the central control plane performs route traversal in some embodiments so that each route specifies an action (either dropping a packet or outputting the packet to a specific interface).
As shown, the process 1800 begins by selecting (at 1805) a route in the FIB. As this process 1800 is performed after the process 1700, the FIB has been narrowed down to a single route per prefix. The process then determines (at 1810) whether the selected route specifies an output interface or to drop traffic sent to addresses in the prefix. Both of these options are final actions that indicate how to process a received packet. As such, when such an action is specified by the route, the process keeps (at 1815) the selected route as is and proceeds to 1850, which is described below. While the example does not include any routes specifying to drop traffic, the connected routes for each of the routing components specify output interfaces. As such, these routes are added to the FIB unmodified.
However, when the selected route does not specify such a final action (instead specifying only a next hop address), the process performs route traversal to identify a final action (e.g., either a next hop address and output interface, or a drop action). The process 1800 identifies (at 1820) a route in the FIB for the current next hop address of the selected route. For instance, the RIB 1515 includes a route 192.168.10.0/31 via 169.0.0.1. In this case the next hop address is 169.0.0.1, and the route traversal process identifies the route for 169.0.0.0/30 as the route for this next hop address (i.e., this is the most specific route matched by the address, or the route for the longest matching prefix).
The process 1800 then determines (at 1825) whether the identified route specifies to drop traffic matching the prefix. If so, the process sets (at 1830) the selected route to drop traffic (i.e., so that the route specifies a drop action) and removes the next hop address from the route. When a router drops a packet, the next hop address is not used and thus need not be stored as part of the configuration data. The process then proceeds to 1850. As mentioned, in the example, none of the routes specify a drop action.
If the identified route for the current next hop address does not specify a drop action, the process determines (at 1735) whether the identified route specifies an output interface (i.e., whether the route specifies a logical router port to which to output packets). In the example, all of the connected routes specify output interfaces (i.e., the port of the routing component to which the routed subnet is connected). When an output interface is specified, the process sets (at 1840) the specified output interface for the selected route, and proceeds to 1850. For instance, the route 10.0.0.0/8 via 1.1.4.1 in the RIB 1520 becomes 10.0.0.0/8 via 1.1.4.1 output to U2 in the FIB 1620 because 1.1.4.1 matches the route 1.1.4.0/30 output to U2.
However, if the identified route for the current next hop address does not specify either a drop action or an output interface, then the route must specify a next hop address, which is not dispositive. Thus, the process sets (at 1845) the next hop address of the identified route as the current next hop address of the selected route (for which a final action is being determined), then proceeds to 1820 to determine whether a final action can be identified using the new next hop address. As an example, the route 10.0.0.0/8 via 1.1.4.1 in the RIB 1525 becomes 10.0.0.0/8 via 169.0.0.3 output to P1 in the FIB 1530. The next hop address 1.1.4.1 matches the route 1.1.4.0/30 via 169.0.0.3, which only specifies a next hop address. This next hop address 169.0.0.3 is used as the next hop address for the route for 10.0.0.0/8, and it matches the route 169.0.0.0/30 output to P1, which is a final action for the route.
Once an action is identified for the route, the process determines (at 1850) whether more routes remain in the FIB for processing. Once all routes have final actions, the process 1800 ends.
IV. Electronic System
Many of the above-described features and applications are implemented as software processes that are specified as a set of instructions recorded on a computer readable storage medium (also referred to as computer readable medium). When these instructions are executed by one or more processing unit(s) (e.g., one or more processors, cores of processors, or other processing units), they cause the processing unit(s) to perform the actions indicated in the instructions. Examples of computer readable media include, but are not limited to, CD-ROMs, flash drives, RAM chips, hard drives, EPROMs, etc. The computer readable media does not include carrier waves and electronic signals passing wirelessly or over wired connections.
In this specification, 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. Also, in some embodiments, multiple software inventions can be implemented as sub-parts of a larger program while remaining distinct software inventions. In some embodiments, multiple software inventions can also be implemented as separate programs. Finally, any combination of separate programs that together implement a software invention described here is within the scope of the invention. In some embodiments, 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.
The bus 1905 collectively represents all system, peripheral, and chipset buses that communicatively connect the numerous internal devices of the electronic system 1900. For instance, 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.
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 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 electronic system. The permanent storage device 1935, on the other hand, is a read-and-write memory device. This device is a non-volatile memory unit that stores instructions and data even when the electronic 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.
Other embodiments use a removable storage device (such as a floppy disk, flash drive, etc.) as the permanent storage device. Like 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. In some embodiments, the invention's 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 electronic 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 electronic 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.
Finally, as shown in
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). Some examples of 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. 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.
While the above discussion primarily refers to microprocessor or multi-core processors that execute software, some embodiments are performed by one or more integrated circuits, such as application specific integrated circuits (ASICs) or field programmable gate arrays (FPGAs). In some embodiments, such integrated circuits execute instructions that are stored on the circuit itself.
As used in this specification, the terms “computer”, “server”, “processor”, and “memory” all refer to electronic or other technological devices. These terms exclude people or groups of people. For the purposes of the specification, the terms display or displaying means displaying on an electronic device. 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 signals.
This specification refers throughout to computational and network environments that include virtual machines (VMs). However, virtual machines are merely one example of data compute nodes (DCNs) or data compute end nodes, also referred to as addressable nodes. DCNs may include non-virtualized physical hosts, virtual machines, containers that run on top of a host operating system without the need for a hypervisor or separate operating system, and hypervisor kernel network interface modules.
VMs, in some embodiments, operate with their own guest operating systems on a host using resources of the host virtualized by virtualization software (e.g., a hypervisor, virtual machine monitor, etc.). The tenant (i.e., the owner of the VM) can choose which applications to operate on top of the guest operating system. Some containers, on the other hand, are constructs that run on top of a host operating system without the need for a hypervisor or separate guest operating system. In some embodiments, the host operating system uses name spaces to isolate the containers from each other and therefore provides operating-system level segregation of the different groups of applications that operate within different containers. This segregation is akin to the VM segregation that is offered in hypervisor-virtualized environments that virtualize system hardware, and thus can be viewed as a form of virtualization that isolates different groups of applications that operate in different containers. Such containers are more lightweight than VMs.
Hypervisor kernel network interface modules, in some embodiments, is a non-VM DCN that includes a network stack with a hypervisor kernel network interface and receive/transmit threads. One example of a hypervisor kernel network interface module is the vmknic module that is part of the ESXi™ hypervisor of VMware, Inc.
It should be understood that while the specification refers to VMs, the examples given could be any type of DCNs, including physical hosts, VMs, non-VM containers, and hypervisor kernel network interface modules. In fact, the example networks could include combinations of different types of DCNs in some embodiments.
While the invention has been described with reference to numerous specific details, one of ordinary skill in the art will recognize that the invention can be embodied in other specific forms without departing from the spirit of the invention. In addition, a number of the figures (including
This application is a continuation application of U.S. patent application Ser. No. 15/011,430, filed Jan. 29, 2016, and now published as U.S. Patent Publication 2017/0126497. U.S. patent application Ser. No. 15/011,430 claims the benefit of U.S. Provisional Patent Application 62/249,250, filed Oct. 31, 2015. U.S. patent application Ser. No. 15/011,430, now published as U.S. Patent Publication 2017/0126497 is incorporated herein by reference.
| Number | Name | Date | Kind |
|---|---|---|---|
| 5504921 | Dev et al. | Apr 1996 | A |
| 5550816 | Hardwick et al. | Aug 1996 | A |
| 5751967 | Raab et al. | May 1998 | A |
| 6006275 | Picazo et al. | Dec 1999 | A |
| 6104699 | Holender et al. | Aug 2000 | A |
| 6219699 | McCloghrie et al. | Apr 2001 | B1 |
| 6359909 | Ito et al. | Mar 2002 | B1 |
| 6456624 | Eccles et al. | Sep 2002 | B1 |
| 6512745 | Abe et al. | Jan 2003 | B1 |
| 6539432 | Taguchi et al. | Mar 2003 | B1 |
| 6680934 | Cain | Jan 2004 | B1 |
| 6785843 | McRae et al. | Aug 2004 | B1 |
| 6914907 | Bhardwaj et al. | Jul 2005 | B1 |
| 6941487 | Balakrishnan et al. | Sep 2005 | B1 |
| 6950428 | Horst et al. | Sep 2005 | B1 |
| 6963585 | Pennec et al. | Nov 2005 | B1 |
| 6999454 | Crump | Feb 2006 | B1 |
| 7046630 | Abe et al. | May 2006 | B2 |
| 7197572 | Matters et al. | Mar 2007 | B2 |
| 7200144 | Terrell et al. | Apr 2007 | B2 |
| 7209439 | Rawlins et al. | Apr 2007 | B2 |
| 7260648 | Tingley et al. | Aug 2007 | B2 |
| 7283473 | Arndt et al. | Oct 2007 | B2 |
| 7342916 | Das et al. | Mar 2008 | B2 |
| 7391771 | Orava et al. | Jun 2008 | B2 |
| 7447197 | Terrell et al. | Nov 2008 | B2 |
| 7450598 | Chen et al. | Nov 2008 | B2 |
| 7463579 | Lapuh et al. | Dec 2008 | B2 |
| 7478173 | Delco | Jan 2009 | B1 |
| 7483411 | Weinstein et al. | Jan 2009 | B2 |
| 7555002 | Arndt et al. | Jun 2009 | B2 |
| 7606260 | Oguchi et al. | Oct 2009 | B2 |
| 7630358 | Lakhani et al. | Dec 2009 | B1 |
| 7643488 | Khanna et al. | Jan 2010 | B2 |
| 7649851 | Takashige et al. | Jan 2010 | B2 |
| 7653747 | Lucco et al. | Jan 2010 | B2 |
| 7710874 | Balakrishnan et al. | May 2010 | B2 |
| 7742459 | Kwan et al. | Jun 2010 | B2 |
| 7764599 | Doi et al. | Jul 2010 | B2 |
| 7778268 | Khan et al. | Aug 2010 | B2 |
| 7792987 | Vohra et al. | Sep 2010 | B1 |
| 7802000 | Huang et al. | Sep 2010 | B1 |
| 7818452 | Matthews et al. | Oct 2010 | B2 |
| 7826482 | Minei et al. | Nov 2010 | B1 |
| 7839847 | Nadeau et al. | Nov 2010 | B2 |
| 7885276 | Lin | Feb 2011 | B1 |
| 7936770 | Frattura et al. | May 2011 | B1 |
| 7937438 | Miller et al. | May 2011 | B1 |
| 7948986 | Ghosh et al. | May 2011 | B1 |
| 7953865 | Miller et al. | May 2011 | B1 |
| 7991859 | Miller et al. | Aug 2011 | B1 |
| 7995483 | Bayar et al. | Aug 2011 | B1 |
| 8027260 | Venugopal et al. | Sep 2011 | B2 |
| 8027354 | Portolani et al. | Sep 2011 | B1 |
| 8031633 | Bueno et al. | Oct 2011 | B2 |
| 8046456 | Miller et al. | Oct 2011 | B1 |
| 8054832 | Shukla et al. | Nov 2011 | B1 |
| 8055789 | Richardson et al. | Nov 2011 | B2 |
| 8060875 | Lambeth | Nov 2011 | B1 |
| 8131852 | Miller et al. | Mar 2012 | B1 |
| 8149737 | Metke et al. | Apr 2012 | B2 |
| 8155028 | Abu-Hamdeh et al. | Apr 2012 | B2 |
| 8166201 | Richardson et al. | Apr 2012 | B2 |
| 8194674 | Pagel et al. | Jun 2012 | B1 |
| 8199750 | Schultz et al. | Jun 2012 | B1 |
| 8223668 | Allan et al. | Jul 2012 | B2 |
| 8224931 | Brandwine et al. | Jul 2012 | B1 |
| 8224971 | Miller et al. | Jul 2012 | B1 |
| 8239572 | Brandwine et al. | Aug 2012 | B1 |
| 8259571 | Raphel et al. | Sep 2012 | B1 |
| 8265075 | Pandey | Sep 2012 | B2 |
| 8281067 | Stolowitz | Oct 2012 | B2 |
| 8312129 | Miller et al. | Nov 2012 | B1 |
| 8339959 | Moisand et al. | Dec 2012 | B1 |
| 8339994 | Gnanasekaran et al. | Dec 2012 | B2 |
| 8345650 | Foxworthy et al. | Jan 2013 | B2 |
| 8351418 | Zhao et al. | Jan 2013 | B2 |
| 8370834 | Edwards et al. | Feb 2013 | B2 |
| 8416709 | Marshall et al. | Apr 2013 | B1 |
| 8456984 | Ranganathan et al. | Jun 2013 | B2 |
| 8504718 | Wang et al. | Aug 2013 | B2 |
| 8559324 | Brandwine et al. | Oct 2013 | B1 |
| 8565108 | Marshall et al. | Oct 2013 | B1 |
| 8600908 | Lin et al. | Dec 2013 | B2 |
| 8611351 | Gooch et al. | Dec 2013 | B2 |
| 8612627 | Brandwine | Dec 2013 | B1 |
| 8625594 | Sakai et al. | Jan 2014 | B2 |
| 8625603 | Ramakrishnan et al. | Jan 2014 | B1 |
| 8625616 | Vobbilisetty et al. | Jan 2014 | B2 |
| 8627313 | Edwards et al. | Jan 2014 | B2 |
| 8644188 | Brandwine et al. | Feb 2014 | B1 |
| 8660129 | Brendel et al. | Feb 2014 | B1 |
| 8705513 | Merwe et al. | Apr 2014 | B2 |
| 8958298 | Zhang et al. | Feb 2015 | B2 |
| 9021066 | Singh et al. | Apr 2015 | B1 |
| 9032095 | Traina et al. | May 2015 | B1 |
| 9059999 | Koponen et al. | Jun 2015 | B2 |
| 9137052 | Koponen et al. | Sep 2015 | B2 |
| 9313129 | Ganichev et al. | Apr 2016 | B2 |
| 9419855 | Ganichev et al. | Aug 2016 | B2 |
| 9485149 | Traina | Nov 2016 | B1 |
| 9503321 | Neginhal et al. | Nov 2016 | B2 |
| 9559980 | Li et al. | Jan 2017 | B2 |
| 9647883 | Neginhal et al. | May 2017 | B2 |
| 9749214 | Han | Aug 2017 | B2 |
| 9787605 | Zhang et al. | Oct 2017 | B2 |
| 10057157 | Goliya et al. | Aug 2018 | B2 |
| 10075363 | Goliya et al. | Sep 2018 | B2 |
| 10079779 | Zhang et al. | Sep 2018 | B2 |
| 10095535 | Dubey et al. | Oct 2018 | B2 |
| 10110431 | Ganichev et al. | Oct 2018 | B2 |
| 10129142 | Goliya et al. | Nov 2018 | B2 |
| 10129180 | Zhang et al. | Nov 2018 | B2 |
| 10153973 | Dubey | Dec 2018 | B2 |
| 10230629 | Masurekar et al. | Mar 2019 | B2 |
| 10341236 | Boutros et al. | Jul 2019 | B2 |
| 10382321 | Boyapati et al. | Aug 2019 | B1 |
| 10411955 | Neginhal et al. | Sep 2019 | B2 |
| 10454758 | Boutros et al. | Oct 2019 | B2 |
| 10601700 | Goliya et al. | Mar 2020 | B2 |
| 20010043614 | Viswanadham et al. | Nov 2001 | A1 |
| 20020067725 | Oguchi et al. | Jun 2002 | A1 |
| 20020093952 | Gonda | Jul 2002 | A1 |
| 20020194369 | Rawlins et al. | Dec 2002 | A1 |
| 20030041170 | Suzuki | Feb 2003 | A1 |
| 20030058850 | Rangarajan et al. | Mar 2003 | A1 |
| 20030067924 | Choe et al. | Apr 2003 | A1 |
| 20030069972 | Yoshimura et al. | Apr 2003 | A1 |
| 20040013120 | Shen | Jan 2004 | A1 |
| 20040073659 | Rajsic et al. | Apr 2004 | A1 |
| 20040098505 | Clemmensen | May 2004 | A1 |
| 20040267866 | Carollo et al. | Dec 2004 | A1 |
| 20050018669 | Arndt et al. | Jan 2005 | A1 |
| 20050027881 | Figueira et al. | Feb 2005 | A1 |
| 20050053079 | Havala | Mar 2005 | A1 |
| 20050083953 | May | Apr 2005 | A1 |
| 20050120160 | Plouffe et al. | Jun 2005 | A1 |
| 20050132044 | Guingo et al. | Jun 2005 | A1 |
| 20060002370 | Rabie et al. | Jan 2006 | A1 |
| 20060018253 | Windisch et al. | Jan 2006 | A1 |
| 20060026225 | Canali et al. | Feb 2006 | A1 |
| 20060029056 | Perera et al. | Feb 2006 | A1 |
| 20060056412 | Page | Mar 2006 | A1 |
| 20060092940 | Ansari et al. | May 2006 | A1 |
| 20060092976 | Lakshman et al. | May 2006 | A1 |
| 20060174087 | Hashimoto et al. | Aug 2006 | A1 |
| 20060187908 | Shimozono et al. | Aug 2006 | A1 |
| 20060193266 | Siddha et al. | Aug 2006 | A1 |
| 20060291387 | Kimura et al. | Dec 2006 | A1 |
| 20060291388 | Amdahl et al. | Dec 2006 | A1 |
| 20070043860 | Pabari | Feb 2007 | A1 |
| 20070064673 | Bhandaru et al. | Mar 2007 | A1 |
| 20070140128 | Klinker et al. | Jun 2007 | A1 |
| 20070156919 | Potti et al. | Jul 2007 | A1 |
| 20070165515 | Vasseur | Jul 2007 | A1 |
| 20070201357 | Smethurst et al. | Aug 2007 | A1 |
| 20070206591 | Doviak et al. | Sep 2007 | A1 |
| 20070297428 | Bose et al. | Dec 2007 | A1 |
| 20080002579 | Lindholm et al. | Jan 2008 | A1 |
| 20080002683 | Droux et al. | Jan 2008 | A1 |
| 20080013474 | Nagarajan et al. | Jan 2008 | A1 |
| 20080049621 | McGuire et al. | Feb 2008 | A1 |
| 20080049646 | Lu | Feb 2008 | A1 |
| 20080059556 | Greenspan et al. | Mar 2008 | A1 |
| 20080071900 | Hecker et al. | Mar 2008 | A1 |
| 20080086726 | Griffith et al. | Apr 2008 | A1 |
| 20080151893 | Nordmark et al. | Jun 2008 | A1 |
| 20080159301 | Heer | Jul 2008 | A1 |
| 20080189769 | Casado et al. | Aug 2008 | A1 |
| 20080225853 | Melman et al. | Sep 2008 | A1 |
| 20080240122 | Richardson et al. | Oct 2008 | A1 |
| 20080253366 | Zuk et al. | Oct 2008 | A1 |
| 20080291910 | Tadimeti et al. | Nov 2008 | A1 |
| 20090031041 | Clemmensen | Jan 2009 | A1 |
| 20090043823 | Iftode et al. | Feb 2009 | A1 |
| 20090064305 | Stiekes et al. | Mar 2009 | A1 |
| 20090083445 | Ganga | Mar 2009 | A1 |
| 20090092137 | Haigh et al. | Apr 2009 | A1 |
| 20090122710 | Bar-Tor et al. | May 2009 | A1 |
| 20090150527 | Tripathi et al. | Jun 2009 | A1 |
| 20090161547 | Riddle et al. | Jun 2009 | A1 |
| 20090249470 | Litvin et al. | Oct 2009 | A1 |
| 20090249473 | Cohn | Oct 2009 | A1 |
| 20090279536 | Unbehagen et al. | Nov 2009 | A1 |
| 20090292858 | Lambeth et al. | Nov 2009 | A1 |
| 20090300210 | Ferris | Dec 2009 | A1 |
| 20090303880 | Maltz et al. | Dec 2009 | A1 |
| 20100002722 | Porat et al. | Jan 2010 | A1 |
| 20100046531 | Louati et al. | Feb 2010 | A1 |
| 20100107162 | Edwards et al. | Apr 2010 | A1 |
| 20100115101 | Lain et al. | May 2010 | A1 |
| 20100131636 | Suri et al. | May 2010 | A1 |
| 20100153554 | Anschutz et al. | Jun 2010 | A1 |
| 20100153701 | Shenoy et al. | Jun 2010 | A1 |
| 20100162036 | Linden et al. | Jun 2010 | A1 |
| 20100165877 | Shukla et al. | Jul 2010 | A1 |
| 20100169467 | Shukla et al. | Jul 2010 | A1 |
| 20100192225 | Ma et al. | Jul 2010 | A1 |
| 20100205479 | Akutsu et al. | Aug 2010 | A1 |
| 20100214949 | Smith et al. | Aug 2010 | A1 |
| 20100275199 | Smith et al. | Oct 2010 | A1 |
| 20100290485 | Martini et al. | Nov 2010 | A1 |
| 20100318609 | Lahiri et al. | Dec 2010 | A1 |
| 20100322255 | Hao et al. | Dec 2010 | A1 |
| 20110016215 | Wang | Jan 2011 | A1 |
| 20110022695 | Dalai et al. | Jan 2011 | A1 |
| 20110026537 | Kolhi et al. | Feb 2011 | A1 |
| 20110032830 | Merwe et al. | Feb 2011 | A1 |
| 20110032843 | Papp et al. | Feb 2011 | A1 |
| 20110075664 | Lambeth et al. | Mar 2011 | A1 |
| 20110075674 | Li et al. | Mar 2011 | A1 |
| 20110085557 | Gnanasekaran et al. | Apr 2011 | A1 |
| 20110085559 | Chung et al. | Apr 2011 | A1 |
| 20110103259 | Aybay et al. | May 2011 | A1 |
| 20110119748 | Edwards et al. | May 2011 | A1 |
| 20110134931 | Merwe et al. | Jun 2011 | A1 |
| 20110142053 | Merwe et al. | Jun 2011 | A1 |
| 20110149964 | Judge et al. | Jun 2011 | A1 |
| 20110149965 | Judge et al. | Jun 2011 | A1 |
| 20110194567 | Shen | Aug 2011 | A1 |
| 20110205931 | Zhou et al. | Aug 2011 | A1 |
| 20110261825 | Ichino | Oct 2011 | A1 |
| 20110283017 | Alkhatib et al. | Nov 2011 | A1 |
| 20110299534 | Koganti et al. | Dec 2011 | A1 |
| 20110310899 | Alkhatib et al. | Dec 2011 | A1 |
| 20110317703 | Dunbar et al. | Dec 2011 | A1 |
| 20120014386 | Xiong et al. | Jan 2012 | A1 |
| 20120014387 | Dunbar et al. | Jan 2012 | A1 |
| 20120131643 | Cheriton | May 2012 | A1 |
| 20120155467 | Appenzeller | Jun 2012 | A1 |
| 20120182992 | Cowart et al. | Jul 2012 | A1 |
| 20120236734 | Sampath et al. | Sep 2012 | A1 |
| 20130007740 | Kikuchi et al. | Jan 2013 | A1 |
| 20130044636 | Koponen et al. | Feb 2013 | A1 |
| 20130044641 | Koponen et al. | Feb 2013 | A1 |
| 20130051399 | Zhang | Feb 2013 | A1 |
| 20130058225 | Casado et al. | Mar 2013 | A1 |
| 20130058229 | Casado et al. | Mar 2013 | A1 |
| 20130058335 | Koponen et al. | Mar 2013 | A1 |
| 20130058350 | Fulton | Mar 2013 | A1 |
| 20130058353 | Koponen et al. | Mar 2013 | A1 |
| 20130060940 | Koponen et al. | Mar 2013 | A1 |
| 20130094350 | Mandal et al. | Apr 2013 | A1 |
| 20130103817 | Koponen et al. | Apr 2013 | A1 |
| 20130103818 | Koponen et al. | Apr 2013 | A1 |
| 20130132536 | Zhang et al. | May 2013 | A1 |
| 20130142048 | Gross, I et al. | Jun 2013 | A1 |
| 20130148541 | Zhang et al. | Jun 2013 | A1 |
| 20130148542 | Zhang et al. | Jun 2013 | A1 |
| 20130148543 | Koponen et al. | Jun 2013 | A1 |
| 20130148656 | Zhang et al. | Jun 2013 | A1 |
| 20130151661 | Koponen et al. | Jun 2013 | A1 |
| 20130151676 | Thakkar et al. | Jun 2013 | A1 |
| 20130208621 | Manghirmalani et al. | Aug 2013 | A1 |
| 20130212148 | Koponen et al. | Aug 2013 | A1 |
| 20130223444 | Liljenstolpe et al. | Aug 2013 | A1 |
| 20130230047 | Subrahmaniam et al. | Sep 2013 | A1 |
| 20130266007 | Kumbhare et al. | Oct 2013 | A1 |
| 20130266015 | Qu et al. | Oct 2013 | A1 |
| 20130266019 | Qu et al. | Oct 2013 | A1 |
| 20130268799 | Mestery et al. | Oct 2013 | A1 |
| 20130329548 | Nakil et al. | Dec 2013 | A1 |
| 20130332602 | Nakil et al. | Dec 2013 | A1 |
| 20130332619 | Xie et al. | Dec 2013 | A1 |
| 20130339544 | Mithyantha | Dec 2013 | A1 |
| 20140003434 | Assarpour et al. | Jan 2014 | A1 |
| 20140016501 | Kamath et al. | Jan 2014 | A1 |
| 20140059226 | Messerli et al. | Feb 2014 | A1 |
| 20140146817 | Zhang | May 2014 | A1 |
| 20140173093 | Rabeela et al. | Jun 2014 | A1 |
| 20140195666 | Dumitriu et al. | Jul 2014 | A1 |
| 20140229945 | Barkai et al. | Aug 2014 | A1 |
| 20140241247 | Kempf et al. | Aug 2014 | A1 |
| 20140269299 | Koornstra | Sep 2014 | A1 |
| 20140328350 | Hao et al. | Nov 2014 | A1 |
| 20140372582 | Ghanwani et al. | Dec 2014 | A1 |
| 20140376550 | Khan et al. | Dec 2014 | A1 |
| 20150016300 | Devireddy et al. | Jan 2015 | A1 |
| 20150063360 | Thakkar et al. | Mar 2015 | A1 |
| 20150063364 | Thakkar et al. | Mar 2015 | A1 |
| 20150089082 | Patwardhan et al. | Mar 2015 | A1 |
| 20150092594 | Zhang et al. | Apr 2015 | A1 |
| 20150103838 | Zhang et al. | Apr 2015 | A1 |
| 20150188770 | Naiksatam et al. | Jul 2015 | A1 |
| 20150222550 | Anand | Aug 2015 | A1 |
| 20150263897 | Ganichev et al. | Sep 2015 | A1 |
| 20150263946 | Tubaltsev et al. | Sep 2015 | A1 |
| 20150263952 | Ganichev et al. | Sep 2015 | A1 |
| 20150271011 | Neginhal et al. | Sep 2015 | A1 |
| 20150271303 | Neginhal et al. | Sep 2015 | A1 |
| 20150299880 | Jorge et al. | Oct 2015 | A1 |
| 20160105471 | Nunes et al. | Apr 2016 | A1 |
| 20160119229 | Zhou | Apr 2016 | A1 |
| 20160182287 | Chiba et al. | Jun 2016 | A1 |
| 20160191374 | Singh et al. | Jun 2016 | A1 |
| 20160226700 | Zhang et al. | Aug 2016 | A1 |
| 20160226754 | Zhang et al. | Aug 2016 | A1 |
| 20160226762 | Zhang et al. | Aug 2016 | A1 |
| 20160261493 | Li | Sep 2016 | A1 |
| 20160294612 | Ravinoothala et al. | Oct 2016 | A1 |
| 20160344586 | Ganichev et al. | Nov 2016 | A1 |
| 20170005923 | Babakian | Jan 2017 | A1 |
| 20170048129 | Masurekar et al. | Feb 2017 | A1 |
| 20170048130 | Goliya et al. | Feb 2017 | A1 |
| 20170063632 | Goliya et al. | Mar 2017 | A1 |
| 20170063633 | Goliya et al. | Mar 2017 | A1 |
| 20170064717 | Filsfils et al. | Mar 2017 | A1 |
| 20170126497 | Dubey et al. | May 2017 | A1 |
| 20170180154 | Duong et al. | Jun 2017 | A1 |
| 20170230241 | Neginhal et al. | Aug 2017 | A1 |
| 20170317919 | Fernando et al. | Nov 2017 | A1 |
| 20180006943 | Dubey | Jan 2018 | A1 |
| 20180062914 | Boutros et al. | Mar 2018 | A1 |
| 20180097734 | Boutros et al. | Apr 2018 | A1 |
| 20180367442 | Goliya et al. | Dec 2018 | A1 |
| 20190020580 | Boutros et al. | Jan 2019 | A1 |
| 20190020600 | Zhang et al. | Jan 2019 | A1 |
| 20190109780 | Nagarkar | Apr 2019 | A1 |
| 20190124004 | Dubey | Apr 2019 | A1 |
| 20190199625 | Masurekar et al. | Jun 2019 | A1 |
| 20190281133 | Tomkins | Sep 2019 | A1 |
| 20190312812 | Boutros et al. | Oct 2019 | A1 |
| 20190334767 | Neginhal et al. | Oct 2019 | A1 |
| 20200021483 | Boutros et al. | Jan 2020 | A1 |
| Number | Date | Country |
|---|---|---|
| 1442987 | Sep 2003 | CN |
| 1714548 | Dec 2005 | CN |
| 103890751 | Jun 2014 | CN |
| 103947164 | Jul 2014 | CN |
| 104335553 | Feb 2015 | CN |
| 1653688 | May 2006 | EP |
| 2838244 | Feb 2015 | EP |
| 3013006 | Apr 2016 | EP |
| 2000244567 | Sep 2000 | JP |
| 2003069609 | Mar 2003 | JP |
| 2003124976 | Apr 2003 | JP |
| 2003318949 | Nov 2003 | JP |
| 2011139299 | Jul 2011 | JP |
| 2011228864 | Nov 2011 | JP |
| 2014534789 | Dec 2014 | JP |
| 1020110099579 | Sep 2011 | KR |
| 2005112390 | Nov 2005 | WO |
| 2008095010 | Aug 2008 | WO |
| 2013020126 | Feb 2013 | WO |
| 2013026049 | Feb 2013 | WO |
| 2013055697 | Apr 2013 | WO |
| 2013081962 | Jun 2013 | WO |
| 2013143611 | Oct 2013 | WO |
| 2013184846 | Dec 2013 | WO |
| 2015015787 | Feb 2015 | WO |
| 2015142404 | Sep 2015 | WO |
| 2016123550 | Aug 2016 | WO |
| 2017027073 | Feb 2017 | WO |
| 2018044746 | Mar 2018 | WO |
| Entry |
|---|
| Agarwal, Sugam, et al., “Traffic Engineering in Software Defined Networks,” 2013 Proceedings IEEE INFOCOM, Apr. 14, 2013, 10 pages, Bell Labs, Alcatel-Lucent, Holmdel, NJ, USA. |
| Aggarwal, R., et al., “Data Center Mobility based on E-VPN, BGP/MPLS IP VPN, IP Routing and NHRP,” draft-raggarwa-data-center-mobility-05.txt, Jun. 10, 2013, 24 pages, Internet Engineering Task Force, IETF, Geneva, Switzerland. |
| Author Unknown, “VMware® NSX Network Virtualization Design Guide,” Month Unknown 2013, 32 pages, Item No. VMW-NSX-NTWK-VIRT-DESN-GUIDE-V2-101. VMware, Inc., Palo Alto, CA, USA. |
| Ballani, Hitesh, et al., “Making Routers Last Longer with ViAggre,” NSDI '09: 6th USENIX Symposium on Networked Systems Design and Implementation, Apr. 2009, 14 pages, USENIX Association. |
| Caesar, Matthew, et al., “Design and Implementation of a Routing Control Platform,” NSDI '05: 2nd Symposium on Networked Systems Design & Implementation , Apr. 2005, 14 pages, Usenix Association. |
| Dobrescu, Mihai, et al., “RouteBricks: Exploiting Parallelism To Scale Software Routers,” SOSP'09, Proceedings of the ACM SIGOPS 22nd Symposium on Operating Systems Principles, Oct. 2009, 17 pages, ACM, New York, NY. |
| Dumitriu, Dan Mihai, et al., U.S. Appl. No. 61/514,990, filed Aug. 4, 2011. |
| Fernando, Rex, et al., “Service Chaining using Virtual Networks with BGP,” Internet Engineering Task Force, IETF, Jul. 7, 2015, 32 pages, Internet Society (ISOC), Geneva, Switzerland, available at https://tools.ietf.org/html/draft-fm-bess-service-chaining-01. |
| Handley, Mark, et al., “Designing Extensible IP Router Software,” Proc. of NSDI, May 2005, 14 pages. |
| Kim, Changhoon, et al., “Revisiting Route Caching: The World Should be Flat,” In Proc. Of International Conference on Passive and Active Network Measurement, Apr. 2009, 10 pages, Springer, Berlin, Heidelberg. |
| Koponen, Teemu, et al., “Network Virtualization in Multi-tenant Datacenters,” Technical Report TR-2013-001E, Aug. 2013, 22 pages, VMware, Inc., Palo Alto, CA, USA. |
| Lakshminarayanan, Karthik, et al., “Routing as a Service,” Report No. UCB/CSD-04-1327, Month Unknown 2004, 16 pages, Computer Science Division (EECS), University of California—Berkeley, Berkeley, California. |
| Lowe, Scott, “Learning NSX, Part 14: Using Logical Routing,” Scott's Weblog: The weblog of an IT pro specializing in cloud computing, virtualization, and networking, all with an open source view, Jun. 20, 2014, 8 pages, available at https://blog.scottlowe.org/2014/06/20/learning-nsx-part-14-using-logical-routing/. |
| Maltz, David A., et al., “Routing Design in Operational Networks: A Look from the Inside,” SIGCOMM '04, Aug. 30-Sep. 3, 2004, 14 pages, ACM, Portland, Oregon, USA. |
| Pelissier, Joe, “Network Interface Virtualization Review,” Jan. 2009, 38 pages. |
| Rosen, E., “Applicability Statement for BGP/MPLS IP Virtual Private Networks (VPNs),” RFC 4365, Feb. 2006, 32 pages, The Internet Society. |
| Sajassi, Ali, et al., “Integrated Routing and Bridging in EVPN draft-sajassi-12vpn-evpn-inter-subnet-forwarding-04”, Jul. 4, 2014, 24 pages. |
| Shenker, Scott, et al., “The Future of Networking, and the Past of Protocols,” Dec. 2, 2011, 30 pages, USA. |
| Wang, Anjing, et al., “Network Virtualization: Technologies, Perspectives, and Frontiers,” Journal of Lightwave Technology, Feb. 15, 2013, 15 pages, IEEE. |
| Wang, Yi, et al., “Virtual Routers on the Move: Live Router Migration as a Network-Management Primitive,” SIGCOMM '08, Aug. 17-22, 2008, 12 pages, ACM, Seattle, Washington, USA. |
| Author Unknown, “Defining Security Policies for Policy-based and Route-based VPNs,” Month Unknown 2018, 5 pages, Fortinet, Inc., retrieved at http://help.fortinet.com/fos50hlp/54/Content/FortiOS/fortigate-ipsecvpn-54/Defining_VPN_Policies/Defining_Policies_for_Policy_and_Route.htm. |
| Berger, L., et al, “The OSPF Opaque LSA Option,” Jul. 2008, 17 pages, RFC 5250, IETF. |
| Keller, Ralph, “Dissemination of Application-Specific Information using the OSPF Routing Protocol,” TIK Report Nr. 181, Nov. 2003, 12 pages, ETH Zurich, Switzerland. |
| Wang, Yushun, et al., “Connect Azure VPN gateways to multiple on-premises policy-based VPN devices using PowerShell,” VPN Gateway Documentation, Apr. 18, 2018, 5 pages, retrieved at https://docs.microsoft.com/en-us/azure/vpn-gateway/vpn-gateway-connect-multiple-policybased-rm-ps. |
| Non-Published commonly Owned U.S. Appl. No. 16/506,182, filed Jul. 9, 2019, 91 pages, Nicira, Inc. |
| Non-published commonly owned U.S. Appl. No. 16/823,050, filed Mar. 18, 2020, 79 pages, Nicira, Inc. |
| Author Unknown, “Cisco Border Gateway Protocol Control Plane for Virtual Extensible LAN,” White Paper, Jan. 23, 2015, 6 pages, Cisco Systems, Inc. |
| Author Unknown, “Cisco Data Center Spine-and-Leaf Architecture: Design Overview,” White Paper, Apr. 15, 2016, 27 pages, Cisco Systems, Inc. |
| Moreno, Victor, “VXLAN Deployment Models—A Practical Perspective,” Cisco Live 2015 Melbourne, Mar. 6, 2015, 72 pages, BRKDCT-2404, Cisco Systems, Inc. |
| Number | Date | Country | |
|---|---|---|---|
| 20190018701 A1 | Jan 2019 | US |
| Number | Date | Country | |
|---|---|---|---|
| 62249250 | Oct 2015 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 15011430 | Jan 2016 | US |
| Child | 16133541 | US |
