WO2017107656A1 - 虚拟化网元故障自愈方法及装置 - Google Patents

虚拟化网元故障自愈方法及装置 Download PDF

Info

Publication number
WO2017107656A1
WO2017107656A1 PCT/CN2016/103518 CN2016103518W WO2017107656A1 WO 2017107656 A1 WO2017107656 A1 WO 2017107656A1 CN 2016103518 W CN2016103518 W CN 2016103518W WO 2017107656 A1 WO2017107656 A1 WO 2017107656A1
Authority
WO
WIPO (PCT)
Prior art keywords
fault
alarm
network element
fault alarm
virtualized network
Prior art date
Application number
PCT/CN2016/103518
Other languages
English (en)
French (fr)
Inventor
潘加强
Original Assignee
中兴通讯股份有限公司
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Publication of WO2017107656A1 publication Critical patent/WO2017107656A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/06—Management of faults, events, alarms or notifications
    • H04L41/0654—Management of faults, events, alarms or notifications using network fault recovery

Definitions

  • the present disclosure relates to the field of communications, for example, to a virtualized network element fault self-healing method and apparatus.
  • NFV network function virtualization
  • the fault alarms generated on the multiple virtualized network elements are also monitored.
  • the manual manual alarm elimination is required.
  • Corresponding fault handling is performed. Each fault alarm needs to be manually performed once. Therefore, manual real-time monitoring is required, and manual processing is repeated for some faults, which reduces work efficiency and wastes human resources.
  • the present disclosure provides a virtualized network element fault self-healing method and device, which reduces the phenomenon of manually monitoring the fault of the virtualized network element in real time.
  • the present disclosure provides a virtualized network element fault self-healing method for a telecommunications network function virtualization system, the method comprising:
  • the fault alarm is processed according to the fault handling rule.
  • the method before the fault alarm of the virtualized network element is monitored and received, the method further includes: setting a corresponding fault processing rule for different fault alarms, and saving the fault processing rule to a database,
  • the fault handling rule includes a fault elimination mode.
  • the method before the failure alarm is received, before the fault processing rule corresponding to the fault alarm is invoked from the database, the method further includes: determining whether there is a corresponding alarm in the database. If the fault handling rule corresponding to the fault alarm exists in the database, the fault processing rule corresponding to the fault alarm is directly invoked; if there is no fault corresponding to the fault alarm in the database Processing the rule, reporting the fault alarm, or determining the fault processing rule of the fault alarm by analyzing the processed fault alarm, and updating the fault processing rule to the database.
  • determining the fault processing rule of the fault alarm by analyzing the processed fault alarm includes: calling a fault processing record of the processed fault, and determining the processed fault and the fault alarm. Whether the fault content is the same or similar, if the processed fault is the same as or similar to the fault content of the fault alarm, the same fault elimination manner as the processed fault alarm is adopted, and the fault handling corresponding to the fault alarm is formed. rule.
  • the method further includes: when receiving the fault alarm, reading the network element identifier, where the network element identifier is used to record the virtualized network element that sends the fault alarm.
  • the method further includes: sending the processing result of the fault alarm to a virtualization network that reports the fault alarm yuan.
  • the fault processing rule corresponding to the fault alarm is called from the database; if the fault content of the fault alarm is not a self-healing fault, the fault alarm is directly reported.
  • the present disclosure also provides a virtualized network element fault self-healing device, including:
  • the monitoring module is configured to monitor a fault alarm of the virtualized network element and receive a fault alarm.
  • Processing module configured to: when receiving a fault alarm, invoke a fault handling rule corresponding to the fault alarm from a database;
  • Execution module configured to process the fault alarm according to the fault handling rule.
  • the apparatus further includes a setting module, configured to set a corresponding fault processing rule for different fault alarms before the fault alarm of the virtualized network element is monitored and received, and set the fault processing rule Saved to the database, the fault handling rule includes a fault elimination mode.
  • the processing module is further configured to: after receiving the fault alarm, before calling the fault processing rule corresponding to the fault alarm from the database, determining whether the fault alarm exists in the database Corresponding fault handling rules, if there is a fault handling rule corresponding to the fault alarm in the database, the fault processing rule corresponding to the fault alarm is directly invoked; if the database does not have the fault alarm corresponding to the fault alarm
  • the fault handling rule is to report the fault alarm, or to analyze the processed fault alarm, determine a fault handling rule of the fault alarm, and update the fault processing rule to a database.
  • the processing module is further configured to call a fault processing record of the processed fault, and determine whether the processed fault alarm is identical or similar to the fault content of the fault alarm;
  • the fault that has been processed is the same as or similar to the fault content of the fault alarm, and the same fault elimination mode as the processed fault alarm is used to form a fault processing rule corresponding to the fault alarm.
  • the device further includes a network element identifier reading module, configured to: when receiving the fault alarm, read the network element identifier, where the network element identifier is set to record and send the fault alarm. Virtualized network elements.
  • the apparatus further includes a processing result sending module, configured to send the processing result of the fault alarm to the reporting after processing the fault alarm according to the fault processing rule The virtualized network element of the fault alarm.
  • the processing module is further configured to: after receiving the fault alarm, determine whether the fault in the fault alarm can be self-healing; if the fault content of the fault alarm is self-healing, the method can be eliminated. If the fault content of the fault alarm is not a fault that can be eliminated by the self-healing, the fault alarm is directly reported.
  • the present disclosure also provides a non-transitory computer readable storage medium storing computer executable instructions arranged to perform the above method.
  • the present disclosure also provides an electronic device, the user equipment comprising:
  • At least one processor At least one processor
  • the memory stores instructions executable by the at least one processor, the instructions being executed by the at least one processor to cause the at least one processor to perform the method described above.
  • the present disclosure provides a virtualized network element fault self-healing method and device.
  • the virtualized network element fault self-healing device monitors, receives, and processes fault alarms, and the entire process is automatically executed by the virtualized network element fault self-healing device. No need to manually monitor faults in real time, which improves work efficiency and saves human resources.
  • FIG. 1 is a flowchart of a virtualized network element faulty device side in a virtualized network element fault self-healing method according to Embodiment 1 of the present disclosure
  • FIG. 2 is a flowchart of an embodiment of a virtualized network element faulty device in a virtualized network element fault self-healing method according to Embodiment 1 of the present disclosure
  • FIG. 3 is a schematic structural diagram of a virtualized network element fault self-healing device according to Embodiment 2 of the present disclosure
  • FIG. 5 is a schematic structural diagram of hardware of an electronic device according to an embodiment of the present disclosure.
  • Embodiment 1 is a diagrammatic representation of Embodiment 1:
  • the present embodiment provides a virtualized network element fault self-healing method.
  • the method for performing the virtualized network element faulty device on the virtualized network element faulty device side is described in FIG. 1.
  • the method includes steps 110 to 130. .
  • step 110 the fault alarm of the virtualized network element is monitored and accepted.
  • step 120 a fault handling rule corresponding to the fault alarm is invoked from the database.
  • step 130 the fault alarm is processed according to the fault handling rule.
  • the corresponding fault processing rule may be set for different fault alarms, and the set fault processing rule is saved to the database, and the fault processing rule generally includes a fault elimination manner. For example, you can set the virtualized network element to be started in advance. In the case of failure, the virtualized network element is restarted to eliminate the fault, and the virtualized network element is used to eliminate the fault when receiving the failure alarm that fails to restart the virtualized network element.
  • the fault handling rules corresponding to different fault alarm settings and fault alarms may be set by the user according to the actual situation, or may be selected according to the recommended default setting when installing the virtual machine, or may be a virtualized network element fault self-healing device. Set according to a variety of fault self-learnings that have been processed before.
  • the fault alarm received by the virtualized network element fault self-healing device includes a network element identifier, and the network element identifier is used to record the virtualized network element that sends the fault alarm, so that the virtualized network element fails to self-heal After the device invokes the corresponding processing rule, it can accurately determine which virtualized network element should be sent to the faulty processing result, so as to avoid the situation that the transmission error causes the fault handling error.
  • step 120 after the fault alarm is received, before the fault processing rule corresponding to the fault alarm is called from the database, it is usually required to determine whether there is a fault processing rule corresponding to the received fault alarm in the database.
  • step S120 includes steps 210 to 240.
  • step 210 a fault alert is received.
  • step 220 it is determined whether there is a fault processing rule corresponding to the received fault alarm in the database. If there is a fault processing rule corresponding to the fault alarm in the database, step 230 is performed, if the database does not exist. The fault processing rule corresponding to the fault alarm is executed 240.
  • step 230 the fault handling rule corresponding to the fault alarm is directly invoked.
  • step 240 the fault alarm is reported, or the corresponding fault processing rule is determined by the self-learning mode, and the fault processing rule is saved to the database.
  • a fault handling rule is set in advance: when the virtualized network element fails to start, the virtualized network element is restarted to eliminate the fault, and the fault processing rule is saved in the database.
  • the fault processing rule is saved in the database.
  • step 240 There is also a fault alarm that is received. There is no preset fault processing rule corresponding to the fault alarm. For this situation, the method in step 240 is often used.
  • the first method is to report the fault alarm to the administrator.
  • Another way is to determine the corresponding fault handling rules through self-learning.
  • the so-called self-learning method is that the reference has been processed.
  • the fault alarm, and the fault handling method of the fault alarm with the same or similar content as the alarm cause of the fault alarm, and the fault processing method is used as a processing means of the fault alarm, and the fault processing rule is invoked after obtaining the processing rule, and
  • the fault processing result is sent to the network element that reports the fault alarm, and the fault processing rule is updated to the database.
  • step 140 self-learning can be performed first to see whether the fault processing rule can be obtained through self-learning, and if the fault processing rule cannot be obtained through self-learning, and then reported; if the self-learning can be used to obtain the fault processing Rules, obtain the fault handling rules through self-learning, save the fault handling rules to the database, and notify the administrator, let the administrator know that the fault handling rules are obtained through self-learning; of course, you can choose not to send to the administrator. , eliminate the fault.
  • the entire process of eliminating the fault in the present disclosure is completed by the virtualized network element fault self-healing system itself, it is difficult for the extremely complicated faults, such as requiring the administrator to input a specific parameter value, to rely solely on the virtualized network element fault.
  • the self-healing system itself is completed, so naturally, in an embodiment of the embodiment, considering the achievability of the solution, after receiving the fault alarm, it is usually determined that the fault in the fault alarm is self-determinable. The more you still have to be involved by the administrator, the special handling method is faulty.
  • the so-called self-healing means that no manual participation is required, and the system automatically performs, for example, restarting or rebuilding, the process can be set to be automatically executed by the system, and if it is a self-healing failure, step 120 and the corresponding steps are performed. If it is necessary for the administrator to participate, the failure of the special handling mode is required to report the fault alarm, and the administrator determines the fault handling mode. This method can be used to perform the rough fault self-healing feasibility screening. The fault alarms that are not suitable for restarting or rebuilding are directly reported to the administrator. It is not necessary to perform subsequent reading of the database and the comparison and comparison steps. The workload of the virtual machine increases work efficiency and saves time and resources.
  • the virtualized network element uses the virtual resource to notify the virtualized network element that reports the fault alarm after the fault is removed.
  • the virtualized network element receives the virtual resource information.
  • the load balancing process is performed, and the virtualized network element can continue to work normally.
  • Embodiment 2 is a diagrammatic representation of Embodiment 1:
  • FIG. 3 A virtualized network element fault self-healing device provided in the second embodiment is shown in FIG. 3 .
  • the virtualized network element fault self-healing device 3 includes a listening module 31, a processing module 32, and an execution module 33.
  • the monitoring module 31 is configured to monitor a fault alarm of the virtualized network element and receive a fault alarm sent by the virtualized network element.
  • the processing module 32 is configured to invoke a corresponding fault handling rule from the database when the listening module 31 receives the fault alert.
  • the execution module 33 is configured to refer to the fault according to the fault processing rule The obstacle alarm is processed.
  • the virtualized network element performs fault processing according to the fault handling rule, and the fault can be eliminated without human intervention in the event of a fault.
  • the virtualized network element fault self-healing device 3 further includes a setting module 34.
  • the corresponding fault processing rule can be set for different fault alarms, and those faults are set.
  • the processing rules are saved to the database, and the fault handling rules usually include a corresponding way to eliminate faults for different fault alarm settings.
  • the fault handling rules corresponding to the fault alarms may be set by the user according to the actual situation, or may be selected according to the recommended default settings when installing the virtualized network element, or may be a virtualized network element fault.
  • the self-healing device is set up according to various fault self-learnings that have been processed before.
  • the virtualized network element fault self-healing device 3 further includes a network element identifier reading module 35, and the network element identifier reading module 35 is configured to read the network element when receiving the fault alarm.
  • the identifier of the network element is set to record the virtualized network element that sends the fault alarm. After the virtualized network element fault self-healing device invokes the corresponding processing rule, it can accurately determine which one should be sent to the fault processing result. Virtualize the network element to avoid the occurrence of a fault in the transmission error.
  • the processing module 32 of the virtualized network element fault self-healing device 3 is further configured to determine whether the fault in the fault alarm is self-determinable after receiving the fault alarm.
  • the more (for example, the most common self-healing means, by restarting or rebuilding the virtualized network element), the fault that must be taken by the administrator to take special treatment; if the fault content of the fault alarm is the fault in the fault alarm
  • the processing module 32 can directly call the corresponding fault processing rule from the database. If the fault content of the fault alarm is not a self-healing fault, the processing module 32 reports the fault alarm to notify the administrator. The administrator decides how to handle the fault. This method can be used to perform rough fault self-healing feasibility screening. For fault alarms that are not suitable for restart or reconstruction, they are directly reported to the administrator. There is no need to perform subsequent reading of the database, and the comparison and comparison steps are performed to improve the work. Efficiency, saving resources and time.
  • the processing module 32 in the virtualized network element fault self-healing device 3 is further configured to, after the monitoring module 31 receives the fault alarm, invoke a fault handling corresponding to the fault alarm from the database. Before the rule, it is determined whether there is a fault handling rule corresponding to the received fault alarm in the database. When the judgment result is that there is no fault corresponding to the received fault alarm in the database When the rule is ruled, the fault alarm is directly reported. When the result of the judgment is that the fault processing rule corresponding to the received fault alarm does not exist in the database, the fault processing rule corresponding to the fault alarm is determined by the self-learning mode, and the fault processing rule is saved to the database.
  • the so-called self-learning method refers to the fault alarm that has been processed, and looks at the fault handling method of the fault alarm similar to the alarm reason content of the fault alarm, and uses the fault processing method as a processing method of the fault alarm.
  • the fault handling rules are updated to the database after the processing rules are obtained.
  • the processing module 32 is further configured to call a fault handling record of the processed fault, determine whether the processed fault alert is identical or similar to the fault content of the received fault alert; and when the processed fault is received with the fault.
  • the fault content of the fault alarm is the same or similar, and the same fault elimination mode as the processed fault alarm is used to form a fault processing rule corresponding to the fault alarm.
  • the virtualized network element fault self-healing device 3 further includes a processing result sending module 36. Since the virtualized network element needs to use the resources of the virtual machine, the processing result sending module 36 is configured to notify the virtualized network element that reports the fault alarm, usually after the fault is eliminated. The virtualized network element receives the message of the fault elimination and enables the repaired virtual resource to continue to work normally.
  • VNF virtualized network function
  • VNFM virtualized network function manager
  • VNFM virtual infrastructure manager
  • VNF virtualized network function manager
  • VIM virtual infrastructure manager
  • a VNF is an example of virtualization of network functions that can be deployed in a virtualized or non-virtualized network. These network functions can be combined to form a network service, which can be deployed on a single virtual machine or across multiple virtual machines.
  • the VNF is also a virtualized network element. The description is clearer and is directly explained by VNFM, VIM and VNF.
  • step 410 a processing rule is defined on the VNFM.
  • the process includes: the user selects a virtualized network element that has been created, and sets a processing method when a specific alarm is received.
  • These specific alarms are alarms that need to be cleared by virtual machine operations (including restart or rebuild, etc.), such as virtual machine startup failure and abnormal module status. Set up to receive these notifications After the alarm is processed, the virtual machine is rebuilt after receiving the alarm that the virtual machine fails to start. If the module is abnormal, the virtual machine where the module is located is restarted.
  • step 420 the VIMM is subscribed to the VIM virtual resource alarm and the virtualized network element alarm. After the subscription is successful, the VIM and the network element send an alarm to the VNFM when there is an alarm.
  • step 430 on the VNFM, the virtualized network element fault self-healing process is started, and the self-healing process monitors the alarm messages sent by the VIM and the network element.
  • step 440 if there is an alarm that the VNF reporting module fails to the VNFM.
  • step 450 the VNFM queries the processing rule database for the processing rules of the alarm.
  • step 460 if the processing rule is to restart the virtual machine, the VNFM notifies the VNF to restart the virtual machine, and the VNF answers the VNFM and agrees to restart the virtual machine.
  • step 470 the VNFM notifies the VIM, carries the virtual machine ID, restarts the specified virtual machine, and the VIM responds to the VNFM, and the virtual machine restarts successfully.
  • step 480 if the processing rule is to rebuild the virtual machine, the VNFM notifies the VNF to rebuild the virtual machine, and then executes sequentially, and the VNF responds to the VNFM and agrees to rebuild the virtual machine.
  • step 490 the VNFM initiates a request to the VIM, carries the ID of the virtual machine, deletes the virtual machine, and returns the VIM to the virtual machine for deletion.
  • step 4100 the VNFM initiates a request to the VIM, carries the parameters for creating the virtual machine, creates a virtual machine, and the VIM returns to the virtual machine to be successfully created.
  • step 4110 the VNFM notifies the VNF of the creation of a successful message, informing the VNF to enable the virtual machine.
  • the process implemented on the VNFM in this example can also be implemented on the NFVO (Network Function Virtualization Orchestrator) and the EMS (Element Management System) to achieve the same processing effect.
  • NFVO Network Function Virtualization Orchestrator
  • EMS Electronic Management System
  • the virtualized network element fault self-device and system in this embodiment realizes self-healing without human intervention, does not require real-time monitoring by people, and the entire process is automatically executed, thereby improving work efficiency and saving human resources.
  • the present disclosure also provides a non-transitory computer readable storage medium storing computer executable instructions arranged to perform the method of any of the above embodiments.
  • the present disclosure also provides a hardware structure diagram of an electronic device.
  • the electronic device includes:
  • At least one processor 40 which is exemplified by a processor 40 in FIG. 5; and a memory 50, may further include a communication interface 60 and a bus 70.
  • the processor 40, the communication interface 60, and the memory 50 can complete communication with each other through the bus 70.
  • Communication interface 60 can be used for information transfer.
  • Processor 40 may invoke logic instructions in memory 50 to perform the methods of the above-described embodiments.
  • logic instructions in the memory 50 described above may be implemented in the form of software functional units and sold or used as separate products, and may be stored in a computer readable storage medium.
  • the memory 50 is a computer readable storage medium and can be used to store software programs, computer executable programs, program instructions or modules corresponding to the methods in the embodiments of the present disclosure.
  • the processor 40 executes the function application and the data processing by running the software program, the instruction or the module stored in the memory 50, that is, the virtualized network element fault self-healing method in the foregoing method embodiment.
  • the memory 50 may include a storage program area and an storage data area, wherein the storage program area may store an operating system, an application required for at least one function; the storage data area may store data created according to usage of the terminal device, and the like. Further, the memory 50 may include a high speed random access memory, and may also include a nonvolatile memory.
  • the technical solution of the present disclosure may be embodied in the form of a software product stored in a storage medium, including one or more instructions for causing a computer device (which may be a personal computer, a server, a network device, etc.) Performing all or part of the steps of the method of the embodiments of the present disclosure.
  • the foregoing storage medium may be a non-transitory storage medium, including: a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk, and the like.
  • the virtualized network element fault self-healing method and device provided by the embodiments of the present disclosure do not require manual real-time monitoring Controlling the failure of virtualized network elements improves work efficiency and saves human resources.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

本公开公开了一种虚拟化网元故障自愈方法及装置。其中，所述虚拟化网元故障自愈方法，包括：虚拟化网元故障自愈装置监听并接收虚拟化网元的故障告警，并从数据库中调用与该故障告警对应的故障处理规则；以及根据所述故障处理规则对该故障告警进行处理，消除所述故障。

Description

虚拟化网元故障自愈方法及装置 技术领域
本公开涉及通讯领域，例如涉及一种虚拟化网元故障自愈方法及装置。
背景技术
随着云计算技术的不断发展和成熟，云平台在多个领域得到了成功的运用。在此基础上，电信运营商为了提高通讯网络的灵活性，降低成本，提出了电信网络功能虚拟化(Network Functions Virtualization，NFV)概念。在虚拟化系统上由多种虚拟化网元来完成原来的物理网元设备所完成的工作，为了使多个网元能正常工作，通常还需要对多个虚拟化网元进行监控管理，方便在虚拟化网元产生故障后能及时对故障做出处理，恢复正常工作。
在相关技术中，也会监控多个虚拟化网元上产生的故障告警，但是在监控到虚拟化网元上的严重的故障告警后需要人为手动的执行告警消除，根据故障告警的详细内容，进行相应的故障处理，每产生一个故障告警都需要手动执行一次故障消除，因此，需要人工实时监控，并且对于一些故障手动重复处理，降低了工作效率，浪费了人力资源。
因此，提供一种能够对虚拟化网元的故障告警自动处理的虚拟化网元故障自愈方法是相关技术中亟需解决的问题。
发明内容
本公开提供了一种虚拟化网元故障自愈方法及装置，减少了人工实时监控虚拟化网元的故障的现象。
本公开提供了一种用于电信网络功能虚拟化系统的虚拟化网元故障自愈方法，所述方法包括：
监听并接收虚拟化网元的故障告警；
当接收到故障告警，从数据库中调用与所述故障告警对应的故障处理规则；以及
根据所述故障处理规则对所述故障告警进行处理。
在本公开一种实施例中，在监听并接收虚拟化网元的故障告警之前，所述方法还包括：针对不同故障告警设置对应的故障处理规则，并将所述故障处理规则保存至数据库，所述故障处理规则包括故障消除方式。
在本公开一种实施例中，在接收到故障告警之后，从数据库中调用与所述故障告警对应的故障处理规则之前，所述方法还包括：判断数据库中是否存在与所述故障告警相对应的故障处理规则，若数据库中存在与所述故障告警相对应的故障处理规则，则直接调用与所述故障告警相对应的故障处理规则；若数据库中不存在与所述故障告警相对应的故障处理规则，将所述故障告警上报，或者通过分析已处理的故障告警，确定所述故障告警的故障处理规则，并将所述故障处理规则更新到数据库。
在本公开一种实施例中，通过分析已处理的故障告警，确定所述故障告警的故障处理规则包括：调用已处理故障的故障处理记录，判断所述已处理的故障与所述故障告警的故障内容是否相同或相似，若所述已处理的故障与所述故障告警的故障内容相同或相似，则采用与所述已处理故障告警的相同故障消除方式，形成所述故障告警相应的故障处理规则。
在本公开一种实施例中，所述方法还包括：当接收到故障告警，读取网元标识，所述网元标识用于记录发送所述故障告警的虚拟化网元。
在本公开一种实施例中，在根据所述故障处理规则对所述故障告警进行处理之后，所述方法还包括：将所述故障告警的处理结果发送给上报所述故障告警的虚拟化网元。
在本公开一种实施例中，在接收到故障告警之后，判断所述故障告警的故障内容是否为自愈可以消除的故障，若所述故障告警的故障内容是自愈可以消除的故障，则从数据库中调用与所述故障告警对应的故障处理规则；若所述故障告警的故障内容不是自愈可以消除的故障，直接将所述故障告警上报。
本公开还提供一种虚拟化网元故障自愈装置，包括：
监听模块：设置为监听虚拟化网元的故障告警，接收故障告警；
处理模块：设置为当接收到故障告警，从数据库中调用与所述故障告警对应的故障处理规则；以及
执行模块：设置为根据所述故障处理规则对所述故障告警进行处理。
在本公开一种实施例中，所述装置还包括设置模块，设置为在监听并接收虚拟化网元的故障告警之前，针对不同故障告警设置对应的故障处理规则，并将所述故障处理规则保存至数据库，所述故障处理规则包括故障消除方式。
在本公开一种实施例中，所述处理模块还设置为，在接收到故障告警之后，从数据库中调用与所述故障告警对应的故障处理规则之前，判断数据库中是否存在与所述故障告警相对应的故障处理规则，若数据库中存在与所述故障告警相对应的故障处理规则，则直接调用与所述故障告警相对应的故障处理规则；若数据库中不存在与所述故障告警相对应的故障处理规则，将所述故障告警上报，或者通过分析已处理的故障告警，确定所述故障告警的故障处理规则，并将所述故障处理规则更新到数据库。
在本公开一种实施例中，所述处理模块还设置为调用已处理故障的故障处理记录，判断所述已处理的故障告警与所述故障告警的故障内容是否相同或相似；以及若所述已处理的故障与所述故障告警的故障内容相同或相似，采用与所述已处理故障告警的相同故障消除方式，形成所述故障告警相应的故障处理规则。
在本公开一种实施例中，所述装置还包括网元标识读取模块，设置为在接收到故障告警时，读取网元标识，所述网元标识设置为记录发送所述故障告警的虚拟化网元。
在本公开一种实施例中，所述装置还包括处理结果发送模块，设置为在根据所述故障处理规则对所述故障告警进行处理之后，将所述故障告警的处理结果发送给上报所述故障告警的虚拟化网元。
在本公开一种实施例中，所述处理模块还设置为，在接收到故障告警之后，判断所述故障告警中的故障是否可以自愈；若所述故障告警的故障内容是自愈可以消除的故障，从数据库中调用与所述故障告警对应的故障处理规则；若所述故障告警的故障内容不是自愈可以消除的故障，直接将所述故障告警上报。
本公开还提供了一种非暂态计算机可读存储介质，存储有计算机可执行指令，所述计算机可执行指令设置为执行上述方法。
本公开还提供了一种电子设备，该用户设备包括：
至少一个处理器；以及
与所述至少一个处理器通信连接的存储器；其中，
所述存储器存储有可被所述至少一个处理器执行的指令，所述指令被所述至少一个处理器执行，以使所述至少一个处理器执行上述的方法。
本公开提供了一种虚拟化网元故障自愈方法及装置，虚拟化网元故障自愈装置对故障告警进行监控、接收以及处理，整个过程都由虚拟化网元故障自愈装置自动执行，不需要人工实时监控故障，提高了工作效率，节省了人力资源。
附图说明
图1为本公开实施例一中的虚拟化网元故障自愈方法中虚拟化网元故障装置侧的工作流程图；
图2为本公开实施例一中的虚拟化网元故障自愈方法中虚拟化网元故障装置侧一种实施例的流程图；
图3为本公开实施例二中的虚拟化网元故障自愈装置的结构示意图；
图4为本公开实施例二中示例的工作流程图；以及
图5是本公开实施例提供的电子设备的硬件结构示意图。
具体实施方式
下面通过实施方式结合附图对本公开作详细说明。
实施例一：
本实施例提供一种虚拟化网元故障自愈方法，在完成虚拟化网元故障自愈时在虚拟化网元故障装置侧的执行方法请参考图1，所述方法包括步骤110至步骤130。
在步骤110中，监听并接受虚拟化网元的故障告警。
在步骤120中，从数据库中调用与所述故障告警对应的故障处理规则。
在步骤130中，根据所述故障处理规则对所述故障告警进行处理。
在执行步骤110中的监听虚拟化网元的故障告警之前，可以针对不同故障告警设置对应的故障处理规则，并将设置好的故障处理规则保存到数据库，故障处理规则通常包括故障消除的方式，例如，可以事先设定在虚拟化网元启动 失败时采用重启该虚拟化网元来消除该故障、在收到重启虚拟化网元失败的故障告警时采用重建该虚拟化网元来消除该故障。对于不同的故障告警设置与故障告警对应的故障处理规则，可以是由用户根据实际情况自行设置，也可以选择在安装虚拟机的时候根据推荐默认设置，也可以是虚拟化网元故障自愈装置根据之前已经处理过的多种故障自学习进行设置。
在本实施例中，虚拟化网元故障自愈装置接收到的故障告警中包括网元标识，该网元标识用于记录发送该故障告警的虚拟化网元，方便虚拟化网元故障自愈装置调用了相应的处理规则后，可以准确的确定应该将该故障处理结果发送给哪一个虚拟化网元，以免出现发送错误导致故障处理错误的情况。
对于步骤120，在接收到故障告警后，从数据库中调用与所述故障告警对应的故障处理规则前，通常还需要判断数据库中是否存在与收到的故障告警相对应的故障处理规则，此时，请参考图2，步骤S120包括步骤210至步骤240。
在步骤210中，接收故障告警。
在步骤220中，判断数据库中是否存在与接收到的该故障告警相对应的故障处理规则，若数据库中存在与所述故障告警相对应的故障处理规则，则执行步骤230，若数据库中不存在与所述故障告警相对应的故障处理规则，执行240。
在步骤230中，直接调用与该故障告警相对应的故障处理规则。
在步骤240中，将该故障告警上报，或者通过自学习方式确定相应的故障处理规则，并将该故障处理规则保存至数据库。
例如，事先设定了一条故障处理规则为：在虚拟化网元启动失败时采用重启该虚拟化网元来消除该故障，并将该故障处理规则保存在数据库中。在收到了一条虚拟化网元重启失败的故障告警时，查看数据库中存储的有没有处理网元启动失败的处理方法，查询数据库发现数据库中已经定义好当启动失败时，采用重启的方式即可，也即是存在了对应的故障处理规则，此时，只需要直接调用这条故障处理规则。
也会存在收到的故障告警没有预设的故障处理规则与该故障告警对应，针对这种情况往往会采用步骤240中的方式来进行，第一种方式是将该故障告警上报，由管理员来决定需要采用的故障消除方式，另外一种方式就是通过自学习的方式来确定相应的故障处理规则，所谓自学习方式，就是参考已经处理过 的故障告警，看与该故障告警的告警原因内容相同或相似的故障告警的故障处理方法，并将该故障处理方法作为该故障告警的处理手段，获得处理规则后调用所述故障处理规则，并发送故障处理结果至上报该故障告警的网元，并将所述故障处理规则更新到数据库。可以想到的是，在步骤140中可以先进行自学习，看能否通过自学习来获得故障处理规则，若不能通过自学习来获得故障处理规则，再上报；若可以通过自学习来获得故障处理规则，就通过自学习的方式获得故障处理规则，保存该故障处理规则到数据库的同时还通知管理员，让管理员知道本条故障处理规则通过自学习方式获得；当然也可以选择不发送给管理员，消除该故障。
由于本公开中，整个消除故障的过程仅靠虚拟化网元故障自愈系统自身完成，所以对于那些极其复杂的故障，比如需要管理员输入特定的参数值，是难以仅仅依靠虚拟化网元故障自愈系统自身来完成的，所以，自然也在本实施例的一种实施方式中，考虑到方案的可实现性，通常在接收到故障告警后，先判断该故障告警中的故障是可以自愈，还是必须要由管理员参与，采取特殊处理方式的故障。所谓自愈也即是不需要人工参与，系统自动执行，例如重启或重建，可以设置好流程由系统自动执行，如果是可以自愈的故障则执行步骤120以及接下来的相应步骤。如果是必须要由管理员参与，采取特殊处理方式的故障就需要将该故障告警上报，由管理员来决定故障处理方式。采用这种方法可以先进行粗略的故障自愈可行性的筛选，对于不适合采用重启或重建的故障告警直接上报给管理员，不需要执行后续的读取数据库以及进行判断比对等步骤，减少虚拟机的工作负担，提高工作效率，节约时间和资源。
由于虚拟化网元使用虚拟资源，在消除故障后，通常还要将消除故障后的虚拟资源的信息通知给上报该故障告警的虚拟化网元，虚拟化网元接收到虚拟资源的信息，可以对其进行负载均衡处理，虚拟化网元可以继续正常工作了。
实施例二：
本实施例二提供的一种虚拟化网元故障自愈装置，请参见图3。
虚拟化网元故障自愈装置3包括监听模块31、处理模块32和执行模块33。监听模块31设置为监听虚拟化网元的故障告警，并接收虚拟化网元发送的故障告警。处理模块32设置为在监听模块31接收到故障告警的时候，从数据库中调用相应的故障处理规则。执行模块33设置为根据所述故障处理规则对所述故 障告警进行处理。虚拟化网元按照该故障处理规则进行故障处理，在发生故障时不需要人为干预就能消除故障。
虚拟化网元故障自愈装置3还包括设置模块34，在监听模块31进行监听虚拟化网元上的故障告警之前，可以针对不同故障告警设置对应的故障处理规则，并将设置好的那些故障处理规则保存到数据库，故障处理规则通常包括针对不同故障告警设置对应的消除故障的方式。对于不同的故障告警设置与该故障告警对应的故障处理规则，可以是由用户根据实际情况自行设置，也可以选择在安装虚拟化网元的时候根据推荐默认设置，也可以是虚拟化网元故障自愈装置根据之前已经处理过的多种故障自学习进行设置。
在本实施例的一种实施方式中，虚拟化网元故障自愈装置3还包括网元标识读取模块35，网元标识读取模块35设置为在接收到故障告警时，读取网元标识，该网元标识设置为记录发送该故障告警的虚拟化网元，方便虚拟化网元故障自愈装置调用了相应的处理规则后，可以准确的确定应该将该故障处理结果发送给哪一个虚拟化网元，以免出现发送错误导致故障处理错误的情况。
由于本公开中，整个消除故障的过程仅靠虚拟化网元故障自愈系统自身完成，所以对于复杂的故障，是难以仅仅依靠虚拟化网元故障自愈系统自身来完成的，所以，在本实施例的一种实施方式中，考虑到方案的可实现性，虚拟化网元故障自愈装置3的处理模块32还设置为在接收到故障告警后，判断该故障告警中的故障是否可以自愈(例如，最常见的自愈手段，通过重启或重建虚拟化网元)，还是必须要由管理员参与，采取特殊处理方式的故障；如果所述故障告警的故障内容是故障告警中的故障是可以自愈的，则处理模块32直接从数据库中调用相应的故障处理规则，如果所述故障告警的故障内容不是自愈可以消除的故障，处理模块32将故障告警上报，通知管理员，由管理员来决定故障处理方式。采用这种方法可以进行粗略的故障自愈可行性的筛选，对于不适合采用重启或重建的故障告警直接上报给管理员，不需要执行后续的读取数据库，进行判断比对等步骤，提高工作效率，节约资源和时间。
在本实施例的一种实施方式中，虚拟化网元故障自愈装置3中的处理模块32还设置为在监听模块31接收到故障告警后，从数据库中调用与该故障告警对应的故障处理规则前，判断数据库中是否存在与收到的故障告警相对应的故障处理规则。当判断结果为数据库中不存在与接收到的故障告警相对应的故障处 理规则时，将该故障告警直接上报。当判断结果为数据库中不存在与接收到的故障告警相对应的故障处理规则时，通过自学习方式确定该故障告警相应的故障处理规则，并将该故障处理规则保存至数据库。所谓自学习方式，就是参考已经处理过的故障告警，看那些与该故障告警的告警原因内容等相似的故障告警的故障处理方法，并将该故障处理方法作为该故障告警的处理手段。获得处理规则后将所述故障处理规则更新到数据库。
处理模块32还设置为调用已处理故障的故障处理记录，判断所述已处理的故障告警与接收到的故障告警的故障内容是否相同或相似；以及当所述已处理的故障与所述接收到的故障告警的故障内容相同或相似，采用与所述已处理故障告警的相同故障消除方式，形成所述故障告警相应的故障处理规则。
在一种实施例中，虚拟化网元故障自愈装置3还包括处理结果发送模块36。由于虚拟化网元需要使用虚拟机的资源，处理结果发送模块36设置为在消除故障后通常还要将故障已经消除的消息通知给上报该故障告警的虚拟化网元。虚拟化网元接收到故障消除的消息，启用修复后的虚拟资源，就可以继续正常工作了。
实施例提供一个示例，来帮助理解本公开的方案，请参考图4。
在使用NFV技术的情况下，原来的物理网元设备由虚拟化网络功能(Virtualized Network Function，VNF)代替，使得网络功能与硬件解耦，VNF与底层的网络功能虚拟化基础架构(Network Functions Virtualization Infrastructure，NFVI)隔离。在本示例中，所述虚拟化网元自愈装置的功能由虚拟化网络功能管理器(VNF Manager，VNFM)管理器来完成，而虚拟基础设施管理器(Virtualised Infrastructure Manager，VIM)提供虚拟资源，另外，一个VNF是一个网络功能的虚拟化的实例，它可以部署在虚拟化或非虚拟化的网络中。这些网络功能可以共同形成一个网络服务，既可以部署在单个虚拟机上，也可以跨多个虚拟机部署，在本示例中VNF也即是一种虚拟化网元，在下面进行描述时，为了描述得更清晰，都直接采用VNFM、VIM和VNF来进行说明。
在步骤410中，在VNFM上定义处理规则。
该过程包括：用户选择已经创建好的虚拟化网元，设置收到特定的告警时处理方法。这些特定的告警是指需要通过虚拟机操作(包括重启或者重建等)才能清除的告警，如虚拟机启动失败以及模块状态异常等。设置在收到这些告 警后的处理规则，如在收到虚拟机启动失败的告警后，重建虚拟机，又如在收到模块状态异常，重启模块所在的虚机等。
在步骤420中，在VNFM上订阅VIM的虚拟资源的告警和虚拟化网元的告警(订阅成功后，VIM和网元有告警时会向VNFM发送告警)。
在步骤430中，在VNFM上，虚拟化网元故障自愈处理进程启动，自愈处理进程监听VIM和网元发来的告警消息。
在步骤440中，如这时如果有VNF上报模块失效的告警给VNFM。
在步骤450中，VNFM查询处理规则数据库中是否有这条告警的处理规则。
在步骤460中，如果处理规则是重启虚拟机，VNFM通知VNF要重启虚拟机，VNF给VNFM应答，同意重启虚拟机。
在步骤470中，VNFM通知VIM，携带虚拟机ID，重启指定的虚拟机，VIM给VNFM应答，虚拟机重启成功。
在步骤480中，如果处理规则是重建虚拟机，VNFM通知VNF重建虚拟机，再顺序执行，VNF给VNFM应答，同意重建虚拟机。
在步骤490中，VNFM向VIM发起请求，携带虚拟机的ID，将虚拟机删除，VIM返回虚拟机删除成功。
在步骤4100中，VNFM向VIM发起请求，携带创建虚拟机的参数，创建虚拟机，VIM返回虚拟机创建成功。
在步骤4110中，VNFM将创建成功的消息通知给VNF，通知VNF启用虚拟机。
本示例中在VNFM上实现的过程，也可以在NFVO(Network Function Virtualization Orchestrator，NFV编排器)和EMS(Element Management System，网元管理系统)上实现，能够达到同等的处理效果。
本实施例中的虚拟化网元故障自装置及系统，在不需要人为参与的情况下实现故障自愈，不需要人实时监控，整个过程自动执行，提高了工作效率，节省人力资源。
本公开还提供了一种非暂态计算机可读存储介质，存储有计算机可执行指令，所述计算机可执行指令设置为执行上述任一实施例中的方法。
本公开还提供了一种电子设备的硬件结构示意图。参见图5，该电子设备包括：
至少一个处理器(processor)40，图5中以一个处理器40为例；以及存储器(memory)50，还可以包括通信接口(Communications Interface)60和总线70。其中，处理器40、通信接口60、存储器50可以通过总线70完成相互间的通信。通信接口60可以用于信息传输。处理器40可以调用存储器50中的逻辑指令，以执行上述实施例的方法。
此外，上述的存储器50中的逻辑指令可以通过软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。
存储器50作为一种计算机可读存储介质，可用于存储软件程序、计算机可执行程序，如本公开实施例中的方法对应的程序指令或模块。处理器40通过运行存储在存储器50中的软件程序、指令或模块，从而执行功能应用以及数据处理，即实现上述方法实施例中的虚拟化网元故障自愈方法。
存储器50可包括存储程序区和存储数据区，其中，存储程序区可存储操作系统、至少一个功能所需的应用程序；存储数据区可存储根据终端设备的使用所创建的数据等。此外，存储器50可以包括高速随机存取存储器，还可以包括非易失性存储器。
本公开的技术方案可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括一个或多个指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本公开实施例所述方法的全部或部分步骤。而前述的存储介质可以是非暂态存储介质，包括：U盘、移动硬盘、只读存储器(ROM，Read-Only Memory)、随机存取存储器(RAM，Random Access Memory)、磁碟或者光盘等多种可以存储程序代码的介质，也可以是暂态存储介质。
以上内容是结合实施方式对本公开所作的详细说明，不能认定本公开的实施只局限于这些说明。对于本公开所属技术领域的普通技术人员来说，对本公开做出的简单推演或替换，都应当视为属于本公开的保护范围。
工业实用性
本公开实施例提供的虚拟化网元故障自愈方法及装置，不需要人工实时监 控虚拟化网元的故障，提高了工作效率，节省了人力资源。

Claims (15)

  1. 一种虚拟化网元故障自愈方法，包括：
    监听并接收虚拟化网元的故障告警；
    当接收到故障告警，从数据库中调用与所述故障告警对应的故障处理规则；以及
    根据所述故障处理规则对所述故障告警进行处理。
  2. 如权利要求1所述的虚拟化网元故障自愈方法，在监听并接收虚拟化网元的故障告警之前，所述方法还包括：针对不同故障告警设置对应的故障处理规则，并将所述故障处理规则保存至数据库，所述故障处理规则包括故障消除方式。
  3. 如权利要求1所述的虚拟化网元故障自愈方法，在接收到故障告警之后，从数据库中调用与所述故障告警对应的故障处理规则之前，所述方法还包括：判断数据库中是否存在与所述故障告警相对应的故障处理规则，若数据库中存在与所述故障告警相对应的故障处理规则，则直接调用与所述故障告警相对应的故障处理规则；若数据库中不存在与所述故障告警相对应的故障处理规则，将所述故障告警上报，或者通过分析已处理的故障告警，确定所述故障告警的故障处理规则，并将所述故障处理规则更新到数据库。
  4. 如权利要求3所述的虚拟化网元故障自愈方法，其中，通过分析已处理的故障告警，确定所述故障告警的故障处理规则包括：调用已处理故障的故障处理记录，判断所述已处理的故障与所述故障告警的故障内容是否相同或相似，若所述已处理的故障与所述故障告警的故障内容相同或相似，则采用与所述已处理故障告警的相同故障消除方式，形成所述故障告警相应的故障处理规则。
  5. 如权利要求1所述的虚拟化网元故障自愈方法，所述方法还包括：当接收到故障告警时，读取网元标识，所述网元标识用于记录发送所述故障告警的 虚拟化网元。
  6. 如权利要求1所述的虚拟化网元故障自愈方法，在根据所述故障处理规则对所述故障告警进行处理之后，所述方法还包括：将所述故障告警的处理结果发送给上报所述故障告警的虚拟化网元。
  7. 如权利要求1-6任意一项所述的虚拟化网元故障自愈方法，在接收到故障告警之后，判断所述故障告警的故障内容是否为自愈可以消除的故障，若所述故障告警的故障内容是自愈可以消除的故障，则从数据库中调用与所述故障告警对应的故障处理规则；若所述故障告警的故障内容不是自愈可以消除的故障，直接将所述故障告警上报。
  8. 一种虚拟化网元故障自愈装置，包括：
    监听模块，设置为监听虚拟化网元的故障告警，接收故障告警；
    处理模块，设置为当接收到故障告警，从数据库中调用与所述故障告警对应的故障处理规则；以及
    执行模块，设置为根据所述故障处理规则对所述故障告警进行处理。
  9. 如权利要求8所述的虚拟化网元故障自愈装置，所述装置还包括设置模块，设置为在监听并接收虚拟化网元的故障告警之前，针对不同故障告警设置对应的故障处理规则，并将所述故障处理规则保存至数据库，所述故障处理规则包括故障消除方式。
  10. 如权利要求8所述的虚拟化网元故障自愈装置，其中，所述处理模块还设置为，在接收到故障告警之后，从数据库中调用与所述故障告警对应的故障处理规则之前，判断数据库中是否存在与所述故障告警相对应的故障处理规则，若数据库中存在与所述故障告警相对应的故障处理规则，则直接调用与所述故障告警相对应的故障处理规则；若数据库中不存在与所述故障告警相对应的故 障处理规则，将所述故障告警上报，或者通过分析已处理的故障告警，确定所述故障告警的故障处理规则，并将所述故障处理规则更新到数据库。
  11. 如权利要求10所述的虚拟化网元故障自愈装置，其中，所述处理模块还设置为调用已处理故障的故障处理记录，判断所述已处理的故障告警与所述故障告警的故障内容是否相同或相似；以及若所述已处理的故障与所述故障告警的故障内容相同或相似，采用与所述已处理故障告警的相同故障消除方式，形成所述故障告警相应的故障处理规则。
  12. 如权利要求8所述的虚拟化网元故障自愈装置，所述装置还包括网元标识读取模块，设置为在接收到故障告警时，读取网元标识，所述网元标识设置为记录发送所述故障告警的虚拟化网元。
  13. 如权利要求8所述的虚拟化网元故障自愈装置，所述装置还包括处理结果发送模块，设置为在根据所述故障处理规则对所述故障告警进行处理之后，将所述故障告警的处理结果发送给上报所述故障告警的虚拟化网元。
  14. 如权利要求8-13任意一项所述的虚拟化网元故障自愈装置，其中，所述处理模块还设置为，在接收到故障告警之后，判断所述故障告警中的故障是否可以自愈；若所述故障告警的故障内容是自愈可以消除的故障，从数据库中调用与所述故障告警对应的故障处理规则；若所述故障告警的故障内容不是自愈可以消除的故障，直接将所述故障告警上报。
  15. 一种非暂态计算机可读存储介质，存储有计算机可执行指令，所述计算机可执行指令设置为执行权利要求1-7中任一项的方法。
PCT/CN2016/103518 2015-12-25 2016-10-27 虚拟化网元故障自愈方法及装置 WO2017107656A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201510995290.2A CN106921508B (zh) 2015-12-25 2015-12-25 虚拟化网元故障自愈方法及装置
CN201510995290.2 2015-12-25

Publications (1)

Publication Number Publication Date
WO2017107656A1 true WO2017107656A1 (zh) 2017-06-29

Family

ID=59088958

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2016/103518 WO2017107656A1 (zh) 2015-12-25 2016-10-27 虚拟化网元故障自愈方法及装置

Country Status (2)

Country Link
CN (1) CN106921508B (zh)
WO (1) WO2017107656A1 (zh)

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020252902A1 (zh) * 2019-06-18 2020-12-24 平安科技（深圳）有限公司 云服务器自检方法、装置、设备及计算机可读存储介质
CN112650642A (zh) * 2020-12-07 2021-04-13 深圳前海微众银行股份有限公司 一种告警处理方法及装置、设备、存储介质
CN113704046A (zh) * 2020-05-21 2021-11-26 中移(苏州)软件技术有限公司 一种故障告警处理方法及装置、设备、存储介质
WO2022127504A1 (zh) * 2020-12-14 2022-06-23 武汉绿色网络信息服务有限责任公司 网元管理方法、装置及存储介质

Families Citing this family (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109391481A (zh) * 2017-08-02 2019-02-26 中国电信股份有限公司 虚拟化网元故障自愈方法和装置
CN107332722A (zh) * 2017-08-31 2017-11-07 郑州云海信息技术有限公司 一种故障信息的排除方法及系统
CN110868309A (zh) * 2018-08-27 2020-03-06 中移(苏州)软件技术有限公司 Vnfm中资源处理的方法、装置及计算机存储介质
CN110430071A (zh) * 2019-07-19 2019-11-08 云南电网有限责任公司信息中心 业务节点故障自愈方法、装置、计算机设备及存储介质
CN110601894B (zh) * 2019-09-18 2023-07-25 中国工商银行股份有限公司 告警处理方法和装置、以及电子设备和可读存储介质
CN114928533B (zh) * 2022-06-13 2024-02-23 中国电信股份有限公司 虚拟网元故障处理方法、装置、电子设备及存储介质

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1878384A (zh) * 2006-07-10 2006-12-13 华为技术有限公司 一种网元故障检测方法
CN101867958A (zh) * 2010-06-18 2010-10-20 中兴通讯股份有限公司 管理无线传感网终端的方法和系统
CN104754629A (zh) * 2013-12-31 2015-07-01 中兴通讯股份有限公司 一种基站设备自愈的实现方法及装置
WO2015154455A1 (zh) * 2014-08-15 2015-10-15 中兴通讯股份有限公司 告警处理方法、装置、nms、oss及ems

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7904396B2 (en) * 2006-03-28 2011-03-08 The United States Of America As Represented By The Administrator Of The National Aeronautics And Space Administration Systems, methods and apparatus for quiesence of autonomic safety devices with self action
US20100128600A1 (en) * 2008-11-26 2010-05-27 A T & T Intellectual Property I, L.P. Automated Network Fault Analysis
CN101924661B (zh) * 2009-06-17 2015-07-22 中兴通讯股份有限公司 告警的处理方法及装置
WO2014101211A1 (zh) * 2012-12-31 2014-07-03 华为技术有限公司 一种虚拟设备重建方法与装置
CN105204955B (zh) * 2015-09-30 2018-05-29 华为技术有限公司 一种虚拟机故障修复方法和装置

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1878384A (zh) * 2006-07-10 2006-12-13 华为技术有限公司 一种网元故障检测方法
CN101867958A (zh) * 2010-06-18 2010-10-20 中兴通讯股份有限公司 管理无线传感网终端的方法和系统
CN104754629A (zh) * 2013-12-31 2015-07-01 中兴通讯股份有限公司 一种基站设备自愈的实现方法及装置
WO2015154455A1 (zh) * 2014-08-15 2015-10-15 中兴通讯股份有限公司 告警处理方法、装置、nms、oss及ems

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020252902A1 (zh) * 2019-06-18 2020-12-24 平安科技（深圳）有限公司 云服务器自检方法、装置、设备及计算机可读存储介质
CN113704046A (zh) * 2020-05-21 2021-11-26 中移(苏州)软件技术有限公司 一种故障告警处理方法及装置、设备、存储介质
CN113704046B (zh) * 2020-05-21 2024-05-03 中移(苏州)软件技术有限公司 一种故障告警处理方法及装置、设备、存储介质
CN112650642A (zh) * 2020-12-07 2021-04-13 深圳前海微众银行股份有限公司 一种告警处理方法及装置、设备、存储介质
WO2022127504A1 (zh) * 2020-12-14 2022-06-23 武汉绿色网络信息服务有限责任公司 网元管理方法、装置及存储介质

Also Published As

Publication number Publication date
CN106921508A (zh) 2017-07-04
CN106921508B (zh) 2021-02-19

Similar Documents

Publication Publication Date Title
WO2017107656A1 (zh) 虚拟化网元故障自愈方法及装置
US11032130B2 (en) Troubleshooting method, apparatus, and system
US10037237B2 (en) Method and arrangement for fault management in infrastructure as a service clouds
GB2505644A (en) Managing network configurations
US10884880B2 (en) Method for transmitting request message and apparatus
EP3522449B1 (en) Service state transition method and device
CN113742031A (zh) 节点状态信息获取方法、装置、电子设备及可读存储介质
WO2016045439A1 (zh) 一种vnfm容灾保护的方法、装置和nfvo、存储介质
CN108199901B (zh) 硬件报修方法、系统、设备、硬件管理服务器与存储介质
CN112395047A (zh) 虚拟机故障疏散方法、系统及计算机可读介质
WO2019141089A1 (zh) 网络告警方法、装置、系统及终端
WO2017045436A1 (zh) 虚拟机故障处理方法和装置
US20190303261A1 (en) Automating and monitoring rolling cluster reboots
EP3905591A1 (en) Server abnormality processing method and management device
CN111610992B (zh) 部署组件更新处理方法、装置及存储介质
US9317355B2 (en) Dynamically determining an external systems management application to report system errors
CN109995554A (zh) 多级数据中心主备切换的控制方法及云调度指挥器
CN108089917A (zh) 一种应用进程控制方法及装置
CN113746676B (zh) 基于容器集群的网卡管理方法、装置、设备、介质及产品
CN107566475B (zh) 一种会话故障转移方法及装置
CN115190046B (zh) 一种服务器集群的检测方法、检测装置及计算设备
CN113835966B (zh) 服务进程管理方法、装置、存储系统以及存储介质
US20230289203A1 (en) Server maintenance control device, server maintenance system, server maintenance control method, and program
CN106230878B (zh) 一种基于AllJoyn框架的设备服务调用方法及装置
CN111083011A (zh) 路由安全防火墙和管理平台的自动化测试方法及装置

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 16877467

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 16877467

Country of ref document: EP

Kind code of ref document: A1