TWI502475B - Visual network debugging method - Google Patents

Description

Visual network debugging method

The invention relates to a network debugging method, in particular to a visual network debugging method.

With the rapid development of network technology, the network becomes an indispensable part of people's life and work; when a network node in a regional network fails, it will cause a user of the network node It is inconvenient to suffer from jealousy or life at work. For network administrators, how to assist users in troubleshooting in complex network nodes has always been a problem that people are looking for and expect to solve.

In view of this, the present invention aims to provide a visual network debugging method, which allows the network administrator to perform a series of automated tests by clicking on the network node to be trouble-shooted, thereby generating an analysis result related to the network node. It is convenient for network administrators to troubleshoot in complex network nodes.

Accordingly, it is an object of the present invention to provide a visual network error detection method.

Therefore, the visual network debugging method of the present invention is adapted to perform debugging through a network topology image placed on an electronic device; wherein the network The road topology diagram has a plurality of network nodes corresponding to a regional network, and the network nodes are respectively composed of a plurality of master nodes and a plurality of root nodes, and the method comprises the following steps: First, when a user When the electronic device selects one of the slave nodes of the network topology as a node to be tested, the electronic device loads and executes a debug application from a node.

Then, the debugging application performs a first debugging mode for the link path of the root node to the node to be tested, so as to generate a first debugging message.

Then, when the debugging application determines that the first debugging message is an error message, the debugging application sequentially links each two adjacent network nodes from the root node to the connecting path of the node to be tested. The link path corresponds to performing a second debug mode to correspondingly generate a plurality of second debug messages.

Then, the debug application generates an analysis result corresponding to one of the nodes to be tested.

11‧‧‧Electronic devices

111‧‧‧Communication interface

112‧‧‧Processing unit

113‧‧‧ memory unit

114‧‧‧Display unit

12‧‧‧Master node device

121‧‧‧ memory unit

122‧‧‧Graphic interface application

123‧‧‧Detection application

125‧‧‧Communication埠

21‧‧‧ root node

22‧‧‧Main node

23‧‧‧ slave node

31‧‧‧First debug page

311‧‧‧First debug message

32‧‧‧Second debugging page

321‧‧‧Second debugging message

322‧‧‧ reminder message

Other features and effects of the present invention will be apparent from the embodiments of the present invention. FIG. 1 is a block diagram illustrating an electronic device and a master node device of the visual network debugging method of the present invention. 2 is a schematic diagram showing one of the network topology diagrams of the visual network debugging method of the present invention; FIG. 3 is a schematic diagram illustrating the visual network debugging method of the present invention. a first debugging page; FIG. 4 is a schematic diagram illustrating a second debugging page of the visual network debugging method of the present invention; and FIG. 5 is a flowchart illustrating the visual network debugging method of the present invention Preferred embodiment.

Before the present invention is described in detail, it should be noted that in the following description, similar elements are denoted by the same reference numerals.

Referring to FIG. 1 and FIG. 2, a preferred embodiment of the visual network debugging method of the present invention is adapted to perform debugging by using a network topology image placed on an electronic device 11. The electronic device 11 has a communication interface 111, a processing unit 112, a memory unit 113, and a display unit 114. The network topology has a plurality of network nodes corresponding to a regional network, and the network The network node is composed of a plurality of master nodes 22 and a plurality of root nodes 21; one master node device 12 corresponding to each master node 22 includes a memory unit 121 and a communication interface 124 having a plurality of communication ports 125. The memory unit 121 is configured to store a graphical interface application 122 and a debug application 123.

In the preferred embodiment, the electronic device 11 is, for example, one of a personal computer, a notebook computer, a mobile device, a tablet computer, or a personal digital assistant; and corresponds to the master node device 12 of each master node 22. The aspect is a switch or a router and the device corresponding to each slave node 23 is an Access Point (AP).

Please refer to FIG. 1 , FIG. 2 and FIG. 5 . First, as shown in step 41 When a user selects one of the master nodes 22 to log in as one node 21 through the electronic device 11, the electronic device 11 loads and executes a memory unit 121 corresponding to the root node 21. Graphical interface application 122. In the preferred embodiment, the user logs in to the master node 22 through an ip address of the electronic device 11 to make the logged-in master node 22 the regional network. The root node 21 in the road.

Then, as shown in step 42, after the graphical interface application 122 is executed by the processing unit 112 of the electronic device 11, the network topology map is generated according to the connection path of the network nodes, and the electronic device 11 is generated. Displayed in display unit 114. The link path of the network nodes may be through a Link Layer Discovery Protocol (LLDP), but is not limited thereto.

Then, as shown in step 43, when the user observes that the state of a certain network node is abnormal from the network topology, the user can use the electronic device 11 to display from the display unit 114. The displayed network topology map selects one of the slave nodes 23 as a node to be tested, and the electronic device 11 loads and executes a debug application from the memory unit 121 corresponding to the root node 21. Program 123.

In the preferred embodiment, when the electronic device 11 is a personal computer, the user can click the node to be tested in the network topology through the mouse in the personal computer, or when the electronic device 11 When it is a mobile device, it can be clicked by the touch panel on the mobile device, and is not limited thereto.

Then, as shown in step 44, the debug application 123 pin A first debugging mode is performed on the link path of the root node 21 to the node to be tested, so as to generate a first debugging message 311.

In the preferred embodiment, when the debug application 123 executes the first debug mode, the graphical interface application 122 generates a first debug page 31 (see FIG. 3) to The debug message 311 is displayed on the display unit 114 of the electronic device 11 by the first debug page 31. The first debugging mode includes the debugging application 123 performing a ping test on the link path of the root node 21 to the node to be tested to determine whether the line connection between the root node 21 and the node to be tested is normal.

Then, as shown in step 45, the debug application 123 determines whether the first debug message 311 is an error message.

If the result of the determination in step 45 is no, the debug application 123 continues to perform step 46. The first debug mode further includes the debug application 123 executing a power over Ethernet (PoE). A diagnostic test to determine whether the node to be tested is powered by a network node to which it is connected.

If the result of the determination in the step 46 is no, the step 49 is executed, and the debugging application 123 generates the content on the first debugging page 31 according to the test result of the node to be tested: "The network connectivity is available, but AP is offline.Please contact the customer support team for more information or reboot the AP manually."

Alternatively, if the determination result in the step 46 is YES, the content displayed on the first debugging page 31 is: "The network connectivity is Available, but AP is offline. Please click below button for auto repair." One of the prompt messages and a repair button is provided, and when the repair button is clicked, step 47 is executed, and the debug application 123 is based on The network node (switch or router) adjacent to the test node performs power-off and power-supply operations through the communication port 125 connected to the node to be tested to restart the node to be tested.

Then, as shown in step 49, the debug application 123 generates the content on the first debug page 31 according to the test result of the node to be tested: "The network connectivity is still unavailable. Please contact customer support for more information "The result of the analysis (when the failure has failed) or the analysis of "This AP has been rebooted and online." (when the troubleshooting is successful).

Alternatively, if the result of the determination in step 45 is YES, step 48 is performed, and the debugging application program 123 sequentially connects the connection path of the root node 21 to the node to be tested for each of the two adjacent network nodes. The link path corresponds to performing a second debug mode to generate a plurality of second debug messages 321 .

In the preferred embodiment, when the debug application 123 executes each of the second debug modes, the graphical interface application 122 generates a second debug page 32 (see FIG. 4) to The second debug message 321 is displayed on the display unit 114 of the electronic device 11 by the second debug page 32.

Each second debug mode includes the debug application 123 performing a ping test for the link path of each two adjacent network nodes. Determine if the line connection between each two adjacent network nodes is normal.

If the line connection between two adjacent network nodes is abnormal, that is, the result of the ping test is a failure, the first debugging mode further includes the debugging application 123 performing an ip conflict diagnosis test to determine Whether the IP address of the node to be tested conflicts with other network nodes in the local area network, and if yes, executing step 49, the debugging application 123 is based on the test result of the node to be tested, and the second detection The error page 32 generates the content of: "There is an IP address conflict with this device on the network"; if the line connection between two adjacent network nodes is normal, the result of the ping test is successful, Then the debug application 123 performs a ping test of the next two adjacent nodes.

If the IP address of the node to be tested does not conflict with other network nodes in the local area network, the first debug mode further includes the debug application 123 performing a line quality diagnostic test. The line quality diagnostic test is for the RJ45 network route used for connecting between two adjacent network nodes, and testing the four sets of twisted pairs, wherein the diagnosis result of each set of twisted pairs It corresponds to one of the following seven states: "NO_CABLE", "OK", "OPEN", "SHORT", "Linedriver", "Mismatch", "N/A". In the preferred embodiment, the seven states are given different weights to determine the RJ45 network route to which the two adjacent network nodes are connected.

For example, assume that the weights corresponding to "NO_CABLE", "OK", "OPEN", "SHORT", "Linedriver", "Mismatch", and "N/A" are 20, 1, 30, 200, 10, 100, respectively. 0; if the four sets of twisted pairs correspond to the four states of "OK", "OPEN", "SHORT", and "Linedriver", Then the line quality of the RJ45 is diagnosed as "SHORT" because the "SHORT" has the highest weight.

In addition, when the line quality diagnosis test result is not "OK", step 49 is executed, and the debug application 123 generates the content on the second debug page 32 according to the above diagnosis result: "The cable is not connected ( "no cable)", "The cable is not connected (open)", "The cable is broken (short)", "The module of PoE in AP is broken (linedriver)", "The cable is broken (mismatch)", The result of the analysis of "the result of cable diagnostic is NA."; when the line quality diagnosis test result is "OK" and the node to be tested among the two adjacent network nodes is one of the endpoints, then the The second debugging mode further includes the debugging application 123 performing the Ethernet power supply diagnostic test, and further determining whether the node to be tested is powered by the network node connected thereto, and if not, executing step 49, The debug application 123 generates the content on the second debug page 32 according to the test result of the node to be tested as follows: "The network connectivity is unavailable. The cable status is ok but the switch not support PoE. Please reboot AP manually or c Ontact customer support for more information." The result of the analysis is: "The network connectivity is unavailable. The cable status is ok. Please click below button for auto repair." A prompt message 322 (see FIG. 4) and a repair button are provided, and when the repair button is clicked, the debug application 123 is based on a network node (switch or router) adjacent to the node to be tested. Through the communication with the node to be tested The 埠125 sequentially performs a power-off power supply operation to restart the node to be tested.

Then, as shown in step 49, the debug application 123 generates the content on the first debug page 31 according to the test result of the node to be tested: "The network connectivity is still unavailable. Please contact customer support for more information "The result of the analysis (when the failure has failed) or the analysis of "This AP has been rebooted and online." (when the troubleshooting is successful).

Alternatively, if the IP address of the node to be tested conflicts with other network nodes in the local area network, then, as shown in step 49, the debugging application 123 is based on the test result of the node to be tested. The debug page 32 generates an analysis result of "There is an IP address conflict with this device on the network".

In summary, the present invention uses the network topology diagram to present the physical connection of the physical network device in a tree diagram. The user only needs to click the node to be tested, and the debugging application 123 directly follows the design process. Performing a relative cross-test, finally deducing the analysis results and even performing a repair action (such as remotely restarting the network node), thereby achieving the function of troubleshooting only with a single click, so that the object of the present invention can be achieved. .

The above is only the preferred embodiment of the present invention, and the scope of the present invention is not limited thereto, that is, the simple equivalent changes and modifications made by the patent application scope and patent specification content of the present invention, All remain within the scope of the invention patent.

41~49‧‧‧Steps

Claims (10)

A visual network debugging method, configured to perform debugging by using a network topology image placed on an electronic device, wherein the network topology map has multiple network nodes corresponding to a regional network And the network nodes are respectively composed of a plurality of master nodes and a plurality of root nodes, and the method comprises the following steps: (a) when a user selects the network topology map by the electronic device When one of the slave nodes is a node to be tested, the electronic device loads and executes a debug application from a node; (b) the debug application connects the root node to the node to be tested The path executes a first debug mode to generate a first debug message correspondingly; (c) when the debug application determines that the first debug message is an error message, the debug application is from the root node a second debugging mode is sequentially performed for the connection path of each two adjacent network nodes to generate a plurality of second debugging messages, and (d) the debugging is performed in the connection path of the node to be tested. The application generates an analysis result corresponding to one of the nodes to be tested. The visual network debugging method of claim 1, wherein the step (a) further comprises a step (e), wherein the user selects one of the master nodes as the electronic device When the root node logs in, the electronic device loads and executes a graphical interface application from the root node, thereby causing the graphical interface application to be based on the links of the network nodes. The path generates the network topology and displays it in the electronic device. The visual network debugging method according to claim 1, wherein in the step (b), when the debugging application executes the first debugging mode, the graphical interface application generates a first Debugging the page to display the first debug message on the electronic device by the first debug page. The visual network debugging method according to claim 1, wherein in the step (b), when the debugging application executes each second debugging mode, the graphical interface application generates a first The second debug page is configured to display each second debug message on the electronic device by the second debug page. The visual network debugging method according to claim 1, wherein in the step (c), each of the second debugging modes includes the debugging application is executed for a link path of every two adjacent network nodes. A ping test. The visual network debugging method according to claim 5, wherein, in the step (c), when the result of the ping test is a failure, each second debugging mode further includes the debugging application executing one The ip conflict diagnostic test determines whether the IP address of the node to be tested conflicts with other network nodes in the local area network. The visual network debugging method according to claim 6, wherein, in the step (c), when the result of the ip conflict diagnosis test is not conflicting, each second debugging mode further includes the debugging. The application performs a line quality diagnostic test. The visual network debugging method according to claim 7, wherein, in the step (c), when the result of the line quality diagnostic test is normal, each second debugging mode further includes the debugging application. Program execution of an Ethernet A power supply diagnostic test is performed to determine whether the node to be tested is powered by a network node connected thereto. The visual network debugging method according to claim 1, wherein in the step (c), the first debugging mode includes the debugging application executing a link path of the root node to the node to be tested. A ping test. The visual network debugging method according to claim 9, wherein, in the step (c), when the result of the ping test is successful, the first debugging mode further includes the debugging application executing a B The network power supply diagnostic test determines whether the node to be tested is powered by the network node connected to it.