Packet Switch Database Versioning for Failover IPC Reduction
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In packet switch systems, failover operations can lead to significant resource overuse and potential freezing of the switch due to excessive IPC communication, especially when applications do not react to backpressure messages, causing unnecessary retransmission of database messages.
Innovation Solution
Implementing a database organization scheme with baseline and incremental pieces identified by version identifiers, where the secondary RPM queries line cards for needed updates and only sends necessary pieces during failover, reducing IPC communication by aggregating and updating only required database components.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If the secondary RPM sends all database pieces during failover, then the line card database is fully updated, but IPC communication resources are excessively consumed causing switch freezing
Solution Approach 1:
The patent extracts only the necessary database pieces (incremental updates) that are needed to synchronize the line card database with the RPM database, rather than transferring all database pieces. This is achieved by comparing version identifiers and sending only the missing or updated portions, thereby reducing IPC communication overhead while maintaining database synchronization reliability.
Solution Approach 2:
The patent applies partial action by sending only the required subset of database updates rather than the complete database. The secondary RPM determines which database pieces are needed based on version identifiers and sends only those specific pieces, avoiding unnecessary transmission of already-synchronized data and reducing resource consumption during failover.
2Productivity
If applications do not react to backpressure messages, then message processing continues, but unnecessary retransmission of database messages occurs increasing traffic
Solution Approach 1:
The patent implements feedback mechanisms where the secondary RPM monitors the processing status of database messages and detects when line cards are unable to process incoming messages. Based on this feedback, the system adjusts its transmission behavior by waiting for backpressure messages and avoiding unnecessary retransmissions, thereby reducing wasted communication resources while maintaining processing throughput.
3Loss of energy
If version identifiers are used to identify database pieces, then only necessary updates are transmitted, but database organization complexity increases
Solution Approach 1:
The patent segments the database into distinct pieces, each identified by a unique version identifier. This segmentation allows the system to track and transmit only the specific pieces that need updating, rather than treating the database as a monolithic structure. The version identifiers enable efficient comparison and determination of which segments require transmission, reducing data transmission overhead despite the added organizational structure.
Data Source
AI summary
In a packet switch with databases (250, 404) used for packet forwarding, the database pieces are identified by version identifiers (410V) which are used by the packet switch's modules (LCx, RPM0, RPM1) in exchanging information on the databases and requesting updates to the databases. For example, if a primary management module fails and the management is transferred to a secondary management module, the secondary management module requests forwarding modules (e.g. line cards) to identify the database pieces stored on the forwarding modules, and to update the databases as needed. Use of version identifiers reduces the amount of data that has to be transferred in connection with such requests.