Inter-Area Forwarders for Multilevel Data Center Fabric Scalability

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The naive approach to multilevel Vinci data center networking faces scalability issues due to growing leaf routing and MAC tables, and impacts stability with intra-area virtual machine mobility, failing to leverage the hierarchical structure for information hiding and optimal connectivity.

Innovation Solution

The introduction of inter-area forwarders (IAFs) in selected switches, which serve as ingress and egress proxies, performing lookups and rewrites on TRILL headers and MAC addresses, and employing default or subnet-based routing schemes to manage inter-area traffic, reducing the burden on leaf switches and enhancing scalability.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Device complexity

If the naive approach to multilevel Vinci data center networking is used, then the hierarchical structure is simple to implement, but scalability is poor due to growing leaf routing and MAC tables

Engineering Contradiction:
Improvehierarchical structure simplicityVSAvoidrouting table size
Core Design Contradiction:
Device complexityVSQuantity of substance

Solution Approach 1:

The patent introduces inter-area forwarders (IAFs) as intermediary devices between different network areas. These IAFs act as proxies that handle inter-area routing decisions, preventing leaf switches from maintaining large routing tables for distant areas. The IAFs perform lookups and rewrites on TRILL headers, managing routing information centrally while keeping leaf tables small.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent segments the network into multiple areas with dedicated inter-area forwarders for each area. This segmentation allows routing information to be organized and managed at the area level rather than globally, reducing the amount of routing information that needs to be stored at each leaf switch while maintaining scalability across the entire network.

Inventive Principle:
Principle #1Segmentation

2Device complexity

If the naive approach is used, then the network structure is simple, but stability is impacted with intra-area virtual machine mobility

Engineering Contradiction:
Improvenetwork structure simplicityVSAvoidstability under VM mobility
Core Design Contradiction:
Device complexityVSReliability

Solution Approach 1:

The IAFs serve as stable intermediaries that handle mobility management between areas. When virtual machines move within an area, the IAFs maintain consistent routing information and perform necessary header rewrites, ensuring stable connectivity even as VM locations change. This intermediary layer isolates mobility impacts from the rest of the network.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Quantity of substance

If inter-area forwarders are introduced, then scalability is improved by reducing leaf routing table burden, but device complexity increases

Engineering Contradiction:
Improverouting table sizeVSAvoidnetwork structure complexity
Core Design Contradiction:
Quantity of substanceVSDevice complexity

Solution Approach 1:

The inter-area forwarders are designed to perform multiple functions: they handle inter-area routing decisions, perform TRILL header lookups and rewrites, manage MAC address translations, and coordinate with BGP route reflectors. By consolidating these functions into specialized IAFs, the patent reduces the burden on leaf switches while distributing the overall complexity across a manageable set of intermediate devices.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Data Source

PatentUS8862772B2System and method for implementing a multilevel data center fabric in a network environment
Publication Date: 2014.10.14 CISCO TECHNOLOGY INC
  • US8862772B2 patent drawing
  • US8862772B2 patent drawing
  • US8862772B2 patent drawing

AI summary

A method is provided in one example embodiment and includes determining whether a first network element with which a second network element is attempting to establish an adjacency is a client type element. If the first network element is determined to be a client type element, the method further includes determining whether the first and second network elements are in the same network area. If the first network element is a client type element and the first and second network elements are determined to be in the same network area, the adjacency is established. Subsequent to the establishing, a determination is made whether the first network element includes an inter-area forwarder (IAF).