CN105740140A

CN105740140A - Software system failure diagnosis method, server and system

Info

Publication number: CN105740140A
Application number: CN201410759411.9A
Authority: CN
Inventors: 杜征
Original assignee: ZTE Corp
Current assignee: ZTE Corp
Priority date: 2014-12-10
Filing date: 2014-12-10
Publication date: 2016-07-06
Also published as: WO2016090929A1

Abstract

The present invention discloses a software system failure diagnosis method. The method comprises: acquiring a failure attribute of a to-be-diagnosed software system by means of a network management system; and performing a match in a preset rule database according to the failure attribute, and generating a failure diagnosis decision list according to a matching degree of the failure attribute and the preset rule database. The present invention further discloses a software system failure diagnosis server and system. According to the software system failure diagnosis method, server and system disclosed by the present invention, intelligent diagnosis and repairing of software system failures, real-time software system failure monitoring and online update of diagnosis rules are achieved, the efficiency and automation degree of software failure diagnosis and repairing are greatly improved, and maintenance and improvement efficiency of the diagnosis system are improved, and thus the technical problems of high learning costs and inconvenience of the existing software system maintenance are solved.

Description

Software system method for diagnosing faults, server and system

Technical field

The present invention relates to software system fault automated analysis field, particularly relate to a kind of software system method for diagnosing faults, server and system.

Background technology

Progress along with technology, the application of large-scale distributed software system increases gradually, towards various aspects such as communication, network service, intelligent management systems, and the complexity of this kind of system and scale it is also proposed higher requirement to safeguarding, constantly increase including personnel amount and personnel's technical ability, maintenance cost and difficulty.

In the maintenance process of software system, it is usually required mainly for the problem of two aspects of reply, is hardware problem on the one hand, is software issue on the one hand.Certain component operation that hardware problem is mainly caused by hardware anomalies is abnormal, it is probably hardware damage or design defect causes, influential system runs, problems often phenomenon compares concentration, the set of problematic phenomenon and questions and prospect is relatively fewer, it is easier to investigation, just can meet requirement by arranging output hardware investigation handbook；Software issue is just more complicated, it is usually because of unreasonable allocation, configuration error, networking component is imperfect, MRP is unreasonable, caused by transmission or other network problems, simultaneously because the complexity of network, the phenomenon of this kind of software issue and the correspondence set of questions and prospect are very huge, the problem that this needs attendant to have an outstanding technical foundation and long-term technological accumulation could solve software system, so that the learning cost that software system is safeguarded is too high, also the maintenance colony making software system cannot towards domestic consumer or general attendant, safeguard inconvenient.

Foregoing is only used for assisting understanding technical scheme, does not represent and admits that foregoing is prior art.

Summary of the invention

Present invention is primarily targeted at a kind of software system method for diagnosing faults of offer, server and system, it is intended to solve the technical problem that learning cost is high, maintenance is inconvenient that existing software system is safeguarded.

For achieving the above object, a kind of software system method for diagnosing faults provided by the invention, described software system method for diagnosing faults comprises the following steps:

The fault attribute being diagnosed software system is obtained by network management system；

Mate in default rule database according to described fault attribute, generate Fault Tree Diagnosis Decision list according to the matching degree of described fault attribute with the rule database preset.

Preferably, described mate in default rule database according to described fault attribute, also include generate the step of Fault Tree Diagnosis Decision list according to the matching degree of described fault attribute with the rule database preset after:

When described fault attribute is mated unsuccessful with the rule database preset, then described fault attribute transmission to accident analysis is analyzed with rule exploitation end；

Receive described accident analysis and the rule exploitation end process new regulation to mating unsuccessful fault attribute and be analyzed gained, and described process new regulation is incorporated in described rule database.

Preferably, also include before the described step being obtained the fault attribute being diagnosed software system by network management system:

Fault attribute data record is formed respectively according to the fault attribute having verified that, and by this fault attribute data record typing fault attribute data base, wherein, described fault attribute includes: configuration attribute, alarm attributes, performance indications attribute, failure cause attribute and solution attribute；

Set up the mapping relations of phenomenon of the failure and described failure cause attribute and solution combinations of attributes, and by these mapping relations typing diagnosis rule data base, wherein, described phenomenon of the failure includes described configuration attribute, alarm attributes and performance indications attribute, described failure cause and solution attribute one_to_one corresponding；

Described fault attribute data base and diagnosis rule data base are collectively incorporated into rule database, and the data in described fault attribute data base and diagnosis rule data base are in correspondence with each other.

Preferably, the fault attribute that described basis has verified that forms fault attribute data record respectively, and by the step in this fault attribute data record typing fault attribute data base particularly as follows:

Adopting data recording fashion to store all fault attribute having verified that, and this fault attribute having verified that become respectively in storehouse typing fault attribute data base, described fault attribute data base includes:

Configuration attribute storehouse, including configuration attribute numbering, software fault numbering queue and allocation list；

Alarm attributes storehouse, including alarm attributes numbering, software fault numbering queue and alarm feature；

Performance indications attribute library, including performance Criterion Attribute numbering, software fault numbering queue and performance indications feature；

Failure cause attribute library, describes including failure cause attribute number, software fault numbering queue and failure cause；

Solution attribute library, describes including solution attribute number, software fault numbering queue and solution.

Preferably, described diagnosis rule data base includes: software fault numbering, software fault title, configuration attribute group, alarm attributes group, performance indications set of properties, failure cause set of properties, solution set of properties and whether software defect mark；

Described configuration attribute includes configuration attribute numbering and configuration attribute weights, and described alarm attributes includes alarm attributes numbering and alarm attributes weights, and described performance indications attribute includes performance index number and performance indications weights.

Preferably, described mating in default rule database according to described fault attribute, the step generating Fault Tree Diagnosis Decision list according to the matching degree of described fault attribute with the rule database preset includes:

The described fault attribute got is mated with mate alarm attributes storehouse, configuration attribute storehouse and the performance indications attribute library in described fault attribute data base respectively；

Software fault numbering queue corresponding to the fault attribute that described fault attribute matched collects sequence, forms preliminary matches bug list；If described fault attribute is not matched to any fault attribute, then form unknown failure attribute list, wherein, described preliminary matches bug list includes the performance indications attribute queue of the software fault numbering of coupling, the configuration attribute queue of coupling, the alarm attributes queue of coupling, coupling, and the fault attribute queue of each coupling is made up of the fault attribute numbering mated；Described unknown failure attribute list includes the configuration attribute not mated, the alarm attributes not mated, the performance indications attribute that do not mate, and the fault attribute queue of everybody coupling is made up of the fault attribute numbering mated；

Described preliminary matches bug list is numbered with the fault attribute in described diagnosis rule data base and mates with fault attribute weights, draw the matching degree of a coupling fault in described preliminary matches bug list, wherein, described fault attribute numbering includes configuration attribute numbering, alarm attributes numbering and performance indications numbering, and described fault attribute weights include configuration attribute weights, alarm attributes weights and performance indications weights；

This coupling fault is ranked up by matching degree according in described preliminary matches bug list coupling fault from large to small, and from diagnosis rule data base, extract the failure cause attribute corresponding with coupling fault phase and solution attribute, forming Fault Tree Diagnosis Decision list, wherein said Fault Tree Diagnosis Decision list includes coupling software fault numbering, coupling software fault title, failure cause attribute and solution attribute.

Additionally, for achieving the above object, the present invention also provides for a kind of software system fault diagnosis server, and described software system fault diagnosis server includes:

Fault attribute acquisition module, for obtaining the fault attribute being diagnosed software system by network management system；

Match decision module, for mating in default rule database according to described fault attribute, generates matching degree Fault Tree Diagnosis Decision list from high to low.

Preferably, described software system fault diagnosis server also includes mating more new module, and described coupling more new module is used for:

Preferably, described software system fault diagnosis server also includes DBM, and described DBM includes:

Attribute builds library unit, for forming fault attribute data record respectively according to the fault attribute having verified that, and by this fault attribute data record typing fault attribute data base, wherein, described fault attribute includes: configuration attribute, alarm attributes, performance indications attribute, failure cause attribute and solution attribute；

Library unit is built in diagnosis, for setting up the mapping relations of phenomenon of the failure and described failure cause attribute and solution combinations of attributes, and by these mapping relations typing diagnosis rule data base, wherein, described phenomenon of the failure includes described configuration attribute, alarm attributes and performance indications attribute, described failure cause and solution attribute one_to_one corresponding；

Rule builds library unit, and for described fault attribute data base and diagnosis rule data base are collectively incorporated into rule database, the data in described fault attribute data base and diagnosis rule data base are in correspondence with each other.

Preferably, described attribute is built library unit and is additionally operable to:

Preferably, described match decision module includes:

Attributes match unit, for mating the described fault attribute got with mate alarm attributes storehouse, configuration attribute storehouse and the performance indications attribute library in described fault attribute data base respectively；

Preliminary matches unit, collects sequence, formation preliminary matches bug list for the software fault numbering queue that the fault attribute that described fault attribute matched is corresponding；If described fault attribute is not matched to any fault attribute, then form unknown failure attribute list, wherein, described preliminary matches bug list includes the performance indications attribute queue of the software fault numbering of coupling, the configuration attribute queue of coupling, the alarm attributes queue of coupling, coupling, and the fault attribute queue of each coupling is made up of the fault attribute numbering mated；Described unknown failure attribute list includes the configuration attribute not mated, the alarm attributes not mated, the performance indications attribute that do not mate, and the fault attribute queue of everybody coupling is made up of the fault attribute numbering mated；

Weights matching unit, mate with fault attribute weights for described preliminary matches bug list is numbered with the fault attribute in described diagnosis rule data base, draw the matching degree of a coupling fault in described preliminary matches bug list, wherein, described fault attribute numbering includes configuration attribute numbering, alarm attributes numbering and performance indications numbering, and described fault attribute weights include configuration attribute weights, alarm attributes weights and performance indications weights；

Decision-making matching unit, for from large to small this coupling fault being ranked up according to the matching degree of in described preliminary matches bug list coupling fault, and from diagnosis rule data base, extract the failure cause attribute corresponding with coupling fault phase and solution attribute, forming Fault Tree Diagnosis Decision list, wherein said Fault Tree Diagnosis Decision list includes coupling software fault numbering, coupling software fault title, failure cause attribute and solution attribute.

Additionally, for achieving the above object, the present invention also provides for a kind of software system fault diagnosis system, and described software system fault diagnosis system includes software system diagnosis server, software system client and accident analysis and rule exploitation end,

Described software system diagnosis server includes fault attribute acquisition module, match decision module and mates more new module, wherein,

Described fault attribute acquisition module, for obtaining the fault attribute being diagnosed software system by network management system；

Described match decision module, for mating in default rule database according to described fault attribute, generates matching degree Fault Tree Diagnosis Decision list from high to low；

Described coupling more new module is used for:

Described coupling more new module is additionally operable to: receives described accident analysis and the rule exploitation end process new regulation to mating unsuccessful fault attribute and be analyzed gained, and described process new regulation is incorporated in described rule database；

Described software system client, for providing fault attribute to software system diagnosis server, and receives described Fault Tree Diagnosis Decision list；

Described accident analysis and rule exploitation end, for receiving the unsuccessful fault attribute of coupling that described software system diagnosis server sends over, and be analyzed obtaining processing new regulation to the unsuccessful fault attribute of this coupling, described process new regulation is incorporated in described rule database.

nullThe present invention obtains the fault attribute being diagnosed software system by network management system，This fault attribute includes configuration attribute、Alarm attributes、Performance indications attribute、Failure cause attribute and solution attribute，Then will be diagnosed the configuration attribute having verified that of software system、The combination of alarm attributes and performance indications attribute is combined with corresponding failure cause and solution and is set up mapping relations，And by the modeling of these mapping relations and warehouse-in，Formed and include software fault attribute database and the rule database of diagnosis rule data base，Mate in default rule database finally according to the fault attribute being diagnosed software system，Matching degree according to fault attribute with the rule database preset generates Fault Tree Diagnosis Decision list，This Fault Tree Diagnosis Decision table is sent to the client being diagnosed software system，Operator are instructed to attempt recovering fault，So，Achieve intelligent diagnostics and the reparation of software system fault，Software system fault is monitored in real time，Online updating diagnostic rule，Substantially increase efficiency and the automaticity of software fault diagnosis and reparation，Also improve maintenance and the improvement efficiency of diagnostic system itself simultaneously，Thus solving the learning cost height that existing software system is safeguarded、Safeguard inconvenient technical problem.

Accompanying drawing explanation

Fig. 1 is the schematic flow sheet of invention software diagnosis method for system fault first embodiment；

Fig. 2 is the schematic flow sheet of invention software diagnosis method for system fault the second embodiment；

Fig. 3 is the schematic flow sheet of invention software diagnosis method for system fault the 3rd embodiment；

Fig. 4 mates in default rule database according to described fault attribute in Fig. 1, generates the refinement schematic flow sheet of the step of Fault Tree Diagnosis Decision list according to the matching degree of described fault attribute with the rule database preset；

Fig. 5 is the high-level schematic functional block diagram of invention software system fault diagnosis server first embodiment；

Fig. 6 is the high-level schematic functional block diagram of invention software system fault diagnosis server the second embodiment；

Fig. 7 is the high-level schematic functional block diagram of invention software system fault diagnosis server the 3rd embodiment；

Fig. 8 is the refinement high-level schematic functional block diagram of DBM in Fig. 7；

Fig. 9 is the refinement high-level schematic functional block diagram of match decision module in Fig. 5；

Figure 10 is the high-level schematic functional block diagram of invention software system fault diagnosis system；

Figure 11 is fault attribute database structure schematic diagram in the present invention；

Figure 12 is diagnosis rule database structure schematic diagram in the present invention；

Figure 13 is the system deployment figure of invention software system fault diagnosis system；

Figure 14 is failure data analyzing process schematic of the present invention；

Figure 15 is the software fault diagnosis flow chart of the rule-based data base of the present invention；

Figure 16 is server and client-side program interaction diagrams in the present invention；

Figure 17 is the flow chart performing diagnosis plan in the present invention；

Figure 18 is the flow chart that in the present invention, server end updates software fault attribute database.

The realization of the object of the invention, functional characteristics and advantage will in conjunction with the embodiments, are described further with reference to accompanying drawing.

Detailed description of the invention

Should be appreciated that specific embodiment described herein is only in order to explain the present invention, is not intended to limit the present invention.

The present invention provides a kind of software system method for diagnosing faults.

With reference to the schematic flow sheet that Fig. 1, Fig. 1 are invention software diagnosis method for system fault first embodiment.

In the first embodiment, this software system method for diagnosing faults comprises the following steps:

Step S10, obtains the fault attribute being diagnosed software system by network management system；

Install and operation service end program at software system fault diagnosis server (i.e. NM server), install and run Client Agent program in software system client (NM client).Client Agent program passes through manmachine command, editor's diagnostic task and diagnosis plan, and is sent to serve end program the message comprising diagnostic task and diagnosis plan with watch on-line system mode by Transmission Control Protocol；Serve end program runs in the NM server treat diagnosing software system, obtains diagnostic task and diagnosis plan that client-side program is sent, and performs diagnostic task, and output diagnostic result feeds back to client-side program.

Step S20, mates in default rule database according to fault attribute, generates Fault Tree Diagnosis Decision list according to the matching degree of fault attribute with the rule database preset.

Mate in default rule database according to fault attribute, the preset failure attribute that coupling is fitted mutually for this fault attribute, and find out failure cause corresponding to preset failure attribute and fault resolution, finally according to fault attribute and the matching degree of preset failure attribute and corresponding failure cause and fault resolution fault in production diagnosis decision lists.

nullIn the present embodiment，The fault attribute being diagnosed software system is obtained by network management system，This fault attribute includes configuration attribute、Alarm attributes、Performance indications attribute、Failure cause attribute and solution attribute，Then will be diagnosed the configuration attribute having verified that of software system、The combination of alarm attributes and performance indications attribute is combined with corresponding failure cause and solution and is set up mapping relations，And by the modeling of these mapping relations and warehouse-in，Formed and include software fault attribute database and the rule database of diagnosis rule data base，Mate in default rule database finally according to the fault attribute being diagnosed software system，Matching degree according to fault attribute with the rule database preset generates Fault Tree Diagnosis Decision list，Finally this Fault Tree Diagnosis Decision table is sent to the client being diagnosed software system，Operator are instructed to attempt recovering fault，So，Achieve intelligent diagnostics and the reparation of software system fault，Software system fault is monitored in real time，Online updating diagnostic rule，Substantially increase efficiency and the automaticity of software fault diagnosis and reparation，Also improve maintenance and the improvement efficiency of diagnostic system itself simultaneously，Thus solving the learning cost height that existing software system is safeguarded、Safeguard inconvenient technical problem.

Further, with reference to the schematic flow sheet that Fig. 2, Fig. 2 are invention software diagnosis method for system fault the second embodiment.

In a second embodiment, also include after step S20:

Step S30, when fault attribute is mated unsuccessful with the rule database preset, is then analyzed fault attribute transmission to accident analysis with rule exploitation end；

Step S40, receives accident analysis and develops the end process new regulation to mating unsuccessful fault attribute and be analyzed gained with rule, and process new regulation be incorporated in rule database.

Accident analysis receives with rule exploitation termination after mating unsuccessful fault attribute, by manmachine command editor with formulate new fault attribute and Failure Diagnostic Code, and the message synchronization of fault attribute and Failure Diagnostic Code will be comprised to serve end program by Transmission Control Protocol.

In the present embodiment, by while generating Fault Tree Diagnosis Decision list, also the matching process of fault attribute with the regular numerical control storehouse preset is judged, if mating unsuccessful, then unsuccessful fault attribute (such as unknown failure table and software defect table) is sent to accident analysis and rule exploitation end, analyze for system developer and edit new fault attribute and Failure Diagnostic Code, and then feed back to server end renewal fault attribute data base and diagnosis rule data base, so, while the intelligent diagnostics realizing software system fault and reparation, also achieve the automatic monitoring of software system, Failure Diagnostic Code is constantly improved when system is run, substantially increase efficiency and the automaticity of software fault diagnosis and reparation.

Further, with reference to the schematic flow sheet that Fig. 3, Fig. 3 are invention software diagnosis method for system fault the 3rd embodiment, referring concurrently to Figure 11 and Figure 12.

In the third embodiment, also include before step S20:

Step S50, fault attribute data record is formed respectively according to the fault attribute having verified that, and by this fault attribute data record typing fault attribute data base, wherein, fault attribute includes: configuration attribute, alarm attributes, performance indications attribute, failure cause attribute and solution attribute；

Preferably, step S50 particularly as follows:

Adopting data recording fashion to store all fault attribute having verified that, and this fault attribute having verified that become respectively in storehouse typing fault attribute data base, fault attribute data base include:

Step S60, set up the mapping relations of phenomenon of the failure and failure cause attribute and solution combinations of attributes, and by these mapping relations typing diagnosis rule data base, wherein, phenomenon of the failure includes configuration attribute, alarm attributes and performance indications attribute, failure cause and solution attribute one_to_one corresponding；

Preferably, diagnosis rule data base includes: software fault numbering, software fault title, configuration attribute group, alarm attributes group, performance indications set of properties, failure cause set of properties, solution set of properties and whether software defect mark；Configuration attribute includes configuration attribute numbering and configuration attribute weights, and alarm attributes includes alarm attributes numbering and alarm attributes weights, and performance indications attribute includes performance index number and performance indications weights.

Step S70, is collectively incorporated into rule database, fault attribute data base and the data in diagnosis rule data base in correspondence with each other by fault attribute data base and diagnosis rule data base.

The attribute of software fault and software fault are set up corresponding relation, form the diagnosis rule data base of software system, by software fault numbering, software fault title, corresponding configuration attribute group, alarm attributes group, performance indications set of properties, failure cause set of properties, solution set of properties with whether software defect identifies forms；Each attribute queue of ownership software fault, is made up of attribute number and attribute weight；Element in software fault attaching relation storehouse and each attribute library has the relation of multi-to-multi, indexes mutually table.

Further, with reference to the refinement schematic flow sheet that Fig. 4, Fig. 4 are step S20 in Fig. 1.

In the present embodiment, step S20 includes:

Step S201, mates with mate alarm attributes storehouse, configuration attribute storehouse and the performance indications attribute library in fault attribute data base respectively by the fault attribute got；

Service end Agent (server) mates the fault attribute data got respectively with the alarm attributes storehouse in fault attribute data base, configuration attribute storehouse and performance indications attribute library.

Step S202, software fault numbering queue corresponding to the fault attribute that fault attribute matched collects sequence, forms preliminary matches bug list；If fault attribute is not matched to any fault attribute, then form unknown failure attribute list, wherein, preliminary matches bug list includes the performance indications attribute queue of the software fault numbering of coupling, the configuration attribute queue of coupling, the alarm attributes queue of coupling, coupling, and the fault attribute queue of each coupling is made up of the fault attribute numbering mated；Unknown failure attribute list includes the configuration attribute not mated, the alarm attributes not mated, the performance indications attribute that do not mate, and the fault attribute queue of everybody coupling is made up of the fault attribute numbering mated；

Software fault numbering queue corresponding to the fault attribute that will match to collects sequence, forms preliminary matches bug list；If corresponding fault attribute is not matched to any software attributes, then form unknown failure attribute list；Preliminary matches bug list by mating software fault numbering, coupling configuration attribute queue, coupling alarm attributes queue, matching performance Criterion Attribute queue form, each match attribute queue is made up of the attribute number mated；Unknown failure attribute list by not mating configuration data, do not mate alarm data, non-matching performance achievement data forms, match attribute queue is made up of the attribute number mated.

Step S203, preliminary matches bug list is numbered with the fault attribute in diagnosis rule data base and mates with fault attribute weights, draw the matching degree of a coupling fault in preliminary matches bug list, wherein, fault attribute numbering includes configuration attribute numbering, alarm attributes numbering and performance indications numbering, and fault attribute weights include configuration attribute weights, alarm attributes weights and performance indications weights；

Server-side proxy program is according to fault attribute each in software fault attaching relation weights in corresponding software fault (namely fault attribute is numbered), calculate each matching degree mating fault in coupling bug list, and by matching degree rearrangement, from diagnosis rule data base, extract failure cause and solution attribute, form Fault Tree Diagnosis Decision table.

Step S204, this coupling fault is ranked up by matching degree according in preliminary matches bug list coupling fault from large to small, and from diagnosis rule data base, extract the failure cause attribute corresponding with coupling fault phase and solution attribute, forming Fault Tree Diagnosis Decision list, wherein Fault Tree Diagnosis Decision list includes coupling software fault numbering, coupling software fault title, failure cause attribute and solution attribute.

Fault Tree Diagnosis Decision table is by mating software fault numbering, coupling software fault title, failure cause attribute, solution attribute；In addition, mate in corresponding process fault attribute data base and diagnosis rule data base, judging whether software defect, proposing to form software defect table by software defect record if existing, this software defect table is made up of each attribute data of the preliminary matches record and coupling that are designated software defect.After completing above-mentioned analysis, Fault Tree Diagnosis Decision table is mail to serve end program by serve end program respectively, and unknown failure attribute list and software defect table mail to accident analysis and rule exploitation client.

In the present embodiment, serve end program (server) analyzes target call according to client, automatically the network management data (fault attribute) of corresponding target is obtained, matching rule base, form Fault Tree Diagnosis Decision table according to matching degree sequence and perform suggestion and return to client, for mating or match the fault of software defect, fault data notifies and is sent to accident analysis and rule exploitation client；Specifically, first service end Agent is sent according to client fault diagnosis task or perform regular monitoring plan, obtain object correspondence network management data, coupling by fault attribute data base and Fault Diagnosis Database, form unknown failure attribute list, final Decision Table for Fault and software defect table, and respectively fault final decision table is sent to Client Agent program, unknown failure attribute list and software defect table are sent to accident analysis and rule exploitation client-side program；Then service end Agent receives new fault attribute and the software fault diagnosis rule that accident analysis and rule exploitation client-side program are sent, and synchronized update is to fault attribute data base and Fault Diagnosis Database.

The basic thought of the present invention is: by network management data corresponding for the known fault for the treatment of diagnosing software system, including configuration data, alarm data and performance indications data, and failure cause corresponding to known fault and solution are as 5 attribute, it is organized as software fault diagnosis rule, and strictly all rules is arranged warehouse-in, forming software fault diagnosis rule base, five attribute arrange as fault attribute data base；Two kinds storehouses are deployed on the NM server being diagnosed software system；Service end Agent is deployed on NM server, Client Agent program is deployed on client PC machine, accident analysis is being treated on diagnosis system development side server with rule exploitation client deployment.Server-side proxy program is according to diagnostic task, by obtaining the data on webmaster, coupling fault attribute data base and Failure Diagnostic Code storehouse, form diagnostic result, and feed back to Client Agent program and accident analysis and rule exploitation client respectively, perform recovery measure for client operation personnel and system developer analyzes software fault.

Below in conjunction with Figure 13 to Figure 18 invention software diagnosis method for system fault being done and describe in detail further, the method includes:

Step 1, service end Agent receive the diagnosis object that client is sent or diagnosis planning cycle timer expiry, and diagnosis process starts；

Step 2, service end Agent are according to diagnosis object or diagnose calculated diagnosis contents of object, it is determined that diagnosis object rank and object number, extract the configuration data of corresponding objects numbering, alarm data, performance indications data in webmaster respectively；

Step 3, the configuration attribute data base in the configuration data of extraction and fault attribute data base is mated, and the configuration attribute numbering that record matching arrives, calculate coupling weights A, and extract the software fault set of properties of corresponding configuration attribute；

Step 4, the alarm attributes data base in the alarm data of extraction and fault attribute data base is mated, and the alarm attributes numbering that record matching arrives, calculate coupling weights B, and extract the software fault set of properties of corresponding configuration attribute；.

Step 5, the performance indications attribute database in the performance indications data of extraction and fault attribute data base is mated, and the performance indications attribute number that record matching arrives, calculate coupling weights C, and extract the software fault set of properties of corresponding performance Criterion Attribute；

Step 6, the software fault set of properties that will match to collect, and are numbered index with software fault, collect the coupling weights of configuration attribute numbering group, alarm attributes numbering group and performance indications numbering group and each attribute that Corresponding matching arrives；

Step 7, according to the software fault of Failure Diagnostic Code storehouse record and the weights (A of corresponding states attribute^~,B^~,C^~) calculate final matching value Z the record of each software fault attribute matched in previous step, it is ranked up according to final matching value Z, forms preliminary matches bug list；

Wherein Z=A^~*A+B^~*B+C^~*C

Step 8, it is empty for preliminary matches bug list, and judges that system is abnormal, then fault data is collected and form unknown failure attribute list；If preliminary matches bug list is not empty, then extracts software reason attribute corresponding to the software fault of Failure Diagnostic Code storehouse record and solution attribute, form software fault decision table；

Step 9, according to whether software defect attribute corresponding to the software fault of Failure Diagnostic Code storehouse record, extract the software fault attribute record confirming as software defect and the fault data of coupling, form software defect table；

Step 10, software fault decision table is sent to Client Agent program by the network system of webmaster；Software defect table and unknown software fault attribute list are sent to accident analysis and rule exploitation client；

Step 11, diagnosis process terminate.

Further, step 3 specifically includes following steps:

Step 3.1 carries out order coupling according to the configuration attribute storehouse in the configuration data extracted and fault attribute data base, and the configuration attribute data in configuration attribute data base are the matched rule that developer edits, and are embodied in following if-then form:

If (the exception configuration of extraction meets Trouble Match rule)

Then calculates the software fault numbering of coupling weights and recording configuration attribute number and correspondence

Step 3.2 is numbered index with configuration attribute after completing all of configuration attribute storehouse coupling, is numbered by the configuration attribute of coupling and coupling weights and the corresponding software fault numbering of correspondence collect；Other attributes match processes are identical with configuration attribute.

In the present embodiment, by will be diagnosed the alarm attributes of software system, attribute of performance and configuration attribute and failure cause attribute and solution attribute set up corresponding relation, and be modeled and put in storage, form fault attribute data base and diagnosis rule data base, by software fault diagnosis and task management and interpersonal be divided into serve end program and Client Agent program alternately, Client Agent program is by setting up fault diagnosis task or formulating fault diagnosis plan, trigger server end obtains software system fault data and analyzes, generate fault diagnosis result, result is divided into final Fault Tree Diagnosis Decision table, unknown failure table and software defect table, and respectively final fault diagnosis table is fed back to client, operator are instructed to attempt recovering fault；Unknown failure table and software defect table are fed back to accident analysis and rule exploitation client, for the analysis of system developer and edit new fault attribute and Failure Diagnostic Code, again feed back to server end and update software fault diagnosis attribute database and software fault diagnosis rule base.So, it is achieved that the intelligent diagnostics of software fault and reparation, also achieve the automatic monitoring of software system fault, can constantly improve Failure Diagnostic Code when system is run simultaneously, substantially increase efficiency and the automaticity of software fault diagnosis and reparation.

In addition, with reference to Figure 15, Figure 16 and Figure 17, the present invention also provides for the interaction flow between software system fault diagnosis server (i.e. server end), software system fault diagnosis client (i.e. client) and accident analysis and rule exploitation client, specifically comprises the following steps that

Step a, Client Agent program organization diagnostic task or diagnosis plan, be packaged into command messages, and be sent to service end Agent；

Step b, service end Agent receive command messages that client sends and decode, if diagnostic task then triggers diagnosis process, and return diagnostic result；If diagnosis plan, then update diagnosis plan, and return diagnosis schedule regeneration result；

Step c, Client Agent program receive diagnostic result, are shown to man machine interface；

Step d, Client Agent program receive diagnosis schedule regeneration result, are shown to man machine interface；

If step e exists software defect record, service end Agent sends software defect message by FTP and develops client to accident analysis with rule

If step f diagnostic result does not mate any known attribute, then notice client finds unknown failure, and organizes unknown failure attribute list, is sent to accident analysis and rule exploitation client by FTP

If step g, server-side proxy program detect diagnosis planned timing device time-out, then performing diagnosis plan, step is identical with step a step f.

Additionally, with reference to Figure 18, the present invention also provides for a kind of server end and updates the flow process of software fault attribute database, specifically comprises the following steps that

Step A, system developer develop the new fault attribute of client-side editing and Failure Diagnostic Code by accident analysis and rule, and are encapsulated as Failure Diagnostic Code message, are sent to service end Agent；

Wherein, fault attribute includes numbering and the fault diagnosis primitive of configuration attribute, alarm attributes and performance indications attribute, and Failure Diagnostic Code includes software fault numbering, five meta-attributes and each attribute shared weights in this software fault.

Step B, server-side proxy program receive Failure Diagnostic Code message and decode, and update respectively to fault attribute data base and Failure Diagnostic Code data base；

Step C, server-side proxy program send diagnosis rule renewal results messages and develop client to accident analysis with rule.

Step B specifically includes following steps:

The numbering of the step B.1 server end fault attribute that basis receives respectively judges whether to increase newly, if newly-increased then directly at the newly-increased record of fault attribute data base, if not newly-increased, then renewal fault diagnosis primitive on former record；

Step B.2 server end judges whether to increase newly according to the numbering of the software fault received, if newly-increased then directly at the newly-increased record of Failure Diagnostic Code data base, if not newly-increased, then updates Trouble Match data on former record.

The present invention further provides a kind of software system fault diagnosis server, with reference to the high-level schematic functional block diagram that Fig. 5, Fig. 5 are invention software system fault diagnosis server first embodiment.

In the first embodiment, this software system fault diagnosis server includes:

Fault attribute acquisition module 10, for obtaining the fault attribute being diagnosed software system by network management system；

Match decision module 20, for mating in default rule database according to fault attribute, generates matching degree Fault Tree Diagnosis Decision list from high to low.

Further, with reference to the high-level schematic functional block diagram that Fig. 6, Fig. 6 are invention software system fault diagnosis server the second embodiment.

In a second embodiment, software system fault diagnosis server also includes mating more new module 30, and this coupling more new module 30 is used for:

When fault attribute is mated unsuccessful with the rule database preset, then fault attribute transmission to accident analysis is analyzed with rule exploitation end；

Receive accident analysis and develop the end process new regulation to mating unsuccessful fault attribute and be analyzed gained with rule, and process new regulation is incorporated in rule database.

Further, with reference to the high-level schematic functional block diagram that Fig. 7, Fig. 7 are invention software system fault diagnosis server the 3rd embodiment, and Fig. 8.

In the third embodiment, software system fault diagnosis server also includes DBM 40, and DBM 40 includes:

Attribute builds library unit 401, for forming fault attribute data record respectively according to the fault attribute having verified that, and by this fault attribute data record typing fault attribute data base, wherein, fault attribute includes: configuration attribute, alarm attributes, performance indications attribute, failure cause attribute and solution attribute；

Preferably, attribute is built library unit 401 and is additionally operable to:

Library unit 402 is built in diagnosis, for setting up the mapping relations of phenomenon of the failure and failure cause attribute and solution combinations of attributes, and by these mapping relations typing diagnosis rule data base, wherein, phenomenon of the failure includes configuration attribute, alarm attributes and performance indications attribute, failure cause and solution attribute one_to_one corresponding；

Rule builds library unit 403, for fault attribute data base and diagnosis rule data base are collectively incorporated into rule database, fault attribute data base and the data in diagnosis rule data base in correspondence with each other.

Further, Fig. 9, Fig. 9 is the refinement high-level schematic functional block diagram of match decision module in Fig. 5, and match decision module 20 includes:

Attributes match unit 201, for mating the fault attribute got with mate alarm attributes storehouse, configuration attribute storehouse and the performance indications attribute library in fault attribute data base respectively；

Preliminary matches unit 202, collects sequence, formation preliminary matches bug list for the software fault numbering queue that the fault attribute that fault attribute matched is corresponding；If fault attribute is not matched to any fault attribute, then form unknown failure attribute list, wherein, preliminary matches bug list includes the performance indications attribute queue of the software fault numbering of coupling, the configuration attribute queue of coupling, the alarm attributes queue of coupling, coupling, and the fault attribute queue of each coupling is made up of the fault attribute numbering mated；Unknown failure attribute list includes the configuration attribute not mated, the alarm attributes not mated, the performance indications attribute that do not mate, and the fault attribute queue of everybody coupling is made up of the fault attribute numbering mated；

Weights matching unit 203, mate with fault attribute weights for preliminary matches bug list is numbered with the fault attribute in diagnosis rule data base, draw the matching degree of a coupling fault in preliminary matches bug list, wherein, fault attribute numbering includes configuration attribute numbering, alarm attributes numbering and performance indications numbering, and fault attribute weights include configuration attribute weights, alarm attributes weights and performance indications weights；

Decision-making matching unit 204, for from large to small this coupling fault being ranked up according to the matching degree of in preliminary matches bug list coupling fault, and from diagnosis rule data base, extract the failure cause attribute corresponding with coupling fault phase and solution attribute, forming Fault Tree Diagnosis Decision list, wherein Fault Tree Diagnosis Decision list includes coupling software fault numbering, coupling software fault title, failure cause attribute and solution attribute.

The present invention further provides a kind of software system fault diagnosis system, this software system fault diagnosis system includes software system diagnosis server 100, software system client 200 and accident analysis and rule exploitation end 300,

Software system diagnosis server 100 includes fault attribute acquisition module 10, match decision module 20 and mates more new module 30, wherein,

Match decision module 20, for mating in default rule database according to fault attribute, generates matching degree Fault Tree Diagnosis Decision list from high to low；

Mate more new module 30 to be used for, when fault attribute is mated unsuccessful with the rule database preset, then fault attribute transmission to accident analysis is analyzed with rule exploitation end；

Mate more new module 30 to be additionally operable to: receive accident analysis and develop the end process new regulation to mating unsuccessful fault attribute and be analyzed gained with rule, and process new regulation be incorporated in rule database；

Software system client 200, for providing fault attribute to software system diagnosis server, and receives described Fault Tree Diagnosis Decision list；

Accident analysis and rule exploitation end 300, for receiving the unsuccessful fault attribute of coupling that software system diagnosis server sends over, and be analyzed the unsuccessful fault attribute of this coupling obtaining processing new regulation, process new regulation be incorporated in rule database.

In the present embodiment, serve end program (i.e. software system diagnosis server) runs in the NM server treat diagnosing software system, obtains network management data as requested；Obtaining diagnostic task and diagnosis plan that Client Agent program is sent, and perform task diagnosis, output diagnostic result feeds back to client；Obtain accident analysis and develop, with rule, fault attribute and the Failure Diagnostic Code that client is sent, and update in fault attribute data base and Failure Diagnostic Code storehouse.

Client Agent program passes through manmachine command, editor's diagnostic task and diagnosis plan, and by Transmission Control Protocol, the message comprising diagnostic task and diagnosis plan information is sent to serve end program；Client Agent program obtains the diagnostic result of serve end program graphical representation, operator perform suggestion according to diagnostic result and reparation and be operated, and attempts recovering fault.Accident analysis and rule exploitation client-side program, by manmachine command editor with formulate new fault attribute and Failure Diagnostic Code, and will comprise the message synchronization of fault attribute and Failure Diagnostic Code to serve end program by Transmission Control Protocol；Accident analysis obtains, with rule exploitation client-side program, diagnostic result and the fault data that serve end program FTP mode is sent, and is supplied to research staff's analyzing and positioning.

These are only the preferred embodiments of the present invention; not thereby the scope of the claims of the present invention is limited; every equivalent structure utilizing description of the present invention and accompanying drawing content to make or equivalence flow process conversion; or directly or indirectly it is used in other relevant technical fields, all in like manner include in the scope of patent protection of the present invention.

Claims

1. a software system method for diagnosing faults, it is characterised in that described software system method for diagnosing faults comprises the following steps:

2. software system method for diagnosing faults as claimed in claim 1, it is characterized in that, mate in default rule database according to described fault attribute, also include generate the step of Fault Tree Diagnosis Decision list according to the matching degree of described fault attribute with the rule database preset after:

3. software system method for diagnosing faults as claimed in claim 1 or 2, it is characterised in that also include before the described step being obtained the fault attribute being diagnosed software system by network management system:

4. software system method for diagnosing faults as claimed in claim 3, it is characterised in that the fault attribute that described basis has verified that forms fault attribute data record respectively, and by the step in this fault attribute data record typing fault attribute data base particularly as follows:

5. software system method for diagnosing faults as claimed in claim 4, it is characterised in that

Described diagnosis rule data base includes: software fault numbering, software fault title, configuration attribute group, alarm attributes group, performance indications set of properties, failure cause set of properties, solution set of properties and whether software defect mark；

6. software system method for diagnosing faults as claimed in claim 5, it is characterized in that, described mate in default rule database according to described fault attribute, generate Fault Tree Diagnosis Decision list according to the matching degree of described fault attribute with the rule database preset and include:

7. a software system fault diagnosis server, it is characterised in that described software system fault diagnosis server includes:

8. software system fault diagnosis server as claimed in claim 7, it is characterised in that described software system fault diagnosis server also includes mating more new module, and described coupling more new module is used for:

9. software system fault diagnosis server as claimed in claim 7 or 8, it is characterised in that described software system fault diagnosis server also includes DBM, and described DBM includes:

10. software system fault diagnosis server as claimed in claim 9, it is characterised in that described attribute is built library unit and is additionally operable to:

11. software system fault diagnosis server as claimed in claim 10, it is characterised in that

12. software system fault diagnosis server as claimed in claim 11, it is characterised in that described match decision module includes:

13. a software system fault diagnosis system, it is characterised in that described software system fault diagnosis system includes software system diagnosis server, software system client and accident analysis and rule exploitation end,

Described coupling more new module is used for: