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

1. A method comprising:

receiving, by a network controller device, a packet intended for an endpoint;

translating, by the network controller device using a table, a first loopback address into a first routable tenant address;

translating, by the network controller device using the table, a second loopback address into a second routable tenant address;

encapsulating the packet as an encapsulated packet having a header field, 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; and

updating a routing table of the proxy device based on migration of the endpoint.

2. The method of claim 1 , further comprising:

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

translating, by the network controller device using the table, the first routable tenant address into the first loopback address based on at least the first routable tenant address;

translating, by the network controller device using the table, the second routable tenant address into the second loopback address based on at least the second routable tenant address; and

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

3. The method of claim 1 , wherein updating of the routing table of the proxy device based on the migration of the endpoint 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 a virtual network identifier (VNID) and the second routable tenant address.

5. The method of claim 1 , further comprising:

establishing, by the network controller device, the 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; and

indexing, in the 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 5 , wherein the VNID is a virtual extensible LAN (VXLAN) identifier.

7. The method of claim 1 , wherein the endpoint is a virtual machine (VM) hosted by a leaf node in a 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:

receive a packet intended for an endpoint,

translate, using a table, a first loopback address into a first routable tenant address,

translate, using the table, a second loopback address into a second routable tenant address,

encapsulate the packet as an encapsulated packet having a header field including 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,

forward the encapsulated packet to the proxy device, and

update a routing table of the proxy device 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 to determine the second routable tenant address and the first routable tenant address;

translate, using the table, the first routable tenant address into the first loopback address based on at least the first routable tenant address;

translate, using the table, the second routable tenant address into the second loopback address based on at least the second routable tenant address; and

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

10. The network controller device of claim 8 , wherein the proxy device updates the routing table of the proxy device 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 a virtual network identifier (VNID) and the second routable tenant address.

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

establish the 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; and

index, in the 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 12 , wherein the VNID is a virtual extensible LAN (VXLAN) identifier.

14. The network controller device of claim 8 , wherein the endpoint is a virtual machine (VM) hosted by a leaf node in a 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:

receive a packet intended for an endpoint;

translate, using a table, a first loopback address into a first routable tenant address;

translate, using the table, a second loopback address into a second routable tenant address;

encapsulate the packet as an encapsulated packet having a header field including 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;

forward the encapsulated packet to the proxy device; and

update a routing table of the proxy device 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 to determine the second routable tenant address and the first routable tenant address;

translate, using the table, the first routable tenant address into the first loopback address based on at least the first routable tenant address;

translate, using the table, the second routable tenant address into the second loopback address based on at least the second routable tenant address; and

forward the second packet to an 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 of the proxy device 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 a virtual network identifier (VNID) and the second routable tenant address.

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

establish the 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; and

index, in the 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 19 , wherein the VNID is a virtual extensible LAN (VXLAN) identifier.