Network equipment fault processing method and system, electronic equipment and storage medium

Abstract

The invention relates to a network equipment fault processing method and system, electronic equipment and a storage medium, and the network equipment fault processing method comprises the steps: obtaining the port state information of at least one network equipment, determining database index information according to the port state information, and carrying out the abnormality analysis based on the database index information, determining a first exception analysis result, performing self-healing planning processing based on the first exception analysis result in combination with the historical fault information to obtain network configuration file information, and then triggering the network device to update a port state according to the network configuration file information; therefore, self-adaptive self-healing processing can be carried out on the network equipment abnormity, the labor cost can be effectively reduced, the processing efficiency can be improved, and the problem that the network equipment abnormity processing efficiency is low due to the fact that abnormity reasons need to be manually searched when the network equipment is abnormal in the prior art is solved.

Description

Technical Field

[0001] The present invention relates to the field of computer technology, and in particular to a network device fault processing method, system, electronic device and storage medium. Background Art

[0002] With the development of the Internet, in the existing network architecture, aggregated links can increase the bandwidth between network devices, effectively improve system reliability, and are widely used in various network architectures. As the traffic carrying port of the aggregated link, once a failure occurs, the aggregated port will cause port traffic loss, the original load balancing state will be destroyed, and the stable operation of the system will be affected.

[0003] In the prior art, when a network device is abnormal, a worker is required to manually search for the cause of the abnormality and solve it. However, with the expansion of network services, the number of network devices is also increasing rapidly, and manual search at this time will be inefficient. Summary of the invention

[0004] The present application provides a network device fault handling method, system, electronic device and storage medium to solve the problem of low efficiency in network device abnormality handling caused by the need to manually search for the cause of the abnormality and solve it when the network device has an abnormality.

[0005] In a first aspect, the present application provides a method for handling a network device failure, comprising:

[0006] Obtaining port status information of at least one network device;

[0007] Determining database indicator information according to the port status information;

[0008] Perform an abnormality analysis based on the database indicator information to determine a first abnormality analysis result;

[0009] Based on the first abnormality analysis result, self-healing planning is performed in combination with historical fault information to obtain network configuration file information;

[0010] According to the network configuration file information, the network device is triggered to update the port status.

[0011] Optionally, the self-healing planning process is performed based on the first abnormality analysis result and in combination with historical fault information to obtain network configuration file information, including:

[0012] When the first abnormality analysis result is a port abnormality result, obtaining at least one historical fault information from a preset fault ticket database;

[0013] Determining whether the database indicator information matches the historical fault information;

[0014] In the case where the database indicator information does not match the historical fault information, generating restart configuration file information corresponding to the network device;

[0015] The restart configuration file information is determined as the network configuration file information.

[0016] Optionally, after determining whether the database indicator information matches the historical fault information, the step further includes:

[0017] When the database indicator information matches the historical fault information, obtaining historical configuration file information corresponding to the historical fault information;

[0018] The historical configuration file information is determined as the network configuration file information.

[0019] Optionally, triggering the network device to update the port status according to the network configuration file information includes:

[0020] According to the network configuration file information, trigger the network device to restart the port, and obtain restart port status information after the network device restarts the port;

[0021] Perform an abnormality analysis based on the restart port status information to determine a second abnormality analysis result;

[0022] In the case where the second abnormality analysis result is a port abnormality result, generating shutdown configuration file information corresponding to the network device;

[0023] According to the shutdown configuration file information, the network device is triggered to close the port state.

[0024] Optionally, after triggering the network device to close the port state according to the closing configuration file information, the method further includes:

[0025] Obtaining closed port status information after the network device closes the port;

[0026] Performing traffic analysis based on the closed port status information to determine a traffic analysis result;

[0027] If the flow analysis result meets the preset flow condition, a self-healing success result is generated;

[0028] When the flow analysis result does not meet the preset flow condition, a self-healing failure result is generated, and fault prompt information is output based on the self-healing failure result.

[0029] Optionally, performing traffic analysis based on the closed port status information to determine a traffic analysis result includes:

[0030] Based on the closed port status information, determine a first flow difference value corresponding to a target port in the network device, wherein the target port is a port closed when the network device closes a port, and the first flow information is a flow difference value before and after the target port is closed;

[0031] Obtaining second flow difference values ​​corresponding to other ports in the network device;

[0032] Comparing the first flow difference value with the second flow difference value to obtain a flow difference comparison result;

[0033] The flow analysis result is generated according to the flow difference comparison result.

[0034] Optionally, determining database indicator information according to the port status information includes:

[0035] Storing the port status information in a preset database;

[0036] From the preset database, preset indicator data corresponding to the network device is extracted to obtain the database indicator information.

[0037] In a second aspect, the present application provides a network device fault handling system, comprising:

[0038] An indicator monitoring module, used to obtain port status information of at least one network device;

[0039] A determination module, used to determine database indicator information according to the port status information;

[0040] An abnormality analysis module, used to perform abnormality analysis based on the database indicator information and determine a first abnormality analysis result;

[0041] A self-healing planning module, configured to perform self-healing planning processing based on the first abnormality analysis result and in combination with historical fault information to obtain network configuration file information;

[0042] The network configuration module is used to trigger the network device to update the port status according to the network configuration file information.

[0043] In a third aspect, an electronic device is provided, comprising a processor, a communication interface, a memory and a communication bus, wherein the processor, the communication interface and the memory communicate with each other via the communication bus;

[0044] Memory, used to store computer programs;

[0045] The processor is used to implement the network device fault handling method described in any one of the first aspects when executing the program stored in the memory.

[0046] According to a fourth aspect, a computer-readable storage medium is provided, on which a computer program is stored. When the computer program is executed by a processor, the network device fault handling method as described in any one of the first aspects is implemented.

[0047] The embodiment of the present application obtains port status information of at least one network device, determines database indicator information based on the port status information, performs an exception analysis based on the database indicator information, determines a first exception analysis result, and performs self-healing planning processing based on the first exception analysis result in combination with historical fault information to obtain network configuration file information, and then triggers the network device to update the port status based on the network configuration file information; thereby, adaptive self-healing processing can be performed on network device exceptions, which can effectively reduce labor costs and improve processing efficiency, thereby solving the problem of low efficiency in network device exception processing caused by the need to manually search for the cause of the exception when an exception occurs in the network device in the existing related technology. BRIEF DESCRIPTION OF THE DRAWINGS

[0048] Figure 1 A flowchart of a method for handling network device failures provided in an embodiment of the present application;

[0049] Figure 2 A schematic diagram of an application scenario of a method for handling network device failures provided in an embodiment of the present application;

[0050] Figure 3 A schematic diagram of another application scenario of a network device fault handling method provided in an embodiment of the present application;

[0051] Figure 4 A schematic diagram of another application scenario of a network device fault handling method provided in an embodiment of the present application;

[0052] Figure 5 A schematic diagram of the structure of a network device fault handling system provided in an embodiment of the present application;

[0053] Figure 6 A schematic diagram of an application scenario of a network device fault handling system provided in an embodiment of the present application;

[0054] Figure 7 A schematic diagram of the structure of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0055] The following will describe the embodiments of the present invention with reference to the accompanying drawings and preferred embodiments. Those skilled in the art can easily understand other advantages and effects of the present invention from the contents disclosed in this specification. The present invention can also be implemented or applied through other different specific embodiments, and the details in this specification can also be modified or changed in various ways based on different viewpoints and applications without departing from the spirit of the present invention. It should be understood that the preferred embodiments are only for illustrating the present invention, not for limiting the scope of protection of the present invention.

[0056] In computer networks, port aggregation is a network technology that increases transmission bandwidth and provides link redundancy by combining multiple physical ports or logical ports into one logical port; link aggregation is a technology that bundles multiple physical interfaces together to form a logical interface, which is mainly used to increase network bandwidth, improve reliability and performance; link bundling is achieved through aggregated interfaces. Multiple Ethernet interfaces are bundled together to form an aggregation group, and these bundled Ethernet interfaces are called member ports of the aggregation group. Each aggregation group uniquely corresponds to a logical interface, called an aggregated interface. It can be seen that existing network links usually require a large number of network devices and ports to be used in conjunction. As the complexity of the network architecture continues to increase, the number of network devices and ports also increases. In order to enable the normal operation of the network architecture, it is necessary to pre-configure network operation and maintenance personnel to discover and handle the anomalies of each network device; however, the large number of network devices only relies on manual maintenance by operation and maintenance personnel, which not only requires a large amount of labor costs, but also has the problem of low efficiency in handling network device anomalies.

[0057] In order to solve the problem of low efficiency in handling network device exceptions due to the need to manually search for the cause of the exception and solve it when an exception occurs in a network device, the present application provides a network device fault handling method, system, electronic device and storage medium, by obtaining port status information of at least one network device, determining database indicator information based on the port status information, performing exception analysis based on the database indicator information, determining a first exception analysis result, and performing self-healing planning processing based on the first exception analysis result in combination with historical fault information to obtain network configuration file information, and then triggering the network device to update the port status based on the network configuration file information; thereby, adaptive self-healing processing can be performed on the network device exception, which can effectively reduce labor costs and improve processing efficiency, thereby solving the problem of low efficiency in handling network device exceptions due to the need to manually search for the cause of the exception and solve it when an exception occurs in a network device.

[0058] Figure 1A flow chart of a network device fault handling method provided for an embodiment of the present application. The method can be applied to one or more electronic devices such as a network device management system, a network client, a network server, etc. In addition, the execution subject of the method can be hardware or software. When the above-mentioned execution subject is hardware, the execution subject can be one or more of the above-mentioned electronic devices. For example, a single electronic device can execute the method, or multiple electronic devices can cooperate with each other to execute the method. When the above-mentioned execution subject is software, the method can be implemented as multiple software or software modules, or as a single software or software module. No specific limitation is made here.

[0059] like Figure 1 As shown, a network device fault handling method provided in an embodiment of the present application may specifically include the following steps:

[0060] Step S110: Acquire port status information of at least one network device.

[0061] Among them, the network device can represent the device in the network architecture, such as switches, routers and other devices, and the port status information can represent the status information of the specific port of the network device; for example, the port status information can include but is not limited to the opening status, packet loss rate, protocol status, transmit and receive optical power, optical attenuation value, voltage and current, temperature, whether it is frequently UP / DOWN and other information; this embodiment does not make specific limitations on this.

[0062] It should be noted that, since the port status information may represent the status information of a specific port of a network device, when there are multiple network devices in the network architecture and the network device has multiple ports, the port status information corresponding to each port in each network device may be obtained; this embodiment does not specifically limit this.

[0063] Step S120: Determine database indicator information according to the port status information.

[0064] Specifically, after the port status information is obtained, the database indicator information may be determined according to the port status information, and the database indicator information may represent indicator information pre-configured for determining port abnormalities.

[0065] It should be noted that after obtaining the port status information, the port status information can be stored in a preset database, so that the database indicator information corresponding to each network device can be extracted from the preset database; for example, in the case where the indicator information pre-configured for judging port abnormality is the opening state, packet loss rate, protocol state, receiving and transmitting optical power, and optical attenuation value, if the port status information collected from network device A includes the opening state, packet loss rate, protocol state, receiving and transmitting optical power, optical attenuation value, voltage and current, temperature, and whether it is frequently UP / DOWN, the opening state, packet loss rate, protocol state, receiving and transmitting optical power, optical attenuation value, voltage and current, temperature, and whether it is frequently UP / DOWN can be stored in the preset database; then the database indicator information corresponding to the network device A can be extracted from the preset database as the opening state, packet loss rate, protocol state, receiving and transmitting optical power, and optical attenuation value information. The above is only an example, and this embodiment does not make specific restrictions on this. In addition, the period for collecting port status information and the period for determining the database indicator information corresponding to the network device can be independent of each other and configured separately, and this embodiment does not make specific restrictions on this.

[0066] Step S130: Perform an abnormality analysis based on the database indicator information to determine a first abnormality analysis result.

[0067] Specifically, after determining the database indicator information, an abnormality analysis can be performed based on the database indicator information to determine a first abnormality analysis result, and the first abnormality analysis result can indicate an analysis result of whether the database indicator information has an abnormality. The first abnormality analysis result can be a port abnormality result or a port normal result, and the port abnormality result can be used to indicate a result that the database indicator information has an abnormality, and the port normal result can be used to indicate a result that the database indicator information does not have an abnormality.

[0068] Specifically, in the process of performing abnormal analysis of database indicator information, each indicator information contained in the database indicator information can be analyzed separately; that is, preset indicator information corresponding to the database indicator information can be obtained, and the preset indicator information is used to indicate the state corresponding to each indicator when the port is normal, such as the port is open, there is no packet loss, the protocol state is UP, the transmit and receive optical power meets the threshold, the optical attenuation value is not too large, the voltage and current are in the normal range, the temperature is in the normal range, and it is not frequently up / down; when the database indicator information includes the open state, packet loss rate, protocol state, transmit and receive optical power, optical attenuation value, voltage and current, temperature, whether it is frequently UP / DOWN, the abnormal analysis at this time is to analyze each indicator information contained in the database indicator information separately, that is, it is necessary to judge whether the port is open, whether there is packet loss, whether the protocol is UP, whether the transmit and receive optical power meets the threshold, whether the optical attenuation value is too large, whether the voltage and current and temperature are in the normal range, and whether it is frequently up / down; then the independent indicator analysis results obtained by analyzing each indicator information separately, and the first abnormal analysis result is obtained by all independent indicator analysis results. Of course, the above is only an example for illustration, and this embodiment does not make specific limitations on this.

[0069] Step S140: Based on the first abnormality analysis result and in combination with historical fault information, self-healing planning is performed to obtain network configuration file information.

[0070] Specifically, after obtaining the first exception analysis result, historical fault information can be obtained, and the historical fault information can represent the pre-stored fault information of the history of each network device; thus, based on the first exception analysis result and in combination with the historical fault information, self-healing planning processing can be performed to obtain network configuration file information, wherein the network configuration file information can represent a configuration file used to trigger the network device to update the port status, and the specific healing planning processing can be to determine the network configuration file information corresponding to the network device based on the fault processing information, or to determine the network configuration file information corresponding to the network device based on the preset exception processing logic. Of course, other methods can also be used to obtain the network configuration file information, and this embodiment does not specifically limit this.

[0071] Step S150: triggering the network device to update the port status according to the network configuration file information.

[0072] Specifically, after determining the network configuration file information, the network device can be triggered to update the port state according to the network configuration file information, and the network device can be used to adaptively change the port state according to the network configuration file information, such as restarting, shutting down, etc., which is not specifically limited in this embodiment. It should be noted that after obtaining the network configuration file information, the configuration file can be sent to the network device to trigger the network device to change the port state according to the network configuration file information.

[0073] It can be seen that this embodiment obtains the port status information of at least one network device, determines the database indicator information based on the port status information, and performs anomaly analysis based on the database indicator information to determine the first anomaly analysis result; it can perform adaptive anomaly analysis on each network device, which requires manual detection and can greatly reduce labor costs; and based on the first anomaly analysis result, self-healing planning is performed in combination with historical fault information to obtain network configuration file information, and then the network device is triggered to update the port status based on the network configuration file information; thereby, adaptive self-healing processing can be performed on network device anomalies without the need for manual processing of all anomalies, which can effectively reduce labor costs and improve processing efficiency, thereby solving the problem of inefficient network device anomaly processing caused by the need to manually search for the cause of the anomaly and solve it when the network device has an anomaly.

[0074] In an optional embodiment of the present application, step S140 performs self-healing planning processing based on the first exception analysis result and in combination with historical fault information to obtain network configuration file information, which may specifically include the following steps: when the first exception analysis result is a port exception result, obtaining at least one historical fault information from a preset fault ticket database; determining whether the database indicator information matches the historical fault information; when the database indicator information does not match the historical fault information, generating restart configuration file information corresponding to the network device; and determining the restart configuration file information as the network configuration file information.

[0075] After obtaining the first abnormality analysis result, this embodiment can determine whether the first abnormality analysis result is a port abnormality result. When the first abnormality analysis result is not a port abnormality result, it indicates that the network device is in a normal state, and there is no need to perform subsequent steps at this time; and when the first abnormality analysis result is a port abnormality result, it indicates that the network device is in an abnormal state. At this time, at least one historical fault information is obtained from a preset fault ticket database, wherein the fault ticket database may be a database pre-configured for the existence of historical fault information, such as a third-party fault ticket database, etc.; thereby, the database indicator information can be matched with the historical fault information, and it can be determined whether the database indicator information matches the historical fault information. When the database indicator information does not match the historical fault information, restart configuration file information corresponding to the network device can be generated at this time, wherein the restart configuration file information can represent a configuration file pre-configured for triggering the network device to restart; and the restart configuration file information can be determined as the network configuration file information.

[0076] In an optional embodiment of the present application, after determining whether the database indicator information matches the historical fault information, the following steps may be specifically included: when the database indicator information matches the historical fault information, obtaining historical configuration file information corresponding to the historical fault information; and determining the historical configuration file information as network configuration file information.

[0077] Specifically, after determining whether the database indicator information matches the historical fault information, if the database indicator information matches the historical fault information, the historical configuration file information corresponding to the historical fault information can be obtained, and the historical configuration file information can indicate the configuration file used when processing the fault indicated by the historical fault information; since the database indicator information matches the historical fault information, it means that the anomaly of the current network device and the fault indicated by the historical fault information belong to the same problem, then the historical configuration file information corresponding to the historical fault information can be determined as the network configuration file information, thereby playing a role in quickly determining the network configuration file information corresponding to the current network device in combination with the historical fault processing situation, which can effectively improve the efficiency of network device anomaly processing.

[0078] In one example, when the optical attenuation value included in the database indicator information has an abnormality of being too large, and the historical fault information also indicates a fault of too large optical attenuation value, the historical configuration file information corresponding to the fault of too large optical attenuation value can be obtained, and the historical configuration file information is determined as the network configuration file information, so that after the subsequent execution of the step of triggering the network device to update the port status according to the network configuration file information, the abnormality of the optical attenuation value of the network device being too large can be quickly resolved, thereby improving the efficiency of abnormal handling of the network device.

[0079] In an optional embodiment of the present application, step S150 triggers the network device to update the port status based on the network configuration file information, which may specifically include the following steps: triggering the network device to restart the port based on the network configuration file information, and obtaining the restart port status information after the network device restarts the port; performing an abnormality analysis based on the restart port status information, and determining a second abnormality analysis result; when the second abnormality analysis result is a port abnormality result, generating a shutdown configuration file information corresponding to the network device; and triggering the network device to close the port status based on the shutdown configuration file information.

[0080] After determining the network configuration file information, this embodiment can trigger the network device to restart the port according to the network configuration file information, and obtain the restart port status information after the network device restarts the port, wherein the restart port is to restart the specific port corresponding to the port status information, and the restart port status information can indicate the port status of the specific port after the restart, that is, the restart port status information and the port status information can contain the same data type, and both are status information of the specific port collected at different time points; thus, an abnormality analysis can be performed based on the restart port status information to determine the second abnormality analysis result, and the abnormality analysis and the second abnormality analysis result are similar to the aforementioned step of "performing an abnormality analysis based on the database indicator information to determine the first abnormality analysis result", which will not be repeated here; further, it can be determined whether the second abnormality analysis result is a port abnormality result, and if the second abnormality analysis result is not a port abnormality result, it means that the abnormality is eliminated after the network device restarts the port, and then there is no need to perform subsequent steps; and if the second abnormality analysis result is a port abnormality result, it means that the abnormality is not eliminated after the network device restarts the port, and then the corresponding closing configuration file information of the network device can be generated, and the closing configuration file information can indicate a configuration file used to trigger the network device to close the port; that is, the network device can be triggered to close the port status according to the closing configuration file information.

[0081] In an optional embodiment of the present application, after triggering the network device to close the port status based on the closing configuration file information, the following steps may be specifically included: obtaining the closed port status information after the network device closes the port; performing traffic analysis based on the closed port status information to determine the traffic analysis result; if the traffic analysis result meets the preset traffic conditions, generating a self-healing success result; if the traffic analysis result does not meet the preset traffic conditions, generating a self-healing failure result, and outputting fault prompt information based on the self-healing failure result.

[0082] In this embodiment, after triggering the network device to close the port state according to the closing configuration file information, the closed port state information after the network device closes the port can be obtained, wherein the closed port is the specific port corresponding to the port state information that is closed, and the closed port state information can indicate the port state of the specific port after being closed, that is, the closed port state information and the aforementioned restart port state information and port state information can contain the same data type, and the three are the state information of the specific port collected at different time points; thereby, traffic analysis can be performed based on the closed port state information to determine the traffic analysis result, wherein the traffic analysis can indicate the analysis of the traffic changes of all ports of the network device after the network device closes the specific port corresponding to the port state information, and the traffic analysis result can indicate whether the traffic changes of all ports of the network device meet the preset traffic conditions; that is, when the traffic analysis result meets the preset traffic conditions, a self-healing success result can be generated, and when the traffic analysis result does not meet the preset traffic conditions, a self-healing failure result can be generated, and a fault prompt information is output based on the self-healing failure result. Among them, the self-healing success result can indicate the result of the current network device anomaly being repaired through self-healing processing, the self-healing failure result can indicate the result of the current network device anomaly being failed to be repaired through self-healing processing, and the output fault prompt information can indicate the information used to prompt the operation and maintenance personnel that the current network device self-healing processing has failed, and then by outputting the output fault prompt information, the operation and maintenance personnel can be prompted to perform manual processing.

[0083] In an optional embodiment of the present application, traffic analysis is performed based on the closed port status information to determine the traffic analysis result, which may specifically include the following steps: based on the closed port status information, determining a first traffic difference corresponding to a target port in the network device, the target port is a port closed when the network device closes the port, and the first traffic information is the traffic difference before and after the target port is closed; obtaining a second traffic difference corresponding to other ports in the network device; comparing the first traffic difference and the second traffic difference to obtain a traffic difference comparison result; and generating a traffic analysis result based on the traffic difference comparison result.

[0084] In the process of performing traffic analysis based on the closed port status information to determine the traffic analysis result, this embodiment can determine a first traffic difference corresponding to a target port in a network device based on the closed port status information, wherein the target port is a port closed when the network device closes the port, that is, a specific port corresponding to the port status information, and the first traffic information is a traffic difference before and after the target port is closed; and obtain second traffic differences corresponding to other ports in the network device, the second traffic difference can represent the traffic difference of other ports before and after the target port is closed; thereby, the first traffic difference and the second traffic difference can be compared to obtain a traffic difference comparison result, and the traffic difference comparison result can represent the result of whether the first traffic difference matches the second traffic difference. The specific way of comparing the first traffic difference and the second traffic difference can be to determine whether the first traffic difference is consistent with the second traffic difference, or to determine whether the target traffic difference between the first traffic difference and the second traffic difference is within a preset difference range. Of course, it can also be a comparison method, which is not specifically limited in this embodiment. Subsequently, a flow analysis result can be generated based on the flow difference comparison result. For example, when the flow difference comparison result indicates that the first flow difference does not match the second flow difference, it can be determined that the flow analysis result does not meet the preset flow condition. When the first flow difference matches the second flow difference, it can be determined that the flow analysis result meets the preset flow condition. Of course, other methods can also be used to determine the flow analysis result, which is not specifically limited in this embodiment.

[0085] In a specific implementation example, Figure 2 As shown, the network equipment includes router R1, router R2, switch S11, and switch S21. The two links between routers R1 and R2 are aggregated links in load balancing mode. Ports P1 and P2 are a group of aggregated ports of router R1, and ports P4 and P5 are a group of aggregated ports of router R2. At this time, the port status information of the router aggregated ports can be collected in real time and stored in the database. Then, the database indicator information corresponding to the aggregated ports P1, P2, P4, and P5 on routers R1 and R2 can be extracted from the database, and anomaly analysis can be performed based on the database indicator information. The specific anomaly analysis may include whether the port is open, whether there is packet loss, whether the protocol is UP, whether the transmit and receive optical power meets the threshold, whether the optical attenuation value is too large, whether the voltage, current, and temperature are within the normal range, whether it is frequently up / down, etc., so as to determine the first anomaly analysis result. Then, according to the first anomaly analysis result, the status of the aggregated ports P1, P2, P4, and P5 of the network device in the database can be read to generate network configuration file information that should be restarted or shut down. For example, Figure 2 The two links between R1 and R2 form a load balancing mode. The traffic of the two ports P1 is 200M / s and the traffic of P2 is 210M / s. Figure 3As shown, when the first abnormal analysis result indicates that port P1 has a traffic loss abnormality from time t1 to t2, firstly, it is possible to check whether there is historical fault information matching the current database indicator information in the third-party fault library. If so, the historical configuration file information corresponding to the historical fault information is used to determine the network configuration file information; if not, the restart configuration file information is determined as the network configuration file information, and the network device is triggered to update the port status according to the network configuration file information.

[0086] like Figure 3 As shown in the flow curve of the ports P1 and P2 of the R1 router, when the restart configuration file information is determined as the network configuration file information, the network configuration file information can be sent to the router R1, that is, the restart operation is performed on the port P1 on the router R1 at time t3. Figure 3 As shown, after the network device, i.e., router R1, is triggered to restart port P1, the restart port status information after router R1 restarts port P1 is obtained to perform abnormal analysis again, and it can be determined that the traffic of port P1 has not been restored after the restart. At this time, the shutdown configuration file information corresponding to port P1 of router R1 can be generated. Subsequently, the network device is triggered to close the port state according to the closing configuration file information, that is, the port P1 is closed at time t4. At this time, the first flow difference corresponding to the target port in the network device is determined, that is, the flow difference before and after the port P1 of the router R1 is determined to be Flow_t4p1, and the second flow difference corresponding to other ports is obtained, that is, Flow_t4p2 corresponding to the port P2; at this time, the first flow difference and the second flow difference are compared to obtain the flow difference comparison result, and the flow analysis result is generated according to the flow difference comparison result, and then it can be judged whether the current flow analysis result meets the preset flow condition. Since the port P1 is closed under normal circumstances, the original port P1 flow is Flow_t4p1 at this time, which will migrate to the port P2, that is, the values ​​of Flow_t4p1 and Flow_t4p2 are compared. If the values ​​of Flow_t4p1 and Flow_t4p2 are equal, it can be determined that the flow analysis result meets the preset flow condition to generate a self-healing success result, otherwise it can be determined that the flow analysis result does not meet the preset flow condition and a self-healing failure result is generated, and according to the self-healing failure result, a fault prompt information is output to prompt manual processing.

[0087] In an optional embodiment of the present application, database indicator information is determined based on port status information, which may specifically include the following steps: storing the port status information in a preset database; extracting preset indicator data corresponding to the network device from the preset database to obtain database indicator information.

[0088] In the process of determining the database indicator information based on the port status information, this embodiment can store the port status information in a preset database, and can extract the preset indicator data corresponding to the network device from the preset database to obtain the database indicator information. The current acquisition of the port status information and the storage of the port status information in the preset database can be continuously executed according to the preset period, and the extraction of the preset indicator data corresponding to the network device from the preset database to obtain the database indicator information can be continuously executed according to the abnormal analysis period. In addition, when executing the steps of "obtaining the restart port status information after the network device restarts the port" and "obtaining the closed port status information after the network device closes the port", it can also be extracted from the preset database, and this embodiment does not specifically limit this.

[0089] like Figure 5 As shown, the present application also discloses an embodiment, providing a network device fault processing system, including:

[0090] The indicator monitoring module 510 is used to obtain the port status information of at least one network device;

[0091] A determination module 520, configured to determine database indicator information according to the port status information;

[0092] An abnormality analysis module 530, configured to perform an abnormality analysis based on the database indicator information and determine a first abnormality analysis result;

[0093] A self-healing planning module 540, configured to perform self-healing planning processing based on the first abnormality analysis result and in combination with historical fault information to obtain network configuration file information;

[0094] The network configuration module 550 is used to trigger the network device to update the port status according to the network configuration file information.

[0095] In an optional embodiment of the present application, the self-healing planning module 540 may include:

[0096] A first acquisition unit, configured to acquire at least one piece of historical fault information from a preset fault ticket database when the first abnormality analysis result is a port abnormality result;

[0097] A first determining unit, used to determine whether the database indicator information matches the historical fault information;

[0098] A first generating unit, configured to generate restart configuration file information corresponding to the network device when the database indicator information does not match the historical fault information;

[0099] The second determining unit is configured to determine the restart configuration file information as the network configuration file information.

[0100] In an optional embodiment of the present application, the self-healing planning module 540 may further include:

[0101] A second acquisition unit, configured to acquire, when the database indicator information matches the historical fault information, historical configuration file information corresponding to the historical fault information;

[0102] The third determining unit is configured to determine the historical configuration file information as the network configuration file information.

[0103] In an optional embodiment of the present application, the network configuration module 550 may include:

[0104] A first triggering unit is used to trigger the network device to restart the port according to the network configuration file information, and obtain restart port status information after the network device restarts the port;

[0105] a fourth determining unit, configured to perform an abnormality analysis based on the restart port status information to determine a second abnormality analysis result;

[0106] A second generating unit, configured to generate shutdown configuration file information corresponding to the network device when the second abnormality analysis result is a port abnormality result;

[0107] The second triggering unit is used to trigger the network device to close the port state according to the closing configuration file information.

[0108] In an optional embodiment of the present application, the network configuration module 550 may further include:

[0109] A third acquisition unit, used to acquire the closed port status information after the network device closes the port;

[0110] a fifth determining unit, configured to perform traffic analysis based on the closed port status information and determine a traffic analysis result;

[0111] A third generating unit, configured to generate a self-healing success result when the traffic analysis result meets a preset traffic condition;

[0112] The fourth generating unit is used to generate a self-healing failure result when the traffic analysis result does not meet the preset traffic condition, and output fault prompt information according to the self-healing failure result.

[0113] In an optional embodiment of the present application, the fifth determining unit may include:

[0114] A determination subunit, configured to determine a first flow difference value corresponding to a target port in the network device based on the closed port state information, wherein the target port is a port closed when the network device closes a port, and the first flow information is a flow difference value before and after the target port is closed;

[0115] An acquisition subunit, used to acquire second flow difference values ​​corresponding to other ports in the network device;

[0116] A comparison subunit, used for comparing the first flow difference value and the second flow difference value to obtain a flow difference comparison result;

[0117] A generating subunit is used to generate the flow analysis result according to the flow difference comparison result.

[0118] In an optional embodiment of the present application, the determining module 520 may include:

[0119] A storage unit, used to store the port status information in a preset database;

[0120] The extraction unit is used to extract the preset indicator data corresponding to the network device from the preset database to obtain the database indicator information.

[0121] The implementation process of the functions and effects of each module in the above system is specifically described in the implementation process of the corresponding steps in the above method, which will not be repeated here.

[0122] In one example, in combination with any of the above-mentioned network device fault processing methods, when the network device fault processing system in this embodiment is specifically implemented, Figure 6 As shown, this can be achieved through the following modules:

[0123] Index monitoring module: monitors the port status of network devices through the SNMP protocol, including the open status, packet loss rate, protocol status, transmit and receive optical power, optical attenuation value, voltage and current, temperature, whether it is frequently UP / DOWN, etc., and stores the results in the database; among them, the network devices of the present application specifically include but are not limited to routers and switches, such as Figure 6 As shown, it may include router R1, router R1, switch S21, switch S221, and switch S22.

[0124] Abnormal analysis module: samples the database indicator data, analyzes the indicators on the aggregation port of the network device, determines whether there are abnormalities, and submits the results to the self-healing planning module or the third-party fault ticket library.

[0125] Self-healing planning module: When an abnormality occurs in an aggregate port, first check whether there is a similar fault in the third-party fault ticket database. If so, refer to the historical fault handling method for processing. If not, restart the faulty port to observe whether the fault disappears. If so, the fault is successfully handled. Otherwise, close the abnormal port. After closing, compare the traffic increase value of the normal port in the aggregate port to see if it is approximately equal to the traffic loss caused by closing the abnormal port. If so, self-healing is successful, otherwise it fails and is handed over to manual handling.

[0126] Network configuration module: Sends configuration files to network devices and changes port status based on the configuration files generated by the self-healing plan.

[0127] like Figure 7 As shown, an embodiment of the present application provides an electronic device, including a processor 710, a communication interface 720, a memory 730 and a communication bus 740, wherein the processor 710, the communication interface 720, and the memory 730 communicate with each other through the communication bus 740;

[0128] Memory 730, for storing computer programs;

[0129] In one embodiment of the present application, the processor 710, when executing the program stored in the memory 730, implements the network device fault handling method provided by any of the aforementioned method embodiments, by obtaining port status information of at least one network device, determining database indicator information based on the port status information, performing an exception analysis based on the database indicator information, determining a first exception analysis result, and performing self-healing planning processing based on the first exception analysis result in combination with historical fault information to obtain network configuration file information, and then triggering the network device to update the port status based on the network configuration file information; thereby, adaptive self-healing processing can be performed on the network device exception, which can effectively reduce labor costs and improve processing efficiency, thereby solving the problem of low efficiency in handling network device exceptions caused by the need to manually search for the cause of the exception and solve it when an exception occurs in the network device.

[0130] The embodiment of the present application also provides a computer-readable storage medium having a computer program stored thereon, wherein the computer program, when executed by a processor, implements the steps of a network device fault handling method as provided in any of the aforementioned method embodiments, by obtaining port status information of at least one network device, determining database indicator information based on the port status information, performing an exception analysis based on the database indicator information, determining a first exception analysis result, and performing self-healing planning processing based on the first exception analysis result in combination with historical fault information to obtain network configuration file information, and then triggering the network device to update the port status based on the network configuration file information; thereby, adaptive self-healing processing can be performed on network device exceptions, which can effectively reduce labor costs and improve processing efficiency, thereby solving the problem of low efficiency in handling network device exceptions caused by the need to manually search for the cause of the exception and solve it when an exception occurs in the network device.

[0131] The system device embodiment described above is only illustrative, wherein the units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0132] Through the description of the above implementation methods, those skilled in the art can clearly understand that each implementation method can be implemented by means of software plus a general hardware platform, and of course, by hardware. Based on this understanding, the above technical solution is essentially or the part that contributes to the relevant technology can be embodied in the form of a software product, and the computer software product can be stored in a computer-readable storage medium, such as ROM / RAM, a disk, an optical disk, etc., including a number of instructions for a computer device (which can be a personal computer, a server, or a network device, etc.) to execute the methods described in each embodiment or some parts of the embodiments.

[0133] It should be understood that the terms used herein are only for the purpose of describing specific example embodiments and are not intended to be limiting. Unless the context clearly indicates otherwise, the singular forms "one", "an" and "said" as used herein may also be meant to include plural forms. The terms "include", "comprise", "contain", and "have" are inclusive, and therefore specify the existence of stated features, steps, operations, elements and / or parts, but do not exclude the existence or addition of one or more other features, steps, operations, elements, parts, and / or combinations thereof. The method steps, processes, and operations described herein are not interpreted as necessarily requiring them to be performed in the specific order described or illustrated, unless the execution order is clearly indicated. It should also be understood that additional or alternative steps may be used.

[0134] The foregoing is merely a specific embodiment of the present invention, which enables those skilled in the art to understand or implement the present invention. Various modifications to these embodiments will be apparent to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of the present invention. Therefore, the present invention will not be limited to the embodiments shown herein, but rather to the widest scope consistent with the principles and novel features claimed herein.

Claims

1. A method for handling network equipment failure, characterized in that: include: Obtaining port status information of at least one network device; Determining database indicator information according to the port status information; Perform an abnormality analysis based on the database indicator information to determine a first abnormality analysis result; Based on the first abnormality analysis result, self-healing planning is performed in combination with historical fault information to obtain network configuration file information; According to the network configuration file information, the network device is triggered to update the port status.

2. The method for handling network device failure according to claim 1, characterized in that: The self-healing planning process is performed based on the first abnormality analysis result and in combination with historical fault information to obtain network configuration file information, including: When the first abnormality analysis result is a port abnormality result, obtaining at least one historical fault information from a preset fault ticket database; Determining whether the database indicator information matches the historical fault information; In the case where the database indicator information does not match the historical fault information, generating restart configuration file information corresponding to the network device; The restart configuration file information is determined as the network configuration file information.

3. The method for handling network device failure according to claim 2, characterized in that: After determining whether the database indicator information matches the historical fault information, the method further includes: When the database indicator information matches the historical fault information, obtaining historical configuration file information corresponding to the historical fault information; The historical configuration file information is determined as the network configuration file information.

4. The method for handling network device failure according to claim 1, characterized in that: The triggering the network device to update the port status according to the network configuration file information includes: According to the network configuration file information, trigger the network device to restart the port, and obtain restart port status information after the network device restarts the port; Perform an abnormality analysis based on the restart port status information to determine a second abnormality analysis result; In the case where the second abnormality analysis result is a port abnormality result, generating shutdown configuration file information corresponding to the network device; According to the shutdown configuration file information, the network device is triggered to close the port state.

5. The method for handling network device failure according to claim 4, characterized in that: After triggering the network device to close the port state according to the closing configuration file information, the method further includes: Obtaining closed port status information after the network device closes the port; Performing traffic analysis based on the closed port status information to determine a traffic analysis result; If the flow analysis result meets the preset flow condition, a self-healing success result is generated; When the flow analysis result does not meet the preset flow condition, a self-healing failure result is generated, and fault prompt information is output based on the self-healing failure result.

6. The method for handling network device failure according to claim 5, characterized in that: The performing traffic analysis based on the closed port status information to determine the traffic analysis result includes: Based on the closed port status information, determine a first flow difference value corresponding to a target port in the network device, wherein the target port is a port closed when the network device closes a port, and the first flow information is a flow difference value before and after the target port is closed; Obtaining second flow difference values ​​corresponding to other ports in the network device; Comparing the first flow difference value with the second flow difference value to obtain a flow difference comparison result; The flow analysis result is generated according to the flow difference comparison result.

7. The method for handling network device failure according to any one of claims 1 to 6, characterized in that: Determining database indicator information according to the port status information includes: Storing the port status information in a preset database; From the preset database, preset indicator data corresponding to the network device is extracted to obtain the database indicator information.

8. A network equipment fault handling system, characterized in that: include: An indicator monitoring module, used to obtain port status information of at least one network device; A determination module, used to determine database indicator information according to the port status information; An abnormality analysis module, used to perform abnormality analysis based on the database indicator information and determine a first abnormality analysis result; A self-healing planning module, configured to perform self-healing planning processing based on the first abnormality analysis result and in combination with historical fault information to obtain network configuration file information; The network configuration module is used to trigger the network device to update the port status according to the network configuration file information.

9. An electronic device, characterized in that: It includes a processor, a communication interface, a memory and a communication bus, wherein the processor, the communication interface and the memory communicate with each other through the communication bus; Memory, used to store computer programs; The processor is used to implement the network device fault handling method described in any one of claims 1-7 when executing the program stored in the memory.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the network device failure handling method according to any one of claims 1 to 7 is implemented.

Images