CN116627686A

CN116627686A - Software fault processing method and device for network equipment

Info

Publication number: CN116627686A
Application number: CN202310380144.3A
Authority: CN
Inventors: 魏方征
Original assignee: Hangzhou DPTech Technologies Co Ltd
Current assignee: Hangzhou DPTech Technologies Co Ltd
Priority date: 2023-04-11
Filing date: 2023-04-11
Publication date: 2023-08-22

Abstract

The application relates to a method and a device for processing software faults of network equipment. The method comprises the following steps: monitoring the running states of a plurality of software in the network equipment in real time; when the running state of the software fails, acquiring attribute information of the software; matching the attribute information with a restarting strategy to determine the restarting priority and the operation rule of the software; and restarting the software according to the restarting priority and the operation rule. The method and the device for processing the software faults of the network equipment can shorten the restarting time of the software system of the gateway equipment, thereby reducing the network interruption time when the software system is restarted due to the software faults.

Description

Software fault processing method and device for network equipment

Technical Field

The disclosure relates to the field of computer information processing, and in particular relates to a method and a device for processing software faults of network equipment.

Background

The network device mainly comprises a router, a gateway, a firewall, a switch and other devices, various terminals (PC, server application terminal and the like) in the local area network are connected together through the network device to form the local area network, and a plurality of local area networks are connected through the network device to form the Internet. Network devices are an important environment in computer networks.

Sometimes, when the software fault of the equipment running in the network is suspended, restarting the equipment software system, and because the gateway equipment forwards the flow dependent software system, the network is in an interrupt state in the restarting process; therefore, the restarting time of the software is very important, if the restarting time is too long, the network of the user is greatly influenced, and if the restarting time can be shortened as much as possible, the influence of the restarting operation on the network is reduced as much as possible.

In the prior art, the network interruption is avoided through a double-machine scheme, the equipment adopts a main-standby double-machine scheme, and when the main equipment is restarted, the standby equipment is switched into the main equipment to bear the network flow forwarding task. In this way, although the primary and standby schemes can avoid the problem of network interruption caused by restarting the device, the primary and standby schemes need double software and hardware resources, and are not applicable to non-dual-machine scenes. Moreover, restarting all module services is time-consuming and has a large impact on the network. Moreover, the configuration data is re-issued each time the configuration data is required to be restarted, so that the time consumption is long.

Therefore, a new method and apparatus for processing software failure of network device are needed.

The above information disclosed in the background section is only for enhancement of understanding of the background of the application and therefore it may contain information that does not form the prior art that is already known to a person of ordinary skill in the art.

Disclosure of Invention

In view of the above, the present application provides a method and apparatus for processing a software failure of a network device, which can shorten the restart time of a software system of a gateway device, thereby reducing the network interruption time when restarting the software system due to the software failure.

Other features and advantages of the application will be apparent from the following detailed description, or may be learned by the practice of the application.

According to an aspect of the present application, a method for processing a software failure of a network device is provided, the method comprising: monitoring the running states of a plurality of software in the network equipment in real time; when the running state of the software fails, acquiring attribute information of the software; matching the attribute information with a restarting strategy to determine the restarting priority and the operation rule of the software; and restarting the software according to the restarting priority and the operation rule.

In an exemplary embodiment of the present application, further comprising: acquiring software information of a plurality of pieces of software in the network equipment; and generating attribute information of the plurality of software according to the software information and the category policy.

In an exemplary embodiment of the present application, generating attribute information of the plurality of software according to the software information and the category policy includes: setting attribute information of the software as a priority class or a non-priority class according to the software information and the class strategy; and setting the attribute information of the software into a control class or a data class according to the software information and the class strategy.

In an exemplary embodiment of the present application, matching the attribute information and the restart policy to determine the restart priority and the operation policy of the software includes: matching the attribute information with a priority strategy in a restarting strategy, and dividing the software into a first priority or a second priority; and matching the attribute information with an operation strategy in a restarting strategy, and dividing the software into direct restarting or forwarding restarting.

In an exemplary embodiment of the present application, restarting the software according to the restart priority and the operation rule includes: restarting the software corresponding to the first priority according to the corresponding operation rule; restarting the software corresponding to the second priority according to the corresponding operation rule; in the restarting process, the software of the control class and the software of the data class transfer data through the shared memory.

In an exemplary embodiment of the present application, restarting software corresponding to a first priority according to its corresponding operation rule includes: restarting an independent process corresponding to control software in the software corresponding to the first priority; restarting the multi-process corresponding to the data type software in the software corresponding to the first priority, and restarting configuration data transmission.

In an exemplary embodiment of the present application, the re-issuing of the configuration data includes: the software of the control class re-issues the configuration data to the software of the data class after the restart.

In an exemplary embodiment of the present application, the data transfer between the software of the control class and the software of the data class through the shared memory includes: the software of the control class stores the rule strategy in the shared memory; storing the mapping information of the virtual memory and the physical memory of the data structure in a preset file; and carrying out data transmission through the shared memory by the software of the preset file control class and the software of the data class.

In an exemplary embodiment of the present application, the data transfer between the software of the preset file control class and the software of the data class through the shared memory includes: the software of the data class acquires an update configuration message; acquiring synchronous address mapping information from the preset file by the software of the data class based on the updating configuration message; and carrying out data transfer based on the synchronous address mapping information.

According to an aspect of the present application, there is provided a software failure processing apparatus of a network device, the apparatus including: the monitoring module is used for monitoring the running states of a plurality of software in the network equipment in real time; the attribute module is used for acquiring attribute information of the software when the running state of the software fails; the matching module is used for matching the attribute information with the restarting strategy to determine the restarting priority and the operation rule of the software; and the restarting module is used for restarting the software according to the restarting priority and the operation rule.

According to an aspect of the present application, there is provided an electronic device including: one or more processors; a storage means for storing one or more programs; when the one or more programs are executed by the one or more processors, the one or more processors are caused to implement the methods as described above.

According to an aspect of the application, a computer-readable medium is proposed, on which a computer program is stored, which program, when being executed by a processor, implements a method as described above.

According to the method and the device for processing the software faults of the network equipment, the running states of a plurality of pieces of software in the network equipment are monitored in real time; when the running state of the software fails, acquiring attribute information of the software; matching the attribute information with a restarting strategy to determine the restarting priority and the operation rule of the software; the restarting time of the gateway equipment software system can be shortened according to the restarting priority and the mode of restarting the software according to the operation rule, so that the network interruption time when the software system is restarted due to software faults is reduced.

It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the application as claimed.

Drawings

The above and other objects, features and advantages of the present application will become more apparent by describing in detail exemplary embodiments thereof with reference to the attached drawings. The drawings described below are only some embodiments of the present application and other drawings may be obtained from these drawings without inventive effort for a person of ordinary skill in the art.

Fig. 1 is a system block diagram illustrating a method and apparatus for processing a software failure of a network device according to an exemplary embodiment.

Fig. 2 is a flow chart illustrating a method of software fault handling for a network device according to an exemplary embodiment.

Fig. 3 is a flowchart illustrating a software fault handling method of a network device according to another exemplary embodiment.

Fig. 4 is a flowchart illustrating a software fault handling method of a network device according to another exemplary embodiment.

Fig. 5 is a schematic diagram illustrating a software fault handling method of a network device according to another exemplary embodiment.

Fig. 6 is a block diagram illustrating a software fault handling apparatus of a network device according to an exemplary embodiment.

Fig. 7 is a block diagram of an electronic device, according to an example embodiment.

Fig. 8 is a block diagram of a computer-readable medium shown according to an example embodiment.

Detailed Description

Example embodiments will now be described more fully with reference to the accompanying drawings. However, the exemplary embodiments can be embodied in many forms and should not be construed as limited to the embodiments set forth herein; rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the concept of the example embodiments to those skilled in the art. The same reference numerals in the drawings denote the same or similar parts, and thus a repetitive description thereof will be omitted.

Furthermore, the described features, structures, or characteristics may be combined in any suitable manner in one or more embodiments. In the following description, numerous specific details are provided to give a thorough understanding of embodiments of the application. One skilled in the relevant art will recognize, however, that the application may be practiced without one or more of the specific details, or with other methods, components, devices, steps, etc. In other instances, well-known methods, devices, implementations, or operations are not shown or described in detail to avoid obscuring aspects of the application.

The block diagrams depicted in the figures are merely functional entities and do not necessarily correspond to physically separate entities. That is, the functional entities may be implemented in software, or in one or more hardware modules or integrated circuits, or in different networks and/or processor devices and/or microcontroller devices.

The flow diagrams depicted in the figures are exemplary only, and do not necessarily include all of the elements and operations/steps, nor must they be performed in the order described. For example, some operations/steps may be decomposed, and some operations/steps may be combined or partially combined, so that the order of actual execution may be changed according to actual situations.

It will be understood that, although the terms first, second, third, etc. may be used herein to describe various components, these components should not be limited by these terms. These terms are used to distinguish one element from another element. Accordingly, a first component discussed below could be termed a second component without departing from the teachings of the present inventive concept. As used herein, the term "and/or" includes any one of the associated listed items and all combinations of one or more.

Those skilled in the art will appreciate that the drawings are schematic representations of example embodiments and that the modules or flows in the drawings are not necessarily required to practice the application and therefore should not be taken to limit the scope of the application.

As shown in fig. 1, the system architecture 10 may include network devices 101, 102, 103, a network 104, and a server 105. The network 104 is the medium used to provide communication links between the network devices 101, 102, 103 and the server 105. The network 104 may include various connection types, such as wired, wireless communication links, or fiber optic cables, among others.

Network devices 101, 102, 103 may be used to interact with server 105 over network 104 to receive or send messages, etc. Various communication client applications may be installed on the network devices 101, 102, 103, such as a route forwarding class application, a firewall class application, a data exchange class application, an instant messaging tool, a mailbox client, social platform software, and the like.

The network devices 101, 102, 103 may be a variety of electronic devices with data processing forwarding functionality including, but not limited to, routers, gateways, firewalls, switches and the like, tablet computers, laptop and desktop computers, and the like.

The network devices 101, 102, 103 may, for example, monitor the running states of a plurality of software in their own devices in real time; the network devices 101, 102, 103 may, for example, obtain attribute information of the software when the running state of the software fails; the network device 101, 102, 103 may, for example, match the attribute information with a restart policy to determine a restart priority and an operation rule of the software; the network device 101, 102, 103 may restart the software, e.g. according to the restart priority and the operation rules.

The server 105 may be a server providing various services, such as a background management server that monitors and manages the network devices 101, 102, 103. The background management server may analyze the states of the network devices 101, 102, 103, and when a software failure is found, the background management server may control the network devices 101, 102, 103 to restart.

The server 105 may, for example, monitor the running status of a plurality of software in the network devices 101, 102, 103 in real time; the server 105 may, for example, acquire attribute information of the software when the running state of the software fails; server 105 may, for example, match the attribute information with a restart policy to determine a restart priority and operational rules for the software; server 105 may restart the software, for example, according to the restart priority and the operational rules.

The network devices 101, 102, 103 and the server 105 may be one entity server, or may be a plurality of servers, for example, it should be noted that the method for processing a software failure of a network device provided in the embodiment of the present application may be executed by the network devices 101, 102, 103 or the server 105, and accordingly, the software failure processing apparatus of the network device may be set in the network devices 101, 102, 103 or the server 105.

Fig. 2 is a flow chart illustrating a method of software fault handling for a network device according to an exemplary embodiment. The software fault handling method 20 of the network device at least comprises steps S202 to S208.

As shown in fig. 2, in S202, the running states of a plurality of software in the network device are monitored in real time. The software running state in the network device may be monitored in real time, for example, by a remote management server, and the network device may also monitor its own software running state in real time, for example.

In S204, when the running state of the software fails, attribute information of the software is acquired. The attribute information of the software includes whether the software belongs to a priority class or a non-priority class, and whether the software belongs to a control class or a data class. The attribute information of the software is determined in advance according to the actual function of the software. The relevant contents will be described in detail in the corresponding embodiment of fig. 3.

Typically, the software of the priority class is a service (such as a routing service, an interface management service, etc.) that affects forwarding; non-priority classes of software may be launched late, such as web services that are only required when a web page is accessed, such services may be launched later.

More specifically, the control class software may be a control layer module of the device, and mainly includes services such as configuration management, system management, and routing management; the software of the data class can be a message forwarding flow of the device and is mainly responsible for forwarding network traffic, and the data class receives a forwarding strategy issued by the control class and executes data forwarding.

In S206, the attribute information and the restart policy are matched to determine the restart priority and the operation rule of the software. The attribute information and a priority strategy in the restarting strategy can be matched, and the software is divided into a first priority or a second priority; and matching the attribute information with an operation strategy in a restarting strategy, and dividing the software into direct restarting or forwarding restarting.

Software of a priority class may be classified as a first priority and software of a non-priority class may be classified as a second priority.

In general, the software of the control class is composed of a plurality of processes, and generally, an independent service module adopts an independent process, for example, a routing module uses an independent routing process, and an interface management module uses an independent interface management process. Therefore, the coupling degree between the service modules can be reduced, and other services can not be influenced when a single service process is suspended.

Dataclasses typically use a single forwarding process, in a multithreaded mode, one thread per cpu, to increase multi-core concurrency processing capability.

In S208, the software is restarted according to the restart priority and the operation rule. Restarting the software corresponding to the first priority according to the corresponding operation rule; restarting the software corresponding to the second priority according to the corresponding operation rule; in the restarting process, the software of the control class and the software of the data class transfer data through the shared memory.

Restarting the software corresponding to the first priority according to the corresponding operation rule, including: restarting an independent process corresponding to control software in the software corresponding to the first priority; restarting the multi-process corresponding to the data type software in the software corresponding to the first priority, and restarting configuration data transmission.

In a specific application, when a single service process of the control class software hangs up, only the hang up process needs to be restarted, and other processes do not need to be restarted. Here, there are two cases: when the control class process is suspended, restarting the corresponding process, and not needing to issue data to the data class; if the data class forwarding process is suspended, after the forwarding process is restarted, the control class process is required to forward all policy configuration data to the data class process again, and normal flow forwarding can be performed after the forwarding process is completed.

More specifically, the re-issuing of the configuration data includes: the software of the control class re-issues the configuration data to the software of the data class after the restart.

Details of "data transfer by shared memory between control class software and data class software" are described in the corresponding embodiment of fig. 4.

According to the software fault processing method of the network equipment, the running states of a plurality of software in the network equipment are monitored in real time; when the running state of the software fails, acquiring attribute information of the software; matching the attribute information with a restarting strategy to determine the restarting priority and the operation rule of the software; the restarting time of the gateway equipment software system can be shortened according to the restarting priority and the mode of restarting the software according to the operation rule, so that the network interruption time when the software system is restarted due to software faults is reduced.

It should be clearly understood that the present application describes how to make and use specific examples, but the principles of the present application are not limited to any details of these examples. Rather, these principles can be applied to many other embodiments based on the teachings of the present disclosure.

Fig. 3 is a flowchart illustrating a software fault handling method of a network device according to another exemplary embodiment. The flow 30 shown in fig. 3 is a complementary description of the flow shown in fig. 2.

As shown in fig. 3, in S302, software information of a plurality of pieces of software in the network device is acquired.

In S304, attribute information of the software is set to a priority class or a non-priority class according to the software information and the class policy.

In one embodiment, the software of the priority class may be a base service, and the software of the priority class affects a forwarded service (e.g., routing service, interface management service, etc.); the non-priority class of software may be configured to be initiated late, such as when a web service is only required when accessing a web page, and the non-priority class of software may be initiated later. There are multiple services that depend on each other, the dependent services are started first, and the dependent services are started later.

In S306, attribute information of the software is set as a control class or a data class according to the software information and the class policy.

In one embodiment, the device software system may be divided into a control class and a data class. The control class is a control layer module of the equipment and mainly comprises services such as configuration management, system management, routing management and the like; the data class is a message forwarding flow of the device and is mainly responsible for forwarding network traffic, and the data class receives a forwarding strategy issued by the control class and executes data forwarding.

The control class is composed of a plurality of processes, and generally independent service modules adopt independent processes, for example, a routing module uses an independent routing process, and an interface management module uses an independent interface management process. Therefore, the coupling degree between the service modules can be reduced, and other services can not be influenced when a single service process is suspended.

When a single service process is suspended, only the suspended process needs to be restarted, and other processes do not need to be restarted. Here, there are two cases: when the control class process is suspended, restarting the corresponding process, and not needing to issue data to the data class; if the data class forwarding process is suspended, after the forwarding process is restarted, the control class process is required to forward all policy configuration data to the data class process again, and normal flow forwarding can be performed after the forwarding process is completed.

The application provides a method for processing software faults of network equipment, and provides a scheme for quickly starting the software of the network equipment. The quick start of the network device is realized by the service module being restarted as required and a memory sharing mechanism between services.

Fig. 4 is a flowchart illustrating a software fault handling method of a network device according to another exemplary embodiment. The flow 40 shown in fig. 4 is a detailed description of "the software of the control class and the software of the data class perform data transfer through the shared memory" in the flow S108 shown in fig. 2.

As shown in fig. 4, in S402, the software of the control class stores the rule policy in the shared memory.

In S404, the virtual memory and the physical memory mapping information of the data structure are stored in a preset file.

In S406, the software of the preset file control class and the software of the data class transfer data through the shared memory. The update configuration message may be obtained, for example, by software of the dataclass; acquiring synchronous address mapping information from the preset file by the software of the data class based on the updating configuration message; and carrying out data transfer based on the synchronous address mapping information.

Software of the data class and the control class can realize large-block data transmission through a shared memory. For a service module needing to issue a large amount of data, the control process and the data class process adopt a shared memory mode to transmit the data.

Fig. 5 is a schematic diagram illustrating a software fault handling method of a network device according to another exemplary embodiment. As shown in fig. 5, for example, the IPS intrusion prevention module needs to issue an IPS feature library rule to a data class process, if data is transferred through a socket inter-process communication manner each time, a large amount of data needs to be transferred, and frequent memory application operation is required, which is low in efficiency. When the shared memory mode is adopted, the IPS rule is processed and established by the control type IPS service process, the processed rule strategy is placed in the memory, meanwhile, the virtual memory and the physical memory mapping information of the data structure are stored in the ips_rule_file, when rule data are needed to be synchronized with the data type process, the data type process only needs to be informed of updating configuration, the data type process reads the content of the ips_rule_file, the memory address mapping information is synchronized, and virtual addresses applied by the IPS control process can be directly accessed in the data type process after synchronization, so that the effect of zero copying of the synchronous rule data is achieved.

When the data class process is restarted abnormally, other control class processes do not need to be restarted. For the module with smaller data volume, the control process re-transmits the configuration data to the data class process; for a module with large data volume or complex operation, the memory address information is directly synchronized to the data class process in a shared memory mode, and data is not required to be transferred by inter-process copying. The quick recovery of the data class process is realized.

According to the software fault processing method of the network equipment, when the equipment software system needs to be restarted, the service processes are restarted as few as possible through restarting according to the need, and the whole machine is prevented from being restarted.

According to the software fault processing method of the network equipment, the control process and the forwarding process transmit the configuration data through the shared memory, so that the configuration recovery speed is improved, and the configuration recovery time is shortened.

Those skilled in the art will appreciate that all or part of the steps implementing the above described embodiments are implemented as a computer program executed by a CPU. When executed by a CPU, performs the functions defined by the above-described method provided by the present application. The program may be stored in a computer readable storage medium, which may be a read-only memory, a magnetic disk or an optical disk, etc.

Furthermore, it should be noted that the above-described figures are merely illustrative of the processes involved in the method according to the exemplary embodiment of the present application, and are not intended to be limiting. It will be readily appreciated that the processes shown in the above figures do not indicate or limit the temporal order of these processes. In addition, it is also readily understood that these processes may be performed synchronously or asynchronously, for example, among a plurality of modules.

The following are examples of the apparatus of the present application that may be used to perform the method embodiments of the present application. For details not disclosed in the embodiments of the apparatus of the present application, please refer to the embodiments of the method of the present application.

Fig. 6 is a block diagram illustrating a software fault handling apparatus of a network device according to another exemplary embodiment. As shown in fig. 6, the software failure processing apparatus 60 of the network device includes: monitoring module 602, attribute module 604, matching module 606, restarting module 608.

The monitoring module 602 is configured to monitor an operation state of a plurality of software in the network device in real time;

the attribute module 604 is configured to obtain attribute information of software when an operation state of the software fails;

the matching module 606 is configured to match the attribute information with a restart policy to determine a restart priority and an operation rule of the software; the matching module 606 is further configured to match the attribute information with a priority policy in a restart policy, and divide the software into a first priority or a second priority; and matching the attribute information with an operation strategy in a restarting strategy, and dividing the software into direct restarting or forwarding restarting.

The restarting module 608 is configured to restart the software according to the restarting priority and the operation rule. The restarting module 608 is further configured to restart the software corresponding to the first priority according to the operation rule corresponding to the software; restarting the software corresponding to the second priority according to the corresponding operation rule; in the restarting process, the software of the control class and the software of the data class transfer data through the shared memory.

According to the software fault processing device of the network equipment, the running states of a plurality of software in the network equipment are monitored in real time; when the running state of the software fails, acquiring attribute information of the software; matching the attribute information with a restarting strategy to determine the restarting priority and the operation rule of the software; the restarting time of the gateway equipment software system can be shortened according to the restarting priority and the mode of restarting the software according to the operation rule, so that the network interruption time when the software system is restarted due to software faults is reduced.

An electronic device 700 according to this embodiment of the application is described below with reference to fig. 7. The electronic device 700 shown in fig. 7 is merely an example, and should not be construed as limiting the functionality and scope of use of embodiments of the present application.

As shown in fig. 7, the electronic device 700 is embodied in the form of a general purpose computing device. Components of electronic device 700 may include, but are not limited to: at least one processing unit 710, at least one memory unit 720, a bus 730 connecting the different system components (including the memory unit 720 and the processing unit 710), a display unit 740, and the like.

Wherein the storage unit stores program code that is executable by the processing unit 710 such that the processing unit 710 performs steps according to various exemplary embodiments of the present application described in the present specification. For example, the processing unit 710 may perform the steps as shown in fig. 2, 3, and 4.

The memory unit 720 may include readable media in the form of volatile memory units, such as Random Access Memory (RAM) 7201 and/or cache memory 7202, and may further include Read Only Memory (ROM) 7203.

The storage unit 720 may also include a program/utility 7204 having a set (at least one) of program modules 7205, such program modules 7205 including, but not limited to: an operating system, one or more application programs, other program modules, and program data, each or some combination of which may include an implementation of a network environment.

Bus 730 may be a bus representing one or more of several types of bus structures including a memory unit bus or memory unit controller, a peripheral bus, an accelerated graphics port, a processing unit, or a local bus using any of a variety of bus architectures.

The electronic device 700 may also communicate with one or more external devices 700' (e.g., keyboard, pointing device, bluetooth device, etc.), devices that enable a user to interact with the electronic device 700, and/or any devices (e.g., routers, modems, etc.) with which the electronic device 700 can communicate with one or more other computing devices. Such communication may occur through an input/output (I/O) interface 750. Also, electronic device 700 may communicate with one or more networks such as a Local Area Network (LAN), a Wide Area Network (WAN) and/or a public network, such as the Internet, through network adapter 760. Network adapter 760 may communicate with other modules of electronic device 700 via bus 730. It should be appreciated that although not shown, other hardware and/or software modules may be used in connection with electronic device 700, including, but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, data backup storage systems, and the like.

From the above description of embodiments, those skilled in the art will readily appreciate that the example embodiments described herein may be implemented in software, or may be implemented in software in combination with the necessary hardware. Thus, as shown in fig. 8, the technical solution according to the embodiment of the present application may be embodied in the form of a software product, which may be stored in a non-volatile storage medium (may be a CD-ROM, a U-disk, a mobile hard disk, etc.) or on a network, and includes several instructions to cause a computing device (may be a personal computer, a server, or a network device, etc.) to perform the above-described method according to the embodiment of the present application.

The software product may employ any combination of one or more readable media. The readable medium may be a readable signal medium or a readable storage medium. The readable storage medium can be, for example, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or a combination of any of the foregoing. More specific examples (a non-exhaustive list) of the readable storage medium would include the following: an electrical connection having one or more wires, a portable disk, a hard disk, random Access Memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

The computer readable storage medium may include a data signal propagated in baseband or as part of a carrier wave, with readable program code embodied therein. Such a propagated data signal may take any of a variety of forms, including, but not limited to, electro-magnetic, optical, or any suitable combination of the foregoing. A readable storage medium may also be any readable medium that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. Program code embodied on a readable storage medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.

Program code for carrying out operations of the present application may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, C++ or the like and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user's computing device, partly on the user's device, as a stand-alone software package, partly on the user's computing device, partly on a remote computing device, or entirely on the remote computing device or server. In the case of remote computing devices, the remote computing device may be connected to the user computing device through any kind of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or may be connected to an external computing device (e.g., connected via the Internet using an Internet service provider).

The computer-readable medium carries one or more programs, which when executed by one of the devices, cause the computer-readable medium to perform the functions of: monitoring the running states of a plurality of software in the network equipment in real time; when the running state of the software fails, acquiring attribute information of the software; matching the attribute information with a restarting strategy to determine the restarting priority and the operation rule of the software; and restarting the software according to the restarting priority and the operation rule.

Those skilled in the art will appreciate that the modules may be distributed throughout several devices as described in the embodiments, and that corresponding variations may be implemented in one or more devices that are unique to the embodiments. The modules of the above embodiments may be combined into one module, or may be further split into a plurality of sub-modules.

From the above description of embodiments, those skilled in the art will readily appreciate that the example embodiments described herein may be implemented in software, or in combination with the necessary hardware. Thus, the technical solution according to the embodiments of the present application may be embodied in the form of a software product, which may be stored in a non-volatile storage medium (may be a CD-ROM, a U-disk, a mobile hard disk, etc.) or on a network, and includes several instructions to cause a computing device (may be a personal computer, a server, a mobile terminal, or a network device, etc.) to perform the method according to the embodiments of the present application.

The exemplary embodiments of the present application have been particularly shown and described above. It is to be understood that this application is not limited to the precise arrangements, instrumentalities and instrumentalities described herein; on the contrary, the application is intended to cover various modifications and equivalent arrangements included within the spirit and scope of the appended claims.

Claims

1. A method for processing a software failure of a network device, comprising:

monitoring the running states of a plurality of software in the network equipment in real time;

when the running state of the software fails, acquiring attribute information of the software;

matching the attribute information with a restarting strategy to determine the restarting priority and the operation rule of the software;

and restarting the software according to the restarting priority and the operation rule.

2. The method as recited in claim 1, further comprising:

acquiring software information of a plurality of pieces of software in the network equipment;

and generating attribute information of the plurality of software according to the software information and the category policy.

3. The method of claim 2, wherein generating attribute information for the plurality of software according to the software information and a category policy comprises:

setting attribute information of the software as a priority class or a non-priority class according to the software information and the class strategy;

and setting the attribute information of the software into a control class or a data class according to the software information and the class strategy.

4. The method of claim 1, wherein matching the attribute information and a restart policy to determine a restart priority and an operation policy of the software comprises:

matching the attribute information with a priority strategy in a restarting strategy, and dividing the software into a first priority or a second priority;

and matching the attribute information with an operation strategy in a restarting strategy, and dividing the software into direct restarting or forwarding restarting.

5. The method of claim 4, wherein restarting the software according to the restart priority and the operation rule comprises:

restarting the software corresponding to the first priority according to the corresponding operation rule;

restarting the software corresponding to the second priority according to the corresponding operation rule;

in the restarting process, the software of the control class and the software of the data class transfer data through the shared memory.

6. The method of claim 5, wherein restarting the software corresponding to the first priority according to its corresponding operation rule comprises:

restarting an independent process corresponding to control software in the software corresponding to the first priority;

restarting the multi-process corresponding to the data type software in the software corresponding to the first priority, and restarting configuration data transmission.

7. The method of claim 6, wherein the re-issuing of configuration data comprises:

the software of the control class re-issues the configuration data to the software of the data class after the restart.

8. The method of claim 5, wherein the software controlling the class and the software controlling the data class transfer data through the shared memory, comprising:

the software of the control class stores the rule strategy in the shared memory;

storing the mapping information of the virtual memory and the physical memory of the data structure in a preset file;

and carrying out data transmission through the shared memory by the software of the preset file control class and the software of the data class.

9. The method of claim 8, wherein the data transfer by the software of the preset file control class and the software of the data class through the shared memory comprises:

the software of the data class acquires an update configuration message;

acquiring synchronous address mapping information from the preset file by the software of the data class based on the updating configuration message;

and carrying out data transfer based on the synchronous address mapping information.

10. A software fault handling device for a network device, comprising:

the monitoring module is used for monitoring the running states of a plurality of software in the network equipment in real time;

the attribute module is used for acquiring attribute information of the software when the running state of the software fails;

the matching module is used for matching the attribute information with the restarting strategy to determine the restarting priority and the operation rule of the software;

and the restarting module is used for restarting the software according to the restarting priority and the operation rule.