A fault handling method and apparatus

Abstract

The application relates to the technical field of network communication, in particular to a fault processing method and device. The method is applied to a controller, a network of which includes a gateway set of at least two gateways for load sharing, each gateway in the gateway set uses a first IP address, and the method comprises the following steps: when detecting that a first gateway in the gateway set is faulty, issuing a second IP address to a second gateway in the gateway set except the first gateway; sending a route announcement carrying an OVS host IP address to the second gateway, receiving a route announcement carrying the second IP address sent by the second gateway; and updating a tunnel destination IP address of a table item with a tunnel destination IP address being the first IP address on the OVS host to the second IP address.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of network communication, in particular to a fault processing method and device. BACKGROUND

[0002] In some networking, a scheme of using dual-active gateway is used, for example, an SDNGW is a dual-active VXLAN gateway, load sharing of the gateway is realized, two SDNGWs share the same MAC and gateway address, and serve as a north-south VXLAN gateway of a VNF (virtual machine), and the configuration is automatically issued by an SDN controller. When one of the GWs fails, the traffic can be switched without sensing, so as to avoid the influence of single point failure on the network.

[0003] In actual application, when the controller detects that a southbound device fails (mainly represented by that the state of the device connected to the controller is inactive, which can be caused by traffic interruption, openflow connection failure, netconf connection failure, etc.), the configuration needs to be issued to the failed device, the configuration issued to all devices will fail, and the northbound (VIM, mano) of the controller is also reported to stop the service deployment process. The main purpose of this function is: in the case of device failure, the configuration will fail to be issued, if the upper-layer application VIM and mano of the controller are not aware of it and continue to complete the service deployment process, the traffic will be affected due to the failure of the configuration. After this function, the upper-layer application can be notified to stop the service deployment process in time, and the problem can be checked.

[0004] However, the isolation of the failed device only solves the problem of failure of the configuration to be issued, and the device failure can be caused in many ways. When the link between the failed gateway and the controller is disconnected, the controller detects that the gateway fails, and the port of the gateway is up. At this time, the traffic will still be hashed to the gateway, and at this time, there is still a case that the port of the gateway is up, but the traffic cannot be forwarded, and at this time, the problem of traffic loss exists. SUMMARY

[0005] The present application provides a fault processing method and device to solve the problem of traffic loss in the prior art.

[0006] In a first aspect, the present application provides a fault processing method applied to a controller, a networking connected to the controller includes a gateway set of at least two gateways for load sharing, each gateway included in the gateway set uses a first IP address, and the method comprises:

[0007] When a first gateway in the gateway set is detected to fail, a second IP address is issued to a second gateway in the gateway set except the first gateway;

[0008] sending a route advertisement carrying the OVS host IP address to the second gateway, and receiving a route advertisement carrying the second IP address sent by the second gateway;

[0009] updating a tunnel destination IP address of a table item with a tunnel destination IP address of the first IP address on the OVS host to the second IP address.

[0010] Optionally, when detecting failure of a first gateway in the gateway set, the step of issuing a second IP address to a second gateway in the gateway set other than the first gateway comprises:

[0011] after detecting disconnection of a connection with the first gateway in the gateway set, prompting a user to input a second IP address;

[0012] based on the second IP address input by the user, issuing a configuration carrying the second IP address to the second gateway.

[0013] Optionally, the step of updating the tunnel destination IP address of the table item with the tunnel destination IP address of the first IP address on the OVS host to the second IP address comprises:

[0014] sending an OVS flow table modification instruction to the OVS host, so that the OVS host updates the tunnel destination IP address of the table item with the tunnel destination IP address of the first IP address in the local flow table from the first IP address to the second IP address after receiving the OVS flow table modification instruction.

[0015] Optionally, the step of updating the tunnel destination IP address of the table item with the tunnel destination IP address of the first IP address on the OVS host to the second IP address comprises:

[0016] sending an OVS flow table for replacing the table item with the tunnel destination IP address of the first IP address on the OVS host to the OVS host, so that the OVS host replaces the table item with the tunnel destination IP address of the first IP address in the local flow table with the OVS flow table after receiving the OVS flow table.

[0017] Optionally, the method further comprises:

[0018] isolating the failed first gateway.

[0019] In a second aspect, the application provides a fault processing apparatus applied to a controller, a networking of which includes a gateway set of at least two gateways for load sharing, each gateway in the gateway set using a first IP address, the apparatus comprising:

[0020] a first sending unit, configured to send a second IP address to a second gateway in the gateway set except the first gateway when detecting that the first gateway in the gateway set fails;

[0021] a second sending unit, configured to send a route advertisement carrying an OVS host IP address to the second gateway, and receive a route advertisement carrying the second IP address sent by the second gateway;

[0022] an updating unit, configured to update a tunnel destination IP address of a table item with the tunnel destination IP address being the first IP address on the OVS host to the second IP address.

[0023] Optionally, when detecting that the first gateway in the gateway set fails, and sending the second IP address to the second gateway in the gateway set except the first gateway, the first sending unit is specifically configured to:

[0024] prompting a user to input a second IP address after detecting that a connection between the first gateway in the gateway set is disconnected;

[0025] sending a configuration carrying the second IP address to the second gateway based on the second IP address input by the user.

[0026] Optionally, when updating the tunnel destination IP address of the table item with the tunnel destination IP address being the first IP address on the OVS host to the second IP address, the updating unit is specifically configured to:

[0027] sending an OVS flow table modification instruction to the OVS host, so that the OVS host updates the tunnel destination IP address of the table item with the tunnel destination IP address being the first IP address in a local flow table from the first IP address to the second IP address after receiving the OVS flow table modification instruction.

[0028] Optionally, when updating the tunnel destination IP address of the table item with the tunnel destination IP address being the first IP address on the OVS host to the second IP address, the updating unit is specifically configured to:

[0029] sending an OVS flow table for replacing the table item with the tunnel destination IP address being the first IP address on the OVS host to the OVS host, so that the OVS host replaces the table item with the tunnel destination IP address being the first IP address in a local flow table to the OVS flow table after receiving the OVS flow table.

[0030] Optionally, the apparatus further comprises:

[0031] an isolating unit, configured to isolate the failed first gateway.

[0032] In a third aspect, an embodiment of the present application provides a fault processing apparatus, comprising:

[0033] a memory configured to store program instructions;

[0034] a processor configured to invoke the program instructions stored in the memory and perform the steps of the method according to any one of the first aspect.

[0035] In a fourth aspect, an embodiment of the present application further provides a computer readable storage medium storing computer executable instructions for causing a computer to perform the steps of the method according to any one of the first aspect.

[0036] In summary, the fault processing method provided by the embodiments of the present application is applied to a controller, the networking of which includes a gateway set of at least two gateways for load sharing, each gateway in the gateway set uses a first IP address, and the method comprises: when detecting that a first gateway in the gateway set is faulty, issuing a second IP address to a second gateway in the gateway set except the first gateway; sending a route advertisement carrying an OVS host IP address to the second gateway, and receiving a route advertisement carrying the second IP address sent by the second gateway; and updating a tunnel destination IP address of a table item on the OVS host with the tunnel destination IP address being the first IP address to the second IP address.

[0037] By using the fault processing method provided by the embodiments of the present application, after detecting that any gateway in the gateway set is faulty, a new IP address is configured to other normal gateways, so that the other normal gateways can establish a tunnel with the OVS host based on the new IP address, quickly recover the service traffic, and not affect the original service and the delivery of new services. The user can continue to run the entire network service without being affected during the replacement or repair of the faulty device. BRIEF DESCRIPTION OF DRAWINGS

[0038] In order to more clearly illustrate the technical solutions in the embodiments of the present application or the prior art, the following will briefly introduce the drawings needed to be used in the description of the embodiments of the present application or the prior art. Obviously, the drawings in the following description are only some embodiments described in the present application, and other drawings can also be obtained by those skilled in the art according to these drawings of the embodiments of the present application.

[0039] Figure 1 A detailed flowchart of a fault processing method provided by an embodiment of the present application;

[0040] Figure 2A detailed flowchart of another fault handling method provided in an embodiment of this application;

[0041] Figure 3 This is a schematic diagram of the structure of a fault handling device provided in an embodiment of this application;

[0042] Figure 4 This is a schematic diagram of another fault handling device provided in an embodiment of this application. Detailed Implementation

[0043] 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.

[0044] 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."

[0045] For example, see Figure 1 The diagram shown is a detailed flowchart of a fault handling method provided in an embodiment of this application. The method is applied to a controller, and the network managed by the controller includes a gateway set of at least two gateways for load balancing. Each gateway in the gateway set uses a first IP address. The method includes the following steps:

[0046] Step 100: When a fault is detected in the first gateway in the gateway set, a second IP address is sent to the second gateway in the gateway set other than the first gateway.

[0047] In this embodiment of the application, when the controller detects a fault in any gateway, it isolates the faulty gateway.

[0048] In this embodiment of the application, when a fault is detected in the first gateway in the gateway set, a preferred implementation method for sending a second IP address to a second gateway in the gateway set other than the first gateway is as follows: after detecting that the connection with the first gateway in the gateway set is broken, the user is prompted to enter a second IP address; based on the second IP address entered by the user, a configuration carrying the second IP address is sent to the second gateway.

[0049] Specifically, the controller (such as an SDN controller) manages the gateway device, and each gateway device is connected through a management network. When the controller detects that the communication connection with a gateway is disconnected, it is determined that the gateway has failed.

[0050] In the embodiment of the application, the gateway set can include at least two gateway devices, and each gateway in the gateway set is used for load sharing, that is, each gateway in the gateway set shares an IP address and a MAC address.

[0051] For example, the gateway set includes gateway 1 and gateway 2, and gateway 1 and gateway 2 share the forwarding of service traffic, that is, the OVS host can hash the service traffic to gateway 1 and gateway 2 for forwarding through a preset hash algorithm, and gateway 1 and gateway 2 share an IP address (such as a first IP address) and a MAC address.

[0052] Of course, the gateway set can also include multiple (such as 3, 4, or n) gateway devices, and the multiple gateway devices are used for load sharing. In the embodiment of the application, no specific limitation is made herein.

[0053] If the controller detects that the first gateway (such as gateway 1) has failed, it issues a new IP address (such as a second IP address) to gateway 2. Specifically, when the controller detects that the connection with the first gateway is disconnected, it prompts the user to input the second IP address, obtains the second IP address input by the user, and issues the second IP address to gateway 2 in the configuration.

[0054] Step 110: sending a route advertisement carrying an OVS host IP address to the second gateway, and receiving a route advertisement carrying the second IP address sent by the second gateway.

[0055] Specifically, the controller and the second gateway mutually advertise class 3 routes, that is, after the second gateway receives the second IP address issued by the controller, it configures the local IP address as the second IP address, and after the configuration is successful, it advertises its IP address (the second IP address) to the controller through the class 3 route advertisement, and at the same time, the controller advertises the IP address of the OVS host managed by it to the second gateway through the class 3 route.

[0056] Step 120: updating the tunnel destination IP address of the table item with the tunnel destination IP address of the first IP address on the OVS host to the second IP address.

[0057] Specifically, in the embodiment of the present application, when updating the tunnel destination IP address of the table entry with the tunnel destination IP address of the first IP address on the OVS host to the second IP address, a preferred implementation is to send an OVS flow table modification instruction to the OVS host, so that the OVS host updates the tunnel destination IP address of the table entry with the tunnel destination IP address of the first IP address in the local flow table from the first IP address to the second IP address after receiving the OVS flow table modification instruction.

[0058] For example, assuming that the table entries with the tunnel destination IP address of the first IP address on the OVS host are table entry 1 and table entry 2, the tunnel destination IP addresses of table entry 1 and table entry 2 are the first IP address before modification, and the OVS host modifies the tunnel destination IP addresses of table entry 1 and table entry 2 from the first IP address to the second IP address after receiving the OVS modification instruction sent by the controller.

[0059] In the embodiment of the present application, when updating the tunnel destination IP address of the table entry with the tunnel destination IP address of the first IP address on the OVS host to the second IP address, another preferred implementation is to send an OVS flow table to the OVS host to replace the table entry with the tunnel destination IP address of the first IP address on the OVS host, so that the OVS host replaces the table entry with the tunnel destination IP address of the first IP address in the local flow table with the OVS flow table after receiving the OVS flow table.

[0060] For example, assuming that the table entries with the tunnel destination IP address of the first IP address on the OVS host are table entry 1 and table entry 2, at this time,

[0061] The process of the fault processing method provided by the embodiment of the present application will be described in detail below in combination with a specific application scenario. For example, referring to Figure 2 As shown in the figure, the detailed flowchart of the fault processing method provided by the embodiment of the present application includes the following steps:

[0062] Step 1, the controller isolates the fault device.

[0063] Specifically, the gateway set includes a plurality of gateway devices, and the plurality of gateway devices share the same VTEP IP. When the controller detects any gateway device fault, the fault device is isolated, that is, the fault device is removed from the networking under its management.

[0064] For example, when the SDNGW device is offline from the controller or other modules of the device fail, resulting in the controller failing to add new services, or the original service traffic in the network is abnormal, the customer checks out the SDNGW device failure and wants to continue running the existing service with a single SDNGW, so that the original service and the new service are not affected. At this time, the customer needs to operate the isolation of the faulty device on the controller.

[0065] Step 2, issue a new VTEP IP to the normal device.

[0066] Specifically, the gateway set also includes other gateway devices that are working normally. At this time, the controller issues the VTEP IP reset by the user to the other gateway devices that are working normally.

[0067] In actual application, the controller requires the customer to input a new VTEP IP (such as IP1) on the controller for the operation of isolation of the faulty device, and the controller retains the original VTEP IP, but only the original VTEP IP is not issued to the device. The controller issues a new VTEP IP to the normal SDNGW device, and after issuing to the device, the corresponding configuration is evpn edge group IP1. In the following process, the normal SDNGW device will establish a tunnel with the OVS host by IP1.

[0068] After isolating the faulty device, the controller deletes the l2vpn evpn neighbor between vBGP and the faulty device on the controller, so as to avoid the influence of the bgp route sent by the faulty device.

[0069] Step 3, the SDNGW and vBGP mutually advertise Class 3 routes.

[0070] For example, after the SDNGW adds the evpn edge group IP1 configuration, it will advertise IP1 to vBGP through Class 3 routes. At the same time, the controller also advertises the VTEP IP (OVS host IP) to the SDNGW in the form of Class 3 routes through vBGP for the OVS host under its management.

[0071] Step 4, the controller modifies the OVS host flow table, so that the remote VTEP IP is the newly issued VTEP IP on the SDNGW.

[0072] Step 5, the OVS host establishes a new tunnel to the normal SDNGW.

[0073] Specifically, after the controller receives the Class 3 routes advertised by the SDNGW, it will update the flow table on the OVS host, and the remote VTEP of the tunnel after encapsulating the vxlan packet through the flow table is IP1. Thus, a new tunnel from the OVS host to the SDNGW IP1 is established.

[0074] Step 6, the SDNGW establishes a tunnel to the OVS host with the new VTEP IP.

[0075] Specifically, after receiving the vBGP announcement containing the Class 3 route of the VTEP of the OVS host, the SDNGW establishes a new tunnel with IP1 as the Tunnel source ip and the VTEP IP of the OVS host as the Tunnel destination ip.

[0076] As can be seen from the above, when the traffic of the virtual machine on the OVS host needs to go to the external network, since the flow table has been changed according to the new VTEP IP on the SDNGW, and the remote end of the tunnel is the IP on the normal SDNGW, the traffic can only go to the normal SDNGW for decapsulation; when the traffic returns to the OVS virtual machine from the SDNGW, since only one evpn edge group IP can be effective on the device, the original VTEP IP on the SDNGW is no longer effective, and IP1 is effective, so the source of the tunnel is IP1 when the traffic returns to the OVS. The entire service traffic goes through the new tunnel, and the influence of the faulty device is completely isolated.

[0077] When the faulty device recovers, the user can cancel the isolation and continue to use the dual-active gateway. When the isolation is cancelled, the controller deletes the temporarily added VTEP IP1 and continues to use the original dual-active VTEP IP. The original VTEP IP is issued to the dual-active gateway, and then the other processes are processed as before the isolation.

[0078] For example, refer to Figure 3 Fig. 1 shows a structure schematic diagram of a fault processing device provided by an embodiment of the present application, which is applied to a controller. The networking of the controller includes a gateway set of at least two gateways for load sharing, and each gateway of the gateway set uses a first IP address. The device includes:

[0079] A first sending unit 30 is configured to issue a second IP address to a second gateway in the gateway set except the first gateway when detecting that the first gateway in the gateway set fails.

[0080] A second sending unit 31 is configured to send a route announcement carrying an OVS host IP address to the second gateway and receive a route announcement carrying the second IP address sent by the second gateway.

[0081] An updating unit 32 is configured to update a tunnel destination IP address of a table item with the tunnel destination IP address being the first IP address on the OVS host to the second IP address.

[0082] Optionally, when a second IP address is assigned to a second gateway in the gateway set other than the first gateway upon detecting failure of the first gateway in the gateway set, the first sending unit 30 is specifically configured to:

[0083] prompting a user to input a second IP address after detecting disconnection of a connection with the first gateway in the gateway set;

[0084] assigning, based on the second IP address input by the user, a configuration carrying the second IP address to the second gateway.

[0085] Optionally, when the tunnel destination IP address of the table entry with the tunnel destination IP address being the first IP address on the OVS host is updated to the second IP address, the updating unit 32 is specifically configured to:

[0086] sending an OVS flow table modification instruction to the OVS host, so that the OVS host updates the tunnel destination IP address of the table entry with the tunnel destination IP address being the first IP address in the local flow table from the first IP address to the second IP address after receiving the OVS flow table modification instruction.

[0087] Optionally, when the tunnel destination IP address of the table entry with the tunnel destination IP address being the first IP address on the OVS host is updated to the second IP address, the updating unit 32 is specifically configured to:

[0088] sending an OVS flow table for replacing the table entry with the tunnel destination IP address being the first IP address on the OVS host to the OVS host, so that the OVS host replaces the table entry with the tunnel destination IP address being the first IP address in the local flow table with the OVS flow table after receiving the OVS flow table.

[0089] Optionally, the apparatus further comprises:

[0090] an isolating unit configured to isolate the failed first gateway.

[0091] The above units can be one or more integrated circuits configured to implement the above methods, for example, one or more Application Specific Integrated Circuits (ASICs), or one or more Digital Signal Processors (DSPs), or one or more Field Programmable Gate Arrays (FPGAs), etc. For example, when a certain unit above is implemented in the form of a processing element scheduling program code, the processing element can be a general-purpose processor, such as a Central Processing Unit (CPU) or other processor that can invoke program code. For another example, the units can be integrated together to implement a system-on-a-chip (SOC).

[0092] Further, the fault processing apparatus provided by the embodiments of the present application is from the hardware layer, and a hardware architecture diagram of the fault processing apparatus can be seen from FIG. 1. Figure 4 As shown in FIG. 1, the fault processing apparatus can include a memory 40 and a processor 41.

[0093] The memory 40 is configured to store program instructions, and the processor 41 invokes the program instructions stored in the memory 40 to execute the above method embodiments according to the obtained program instructions. The specific implementation and technical effects are similar, and will not be repeated here.

[0094] Optionally, the present application also provides a controller including at least one processing element (or chip) for executing the above method embodiments.

[0095] Optionally, the present application also provides a program product, for example, a computer readable storage medium, which stores computer executable instructions for causing the computer to execute the above method embodiments.

[0096] Here, the machine readable storage medium can be any electronic, magnetic, optical, or other physical storage apparatus, which can contain or store information, such as executable instructions, data, etc. For example, the machine readable storage medium can be a RAM (Random Access Memory), a volatile memory, a non-volatile memory, a flash memory, a storage drive (such as a hard disk drive), a solid state drive, any type of storage disc (such as an optical disc, a DVD, etc.), or similar storage medium, or a combination thereof.

[0097] The systems, apparatuses, modules, or units disclosed 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, and the specific form of the computer can be a personal computer, a laptop computer, a cellular phone, a camera phone, a smart phone, a personal digital assistant, a media player, a navigation device, an email device, a game console, a tablet computer, a wearable device, or a combination of any of these devices.

[0098] For the convenience of description, the above apparatuses are described in various units according to functions in the description. Of course, the functions of the units can be implemented in one or more software and / or hardware in the implementation of the present application.

[0099] Those skilled in the art should understand that the embodiments of the present application can be provided as a method, a system, or a computer program product. Therefore, the present application can take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware aspects. Moreover, the embodiments of the present 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.

[0100] The present application is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to the embodiments of the present application. It should be understood that each flow and / or block in the flowcharts and / or block diagrams, and the combination of the flows and / or blocks in the flowcharts 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, a special-purpose computer, an embedded processor, or other programmable data processing apparatus to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing apparatus produce the functions described in the flowcharts and / or block diagrams for implementing the flows and / or blocks in the flowcharts and / or block diagrams. Figure 1 The functions specified in one or more flows and / or blocks Figure 1 The apparatus that performs the functions specified in one or more flows and / or blocks.

[0101] Moreover, these computer program instructions can also be stored in a computer-readable memory capable of directing the computer or other programmable data processing apparatus to work in a specific manner, so that the instructions stored in the computer-readable memory produce a product including instruction apparatus, which implements the functions described in the flowcharts and / or block diagrams for implementing the flows and / or blocks in the flowcharts and / or block diagrams. Figure 1 The functions specified in one or more flows and / or blocks Figure 1 The apparatus that performs the functions specified in one or more flows and / or blocks.

[0102] These computer program instructions can also be loaded into a computer or other programmable data processing devices, so that a series of operation steps are performed on the computer or other programmable data processing devices to generate computer-implemented processes, thus the instructions executed on the computer or other programmable data processing devices provide processes for implementing the functions specified in the flow Figure 1 one flow or multiple flows and / or blocks Figure 1 one block or multiple blocks.

[0103] The above only the preferred embodiment of the present application, and not to limit the present application, any modification, equivalent replacement, improvement, etc. made within the spirit and principles of the present application, should be included within the scope of the present application.

Claims

1. A failure handling method characterized by, The method is applied to a controller, the controller is applied to a networking including at least two gateway sets for load sharing, each gateway in the gateway set is assigned a first IP address, and the method comprises the following steps: When detecting a failure of a first gateway in the gateway set, a second IP address is assigned to a second gateway in the gateway set except the first gateway; A route announcement carrying an OVS host IP address is sent to the second gateway, and a route announcement carrying the second IP address sent by the second gateway is received; A tunnel destination IP address of a table item with a tunnel destination IP address being the first IP address on the OVS host is updated to the second IP address.

2. The method of claim 1, wherein, When detecting a failure of a first gateway in the gateway set, a second IP address is assigned to a second gateway in the gateway set except the first gateway, and the step comprises the following steps: After detecting a disconnection with the first gateway in the gateway set, a user is prompted to input a second IP address; Based on the second IP address input by the user, a configuration carrying the second IP address is assigned to the second gateway.

3. The method of claim 1, wherein, The step of updating the tunnel destination IP address of the table item with the tunnel destination IP address being the first IP address on the OVS host to the second IP address comprises the following steps: An OVS flow table modification instruction is sent to the OVS host, so that the OVS host updates the tunnel destination IP address of the table item with the tunnel destination IP address being the first IP address in the local flow table from the first IP address to the second IP address after receiving the OVS flow table modification instruction.

4. The method of claim 1, wherein, The step of updating the tunnel destination IP address of the table item with the tunnel destination IP address being the first IP address on the OVS host to the second IP address comprises the following steps: An OVS flow table for replacing the table item with the tunnel destination IP address being the first IP address on the OVS host is sent to the OVS host, so that the OVS host replaces the table item with the tunnel destination IP address being the first IP address in the local flow table with the OVS flow table after receiving the OVS flow table.

5. The method of claim 1, wherein, The method further comprises the following steps: The failed first gateway is isolated.

6. A failure handling apparatus characterized by comprising: The method is applied to a controller, the controller is applied to a networking including at least two gateway sets for load sharing, each gateway in the gateway set is assigned a first IP address, and the method comprises the following steps: A first sending unit is configured to assign a second IP address to a second gateway in the gateway set except a first gateway in the gateway set when detecting a failure of the first gateway; A second sending unit is configured to send a route announcement carrying an OVS host IP address to the second gateway, and receive a route announcement carrying the second IP address sent by the second gateway; An updating unit is configured to update a tunnel destination IP address of a table item with the tunnel destination IP address being the first IP address on the OVS host to the second IP address.

7. The apparatus of claim 6, wherein, When assigning a second IP address to a second gateway in the gateway set except a first gateway in the gateway set when detecting a failure of the first gateway, the first sending unit is specifically configured to prompting a user to input a second IP address after detecting that the connection between the first gateway in the gateway set is disconnected; based on the second IP address input by the user, issuing a configuration carrying the second IP address to the second gateway.

8. The apparatus of claim 6, wherein, When updating the tunnel destination IP address of the table entry with the tunnel destination IP address being the first IP address on the OVS host to the second IP address, the updating unit is specifically configured to: send an OVS flow table modification instruction to the OVS host, so that the OVS host updates the tunnel destination IP address of the table entry with the tunnel destination IP address being the first IP address in the local flow table from the first IP address to the second IP address after receiving the OVS flow table modification instruction.

9. The apparatus of claim 6, wherein, When updating the tunnel destination IP address of the table entry with the tunnel destination IP address being the first IP address on the OVS host to the second IP address, the updating unit is specifically configured to: send an OVS flow table for replacing the table entry with the tunnel destination IP address being the first IP address on the OVS host to the OVS host, so that the OVS host replaces the table entry with the tunnel destination IP address being the first IP address in the local flow table with the OVS flow table after receiving the OVS flow table.

10. The apparatus of claim 6, wherein, The device further comprises: an isolating unit configured to isolate the first gateway in failure.

Images