Static route types for logical routers

• US 10,095,535 B2
• Filed: 01/29/2016
• Issued: 10/09/2018
• Est. Priority Date: 10/31/2015
• Status: Active Grant

• Current Assignee: Nicira Incorporated (Broadcom, Inc.)
• Original Assignee: Nicira Incorporated (Broadcom, Inc.)
• Inventors: Dubey, Ankur, Ravinoothala, Sreeram, Zhang, Ronghua, Zhang, Xuan
• Primary Examiner(s): HUQ, FARZANA B
• Application Number:
  US15/011,430
• Publication Number:
  US 20170126497A1
• Time in Patent Office: 984 Days
• Field of Search: 709221
• CPC Class Codes: G06F 2009/45595 Network integration; Enabling network access in virtual machine instances
• CPC Class Codes: G06F 9/45558 Hypervisor-specific management and integration aspects
• CPC Class Codes: H04L 41/0806 for initial configuration or provisioning, e.g. plug-and-play
• CPC Class Codes: H04L 41/0895 Configuration of virtualised networks or elements, e.g. virtualised network function or OpenFlow elements

Abstract

Some embodiments provide method for implementing a logical router of a logical network. The method receives a configuration for a first logical router. The configuration includes a static route for the first logical router. The method defines several routing components with separate routing tables for the logical router. The method adds a first route, having a first static route type, for the static route to the routing tables of at least a first subset of the routing components. Based on the connection of a second logical router to the first logical router, adding a second route, having a second static route type, to the routing tables of at least a second subset of the routing components.

Claims

1. A method for implementing a first logical router of a logical network, the method comprising:

receiving a configuration for the first logical router, the configuration comprising a static route for the first logical router;

defining a plurality of logical routing components with separate routing tables for the first logical router, the plurality of logical routing components comprising a distributed routing component and at least one centralized routing component, wherein the distributed routing component is implemented by a plurality of managed forwarding elements;

adding a static first route for the static route to the routing tables of at least a first subset of the routing components of the first logical router, the static first added route having a first static route type; and

based on a connection of a second logical router to the first logical router;

defining a logical switch that connects to the distributed routing component of the first logical router and a logical routing component of the second logical router, the logical switch having an assigned subnet;

adding a connected second route for the assigned subnet to the routing table of the distributed routing component; and

adding a static third route for the assigned subnet to the routing tables of the centralized routing components of the first logical router, the static third added route having a second static route type different from the first static route type; and

distributing the routing tables of the plurality of logical routing components to the plurality of managed forwarding elements, wherein the managed forwarding elements use routes in the distributed routing tables to process network traffic.

2. The method of claim 1, wherein the first static route type and the second static route type have different default priorities.

3. The method of claim 1, wherein the first static route type and the second static route type have different default administrative distances.

4. The method of claim 1, wherein the static first route is added to the distributed routing component and only one of the centralized routing components of the first logical router.

5. The method of claim 1, wherein the static first route is added to all of the logical routing components of the first logical router.

6. The method of claim 1, wherein the second logical router advertises a second subnet for which the second logical router is a next hop, the method further comprising adding a static fourth route to the routing tables of at least a third subset of the routing components, the static fourth route having a third static route type different from the first and second static route types.

7. The method of claim 6, wherein the third static route type has a different default administrative distance than both the first static route type and the second static route type.

8. The method of claim 1, wherein the method is performed by a management plane of a network controller, wherein distributing the routing tables comprises providing the routing tables to a central control plane of the network controller that uses the routing tables to generate a forwarding information base for each of the logical routing components and distributes the generated forwarding information bases to the managed forwarding elements.

9. The method of claim 8, wherein the central control plane identifies a preferred route in a particular routing table for each network address prefix for which at least one route is present in the particular routing table and performs route traversal to identify an output action for the route.

10. A non-transitory machine readable medium storing a program for execution by at least one processing unit, the program comprising sets of instructions for:

receiving a configuration for a first logical router, the configuration comprising a static route for the first logical router;

defining a plurality of logical routing components with separate routing tables for the first logical router, the plurality of logical routing components comprising a distributed routing component and at least one centralized routing component, wherein the distributed routing component is implemented by a plurality of managed forwarding elements;

adding a static first route for the static route to the routing tables of at least a first subset of the routing components of the first logical router, the static first added route having a first static route type; and

based on a connection of a second logical router to the first logical router;

defining a logical switch that connects to the distributed routing component of the first logical router and a logical routing component of the second logical router, the logical switch having an assigned subnet;

adding a connected second route for the assigned subnet to the routing table of the distributed routing component; and

adding a static third route for the assigned subnet to the routing tables of the centralized routing components of the first logical router, the static third added route having a second static route type different from the first static route type; and

distributing the routing tables of the plurality of logical routing components to the plurality of managed forwarding elements, wherein the managed forwarding elements use routes in the distributed routing tables to process network traffic.

11. The non-transitory machine readable medium of claim 10, wherein the first static route type and the second static route type have different default priorities.

12. The non-transitory machine readable medium of claim 10, wherein the first static route type and the second static route type have different default administrative distances.

13. The non-transitory machine readable medium of claim 10, wherein the static first route is added to the distributed routing component and only one of the centralized routing components of the first logical router.

14. The non-transitory machine readable medium of claim 10, wherein the static first route is added to all of the logical routing components of the first logical router.

15. The non-transitory machine readable medium of claim 10, wherein the second logical router advertises a second subnet for which the second logical router is a next hop, the program further comprising a set of instructions for adding a static fourth route to the routing tables of at least a third subset of the routing components, the static fourth route having a third static route type different from the first and second static route types.

16. The non-transitory machine readable medium of claim 15, wherein the third static route type has a different default administrative distance than both the first static route type and the second static route type.

17. The non-transitory machine readable medium of claim 10, wherein the program is a management plane of a network controller, wherein the set of instructions for distributing the routing tables comprises a set of instructions for providing the routing tables to a central control plane of the network controller that uses the routing tables to generate a forwarding information base for each of the logical routing components and distributes the generated forwarding information bases to the managed forwarding elements.

18. The non-transitory machine readable medium of claim 17, wherein the central control plane identifies a preferred route in a particular routing table for each network address prefix for which at least one route is present in the particular routing table and performs route traversal to identify an output action for the route.