CN115037602A

CN115037602A - Fault processing method and device

Info

Publication number: CN115037602A
Application number: CN202210379132.4A
Authority: CN
Inventors: 陈禄建
Original assignee: New H3C Technologies Co Ltd
Current assignee: New H3C Technologies Co Ltd
Priority date: 2022-04-12
Filing date: 2022-04-12
Publication date: 2022-09-09

Abstract

The present application relates to the field of network communication technologies, and in particular, to a method and an apparatus for processing a fault. The method is applied to a controller, the networking managed by the controller comprises 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 a first gateway in the gateway set is detected to be in fault, issuing a second IP address to a second gateway except the first gateway in the gateway set; sending a route advertisement carrying an OVS host IP address to the second gateway, and receiving the route advertisement carrying the second IP address sent by the second gateway; and updating the tunnel destination IP address of the table entry of which the tunnel destination IP address is the first IP address on the OVS host computer into the second IP address.

Description

Fault processing method and device

Technical Field

The present application relates to the field of network communication technologies, and in particular, to a method and an apparatus for processing a fault.

Background

In some networking, a dual-active gateway scheme is used, for example, the SDNGW is a dual-active VXLAN gateway, gateway load sharing is realized, two SDNGWs share the same MAC and gateway address, serve as a south-north VXLAN gateway of a VNF (virtual machine), and are automatically issued by an SDN controller. When one of the GWs fails, the traffic may not sense the handover, thereby avoiding the impact of a single point of failure on the network.

In practical application, when the controller detects that a southbound device fails (mainly shown that the device state of a nanotube on the controller is inactive, which may be caused by flow failure, openflow connection failure, netconf connection failure, and the like), when configuration needs to be issued to the failed device, the configuration is issued to all devices and fails, and meanwhile, an error is reported to the northbound (VIM, mano) of the controller, so that the VIM and the mano in the northbound direction are notified to stop a service deployment process. The main purposes of this function are: when the device has failed, the configuration will be failed to issue, and if the upper-layer application VIM and mano as the controller cannot sense and continue to complete the service deployment process, it is determined that the flow is affected by the failure of the configuration issue. With the function, the upper layer application can be informed to stop the service deployment process in time to troubleshoot problems.

However, the fault device isolation only solves the problem of configuration delivery failure, and the device fault conditions may be divided into multiple cases. When a link between a failed gateway and a controller is disconnected, the controller detects the gateway failure, and the port up of the gateway still has hash on the gateway at this time, and at this time, there is still a situation that the port up of the gateway cannot forward the traffic, and at this time, the traffic is lost.

Disclosure of Invention

The application provides a fault processing method and device, which are used for solving the problem of flow loss in the prior art.

In a first aspect, the present application provides a fault handling method applied to a controller, where a networking managed by the controller includes a gateway set including at least two gateways for load sharing, where each gateway included in the gateway set uses a first IP address, the method includes:

when a first gateway in the gateway set is detected to be in fault, issuing a second IP address to a second gateway except the first gateway in the gateway set;

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

and updating the tunnel destination IP address of the table entry of which the tunnel destination IP address is the first IP address on the OVS host computer into the second IP address.

Optionally, when a failure of a first gateway in the gateway set is detected, the step of issuing a second IP address to a second gateway in the gateway set except the first gateway includes:

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

and issuing the configuration carrying the second IP address to the second gateway based on the second IP address input by the user.

Optionally, the step of updating the tunnel destination IP address of the entry whose tunnel destination IP address is the first IP address on the OVS host to the second IP address includes:

and 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 of which the tunnel destination IP address is the first IP address in the local flow table into the second IP address from the first IP address after receiving the OVS flow table modification instruction.

and sending an OVS flow table used for replacing the table entry with the tunnel destination IP address as 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 as the first IP address in the local flow table with the OVS flow table after receiving the OVS flow table.

Optionally, the method further comprises:

isolating the failed first gateway.

In a second aspect, the present application provides a fault handling apparatus applied to a controller, where a networking managed by the controller includes a gateway set including at least two gateways for load sharing, where each gateway included in the gateway set uses a first IP address, the apparatus includes:

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

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

and the updating unit is used for updating the tunnel destination IP address of the table entry of which the tunnel destination IP address is the first IP address on the OVS host computer into the second IP address.

Optionally, when a failure of a first gateway in the gateway set is detected and a second IP address is issued to a second gateway in the gateway set except the first gateway, the first sending unit is specifically configured to:

Optionally, when the tunnel destination IP address of the entry whose tunnel destination IP address is the first IP address on the OVS host is updated to the second IP address, the updating unit is specifically configured to:

and sending an OVS flow table modifying instruction to the OVS host, so that the OVS host updates the tunnel destination IP address of the table entry of which the tunnel destination IP address is 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 modifying instruction.

Optionally, the apparatus further comprises:

and the isolation unit is used for isolating the first gateway with the fault.

In a third aspect, an embodiment of the present application provides a fault handling apparatus, including:

a memory for storing program instructions;

a processor for calling the program instructions stored in the memory and executing the steps of the method according to any one of the above first aspect in accordance with the obtained program instructions.

In a fourth aspect, 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 above first aspects.

In summary, the fault handling method provided in the embodiment of the present application is applied to a controller, where a networking managed by the controller includes a gateway set including at least two gateways for load sharing, where each gateway included in the gateway set uses a first IP address, and the method includes: when a first gateway in the gateway set is detected to be in fault, issuing a second IP address to a second gateway except the first gateway in the gateway set; sending a route advertisement carrying an OVS host IP address to the second gateway, and receiving the route advertisement carrying the second IP address sent by the second gateway; and updating the tunnel destination IP address of the table entry of which the tunnel destination IP address is the first IP address on the OVS host computer into the second IP address.

By adopting the fault processing method provided by the embodiment of the application, after the fault of any gateway in the gateway set is detected, new IP addresses are configured to other normal gateways, so that the other normal gateways can establish a tunnel with an OVS host based on the new IP addresses, the service flow can be quickly recovered, and the original service and the new service are not influenced. The whole network service can continue to run unaffected during the period of replacing or repairing the fault equipment by the user.

Drawings

In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings required to be used in the embodiments of the present application or the technical solutions in the prior art are briefly described below, it is obvious that the drawings in the following description are only some embodiments described in the present application, and other drawings can be obtained by those skilled in the art according to the drawings of the embodiments of the present application.

Fig. 1 is a detailed flowchart of a fault handling method according to an embodiment of the present application;

fig. 2 is a detailed flowchart of another fault handling method provided in an embodiment of the present application;

fig. 3 is a schematic structural diagram of a fault handling apparatus according to an embodiment of the present application;

fig. 4 is a schematic structural diagram of another fault handling apparatus according to an embodiment of the present application.

Detailed Description

The terminology used in the embodiments of the present application is for the purpose of describing particular embodiments only and is not intended to be limiting of the application. As used in this application and the claims, the singular forms "a", "an", and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It should also be understood that the term "and/or" as used herein is meant to encompass any and all possible combinations of one or more of the associated listed items.

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

Illustratively, referring to fig. 1, a detailed flowchart of a fault handling method provided in this embodiment is shown, where the method is applied to a controller, a networking managed by the controller includes a gateway set of at least two gateways for load sharing, and each gateway included in the gateway set uses a first IP address, and the method includes the following steps:

step 100: and when the failure of a first gateway in the gateway set is detected, issuing a second IP address to a second gateway except the first gateway in the gateway set.

In the embodiment of the application, when the controller detects any gateway fault, the controller isolates the gateway with the fault.

In this embodiment of the present application, when a failure of a first gateway in the gateway set is detected, and a second IP address is issued to a second gateway in the gateway set except the first gateway, a preferred implementation manner is: prompting a user to input a second IP address after detecting that the connection with the first gateway in the gateway set is disconnected; and issuing the configuration carrying the second IP address to the second gateway based on the second IP address input by the user.

Specifically, a controller (such as an SDN controller) manages gateway devices, and is in communication connection with each gateway device through a management network, and when the controller detects that the communication connection with one gateway is disconnected, it is determined that the gateway has a fault.

In this embodiment, the gateway set may include at least two gateway devices, and each gateway included in the gateway set is used for load sharing, that is, each gateway included in the gateway set shares one IP address and one MAC address.

For example, the gateway set includes a gateway 1 and a gateway 2, the gateway 1 and the gateway 2 load-share and forward the traffic, that is, the OVS host will hash the traffic to the gateway 1 and the gateway 2 respectively through a preset hash algorithm to forward, and the gateway 1 and the gateway 2 share one IP address (e.g., the first IP address) and one MAC address.

Of course, the number of the gateways included in the gateway set may also be multiple (e.g., 3, 4, n), and multiple gateways are used for load sharing, which is not specifically limited in this embodiment of the application.

If the controller detects that the first gateway (e.g., gateway 1) is faulty, a new IP address (e.g., a second IP address) is issued to the gateway 2, and specifically, if the controller detects that the connection with the first gateway is disconnected, the controller prompts the user to input the second IP address, obtains the second IP address input by the user, and carries the second IP address in the configuration and issues the second IP address to the gateway 2.

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

Specifically, the controller and the second gateway advertise a 3-class route, that is, after receiving the second IP address sent by the controller, the second gateway configures the local IP address as the second IP address, and after successful configuration, advertises its own IP address (the second IP address) to the controller in a 3-class route advertising manner, and at the same time, the controller advertises the IP address of the OVS host managed by the controller to the second gateway in a 3-class route manner.

Step 120: and updating the tunnel destination IP address of the table entry of which the tunnel destination IP address is the first IP address on the OVS host computer into the second IP address.

Specifically, in this embodiment of the present application, when the tunnel destination IP address of the entry whose tunnel destination IP address is the first IP address on the OVS host is updated to the second IP address, a preferable implementation manner is as follows: and 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 of which the tunnel destination IP address is the first IP address in the local flow table into the second IP address from the first IP address after receiving the OVS flow table modification instruction.

For example, assuming that the entry whose tunnel destination IP address on the OVS host is the first IP address is entry 1 and entry 2, before the entry is not modified, the tunnel destination IP address of entry 1 and entry 2 is the first IP address, and after the OVS host receives the OVS modification instruction sent by the controller, the tunnel destination IP address of entry 1 and entry 2 is modified from the first IP address to the second IP address.

In this embodiment of the present application, when the tunnel destination IP address of the entry whose tunnel destination IP address is the first IP address on the OVS host is updated to the second IP address, another preferable implementation manner is: and sending an OVS flow table used for replacing the table entry with the tunnel destination IP address as 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 as the first IP address in the local flow table with the OVS flow table after receiving the OVS flow table.

For example, suppose that the entries with the destination IP addresses of the tunnels on the OVS host being the first IP address are entry 1 and entry 2, at this time,

the following describes in detail a process of the fault handling method provided in the embodiment of the present application with reference to a specific application scenario. Exemplarily, referring to fig. 2, a detailed flowchart of a fault handling method provided in an embodiment of the present application includes the following steps:

step 1, isolating fault equipment by a controller.

Specifically, the gateway set includes a plurality of gateway devices, the plurality of gateway devices share the same VTEP IP, and when the controller detects a failure of any one of the gateway devices, the controller isolates the failed device, that is, the failed device is removed from the networking managed by the controller.

For example, when the SDNGW device goes off-line from the controller or other modules of the device fail, causing a failure of a newly added service of the controller, or an abnormal flow of an original service in networking, and after the client checks out the failure of the SDNGW device, the client wants to continue to operate the existing service by using a single SDNGW, so that neither the original service nor the newly added service is affected. Then the customer needs to operate the isolation fault device on the controller at this point.

And 2, issuing a new VTEP IP to normal equipment.

Specifically, the gateway set further includes other gateway devices that work normally, and at this time, the controller issues the VTEP IP reset by the user to the other gateway devices that work normally.

In practice, the faulty device is operationally isolated at the controller, which requests the customer to enter a new VTEP IP (e.g., IP1), while the controller retains the original VTEP IP, except that the original VTEP IP does not originate the device. The controller issues a new VTEP IP to the normal SDNGW device, and after the new VTEP IP is issued to the device, the corresponding configuration is evpn edge group IP 1. In the following process, the normal SDNGW device will tunnel with the OVS host through IP 1.

After the fault equipment is isolated, deleting l2vpn evpn neighbors between vBGP and the fault equipment on the controller so as to avoid the influence of a bgp route sent by the fault equipment.

And step 3, mutually advertising the 3-type route between the SDNGW and the vBGP.

For example, after the evpn edge group IP1 is newly added to the SDNGW, IP1 is advertised to the bgp through a type 3 route. Meanwhile, for the OVS host managed by the controller, the VTEP IP (OVS host IP) is also announced to the SDNGW in a 3-type routing mode through vBGP.

And step 4, the controller modifies the OVS host flow table to enable the remote VTEP IP to be the VTEP IP newly issued on the SDNGW.

And step 5, the OVS host establishes a new tunnel to the normal SDNGW.

Specifically, after receiving the type 3 route notified by the SDNGW, the controller updates the flow table on the OVS host, and implements that the far-end VTEP of the tunnel after encapsulating the vxlan message is IP1 through the flow table. Thereby enabling a new tunnel setup of the OVS host to SDNGW IP 1.

And 6, establishing a tunnel to the OVS host by the SDNGW with the new VTEP IP.

Specifically, after receiving the vBGP advertisement, the SDNGW establishes a new Tunnel by using IP1 as a Tunnel source IP and using the VTEP IP of the OVS host as a Tunnel destination IP after receiving the 3-type route containing the VTEP of the OVS host.

From the above, when the virtual machine flow on the OVS host needs to go to the external network, the flow table is changed according to the new VTEP IP on the SDNGW, and the far end of the tunnel is the IP on the normal SDNGW, so the flow can only go to the normal SDNGW to decapsulate; when the flow returns to the OVS virtual machine from the SDNGW, because only one evpn edge group IP on the equipment takes effect, the original VTEP IP on the SDNGW does not take effect, and the effective IP is IP1, when the flow returns to the OVS, the source of the tunnel is IP 1. The whole service flow is completed by walking a new tunnel, and the influence of the fault equipment is completely isolated.

When the failed 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 once, and then other processes are processed according to isolation.

Exemplarily, referring to fig. 3, a schematic structural diagram of a fault handling apparatus provided in an embodiment of the present application is applied to a controller, where a networking managed by the controller includes a gateway set including at least two gateways for load sharing, and each gateway includes a first IP address, and the apparatus includes:

a first sending unit 30, configured to, when a failure of a first gateway in the gateway set is detected, issue a second IP address to a second gateway in the gateway set except the first gateway;

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

an updating unit 32, configured to update the tunnel destination IP address of the entry whose tunnel destination IP address is the first IP address on the OVS host to the second IP address.

Optionally, when detecting that a first gateway in the gateway set fails, and issuing a second IP address to a second gateway in the gateway set except the first gateway, the first sending unit 30 is specifically configured to:

Optionally, when the tunnel destination IP address of the entry whose tunnel destination IP address is the first IP address on the OVS host is updated to the second IP address, the updating unit 32 is specifically configured to:

Optionally, the apparatus further comprises:

and the isolation unit is used for isolating the first gateway with the fault.

The above units may 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 microprocessors (DSPs), or one or more Field Programmable Gate Arrays (FPGAs), among others. For another example, when one of the above units is implemented in the form of a Processing element scheduler code, the Processing element may be a general-purpose processor, such as a Central Processing Unit (CPU) or other processor capable of calling program code. For another example, these units may be integrated together and implemented in the form of a system-on-a-chip (SOC).

Further, in the fault handling apparatus provided in the embodiment of the present application, from a hardware level, a schematic diagram of a hardware architecture of the fault handling apparatus may be shown in fig. 4, where the fault handling apparatus may include: a memory 40 and a processor 41, which,

memory 40 is used to store program instructions; processor 41 calls program instructions stored in memory 40 and executes the above-described method embodiments in accordance with the obtained program instructions. The specific implementation and technical effects are similar, and are not described herein again.

Optionally, the present application also provides a controller comprising at least one processing element (or chip) for performing the above-described method embodiments.

Optionally, the present application also provides a program product, such as a computer-readable storage medium, having stored thereon computer-executable instructions for causing the computer to perform the above-described method embodiments.

Here, a machine-readable storage medium may be any electronic, magnetic, optical, or other physical storage device that can contain or store information such as executable instructions, data, and so forth. For example, the machine-readable storage medium may be: RAM (random Access Memory), volatile Memory, non-volatile Memory, flash Memory, a storage drive (e.g., a hard drive), a solid state drive, any type of storage disk (e.g., an optical disk, a dvd, etc.), or similar storage medium, or a combination thereof.

The systems, devices, modules or units illustrated in the above embodiments may be implemented by a computer chip or an entity, or by a product with certain functions. A typical implementation device is a computer, which may take the form of a personal computer, laptop computer, cellular telephone, camera phone, smart phone, personal digital assistant, media player, navigation device, email messaging device, game console, tablet computer, wearable device, or a combination of any of these devices.

For convenience of description, the above devices are described as being divided into various units by function, and are described separately. Of course, the functionality of the units may be implemented in one or more software and/or hardware when implementing the present application.

As will be appreciated by one skilled in the art, embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, embodiments of the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.

The present application is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the application. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

Furthermore, these computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

The above description is only exemplary of the present application and should not be taken as limiting the present application, as any modification, equivalent replacement, or improvement made within the spirit and principle of the present application should be included in the scope of protection of the present application.

Claims

1. A method for handling a failure, applied to a controller, wherein a network managed by the controller includes a gateway set of at least two gateways for load sharing, and each gateway included in the gateway set uses a first IP address, the method comprising:

2. The method of claim 1, wherein issuing a second IP address to a second gateway in the set of gateways other than the first gateway upon detecting a failure of the first gateway in the set of gateways comprises:

3. The method of claim 1, wherein the step of updating the tunnel destination IP address of the entry on the OVS host having the tunnel destination IP address as the first IP address to the second IP address comprises:

4. The method of claim 1, wherein the step of updating the tunnel destination IP address of the entry on the OVS host having the tunnel destination IP address as the first IP address to the second IP address comprises:

5. The method of claim 1, wherein the method further comprises:

isolating the failed first gateway.

6. A fault handling apparatus applied to a controller, wherein a network managed by 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, the apparatus comprising:

7. The apparatus of claim 6, wherein when a failure of a first gateway in the gateway set is detected and a second IP address is issued to a second gateway in the gateway set except for the first gateway, the first sending unit is specifically configured to:

8. The apparatus according to claim 6, wherein when the tunnel destination IP address of the entry whose tunnel destination IP address is the first IP address on the OVS host is updated to the second IP address, the updating unit is specifically configured to:

9. The apparatus according to claim 6, wherein when the tunnel destination IP address of the entry whose tunnel destination IP address is the first IP address on the OVS host is updated to the second IP address, the updating unit is specifically configured to:

10. The apparatus of claim 6, wherein the apparatus further comprises:

and the isolation unit is used for isolating the first gateway with the fault.