Multicast Protocol State Synchronization for Network Failover
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In networking devices, unplanned failover or restart of a multicast protocol leads to traffic disruption and unnecessary processing power waste due to the need for one protocol to relearn paths and reprogram ASICs, causing flow misses and traffic losses.
Innovation Solution
A method to regenerate or update the knowledge of networking device states by accessing a centralized database to read multicast flow events, generating a multicast protocol packet based on these events, and sending it to the multicast protocol, allowing both active and standby protocols to maintain synchronized state information without erasing existing paths.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If a multicast protocol is restarted or failover occurs, then the protocol needs to relearn paths and reprogram ASICs to restore functionality, but this causes traffic disruption, flow misses, and unnecessary processing power waste
Solution Approach 1:
The standby multicast protocol maintains synchronized state information with the active protocol through continuous state event processing. When failover occurs, the standby protocol already has pre-loaded path information and ASIC programming data, eliminating the need to relearn paths and reducing traffic disruption time.
Solution Approach 2:
The standby protocol creates and maintains a copy of the active protocol's state information by processing state events. This copied state includes path routing data and ASIC programming parameters, allowing the standby to immediately resume functionality without relearning upon failover.
2Reliability
If the standby protocol processes all state events to maintain synchronized state information, then failover recovery is faster, but processing power is consumed during standby operation
Solution Approach 1:
The standby protocol processes state events partially - it maintains synchronization for critical path information and ASIC programming data while avoiding full processing of all state events. This selective processing reduces energy consumption during standby while ensuring sufficient state information is available for rapid failover recovery.
Data Source
AI summary
Examples include receiving a recovery signal and access data stored in a centralized database of a networking device in response to the recovery signal. The data may include information associated to past multicast flow events. Additionally, examples include determining a rebuilt multicast flow event based on the data, generating a multicast protocol packet based on the multicast flow event, and sending the multicast protocol packet to a multicast protocol in the networking device.