Subnet Route Management via CPU Intermediary
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing methods for managing invalid subnet routes are inefficient and complex, particularly when multiple subnet routes are directed to the same next-hop host route, leading to excessive hardware modifications and low switching efficiency between validity and invalidity.
Innovation Solution
A method that detects invalid next-hop host routes, generates deletion or addition instructions, intercepts and converts these instructions into updating instructions, and updates the next-hop egress to a CPU, allowing for simplified management and rapid switching without modifying the subnet routes directly.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If multiple subnet routes are directed to the same next-hop host route and the host route becomes invalid, then all subnet routes must be individually modified to redirect to CPU, but this causes excessive hardware modification operations and reduces switching efficiency
Solution Approach 1:
The patent introduces an intermediary mechanism by redirecting traffic from invalid subnet routes through the CPU instead of directly modifying each subnet route entry. The CPU acts as a mediator that handles ARP relearning and restores routes when valid, avoiding the need for individual hardware modifications of multiple subnet routes and improving switching efficiency.
2Ease of operation
If multiple subnet routes are individually modified when next-hop host route becomes invalid, then route management can handle each route separately, but this increases device complexity and management overhead
Solution Approach 1:
The patent merges the handling of multiple invalid subnet routes into a single operation by redirecting all traffic to the CPU through the invalid next-hop host route. This consolidation approach combines what would otherwise be multiple individual hardware modification operations into one unified process, reducing device complexity and management overhead.
3Reliability
If subnet routes are restored when next-hop host route becomes valid, then routing functionality is recovered, but multiple restoration operations are required which reduces switching efficiency
Solution Approach 1:
The patent applies preliminary action by maintaining the subnet route entries in the routing table even when the next-hop host route is invalid. The routes remain configured and ready, with traffic temporarily redirected through the CPU. When the host route is restored, traffic flow is immediately recovered without requiring time-consuming restoration operations, thus reducing loss of time.
Data Source
AI summary
Provided are a method for processing a subnet route and message forwarding equipment. The method includes: it is detected that a next-hop host route to which the subnet route is directed becomes invalid; when the next-hop host route becomes invalid, a deletion instruction for deleting the next-hop host route is generated and issued; the deletion instruction is intercepted, and converted into a first updating instruction for modifying the next-hop host route; and a next-hop egress of the next-hop host route is updated into a Central Processing Unit (CPU) of the message forwarding equipment according to the first updating instruction. According to the disclosure, management over the subnet route can be simplified, and switching efficiency of the subnet route can be improved.