CN113572637A

CN113572637A - Network fault automatic preprocessing method and device

Info

Publication number: CN113572637A
Application number: CN202110803966.9A
Authority: CN
Inventors: 薛竹
Original assignee: Unihub China Information Technology Co Ltd
Current assignee: Unihub China Information Technology Co Ltd; Zhongying Youchuang Information Technology Co Ltd
Priority date: 2021-07-16
Filing date: 2021-07-16
Publication date: 2021-10-29

Abstract

The invention discloses a network fault automatic preprocessing method and a device, wherein the method comprises the following steps: performing correlation analysis according to the network alarm and the routing inspection abnormity to obtain a fault type; matching with a built-in preprocessing rule according to the fault type, if the fault type is not matched with the built-in preprocessing rule, sending a list to perform fault processing, and if the fault type is matched with the built-in preprocessing rule, performing next step of diagnosis and analysis; judging whether automatic preprocessing can be carried out, if so, automatically loading a recovery instruction set, completing automatic issuing of the instruction, if not, judging whether manual preprocessing can be carried out, if so, manually issuing the recovery instruction set, completing manual issuing of the instruction, and if not, dispatching the order to carry out fault processing; and after the recovery instruction is issued, judging whether the fault is recovered, if so, finishing the fault processing, and if not, dispatching the order to perform the fault processing. The method and the device can timely and effectively prevent and preprocess the fault by making a flow analysis means and a preprocessing rule, reduce the working pressure of network operation and maintenance personnel and improve the operation and maintenance efficiency.

Description

Network fault automatic preprocessing method and device

Technical Field

The invention relates to the field of network fault positioning, in particular to a network fault automatic preprocessing method and a network fault automatic preprocessing device.

Background

After receiving fault reporting, operation and maintenance personnel need to adopt a manual mode to judge faults and locate problems, and because network fault location is complicated and complex and involves more links, after receiving fault reporting, the operation and maintenance personnel often tie up the hands ineligibly, the problems are blocked for a long time, and the faults cannot be solved.

Disclosure of Invention

In order to solve the problems existing in the manual network fault positioning, the invention provides a network fault automatic preprocessing method and a network fault automatic preprocessing device.

In order to achieve the purpose, the invention adopts the following technical scheme:

in an embodiment of the present invention, an automated network failure preprocessing method is provided, where the method includes:

performing correlation analysis according to the network alarm and the routing inspection abnormity to obtain a fault type;

matching with a built-in preprocessing rule according to the fault type, if the fault type is not matched with the built-in preprocessing rule, sending a list to perform fault processing, and if the fault type is matched with the built-in preprocessing rule, performing next step of diagnosis and analysis;

judging whether automatic preprocessing can be carried out, if so, automatically loading a recovery instruction set, completing automatic issuing of the instruction, if not, judging whether manual preprocessing can be carried out, if so, manually issuing the recovery instruction set, completing manual issuing of the instruction, and if not, dispatching the order to carry out fault processing;

and after the recovery instruction is issued, judging whether the fault is recovered, if so, finishing the fault processing, and if not, dispatching the order to perform the fault processing.

Further, the preprocessing rules are set according to different fault types;

the preprocessing rules include common causes for the occurrence of fault types, and allow for modification and expansion depending on the actual situation.

Furthermore, a label is set for the preprocessing rule, and the preprocessing is controlled to be in a manual mode or an automatic mode.

Further, the automatic/manual preprocessing comprises specific processing methods and instructions aiming at fault types, wherein certain fault types correspond to a plurality of instructions, and the entries and commands of the instructions are allowed to be added and modified according to actual conditions.

In an embodiment of the present invention, a network failure automatic preprocessing apparatus is further provided, where the apparatus includes:

the correlation analysis module is used for performing correlation analysis according to the network alarm and the routing inspection abnormity to obtain a fault type;

the preprocessing rule module is used for matching with a built-in preprocessing rule according to the fault type, if the fault type does not conform to the preset preprocessing rule, dispatching the order to perform fault processing, and if the fault type conforms to the preset preprocessing rule, performing the next step of diagnosis and analysis;

the automatic/manual preprocessing module is used for judging whether automatic preprocessing can be carried out or not, if so, automatically loading a recovery instruction set and finishing automatic issuing of the instruction, if not, judging whether manual preprocessing can be carried out or not, if so, manually issuing the recovery instruction set and finishing manual issuing of the instruction, and if not, dispatching the order to carry out fault processing;

and the fault recovery judging module is used for judging whether the fault is recovered after the recovery instruction is issued, if so, finishing the fault processing, and if not, dispatching the order to perform the fault processing.

Further, the preprocessing rules are set according to different fault types;

In an embodiment of the present invention, a computer device is further provided, which includes a memory, a processor, and a computer program stored on the memory and executable on the processor, and when the processor executes the computer program, the foregoing network fault automation preprocessing method is implemented.

In an embodiment of the present invention, a computer-readable storage medium is further provided, in which a computer program for executing the network failure automation preprocessing method is stored.

Has the advantages that:

1. according to the invention, by making a flow analysis means and a preprocessing rule, the fault is effectively prevented and preprocessed in time, the working pressure of network operation and maintenance personnel is reduced, and the operation and maintenance efficiency is improved.

2. According to the invention, different preprocessing rules are built in according to the fault type, and the preprocessing rules can be modified and expanded according to the actual situation, so that the reliability and flexibility of the device are enhanced, and the operation and maintenance problem is solved practically.

3. According to the invention, different preprocessing instructions are set according to the preprocessing rules, the entries and commands of the preprocessing instructions can be added and modified according to the actual conditions, and the expandability of the device is high.

Drawings

FIG. 1 is a schematic flow diagram of a network fault automated pre-processing method of the present invention;

FIG. 2 is a block diagram of a preprocessing of an OSPF neighbor Down according to an embodiment of the present invention;

FIG. 3 is a flow chart illustrating the preprocessing of an OSPF neighbor Down according to an embodiment of the present invention;

FIG. 4 is a schematic structural diagram of an automated network failure preprocessing apparatus according to an embodiment of the present invention;

fig. 5 is a schematic structural diagram of a computer device according to an embodiment of the present invention.

Detailed Description

The principles and spirit of the present invention will be described below with reference to several exemplary embodiments, which should be understood to be presented only to enable those skilled in the art to better understand and implement the present invention, and not to limit the scope of the present invention in any way. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the disclosure to those skilled in the art.

As will be appreciated by one skilled in the art, embodiments of the present invention may be embodied as a system, apparatus, device, method, or computer program product. Accordingly, the present disclosure may be embodied in the form of: entirely hardware, entirely software (including firmware, resident software, micro-code, etc.), or a combination of hardware and software.

According to the embodiment of the invention, an evaluation model is established according to data such as alarm and routing inspection results and built-in predefined rules, the network is analyzed and evaluated, network hidden dangers are found in advance, the faults are prevented, the faults are quickly positioned, and the faults are preprocessed, so that the faults possibly caused by the hidden dangers of the network are solved.

The principles and spirit of the present invention are explained in detail below with reference to several representative embodiments of the invention.

Fig. 1 is a schematic flow chart of an automated network failure preprocessing method according to an embodiment of the present invention. As shown in fig. 1, the method includes:

performing correlation analysis according to network alarm (passive reception) and routing inspection abnormity (active detection) to obtain a fault type;

It should be noted that although the operations of the method of the present invention have been described in the above embodiments and the accompanying drawings in a particular order, this does not require or imply that these operations must be performed in this particular order, or that all of the operations shown must be performed, to achieve the desired results. Additionally or alternatively, certain steps may be omitted, multiple steps combined into one step execution, and/or one step broken down into multiple step executions.

For a clearer explanation of the above network fault automatic preprocessing method, a specific embodiment is described below, however, it should be noted that the embodiment is only for better explaining the present invention and is not to be construed as an undue limitation to the present invention.

Example (b):

fig. 2 is a block diagram of preprocessing of an OSPF neighbor Down according to an embodiment of the present invention. As shown in fig. 2, includes:

1. the type of failure: OSPF neighbor Down.

2. The method is characterized in that preprocessing rules are built in, and common reasons of the faults comprise: BFD fault, opposite terminal equipment fault, CPU utilization rate overhigh, link fault, interface without UP, IP addresses at two ends not in the same network segment, RouterID configuration conflict, configuration inconsistency of area types at two ends and configuration inconsistency of OSPF parameters at two ends.

3. Automatic/manual preprocessing, and the specific method and instructions for processing the faults comprise: reducing the number of OSPF enabled interfaces, modifying the IP addresses of both ends to make them in the same network segment, modifying MTU values of both ends of link to be consistent, modifying configuration to make RouterID unique in AS domain and modifying configuration to make OSPF Area IDs of both ends consistent, etc. In order to ensure safety and reliability, preprocessing instructions are issued in a manual mode in the early stage, and after the preprocessing instructions are verified to be mature and reliable for multiple times, the preprocessing instructions are issued in an automatic mode. The switch (label) can control which preprocesses are manual mode, and which preprocesses are automatic mode, and can be adjusted dynamically.

Fig. 3 is a schematic diagram illustrating a preprocessing flow of an OSPF neighbor Down according to an embodiment of the present invention. As shown in fig. 3, the specific pretreatment process is as follows:

s01, checking the reason of OSPF neighbor Down through log

The viewing log information is as follows:

NBR_DOWN_REASON(l):Neighbor state leaves full or changed to Down.

(ProcessId＝[USHORT],NeighborRouterId＝[IPADDR],NeighborAreaId＝[ULONG],NeighborInterface＝[STRING],NeighborDownIm mediate reason＝[STRING],NeighborDownPrimeReason＝[STRING],NeighborChangeTime＝[STRING])

this key records the reason for the OSPF neighbor Down.

The reasons for the OSPF neighbor Down are the following:

(1)Neighbor Down Due to Inactivity

indicating that no Hello message received within the deadline results in an OSPF neighbor Down, which case please execute S02.

(2)Neighbor Down Due to Kill Neighbor

Indicating that the operation of restarting the ospf process is performed because of the interface Down, BFD Down or the like. At this time, the specific reason can be judged by looking at the neighbordynprimereason field:

a. if the Interface State Change is Physical Interface State Change, the Interface State is changed, a display Interface command is executed to check the Interface State, and the Interface fault is eliminated.

b. If the Session state is BFD Session Down, the state of BFD Session is changed into Down, and the BFD fault is checked.

c. If the OSPF Process Reset is used, the operation of 'restarting the OSPF Process' is performed, the OSPF Process is restarting, and the OSPF Process needs to wait for the OSPF to reestablish the neighbor relation.

(3) Neighbor Down Due to 1-Wayhello Received or Neighbor Down Due to sequence Num Mismatch

Indicating that the local side OSPF state also becomes Down because the opposite side OSPF state first becomes Down, thus sending 1-Wayhello to the local side. This situation requires the peer device to be checked for reasons. Otherwise, S09 is executed.

S02, checking whether the link fails: it is checked whether the device link is down. If the link is normal, S03 is performed.

S03, checking whether the CPU utilization rate is too high

Executing the display CPU-use command checks whether the CPU utilization ROUT field value of the failed device exceeds 60%. If the CPU utilization rate is too high, OSPF can not normally transmit and receive protocol messages, and neighbor oscillation is caused. If the CPU utilization exceeds 60%, S09 is executed, otherwise S04 is executed.

S04, checking whether the interface state is UP

Executing a display interface command to check the state of the physical layer of the interface, and if the state of the physical layer of the interface is Down, firstly processing the problem of interface failure; if the interface physical layer state is UP, the display OSPF interface is executed to check whether the interface state is Down under the OSPF protocol. The normal state of the interface under the OSPF protocol may be DR, BDR, DR Other or P2P, etc.

(1) If the state of the interface is Down under the OSPF protocol, executing a command display OSPF cumulant to check whether the number of enabled interfaces under the OSPF process exceeds the specification, and if so, reducing the number of enabled interfaces of the OSPF.

(2) If the interface state is not Down under the OSPF protocol, S05 is executed.

S05, if the interface is broadcast network or NBMA network, checking whether the IP addresses of both ends are in the same network segment.

(1) If the IP addresses are not in the same network segment, the IP addresses at the two ends are modified to be in the same network segment.

(2) If the IP addresses are in the same network segment, execution proceeds to S06.

S06, checking whether MTUs of each interface are consistent

If OSPF MTU-enable is enabled on the interface, the MTUs of the interface are required to be consistent, otherwise the OSPF neighbors cannot negotiate successfully.

(1) And if the MTU value configurations of the interfaces are not consistent, the MTU values at the two ends of the link are modified to be consistent.

(2) If the MTU value configuration of the interface is consistent, S07 is executed.

S07, checking whether the priority of each interface is nonzero

For Broadcast and NBMA type network segments, at least one of the interface priorities is non-zero to ensure that DR can be correctly elected, otherwise the neighbor states on both sides can only reach 2-Way.

The command display ospf interface is executed to view the priority of the interface.

S08, checking whether the configuration of OSPF at two ends has error

(1) Checking whether OSPF Router ID configurations at both ends are the same

If so, the ospf Router-ID command is executed to modify the configuration to make the Router ID unique within the AS domain, otherwise the following check is continued.

(2) Checking whether the OSPF Area ID configurations at both ends are consistent

If not, the configuration is modified to make the OSPF Area IDs at both ends consistent, otherwise, the following checks are continued.

(3) Checking whether other configurations of OSPF at both ends are consistent

The command display ospf error is executed every 10 seconds for 5 minutes.

a. And looking up the Bad authentication type field, if the count value corresponding to the field is increased all the time, the OSPF authentication types configured by the two devices for establishing the neighbor are inconsistent, and the two devices need to execute the area-authentication-mode command to configure the same authentication type.

b. And looking up the Hello timer mismatch field, if the count value corresponding to the field is increased all the time, indicating that the Hello timer configuration on the interface is inconsistent, and executing an ospf timer Hello command to make the Hello timer interval configuration consistent by checking the interface configuration of the equipment at the two ends.

c. And looking up the Dead timer mismatch field, if the count value corresponding to the field is always increased, indicating that the Dead timer configuration of the interface is inconsistent, and executing an ospf timer Dead command to make the Dead timer interval configuration consistent by checking the interface configuration of the equipment at the two ends.

If the fault still exists, S09 is executed.

And S09, collecting the execution result of the steps, the configuration file of the equipment, the log information and the alarm information, and transferring the order to fault processing.

Based on the same invention concept, the invention also provides a network fault automatic preprocessing device. The implementation of the device can be referred to the implementation of the method, and repeated details are not repeated. The term "module," as used below, may be a combination of software and/or hardware that implements a predetermined function. Although the means described in the embodiments below are preferably implemented in software, an implementation in hardware, or a combination of software and hardware is also possible and contemplated.

Fig. 4 is a schematic structural diagram of an automatic network failure preprocessing apparatus according to an embodiment of the present invention. As shown in fig. 4, the apparatus includes:

the correlation analysis module 101 is used for performing correlation analysis according to the network alarm and the routing inspection abnormity to obtain a fault type;

the preprocessing rule module 102 is configured to match a built-in preprocessing rule according to a fault type, send a list to perform fault processing if the fault type does not match the built-in preprocessing rule, and perform the next step of diagnosis and analysis if the fault type does match the built-in preprocessing rule;

the preprocessing rules are set according to different fault types;

the preprocessing rules comprise common reasons for fault types, and are allowed to be modified and expanded according to actual conditions;

the automatic/manual preprocessing module 103 is used for judging whether automatic preprocessing can be performed, if so, automatically loading a recovery instruction set and completing automatic issuing of the instruction, if not, judging whether manual preprocessing can be performed, if so, manually issuing the recovery instruction set and completing manual issuing of the instruction, and if not, dispatching the order to perform fault processing;

the automatic/manual preprocessing comprises specific processing methods and instructions aiming at fault types, wherein some fault types correspond to a plurality of instructions, and the entries and commands of the instructions are allowed to be added and modified according to actual conditions;

setting a label for the pretreatment rule, and controlling the pretreatment to be in a manual mode or an automatic mode;

and the fault recovery judging module 104 is configured to judge whether the fault is recovered after the recovery instruction is issued, if yes, finish fault processing, and if not, forward the order to the fault processing.

It should be noted that although several modules of the network fault automation pre-processing apparatus are mentioned in the above detailed description, such division is merely exemplary and not mandatory. Indeed, the features and functionality of two or more of the modules described above may be embodied in one module according to embodiments of the invention. Conversely, the features and functions of one module described above may be further divided into embodiments by a plurality of modules.

Based on the aforementioned inventive concept, as shown in fig. 5, the present invention further provides a computer device 200, which includes a memory 210, a processor 220, and a computer program 230 stored on the memory 210 and operable on the processor 220, wherein the processor 220 implements the aforementioned network failure automated preprocessing method when executing the computer program 230.

Based on the above inventive concept, the present invention further provides a computer-readable storage medium storing a computer program for executing the foregoing network fault automation preprocessing method.

According to the automatic network fault preprocessing method and device provided by the invention, the faults are effectively prevented and preprocessed in time by making a flow analysis means and a preprocessing rule, the working pressure of network operation and maintenance personnel is reduced, and the operation and maintenance efficiency is improved.

While the spirit and principles of the invention have been described with reference to several particular embodiments, it is to be understood that the invention is not limited to the disclosed embodiments, nor is the division of aspects, which is for convenience only as the features in such aspects may not be combined to benefit. The invention is intended to cover various modifications and equivalent arrangements included within the spirit and scope of the appended claims.

The limitation of the protection scope of the present invention is understood by those skilled in the art, and various modifications or changes which can be made by those skilled in the art without inventive efforts based on the technical solution of the present invention are still within the protection scope of the present invention.

Claims

1. An automated network failure preprocessing method, comprising:

2. The method according to claim 1, wherein the preprocessing rules are set according to different fault types;

the preprocessing rules include common reasons for the fault type to occur, and are allowed to be modified and expanded according to actual conditions.

3. The method according to claim 1 or 2, wherein a label is set for the preprocessing rule, and the preprocessing is controlled to be manual or automatic.

4. The method according to claim 1, wherein the automatic/manual preprocessing comprises specific processing methods and instructions for fault types, some fault types correspond to multiple instructions, and the entries and commands of the instructions are allowed to be added and modified according to actual conditions.

5. An automated network failure preprocessing apparatus, comprising:

6. The network fault automated preprocessing device of claim 5, wherein the preprocessing rules are set according to different fault types;

7. The automatic preprocessing device of network fault according to claim 5 or 6, characterized in that, setting label for the preprocessing rule, controlling preprocessing to be manual mode or automatic mode.

8. The device according to claim 5, wherein the automatic/manual preprocessing comprises specific processing methods and instructions for fault types, some fault types correspond to multiple instructions, and the entries and commands of the instructions allow addition and modification according to actual conditions.

9. A computer device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, wherein the processor implements the method of claim 1 or 2 or 4 when executing the computer program.

10. A computer-readable storage medium, characterized in that the computer-readable storage medium stores a computer program for executing the method of claim 1 or 2 or 4.