Zonal Checksums for Network Routing Consistency

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In computer networks, ensuring consistency between routing and forwarding tables is challenging, particularly when changes in network topology occur, as errors can cause discrepancies between the routing information base (RIB), forwarding information base (FIB), and packet forwarding engines (PFEs), leading to inconsistent forwarding tables.

Innovation Solution

The implementation of zonal checksum calculations using consistency values such as zone identifiers, checksums, and timestamps across the RIB, FIB, and PFEs, with a collector daemon performing consistency checks and initiating actions when inconsistencies are detected, ensures that all tables reflect the same routing information, using a routing protocol daemon and control plane kernel to propagate and verify these values.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If zonal checksum calculations and consistency checks are implemented across RIB, FIB, and PFEs, then reliability of routing information is improved, but device complexity increases

Engineering Contradiction:
Improveconsistency of routing informationVSAvoidcomplexity of consistency checking mechanism
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent divides the routing information into zones and implements zonal checksum calculations. Each zone represents a segment of routing data, allowing localized consistency verification. This segmentation enables the system to check consistency of specific zones rather than entire routing tables, making the complexity manageable while maintaining reliability across distributed RIB, FIB, and PFE components.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent implements a feedback mechanism where checksum values are calculated and compared across RIB, FIB, and PFEs. When inconsistencies are detected, the system generates notifications and triggers corrective actions. This feedback loop continuously monitors and maintains routing consistency, improving reliability through automated detection and correction of discrepancies.

Inventive Principle:
Principle #23Feedback

2Measurement precision

If consistency checks are performed frequently to maintain routing accuracy, then measurement precision of routing state is improved, but loss of time for network operations increases

Engineering Contradiction:
Improveaccuracy of routing state verificationVSAvoidtime consumed by consistency checks
Core Design Contradiction:
Measurement precisionVSLoss of time

Solution Approach 1:

The patent implements periodic consistency checks using timestamps and epoch-based validation. Instead of continuous monitoring, the system performs checks at scheduled intervals or triggered by specific events (e.g., routing changes). This periodic approach maintains measurement precision by verifying routing state accuracy while minimizing time loss by avoiding unnecessary continuous verification.

Inventive Principle:
Principle #19Periodic action

Solution Approach 2:

The patent uses preliminary checksum calculations that are prepared in advance and stored with routing information. When consistency checks are needed, these pre-computed values are quickly retrieved and compared rather than calculating everything from scratch. This preliminary action reduces the time required for verification while maintaining accurate detection of routing inconsistencies.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentEP3890254B1Route consistency checker for network devices
Publication Date: 2024.03.27 JUNIPER NETWORKS INC
  • EP3890254B1 patent drawingFigure 1
  • EP3890254B1 patent drawingFigure 2
  • EP3890254B1 patent drawingFigure 3

AI summary

In general, this disclosure describes a network device that checks consistency between routing objects in a routing information base (RIB), a forwarding information base (FIB), and packet forwarding engine (PFE) forwarding tables. A method includes generating a marker that causes a routing protocol daemon, a control plane kernel, and PFEs of a network device to calculate zonal checksums for a plurality of zones using consistency values for each routing object within a RIB, a FIB, and corresponding forwarding tables respectively. The method includes performing a consistency check on the RIB, the FIB, and the forwarding tables to determine whether the routing objects in each of the RIB, the FIB, and the forwarding tables are consistent with each other. The method includes, when the RIB, the FIB, and the forwarding tables are not consistent, performing an action related to at least one of RIB, the FIB, or the forwarding tables.