Cisco Technology, Inc.

Jon Langemak

Kyle Andrew Donald Mestery

Christopher Blair Murray

Alvin Wong

Rahim Lalani

Alvaro Cesar Pereira

Hari Shankar

William Mark Townsley

Jeffery Rodd Daviss

Rashmi Garg

Eui Sun Ahn

Techniques for using global virtual network instance (VNI) labels in a multi-domain network to route network data with a multi-tenant network overlay are described herein. A routing device provisioned in a network domain of the multi-domain network may register with a service discovery system of the network domain for use of network configuration data to establish routes through the multi-domain network with network nodes. Each network domain of the multi-domain network may include an application programming interface (API) server for processing API requests to make changes to configurations of a network domain. A border gateway protocol (BGP) large community may be utilized to encode global VNI labels, network addresses, local next hop nodes, and/or additional network information and sent to routing devices provisioned in separate network domains. A service chain may be signaled by global VNI labels to route network traffic through various services prior to reaching a destination endpoint.

Using global virtual network instance (VNI) labels to signal a service chain

Encoding end-to-end tenant reachability information in border gateway protocol (BGP) communities

Application programming interface (API)-based multi-tenant routing control plane

Techniques for a hub node to, provisioned in a network site of a hub and spoke overlay network, to receive a network advertisement from the spoke, decode network routing requirements from a border gateway protocol (BGP) large community associated with the network advertisement, and store the network routing requirements in association with a route associated with the spoke. The routing requirements may indicate one or more service(s) to be applied to the packet, a trust level associated with the spoke, and/or a trust zone associated with the spoke. The hub node may receive a packet from the spoke to be transmitted to destination spoke. The hub node may then route the packet to the destination spoke, drop the packet, or send the packet to a service node configured to apply the one or more services to the packet based on the routing requirements.

Marking spoke links for network segregation and service chaining in hub and spoke overlay networks

Encoding local next-hop information into border gateway protocol (BGP) routes

Service discovery for control plane and establishing border gateway protocol sessions

Growing community of inventors

Rockford, MN, United States of America

Jon Langemak