DR Protocol Packet Handling for Version-Compatible Link Aggregation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Inconsistent software versions between network devices in a distributed resilient network interconnect (DRNI) system can lead to abnormal link aggregation, as the receiving device may not be able to parse protocol packets due to version incompatibility.
Innovation Solution
A method for processing protocol packets in a DR system where the first member device sends an interface identifier and the protocol packet directly to the second member device, allowing the second device to perform protocol processing based on its own software version, eliminating the need for a private message and ensuring compatibility during version upgrades.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If network device A uses a private message to synchronize ARP data to network device B, then the ARP data can be synchronized between devices, but if the software versions are inconsistent, network device B cannot parse the private message, resulting in abnormal link aggregation
Solution Approach 1:
The patent extracts the ARP data from the private message format and transmits it directly as protocol packets. By removing the private message wrapper that causes version compatibility issues, the solution allows devices with different software versions to exchange ARP data successfully while maintaining link aggregation stability.
Solution Approach 2:
The patent introduces an interface identifier as an intermediary element that enables devices with different software versions to communicate effectively. The interface identifier allows the receiving device to correctly process and parse the protocol packets without requiring version-matching private message formats.
2Adaptability or versatility
If network device A is upgraded in version but network device B is not upgraded, then network device A can support new features, but network device B cannot parse the private message from network device A, resulting in abnormal link aggregation
Solution Approach 1:
The patent makes the protocol packet format universal by transmitting ARP data directly without device-specific private message wrappers. This universal format ensures that both upgraded and non-upgraded devices can parse and process the data correctly, maintaining link aggregation normality across different software versions.
3Loss of information
If a private message is used to carry ARP data, then the data can be transmitted between devices, but the receiving device may not be able to parse the data due to version inconsistency
Solution Approach 1:
The patent extracts the essential ARP data from the private message structure and transmits it in a standardized protocol packet format. This extraction eliminates the version-specific parsing requirements while ensuring complete ARP data transmission between devices with different software versions.
Data Source
Figure 1~2
Figure 3~4
AI summary
The present disclosure provides a method and apparatus for processing a protocol packet. The method includes: when a first member device of a distributed relay (DR) system receives a first protocol packet through a first DR interface, the first member device performs protocol processing based on the first DR interface and the first protocol packet; and the first member device sends, to a second member device of the DR system, a first type packet comprising an interface identifier of the first DR interface and the first protocol packet, so that the second member device determines that the first protocol packet is received through a second DR interface corresponding to the interface identifier, and performs protocol processing based on the second DR interface and the first protocol packet.