Device exception handling method, network equipment, communication system, medium and product

Abstract

The embodiments of the present invention provide a device exception handling method, a communication system, a network device, a medium and a product. The method is applied to a first network device that performs network communication. Under normal circumstances, data packets can be transmitted between the gateway in the first network device and the second network device. When an abnormality occurs in the gateway in the first network device, the method provides a new way to suspend the transmission of data packets between network devices: the first network device is newly equipped with a monitoring function for the running status of the gateway. With the help of this function, if the first network device monitors that an abnormality occurs in its own gateway, it can use the physical network card corresponding to the first network device to actively send an abnormal notification message, so that the second network device can actively suspend the transmission of data packets with the abnormal gateway. At this time, the data packet can continue to be transmitted in the second network device and other network devices, which is to improve the impact of the gateway abnormality on the packet transmission.

Description

Technical Field

[0001] The present invention relates to the field of network communication technology, and in particular to a device exception processing method, network equipment, communication system, medium and product. Background Art

[0002] With the development of network devices, the functions of network devices are becoming more and more abundant. For example, network devices can be integrated with gateways at the same time, so that the network devices can process and forward data messages during network communication.

[0003] In practice, when a gateway in a network device is abnormal, the gateway is obviously unable to process data messages normally. In this case, continuing to send messages to the abnormal gateway will obviously affect the normal processing and transmission of data messages.

[0004] Based on the above description, how to improve the impact of gateway anomalies on data message transmission becomes an urgent problem to be solved. Summary of the invention

[0005] In view of this, an embodiment of the present invention provides a device exception handling method, network device, communication system, medium and product, which are used to prevent data packets from passing through the abnormal gateway when an abnormality occurs in the gateway of the network device, thereby improving the impact of the gateway abnormality on the message transmission.

[0006] In a first aspect, an embodiment of the present invention provides a device exception handling method, which is applied to a first network device, and the method includes:

[0007] Monitoring the running status of the gateway in the first network device;

[0008] If it is monitored that an abnormality occurs in the gateway of the first network device, an abnormality notification message is generated;

[0009] The abnormal notification message is sent to the second network device by using the physical network card corresponding to the first network device, so that the second network device suspends data message transmission with the gateway in the first network device.

[0010] In a second aspect, an embodiment of the present invention provides a device exception handling method, which is applied to a second network device, and the method includes:

[0011] Receive notification message;

[0012] Determine, according to the payload in the notification message, whether the notification message is an abnormal notification message, wherein the abnormal notification message reflects that an abnormality occurs in the gateway in the first network device;

[0013] If the notification message is the abnormal notification message, the target routing information is managed to suspend data message transmission with the gateway in the first network device, and the target routing information is used for data message transmission between the second network device and the gateway in the first network device.

[0014] In a third aspect, an embodiment of the present invention provides a network device, including: a monitoring program and a gateway;

[0015] The monitoring program is used to monitor the running status of the gateway in the network device; if an abnormality occurs in the gateway in the network device, an abnormality notification message is generated;

[0016] The network device is used to send the abnormal notification message by using the physical network card corresponding to the network device, so that the receiving device of the abnormal notification message suspends data message transmission with the gateway in the network device.

[0017] In a fourth aspect, an embodiment of the present invention provides a network device, including: the network device and a target device in a communication system perform data message transmission;

[0018] The network device includes: a port and a processing component;

[0019] The processing component is used to receive the notification message using the port;

[0020] Determine, according to the payload in the notification message, whether the notification message is an abnormal notification message, wherein the abnormal notification message reflects that an abnormality occurs in the gateway of the target device;

[0021] If the notification message is the abnormal notification message, the target routing information is managed to suspend data message transmission with the gateway in the first network device, and the target routing information is used for data message transmission between the second network device and the gateway in the first network device.

[0022] In a fifth aspect, an embodiment of the present invention provides a network device, comprising a processor and a memory, wherein the memory is used to store one or more computer instructions, wherein the one or more computer instructions, when executed by the processor, implement the device exception handling method in the first aspect or the second aspect. The electronic device may also include a communication interface for communicating with other devices or communication systems.

[0023] In a sixth aspect, an embodiment of the present invention provides a communication system, including: a first network device and a second network device for transmitting data packets, wherein the first network device includes a gateway;

[0024] The first network device is used to monitor the running status of the gateway in the first network device; if an abnormality occurs in the gateway, an abnormality notification message is generated; and the abnormality notification message is sent using the physical network card corresponding to the first network device;

[0025] The second network device is used to manage the target routing information in response to the reception of the abnormal notification message to suspend the data message transmission with the gateway in the first network device, and the target routing information is used for the second network device to transmit data messages with the gateway in the first network device.

[0026] In the seventh aspect, an embodiment of the present invention provides a non-temporary machine-readable storage medium, on which executable code is stored. When the executable code is executed by a processor of an electronic device, the processor can at least implement the device exception handling method described in the first aspect or the second aspect.

[0027] In an eighth aspect, an embodiment of the present invention provides a computer program product, which includes a computer program or instructions. When the computer program or instructions are executed by a processor, the processor is enabled to implement the device exception handling method as described in the first or second aspect above.

[0028] Under normal circumstances, data packets can be transmitted between the gateway in the first network device and the second network device. The device exception handling method provided in the embodiment of the present invention can be applied to the first network device, and the first network device is newly provided with a monitoring function of the gateway operation status. When the first network device monitors that an abnormality has occurred in its own gateway, it can actively generate an abnormal notification message, and send the abnormal notification message with the help of a physical network card, so that the second network device responds to the reception of the abnormal notification message and actively suspends data packet transmission with the abnormal gateway in the first network device. At this time, the data packet can continue to be transmitted in the second network device and other network devices, which can improve the data packet transmission delay caused by the abnormality of the gateway in the first network device, or even packet loss, that is, it can reduce the impact of the gateway abnormality on the message transmission.

[0029] It can be seen that when an abnormality occurs in the gateway in the first network device, compared with the first network device actively suspending the data packet transmission between the first network device and the second network device, the above method provides a new way to suspend the data packet transmission: the first network device actively reports the abnormality of its own gateway to the second network device, so that the second network device actively suspends the data packet transmission between the first network device. BRIEF DESCRIPTION OF THE DRAWINGS

[0030] In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the following briefly introduces the drawings required for use in the embodiments or the description of the prior art. Obviously, the drawings described below are some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.

[0031] Figure 1 A schematic diagram of the structure of a communication system provided by an embodiment of the present invention;

[0032] Figure 2 A schematic diagram of a network device structure provided by an embodiment of the present invention;

[0033] Figure 3 A schematic diagram of the structure of another network device provided by an embodiment of the present invention;

[0034] Figure 4 A schematic diagram of the structure of another communication system provided by an embodiment of the present invention;

[0035] Figure 5 A schematic diagram of the structure of another communication system provided by an embodiment of the present invention;

[0036] Figure 6 A schematic diagram of a notification message data structure provided by an embodiment of the present invention;

[0037] Figure 7 A flowchart of a device exception handling method provided by an embodiment of the present invention;

[0038] Figure 8 A flowchart of another device exception handling method provided by an embodiment of the present invention;

[0039] Fig. 9 A schematic diagram of the structure of a device abnormality handling apparatus provided by an embodiment of the present invention;

[0040] Fig.10 A schematic diagram of the structure of a device abnormality handling apparatus provided by an embodiment of the present invention;

[0041] Fig.11 A schematic diagram of the structure of another network device provided in an embodiment of the present invention. DETAILED DESCRIPTION

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

[0043] The terms used in the embodiments of the present invention are only for the purpose of describing specific embodiments, and are not intended to limit the present invention. The singular forms "a", "said" and "the" used in the embodiments of the present invention and the appended claims are also intended to include plural forms, unless the context clearly indicates other meanings, and "multiple" generally includes at least two, but does not exclude the inclusion of at least one.

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

[0045] As used herein, the words "if" and "if" may be interpreted as "at the time of" or "when" or "in response to determining" or "in response to identifying", depending on the context. Similarly, the phrases "if it is determined" or "if (stated condition or event) is identified" may be interpreted as "when determining" or "in response to determining" or "when identifying (stated condition or event)" or "in response to identifying (stated condition or event)", depending on the context.

[0046] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, stored data, displayed data, etc.) involved in the present invention are all information and data authorized by the user or fully authorized by all parties, and the collection, use and processing of relevant data must comply with the relevant laws, regulations and standards of relevant countries and regions, and provide corresponding operation entrances for users to choose to authorize or refuse.

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

[0048] Before describing in detail the contents provided by each embodiment of the present invention, it is also possible to introduce the relevant concepts and backgrounds involved in each embodiment of the present invention.

[0049] When using the services provided by the service provider, users can generate messages, which can be transmitted between different network devices in the communication system to ensure that users can use the application or cloud service normally. Optionally, the service provider can provide services in the form of applications or cloud services. And the messages generated in the process of using the service can be called data messages, which can be expressed in the form of data streams, and the payload in the data messages is specific service data. For example, when the cloud service is a cloud game, the data message includes game data; when the cloud service is a computing service, the data message includes the computing results.

[0050] In practice, as described in the background technology, a network device may be integrated with a gateway. When a gateway in a network device fails, continuing to send data packets to the abnormal gateway will affect the normal processing and transmission of the data packets. In this case, the solutions provided in the following embodiments of the present invention can be used to improve the impact of gateway abnormalities on data packet processing and forwarding.

[0051] Based on the above description, some embodiments of the present invention are described in detail below in conjunction with the accompanying drawings. In the case where there is no conflict between the embodiments, the following embodiments and the features in the embodiments can be combined with each other. In addition, the step sequence in the following method embodiments is only an example and not a strict limitation.

[0052] To facilitate understanding of the solution, the following may first describe from the perspective of the communication system how to avoid affecting the normal processing and transmission of data messages when a gateway in a network device is abnormal.

[0053] Figure 1 FIG. 1 is a schematic diagram of a communication system provided by an embodiment of the present invention. Figure 1 As shown, the system may include: a first network device and a second network device, wherein the first network device includes a gateway.

[0054] Under normal circumstances, the transmission process of data packets between network devices in a communication system can be: the first network device can receive a data packet from a second network device and process the data packet. Among them, the first network device can be integrated with a gateway, so that the gateway completes the processing of the data packet. Furthermore, the first network device can also forward the processing result of the data packet to the second network device, that is, to achieve normal processing and transmission of data packets between network devices. Optionally, the Border Gateway Protocol (BGP) can be used between different network devices for data packet transmission.

[0055] It should be noted that the embodiments of the present invention are described by taking the example of sending the processing result of the data message to the second network device, but the present invention does not limit the recipient of the processing result of the data message, which can be the second network device or other network devices in the communication system.

[0056] Optionally, a gateway, a switch, a server providing services, etc. may be integrated in the first network device, and a switch, a router, etc. may be integrated in the second network device and other network devices.

[0057] At the same time, the first network device mentioned in each embodiment of the present invention also has a new monitoring function for the running status of the gateway. With the help of this monitoring function, the first network device can monitor the running status of its own gateway. When the first network device monitors that an abnormality has occurred in its own gateway, it can generate an abnormal notification message, and send the abnormal notification message to the second network device with the help of the physical network card corresponding to the first network device. After receiving the abnormal notification message, the second network device can actively suspend data message transmission with the abnormal gateway in the first network device.

[0058] Regarding the process of suspending data message transmission with the abnormal gateway in the first network device, in an optional manner, the second network device can actively suspend data message transmission by managing target routing information. Optionally, the management of target routing information can specifically include setting the target routing information to an unavailable state or directly deleting the target recruitment information, wherein the target routing information includes routing information required for data message transmission between the gateway in the first network device and the second network device. Optionally, the target routing information can include five-tuple information of the data message, the next hop address, and the like.

[0059] In addition, the management results of the target routing information can also be synchronized to all devices in the communication network, which means that routing convergence is achieved. The completion of routing convergence will prevent the first network device with an abnormal gateway from receiving new data packets, which means that data packets are removed from the first network device. Among them, routing convergence can be achieved at the second level by sending notification messages and further setting the routing information status, thereby reducing the impact of gateway anomalies on message transmission, and thus reducing the impact of gateway anomalies on user service use.

[0060] In this embodiment, the first network device in the communication system is newly equipped with a monitoring function for the operation status of the gateway. When the first network device monitors that an abnormality has occurred in its own gateway, it can actively generate an abnormality notification message and send the abnormality notification message with the help of a physical network card, so that the second network device responds to the reception of the abnormality notification message and actively suspends data message transmission with the gateway in the first network device. At this time, data messages can still be transmitted in the second network device and other network devices, which can improve the data message transmission delay or even packet loss caused by the abnormality of the gateway in the first network device, that is, it can reduce the impact of the gateway abnormality on message transmission.

[0061] That is to say, when an abnormality occurs in the gateway of the first network device, compared with the first network device actively suspending the message transmission between the first network device and the second network device, the above method provides a new way to suspend the data message transmission between network devices: the first network device actively reports the abnormality of its own gateway to the second network device, so that the second network device actively suspends the data message transmission between the first network device.

[0062] for Figure 1 In the communication system shown, after an abnormality occurs in the gateway of the first network device, the gateway can be restored to normal through operation and maintenance. Similarly, the first network device can also monitor that its own gateway has returned to normal. At this time, the first network device can generate a recovery notification message and send the recovery notification message to the second network device using the physical network card corresponding to the first network device. In response to receiving the recovery notification message, the second network device can resume data message transmission with the gateway in the first network device.

[0063] As for the process of resuming data message transmission with the abnormal gateway in the first network device, an optional method is that the second network device can also achieve it by managing the target routing information. Specifically, in the case where the second network device sets the target routing information to an unavailable state when the gateway is abnormal, the second network device can restore the data message transmission with the gateway in the first network device by setting the target routing information to an available state. Similarly, in the case where the second network device deletes the target routing information when the gateway is abnormal, the second network device can restore the data message transmission with the gateway in the first network device by recreating the target routing information.

[0064] Similarly, when the management result of the target routing information is synchronized to all devices in the communication network, that is, routing convergence is completed, the first network device whose gateway has returned to normal can continue to receive data packets, that is, the data packets are re-injected into the first network device.

[0065] It should be noted that, according to the above description, the exception notification message and the recovery notification message are generated by the first network device based on the monitoring results, and both play the role of notifying the second network device of the operating status of the gateway in the first network device. Therefore, unlike data messages, the messages generated by the first network device based on the monitoring results can also be collectively referred to as notification messages, and depending on the content of the monitoring results, the notification messages may specifically include exception notification messages or recovery notification messages.

[0066] In this embodiment, when the gateway returns to normal, the first network device may also send a recovery notification message so that the second network device actively recovers the data message transmission between the gateway in the first network device and the second network device.

[0067] based on Figure 1 The communication system shown in the figure, the structures and working processes of the first network device and the second network device can be described in detail below. The first network device is first introduced below.

[0068] Figure 2 A schematic diagram of the structure of a network device provided in an embodiment of the present invention. The network device is Figure 1 The first network device in the embodiment shown. Figure 2 As shown, the network device may include a listener and a gateway.

[0069] The monitoring program can monitor the running status of the gateway in the network device (that is, the first network device). If an abnormality occurs in the gateway in the first network device, the monitoring program can generate an abnormality notification message. The first network device can use its corresponding physical network card to send the abnormality notification message so that the receiving device of the abnormality notification message (that is, the second network device) suspends data message transmission with the gateway in the first network device.

[0070] Afterwards, when the monitoring program monitors that the gateway in the first network device has returned to normal, the monitoring program can generate a recovery notification message and send the recovery notification message to the second network device using the physical network card corresponding to the first network device. In response to receiving the recovery notification message, the second network device can resume data message transmission with the gateway in the first network device.

[0071] In this embodiment, the monitoring function of the gateway operation status in the first network device can be implemented by a monitoring program. In addition, the contents not described in detail in this embodiment and the technical effects that can be achieved can be found in Figure 1 The relevant description in the illustrated embodiment will not be repeated here.

[0072] The second network device will be introduced below.

[0073] Figure 3 A schematic diagram of the structure of another network device provided in an embodiment of the present invention. The network device is Figure 1 The second network device in the embodiment shown. Figure 3 As shown, the network device may include ports and processing components.

[0074] The processing component can receive a notification message via the interface. The notification message can be generated by a target device that transmits data messages with the second network device in the communication system. The target device can be, for example, Figure 1 Afterwards, the processing component may also determine whether the received notification message is an abnormal notification message or a recovery notification message according to the payload in the received notification message.

[0075] Specifically, in one case, if the payload carried by the notification message is a first preset value, the notification message is determined to be an abnormal notification message, and the processing component can manage the target routing information used in the data message transmission process with the gateway in the first network device to suspend the data message transmission between itself and the gateway in the first network device. The specific management method can include deleting the target routing information or setting the target routing information to an unavailable state.

[0076] In another case, if the payload carried by the notification message is a second preset value, the notification message is determined to be a recovery notification message, and the processing component can also manage the target routing information to restore data message transmission between itself and the gateway in the first network device. The specific management method can include recreating the target routing information or setting the target routing information to an available state.

[0077] Optionally, optional implementations of the processing component may include a field programmable gate array (FPGA), an application specific integrated circuit (ASIC), and the like.

[0078] In this embodiment, the second network device can receive the notification message via the port and determine the message content according to the message payload. Afterwards, when it is determined that the notification message is specifically an abnormal notification message, the data message transmission between the second network device and the gateway in the first network device can be suspended or resumed by setting the routing information status.

[0079] In addition to notification messages, during the process of message data transmission between the first network device and the second network device, optionally, the processing component in the second network device can also receive data messages through the port. In other words, the message transmitted between the first network device and the second network device may include a data message or a notification message. After receiving the message, the processing component of the second network device can first identify the message type and then perform corresponding processing according to the message type.

[0080] Specifically, optionally, the processing component may first parse the message, and distinguish whether the received message is a notification message or a data message based on the parsed type identifier. If the parsed type identifier is a preset identifier, the received message is a notification message. At this time, the processing component may further determine whether the notification message is an abnormal notification message or a recovery notification message based on the payload carried by the notification message. Finally, for the identified message type, the processing component may manage the target routing information accordingly.

[0081] In this embodiment, the second network device can receive the message via the port, and determine the message type through different information carried in the message, such as type identification and payload, so as to finally execute a processing action corresponding to the message type.

[0082] The first network device mentioned in the above embodiments of the present invention may have different forms of expression, and may optionally be a physical host. In order to improve the resource utilization of the physical host and the security of the network device, the first network device may optionally be a container running in an isolated environment provided by the physical host. The internal structure of the second network device may also be adjusted accordingly according to the form of expression of the first network device.

[0083] Figure 4 Another communication system provided by an embodiment of the present invention. Figure 2 and Figure 3 The network device shown, in this embodiment, the first network device can be expressed as a container deployed on a physical host, and the physical host can include at least one physical network card, and the first network device can include at least one virtual network card obtained by virtualizing the physical network card on the physical host. Among them, it can be considered that any virtual network card on the first network device belongs to the physical network card that virtualizes the virtual network card. Optionally, the virtual network card in the first network device can belong to multiple completely different physical network cards, or multiple physical network cards that are not completely the same, or the same physical network card. Optionally, the gateway in the first network device can be expressed as a virtual gateway, and the virtual gateway can be deployed in a physical network or a cloud network.

[0084] Corresponding to the first network device in the form of a container, the second network device may include only one physical port and at least one virtual port obtained by virtualizing the physical port. Optionally, the virtual port in the second network device has a corresponding relationship with the network device deployed in the physical host and expressed as a container. Optionally, the virtual port and the network device in the physical host may be in a one-to-one correspondence.

[0085] It needs to be explained that: Figure 4 The figure shows the relationship between a virtual network card, a physical network card, a virtual port, and a network device: the virtual network card 1 included in the first network device belongs to the physical network card 1 in the physical host, and the virtual network card 2 belongs to the physical network card 2 in the physical host, that is, the virtual network cards included in the first network device belong to completely different physical network cards. And the virtual port 1 corresponds to the first network device in the physical host, and the virtual port 2 corresponds to other network devices in the physical host (not shown in the figure), that is, the virtual ports in the second network device correspond to the network devices in the physical host one by one. But Figure 4 This is just a schematic representation, and this solution does not limit the relationship between them.

[0086] Based on the first network device and the second network device of the above structure, the monitoring program in the first network device can monitor the running status of its own gateway in real time, and generate corresponding notification messages (i.e., abnormal notification messages or recovery notification messages) according to the monitored running status. The abnormality of the gateway in the first network device will also cause the virtual network card in the first network device to be unusable.

[0087] To this end, the listening program can call the interface of the first target physical network card on the physical host, so that the first network device responds to the call and uses the first target physical network card to forward the notification message generated by the listening program to the second network device. The second network device can use its own target virtual port to receive the notification message. Figure 4 It can be known that the first target physical network card can be physical network card 1, and the first target physical network card can be any physical network card to which the virtual network card on the first network device belongs. The target virtual port can be virtual port 1, which corresponds to the first network device.

[0088] In this embodiment, when an abnormality occurs in the gateway of the first network device in the form of a container, the first network device in the form of a container can send an abnormality notification message with the help of the physical network card of the physical host where the container is located, and the second network device can use the virtual port corresponding to the first network device to receive the abnormality notification message and actively suspend the data message transmission between the abnormal gateway, thereby reducing the impact of the gateway abnormality on the data message transmission.

[0089] For the first network device in the form of a container, after receiving the notification message, the second network device may also choose to actively suspend or resume data message transmission with the gateway in the first network device according to the content of the notification message.

[0090] For the method of actively suspending data message transmission, in addition to Figure 1 In another optional way of managing routing information mentioned in the illustrated embodiment, the second network device can receive the abnormal notification message with the help of the target virtual port, and then the processing component in the second network device can also parse the message to obtain the port identifier carried therein. Based on the parsing result, the processing component can turn off the routing function of the target virtual port with the port identifier. It should be noted that the processing component turns off the routing function of the target virtual port, and other functions of the port, such as the switching function, are still turned on.

[0091] And the shutdown state of the routing function in the target virtual port can also be synchronized to all devices in the communication network, and the routing convergence is completed. Finally, the first network device with abnormal gateway will not receive the data message, which means that the data message is removed from the first network device.

[0092] Similarly, after the second network device receives the recovery notification message via the target virtual port, the processing component may also enable the routing function of the target virtual port having the port identifier parsed from the recovery notification message.

[0093] In this embodiment, for the first network device in the form of a container, when the running state of the gateway in the first network device changes and the second network device receives the corresponding notification message, the second network device can actively suspend or resume the data message transmission between the gateway and the second network device by closing or opening the virtual port. In this way, when an abnormality occurs in the gateway in the first network device, the impact of the gateway abnormality on the data message transmission can be reduced. When the gateway in the first network device returns to normal, normal transmission of data messages can also be achieved.

[0094] For the first network device in the form of a container, optionally, the physical host where the first network device is located can serve as a node in a cluster, and multiple network devices including the first network device can be deployed on the physical host, and each network device is a container under the node.

[0095] In one case, after the physical network card on the physical host is virtualized, the virtual network card virtualized by the physical network card can be included in the first network device, that is, the first network device exclusively occupies the preset number of physical network cards. In this case, when an abnormality occurs in the gateway of the first network device, the first network device can actively suspend the data message transmission between the first network device and the second network device, which can also reduce the impact of the gateway abnormality on the data message transmission.

[0096] Specifically, the first network device can actively close the port of the physical network card that it exclusively owns, and further, the second network device will also close the port used for data message transmission with the first network device. Ultimately, the closing of both ports can prevent the first network device from receiving data messages. In addition, the closed status of both ports can also be synchronized to all devices in the communication system, thereby achieving routing convergence.

[0097] It can be seen that for the first network device in the form of a container, when the gateway in the device exclusively occupies the physical network card, the same effect can be achieved regardless of whether the suspension of data message transmission between the gateway and the second network device is actively initiated by the first network device or the second network device.

[0098] However, in order to improve the resource utilization of the physical host, there is another more common situation: after the physical network card on the physical host is virtualized, the virtualized virtual network card can be included in multiple network devices on the physical host, that is, multiple network devices on the physical host share the physical network card on the physical host.

[0099] Assume that the virtual network cards in the first network device and the third network device are virtualized from the same physical network card on the physical host, that is, the first network device and the third network device share the same physical network card on the physical host, such as the first target physical network card on the physical host. And when the gateway on the first network device is abnormal, if the first network device actively closes the port of the first target physical network card, then the first network device and the third network device will not be able to receive data packets. But for the third network device with a normal gateway, this is obviously unreasonable. Optionally, the first target physical network card can be any physical network card on the physical host.

[0100] The above-mentioned problems can be overcome by using the solutions provided by the embodiments of the present invention. The specific reason is: when the first network device behaves as a container, the first network device and the third network device share the first target physical network card on the physical host, and an abnormality occurs in the gateway in the first network device, the first network device can notify the abnormal state of the gateway to the second network device by means of an abnormal notification message. Since the target routing information is exclusive to the first network device, the target virtual port in the second network device is also exclusively occupied by the first network device. Therefore, whether the second network device suspends the data packet transmission between the second network device and the abnormal gateway by setting the target routing information state or by shutting down the virtual port routing function, it will not affect the third network device.

[0101] Figure 5 Another communication system provided by an embodiment of the present invention. Figure 2 and Figure 3 As shown in the network device, in this embodiment, the first network device may be a physical host, and the physical host includes at least one physical network card.

[0102] For the first network device in the form of a physical host, the second network device may include a physical port, and the physical port corresponds to a physical network card on the physical host, and specifically may be a one-to-one correspondence.

[0103] Figure 5 It shows a relationship between a physical network card and a physical port: physical network card 3 corresponds to physical port 3, and physical network card 4 corresponds to physical port 4.

[0104] Based on the first network device and the second network device of the above structure, the monitoring program in the first network device can monitor the running status of its own gateway in real time, and generate an abnormal notification message or a recovery notification message according to the monitored running status. Afterwards, the monitoring program can call the interface of the second target physical network card on the physical host, so that the first network device responds to the call and uses the second target physical network card to forward the notification message generated by the monitoring program to the second network device. The second network device can use its own target physical port corresponding to the first network device to receive the notification message. Optionally, in combination Figure 5 It can be known that the second target physical network card can be physical network card 3, and the second target physical network card can be any physical network card on the first network device. The target physical port can be virtual port 3, which corresponds to physical network card 3.

[0105] In this embodiment, when an abnormality occurs in the gateway of the first network device in the form of a physical host, the first network device in the form of a physical host can directly send an abnormality notification message with the help of the physical network card configured by itself, and the second network device can use the target physical port corresponding to the first network device to receive the abnormality notification message, and actively suspend the data message transmission between it and the abnormal gateway, thereby reducing the impact of the gateway abnormality on the data message transmission.

[0106] Similar to the first network device that appears as a container, for the first network device that appears as a physical host, after receiving the notification message, the second network device can also choose to actively suspend or resume data message transmission between the gateway in the first network device according to the content of the notification message.

[0107] For the method of actively suspending data message transmission, in addition to Figure 1 In another optional manner of managing routing information mentioned in the illustrated embodiment, the second network device may parse the abnormal notification message received by means of the target physical port to obtain the port identifier carried therein. The processing component in the second network device may shut down the routing function of the target physical port having the port identifier, and at this time, other functions of the target physical port, such as the switching function, are not affected.

[0108] In addition, the shutdown state of the routing function in the target physical port can also be synchronized to all devices in the communication network. At this time, routing convergence is completed, and the first network device with an abnormal gateway will not receive data packets, which means that data packets are removed from the first network device.

[0109] Similarly, after the second network device receives the recovery notification message via the target physical port, the processing component may also enable the routing function of the target physical port having the port identifier parsed from the recovery notification message.

[0110] In this embodiment, for the first network device that behaves as a physical host, when the running state of the gateway in the first network device changes and the second network device receives the corresponding notification message, the second network device can actively suspend or resume the data message transmission between the gateway and the gateway by closing or opening the physical port. In this way, when an abnormality occurs in the gateway in the first network device, the impact of the gateway abnormality on the data message transmission can be reduced. When the gateway in the first network device returns to normal, normal transmission of data messages can also be achieved.

[0111] Optionally, the notification message mentioned in each embodiment of the present invention may have Figure 6 The structure shown. Figure 6 As shown, the notification message includes the following fields: source LAN address, i.e., source Media Access Control address (MAC address for short), destination LAN address, i.e., destination MAC address, type identifier, port identifier, and message data. After receiving the message, the second network device can obtain the type identifier, port identifier, and message data of the message by parsing, and perform corresponding operations according to the parsed content. For the specific process, please refer to the relevant descriptions in the above embodiments, which will not be repeated here.

[0112] In addition, based on the solutions provided in the above embodiments, the beneficial effects thereof can also be understood in combination with the following contents:

[0113] In practice, bidirectional forwarding detection (BFD) can also be used to determine the running status of the gateway. Specifically, a BFD session can be established between the first network device and the second network device to periodically send BFD control messages through this session channel to monitor the running status of the gateway in the network device, and the monitoring results can also be ultimately used to achieve routing convergence. Optionally, BFD can be implemented in the form of hardware or software.

[0114] When BFD is implemented by hardware, since existing network devices are usually not equipped with devices for implementing BFD, it is impossible to implement anomaly detection by using BFD. Adding new devices to network devices will increase the cost of network devices.

[0115] When implementing BFD using software, the software needs to be deployed on the physical host together with the network devices that need to be monitored and are represented as containers. Considering that BFD is performed in real time, the software will consume the central processing unit (CPU) resources of the physical host when it is running. On the other hand, since multiple containers can be deployed on the physical host at the same time, a large number of BFD sessions need to be established. A large number of BFD sessions will not only consume more CPU resources on the physical host, but also reduce the real-time performance of running status monitoring, further prolonging the time required to achieve routing convergence, and ultimately have a significant impact on the transmission of data packets.

[0116] By using the solutions provided by the embodiments of the present invention, there is no need to deploy additional hardware or establish a session. The gateway operation status can be detected by using a newly added monitoring program in the network device, and the operation status can be quickly monitored without occupying a large amount of CPU resources of the physical host.

[0117] Above Figure 1 to Figure 6 The illustrated embodiment has described how to improve the impact of gateway anomalies on data message transmission when an anomaly occurs in the gateway of the first network device from the perspective of system structure and device internal structure. On this basis, the working processes of the first network device and the second network device in the communication system can also be described from the perspective of the process.

[0118] Figure 7 The flowchart of a method for detecting abnormal device status provided by an embodiment of the present invention is shown in FIG. The method provided by an embodiment of the present invention can be executed by the first network device in each of the above embodiments. Figure 7 As shown, the method may include the following steps:

[0119] S101: monitor the running status of a gateway in a first network device.

[0120] S102: If it is monitored that an abnormality occurs in the gateway of the first network device, an abnormality notification message is generated.

[0121] S103: Using the physical network card corresponding to the first network device, send an abnormal notification message to the second network device, so that the second network device suspends data message transmission with the gateway in the first network device.

[0122] The first network device can monitor the operating status of its own gateway, and when it detects that the gateway has an abnormality, the first network device can generate an abnormality notification message, and use its corresponding physical network card to send the message to the second network device that transmits data messages with the gateway in the first network device, so that the second network device actively suspends the transmission of data messages with this abnormal gateway.

[0123] In addition, the contents not described in detail in this embodiment can be found in Figure 1 and Figure 2 The relevant contents in the illustrated embodiment will not be repeated here.

[0124] In this embodiment, the first network device is newly equipped with a monitoring function for the operation status of the gateway. When the first network device monitors that an abnormality has occurred in its own gateway, it can actively generate an abnormality notification message and send the abnormality notification message with the help of a physical network card, so that the second network device responds to the reception of the abnormality notification message and actively suspends data message transmission with the gateway in the first network device. At this time, data messages can still be transmitted in the second network device and other network devices, which can reduce the impact of gateway abnormalities on message transmission.

[0125] That is to say, when an abnormality occurs in the gateway of the first network device, compared with the first network device actively suspending the message transmission between the first network device and the second network device, the above method provides a new way to suspend the data message transmission between network devices: the first network device actively reports the abnormality of its own gateway to the second network device, so that the second network device actively suspends the data message transmission between the first network device.

[0126] It is easy to understand that after the abnormal gateway is operated and maintained, the gateway can also return to normal. At this time, the first network device can also monitor that its own gateway has returned to normal and generate a recovery notification message. After receiving the recovery notification message, the second network device can actively resume the data message transmission between it and the gateway in the first network device.

[0127] Optionally, the first network device can be specifically expressed as a container deployed on a physical host. In this case, the first network device can use the first target physical network card in the physical host to send an abnormal notification message to the second network device, so that the second network device suspends data message transmission between the second network device and the abnormal gateway. The internal structure, specific working process and technical effects of the container-type network device can be found in Figure 4 The relevant contents in the illustrated embodiment will not be repeated here.

[0128] More specifically, for the first network device represented as a container, in one optional case, the network device can exclusively occupy the first target physical network card in the physical host; in another optional case, the virtual network card included in the first network device can share the physical network card in the physical host with other network devices in the physical host, such as the third network device. In either case, the first network device can use the first target physical network card to send an exception notification message.

[0129] Optionally, the first network device can also directly behave as a physical host. In this case, the first network device can directly use the second target physical network card deployed on itself to send the abnormal notification message to the second network device. The internal structure, specific working process and technical effects of the container-based network device can be found in Figure 5 The relevant contents in the illustrated embodiment will not be repeated here.

[0130] Figure 8 This is a flowchart of another device abnormality method provided by an embodiment of the present invention. The method provided by an embodiment of the present invention can be executed by the second network device in each of the above embodiments. Figure 8 As shown, the method may include the following steps:

[0131] S201, receiving a notification message.

[0132] S202: Determine whether the notification message is an abnormal notification message according to the payload in the notification message, where the abnormal notification message reflects that an abnormality occurs in the gateway in the first network device.

[0133] S203, if the notification message is an abnormal notification message, manage the target routing information to suspend the data message transmission between the second network device and the gateway in the first network device, and the target routing information is used for the data message transmission between the second network device and the gateway in the first network device.

[0134] The second network device can receive the notification message and determine whether the notification message is an abnormal notification message or a recovery notification message based on the payload in the notification message. When the notification message is an abnormal notification message, in an optional manner, the second network device can manage the target routing information to actively suspend the data message transmission between the gateway in the first network device. The target routing information is the routing information used when the second network device and the gateway in the first network device transmit data messages. The management method of the target routing information may include deleting the target routing information or setting the target routing information to an unavailable state.

[0135] Optionally, the second network device can also receive data messages. When the second network device receives a message, it can parse the received message and determine whether the message is a notification message or a data message based on the parsed type identifier. If it is a notification message, it can further determine whether the notification message is an abnormal notification message or a recovery notification message based on the payload in the message.

[0136] In addition, the contents not described in detail in this embodiment can be found in Figure 1 and Figure 3 The relevant contents in the illustrated embodiment will not be repeated here.

[0137] In this embodiment, when an abnormality occurs in a gateway in the first network device, in response to an abnormality notification message sent by the first network device via a physical network card, the second network device may actively suspend data message transmission with the abnormal gateway.

[0138] Optionally, when the gateway in the first network device returns to normal, similarly, the second network device may also respond to the recovery notification message sent by the first network device via the physical network card to actively restore data message transmission with the abnormal gateway.

[0139] For the first network device that is a container, the second network device can use the target virtual port corresponding to the first network device to receive the notification message. Alternatively, the second network device can also actively suspend the data message transmission between the abnormal gateway and the target virtual network port by shutting down the routing function of the target virtual network port. The internal structure, specific working process and technical effects of the first network device and the second network device can be found in Figure 4 The relevant contents in the illustrated embodiment will not be repeated here.

[0140] For the first network device that behaves as a physical host, the second network device can use its own target physical port to receive the notification message. Alternatively, the second network device can also actively suspend the data message transmission between the abnormal gateway and the target physical port by shutting down the routing function of the target physical network port. The internal structure, specific working process and technical effects that can be achieved by the first network device and the second network device can be found in Figure 5 The relevant contents in the illustrated embodiment will not be repeated here.

[0141] The following will describe in detail the device exception handling apparatus of one or more embodiments of the present invention. Those skilled in the art will appreciate that the apparatus can be configured using commercially available hardware components through the steps taught in this solution.

[0142] Fig. 9 The structure diagram of a device exception handling device provided by an embodiment of the present invention. The device functions as a network device. Fig. 9 As shown, the device may include:

[0143] The monitoring module 11 is used to monitor the running status of the gateway in the first network device.

[0144] The generating module 12 is configured to generate an abnormality notification message if it is monitored that an abnormality occurs in the gateway of the first network device.

[0145] The sending module 13 is used to use the physical network card corresponding to the first network device to send the abnormal notification message to the second network device, so that the second network device suspends data message transmission with the gateway in the first network device.

[0146] Optionally, the first network device includes a container deployed on a physical host, the physical host includes a first target physical network card, and the first network device includes a virtual network card obtained by virtualizing the first target physical network card.

[0147] The sending module 13 is used to send the abnormal notification message to the second network device by using the first target physical network card in the physical host.

[0148] A third network device is also deployed in the physical host, and each of the first network device and the third network device includes a virtual network card obtained by virtualizing the first target physical network card.

[0149] Optionally, the first network device includes a physical host, and the physical host includes a second target physical network card.

[0150] The sending module 13 is used to send the abnormal notification message to the second network device by using the second target physical network card.

[0151] Optionally, the generating module 11 is configured to generate a recovery notification message if it is monitored that the gateway in the first network device has returned to normal.

[0152] The sending module 13 is used to send the recovery notification message to the second network device, so that the second network device can resume data message transmission with the gateway in the first network device.

[0153] Fig. 9 The device shown can perform Figure 7 For the method of the embodiment shown in the figure, the part not described in detail in this embodiment can be referred to Figure 7 The implementation process and technical effects of this technical solution refer to Figure 7 The description in the illustrated embodiment will not be repeated here.

[0154] Fig.10 This is a schematic diagram of the structure of another device exception handling device provided by an embodiment of the present invention. The device can act as a gateway. Fig.10 As shown, the device may include:

[0155] The receiving module 21 is used to receive a notification message.

[0156] The identification module 22 is used to determine whether the notification message is an abnormal notification message according to the payload in the notification message, and the abnormal notification message reflects that an abnormality occurs in the gateway in the first network device.

[0157] The processing module 23 is used to manage the target routing information if the notification message is the abnormal notification message, so as to make the second network device suspend the data message transmission with the gateway in the first network device. The target routing information is used for the second network device to transmit data messages with the gateway in the first network device.

[0158] The processing module 23 is used to manage the target routing information if the notification message is a recovery notification message, so that the second network device can resume data message transmission with the gateway in the first network device. Optionally, the first network device includes a container deployed on a physical host.

[0159] The second network device includes a physical port and a virtual port obtained by virtualizing the physical port, and the virtual port corresponds to the network device deployed on the physical host.

[0160] The receiving module 21 is used to receive the notification message by using the target virtual port in the second network device corresponding to the first network device.

[0161] Optionally, the processing module 23 is used to disable the routing function of the target virtual port;

[0162] Alternatively, setting the target routing information to an unavailable state, the target routing information including a port identifier of the target virtual port;

[0163] Alternatively, the target routing information is deleted.

[0164] Optionally, the processing module 23 is configured to obtain a port identifier carried in the abnormal notification message; and disable a routing function of the target virtual port having the port identifier.

[0165] Optionally, the first network device includes a physical host, the physical host includes a physical network card, and the second network device includes a physical port, the physical port corresponds to the physical network card.

[0166] The receiving module 21 is used to receive the notification message by using a target physical port in the second network device, where the target physical port corresponds to a target physical network card in the first network device.

[0167] Optionally, the identification module 22 is used to parse the received message to obtain the type identifier carried in the message;

[0168] If the type identifier is a preset identifier, it is determined that the received message is the notification message.

[0169] Optionally, the identification module 22 is used to determine that the notification message is the abnormal notification message if the payload carried by the notification message is a first preset value;

[0170] If the payload carried by the notification message is a second preset value, it is determined that the notification message is a recovery notification message.

[0171] Fig.10 The device shown can perform Figure 8 For the method of the embodiment shown in the figure, the part not described in detail in this embodiment can be referred to Figure 8 The implementation process and technical effects of this technical solution refer to Figure 8 The description in the illustrated embodiment will not be repeated here.

[0172] In addition, in a possible design, the device exception handling method provided in the above embodiments can be applied to a network device. Fig.11 As shown, the network device may include: a processor 31 and a memory 32. The memory 32 is used to store the information that supports the network device to execute the above Figure 6 The program of the device exception handling method provided in the illustrated embodiment, the processor 31 is configured to execute the program stored in the memory 32 .

[0173] The program includes one or more computer instructions, wherein the one or more computer instructions can achieve the above-mentioned Figure 7 or Figure 8 The steps in the device exception handling method provided in the illustrated embodiment.

[0174] Optionally, the processor 31 is further configured to execute the aforementioned Figure 7 or Figure 8 All or part of the steps in the illustrated embodiments.

[0175] The structure of the electronic device may further include a communication interface 33 for the electronic device to communicate with other devices or communication systems.

[0176] In addition, an embodiment of the present invention provides a non-transitory machine-readable storage medium for storing computer software instructions used by the above electronic device, which includes instructions for executing the above Figure 7 or Figure 8 The procedures involved in the device exception handling method shown.

[0177] In addition, an embodiment of the present invention provides a computer program product. The computer program product includes a computer program or an instruction. When the computer program or the instruction is executed by a processor, the processor is enabled to implement the above Figure 7 or Figure 8 The steps or functions of the device exception handling method shown.

[0178] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention, rather than to limit it. Although the present invention has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or make equivalent replacements for some of the technical features therein. However, these modifications or replacements do not deviate the essence of the corresponding technical solutions from the spirit and scope of the technical solutions of the embodiments of the present invention.

Claims

1. A method for handling device abnormalities, characterized in that: Applied to a first network device, the method comprises: Monitoring the running status of the gateway in the first network device; If it is monitored that an abnormality occurs in the gateway of the first network device, an abnormality notification message is generated; The abnormal notification message is sent to the second network device by using the physical network card corresponding to the first network device, so that the second network device suspends data message transmission with the gateway in the first network device.

2. The method according to claim 1, characterized in that The first network device includes a container deployed on a physical host, the physical host includes a first target physical network card, and the first network device includes a virtual network card obtained by virtualizing the first target physical network card; The sending the abnormal notification message to the second network device by using the physical network card corresponding to the first network device includes: The exception notification message is sent to the second network device by using the first target physical network card in the physical host.

3. The method according to claim 2, characterized in that A third network device is also deployed in the physical host, and the first network device and the third network device each include a virtual network card obtained by virtualizing the first target physical network card.

4. The method according to claim 1, characterized in that: The first network device includes a physical host, and the physical host includes a second target physical network card; The sending the abnormal notification message to the second network device by using the physical network card corresponding to the first network device includes: The exception notification message is sent to the second network device by using the second target physical network card.

5. The method according to any one of claims 1 to 4, characterized in that The method further comprises: If it is monitored that the gateway in the first network device has returned to normal, a recovery notification message is generated; The recovery notification message is sent to the second network device, so that the second network device resumes data message transmission with the gateway in the first network device.

6. A method for handling device abnormalities, characterized in that: Applied to the second network device, the method comprises: Receive notification message; Determine whether the notification message is an abnormal notification message according to the payload in the notification message, the abnormal notification message is generated and sent by the first network device, and the abnormal notification message reflects that an abnormality occurs in the gateway in the first network device; If the notification message is the abnormal notification message, the target routing information is managed to make the second network device suspend data message transmission with the gateway in the first network device, and the target routing information is used for the second network device to transmit data messages with the gateway in the first network device.

7. The method according to claim 6, characterized in that The method further comprises: If the notification message is a recovery notification message, the target routing information is managed so that the second network device resumes data message transmission with the gateway in the first network device.

8. The method according to claim 6 or 7, characterized in that: The first network device includes a container deployed on a physical host; The second network device includes a physical port and a virtual port obtained by virtualizing the physical port, wherein the virtual port corresponds to the network device deployed on the physical host; The receiving notification message includes: The notification message is received by using the target virtual port in the second network device corresponding to the first network device.

9. The method according to claim 8, characterized in that The managing target routing information so that the second network device suspends data message transmission with the gateway in the first network device includes: Disable the routing function of the target virtual port; Alternatively, setting the target routing information to an unavailable state, the target routing information including a port identifier of the target virtual port; Alternatively, the target routing information is deleted.

10. The method according to claim 9, characterized in that The step of disabling the routing function of the target virtual port includes: Obtaining a port identifier carried in the abnormal notification message; The routing function of the target virtual port having the port identifier is disabled.

11. The method according to claim 6 or 7, characterized in that: The first network device includes a physical host, and the physical host includes a physical network card; the second network device includes a physical port, and the physical port corresponds to the physical network card; The receiving notification message includes: The notification message is received using a target physical port in the second network device, where the target physical port corresponds to a target physical network card in the first network device.

12. The method according to claim 6, characterized in that The method further comprises: Parsing the received message to obtain the type identifier carried in the message; If the type identifier is a preset identifier, it is determined that the received message is the notification message.

13. The method according to claim 6 or 7, characterized in that: The determining, according to the payload in the notification message, whether it is the abnormal notification message includes: If the payload carried by the notification message is a first preset value, determining that the notification message is the abnormal notification message; If the payload carried by the notification message is a second preset value, it is determined that the notification message is a recovery notification message.

14. A communication system, characterized in that: include: A first network device and a second network device for transmitting data packets, wherein the first network device includes a gateway; The first network device is used to monitor the running status of the gateway in the first network device; if an abnormality occurs in the gateway, an abnormality notification message is generated; and the abnormality notification message is sent using the physical network card corresponding to the first network device; The second network device is used to manage target routing information in response to receiving the abnormal notification message to suspend data message transmission with the gateway in the first network device, and the target routing information is used for data message transmission between the second network device and the gateway in the first network device.

15. The system according to claim 14, characterized in that The first network device further includes: a monitoring program for monitoring the running status of the gateway; if an abnormality occurs in the gateway, the abnormality notification message is generated.

16. The system according to claim 15, characterized in that The first network device includes a container deployed on a physical host, the physical host includes a first target physical network card, and the first network device includes a virtual network card obtained by virtualizing the first target physical network card; The second network device includes a physical port and a virtual port obtained by virtualizing the physical port, wherein the virtual port corresponds to the network device deployed on the physical host; The first network device is configured to send the abnormal notification message by using the first target physical network card in response to the interface call of the first target physical network card by the monitoring program; The second network device is used to receive the abnormal notification message by using the target virtual port in the second network device corresponding to the first network device.

17. The system according to claim 16, characterized in that The second network device includes a processing component, which is used to obtain a port identifier carried in the abnormal notification message; shut down the routing function of the target virtual port having the port identifier; Alternatively, setting the target routing information to an unavailable state, the target routing information including a port identifier of the target virtual port; Alternatively, the target routing information is deleted.

18. The system according to claim 15, characterized in that The monitoring program is used to generate a recovery notification message if the gateway returns to normal; The second network device is used to set the target routing information to an available state or recreate the target routing information in response to receiving the recovery notification message.

19. The system according to claim 14, characterized in that The second network device includes a processing component, configured to parse a message received by the second network device to obtain a type identifier carried in the message; If the type identifier is a preset identifier, determining that the received message is the notification message; Determine whether the notification message is the abnormal notification message according to the payload in the notification message.

20. A network device, characterized in that: include: Listeners and gateways; The monitoring program is used to monitor the running status of the gateway in the network device; if an abnormality occurs in the gateway in the network device, an abnormality notification message is generated; The network device is used to send the abnormal notification message by using the physical network card corresponding to the network device, so that the receiving device of the abnormal notification message suspends data message transmission with the gateway in the network device.

21. The device according to claim 20, characterized in that The network device includes a container deployed on a physical host, the physical host includes a first target physical network card, and the network device includes a virtual network card obtained by virtualizing the first target physical network card; The network device is used to send the abnormal notification message to the receiving device by using the first target physical network card in the physical host.

22. The device according to claim 20, characterized in that The network device includes a physical host, and the physical host includes a second target physical network card; The network device is used to send the abnormal notification message to the receiving device by using the second target physical network card.

23. A network device, characterized in that: The network device transmits data packets with a target device in a communication system; the network device comprises: a port and a processing component; The processing component is used to receive the notification message using the port; Determine whether the notification message is an abnormal notification message according to the payload in the notification message, the abnormal notification message is generated and sent by the target device, and the abnormal notification message reflects that an abnormality occurs in the gateway of the target device; If the notification message is the abnormal notification message, the target routing information is managed to make the network device suspend data message transmission with the gateway in the target device, and the target routing information is used for data message transmission between the network device and the gateway in the target device.

24. The device according to claim 23, characterized in that The target device includes a container deployed on a physical host; The ports in the network device include physical ports and virtual ports obtained by virtualizing the physical ports, and the virtual ports correspond to devices deployed on the physical host; The network device is used to receive the abnormal notification message by using the target virtual port in the network device corresponding to the target device.

25. The device according to claim 23, characterized in that The target device includes a physical host, and the physical host includes a physical network card; The port in the network device includes a physical port, and the physical port corresponds to the physical network card; The network device is used to receive the abnormal notification message by using a target physical port in the network device, and the target physical port corresponds to a target physical network card in the target device.

26. A network device, characterized in that: include: A memory and a processor; wherein the memory stores executable code, and when the executable code is executed by the processor, the processor executes the device exception handling method as described in any one of claims 1 to 13.

27. A non-transitory machine-readable storage medium, characterized in that The non-transitory machine-readable storage medium stores executable code, and when the executable code is executed by a processor of an electronic device, the processor is caused to execute the device exception handling method according to any one of claims 1 to 13.

28. A computer program product, characterized in that The computer program product includes a computer program or instructions, so that the computer program or instructions can implement the steps in the device abnormality handling method according to any one of claims 1 to 13.

Images