Router Fast Flooding for Network Failure Recovery
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current network failure recovery methods, such as IP Fast Re-Route and Loop Free Alternative, are inefficient due to reliance on slow flooding mechanisms that require domain-wide synchronization, leading to prolonged network downtime and potential traffic outages or routing loops.
Innovation Solution
A fast flooding based method that initiates a fast failure notification message with a specific MAC address, allowing for rapid dissemination of network failure information independently of routing table updates, using a common message format different from traditional IGP protocols, and bypassing adjacency checks to minimize convergence time.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If normal flooding mechanism is used for failure notification, then routing table update is synchronized across the network, but convergence time is prolonged due to slow propagation
Solution Approach 1:
The patent segments the failure notification process into two independent parts: (1) fast flooding of failure notification messages at Layer 2 to achieve rapid propagation, and (2) subsequent routing table updates at Layer 3. This segmentation allows the notification to spread quickly across the network while routing updates follow independently, resolving the contradiction between synchronization reliability and convergence speed.
Solution Approach 2:
The patent introduces a Layer 2 switching infrastructure as an intermediary between the failure detection point and the routing protocols. The Layer 2 switch rapidly floods failure notification frames throughout the network before Layer 3 routing updates are complete, acting as a mediator that decouples the timing between notification propagation and routing convergence.
2Loss of time
If fast flooding is implemented independently of routing table updates, then convergence speed is improved, but network stability may be compromised due to potential routing loops
Solution Approach 1:
The patent performs preliminary action by flooding failure notification messages throughout the network before routing table updates are complete. This ensures all routers are aware of the failure condition in advance, allowing them to proactively prepare for rerouting while maintaining stability through coordinated update timing.
Solution Approach 2:
The patent implements feedback mechanisms where routers monitor the flooding process and routing update progress, adjusting their behavior to prevent routing loops. The system provides feedback between the fast flooding process and routing updates, ensuring stability while maintaining fast convergence.
3Adaptability or versatility
If traditional IGP flooding protocol message format is used, then protocol compatibility is maintained, but message processing overhead increases due to adjacency checks
Solution Approach 1:
The patent extracts the essential failure notification function from the traditional IGP flooding protocol message format. By using a simplified Layer 2 frame structure instead of full IGP PDUs, it removes the complexity of adjacency checks and routing protocol processing overhead while maintaining the core functionality of failure notification and router compatibility.
Data Source
AI summary
A method in a router for initiating fast flooding based fast convergence to recover from a network failure is disclosed. The method also starts with detecting a network failure. Responsive to the detected network failure, the router floods a layer 2 fast failure notification message out a set of one or more interfaces of the router. The fast failure notification message includes information that identifies the network failure and indicates to a router that receives the fast failure notification message to flood the fast failure notification message out its interfaces that are not blocked by a spanning tree protocol (STP) independently of updating its routing table to reflect the network failure. The method continues with the router updating a routing table to reflect the network failure.