Dual-computer hot standby method and device in SDWAN, IPRAN or RTN

Abstract

The invention provides a dual-computer hot standby method and device in an SDWAN, an IPRAN or an RTN. A management and control platform creates a protection group; in response to an equipment state notification sent when the first core node is used as the main equipment, recording the equipment state of the first core node in the protection group as a main equipment state, and recording the equipment state of the second core node as a standby equipment state; in response to the service created by the user based on the selected service type, the protection group and the CPE, determining that the core node with the device state being the main device state in the current protection group is the first core node; and creating service configuration information corresponding to the service according to the service type, and respectively issuing the service configuration information to the first core node and the CPE to realize transmission of the service between the first core node and the CPE. According to the scheme, on the premise that the implementation complexity is reduced and the service issuing efficiency is improved, dual-computer hot standby in the SDWAN, the IPRAN or the RTN can be realized.

Description

Technical Field

[0001] The embodiments of the present disclosure relate to the field of communication technology, and in particular to a dual-machine hot standby method and device in SDWAN, IPRAN or RTN. Background Art

[0002] In modern communication networks, as business demands continue to grow, network reliability and high availability have become critical. Software-defined wide area networks (SDWAN), IP bearer networks (IPRAN), and packet transport networks (PTN), as new generation network architectures, are widely used in enterprise and operator networks to provide efficient business transmission and management.

[0003] However, in the current network, there is often only one core node that undertakes critical tasks. Any abnormal status of the core network equipment will lead to interruption of the entire network's business and services, causing unacceptable business impact and losses to users.

[0004] Traditional dual-machine hot standby solutions mostly rely on hardware redundancy or complex high-availability configurations. When issuing services through the management and control platform, it is necessary to identify the primary device first and then issue it. In situations such as device switching, the primary device needs to be identified in a timely manner. This implementation method is not only complex, but also inefficient in issuing services. Summary of the invention

[0005] In view of this, the present application provides a dual-machine hot standby method and device method, device, electronic device and storage medium in SDWAN, IPRAN or RTN, which can realize dual-machine hot standby in SDWAN, IPRAN or RTN while reducing implementation complexity and improving service delivery efficiency.

[0006] To solve the above technical problems, the technical solution of this application is implemented as follows: In one embodiment, a dual-machine hot standby method in SDWAN, IPRAN or RTN is provided, where a management and control platform creates a protection group, where the protection group includes a first core node and a second core node; the method includes: In response to a device status notification sent when the first core node serves as a master device, recording the device status of the first core node in the protection group as a master device status, and recording the device status of the second core node as a standby device status; In response to a service created by a user based on a selected service type, a protection group, and a CPE, determining a core node whose device state in the current protection group is a master device state as a first core node; Based on the service type, service configuration information corresponding to the service is generated, and the service configuration information is sent to the first core node and the CPE respectively to realize transmission of the service between the first core node and the CPE.

[0007] Wherein, the method further comprises: In response to a user input for switching the master device in the protection group, updating the device state of the first core node in the protection group to a standby device state, and updating the device state of the second core node to a master device state; The first core node is notified to switch the device state, so that the first core node pushes the configuration information to the backup device and switches to the backup device, and the second core node switches to the main device.

[0008] Wherein, the method further comprises: In response to a command to replace the protection group, obtaining service configuration information of the corresponding protection group in the platform database according to the first protection group identifier carried in the command; Sending the acquired service configuration information to the protection group corresponding to the second protection group identifier carried in the command to realize fast switching of the protection group corresponding to the service; The first protection group identifier is the protection group identifier of the protection group to be replaced; and the second protection group identifier is the protection group identifier of the protection group to be replaced.

[0009] Wherein, the method further comprises: In response to a device status notification sent by the second core node when the first core node abnormally switches to a master device, the device status of the first core node in the protection group is updated to a backup device status, and the device status of the second core node is updated to a master device status.

[0010] The configuration information of the first core node and the second core node is configured through a web interface; the configuration information includes: a heartbeat interface, a virtual IP, a health monitoring option, and an initial state; the heartbeat interface, the virtual IP, and the health monitoring option are the same on the first core node and the second core node; the initial state of the first core node is a master device state, and the initial state of the second core node is a standby device state; The heartbeat interface is used for communicating between the first core node and the second core node through a heartbeat line to determine whether the opposite core node is in an abnormal state; The virtual IP is used for the core node to communicate with the CPE when it acts as a master device; The health monitoring option is used to perform health monitoring when the core node is used as a master device; if the monitoring result does not meet the preset conditions, the device status is determined to be abnormal, and no heartbeat message is sent to the core node used as a backup device.

[0011] The health monitoring options include any one or any combination of the following: Ping detection, HTTP service detection, interface status monitoring, network connectivity, link quality detection, CPU usage, and memory usage.

[0012] in, If the interface of the first core node and the second core node used for service communication with the CPE is not the same as the interface for communication with the control platform, respectively configure virtual IPs for different interfaces; If the first core node and the second core node use different interfaces for communicating with different servers, virtual IPs are configured for different interfaces respectively.

[0013] In another embodiment, a dual-machine hot standby device in SDWAN, IPRAN or RTN is provided, the device comprising: A configuration unit, configured to create a protection group, wherein the protection group includes a first core node and a second core node; A processing unit, configured to, in response to a device status notification sent when the first core node acts as a master device, record the device status of the first core node in the protection group as a master device status, and record the device status of the second core node as a standby device status; A determining unit, configured to determine, in response to a service type, a protection group, and a service created by a CPE selected by a user, a core node whose device state in the current protection group is a master device state as a first core node; A generating unit, configured to generate service configuration information corresponding to the service based on the service type; The sending unit is used to send the service configuration information to the first core node and the CPE respectively to realize the transmission of the service between the first core node and the CPE.

[0014] In another embodiment, an electronic device is provided, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements a dual-machine hot standby method in SDWAN, IPRAN, or RTN when executing the program.

[0015] In another embodiment, a computer-readable storage medium is provided, on which a computer program is stored, and when the program is executed by a processor, a dual-machine hot standby method in SDWAN, IPRAN or RTN is implemented.

[0016] As can be seen from the above technical solution, in the above embodiment, a protection group is created on the control platform, and the protection group includes two core nodes; the status of the core nodes in the protection group is updated to indicate the main device working in the current network; when the user creates a task on the control platform, the corresponding protection group can be directly selected, and there is no need to determine who is the main device in the current dual-machine hot standby. The control platform sends service configuration information to the main device according to the core node in the protection group that is in the main device state to realize the service transmission. This solution can realize dual-machine hot standby in SDWAN, IPRAN or RTN under the premise of reducing the implementation complexity and improving the efficiency of service delivery. BRIEF DESCRIPTION OF THE DRAWINGS

[0017] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings required for use in the description of the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without creative work.

[0018] Figure 1 A schematic diagram of a service transmission system with a single core node in the prior art; Figure 2 This is a schematic diagram of a dual-machine hot standby service transmission system in an embodiment of the present application; Figure 3 This is a schematic diagram of a dual-machine hot standby process in an embodiment of the present application; Figure 4 This is another schematic diagram of a dual-machine hot standby process in an embodiment of the present application; Figure 5 This is a schematic diagram of the process of actively updating the main device in an embodiment of the present application; Figure 6 This is a schematic diagram of the process of replacing a protection group in an embodiment of the present application; Figure 7 This is a schematic diagram of the structure of a dual-machine hot standby device in SDWAN, IPRAN or RTN in an embodiment of the present application; Figure 8 A schematic diagram of the physical structure of an electronic device provided by an embodiment of the present invention. DETAILED DESCRIPTION

[0019] The following will be combined with the drawings in the embodiments of the present application to clearly and completely describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.

[0020] The terms "first", "second", "third", "fourth", etc. (if any) in the specification and claims of the present invention and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe the order or precedence of the objects. It should be understood that the data used in this way can be interchanged where appropriate, so that the implementation of the present invention described herein can be implemented in an order other than those illustrated or described herein. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions. For example, a process, method, system, product or device that includes a series of steps or units is not necessarily limited to those steps or units that are clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0021] The technical solution of the present invention is described in detail with specific embodiments below. The following specific embodiments can be combined with each other, and the same or similar concepts or processes may not be described in detail in some embodiments.

[0022] Traditional dual-machine hot standby solutions mostly rely on hardware redundancy or complex high-availability configurations. When issuing services through the management and control platform, the primary device must be identified first and then issued. In situations such as device switching, the primary device must be identified in a timely manner. This implementation method is not only complex but also costly.

[0023] Based on the above problems, a dual-machine hot standby method in SDWAN, IPRAN or RTN is provided in an embodiment of the present application, which is applied to SDWAN, IPRAN or RTN, by creating a protection group on the management and control platform, which includes two core nodes; by updating the status of the core nodes in the protection group to indicate the main device working in the current network; when the user creates a task on the management and control platform, he can directly select the corresponding protection group, without determining who is the main device in the current dual-machine hot standby. The management and control platform sends service configuration information to the main device according to the core node in the protection group that is in the main device state to realize the service transmission. This solution can realize dual-machine hot standby in SDWAN, IPRAN or RTN under the premise of reducing the implementation complexity and improving the efficiency of service delivery.

[0024] In the embodiment of the present application, before implementing dual-machine hot standby, the relevant configuration implementation of dual-machine hot standby is given.

[0025] See also Figure 1 , Figure 1 The diagram is a schematic diagram of a single core node service transmission system in the prior art. The entire service transmission system includes a management and control platform and a core node. The core node corresponds to a SW, which can correspond to one or more CPEs. Figure 1In the example, one CPE is used. When the management platform has corresponding services, it can be directly sent to the corresponding core node and CPE for service transmission. If the core node is abnormal, the service transmission cannot be performed normally.

[0026] The implementation of dual-machine hot standby in the embodiment of the present application is to add a core node in the service transmission system. Figure 2 , Figure 2 This is a schematic diagram of a dual-machine hot standby service transmission system in an embodiment of the present application. Figure 1 A core node is added to the business transmission system in the system. After the core node is added, the business transmission system includes a management and control platform and two core nodes (the first core node and the second core node). The two core nodes correspond to one SW and one CPE.

[0027] Figure 2 In the example, the first core node and the second core node correspond to one CPE. In actual applications, the core node can carry many services, and each service requires a CPE. Therefore, the core node will correspond to multiple CPEs.

[0028] The management and control platform creates a protection group, connects the two core nodes to the management and control platform, and adds the two core nodes to the protection group; the protection group includes the first core node and the second core node; an initial device state is set for each core node, and the initial device state can be empty or in the standby device state.

[0029] You also need to configure configuration information on the two core nodes. The configuration information can be configured through the web interface of the core node. The specific configuration information is as follows: Heartbeat interface: The heartbeat interface is used for communication between the first core node and the second core node through the heartbeat line to determine whether the peer core node is in an abnormal state; If the first core node does not receive the heartbeat message sent by the second core node within the preset time, the second core node is confirmed to be abnormal. The abnormal state here includes the situation that some indicators do not meet the preset values, and also includes the situation of equipment failure, that is, the situation that the heartbeat message is not sent to the opposite core node.

[0030] Virtual IP: used for core node to communicate with CPE when it is the master device; The configured core nodes can be one or more: If the interface used by the first core node and the second core node to communicate with the CPE for service communication is not the same as the interface used to communicate with the management and control platform, virtual IPs are configured for different interfaces respectively; If the first core node and the second core node use different interfaces for communicating with different servers, virtual IPs are configured for different interfaces respectively.

[0031] That is, the core node needs several interfaces to communicate with the management and control platform, CPE, and server, so several virtual IPs are configured.

[0032] The traditional dual-machine hot standby method only supports the use and management of a single virtual IP. The implementation method of the embodiment of the present application supports the use and management of multiple virtual IPs, allowing users to manage multiple services in the same dual-machine hot standby configuration.

[0033] Health monitoring option: used for health monitoring when the core node is used as the master device; if the monitoring result does not meet the preset conditions, the device status is determined to be abnormal and no heartbeat message is sent to the core node used as the backup device.

[0034] The core node as the backup device monitors the heartbeat message sent by the core node as the master device all the time, and determines that the device status of the core node as the master device is abnormal when the heartbeat message sent by the core node as the master device cannot be received within a preset time.

[0035] When a core node device serving as a master device fails, the heartbeat message cannot be sent directly. In the embodiment of the present application, the device failure is regarded as a situation in a broad sense of device status abnormality.

[0036] Among them, the health monitoring options include any one or any combination of the following, and are not limited to the following examples: Ping detection, HTTP service detection, interface status monitoring, network connectivity, link quality detection, CPU usage, and memory usage.

[0037] Initial state: one of the core nodes is set to the master device state, and the other core node device is set to the backup device state; the specific backup device state and master device state can be set by the implementer according to the actual situation without restriction.

[0038] Among them, the heartbeat interface, virtual IP and health monitoring options are the same on the first core node and the second core node; the initial states of the two core nodes are different: the initial state of the first core node is the master device state, and the initial state of the second core node is the backup device state; the first and second here are for the convenience of description, and are not two different categories of devices.

[0039] The following is a detailed description of the hot standby process of dual machines in SDWAN, IPRAN or RTN in the embodiment of the present application in conjunction with the accompanying drawings. The implementation process in SDWAN, IPRAN or RTN is the same, and the embodiments of the present application will not be described in detail separately, and a general implementation method is given.

[0040] See also Figure 3 , Figure 3This is a schematic diagram of a dual-machine hot standby process in an embodiment of the present application. The specific steps are: Step 301 , in response to a device status notification sent by the first core node as a master device, the device status of the first core node in the protection group is recorded as a master device status, and the device status of the second core node is recorded as a standby device status.

[0041] In this embodiment, taking the initial startup of the device as an example, after the first core node and the second core node are started, according to the configuration information, after the first core node runs as the main device, it will send a device status notification to the management and control platform; after the second core node runs as the backup device, it does not need to send a device status notification to the management and control platform.

[0042] When the management and control platform receives the device status notification, it determines the protection group corresponding to the first core node that sends the device status notification; records the device status of the first core node in the protection group as the main device status, and records the device status of the second core node as the backup device status.

[0043] If the initial device states of the first core node and the second core node are used, the device state of the first core node is updated to the main device state, and the device state of the second core node remains unchanged. This embodiment takes the implementation method in which the initial device state is empty as an example.

[0044] Step 302: In response to a service type, a protection group and a service created by a user based on the selected CPE, a core node in the protection group whose device state is currently a master device state is determined as a first core node.

[0045] When a user wants to create a service, he / she selects the service type, corresponding protection group and CPE on the management and control platform. The management and control platform determines the core node in the master device state in the protection group according to the selected protection group. If the management and control platform manages multiple protection groups, it is necessary to find the corresponding protection group according to the protection group identifier of the protection group selected by the user, and then determine the core node in the protection group that is in the master device state; in the specific implementation, the master device state can be used to identify the role of a core node as a master device, and the state is online; a core node can also be identified by two parameters: role and state. This is not restricted in the embodiments of the present application, and is identified by the master device state and the backup device state.

[0046] Step 303: Generate service configuration information corresponding to the service based on the service type, and send the service configuration information to the first core node and the CPE respectively to realize transmission of the service between the first core node and the CPE.

[0047] The management and control platform generates service configuration information based on the device ID of the core node as the main device in the protection group, the ID of the corresponding CPE, and the service type that the user wants to send. Taking the "vxlan over wireguard" Layer 2 encryption service as an example, when the user creates a service, he selects the service type as "vxlan over wireguard" on the management and control platform. The management and control platform generates vxlan and wireguard configuration items for CPE and core nodes based on the device ID of the core node as the main device, the ID of CPE, and the service type, such as vxlan id, wireguarg key, and other service configurations, and sends these configuration items to the core node as the main device and the corresponding CPE.

[0048] Between the CPE and the core node in the master device state, device communication is carried out through the virtual IP to realize service transmission.

[0049] In this embodiment, a protection group is created on the management and control platform, and the protection group includes two core nodes; the status of the core nodes in the protection group is updated to indicate the main device working in the current network; when the user creates a task on the management and control platform, the corresponding protection group can be directly selected without determining who is the main device in the current dual-machine hot standby. The management and control platform sends service configuration information to the main device based on the core node in the protection group that is in the main device state to realize the service transmission. This solution can realize dual-machine hot standby in SDWAN, IPRAN or RTN under the premise of reducing the implementation complexity and improving the efficiency of service delivery.

[0050] See also Figure 4 , Figure 4 This is another schematic diagram of a dual-machine hot standby process in an embodiment of the present application. The specific steps are: Step 401, in response to a device status notification sent by the second core node when the first core node abnormally switches to a master device, the device status of the first core node in the protection group is updated to a standby device status, and the device status of the second core node is updated to a master device status.

[0051] The first core node and the second core node run the Keepalived service and interact through the VRRP protocol to determine the master and backup roles.

[0052] The first core node and the second core node exchange heartbeat messages. If the first core node and the second core node do not receive the heartbeat message sent by the opposite core node within a preset time, it is determined that the status of the opposite core node is abnormal.

[0053] In an embodiment of the present application, each core node is monitored according to the configured health monitoring options. If there are multiple configured monitoring items and any one of them does not meet the preset conditions, the state of the core node is determined to be abnormal. When the state of the core node is determined to be abnormal, a heartbeat message is not sent to the core node serving as a backup device.

[0054] The abnormal device status referred to in the embodiments of the present application is a broad term, which also includes device failure. The core node of the main device directly does not send a heartbeat message, so the core node of the backup device will not receive the heartbeat message.

[0055] Among them, the health monitoring options include any one or any combination of the following, and are not limited to the following examples: When a master-slave switch occurs, the new master device takes over the virtual IP and communicates with the CPE, management and control platform and other networks through the virtual IP. Then, the business and management configurations are gradually put into effect to achieve automated business recovery. The business always runs between the CPE and the core node of the master role.

[0056] Step 402: In response to a service created by a user based on a service type, a protection group, and a CPE selected by the user, a core node whose device state in the current protection group is a master device state is determined as a second core node.

[0057] When a user wants to create a service, he / she selects the service type, corresponding protection group and CPE on the management and control platform. The management and control platform determines the core node in the master device state in the protection group according to the selected protection group. If the management and control platform manages multiple protection groups, it is necessary to find the corresponding protection group according to the protection group identifier of the protection group selected by the user, and then determine the core node in the protection group that is in the master device state; in the specific implementation, the master device state can be used to identify the role of a core node as a master device, and the state is online; a core node can also be identified by two parameters: role and state. This is not restricted in the embodiments of the present application, and is identified by the master device state and the backup device state.

[0058] Step 403: Generate service configuration information corresponding to the service based on the service type, and send the service configuration information to the second core node and the CPE respectively to realize transmission of the service between the second core node and the CPE.

[0059] Between the CPE and the core node in the master device state, device communication is carried out through the virtual IP to realize service transmission.

[0060] In this embodiment, a protection group is created on the management and control platform, and the protection group includes two core nodes; the status of the core nodes in the protection group is updated to indicate the main device working in the current network; when the user creates a task on the management and control platform, the corresponding protection group can be directly selected without determining who is the main device in the current dual-machine hot standby. The management and control platform sends service configuration information to the main device based on the core node in the protection group that is in the main device state to realize the service transmission. This solution can realize dual-machine hot standby in SDWAN, IPRAN or RTN under the premise of reducing the implementation complexity and improving the efficiency of service delivery.

[0061] Regardless of whether the core node initially serves as the master device or is subsequently switched to the master device, when it becomes the new master device, it will automatically send a device status notification to the management and control platform to inform the platform of the status changes of the devices in the protection group.

[0062] After receiving the device status notification, the management and control platform will synchronize the status information of the core nodes in the protection group to ensure the accuracy of business monitoring and management; and it can be displayed in the alarm bar, so that users can promptly understand the current main device, perceive anomalies, troubleshoot, etc.

[0063] See also Figure 5 , Figure 5 This is a schematic diagram of the process of actively updating the master device in the embodiment of this application. The specific steps are: Step 501, in response to a user input to switch a master device in a protection group, the device state of the first core node in the protection group is updated to a standby device state, and the device state of the second core node is updated to a master device state.

[0064] Step 502, notifying the first core node to switch the device state, so that the first core node pushes the configuration information to the backup device and switches to the backup device, and the second core node switches to the main device.

[0065] In this embodiment, when the first core node switches the device state, in order to avoid the configuration information of the first core node and the second core node being out of sync at this time, the configuration information needs to be synchronized once.

[0066] In this embodiment, the management and control platform supports users to manually switch between the primary and standby devices. The user logs in to the main control platform, finds the corresponding protection group, checks whether the current status of the primary and standby devices is what is currently needed, and switches by clicking the "manual switch" button displayed on the page. The management and control platform sends a manual switching instruction to the first core node in the primary device state; after receiving the manual switching instruction, the first core node actively pushes the configuration information to the standby device, and then lowers its own status, and the original standby device is promoted to the primary. This embodiment can realize one-click switching of primary and standby devices through the management and control platform according to actual needs, can flexibly meet user needs, and improve user experience.

[0067] The management and control platform also supports the replacement of protection groups. When the equipment in the entire protection group needs to be replaced, since the protection group is responsible for the business, if the user needs to delete the business one by one and then create the business on the new protection group, it will be a time-consuming and labor-intensive workload for the user, and the business interruption time will be too long. The management and control platform has added a new protection group replacement function. The user only needs to select the protection group to be replaced and the replaced protection group to achieve one-click replacement. The management and control platform identifies the protection group IDs of the two protection groups, retrieves the business configuration information in the management and control platform database according to the protection group ID, and sends the business configuration information to the new protection group to achieve rapid switching of services.

[0068] See also Figure 6 , Figure 6 This is a flow chart of replacing a protection group in an embodiment of the present application. The specific steps are: Step 601: In response to a command to replace a protection group, obtain service configuration information of a corresponding protection group in a platform database according to a first protection group identifier carried in the command.

[0069] The business configuration information on the management and control platform includes relevant business configuration information for the business issued to each protection group.

[0070] Step 602, the acquired service configuration information is sent to the protection group corresponding to the second protection group identifier carried in the command to realize rapid switching of the protection group corresponding to the service; wherein, the first protection group identifier is the protection group identifier of the protection group to be replaced; the second protection group identifier is the protection group identifier of the protection group to be replaced.

[0071] In specific implementation, when modifying the configuration information on the core node, only the configuration information of the core node in the master device state is directly modified, such as directly updating the configuration information through the web page of the core node in the master device state, or sending the configuration information to the core node currently in the master device state through the management and control platform; this is when the new configuration information on the core node in the master device state takes effect, it needs to be synchronized with the core node in the backup device state, so that the backup device can obtain the latest configuration information in time when it switches to the master device.

[0072] In the embodiment of the present application, two core nodes are taken as an example. In actual applications, multiple core nodes can also be used for master-slave implementation. In this case, it is necessary to configure a priority for each core node, and the configuration adopts a non-preemptive switching mechanism to ensure that after the master-slave switching, even if the master device is restored, the backup device still maintains the master state to prevent frequent switching.

[0073] For example, the protection group includes a first core node, a second core node, and a third core node; and the priority of the first core node is greater than the priority of the third core node, and the priority of the third core node is greater than the priority of the second core node.

[0074] If the current first core node is the master device, then the second core node and the third core node are both backup devices. When the first core node is in an abnormal state, the second core node and the third core node compete for the master device through priority. Since the priority of the third core node is greater than that of the second core node, the third core node eventually switches its role as the master device. If the status of the first core node subsequently returns to normal, the first core node does not switch to the primary device because the non-preemptive switching mode is adopted.

[0075] In the embodiment of the present application, the automatic notification mechanism is used to simplify configuration and management. Through the centralized management of the control platform, the hot standby parameters of the dual-machine are configured in combination with the device Web interface. The use of the protection group in the platform makes it unnecessary to pay attention to which device is the main device when configuring the service. The service only needs to be sent to the protection group. This realizes the rapid deployment of equipment management, hot standby and services, greatly reducing the complexity of implementation. The real-time synchronization mechanism of the configuration of the devices in the protection group ensures the consistency and continuity of the service configuration after the active / standby switchover in any situation. It also integrates multiple health detection and non-preemptive switching strategies to avoid frequent device switching and ensure business stability. It uses the status monitoring of devices in the protection group to ensure that when the main device fails, the backup device elects a new main device and quickly takes over the virtual IP to achieve rapid business recovery. When the active / standby switch occurs, the management and control platform is notified in time, so that the management personnel can grasp the equipment status in time and respond quickly, realizing real-time monitoring and visualization.

[0076] Based on the same inventive concept, the present application also provides a dual-machine hot standby device in SDWAN, IPRAN or RTN. Figure 7 , Figure 7 This is a schematic diagram of the structure of a dual-machine hot standby device in SDWAN, IPRAN or RTN in an embodiment of the present application. The device includes: A configuration unit 701 is used to create a protection group, where the protection group includes a first core node and a second core node; A processing unit 702 is configured to record the device status of the first core node in the protection group as the master device status and the device status of the second core node as the backup device status in response to the device status notification sent when the first core node serves as the master device; A determining unit 703 is configured to determine, in response to a service type, a protection group, and a service created by a CPE selected by a user, a core node whose device state is a master device state in the current protection group as a first core node; A generating unit 704, configured to generate service configuration information corresponding to the service based on the service type; The sending unit 705 is used to send service configuration information to the first core node and the CPE respectively to realize the transmission of the service between the first core node and the CPE.

[0077] In another embodiment, The processing unit 702 is further configured to update the device state of the first core node in the protection group to the standby device state and the device state of the second core node to the master device state in response to the user input for switching the master device in the protection group; The issuing unit 705 is further used to notify the first core node to switch the device state, so that the first core node pushes the configuration information to the backup device and switches to the backup device, and the second core node switches to the main device.

[0078] In another embodiment, Processing unit 702 is further used to respond to a command to replace the protection group, obtain business configuration information of the corresponding protection group in the platform database according to the first protection group identifier carried in the command; send the obtained business configuration information to the protection group corresponding to the second protection group identifier carried in the command to realize rapid switching of the protection group corresponding to the business; wherein the first protection group identifier is the protection group identifier of the protection group to be replaced; and the second protection group identifier is the protection group identifier of the protection group to be replaced.

[0079] In another embodiment, The processing unit 702 is further used to update the device status of the first core node in the protection group to a backup device status and the device status of the second core node to a master device status in response to a device status notification sent by the second core node when the first core node abnormally switches to a master device.

[0080] In another embodiment, configuration information of the first core node and the second core node is configured through a web interface; the configuration information includes: a heartbeat interface, a virtual IP, a health monitoring option, and an initial state; wherein the heartbeat interface, the virtual IP, and the health monitoring option are the same on the first core node and the second core node; the initial state of the first core node is a master device state, and the initial state of the second core node is a standby device state; The heartbeat interface is used for communication between the first core node and the second core node through the heartbeat line to determine whether the opposite core node is in an abnormal state; The virtual IP is used to communicate with the CPE when the core node acts as the master device; The health monitoring option is used to perform health monitoring when the core node is used as the master device; if the monitoring result does not meet the preset conditions, the device status is determined to be abnormal and no heartbeat message is sent to the core node used as the backup device.

[0081] In another embodiment, the health monitoring options include any one or any combination of the following: Ping detection, HTTP service detection, interface status monitoring, network connectivity, link quality detection, CPU usage, and memory usage.

[0082] In another embodiment, If the interface used by the first core node and the second core node to communicate with the CPE for service communication is not the same as the interface used to communicate with the management and control platform, virtual IPs are configured for different interfaces respectively; If the first core node and the second core node use different interfaces for communicating with different servers, virtual IPs are configured for different interfaces respectively.

[0083] In another embodiment, an electronic device is also provided, including a memory, a processor, and a computer program stored in the memory and executable on the processor, and when the processor executes the program, a dual-machine hot standby method in SDWAN, IPRAN, or RTN is implemented.

[0084] In another embodiment, a computer-readable storage medium is provided, on which computer instructions are stored. When the instructions are executed by a processor, a dual-machine hot standby method in SDWAN, IPRAN or RTN is implemented.

[0085] Figure 8 Schematic diagram of the physical structure of an electronic device provided by an embodiment of the present invention. Figure 8 As shown, the electronic device may include: a processor (Processor) 810, a communication interface (Communications Interface) 820, a memory (Memory) 830 and a communication bus 840, wherein the processor 810, the communication interface 820, and the memory 830 communicate with each other through the communication bus 840. The processor 810 may call the logic instructions in the memory 830 to execute the following method: The management and control platform creates a protection group, which includes the first core node and the second core node; In response to a device status notification sent when the first core node serves as a master device, the device status of the first core node in the protection group is recorded as a master device status, and the device status of the second core node is recorded as a standby device status; In response to a service created by a user based on a selected service type, a protection group, and a CPE, determining a core node in a current protection group whose device state is a master device state as a first core node; The service configuration information corresponding to the service is generated based on the service type, and the service configuration information is respectively issued to the first core node and the CPE to realize the transmission of the service between the first core node and the CPE.

[0086] In addition, the logic instructions in the above-mentioned memory 830 can be implemented in the form of a software functional unit and can be stored in a computer-readable storage medium when it is sold or used as an independent product. Based on this understanding, the technical solution of the present invention 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 of various embodiments of the present invention. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), disk or optical disk, etc. Various media that can store program codes.

[0087] The device embodiments described above are merely illustrative, wherein the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they may be located in one place, or they may be distributed on multiple network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the scheme of this embodiment. Ordinary technicians in this field can understand and implement it without paying creative labor.

[0088] Through the description of the above implementation methods, those skilled in the art can clearly understand that each implementation method can be implemented by means of software plus a necessary general hardware platform, and of course, can also be implemented by hardware. Based on this understanding, the above technical solution is essentially or the part that contributes to the prior art can be embodied in the form of a software product, and the computer software product can be stored in a computer-readable storage medium, such as ROM / RAM, a disk, an optical disk, etc., including a number of instructions for a computer device (which can be a personal computer, a server, or a network device, etc.) to execute the methods described in each embodiment or some parts of the embodiments.

[0089] The flow chart and block diagram in the accompanying drawings of the present application show the possible architecture, function and operation of the system, method and computer program product according to the various embodiments disclosed in the present application. In this regard, each box in the flow chart or block diagram can represent a module, a program segment or a part of a code, and the above-mentioned module, program segment or a part of a code contains one or more executable instructions for realizing the specified logical function. It should also be noted that in some implementations as replacements, the functions marked in the box can also occur in the order of the standards in different figures. For example, the boxes represented by two connections 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 or flow chart, and the combination of the boxes in the block diagram or flow chart can be implemented with a dedicated hardware-based system that performs the specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions.

[0090] Those skilled in the art will appreciate that the features described in the various embodiments and / or claims disclosed in this application may be combined and / or combined in a variety of ways, even if such combinations and / or combinations are not explicitly described in this application. In particular, without departing from the spirit and teachings of this application, the features described in the various embodiments and / or claims of this application may be combined and / or combined in a variety of ways, and all of these combinations and / or combinations fall within the scope disclosed in this application.

[0091] Specific embodiments are used herein to illustrate the principles and implementation methods of the present invention. The description of the above embodiments is only used to help understand the method of the present invention and its core ideas, and is not used to limit the present application. For those skilled in the art, changes can be made in the specific implementation methods and application scopes according to the ideas, spirits and principles of the present invention, and any modifications, equivalent substitutions, improvements, etc. made therein should be included in the scope of protection of this application.

Claims

1. A dual-machine hot standby method in SDWAN, IPRAN or RTN, characterized in that: The management and control platform creates a protection group, the protection group including a first core node and a second core node; the method includes: In response to a device status notification sent when the first core node serves as a master device, recording the device status of the first core node in the protection group as a master device status, and recording the device status of the second core node as a standby device status; In response to a service created by a user based on a selected service type, a protection group, and a CPE, determining a core node whose device state in the current protection group is a master device state as a first core node; Based on the service type, service configuration information corresponding to the service is generated, and the service configuration information is sent to the first core node and the CPE respectively to realize transmission of the service between the first core node and the CPE.

2. The method according to claim 1, characterized in that: The method further comprises: In response to a user input for switching the master device in the protection group, updating the device state of the first core node in the protection group to a standby device state, and updating the device state of the second core node to a master device state; The first core node is notified to switch the device state, so that the first core node pushes the configuration information to the backup device and switches to the backup device, and the second core node switches to the main device.

3. The method according to claim 1, characterized in that The method further comprises: In response to a command to replace the protection group, obtaining service configuration information of the corresponding protection group in the platform database according to the first protection group identifier carried in the command; Sending the acquired service configuration information to the protection group corresponding to the second protection group identifier carried in the command to realize fast switching of the protection group corresponding to the service; The first protection group identifier is the protection group identifier of the protection group to be replaced; and the second protection group identifier is the protection group identifier of the protection group to be replaced.

4. The method according to claim 1, characterized in that: The method further comprises: In response to a device status notification sent by the second core node when the first core node abnormally switches to a master device, the device status of the first core node in the protection group is updated to a backup device status, and the device status of the second core node is updated to a master device status.

5. The method according to claim 1, characterized in that Configuration information of the first core node and the second core node is configured through a web interface; the configuration information includes: a heartbeat interface, a virtual IP, a health monitoring option, and an initial state; wherein the heartbeat interface, the virtual IP, and the health monitoring option are the same on the first core node and the second core node; the initial state of the first core node is a master device state, and the initial state of the second core node is a standby device state; The heartbeat interface is used for communicating between the first core node and the second core node through a heartbeat line to determine whether the opposite core node is in an abnormal state; The virtual IP is used for the core node to communicate with the CPE when it acts as a master device; The health monitoring option is used to perform health monitoring when the core node is used as a master device; if the monitoring result does not meet the preset conditions, the device status is determined to be abnormal, and no heartbeat message is sent to the core node used as a backup device.

6. The method according to claim 5, characterized in that The health monitoring options include any one or any combination of the following: Ping detection, HTTP service detection, interface status monitoring, network connectivity, link quality detection, CPU usage, and memory usage.

7. The method according to claim 5, characterized in that If the interface of the first core node and the second core node used for service communication with the CPE is not the same as the interface for communication with the control platform, respectively configure virtual IPs for different interfaces; If the first core node and the second core node use different interfaces for communicating with different servers, virtual IPs are configured for different interfaces respectively.

8. A dual-machine hot standby device in SDWAN, IPRAN or RTN, characterized in that: The device comprises: A configuration unit, configured to create a protection group, wherein the protection group includes a first core node and a second core node; A processing unit, configured to, in response to a device status notification sent when the first core node acts as a master device, record the device status of the first core node in the protection group as a master device status, and record the device status of the second core node as a standby device status; A determining unit, configured to determine, in response to a service type, a protection group, and a service created by a CPE selected by a user, a core node whose device state in the current protection group is a master device state as a first core node; A generating unit, configured to generate service configuration information corresponding to the service based on the service type; The sending unit is used to send the service configuration information to the first core node and the CPE respectively to realize the transmission of the service between the first core node and the CPE.

9. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that: When the processor executes the program, the method according to any one of claims 1 to 7 is implemented.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the program is executed by a processor, the method described in any one of claims 1 to 7 is implemented.

Images