CN118101552A - Fault handling method, device, equipment and storage medium - Google Patents
Fault handling method, device, equipment and storage medium Download PDFInfo
- Publication number
- CN118101552A CN118101552A CN202211468549.4A CN202211468549A CN118101552A CN 118101552 A CN118101552 A CN 118101552A CN 202211468549 A CN202211468549 A CN 202211468549A CN 118101552 A CN118101552 A CN 118101552A
- Authority
- CN
- China
- Prior art keywords
- pes
- target
- link
- channel
- forwarding
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L45/00—Routing or path finding of packets in data switching networks
- H04L45/22—Alternate routing
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
- H04L12/46—Interconnection of networks
- H04L12/4641—Virtual LANs, VLANs, e.g. virtual private networks [VPN]
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer Security & Cryptography (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
The application discloses a fault processing method, device, equipment and storage medium, and relates to the technical field of communication. The method is applied to an EVPN multi-homing networking, wherein the EVPN multi-homing networking comprises a CE, a first PE and N second PEs; the CE, the first PE, and the N second PEs are connected to each other, where N is an integer greater than 1, and the method includes: when detecting that a link channel between a first PE for forwarding flow data and a CE breaks down, acquiring an escape channel link table, and determining a target PE from N second PEs according to the escape channel link table; and determining a target link channel for forwarding the flow data according to the target PE, and forwarding the flow data according to the target link channel so as to quickly complete convergence of the flow data.
Description
Technical Field
The present application relates to the field of communications technologies, and in particular, to a fault processing method, apparatus, device, and storage medium.
Background
The ethernet virtual private network (Ethernet Virtual Private Network, EVPN) is a two-layer virtual private network (Virtual Private Network, VPN), the control plane interacts EVPN routing information through a multiprotocol border gateway protocol (Multiprotocol Border Gateway Protocol, MP-BGP), and the data plane may forward the message using MPLS (Multi-Protocol Label Switch, multiprotocol label switching) or VXLAN (Virtual eXtensible Local Area Network, virtual extended local area network).
Currently, ethernet virtual private networks generally operate in a dual homing scenario. As shown in fig. 1, the customer edge device (customer edge equipment, CE) accesses the merchant edge device (provider edge router, PE), PE1 and PE2, and the PE1 and PE2 operate in a single-active mode (or single-active redundancy) mode, i.e., at the same time, only one of the PEs 1 and PE2 is responsible for forwarding the message of the CE1. The PE responsible for forwarding the message of CE1 may be referred to as designated forwarder (DESIGNATED FORWARDER, DF) at this time, and the PE not responsible for forwarding the message of CE1 may be referred to as Non-designated forwarder (Non-DESIGNATED FORWARDER, NDF). When traffic data (or message) is transmitted, the remote CE forwards the traffic data to the PE1 via the remote PE first, and then forwards the traffic data to the destination CE1 via the PE 1. If the link between CE1 and PE1 in FIG. 1 fails, PE1 will switch to the NDF for CE1 and PE2 will switch to the DF for CE1, a process known as the fault tangent process.
If the ethernet virtual private network has multiple paths, multiple traffic forwarding paths are generated, and when the main link fails, how to quickly complete traffic convergence is a problem that needs to be solved at present.
Disclosure of Invention
The application provides a fault processing method which is used for rapidly completing convergence of flow data.
In a first aspect, a fault handling method is provided, where the method is applied to an EVPN multi-homing networking, where the EVPN multi-homing networking includes a CE, a first PE, and N second PEs; the CE, the first PE, and the N second PEs are connected to each other, where N is an integer greater than 1, and the method includes:
When detecting that a link channel between the first PE for forwarding flow data and the CE fails, acquiring an escape channel link table, and determining a target PE from the N second PEs according to the escape channel link table; and determining a target link channel for forwarding the flow data according to the target PE, and forwarding the flow data according to the target link channel.
In one possible implementation manner, before obtaining the escape path link table when the link between the first PE and the CE for the traffic data to be forwarded fails, the method further includes:
Acquiring session state tables corresponding to the first PE and the N second PEs respectively; the session state table comprises source addresses corresponding to the first PE and the N second PEs respectively; determining respective election results of the first PE and the N second PEs according to the source addresses corresponding to the first PE and the N second PEs respectively and the Ethernet segment identifiers connected with the CE; and generating the escape channel link table according to the election results of the first PE and the N second PEs.
In one possible implementation, the first PE has a bidirectional link path with the target PE; the escape channel link table comprises the election results of the first PE and the N second PEs and the priority of each election result; the determining, according to the target PE, a target link path for forwarding the traffic data includes:
Switching the election result of the target PE in the escape link channel table to the election result with the highest priority, closing a link channel of the target PE pointing to the first PE, determining that the target link channel for forwarding the flow data is forwarding the flow data to the target PE through the first PE, and forwarding the flow data to the CE through the target PE.
In one possible implementation manner, after the selecting result of the target PE in the escape link path table is switched to the selecting result with the highest priority, the method further includes:
And switching the link channels pointing to the first PE in the second PE except the target PE to point to the target PE.
In one possible implementation manner, after the forwarding the traffic data according to the target link channel, the method further includes:
triggering the first PE to generate a cancel routing notification; wherein the rerouting notification is used to characterize a failure of a link path of traffic data sent to the CE via the first PE; and when the target PE and the second PE which are remained except the target PE receive the withdrawal route notification, updating the escape channel link table so that the traffic data is not forwarded through the first PE when the traffic data is forwarded next time.
In one possible implementation, the updating the escape route link table includes at least one of:
marking the first PE as invalid, or deleting the first PE in the escape channel link table, the election result of the first PE and the priority of the election result of the first PE; modifying the PE with BDF as a selection result of the N second PEs into DF; and modifying the PE with the NDF as the selection result of the N second PEs into BDF.
In a second aspect, a fault handling device is provided, where the fault handling device is applied to an EVPN multi-homing network, where the EVPN multi-homing network includes a CE, a first PE, and N second PEs; wherein the CE, the first PE, and the N second PEs are connected to each other, N is an integer greater than 1, and the apparatus includes:
The failure detection module is used for acquiring an escape channel link table when detecting that a link channel between the first PE for forwarding flow data and the CE fails, and determining a target PE from the N second PEs according to the escape channel link table; and the fault processing module is used for determining a target link channel for forwarding the flow data according to the target PE, and forwarding the flow data according to the target link channel.
In one possible implementation, the apparatus further includes a generation module;
the generation module is used for acquiring session state tables corresponding to the first PE and the N second PEs respectively; the session state table comprises source addresses corresponding to the first PE and the N second PEs respectively; determining respective election results of the first PE and the N second PEs according to the source addresses corresponding to the first PE and the N second PEs respectively and the Ethernet segment identifiers connected with the CE; and generating the escape channel link table according to the election results of the first PE and the N second PEs.
In a third aspect, there is provided an electronic device comprising:
a memory for storing a computer program; a processor for carrying out the method steps of any one of the first aspects when executing a computer program stored on the memory.
In a fourth aspect, there is provided a computer readable storage medium having stored therein a computer program which, when executed by a processor, carries out the method steps according to any of the first aspects.
In the embodiment of the application, the EVPN multi-homing networking constructed comprises CE, first PE and N (N > 1) second PE, and forms a connection relation with each other, under the multi-homing scene, because when detecting that the link channel between the first PE for forwarding the flow data and the CE has faults, an escape channel link table is obtained, and a target PE is determined from the N second PE according to the escape channel link table, wherein the escape channel link table comprises the respective election results of the first PE and the N second PE, and the priority of each election result, the target link channel for forwarding the flow data is determined according to the target PE, and the flow data is forwarded according to the target link channel, therefore, in the complex link connection relation, an optimal alternative link channel can be quickly locked, the convergence of the flow data can be quickly completed, and the packet loss of the flow data is reduced.
The technical effects of each of the second to fourth aspects and the technical effects that may be achieved by each aspect are referred to above for the technical effects that may be achieved by the first aspect or each possible aspect in the first aspect, and the detailed description is not repeated here.
Drawings
Fig. 1 is a schematic diagram of an application scenario of an existing EVPN-based multi-homing networking;
fig. 2 is a schematic diagram of an application scenario based on EVPN multi-homing networking provided in an embodiment of the present application;
FIG. 3 is a flowchart of a fault handling method according to an embodiment of the present application;
Fig. 4 is a schematic diagram of forwarding traffic data according to an embodiment of the present application;
fig. 5 is a schematic structural diagram of a fault handling apparatus according to an embodiment of the present application;
FIG. 6 is a schematic diagram of another fault handling apparatus according to an embodiment of the present application;
Fig. 7 is a schematic structural diagram of an electronic device according to an embodiment of the present application.
Detailed Description
In order to make the objects, technical solutions and advantages of the present application more apparent, the present application will be further described in detail with reference to the accompanying drawings. The specific method of operation in the method embodiment may also be applied to the device embodiment or the system embodiment. In the description of the present application, "a plurality of" means "at least two". "and/or", describes an association relationship of an association object, and indicates that there may be three relationships, for example, a and/or B, and may indicate: a exists alone, A and B exist together, and B exists alone. A is connected with B, and can be represented as follows: both cases of direct connection of A and B and connection of A and B through C. In addition, in the description of the present application, the words "first," "second," and the like are used merely for distinguishing between the descriptions and not be construed as indicating or implying a relative importance or order.
For a better understanding of the embodiments of the present application, some of the terms in the embodiments of the present application are explained below for easy understanding by those skilled in the art.
(1) An ethernet segment (ETHERNET SEGMENT, ES) refers to a set of ethernet links when a customer premises device (customer site) is connected to one or more PEs over the set of links, the set of links is referred to as an ethernet segment.
(2) An ethernet segment identifier (ETHERNET SEGMENT IDENTIFIER, ESI) that identifies a unique non-zero identifier of the ethernet segment.
(3) The single active redundancy mode refers to when only one PE among all PEs connected to the ES is allowed to assign forwarding traffic data to the ES.
(4) PE is in charge of service access, and completes forwarding of message (or flow data, etc.), for example, the message is sent from one end user network to a public network tunnel, and then sent to the other end user network through the public network tunnel.
(5) An Ethernet Virtual private line service (Ethernet Virtual PRIVATE LINE, EVPL) is generally used in the case where the IDs of the wireless Virtual local area networks of the plurality of users are the same.
(6) The bidirectional forwarding detection (Bidirectional Forwarding Detection, BFD) is a network protocol for detecting faults between two forwarding points, can provide millisecond detection, can realize rapid detection of links, and can realize rapid convergence of routes by linking with an upper layer routing protocol, thereby ensuring the permanence of services. The main working process of BFD is as follows: firstly, BFD establishes a BFD session on a link between two endpoints (established by means of an upper layer protocol, such as neighbor establishment by OSPF, which informs BFD of neighbor information, and BFD reestablishes BFD neighbors based on this information), and if multiple links exist between two endpoints, a BFD session may be established for each link. BFD performs BFD detection between two network nodes that establish a session. Secondly, if the link failure is found, the BFD neighbor is removed, and the upper layer protocol is immediately informed, and then the upper layer protocol immediately performs corresponding switching.
(7) DF may mainly perform the following tasks: multicast and broadcast messages are sent to the CEs, if flooding unknown unicast traffic is allowed, unknown unicast traffic may be sent to the CEs for a certain EVPN instance (EVPN INSTANCE, EVI), known unicast traffic may be sent to the CEs for a certain EVI in single active mode, etc.
(8) The backup forwarder (Backup Designated Forwarder, BDF) may be responsible for taking over the DF behaviour when the DF fails.
(9) The reverse operation of the route advertisement is to tell the neighbor that a destination is not reachable and to delete the corresponding route.
Embodiments of the present application will be described in detail below with reference to the accompanying drawings.
The following description is made for some simple descriptions of application scenarios applicable to the technical solution of the embodiment of the present application, and it should be noted that the application scenarios described below are only used for illustrating the embodiment of the present application, but not limiting. In the specific implementation, the technical scheme provided by the embodiment of the application can be flexibly applied according to actual needs.
Fig. 2 is a schematic diagram of an application scenario based on EVPN multi-homing networking according to an embodiment of the present application. As shown, the scene mainly includes CE a, PE 11, PE 12, PE 13, far-end PE 14, far-end CE B; wherein CE A is connected with PE 11, PE 12, PE 13 respectively, PE 11, PE 12, PE 13, distal PE 14 are connected with each other, distal CE B is connected with distal PE 14. The number of PEs may be greater, and fig. 2 only depicts a scenario with 4 PEs. The devices will be described one by one.
CE a may be configured to receive traffic data from the PEs 11, 12, 13.
The PE 11, the PE 12 and the PE 13 can be configured in a static BFD configuration mode in advance to complete interconnection configuration, so that fault detection can be conveniently carried out on the PE 11, the PE 12 and the PE 13, and further, the method can be used for forwarding flow data from the PE14 and the like. The static BFD configuration mode refers to manually configuring BFD session parameters through a command line, including configuring a local identifier, a remote identifier, and the like, then manually issuing a BFD session establishment request, and finally each PE 11, PE 12, and PE 13 are successfully configured with each other, and generate respective session state tables (also referred to as BFD session state tables), so as to facilitate the subsequent completion of association between the local ES and the EVPN device. As shown in table 1, a session state table of PE 11 is exemplarily shown.
Table 1: PE 11 session state table
In other embodiments, the PE 11, the PE 12, and the PE 13 may be configured by dynamic BFD in advance, so as to complete the interconnection configuration. The dynamic BFD configuration refers to that a local identifier for dynamically establishing BFD is dynamically allocated by a system for triggering the establishment of BFD session, and a remote identifier is obtained by matching and learning after receiving the value of the local identifier carried in the opposite-end BFD message. In the embodiment of the application, the BDF configuration mode among the PEs is not limited.
The remote PE 14, which is accessed by the remote CE B in communication with the CE a, is operable to receive traffic data from the remote CE B and forward the traffic data to any one of the PEs 11, 12, 13. The remote CE B may access one PE or may access multiple PEs, and the embodiment of the present application is not limited herein. If the remote CE B accesses multiple PEs, the remote PE may refer to DF among multiple PEs accessed in the remote CE.
When the PE equipment of the main link fails, in the multi-homing scenario, an error path is easily selected under the condition that the path multipath of the escape link exists, so that traffic data cannot be converged rapidly.
In view of this, in the embodiment of the present application, a fault handling method is provided, in a multi-homing scenario, how to select an optimal escape link channel from a plurality of alternative escape link channels when a main link used for forwarding traffic data fails, so as to quickly complete convergence of the traffic data.
Although embodiments of the present application provide the method operational steps shown in the following embodiments or figures, more or fewer operational steps may be included in the method, either on a routine or non-inventive basis. In steps where there is logically no necessary causal relationship, the execution order of the steps is not limited to the execution order provided by the embodiments of the present application. The method may be performed sequentially or and in accordance with the method shown in the embodiments or drawings when the actual process or apparatus is performed.
Fig. 3 is a flowchart of a fault handling method according to an embodiment of the present application. The method is applied to an EVPN multi-homing networking, wherein the EVPN multi-homing networking can comprise a CE, a first PE and N second PEs; the CE, the first PE and the N second PEs are connected with each other, and N is an integer greater than 1. The flow may be performed by a fault handling device, as shown, the flow comprising the steps of:
301: and when detecting that the link channel between the first PE and the CE for forwarding the flow data fails, acquiring an escape channel link table.
In this step, the first PE may specifically be PE 11 in fig. 2, and the CE may specifically be CE a in fig. 2.
Optionally, the escape route link table may be obtained by: acquiring session state tables corresponding to the first PE and the N second PEs (such as PE 12 and PE 13 in FIG. 2) respectively, and determining Source addresses (Source-addresses) corresponding to the first PE and the N second PEs from the session state tables respectively; determining the election results of the first PE and the N second PEs according to the source addresses corresponding to the first PE and the N second PEs respectively and the Ethernet segment identifiers of the first PE and the N second PEs respectively connected with the CE; and generating an escape channel link table according to the election results of the first PE and the N second PEs.
Alternatively, the election result may include: DF. BDF and NDF.
In some embodiments, determining the election result of each of the first PE and the N second PEs may be performed by: based on Ethernet segment routing, obtaining source addresses of the far-end same ES equipment, sorting the PEs of the multi-homing scene according to the sequence of the source addresses, distributing serial numbers to the PEs according to the sorting, selecting PE (e.g. PE 11) with a beginning serial number from the PEs as DF, selecting PE (e.g. PE 12) with a beginning serial number only inferior to the PE with the beginning serial number as BDF, and selecting PE (e.g. PE 13) with the remaining serial number as NDF, thereby completing election, and further completing the binding of the election result of the multi-homing networking same ES equipment with the state information of the PE equipment. Taking the above PE 11 as an example, table 2 exemplarily shows a table of association between device status information and election results provided in an embodiment of the present application.
Table 2: association table of equipment state information and election result
In other embodiments, the PE with the largest available bandwidth or bandwidth rate may be selected from the first PE and the N second PEs as DF, and so on to obtain the PE with the BDF role and the PE with the NDF role.
Optionally, according to the election results of the first PE and the N second PEs, an escape route link table is generated, specifically by the following manner: different priorities are set for different election results, for example, if the election result of the PE device is DF, the set priority is highest, so that a link channel where the PE device with the election result of DF is a main link channel (also called an optimal link channel), if the election result of the PE device is BDF, the set priority is middle, and if the election result of the PE device is NDF, the set priority is lowest, an escape link channel table is generated, and the follow-up selection of the optimal link channel is facilitated for forwarding flow data. Taking the above-mentioned PE 11, PE 12, and PE 13 in fig. 2 as examples, table 3 exemplarily shows an escape link channel table provided by an embodiment of the present application.
Table 3: escape link channel table
| Name of the name | Source address | Output address | Election result | Priority level |
| PE 11 | 1.1.1.1 | 1::1 | DF | High height |
| PE 12 | 2.2.2.2 | 2::2 | BDF | In (a) |
| PE 13 | 3.3.3.3 | 3::3 | NDF | Low and low |
As can be seen from table 3, the election result of the PE 11 is DF, and the DF has the highest priority, so the PE 11 can play a role of forwarding traffic data, and the link channel is the optimal link channel.
302: After the escape channel link table is obtained, determining a target PE from N second PEs according to the escape channel link table.
In this step, the optimal path (optimal link path) for forwarding the traffic data via the PE 11 (first PE) is known from the above table 3, and the PE 11 is detected as failed and cannot forward the traffic data any more, so that the PE 12 in the above table 3 can be determined as the target PE for completing the traffic data forwarding next according to the priority rule.
Optionally, the first PE and the target PE (PE 12) have a bidirectional link path, which may be preset before the failure occurs, specifically, may further include a link path set by the first PE and other PEs, for example, a unidirectional link path in which the first PE and the PE 13 have the PE 13 pointing to the first PE.
Optionally, determining the target link path for forwarding the traffic data may include the following operations: switching the election result of the target PE in the escape link channel table to the election result with the highest priority (specifically, switching BDF of PE12 to DF), closing the link channel of the target PE pointing to the first PE, preventing the flow data from wrapping back to the first PE, determining that the target link channel for forwarding the flow data is forwarding the flow data to the target PE through the first PE, and forwarding the flow data to CE (shown as CE A in FIG. 2) through the target PE, thereby forming an optimal alternative link channel and rapidly completing convergence of the flow data.
Optionally, after switching the election result of the target PE in the escape link channel table to the election result with the highest priority, the link channels of the second PE remaining except the target PE, which are directed to the first PE, may be further switched to be directed to the target PE, for example, the unidirectional link channel of the PE 13, which is directed to the first PE, is set to be directed to the target PE (PE 12) by the PE 13, so as to ensure that in the single active mode, the CE-side interconnection traffic data of the PE 13 may be reached.
303: And after the target link channel is determined, forwarding the flow data according to the target link channel.
Optionally, after forwarding the traffic data according to the target link channel and completing the fast fault switching, the first PE may be triggered to generate a revocation routing notification, where the revocation routing notification is used to characterize that a link channel of the traffic data sent to the CE via the first PE has a fault; when the target PE and the rest of the second PE receive the route withdrawal notification, the escape channel link table is updated, so that when the traffic data is forwarded next time, the traffic data is forwarded directly according to the redefined link channel without forwarding the traffic data through the first PE, and the forwarding efficiency of the traffic data is improved. Taking the above PE 11, PE 12, PE 13, and far-end PE 14 as examples, the PE 11 sends a withdrawal route notification to the PE 12, PE 13, and far-end PE 14, respectively, and when the PE 12, PE 13, and far-end PE 14 receive the withdrawal route notification, a reselection can be performed to update the escape route link table.
Optionally, the step of updating the escape path link table may be to mark the first PE as invalid in the escape path link table, or delete the first PE in the escape path link table, the election result of the first PE, and the priority of the election result of the first PE; the selection result of the N second PEs may be changed to DF, for example, the selection result of the PE 12 is changed to DF, so that the PE 12 serves as a Designated Forwarder (DF) to forward the next traffic data; and modifying the PE with the NDF as the election result of the N second PEs into BDF, for example, modifying the election result of the PE 13 into BDF, so that the PE 13 is used as a backup repeater (BDF), and when the PE 12 also fails, the PE can be immediately used as an alternative path (alternative link channel) for forwarding the traffic data, thereby completing the rapid convergence of the traffic data and preventing the loss of the traffic packet. Further, after receiving the withdrawal routing notification, the remote PE 14 changes the traffic policy of the primary PE 11, and loads the traffic policy on the PE 12 and/or the PE 13, for example, in some embodiments, the remote PE 14 forwards traffic data from the remote CE to the PE 12 after receiving the traffic data from the remote CE, and then forwards the traffic data from the PE 12 to the CE a; in other embodiments, the remote PE 14 receives traffic data from the remote CE, forwards it to the PE 13, and then forwards it from the PE 13 to the CE a.
In the embodiment of the application, the EVPN multi-homing networking constructed comprises CE, first PE and N (N > 1) second PE, and forms a connection relation with each other, under the multi-homing scene, because when detecting that the link channel between the first PE for forwarding the flow data and the CE has faults, an escape channel link table is obtained, a target PE is determined from the N second PE according to the escape channel link table, a target link channel for forwarding the flow data is determined according to the target PE, and the flow data is forwarded according to the target link channel, therefore, one most alternative link channel can be quickly locked from a complex link connection relation, the convergence of the flow data can be quickly completed, and the packet loss of the flow data is reduced.
Based on the flow shown in fig. 3, taking a three-homing scenario as an example, fig. 4 illustrates a forwarding schematic diagram of traffic data in an EVPN multi-homing network according to an embodiment of the present application. As shown, fig. 4 (a) is a schematic forwarding diagram for characterizing traffic data before failure, where the main link channel 401 is: the remote CE B- & gt remote PE 14- & gt PE 11- & gt CE A, a bidirectional link channel is arranged between PE 11 and PE 12, and a unidirectional link channel is arranged between PE 11 and PE 13. Fig. 4 (b) is a schematic forwarding diagram of traffic data for representing a fault, which is converted from a main link channel 401 to an escape link channel 402: the bidirectional link path between the far end CE b→the far end PE 14→the PE 11→the PE 12→ce a, the bidirectional link path between the PE 11 and the PE 12 becomes the unidirectional link path of the PE 11 directed to the PE 12, and the unidirectional link path of the PE 11 and the PE 13 becomes the unidirectional link path of the PE 13 directed to the PE 12. Fig. 4 (C) is a schematic diagram of forwarding flow data after a fault, and is converted into a dual-return dual-active scenario, where escape link path 403 is a far end CE b→a far end PE 14→pe 12→ce a, and escape link path 404 is a far end CE b→a far end PE 14→pe 13→ce a, and the two-way link path is converted between PE 12 and PE 13.
Based on the same technical conception, the embodiment of the application also provides a structural schematic diagram of the fault processing device.
Fig. 5 is a schematic structural diagram of a fault handling device according to an embodiment of the present application, where the fault handling device is applied to an EVPN multi-homing network, and the EVPN multi-homing network includes a CE, a first PE, and N second PEs; the CE, the first PE and the N second PEs are connected with each other, and N is an integer greater than 1. As shown, the apparatus includes: fault detection module 501, fault handling module 502.
The fault detection module 501 is configured to obtain an escape path link table when a link path between the first PE and the CE for forwarding traffic data is detected to be faulty, and determine a target PE from the N second PEs according to the escape path link table.
The fault processing module 502 is configured to determine a target link channel for forwarding the traffic data according to the target PE, and forward the traffic data according to the target link channel.
Optionally, the fault handling module 502 is further configured to: and switching the link channels pointing to the first PE in the second PE except the target PE to point to the target PE.
Optionally, the first PE and the target PE have a bidirectional link channel; the escape channel link table comprises the election results of the first PE and the N second PEs and the priority of each election result; the fault handling module 502 is specifically configured to: switching the election result of the target PE in the escape link channel table to the election result with the highest priority, closing a link channel of the target PE pointing to the first PE, determining that the target link channel for forwarding the flow data is forwarding the flow data to the target PE through the first PE, and forwarding the flow data to the CE through the target PE.
In some embodiments, the schematic structural diagram of the fault handling apparatus may further include a generating module and an updating module in addition to the modules in fig. 6. Fig. 6 is a schematic structural diagram of another fault handling apparatus according to an embodiment of the present application. As shown, the apparatus includes: fault detection module 501, fault processing module 502, generation module 601, update module 602; the description of the fault detection module 501 and the fault processing module 502 is described with reference to fig. 5, and will not be repeated here.
A generating module 601, configured to obtain session state tables corresponding to the first PE and the N second PEs respectively; the session state table comprises source addresses corresponding to the first PE and the N second PEs respectively; determining respective election results of the first PE and the N second PEs according to the source addresses corresponding to the first PE and the N second PEs respectively and the Ethernet segment identifiers connected with the CE; and generating the escape channel link table according to the election results of the first PE and the N second PEs.
An update module 602, configured to trigger the first PE to generate a revocation routing notification; wherein the rerouting notification is used to characterize a failure of a link path of traffic data sent to the CE via the first PE; and when the target PE and the second PE which are remained except the target PE receive the withdrawal route notification, updating the escape channel link table so that the traffic data is not forwarded through the first PE when the traffic data is forwarded next time.
Optionally, the update module 602 specifically performs at least one of the following operations: marking the first PE pair as invalid, or deleting the first PE in the escape channel link table, the election result of the first PE and the priority of the election result of the first PE; modifying the PE with BDF as a selection result of the N second PEs into DF; and modifying the PE with the NDF as the selection result of the N second PEs into BDF.
It should be noted that, the above device provided in the embodiment of the present application can implement all the method steps in the embodiment of the fault processing method, and can achieve the same technical effects, and detailed descriptions of the same parts and beneficial effects as those in the embodiment of the present application are omitted herein.
Based on the same technical concept, the embodiment of the application also provides electronic equipment, which can realize the function of the fault processing device.
Fig. 7 is a schematic structural diagram of an electronic device according to an embodiment of the present application.
At least one processor 701, and a memory 702 connected to the at least one processor 701, in which the specific connection medium between the processor 701 and the memory 702 is not limited in the embodiment of the present application, and in fig. 7, the connection between the processor 701 and the memory 702 through the bus 700 is taken as an example. Bus 700 is shown in bold lines in fig. 7, and the manner in which the other components are connected is illustrated schematically and not by way of limitation. The bus 700 may be divided into an address bus, a data bus, a control bus, etc., and is represented by only one thick line in fig. 7 for convenience of representation, but does not represent only one bus or one type of bus. Alternatively, the processor 701 may be referred to as a controller, and the names are not limited.
In an embodiment of the present application, the memory 702 stores instructions executable by the at least one processor 701, and the at least one processor 701 may perform a fault handling method as described above by executing the instructions stored in the memory 702. The processor 701 may implement the functions of the respective modules in the apparatus shown in fig. 5 or 6.
The processor 701 is a control center of the apparatus, and may connect various parts of the entire control device using various interfaces and lines, and by executing or executing instructions stored in the memory 702 and invoking data stored in the memory 702, various functions of the apparatus and processing data, thereby performing overall monitoring of the apparatus.
In one possible design, processor 701 may include one or more processing units, and processor 701 may integrate an application processor and a modem processor, wherein the application processor primarily processes operating systems, driver interfaces, application programs, and the like, and the modem processor primarily processes wireless communications. It will be appreciated that the modem processor described above may not be integrated into the processor 701. In some embodiments, processor 701 and memory 702 may be implemented on the same chip, or they may be implemented separately on separate chips in some embodiments.
The processor 701 may be a general purpose processor such as a Central Processing Unit (CPU), digital signal processor, application specific integrated circuit, field programmable gate array or other programmable logic device, discrete gate or transistor logic device, discrete hardware components, and may implement or perform the methods, steps, and logic blocks disclosed in embodiments of the application. The general purpose processor may be a microprocessor or any conventional processor or the like. The steps of a fault handling method disclosed in connection with the embodiments of the present application may be directly embodied as execution completion by a hardware processor, or may be executed in combination by hardware and software modules in the processor.
The memory 702 is a non-volatile computer-readable storage medium that can be used to store non-volatile software programs, non-volatile computer-executable programs, and modules. The Memory 702 may include at least one type of storage medium, and may include, for example, flash Memory, hard disk, multimedia card, card Memory, random access Memory (Random Access Memory, RAM), static random access Memory (Static Random Access Memory, SRAM), programmable Read-Only Memory (Programmable Read Only Memory, PROM), read-Only Memory (ROM), charged erasable programmable Read-Only Memory (ELECTRICALLY ERASABLE PROGRAMMABLE READ-Only Memory, EEPROM), magnetic Memory, magnetic disk, optical disk, and the like. Memory 702 is any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer, but is not limited to such. The memory 702 in embodiments of the present application may also be circuitry or any other device capable of performing storage functions for storing program instructions and/or data.
By programming the processor 701, the code corresponding to one of the fault handling methods described in the foregoing embodiments may be cured into the chip, so that the chip can execute one of the fault handling methods of the embodiment shown in fig. 2 at runtime. How to design and program the processor 701 is a technology well known to those skilled in the art, and will not be described in detail herein.
It should be noted that, the above-mentioned power-on electronic device provided in the embodiment of the present application can implement all the method steps implemented in the above-mentioned method embodiment, and can achieve the same technical effects, and specific details of the same parts and beneficial effects as those of the method embodiment in the present embodiment are not described herein.
The embodiment of the application also provides a computer readable storage medium, wherein the computer readable storage medium stores computer executable instructions for causing a computer to execute the fault processing method in the embodiment.
Embodiments of the present application also provide a computer program product which, when invoked by a computer, causes the computer to perform a fault handling method as in the above embodiments.
It will be appreciated by those skilled in the art that 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, 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 the application. It will be understood that each flow and/or block of the flowchart illustrations and/or block diagrams, and combinations of flows and/or blocks in the flowchart illustrations 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 fault handling device to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable fault handling device, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable fault handling 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 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.
Claims (10)
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211468549.4A CN118101552A (en) | 2022-11-22 | 2022-11-22 | Fault handling method, device, equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211468549.4A CN118101552A (en) | 2022-11-22 | 2022-11-22 | Fault handling method, device, equipment and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN118101552A true CN118101552A (en) | 2024-05-28 |
Family
ID=91144580
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202211468549.4A Pending CN118101552A (en) | 2022-11-22 | 2022-11-22 | Fault handling method, device, equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN118101552A (en) |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102724128A (en) * | 2012-06-28 | 2012-10-10 | 杭州华三通信技术有限公司 | Message forwarding method and equipment for multi-protocol label switching (MPLS) layer 3 virtual private network (L3VPN)-based for dual-homing networking |
| CN105791072A (en) * | 2014-12-22 | 2016-07-20 | 华为数字技术(苏州)有限公司 | Access method and device of Ethernet virtual network |
| WO2019201014A1 (en) * | 2018-04-17 | 2019-10-24 | 中兴通讯股份有限公司 | Ethernet segment identifier adjacency detection processing method, device, and storage medium |
| CN113973072A (en) * | 2020-07-23 | 2022-01-25 | 华为技术有限公司 | Message sending method, equipment and system |
| CN115277305A (en) * | 2022-06-30 | 2022-11-01 | 新华三技术有限公司 | A network management method, apparatus, device, and machine-readable storage medium |
-
2022
- 2022-11-22 CN CN202211468549.4A patent/CN118101552A/en active Pending
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102724128A (en) * | 2012-06-28 | 2012-10-10 | 杭州华三通信技术有限公司 | Message forwarding method and equipment for multi-protocol label switching (MPLS) layer 3 virtual private network (L3VPN)-based for dual-homing networking |
| CN105791072A (en) * | 2014-12-22 | 2016-07-20 | 华为数字技术(苏州)有限公司 | Access method and device of Ethernet virtual network |
| WO2019201014A1 (en) * | 2018-04-17 | 2019-10-24 | 中兴通讯股份有限公司 | Ethernet segment identifier adjacency detection processing method, device, and storage medium |
| CN113973072A (en) * | 2020-07-23 | 2022-01-25 | 华为技术有限公司 | Message sending method, equipment and system |
| CN115277305A (en) * | 2022-06-30 | 2022-11-01 | 新华三技术有限公司 | A network management method, apparatus, device, and machine-readable storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11863351B2 (en) | Logical router comprising disaggregated network elements | |
| CN112995029B (en) | A method, device and system for handling transmission path faults | |
| CN111510379B (en) | EVPN message processing method, device and system | |
| US8576721B1 (en) | Local forwarding bias in a multi-chassis router | |
| US11283672B2 (en) | Forwarding detection of an aggregated interface | |
| US9722861B2 (en) | Fault-resilient broadcast, multicast, and unicast services | |
| US10110397B2 (en) | Method and device for switching tunnels and switch | |
| WO2021258754A1 (en) | Message indication method and apparatus, and device and storage medium | |
| CN112087386B (en) | A message processing method, device and system | |
| US9832121B1 (en) | Next hop instruction associations for forwarding unit programming within a network device | |
| US9628409B1 (en) | Designated forwarder election for multi-homed data center interconnect using multicast routing protocol state information | |
| US9350654B1 (en) | Microloop protection for multi-protocol label switching paths | |
| CN111740907A (en) | Message transmission method, device, equipment and machine readable storage medium | |
| CN113615132A (en) | Fast flooding topology protection | |
| CN104717143B (en) | For returning the method and apparatus of scene muticast data transmission more | |
| CN113973072B (en) | Message sending method, device and system | |
| WO2016123904A1 (en) | Routing convergence method, device and virtual private network system | |
| US10965589B2 (en) | Fast receive re-convergence of multi-pod multi-destination traffic in response to local disruptions | |
| CN114531396B (en) | A method and device for failback in Ethernet virtual private network | |
| CN118101552A (en) | Fault handling method, device, equipment and storage medium | |
| WO2016173196A1 (en) | Method and apparatus for learning address mapping relationship | |
| CN120880835B (en) | Tunnel tag processing methods, devices, and network equipment | |
| CN116648885B (en) | Routing transmission method and device | |
| CN115955430A (en) | A multicast routing method and routing device | |
| CN118368241A (en) | Method and device for generating forwarding table entries |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |