Implementing logical router uplinks

• US 10,079,779 B2
• Filed: 07/30/2015
• Issued: 09/18/2018
• Est. Priority Date: 01/30/2015
• Status: Active Grant

• Current Assignee: Nicira Incorporated (Broadcom, Inc.)
• Original Assignee: Nicira Incorporated (Broadcom, Inc.)
• Inventors: Zhang, Ronghua, Ravinoothala, Sreeram
• Primary Examiner(s): Zaidi, Iqbal
• Application Number:
  US14/814,469
• Publication Number:
  US 20160226762A1
• Time in Patent Office: 1,146 Days
• Field of Search: 370230-339
• CPC Class Codes: H04L 12/4633 Interconnection of networks using encapsulation techniques, e.g. tunneling
• CPC Class Codes: H04L 12/4654 wherein a VLAN tag represents a customer VLAN, e.g. C-Tag
• CPC Class Codes: H04L 12/66 Arrangements for connecting between networks having differing types of switching systems, e.g. gateways
• CPC Class Codes: H04L 2012/4629 using multilayer switching, e.g. layer 3 switching
• CPC Class Codes: H04L 2101/663 Transport layer addresses, e.g. aspects of transmission control protocol [TCP] or user datagram protocol [UDP] ports
• CPC Class Codes: H04L 41/0654 using network fault recovery ring fault isolation or reconfiguration in loop networks without recovery actions by a network management system H04L12/437
• CPC Class Codes: H04L 41/122 of virtualised topologies, e.g. software-defined networks [SDN] or network function virtualisation [NFV]
• CPC Class Codes: H04L 41/145 involving simulating, designing, planning or modelling of a network
• CPC Class Codes: H04L 41/40 using virtualisation of network functions or resources, e.g. SDN or NFV entities
• CPC Class Codes: H04L 41/5041 characterised by the time relationship between creation and deployment of a service
• CPC Class Codes: H04L 41/5077 wherein the managed service relates to simple transport services, i.e. providing only network infrastructure
• CPC Class Codes: H04L 43/08 Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
• CPC Class Codes: H04L 43/106 using time related information in packets, e.g. by adding timestamps
• CPC Class Codes: H04L 45/02 Topology update or discovery
• CPC Class Codes: H04L 45/033 by updating distance vector protocols
• CPC Class Codes: H04L 45/122 by minimising distances, e.g. by selecting a route with minimum of number of hops
• CPC Class Codes: H04L 45/22 Alternate routing
• CPC Class Codes: H04L 45/28 using route fault recovery
• CPC Class Codes: H04L 45/306 Route determination based on the nature of the carried application
• CPC Class Codes: H04L 45/38 Flow based routing
• CPC Class Codes: H04L 45/42 : Centralised routing
• CPC Class Codes: H04L 45/44 : Distributed routing
• CPC Class Codes: H04L 45/586 : of virtual routers
• CPC Class Codes: H04L 45/64 : using an overlay routing layer
• CPC Class Codes: H04L 45/72 : Routing based on the source address
• CPC Class Codes: H04L 45/74 : Address processing for routing
• CPC Class Codes: H04L 45/742 : Route cache; Operation thereof
• CPC Class Codes: H04L 45/745 : Address table lookup; Address filtering
• CPC Class Codes: H04L 47/19 : at layers above the network layer network arrangements for networked applications for scheduling or organising the servicing of application requests H04L67/60
• CPC Class Codes: H04L 49/25 : Routing or path finding in a switch fabric
• CPC Class Codes: H04L 49/3009 : Header conversion, routing tables or routing tags
• CPC Class Codes: H04L 49/3063 : Pipelined operation
• CPC Class Codes: H04L 49/354 : for supporting virtual local area networks [VLAN]
• CPC Class Codes: H04L 49/9068 : in the network interface card
• CPC Class Codes: H04L 61/103 : across network layers, e.g. resolution of network layer into physical layer addresses or address resolution protocol [ARP]
• CPC Class Codes: H04L 61/2503 : Translation of Internet protocol [IP] addresses
• CPC Class Codes: H04L 61/2585 : through application level gateway [ALG]
• CPC Class Codes: H04L 67/1001 : for accessing one among a plurality of replicated servers
• CPC Class Codes: H04L 67/1038 : Load balancing arrangements to avoid a single path through a load balancer
• CPC Class Codes: H04L 67/1095 : Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes
• CPC Class Codes: H04L 67/568 : Storing data temporarily at an intermediate stage, e.g. caching
• CPC Class Codes: H04L 67/63 : Routing a service request depending on the request content or context
• CPC Class Codes: H04L 69/321 : Interlayer communication protocols or service data unit [SDU] definitions; Interfaces between layers
• CPC Class Codes: H04L 69/326 : in the transport layer [OSI layer 4] H04L69/16 takes precedence
• CPC Class Codes: H04L 69/329 : in the application layer [OSI layer 7]

Abstract

Some embodiments provide a method for defining a gateway component of a logical router. The method assigns each of several uplinks to different gateway machines. For one of the uplinks, the method defines a first centralized gateway component of the logical router for implementation on a first gateway machine to which the uplink is assigned. The method defines a first local interface for the first gateway component configured according to the uplink. The first local interface for the first gateway component forwards traffic to a network external to the implementation of the logical router. The method defines a second interface for the first gateway component configured according to a second uplink. The second interface is for redirecting traffic processed according to the second uplink configuration to a second centralized gateway component implemented on a second gateway machine. The second gateway component forwards the traffic to the external network.

Claims

1. A method for defining a centralized gateway component of a logical router, the method comprising:

for each of a plurality of uplinks configured for the logical router, assigning the uplink to a different gateway machine;

for a first one of the uplinks, defining a first centralized gateway component of the logical router for implementation on a first gateway machine to which the first uplink is assigned;

defining a first local interface for the first centralized gateway component configured according to the first uplink, the first local interface for the first centralized gateway component to forward traffic to a network external to the implementation of the logical router;

defining a second interface for the first centralized gateway component configured according to a second uplink, the second interface for redirecting traffic processed according to the second uplink configuration to a second centralized gateway component implemented on a second gateway machine for the second centralized gateway component to forward the traffic to the external network;

defining a distributed routing component of the logical router for implementation by a plurality of managed forwarding elements at a plurality of machines, the plurality of machines comprising at least the gateway machines to which the uplinks are assigned; and

defining a third interface for the first centralized gateway component, the third interface for the first centralized gateway component to exchange traffic with the distributed routing component.

2. The method of claim 1 further comprising configuring the first centralized gateway component to exchange dynamic routing information with the external network, wherein routes learned by the first centralized gateway component through the exchange of dynamic routing information are incorporated into a routing information base (RIB) of the first centralized gateway component for output via the first local interface.

3. The method of claim 1, wherein the first centralized gateway component learns routing information from the external network using a dynamic routing protocol and provides the routing information for incorporation into a RIB of the distributed routing component.

4. A method for defining a centralized gateway component of a logical router, the method comprising:

for each of a plurality of uplinks configured for the logical router, assigning the uplink to a different gateway machine;

for a first one of the uplinks, defining a first centralized gateway component of the logical router for implementation on a first gateway machine to which the first uplink is assigned;

defining a first local interface for the first centralized gateway component configured according to the first uplink, the first local interface for the first centralized gateway component to forward traffic to a network external to the implementation of the logical router;

defining a second interface for the first centralized gateway component configured according to a second uplink, the second interface for redirecting traffic processed according to the second uplink configuration to a second centralized gateway component implemented on a second gateway machine for the second centralized gateway component to forward the traffic to the external network; and

configuring the first centralized gateway component to exchange dynamic routing information with the external network, wherein routes learned by the first centralized gateway component through the exchange of dynamic routing information are incorporated into a routing information base (RIB) of the first centralized gateway component for output via the first local interface, wherein the second centralized gateway component also exchanges dynamic routing information with the external network, wherein routes learned by the second centralized gateway component are incorporated into the RIB of the first centralized gateway component for output via the second interface.

5. The method of claim 4, wherein routes learned by the first centralized gateway component have a shorter administrative distance in the RIB of the first centralized gateway component than routes learned by the second centralized gateway component.

6. The method of claim 4, wherein routes learned by the first centralized gateway component are preferred by the first centralized gateway component to routes learned by the second centralized gateway component.

7. The method of claim 4 further comprising defining a distributed routing component of the logical router for implementation by a plurality of managed forwarding elements at a plurality of machines, the plurality of machines comprising at least the gateway machines to which the uplinks are assigned.

8. A method for defining a centralized gateway component of a logical router, the method comprising:

for each of a plurality of uplinks configured for the logical router, assigning the uplink to a different gateway machine;

for a first one of the uplinks, defining a first centralized gateway component of the logical router for implementation on a first gateway machine to which the first uplink is assigned;

defining a first local interface for the first centralized gateway component configured according to the first uplink, the first local interface for the first centralized gateway component to forward traffic to a network external to the implementation of the logical router;

defining a second interface for the first centralized gateway component configured according to a second uplink, the second interface for redirecting traffic processed according to the second uplink configuration to a second centralized gateway component implemented on a second gateway machine for the second centralized gateway component to forward the traffic to the external network; and

defining a distributed routing component of the logical router for implementation by a plurality of managed forwarding elements at a plurality of machines, the plurality of machines comprising at least the gateway machines to which the uplinks are assigned, wherein the first centralized gateway component learns routing information from the external network using a dynamic routing protocol, and passes the learned routing information to a centralized network controller for incorporation into the RIB of the distributed routing component.

9. The method of claim 8, wherein the centralized network controller distributes the RIB to the plurality of machines that implement the distributed routing component.

10. The method of claim 8, wherein the first centralized gateway component receives traffic directly from the external network through the first interface.

11. A method for defining centralized gateway components of a logical router, the method comprising:

for each of a plurality of uplinks configured for the logical router, assigning the uplink to a different gateway machine;

for a first one of the uplinks, defining a first centralized gateway component of the logical router for implementation on a first gateway machine to which the first uplink is assigned;

defining a first local interface for the first centralized gateway component configured according to the first uplink, the first local interface for the first centralized gateway component to forward traffic to a network external to the implementation of the logical router;

defining a second interface for the first centralized gateway component configured according to a second uplink, the second interface of the first centralized gateway component for redirecting traffic processed according to the second uplink configuration to a second centralized gateway component implemented on a second gateway machine for the second centralized gateway component to forward the traffic to the external network;

for a second one of the uplinks, defining the second centralized gateway component of the logical router for implementation on the second gateway machine to which the second uplink is assigned;

defining a first local interface for the second centralized gateway component configured according to the second uplink, the first local interface for the second centralized gateway component to forward traffic to the external network; and

defining a second interface for the second centralized gateway component configured according to the first uplink, the second interface of the second centralized gateway component for redirecting traffic processed according to the first uplink configuration to the first centralized gateway component for the first centralized gateway component to forward the traffic to the external network.

12. The method of claim 11, wherein the first and second uplinks have different service policies configured.

13. The method of claim 11, wherein the first and second uplinks have different L3 connectivity with the external network.

14. A non-transitory machine readable medium storing a program which when executed by at least one processing unit defines a centralized gateway component of a logical router, the program comprising sets of instructions for:

for each of a plurality of uplinks configured for the logical router, assigning the uplink to a different gateway machine;

for a first one of the uplinks, defining a first centralized gateway component of the logical router for implementation on a first gateway machine to which the first uplink is assigned;

defining a first local interface for the first centralized gateway component configured according to the first uplink, the first local interface for the first centralized gateway component to forward traffic to a network external to the implementation of the logical router;

defining a second interface for the first centralized gateway component configured according to a second uplink, the second interface for redirecting traffic processed according to the second uplink configuration to a second centralized gateway component implemented on a second gateway machine for the second centralized gateway component to forward the traffic to the external network;

defining a distributed routing component of the logical router for implementation by a plurality of managed forwarding elements at a plurality of machines, the plurality of machines comprising at least the gateway machines to which the uplinks are assigned; and

defining a third interface for the first centralized gateway component, the third interface for the first centralized gateway component to exchange traffic with the distributed routing component.

15. The non-transitory machine readable medium of claim 14, wherein the program further comprises a set of instructions for configuring the first centralized gateway component to exchange dynamic routing information with the external network, wherein routes learned by the first centralized gateway component through the exchange of dynamic routing information are incorporated into a routing information base (RIB) of the first centralized gateway component for output via the first local interface.

16. The non-transitory machine readable medium of claim 14, wherein the first centralized gateway component learns routing information from the external network using a dynamic routing protocol and provides the routing information for incorporation into a RIB of the distributed routing component.

17. A non-transitory machine readable medium storing a program which when executed by at least one processing unit defines a centralized gateway component of a logical router, the program comprising sets of instructions for:

for each of a plurality of uplinks configured for the logical router, assigning the uplink to a different gateway machine;

for a first one of the uplinks, defining a first centralized gateway component of the logical router for implementation on a first gateway machine to which the first uplink is assigned;

defining a first local interface for the first centralized gateway component configured according to the first uplink, the first local interface for the first centralized gateway component to forward traffic to a network external to the implementation of the logical router;

defining a second interface for the first centralized gateway component configured according to a second uplink, the second interface for redirecting traffic processed according to the second uplink configuration to a second centralized gateway component implemented on a second gateway machine for the second centralized gateway component to forward the traffic to the external network; and

configuring the first centralized gateway component to exchange dynamic routing information with the external network, wherein routes learned by the first centralized gateway component through the exchange of dynamic routing information are incorporated into a routing information base (RIB) of the first centralized gateway component for output via the first local interface, wherein the second centralized gateway component also exchanges dynamic routing information with the external network, wherein routes learned by the second centralized gateway component are incorporated into the RIB of the first centralized gateway component for output via the second interface.

18. The non-transitory machine readable medium of claim 17, wherein routes learned by the first centralized gateway component have a shorter administrative distance in the RIB of the first centralized gateway component than routes learned by the second centralized gateway component.

19. The non-transitory machine readable medium of claim 17, wherein the program further comprises a set of instructions for defining a distributed routing component of the logical router for implementation by a plurality of managed forwarding elements at a plurality of machines, the plurality of machines comprising at least the gateway machines to which the uplinks are assigned.

20. A non-transitory machine readable medium storing a program which when executed by at least one processing unit defines centralized gateway components of a logical router, the program comprising sets of instructions for:

for each of a plurality of uplinks configured for the logical router, assigning the uplink to a different gateway machine;

for a first one of the uplinks, defining a first centralized gateway component of the logical router for implementation on a first gateway machine to which the first uplink is assigned; and

defining a first local interface for the first centralized gateway component configured according to the first uplink, the first local interface for the first centralized gateway component to forward traffic to a network external to the implementation of the logical router;

defining a second interface for the first centralized gateway component configured according to a second uplink, the second interface of the first centralized gateway component for redirecting traffic processed according to the second uplink configuration to a second centralized gateway component implemented on a second gateway machine for the second centralized gateway component to forward the traffic to the external network;

for a second one of the uplinks, defining the second centralized gateway component of the logical router for implementation on the second gateway machine to which the second uplink is assigned;

defining a first local interface for the second centralized gateway component configured according to the second uplink, the first local interface for the second centralized gateway component to forward traffic to the external network; and

defining a second interface for the second centralized gateway component configured according to the first uplink, the second interface of the second centralized gateway component for redirecting traffic processed according to the first uplink configuration to the first centralized gateway component for the first centralized gateway component to forward the traffic to the external network.

21. The non-transitory machine-readable medium of claim 20, wherein the first and second uplinks have different service policies configured.

22. The non-transitory machine-readable medium of claim 20, wherein the first and second uplinks have different L3 connectivity with the external network.