IRB L2 Address Synchronization for Multi-Chassis Link Aggregation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional multi-homing configurations in network redundancy rely on Virtual Router Redundancy Protocol (VRRP) for presenting a virtual network address, which requires multiple instances and periodic messaging, leading to inefficiencies and address conservation issues in customer networks with thousands of virtual LANs.

Innovation Solution

Implementing a lightweight protocol like Inter-chassis Configuration Protocol (ICCP) for synchronizing Integrated Routing and Bridging (IRB) L2 addresses among multiple PE routers, enabling active-active multi-homing with a multi-chassis link aggregation group (LAG) to provide redundant L2 connectivity without relying on virtual gateway addresses.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If VRRP is used for multi-homing configurations, then network redundancy is achieved, but network address conservation is compromised and device complexity increases due to multiple instances and periodic messaging

Engineering Contradiction:
Improvenetwork redundancyVSAvoidnetwork addresses
Core Design Contradiction:
ReliabilityVSQuantity of substance

Solution Approach 1:

The patent merges the L2 addressing functions of multiple PE routers by synchronizing IRB L2 addresses across the chassis group. Instead of each router maintaining separate virtual gateway addresses via VRRP, all PE routers share a synchronized view of L2 addresses, allowing any router to forward traffic destined for any member's L2 address. This consolidation eliminates the need for multiple VRRP instances and conserves network addresses.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The synchronized IRB L2 address mechanism provides universal L2 address recognition across all PE routers in the chassis group. Each router can receive and forward traffic destined for any member's L2 address, making the system universally responsive to L2 traffic without requiring separate virtual gateway configurations for each router, thereby reducing address consumption.

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

2Reliability

If VRRP is used for multi-homing configurations, then network redundancy is achieved, but device complexity increases due to multiple instances and periodic messaging

Engineering Contradiction:
Improvenetwork redundancyVSAvoidVRRP instances
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent extracts the periodic messaging and instance management overhead of VRRP from the system. By using lightweight L2 address synchronization mechanisms, the solution removes the need for continuous VRRP advertisement messages and multiple VRRP instance configurations, significantly reducing device complexity while preserving redundancy capabilities.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent replaces complex, long-lived VRRP instances with simpler, lighter-weight L2 address synchronization objects. The synchronized IRB L2 address information is maintained as lightweight data structures that can be quickly updated and propagated, eliminating the burden of managing multiple persistent VRRP instances and their associated periodic messaging.

Inventive Principle:
Principle #27Cheap short-living objects (Disposable)

3Productivity

If active-active multi-homing with multi-chassis LAG is implemented, then network efficiency is improved, but L2 address synchronization complexity increases

Engineering Contradiction:
Improvenetwork efficiencyVSAvoidL2 address synchronization
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The L2 address synchronization mechanism operates autonomously within the chassis group, with PE routers automatically exchanging and updating IRB L2 address information through lightweight protocols. The system self-manages the synchronization process without requiring external control or complex configuration, allowing active-active multi-homing to achieve high network efficiency while keeping synchronization complexity manageable.

Inventive Principle:
Principle #25Self-service

4Reliability

If VRRP periodic messaging is used, then virtual gateway address presentation is achieved, but network time response increases due to periodic updates

Engineering Contradiction:
Improvevirtual gateway presentationVSAvoidaddress synchronization time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent replaces periodic VRRP messaging with event-driven L2 address synchronization. Changes in L2 address assignments trigger immediate synchronization updates across the chassis group, eliminating the delay inherent in periodic VRRP advertisement cycles. This event-driven approach maintains accurate virtual gateway presentation while significantly reducing address synchronization time.

Inventive Principle:
Principle #19Periodic action

Data Source

PatentUS8787149B1MAC address synchronization for multi-homing with multichassis link aggregation
Publication Date: 2014.07.22 JUNIPER NETWORKS INC
  • US8787149B1 patent drawing
  • US8787149B1 patent drawing
  • US8787149B1 patent drawing

AI summary

In general, techniques are described for using a light-weight protocol to synchronize layer two (L2) addresses that identify routable traffic to multiple L3 devices, such as PE routers, that cooperatively employ an active-active redundancy configuration using a multi-chassis LAG to provide an L2 network with redundant connectivity. In one example, a network device establishes a multi-chassis LAG with a peer network device to provide redundant connectivity to a layer three (L3) network. A synchronization module of the network device receives a synchronization message that specifies an L2 address of the peer network device. When the network device receives an L2 packet data unit (PDU) from the L2 network, a routing instance of the network device routes an L3 packet encapsulated therein when the PDU has an L2 destination address that matches the L2 address of the peer network device.