CN106712997B - Method, equipment and system for recovering table entry - Google Patents
Method, equipment and system for recovering table entry Download PDFInfo
- Publication number
- CN106712997B CN106712997B CN201510790717.5A CN201510790717A CN106712997B CN 106712997 B CN106712997 B CN 106712997B CN 201510790717 A CN201510790717 A CN 201510790717A CN 106712997 B CN106712997 B CN 106712997B
- Authority
- CN
- China
- Prior art keywords
- entry
- service
- equipment
- entries
- table item
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/06—Management of faults, events, alarms or notifications
- H04L41/0654—Management of faults, events, alarms or notifications using network fault recovery
- H04L41/0668—Management of faults, events, alarms or notifications using network fault recovery by dynamic selection of recovery network elements, e.g. replacement by the most appropriate element after failure
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
The embodiment of the invention provides a method, equipment and a system for recovering table entries. The method comprises the following steps: after being restarted, the first equipment receives a first table item sent by the second equipment, wherein the first table item is a table item in a first table item set on the second equipment; the first device recovers the table entry according to the first table entry; and the first device switches the service from the second device to the first device when receiving an end identifier sent by the second device, wherein the end identifier indicates that all the entries in the first entry set are sent to the end. According to the method, the device and the system for recovering the table items, after the first device is restarted, the table items are recovered by receiving the first table items sent by the second device, and when the end marks indicating the end of sending all the first table items are received, the service is switched from the second device to the first device, so that the condition that the service is switched to the first device when the table items are not completely recovered is avoided, and the service is not interrupted.
Description
Technical Field
The present invention relates to the field of communications, and in particular, to a method, device and system for entry recovery.
Background
China Mobile static Internet Protocol Radio Access Network (IPRAN) is in large-scale commercial use, and labels, routes and the like of network nodes are statically configured instead of dynamically learned. In order to make the service not interrupted during the switching and back-switching process when the main device fails, an Address Resolution Protocol (ARP) dual-device hot standby may be deployed at the L2/L3 node, as shown in fig. 1: the master device backs up the learned ARP entry to the Backup device through a Remote Backup Server (RBS)/Remote Backup Profile (RBP) mechanism. However, with the expansion of the service, the Traffic of the L2/L3 node increases, the configuration file will reach tens of thousands of lines, and when the whole host device is restarted and recovered, due to the reestablishment of a large number of Pseudo Wires (PW), Traffic Engineering (TE), Operation Administration and Maintenance (OAM), the problem that ARP entries are not recovered during the service cut-back due to various timing sequences can be generated, thereby causing corresponding service interruption.
Disclosure of Invention
Embodiments of the present invention provide a method, an apparatus, and a system for recovering a table entry, which can enable a service to be uninterrupted.
In a first aspect, a method for entry recovery is provided, including:
after being restarted, the first equipment receives a first table item sent by the second equipment, wherein the first table item is a table item in a first table item set on the second equipment;
the first device recovers the table entry according to the first table entry;
and the first device switches the service from the second device to the first device when receiving an end identifier sent by the second device, wherein the end identifier indicates that all the entries in the first entry set are sent to the end.
With reference to the first aspect, in a first possible implementation manner of the first aspect, the method further includes: the first device obtains a second entry from the local storage file, wherein the second entry is an entry in a second entry set backed up in the local storage file;
the first device performs entry recovery according to the first entry, including:
and the first equipment recovers the table entry according to the first table entry and the second table entry.
With reference to the first possible implementation manner of the first aspect, in a second possible implementation manner of the first aspect, the performing, by the first device, entry recovery according to the first entry and the second entry includes:
the first device writes the first table entry received from the second device into a memory of the first device;
the first device writes the second table entry acquired from the local storage file into a memory of the first device;
when the table entry name of the first table entry is the same as the table entry name of the second table entry, the first table entry covers the second table entry.
With reference to the first possible implementation manner of the first aspect or the second possible implementation manner of the first aspect, in a third possible implementation manner of the first aspect, the method further includes:
after receiving the end identifier sent by the second device and switching the service from the second device to the first device, the first device deletes the entry with the entry name different from that of any entry in the first entry set from the recovered entries.
With reference to any one possible implementation manner of the first aspect to the third possible implementation manner of the first aspect, in a fourth possible implementation manner of the first aspect, the method further includes:
and the first equipment switches the service from the second equipment to the first equipment when determining that the second equipment fails.
With reference to any one possible implementation manner of the first aspect to the fourth possible implementation manner of the first aspect, in a fifth possible implementation manner of the first aspect, the method further includes:
the first device updates the second set of entries in the local storage file according to the recovered entries.
With reference to the first aspect and any one of the first possible implementation manner to the fifth possible implementation manner of the first aspect, in a sixth possible implementation manner of the first aspect, the first entry is an Address Resolution Protocol (ARP) entry, a Broadband Remote Access Server (BRAS) user entry, a Dynamic Host Configuration Protocol (DHCP) Snooping entry, or an Internet Group Management Protocol (IGMP) Snooping entry.
In a second aspect, a method for entry recovery is provided, including:
the second equipment determines that the first equipment is restarted;
the second device sends a first table entry to the first device, so that the first device can recover the table entry according to the first table entry, wherein the first table entry is a table entry in a first table entry set on the second device;
and the second device sends an end identifier to the first device when all the entries in the first entry set are sent to the end, so that the first device switches the service from the second device to the first device when receiving the end identifier.
With reference to the second aspect, in a first possible implementation manner of the second aspect, the first entry is an address resolution protocol ARP entry, a broadband remote access server BRAS user entry, a dynamic host configuration protocol Snooping DHCP Snooping entry, or an internet group management protocol Snooping IGMP Snooping entry.
In a third aspect, a first device for entry recovery is provided, including:
a receiving module, configured to receive a first entry sent by a second device after the first device is restarted, where the first entry is an entry in a first entry set on the second device;
a recovery module, configured to perform entry recovery according to the first entry received by the receiving module;
a first switching module, configured to switch a service from the second device to the first device when receiving an end identifier sent by the second device, where the end identifier is used to indicate that all entries in the first entry set end to be sent.
With reference to the third aspect, in a first possible implementation manner of the third aspect, the first device further includes:
an obtaining module, configured to obtain a second entry from a local storage file, where the second entry is an entry in a second entry set backed up in the local storage file;
wherein the recovery module is further configured to:
and performing table entry recovery according to the first table entry and the second table entry.
With reference to the first possible implementation manner of the third aspect, in a second possible implementation manner of the third aspect, the recovery module is specifically configured to:
writing the first table entry received from the second device into a memory of the first device;
writing the second table entry obtained from the local storage file into the memory of the first device;
when the table entry name of the first table entry is the same as the table entry name of the second table entry, the first table entry covers the second table entry.
With reference to the first possible implementation manner of the third aspect or the second possible implementation manner of the third aspect, in a third possible implementation manner of the third aspect, the recovery module is further configured to delete, in the recovered entry, an entry whose entry name is different from an entry name of any entry in the first entry set after the first switching module receives the end identifier sent by the second device and switches the service from the second device to the device.
With reference to any one possible implementation manner of the first possible implementation manner of the third aspect to the third possible implementation manner of the third aspect, in a fourth possible implementation manner of the third aspect, the first device further includes:
and the second switching module is used for switching the service from the second equipment to the equipment when the second equipment is determined to have the fault.
With reference to the first possible implementation manner of the third aspect to the fourth possible implementation manner of the third aspect, in a fifth possible implementation manner of the third aspect, the first device further includes:
and the updating module is used for updating the second table item set in the local storage file according to the recovered table item.
With reference to the third aspect and any one possible implementation manner of the first possible implementation manner to the fifth possible implementation manner of the third aspect, in a sixth possible implementation manner of the third aspect, the first entry is an Address Resolution Protocol (ARP) entry, a Broadband Remote Access Server (BRAS) user entry, a Dynamic Host Configuration Protocol (DHCP) Snooping entry, or an Internet Group Management Protocol (IGMP) Snooping entry.
In a fourth aspect, a second device for entry recovery is provided, including:
the determining module is used for determining that the first equipment is restarted;
a first sending module, configured to send a first entry to the first device after the determining module determines that the first device is restarted, so that the first device performs entry recovery according to the first entry, where the first entry is an entry in a first entry set on the second device;
a second sending module, configured to send an end identifier to the first device when sending of all entries in the first entry set is ended, so that the first device switches a service from the second device to the first device when receiving the end identifier.
With reference to the fourth aspect, in a first possible implementation manner of the fourth aspect, the first entry is an address resolution protocol ARP entry, a broadband remote access server BRAS user entry, a dynamic host configuration protocol Snooping DHCP Snooping entry, or an internet group management protocol Snooping IGMP Snooping entry.
In a fifth aspect, a system for entry recovery is provided, including: the first device for entry recovery of the third aspect and the second device for entry recovery of the fourth aspect are described above.
In a sixth aspect, a first device for entry recovery is provided, including: a processor and a memory;
the memory stores a program, and the processor executes the program to perform the method for entry recovery according to the first aspect or any one of the possible implementation manners of the first aspect.
A seventh aspect provides a second device for entry recovery, including: a processor and a memory.
The memory stores a program, and the processor executes the program to perform the method for entry recovery according to the second aspect or any one of the possible implementations of the second aspect.
Based on the above technical solution, in the method, the device, and the system for recovering entries according to the embodiments of the present invention, after the first device is restarted, the first device performs entry recovery by receiving the first entry sent by the second device, and when receiving the end identifier indicating that all the first entries are sent to the end, the service is switched from the second device to the first device, so that switching the service to the first device without completing entry recovery is avoided, and thus the service is not interrupted.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings needed to be used in the embodiments of the present invention will be briefly described below, and it is obvious that the drawings described below are only some embodiments of the present invention, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without creative efforts.
Fig. 1 is a schematic diagram of an application scenario of an embodiment of the present invention.
FIG. 2 is a diagram illustrating a method for entry recovery according to an embodiment of the present invention.
FIG. 3 is a schematic diagram illustrating an interaction flow of entry recovery according to an embodiment of the present invention.
FIG. 4 is a diagram illustrating a method for entry recovery according to yet another embodiment of the invention.
FIG. 5 is a schematic block diagram of an entry recovery apparatus according to an embodiment of the present invention.
FIG. 6 is a schematic block diagram of an entry recovery apparatus according to yet another embodiment of the present invention.
FIG. 7 is a schematic block diagram of a system according to an embodiment of the present invention.
Fig. 8 is a schematic structural diagram of an entry recovery apparatus according to an embodiment of the present invention.
Fig. 9 is a schematic structural diagram of an entry recovery apparatus according to yet another embodiment of the present invention.
Detailed Description
The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are some, not all, embodiments of the present invention. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
Fig. 1 is a schematic diagram of an application scenario of an embodiment of the present invention. Fig. 1 is a diagram illustrating a typical network configuration of a mobile ip ran network. In the scenario shown in fig. 1, a base station is hung under an access ring Packet Transport Network device (PTN) -1/2, a Virtual Leased Line (VLL) is deployed and doubly returned to PTN-3/4, PTN-3/4 is at an L2/L3 node, a mode that the VLL accesses a three-Layer Virtual Private Network (L3 VPN) may be adopted to implement service conversion from two layers to three layers, and a service may also be forwarded between PTN-3/4 and PTN-5/6 by using an L3 VPN. The first device and the second device of the ARP table entry hot standby in the embodiment of the invention can be respectively deployed at the PTN-3 and PTN-4 positions.
When the first device is in the master state and the second device is in the standby state, the first device may back up the learned new entry to the second device through the RBS/RBP mechanism. Therefore, when the first device fails or is overhauled or otherwise needs to suspend forwarding the current service, the first device is switched from the main state to the standby state, and the second device is switched from the standby state to the main state, so that the service is switched from the first device to the second device, and the forwarding of the service is not interrupted. The service is switched from the first device to the second device by using a Virtual Router Redundancy Protocol (VRRP)/cross device link aggregation (E-Trunk) configured by the first device and the second device. When two devices capable of forwarding services need to determine the master/standby state, the first device and the second device may send heartbeat messages to each other, and may determine their own roles in the backup group according to the heartbeat messages, if the priority of the first device is determined to be higher than the priority of the second device, the first device is in the master state, the second device is in the standby state, and then only the device in the master state can send heartbeat messages to the standby device. When the second device no longer receives the heartbeat message sent by the first device within a certain time threshold, the second device may consider that the first device is faulty, and at this time, only the second device may forward the service, that is, the priority of the second device is the highest, the second device is raised to the master state, so that the service is switched from the first device to the second device, and forwarding of the service is not interrupted.
And when the fault of the first equipment is eliminated or the maintenance is finished or the forwarding service is restarted, restarting the whole machine. After the complete machine of the first device is restarted, the first device receives the message sent by the second device, and can determine that the priority of the first device is higher than that of the second device, at this time, the first device is in a master state, the second device is in a standby state, and therefore the service is switched from the second device to the first device. However, since a large amount of PW, TE, OAM, etc. needs to be re-established, there is a problem that the entry on the second device is still not backed up when the service is switched back to the first device, resulting in service interruption.
For example, after the whole first device is restarted, the heartbeat message sent by the second device is not received all the time, and after the time threshold is exceeded, the first device is directly raised to the main state, so that the first device does not back up the ARP entry on the second device, which causes service interruption. Or after the whole first device is restarted, the heartbeat message sent by the second device is received, but until the service is switched back to the first device, the channel of the ARP hot standby is not established all the time, that is, the first device cannot receive the ARP table entry sent by the second device, so that the first device does not back up the ARP table entry, and the service is interrupted. Or after the first equipment is restarted, the heartbeat message sent by the second equipment is received, the ARP hot standby channel is also established, but if the establishment is too late, when the waiting recovery (WTR) is counted down when the business is switched back to the first equipment, the ARP list item is still not backed up, and the business is interrupted. Or after the first equipment is restarted, the heartbeat message sent by the second equipment is received, the ARP hot standby channel is also established, but the ARP list item is slowly backed up due to the high CPU of the main control board, and the ARP list item is not completely backed up when the service is switched back to the first equipment, so that the service is interrupted. Or the bidirectional forwarding detection (which can play a role of fast convergence time) of the first device and the second device is restored first, and the VRRP/E-TRUNK heartbeat is resumed (that is, the first device can receive the heartbeat message), so that the first device quickly determines that the priority of the first device is higher than that of the second device, and then the first device is upgraded to the main device, and thus the first device does not have to back up the ARP entry on the second device, which causes service interruption.
In the prior art, when the whole machine is restarted, the time for switching back the VRRP/E-TRUNK to the WTR is prolonged, namely, a larger time experience value is set, or a time threshold value is set for the VRRP/E-TRUNK heartbeat timeout, and the like, so that time is strived for RBS establishment and ARP hot standby. However, because different network pressures are different, ARP entry backup completion times are different, and the network of an operator is also expanding, it is difficult to provide an experience value suitable for all networks, and even impossible to adapt to the continuous expansion of the network.
The technical scheme of the invention can be applied to various double-computer backup scenes. For example: the method includes the following steps that ARP table entries of L2L3 nodes in an Access network are subjected to dual-computer hot standby, user table entries of Broadband Remote Access Servers (BRAS), DHCPsnooping (Dynamic Host Configuration Protocol) table entries or dual-computer hot standby of Internet Group Management Protocol Snooping (IGMP Snooping) table entries, and the like. Correspondingly, the table entries in the embodiment of the present invention include ARP table entries, BRAS user table entries, DHCP Snooping table entries, or IGMP Snooping table entries.
In the embodiment of the invention, the service is the service based on the table entry. For example, if the entry is an ARP entry, the traffic is a forwarding traffic based on the ARP entry. For convenience of description, the following embodiments take the ARP entry as an example for illustration, but the present invention is not limited to this.
FIG. 2 is a diagram illustrating a method 100 for entry recovery according to an embodiment of the present invention. As shown in fig. 2, the method 100 may be performed by a first device, comprising:
s110, after the first device is restarted, receiving a first table item sent by a second device, wherein the first table item is a table item in a first table item set on the second device;
s120, the first device recovers the table entry according to the first table entry;
s130, when receiving the end identifier sent by the second device, the first device switches the service from the second device to the first device, where the end identifier indicates that all entries in the first entry set are sent to the end.
In the embodiment of the present invention, the first device may be a primary device in a dual-device backup scenario, and the second device may be a secondary device in the dual-device backup scenario, but the present invention is not limited to this, for example, in a scenario where functions of the primary and secondary devices are similar, the first device and the second device may also be interchanged.
Specifically, in the case of restarting after a failure of the first device, an entry (denoted as a first entry) on the second device needs to be backed up from the second device for entry recovery. Since the first device and the second device are configured with VRRP/E-TRUNK, when the first device is restarted, it may be determined that the priority of the first device is higher than that of the second device according to the received message of the second device, and therefore, the first device is about to be raised to the master state. However, the VRRP/E-TRUNK is set on the first device to be linked with the table entry backup, and the first device may be set in the master state only when the end identifier is received, that is, the first device completes all the first table entries from the second device backup. Therefore, when receiving the end identifier sent by the second device, the first device switches the service from the second device to the first device, so that the service is not interrupted.
Therefore, in the method for recovering entries in the embodiment of the present invention, after the first device is restarted, the first device performs entry recovery by receiving the first entry sent by the second device, and when an end identifier indicating that all the first entries are sent is received, the service is switched from the second device to the first device, so that switching the service to the first device without completing entry recovery is avoided, and thus the service is not interrupted.
In S110, after being restarted, the first device receives a first entry sent by the second device, where the first entry is an entry in a first entry set on the second device.
Specifically, in the embodiment of the present invention, after the first device is restarted, the first device receives all entries in the first entry set from the second device in a manner of receiving a message to perform entry recovery, for example, the first device backs up the first entry to a memory of the first device, so that the service is not interrupted when being switched back to the first device.
It should be understood that the first entry may be an entry backed up to the second device before the first device fails, or may be a new entry learned by the second device according to a new service after the service is switched from the first device to the second device.
In S120, the first device performs entry recovery according to the first entry.
Specifically, after being restarted, the first device receives a first entry sent by the second device, and performs entry recovery according to the first entry, that is, recovers the first entry to the memory of the first device. The recovery process may be performed simultaneously with receiving the first entry, and entry recovery is also completed when all entries in the first set of entries are received.
In S130, the first device switches the service from the second device to the first device when receiving an end identifier sent by the second device, where the end identifier indicates that all entries in the first entry set are sent to the end.
Specifically, when all the entries in the first entry set are sent to the end, the second device sends an end identifier to the first device. The second device may carry an end identifier in the packet that sends the first entry, and when receiving the end identifier, the first device determines that all entries in the first entry set have been received. The first device and the second device are configured with VRRP/E-TRUNK, the first device sets the VRRP/E-TRUNK to be linked with the first list item backup, and when the ending identification is received, the first device can be lifted to be the main device. At this time, the service may be switched from the second device to the first device so that the service is not interrupted.
Therefore, in the method for recovering entries in the embodiment of the present invention, after the first device is restarted, the first device performs entry recovery by receiving the first entry sent by the second device, and when an end identifier indicating that all the first entries are sent is received, the service is switched from the second device to the first device, so that switching the service to the first device without completing entry recovery is avoided, and thus the service is not interrupted.
In an embodiment of the present invention, optionally, the method may further include:
the first device acquires a second table entry from a local storage file, wherein the second table entry is a table entry in a second table entry set backed up from the local storage file;
in this case, the first device performs entry recovery according to the first entry, including: and the first equipment recovers the table entry according to the first table entry and the second table entry.
Specifically, the first device may persist the entry, that is, convert the entry in the memory into a file in the storage medium, and data in the file is not lost even when the overall device is powered down. For example, a local storage file is recorded locally, and the second entry is stored in a local memory card (cfcard) or other storage medium periodically by means of a write log. After the first device is restarted, data can be read from the local storage file and written into the memory to recover the second entry, and meanwhile, the first device can still receive the first entry sent by the second device. And the first device performs entry recovery according to the second entry in the local storage file and the first entry received from the second device, and switches the service from the second device to the first device when receiving the end identifier sent by the second device.
Restoring the second entry to memory from the first device's local storage file is similar to a configuration restore, and is done almost instantaneously, and thus generally faster than the first device backing up the first entry from the second device.
It should be understood that the second device may also store the entry in the memory in a local storage file of the second device, so as to perform entry recovery when a subsequent service is switched back to the second device.
Optionally, in a case that the first entry and the second entry exist simultaneously, the first device performs entry recovery according to the first entry and the second entry. Specifically, the first device writes the first entry received from the second device into a memory of the first device; the first device writes the second table entry acquired from the local storage file into a memory of the first device; when the table entry name of the first table entry is the same as the table entry name of the second table entry, the first table entry covers the second table entry.
Specifically, the first entry is an entry received from the second device, and when the first device fails, the second device may start a learning function, reestablish a new entry, or update the content of the entry in the process of forwarding the service by the second device. For example, since the second device may actively learn entries while being the master device, for a first entry with the same name as the second entry, the entry content may already be different, and the content of the first entry may better serve the current traffic. Therefore, for the first entry and the second entry with the same name, the first entry is updated and the second entry is to be overwritten.
For example, for an ARP entry, the entry name may be an Internet Protocol (IP) address. When the first device fails, the second device may start a learning function, reestablish a new entry, or update a Media Access Control (MAC) address corresponding to the IP address during the process of forwarding the service. Therefore, when the IP address of the first table entry is the same as the IP address of the second table entry, the first table entry overwrites the second table entry.
In the embodiment of the present invention, optionally, the method further includes: after receiving the end identifier sent by the second device and switching the service from the second device to the first device, the first device deletes the entry with the entry name different from that of any entry in the first entry set from the recovered entries.
In particular, when the first device has received all of the entries in the first set of entries, the first device may have previously recovered all of the entries in the second set of entries from the local storage file. In this case, an entry having an entry name different from that of any entry in the first entry set needs to be deleted from the restored entries. That is, the deleted entry is an entry whose entry name is different from that of any entry in the first entry set in the second entry set.
That is, after the first device receives the end identifier, if the entry name of the first entry is the same as the entry name of the second entry, the first entry covers the second entry; if a third entry exists in the second entry set (the third entry represents an entry whose entry name is different from the entry name of any entry in the first entry set), the third entry is deleted, and this deletion process may be referred to as an aging process.
Optionally, in an embodiment of the present invention, the method further includes: and the first equipment switches the service from the second equipment to the first equipment when determining that the second equipment fails.
Specifically, after the first device is restarted, the second entry is restored from the local storage file by reading data, and at the same time, the first device receives the first entry sent by the second device. As described above, if the second device finishes sending all the first entries, the second device sends the end identifier to the first device, and the first device performs service switching accordingly.
When the second device is in the master state, a heartbeat message is sent to the first device, and when the first device does not receive the heartbeat message any more within a certain time threshold, the first device can consider that the second device fails. And if the second equipment fails without sending all the first table entries, the first equipment performs service switching when determining that the second equipment fails. That is, the first device has not received the end identifier, the second device fails, and at this time, the priority of the first device is the highest, the first device is upgraded to the master device, and the first device switches the service from the second device to the first device. Because the recovery of the entries from the local storage file is almost instantaneously completed, when the first device switches the service from the second device to the first device, the first device has already recovered all entries in the second entry set from the local storage file, and has obtained a part of the first entries from the second device, and if an entry with the same name as the first entry exists in the second entry, the first entry may also cover the second entry, so that the service is processed according to the recovered entries, and the service is not interrupted.
It should be understood that the time threshold may be set according to practical applications, and the present invention is not limited thereto.
Optionally, in an embodiment of the present invention, the method further includes: the first device updates the second set of entries in the local storage file according to the recovered entries.
Specifically, the recovered entry is the current latest entry. For example, when the first device receives the end identifier, the recovered entries include all first entries in the first entry set and all second entries in the second entry set, and in a case where a third entry (the third entry indicates an entry having a different entry name from any entry in the first entry set), the third entry is to be deleted; when the first device does not receive the end identifier and the second device fails, the first device is raised to a main state, and the service is switched from the first device to the second device, and at this time, the entries recovered on the memory of the first device include part of the first entries in the first entry set and all of the second entries in the second entry set. In addition, after the service is resumed and forwarded on the first device, the first device may dynamically learn a new entry, and the priority of the new entry, the priority of the first entry, and the priority of the second entry are sequentially reduced, and in the memory, the entry with a high priority may cover the entry with a low priority. The first device updates the locally stored file based on the latest entry recovered. After the first device operates stably, when the table entry changes, the first device can also update the table entry into the local storage file in real time.
The first device writes the recovered first entry into a local storage file, where the first entry is triggered by a service corresponding to the first entry, and when the second device sends the first entry to the first device, the first entry may be marked with a special identifier, so that the first device can identify that the first entry is an entry on the second device. Correspondingly, when the learned new entry is written into the local storage file, the learned new entry is also triggered by the service corresponding to the new entry.
Therefore, in the method for recovering entries in the embodiment of the present invention, after the first device is restarted, the first entry sent by the second device is received to recover the entries, and when the end identifier indicating that all the first entries are sent is received, the service is switched from the second device to the first device, so that the service is switched to the first device without completing entry recovery, and thus the service is not interrupted; in addition, in combination with recovering the entries from the local storage file, when the second device fails without sending all the first entries, the service can be uninterrupted.
In an embodiment of the present invention, after determining that the first device is restarted, the second device sends the first entry to the first device, and the first device backs up the first entry on the second device by receiving a message. Meanwhile, the first device may also recover the second entry from the local storage file by reading data. For the first table entry and the second table entry with the same name, the first table entry covers the second table entry. When the message received by the first device carries the end identifier, the first device may have previously recovered all entries in the second entry set from the local storage file, and therefore, entries having different entry names from any entry in the first entry set may be deleted from the recovered entries. When the message received by the first device carries the end identifier, the first device may switch the service from the second device to the first device, and since all the entries on the second device are restored to the first device at this time, the service is not interrupted.
As shown in fig. 3, an interaction flow diagram of one embodiment of the present invention is shown. The flow of the present embodiment starts from the first device restart. The meaning of various terms in this embodiment is the same as that of the foregoing embodiments.
201, the first device restarts, and acquires the second entry from the local storage file for entry recovery.
The second device determines 202 that the first device reboots.
203, the second device sends the first table entry to the first device.
204, the first device performs entry recovery according to the first entry and the second entry, and when the entry name of the first entry is the same as the entry name of the second entry, the first entry covers the second entry.
In one case, if the second device fails without sending all the first entries, the first device performs service switching when determining that the second device fails.
Since the recovery of the entries from the local storage file is almost instantaneously complete, the first device may process the traffic using entries recovered from all entries in the second set of entries and from the portion of the first entries that have been received, so that the traffic is not interrupted.
206, in another case, the second device does not have a failure during the sending of the table entry, and the second device sends an end identifier to the first device when the sending of all the table entries in the first table entry set is ended.
And 207, the first device switches the service from the second device to the first device when receiving the end identifier.
If an entry having an entry name different from the entry name of any entry in the first entry set exists in the restored entries, the first device deletes such entry. In addition, the first device updates the latest entry to the local storage file. In the stable operation of the first device, when the table entry is changed, the changed table entry is also updated to the local storage file.
As shown in FIG. 4, a schematic flow chart diagram of a method 300 of entry recovery according to an embodiment of the present invention is shown, where the method 300 may be performed by a second device. As shown in fig. 4, the method 300 includes:
s310, the second equipment determines that the first equipment is restarted;
s320, the second device sends a first entry to the first device, so that the first device can recover entries according to the first entry, where the first entry is an entry in a first entry set on the second device;
s330, when all the entries in the first entry set are sent to the end, the second device sends an end identifier to the first device, so that the first device switches the service from the second device to the first device when receiving the end identifier.
Specifically, VRRP/E-TRUNK is configured on the first device and the second device, and after the first device is restarted, the first device needs to re-determine the active/standby state with the second device and sends a heartbeat message to the second device, and the second device receives the heartbeat message and can determine that the first device is restarted. At this time, the second device serving as the primary device sends a message carrying a first entry to the standby device (i.e., the first device), so that the first device receives the first entry and performs entry recovery according to the first entry, where the first entry is an entry in a first entry set on the second device. In addition, the second device can know that the priority of the second device is lower than that of the first device according to the heartbeat message sent by the first device. However, since the VRRP/E-TRUNK configured on the first device is linked with the first table entry backup, the first device may be upgraded to the master device when the ending identifier is received. Therefore, after the second device finishes sending all the entries in the first entry set, the second device carries the end identifier in the message, so that the first device switches the service from the second device to the first device when receiving the end identifier, and the forwarding of the service is not interrupted.
Therefore, in the method for recovering the table entry in the embodiment of the present invention, the second device sends the end identifier to the first device when all the table entries are sent, so that switching the service to the first device without completing the table entry recovery is avoided, and the service is not interrupted.
In S310, the second device determines that the first device reboots.
Specifically, VRRP/E-TRUNK is configured on the first device and the second device, and after the first device is restarted, the first device needs to re-determine the active/standby state with the second device and sends a heartbeat message to the second device, and the second device can determine that the first device is restarted after receiving the heartbeat message. Then, the second device also sends a heartbeat message to the first device, so that the first device determines the priority level according to the heartbeat message. In S320, the second device sends a first entry to the first device, so that the first device performs entry recovery according to the first entry, where the first entry is an entry in a first entry set on the second device.
Specifically, the second device determines that its priority is lower than that of the first device according to the heartbeat message sent by the first device, but the first device sets VRRP/E-TRUNK linked with the table backup, and only when receiving the end identifier, the second device can be in the master state. At this time, the second device is still in the master state, and sends the first entry on the second device to the first device in the form of a message, so that the first device can recover the entry according to the first entry, thereby preventing service interruption.
In S330, the second device sends an end identifier to the first device when all entries in the first entry set are sent to the end, so that the first device switches the service from the second device to the first device when receiving the end identifier.
Specifically, after the first device is restarted, the second device sends the first table entry to the first device, the first device is provided with VRRP/E-TRUNK linked with table entry backup, and the first device can be raised to the master state only when the end identifier is received, that is, when the first device completes all the first table entries from the second device backup. Therefore, when the second device finishes sending all the entries in the first entry set, the message for sending the first entry carries an end identifier, so that the first device switches the service from the second device to the first device when receiving the end identifier, and the first device can back up all the entries on the first device, so that the service is not interrupted.
Optionally, the first entry is an ARP entry, a BRAS user entry, a DHCP Snooping entry, or an igmpssnooping entry.
It should be understood that, in the embodiment of the present invention, the interaction between the first device and the second device and the related characteristics, functions, and the like described in the first device side correspond to the description in the second device side, and for brevity, no further description is provided here.
It should be understood that, in various embodiments of the present invention, the sequence numbers of the above-mentioned processes do not mean the execution sequence, and the execution sequence of each process should be determined by its function and inherent logic, and should not constitute any limitation on the implementation process of the embodiments of the present invention.
The method for entry recovery according to the embodiment of the present invention is described in detail above with reference to fig. 2, fig. 3, and fig. 4, and the apparatus for entry recovery according to the embodiment of the present invention is described in detail below with reference to fig. 5 and fig. 6.
FIG. 5 illustrates a schematic block diagram of a first apparatus 500 for entry recovery in accordance with an embodiment of the present invention. As shown in fig. 5, the first apparatus 500 includes:
a receiving module 510, configured to receive a first entry sent by a second device after the first device is restarted, where the first entry is an entry in a first entry set on the second device;
a recovering module 520, configured to perform entry recovery according to the first entry received by the receiving module;
a first switching module 530, configured to switch the service from the second device to the first device when receiving an end identifier sent by the second device, where the end identifier is used to indicate that all entries in the first entry set are sent end.
Therefore, in the table entry recovery device according to the embodiment of the present invention, after the first device is restarted, the first device performs table entry recovery by receiving the first table entry sent by the second device, and when receiving the end identifier indicating that all the first table entries are sent, the service is switched from the second device to the first device, so that switching of the service to the first device without completing table entry recovery is avoided, and thus the service is not interrupted.
In this embodiment of the present invention, optionally, the first device further includes:
an obtaining module, configured to obtain a second entry from a local storage file, where the second entry is an entry in a second entry set backed up in the local storage file;
wherein the recovery module is further to:
and recovering the table items according to the first table item and the second table item.
In this embodiment of the present invention, optionally, the recovery module is specifically configured to:
writing the first table entry received from the second device into a memory of the first device;
writing the second table entry obtained from the local storage file into a memory of the first device;
and when the table item name of the first table item is the same as the table item name of the second table item, the first table item covers the second table item.
Optionally, in this embodiment of the present invention, the recovering module is further configured to delete, in the recovered entry, an entry whose entry name is different from an entry name of any entry in the first entry set after the first switching module switches the service from the second device to the first device after receiving the end identifier sent by the second device.
In this embodiment of the present invention, optionally, the first device further includes:
and the second switching module is used for switching the service from the second equipment to the first equipment when the second equipment is determined to have a fault.
Optionally, in an embodiment of the present invention, the first device further includes:
and the updating module is used for updating the second table item set in the local storage file according to the recovered table item.
In this embodiment of the present invention, optionally, the first entry is an address resolution protocol ARP entry, a broadband remote access server BRAS user entry, a dynamic host configuration protocol Snooping DHCP Snooping entry, or an internet group management protocol Snooping IGMP Snooping entry.
It should be understood that the first device 500 for entry recovery according to the embodiment of the present invention may correspond to an execution main body of the method for entry recovery according to the embodiment of the present invention, and the above and other operations and/or functions of each module in the first device 500 are respectively for implementing corresponding steps of each foregoing method, and are not described herein again for brevity.
Therefore, in the device for recovering the table entry in the embodiment of the present invention, after the first device is restarted, the first device performs table entry recovery by receiving the first table entry sent by the second device, and when receiving the end identifier indicating that all the first table entries are sent, the service is switched from the second device to the first device, so that the service is switched to the first device without completing table entry recovery, and thus the service is not interrupted; in addition, in combination with recovering the entries from the local storage file, when the second device fails without sending all the first entries, the service can be uninterrupted.
FIG. 6 is a schematic block diagram of a second apparatus 700 for entry recovery according to an embodiment of the present invention. As shown in fig. 6, the second apparatus 700 includes:
a determining module 710 for determining that the first device reboots;
a first sending module 720, configured to send a first entry to the first device after the determining module determines that the first device is restarted, so that the first device performs entry recovery according to the first entry, where the first entry is an entry in a first entry set on the second device;
a second sending module 730, configured to send an end identifier to the first device when sending of all entries in the first entry set is ended, so that the first device switches the service from the second device to the first device when receiving the end identifier.
Therefore, in the table entry recovery device according to the embodiment of the present invention, the second device sends the end identifier to the first device when all the table entries are sent, so that switching of a service to the first device without completing the table entry recovery is avoided, and thus the service is not interrupted.
Optionally, in this embodiment of the present invention, the first entry is an address resolution protocol ARP entry, a broadband remote access server BRAS user entry, a dynamic host configuration protocol Snooping DHCP Snooping entry, or an internet group management protocol Snooping IGMP Snooping entry.
It should be understood that the second device 700 for entry recovery according to the embodiment of the present invention may correspond to an execution main body of the method for entry recovery according to the embodiment of the present invention, and the above and other operations and/or functions of each module in the second device 700 are respectively for implementing corresponding steps of each foregoing method, and are not described herein again for brevity.
The embodiment of the invention also provides a system for recovering the table entry. As shown in fig. 7, the system 900 includes:
the foregoing first apparatus 500 of an embodiment of the present invention and the second apparatus 700 of an embodiment of the present invention.
Fig. 8 shows a structure of a first apparatus provided in another embodiment of the present invention, which includes at least one processor 1102 (e.g., a CPU), at least one network interface 1105 or other communication interfaces, a memory 1106, and at least one communication bus 1103 for implementing connection communication between these devices. The processor 1102 is operable to execute executable modules, such as computer programs, stored in the memory 1106. The Memory 1106 may comprise a high-speed Random Access Memory (RAM) and may also include a non-volatile Memory (non-volatile Memory), such as at least one disk Memory. The communication connection with at least one other network element is made through at least one network interface 1105 (which may be wired or wireless).
In some embodiments, the memory 1106 stores routines 11061, and the processor 1102 executes the routines 11061 to perform operations for:
after the first device is restarted, receiving a first table item sent by a second device, wherein the first table item is a table item in a first table item set on the second device;
performing table item recovery according to the first table item;
and switching the service from the second device to the first device when receiving an end identifier sent by the second device, wherein the end identifier indicates that all the entries in the first entry set are sent to the end.
Optionally, the processor 1102 is configured to obtain a second entry from the local storage file, where the second entry is an entry in a second entry set backed up in the local storage file;
the processor 1102 is specifically configured to perform entry recovery according to the first entry and the second entry.
Optionally, the processor 1102 is configured to write the first entry received from the second device into a memory of the first device;
writing the second table entry obtained from the local storage file into a memory of the first device;
and when the table item name of the first table item is the same as the table item name of the second table item, the first table item covers the second table item.
Optionally, the processor 1102 is configured to delete an entry with an entry name different from that of any entry in the first entry set from the recovered entries after receiving the end identifier sent by the second device and switching the service from the second device to the first device.
Optionally, the processor 1102 is configured to switch traffic from the second device to the first device when it is determined that the second device fails.
Optionally, the processor 1102 is configured to update the second set of entries in the local storage file according to the recovered entries.
Optionally, the first entry is an address resolution protocol ARP entry, a broadband remote access server BRAS user entry, a dynamic host configuration protocol Snooping DHCP Snooping entry, or an internet group management protocol Snooping IGMP Snooping entry.
As can be seen from the above technical solutions provided in the embodiments of the present invention, after the first device is restarted, the entry recovery is performed by receiving the first entry sent by the second device, and when the end identifier indicating that all the first entries are sent is received, the service is switched from the second device to the first device, so that the service is prevented from being switched to the first device without completing the entry recovery, and the service is not interrupted; in addition, in combination with recovering the entries from the local storage file, when the second device fails without sending all the first entries, the service can be uninterrupted.
Fig. 9 shows a structure of a second apparatus provided in another embodiment of the present invention, which includes at least one processor 1302 (e.g., a CPU), at least one network interface 1305 or other communication interfaces, a memory 1306, and at least one communication bus 1303, which is used to implement connection communication between these devices. The processor 1302 is configured to execute executable modules, such as computer programs, stored in the memory 1306. The Memory 1306 may include a high-speed Random Access Memory (RAM) and may further include a non-volatile Memory (non-volatile Memory), such as at least one disk Memory. The communication connection with at least one other network element is implemented via at least one network interface 1305 (which may be wired or wireless).
In some embodiments, memory 1306 stores program 13061 and processor 1302 executes program 13061 to:
determining that the first device is restarted;
sending a first table entry to the first device so that the first device can perform table entry recovery according to the first table entry, wherein the first table entry is a table entry in a first table entry set on the second device;
and when the sending of all the entries in the first entry set is finished, sending a finishing identifier to the first device, so that the first device can switch the service from the second device to the first device when receiving the finishing identifier.
Optionally, the first entry is an address resolution protocol ARP entry, a broadband remote access server BRAS user entry, a dynamic host configuration protocol Snooping DHCP Snooping entry, or an internet group management protocol Snooping IGMP Snooping entry.
It can be seen from the above technical solutions provided in the embodiments of the present invention that, by sending the end identifier to the first device when all the entries are sent, the embodiments of the present invention avoid switching the service to the first device without completing entry recovery, so that the service is not interrupted.
It should be understood that the specific examples are provided only to assist those skilled in the art to better understand the embodiments of the present invention, and are not intended to limit the scope of the embodiments of the present invention.
It should also be understood that in the present embodiment, "B corresponding to a" means that B is associated with a, from which B can be determined. It should also be understood, however, that determining B from a does not mean determining B from a alone, but may also be determined from a and/or other information.
Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present invention.
It is clear to those skilled in the art that, for convenience and brevity of description, the specific working processes of the above-described systems, apparatuses and units may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.
In the several embodiments provided in the present application, it should be understood that the disclosed system, apparatus and method may be implemented in other ways. For example, the above-described apparatus embodiments are merely illustrative, and for example, the division of the units is only one logical division, and other divisions may be realized in practice, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.
The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.
In addition, functional units in the embodiments of the present invention may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit.
The functions, if implemented in the form of software functional units and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present invention may be embodied in the form of a software product, which is stored in a storage medium and includes instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method according to the embodiments of the present invention. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk, and other various media capable of storing program codes.
The above description is only for the specific embodiments of the present invention, but the scope of the present invention is not limited thereto, and any person skilled in the art can easily conceive of the changes or substitutions within the technical scope of the present invention, and all the changes or substitutions should be covered within the scope of the present invention. Therefore, the protection scope of the present invention shall be subject to the protection scope of the appended claims.
Claims (19)
1. A method for entry recovery, comprising:
after being restarted, first equipment receives a first table item sent by second equipment, wherein the first table item is a table item in a first table item set on the second equipment;
the first device restores the first table entry to a memory of the first device;
and when receiving an end identifier sent by the second device, the first device switches the service from the second device to the first device, wherein the end identifier indicates that all entries in the first entry set are sent to the end.
2. The method of claim 1, further comprising:
the first equipment acquires a second table entry from a local storage file, wherein the second table entry is a table entry in a second table entry set backed up in the local storage file;
wherein, the first device performs entry recovery according to the first entry, including:
and the first equipment recovers the table entry according to the first table entry and the second table entry.
3. The method of claim 2, wherein the first device performing entry recovery according to the first entry and the second entry comprises:
the first device writes the first table entry received from the second device into a memory of the first device;
the first device writes the second entry obtained from the local storage file into a memory of the first device;
and when the table item name of the first table item is the same as the table item name of the second table item, the first table item covers the second table item.
4. A method according to claim 2 or 3, characterized in that the method further comprises:
and after the first device receives the end identifier sent by the second device and switches the service from the second device to the first device, deleting the table entries with the table entry names different from the table entry names of any table entries in the first table entry set from the recovered table entries.
5. A method according to claim 2 or 3, characterized in that the method further comprises:
and the first equipment switches the service from the second equipment to the first equipment when determining that the second equipment has the fault.
6. A method according to claim 2 or 3, characterized in that the method further comprises:
and the first equipment updates the second item set in the local storage file according to the recovered items.
7. The method according to any of claims 1 to 3, wherein the first entry is an Address resolution protocol, ARP, entry, a broadband remote Access Server, BRAS, user entry, a dynamic host configuration protocol Snooping, DHCPsnooping, entry, or an Internet group management protocol Snooping, IGMP Snooping entry.
8. A method for entry recovery, comprising:
the second equipment determines that the first equipment is restarted;
the second device sends a first entry to the first device, so that the first device can restore the first entry to a memory of the first device, wherein the first entry is an entry in a first entry set on the second device;
and the second device sends an end identifier to the first device when all the entries in the first entry set are sent to the end, so that the first device switches the service from the second device to the first device when receiving the end identifier.
9. The method of claim 8, wherein the first entry is an Address Resolution Protocol (ARP) entry, a Broadband Remote Access Server (BRAS) user entry, a Dynamic Host Configuration Protocol (DHCP) Snooping (DHCPsnooping) entry, or an Internet group management protocol (IGMP Snooping) entry.
10. A first device, comprising:
a receiving module, configured to receive a first entry sent by a second device after the first device is restarted, where the first entry is an entry in a first entry set on the second device;
a recovery module, configured to recover the first entry received by the receiving module to a memory of the first device;
a first switching module, configured to switch a service from the second device to the first device when receiving an end identifier sent by the second device, where the end identifier is used to indicate that all entries in the first entry set are sent to the end.
11. The first device of claim 10, further comprising:
an obtaining module, configured to obtain a second entry from a local storage file, where the second entry is an entry in a second entry set backed up in the local storage file;
wherein the recovery module is further to:
and recovering the table items according to the first table item and the second table item.
12. The first device of claim 11, wherein the recovery module is specifically configured to:
writing the first table entry received from the second device into a memory of the first device;
writing the second table entry obtained from the local storage file into a memory of the first device;
and when the table item name of the first table item is the same as the table item name of the second table item, the first table item covers the second table item.
13. The first device according to claim 11 or 12, wherein the recovering module is further configured to delete an entry with an entry name different from that of any entry in the first entry set from the recovered entries after the first switching module switches traffic from the second device to the first device after receiving the end identifier sent by the second device.
14. The first device according to claim 11 or 12, characterized in that the first device further comprises:
and the second switching module is used for switching the service from the second equipment to the first equipment when the second equipment is determined to have a fault.
15. The first device according to claim 11 or 12, characterized in that the first device further comprises:
and the updating module is used for updating the second table item set in the local storage file according to the recovered table item.
16. The apparatus according to any of claims 10 to 12, wherein the first entry is an address resolution protocol, ARP, broadband remote access server, BRAS, user entry, dynamic host configuration protocol, Snooping, DHCPSnooping, or internet group management protocol, Snooping, IGMP Snooping entry.
17. A second apparatus, comprising:
the determining module is used for determining that the first equipment is restarted;
a first sending module, configured to send a first entry to the first device after the determining module determines that the first device is restarted, so that the first device recovers the first entry to a memory of the first device, where the first entry is an entry in a first entry set on the second device;
a second sending module, configured to send an end identifier to the first device when sending of all entries in the first entry set is ended, so that the first device switches a service from the second device to the first device when receiving the end identifier.
18. The second device of claim 17, wherein the first entry is an Address Resolution Protocol (ARP) entry, a Broadband Remote Access Server (BRAS) user entry, a Dynamic Host Configuration Protocol (DHCP) Snooping (DHCPsnooping) entry, or an Internet group management protocol (IGMP Snooping) entry.
19. A system for entry recovery, comprising:
a first device according to any one of claims 10 to 16 and a second device according to claim 17 or 18.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201510790717.5A CN106712997B (en) | 2015-11-16 | 2015-11-16 | Method, equipment and system for recovering table entry |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201510790717.5A CN106712997B (en) | 2015-11-16 | 2015-11-16 | Method, equipment and system for recovering table entry |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN106712997A CN106712997A (en) | 2017-05-24 |
| CN106712997B true CN106712997B (en) | 2020-04-14 |
Family
ID=58933397
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201510790717.5A Active CN106712997B (en) | 2015-11-16 | 2015-11-16 | Method, equipment and system for recovering table entry |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN106712997B (en) |
Families Citing this family (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107331079B (en) * | 2017-06-06 | 2019-11-26 | 浪潮金融信息技术有限公司 | Method for processing business and device |
| CN109117311A (en) * | 2018-08-22 | 2019-01-01 | 郑州云海信息技术有限公司 | A kind of fault recovery method and device |
| CN112152920B (en) * | 2019-06-28 | 2021-12-28 | 华为技术有限公司 | Method and device for realizing table entry backup |
| CN113810260A (en) * | 2020-06-17 | 2021-12-17 | 中国联合网络通信集团有限公司 | Network networking method and system |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101471940A (en) * | 2007-12-28 | 2009-07-01 | 华为技术有限公司 | Method, system and device for synchronizing BGP route |
| CN101557317A (en) * | 2009-05-26 | 2009-10-14 | 杭州华三通信技术有限公司 | Active dialogue backup system, equipment and method in dual-server hot-backup network |
| CN101577719A (en) * | 2009-06-09 | 2009-11-11 | 华为技术有限公司 | Double hot standby method, device and system |
| CN102148677A (en) * | 2010-02-10 | 2011-08-10 | 杭州华三通信技术有限公司 | Method for updating address resolution protocol table entries and core switch |
| CN104518960A (en) * | 2014-12-05 | 2015-04-15 | 华为技术有限公司 | Delayed back-switching method, devices and system |
| CN104683486A (en) * | 2015-03-27 | 2015-06-03 | 杭州华三通信技术有限公司 | Method and device for processing synchronous messages in distributed system and distributed system |
Family Cites Families (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JP6052044B2 (en) * | 2013-04-30 | 2016-12-27 | 富士通株式会社 | Packet transport network system |
| CN104572198B (en) * | 2014-12-31 | 2018-04-10 | 华为技术有限公司 | A kind of service restoration method and device |
-
2015
- 2015-11-16 CN CN201510790717.5A patent/CN106712997B/en active Active
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101471940A (en) * | 2007-12-28 | 2009-07-01 | 华为技术有限公司 | Method, system and device for synchronizing BGP route |
| CN101557317A (en) * | 2009-05-26 | 2009-10-14 | 杭州华三通信技术有限公司 | Active dialogue backup system, equipment and method in dual-server hot-backup network |
| CN101577719A (en) * | 2009-06-09 | 2009-11-11 | 华为技术有限公司 | Double hot standby method, device and system |
| CN102148677A (en) * | 2010-02-10 | 2011-08-10 | 杭州华三通信技术有限公司 | Method for updating address resolution protocol table entries and core switch |
| CN104518960A (en) * | 2014-12-05 | 2015-04-15 | 华为技术有限公司 | Delayed back-switching method, devices and system |
| CN104683486A (en) * | 2015-03-27 | 2015-06-03 | 杭州华三通信技术有限公司 | Method and device for processing synchronous messages in distributed system and distributed system |
Also Published As
| Publication number | Publication date |
|---|---|
| CN106712997A (en) | 2017-05-24 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN107623593B (en) | Method and equipment for hot standby of dual computers based on CU separation | |
| CN106712997B (en) | Method, equipment and system for recovering table entry | |
| CN102752209B (en) | Realize address fast switch over method and the routing forwarding equipment of backup services | |
| CN103514173B (en) | The method and node device of data processing | |
| CN111130879B (en) | PBFT algorithm-based cluster exception recovery method | |
| CN112039769B (en) | Routing processing method and network equipment | |
| CN105472049B (en) | CGN backup protection method and device for carrier-grade network address conversion | |
| CN102447587B (en) | Graceful restart method based on OSPF (Open Shortest Path First Interior Gateway Protocol) protocol and router thereof | |
| CN102624635A (en) | Method and device for realizing graceful restart | |
| CN105242990A (en) | Cloud platform based data backup method and apparatus | |
| CN111176888B (en) | Disaster recovery method, device and system for cloud storage | |
| CN113169895A (en) | N +1 redundancy for virtualization services with low latency failover | |
| CN105634832B (en) | A kind of backup method and device of server | |
| CN105589735B (en) | Remote disaster recovery method, device and system | |
| CN105340226A (en) | Primary and secondary system handover method for dynamic route device, and apparatus thereof | |
| CN112367182B (en) | Configuration method and device of disaster recovery main and standby equipment | |
| JP5775473B2 (en) | Edge device redundancy system, switching control device, and edge device redundancy method | |
| CN111083049B (en) | User table item recovery method and device, electronic equipment and storage medium | |
| CN109815065B (en) | Main-standby switching method and device for dual computers and electronic equipment | |
| CN109189854B (en) | Method and node equipment for providing continuous service | |
| CN105939254A (en) | Method and device for switching state of VRRP (Virtual Router Redundancy Protocol) backup set | |
| WO2024036990A1 (en) | Data recovery method and apparatus, network device, and storage medium | |
| US11042430B2 (en) | Elastic consistency high availability in multiple boards | |
| CN111683160A (en) | MAC address recovery method and device | |
| CN101582802A (en) | Operation maintenance system and method of network access device |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |