Fault diagnosis method and device of cloud physical machine, storage medium and electronic equipment

Abstract

The embodiment of the invention provides a fault diagnosis method and device of a cloud physical machine, a storage medium and electronic equipment, and relates to the field of cloud computing, the method is applied to a cloud physical machine inspection system, the cloud physical machine inspection system comprises a cloud physical machine resource pool, a switch and a cloud physical machine node, and the cloud physical machine node corresponds to a server of the cloud physical machine. The cloud physical machine nodes are connected with the switch, the cloud physical machine resource pool is used for managing the cloud physical machine nodes, and the method comprises the following steps: obtaining an inspection result obtained by inspecting the cloud physical machine nodes, the inspection result being used for indicating a faulted cloud physical machine node having a fault and an operation stage of the faulted cloud physical machine node when the faulted cloud physical machine node has a fault; performing fault diagnosis on the fault cloud physical machine node according to the inspection result to obtain a fault diagnosis result; and sending the fault diagnosis result to the target object. The problem that the troubleshooting efficiency of the cloud physical machine is low in the related technology is solved.

Description

Technical Field

[0001] The embodiments of the present application relate to the field of cloud computing, and more specifically, to a fault diagnosis method, device, storage medium, and electronic device for a cloud physical machine. Background Art

[0002] In the field of cloud computing technology, bare metal services are a computing service that combines the elasticity of virtual machines with the performance of physical machines. They can provide individuals or enterprises with exclusive cloud physical servers. When creating a bare metal cloud physical machine, you can just create a virtual machine by specifying the hardware requirements, such as processor, memory, image, network and other configurations. And users can flexibly apply for use on demand. However, the process involved in the cloud platform's release of cloud physical machines is relatively complicated. From bare metal registration, bare metal inspection, to cloud physical machine deployment and release, the entire process also involves the control of bare metal direct-connected switches and the creation of PXE (Preboot Execution Environment) networks. Therefore, failures are very likely to occur during the deployment and release of cloud physical machines. Usually, when a cloud platform releases a bare metal cloud physical machine, a manual troubleshooting method is used. This method is time-consuming and cumbersome, and the troubleshooting efficiency is low.

[0003] Therefore, in the related art, there is a problem of low efficiency in troubleshooting cloud physical machines.

[0004] In view of the low efficiency of cloud physical machine troubleshooting in related technologies, no effective solution has been proposed yet. Summary of the invention

[0005] The embodiments of the present application provide a cloud physical machine fault diagnosis method, device, storage medium and electronic device to at least solve the problem of low efficiency of cloud physical machine fault troubleshooting in related technologies.

[0006] According to an embodiment of the present application, a fault diagnosis method for a cloud physical machine is provided, which is applied to a cloud physical machine inspection system. The cloud physical machine inspection system includes a cloud physical machine resource pool, a switch, and a cloud physical machine node. The cloud physical machine node corresponds to a server of the cloud physical machine. The cloud physical machine node is connected to the switch. The cloud physical machine resource pool is used to manage the cloud physical machine node. The method includes: obtaining an inspection result obtained by inspecting the cloud physical machine node, the inspection result is used to indicate a faulty cloud physical machine node and the operating stage of the faulty cloud physical machine node when the fault occurs; performing fault diagnosis on the faulty cloud physical machine node according to the inspection result to obtain a fault diagnosis result; and sending the fault diagnosis result to a target object.

[0007] In an exemplary embodiment, a fault diagnosis is performed on the faulty cloud physical machine node according to the inspection result to obtain a fault diagnosis result, including: obtaining first virtual LAN information of a cloud physical machine deployment boot network, wherein the cloud physical machine deployment boot network is created by the cloud physical machine resource pool, and the cloud physical machine deployment boot network is used to guide the cloud physical machine to be deployed in the cloud physical machine resource pool; and obtaining second virtual LAN information of a target port of a target switch, wherein the target switch represents a switch connected to the faulty cloud physical machine node, and the target port represents a port connected to the target switch and the faulty cloud physical machine node; comparing the first virtual LAN information and the second virtual LAN information to obtain a comparison result; and determining the fault diagnosis result as inconsistent virtual LAN information when it is determined that the comparison result indicates that the first virtual LAN information and the second virtual LAN information are inconsistent.

[0008] In an exemplary embodiment, obtaining first virtual LAN information of a cloud physical machine deployment boot network and obtaining second virtual LAN information of a target port of a target switch include: determining a fault type of the faulty cloud physical machine node according to an operation stage at which the faulty cloud physical machine node is located when the fault occurs, and obtaining the first virtual LAN information and the second virtual LAN information in a manner corresponding to the fault type; wherein, when it is determined that the fault occurrence stage is an inspection stage, the fault type is determined to be a cloud physical machine inspection fault, and when it is determined that the fault occurrence stage is a deployment stage, the fault type is determined to be a cloud physical machine deployment fault.

[0009] In an exemplary embodiment, the first virtual LAN information and the second virtual LAN information are obtained in a manner corresponding to the fault type, including: when it is determined that the fault type is a check fault of the cloud physical machine, obtaining a configuration file of the cloud physical machine resource pool; obtaining first login information from the configuration file, and logging in to a first management system according to the first login information, wherein the first login information represents the login information of the cloud physical machine resource pool, the first management system represents the management system of the cloud physical machine resource pool, and the first management system is used to manage network configuration information of the cloud physical machine resource pool; obtaining the first virtual LAN information from the first management system; obtaining the second login information from the first management system, and logging in to the second management system according to the second login information, wherein the second login information represents the login information of the target switch, the second management system represents the management system of the target switch, and the second management system is used to manage the network configuration information of the target switch; obtaining the second virtual LAN information from the second management system.

[0010] In an exemplary embodiment, the first virtual LAN information and the second virtual LAN information are obtained in a manner corresponding to the fault type, including: when it is determined that the fault type is the cloud physical machine deployment failure, obtaining a configuration file of the cloud physical machine resource pool, obtaining first login information from the configuration file, and logging in to the first management system according to the first login information; obtaining the first virtual LAN information from the first management system; obtaining attribute information of the network connection port of the faulty cloud physical machine node, obtaining the second login information from the attribute information, and logging in to the second management system according to the second login information; obtaining the second virtual LAN information from the second management system.

[0011] In an exemplary embodiment, after comparing the first virtual LAN information and the second virtual LAN information to obtain a comparison result, the method further includes: when it is determined that the comparison result indicates that the first virtual LAN information and the second virtual LAN information are consistent, obtaining the network addresses of all network connection ports of the cloud physical machine deployment boot network to obtain multiple network addresses, and performing a network connectivity test on the multiple network addresses; when it is determined that the network connectivity test has failed, determining a network connectivity fault based on the fault diagnosis result.

[0012] In an exemplary embodiment, performing a network connectivity test on the multiple network addresses includes: selecting a first network address and a second network address from the multiple network addresses, and sending an echo request message to the second network address through the first network address; when it is determined that the second network address has received the echo request message, sending an echo reply message to the first network address through the second network address; when it is determined that the first network address has received the echo reply message, determining that the first network address and the second network address are connected; traversing the multiple network addresses, and when it is determined that any two network addresses are connected, determining that the network connectivity test has passed.

[0013] According to another embodiment of the present application, a fault diagnosis device for a cloud physical machine is provided, including: an acquisition module, used to obtain inspection results obtained by inspecting cloud physical machine nodes, wherein the inspection results are used to indicate a faulty cloud physical machine node and the operating stage of the faulty cloud physical machine node when the fault occurs; a diagnosis module, used to perform fault diagnosis on the faulty cloud physical machine node according to the inspection results to obtain a fault diagnosis result; and a sending module, used to send the fault diagnosis result to a target object.

[0014] According to another embodiment of the present application, a computer-readable storage medium is provided, in which a computer program is stored, wherein the computer program is configured to execute the steps of any of the above method embodiments when run.

[0015] According to another embodiment of the present application, an electronic device is provided, including a memory and a processor, wherein the memory stores a computer program, and the processor is configured to run the computer program to execute the steps in any one of the above method embodiments.

[0016] According to another embodiment of the present application, a computer program product is provided, including a computer program, and when the computer program is executed by a processor, the steps in the above method embodiment are implemented.

[0017] Through the present application, cloud physical machine nodes can be inspected to obtain faulty cloud physical machine nodes and the operating stage of the faulty cloud physical machine nodes when the fault occurs, and then fault diagnosis can be performed on the faulty cloud physical machine nodes according to the operating stage of the faulty cloud physical machine nodes when the fault occurs. The fault diagnosis results can then be sent to the target object, thereby solving the problem of low efficiency in troubleshooting cloud physical machines in related technologies. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] Figure 1 It is a hardware structure block diagram of a server device of a cloud physical machine fault diagnosis method according to an embodiment of the present application;

[0019] Figure 2 is a flow chart of a fault diagnosis method for a cloud physical machine according to an embodiment of the present application;

[0020] Figure 3 is a schematic diagram of a fault diagnosis method for a cloud physical machine according to an embodiment of the present application (I);

[0021] Figure 4 is a schematic diagram of a fault diagnosis method for a cloud physical machine according to an embodiment of the present application (II);

[0022] Figure 5 It is a structural block diagram of a fault diagnosis device for a cloud physical machine according to an embodiment of the present application. DETAILED DESCRIPTION

[0023] The embodiments of the present application will be described in detail below with reference to the accompanying drawings and in combination with the embodiments.

[0024] It should be noted that the terms "first", "second", etc. in the specification and claims of this application and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence.

[0025] The method embodiments provided in the embodiments of the present application can be executed in a server device or a similar computing device. Taking running on a server device as an example, Figure 1 1 is a hardware structure block diagram of a server device of a cloud physical machine fault diagnosis method according to an embodiment of the present application. Figure 1 As shown, the server device may include one or more ( Figure 1 Only one is shown in the figure) a processor 102 (the processor 102 may include but is not limited to a processing device such as a microprocessor MCU or a programmable logic device FPGA) and a memory 104 for storing data, wherein the server device may also include a transmission device 106 and an input / output device 108 for communication functions. It can be understood by those skilled in the art that Figure 1 The structure shown is only for illustration and does not limit the structure of the above server device. Figure 1 More or fewer components as shown, or with Figure 1 Different configurations are shown.

[0026] The memory 104 can be used to store computer programs, for example, software programs and modules of application software, such as the computer program corresponding to the fault diagnosis method of the cloud physical machine in the embodiment of the present application. The processor 102 executes various functional applications and data processing by running the computer program stored in the memory 104, that is, the fault diagnosis method of the above-mentioned cloud physical machine is realized. The memory 104 may include a high-speed random access memory, and may also include a non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some instances, the memory 104 may further include a memory remotely arranged relative to the processor 102, and these remote memories can be connected to the server device via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0027] The transmission device 106 is used to receive or send data via a network. The specific example of the above network may include a wireless network provided by a communication provider of the server device. In one example, the transmission device 106 includes a network adapter (Network Interface Controller, referred to as NIC), which can be connected to other network devices through a base station so as to communicate with the Internet. In one example, the transmission device 106 can be a radio frequency (RF) module, which is used to communicate with the Internet wirelessly.

[0028] The following is an explanation of the professional terms that appear in this application:

[0029] Bare Metal Server: A physical server without an operating system installed, also referred to as bare metal.

[0030] Cloud physical machine: The concept in the cloud platform corresponds to the virtual machine, which refers to a bare metal server on the cloud platform with an operating system installed.

[0031] Openstack: An open source cloud computing management platform.

[0032] Ironic: Bare metal service in OpenStack, used to manage and deploy bare metal.

[0033] bm-pxe network: A network dedicated to PXE (Preboot Execution Environment) booting during bare metal server deployment and management. PXE is a protocol that allows network booting, which enables computers to boot operating systems over the network without local storage devices.

[0034] In this embodiment, a fault diagnosis method for a cloud physical machine is provided, which is applied to a cloud physical machine inspection system. The cloud physical machine inspection system includes a cloud physical machine resource pool, a switch, and a cloud physical machine node. The cloud physical machine node corresponds to a server of the cloud physical machine. The cloud physical machine node is connected to the switch, and the cloud physical machine resource pool is used to manage the cloud physical machine node. Figure 2 is a flow chart of a fault diagnosis method for a cloud physical machine according to an embodiment of the present application, such as Figure 2 As shown, the process includes the following steps:

[0035] Step S202, obtaining an inspection result obtained by inspecting the cloud physical machine node, wherein the inspection result is used to indicate a faulty cloud physical machine node and an operation stage of the faulty cloud physical machine node when the fault occurs;

[0036] It should be noted that in the above step S202, the operation stage in which the faulty cloud physical machine node is located when the fault occurs includes the inspection stage and the deployment stage, wherein the inspection stage refers to the stage of obtaining the hardware information of the bare metal server, and the deployment stage refers to the stage of deploying the operating system on the bare metal server after the inspection stage passes.

[0037] Step S204, performing fault diagnosis on the faulty cloud physical machine node according to the inspection result to obtain a fault diagnosis result;

[0038] Step S206: sending the fault diagnosis result to the target object.

[0039] Through the above steps, the cloud physical machine nodes can be inspected to obtain the faulty cloud physical machine nodes and the operating stage of the faulty cloud physical machine nodes when the fault occurs, and then the faulty cloud physical machine nodes can be diagnosed according to the operating stage of the faulty cloud physical machine nodes when the fault occurs, and then the fault diagnosis results can be sent to the target object, thereby solving the problem of low efficiency of cloud physical machine fault troubleshooting in related technologies.

[0040] In an exemplary embodiment, the specific implementation process of performing fault diagnosis on the faulty cloud physical machine node according to the inspection result to obtain the fault diagnosis result in the above step S202 includes: obtaining first virtual LAN information of the cloud physical machine deployment boot network, wherein the cloud physical machine deployment boot network is created by the cloud physical machine resource pool, and the cloud physical machine deployment boot network is used to guide the cloud physical machine to be deployed in the cloud physical machine resource pool; and obtaining second virtual LAN information of the target port of the target switch, wherein the target switch represents the switch connected to the faulty cloud physical machine node, and the target port represents the port connected to the target switch and the faulty cloud physical machine node; comparing the first virtual LAN information and the second virtual LAN information to obtain a comparison result; when it is determined that the comparison result indicates that the first virtual LAN information and the second virtual LAN information are inconsistent, determining the fault diagnosis result as inconsistent virtual LAN information.

[0041] Optionally, in the above embodiment, the cloud physical machine deployment boot network is the bm-pxe network, and the first virtual local area network information of the cloud physical machine deployment boot network is the VLAN (Virtual Local Area Network) information of the bm-pxe network. The cloud physical machine node is connected to the port of the switch, the target port is the port where the failed cloud physical machine node is connected to the switch, and the second virtual local area network information is the VLAN information of the target port.

[0042] Through the above embodiments, the virtual LAN information of the cloud physical machine deployment boot network and the virtual LAN information of the switch port connected to the cloud physical machine node can be compared, so as to quickly determine whether the fault is caused by inconsistent virtual LAN information, thereby improving troubleshooting efficiency.

[0043] In an exemplary embodiment, the above-mentioned process of obtaining the first virtual LAN information of the cloud physical machine deployment boot network and obtaining the second virtual LAN information of the target port of the target switch can be implemented in the following way: determine the fault type of the faulty cloud physical machine node according to the running stage when the faulty cloud physical machine node fails, and obtain the first virtual LAN information and the second virtual LAN information according to the method corresponding to the fault type; wherein, when it is determined that the fault occurrence stage is the inspection stage, the fault type is determined to be a cloud physical machine inspection fault, and when it is determined that the fault occurrence stage is the deployment stage, the fault type is determined to be a cloud physical machine deployment fault.

[0044] Optionally, in the above embodiment, the inspection phase needs to perform inspection operations on the bare metal server to obtain basic information such as the server's processor, memory, hard disk, etc., and the deployment phase needs to write the user image to the hard disk of the bare metal server, and then control the switch to switch the bare metal network to the user network.

[0045] Through the above embodiments, fault diagnosis can be performed on the faulty nodes of the cloud physical machine according to different fault types, and the effect of targeted troubleshooting can be achieved for specific fault scenarios, thereby locating the fault problem more quickly.

[0046] In an exemplary embodiment, the implementation process of obtaining the first virtual LAN information and the second virtual LAN information in a manner corresponding to the fault type includes: when it is determined that the fault type is a cloud physical machine inspection fault, obtaining a configuration file of the cloud physical machine resource pool; obtaining first login information from the configuration file, and logging in to a first management system according to the first login information, wherein the first login information represents the login information of the cloud physical machine resource pool, the first management system represents the management system of the cloud physical machine resource pool, and the first management system is used to manage network configuration information of the cloud physical machine resource pool; obtaining the first virtual LAN information from the first management system; obtaining second login information from the first management system, and logging in to the second management system according to the second login information, wherein the second login information represents the login information of the target switch, the second management system represents the management system of the target switch, and the second management system is used to manage the network configuration information of the target switch; obtaining the second virtual LAN information from the second management system.

[0047] Optionally, in the above embodiment, the configuration file of the cloud physical machine resource pool includes the environment address of the bare metal resource pool, the endpoint address, and token and other information (equivalent to the first login information), wherein the endpoint is the access point of the service in openStack, which is used to interact with the services of openStack, and the token is the authentication credential for accessing the service. The content in the above configuration file can be used to log in to the management system of the cloud physical machine resource pool, and then the VLAN information of the bm-pxe network can be obtained.

[0048] In the management system of the cloud physical machine resource pool, you can also obtain the login information of the target switch (equivalent to the second login information), including the IP address, login account and password. The target switch represents the switch to which the faulty physical machine node is connected. You can log in to the management system of the target switch through the above IP address, login account and password, and then obtain the VLAN information of the port connecting the faulty cloud physical machine node to the switch.

[0049] In an exemplary embodiment, the above-mentioned implementation process of obtaining the first virtual LAN information and the second virtual LAN information in a manner corresponding to the fault type also includes: when it is determined that the fault type is the cloud physical machine deployment failure, obtaining the configuration file of the cloud physical machine resource pool, obtaining the first login information from the configuration file, and logging in to the first management system according to the first login information; obtaining the first virtual LAN information from the first management system; obtaining the attribute information of the network connection port of the faulty cloud physical machine node, obtaining the second login information from the attribute information, and logging in to the second management system according to the second login information; obtaining the second virtual LAN information from the second management system.

[0050] Optionally, in the above embodiment, the cloud physical machine node can be connected to different networks. The name and port information of the target switch can be obtained by viewing the properties of the network connection port, and then the corresponding IP address, login account and password can be obtained from the configuration file according to the name and port information of the target switch. The management system of the target switch can be logged in through the above IP address, login account and password, and the VLAN information of the port connecting the faulty cloud physical machine node to the switch can be obtained.

[0051] In an exemplary embodiment, after executing the above-mentioned step of comparing the first virtual LAN information and the second virtual LAN information to obtain a comparison result, the method also includes: when it is determined that the comparison result indicates that the first virtual LAN information and the second virtual LAN information are consistent, obtaining the network addresses of all network connection ports of the cloud physical machine deployment boot network, obtaining multiple network addresses, and performing a network connectivity test on the multiple network addresses; when it is determined that the network connectivity test has failed, determining a network connectivity failure based on the fault diagnosis result.

[0052] In an exemplary embodiment, the network connectivity test can be performed on the multiple network addresses in the following manner, specifically including: selecting the first network address and the second network address from the multiple network addresses, and sending an echo request message to the second network address through the first network address; when it is determined that the second network address has received the echo request message, sending an echo reply message to the first network address through the second network address; when it is determined that the first network address has received the echo reply message, determining that the first network address and the second network address are connected; traversing the multiple network addresses, and when it is determined that any two network addresses are connected, determining that the network connectivity test has passed.

[0053] Obviously, the embodiments described above are only some embodiments of the present application, not all embodiments. In order to better understand the verification method of the above test case, the above process is described below in conjunction with the embodiments, but it is not intended to limit the technical solutions of the embodiments of the present application, specifically:

[0054] In an alternative embodiment, Figure 3 is a schematic diagram of a fault diagnosis method for a cloud physical machine according to an embodiment of the present application (I), such as Figure 3 As shown, the specific steps include:

[0055] Step S301: Power on the cloud physical machine inspection system.

[0056] Optionally, the architecture of the above cloud physical machine inspection system is as follows: Figure 4 As shown, the cloud physical machine inspection system is interconnected with the cloud physical machine resource pool, cloud physical machine nodes, and switches through a management network, wherein the cloud physical machine nodes correspond to physical servers, and the cloud physical machine nodes are connected to the switch, which is then connected to the cloud physical machine resource pool to generate a cloud physical machine instance. The cloud physical machine resource pool includes multiple cloud physical machine node instances to perform unified resource management on the cloud physical machine nodes.

[0057] Step S302: Read the configuration file and parse the input parameters.

[0058] The input parameters of the cloud physical machine fault inspection system include the unique identifier of the cloud physical machine node, the designated port information of the cloud physical machine node access switch, etc. After parsing the input parameters, they will be saved in global variables for easy use in subsequent processing.

[0059] Step S303: Login authentication.

[0060] The configuration file contains the IP address, account number, and password of the cloud physical machine resource pool. The cloud physical machine inspection system can log in to the bare metal resource pool management system through the account number and password.

[0061] Step S304: Fault diagnosis.

[0062] If the fault occurs in the inspection phase, the bare metal inspection system first logs in to the management system of the cloud physical machine resource pool and reads the VLAN of the BM-PXE network through the control command. After the acquisition is completed, the IP address, login account and password of the switch are read through the control command. Then log in to the management system of the switch to obtain the VLAN of the specified port of the input parameter, and then compare the VLAN of the BM-PXE network with the VLAN of the specified port. If they are inconsistent, the cause of the fault is determined to be VLAN inconsistency. If the two VLANs are consistent, the detection and processing of the BM-PXE network is entered. First, the cloud physical machine inspection system obtains all ports (equivalent to network connection nodes) under the network through the BM-PXE network name in the cloud physical machine resource pool. The obtained port is parsed to extract the IP address and save it. Then all the obtained BM-PXE port IPs are pinged (equivalent to network connectivity test). If there is a ping failure, the fault diagnosis result is determined to be a network connectivity failure. If any abnormality occurs during the above execution process, the cloud physical machine inspection system will stop and return the abnormal result.

[0063] If the fault occurs in the cloud physical machine inspection and acquisition of server hardware information stage, the cloud physical machine inspection system first logs in to the management system of the cloud physical machine resource pool and reads the VLAN of the bm-pxe network through the control command. After the acquisition is completed, all ports of the current cloud physical machine node are obtained according to the unique identifier of the current cloud physical machine fault node, and each port is processed. During the port processing process, the name and port information of the switch connected to the current cloud physical machine node are obtained from the port attributes. Then read the IP address, account and password of the switch corresponding to the switch name in the configuration file, so as to log in to the switch management system to obtain the VLAN of the switch port connected to the cloud physical machine node, and then compare the VLAN of the bm-pxe network with the VLAN of the switch port. If they are inconsistent, it is determined that the cause of the fault is inconsistent VLAN. If the VLANs are consistent, the bm-pxe network is diagnosed. The specific process is the same as the processing process of the above inspection stage, which will not be repeated here.

[0064] Step S305: Output the fault diagnosis result.

[0065] The above fault diagnosis results are output and sent to the target object.

[0066] Through the above embodiments, it is possible to automatically check whether the VLAN of the cloud physical machine and the switch is set correctly, and automatically check whether the PEX network of the cloud physical machine is deployed correctly, thereby reducing the cost of manual troubleshooting and improving the reliability of cloud service products such as cloud physical machine services.

[0067] Through the description of the above implementation methods, those skilled in the art can clearly understand that the method according to the above embodiment can be implemented by means of software plus a necessary general hardware platform, and of course by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of the present application, or the part that contributes to the prior art, can be embodied in the form of a software product, which is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk), and includes a number of instructions for a terminal device (which can be a mobile phone, computer, server, or network device, etc.) to execute the methods described in each embodiment of the present application.

[0068] In this embodiment, a fault diagnosis device for a cloud physical machine is also provided. The system is used to implement the above-mentioned embodiments and preferred implementation modes, and the descriptions that have been made will not be repeated. As used below, the term "module" can be a combination of software and / or hardware that implements a predetermined function. Although the system described in the following embodiments is preferably implemented in software, the implementation of hardware, or a combination of software and hardware, is also possible and conceivable.

[0069] Figure 5 is a structural block diagram of a fault diagnosis device for a cloud physical machine according to an embodiment of the present application, such as Figure 5 As shown, the device comprises:

[0070] An acquisition module 52 is used to acquire an inspection result obtained by inspecting the cloud physical machine node, wherein the inspection result is used to indicate the failed cloud physical machine node and the operation stage of the failed cloud physical machine node when the failure occurs;

[0071] A diagnosis module 54, configured to perform fault diagnosis on the faulty cloud physical machine node according to the inspection result to obtain a fault diagnosis result;

[0072] The sending module 56 is used to send the fault diagnosis result to the target object.

[0073] Through the above-mentioned device, the cloud physical machine nodes can be inspected to obtain the faulty cloud physical machine nodes and the operating stage of the faulty cloud physical machine nodes when the fault occurs, and then the faulty cloud physical machine nodes can be diagnosed according to the operating stage of the faulty cloud physical machine nodes when the fault occurs, and then the fault diagnosis results can be sent to the target object, thereby solving the problem of low efficiency of cloud physical machine fault troubleshooting in related technologies.

[0074] In an exemplary embodiment, the above-mentioned diagnostic module 54 is also used to: obtain the first virtual LAN information of the cloud physical machine deployment boot network, wherein the cloud physical machine deployment boot network is created by the cloud physical machine resource pool, and the cloud physical machine deployment boot network is used to guide the cloud physical machine to be deployed in the cloud physical machine resource pool; and obtain the second virtual LAN information of the target port of the target switch, the target switch represents the switch connected to the faulty cloud physical machine node, and the target port represents the port connecting the target switch to the faulty cloud physical machine node; compare the first virtual LAN information and the second virtual LAN information to obtain a comparison result; when it is determined that the comparison result indicates that the first virtual LAN information and the second virtual LAN information are inconsistent, determine the fault diagnosis result as inconsistent virtual LAN information.

[0075] In an exemplary embodiment, the above-mentioned diagnostic module 54 is also used to: determine the fault type of the faulty cloud physical machine node according to the operating stage at which the faulty cloud physical machine node is when the fault occurs, and obtain the first virtual LAN information and the second virtual LAN information according to the method corresponding to the fault type; wherein, when it is determined that the fault occurrence stage is the inspection stage, the fault type is determined to be a cloud physical machine inspection fault, and when it is determined that the fault occurrence stage is the deployment stage, the fault type is determined to be a cloud physical machine deployment fault.

[0076] In an exemplary embodiment, the above-mentioned diagnostic module 54 is also used to: when it is determined that the fault type is the cloud physical machine inspection fault, obtain the configuration file of the cloud physical machine resource pool; obtain the first login information from the configuration file, and log in to the first management system according to the first login information, wherein the first login information represents the login information of the cloud physical machine resource pool, the first management system represents the management system of the cloud physical machine resource pool, and the first management system is used to manage the network configuration information of the cloud physical machine resource pool; obtain the first virtual LAN information from the first management system; obtain the second login information from the first management system, and log in to the second management system according to the second login information, wherein the second login information represents the login information of the target switch, the second management system represents the management system of the target switch, and the second management system is used to manage the network configuration information of the target switch; obtain the second virtual LAN information from the second management system.

[0077] In an exemplary embodiment, the above-mentioned diagnostic module 54 is also used to: when it is determined that the fault type is the cloud physical machine deployment failure, obtain the configuration file of the cloud physical machine resource pool, obtain the first login information from the configuration file, and log in to the first management system according to the first login information; obtain the first virtual LAN information from the first management system; obtain the attribute information of the network connection port of the faulty cloud physical machine node, obtain the second login information from the attribute information, and log in to the second management system according to the second login information; obtain the second virtual LAN information from the second management system.

[0078] In an exemplary embodiment, the above-mentioned diagnostic module 54 is also used to: when it is determined that the comparison result indicates that the first virtual LAN information and the second virtual LAN information are consistent, obtain the network addresses of all network connection ports of the cloud physical machine deployment boot network, obtain multiple network addresses, and perform network connectivity tests on the multiple network addresses; when it is determined that the network connectivity test fails, determine the network connectivity failure based on the fault diagnosis result.

[0079] In an exemplary embodiment, the above-mentioned diagnostic module 54 is also used to: select the first network address and the second network address from the multiple network addresses, and send an echo request message to the second network address through the first network address; when it is determined that the second network address has received the echo request message, send an echo reply message to the first network address through the second network address; when it is determined that the first network address has received the echo reply message, determine that the first network address and the second network address are connected; traverse the multiple network addresses, and when it is determined that any two network addresses are connected, determine that the network connectivity test has passed.

[0080] It should be noted that the above modules can be implemented by software or hardware. For the latter, it can be implemented in the following ways, but not limited to: the above modules are all located in the same processor; or the above modules are located in different processors in any combination.

[0081] An embodiment of the present application further provides a computer-readable storage medium, in which a computer program is stored, wherein the computer program is configured to execute the steps of any of the above method embodiments when running.

[0082] Optionally, in this embodiment, the storage medium may be configured to store program codes for executing the following steps:

[0083] S1, obtaining an inspection result obtained by inspecting the cloud physical machine node, wherein the inspection result is used to indicate a faulty cloud physical machine node and an operation stage of the faulty cloud physical machine node when the fault occurs;

[0084] S2, performing fault diagnosis on the faulty cloud physical machine node according to the inspection result to obtain a fault diagnosis result;

[0085] S3, sending the fault diagnosis result to the target object.

[0086] In an exemplary embodiment, the computer-readable storage medium may include, but is not limited to, various media that can store computer programs, such as a USB flash drive, a read-only memory (ROM), a random access memory (RAM), a mobile hard disk, a magnetic disk or an optical disk.

[0087] An embodiment of the present application further provides an electronic device, including a memory and a processor, wherein a computer program is stored in the memory, and the processor is configured to run the computer program to execute the steps in any one of the above method embodiments.

[0088] Optionally, in this embodiment, the processor may be configured to perform the following steps through a computer program:

[0089] S1, obtaining an inspection result obtained by inspecting the cloud physical machine node, wherein the inspection result is used to indicate a faulty cloud physical machine node and an operation stage of the faulty cloud physical machine node when the fault occurs;

[0090] S2, performing fault diagnosis on the faulty cloud physical machine node according to the inspection result to obtain a fault diagnosis result;

[0091] S3, sending the fault diagnosis result to the target object.

[0092] An embodiment of the present application further provides a computer program product, which includes a computer program. When the computer program is executed by a processor, the steps in any one of the above method embodiments are implemented.

[0093] Optionally, in this embodiment, the computer program may be configured to perform the following steps by means of the computer program:

[0094] S1, obtaining an inspection result obtained by inspecting the cloud physical machine node, wherein the inspection result is used to indicate a faulty cloud physical machine node and an operation stage of the faulty cloud physical machine node when the fault occurs;

[0095] S2, performing fault diagnosis on the faulty cloud physical machine node according to the inspection result to obtain a fault diagnosis result;

[0096] S3, sending the fault diagnosis result to the target object.

[0097] For specific examples in this embodiment, reference may be made to the examples described in the above embodiments and exemplary implementation modes, and this embodiment will not be described in detail herein.

[0098] Obviously, those skilled in the art should understand that the above modules or steps of the present application can be implemented by a general computing device, they can be concentrated on a single computing device, or distributed on a network composed of multiple computing devices, they can be implemented by a program code executable by a computing device, so that they can be stored in a storage device and executed by the computing device, and in some cases, the steps shown or described can be executed in a different order from that herein, or they can be made into individual integrated circuit modules, or multiple modules or steps therein can be made into a single integrated circuit module for implementation. Thus, the present application is not limited to any specific combination of hardware and software.

[0099] The above description is only the preferred 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 modifications and variations. Any modification, equivalent replacement, improvement, etc. made within the principles of the present application shall be included in the protection scope of the present application.

Claims

1. A fault diagnosis method for a cloud physical machine, characterized in that: Applied to a cloud physical machine inspection system, the cloud physical machine inspection system includes a cloud physical machine resource pool, a switch, and a cloud physical machine node, the cloud physical machine node corresponds to a server of the cloud physical machine, the cloud physical machine node is connected to the switch, the cloud physical machine resource pool is used to manage the cloud physical machine node, and the method includes: Obtaining an inspection result obtained by inspecting the cloud physical machine node, wherein the inspection result is used to indicate a faulty cloud physical machine node and an operation stage of the faulty cloud physical machine node when the fault occurs; Perform fault diagnosis on the faulty cloud physical machine node according to the inspection result to obtain a fault diagnosis result; and send the fault diagnosis result to a target object.

2. The method according to claim 1, characterized in that Performing fault diagnosis on the faulty cloud physical machine node according to the inspection result to obtain a fault diagnosis result, including: Acquire first virtual local area network information of a cloud physical machine deployment boot network, wherein the cloud physical machine deployment boot network is created by the cloud physical machine resource pool, and the cloud physical machine deployment boot network is used to guide the cloud physical machine to be deployed in the cloud physical machine resource pool; and obtaining second virtual local area network information of a target port of a target switch, wherein the target switch represents a switch connected to the failed cloud physical machine node, and the target port represents a port connected to the target switch and the failed cloud physical machine node; Comparing the first virtual local area network information with the second virtual local area network information to obtain a comparison result; When it is determined that the comparison result indicates that the first virtual local area network information and the second virtual local area network information are inconsistent, the fault diagnosis result is determined as inconsistent virtual local area network information.

3. The method according to claim 2, characterized in that Acquiring the first virtual local area network information of the cloud physical machine deployment boot network and acquiring the second virtual local area network information of the target port of the target switch includes: Determine the fault type of the faulty cloud physical machine node according to the operation stage at which the faulty cloud physical machine node is located when the fault occurs, and obtain the first virtual local area network information and the second virtual local area network information according to the method corresponding to the fault type; Among them, when it is determined that the fault occurrence stage is the inspection stage, the fault type is determined to be a cloud physical machine inspection fault; when it is determined that the fault occurrence stage is the deployment stage, the fault type is determined to be a cloud physical machine deployment fault.

4. The method according to claim 3, characterized in that Acquiring the first virtual local area network information and the second virtual local area network information according to a method corresponding to the fault type includes: When it is determined that the fault type is a check fault of the cloud physical machine, obtaining a configuration file of the cloud physical machine resource pool; Acquire first login information from the configuration file, and log in to a first management system according to the first login information, wherein the first login information represents login information of the cloud physical machine resource pool, the first management system represents a management system of the cloud physical machine resource pool, and the first management system is used to manage network configuration information of the cloud physical machine resource pool; Acquire the first virtual local area network information from the first management system; Acquire second login information from the first management system, and log in to the second management system according to the second login information, wherein the second login information represents the login information of the target switch, the second management system represents the management system of the target switch, and the second management system is used to manage the network configuration information of the target switch; The second virtual local area network information is obtained from the second management system.

5. The method according to claim 3, characterized in that: Acquiring the first virtual local area network information and the second virtual local area network information according to a method corresponding to the fault type includes: When it is determined that the fault type is a cloud physical machine deployment fault, obtain a configuration file of the cloud physical machine resource pool, obtain first login information from the configuration file, and log in to a first management system according to the first login information; obtain first virtual local area network information from the first management system; Acquire attribute information of the network connection port of the faulty cloud physical machine node, acquire the second login information from the attribute information, and log in to the second management system according to the second login information; The second virtual local area network information is obtained from the second management system.

6. The method according to claim 2, characterized in that After comparing the first virtual local area network information and the second virtual local area network information to obtain a comparison result, the method further includes: When it is determined that the comparison result indicates that the first virtual local area network information and the second virtual local area network information are consistent, obtaining network addresses of all network connection ports of the cloud physical machine deployment boot network to obtain multiple network addresses, and performing a network connectivity test on the multiple network addresses; In the case where it is determined that the network connectivity test fails, the fault diagnosis result is used to determine a network connectivity fault.

7. The method according to claim 6, characterized in that Performing a network connectivity test on the multiple network addresses includes: Selecting a first network address and a second network address from the multiple network addresses, and sending an echo request message to the second network address through the first network address; In a case where it is determined that the second network address has received the echo request message, sending an echo reply message to the first network address through the second network address; In a case where it is determined that the first network address has received the echo response message, determining that the first network address and the second network address are connected; The multiple network addresses are traversed, and when it is determined that any two network addresses are connected, it is determined that the network connectivity test has passed.

8. A fault diagnosis device for a cloud physical machine, characterized in that: The device comprises: An acquisition module is used to acquire inspection results obtained by inspecting cloud physical machine nodes, wherein the inspection results are used to indicate a faulty cloud physical machine node and the operation stage of the faulty cloud physical machine node when the fault occurs; a diagnosis module is used to perform fault diagnosis on the faulty cloud physical machine node according to the inspection results to obtain a fault diagnosis result; The sending module is used to send the fault diagnosis result to the target object.

9. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, wherein the computer program implements the steps of the method described in any one of claims 1 to 7 when executed by a processor.

10. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that: When the processor executes the computer program, the steps of the method described in any one of claims 1 to 7 are implemented.

Images