Techniques for managing software defined networking controller in-band communications in a data center network

• US 10,171,357 B2
• Filed: 07/12/2016
• Issued: 01/01/2019
• Est. Priority Date: 05/27/2016
• Status: Active Grant

• Current Assignee: Cisco Technology, Inc. (Cisco Systems, Inc.)
• Original Assignee: Cisco Technology, Inc. (Cisco Systems, Inc.)
• Inventors: Chander, Vijay, Yang, Yibin, Jain, Praveen, Mehta, Munish
• Primary Examiner(s): Nguyen, Hanh N
• Application Number:
  US15/208,018
• Publication Number:
  US 20170346736A1
• Time in Patent Office: 903 Days
• CPC Class Codes: H04L 12/4633 Interconnection of networks using encapsulation techniques, e.g. tunneling
• CPC Class Codes: H04L 12/4641 Virtual LANs, VLANs, e.g. virtual private networks [VPN] LAN interconnection over a bridge based backbone H04L12/462; encapsulation techniques H04L12/4633; routing of packets H04L45/00; packet switches H04L49/00; virtual private networks for security H04L63/0272
• CPC Class Codes: H04L 45/74 Address processing for routing
• CPC Class Codes: H04L 45/745 Address table lookup; Address filtering

Abstract

According to one or more embodiments of this disclosure, a network controller in a data center network establishes a translation table for in-band traffic in a data center network, the translation table resolves ambiguous network addresses based on one or more of a virtual network identifier (VNID), a routable tenant address, or a unique loopback address. The network controller device receives packets originating from applications and/or an endpoints operating in a network segment associated with a VNID. The network controller device translates, using the translation table, unique loopback addresses and/or routable tenant addresses associated with the packets into routable tenant addresses and/or unique loopback addresses, respectively.

Claims

1. A method, comprising:

establishing, by a network controller device, a translation table for resolving network addresses for in-band traffic in a data center network based on one or more of a virtual network identifier (VNID), a routable tenant address, or a unique loopback address;

receiving, by the network controller device, a packet originating from an application associated with a first unique loopback address and intended for an endpoint in a first network segment associated with a first VNID, the endpoint associated with a second unique loopback address;

translating, by the network controller device using the translation table, the first unique loopback address into a first routable tenant address and the first VNID based on the first unique loopback address;

translating, by the network controller device using the translation table, the second loopback address into a second routable tenant address and the first VNID based on the second unique loopback address;

encapsulating the packet as an encapsulated packet having a header field including the first VNID, an outer address field including an address for a proxy device, an inner source address field including the first routable tenant address, and an inner destination field including the second routable tenant address;

forwarding, by the network controller device, the encapsulated packet to the proxy device to route the encapsulated packet in the data center network to the endpoint in the first network segment associated with the first VNID; and

updating a routing table based on migration of the endpoint from a first host to a second host.

2. The method of claim 1, further comprising:

decapsulating, by the network controller device, a second packet originating from the endpoint in the first network segment to determine the first VNID, the second routable tenant address, and the first routable tenant address;

translating, by the network controller device using the translation table, the first routable tenant address into the first unique loopback address based on the first VNID and the first routable tenant address;

translating, by the network controller device using the translation table, the second routable tenant address into the second unique loopback address based on the first VNID and the second routable tenant address; and

forwarding, by the network controller device, the second packet to the application associated with a first unique loopback address.

3. The method of claim 1, wherein updating of the routing table based on the migration of the endpoint from the first host to the second host is performed via the proxy device.

4. The method of claim 1, wherein forwarding the encapsulated packet to the proxy device further causes the proxy device to decapsulate the encapsulated packet to determine the VNID and the second routable tenant address.

5. The method of claim 1, wherein establishing the translation table for the in-band traffic further comprises:

indexing, in the translation table, each loopback address of a plurality of loopback addresses according to one respective VNID and one respective tenant address.

6. The method of claim 1, wherein the VNID is a virtual extensible LAN (VXLAN) identifier.

7. The method of claim 1, wherein the endpoint in the first network segment is a virtual machine (VM) hosted by a leaf node in the data center network.

8. A network controller device, comprising:

one or more computer processors; and

a memory storing instructions that, when executed by the one or more computer processors, cause the network controller device to;

establish a translation table for resolving network addresses for in-band traffic in a data center network based on one or more of a virtual network identifier (VNID), a routable tenant address, or a unique loopback address;

receive a packet originating from an application associated with a first unique loopback address and intended for an endpoint in a first network segment associated with a first VNID, the endpoint associated with a second unique loopback address;

translate, using the translation table, the first unique loopback address into a first routable tenant address and the first VNID based on the first unique loopback address;

translate, using the translation table, the second loopback address into a second routable tenant address and the first VNID based on the second unique loopback address;

encapsulate the packet as an encapsulated packet having a header field including the first VNID, an outer address field including an address for a proxy device, an inner source address field including the first routable tenant address, and an inner destination field including the second routable tenant address; and

forward the encapsulated packet to the proxy device to route the encapsulated packet in the data center network to the endpoint in the first network segment associated with the first VNID,

wherein,

a routing table is updated based on migration of the endpoint.

9. The network controller device of claim 8, wherein the instructions further cause the network controller device to:

decapsulate a second packet originating from the endpoint in the first network segment to determine the first VNID, the second routable tenant address, and the first routable tenant address;

translate, using the translation table, the first routable tenant address into the first unique loopback address based on the first VNID and the first routable tenant address;

translate, using the translation table, the second routable tenant address into the second unique loopback address based on the first VNID and the second routable tenant address; and

forward the second packet to the application associated with a first unique loopback address.

10. The network controller device of claim 8, wherein the proxy device updates the routing table based on the migration of the endpoint from a first host to a second host.

11. The network controller device of claim 8, wherein forwarding the encapsulated packet to the proxy device further causes the proxy device to decapsulate the encapsulated packet to determine the VNID and the second routable tenant address.

12. The network controller device of claim 8, wherein establishing the translation table for the in-band traffic further comprises:

indexing, in the translation table, each loopback address of a plurality of loopback addresses according to one respective VNID and one respective tenant address.

13. The network controller device of claim 8, wherein the VNID is a virtual extensible LAN (VXLAN) identifier.

14. The network controller device of claim 8, wherein the endpoint in the first network segment is a virtual machine (VM) hosted by a leaf node in the data center network.

15. A non-transitory computer-readable medium storing instructions that, when executed by a network controller device, cause the network controller device to:

establish a translation table for resolving network addresses for in-band traffic in a data center network based on one or more of a virtual network identifier (VNID), a routable tenant address, or a unique loopback address;

receive a packet originating from an application associated with a first unique loopback address and intended for an endpoint in a first network segment associated with a first VNID, the endpoint associated with a second unique loopback address;

translate, using the translation table, the first unique loopback address into a first routable tenant address and the first VNID based on the first unique loopback address;

translate, using the translation table, the second loopback address into a second routable tenant address and the first VNID based on the second unique loopback address;

encapsulate the packet as an encapsulated packet having a header field including the first VNID, an outer address field including an address for a proxy device, an inner source address field including the first routable tenant address, and an inner destination field including the second routable tenant address; and

forward the encapsulated packet to the proxy device to route the encapsulated packet in the data center network to the endpoint in the first network segment associated with the first VNID

wherein,

a routing table is updated based on migration of the endpoint.

16. The non-transitory computer-readable medium of claim 15, wherein the instructions further cause the network controller device to:

decapsulate a second packet originating from the endpoint in the first network segment to determine the first VNID, the second routable tenant address, and the first routable tenant address;

translate, using the translation table, the first routable tenant address into the first unique loopback address based on the first VNID and the first routable tenant address;

translate, using the translation table, the second routable tenant address into the second unique loopback address based on the first VNID and the second routable tenant address; and

forward the second packet to the application associated with a first unique loopback address.

17. The non-transitory computer-readable medium of claim 15, wherein the proxy device updates the routing table based on the migration of the endpoint from a first host to a second host.

18. The non-transitory computer-readable medium of claim 15, wherein forwarding the encapsulated packet to the proxy device further causes the proxy device to decapsulate the encapsulated packet to determine the VNID and the second routable tenant address.

19. The non-transitory computer-readable medium of claim 15, wherein establishing the translation table for the in-band traffic further comprises:

indexing, in the translation table, each loopback address of a plurality of loopback addresses according to one respective VNID and one respective tenant address.

20. The non-transitory computer-readable medium of claim 15, wherein the VNID is a virtual extensible LAN (VXLAN) identifier.