# US 12,113,698 B2 · Techniques for allowing software defined (SD) network fabrics to accept network devices from other fabric technologies > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 12,113,698 B2 - Document ID: US12113698B2 - Status: Granted - Kind: B2 - Application number: 17/446,918 - Filed: 2021-09-03 - Published: 2023-03-09 - Granted: 2024-10-08 - Earliest claimed: 2021-09-03 - Assignees: Cisco Technology, Inc. - Applicants: Cisco Technology, Inc. - Inventors: Rajeev Kumar; Sanjay K. Hooda; Balaji Pitta Venkatachalapathy; Prakash C. Jain; Rajagopal Venkatraman - Web page: https://patentgrep.com/patent/US12113698B2 ## CPC - H04L 45/745: Address table lookup; Address filtering - H04L 45/02: Topology update or discovery - H04L 45/64: using an overlay routing layer - H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M) ## Abstract Techniques and apparatus for allowing a network fabric to accept network devices associated with other fabric networks are described. An example technique involves establishing a communication session between a first network node and a first control plane of the network fabric, wherein the first network node supports a second control plane different from the first control plane; First routing information from the first network node is imported into a first routing table of the first control plane. Second routing information from a second network node is imported into a second routing table of the first network node. ## Claims ### Claim 1 A computer-implemented method comprising: establishing, by a controller of a first network fabric that supports a first control plane, a communication session between (i) a first network node within a second network fabric different from the first network fabric and (ii) the controller, wherein the first network node supports a second control plane different from the first control plane, and the communication session is established using the second control plane; importing, by the controller via the communication session, first routing information from the first network node into a first routing table of the first control plane, wherein the first routing information comprises a first endpoint identifier of the first network node, the first endpoint identifier being associated with a first overlay identifier for the first network node; and exporting, by the controller via the communication session, second routing information from at least one second network node within the first network fabric into a second routing table of the first network node. ### Claim 2 (depends on 1) The computer-implemented method of claim 1, wherein: the first overlay identifier for the first network node is an original overlay identifier assigned to the first network node via the second control plane; and the original overlay identifier is maintained as the first routing information is imported into the first routing table. ### Claim 3 (depends on 2) The computer-implemented method of claim 2, further comprising: receiving, by the controller, a request for a route associated with the first network node; in response to the request, determining, by the controller, information associated with the route, based on the first routing information within the first routing table; and sending, by the controller, a response comprising an indication of the information associated with the route. ### Claim 4 (depends on 3) The computer-implemented method of claim 3, wherein the indication of the information associated with the route comprises the original overlay identifier for the first network node. ### Claim 5 (depends on 1) The computer-implemented method of claim 1, further comprising providing, by the controller, reflection of the first endpoint identifier to the at least one second network node. ### Claim 6 (depends on 1) The computer-implemented method of claim 1, further comprising providing, by the controller, an indication within the first routing table of the first control plane associated with the first routing information. ### Claim 7 (depends on 1) The computer-implemented method of claim 1, wherein the second routing information comprises at least one second endpoint identifier of the at least one second network node, the at least one second endpoint identifier being associated with a second overlay identifier for the at least one second network node. ### Claim 8 (depends on 7) The computer-implemented method of claim 7, wherein: the second overlay identifier for the at least one second network node is an original overlay identifier associated to the at least one second network node via the first control plane; and the original overlay identifier is maintained as the second routing information is exported into the second routing table. ### Claim 9 (depends on 7) The computer-implemented method of claim 7, further comprising providing, by the controller, reflection of the at least one second endpoint identifier to the first network node. ### Claim 10 A network device comprising: one or more memories collectively storing computer-executable instructions; and one or more processors coupled to the one or more memories, the one or more processors being collectively configured to execute the computer-executable instructions to cause the network device to perform an operation comprising: establishing a communication session between the network device and a first network node, wherein the network device is a controller of a first network fabric that supports a first control plane, the first network node is within a second network fabric different from the first network fabric and supports a second control plane different from the first control plane, and the communication session is established using the second control plane; importing, via the communication session, first routing information from the first network node into a first routing table of the first control plane, wherein the first routing information comprises a first endpoint identifier of the first network node, the first endpoint identifier being associated with a first overlay identifier for the first network node; and exporting, via the communication session, second routing information from at least one second network node within the first network fabric into a second routing table of the first network node. ### Claim 11 (depends on 10) The network device of claim 10, wherein: the first overlay identifier for the first network node is an original overlay identifier assigned to the first network node via the second control plane; and the original overlay identifier is maintained as the first routing information is imported into the first routing table. ### Claim 12 (depends on 11) The network device of claim 11, the operation further comprising: receiving a request for a route associated with the first network node; in response to the request, determining information associated with the route, based on the first routing information within the first routing table; and sending a response comprising an indication of the information associated with the route. ### Claim 13 (depends on 12) The network device of claim 12, wherein the indication of the information associated with the route comprises the original overlay identifier for the first network node. ### Claim 14 (depends on 10) The network device of claim 10, the operation further comprising providing reflection of the first endpoint identifier to the at least one second network node. ### Claim 15 (depends on 10) The network device of claim 10, the operation further comprising providing an indication within the first routing table of the first control plane associated with the first routing information. ### Claim 16 (depends on 10) The network device of claim 10, wherein the second routing information comprises at least one second endpoint identifier of the at least one second network node, the at least one second endpoint identifier being associated with a second overlay identifier for the at least one second network node. ### Claim 17 (depends on 16) The network device of claim 16, wherein: the second overlay identifier for the at least one second network node is an original overlay identifier associated to the at least one second network node via the first control plane; and the original overlay identifier is maintained as the second routing information is exported into the second routing table. ### Claim 18 (depends on 16) The network device of claim 16, the operation further comprising providing reflection of the at least one second endpoint identifier to the first network node. ### Claim 19 A non-transitory computer-readable medium comprising computer program code that, when collectively executed by one or more processors, performs an operation comprising: establishing, by a controller of a first network fabric that support a first control plane, a communication session between (i) a first network node within a second network fabric different from the first network fabric and (ii) the controller, wherein the first network node supports a second control plane different from the first control plane, and the communication session is established using the second control plane; importing, by the controller via the communication session, first routing information from the first network node into a first routing table of the first control plane, wherein the first routing information comprises a first endpoint identifier of the first network node, the first endpoint identifier being associated with a first overlay identifier for the first network node; and exporting, by the controller via the communication session, second routing information from at least one second network node within the first network fabric into a second routing table of the first network node. ### Claim 20 (depends on 19) The non-transitory computer-readable medium of claim 19, wherein: the first overlay identifier for the first network node is an original overlay identifier assigned to the first network node via the second control plane; and the original overlay identifier is maintained as the first routing information is imported into the first routing table.