Static route configuration for logical router

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

receiving a configuration of a static route for the logical router, wherein the logical router comprises (i) a distributed routing component that interfaces with other logical forwarding elements to process data traffic internal to the logical network and (ii) one or more centralized routing components that interface with an external physical network to process data traffic between the logical network and the external physical network, wherein the distributed routing component and each of the centralized routing components have separate routing tables, wherein the distributed routing component is implemented across a plurality of physical machines that implement the logical network;

identifying which of the centralized routing components require addition of a route to a corresponding routing table to implement the configuration of the static route; and

adding routes for a same prefix as the configured static route to (i) each of the corresponding separate routing tables of the identified centralized routing components and (ii) the routing table of the distributed routing component.

2. The method of claim 1 , wherein the configuration of the static route comprises the prefix and a next hop address.

3. The method of claim 2 , wherein the configuration of the static route further comprises an output interface.

4. The method of claim 1 , wherein the static route includes a next hop address that is an address in the logical network, wherein the distributed routing component and each of the centralized routing components of the logical router are identified as requiring addition of a route to a corresponding routing table.

5. A method for implementing a logical router in a logical network, the method comprising:

for the logical router, receiving a configuration of a static route including a next hop address that is an address in the logical network, wherein the logical router comprises (i) a distributed routing component that interfaces with other logical forwarding elements and (ii) one or more centralized routing components that interface with an external physical network, wherein the distributed routing component and each of the centralized routing components have separate routing tables, wherein the distributed routing component is implemented across a plurality of physical machines that implement the logical network;

determining that the static route should be added to the routing table of the distributed routing component and each of the centralized routing components;

adding the static route as configured to the distributed routing component; and

adding routes for a same prefix as the configured static route to each of the centralized routing components, the routes including a next hop address of an interface of the distributed routing component to which the centralized routing components connect.

6. The method of claim 5 , wherein the configuration of the static route further comprises an output interface.

7. The method of claim 5 , wherein the distributed routing component interfaces with the other logical forwarding elements to process data traffic internal to the logical network, and wherein the centralized routing components interface with the external physical network to process data traffic between the logical network and the external physical network.

8. A method for implementing a logical router in a logical network, the method comprising:

for the logical router, receiving a configuration of a static route including a next hop address that is an address in the external physical network, wherein no output interface is specified for the static route, wherein the logical router comprises (i) a distributed routing component that interfaces with other logical forwarding elements and (ii) one or more centralized routing components that interface with an external physical network, wherein the distributed routing component and each of the centralized routing components have separate routing tables, wherein the distributed routing component is implemented across a plurality of physical machines that implement the logical network;

identifying the centralized routing components with connectivity to the next hop address; and

adding the static route as configured to the routing table of each identified centralized routing components with connectivity to the next hop address;

based on a determination that the configured static route is not a default route, adding routes to the to the routing table of the distributed routing component, the next hop address for each added route being an address of an interface of the centralized routing components to which the configured static route was added.

9. The method of claim 8 , wherein the method is performed by a centralized network controller that manages the logical router.

10. The method of claim 9 further comprising distributing the routing tables with the added routes to local network controllers operating on the plurality of physical machines that implement the distributed routing component.

11. The method of claim 8 , wherein adding a route to a particular routing table comprises adding or modifying an entry of the particular routing table.

12. A non-transitory machine readable medium storing a program which when executed by at least one processing unit implements a logical router in a logical network, the program comprising sets of instructions for:

receiving a configuration of a static route for the logical router, wherein the logical router comprises (i) a distributed routing component that interfaces with other logical forwarding elements to process data traffic internal to the logical network and (ii) one or more centralized routing components that interface with an external physical network to process data traffic between the logical network and the external physical network, wherein the distributed routing component and each of the centralized routing components have separate routing tables, wherein the distributed routing component is implemented across a plurality of physical machines that implement the logical network;

identifying which of the centralized routing components require addition of a route to a corresponding routing table to implement the configuration of the static route; and

adding routes for a same prefix as the configured static route to (i) each of the corresponding separate routing tables of the identified centralized routing components and (ii) the routing table of the distributed routing component.

13. The non-transitory machine readable medium of claim 12 , wherein the configuration of the static route comprises the prefix and a next hop address.

14. The non-transitory machine readable medium of claim 13 , wherein the configuration of the static route further comprises an output interface.

15. The non-transitory machine readable medium of claim 12 , wherein (i) the static route includes a next hop address that is an address in the logical network, (ii) the distributed routing component and each of the centralized routing components of the logical router are identified as requiring addition of a route to a corresponding routing table, and (iii) the set of instructions for adding routes for the same prefix as the configured static route to the separate routing tables for the distributed routing component and each of the identified centralized routing components comprises sets of instructions for:

adding the static route as configured to the distributed routing component; and

adding routes for the same prefix as the configured static route to each of the centralized routing components, the routes including a next hop address of an interface of the distributed routing component to which the centralized routing components connect.

16. The non-transitory machine readable medium of claim 12 , wherein (i) the static route includes a next hop address that is an address in the external physical network, (ii) no output interface is specified for the static route, (iii) the set of instructions for identifying which of the centralized routing components require addition of a route to the corresponding routing table comprises a set of instructions for identifying centralized routing components with connectivity to the next hop address, and (iv) the set of instructions for adding routes to the corresponding routing tables for the identified centralized routing components comprises a set of instructions for adding the static route as configured to the corresponding separate routing tables of each of the identified centralized routing components with connectivity to the next hop address.

17. The non-transitory machine readable medium of claim 16 , wherein:

the set of instructions for identifying which of the routing components require addition of a route to the corresponding routing table further comprises a set of instructions for determining whether the configured static route is a default route; and

the set of instructions for adding routes to the corresponding routing tables of the identified routing components comprises a set of instructions for adding routes for the same prefix as the configured static route to the routing table of the distributed routing component based on a determination that the configured static route is not a default route, the next hop address for each added route being an address of an interface of the centralized routing component to which the configured static route was added.

18. The non-transitory machine readable medium of claim 12 , wherein the program is a centralized network controller that manages the logical router, the program further comprising a set of instructions for distributing the routing tables with the added routes to local network controllers operating on the plurality of physical machines that implement the distributed routing component.

19. The non-transitory machine readable medium of claim 12 , wherein the set of instructions for adding a route to a particular routing table comprises a set of instructions for adding or modifying an entry of the particular routing table.