SDN (Software Defined Network)-based network troubleshooting method and equipment

Abstract

The invention discloses a network troubleshooting method and device based on an SDN, and the method comprises the steps: enabling a service monitoring function of a specified service through an SDN controller, and searching a mounting switch of a service IP of the specified service; according to the mounted switch, obtaining information of each hop returned by the trace operation between the source host and the destination host, performing path analysis on the information of each hop, and determining service path information of the specified service; in a preset service monitoring period, according to the mounted switch, controlling a ping operation between the source host and the destination host; obtaining multiple ping operation results of the source host and the target host within a set time length, performing connectivity analysis on the multiple ping operation results, and determining whether the specified service has a network fault; and when the specified service has a network fault, determining fault prompt information of the specified service according to the service path information. Through the steps, the fault point can be quickly positioned, and the troubleshooting efficiency is improved.

Description

Technical Field

[0001] The present application relates to the field of network failures, and in particular to a network failure troubleshooting method and device based on SDN. Background Art

[0002] In the digital age, the rapid advancement of network technology has led to a surge in the number of data centers. These data centers are not only numerous, but the businesses running inside them are also becoming increasingly complex, which places higher demands on the manpower and technical level of the operation and maintenance team.

[0003] Today's traditional network troubleshooting methods lack full-network, full-time monitoring, and prominent user-side problems lead to low troubleshooting efficiency. They are unable to assist operation and maintenance personnel in quickly locating fault points when emergencies occur, resulting in prolonged fault time. Summary of the invention

[0004] The embodiments of the present application provide a network fault troubleshooting method and device based on SDN, which are used to solve the problem of how to quickly locate the fault point when an emergency occurs.

[0005] The present application embodiment adopts the following technical solutions:

[0006] On the one hand, an embodiment of the present application provides a network troubleshooting method based on SDN, the method comprising: an SDN controller enables a specified service monitoring function, and searches for a mounted switch of a service IP of a specified service; according to the mounted switch, per-hop information returned by a track operation between a source host and a destination host is obtained, and a path analysis is performed on the per-hop information to determine the service path information of the specified service; within a preset service monitoring period, according to the mounted switch, a ping operation is controlled between the source host and the destination host; multiple ping operation results between the source host and the destination host within a set time period are obtained, and connectivity analysis is performed on the multiple ping operation results to determine whether a network failure occurs in the specified service; when a network failure occurs in the specified service, the fault prompt information of the specified service is determined according to the service path information.

[0007] In one example, the path analysis of the each-hop information to determine the service path information of the specified service specifically includes: determining the target switch IP, the interface and the port number of the target switch to which each-hop path belongs; querying the physical state and configuration parameter information of the interface of the target switch to obtain the interface information; and determining the service path information of the specified service according to the target switch IP, the port number and the interface information of each-hop path.

[0008] In one example, determining the fault information of the designated service according to the service path information specifically includes: extracting the target switch IP of each hop path from the service path information; obtaining the latest IP, latest interface information and latest port number of the target switch at the fault time according to the target switch IP; judging whether the latest interface physical state of each hop path is normal according to the latest interface information; if so, comparing the latest IP of the target switch with the target switch IP to obtain an IP comparison result, and comparing the latest interface configuration parameter information with the interface configuration parameter information to obtain an interface configuration comparison result, and comparing the latest port number with the port number to obtain a port comparison result; determining the fault prompt information of the designated service according to the IP comparison result, the interface configuration comparison result and the port comparison result.

[0009] In one example, the connectivity analysis of the multiple ping operation results to determine whether the specified service has a network failure specifically includes: determining whether the specified service has a network failure based on whether the number of packet losses in the multiple ping operation results is greater than a first preset number threshold; or determining whether the specified service has a network failure based on whether the number of consecutive packet losses in the ping operation results exceeds a second preset number threshold.

[0010] In one example, after determining the fault prompt information of the specified service according to the service path information, the method further includes: generating fault prompt information of the specified service, and sending the fault prompt information to a user display interface; when receiving a log information query, retrieving historical log information of the faulty target switch within a historical period before the fault time; highlighting the fault location in the historical log information; the fault location includes at least one of the faulty target switch IP, the faulty interface, and the faulty port number; and sending the historical log information to the user display interface.

[0011] In one example, after determining the fault prompt information of the specified service according to the service path information, the method further includes: enabling the device monitoring function of the switch in the network environment, and detecting the device status and log information of the monitoring switch during the device monitoring cycle; when the device status is abnormal or the log information is abnormal, generating device fault information of the monitoring switch, and sending the device fault information to the user display interface.

[0012] In one example, after determining the fault prompt information of the specified service according to the service path information, the method further includes: enabling the link monitoring function of the switch in the network environment, and detecting the link status of the corresponding switch within the link monitoring cycle; when the link status changes, determining the fault prompt information of the link, and sending the link fault prompt information to the user display interface.

[0013] In one example, the SDN controller enables a service monitoring function for a specified service, specifically including: the SDN controller receives service network information for a specified service, and sets service monitoring information for the specified service based on the service network information; the service network information includes a service IP, a source host IP, a destination host IP, and a port number; in a switch in a managed network environment, the network location of the mounted switch is closest to the destination host; in the managed network environment, a connectivity test is performed on the specified service to determine whether the specified service is in an address reachable state; when in an address reachable state, the service monitoring function of the specified service is enabled.

[0014] In one example, before the SDN controller enables the service monitoring function of the specified service, the method also includes: the SDN controller receives management information of the switch to be managed that is related to the specified service; the management information includes basic configuration information of the switch and network topology information; the management information is verified, and after the verification is passed, the switch is managed according to the management information.

[0015] On the other hand, an embodiment of the present application provides an SDN-based network troubleshooting device, comprising: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor so that the at least one processor can execute any one of the above-described SDN-based network troubleshooting methods.

[0016] At least one of the above technical solutions adopted in the embodiments of the present application can achieve the following beneficial effects:

[0017] By enabling the service monitoring function of the specified service, the running status of the service can be monitored in real time or regularly. By finding the switch mounted with the service IP, the specific location of the service in the network can be quickly determined, which is convenient for quick positioning. Furthermore, by using track and ping operations, the service path information and whether the service path is reachable can be obtained. When the service network is unreachable, the network failure can be quickly determined, and the fault point can be located according to the service path information, thereby improving the efficiency of network troubleshooting. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] In order to more clearly illustrate the technical solution of the present application, some embodiments of the present application will be described in detail below in conjunction with the accompanying drawings, in which:

[0019] Figure 1 A flowchart of a network troubleshooting method based on SDN provided in an embodiment of the present application;

[0020] Figure 2 A schematic diagram of the architecture of a network troubleshooting system based on SDN provided in an embodiment of the present application;

[0021] Figure 3 A schematic diagram of the structure of a network troubleshooting device based on SDN provided in an embodiment of the present application. DETAILED DESCRIPTION

[0022] In order to make the purpose, technical solution and advantages of the present application clearer, the technical solution of the present application will be clearly and completely described below in conjunction with specific embodiments and corresponding drawings. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in the field without creative work are within the scope of protection of the present application.

[0023] Some embodiments of the present application are described in detail below with reference to the accompanying drawings.

[0024] Figure 1 A flow chart of a network troubleshooting method based on SDN provided in an embodiment of the present application. The method can be applied to different business fields, and some input parameters or intermediate results in the process allow manual intervention and adjustment to help improve accuracy.

[0025] In the digital age, the rapid progress of network technology has led to a surge in the number of data centers. These data centers are not only numerous, but the services they run are also increasingly complex, which places higher demands on the manpower and technical level of the operation and maintenance team. In order to improve the operation and maintenance efficiency of data centers, most data centers have begun to adopt software-defined network (SDN) controllers. SDN controllers automate operation and maintenance work through software, greatly reducing the workload of operation and maintenance personnel. However, the introduction of SDN controllers is not only for automation, but also for intelligence. By integrating more SDN-related components, SDN controllers can further realize intelligent operation and maintenance on the basis of automation. This means that when an emergency occurs, SDN controllers can assist operation and maintenance personnel to quickly locate the fault point and collect necessary information, thereby shortening the troubleshooting time and accelerating the recovery of services. How to effectively achieve this transformation has become an urgent issue facing data center operation and maintenance personnel.

[0026] The embodiment of the present application provides a network troubleshooting method and system based on SDN, which manages the switch system by deploying an SDN controller in a data center and based on the switch access information set in the SDN controller. Users can set up service monitoring in the SDN controller to monitor specific IP services in real time. When a service anomaly is detected, the SDN controller will query the switch information and give corresponding fault prompt information. Users can quickly find log information related to the cause of the fault in the switch on the SDN controller page based on the fault prompt information. In addition, users can also set up device monitoring, link monitoring, etc. in the SDN controller. The SDN will give corresponding fault prompt information based on the corresponding fault type to assist users in troubleshooting.

[0027] Figure 1 The process in includes the following steps:

[0028] S101: The SDN controller enables a service monitoring function of a specified service and searches for a switch on which a service IP of the specified service is mounted.

[0029] In some embodiments of the present application, the SDN controller needs to complete the management of the switch, and the management process is as follows: the SDN controller receives management information of the switch to be managed related to the specified service. The management information includes basic configuration information of the switch and network topology information. Then, the management information is verified, and after the verification is passed, the switch is managed according to the management information.

[0030] Furthermore, when the service monitoring function of a designated service is enabled, a connectivity test, ie, a ping operation, needs to be performed on the designated service, so that the service monitoring function is enabled only when the address is reachable.

[0031] Based on this, the SDN controller receives the service network information of the specified service, and sets the service monitoring information of the specified service according to the service network information. The service network information includes the service IP, source host IP, destination host IP, and port number. In the switch of the managed network environment, the network location where the switch is mounted is closest to the destination host. In the managed network environment, the connectivity test is performed on the specified service to determine whether the specified service is in the address reachable state. When the address is reachable, the service monitoring function of the specified service is enabled.

[0032] It should be noted that the key to network troubleshooting is to deploy a powerful SDN controller in the data center. The controller can manage the switch system comprehensively and finely based on the preset switch access information. To achieve this goal, it is necessary to first establish a stable and efficient information channel between the SDN controller and the switch. This requires a series of preparatory work to be completed before the SDN controller starts to manage the switch devices in the data center. These work include but are not limited to:

[0033] First, statistics are collected on the switch management information, including the management addresses and management information (such as IP addresses, port numbers, management user names and passwords) of all switches that need to be managed by the SDN controller, to ensure that this information is accurate. Secondly, physical links and management networks are built based on the statistical management information to ensure smooth communication between the SDN controller and the switch. Finally, the switch is initialized and necessary initialization configuration is completed on the switch: management IP is configured, and SSH or SNMP protocols are enabled so that the SDN controller can connect to the switch securely and reliably through these protocols.

[0034] Since there are switches that do not have switch IP, the switch closest to the destination host is used as the mounting switch. During data transmission, even if the switch does not have a switch IP, the service path of the switch can be traced. On the contrary, if the mounting host is in a switch in the middle network, the switches that do not have switch IPs in the middle may be ignored, resulting in an incomplete service path. In addition, the relationship between interfaces, ports and IPs is that a switch has multiple interfaces, an interface has multiple ports, and the IP is on one port.

[0035] After completing the above preparatory work, users can access the web management page of the SDN controller through a PC. In this page, users can easily enter the management information of the previously counted switches, including the management network IP reachable by the SDN controller, management username and password, SNMP-related configuration, etc. After receiving this information, the SDN controller will immediately verify the input information through SSH or SNMP, etc. Once the verification is passed, the SDN controller will save the management information of these switches to its own database. In this way, in the subsequent use process, the SDN controller can flexibly control the network according to these saved device management information, and obtain various status information of the switch in real time. At this point, the SDN controller has completed the management of the switches in the data center.

[0036] The service monitoring function is a key function of the SDN controller. When there are some key services in the network, it is necessary to ensure that when the service fails, it can be discovered in time and the troubleshooting work can be completed quickly to restore the service. The user can use the troubleshooting assistant function of the SDN controller front-end interface to set the service monitoring function according to the actual service information, the service access device, source, destination IP and port number information. The steps to set up service monitoring are as follows: the user first needs to log in to the management interface of the SDN controller through a browser or other client tool. In the management interface of the SDN controller, find and click "Service Monitoring" or similar configuration items to enter the service monitoring setting page, and then set the service monitoring rules. First, you need to select or enter the ID or name of the network device to which the service to be monitored is connected. The source IP address specifies the source IP address of the service to be monitored, which can be a single IP address or an IP address segment; the destination IP address specifies the destination IP address of the service to be monitored, which supports a single IP address and an IP address segment; the port number specifies the network port number used by the service, which can be a single port number or a port range; then set a monitoring threshold. According to business needs, set the monitoring threshold, such as bandwidth utilization, delay time, packet loss rate, etc. When these indicators exceed the preset threshold, the system will trigger an alarm; after completing the above settings, click the Save or Apply button to save the service monitoring rules to the SDN controller. After the service monitoring settings are completed, the SDN controller will detect the connectivity of the service information. If the current service information is in a reachable address state, the monitoring of the service will be enabled.

[0037] When determining business monitoring rules, the following key factors need to be considered: First, business needs. According to the importance and sensitivity of the business, determine the indicators and thresholds that need to be monitored. For example, for businesses with extremely high real-time requirements, you may need to set lower delay and packet loss rate thresholds. Secondly, consider the network conditions. Consider the actual operation of the network, such as bandwidth capacity, equipment performance, etc., to ensure that the set monitoring rules are neither too loose to fail to detect potential problems in time, nor too strict to cause frequent false alarms. Then you can also consider historical data. If possible, you can refer to the operation data of similar businesses in the past and combine historical data to set reasonable monitoring thresholds. Finally, you can also consider dynamic adjustment. As the network environment and business needs change, the monitoring rules also need to be dynamically adjusted. The SDN controller should support users to modify and update monitoring rules at any time to adapt to the changing network environment.

[0038] S102: According to the mounted switch, obtain per-hop information returned by the track operation between the source host and the destination host, perform path analysis on the per-hop information, and determine service path information of the designated service.

[0039] In some embodiments of the present application, the SDN controller uses track technology to obtain path information between services. Through the track operation initiated by the access device, the SDN controller can collect information about each hop through which the traffic passes, thereby accurately depicting the traffic path of the service. This information not only includes the IP address of each hop, but also further refines the specific device interface type (such as router interface or VLAN interface), as well as the physical status and configuration details of these interfaces. The SDN controller will store all the information in its own database for use in subsequent fault analysis.

[0040] Based on this, first determine the target switch IP, interface and port number of each hop path. Then, query the physical state and configuration parameter information of the interface of the target switch to obtain the interface information. Finally, determine the service path information of the specified service based on the target switch IP, port number and interface information of each hop path.

[0041] S103: within a preset service monitoring period, according to the mounted switch, controlling a ping operation to be performed between the source host and the destination host.

[0042] In some embodiments of the present application, the user sets up service monitoring based on the access device IP, source IP, destination IP and port number information of the service. After performing service monitoring, the SDN controller will periodically initiate a ping operation based on the location information of the service access device, using the preset source IP address, destination IP address and port number.

[0043] S104: Acquire multiple ping operation results between the source host and the destination host within a set time period, perform connectivity analysis on the multiple ping operation results, and determine whether a network failure occurs to the designated service.

[0044] When determining whether a network failure occurs for a specified service, whether a network failure occurs for the specified service is determined based on whether the number of packet losses in the results of multiple ping operations is greater than a first preset number threshold. That is, when it is greater, it is determined that a network failure occurs. Alternatively, whether a network failure occurs for the specified service is determined based on whether the number of consecutive packet losses in the results of the ping operations exceeds a second preset number threshold. That is, when it is greater, it is determined that a network failure occurs.

[0045] It should be noted that the connectivity of the service is continuously detected by periodically initiating ping operations, that is, the SDN controller connects to the switch through ssh and other methods according to the access device (managed switch) set in the service monitoring. The periodicity of this ping operation is set to 1 second by default, and its parameters include the source and destination addresses, as well as the specific port number used, to ensure the real-time and effectiveness of monitoring. The SDN controller also sets strict fault judgment criteria in the ping operation. It should also be noted that if there are more than 5 packet losses within 1 minute, or no response is received for 5 consecutive seconds, the SDN controller will determine that the service has failed and record the time when the failure occurred. This design not only ensures the sensitivity of fault detection, but also avoids false alarms caused by occasional network fluctuations.

[0046] S105: When a network failure occurs in the designated service, determine the failure prompt information of the designated service according to the service path information.

[0047] In some embodiments of the present application, when a monitoring service set in the service monitoring function of the SDN controller fails, that is, the ping detection is abnormal, the SDN controller will query the status of the vlan and routing interface in the path based on the previously saved service path information to confirm whether its status is normal, and compare whether the interface configuration has changed. In addition, if the interface is a vlan interface, it will also query whether the vlan configuration and the status of the physical interface corresponding to the vlan have changed, and whether the configuration has changed. If the device enables the spanning tree function, it will also query whether the spanning tree interface status of the vlan is forwarding at this time.

[0048] As mentioned above, if the port status is abnormal, the configuration information is changed, or the corresponding interface status of the spanning tree is non-forwarding, the corresponding information will be returned according to the corresponding scenario, and there will be corresponding prompts in the front-end interface of the SDN controller to prompt the user that the status, configuration or spanning tree of a specific device in the path is abnormal, and corresponding prompt information will be given.

[0049] The specific steps are as follows: Extract the IP address of the target switch that each hop (i.e., each step of transmission) passes through from the determined service path information. These IP addresses represent the switches involved in the service path; for each extracted target switch IP, query the latest status information of the switch when the fault occurs. This includes the latest IP address (although the IP address usually does not change frequently, this step is to ensure the accuracy of the information), the latest interface information (including physical status and configuration parameters) and the latest port number; based on the latest interface information obtained, first determine whether the physical status of the switch interface on each hop path is normal. If the physical status of an interface is abnormal (such as disconnection, failure, etc.), this point can be directly used as one of the fault points; if the physical status of the interface is normal, further perform the following comparison: compare the latest IP address of the target switch with the IP address recorded in the service path information to obtain the IP comparison result. Compare the latest interface configuration parameter information with the interface configuration parameter information recorded in the service path information to obtain the interface configuration comparison result; compare the latest port number with the port number recorded in the service path information to obtain the port comparison result; based on the analysis results, generate fault prompt information, which should clearly indicate the cause of the fault point.

[0050] Users can understand the cause of the current monitoring service failure to a certain extent based on the prompt information given by the SDN controller front-end interface. If you need to find more fault information, users can select the fault prompt information item on the SDN controller front-end interface and click Log Information Query.

[0051] When receiving a log information query, the SDN controller retrieves the historical log information of the faulty target switch within the historical length of time before the fault time. In the historical log information, the fault location is highlighted; wherein the fault location includes at least one of the faulty target switch IP, the faulty interface, and the faulty port number. The historical log information is sent to the user display interface.

[0052] For example, the SDN controller displays the switch log information from 5 minutes before the recorded fault occurrence to the time of query on the front-end page based on the selected fault information, and highlights the fault IP, VLAN, interface number and other information to facilitate users to check the fault based on the fault information. Users can also customize the time period to collect the required log information.

[0053] In addition, users can also configure device monitoring and link monitoring functions in the SDN controller troubleshooting assistant function according to actual needs.

[0054] The SDN controller enables the device monitoring function of the switch in the network environment, and detects the device status and log information of the monitoring switch during the device monitoring cycle. When the device status is abnormal or the log information is abnormal, the device fault information of the monitoring switch is generated and sent to the user display interface.

[0055] It should be noted that the user sets the managed switch device as the device monitoring object in the front-end interface of the SDN controller. The SDN controller will obtain the device status and log information through the managed information. When a high-priority log or abnormal device status (unable to connect, etc.) occurs, the SDN controller will generate corresponding prompt information based on the log information or the current abnormal status of the device to assist the user in troubleshooting.

[0056] In addition, the SDN controller enables the link monitoring function of the switch in the network environment, and detects the link status of the corresponding switch during the link monitoring cycle. Then, when the link status changes, the fault prompt information of the link is determined and sent to the user display interface.

[0057] It should be noted that after the switches in the network are managed, the SDN controller will enable LLDP-related functions in the switches, obtain LLDP neighbor information, and generate a network topology diagram on the front-end interface based on the LLDP information. The link monitoring function is that when the user needs to monitor some key links, he can select the link information obtained by LLDP in the front-end interface of the SDN controller and set the link as a link monitoring object. The SDN controller will connect the switch devices at both ends of the link through the managed information and periodically detect the link status. If the link status changes, a corresponding prompt message will be generated, and relevant log information during the change will be collected and displayed on the front-end interface of the SDN controller to assist users in troubleshooting.

[0058] It should be noted that although the embodiments of the present application are based on Figure 1 Steps S101 to S105 are described in sequence, but this does not mean that steps S101 to S105 must be performed in a strict order. Figure 1 The order shown in the figure is to introduce and explain step S101 to step S105 in sequence, in order to facilitate those skilled in the art to understand the technical solution of the embodiment of the present application. In other words, in the embodiment of the present application, the order between step S101 to step S105 can be appropriately adjusted according to actual needs.

[0059] pass Figure 1The method is to set up service monitoring in the SDN controller, and determine the service path information and ping threshold based on the per-hop information returned by the track operation to determine whether the service has a network failure. This can greatly improve the speed and accuracy of locating the fault point, and compared with other traditional methods, it greatly reduces manpower consumption.

[0060] In addition, by configuring device monitoring and link monitoring, you can detect device anomalies in a timely manner, thereby quickly locating and resolving potential network failures to prevent the impact of failures from expanding. You can also predict possible failures by analyzing device status and log information, and take preventive measures in advance.

[0061] The link monitoring function can quickly locate faulty links and generate fault prompt information to help operation and maintenance personnel quickly troubleshoot faults. It can also understand changes in network topology, thereby optimizing the network structure and improving network efficiency and reliability.

[0062] More intuitively, Figure 2 A schematic diagram of the architecture of an SDN-based network troubleshooting system provided in an embodiment of the present application.

[0063] exist Figure 2 In the process, the SDN controller is used to manage the switch. The SDN controller includes three parts: SDNweb front-end interface, SDN controller, and SDN database.

[0064] Among them, the SDN database is used to store each hop information, the front-end interface is used to display fault information, and the SDN controller centrally manages and controls the equipment, links and other resources in the network, monitors the network status and traffic in real time, and provides a wealth of troubleshooting tools and functions.

[0065] Figure 3 A schematic diagram of the structure of a network troubleshooting device based on SDN provided in an embodiment of the present application includes:

[0066] at least one processor; and,

[0067] a memory communicatively connected to the at least one processor; wherein,

[0068] The memory stores instructions that can be executed by the at least one processor, and the instructions are executed by the at least one processor so that the at least one processor can execute any one of the above-mentioned SDN-based network fault troubleshooting methods.

[0069] Some embodiments of the present application provide a SDN-based network troubleshooting non-volatile computer storage medium storing computer executable instructions, wherein the computer executable instructions can execute any of the above-mentioned SDN-based network troubleshooting methods.

[0070] Each embodiment in this application is described in a progressive manner, and the same or similar parts between the embodiments can be referred to each other, and each embodiment focuses on the differences from other embodiments. In particular, for the device and medium embodiments, since they are basically similar to the method embodiments, the description is relatively simple, and the relevant parts can be referred to the partial description of the method embodiments.

[0071] The devices and media provided in the embodiments of the present application correspond one-to-one to the methods. Therefore, the devices and media also have similar beneficial technical effects as the corresponding methods. Since the beneficial technical effects of the methods have been described in detail above, the beneficial technical effects of the devices and media will not be repeated here.

[0072] Those skilled in the art will appreciate that embodiments of the present invention may be provided as methods, systems, or computer program products. Therefore, the present invention may take the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware. Moreover, the present invention may take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0073] The present invention is described with reference to flowcharts and / or block diagrams of methods, devices (systems), and computer program products according to embodiments of the present invention. It should be understood that each process and / or block in the flowchart and / or block diagram, as well as the combination of processes and / or blocks in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0074] These computer program instructions may also be stored in a computer readable memory capable of directing a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer readable memory produce an article of manufacture including an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.

[0075] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for implementing the process. Figure 1 A process or multiple processes and / or boxes Figure 1 The steps for the functions specified in one or more boxes.

[0076] In a typical configuration, a computing device includes one or more processors (CPU), input / output interfaces, network interfaces, and memory.

[0077] The memory may include non-permanent storage in a computer-readable medium, random access memory (RAM) and / or non-volatile memory in the form of read-only memory (ROM) or flash RAM. The memory is an example of a computer-readable medium.

[0078] Computer readable media include permanent and non-permanent, removable and non-removable media that can be implemented by any method or technology to store information. Information can be computer readable instructions, data structures, program modules or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, compact disk read-only memory (CD-ROM), digital versatile disk (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices or any other non-transmission media that can be used to store information that can be accessed by a computing device. As defined herein, computer readable media does not include temporary computer readable media (transitory media), such as modulated data signals and carrier waves.

[0079] It should also be noted that the terms "include", "comprises" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, commodity or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, commodity or device. In the absence of more restrictions, the elements defined by the sentence "comprises a ..." do not exclude the existence of other identical elements in the process, method, commodity or device including the elements.

[0080] The above is only an embodiment of the present application and is not intended to limit the present application. For those skilled in the art, the present application may have various changes and variations. Any modification, equivalent replacement, improvement, etc. made within the technical principle of the present application should all fall within the protection scope of the present application.

Claims

1. A network troubleshooting method based on SDN, characterized in that: The method comprises: The SDN controller enables the service monitoring function of the specified service and searches for the switch on which the service IP of the specified service is mounted; According to the mounted switch, obtaining per-hop information returned by the track operation between the source host and the destination host, performing path analysis on the per-hop information, and determining service path information of the designated service; Within a preset service monitoring period, according to the mounted switch, controlling a ping operation between the source host and the destination host; Obtain multiple ping operation results between the source host and the destination host within a set time period, perform connectivity analysis on the multiple ping operation results, and determine whether a network failure occurs to the designated service; When a network failure occurs in the designated service, fault prompt information of the designated service is determined according to the service path information.

2. The method according to claim 1, characterized in that The performing path analysis on the each-hop information to determine the service path information of the designated service specifically includes: Determine the target switch IP, interface and port number of each hop path; Query the physical status and configuration parameter information of the interface of the target switch to obtain the interface information; The service path information of the designated service is determined according to the target switch IP, port number and interface information of each hop path.

3. The method according to claim 2, characterized in that The determining the fault information of the designated service according to the service path information specifically includes: Extracting the target switch IP of each hop path from the service path information; According to the target switch IP, obtain the latest IP, latest interface information and latest port number of the target switch at the time of the failure; According to the latest interface information, determining whether the latest interface physical state of each hop path is normal; If yes, compare the latest IP of the target switch with the IP of the target switch to obtain an IP comparison result, and compare the latest interface configuration parameter information with the interface configuration parameter information to obtain an interface configuration comparison result, and compare the latest port number with the port number to obtain a port comparison result; The fault prompt information of the designated service is determined according to the IP comparison result, the interface configuration comparison result and the port comparison result.

4. The method according to claim 1, characterized in that The performing connectivity analysis on the results of the multiple ping operations to determine whether a network failure occurs in the designated service specifically includes: Determining whether a network failure occurs in the designated service according to whether the number of packet losses in the results of the multiple ping operations is greater than a first preset number threshold; or When the number of consecutive packet losses in the ping operation result exceeds a second preset number threshold, it is determined whether a network failure occurs in the designated service.

5. The method according to claim 1, characterized in that After determining the fault prompt information of the designated service according to the service path information, the method further includes: Generate fault prompt information of the specified service, and send the fault prompt information to a user display interface; When receiving a log information query, retrieve the historical log information of the fault target switch within the historical length of time before the fault time; In the historical log information, the fault location is highlighted; the fault location includes at least one of the fault target switch IP, the fault interface, and the fault port number; The historical log information is sent to the user display interface.

6. The method according to claim 1, characterized in that After determining the fault prompt information of the designated service according to the service path information, the method further includes: Enable the device monitoring function of the switch in the network environment, and detect and monitor the device status and log information of the switch during the device monitoring cycle; When the device state is abnormal or the log information is abnormal, device fault information of the monitoring switch is generated, and the device fault information is sent to the user display interface.

7. The method according to claim 1, characterized in that After determining the fault prompt information of the designated service according to the service path information, the method further includes: Enable the link monitoring function of the switch in the network environment, and detect the link status of the corresponding switch during the link monitoring period; When the link status changes, the link fault prompt information is determined, and the link fault prompt information is sent to the user display interface.

8. The method according to claim 1, characterized in that The SDN controller enables the service monitoring function of the specified service, specifically including: The SDN controller receives service network information of a specified service, and sets service monitoring information of the specified service according to the service network information; the service network information includes a service IP, a source host IP, a destination host IP and a port number; in the switches in the managed network environment, the network location of the mounted switch is closest to the destination host; In the managed network environment, a connectivity test is performed on the designated service to determine whether the designated service is in an address reachable state; When the address is reachable, a service monitoring function of the designated service is enabled.

9. The method according to claim 1, characterized in that: Before the SDN controller enables the service monitoring function of the specified service, the method further includes: The SDN controller receives management information of a switch to be managed related to a specified service; the management information includes basic configuration information of the switch and network topology information; The management information is verified, and after the verification is passed, the switch is managed according to the management information.

10. A network troubleshooting device based on SDN, characterized in that: include: at least one processor; as well as, a memory communicatively connected to the at least one processor; wherein, The memory stores instructions that can be executed by the at least one processor, and the instructions are executed by the at least one processor so that the at least one processor can execute the SDN-based network troubleshooting method described in any one of claims 1 to 9.

Images