A device fault processing method and apparatus

Abstract

The application relates to the technical field of network communication, in particular to a device fault processing method and device. The method is applied to a first network device, and the method comprises the following steps: receiving a first extended LLDP packet sent by a second network device, wherein the second network device is a neighbor network device of the first network device; determining a reason for disconnection of the second network device from a cloud platform after determining that the second network device is disconnected from the cloud platform, carrying the reason in a self-defined field of the first extended LLDP packet, and sending the first extended LLDP packet to the first network device; and reporting the reason for disconnection of the second network device from the cloud platform to the cloud platform, so that the cloud platform performs fault processing on the second network device based on the reason for disconnection of the second network device from the cloud platform.

Description

Technical Field

[0001] This application relates to the field of network communication technology, and in particular to a method and apparatus for handling equipment faults. Background Technology

[0002] Many manufacturers have launched their own cloud platforms that support the management of various devices and terminals, such as switches, ACs, APs, and other smart terminals that need to be managed. Users can directly log in to the cloud control platform to configure, manage, and monitor all their devices in real time. Cloud management is convenient and fast, and is the main solution promoted by various manufacturers.

[0003] In a typical hierarchical network structure, all network devices connect to the internet through a management VLAN and establish a connection with the cloud management platform. The cloud platform configures and manages any network device through agreed protocols or interfaces.

[0004] In this networking configuration, the stability of the connection between the lower-layer network devices and the cloud management platform depends on the network status of the upper-layer network devices. If the configuration or network status of the upper-layer or even higher-layer network devices is faulty, all lower-layer devices will be affected and unable to maintain a connection with the cloud management platform.

[0005] When the management network is down, administrators may be unable to log in to the access switch to operate and troubleshoot, and may need to go to the equipment room or the site to further locate and resolve the problem. Therefore, how to quickly locate and resolve network faults in the cloud has become an urgent problem to be solved. Summary of the Invention

[0006] This application provides a method and apparatus for handling equipment failures.

[0007] In a first aspect, this application provides a device fault handling method, applied to a first network device, the method comprising:

[0008] The system receives a first extended LLDP message sent by a second network device, wherein the second network device is a neighboring network device of the first network device. After determining that the connection with the cloud platform is lost, the second network device determines the reason for the loss of connection with the cloud platform and sends it to the first network device in a custom field of the first extended LLDP message.

[0009] The reason for the second network device's disconnection from the cloud platform is reported to the cloud platform, so that the cloud platform can handle the fault of the second network device based on the reason for the disconnection.

[0010] Optionally, the method further includes:

[0011] Parse the first extended LLDP message to find out the reason why the second network device disconnected from the cloud platform.

[0012] Optionally, the method further includes:

[0013] Receive the device information acquisition instruction for the second network device sent by the cloud platform;

[0014] The device information acquisition instruction is carried in a custom field of the second extended LLDP message and sent to the second network device;

[0015] The second network device receives a third extended LLDP message sent by the second network device, wherein the custom field of the third extended LLDP message carries device information obtained by the second network device based on the device information acquisition instruction;

[0016] The device information is reported to the cloud platform.

[0017] Optionally, the device information includes the first configuration information of the second network device; the method further includes:

[0018] The administrator receives second configuration information sent by the cloud platform, wherein when the administrator determines that the first configuration information causes the second network device to disconnect from the cloud platform, the administrator sends the latest second configuration information to the second network device based on the cloud platform.

[0019] The second configuration information is carried in a custom field of the fourth LLDP message and sent to the second network device.

[0020] Secondly, this application provides a device fault handling method applied to a cloud platform, the method comprising:

[0021] The system receives a report from the first network device explaining why the second network device has disconnected from the cloud platform. The second network device and the first network device are neighboring network devices. After determining that the connection with the cloud platform has been lost, the second network device determines the reason for the disconnection and sends it to the first network device in a custom field of the first extended LLDP message.

[0022] The fault handling of the second network device is carried out based on the reason why the second network device is disconnected from the cloud platform.

[0023] Optionally, the method further includes:

[0024] Send a device information acquisition instruction for the second network device to the first network device, so that the first network device carries the device information acquisition instruction in a custom field of a second extended LLDP message and sends it to the second network device, and the second network device carries the device information acquired based on the device information acquisition instruction in a custom field of a third extended LLDP message and sends it to the first network device.

[0025] Receive the device information reported by the first network device and display it to the administrator.

[0026] Optionally, the method further includes:

[0027] Obtain second configuration information, wherein the administrator configures the second configuration information when it is determined that the first configuration information causes the second network device to disconnect from the cloud platform;

[0028] The second configuration information is sent to the first network device, so that the first network device carries the second configuration information in a custom field of the fourth LLDP message and sends it to the second network device.

[0029] Thirdly, this application provides a device fault handling apparatus, applied to a first network device, the apparatus comprising:

[0030] The receiving unit is configured to receive a first extended LLDP message sent by a second network device, wherein the second network device is a neighboring network device of the first network device, and after determining that the connection with the cloud platform is lost, the second network device determines the reason for the loss of connection with the cloud platform and sends it to the first network device in a custom field of the first extended LLDP message.

[0031] The reporting unit is used to report the reason for the disconnection between the second network device and the cloud platform to the cloud platform, so that the cloud platform can perform fault handling on the second network device based on the reason for the disconnection.

[0032] Optionally, the device further includes:

[0033] The parsing unit is used to parse the first extended LLDP message to obtain the reason why the second network device disconnected from the cloud platform.

[0034] Optionally, the device further includes:

[0035] The receiving unit is further configured to receive a device information acquisition instruction for the second network device sent by the cloud platform;

[0036] The sending unit is used to carry the device information acquisition instruction in a custom field of the second extended LLDP message and send it to the second network device;

[0037] The receiving unit is further configured to receive a third extended LLDP message sent by the second network device, wherein the custom field of the third extended LLDP message carries device information obtained by the second network device based on the device information acquisition instruction;

[0038] The reporting unit is also used to report the device information to the cloud platform.

[0039] Optionally, the device information includes the first configuration information of the second network device; the apparatus further includes:

[0040] The receiving unit is further configured to receive second configuration information sent by the cloud platform, wherein when the administrator determines that the first configuration information causes the second network device to disconnect from the cloud platform, the administrator sends the latest second configuration information to the second network device based on the cloud platform.

[0041] The sending unit is further configured to carry the second configuration information in a custom field of the fourth LLDP message and send it to the second network device.

[0042] Fourthly, this application provides a device for handling equipment failures, applied to a cloud platform, the device comprising:

[0043] The receiving unit is used to receive the reason reported by the first network device for the second network device disconnecting from the cloud platform, wherein the second network device and the first network device are neighboring network devices. After determining that the connection with the cloud platform is disconnected, the second network device determines the reason for the disconnection and sends it to the first network device in a custom field of the first extended LLDP message.

[0044] The processing unit is used to perform fault handling on the second network device based on the reason why the second network device is disconnected from the cloud platform.

[0045] Optionally, the device further includes:

[0046] The sending unit is configured to send a device information acquisition instruction of the second network device to the first network device, so that the first network device carries the device information acquisition instruction in a custom field of a second extended LLDP message and sends it to the second network device, and the second network device carries the device information acquired based on the device information acquisition instruction in a custom field of a third extended LLDP message and sends it to the first network device.

[0047] The receiving unit is further configured to receive the device information reported by the first network device and display it to the administrator.

[0048] Optionally, the device further includes:

[0049] An acquisition unit is used to acquire second configuration information, wherein the administrator configures the second configuration information when it is determined that the first configuration information causes the second network device to disconnect from the cloud platform;

[0050] The sending unit is further configured to send the second configuration information to the first network device, so that the first network device carries the second configuration information in a custom field of the fourth LLDP message and sends it to the second network device.

[0051] Fifthly, embodiments of this application provide a device for handling equipment malfunctions, the device comprising:

[0052] Memory, used to store program instructions;

[0053] A processor is configured to invoke program instructions stored in the memory and execute the steps of the method as described in any one of the first or second aspects above, according to the obtained program instructions.

[0054] In a sixth aspect, embodiments of this application also provide a computer-readable storage medium storing computer-executable instructions for causing the computer to perform the steps of the method as described in any one of the first or second aspects above.

[0055] In summary, the device fault handling method provided in this application embodiment is applied to a first network device. The method includes: receiving a first extended LLDP message sent by a second network device, wherein the second network device is a neighboring network device of the first network device; after determining that the connection with the cloud platform is lost, the second network device determines the reason for the loss of connection with the cloud platform and carries it in a custom field of the first extended LLDP message, and sends it to the first network device; and reporting the reason for the loss of connection between the second network device and the cloud platform to the cloud platform, so that the cloud platform can perform fault handling on the second network device based on the reason for the loss of connection between the second network device and the cloud platform.

[0056] Using the device fault handling method provided in this application embodiment, the offline device sends the preliminary reason for the device's offline status detected by the device to other online neighboring network devices by extending the custom field of the LLDP message. The other online neighboring network devices report the reason for the device's offline status to the cloud platform, so as to achieve the effect of quickly locating the fault. Attached Figure Description

[0057] To more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the drawings used in the description of the embodiments of this application or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments recorded in this application. For those skilled in the art, other drawings can be obtained based on these drawings of the embodiments of this application.

[0058] Figure 1 A detailed flowchart of a device fault handling method provided in this application embodiment;

[0059] Figure 2 A schematic diagram of a network architecture provided in an embodiment of this application;

[0060] Figure 3 This is a schematic diagram of a cloud platform information display provided in an embodiment of this application;

[0061] Figure 4 This is another schematic diagram of cloud platform information display provided in an embodiment of this application;

[0062] Figure 5 This is another schematic diagram of cloud platform information display provided in an embodiment of this application;

[0063] Figure 6 A detailed flowchart of another device fault handling method provided in this application embodiment;

[0064] Figure 7 This is a schematic diagram of the structure of a device for handling equipment failures provided in an embodiment of this application;

[0065] Figure 8 This is a schematic diagram of another device fault handling apparatus provided in an embodiment of this application;

[0066] Figure 9 A schematic diagram of the hardware architecture of a device fault handling apparatus provided in an embodiment of this application;

[0067] Figure 10 A schematic diagram of the hardware architecture of another device fault handling device provided in an embodiment of this application. Detailed Implementation

[0068] The terminology used in the embodiments of this application is for the purpose of describing particular embodiments only and is not intended to limit the application. The singular forms “a,” “the,” and “the” as used in this application and claims are also intended to include the plural forms unless the context clearly indicates otherwise. It should also be understood that the term “and / or” as used herein refers to any and all possible combinations comprising one or more of the associated listed items.

[0069] It should be understood that although the terms first, second, third, etc., may be used to describe various information in embodiments of this application, such information should not be limited to these terms. These terms are only used to distinguish information of the same type from one another. For example, without departing from the scope of this application, first information may also be referred to as second information, and similarly, second information may also be referred to as first information. Depending on the context, the word "if" may also be interpreted as "when," "when," or "in response to a determination."

[0070] For example, see Figure 1 The diagram shown is a detailed flowchart of a device fault handling method provided in an embodiment of this application. The method is applied to a first network device and includes the following steps:

[0071] Step 100: Receive the first extended LLDP message sent by the second network device.

[0072] In this embodiment of the application, the second network device is a neighboring network device of the first network device. After determining that the connection with the cloud platform is broken, the second network device determines the reason for the disconnection and sends it to the first network device in a custom field of the first extended LLDP (Link Layer Discovery Protocol) message.

[0073] For example, see Figure 2 The diagram shown is a network architecture diagram provided in an embodiment of this application. Access switch A and aggregation switch A are neighboring network devices. If a network failure occurs between aggregation switch A and access switch A, access switch A and its lower-level network devices will be unable to connect to the cloud management platform.

[0074] So, after access switch A determines that the connection with the operation and management platform has been lost, it will establish a connection with the cloud management platform based on a preset mechanism (protocol). During the connection establishment process, it will determine at which step the connection establishment failed, thereby determining the reason for the failure.

[0075] For example, regarding a specific device, the reasons for disconnection are shown in Table 1, and include the following:

[0076]

[0077]

[0078]

[0079] Table 1

[0080] In practical applications, the management link between access switch A and the operation and management platform is a Layer 3 link. If the physical link between access switch A and aggregation switch A is normal and the connection port status is UP, then the Layer 2 link between access switch A and aggregation switch A is normal. At this time, access switch A can encapsulate the determined reason for disconnection from the cloud management platform (e.g., DNS resolution failure) into a custom field (custom TLV field) of the extended LLDP message and send the extended LLDP message to aggregation switch A through the Layer 2 link.

[0081] For example, in this embodiment of the application, the custom TLV field format is defined as shown in Table 2:

[0082]

[0083] Table 2

[0084] TLVs are the units that make up LLDPDUs, and each TLV represents a piece of information. In this application embodiment, a preferred implementation is to use organization-defined TLVs (127).

[0085] In this embodiment of the application, after receiving a first extended LLDP message sent by a second network device, which carries the reason for the disconnection from the cloud management platform, the first network device parses the first extended LLDP message to obtain the reason for the disconnection between the second network device and the cloud platform.

[0086] Step 110: Report the reason why the second network device disconnected from the cloud platform to the cloud platform, so that the cloud platform can handle the fault of the second network device based on the reason why the second network device disconnected from the cloud platform.

[0087] For example, core switch A receives an LLDP message sent by access switch A, parses out custom information (the reason for disconnection from the cloud management platform), and reports it to the cloud management platform.

[0088] On the cloud management platform side, it can display the event / reason reported by the first network device that the second network device has lost connection with the cloud management platform. For an example, see [link to example]. Figure 3The diagram shown is a schematic representation of cloud platform information display provided in an embodiment of this application, including at least the following information: offline device (access switch A), and reporting device (core switch / aggregation switch). That is, on the cloud management platform's display page, the reason for the offline status of the device can be seen, as well as from which device and which physical port the information was obtained.

[0089] Furthermore, in this embodiment of the application, the device information acquisition instruction of the second network device sent by the cloud platform is received; the device information acquisition instruction is carried in a custom field of the second extended LLDP message and sent to the second network device.

[0090] Still with Figure 3 As shown, the display page can also include user-operable instruction / command input boxes, which default to obtaining the reason for the cloud platform disconnection, and can also include a clickable button for "Send to reporting device". Users can use this function to send operation instructions to the second network device to obtain further information.

[0091] At this point, users can obtain further information from the cloud management platform. One method is to directly use predefined operation commands; for example, see [link to relevant documentation]. Figure 4 As shown.

[0092] Alternatively, you can directly use a custom method to issue commands to retrieve information. For an example, see [link to relevant documentation]. Figure 5 As shown.

[0093] After receiving the operation command sent by the cloud management platform, the first network device will carry the received operation command in an LLDP extended message and transmit it to the second network device. The second network device will parse the extended LLDP message to obtain the operation command and then execute the operation command.

[0094] Next, the first network device receives a third extended LLDP message sent by the second network device. The custom field of the third extended LLDP message carries device information obtained by the second network device based on the device information acquisition instruction.

[0095] Finally, the first network device parses the third extended LLDP message to obtain device information and reports the device information to the cloud platform.

[0096] Furthermore, if the device information includes the first configuration information of the second network device, the method further includes: receiving the second configuration information sent by the cloud platform, wherein when the administrator determines that the first configuration information causes the second network device to disconnect from the cloud platform, the administrator sends the latest second configuration information to the second network device based on the cloud platform; and carries the second configuration information in a custom field of a fourth LLDP message and sends it to the second network device.

[0097] For example, if the operation command is to obtain network configuration information, the second network device will carry its local network configuration information in an extended LLDP and send it to the first network device.

[0098] In practical applications, after collecting sufficient information, administrators can pinpoint the cause of the problem. At this point, they can directly issue configurations to restore the network. In this way, even when unable to log in to the faulty device, the problem can be solved quickly and remotely.

[0099] The cloud management platform sends the updated and correct configuration information to the first network device. The first network device then sends the received correct configuration information from the cloud management platform in an extended LLDP message to the second network device. The second network device parses the correct configuration information, performs configuration updates / replacements, and finally establishes a connection with the cloud management platform, successfully connecting to the cloud management platform.

[0100] For example, see Figure 6 The diagram shown is a detailed flowchart of a device fault handling method provided in an embodiment of this application. This method is applied to a cloud platform and includes the following steps:

[0101] Step 600: Receive the reason reported by the first network device that the second network device has lost connection with the cloud platform.

[0102] In this context, the second network device and the first network device are neighboring network devices. After determining that the connection with the cloud platform is broken, the second network device determines the reason for the break and sends it to the first network device in a custom field of the first extended LLDP message.

[0103] Step 610: Perform fault handling on the second network device based on the reason why the second network device disconnected from the cloud platform.

[0104] In this embodiment of the application, the above method may further include the following steps:

[0105] Specifically, the system sends a device information acquisition instruction for the second network device to the first network device, so that the first network device carries the device information acquisition instruction in a custom field of a second extended LLDP message and sends it to the second network device. The second network device then carries the device information acquired based on the device information acquisition instruction in a custom field of a third extended LLDP message and sends it to the first network device. The system also receives the device information reported by the first network device and displays it to the administrator.

[0106] Further, the administrator obtains second configuration information, wherein when the administrator determines that the first configuration information causes the second network device to disconnect from the cloud platform, the administrator configures the second configuration information; and sends the second configuration information to the first network device, so that the first network device carries the second configuration information in a custom field of the fourth LLDP message and sends it to the second network device.

[0107] Based on the same inventive concept as the above-described embodiments, see, for example, the following: Figure 7 The diagram shown is a structural schematic of a device fault handling apparatus provided in an embodiment of this application. This apparatus is applied to a first network device and includes:

[0108] The receiving unit 70 is used to receive a first extended LLDP message sent by a second network device, wherein the second network device is a neighboring network device of the first network device, and after determining that the connection with the cloud platform is broken, the second network device determines the reason for the disconnection from the cloud platform and sends it to the first network device in a custom field of the first extended LLDP message.

[0109] The reporting unit 71 is used to report the reason for the disconnection between the second network device and the cloud platform to the cloud platform, so that the cloud platform can perform fault handling on the second network device based on the reason for the disconnection between the second network device and the cloud platform.

[0110] Optionally, the device further includes:

[0111] The parsing unit is used to parse the first extended LLDP message to obtain the reason why the second network device disconnected from the cloud platform.

[0112] Optionally, the device further includes:

[0113] The receiving unit 70 is further configured to receive a device information acquisition instruction for the second network device sent by the cloud platform;

[0114] The sending unit is used to carry the device information acquisition instruction in a custom field of the second extended LLDP message and send it to the second network device;

[0115] The receiving unit 70 is further configured to receive a third extended LLDP message sent by the second network device, wherein the custom field of the third extended LLDP message carries device information obtained by the second network device based on the device information acquisition instruction;

[0116] The reporting unit 71 is also used to report the device information to the cloud platform.

[0117] Optionally, the device information includes the first configuration information of the second network device; the apparatus further includes:

[0118] The receiving unit 70 is further configured to receive second configuration information sent by the cloud platform, wherein when the administrator determines that the first configuration information causes the second network device to disconnect from the cloud platform, the administrator sends the latest second configuration information to the second network device based on the cloud platform.

[0119] The sending unit is further configured to carry the second configuration information in a custom field of the fourth LLDP message and send it to the second network device.

[0120] For example, see Figure 8 The diagram shown is a structural schematic of a device for handling equipment failures according to an embodiment of this application. This device is applied to a cloud platform and includes:

[0121] The receiving unit 80 is used to receive the reason reported by the first network device for the second network device disconnecting from the cloud platform. The second network device and the first network device are neighboring network devices. After determining that the connection with the cloud platform is disconnected, the second network device determines the reason for the disconnection and sends it to the first network device in a custom field of the first extended LLDP message.

[0122] Processing unit 81 is used to perform fault handling on the second network device based on the reason why the second network device is disconnected from the cloud platform.

[0123] Optionally, the device further includes:

[0124] The sending unit is configured to send a device information acquisition instruction of the second network device to the first network device, so that the first network device carries the device information acquisition instruction in a custom field of a second extended LLDP message and sends it to the second network device, and the second network device carries the device information acquired based on the device information acquisition instruction in a custom field of a third extended LLDP message and sends it to the first network device.

[0125] The receiving unit 80 is further configured to receive the device information reported by the first network device and display it to the administrator.

[0126] Optionally, the device further includes:

[0127] An acquisition unit is used to acquire second configuration information, wherein the administrator configures the second configuration information when it is determined that the first configuration information causes the second network device to disconnect from the cloud platform;

[0128] The sending unit is further configured to send the second configuration information to the first network device, so that the first network device carries the second configuration information in a custom field of the fourth LLDP message and sends it to the second network device.

[0129] These units can be one or more integrated circuits configured to implement the above methods, such as one or more Application Specific Integrated Circuits (ASICs), one or more digital signal processors (DSPs), or one or more Field Programmable Gate Arrays (FPGAs). Alternatively, when one of these units is implemented using processing element scheduler code, the processing element can be a general-purpose processor, such as a Central Processing Unit (CPU) or other processor capable of calling program code. Furthermore, these units can be integrated together to form a system-on-a-chip (SOC).

[0130] Furthermore, regarding the equipment fault handling device provided in this application embodiment, from a hardware perspective, the hardware architecture schematic diagram of the equipment fault handling device can be found in [reference needed]. Figure 9 As shown, the device fault handling apparatus may include: a memory 90 and a processor 91.

[0131] The memory 91 is used to store program instructions; the processor 90 calls the program instructions stored in the memory 91 and executes the method embodiment applied to the first network device according to the obtained program instructions. The specific implementation and technical effects are similar, and will not be described again here.

[0132] Optionally, this application also provides a network device, including at least one processing element (or chip) for performing the method embodiments described above applied to the first network device.

[0133] Optionally, this application also provides a program product, such as a computer-readable storage medium storing computer-executable instructions for causing the computer to perform the above-described method embodiment applied to the first network device.

[0134] Furthermore, regarding the equipment fault handling device provided in this application embodiment, from a hardware perspective, the hardware architecture schematic diagram of the equipment fault handling device can be found in [reference needed]. Figure 10 As shown, the device fault handling apparatus may include: a memory 100 and a processor 101.

[0135] The memory 101 is used to store program instructions; the processor 100 calls the program instructions stored in the memory 101 and executes the above-described method embodiment applied to the cloud platform according to the obtained program instructions. The specific implementation method and technical effect are similar, and will not be described again here.

[0136] Optionally, this application also provides a cloud platform, including at least one processing element (or chip) for performing the above-described method embodiments applied to the cloud platform.

[0137] Optionally, this application also provides a program product, such as a computer-readable storage medium storing computer-executable instructions for causing the computer to perform the above-described method embodiments applied to a cloud platform.

[0138] Here, a machine-readable storage medium can be any electronic, magnetic, optical, or other physical storage device that can contain or store information, such as executable instructions, data, etc. For example, a machine-readable storage medium can be: RAM (Random Access Memory), volatile memory, non-volatile memory, flash memory, storage drives (such as hard disk drives), solid-state drives, any type of storage disk (such as optical discs, DVDs, etc.), or similar storage media, or combinations thereof.

[0139] The systems, devices, modules, or units described in the above embodiments can be implemented by computer chips or entities, or by products with certain functions. A typical implementation device is a computer, which can take the form of a personal computer, laptop computer, cellular phone, camera phone, smartphone, personal digital assistant, media player, navigation device, email sending and receiving device, game console, tablet computer, wearable device, or any combination of these devices.

[0140] For ease of description, the above devices are described separately by function as various units. Of course, in implementing this application, the functions of each unit can be implemented in one or more software and / or hardware.

[0141] Those skilled in the art will understand that embodiments of this application can be provided as methods, systems, or computer program products. Therefore, this application can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, embodiments of this application can take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0142] This application is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this application. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart... Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0143] Furthermore, these computer program instructions can also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to operate in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in the process. Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0144] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0145] The above description is merely a preferred embodiment of this application and is not intended to limit this application. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the scope of protection of this application.

Claims

1. A method for handling equipment malfunctions, characterized in that, Applied to a first network device, the method includes: The system receives a first extended LLDP message sent by a second network device, wherein the second network device is a neighboring network device of the first network device. After determining that the connection with the cloud platform is lost, the second network device determines the reason for the loss of connection with the cloud platform and sends it to the first network device in a custom field of the first extended LLDP message. The reason for the second network device disconnecting from the cloud platform is reported to the cloud platform so that the cloud platform can handle the fault of the second network device based on the reason for the disconnection. Parse the first extended LLDP message to determine the reason why the second network device disconnected from the cloud platform; Receive the device information acquisition instruction for the second network device sent by the cloud platform; The device information acquisition instruction is carried in a custom field of the second extended LLDP message and sent to the second network device; The second network device receives a third extended LLDP message sent by the second network device, wherein the custom field of the third extended LLDP message carries device information obtained by the second network device based on the device information acquisition instruction; The device information is reported to the cloud platform; The device information includes the first configuration information of the second network device; the method further includes: The administrator receives second configuration information sent by the cloud platform, wherein when the administrator determines that the first configuration information causes the second network device to disconnect from the cloud platform, the administrator sends the latest second configuration information to the second network device based on the cloud platform. The second configuration information is carried in a custom field of the fourth LLDP message and sent to the second network device.

2. A method for handling equipment malfunctions, characterized in that, Applied to a cloud platform, the method includes: The system receives a report from the first network device explaining why the second network device has disconnected from the cloud platform. The second network device and the first network device are neighboring network devices. After determining that the connection with the cloud platform has been lost, the second network device determines the reason for the disconnection and sends it to the first network device in a custom field of the first extended LLDP message. Based on the reason why the second network device disconnected from the cloud platform, the fault handling of the second network device was carried out; Send a device information acquisition instruction for the second network device to the first network device, so that the first network device carries the device information acquisition instruction in a custom field of a second extended LLDP message and sends it to the second network device, and the second network device carries the device information acquired based on the device information acquisition instruction in a custom field of a third extended LLDP message and sends it to the first network device. Receive the device information reported by the first network device and display it to the administrator; Obtain second configuration information, wherein the administrator configures the second configuration information when it is determined that the first configuration information causes the second network device to disconnect from the cloud platform; The second configuration information is sent to the first network device, so that the first network device carries the second configuration information in a custom field of the fourth LLDP message and sends it to the second network device.

3. A device for handling equipment malfunctions, characterized in that, Applied to a first network device, the device includes: The receiving unit is configured to receive a first extended LLDP message sent by a second network device, wherein the second network device is a neighboring network device of the first network device, and after determining that the connection with the cloud platform is lost, the second network device determines the reason for the loss of connection with the cloud platform and sends it to the first network device in a custom field of the first extended LLDP message. The reporting unit is used to report the reason why the second network device is disconnected from the cloud platform to the cloud platform, so that the cloud platform can perform fault handling on the second network device based on the reason why the second network device is disconnected from the cloud platform; The parsing unit is used to parse the first extended LLDP message to obtain the reason why the second network device disconnected from the cloud platform. The receiving unit is further configured to receive a device information acquisition instruction for the second network device sent by the cloud platform; The sending unit is used to carry the device information acquisition instruction in a custom field of the second extended LLDP message and send it to the second network device; The receiving unit is further configured to receive a third extended LLDP message sent by the second network device, wherein the custom field of the third extended LLDP message carries device information obtained by the second network device based on the device information acquisition instruction; The reporting unit is also used to report the device information to the cloud platform; The device information includes the first configuration information of the second network device; The receiving unit is further configured to receive second configuration information sent by the cloud platform, wherein when the administrator determines that the first configuration information causes the second network device to disconnect from the cloud platform, the administrator sends the latest second configuration information to the second network device based on the cloud platform. The sending unit is further configured to carry the second configuration information in a custom field of the fourth LLDP message and send it to the second network device.

4. A device for handling equipment malfunctions, characterized in that, The device, applied to a cloud platform, includes: The receiving unit is used to receive the reason reported by the first network device for the second network device disconnecting from the cloud platform, wherein the second network device and the first network device are neighboring network devices. After determining that the connection with the cloud platform is disconnected, the second network device determines the reason for the disconnection and sends it to the first network device in a custom field of the first extended LLDP message. The processing unit is used to perform fault handling on the second network device based on the reason why the second network device is disconnected from the cloud platform; The sending unit is configured to send a device information acquisition instruction of the second network device to the first network device, so that the first network device carries the device information acquisition instruction in a custom field of a second extended LLDP message and sends it to the second network device, and the second network device carries the device information acquired based on the device information acquisition instruction in a custom field of a third extended LLDP message and sends it to the first network device. The receiving unit is further configured to receive the device information reported by the first network device and display it to the administrator; The acquisition unit is used to acquire second configuration information, wherein the administrator configures the second configuration information when it is determined that the first configuration information causes the second network device to disconnect from the cloud platform; The sending unit is further configured to send the second configuration information to the first network device, so that the first network device carries the second configuration information in a custom field of the fourth LLDP message and sends it to the second network device.

5. A device for handling equipment malfunctions, characterized in that, The equipment fault handling device includes: Memory, used to store program instructions; A processor is configured to invoke program instructions stored in the memory and execute the steps of the method as described in any one of claims 1 or 2 according to the obtained program instructions.

6. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer-executable instructions for causing the computer to perform the steps of the method as described in any one of claims 1 or 2.

Images