IRF Stack Link Traffic Forwarding via Virtual Device Segmentation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In an Intelligent Resilient Framework (IRF) system, traffic flow between virtual devices (VDs) is hindered due to the lack of shared forwarding entries across member devices, as each forwarding chip belongs exclusively to a managing VD, preventing data plane transmission across member devices.

Innovation Solution

Each member device is allocated to at least two VDs, with multiple stack links configured among interface boards, allowing interface boards to forward service messages across member devices by using forwarding entries specific to their corresponding VD, and managing VD configures and manages these entries for seamless transmission.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If each forwarding chip belongs exclusively to a managing VD, then resource isolation and security are improved, but data plane transmission across member devices is blocked

Engineering Contradiction:
Improveresource isolationVSAvoiddata plane transmission
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent segments the forwarding functionality by creating separate forwarding instances for each virtual device on the interface board. Each VD gets its own forwarding entry set, allowing independent forwarding decisions while maintaining physical resource sharing. This resolves the contradiction by enabling both isolation (each VD has dedicated forwarding logic) and transmission (forwarding entries enable data plane flow across member devices).

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The interface board is designed to serve multiple VDs simultaneously by hosting forwarding instances for each VD. The same physical interface board can forward traffic for multiple different virtual devices, making it a universal resource that satisfies both the isolation requirement (separate forwarding logic per VD) and the transmission requirement (shared physical infrastructure enabling cross-member-device communication).

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

2Device complexity

If stack links are shared by all VDs, then system complexity is reduced, but traffic flow forwarding between different VDs cannot be achieved

Engineering Contradiction:
Improvestack link configurationVSAvoidtraffic flow forwarding
Core Design Contradiction:
Device complexityVSProductivity

Solution Approach 1:

The patent applies local quality by associating specific forwarding entries with specific VDs on the interface board. Each VD receives forwarding entries tailored to its traffic requirements, enabling precise control over which traffic flows are permitted. This local differentiation allows the system to maintain simple shared stack link infrastructure while achieving complex per-VD traffic flow control through localized forwarding entry configuration.

Inventive Principle:
Principle #3Local quality

Data Source

PatentEP2641377B1Forwarding traffic flow in intelligent resilient framework system
Publication Date: 2014.10.08 NEW H3C TECH CO LTD
  • EP2641377B1 patent drawingFigure 1~2
  • EP2641377B1 patent drawingFigure 3~4

AI summary

A method and member device for forwarding service messages in an Intelligent Resilient Framework (IRF) system and an IRF system. In the method, each member device in the IRF system is allocated to at least two virtual devices, and at least one stack link for each virtual device is configured in order to connect interface boards among different member devices. When it is determined according to a forwarding entry of an interface board in a first member device receiving a service message that the service message is to be transmitted to a second member device, the service message is forwarded via the at least one stack link configured for the virtual device of that interface board.