Autonomic locator/identifier separation protocol for secure hybrid cloud extension

Patent metadata

Field	Value
Publication number	US-9560018-B2
Application number	US-201414563688-A
Country	US
Kind code	B2
Filing date	Dec 8, 2014
Priority date	Dec 8, 2014
Publication date	Jan 31, 2017
Grant date	Jan 31, 2017

Abstract

A method is provided in one example embodiment and includes configuring a local network element as an autonomic registrar for a designated network domain; establishing an autonomic control plane (“ACP”) between the local network element and one or more remote network elements identified by local network element as a remote neighbor; designating a locally-defined subnet at the local network element to be extended to each of the one or more remote network elements; and executing an ACP command at the local network element, wherein the executing triggers a message to each of the one or more remote network elements, the message including information regarding the designated local subnet. The information included in the message is used by each of the remote network elements to auto-resolve its Locator/Identifier Separation Protocol (“LISP”) configuration, enabling the designated local subnet to be extended to each of the one or more remote network elements.

First claim

What is claimed is:

1. A method comprising:
configuring a local network element as an autonomic registrar for a designated network domain;
establishing an autonomic control plane (“ACP”) between the local network element and one or more remote network elements identified by the local network element as a remote neighbor;
designating a locally-defined subnet at the local network element to be extended to each of the one or more remote network elements; and
executing an ACP command at the local network element, wherein the executing triggers a message to each of the one or more remote network elements, the message including information regarding the designated local subnet;
wherein the information included in the message is used by each of the remote network elements to auto-resolve Locator/Identifier Separation Protocol (“LISP”) configuration of the remote network element, thereby enabling the designated local subnet to be extended to each of the one or more remote network elements.

2. The method of claim 1 , wherein the message is sent via the ACP.

3. The method of claim 1 , wherein the information included in the message identifies at least one of a LISP mode in which the remote network element is to operate, an index of a LISP interface, the designated local subnets, a default gateway for each of the designated local subnets, an Internet Protocol (“IP”) address for a proxy egress tunnel router (“PeTR”), an IP address for a map server function, and an IP address for a map resolver function.

4. The method of claim 1 , wherein the local network element is deployed in an enterprise data center and the one or more remote network elements are deployed in a public cloud network.

5. The method of claim 1 , wherein each of the local network element and the one or more remote network elements are LISP-enabled routers.

6. The method of claim 1 further comprising:
creating at the local network element a local LISP loopback interface and enabling routing on the local LISP loopback interface;
establishing secure IP tunnels between the local network element and each of one or more remote network elements.

7. The method of claim 1 , wherein the local network element comprises a proxy ingress/egress tunnel router (“PxTR”) and each of the one or more remote network elements comprises an ingress/egress tunnel router (“xTR”).

8. Non-transitory tangible media that includes code for execution and when executed by a processor is operable to perform operations comprising:
configuring a local network element as an autonomic registrar for a designated network domain;
establishing an autonomic control plane (“ACP”) between the local network element and one or more remote network elements identified by the local network element as a remote neighbor;
designating a locally-defined subnet at the local network element to be extended to each of the one or more remote network elements; and
executing an ACP command at the local network element, wherein the executing triggers a message to each of the one or more remote network elements, the message including information regarding the designated local subnet;
wherein the information included in the message is used by each of the remote network elements to auto-resolve Locator/Identifier Separation Protocol (“LISP”) configuration of the remote network element, thereby enabling the designated local subnet to be extended to each of the one or more remote network elements.

9. The media of claim 8 , wherein the message is sent via the ACP.

10. The media of claim 8 , wherein the information included in the message identifies at least one of a LISP mode in which the remote network element is to operate, an index of a LISP interface, the designated local subnets, a default gateway for each of the designated local subnets, an Internet Protocol (“IP”) address for a proxy egress tunnel router (“PeTR”), an IP address for a map server function, and an IP address for a map resolver function.

11. The media of claim 8 , wherein each of the local network element and the one or more remote network elements are LISP-enabled routers.

12. The media of claim 8 , wherein the operations further comprise:
creating at the local network element a local LISP loopback interface and enabling routing on the local LISP loopback interface;
establishing secure IP tunnels between the local network element and each of one or more remote network elements.

13. The media of claim 8 , wherein the local network element comprises a proxy ingress/egress tunnel router (“PxTR”) and each of the one or more remote network elements comprises an ingress/egress tunnel router (“xTR”).

14. An apparatus comprising:
a memory element configured to store data; and
a processor operable to execute instructions associated with the data;
wherein the apparatus:
configures a local network element as an autonomic registrar for a designated network domain;
establishes an autonomic control plane (“ACP”) between the local network element and one or more remote network elements identified by the local network element as a remote neighbor;
designates a locally-defined subnet at the local network element to be extended to each of the one or more remote network elements; and
executes an ACP command at the local network element, wherein the executing triggers a message to each of the one or more remote network elements, the message including information regarding the designated local subnet;
wherein the information included in the message is used by each of the remote network elements to auto-resolve Locator/Identifier Separation Protocol (“LISP”) configuration of the remote network element, thereby enabling the designated local subnet to be extended to each of the one or more remote network elements.

15. The apparatus of claim 14 , wherein the message is sent via the ACP.

16. The apparatus of claim 14 , wherein the information included in the message identifies at least one of a LISP mode in which the remote network element is to operate, an index of a LISP interface, the designated local subnets, a default gateway for each of the designated local subnets, an Internet Protocol (“IP”) address for a proxy egress tunnel router (“PeTR”), an IP address for a map server function, and an IP address for a map resolver function.

17. The apparatus of claim 14 , wherein the local network element is deployed in an enterprise data center and the one or more remote network elements are deployed in a public cloud network.

18. The apparatus of claim 14 , wherein each of the local network element and the one or more remote network elements are LISP-enabled routers.

19. The apparatus of claim 14 , wherein the local network element comprises a proxy ingress/egress tunnel router (“PxTR”).

20. The apparatus of claim 14 , wherein each of the one or more remote network elements comprises an ingress/egress tunnel router (“xTR”).

Assignees

• Cisco Tech Inc

Inventors

• Bellagamba Patrice
• Behringer Michael H
• Freitas Santiago Vazquez

Classifications

• H04L63/0281 Primary

  Proxies · CPC title

• H04L61/103 Primary

  across network layers, e.g. resolution of network layer into physical layer addresses or address resolution protocol [ARP] · CPC title

• H04L67/10

  in which an application is distributed across nodes in the network (software deployment G06F8/60; multiprogramming arrangements G06F9/46) · CPC title

• H04L67/141

  Setup of application sessions (admission control or resource allocation in data switching networks H04L47/70) · CPC title

• H04L45/64

  using an overlay routing layer · CPC title