Network device mobility

Patent metadata

Field	Value
Publication number	US-9647923-B2
Application number	US-201314011356-A
Country	US
Kind code	B2
Filing date	Aug 27, 2013
Priority date	Apr 9, 2013
Publication date	May 9, 2017
Grant date	May 9, 2017

Abstract

According to one example embodiment, an EID-NOTIFY packet is defined for use with the Location/Identifier Separation Protocol (LISP). A first-hop network element may send EID-NOTIFY responsive to decoding a data packet from a previously undetected host on its subnetwork. A site network element may receive EID-NOTIFY, and send a MAP-REGISTER message to a mapping system. EID-NOTIFY may have substantially the same format as MAP-NOTIFY. This may enable the site network element to be removed more than one hop from the subnetwork.

First claim

What is claimed is:

1. A method to be performed by a first network element, comprising:
identifying an endpoint machine communicatively coupled to the first network element, the endpoint machine having an associated endpoint identifier (EID); and
without performing a Location/Identifier Separation Protocol (LISP) encapsulation or decapsulation, sending an EID-NOTIFY message including the EID and a routing locator (RLOC) of the first network element, the EID-NOTIFY message configured to inform a second network element the endpoint machine is communicatively coupled to the first network element.

2. The method of claim 1 , wherein the second network element is configured to provide LISP encapsulation or decapsulation.

3. The method of claim 1 , wherein sending the EID-NOTIFY message comprises providing the message on a control plane.

4. The method of claim 1 , wherein the EID-NOTIFY message is a LISP encapsulated control message.

5. The method of claim 1 , wherein the EID-NOTIFY message has substantially the same form as a LISP MAP-NOTIFY message.

6. The method of claim 1 , wherein the EID-NOTIFY message includes a LISP type value of fourteen.

7. The method of claim 1 , further comprising:
receiving an EID-CONTROL message; and
sending a MAP-REGISTER message.

8. The method of claim 7 , wherein sending the EID-CONTROL message comprises multicasting the EID-CONTROL message.

9. A first-hop network element, comprising:
a network interface;
a processor; and
a memory having stored thereon executable instructions configured to instruct the processor to:
receive a packet on the network interface from an endpoint host, the packet comprising an endpoint identifier (EID) associated with the endpoint host;
format an EID-NOTIFY message, including the EID, a routing locator (RLOC) of the first-hop network element, and a type value identifying the message as an EID-NOTIFY message; and
without performing a Location/Identifier Separation Protocol (LISP) encapsulation or decapsulation, forward the EID-NOTIFY message to a site gateway router, wherein the site gateway router is located two or more hops from the endpoint host.

10. The first-hop network element of claim 9 , wherein the instructions are further configured to instruct the processor to add the EID to a local routing database.

11. The first-hop network element of claim 9 , wherein the EID-NOTIFY message is a LISP encapsulated control message.

12. The first-hop network element of claim 11 , wherein the EID-NOTIFY message has substantially the same format as a LISP MAP-NOTIFY message.

13. The first-hop network element of claim 11 , wherein the EID-NOTIFY message has a LISP type value of fourteen.

14. The first-hop network element of claim 11 , wherein the first-hop network element is not configured to perform LISP encapsulation and decapsulation.

15. A site network element, comprising:
a processor;
a network interface; and
a memory having stored thereon a routing table and software instructions configured to instruct the processor to:
receive an incoming EID-NOTIFY message on the network interface, the EID-NOTIFY message including an endpoint identifier (EID) for a host connected to a subnetwork of the site network element and a routing locator (RLOC) of the first-hop router, wherein the host is located two or more hops from the site network element; and
without performing a Location/Identifier Separation Protocol (LISP) encapsulation or decapsulation, send an outgoing MAP-REGISTER message on the network interface.

16. The site network element of claim 15 , wherein sending the outgoing MAP-REGISTER message on the network interface comprises multicasting the MAP-REGISTER message.

17. The site network element of claim 15 , wherein the EID-NOTIFY message is a LISP encapsulated control message.

18. The site network element of claim 15 , wherein the EID-NOTIFY message has substantially the same format as a LISP MAP-NOTIFY message.

19. The site network element of claim 15 , wherein the EID-NOTIFY message includes a LISP type value of fourteen.

20. The site network element of claim 15 , wherein the EID-NOTIFY message is received on the network interface over a LISP control plane.

Assignees

• Cisco Tech Inc

Inventors

• Subramanian Srinivas
• Agrawal Rituparna
• Shvarts Lev
• Leong Johnson
• Alvarez Daniel A

Classifications

• H04L45/02 Primary

  Topology update or discovery · CPC title