Data routing of extranet flows in fabric networks
In accordance with various embodiments, a method is performed including receiving, at a first node associated with a first instance identifier, a packet from a first host addressed to a second host. The method includes sending, from the first node to the second node, the packet. The method includes receiving, from the second node, a solicit map-request for the second host including the first instance identifier of the first node and the second instance identifier of the second node for the second host. The method includes sending, in response to receiving the solicit map-request for the second host, a map-request for the second host. The method includes receiving, in response to sending the map-request for the second host, a map-reply indicating a third node associated with the second instance identifier. The method includes sending, from the first node to the third node, the packet.
1. A method comprising:
receiving, at a first node associated with a first instance identifier, a packet from a first host addressed to a second host;
sending, from the first node to a second node associated with a second instance identifier, the packet from the first host addressed to the second host, wherein sending, from the first node to the second node, the packet from the first host addressed to the second host comprises identifying the second node based on a map-cache entry of the second host stored by the first node;
receiving, from the second node, a solicit map-request for the second host, the solicit map-request including the first instance identifier of the first node and the second instance identifier of the second node;
sending, in response to receiving the solicit map-request for the second host, a map-request for the second host;
receiving, in response to sending the map-request for the second host, a map-reply indicating a third node associated with the second instance identifier;
sending, from the first node to the third node, the packet from the first host addressed to the second host;
updating the map-cache entry of the second host stored by the first node to include information regarding the third node rather than information regarding the second node; and
sending one or more additional map-requests for other instance identifiers of the second host to update additional map-cache entries of the second host stored by the first node.
2. The method of claim 1 , further comprising encapsulating the packet with the second instance identifier prior to sending the packet from the first node to the second node.
3. The method of claim 1 , wherein the first instance identifier of the first node is included in an Endpoint Identifier (EID)-Prefix field of the solicit map-request.
4. The method of claim 1 , wherein the second instance identifier of the second node is included in a Source-Endpoint Identifier (EID) field of the solicit map-request.
5. The method of claim 1 , wherein the map-request for the second host includes the first instance identifier of the first node received in the solicit map-request.
6. The method of claim 1 , wherein the solicit map-request is received in response to determining that the second host is not associated with the second node.
7. The method of claim 1 , wherein the second instance identifier is different than the first instance identifier.
8. A first node associated with a first instance identifier, the first node comprising:
a network interface; and
one or more processors configured to:
receive, via the network interface, a packet from a first host addressed to a second host;
send, via the network interface to a second node associated with a second instance identifier, the packet from the first host addressed to the second host, wherein the one or more processors being configured to send the packet from the first host addressed to the second host comprises the one or more processors being operative to identify the second node based on a map-cache entry of the second host stored by the first node;
receive, via the network interface from the second node, a solicit map-request for the second host, the solicit map-request including the first instance identifier of the first node and second instance identifier of the second node;
send, via the network interface in response to receiving the solicit map-request for the second host, a map-request for the second host;
receive, via the network interface in response to sending the map-request for the second host, a map-reply indicating a third node associated with the second instance identifier;
send, via the network interface to the third node, the packet from the first host addressed to the second host;
update the map-cache entry of the second host stored by the first node to include information regarding the third node rather than information regarding the second node; and
send one or more additional map-requests for other hosts associated with the second instance identifier to update additional map-cache entries of the other hosts stored by the first node.
9. The first node of claim 8 , wherein the first instance identifier of the first node is included in an Endpoint Identifier (EID)-Prefix field of the solicit map-request and the second instance identifier of the second node is included in a Source-Endpoint Identifier (EID) field of the solicit map-request.
10. A non-transitory computer readable storage medium that stores a set of instructions which when executed by a processor perform a method comprising:
receiving, at a first node associated with a first instance identifier, a packet from a first host addressed to a second host;
sending, from the first node to a second node associated with a second instance identifier, the packet from the first host addressed to the second host, wherein sending, from the first node to the second node, the packet from the first host addressed to the second host includes identifying the second node based on a map-cache entry of the second host stored by the first node;
receiving, from the second node, a solicit map-request for the second host, the solicit map-request including the first instance identifier of the first node and the second instance identifier of the second node;
sending, in response to receiving the solicit map-request for the second host, a map-request for the second host;
receiving, in response to sending the map-request for the second host, a map-reply indicating a third node associated with the second instance identifier;
sending, from the first node to the third node, the packet from the first host addressed to the second host;
updating the map-cache entry of the second host stored by the first node to include information regarding the third node rather than information regarding the second node; and
sending one or more additional map-requests for other instance identifiers of the second host to update additional map-cache entries of the second host stored by the first node.
11. The non-transitory computer readable storage medium of claim 10 , further comprising encapsulating the packet with the second instance identifier prior to sending the packet from the first node to the second node.
12. The non-transitory computer readable storage medium of claim 10 , wherein the first instance identifier of the first node is included in an Endpoint Identifier (EID)-Prefix field of the solicit map-request.
13. The non-transitory computer readable storage medium of claim 10 , wherein the second instance identifier of the second node is included in a Source-Endpoint Identifier (EID) field of the solicit map-request.
14. The non-transitory computer readable storage medium of claim 10 , wherein the map-request for the second host includes the first instance identifier of the first node received in the solicit map-request.
15. The non-transitory computer readable storage medium of claim 10 , wherein the solicit map-request is received in response to determining that the second host is not associated with the second node.
16. The non-transitory computer readable storage medium of claim 10 , wherein the second instance identifier is different than the first instance identifier.