Connectivity to internet via shared services in enterprise fabric based network with lisp control plane

Patent metadata

Field	Value
Publication number	US-2018367337-A1
Application number	US-201816010444-A
Country	US
Kind code	A1
Filing date	Jun 16, 2018
Priority date	Jun 19, 2017
Publication date	Dec 20, 2018
Grant date	—

Abstract

In one embodiment, a method is performed at a first node. The method may include receiving, at a first node, a request from a source host associated with a network to communicate with a destination host. The first node may determine whether the destination host is associated with the network. If the destination host is not associated with the network, the first node may determine an instance identifier (IID) and a proxy egress tunnel router (PETR) locator address used to communicate with the destination host. The first node may send an indicator to an ingress tunnel router (ITR) to encapsulate a packet with the IID and the PETR locator address before sending the packet from the source host to the destination host.

First claim

What is claimed is:

1 . A method comprising:
receiving, at a first node, a request from a source host associated with a network to communicate with a destination host; determining whether the destination host is associated with the network; on a condition that the destination host is not associated with the network, determining an instance identifier (IID) and a proxy egress tunnel router (PETR) locator address used to communicate with the destination host; and sending an indicator to an ingress tunnel router (ITR) to encapsulate a packet with the IID and the PETR locator address before sending the packet from the source host to the destination host.

2 . The method of claim 1 , wherein at least one of a source IID or a destination IID is associated with a virtual network used to send the packet from the source host to the destination host.

3 . The method of claim 2 , further comprising configuring an ingress tunnel router (ITR) with the IID and the PETR locator address associated with the virtual network.

4 . The method of claim 1 , wherein determining the IID and the PETR locator address used to communicate with the destination host comprises looking up a destination prefix in an extranet policy table.

5 . The method of claim 1 , further comprising:
generating a policy as a function of the IID and the PETR locator address; and sending an unknown map reply (UMR) comprising the policy to the ITR.

6 . The method of claim 1 , wherein the IID comprises an encapsulation IID, the method further comprising using a proxy egress tunnel router (PETR) configuration at the ingress tunnel router (ITR) to determine the encapsulation IID and the PETR locator address.

7 . The method of claim 1 , wherein the IID and the PETR locator address are associated with a shared virtual routing and forwarding (VRF) instance.

8 . The method of claim 1 , further comprising:
configuring a mapping system with the IID and the PETR locator address; and sending a reply from the mapping system, the reply comprising the IID and the PETR locator address.

9 . The method of claim 1 , further comprising encoding the IID and the PETR locator address.

10 . A device comprising:
a network interface in communication with a network; a processor configured to execute computer readable instructions included on a non-transitory memory; and a non-transitory memory including processor-readable instructions, that when executed by the processor, cause the device to
receive a request from a source host associated with the network to communicate with a destination host;
determine whether the destination host is associated with the network;
on a condition that the destination host is not associated with the network, determine an instance identifier (IID) and a proxy egress tunnel router (PETR) locator address used to communicate with the destination host; and
send an indicator to an ingress tunnel router (ITR) to encapsulate a packet with the IID and the PETR locator address before sending the packet from the source host to the destination host.

11 . The device of claim 10 , wherein at least one of a source IID or a destination IID is associated with a virtual network used to send the packet from the source host to the destination host.

12 . The device of claim 11 , wherein the processor-readable instructions cause the device to configure an ingress tunnel router (ITR) with the IID and the PETR locator address associated with the virtual network.

13 . The device of claim 10 , wherein determining the IID and the PETR locator address used to communicate with the destination host comprises looking up a destination prefix in an extranet policy table.

14 . The device of claim 10 , wherein the processor-readable instructions cause the device to:
generate a policy as a function of the IID and the PETR locator address; and send an unknown map reply (UMR) comprising the policy to the ITR.

15 . The device of claim 10 , wherein the IID comprises an encapsulation IID, and wherein the processor-readable instructions cause a proxy egress tunnel router (PETR) configuration to be used at the ingress tunnel router (ITR) to determine the encapsulation IID and the PETR locator address.

16 . The device of claim 10 , wherein the IID and the PETR locator address are associated with a shared virtual routing and forwarding (VRF) instance.

17 . The device of claim 10 , wherein the processor-readable instructions cause the device to:
configure a mapping system with the IID and the PETR locator address; and sending a reply from the mapping system, the reply comprising the IID and the PETR locator address.

18 . The device of claim 10 , wherein the processor-readable instructions cause the device to encode the IID and the PETR locator address.

19 . The device of claim 10 , wherein the device comprises at least one of a map server map resolver (MSMR) device or a gateway device.

20 . A non-transitory computer readable storage medium storing one or more programs, the one or more programs comprising instructions, which, when executed by a computing device with a non-transitory memory and one or more processors, cause the computing device to perform or cause performance of:
receiving a request from a source host associated with a network to communicate with a destination host; determining whether the destination host is associated with the network; on a condition that the destination host is not associated with the network, determining an instance identifier (IID) and a proxy egress tunnel router (PETR) locator address used to communicate with the destination host; and sending an indicator to an ingress tunnel router (ITR) to encapsulate a packet with the IID before sending the packet from the source host to the destination host.

Assignees

• Cisco Tech Inc

Inventors

• Jain Prakash Chand
• Hooda Sanjay Kumar
• Moreno Victor M
• Kondalam Satish Kumar

Classifications

• H04L12/4633 Primary

  Interconnection of networks using encapsulation techniques, e.g. tunneling · CPC title

• H04L12/4625

  Single bridge functionality, e.g. connection of two networks over a single bridge · CPC title

• H04L45/74

  Address processing for routing · CPC title

• H04L2212/00

  Encapsulation of packets · CPC title