US 12,081,430 B2
Marking spoke links for network segregation and service chaining in hub and spoke overlay networks
Hari Shankar, San Jose, CA (US); Eui Sun Ahn, Burnaby (CA); Jeffery Rodd Daviss, Port Coquitlam (CA); Rashmi Garg, Pleasanton, CA (US); Jon Langemak, Rockford, MN (US); and William Mark Townsley, San Francisco, CA (US)
Assigned to Cisco Technology, Inc., San Jose, CA (US)
Filed by Cisco Technology, Inc., San Jose, CA (US)
Filed on Jul. 8, 2022, as Appl. No. 17/860,957.
Prior Publication US 2024/0015091 A1, Jan. 11, 2024
Int. Cl. H04L 45/12 (2022.01); H04L 9/40 (2022.01); H04L 12/46 (2006.01); H04L 45/02 (2022.01)
CPC H04L 45/123 (2013.01) [H04L 12/4633 (2013.01); H04L 45/02 (2013.01); H04L 63/0236 (2013.01)] 20 Claims
OG exemplary drawing
 
1. A method comprising:
receiving a network advertisement at a first hub node of a hub and spoke network, the network advertisement indicating a first tunneled connection connecting a first spoke network to the first hub node and a first border gateway protocol (BGP) large community string associated with the first tunneled connection;
decoding, from a first portion of the first BGP large community string, a first indication of a first virtual network instance (VNI) type of the first spoke network;
decoding, from a second portion of the first BGP large community string, a second indication of a first routing requirement associated with the first spoke network, the first routing requirement indicating a routing action to perform on network traffic associated with the first spoke network;
storing, in a routing table associated with the first hub node, a first routing entry including a first address of the first tunneled connection, the first indication of the first VNI type, and the second indication of the first routing requirement;
receiving, at the first hub node, a first data packet to be transmitted from the first spoke to a destination node;
determining a route to transmit the first data packet from the first spoke to the destination node based at least in part on the routing table, the route including the first tunneled connection and a second tunneled connection connecting a second spoke network of the hub and spoke network to a second hub node of the hub and spoke network;
identifying the first routing requirement and a second routing requirement associated with the second spoke network based at least in part on the first routing entry and a second routing entry including a second address of the second tunneled connection and a second BGP large community string; and
based at least in part on the first routing requirement and the second routing requirement, one of:
sending the first data packet to the second hub node;
sending the first data packet to a first service node of the hub and spoke network configured to apply one or more services to the first data packet associated with at least one of the first routing requirement or the second routing requirement; or
dropping the first data packet.