A method and system for rapid network device fault recovery based on neighbor device assistance

Abstract

This invention discloses a method and system for rapid network device fault recovery based on neighbor device assistance, relating to the fields of computer network and communication technology. The method includes: collecting neighbor device identifiers and interface information; synchronizing target device configuration data through private extended fields; outputting neighbor-side configuration; receiving target device configuration data; using the neighbor-side configuration as input; determining topology consistency by combining interface mapping and device identifiers; and transmitting back configuration data; performing fragmentation and reassembly, configuration judgment, and consistency verification on the transmitted configuration data; and loading the configuration data. The method described in this invention achieves better results in terms of the executability of configuration recovery after fault replacement, the reliability of configuration and topology matching, and configuration consistency control in scenarios involving multiple neighbors.

Description

Technical Field

[0001] This invention relates to the field of computer network and communication technology, specifically to a method and system for rapid network device fault recovery based on neighbor device assistance. Background Technology

[0002] In existing technologies, network device fault recovery typically relies on centralized network management platforms, manual backup and recovery, or controller-based centralized distribution mechanisms.

[0003] Centralized network management platform solutions require the deployment of a dedicated management system in the network and continuous maintenance of configuration backups. They also have high requirements for the availability of the management link, the compatibility of the platform and devices, and version consistency. When the management link is abnormal or the platform is unavailable, the fault recovery process may not be completed.

[0004] Manual backup and recovery relies on maintenance personnel exporting configuration files in advance and manually importing them after a failure. This method involves numerous steps, is time-consuming, prone to errors, and heavily dependent on personnel experience, making it difficult to meet the requirements for rapid recovery. Centralized distribution based on the controller typically requires the introduction of an additional control plane or control protocol, and distribution delays or failures may occur when devices are replaced, topology changes occur, or the controller and device connectivity is disrupted.

[0005] While some existing technologies can utilize neighbor discovery mechanisms to obtain port connection information, they are typically only used for topology discovery or link maintenance. They fail to combine the historical configuration of the neighbor side with the interface mapping relationship to complete topology consistency determination and configuration backhaul under the specific triggering condition of "empty configuration after fault replacement". At the same time, for key links such as fragmented transmission, fragmented reassembly, and consistency verification of configuration backhaul by multiple neighbors when the configuration data is large, existing solutions often lack unified and executable process constraints, which can easily lead to problems such as mismatch, misoverwrite, or inconsistent recovery in actual deployment. Summary of the Invention

[0006] In view of the above-mentioned problems, the present invention is proposed.

[0007] Therefore, the technical problem solved by this invention is that existing centralized network management distribution, manual backup import, or controller centralized configuration recovery methods have strong dependence on management links and central platforms, cumbersome configuration recovery steps after fault replacement and low recovery efficiency, and are prone to mismatch and misoverwrite when topology changes or port mapping is inconsistent. Furthermore, it addresses the problem of how to use the neighbor-side configuration saved by adjacent devices and combine interface mapping and device identifier to determine topology consistency when the target device is fault-replaced and the configuration fields are empty, and then return the configuration data and complete the configuration loading under the constraints of fragmentation reassembly and consistency verification.

[0008] To address the aforementioned technical problems, this invention provides the following technical solution: a method for rapid network device fault recovery based on neighbor device assistance, comprising collecting neighbor device identifiers and interface information, synchronizing target device configuration data through private extended fields, and outputting neighbor-side configuration.

[0009] Receive the target device configuration data, take the neighbor-side configuration as input, combine the interface mapping and device identifier to determine topology consistency, and send back the configuration data.

[0010] The returned configuration data is fragmented, reassembled, and its configuration is judged and verified for consistency before the configuration data is loaded.

[0011] The received target device configuration data includes data where the configuration fields in the received replacement target device configuration data are empty after the target device has been replaced due to a fault.

[0012] Taking the neighbor-side configuration as input includes calling the neighbor-side configuration and extracting and replacing the historical device identifier, historical interface mapping and historical configuration data corresponding to the target device.

[0013] As a preferred embodiment of the network device fault rapid recovery method based on neighbor device assistance described in this invention, the step of collecting neighbor device identifiers and interface information includes ensuring that the ports of the network devices are in a link-connected state.

[0014] The target device periodically sends link discovery messages to neighboring devices and receives response messages from neighboring devices.

[0015] The neighboring device identifier and the interface information corresponding to the target port are obtained by parsing the link discovery message.

[0016] Write the neighbor device identifiers and interface information into the local neighbor relationship table according to the association relationship between the target end interface name, the peer end interface name, and the neighbor device identifier.

[0017] Record the reception time and message sequence number as historical records.

[0018] As a preferred embodiment of the network device fault rapid recovery method based on neighbor device assistance described in this invention, the output neighbor-side configuration includes extracting target device configuration data from the private extended field of the link discovery message.

[0019] Using the target interface name, peer interface name, and neighbor device identifier recorded in the local neighbor relationship table as indexes, the target device configuration data, the corresponding target interface name, and the peer interface name are bound together and then written into the neighbor-side configuration table.

[0020] The output includes the configuration data written to the target device, the neighbor-side configuration after the corresponding target interface name and peer interface name are bound together.

[0021] As a preferred embodiment of the network device fault rapid recovery method based on neighbor device assistance described in this invention, the step of receiving target device configuration data includes the replacement target device periodically sending link discovery messages to neighboring devices.

[0022] Replace the empty data in the private extension field of the link discovery message with the target device configuration data.

[0023] Neighboring devices receive link discovery messages, parse the messages to obtain the neighboring device identifier and the interface information corresponding to the target port.

[0024] Record the reception time and message sequence number as historical records.

[0025] The neighboring device locates the link discovery message based on the target interface name, peer interface name, and neighboring device identifier already written in the local neighbor relationship table.

[0026] The condition for triggering a data return is defined as the condition where the configuration data of the target device being replaced is in an empty state.

[0027] As a preferred embodiment of the network device fault rapid recovery method based on neighbor device assistance described in this invention, the method for determining topology consistency and transmitting configuration data includes calling the local neighbor relationship table and the neighbor-side configuration table, reading the target end interface name, peer end interface name, neighbor device identifier and target device configuration data corresponding to the location, and constructing an interface mapping by the target end interface name, peer end interface name and neighbor device identifier.

[0028] Neighboring devices compare the target interface name, peer interface name, neighboring device identifier, and interface mapping obtained from the link discovery message.

[0029] Topology consistency is determined when the comparison results meet the following conditions: the target end interface name is consistent, the peer end interface name is consistent, and the adjacent device identifiers are consistent.

[0030] The adjacent device uses the target device's configuration data as the return configuration data and sends the return configuration data to the replaced target device through the private extension field of the link discovery message.

[0031] The private extended field carries the target interface name and peer interface name corresponding to the returned configuration data.

[0032] When the comparison results do not meet the requirements of the target end interface name being consistent, the peer end interface name being consistent, and the adjacent device identifier being consistent, the adjacent device will not send back configuration data, but will record the corresponding message sequence number as a historical record.

[0033] As a preferred embodiment of the network device fault rapid recovery method based on neighbor device assistance described in this invention, the fragmentation reassembly and configuration judgment includes: when the length of the backhaul configuration data exceeds the length of the private extension field of the link discovery message, the neighbor device splits the backhaul configuration data into multiple configuration fragments, and writes a fragmentation tag and fragmentation sequence number into the private extension field of each configuration fragment.

[0034] The replaced target device receives the link discovery message.

[0035] The adjacent device identifier, the target interface name, and the peer interface name are used as indexes to establish a reorganization cache, which is then written to the configuration fragments in sequence according to the fragment number.

[0036] When the received configuration fragment has an end marker and the fragment sequence number is consecutive, the target device after replacement outputs the reassembled return configuration data.

[0037] Configuration determination includes determining whether the configuration data of the target device to be replaced is in an empty state.

[0038] When it is determined that the configuration data of the target device to be replaced is in an empty state, the reconstructed configuration data is output and then a consistency check is performed.

[0039] The consistency verification process includes, when the replaced target device receives the reassembled backhaul configuration data from two adjacent devices, calculating the configuration summary for each reassembled backhaul configuration data and performing a consistency comparison.

[0040] The consistency check is considered successful when the consistency comparison results show that the two configuration digests are consistent.

[0041] If the consistency comparison result does not meet the conditions, the consistency verification is deemed to have failed, and the adjacent device identifier and message sequence number are recorded as historical records.

[0042] As a preferred embodiment of the network device fault rapid recovery method based on neighbor device assistance described in this invention, the loading of configuration data includes: the replaced target device performing syntax parsing on the reconstructed return configuration data.

[0043] The replaced target device establishes a binding relationship between the configuration content corresponding to the target interface name and the peer interface name in the returned configuration data and the local port based on the target interface name and peer interface name recorded in the local neighbor relationship table.

[0044] The replaced target device will send back configuration data to the running configuration area and continue to periodically send link discovery messages.

[0045] Another objective of this invention is to provide a network device fault rapid recovery system based on neighbor device assistance. This system can maintain the neighbor-side configuration on the adjacent device side and trigger topology consistency determination and configuration backhaul when the configuration field of the replacement target device is detected to be empty. This solves the problems of current configuration recovery technologies that rely on centralized network management or manual intervention, such as high dependence on the central platform, unclear triggering conditions for configuration backhaul after fault replacement, and easy occurrence of mismatched configurations.

[0046] As a preferred embodiment of the network device fault rapid recovery system based on neighbor device assistance described in this invention, it includes a neighbor information collection and configuration synchronization module, a topology consistency determination and configuration feedback module, and a configuration reassembly verification and loading module.

[0047] The neighbor information collection and configuration synchronization module is used to collect the identifiers and interface information of neighboring devices, synchronize the target device configuration data through private extended fields, and output the neighbor-side configuration.

[0048] The topology consistency determination and configuration feedback module is used to receive the target device configuration data, take the neighbor side configuration as input, combine the interface mapping and device identifier to determine topology consistency, and feedback the configuration data.

[0049] The configuration reorganization verification and loading module is used to perform fragment reorganization and configuration judgment on the returned configuration data and perform consistency verification, and load the configuration data.

[0050] Another object of the present invention is to provide a network device fault rapid recovery device based on neighbor device assistance, including a memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program to implement the steps of a network device fault rapid recovery method based on neighbor device assistance.

[0051] Another object of the present invention is to provide a storage medium for rapid recovery of network device faults based on neighbor device assistance, wherein a computer program is stored thereon, and when the computer program is executed by a processor, the steps of a method for rapid recovery of network device faults based on neighbor device assistance are implemented.

[0052] The beneficial effects of this invention are as follows: The network device fault rapid recovery method based on neighbor device assistance provided by this invention, through a scheme that forms a neighbor-side configuration on the adjacent device side and triggers configuration backhaul when the configuration field of the replacement target device is detected to be empty, enables the network device after fault replacement to obtain the historical configuration corresponding to the original device without relying on a centralized management platform; by combining interface mapping and device identifier for topology consistency determination, it ensures that the backhauled configuration data is consistent with the current physical connection relationship, avoiding mismatched configurations; by performing fragmentation and reassembly, configuration judgment and consistency verification on the backhauled configuration data, it ensures the integrity and consistency of the configuration data during transmission and loading, thereby giving the configuration loading process executable logical constraints. This invention achieves better results in terms of configuration recovery executability after fault replacement, reliability of configuration and topology matching, and configuration consistency control in scenarios with multiple neighbors. Attached Figure Description

[0053] To more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings used in the following description of the embodiments will be briefly introduced. Obviously, the drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0054] Figure 1 This is an overall flowchart of a method for rapid network device fault recovery based on neighbor device assistance, provided in Embodiment 1 of the present invention.

[0055] Figure 2 This is a schematic diagram of the device relationships in a method for rapid network device fault recovery based on neighbor device assistance, provided in Embodiment 1 of the present invention. Detailed Implementation

[0056] To make the above-mentioned objects, features, and advantages of the present invention more apparent and understandable, specific embodiments of the present invention will be described in detail below with reference to the accompanying drawings. Obviously, the described embodiments are only a part of the embodiments of the present invention, and not all of them. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort should fall within the protection scope of the present invention.

[0057] Example 1, referring to Figure 1-2 As an embodiment of the present invention, a method for rapid network device fault recovery based on neighbor device assistance is provided, comprising: S1: Collect neighboring device identifiers and interface information, synchronize target device configuration data through private extended fields, and output neighbor-side configuration.

[0058] Ensure that the ports of the network device are in a linked state.

[0059] The target device periodically sends link discovery messages to neighboring devices and receives response messages from neighboring devices.

[0060] The neighboring device identifier and the interface information corresponding to the target port are obtained by parsing the link discovery message.

[0061] The neighboring device identifiers include the device type identifier, the device physical address identifier, and the device system identifier.

[0062] The interface information includes the target interface name, the peer interface name, the peer interface physical address, and the port link status.

[0063] Write the neighbor device identifiers and interface information into the local neighbor relationship table according to the association relationship between the target end interface name, the peer end interface name, and the neighbor device identifier.

[0064] A preferred approach for writing to the local neighbor table is:

[0065] in, Represents a uniform index triple. Indicates the target interface name. Indicates the peer interface name. Indicates the physical address identifier of adjacent devices. Indicates the time of reception.

[0066] Record the reception time and message sequence number as historical records.

[0067] A preferred approach to using the recorded reception time and message sequence number as historical records is:

[0068] in, Represents the local neighbor relationship table. Indicates the type identifier of adjacent devices. Indicates the system identifier of adjacent devices. Indicates the physical address of the peer interface. Indicates the port link status. Indicates the message sequence number.

[0069] Furthermore, target device configuration data is extracted from the private extended fields of the link discovery message; Using the target interface name, peer interface name, and neighbor device identifier recorded in the local neighbor relationship table as indexes, the target device configuration data, the corresponding target interface name, and the peer interface name are bound together and then written into the neighbor-side configuration table.

[0070] Writing to the neighbor-side configuration table includes when the target device's configuration data changes in the link discovery message.

[0071] Neighboring devices locate the corresponding entry in the neighbor-side configuration table based on the same index and update the target device configuration data.

[0072] Update the reception time and message sequence number of the entry when the target device configuration data in the link discovery message is empty.

[0073] Neighboring devices ensure that the target device configuration data in the neighbor-side configuration table is not overwritten, and record the reception time and message sequence number of this empty state data.

[0074] A preferred approach for writing and updating the neighbor-side configuration table without overwriting empty states is as follows:

[0075]

[0076] in, Indicates time Received link discovery message, This function represents the extraction of target device configuration data from private extended fields. This indicates the target device configuration data. Represents empty state data. This represents the neighbor-side configuration table. This represents the most recent non-empty target device configuration data under the same index. It represents the most recent valid record time before the current time.

[0077] Output the target device configuration data, the corresponding target interface name and the neighbor test configuration after establishing the binding relationship between the target interface name and the peer interface name.

[0078] S2: Receive the target device configuration information, take the neighbor-side configuration as input, combine the interface mapping and device identifier to determine the topology consistency, and send back the configuration data.

[0079] like Figure 2 As shown, the replaced target device periodically sends link discovery messages to adjacent devices, and the private extension field of the link discovery message replaces the target device configuration data with empty data.

[0080] Neighboring devices receive link discovery messages, parse the messages to obtain the neighboring device identifier and the interface information corresponding to the target port.

[0081] The reception time and message sequence number are recorded as historical records. Neighboring devices locate the link discovery message based on the target end interface name, peer end interface name, and neighboring device identifier already written in the local neighbor relationship table.

[0082] The condition for triggering a data return is defined as the condition where the configuration data of the target device being replaced is in an empty state.

[0083] A preferred approach to using empty-state data as the backhaul trigger condition is as follows:

[0084]

[0085] in, This indicates that the target device configuration data will be replaced. Indicates the target device after replacement at time Link discovery messages sent and received by neighboring devices. This indicates the extraction of private extended fields. This indicates the return trigger flag.

[0086] Furthermore, the local neighbor relationship table and the neighbor-side configuration table are called to read the target end interface name, peer end interface name, neighbor device identifier and target device configuration data corresponding to the location, and the target end interface name, peer end interface name and neighbor device identifier are used to form an interface mapping.

[0087] Neighboring devices compare the target interface name, peer interface name, neighboring device identifier, and interface mapping obtained from the link discovery message.

[0088] Topology consistency is determined when the comparison results meet the following conditions: the target end interface name is consistent, the peer end interface name is consistent, and the adjacent device identifiers are consistent.

[0089] A preferred approach to determining topological consistency is:

[0090] in, This indicates a topology consistency flag.

[0091] The adjacent device uses the target device's configuration data as the return configuration data and sends the return configuration data to the replaced target device through the private extension field of the link discovery message.

[0092] A preferred method for sending back configuration data is:

[0093] in, This indicates that configuration data is being sent back.

[0094] The private extended field carries the target interface name and peer interface name corresponding to the returned configuration data.

[0095] When the comparison results do not meet the requirements of the target end interface name being consistent, the peer end interface name being consistent, and the adjacent device identifier being consistent, the adjacent device will not send back configuration data, but will record the corresponding message sequence number as a historical record.

[0096] S3: Perform fragmentation and reassembly, configuration judgment and consistency verification on the returned configuration data, and load the configuration data.

[0097] When the length of the backhaul configuration data exceeds the length of the private extension field of the link discovery message, the adjacent device will split the backhaul configuration data into multiple configuration fragments and write a fragment tag and fragment sequence number into the private extension field of each configuration fragment.

[0098] A preferred approach to determining the number of shards is as follows:

[0099] in, Indicates the number of shards configured. Function representing data length This indicates the length carried by the private extended field.

[0100] Fragmentation markers include a start marker and an end marker.

[0101] The replaced target device receives the link discovery message, uses the neighboring device identifier, the target end interface name and the peer end interface name as indexes to establish a reassembly cache, and writes it into the configuration fragments in sequence according to the fragment number.

[0102] When the received configuration fragment has an end marker and the fragment sequence number is consecutive, the target device after replacement outputs the reassembled return configuration data.

[0103] A preferred option for reorganization is:

[0104] in, This indicates the completion of the restructuring. This indicates that the end marker has reached the indicated quantity. This indicates a continuous indication of the segment sequence number.

[0105] Configuration determination includes determining whether the configuration data of the target device to be replaced is in an empty state.

[0106] When it is determined that the configuration data of the target device to be replaced is in an empty state, the reconstructed configuration data is output and sent back for consistency verification.

[0107] A preferred scheme for consistency verification is:

[0108] in, This indicates that the consistency check has passed. This indicates the reassembled configuration data transmitted back from two adjacent devices. Indicates and Different configuration data from two adjacent devices are recombined and transmitted back.

[0109] The consistency verification process includes, when the replaced target device receives the reassembled backhaul configuration data from two adjacent devices, calculating the configuration summary for each reassembled backhaul configuration data and performing a consistency comparison.

[0110] The consistency check is considered successful when the consistency comparison results show that the two configuration digests are consistent.

[0111] If the consistency comparison result does not meet the conditions, the consistency verification is deemed to have failed, and the adjacent device identifier and message sequence number are recorded as historical records.

[0112] Furthermore, the replaced target device will perform syntax parsing on the reassembled return configuration data.

[0113] The replaced target device establishes a binding relationship between the configuration content corresponding to the target interface name and the peer interface name in the returned configuration data and the local port based on the target interface name and peer interface name recorded in the local neighbor relationship table.

[0114] The replaced target device will send back configuration data to the running configuration area and continue to periodically send link discovery messages.

[0115] Example 2, an embodiment of the present invention, provides a network device fault rapid recovery system based on neighbor device assistance, including a neighbor information collection and configuration synchronization module, a topology consistency determination and configuration backhaul module, and a configuration reassembly verification and loading module.

[0116] The neighbor information collection and configuration synchronization module is used to collect the identification and interface information of neighboring devices, synchronize the target device configuration data through private extended fields, and output the neighbor-side configuration.

[0117] The topology consistency determination and configuration feedback module is used to receive the target device configuration information, take the neighbor side configuration as input, combine the interface mapping and device identifier to determine topology consistency, and feedback the configuration data.

[0118] The configuration reassembly verification and loading module is used to perform fragment reassembly and configuration judgment on the returned configuration data, perform consistency verification, and load the configuration data.

[0119] This embodiment also provides a computer device, including a memory and a processor. The memory stores a computer program, and when the processor executes the computer program, it implements the network device fault rapid recovery method based on neighbor device assistance as proposed in the above embodiment.

[0120] This embodiment also provides a computer-readable storage medium storing a computer program thereon. When the computer program is executed by a processor, it implements the network device fault rapid recovery method based on neighbor device assistance as proposed in the above embodiment.

[0121] If the aforementioned functions are implemented as software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this invention, essentially, or the part that contributes to the prior art, or a portion of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this invention. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0122] The logic and / or steps represented in the flowchart or otherwise described herein, for example, can be considered as a sequenced list of executable instructions for implementing logical functions, and can be embodied in any computer-readable medium for use by, or in conjunction with, an instruction execution system, apparatus, or device (such as a computer-based system, a processor-including system, or other system that can fetch and execute instructions from, an instruction execution system, apparatus, or device). For the purposes of this specification, "computer-readable medium" can be any means that can contain, store, communicate, propagate, or transmit programs for use by, or in conjunction with, an instruction execution system, apparatus, or device.

[0123] More specific examples of computer-readable media (a non-exhaustive list) include: electrical connections (electronic devices) having one or more wires, portable computer disk drives (magnetic devices), random access memory (RAM), read-only memory (ROM), erasable and editable read-only memory (EPROM or flash memory), fiber optic devices, and portable optical disc read-only memory (CDROM). Furthermore, computer-readable media can even be paper or other suitable media on which the program can be printed, because the program can be obtained electronically, for example, by optically scanning the paper or other medium, followed by editing, interpreting, or otherwise processing as necessary, and then stored in computer memory.

[0124] It should be understood that various parts of the present invention can be implemented in hardware, software, firmware, or a combination thereof. In the above embodiments, multiple steps or methods can be implemented in software or firmware stored in memory and executed by a suitable instruction execution system. For example, if implemented in hardware, as in another embodiment, it can be implemented using any one or a combination of the following techniques known in the art: discrete logic circuits having logic gates for implementing logical functions on data signals, application-specific integrated circuits (ASICs) having suitable combinational logic gates, programmable gate arrays (PGAs), field-programmable gate arrays (FPGAs), etc.

[0125] It should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention and not to limit it. Although the present invention has been described in detail with reference to preferred embodiments, those skilled in the art should understand that modifications or equivalent substitutions can be made to the technical solutions of the present invention without departing from the spirit and scope of the technical solutions of the present invention, and all such modifications or substitutions should be covered within the scope of the claims of the present invention.

Claims

1. A method for rapid network device fault recovery based on neighbor device assistance, characterized in that, include: Collect neighboring device identifiers and interface information, synchronize target device configuration data through private extended fields, and output neighbor-side configuration; Receive the target device configuration data, take the neighbor side configuration as input, combine the interface mapping and device identifier to determine topology consistency, and send back the configuration data; Perform fragmentation and reassembly, configuration judgment and consistency verification on the returned configuration data, and load the configuration data; The received target device configuration data includes data where the configuration fields in the received replacement target device configuration data are empty after the target device has been replaced due to a fault. Taking the neighbor-side configuration as input includes calling the neighbor-side configuration and extracting and replacing the historical device identifier, historical interface mapping and historical configuration data corresponding to the target device.

2. The method for rapid network device fault recovery based on neighbor device assistance as described in claim 1, characterized in that: The collection of adjacent device identifiers and interface information includes, Ensure that the ports of the network device are in a linked state; The target device periodically sends link discovery messages to neighboring devices and receives response messages from neighboring devices. The neighboring device identifier and the interface information corresponding to the target port are obtained by parsing the link discovery message; Write the neighbor device identifiers and interface information into the local neighbor relationship table according to the association relationship between the target end interface name, the peer end interface name, and the neighbor device identifier; Record the reception time and message sequence number as historical records.

3. The method for rapid network device fault recovery based on neighbor device assistance as described in claim 1 or 2, characterized in that: The output neighbor-side configuration includes, Extract the target device configuration data from the private extended fields of the link discovery message; Using the target end interface name, peer end interface name and neighbor device identifier recorded in the local neighbor relationship table as indexes, the target device configuration data, the corresponding target end interface name and peer end interface name are bound together and then written into the neighbor side configuration table. The output includes the configuration data written to the target device, the neighbor-side configuration after the corresponding target interface name and peer interface name are bound together.

4. The method for rapid network device fault recovery based on neighbor device assistance as described in claim 3, characterized in that: The received target device configuration data includes, The replaced target device periodically sends link discovery messages to neighboring devices; Replace empty data in the private extension field of the link discovery message with the target device configuration data; Neighboring devices receive link discovery messages, parse the link discovery messages to obtain the neighboring device identifier and the interface information corresponding to the target port; Record the reception time and message sequence number as historical records; The neighboring device locates the link discovery message based on the target end interface name, peer end interface name, and neighboring device identifier already written in its local neighbor relationship table; The condition for triggering a data return is defined as the condition where the configuration data of the target device being replaced is in an empty state.

5. The method for rapid network device fault recovery based on neighbor device assistance as described in claim 1, 2, or 4, characterized in that: Determining topology consistency and sending back configuration data includes, Call the local neighbor relationship table and the neighbor-side configuration table to read the target end interface name, peer end interface name, neighbor device identifier and target device configuration data corresponding to the location, and construct an interface mapping with the target end interface name, peer end interface name and neighbor device identifier; Neighboring devices compare the target end interface name, peer end interface name, neighboring device identifier, and interface mapping obtained from the link discovery message with the interface mapping. Topology consistency is determined when the comparison results meet the following conditions: the target end interface name is consistent, the peer end interface name is consistent, and the adjacent device identifiers are consistent. The adjacent device uses the target device's configuration data as the return configuration data and sends the return configuration data to the replaced target device through the private extension field of the link discovery message; The private extended field carries the target interface name and peer interface name corresponding to the returned configuration data; When the comparison results do not meet the requirements of the target end interface name being consistent, the peer end interface name being consistent, and the adjacent device identifier being consistent, the adjacent device will not send back configuration data, but will record the corresponding message sequence number as a historical record.

6. The method for rapid network device fault recovery based on neighbor device assistance as described in claim 5, characterized in that: The fragmentation reassembly and configuration determination includes, When the length of the backhaul configuration data exceeds the length of the private extension field of the link discovery message, the adjacent device will split the backhaul configuration data into multiple configuration fragments and write a fragment tag and fragment sequence number into the private extension field of each configuration fragment. The replaced target device receives the link discovery message; Establish a reorganization cache by using the adjacent device identifier, the target end interface name and the peer end interface name as indexes, and write it into the configuration fragments in sequence according to the fragment number; When the received configuration fragment has an end marker and the fragment sequence number is consecutive, the target device after replacement outputs the reassembled return configuration data; Configuration determination includes determining whether the configuration data of the target device to be replaced is in an empty state; When it is determined that the configuration data of the target device to be replaced is in an empty state, the reconstructed configuration data is output and then a consistency check is performed. The consistency verification process includes, when the replaced target device receives the reassembled return configuration data from two adjacent devices, calculating the configuration summary for each reassembled return configuration data and performing a consistency comparison. The consistency check is considered passed when the consistency comparison results show that the two configuration digests are consistent. If the consistency comparison result does not meet the conditions, the consistency verification is deemed to have failed, and the adjacent device identifier and message sequence number are recorded as historical records.

7. The method for rapid network device fault recovery based on neighbor device assistance as described in claim 1, 2, 4 or 6, characterized in that: The loaded configuration data includes, The target device after replacement will perform syntax parsing on the reconstructed return configuration data; The replaced target device establishes a binding relationship between the configuration content corresponding to the target interface name and the peer interface name in the returned configuration data and the local port based on the target interface name and peer interface name recorded in the local neighbor relationship table. The replaced target device will send back configuration data to the running configuration area and continue to periodically send link discovery messages.

8. A network device fault rapid recovery system based on neighbor device assistance, employing the network device fault rapid recovery method based on neighbor device assistance as described in any one of claims 1 to 7, characterized in that: This includes a neighbor information collection and configuration synchronization module, a topology consistency determination and configuration feedback module, and a configuration reassembly verification and loading module; The neighbor information collection and configuration synchronization module is used to collect neighbor device identifiers and interface information, synchronize target device configuration data through private extended fields, and output neighbor-side configuration. The topology consistency determination and configuration feedback module is used to receive the target device configuration data, take the neighbor side configuration as input, combine the interface mapping and device identifier to determine topology consistency, and feedback the configuration data. The configuration reorganization verification and loading module is used to perform fragment reorganization and configuration judgment on the returned configuration data and perform consistency verification, and load the configuration data.

9. A computer device comprising a memory and a processor, wherein the memory stores a computer program, characterized in that, When the processor executes the computer program, it implements the steps of the network device fault rapid recovery method based on neighbor device assistance as described in any one of claims 1 to 7.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by the processor, it implements the steps of the network device fault rapid recovery method based on neighbor device assistance as described in any one of claims 1 to 7.

Images