Dual-master device management system and method, electronic device and storage medium

Abstract

The embodiment of the invention provides a dual-master device management system and method, an electronic device and a storage medium, and relates to the technical field of security services. The system comprises a first controller, a second controller, at least one first CPE device and at least one second CPE device, and the first controller and the second controller are connected through a node line so as to perform data synchronization and node communication between the first controller and the second controller; the first CPE equipment is provided with a first main line and a first standby line, is connected with the first controller through the first main line and is connected with the second controller through the first standby line; and the second CPE equipment establishes connection with the second controller through the second main line and establishes connection with the first controller through the second standby line. The system adopts a double-main-controller architecture, can realize quick failover, improves the reliability of the network, has relatively high availability, and solves the problem of service interruption caused by a single-point fault in the existing method.

Description

Technical Field

[0001] The present application relates to the field of security service technology, and in particular to a dual-master device management system, method, electronic device and storage medium. Background Art

[0002] With the development of network technology, SD-WAN, as a new type of network architecture, provides a more flexible and cost-effective network connection solution. In traditional SD-WAN deployment, the controller is the central node of the entire network, responsible for managing network devices, routing policies, and network policies. However, this centralized architecture has the risk of single point failure. Once the controller fails, the entire network may be affected, resulting in service interruption and data transmission delay, which is a serious security risk for enterprises relying on SD-WAN. Summary of the invention

[0003] The purpose of the embodiments of the present application is to provide a dual-master device management system, method, electronic device and storage medium, which adopts a dual-master controller architecture, can achieve fast failover, improve network reliability, have strong high availability, and solve the service interruption problem caused by single point failure in existing methods.

[0004] The embodiment of the present application provides a dual-master device management system, the system comprising a first controller, a second controller, at least one first CPE device and at least one second CPE device, wherein:

[0005] The first controller and the second controller are connected via a node line to perform data synchronization and node communication between each other;

[0006] The first CPE device has a first main line and a first backup line, is connected to the first controller through the first main line, and is connected to the second controller through the first backup line;

[0007] The second CPE device has a second main line and a second backup line, and is connected to the second controller via the second main line, and is connected to the first controller via the second backup line.

[0008] In the above implementation process, a dual-main controller architecture is set up. When one of the controllers fails, the CPE device can connect to the other controller through a backup line, ensuring the continuous operation of the network and the continuity of services, achieving rapid fault transfer, improving the reliability of the network, and having strong high availability, which solves the service interruption problem caused by single point failure in existing methods.

[0009] Furthermore, the first backup line is used to disconnect the first main line and establish a connection with the second controller if the first controller fails;

[0010] The second backup line is used to disconnect the second main line and establish a connection with the first controller if the second controller fails.

[0011] In the above implementation process, the CPE device supports primary and backup registration lines. When the primary line fails, it automatically switches to the backup line and re-establishes the management channel, ensuring the normal operation of the system and enhancing the high availability of the network.

[0012] Further, the node line is used to synchronize data generated during the fault from the first controller without fault to the second controller after the fault is recovered, or synchronize data generated during the fault from the second controller without fault to the first controller after the fault is recovered;

[0013] The user also initiates a management task to the first CPE device through the first controller, or initiates a management task to the second CPE device through the first controller, the node line and the second controller.

[0014] In the above implementation process, real-time data synchronization is performed through the node line to ensure the consistency of data between the two controllers; the administrator can initiate management tasks through any controller node to achieve the function of managing the entire network CPE devices through any controller.

[0015] The embodiment of the present application further provides a dual-master device management method, which is applied to the above-mentioned dual-master device management system, and the method includes:

[0016] If the first controller fails, the first main line is disconnected, the first CPE device automatically switches to the first backup line, and establishes a connection with the second controller through the first backup line;

[0017] If the second controller fails, the second main line is disconnected, the second CPE device automatically switches to the second backup line, and establishes a connection with the first controller through the second backup line.

[0018] In the above implementation process, a dual-main controller architecture is adopted, and a main and backup line is set. When the main line fails, the CPE device automatically switches to the backup line and re-establishes the management channel. The management authority of the CPE device can be transferred to other controllers through the backup line, realizing fast fault transfer, improving network reliability, reducing the impact of faults on network services, having strong high availability, and solving the service interruption problem caused by single point failure in existing methods.

[0019] Furthermore, if the first CPE device detects that the first controller has returned to normal, the first backup line is disconnected, and a connection is reestablished with the first controller via the first main line. Meanwhile, the second controller synchronizes data generated during the fault to the first controller via the node line.

[0020] In the above implementation process, after the fault is restored, the CPE device re-establishes a channel with the corresponding controller through the main line, and synchronizes the data generated during the fault, without affecting the normal operation of the system.

[0021] Furthermore, if the second controller recovers, the second CPE device disconnects the second backup line and reconnects to the second controller through the second main line. Meanwhile, the first controller synchronizes the data generated during the failure to the second controller through the node line.

[0022] In the above implementation process, after the fault is restored, the CPE device re-establishes a channel with the corresponding controller through the main line, and synchronizes the data generated during the fault, without affecting the normal operation of the system.

[0023] Further, when a user accesses the first controller, the user accesses the first CPE device through the first main line and accesses the second CPE device through the node line and the second main line;

[0024] When the user accesses the second controller, the user accesses the second CPE device through the second main line, and accesses the first CPE device through the node line and the first main line.

[0025] In the above implementation process, the administrator initiates a management task through any controller node. The system can decide whether to execute it locally or require cross-node coordination based on the nature and strategy of the task, so that the entire network of devices can be managed through any controller.

[0026] Furthermore, if the first controller fails, the user can access the first CPE device through the second controller and the first backup line, and access the second CPE device through the second main line.

[0027] In the above implementation process, after the first controller fails, the first CPE device can still be accessed through the second controller and the first backup line, and the second CPE device can be accessed through the second main line, thereby avoiding network interruption caused by controller failure.

[0028] An embodiment of the present application further provides an electronic device, which includes a memory and a processor, wherein the memory is used to store a computer program, and the processor runs the computer program to enable the electronic device to execute a dual-master device management method.

[0029] An embodiment of the present application further provides a readable storage medium, wherein the readable storage medium stores computer program instructions, and when the computer program instructions are read and executed by a processor, the dual-master device management method is executed. BRIEF DESCRIPTION OF THE DRAWINGS

[0030] In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings required for use in the embodiments of the present application will be briefly introduced below. It should be understood that the following drawings only show certain embodiments of the present application and therefore should not be regarded as limiting the scope. For ordinary technicians in this field, other related drawings can be obtained based on these drawings without paying creative work.

[0031] Figure 1 A schematic diagram of the structure of a dual-master device management system provided in an embodiment of the present application;

[0032] Figure 2 A schematic diagram of line connections after a failure of controller A provided in an embodiment of the present application;

[0033] Figure 3 A flowchart of a dual-master device management method provided in an embodiment of the present application.

[0034] icon:

[0035] 100 - first controller, 200 - second controller; 300 - first CPE device; 400 - second CPE device. DETAILED DESCRIPTION

[0036] The technical solutions in the embodiments of the present application will be described below in conjunction with the drawings in the embodiments of the present application.

[0037] It should be noted that similar reference numerals and letters represent similar items in the following drawings, so once an item is defined in one drawing, it does not need to be further defined and explained in subsequent drawings. At the same time, in the description of this application, the terms "first", "second", etc. are only used to distinguish the description and cannot be understood as indicating or implying relative importance.

[0038] Example 1

[0039] Please see Figure 1 , Figure 1 A schematic diagram of the structure of a dual-master device management system provided in an embodiment of the present application, the system includes a first controller 100, a second controller 200, at least one first CPE (Customer Premise Equipment, a client device for accessing a network) device and at least one second CPE device 400, wherein:

[0040] The first controller 100 and the second controller 200 are connected via a node line to perform data synchronization and node communication between each other;

[0041] The first CPE device 300 has a first main line and a first backup line, and is connected to the first controller 100 through the first main line, and is connected to the second controller 200 through the first backup line;

[0042] The second CPE device 400 has a second main line and a second backup line, and is connected to the second controller 200 through the second main line, and is connected to the first controller 100 through the second backup line.

[0043] The present application provides a dual-master failover device management system for an SD-WAN (software-defined networking in a wide area network) controller, which can solve the network interruption problem caused by a single point failure in the SD-WAN network and improve the reliability and fault recovery capability of the entire network.

[0044] like Figure 1 As shown, the system adopts a dual-node controller deployment, that is, the system deploys two controllers, namely Controller A (first controller 100) and Controller B (second controller 200). Both controllers have complete network management capabilities. They are connected through node line E, and can perform data synchronization and node communication, so that all management data can be synchronized in real time between the two controllers through node line E. Cross-node communication and cross-node device management can also be achieved through node line E. For example, when the administrator accesses controller A, CPE device B is managed through node line E and the second main line D.

[0045] This application adopts a dual-master controller architecture. Even if one controller fails, the other controller can immediately take over its responsibilities to ensure the continuous operation of the network and the continuity of services. Compared with single-point control, the reliability of the network is improved.

[0046] The first backup line is used to disconnect the first main line and establish a connection with the second controller 200 if the first controller 100 fails;

[0047] The second backup line is used to disconnect the second main line and establish a connection with the first controller 100 if a failure occurs in the second controller 200 .

[0048] A node line, used to synchronize data generated during a fault from a first controller 100 that is not faulty to a second controller 200 that has recovered from the fault, or synchronize data generated during a fault from a second controller 200 that is not faulty to a first controller 100 that has recovered from the fault;

[0049] The user also initiates a management task to the first CPE device 300 through the first controller 100 , or initiates a management task to the second CPE device 400 through the first controller 100 , the node line and the second controller 200 .

[0050] Specifically, the CPE device supports primary and backup registration lines, the first primary line of CPE device A (first CPE device 300) is used to connect to controller A, and the first backup line is used to connect to controller B; the second primary line of CPE device B (second CPE device 400) is used to connect to controller B, and the second backup line is used to connect to controller A. Under normal circumstances, a management channel is established between CPE device A and controller A through the first primary line, and a management channel is established between CPE device B and controller B through the second primary line.

[0051] Figure 1 A represents the main line (first main line) of CPE device A, B represents the backup line (first backup line) of CPE device A, D represents the main line (second main line) of CPE device B, and C represents the backup line (second backup line) of CPE device B.

[0052] The administrator has the authority to manage CPE devices in the entire network. The administrator can manage CPE devices in the entire network by accessing any controller. For example, when the administrator accesses controller A, CPE device A is managed through the first main line A, and CPE device B is managed through node line E and the second main line D; when the administrator accesses controller B, CPE device B is managed through the second main line D, and CPE device A is managed through node line E and the first main line A.

[0053] Under normal working conditions, the CPE device will select the main line to register with the corresponding controller, that is, CPE device A registers with controller A through the first main line A, and CPE device B registers with controller B through the second main line D.

[0054] When one of the controllers fails, the CPE device connected to it will automatically switch to the backup line and manage the CPE device by accessing the controller corresponding to the backup line.

[0055] like Figure 2The figure shows a line connection diagram after a failure of controller A. When controller A fails, CPE device A detects that the first main line A is disconnected and cannot establish a connection with controller A. It will automatically switch to the first backup line B to establish a connection channel with controller B. The administrator can still manage the entire network CPE devices by accessing controller B, that is, use the first backup line B to manage CPE device A and use the second main line D to manage CPE device B.

[0056] After the failure of controller A is restored, CPE device A detects that controller A has returned to normal, disconnects from the first backup line B of the controller, and reestablishes a connection channel with controller A through the first main line A. At the same time, controller B will synchronize the data generated during the downtime to controller A through node line E, and resume normal management after controller A is restored.

[0057] The role of the node line includes two aspects. On the one hand, under normal working conditions, real-time data synchronization is performed through the node line to ensure the consistency of data between the two controllers, so that when the CPE device switches to another controller through the backup line, the controller can achieve seamless switching during fault transfer; on the other hand, after the fault is recovered, the data generated during the fault can be promptly transmitted to the controller after the fault is recovered, ensuring that the controller after the fault is recovered can manage the CPE device normally.

[0058] When the main controller fails, the system can quickly transfer the management rights of the CPE device to other controllers, reducing the impact of the failure on network services, thereby achieving rapid failover. At the same time, through load balancing and failover mechanisms, it ensures that the network can still maintain high availability in the face of various failure situations, thereby enhancing the high availability of the network.

[0059] This application can ensure the continuity and stability of network services and improve user experience.

[0060] Through automated fault detection and failover mechanisms, manual intervention is reduced, and the complexity and cost of network maintenance are lowered.

[0061] Example 2

[0062] The present application embodiment provides a dual-master device management method, which is applied to the dual-master device management system in Embodiment 1. Specifically:

[0063] This application adopts a dual-master controller architecture: by deploying two master controllers (Controller A and Controller B), both controllers have complete network management capabilities and can synchronize data and communications in real time. This mechanism ensures that when any controller fails, the other controller can seamlessly take over its responsibilities, thereby significantly improving the reliability and fault recovery capabilities of the network.

[0064] Intelligent node communication and cross-node device management: This application implements an intelligent node communication mechanism that allows administrators to initiate management tasks through any controller node. The system can decide whether to execute locally or require cross-node coordination based on the nature and strategy of the task. This mechanism allows the management of all network devices through any controller, greatly improving the flexibility and efficiency of network management. In addition, when the main line fails, the CPE device can automatically switch to the backup line and re-establish the management channel, further enhancing system availability.

[0065] like Figure 3 FIG. 1 is a flow chart of a dual-master device management method, the method comprising:

[0066] Step S100: If the first controller 100 fails, the first main line is disconnected, the first CPE device 300 automatically switches to the first backup line, and establishes a connection with the second controller 200 through the first backup line;

[0067] Step S200: If the second controller 200 fails, the second main line is disconnected, the second CPE device 400 automatically switches to the second backup line, and establishes a connection with the first controller 100 through the second backup line.

[0068] With fault detection and automatic switching functions: CPE equipment supports primary and backup registration lines. When the primary line fails, it automatically switches to the backup line and re-establishes the management channel through the backup line, ensuring the normal operation of the system and enhancing the high availability of the network.

[0069] By deploying dual-active controllers and adopting a failover mechanism, high availability of the controllers is achieved, reducing network interruption time caused by controller failures.

[0070] Rapid recovery after controller failure: The system can quickly enable backup lines, that is, quickly complete failover and network recovery after a failure occurs, improving network stability and reliability.

[0071] If the first CPE device 300 detects that the first controller 100 has returned to normal, it disconnects the first backup line and reestablishes a connection with the first controller 100 through the first main line. At the same time, the second controller 200 synchronizes the data generated during the fault to the first controller 100 through the node line.

[0072] If the second controller 200 returns to normal, the second CPE device 400 disconnects the second backup line and reconnects to the second controller 200 through the second main line. At the same time, the first controller 100 synchronizes the data generated during the failure to the second controller 200 through the node line.

[0073] Fault recovery: When the controller node recovers from a fault, it automatically re-establishes the channel and synchronizes the data generated during the fault from other nodes. Through automated fault detection and failover mechanisms, manual intervention is reduced, reducing the complexity and cost of network maintenance.

[0074] Node communication mechanism: The two controllers can achieve data synchronization and node communication through the node line, realizing seamless switching during failover and avoiding network configuration loss and inconsistency. Therefore, after the CPE device enables the backup line to connect to another fault-free controller, the fault-free controller can manage the CPE device normally through the backup line.

[0075] When a user accesses the first controller 100, the user accesses the first CPE device 300 through the first main line, and accesses the second CPE device 400 through the node line and the second main line;

[0076] When a user accesses the second controller 200, the user accesses the second CPE device 400 through the second main line, and accesses the first CPE device 300 through the node line and the first main line.

[0077] The setting of node lines enables administrators to have the authority to manage CPE devices in the entire network. Administrators can manage CPE devices in the entire network by accessing any controller. This application adopts a node communication mechanism. Administrators initiate management tasks through any controller node. The system can decide whether to execute locally or require cross-node coordination based on the nature and strategy of the task, and can realize the function of managing CPE devices in the entire network through any controller.

[0078] If the first controller 100 fails, the user can access the first CPE device 300 through the second controller 200 and the first backup line, and access the second CPE device 400 through the second main line.

[0079] The present application sets up a dual-main controller architecture. When one of the controllers fails, the CPE device can connect to the other controller through a backup line, thereby ensuring the continuous operation of the network and the continuity of services, improving the user experience, achieving rapid failover, and improving the reliability of the network. It has strong high availability and solves the problem of service interruption caused by single point failure in existing methods.

[0080] An embodiment of the present application also provides an electronic device, which includes a memory and a processor, wherein the memory is used to store a computer program, and the processor runs the computer program to enable the electronic device to execute the dual-master device management method described in Example 2.

[0081] An embodiment of the present application further provides a readable storage medium, wherein the readable storage medium stores computer program instructions. When the computer program instructions are read and executed by a processor, the dual-master device management method described in Embodiment 2 is executed.

[0082] In several embodiments provided in the present application, it should be understood that the disclosed devices and methods can also be implemented in other ways. The device embodiments described above are merely schematic. For example, the flowcharts and block diagrams in the accompanying drawings show the possible architecture, functions and operations of the devices, methods and computer program products according to multiple embodiments of the present application. In this regard, each box in the flowchart or block diagram can represent a module, a program segment or a part of a code, and the module, a program segment or a part of a code contains one or more executable instructions for implementing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the box can also occur in a different order from the order marked in the accompanying drawings. For example, two consecutive boxes can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each box in the block diagram and / or flowchart, and the combination of boxes in the block diagram and / or flowchart can be implemented with a dedicated hardware-based system that performs a specified function or action, or can be implemented with a combination of dedicated hardware and computer instructions.

[0083] In addition, the functional modules in the various embodiments of the present application may be integrated together to form an independent part, or each module may exist separately, or two or more modules may be integrated to form an independent part.

[0084] If the functions are implemented in the form of software function modules 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 the present application can be essentially or partly embodied in the form of a software product that contributes to the prior art. The computer software product is stored in a storage medium, including several instructions to enable a computer device (which can be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the methods described in each embodiment of the present application. The aforementioned storage medium includes: various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.

[0085] The above description is only an embodiment of the present application and is not intended to limit the scope of protection of the present application. For those skilled in the art, the present application may have various changes and variations. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of the present application should be included in the scope of protection of the present application. It should be noted that similar reference numerals and letters represent similar items in the following drawings, so once an item is defined in one drawing, it does not need to be further defined and explained in the subsequent drawings.

[0086] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any technician familiar with the technical field can easily think of changes or substitutions within the technical scope disclosed in the present application, which should be included in the protection scope of the present application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.

[0087] It should be noted that, in this article, relational terms such as first and second, etc. are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Moreover, the terms "include", "comprise" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, the elements defined by the sentence "comprise a ..." do not exclude the existence of other identical elements in the process, method, article or device including the elements.

Claims

1. A dual-master device management system, characterized in that: The system comprises a first controller, a second controller, at least one first CPE device and at least one second CPE device, wherein: The first controller and the second controller are connected via a node line to perform data synchronization and node communication between each other; The first CPE device has a first main line and a first backup line, is connected to the first controller through the first main line, and is connected to the second controller through the first backup line; The second CPE device has a second main line and a second backup line, and is connected to the second controller via the second main line, and is connected to the first controller via the second backup line.

2. The dual-master device management system according to claim 1, characterized in that: The first backup line is used to disconnect the first main line and establish a connection with the second controller if the first controller fails; The second backup line is used to disconnect the second main line and establish a connection with the first controller if the second controller fails.

3. The dual-master device management system according to claim 1, characterized in that: A node line, used to synchronize data generated during a fault from a first controller that is not at fault to a second controller after fault recovery, or synchronize data generated during a fault from a second controller that is not at fault to the first controller after fault recovery; The user also initiates a management task to the first CPE device through the first controller, or initiates a management task to the second CPE device through the first controller, the node line and the second controller.

4. A dual-master device management method, characterized in that: Applied to the dual-master device management system according to any one of claims 1 to 3, the method comprising: If the first controller fails, the first main line is disconnected, the first CPE device automatically switches to the first backup line, and establishes a connection with the second controller through the first backup line; If the second controller fails, the second main line is disconnected, the second CPE device automatically switches to the second backup line, and establishes a connection with the first controller through the second backup line.

5. The dual-master device management method according to claim 4, characterized in that ； If the first CPE device detects that the first controller has returned to normal, it disconnects the first backup line and reconnects with the first controller through the first main line. At the same time, the second controller synchronizes the data generated during the failure to the first controller through the node line.

6. The dual-master device management method according to claim 4, characterized in that: If the second controller recovers, the second CPE device disconnects the second backup line and reconnects to the second controller through the second main line. Meanwhile, the first controller synchronizes the data generated during the failure to the second controller through the node line.

7. The dual-master device management method according to claim 4, characterized in that: When a user accesses the first controller, the user accesses the first CPE device through the first main line and accesses the second CPE device through the node line and the second main line; When the user accesses the second controller, the user accesses the second CPE device through the second main line, and accesses the first CPE device through the node line and the first main line.

8. The dual-master device management method according to claim 4, characterized in that: If the first controller fails, the user can access the first CPE device through the second controller and the first backup line, and access the second CPE device through the second main line.

9. An electronic device, characterized in that: The electronic device comprises a memory and a processor, the memory is used to store a computer program, and the processor runs the computer program to enable the electronic device to execute the dual-master device management method according to any one of claims 4 to 8.

10. A readable storage medium, characterized in that: The readable storage medium stores computer program instructions, and when the computer program instructions are read and executed by a processor, the dual-master device management method according to any one of claims 4 to 8 is executed.

Images