A method for detecting network device status and correcting errors using a domestic operating system

Abstract

The present application relates to a method for a domestic operating system to detect the status of a network device and correct errors, including 101 reading an attribute configuration file, 102 determining a target network port that needs to be detected currently, and 103 judging whether the target network port name exists and whether the target network port is not marked as a fault state or an ignored state: if one of the conditions is not satisfied, 102 is executed; if both conditions are satisfied, 104 is executed to obtain hardware attribute information of the target network port name, and compare the hardware attribute information with the hardware attribute information of the network port: if the comparison is inconsistent, it is marked as a fault state and a child process is created, and the child process adjusts the target network port, and the main process executes 102; if the comparison is consistent, 105 is continued to be executed to obtain the software status information of the target network port, and judge whether the software status is in a normal state: if not, it is marked as a fault state, and a child process is created, and the child process adjusts the target network port, and the main process continues to execute 102; if so, it is marked as a normal state.

Description

Technical Field

[0001] The present application relates to the field of computer technology, and in particular to a method for a domestic operating system to detect the status of network equipment and correct errors. Background Art

[0002] Large business scenarios generally have more members, such as Figure 1 The business scenario shown requires simultaneous access to multiple devices, including hosts (including host A (including: customer business software, operating system and network card hardware), host B and host C), servers (server A and server B), databases (storage systems include database A, database B and database C), switches (including primary switches and secondary switches) and special devices (including special devices A, special devices B and special devices C). Many members often communicate through a complex internal business network. In such a usage scenario, the stability of network communication is crucial. During the long-term maintenance phase of large projects, many anomalies such as various hardware equipment failures and software failures will inevitably occur. As the underlying foundation, the domestic operating system should have the function of detecting and recovering abnormal network communication status, and a certain degree of network error detection and correction functions need to be implemented.

[0003] The fault-tolerant mechanism of large business systems allows a single device to be in an abnormal state. As long as the device can be restored to normal within a certain period of time by replacing a backup device or restarting, the stability of the entire business system can be guaranteed. However, if a single device has a network problem and the user fails to be informed in time and perform the corresponding recovery operation, it is likely that the core functions of the business system will be affected due to factors such as long-term connection interruption, causing business network failure.

[0004] Existing technical means are mainly used to analyze the cause of a business network failure after it has occurred. Currently, there is no technology on domestic operating systems that can detect abnormal network device status and promptly alert users. Summary of the invention

[0005] To solve the above problems, the present invention provides a method for detecting the status of network devices and correcting errors using a domestic operating system, which adopts the following technical solutions:

[0006] A method for detecting the status of network equipment and correcting errors by a domestic operating system, comprising:

[0007] Step S101, when the power-on is detected, the attribute configuration file is read, the attribute configuration file includes a list of network port names that need to be monitored and a monitoring cycle period configured by the user, and the list of network port names specifies the monitoring order of multiple network ports that the user needs to monitor;

[0008] Step S102, determining a target network port that needs to be detected currently from the multiple network ports based on the network port name list;

[0009] Step S103, determining whether the target network port name corresponding to the target network port exists, and whether the target network port is not marked as a fault state or an ignored state:

[0010] If all the above conditions are met, continue to step S104;

[0011] If one of them is not satisfied, step S102 is executed to traverse the next target network port;

[0012] Step S104, obtaining hardware attribute information corresponding to the target network port name corresponding to the monitored target network port in the domestic operating system, and comparing the hardware attribute information with the network port hardware attribute information configured by the user in the attribute configuration file:

[0013] If the comparison is inconsistent, the state of the target network port is marked as a fault state, and a subprocess corresponding to the target network port is created, and the target network port is adjusted through the subprocess until the target network port is not in a fault state. At the same time, the main process of the network monitoring software executes step S102 to traverse the next target network port;

[0014] If the comparison is consistent, continue to step S105;

[0015] Step S105, obtaining the software status information of the target network port, and judging whether the software status of the target network port is in a normal state based on the software status information:

[0016] If not, the state of the target network port is marked as a fault state, and a subprocess corresponding to the target network port is created, and the target network port is adjusted through the subprocess until the target network port is not in a fault state. At the same time, the main process of the network monitoring software continues to execute step S102 to traverse the next target network port;

[0017] If yes, then mark the state of the target network port as normal, and proceed to step S106;

[0018] Step S106, determining whether the target network port name is the last network port name in the network port name list, if so, proceeding to step S107, if not, proceeding to step S102;

[0019] Step S107, updating the status of the multiple network ports to the network monitoring software display interface, and performing sleep based on the monitoring cycle. After the sleep ends, continue to execute step S102. The status of the multiple network ports includes normal status, fault status and ignored status.

[0020] In another possible implementation, the hardware attribute information includes duplex file information, speed file information, and carrier file information, wherein the duplex file information is used to describe the half / full-duplex working mode, the speed file information is used to describe the network port rate mode, and the carrier file information is used to describe the network cable status. The hardware attribute information corresponding to the target network port name corresponding to the monitored target network port in the domestic operating system is obtained, including:

[0021] According to the target network port device directory automatically generated by the domestic operating system kernel, query the corresponding duplex file information, speed file information and carrier file information under the target network port device directory.

[0022] In another possible implementation, in step S104, adjusting the target network port through a sub-process until the target network port is no longer in a fault state includes:

[0023] Output prompt information of abnormal network port hardware status and provide a "processed" graphical button interface;

[0024] The subprocess enters a dormant state, waiting for the user operation, and wakes up the subprocess when it is detected that the user triggers the "processed" graphical button interface;

[0025] The sub-process executes the operations from step S103 to step S105 on the target network port.

[0026] In another possible implementation, in step S105, adjusting the target network port through a sub-process until the target network port is no longer in a fault state includes:

[0027] Outputting prompt information of abnormal network port software status, and providing a graphical button interface of "process" and "ignore" for the user to select;

[0028] When the child process detects the graphical button interface “processed” by the user, reopen the target network port, and perform the operations of step S103 to step S105 on the target network port;

[0029] When the sub-process detects that the user triggers the "Ignore" graphical button interface, the fault state of the target network port is modified to an ignore state, and the sub-process exits.

[0030] In summary, this application includes the following beneficial technical effects:

[0031] 1. It can obtain various types of network card information through the ioctl interface and the device attribute files generated by the system kernel. It can monitor the hardware and software status of the network card device in real time in the background and detect whether there are network anomalies.

[0032] 2. The graphical main interface allows users to view network card status information and make special settings for specified network card devices; the pop-up interface promptly notifies users of the specific exception type after a network exception occurs, and provides different recovery plans based on the exception type, allowing users to deal with network exceptions in a targeted manner. BRIEF DESCRIPTION OF THE DRAWINGS

[0033] Figure 1 This is a structural example diagram of a large-scale business scenario in an embodiment of the present application.

[0034] Figure 2 It is a flow chart of a method for a domestic operating system to detect the status of network equipment and correct errors in an embodiment of the present application.

[0035] Figure 3 It is a network port state transition diagram in an embodiment of the present application. DETAILED DESCRIPTION

[0036] The present application is further described in detail below in conjunction with the accompanying drawings.

[0037] After reading this specification, those skilled in the art may make non-creative modifications to this embodiment as needed, but such modifications are protected by patent law as long as they are within the scope of the claims of this application.

[0038] In order to make the purpose, technical solution and advantages of the embodiments of the present application clearer, the technical solution in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are 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 this field without creative work are within the scope of protection of this application.

[0039] In addition, the term "and / or" in this article is only a description of the association relationship of associated objects, indicating that there can be three relationships. For example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone. In addition, the character " / " in this article, unless otherwise specified, generally means that the associated objects before and after are in an "or" relationship.

[0040] The embodiments of the present application are further described in detail below in conjunction with the drawings in the specification.

[0041] The embodiment of the present application provides a method for a domestic operating system to detect the status of a network device and correct errors. The method is implemented by network monitoring software. The network monitoring function can be realized by simply installing the network monitoring software on the device to be monitored. Figure 2 as well as Figure 3 As shown, the method specifically includes:

[0042] Step S101, when power-on is detected, read the attribute configuration file.

[0043] The attribute configuration file includes a list of network port names whose status needs to be monitored and a monitoring cycle period configured by the user. The list of network port names specifies the monitoring order of multiple network ports that the user needs to monitor.

[0044] For the embodiment of the present application, when the device is turned on, the network monitoring software service will automatically start and continue to run in the background of the device's operating system. The network monitoring software will read the attribute configuration file, which records the user-configured list of network port names that need to be monitored, the monitoring cycle, and the network port hardware attribute information of each network port, wherein the network port name list specifies the monitoring order of multiple network ports, and the network monitoring software will periodically monitor each network port in turn according to the monitoring cycle and the network port name list until the operating system is shut down or the network monitoring software service is shut down.

[0045] Furthermore, in an embodiment of the present application, the attribute configuration file can be modified by the user according to needs. When the user needs to modify the attribute configuration file, the user must first close the network monitoring software service, and then modify the attribute configuration file, and then restart the network monitoring software service. After restarting the network monitoring software, the network monitoring software will read the new attribute configuration file and continue to run in the background without restarting the machine.

[0046] Step S102, determining a target network port that needs to be detected currently from multiple network ports based on the network port name list;

[0047] Step S103, determining whether the target network port name corresponding to the target network port exists, and whether the target network port is not marked as a fault state or an ignored state:

[0048] If all the above conditions are met, continue to step S104;

[0049] If one of the conditions is not satisfied, step S102 is executed to continue traversing the next target network port.

[0050] For the embodiment of the present application, since the host may replace the network card device in some business scenarios, resulting in a change in the device network port name, the network monitoring software will not be able to identify and access the network port name before the change, so it is necessary to first determine whether there is a target network port name that needs to be monitored in the operating system;

[0051] The fault status refers to the abnormal hardware status and / or abnormal software status of the network port. The ignored status is a special status manually added by the user, indicating that the abnormal software status of the current network port is normal.

[0052] Step S104, obtaining hardware attribute information corresponding to the target network port name corresponding to the monitored target network port in the domestic operating system, and comparing the hardware attribute information with the network port hardware attribute information configured by the user in the attribute configuration file:

[0053] If the comparison is inconsistent, the target network port status is marked as faulty (corresponding to Figure 3 The network monitoring software detects an abnormal hardware status), and creates a subprocess corresponding to the target network port, and adjusts the target network port through the subprocess until the target network port is no longer in a faulty state. At the same time, the main process of the network monitoring software executes step S102 to traverse the next target network port;

[0054] If the comparison is consistent, continue to step S105.

[0055] For the embodiment of the present application, the hardware attribute information includes duplex file information, speed file information and carrier file information, wherein the duplex file information is used to describe the half / full-duplex working mode, the speed file information is used to describe the network port rate mode, and the carrier file information is used to describe the network cable status. According to the target network port device directory automatically generated by the domestic operating system kernel (the system kernel will generate a device directory for each network port separately by default, and the directory address is / sys / class / net / target network port name. The attribute file of the network port will be stored in the directory to record the hardware attribute information of the network port), the corresponding duplex file information and speed file information under the target network port device directory are queried. and carrier file information, and compare the acquired hardware attribute information with the network port hardware attribute information configured by the user in the attribute configuration file. When the attribute comparison is inconsistent, it means that there is an attribute difference, that is, the hardware status of the target network port is abnormal. The network monitoring software will mark the target network port as a fault state and create a sub-process corresponding to the target network port, which is specifically used to manage the target network port. Subsequently, the target network port will be adjusted through the sub-process until the target network port is not in a fault state. At this time, the main process of the network monitoring software will continue to execute step S102 to determine a new target network port; and when the attribute comparison is consistent, it means that the current hardware status of the target network port is normal, and you can directly continue to execute step S105 to perform software-level detection.

[0056] When adjusting the target network port with abnormal hardware status through the child process, it specifically includes:

[0057] Step Sa, outputting prompt information of abnormal network port hardware status, and providing a "processed" graphical button interface.

[0058] For the embodiment of the present application, the prompt information of the abnormal network port hardware status may be "Network port hardware status is abnormal", which may be displayed in the form of a pop-up window. Specifically, since there are multiple types of hardware attribute information, when the cause of the abnormal network port hardware status is inconsistent duplex file information, a prompt of "Half / full-duplex mode abnormality" may be displayed in the pop-up window, and when the cause of the abnormal network port hardware status is inconsistent speed file information, a prompt of "Network port rate abnormality" may be displayed in the pop-up window, and when the carrier file information is inconsistent, a prompt of "Network cable is not properly plugged in or the network cable is faulty" may be displayed in the pop-up window.

[0059] Step Sb, the subprocess enters a dormant state, waiting for user operation, and wakes up the subprocess when it is detected that the user triggers the "processed" graphical button interface.

[0060] For the embodiment of the present application, since the cause of the abnormality at this time is the abnormal state of the network port hardware, the user needs to operate the network port hardware before it can be restored, that is, after the pop-up window displays a prompt message for prompting the user that the network port hardware state is abnormal (corresponding to Figure 3 In the pop-up window interface, after the user operates the hardware, click the "Processed" button. ), the sub-process will enter the dormant state, waiting for the user to operate the hardware and click the "Processed" graphical button, and then the sub-process will be awakened.

[0061] In step Sc, the subprocess executes the operations of step S103 to step S105 on the target network port.

[0062] For the embodiment of the present application, after the child process is awakened, the child process directly detects the hardware status and software status of the target network port, that is, the child process executes steps S103 to S105 on the target network port. Specifically, when executing steps S104 and S105, if there is still an abnormality in the hardware status or the software status, there is no need to continue to create a child process, but directly display the corresponding prompt information and buttons on the window graphical interface that has popped up before. When there is no abnormality in the hardware status and the software status, it means that the target network port is currently in a normal state, then the mark of the fault state of the target network port can be cancelled, and the target network port can be marked as a normal state (corresponding to Figure 3 The network monitoring software detects that the hardware and software status of the network port are normal). At this time, the sub-process exits. When traversing the detection network port in the next cycle, the main process of the network monitoring software will start to access and detect the target network port.

[0063] Step S105, obtaining the software status information of the target network port, and judging whether the software status of the target network port is in a normal state based on the software status information:

[0064] If not, mark the target network port as faulty (corresponding to Figure 3 "The network monitoring software detects that the soft state of the network port is abnormal"), and creates a child process corresponding to the target network port, and adjusts the target network port through the child process until the target network port is not in a faulty state; at the same time, the main process of the network monitoring software executes step S102 to traverse the next target network port;

[0065] If yes, the state of the target network port is marked as normal, and step S106 is continued.

[0066] For the embodiment of the present application, the software status information of the target network port is obtained through ioctl, specifically through the ioctl interface query (ioctl is an interface function for operating the device driver provided by the system kernel, and the software status of each network port can be queried). When the software status information of the target network port is UP&RUNNING, it indicates that the software status of the target network port is in a normal state, and the target network port can be marked as a normal state, and the main process of the network monitoring software continues to execute step S106;

[0067] When the software status information of the target network port is not UP&RUNNING, it means that there is an abnormality in the software status of the target network port. At this time, the main process of the network monitoring software will mark the target network port as a faulty state, and create a child process corresponding to the target network port. The target network port will be adjusted through the child process until the target network port is no longer in a faulty state. At this time, the main process of the network monitoring software will skip the target network port and execute step S102 to determine a new target network port in the order recorded in the network port name list, and continue to detect the new target network port.

[0068] Specifically, when adjusting the target network port with abnormal software status through a subprocess, the specific steps include:

[0069] Step Sd: outputting prompt information of abnormal network port software status, and providing a graphical button interface of "process" and "ignore" for the user to select.

[0070] For the embodiment of the present application, the prompt message of the abnormal network port software status can be "Network port is closed / soft status is abnormal", which can be displayed in the form of a pop-up window. Because the application software will change the network port status in some business scenarios, the change of the network port status is a normal phenomenon at this time, and the recovery plan of the network monitoring software will temporarily cause the host network to be completely disconnected, thereby affecting the upper-layer business transmission. Therefore, whenever the prompt message of the abnormal network port software status appears, the user needs to decide whether to process it at the current moment, that is, the network monitoring software will provide two graphical option interfaces of "Process" and "Ignore" for users to choose.

[0071] Step Se, when the sub-process detects that the user triggers the graphical button interface of "Processing", reopen the target network port and perform the operations of step S103 to step S105 on the target network port.

[0072] For the embodiment of the present application, when the user clicks the graphical option of "Process", the subprocess will reopen the target network port (this process is equivalent to reinitializing the physical network card, so the network of the physical host will be completely disconnected in this process, and the network of the QEMU host maintained by the QEMU software on the physical host depends on the network of the physical host, which will cause the QEMU host network to be completely disconnected until the initialization is completed and the target network port is opened). After the subprocess of the network monitoring software resets the network, it will re-monitor the hardware status and software status of the target network port according to steps S103 to S105. If there are still abnormalities in the hardware status or software status, there is no need to continue to create a subprocess. Instead, the corresponding prompt information and buttons are directly displayed on the graphical interface of the window that has popped up before. When there are no abnormalities in the hardware status and software status, it means that the target network port is currently in a normal state, then the fault status mark of the target network port can be canceled, and the target network port can be marked as normal (corresponding to Figure 3 In the pop-up window, the user clicks the "Process" button. After the network monitoring software reinitializes the network port, the hardware and software status of the detection network port are normal). At this time, the sub-process exits. When the next cycle traverses the detection network port, the main process of the network monitoring software will start to access and detect the target network port.

[0073] Step Sf, when the child process detects that the user triggers the "Ignore" graphical button interface (corresponding to Figure 3 Middle: On the pop-up window, the user clicks the "Ignore" button to change the fault status of the target network port to the ignored status and exit.

[0074] For the embodiment of the present application, when the user clicks the graphical option of processing, the subprocess of the network monitoring software will cancel the mark of the fault state of the target network port and change it to the mark of the ignored state (the network port marked as the ignored state indicates that the network port is blocked by the user. When the network monitoring software detects the network port, it will automatically skip the network port with the ignored state mark and continue to traverse the next network port. The mark of the ignored state can be canceled by the user in the interface of the network detection software (corresponding to Figure 3 In the network monitoring software interface, the user clicks the "Remove" button)), and then the child process exits.

[0075] Step S106, determining whether the target network port name is the last network port name in the network port name list, if so, proceeding to step S107, if not, proceeding to step S102;

[0076] Step S107, updating the status of multiple network ports to the network monitoring software display interface, and performing sleep based on the monitoring cycle. After the sleep ends, continue to execute step S102. The status of multiple network ports includes normal status, fault status and ignored status.

[0077] For the embodiment of the present application, after the network monitoring software has completed detection of all network ports, the main process of the network monitoring software will update the status of each network port (normal status, fault status, or ignored status) to the interface of the network monitoring software, and continue to sleep based on the monitoring cycle in the attribute configuration file. After the sleep period ends, step S102 will continue to be executed to perform a new round of loop traversal.

[0078] Specifically, for the network port marked as ignored, the network monitoring software will provide a release visualization button. When the user clicks the button, the network monitoring software will cancel the ignore status mark of the network port. In the next cycle, the main process of the network monitoring software will revisit the network port and monitor the hardware status and software status.

[0079] Furthermore, when the user needs to modify the network device attribute information, he needs to first close the network monitoring software, then modify the attribute configuration file, and then restart the network monitoring software service. After restarting, the service will read the new configuration content and continue to run in the background without restarting the machine.

[0080] This application obtains various types of network card information through the ioctl interface and the device attribute file generated by the system kernel in multiple ways. It can monitor the hardware and software status of the network card device in real time in the background and detect whether there are network anomalies. It also uses a graphical main interface to facilitate users to view network card status information, and perform special settings for specified network card devices and set up a pop-up interface. After a network anomaly occurs, a pop-up window will be displayed in time to notify the user of the specific anomaly category, and different recovery plans will be provided according to the anomaly type, so that users can deal with network anomalies in a targeted manner.

[0081] The above are only some implementation methods of the present application. It should be pointed out that for ordinary technicians in this technical field, several improvements and modifications can be made without departing from the principles of the present application. These improvements and modifications should also be regarded as the scope of protection of the present application.

Claims

1. A method for detecting the status of network equipment and correcting errors by a domestic operating system, characterized in that: include: Step S101, when the power-on is detected, the attribute configuration file is read, the attribute configuration file includes a list of network port names that need to be monitored and a monitoring cycle period configured by the user, and the list of network port names specifies the monitoring order of multiple network ports that the user needs to monitor; Step S102, determining a target network port that needs to be detected currently from the multiple network ports based on the network port name list; Step S103, determining whether the target network port name corresponding to the target network port exists, and whether the target network port is not marked as a fault state or an ignored state: If all the above conditions are met, continue to step S104; If one of them is not satisfied, step S102 is executed to traverse the next target network port; Step S104, obtaining hardware attribute information corresponding to the target network port name corresponding to the monitored target network port in the domestic operating system, and comparing the hardware attribute information with the network port hardware attribute information configured by the user in the attribute configuration file: If the comparison is inconsistent, the state of the target network port is marked as a fault state, and a subprocess corresponding to the target network port is created, and the target network port is adjusted through the subprocess until the target network port is not in a fault state. At the same time, the main process of the network monitoring software executes step S102 to traverse the next target network port; If the comparison is consistent, continue to step S105; Step S105, obtaining the software status information of the target network port, and judging whether the software status of the target network port is in a normal state based on the software status information: If not, the state of the target network port is marked as a fault state, and a subprocess corresponding to the target network port is created, and the target network port is adjusted through the subprocess until the target network port is not in a fault state. At the same time, the main process of the network monitoring software continues to execute step S102 to traverse the next target network port; If yes, the state of the target network port is marked as normal, and step S106 is continued; the software state information of the target network port is obtained by querying the ioctl interface. When the software state information of the target network port is UP&RUNNING, it indicates that the software state of the target network port is in normal state, and the target network port is marked as normal; Step S106, determining whether the target network port name is the last network port name in the network port name list, if so, proceeding to step S107, if not, proceeding to step S102; Step S107, updating the status of the multiple network ports to the display interface of the network monitoring software, and performing sleep based on the monitoring cycle, and after the sleep is over, continuing to perform step S102, the status of the multiple network ports includes a normal state, a fault state and an ignored state; In step S104, the target network port is adjusted by a sub-process until the target network port is no longer in a fault state, including: Output the prompt information of abnormal network port hardware status and provide a "processed" graphical button interface; The subprocess enters a dormant state, waiting for the user operation, and wakes up the subprocess when it is detected that the user triggers the "processed" graphical button interface; The subprocess performs the operations of step S103 to step S105 on the target network port; In step S105, the target network port is adjusted by a sub-process until the target network port is no longer in a fault state, including: Outputting prompt information of abnormal network port software status, and providing a graphical button interface of "process" and "ignore" for the user to select; When the child process detects the graphical button interface "processed" by the user, reopen the target network port and perform the operations of step S103 to step S105 on the target network port; When the subprocess detects that the user triggers the “ignore” graphical button interface, the fault state of the target network port is modified to an ignore state, and the subprocess exits.

2. According to claim 1, a method for detecting network device status and correcting errors by a domestic operating system is characterized in that: The hardware attribute information includes duplex file information, speed file information and carrier file information, wherein the duplex file information is used to describe the half / full-duplex working mode, the speed file information is used to describe the network port rate mode, and the carrier file information is used to describe the network cable status. The hardware attribute information corresponding to the target network port name corresponding to the monitored target network port in the domestic operating system is obtained, including: According to the target network port device directory automatically generated by the domestic operating system kernel, query the corresponding duplex file information, speed file information and carrier file information under the target network port device directory.

Images