Logical router with multiple routing components

• US 9,787,605 B2
• Filed: 07/30/2015
• Issued: 10/10/2017
• Est. Priority Date: 01/30/2015
• Status: Active Grant

• Current Assignee: Nicira Incorporated (Broadcom, Inc.)
• Original Assignee: Nicira Incorporated (Broadcom, Inc.)
• Inventors: Zhang, Ronghua, Chandrashekhar, Ganesan, Ravinoothala, Sreeram, Fan, Kai-Wei
• Primary Examiner(s): Zaidi, Iqbal
• Application Number:
  US14/814,473
• Publication Number:
  US 20160226754A1
• Time in Patent Office: 803 Days
• Field of Search: 370328-339, 370389-409
• 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 implementing a logical router in a network. The method receives a definition of a logical router for implementation on a set of network elements. The method defines several routing components for the logical router. Each of the defined routing components includes a separate set of routes and separate set of logical interfaces. The method implements the several routing components in the network. In some embodiments, the several routing components include one distributed routing component and several centralized routing components.

Claims

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

at a set of network controllers, receiving a definition of a logical router for implementation by a set of network elements, the definition of the logical router comprising specification of a plurality of interfaces for connecting with an external network;

defining a plurality of routing components for the logical router, each of the defined routing components comprising a separate set of routes and separate set of logical interfaces, wherein defining the plurality of routing components comprises;

assigning a first one of the plurality of interfaces to a first gateway machine and a second one of the plurality of interfaces to a second gateway machine;

defining a first centralized routing component for implementation on the first gateway machine by defining (i) a first interface for the first centralized routing component using configuration details of the first interface assigned to the first gateway machine and (ii) a second interface for the first centralized routing component used to communicate with a distributed routing component; and

defining a second centralized routing component for implementation on the second gateway machine by defining (i) a first interface for the second centralized routing component using configuration details of the second interface assigned to the second gateway machine and (ii) a second interface for the second centralized routing component used to communicate with the distributed routing component; and

generating data for configuring the set of network elements to implement the plurality of routing components of the logical router in the network.

2. The method of claim 1, wherein the plurality of routing components comprises the distributed routing component and a plurality of centralized routing components that includes at least the first and second centralized routing components.

3. The method of claim 2 further comprising automatically defining a logical switch for logically handling traffic between the distributed routing component and the plurality of centralized routing components.

4. The method of claim 3, wherein implementing the plurality of routing components in the network comprises implementing each of the centralized routing components on a single machine and implementing the distributed routing component and logical switch across a plurality of machines.

5. The method of claim 1, wherein each interface comprises a network address and a data link address.

6. The method of claim 5, wherein network address data for the first interface of the first centralized routing component is based on network address data for the first one of the plurality of interfaces and network address data for the second interface of the first centralized routing component is generated separately from any configuration details of the definition of the logical router.

7. The method of claim 5, wherein the second interface of the first centralized routing component and the second interface of the second centralized routing component have different network addresses and different data link layer addresses.

8. The method of claim 5, wherein the second interface of the first centralized routing component and the second interface of the second centralized routing component have a same network address and different data link layer addresses.

9. The method of claim 1, wherein defining the plurality of routing components further comprises defining a logical switch with ports to which the second interface of the first centralized routing component, the second interface of the second centralized routing component, and an interface of the distributed routing component all couple.

10. The method of claim 1, wherein the definition of the logical router is received through an application programming interface (API).

11. The method of claim 1, wherein the logical router is a first logical router, the method further comprising receiving a definition of a second logical router that connects to an interface of the first logical router.

12. The method of claim 11, wherein the second logical router only communicates with the external network through the first logical router.

13. The method of claim 12 further comprising defining a single distributed routing component for the second logical router when no stateful services are configured for the second logical router.

14. The method of claim 12 further comprising defining (i) a distributed routing component and (ii) two centralized routing components for the second logical router when stateful services are configured for the second logical router, each of the defined routing components for the second logical router comprising a separate set of routes and a separate set of logical interfaces.

15. The method of claim 14 further comprising defining a logical switch with ports to which an interface of each of the two centralized routing components and a single interface of a distributed routing component of the first logical router couple.

16. The method of claim 14, wherein a first of the two centralized routing components of the second logical router is designated as active and a second of the two centralized routing components of the second logical router is designated as standby, wherein the first centralized routing component of the second logical router responds to ARP requests and the second centralized routing component of the second logical router does not respond to ARP requests.

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

at the network controller, receiving a definition of a logical router for implementation by a set of network elements, the definition of the logical router comprising specification of a plurality of interfaces for connecting with an external network;

defining a plurality of routing components for the logical router, each of the defined routing components comprising a separate set of routes and separate set of logical interfaces, wherein defining the plurality of routing components comprises;

assigning a first one of the plurality of interfaces to a first gateway machine and a second one of the plurality of interfaces to a second gateway machine;

defining a first centralized routing component for implementation on the first gateway machine by defining (i) a first interface for the first centralized routing component using configuration details of the first interface assigned to the first gateway machine and (ii) a second interface for the first centralized routing component used to communicate with a distributed routing component; and

defining a second centralized routing component for implementation on the second gateway machine by defining (i) a first interface for the second centralized routing component using configuration details of the second interface assigned to the second gateway machine and (ii) a second interface for the second centralized routing component used to communicate with the distributed routing component; and

generating data for configuring the set of network elements to implement the plurality of routing components of the logical router in the network.

18. The machine readable medium of claim 17, wherein the plurality of routing components comprises the distributed routing component and a plurality of centralized routing components that includes at least the first and second centralized routing components, the program further comprising a set of instructions for automatically defining a logical switch for logically handling traffic between the distributed routing component and the plurality of centralized routing components, wherein the set of instructions for implementing the plurality of routing components in the network comprises a set of instructions for implementing each of the centralized routing components on a single machine and implementing the distributed routing component and logical switch across a plurality of machines.

19. The machine readable medium of claim 17, wherein each interface comprises a network address and a data link address.

20. The machine readable medium of claim 19, wherein network address data for the first interface of the first centralized routing component is based on network address data for the first one of the plurality of interfaces and network address data for the second interface of the first centralized routing component is generated separately from any configuration details of the definition of the logical router.

21. The machine readable medium of claim 17, wherein the set of instructions for defining the plurality of routing components further comprises a set of instructions for defining a logical switch with ports to which the second interface of the first centralized routing component, the second interface of the second centralized routing component, and an interface of the distributed routing component all couple.

22. The machine readable medium of claim 17, wherein the logical router is a first logical router, the program further comprising a set of instructions for receiving a definition of a second logical router that connects to an interface of the first logical router, wherein the second logical router only communicates with the external network through the first logical router.

23. The machine readable medium of claim 22, wherein the program further comprises a set of instructions for defining a single distributed routing component for the second logical router when no stateful services are configured for the second logical router.

24. The machine readable medium of claim 22, wherein the program further comprises a set of instructions for defining (i) a distributed routing component and (ii) two centralized routing components for the second logical router when stateful services are configured for the second logical router, each of the defined routing components for the second logical router comprising a separate set of routes and a separate set of logical interfaces.

25. The machine readable medium of claim 24, wherein the program further comprises a set of instructions for defining a logical switch with ports to which an interface of each of the two centralized routing components and a single interface of a distributed routing component of the first logical router couple.