WO2016045439A1

WO2016045439A1 - Vnfm disaster-tolerant protection method and device, nfvo and storage medium

Info

Publication number: WO2016045439A1
Application number: PCT/CN2015/084609
Authority: WO
Inventors: 施政法
Original assignee: 中兴通讯股份有限公司
Priority date: 2014-09-25
Filing date: 2015-07-21
Publication date: 2016-03-31
Also published as: CN105577408A

Abstract

Disclosed is a VNFM disaster-tolerant protection method. The method comprises: after determining that a VNFM is abnormal, stopping all operations related to the abnormal VNFM, and creating a new VNFM according to information about the abnormal VNFM; mounting a shared disk which stores abnormal VNFM running data and is already downloaded from the abnormal VNFM at the new VNFM; and after determining that the new VNFM runs normally, updating VNFM information stored on an NFVO and all VNF entities managed by the abnormal VNFM, and starting a management process of the new VNFM after the update is completed. Also disclosed at the same time are a VNFM disaster-tolerant protection device, an NFVO and a storage medium.

Description

Method, device and NFVO, storage medium for VNFM disaster tolerance protection

Technical field

The present invention relates to the field of virtualization technologies in mobile communications, and in particular, to a virtual network function manager (VNFM) disaster tolerance protection method, device, and network function virtualization coordinator (NFV) , storage media.

Background technique

Currently, according to the European Telecommunications Standardization Institute (ETSI) Network Function Virtualization (NFV) specification, VNFM is mainly responsible for the management of virtual network function (VNF) entities in the system. According to the definition of the ETSI NFV specification, the lifecycle management of a VNF entity includes operations such as instantiation, elastic scaling, shrinking, and instance termination, all of which require the participation of VNFM. On the one hand, the VNFM interacts with the VNF entity to monitor the state of the VNF entity, shield the private characteristics of the VNF entity, complete the software deployment and data configuration of the VNF entity, and on the other hand, the VNFM interacts with the NFVO to provide operations for the NFVO. The necessary verification and feedback of the virtual resource information required for the operation. Therefore, if the VNFM does not work properly, the management of the VNF entity cannot be performed correctly. Therefore, an effective disaster recovery protection mechanism must be proposed for the VNFM.

At present, in the communication field, for the disaster recovery protection of network element equipment, the protection mechanism of the dual-machine primary and backup is usually adopted. However, for VNFM deployed on a virtualization platform, the following disadvantages exist:

When the active and standby machines are abnormal at the same time, they cannot play the role of protection. Two sets of resources are required to be occupied at the same time. The resource utilization is not high. The data synchronization between the primary and backup machines consumes a large amount of resources. Manual intervention is required to restore the abnormality. Host, otherwise it will not provide subsequent protection.

Summary of the invention

In order to solve the existing technical problems, the embodiments of the present invention provide a VNFM disaster tolerance protection method and apparatus, and an NFVO and a storage medium.

An embodiment of the present invention provides a VNFM disaster recovery protection method, where the method includes:

After determining the VNFM abnormality, stopping all operations related to the abnormal VNFM, and creating a new VNFM according to the information of the abnormal VNFM;

Mounting a shared disk that has stored the abnormal VNFM operation data and has been unloaded from the abnormal VNFM on a new VNFM;

After determining that the new VNFM is operating normally, the VNFM information stored on the NFVO and all the VNF entities managed by the abnormal VNFM is updated, and the management process of the new VNFM is started after the update is completed.

Wherein the shared disk is: a shared disk on the virtualization platform, correspondingly,

The mounting of the shared disk on the new VNFM includes: mounting the shared disk by using the mount command;

The method for uninstalling the shared disk includes: uninstalling the shared disk by uninstalling the unmount command.

The creating a new VNFM according to the information of the abnormal VNFM includes:

Create a new VNFM on the virtualization platform according to the virtual machine specification, network parameters, and software information of the abnormal VNFM, and apply to the virtualized infrastructure manager VIM to create a virtual resource required for creating a new VNFM during the creation process, and Deploy software programs to the new VNFM.

The VNFM information stored on the NFVO and all VNF entities managed by the abnormal VNFM includes:

The VNFM information change request is sent to all the VNF entities managed by the abnormal VNFM by the new VNFM, and after receiving the change request, each VNF entity updates its stored VNFM information, and returns a change completion response through the new VNFM. To the NFVO, the The NFVO updates the VNFM information stored by itself.

In one embodiment, the method further includes:

Monitor the operation of VNFM for abnormalities through heartbeat information.

The determining whether the VNFM is abnormal includes:

Sending heartbeat information to the VNFM. If the heartbeat response returned by the VNFM is received, it is determined that the VNFM is running normally; otherwise, it is checked whether the maximum number of consecutive attempts to send heartbeat information to the VNFM is exceeded. If not, the system waits for the next time. A heartbeat response, otherwise, it is determined that the VNFM is operating abnormally.

In one embodiment, the method further includes:

After the new VNFM starts performing the management operation, the resources of the abnormal VNFM are released, and the information of the abnormal VNFM stored on the NFVO is deleted.

Embodiments of the present invention also provide a storage medium including a set of instructions that, when executed, cause at least one processor to perform the operations described above.

The embodiment of the present invention further provides a VNFM disaster recovery protection device, where the device includes: a VNFM monitoring module and a VNFM disaster tolerance module;

The VNFM monitoring module is configured to: after determining that the VNFM is abnormal, triggering the VNFM disaster tolerance module;

The VNFM disaster tolerance module is configured to stop all operations related to the abnormal VNFM under the trigger of the VNFM monitoring module, and create a new VNFM according to the abnormal VNFM information; the abnormal VNFM will be stored A shared disk that runs data and has been unmounted from the abnormal VNFM is mounted on the new VNFM;

It is further configured to update the VNFM information stored on the NFVO and all the VNF entities managed by the abnormal VNFM after the new VNFM is running normally, and start the management process of the new VNFM after the update is completed.

In an embodiment, the VNFM monitoring module is further configured to monitor by heartbeat information. Whether the operation of VNFM is abnormal.

In one embodiment, the VNFM disaster tolerance module is further configured to release the resource of the abnormal VNFM after the new VNFM starts performing the management operation, and delete the information of the abnormal VNFM stored on the NFVO.

Embodiments of the present invention also provide an NFVO that includes the apparatus described above.

The VNFM disaster tolerance protection method and apparatus and the NFVO and the storage medium provided by the embodiments of the present invention, after determining the VNFM abnormality, stop all operations related to the abnormal VNFM, and create a new VNFM according to the abnormal VNFM information; A shared disk that stores abnormal VNFM operation data and has been unloaded from the abnormal VNFM is mounted on the new VNFM; after the new VNFM is determined to be operating normally, the NFVO is updated and stored on all VNF entities managed by the abnormal VNFM. The VNFM information, after the update is completed, starts the new VNFM management process. Compared with the prior art, the embodiment of the present invention reduces the storage and resource overhead of the synchronization of the active and standby data of the disaster recovery system by dynamically mounting the shared disk. Moreover, the solution can be automatically deployed and automatically applied on the virtualization platform. The feature of the resource is that the fault re-emergence mechanism is used to replace the traditional dual-system active/standby disaster recovery, which avoids the disadvantage that the faulty host of the dual-system active/standby solution cannot be automatically recovered. In addition, the abnormal reply of the embodiment of the present invention does not require manual participation. The automatic operation of the system.

DRAWINGS

In the drawings, which are not necessarily to scale, the Like reference numerals with different letter suffixes may indicate different examples of similar components. The drawings generally illustrate the various embodiments discussed herein by way of example and not limitation.

1 is a schematic flowchart of a method for implementing VNFM disaster recovery protection according to an embodiment of the present invention;

2 is a schematic diagram of migration of a shared disk according to an embodiment of the present invention;

3 is a schematic structural diagram of a VNFM disaster recovery protection device according to an embodiment of the present invention;

4 is a schematic structural diagram of an NFVO according to an embodiment of the present invention;

FIG. 5 is a flowchart of a VNFM disaster tolerance decision according to an embodiment of the present invention;

FIG. 6 is a flowchart of VNFM disaster tolerance according to an embodiment of the present invention;

FIG. 7 is a flowchart of updating VNFM information according to an embodiment of the present invention.

detailed description

In the embodiment of the present invention, after determining the VNFM abnormality, all operations related to the abnormal VNFM are stopped, and a new VNFM is created according to the abnormal VNFM information; an abnormal VNFM running data is stored, and the abnormal VNFM has been stored. The shared disk that is unloaded is mounted on the new VNFM; after the new VNFM is determined to be running normally, the VNFM information stored on the NFVO and all VNF entities managed by the abnormal VNFM is updated, and the management of the new VNFM is started after the update is completed. The process, that is, the management operation is started by the new VNFM instead of the abnormal VNFM.

The present invention will be further described in detail below with reference to the accompanying drawings and specific embodiments.

FIG. 1 is a schematic flowchart of a method for implementing VNFM disaster recovery protection according to an embodiment of the present invention. As shown in FIG. 1 , the method includes:

Step 101: After determining the VNFM abnormality, stop all operations related to the abnormal VNFM, and create a new VNFM according to the information of the abnormal VNFM;

In the embodiment of the present invention, after determining that the VNFM is abnormal, the NFVO stops receiving all operation requests related to the abnormal VNFM, and of course, the VNFM itself does not perform any management operation; according to the abnormal VNFM information, such as: virtual machine specifications. Create a new VNFM on the virtualization platform, network parameters, and software information. During the creation process, you need to apply to the Virtualization Infrastructure Manager (VIM) to create virtual resources needed for the new VNFM and deploy to the new VNFM. software program.

Step 102: Mount a shared disk that has been stored with abnormal VNFM operation data and has been uninstalled from the abnormal VNFM on the new VNFM.

In the embodiment of the present invention, the shared disk on the virtualization platform, that is, the cloud disk is used to store the data of the VNFM runtime, and after the abnormality occurs, the shared disk is unloaded from the abnormal VNFM and Mounted to the new VNFM, the mount of the shared disk can be completed by the mount command.

In the actual operation process, NFVO can create the shared disk through the virtualization platform instruction, and connect the shared disk to the specified virtual machine when instantiating the VNFM, and can complete the mounting of the shared disk by using a mount command; The unloading of the shared disk can be completed by using the unmount command. After the VNFM exception is determined, the shared disk can be unloaded from the abnormal VNFM.

Here, the migration of the shared disk can quickly migrate the data that needs to be migrated on the abnormal VNFM to the new VNFM, and avoid the real-time data synchronization necessary for the local disk. For the basic principle, see the migration diagram of the shared disk shown in Figure 2. . The solution requires that the VNFM software program be separated from the data file, that is, stored on the local disk of the VNFM virtual machine and the shared disk of the virtualization platform.

The shared disk of the virtualization platform used in the embodiment of the present invention can further enhance the reliability of the disk disaster recovery solution provided by the virtualization platform.

Step 103: After determining that the new VNFM is running normally, update the VNFM information stored on the NFVO and all the VNF entities managed by the abnormal VNFM, and start the management process of the new VNFM after the update is completed;

Specifically, the NFVO can monitor whether the new VNFM is running normally through the heartbeat information, and after determining that it is running normally, send a VNFM information change request to all the VNF entities managed by the abnormal VNFM through the new VNFM, and each VNF entity receives the request. After the change request, the VNFM information stored by itself is updated, for example, an IP address, and the response is returned to the NFVO through the new VNFM, and the NFVO updates the VNFM information stored by itself, and the new VNFM management process is started after the update is completed. That is: the management operation is started by the new VNFM instead of the abnormal VNFM.

Here, although the new VNFM is created by the NFVO, in addition to the information of the new VNFM itself, the new VNFM and all VNF entities it manages are created during the creation process. The connection information and other NFVO are not known. The NFVO updates its own stored VNFM information, which is a fixed storage space in which the VNFM information cached when a new VNFM is created is stored in the NFVO.

Compared with the prior art, the embodiment of the present invention reduces the storage and resource overhead of the synchronization of the active and standby data of the disaster recovery system by dynamically mounting the shared disk. Moreover, the solution can be automatically deployed and automatically applied on the virtualization platform. The feature of the resource is that the fault re-emergence mechanism is used to replace the traditional dual-system active/standby disaster recovery, which avoids the disadvantage that the faulty host of the dual-system active/standby solution cannot be automatically recovered. In addition, the abnormal reply of the embodiment of the present invention does not require manual participation. The automatic operation of the system.

In addition, the solution is also repetitive, that is, no matter how many times the VNFM fails, a new VNFM can be generated to take over and ensure the normal operation of the system.

Preferably, in an embodiment of the present invention, the method further includes: monitoring whether the operation of the VNFM is abnormal through the heartbeat information, specifically,

After the NFVO sends the heartbeat information to the VNFM, if the heartbeat response returned by the VNFM is received, it is determined that the VNFM is running normally; otherwise, it is checked whether the maximum number of retries is exceeded, that is, the maximum number of consecutive heartbeat messages continuously sent to the VNFM is set. If not exceeded, wait for the next heartbeat response, otherwise, determine that the VNFM is running abnormally.

Preferably, in an embodiment of the present invention, the method further includes: after the new VNFM starts performing the management operation, releasing the resource of the abnormal VNFM, and deleting the information of the abnormal VNFM stored on the NFVO.

Here, the timely recovery of abnormal VNFM resources ensures efficient use of resources on the virtualization platform.

Embodiments of the present invention also provide a computer readable storage medium comprising a set of instructions that, when executed, cause at least one processor to perform the operations described above.

The embodiment of the present invention further provides a VNFM disaster recovery protection device, as shown in FIG. 3, the device includes: a VNFM monitoring module 301 and a VNFM disaster tolerance module 302;

The VNFM monitoring module 301 is configured to trigger the VNFM disaster tolerance module after determining that the VNFM is abnormal.

The VNFM disaster tolerance module 302 is configured to stop all operations related to the abnormal VNFM under the trigger of the VNFM monitoring module 301, and create a new VNFM according to the abnormal VNFM information; an abnormal VNFM will be stored. A shared disk that is running data and has been unmounted from the abnormal VNFM is mounted on the new VNFM;

In practical applications, the VNFM monitoring module 301 and the VNFM disaster tolerance module 302 may be a central processing unit (CPU), a digital signal processor (DSP), or a programmable logic array (Field-Programmable Gate). Array, FPGA) implementation.

In the embodiment of the present invention, after the VNFM disaster recovery module 302 determines that the VNFM is abnormal, it stops receiving all operation requests related to the abnormal VNFM, and of course, the VNFM itself does not perform any management operation; according to the abnormal VNFM information. For example, virtual machine specifications, network parameters, and software information are used to create a new VNFM on the virtualization platform. During the creation process, VIM is required to create a virtual resource required for creating a new VNFM, and deploy a software program to the new VNFM. .

In the embodiment of the present invention, the shared disk on the virtualization platform, that is, the cloud disk, is used to store the data of the VNFM runtime. After the abnormality occurs, the VNFM disaster recovery module 302 unloads and mounts the shared disk from the abnormal VNFM. On the new VNFM, the mount of the shared disk can be done by the mount command.

During the actual operation, the VNFM disaster tolerance module 302 can create the shared disk by using a virtualization platform instruction, and connect the shared disk to the specified virtual machine when instantiating the VNFM. The mount command completes the mount of the shared disk. Correspondingly, the unmount command can be used to unmount the shared disk. After the VNFM exception is determined, the shared disk can be unloaded from the abnormal VNFM.

Preferably, in an embodiment of the present invention, the VNFM monitoring module 301 is further configured to monitor whether the operation of the VNFM is abnormal through the heartbeat information; specifically,

After the VNFM monitoring module 301 sends the heartbeat information to the VNFM, if the heartbeat response returned by the VNFM is received, it is determined that the VNFM is running normally; otherwise, it is checked whether the maximum number of retries is exceeded, that is, the set frequent test sends a heartbeat to the VNFM. The maximum number of times of information, if not exceeded, waits for the next time, otherwise, it is determined that the VNFM is operating abnormally.

Preferably, in an embodiment of the present invention, the VNFM disaster tolerance module 302 is further configured to: after the new VNFM starts performing a management operation, release the resource of the abnormal VNFM, and delete the abnormality stored on the NFVO. VNFM information.

The embodiment of the present invention further provides an NFVO. As shown in FIG. 4, the NFVO 40 includes the VNFM disaster recovery protection device described above.

Compared with the prior art, the embodiment of the present invention reduces the storage and resource overhead of the synchronization of the active and standby data of the disaster recovery system by dynamically mounting the shared disk. Moreover, the solution utilizes the virtualization platform. On the other hand, the fault can be automatically deployed and automatically applied for the resource. The fault re-emergence mechanism is used to replace the traditional dual-system active/standby disaster recovery. The response does not require manual participation, and the automatic operation of the system is realized.

The implementation of the technical solution of the present invention will be further described in detail below with reference to the accompanying drawings and specific embodiments. In this embodiment, the VNFM monitoring module and the VNFM disaster tolerant module are set on the NFVO, and the interface message change between the NFVO-VNFM and the VNFM-VNF entity is involved. The technical solution of the present invention is described as follows in three embodiments. :

Embodiment 1: The abnormal monitoring process of the VNFM.

The VNFM monitoring module in the NFVO is responsible for monitoring the VNFM status and completing the decision of the disaster tolerance condition. The process is shown in Figure 5, including the following processing steps:

Step 501: NFVO starts normally, and VNFM and VNF are automatically deployed;

Step 502: The VNFM monitoring module acquires the deployed VNFM information, and sequentially sends a heartbeat message to the VNFM.

Step 503: The VNFM receives the heartbeat information sent by the VNFM monitoring module in the NFVO, and returns a response.

Step 504: The VNFM monitoring module receives the heartbeat response of the VNFM, and considers that the state is normal, waiting for the next heartbeat, otherwise proceeding to step 505;

Step 505: The VNFM monitoring module in the NFVO does not receive the heartbeat response of the VNFM, and checks whether the predefined maximum number of retries is exceeded, that is, whether the maximum number of consecutive heartbeat messages continuously sent to the VNFM is exceeded. If the maximum number of retries is not exceeded, the number of retries is incremented by one, waiting for the next heartbeat, otherwise step 506 is continued;

Step 506: The VNFM monitoring module in the NFVO does not receive the heartbeat response of the VNFM, and the maximum number of retries is reached, the disaster tolerance condition is established, and the notification is sent to the VNFM disaster recovery module. Inform them to begin the VNFM disaster recovery process.

Embodiment 2: VNFM disaster tolerance process.

The NFVO disaster recovery process is controlled by the VNFM disaster recovery module. The main tasks include the opening and closing of management status, the creation of new VNFM, the change of VNFM information, and the resource recovery of abnormal VNFM. The process is shown in Figure 6. The following processing steps:

Step 601: The VNFM monitoring module sends a disaster tolerance request to the VNFM disaster recovery module when the disaster tolerance condition is met.

Step 602: After receiving the request, the VNFM disaster tolerance module first sets the VNFM and the VNF entity managed by the VNFM to a management state, that is, does not allow subsequent operations;

Step 603: The VNFM disaster tolerance module starts to create and start a new VNFM.

Specifically, unmount the shared disk of the failed VNFM, and apply to VIM to create the virtual resources needed for the new VNFM, and deploy the software program to the new VNFM; then mount the shared disk to the new VNFM and start the new VNFM.

Step 604: The VNFM monitoring module monitors the new VNFM.

Step 605: After the heartbeat between the VNFM monitoring module and the new VNFM is normal, send an access completion notification to the VNFM disaster recovery module.

Step 606: After receiving the notification, the VNFM disaster recovery module completes updating the VNFM information on the NFVO and the VNF.

Step 607: The VNFM disaster recovery module releases the resources of the abnormal VNFM, and deletes related information stored on the NFVO.

Step 608: The VNFM opens the management state of the new VNFM and the VNF entity it manages, and the management operation can be performed normally.

Embodiment 3: VNFM information update process.

After the new VNFM is created and running normally, it is necessary to modify the VNFM information on the NFVO and VNF entities, such as the IP address, so that the new VNFM can take over the original VNFM. The managed VNF entity, see Figure 7, includes the following processing steps:

Step 701: The VNFM monitoring module sends a new VNFM access completion notification to the VNFM disaster recovery module.

Step 702: The VNFM disaster tolerance module sends a change VNFM request to the new VNFM.

Step 703: The new VNFM sends a change VNFM request to the VNF entity originally managed by the abnormal VNFM.

Step 704: After receiving the change request, each VNF entity updates the VNFM information stored by itself.

Step 705: Each VNF entity returns a change completion response to the new VNFM.

Step 706: After receiving the response of all the VNF entities, the new VNFM returns a response to the VNFM disaster recovery module.

Step 707: The VNFM disaster tolerance module updates the VNFM information on the NFVO.

Those skilled in the art will appreciate that embodiments of the present invention can be provided as a method, system, or computer program product. Accordingly, the present invention can take the form of a hardware embodiment, a software embodiment, or a combination of software and hardware. Moreover, the invention can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage and optical storage, etc.) including computer usable program code.

The present invention has been described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (system), and computer program products according to embodiments of the invention. It will be understood that each flow and/or block of the flowchart illustrations and/or FIG. These computer program instructions can be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing device to produce a machine for the execution of instructions for execution by a processor of a computer or other programmable data processing device. Means for implementing the functions specified in one or more of the flow or in a block or blocks of the flow chart.

The computer program instructions can also be stored in a computer readable memory that can direct a computer or other programmable data processing device to operate in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture comprising the instruction device. The apparatus implements the functions specified in one or more blocks of a flow or a flow and/or block diagram of the flowchart.

These computer program instructions can also be loaded onto a computer or other programmable data processing device such that a series of operational steps are performed on a computer or other programmable device to produce computer-implemented processing for execution on a computer or other programmable device. The instructions provide steps for implementing the functions specified in one or more of the flow or in a block or blocks of a flow diagram.

The above is only the preferred embodiment of the present invention and is not intended to limit the scope of the present invention.

Claims

A virtual network function manager VNFM disaster tolerance protection method, the method comprising:

After determining the VNFM abnormality, stopping all operations related to the abnormal VNFM, and creating a new VNFM according to the information of the abnormal VNFM;

Mounting a shared disk that has stored the abnormal VNFM operation data and has been unloaded from the abnormal VNFM on the new VNFM;

After determining that the new VNFM is running normally, the VNFM information stored on the network function virtualization coordinator NFVO and all the virtual network function VNF entities managed by the abnormal VNFM is updated, and the management process of the new VNFM is started after the update is completed.
The method of claim 1, wherein the shared disk is: a shared disk on a virtualization platform, correspondingly,

The mounting of the shared disk on the new VNFM includes: mounting the shared disk by using the mount command;

The method for uninstalling the shared disk includes: uninstalling the shared disk by uninstalling the unmount command.
The method of claim 1, wherein the creating a new VNFM based on the information of the abnormal VNFM comprises:

Create a new VNFM on the virtualization platform according to the virtual machine specification, network parameters, and software information of the abnormal VNFM, and apply to the virtualized infrastructure manager VIM to create a virtual resource required for creating a new VNFM during the creation process, and Deploy software programs to the new VNFM.
The method of claim 1, wherein the updating of the VNFM information stored on the NFVO and on all VNF entities managed by the abnormal VNFM comprises:

Sending a VNFM information change request to all VNF entities managed by the abnormal VNFM by the new VNFM, and each VNF entity updates its own storage after receiving the change request. VNFM information, and by the new VNFM return change completion response to the NFVO, the NFVO updates its own stored VNFM information.
The method of any of claims 1-4, wherein the method further comprises:

Monitor the operation of VNFM for abnormalities through heartbeat information.
The method of claim 5 wherein said determining whether the VNFM is abnormal comprises:

Sending heartbeat information to the VNFM. If the heartbeat response returned by the VNFM is received, it is determined that the VNFM is running normally; otherwise, it is checked whether the maximum number of consecutive attempts to send heartbeat information to the VNFM is exceeded. If not, the system waits for the next time. A heartbeat response, otherwise, it is determined that the VNFM is operating abnormally.
The method of any of claims 1-4, wherein the method further comprises:

After the new VNFM starts performing the management operation, the resources of the abnormal VNFM are released, and the information of the abnormal VNFM stored on the NFVO is deleted.
A VNFM disaster recovery protection device, the device includes: a VNFM monitoring module and a VNFM disaster tolerance module; wherein

The VNFM monitoring module is configured to: after determining that the VNFM is abnormal, triggering the VNFM disaster tolerance module;

The VNFM disaster tolerance module is configured to stop all operations related to the abnormal VNFM under the trigger of the VNFM monitoring module, and create a new VNFM according to the abnormal VNFM information; the abnormal VNFM will be stored A shared disk that runs data and has been unmounted from the abnormal VNFM is mounted on the new VNFM;

It is further configured to update the VNFM information stored on the NFVO and all the VNF entities managed by the abnormal VNFM after the new VNFM is running normally, and start the management process of the new VNFM after the update is completed.
The apparatus of claim 8, wherein the VNFM monitoring module is further configured to monitor whether the operation of the VNFM is abnormal by heartbeat information.
The device according to claim 8 or 9, wherein the VNFM disaster tolerance module is further configured to: after the new VNFM starts performing a management operation, release resources of the abnormal VNFM, and delete the stored on the NFVO Abnormal VNFM information.
A network function virtualization coordinator, NFVO, comprising the apparatus of any of claims 8-10.
A storage medium comprising a set of instructions that, when executed, cause at least one processor to perform the operations of any of claims 1-7.