CN112367182A - Configuration method and device of disaster recovery main and standby equipment - Google Patents
Configuration method and device of disaster recovery main and standby equipment Download PDFInfo
- Publication number
- CN112367182A CN112367182A CN202011055551.XA CN202011055551A CN112367182A CN 112367182 A CN112367182 A CN 112367182A CN 202011055551 A CN202011055551 A CN 202011055551A CN 112367182 A CN112367182 A CN 112367182A
- Authority
- CN
- China
- Prior art keywords
- vbras
- identifier
- list
- identifier list
- disaster recovery
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
- 238000011084 recovery Methods 0.000 title claims abstract description 116
- 238000000034 method Methods 0.000 title claims abstract description 59
- 239000013256 coordination polymer Substances 0.000 claims abstract description 177
- 238000009499 grossing Methods 0.000 claims description 10
- 230000006870 function Effects 0.000 description 31
- 230000008569 process Effects 0.000 description 12
- 238000010586 diagram Methods 0.000 description 7
- 230000004044 response Effects 0.000 description 5
- 230000006855 networking Effects 0.000 description 2
- 230000005540 biological transmission Effects 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 230000006872 improvement Effects 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 231100000817 safety factor Toxicity 0.000 description 1
- 238000000926 separation method Methods 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/06—Management of faults, events, alarms or notifications
- H04L41/0654—Management of faults, events, alarms or notifications using network fault recovery
- H04L41/0663—Performing the actions predefined by failover planning, e.g. switching to standby network elements
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/0803—Configuration setting
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Hardware Redundancy (AREA)
- Telephonic Communication Services (AREA)
Abstract
The application provides a configuration method and a device of disaster recovery main and standby equipment, the method is applied to first vBRAS-CP equipment, and the method comprises the following steps: receiving a first heartbeat notification message which is sent by a second vBRAS-CP device and comprises a first identification list; acquiring a second identifier list in the first vBRAS-CP device, and judging whether a first UP device identifier exists in the second identifier list; if the first UP device identifier exists, identifying the configuration states of the first UP device corresponding to the first UP device identifier in a first identifier list and a second identifier list; if the first UP device is in the configured state in the second identification list and is updated from the configured state to the unconfigured state in the first identification list, the user access function of the first UP device is forbidden; and sending a first notification message to the first UP device so that the first UP device does not send a user service message to the first vBRAS-CP device.
Description
Technical Field
The present application relates to the field of communications technologies, and in particular, to a method and an apparatus for configuring a disaster recovery master device and a disaster recovery backup device.
Background
With the expansion of enterprise scale, the stand-alone backup of user data cannot meet the requirements of key services on the availability, real-time performance and safety of the system. Backup data is often destroyed by various factors, such as earthquake, fire, loss, etc. The occurrence of the remote disaster recovery scheme can further improve the disaster recovery capability of the data against various safety factors by establishing backup systems at different places.
For a Broadband Remote Access Server (BRAS) forwarding Control separation system, a Control Plane (CP) of the BRAS, namely a virtual Broadband Remote Access Server-Control Plane (vBRAS-CP) device for realizing the Control Plane function is arranged in a Data Center (DC). The remote disaster recovery scheme refers to that dual-computer backup is carried out on vBRAS-CP equipment in two different DCs. The two vBRAS-CP devices belong to different DCs respectively, and are configured to be in a master/standby state. Therefore, when the main vBRAS-CP equipment fails or a link between the main vBRAS-CP equipment and User Plane (UP) equipment of the BRAS fails, User services can be quickly switched to the standby vBRAS-CP equipment.
In a remote disaster tolerance environment, the primary and secondary vBRAS-CP devices have different priorities. The priority of the primary vBRAS-CP device is higher than that of the standby vBRAS-CP. And after the vBRAS-CP equipment between the DCs decides respective roles, the primary and standby vBRAS-CP equipment updates the priority of the respective equipment. Meanwhile, the primary vBRAS-CP device sends a notification message to the accessed UP device and notifies the UP device of the latest priority of the device. After acquiring the priority of the primary vBRAS-CP equipment, the UP equipment compares the priority of the primary vBRAS-CP equipment with the priority of another vBRAS-CP equipment, and selects the vBRAS-CP equipment with higher priority between the primary vBRAS-CP equipment and the another vBRAS-CP equipment as the primary vBRAS-CP equipment.
In order to ensure that the user service that has been accessed and the user service that is newly accessed are not affected after the primary DC fails, the primary and secondary DCs need to have the same configuration at this time. For example, the primary and standby DCs configure the same disaster recovery backup group, and the UP devices backed UP in the disaster recovery backup group also configure the same.
However, in practical applications, the respective physical locations of the main and standby DCs may be far apart. For example, the primary DC is deployed in a provincial central machine room, and the standby DC is deployed in a county machine room; moreover, it is difficult for the administrator to ensure that the configuration can be modified for the primary and secondary vbrs-CP devices included in the primary and secondary DC at the same time. Therefore, the situation that the configuration of the UP devices in the disaster recovery backup group is inconsistent often occurs.
For example, the UP1024 (i.e., the UP device numbered 1024) needs to support the disaster recovery backup of the primary and secondary vbrs-CP devices, but the primary vbrs-CP device does not configure the UP1024 in the disaster recovery backup group, and the backup primary vbrs-CP device includes the disaster recovery backup group with correct configuration. Therefore, the UP1024 does not receive the device priority issued by the primary vbrs-CP device, so that the UP1024 cannot drain the user service to the primary vbrs-CP device, which causes the service exception of the UP 1024.
At present, in order to overcome the foregoing problems, the existing methods are: deleting all disaster-tolerant backup groups in the main backup DC, and enabling the UP device to delete the recorded priority of the main backup vBRAS-CP device. The disaster tolerant backup groups in the primary and backup DCs are then rebuilt. However, in the above manner, deleting all the disaster recovery backup groups in the primary and backup DC may affect the service functions of other UP devices in the disaster recovery backup group, resulting in interruption of other UP service functions.
Disclosure of Invention
In view of this, the present application provides a configuration method and an apparatus for a disaster recovery master backup device, so as to solve the problem in the prior art that deleting all disaster recovery backup groups in a master backup DC affects service functions of other UP devices in the disaster recovery backup group, resulting in interruption of other UP service functions.
In a first aspect, the present application provides a configuration method for a disaster recovery master backup device, where the method is applied to a first vbrs-CP device, where the first vbrs-CP device is in a vbrs-CP device group, and the vbrs-CP device group further includes a second vbrs-CP device, and the method includes:
receiving a first heartbeat notification message sent by the second vBRAS-CP device, wherein the first heartbeat notification message comprises a first identifier list configured by a disaster recovery backup group in the second vBRAS-CP device, and the first identifier list comprises a first UP device identifier;
acquiring a second identifier list configured by a disaster recovery backup group in the first vBRAS-CP device, and judging whether the first UP device identifier exists in the second identifier list or not;
if the first UP device identifier exists in the second identifier list, identifying the configuration states of the first UP device corresponding to the first UP device identifier in the first identifier list and the second identifier list respectively;
if the configuration state of the first UP device in the second identification list is a configured state and the configuration state in the first identification list is updated from the configured state to an unconfigured state, closing the user access function of the first UP device;
and sending a first notification message to the first UP device so that the first UP device does not send a user service message to the first vBRAS-CP device.
In a second aspect, the present application provides a configuration apparatus for a disaster recovery master backup device, where the apparatus is applied to a first vbrs-CP device, where the first vbrs-CP device is in a vbrs-CP device group, and the vbrs-CP device group further includes a second vbrs-CP device, and the apparatus includes:
a receiving unit, configured to receive a first heartbeat notification message sent by the second vbrs-CP device, where the first heartbeat notification message includes a first identifier list configured in a disaster recovery backup group in the second vbrs-CP device, and the first identifier list includes a first UP device identifier;
a determining unit, configured to obtain a second identifier list configured by a disaster recovery backup group in the first vbrs-CP device, and determine whether the first UP device identifier already exists in the second identifier list;
an identifying unit, configured to identify, if the first UP device identifier already exists in the second identifier list, a configuration state of a first UP device corresponding to the first UP device identifier in the first identifier list and the second identifier list, respectively;
a processing unit, configured to close a user access function of the first UP device if the configuration state of the first UP device in the second identifier list is a configured state and the configuration state in the first identifier list is updated from the configured state to an unconfigured state;
a sending unit, configured to send a first notification message to the first UP device, so that the first UP device does not send a user service packet to the first vbrs-CP device.
In a third aspect, the present application provides a network device comprising a processor and a machine-readable storage medium storing machine-executable instructions executable by the processor, the processor being caused by the machine-executable instructions to perform the method provided by the first aspect of the present application.
Therefore, by applying the configuration method and device for the disaster recovery backup device provided by the present application, the first vbrs-CP device receives a first heartbeat notification message sent by the second vbrs-CP device, where the first heartbeat notification message includes a first identifier list configured in the disaster recovery backup group in the second vbrs-CP device, and the first identifier list includes a first UP device identifier. And the first vBRAS-CP equipment acquires a second identifier list configured by the disaster recovery backup group in the first vBRAS-CP equipment and judges whether the first UP equipment identifier exists in the second identifier list or not. If the first UP device identifier already exists in the second identifier list, the first vbrs-CP device identifies the configuration states of the first UP device corresponding to the first UP device identifier in the first identifier list and the second identifier list, respectively. And if the configuration state of the first UP device in the second identification list is the configured state and the configuration state in the first identification list is updated from the configured state to the unconfigured state, the first vBRAS-CP device closes the user access function of the first UP device. And the first vBRAS-CP equipment sends a first notification message to the first UP equipment so that the first UP equipment does not send a user service message to the first vBRAS-CP equipment.
When the UP devices configured by the disaster recovery backup group between the vbrs-CP devices are inconsistent, the vbrs-CP device can automatically close the relevant service functions configured with different UP devices, and does not affect the service functions of other UP devices configured with the same configuration, so as to solve the problem that deleting all the disaster recovery backup groups in the primary and backup DC in the prior art will affect the service functions of other UP devices in the disaster recovery backup group, resulting in interruption of other UP service functions.
Drawings
Fig. 1 is a flowchart of a configuration method of a disaster recovery primary and backup device according to an embodiment of the present application;
fig. 2 is a schematic networking diagram of disaster recovery backup according to an embodiment of the present application;
fig. 3 is a schematic diagram of a TLV field extended in a message provided in an embodiment of the present application;
fig. 4 is a configuration apparatus structure diagram of a disaster recovery main backup device according to an embodiment of the present application;
fig. 5 is a hardware structure diagram of a network device according to an embodiment of the present application.
Detailed Description
Reference will now be made in detail to the exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, like numbers in different drawings represent the same or similar elements unless otherwise indicated. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present application. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the present application, as detailed in the appended claims.
The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the application. As used in this application and the appended claims, the singular forms "a", "an", and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It should also be understood that the term "and/or" as used herein refers to and encompasses any and all possible combinations of one or more of the corresponding listed items.
It is to be understood that although the terms first, second, third, etc. may be used herein to describe various information, such information should not be limited to these terms. These terms are only used to distinguish one type of information from another. For example, first information may also be referred to as second information, and similarly, second information may also be referred to as first information, without departing from the scope of the present application. The word "if" as used herein may be interpreted as "at … …" or "when … …" or "in response to a determination", depending on the context.
The following describes in detail a configuration method of disaster recovery main backup devices provided in an embodiment of the present application. Referring to fig. 1, fig. 1 is a flowchart of a configuration method of a disaster recovery primary and standby device according to an embodiment of the present application. The method is applied to a first vbrs-CP device, and the method for configuring a disaster recovery master backup device provided in the embodiment of the present application may include the following steps.
Specifically, as shown in fig. 2, fig. 2 is a schematic networking diagram of disaster recovery backup provided in the embodiment of the present application. The first vBRAS-CP device is in a vBRAS-CP device group, and the vBRAS-CP device group further comprises a second vBRAS-CP device. And a disaster tolerance heartbeat channel is established between the first vBRAS-CP equipment and the second vBRAS-CP equipment. The channel can be used for exchanging heartbeat notification messages between the first vBRAS-CP equipment and the second vBRAS-CP equipment so as to mutually know the current state of the opposite end and synchronize data.
Each vBRAS-CP device creates a disaster-tolerant backup group, and each disaster-tolerant backup group consists of a plurality of UP devices. The UP devices included in the disaster recovery backup group created by the first vbrs-CP device should be the same as the UP devices included in the disaster recovery backup group created by the second vbrs-CP device (the same specifically means that the number of the UP devices is the same and the labels indicating the UP devices are the same), and the configuration of the same UP device in each disaster recovery backup group should also be the same.
After each vBRAS-CP device creates a disaster recovery backup group, if a disaster recovery heartbeat channel is established between the first vBRAS-CP device and the second vBRAS-CP device, the two parties mutually announce a heartbeat announcement message to inform the opposite end of the configuration state of the UP device in the disaster recovery backup group.
Further, a disaster tolerance heartbeat channel is established between the first vBRAS-CP device and the second vBRAS-CP device. The second vbrs-CP device generates a heartbeat notification message (which may be referred to as a first heartbeat notification message in this embodiment), where the first heartbeat notification message includes a first identifier list configured by the disaster recovery backup group in the second vbrs-CP device, and the first identifier list includes a first UP device identifier.
It can be understood that, in the embodiment of the present application, the device identifier including all the UP devices in the disaster recovery backup group in the first identifier list is described by taking the first UP device identifier as an example. The first UP device identification may be embodied as one or more.
It should be noted that the identifier list includes the device identifier of the UP device and the configuration state corresponding to the UP device.
And after the second vBRAS-CP equipment generates a first heartbeat notification message, notifying the established disaster recovery heartbeat channel, and sending the first heartbeat notification message to the first vBRAS-CP equipment.
After receiving the first heartbeat notification message, the first vBRAS-CP device acquires a first identifier list configured by a disaster recovery backup group in the second vBRAS-CP device, and acquires a first UP device identifier from the first identifier list.
Specifically, the first vbrs-CP device obtains a second identifier list configured by the disaster recovery backup group in the first vbrs-CP device. As described in step 110, the first vbrs-CP device determines whether the aforementioned first UP device identifier already exists in the second identifier list.
If the first UP device id already exists in the second id list, go to step 130; otherwise, step 130 is not performed.
Specifically, according to the judgment in step 120, if the first UP device identifier already exists in the second identifier list, the first vbrs-CP device obtains the configuration state of the UP device corresponding to the first UP device identifier from the first identifier list and the second identifier list, respectively.
And the first vBRAS-CP device identifies the configuration states of the first UP device corresponding to the first UP device identification in the first identification list and the second identification list respectively.
Specifically, if the configuration state of the first UP device in the second identifier list is the configured state, and the configuration state in the first identifier list is updated from the configured state to the unconfigured state, the first vbrs-CP device closes the user access function of the first UP device in the disaster recovery backup group of the first vbrs-CP device.
Further, if the configuration state of the first UP device in the second identifier list is a configured state, and the configuration state in the first identifier list is updated from an unconfigured state to a configured state, the first vbrs-CP device opens the user access function of the first UP device.
Further, if the configuration state of the first UP device identifier in the second identifier list is an unconfigured state, and the configuration state in the first identifier list is a configured state, the first vbrs-CP device records the configuration state of each UP device corresponding to each UP device identifier in the first identifier list.
In this embodiment of the present application, the first vbrs-CP device divides a sub-memory region in a memory, and stores a configuration state of each UP device corresponding to each UP device identifier in the first identifier list into the sub-memory region.
Specifically, according to the judgment in step 140, the first vbrs-CP device determines that the configuration state of the UP device in the local disaster recovery backup group is the configured state, and the configuration state of the UP device in the disaster recovery backup group in the second vbrs-CP device is the unconfigured state, and after the first vbrs-CP device closes the user access function of the first UP device in the disaster recovery backup group, the first vbrs-CP device generates a notification message (which may be denoted as a first notification message in this embodiment of the present application).
The first vBRAS-CP device sends a first notification message to the first UP device. And after receiving the first notification message, the first UP device does not send the user service message to the first vBRAS-CP device.
Further, according to the judgment in step 140, the first vbrs-CP device determines that the configuration state of the UP device in the local disaster recovery backup group is the configured state, and the configuration state of the UP device in the disaster recovery backup group in the second vbrs-CP device is the configured state, and after the first vbrs-CP device starts the user access function of the first UP device in its own disaster recovery backup group, when the first vbrs-CP device is the primary first vbrs-CP device, the first vbrs-CP device generates a notification message (which may be denoted as a second notification message in this embodiment of the present application).
And the first vBRAS-CP equipment sends a second notification message to the first UP equipment, and the first UP equipment sends a user service message to the first vBRAS-CP equipment after receiving the second notification message.
It should be noted that, after the first vbrs-CP device starts the user access function of the first UP device in the disaster recovery backup group, the primary vbrs-CP device in the vbrs-CP device group generates a second notification message, and sends the second notification message to the first UP device, so as to notify the first UP device to send the user service packet to the primary vbrs-CP device.
Further, according to the judgment in step 140, the first vbrs-CP device determines that the configuration state of the UP device in the local disaster recovery backup group is an unconfigured state, while the configuration state of the UP device in the disaster recovery backup group in the second vbrs-CP device is a configured state, and after the first vbrs-CP device records the configuration state of each UP device corresponding to each UP device identifier in the first identifier list, the first vbrs-CP device generates an ACK message, where the ACK message includes the second identifier list configured in the disaster recovery backup group in the first vbrs-CP device.
And the first vBRAS-CP device sends an ACK message to the second vBRAS-CP device. After receiving the ACK message, the second vbrs-CP device obtains a second identifier list configured by the disaster recovery backup group in the first vbrs-CP device, and performs the foregoing steps 110 to 150, and determines and identifies whether the configuration state of each UP device in the first identifier list of the home terminal is the same as the configuration state of each UP device in the second identifier list. It is understood that the specific identification process is the same as the judgment and identification process of the first vbrs-CP device, and will not be repeated here.
Optionally, in this embodiment of the present application, the method further includes a step in which the first vbrs-CP device notifies the second vbrs-CP device of the configuration state of the UP device in the disaster recovery backup group of the first vbrs-CP device.
Specifically, after the first vbrs-CP device receives the first heartbeat notification message sent by the second vbrs-CP device, the first vbrs-CP device may generate an ACK message and send the ACK message to the second vbrs-CP device, where the ACK message includes a second identifier list configured by the disaster recovery backup group in the first vbrs-CP device.
After receiving the ACK message, the second vbrs-CP device obtains a second identifier list configured by the disaster recovery backup group in the first vbrs-CP device, and performs the foregoing steps 110 to 150, and determines and identifies whether the configuration state of each UP device in the first identifier list of the home terminal is the same as the configuration state of each UP device in the second identifier list. It is understood that the specific identification process is the same as the judgment and identification process of the first vbrs-CP device, and will not be repeated here.
Optionally, in this embodiment of the present application, the method further includes a step of notifying, by each vbrs-CP device, a configuration state of the UP device in its disaster recovery backup group when the first vbrs-CP device and the second vbrs-CP device reestablish heartbeat connection.
Specifically, when a heartbeat connection is reestablished between a first vBRAS-CP device and a second vBRAS-CP device, the first vBRAS-CP device generates a smoothing request message, and the smoothing request message comprises a second identification list of a disaster recovery backup group in the first vBRAS-CP device.
After receiving the smoothing request message, the second vbrs-CP device obtains a second identifier list configured by the disaster recovery backup group in the first vbrs-CP device, and performs the foregoing steps 110 to 150, and determines and identifies whether the configuration state of each UP device in the first identifier list of the home terminal is the same as the configuration state of each UP device in the second identifier list. It is understood that the specific identification process is the same as the judgment and identification process of the first vbrs-CP device, and will not be repeated here.
Further, the second vBRAS-CP device generates a smooth response message, the smooth response message comprises a first identification list of the disaster recovery backup group in the second vBRAS-CP device, and the smooth response message is sent to the first vBRAS-CP device.
After receiving the smooth response message, the first vbrs-CP device obtains the first identifier list configured by the disaster recovery backup group in the second vbrs-CP device, and performs the foregoing steps 110 to 150, which are not repeated here.
It can be understood that, the process of reestablishing the heartbeat connection between the first vbrs-CP device and the second vbrs-CP device, that is, the process of reestablishing the TCP connection is resumed after the vbrs-CP device at a certain end is restarted or the transmission network between the first vbrs-CP device and the second vbrs-CP device fails.
Optionally, in this embodiment of the present application, the method further includes a step of notifying, by each vbrs-CP device, the configuration state of the UP device after the configuration state is changed in the disaster recovery backup group of the vbrs-CP device.
Specifically, when the configuration state of each UP device corresponding to each UP device identifier in the second identifier list is changed, the first vbrs-CP device generates a heartbeat notification message (in this embodiment, the heartbeat notification message may be denoted as a second heartbeat notification message), where the second heartbeat notification message includes the second identifier list after the disaster recovery backup group in the first vbrs-CP device is changed.
And the first vBRAS-CP equipment sends a second heartbeat notification message to the second vBRAS-CP equipment. After receiving the second heartbeat notification message, the second vbrs-CP device obtains the second identifier list after the disaster recovery backup group in the first vbrs-CP device is changed, and performs the aforementioned steps 110 to 150, and determines and identifies whether the configuration state of each UP device in the first identifier list of the home terminal is the same as the configuration state of each UP device in the second identifier list. It is understood that the specific identification process is the same as the judgment and identification process of the first vbrs-CP device, and will not be repeated here.
It can be understood that, after the second vbrs-CP device receives the second heartbeat notification message, the second vbrs-CP device may generate an ACK message, and carry the first identifier list configured by the disaster recovery backup group in the second vbrs-CP device in the ACK message.
In a similar way, when the configuration state of each UP device corresponding to each UP device identifier in the first identifier list is changed, the second vbrs-CP device generates a second heartbeat notification message, where the second heartbeat notification message includes the first identifier list after the disaster recovery backup group in the second vbrs-CP device is changed.
And the second vBRAS-CP equipment sends a second heartbeat notification message to the first vBRAS-CP equipment. After receiving the second heartbeat notification message, the first vbrs-CP device obtains the first identifier list after the disaster recovery backup group in the second vbrs-CP device is changed, and performs the foregoing steps 110 to 150, which are not repeated here.
It can be understood that, after the first vbrs-CP device receives the second heartbeat notification message, the first vbrs-CP device may generate an ACK message, and carry the second identifier list configured by the disaster recovery backup group in the first vbrs-CP device in the ACK message.
Optionally, in this embodiment of the present application, the method further includes a step of sending, by the vbrs-CP device, a notification message (which may be referred to as a third notification message in this embodiment of the present application) to the UP device when the UP device is deleted from the disaster recovery backup group.
Specifically, when the UP device corresponding to any UP device identifier in the second identifier list is deleted from the disaster recovery backup group, the first vbrs-CP device generates a third notification message.
And the first vBRAS-CP equipment sends a third notification message to the UP equipment, and after the UP equipment receives the third notification message, the UP equipment does not send a user service message to the first vBRAS-CP equipment any more.
Similarly, when the UP device corresponding to any UP device identifier in the first identifier list is deleted from the disaster recovery backup group, the second vbrs-CP device generates a third notification message.
And the second vBRAS-CP equipment sends a third notification message to the UP equipment, and after the UP equipment receives the third notification message, the UP equipment does not send a user service message to the second vBRAS-CP equipment any more.
Optionally, in this embodiment of the application, a TLV field is extended in each of the heartbeat notification message, the ACK message, and the smoothing message, and the TLV field carries an identification list. As shown in fig. 3, fig. 3 is a schematic diagram of a TLV field extended in a message provided in this embodiment of the present application.
In fig. 3, the aforementioned types of messages include a Type (Type) field, a Length (Length) field, a Group (Group) ID field, an identification List Length (UP _ List Length) field of the UP device, and a TLV field.
Wherein, the value of the Type field is filled as a UP _ List, and the value of the TLV field is filled as an identification List of the UP device.
Therefore, by applying the configuration method and device for the disaster recovery backup device provided by the present application, the first vbrs-CP device receives a first heartbeat notification message sent by the second vbrs-CP device, where the first heartbeat notification message includes a first identifier list configured in the disaster recovery backup group in the second vbrs-CP device, and the first identifier list includes a first UP device identifier. And the first vBRAS-CP equipment acquires a second identifier list configured by the disaster recovery backup group in the first vBRAS-CP equipment and judges whether the first UP equipment identifier exists in the second identifier list or not. If the first UP device identifier already exists in the second identifier list, the first vbrs-CP device identifies the configuration states of the first UP device corresponding to the first UP device identifier in the first identifier list and the second identifier list, respectively. And if the configuration state of the first UP device in the second identification list is the configured state and the configuration state in the first identification list is updated from the configured state to the unconfigured state, the first vBRAS-CP device closes the user access function of the first UP device. And the first vBRAS-CP equipment sends a first notification message to the first UP equipment so that the first UP equipment does not send a user service message to the first vBRAS-CP equipment.
When the UP devices configured by the disaster recovery backup group between the vbrs-CP devices are inconsistent, the vbrs-CP device can automatically close the relevant service functions configured with different UP devices, and does not affect the service functions of other UP devices configured with the same configuration, so as to solve the problem that deleting all the disaster recovery backup groups in the primary and backup DC in the prior art will affect the service functions of other UP devices in the disaster recovery backup group, resulting in interruption of other UP service functions.
Based on the same inventive concept, the embodiment of the present application further provides a configuration apparatus of the disaster recovery main and standby device corresponding to the configuration method of the disaster recovery main and standby device. Referring to fig. 4, fig. 4 is a structural diagram of a configuration apparatus of a disaster recovery primary and standby device provided in this embodiment, where the apparatus is applied to a first vbrs-CP device, the first vbrs-CP device is in a vbrs-CP device group, the vbrs-CP device group further includes a second vbrs-CP device, and the apparatus includes:
a receiving unit 410, configured to receive a first heartbeat notification message sent by the second vbrs-CP device, where the first heartbeat notification message includes a first identifier list configured in a disaster recovery backup group in the second vbrs-CP device, and the first identifier list includes a first UP device identifier;
a determining unit 420, configured to obtain a second identifier list configured by the disaster recovery backup group in the first vbrs-CP device, and determine whether the first UP device identifier already exists in the second identifier list;
an identifying unit 430, configured to identify, if the first UP device identifier already exists in the second identifier list, configuration states of a first UP device corresponding to the first UP device identifier in the first identifier list and the second identifier list, respectively;
a processing unit 440, configured to close a user access function of the first UP device if the configuration state of the first UP device in the second identifier list is a configured state and the configuration state in the first identifier list is updated from the configured state to an unconfigured state;
a sending unit 450, configured to send a first notification message to the first UP device, so that the first UP device does not send a user service packet to the first vbrs-CP device.
Optionally, the sending unit 450 is further configured to send an ACK message to the second vbrs-CP device, where the ACK message includes a second identifier list configured in the disaster recovery backup group in the first vbrs-CP device.
Optionally, the processing unit 440 is further configured to, if the configuration state of the first UP device in the second identifier list is a configured state, and the configuration state in the first identifier list is updated from an unconfigured state to a configured state, open a user access function of the first UP device.
Optionally, the sending unit 450 is further configured to send a second notification message to the first UP device when the first vbrs-CP device is the active first vbrs-CP device, so that the first UP device sends a user service packet to the first vbrs-CP device.
Optionally, the apparatus further comprises: a recording unit (not shown in the figure), configured to record the configuration state of each UP device corresponding to each UP device identifier in the first identifier list if the configuration state of the first UP device in the second identifier list is an unconfigured state and the configuration state in the first identifier list is a configured state.
Optionally, the sending unit 450 is further configured to send a smoothing message to the second vbrs-CP device when the heartbeat connection is reestablished between the first vbrs-CP device and the second vbrs-CP device, where the smoothing message includes a second identifier list of the disaster recovery backup group in the first vbrs-CP device.
Optionally, the sending unit 450 is further configured to send a second heartbeat notification message to the second vbrs-CP device when the configuration state of each UP device corresponding to each UP device identifier in the second identifier list is changed, where the second heartbeat notification message includes a second identifier list after the disaster recovery backup group in the first vbrs-CP device is changed.
Optionally, the sending unit 450 is further configured to send a third notification message to the UP device when the UP device corresponding to any UP device identifier in the second identifier list is deleted from the disaster recovery backup group, so that the UP device does not send a user service packet to the first vbrs-CP device any more.
Optionally, the heartbeat advertisement message includes a TLV field, and the identifier list is carried in the TLV field;
the ACK message comprises a TLV field, and the identification list is carried in the TLV field;
the smoothing message comprises a TLV field, and the identification list is carried in the TLV field.
Therefore, by applying the configuration device of the disaster recovery primary and standby device provided by the present application, the device receives a first heartbeat notification message sent by a second vbrs-CP device, where the first heartbeat notification message includes a first identifier list configured by a disaster recovery backup group in the second vbrs-CP device, where the first identifier list includes a first UP device identifier. The device obtains a second identification list configured by the disaster recovery backup group in the device, and judges whether the first UP equipment identification exists in the second identification list. If the first UP device identifier already exists in the second identifier list, the apparatus identifies the configuration states of the first UP device corresponding to the first UP device identifier in the first identifier list and the second identifier list, respectively. If the configuration state of the first UP device in the second identification list is the configured state and the configuration state in the first identification list is updated from the configured state to the unconfigured state, the device closes the user access function of the first UP device. The device sends a first notification message to the first UP device, so that the first UP device does not send a user service message to the device.
When the UP devices configured by the disaster recovery backup group between the vbrs-CP devices are inconsistent, the vbrs-CP device can automatically close the relevant service functions configured with different UP devices, and does not affect the service functions of other UP devices configured with the same configuration, so as to solve the problem that deleting all the disaster recovery backup groups in the primary and backup DC in the prior art will affect the service functions of other UP devices in the disaster recovery backup group, resulting in interruption of other UP service functions.
Based on the same inventive concept, the present application further provides a network device, as shown in fig. 5, including a processor 510, a transceiver 520, and a machine-readable storage medium 530, where the machine-readable storage medium 530 stores machine-executable instructions capable of being executed by the processor 510, and the processor 510 is caused by the machine-executable instructions to perform the configuration method of the disaster-tolerant primary and backup device provided in the present application. The configuration apparatus of the disaster recovery main-standby device shown in fig. 4 can be implemented by using a hardware structure of a network device shown in fig. 5.
The computer-readable storage medium 530 may include a Random Access Memory (RAM) or a Non-volatile Memory (NVM), such as at least one disk Memory. Alternatively, the computer-readable storage medium 530 may also be at least one storage device located remotely from the processor 510.
The Processor 510 may be a general-purpose Processor, and includes a Central Processing Unit (CPU), a Network Processor (NP), and the like; the Integrated Circuit can also be a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA), or other Programmable logic devices, discrete Gate or transistor logic devices, discrete hardware components.
In the embodiment of the present application, the processor 510 reads the machine executable instructions stored in the machine readable storage medium 530, and the machine executable instructions cause the processor 510 itself and the transceiver 520 to perform the configuration method of the disaster recovery primary and backup device described in the embodiment of the present application.
In addition, the embodiment of the present application provides a machine-readable storage medium 530, where the machine-readable storage medium 530 stores machine executable instructions, and when the machine executable instructions are called and executed by the processor 510, the machine executable instructions cause the processor 510 itself and the calling transceiver 520 to perform the configuration method of the disaster recovery primary standby device described in the embodiment of the present application.
The implementation process of the functions and actions of each unit in the above device is specifically described in the implementation process of the corresponding step in the above method, and is not described herein again.
For the device embodiments, since they substantially correspond to the method embodiments, reference may be made to the partial description of the method embodiments for relevant points. The above-described embodiments of the apparatus are merely illustrative, and the units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the modules can be selected according to actual needs to achieve the purpose of the scheme of the application. One of ordinary skill in the art can understand and implement it without inventive effort.
As for the configuration apparatus of the disaster recovery primary and backup device and the machine-readable storage medium embodiment, since the contents of the related method are substantially similar to those of the foregoing method embodiment, the description is relatively simple, and the relevant points can be referred to the partial description of the method embodiment.
The above description is only exemplary of the present application and should not be taken as limiting the present application, as any modification, equivalent replacement, or improvement made within the spirit and principle of the present application should be included in the scope of protection of the present application.
Claims (10)
1. A configuration method of disaster recovery main standby equipment is characterized in that the method is applied to first vBRAS-CP equipment, the first vBRAS-CP equipment is in a vBRAS-CP equipment group, the vBRAS-CP equipment group further comprises second vBRAS-CP equipment, and the method comprises the following steps:
receiving a first heartbeat notification message sent by the second vBRAS-CP device, wherein the first heartbeat notification message comprises a first identifier list configured by a disaster recovery backup group in the second vBRAS-CP device, and the first identifier list comprises a first UP device identifier;
acquiring a second identifier list configured by a disaster recovery backup group in the first vBRAS-CP device, and judging whether the first UP device identifier exists in the second identifier list or not;
if the first UP device identifier exists in the second identifier list, identifying the configuration states of the first UP device corresponding to the first UP device identifier in the first identifier list and the second identifier list respectively;
if the configuration state of the first UP device in the second identification list is a configured state and the configuration state in the first identification list is updated from the configured state to an unconfigured state, closing the user access function of the first UP device;
and sending a first notification message to the first UP device so that the first UP device does not send a user service message to the first vBRAS-CP device.
2. The method of claim 1, wherein after receiving the first heartbeat announcement message sent by the second vbars-CP device, the method further comprises:
and sending an ACK message to the second vBRAS-CP equipment, wherein the ACK message comprises a second identification list configured by the disaster recovery backup group in the first vBRAS-CP equipment.
3. The method of claim 1, further comprising:
and if the configuration state of the first UP device in the second identification list is the configured state and the configuration state in the first identification list is updated from the unconfigured state to the configured state, starting the user access function of the first UP device.
4. The method of claim 3, further comprising:
and when the first vBRAS-CP device is the active first vBRAS-CP device, sending a second notification message to the first UP device so that the first UP device sends a user service message to the first vBRAS-CP device.
5. The method of claim 2, wherein before sending the ACK message to the vbars-CP device, the method further comprises:
if the configuration state of the first UP device in the second identifier list is an unconfigured state and the configuration state in the first identifier list is a configured state, recording the configuration state of each UP device corresponding to each UP device identifier in the first identifier list.
6. The method of claim 1, further comprising:
when the first vBRAS-CP equipment and the second vBRAS-CP equipment reestablish heartbeat connection, sending a smoothing message to the second vBRAS-CP equipment, wherein the smoothing message comprises a second identification list of the disaster recovery backup group in the first vBRAS-CP equipment.
7. The method of claim 1, further comprising:
and when the configuration state of each UP device corresponding to each UP device identifier in the second identifier list is changed, sending a second heartbeat notification message to the second vBRAS-CP device, wherein the second heartbeat notification message comprises the second identifier list after the disaster recovery backup group in the first vBRAS-CP device is changed.
8. The method of claim 1, further comprising:
and when the UP device corresponding to any UP device identifier in the second identifier list is deleted from the disaster recovery backup group, sending a third notification message to the UP device so that the UP device does not send a user service message to the first vBRAS-CP device any more.
9. The method according to any of claims 1-8, wherein the heartbeat advertisement message includes a TLV field in which the list of identifications is carried;
the ACK message comprises a TLV field, and the identification list is carried in the TLV field;
the smoothing message comprises a TLV field, and the identification list is carried in the TLV field.
10. A configuration apparatus of disaster recovery master backup device, wherein the apparatus is applied to a first vbars-CP device, the first vbars-CP device is in a vbars-CP device group, the vbars-CP device group further includes a second vbars-CP device, and the apparatus comprises:
a receiving unit, configured to receive a first heartbeat notification message sent by the second vbrs-CP device, where the first heartbeat notification message includes a first identifier list configured in a disaster recovery backup group in the second vbrs-CP device, and the first identifier list includes a first UP device identifier;
a determining unit, configured to obtain a second identifier list configured by a disaster recovery backup group in the first vbrs-CP device, and determine whether the first UP device identifier already exists in the second identifier list;
an identifying unit, configured to identify, if the first UP device identifier already exists in the second identifier list, a configuration state of a first UP device corresponding to the first UP device identifier in the first identifier list and the second identifier list, respectively;
a processing unit, configured to close a user access function of the first UP device if the configuration state of the first UP device in the second identifier list is a configured state and the configuration state in the first identifier list is updated from the configured state to an unconfigured state;
a sending unit, configured to send a first notification message to the first UP device, so that the first UP device does not send a user service packet to the first vbrs-CP device.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011055551.XA CN112367182B (en) | 2020-09-29 | 2020-09-29 | Configuration method and device of disaster recovery main and standby equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011055551.XA CN112367182B (en) | 2020-09-29 | 2020-09-29 | Configuration method and device of disaster recovery main and standby equipment |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112367182A true CN112367182A (en) | 2021-02-12 |
| CN112367182B CN112367182B (en) | 2022-05-27 |
Family
ID=74506853
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011055551.XA Active CN112367182B (en) | 2020-09-29 | 2020-09-29 | Configuration method and device of disaster recovery main and standby equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112367182B (en) |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113794581A (en) * | 2021-08-05 | 2021-12-14 | 新华三大数据技术有限公司 | Distributed CP unified deployment method, network equipment and storage medium |
| CN114095342A (en) * | 2021-10-21 | 2022-02-25 | 新华三大数据技术有限公司 | Method and device for realizing backup |
| WO2023274164A1 (en) * | 2021-06-28 | 2023-01-05 | 中兴通讯股份有限公司 | Automatic main/standby switching method, control plane device, vbras system and storage medium |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107623593A (en) * | 2017-08-31 | 2018-01-23 | 北京华为数字技术有限公司 | Method and device for dual-computer hot backup based on CU separation |
| CN108880917A (en) * | 2018-08-23 | 2018-11-23 | 华为技术有限公司 | Switching method and device of control surface equipment and switching control separation system |
| CN109889390A (en) * | 2019-03-13 | 2019-06-14 | 赛特斯信息科技股份有限公司 | The method for turning to realize HA hot-backup function under control separation scene |
| CN110830310A (en) * | 2019-11-28 | 2020-02-21 | 新华三大数据技术有限公司 | Cross-data-center disaster backup method and BRAS system |
| WO2020040547A1 (en) * | 2018-08-21 | 2020-02-27 | Samsung Electronics Co., Ltd. | Method for mission critical data (mcdata) file distribution optimization in mcdata client system |
-
2020
- 2020-09-29 CN CN202011055551.XA patent/CN112367182B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107623593A (en) * | 2017-08-31 | 2018-01-23 | 北京华为数字技术有限公司 | Method and device for dual-computer hot backup based on CU separation |
| WO2020040547A1 (en) * | 2018-08-21 | 2020-02-27 | Samsung Electronics Co., Ltd. | Method for mission critical data (mcdata) file distribution optimization in mcdata client system |
| CN108880917A (en) * | 2018-08-23 | 2018-11-23 | 华为技术有限公司 | Switching method and device of control surface equipment and switching control separation system |
| CN109889390A (en) * | 2019-03-13 | 2019-06-14 | 赛特斯信息科技股份有限公司 | The method for turning to realize HA hot-backup function under control separation scene |
| CN110830310A (en) * | 2019-11-28 | 2020-02-21 | 新华三大数据技术有限公司 | Cross-data-center disaster backup method and BRAS system |
Cited By (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2023274164A1 (en) * | 2021-06-28 | 2023-01-05 | 中兴通讯股份有限公司 | Automatic main/standby switching method, control plane device, vbras system and storage medium |
| CN113794581A (en) * | 2021-08-05 | 2021-12-14 | 新华三大数据技术有限公司 | Distributed CP unified deployment method, network equipment and storage medium |
| CN113794581B (en) * | 2021-08-05 | 2023-11-07 | 新华三大数据技术有限公司 | Distributed CP unified deployment method, network equipment and storage medium |
| CN114095342A (en) * | 2021-10-21 | 2022-02-25 | 新华三大数据技术有限公司 | Method and device for realizing backup |
| CN114095342B (en) * | 2021-10-21 | 2023-12-26 | 新华三大数据技术有限公司 | Backup realization method and device |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112367182B (en) | 2022-05-27 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| JP7438202B2 (en) | UE migration methods, devices, systems, and storage media | |
| CN111225401B (en) | Method and related equipment for realizing disaster tolerance | |
| CN112367182B (en) | Configuration method and device of disaster recovery main and standby equipment | |
| CN110535676B (en) | SMF dynamic disaster tolerance realization method, device, equipment and storage medium | |
| EP3490224A1 (en) | Data synchronization method and system | |
| US20210037456A1 (en) | Method and network device for selecting service network, and management device | |
| US20210105664A1 (en) | Communication system, communication control apparatus, node apparatus, and communication method | |
| US8284672B2 (en) | System and method for path failure recovery in a communications environment | |
| CN109995844B (en) | Method and device for realizing control plane resource migration and network function entity | |
| CN107404509B (en) | Distributed service configuration system and information management method | |
| CN105338078A (en) | Data storage method and device used for storing system | |
| CN110943928B (en) | Method for synchronizing forwarding information states, controller, network forwarding device and storage medium | |
| US20130139178A1 (en) | Cluster management system and method | |
| WO2021004517A1 (en) | Method, device and system for implementing core network sub-slice disaster recovery | |
| CN112367252B (en) | Method and device for realizing disaster recovery backup | |
| CN104272789B (en) | Mobile communication system, call processing node and communication control method | |
| CN109189854B (en) | Method and node equipment for providing continuous service | |
| EP3570169A1 (en) | Method and system for processing device failure | |
| US10122540B2 (en) | Device and method for managing multicast group in wireless network | |
| CN109344202B (en) | Data synchronization method and management node | |
| CN113821342B (en) | Method, device, equipment and readable medium for balancing cluster websocket service load | |
| CN114095342B (en) | Backup realization method and device | |
| CN112437146B (en) | A device state synchronization method, device and system | |
| CN114301763B (en) | Distributed cluster fault processing method and system, electronic equipment and storage medium | |
| CN116744352A (en) | Network disaster recovery method, device and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |