Overlay Fabric Heterogeneous Capabilities

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In datacenter overlay fabrics, the addition of new functionalities such as MACSEC link encryption and Multi Site/Remote Leaf connectivity requires upgrading all spine switches, which is costly and inefficient, as not all underlay traffic needs these features, and previous generation switches may be disconnected from the network if they do not support these modern functions.

Innovation Solution

Implementing Type Link Values (TLVs) in protocols like ISIS to distribute node-level functions and capabilities as attributes for topological selection, allowing traffic to flow only through links and nodes that support specific features, such as MACSEC encryption, while older switches can still be used for non-encrypted traffic, and using topology IDs and Tunnel Endpoint addresses to manage feature support across the network.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If all spine switches are upgraded to support new functionalities such as MACSEC link encryption and Multi Site/Remote Leaf connectivity, then network security and functionality are improved, but deployment cost and complexity increase significantly

Engineering Contradiction:
Improvenetwork securityVSAvoiddeployment cost
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent applies local quality by enabling different spine switches to have different capability sets. Specifically, some spine switches can support MACSEC encryption while others can support Multi Site/Remote Leaf connectivity, and the system dynamically routes traffic based on the required capability. This allows the network to provide enhanced security and functionality only where needed, rather than requiring all switches to support all features, thereby reducing overall deployment cost and complexity while maintaining necessary security and functionality.

Inventive Principle:
Principle #3Local quality

Solution Approach 2:

The patent segments the overlay fabric into multiple capability-based topologies. By dividing the network into distinct capability groups (e.g., encryption-capable switches vs. multi-site-capable switches), the system can selectively apply different features to different segments. This segmentation allows older switches to remain in the network for non-encrypted traffic while newer switches handle encrypted or multi-site traffic, avoiding the need to replace all switches and reducing deployment costs.

Inventive Principle:
Principle #1Segmentation

2Adaptability or versatility

If all spine switches are upgraded to support modern functionalities, then feature compatibility is improved, but resource efficiency and cost-effectiveness deteriorate

Engineering Contradiction:
Improvefeature compatibilityVSAvoidresource efficiency
Core Design Contradiction:
Adaptability or versatilityVSProductivity

Solution Approach 1:

The patent implements local quality by allowing different spine switches to provide different features based on their capabilities. The system dynamically selects appropriate switches for specific traffic types - for example, using MACSEC-capable switches for encrypted traffic and Multi Site-capable switches for remote leaf connectivity. This ensures feature compatibility is achieved only where necessary, maximizing resource efficiency by avoiding unnecessary upgrades of switches that don't need advanced features.

Inventive Principle:
Principle #3Local quality

Solution Approach 2:

The patent applies partial action by implementing feature support selectively rather than universally. Instead of upgrading all spine switches to support all modern functionalities, the system deploys specific features on specific switches based on traffic requirements. This partial implementation achieves sufficient feature compatibility for current needs while avoiding the waste of resources that would result from universal upgrading.

Inventive Principle:
Principle #16Partial or excessive action

3Adaptability or versatility

If previous generation switches are disconnected from the network due to lack of feature support, then network functionality is improved, but network integrity and legacy traffic handling deteriorate

Engineering Contradiction:
Improvefeature supportVSAvoidnetwork integrity
Core Design Contradiction:
Adaptability or versatilityVSStability of the object's composition

Solution Approach 1:

The patent segments the network into capability-based groups, creating distinct topologies for different feature sets. Previous generation switches are placed in segments that handle traffic types they can support (e.g., standard unencrypted traffic), while newer switches handle advanced traffic types (e.g., encrypted or multi-site traffic). This segmentation allows legacy switches to remain connected and functional within their capability scope, maintaining network integrity while providing modern features where needed.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces capability advertisement and topology selection mechanisms as intermediaries between legacy switches and modern features. These intermediaries allow the network to dynamically route traffic through appropriate switches based on capability requirements, enabling legacy switches to coexist with modern features without direct conflict. The intermediary mechanisms ensure that traffic requiring advanced features is routed through capable switches while legacy traffic flows through older switches, maintaining overall network integrity.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS10574481B2Heterogeneous capabilities in an overlay fabric
Publication Date: 2020.02.25 CISCO TECHNOLOGY INC
  • US10574481B2 patent drawing
  • US10574481B2 patent drawing
  • US10574481B2 patent drawing

AI summary

Heterogeneous capabilities in an overlay fabric may be provided. First, it may be determined that a first link and a second link support a feature. Then the first link and the second link may be traversed with traffic between a host in a first Endpoint Group (EPG) connected to a first leaf switch and a second host in a second EPG connected to a second leaf switch when a topology preference for the feature is indicated for the traffic.