A flow recovery method and device

Abstract

The present application relates to the field of network communication technology, and in particular to a traffic recovery method and device. The method includes: detecting whether each ED in each fabric network is faulty, and / or detecting whether the uplink connecting each ED to the border device, and / or the downlink connecting each ED to the interconnected switch is faulty; if a target ED in any fabric network is detected to be faulty, and / or an uplink connecting the target ED to the target border device is faulty, and / or a downlink connecting the target ED to the interconnected switch is faulty, then the configuration file of the target ED is sent to the target border device, so that the target border device forwards traffic based on the configuration file.

Description

Technical Field

[0001] The present application relates to the field of network communication technology, and in particular to a flow recovery method and device. Background Art

[0002] SDN (Software Defined Network) is a new type of network architecture. Its core idea is to separate the control layer and forwarding layer of network devices, and centrally and flexibly control network traffic through controllers, thus providing a good platform for innovation of core networks and applications.

[0003] At present, in a multi-fabric network, when configuring the egress gateway for the first time on the controller, it is necessary to select the primary and backup egress gateway members, and determine the primary fabric by setting the priority of the primary and backup egress gateway members. All traffic on the fabrics passes through the corresponding ED (for example, the ED of each fabric network is connected to the border of the fabric network upstream and to the interconnection switch downstream, that is, each ED is interconnected through the interconnection switch), and converges to fabric1 or fabric2 to exit the external network. As for whether the traffic specifically goes through fabric1 or fabric2, it mainly depends on which one is the current primary fabric. All traffic goes out through the current primary fabric. Assuming that fabric1 and fabric2 are in a primary and backup relationship with each other, the backup fabric uses ED to interconnect with the primary fabric, and imports traffic to the primary fabric through ED, and the primary fabric sends it to the external network.

[0004] However, when an ED in any fabric network fails, or the upstream port connecting the ED to the border, or the downstream port connecting the ED to other EDs in other fabric networks fails, it may affect the normal forwarding of east-west traffic or north-south traffic, or all traffic in the multi-fabric network. Summary of the invention

[0005] The present application provides a flow recovery method and device.

[0006] In a first aspect, the present application provides a traffic recovery method, which is applied to a controller, wherein the edge devices ED of each fabric network managed by the controller are respectively communicated with the interconnection switch, and the border devices of each fabric network are respectively communicated with the interconnection switch, and the method includes:

[0007] Detecting whether each ED in each fabric network is faulty, and / or detecting whether an uplink connecting each ED and a border device, and / or a downlink connecting each ED and the interconnection switch is faulty;

[0008] If a target ED failure in any fabric network is detected, and / or an uplink failure between the target ED and the target border device, and / or a downlink failure between the target ED and the interconnected switch is detected, the configuration file of the target ED is sent to the target border device, so that the target border device forwards traffic based on the configuration file.

[0009] Optionally, the method further comprises:

[0010] The detected fault information related to the target ED is sent to the interconnection switch, so that the interconnection switch cancels the routing table entry used to forward the received traffic sent by other EDs to the target ED, wherein after the target border device completes the configuration file of the target ED, the routing table entry used to forward the received traffic sent by other EDs to the target border device is notified to the interconnection switch through BGP.

[0011] Optionally, the controller monitors the status of each ED in real time through an openflow connection established with each ED in each fabric network;

[0012] The steps to detect a target ED failure in any fabric network include:

[0013] If it is monitored that a target ED in any fabric network is in an inactive state for a preset period of time, it is determined that the target ED is faulty.

[0014] Optionally, the controller monitors the link status of the uplink connecting each ED to the corresponding border device and the downlink connecting each ED to the interconnection switch through the openflow connection established between each ED and each border device and the interconnection switch in each fabric network;

[0015] The step of detecting whether an uplink connecting each ED and a border device and / or a downlink connecting each ED and the interconnection switch is faulty comprises:

[0016] If it is monitored that the state of the interface constituting any uplink / downlink becomes down, it is determined that any uplink / downlink fails.

[0017] Optionally, the method further comprises:

[0018] If it is detected that the target ED fails and / or the uplink failure between the target ED and the target border device fails and / or the downlink failure between the target ED and the interconnection switch fails, the configuration file of the target ED is sent to the target ED, so that the target ED forwards traffic based on the configuration file;

[0019] The detected fault recovery information related to the target ED is sent to the interconnection switch, so that the interconnection switch cancels the routing table entry used to forward the received traffic sent by other EDs to the target border device, wherein, after configuring the configuration file of the target ED, the target ED device notifies the interconnection switch through BGP of the routing table entry used to forward the received traffic sent by other EDs to the target ED device.

[0020] In a second aspect, the present application provides a traffic recovery device, which is applied to a controller, wherein the edge devices ED of each fabric network managed by the controller are respectively communicated with the interconnection switch, and the border devices of each fabric network are respectively communicated with the interconnection switch, and the device includes:

[0021] A detection unit, used to detect whether each ED in each fabric network is faulty, and / or detect whether an uplink connecting each ED and a border device, and / or a downlink connecting each ED and the interconnection switch is faulty;

[0022] The sending unit is used to send the configuration file of the target ED to the target border device if the detection unit detects a target ED failure in any fabric network, and / or an uplink failure between the target ED and the target border device, and / or a downlink failure between the target ED and the interconnected switch, so that the target border device forwards traffic based on the configuration file.

[0023] Optionally, the sending unit is further used for:

[0024] The detected fault information related to the target ED is sent to the interconnection switch, so that the interconnection switch cancels the routing table entry used to forward the received traffic sent by other EDs to the target ED, wherein after the target border device completes the configuration file of the target ED, the routing table entry used to forward the received traffic sent by other EDs to the target border device is notified to the interconnection switch through BGP.

[0025] Optionally, the controller monitors the status of each ED in real time through an openflow connection established with each ED in each fabric network;

[0026] When detecting a target ED failure in any fabric network, the detection unit is specifically used to:

[0027] If it is monitored that a target ED in any fabric network is in an inactive state for a preset period of time, it is determined that the target ED is faulty.

[0028] Optionally, the controller monitors the link status of the uplink connecting each ED to the corresponding border device and the downlink connecting each ED to the interconnection switch through the openflow connection established between each ED and each border device and the interconnection switch in each fabric network;

[0029] When detecting whether an uplink connecting each ED and a border device, and / or a downlink connecting each ED and the interconnection switch is faulty, the detection unit is specifically used to:

[0030] If it is monitored that the state of the interface constituting any uplink / downlink becomes down, it is determined that any uplink / downlink fails.

[0031] Optionally, if the detection unit detects that the target ED has recovered from a fault, and / or the uplink fault between the target ED and the target border device has recovered from a fault, and / or the downlink fault between the target ED and the interconnection switch has recovered from a fault, the sending unit is further configured to send a configuration file of the target ED to the target ED, so that the target ED forwards traffic based on the configuration file;

[0032] The sending unit is further used to send the detected fault recovery information related to the target ED to the interconnected switch, so that the interconnected switch cancels the routing table entry used to forward the received traffic sent by other EDs to the target border device, wherein, after configuring the configuration file of the target ED, the target ED device notifies the interconnected switch through BGP of the routing table entry used to forward the received traffic sent by other EDs to the target ED device.

[0033] In a third aspect, an embodiment of the present application provides a flow recovery device, the flow recovery device comprising:

[0034] A memory for storing program instructions;

[0035] The processor is used to call the program instructions stored in the memory, and execute the steps of the method as described in any one of the first aspects above according to the obtained program instructions.

[0036] In a fourth aspect, an embodiment of the present application further provides a computer-readable storage medium, wherein the computer-readable storage medium stores computer-executable instructions, and the computer-executable instructions are used to enable the computer to execute the steps of the method described in any one of the first aspects above.

[0037] In summary, the traffic recovery method provided in the embodiment of the present application is applied to a controller, and the edge devices ED of each fabric network managed by the controller are respectively communicated with the interconnection switch, and the border devices of each fabric network are respectively communicated with the interconnection switch. The method includes: detecting whether each ED in each fabric network is faulty, and / or detecting whether the uplink connecting each ED to the border device, and / or the downlink connecting each ED to the interconnection switch is faulty; if a target ED failure in any fabric network is detected, and / or an uplink failure connecting the target ED to the target border device, and / or a downlink failure connecting the target ED to the interconnection switch is detected, then the configuration file of the target ED is sent to the target border device, so that the target border device forwards traffic based on the configuration file.

[0038] By adopting the traffic recovery method provided in the embodiment of the present application, a communication link is established between the border device and the interconnected switch in each fabric network. When an ED failure of any fabric network / an uplink failure between ED and the border device / a downlink failure between ED and the interconnected switch is detected, the border device assumes the function of ED by sending the ED configuration to the border device, thereby realizing rapid recovery of traffic, avoiding interruption of departmental / all traffic due to failure, and improving network stability. BRIEF DESCRIPTION OF THE DRAWINGS

[0039] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings required for use in the embodiments of the present application or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments recorded in this application. For ordinary technicians in this field, other drawings can also be obtained based on these drawings of the embodiments of the present application.

[0040] Figure 1 A multi-fabric networking diagram provided for related technologies;

[0041] Figure 2A detailed flow chart of a flow recovery method provided in an embodiment of the present application;

[0042] Figure 3 A schematic diagram of a multi-fabric network provided in an embodiment of the present application;

[0043] Figure 4 A schematic diagram of the structure of a flow recovery device provided in an embodiment of the present application;

[0044] Figure 5 A schematic diagram of the structure of another flow recovery device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0045] The terms used in the embodiments of the present application are only for the purpose of describing specific embodiments, rather than limiting the present application. The singular forms of "a", "said" and "the" used in the present application and claims are also intended to include plural forms, unless the context clearly indicates other meanings. It should also be understood that the term "and / or" used herein refers to any or all possible combinations of one or more associated listed items.

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

[0047] Purpose of multiple fabrics: From the perspective of construction, one computer room was built at the beginning, and then another computer room was built. The two computer rooms have their own spines, leaves, and gateways. The two computer rooms have interconnection requirements. From the perspective of fault domain isolation, the two racks in the computer room are too far away, or the computer room itself is too far away, and the network cable is too expensive, so it is impossible to ensure that all leaves and spines are connected in full mesh. It is hoped that each rack has a set of resources, and the racks can be seamlessly connected.

[0048] For example, see Figure 1As shown in the figure, it is a multi-fabric networking diagram provided by the related technology. All the traffic on the fabrics goes out through the corresponding ED and converges to fabric1 or fabric2 to go out to the external network. As for whether the traffic goes through fabric1 or fabric2, it mainly depends on which one is the current master fabric. All the traffic goes out through the current master fabric. As shown in the figure, fabric1 and fabric2 are in a master-slave relationship with each other. All other fabrics use ED to interconnect with the master fabric and direct the traffic to the master fabric through ED.

[0049] For example, fabric1 includes gateway (FW1), Border device (border1), Leaf device (Leaf1), ED1, VM1 accesses the network via Leaf1, ED1 is connected to the interconnection exchange communication, and FW1 is connected to the external Internet via Router; similarly, fabric1 includes gateway (FW2), Border device (border2), Leaf device (Leaf2), ED2, VM2 accesses the network via Leaf2, ED2 is connected to the interconnection exchange communication, and FW2 is connected to the external Internet via Router.

[0050] If fabric1 is the active fabric and fabric2 is the standby fabric, the traffic from VM2 to the Internet is sent to the interconnection switch via ED2 included in fabric2. The interconnection switch forwards the traffic received from ED2 to ED1, which is finally forwarded to the Router via border1 and FW1. The Router forwards the traffic to the Internet. However, when ED1 or ED2 fails in the fabric networking, the uplink (link 1) between ED1 and border1, the downlink (link 2) between ED1 and the interconnection switch, the uplink (link 4) between ED2 and border2, and the downlink (link 3) between ED2 and the interconnection switch fail, part or all of the traffic will be interrupted. For example, if link 2 or link 3 fails, the traffic between fabric1 and fabric2 will be interrupted. If fabric1 is the active fabric, the traffic related to VM2 cannot be sent to the external network.

[0051] For example, see Figure 2 As shown, it is a detailed flow chart of a traffic recovery method provided by an embodiment of the present application. The method is applied to a controller, and the edge devices ED of each fabric network managed by the controller are respectively communicated with the interconnection switch, and the border devices of each fabric network are respectively communicated with the interconnection switch. The method includes the following steps:

[0052] Step 200: Detect whether each ED in each fabric network is faulty, and / or detect whether an uplink connecting each ED and a border device, and / or a downlink connecting each ED and the interconnection switch is faulty.

[0053] In the present application, see Figure 3 As shown in FIG. 1 , a schematic diagram of a multi-fabric network provided in an embodiment of the present application is shown in FIG. Figure 1 Based on the networking of , in each fabric networking, add the connection between border and interconnection switch, that is, add the connection between border1 and interconnection switch, and the connection between border2 and interconnection switch. The role of interconnection switch is to make border1, border2, ED1, ED2 (more fabric EDs are similar) fully interconnected, underlay is manually configured, and basic traffic can pass.

[0054] In the embodiment of the present application, the controller manages each device in the fabric network and manages the interconnected switches. The controller establishes an openflow connection with each ED device, border device and interconnected switch. The controller can monitor the operating status of each device / link through the openflow connection established with each device.

[0055] Step 210: If a target ED failure in any fabric network is detected, and / or an uplink failure between the target ED and the target border device, and / or a downlink failure between the target ED and the interconnected switch is detected, the configuration file of the target ED is sent to the target border device, so that the target border device forwards traffic based on the configuration file.

[0056] In an embodiment of the present application, the controller monitors the status of each ED in real time through an openflow connection established between the controller and each ED in each fabric network. Therefore, when detecting whether each ED in each fabric network is faulty, a preferred implementation method is to determine that the target ED in any fabric network is faulty if it is monitored that the target ED in any fabric network is in an inactive state for a preset period of time.

[0057] Specifically, the controller and the ED device monitor the status of the ED device in real time through the established openflow connection. When the ED device is in the inactive state for a certain period of time, it can be considered that the device has failed. At this time, the controller sends the configuration file of the target ED to the target border device, so that the target border device forwards traffic based on the configuration file.

[0058] That is to say, when an ED device failure is detected, the border device directly connected to it (the border device in the same fabric networking) can assume the roles of both border and ED at the same time, and the faulty ED device is discarded to prevent possible residual configuration on the ED from affecting traffic diversion. At the same time, the controller sends down the configuration fragment (the configuration file of the faulty ED) to make the interface between the border and the interconnected switch UP. Afterwards, the controller takes back the configuration originally sent to the faulty ED. Of course, when the ED device status is inactive, the configuration cannot be deleted, but the configuration of the faulty ED cached in the controller memory must be deleted. Afterwards, the controller will send down both the border and ED configurations to the existing border, realizing the role change from border to border / ED integration. The border role is changed to border / ED integration. The interconnected switch can forward the traffic sent by ED devices in other fabric networking to the border device.

[0059] In the embodiment of the present application, the controller monitors the link status of the uplink connecting each ED to the corresponding border device and the downlink connecting each ED to the interconnected switch through the openflow connection established between each ED and each border device and the interconnected switch in each fabric network. Then, when detecting whether the uplink connecting each ED to the border device and / or the downlink connecting each ED to the interconnected switch is faulty, a preferred implementation method is to determine that any uplink / downlink is faulty if it is monitored that the state of the interface constituting any uplink / downlink becomes down.

[0060] In actual applications, when pre-configuring the controller, based on the actual networking, the ED upstream interface (the interface connected to the border) and downstream interface (the interface connected to the interconnected switch) are specified. In this way, the controller can monitor the interfaces on the ED, border, and interconnected switches through the openflow protocol, and use the comprehensive information to determine the up / down status of the ED upstream and downstream interfaces. When the upstream or downstream port of the ED device fails or the connection is disconnected, causing the port status to be down, the device will send the interface status change through openflow. At this time, the controller senses the status change of the upstream or downstream port of the ED device and starts the border switching process to the border / ED unified process.

[0061] In the embodiment of the present application, the above-mentioned flow recovery method may further include the following steps:

[0062] The detected fault information related to the target ED is sent to the interconnection switch, so that the interconnection switch cancels the routing table entry used to forward the received traffic sent by other EDs to the target ED, wherein after the target border device completes the configuration file of the target ED, the routing table entry used to forward the received traffic sent by other EDs to the target border device is notified to the interconnection switch through BGP.

[0063] Specifically, when each ED device is operating normally, the ED device will notify the interconnected switch through BGP of the routing table entries used to forward the traffic received from other EDs to the target ED. Then, when the target ED device fails / the uplink and downlink links fail, the controller can send fault information related to the target ED to the interconnected switch, so that the interconnected switch cancels the routing table entries used to forward the traffic received from other EDs to the target ED.

[0064] Correspondingly, after the target border device carries the target ED device function, the routing table entry for forwarding the received traffic sent by other EDs to the target border device can be notified to the interconnection switch through BGP.

[0065] Further, if it is detected that the target ED fails and / or the uplink failure of the target ED connected to the target border device fails and / or the downlink failure of the target ED connected to the interconnection switch fails, the configuration file of the target ED is sent to the target ED, so that the target ED forwards traffic based on the configuration file;

[0066] The detected fault recovery information related to the target ED is sent to the interconnection switch, so that the interconnection switch cancels the routing table entry used to forward the received traffic sent by other EDs to the target border device, wherein, after configuring the configuration file of the target ED, the target ED device notifies the interconnection switch through BGP of the routing table entry used to forward the received traffic sent by other EDs to the target ED device.

[0067] That is to say, when the ED device or the uplink and downlink links in the network are repaired, the ED device will send the ED device status and port status through the openflow protocol. After the controller detects that the ED device or the corresponding connection port is UP, it will automatically go through the switching process. The current border / ED device is switched to a border device, and the ED device that is under repair is used as an ED device. Specifically, the controller deletes all configurations on the current border / ED device; then, according to the role after switching, the corresponding configurations are issued to the border and ED respectively; finally, the system log is printed to prompt the user that the border and the interconnected switch are down, and the role has been switched and the configuration has been issued. In this way, after the faulty device or link is restored, the traffic is quickly restored.

[0068] For example, see Figure 4 As shown, it is a structural schematic diagram of a flow recovery device provided in an embodiment of the present application. The device is applied to a controller, and the edge devices ED of each fabric network managed by the controller are respectively connected to the interconnection switch for communication, and the border devices of each fabric network are respectively connected to the interconnection switch for communication. The device includes:

[0069] The detection unit 40 is used to detect whether each ED in each fabric network is faulty, and / or detect whether the uplink connecting each ED and the border device, and / or the downlink connecting each ED and the interconnection switch is faulty;

[0070] The sending unit 41, if the detection unit 40 detects a target ED failure in any fabric network, and / or an uplink failure between the target ED and the target border device, and / or a downlink failure between the target ED and the interconnected switch, then the sending unit 41 is used to send the configuration file of the target ED to the target border device, so that the target border device forwards traffic based on the configuration file.

[0071] Optionally, the sending unit 41 is further configured to:

[0072] The detected fault information related to the target ED is sent to the interconnection switch, so that the interconnection switch cancels the routing table entry used to forward the received traffic sent by other EDs to the target ED, wherein after the target border device completes the configuration file of the target ED, the routing table entry used to forward the received traffic sent by other EDs to the target border device is notified to the interconnection switch through BGP.

[0073] Optionally, the controller monitors the status of each ED in real time through an openflow connection established with each ED in each fabric network;

[0074] When detecting a target ED failure in any fabric network, the detection unit 40 is specifically used to:

[0075] If it is monitored that a target ED in any fabric network is in an inactive state for a preset period of time, it is determined that the target ED is faulty.

[0076] Optionally, the controller monitors the link status of the uplink connecting each ED to the corresponding border device and the downlink connecting each ED to the interconnection switch through the openflow connection established between each ED and each border device and the interconnection switch in each fabric network;

[0077] When detecting whether an uplink connecting each ED and a border device, and / or a downlink connecting each ED and the interconnection switch is faulty, the detection unit 40 is specifically used to:

[0078] If it is monitored that the state of the interface constituting any uplink / downlink becomes down, it is determined that any uplink / downlink fails.

[0079] Optionally, if the detection unit detects that the target ED has recovered from a fault, and / or the uplink fault between the target ED and the target border device has recovered from a fault, and / or the downlink fault between the target ED and the interconnection switch has recovered from a fault, the sending unit is further configured to send a configuration file of the target ED to the target ED, so that the target ED forwards traffic based on the configuration file;

[0080] The sending unit 41 is also used to send the detected fault recovery information related to the target ED to the interconnected switch, so that the interconnected switch cancels the routing table entry used to forward the received traffic sent by other EDs to the target border device, wherein, after configuring the configuration file of the target ED, the target ED device notifies the interconnected switch through BGP of the routing table entry used to forward the received traffic sent by other EDs to the target ED device.

[0081] The above units may be one or more integrated circuits configured to implement the above methods, such as one or more application specific integrated circuits (ASIC), or one or more digital singnal processors (DSP), or one or more field programmable gate arrays (FPGA). For another example, when a certain unit above is implemented in the form of a processing element scheduling program code, the processing element may be a general-purpose processor, such as a central processing unit (CPU) or other processors that can call program codes. For another example, these units may be integrated together and implemented in the form of a system-on-a-chip (SOC).

[0082] Furthermore, the flow recovery device provided in the embodiment of the present application, from the hardware level, the hardware architecture diagram of the flow recovery device can be seen in Figure 5 As shown, the flow recovery device may include: a memory 50 and a processor 51,

[0083] The memory 50 is used to store program instructions; the processor 51 calls the program instructions stored in the memory 50 and executes the above method embodiment according to the obtained program instructions. The specific implementation method and technical effect are similar and will not be repeated here.

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

[0085] Optionally, the present application also provides a program product, such as a computer-readable storage medium, which stores computer-executable instructions, and the computer-executable instructions are used to enable the computer to execute the above method embodiments.

[0086] Here, the machine-readable storage medium may be any electronic, magnetic, optical or other physical storage device that may contain or store information, such as executable instructions, data, etc. For example, the machine-readable storage medium may be: RAM (RadomAccess Memory), volatile memory, non-volatile memory, flash memory, storage drive (such as hard disk drive), solid state drive, any type of storage disk (such as CD, DVD, etc.), or similar storage medium, or a combination thereof.

[0087] The systems, devices, modules or units described in the above embodiments may be implemented by computer chips or entities, or by products with certain functions. A typical implementation device is a computer, which may be in the form of 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 transceiver, a game console, a tablet computer, a wearable device or a combination of any of these devices.

[0088] For the convenience of description, the above device is described in various units according to their functions. Of course, when implementing the present application, the functions of each unit can be implemented in the same or multiple software and / or hardware.

[0089] Those skilled in the art will appreciate that the embodiments of the present application may be provided as methods, systems, or computer program products. Therefore, the present application may adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment in combination with software and hardware. Moreover, the embodiments of the present application may adopt 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.) that contain computer-usable program code.

[0090] 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 process and / or box in the flowchart and / or block diagram, as well as the combination of the processes and / or boxes in the flowchart and / or block diagram, 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 device to generate a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0091] Moreover, these computer program instructions can also be stored in a computer-readable memory that can guide a computer or other programmable data processing device to work in a specific manner, so that the instructions stored in the computer-readable memory produce a product including an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 The function specified in one or more boxes.

[0092] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for executing on the computer or other programmable device to implement the process. Figure 1 A process or multiple processes and / or boxes Figure 1 The steps for the functions specified in one or more boxes.

[0093] The above description is only a preferred embodiment of the present application and is not intended to limit the present application. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of the present application shall be included in the scope of protection of the present application.

Claims

1. A flow recovery method, characterized in that: Applied to a controller, the edge devices ED of each fabric network managed by the controller are respectively connected to the interconnection switch in communication, and the border devices of each fabric network are respectively connected to the interconnection switch in communication. The controller monitors the status of each ED in real time through the openflow connection established between each ED in each fabric network; the controller monitors the link status of the uplink connected to each ED and the corresponding border device, and the downlink connected to each ED and the interconnection switch through the openflow connection established between each ED in each fabric network and each border device and the interconnection switch; the method includes: Detecting whether each ED in each fabric network is faulty, and / or detecting whether an uplink connecting each ED and a border device, and / or a downlink connecting each ED and the interconnection switch is faulty; If a target ED failure in any fabric network is detected, and / or an uplink failure between the target ED and the target border device, and / or a downlink failure between the target ED and the interconnection switch is detected, the configuration file of the target ED is sent to the target border device, so that the target border device forwards traffic based on the configuration file; The steps to detect a target ED failure in any fabric network include: If it is detected that the target ED in any fabric network is in an inactive state for a preset period of time, it is determined that the target ED is faulty; The step of detecting whether an uplink connecting each ED and a border device and / or a downlink connecting each ED and the interconnection switch is faulty includes: If it is monitored that the state of the interface constituting any uplink / downlink becomes down, it is determined that any uplink / downlink is faulty; The detected fault information related to the target ED is sent to the interconnection switch, so that the interconnection switch cancels the routing table entry used to forward the received traffic sent by other EDs to the target ED, wherein after the target border device completes the configuration file of the target ED, the routing table entry used to forward the received traffic sent by other EDs to the target border device is notified to the interconnection switch through BGP.

2. The method according to claim 1, characterized in that The method further comprises: If it is detected that the target ED fails and / or the uplink failure between the target ED and the target border device fails and / or the downlink failure between the target ED and the interconnection switch fails, the configuration file of the target ED is sent to the target ED, so that the target ED forwards traffic based on the configuration file; The detected fault recovery information related to the target ED is sent to the interconnection switch, so that the interconnection switch cancels the routing table entry used to forward the received traffic sent by other EDs to the target border device, wherein, after configuring the configuration file of the target ED, the target ED device notifies the interconnection switch through BGP of the routing table entry used to forward the received traffic sent by other EDs to the target ED device.

3. A flow recovery device, characterized in that: Applied to a controller, the edge devices ED of each fabric network managed by the controller are respectively connected to the interconnection switch in communication, and the border devices of each fabric network are respectively connected to the interconnection switch in communication. The controller monitors the status of each ED in real time through the openflow connection established between each ED in each fabric network; the controller monitors the link status of the uplink connected to each ED and the corresponding border device, and the downlink connected to each ED and the interconnection switch through the openflow connection established between each ED in each fabric network and each border device and the interconnection switch; the device comprises: A detection unit, used to detect whether each ED in each fabric network is faulty, and / or detect whether an uplink connecting each ED and a border device, and / or a downlink connecting each ED and the interconnection switch is faulty; The sending unit is used to send the configuration file of the target ED to the target border device if the detection unit detects a target ED failure in any fabric network, and / or an uplink failure between the target ED and the target border device, and / or a downlink failure between the target ED and the interconnection switch, so that the target border device forwards traffic based on the configuration file; When detecting a target ED failure in any fabric network, the detection unit is specifically used to: If it is detected that the target ED in any fabric network is in an inactive state for a preset period of time, it is determined that the target ED is faulty; When detecting whether an uplink connecting each ED and a border device, and / or a downlink connecting each ED and the interconnection switch is faulty, the detection unit is specifically used to: If it is monitored that the state of the interface constituting any uplink / downlink becomes down, it is determined that any uplink / downlink is faulty; The sending unit is also used for: The detected fault information related to the target ED is sent to the interconnection switch, so that the interconnection switch cancels the routing table entry used to forward the received traffic sent by other EDs to the target ED, wherein after the target border device completes the configuration file of the target ED, the routing table entry used to forward the received traffic sent by other EDs to the target border device is notified to the interconnection switch through BGP.

4. The device according to claim 3, characterized in that If the detection unit detects that the target ED has recovered from a fault, and / or the uplink fault between the target ED and the target border device has recovered from a fault, and / or the downlink fault between the target ED and the interconnection switch has recovered from a fault, the sending unit is further configured to send a configuration file of the target ED to the target ED, so that the target ED forwards traffic based on the configuration file; The sending unit is further used to send the detected fault recovery information related to the target ED to the interconnected switch, so that the interconnected switch cancels the routing table entry used to forward the received traffic sent by other EDs to the target border device, wherein, after configuring the configuration file of the target ED, the target ED device notifies the interconnected switch through BGP of the routing table entry used to forward the received traffic sent by other EDs to the target ED device.

Images