Hot Standby Neighbor Discovery Protocol for IPv6 Failover
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The existing Neighbor Discovery (ND) protocol for IPv6 faces challenges in timely switchover to a hot standby network device upon primary device failure, leading to prolonged downtime and potential service disruptions, especially in critical services like VoIP, due to the need to rebuild Neighbor Cache entries, which can take up to 10 minutes.
Innovation Solution
The Hot Standby Neighbor Discovery Protocol (HSNDP) implements synchronization messages to maintain and update IPv6 states in a standby device, allowing it to immediately process traffic without restarting state machines, thereby reducing failover time to less than three seconds by introducing a DEFERRED state in the Neighbor Cache and enabling seamless switchover between active and standby nodes.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Loss of time
If the standby device waits for the primary device to fail before synchronizing Neighbor Cache entries, then the synchronization process is simpler, but the failover time increases to up to 10 minutes causing service disruptions
Solution Approach 1:
The standby device performs preliminary synchronization of Neighbor Cache entries with the primary device before actual failover occurs. The standby device continuously receives and processes Neighbor Solicitation and Advertisement messages from the primary device, maintaining updated Neighbor Cache entries in advance. This preliminary action ensures that when failover is needed, the standby device already has the necessary network topology and routing information, reducing failover time to less than three seconds.
2Reliability
If the standby device continuously synchronizes Neighbor Cache entries with the primary device, then failover time is reduced to less than three seconds, but the protocol complexity and message processing overhead increase
Solution Approach 1:
The standby device maintains continuous synchronization with the primary device by continuously processing Neighbor Solicitation and Advertisement messages. This continuous action ensures that Neighbor Cache entries are always up-to-date without interruption. The standby device monitors network changes in real-time and updates its routing information continuously, ensuring service continuity and enabling rapid failover when needed.
3Loss of time
If the standby device restarts IPv6 state machines upon switchover, then the state machine initialization is simpler, but the service disruption time increases significantly
Solution Approach 1:
The standby device performs preliminary synchronization of IPv6 state machine states with the primary device before failover. By maintaining synchronized Neighbor Cache entries and routing information in advance, the standby device eliminates the need to restart state machines during failover. The state machines continue operating with preserved context, reducing service disruption time to less than three seconds.
Data Source
AI summary
Techniques are provided herein for receiving synchronization messages at a second network device that is in a hot standby configuration from a first network device that is maintaining Internet Protocol version 6 (IPv6) state machines for one or more neighbor devices. The synchronization messages are configured to indicate an IPv6 state for each state machine maintained in the first network device. An IPv6 state for corresponding state machines is updated in the second network device based on the synchronization messages such that the IPv6 states in the second network device allows the second network device to actively process IPv6 traffic for the one or more neighbor devices upon traffic switchover from the first network device to the second network device without restarting the corresponding IPv6 state machine associated with each of the one or more neighbor devices in the second network device. The roles of the first and second device with respect to active and standby state are reversed after a switchover.