Split-Horizon Flooding in L2 Network Traffic Forwarding

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In layer two (L2) networks, data loops can significantly consume bandwidth and resources, leading to multiple copies of packets being received at the destination, necessitating the elimination of such loops to ensure efficient network traffic delivery.

Innovation Solution

Implementing the split-horizon rule through the logical construct of a single 'flooding next hop' identifier to represent all corresponding next hops in the L2 network, allowing high-level control plane software to maintain network topology without ensuring compliance with the split-horizon rule, and utilizing lower-level components to derive specific next hops for forwarding traffic.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If network traffic is flooded to all output ports to ensure delivery to unknown destinations, then network traffic delivery reliability is improved, but data loops are created that consume bandwidth and resources

Engineering Contradiction:
Improvenetwork traffic delivery reliabilityVSAvoidbandwidth and resource consumption
Core Design Contradiction:
ReliabilityVSLoss of energy

Solution Approach 1:

The patent segments the flooding process by introducing the split-horizon rule that divides output ports into two segments: those that should receive flooded traffic and those that should not. Specifically, when a device receives traffic on an ingress port, it segments the flooding targets to exclude the ingress port itself, thereby preventing data loops while maintaining delivery reliability to legitimate destinations.

Inventive Principle:
Principle #1Segmentation

2Reliability

If split-horizon rule is enforced at high-level control plane software, then data loop prevention is improved, but device complexity and software burden increase

Engineering Contradiction:
Improvedata loop preventionVSAvoidcontrol plane software complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent extracts the split-horizon rule enforcement from the high-level control plane software and relocates it to lower-level forwarding components. This extraction allows the control plane to maintain simplified routing tables without embedded split-horizon logic, while the forwarding components independently apply the rule by automatically excluding ingress ports from flooding targets, thereby reducing control plane complexity.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent introduces an intermediary mechanism where the control plane software provides routing information to forwarding components, and the forwarding components act as intermediaries that enforce the split-horizon rule. This intermediary layer allows the control plane to remain simple while still achieving reliable data loop prevention through the forwarding components' automated enforcement.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Productivity

If forwarding information specifies all next hops for flooding, then flood list expansion capability is improved, but memory usage and information overhead increase

Engineering Contradiction:
Improveflood list expansion capabilityVSAvoidmemory usage
Core Design Contradiction:
ProductivityVSQuantity of substance

Solution Approach 1:

The patent applies local quality by storing compressed routing information at the control plane level that specifies next hops without full flood lists. The actual flood list expansion occurs locally at each forwarding component based on its specific ingress port context. This allows compact storage of routing information while maintaining complete flooding capability where needed, reducing overall memory usage.

Inventive Principle:
Principle #3Local quality

Data Source

PatentUS7649904B1Seamless split-horizon flooding of layer two (L2) network traffic on non-native and mixed architectures
Publication Date: 2010.01.19 JUNIPER NETWORKS INC
  • US7649904B1 patent drawing
  • US7649904B1 patent drawing
  • US7649904B1 patent drawing

AI summary

A forwarding component of a routing node floods copies of a packet to a plurality of next hops associated with the same layer two (L2) network as an interface on which the packet was received. The plurality of next hops excludes a next hop that corresponds to the interface that received the packet. The forwarding component requires that forwarding information installed by a control unit specify the plurality of next hops to which to flood the copies of the packet, and the forwarding component is not capable of deriving the plurality of next hops to which to flood the copies of the packet from a single flooding next hop identifier after the packet is received. Prior to receiving the packet, a flooding next hop control module derives the plurality of next hops based on the flooding next hop and installs the derived next hops into the forwarding information.