CN110391951B

CN110391951B - Ethernet segment identifier adjacency detection processing method and device and storage medium

Info

Publication number: CN110391951B
Application number: CN201810344453.4A
Authority: CN
Inventors: 王玉保
Original assignee: ZTE Corp
Current assignee: ZTE Corp
Priority date: 2018-04-17
Filing date: 2018-04-17
Publication date: 2022-11-08
Anticipated expiration: 2038-04-17
Also published as: CN110391951A; WO2019201014A1

Abstract

The invention provides a method and a device for detecting and processing the adjacency of Ethernet segment identifiers and a storage medium, wherein the method comprises the following steps: detecting ESI adjacency detection events on links of the ESI by the first PE, wherein the ESI adjacency detection events are used for indicating changes of detection results of ESI-identified link faults; the first PE sends a first message to the second PE, the first message is used for informing the ESI adjacent detection event to the second PE, wherein the first message carries fault identification information of the ESI, and the fault identification information is used for indicating the second PE to execute an updating process of a forwarding state corresponding to the ESI.

Description

Ethernet segment identifier adjacency detection processing method and device and storage medium

Technical Field

The present invention relates to the field of communications, and in particular, to a method and an apparatus for detecting and processing proximity of ethernet segment identifiers, and a storage medium.

Background

An Ethernet Virtual Private Network (EVPN) technology is used as a next-generation two-layer Virtual Private Network (L2 Virtual Private Network, abbreviated as L2 VPN) technology, and includes Provider Backbone bridging Ethernet Virtual Private Network (abbreviated as PBB EVPN), multi-Protocol Label Switching (Multi-Protocol Label Switching Ethernet Virtual Private Network, abbreviated as MPLS pn), virtual extended local area Network (Virtual extended LAN Ethernet Virtual Private Network, abbreviated as VXLAN EVPN), and the like. The IETF has detailed definitions of the control plane of EVPN in RFC7432, and detailed definitions of the data plane of MPLS EVPN. Then, the IETF defines the control plane and forwarding plane of VXLAN EVPN in detail by RFC8365 and the control plane and forwarding plane of PBB EVPN in detail by RFC7623, in addition to RFC 7432. Whether MPLS EVPN, VXLAN EVPN or PBB EVPN, there is a corresponding description for the scenario of ES multi-homing access to PE, and a typical networking is as shown in fig. 1 (the lower network in fig. 1 is also referred to as an underlay network):

RFC7432 uses the ESI field to uniquely identify an ES with dual-homed/multi-homed access features in EVPN routes, while using an ESI value of 0 indicates an ES with only single-homed access features.

A certain ES accesses a plurality of PEs, each PE accessed by the ES is called an adjacent PE of the ES, and the ES is called to have an adjacent relation with the adjacent PE. The ESI of the same ES on each of its neighboring PEs is the same.

The physical link of the ES connected with a certain adjacent PE is called the adjacent link of the ES on the adjacent PE, the state change detection on the adjacent link comprises physical state change detection, protocol state change detection and detection state change detection, which are collectively called ESI adjacent detection of the ES, and the change of the ESI adjacent detection state is called ESI adjacent detection event.

In an EVPN network, if a PE node is not an adjacent PE of an ES, it is called a non-adjacent PE of the ES. Non-contiguous PEs are able to learn of the existence of remote ESIs, as well as which contiguous PEs are currently available for each remote ESI, and their forwarding information to the contiguous PEs of each remote ESI.

RFC7432 defines five classes of EVPN routes, where the first class of EVPN routes, referred to as Ethernet Auto-discovery (EAD) routes, are used only in MPLS/VXLAN EVPN; the second type of EVPN routing, referred to as MAC distribution routing, also known as MAC routing, is used in both PBB EVPN and MPLS/VXLAN EVPN, but functions differently.

PBB EVPN differs from MPLS/VXLAN EVPN in how non-adjacent PEs discover adjacent PEs: the ESI is mapped into B-MAC (Backbone MAC) firstly, and then the effective/ineffective of ESI adjacent link is represented by the release and the withdrawal of MAC route; the latter issues ESI information directly to the remote PE via the EAD route.

In MPLS/VXLAN EVPN, there are two granularities for the EAD routing defined by RFC7432, one is ethernet segment-auto-discovery (EAD-ES) routing, and the other is ethernet auto-discovery EVPN Instance (EAD-EVI) routing, which are issued externally by each adjacent PE of each ES. The issuance and withdrawal of an EAD-ES and EAD-EVI route is affected by ESI adjacency detection events of that ES on the corresponding adjacency PE.

The non-adjacent PE in the PBB EVPN does not know the ESI information, and the protection technology based on ESI peer-to-peer bidirectional forwarding detection BFD cannot be implemented in the PBB EVPN; in MPLS/VXLAN EVPN, EAD-ES and EAD-EVI routes are carried in BGP protocol messages, and convergence performance hardly reaches BFD level performance by depending on propagation of ESI adjacency detection events.

Aiming at the problems that ESI adjacency detection events can only depend on BGP route propagation and convergence performance hardly reaches BFD level performance in the related technology, an effective solution is not provided.

Disclosure of Invention

The embodiment of the invention provides a method, a device and a storage medium for processing Ethernet segment identifier adjacency detection, which at least solve the problems that ESI adjacency detection events in the related technology only depend on BGP route transmission and convergence performance hardly reaches BFD level performance.

According to an embodiment of the present invention, a method for detecting and processing adjacency of ethernet segment identifiers is provided, which includes: detecting ESI adjacency detection events on links of the ESI by the first PE, wherein the ESI adjacency detection events are used for indicating changes of detection results of ESI-identified link faults;

the method comprises the steps that a first PE sends a first message to a second PE, wherein the first message is used for informing an ESI adjacent detection event to the second PE, the first message carries fault identification information of the ESI, and the fault identification information is used for indicating the second PE to execute an updating process of a forwarding state corresponding to the ESI.

Optionally, detecting the ESI adjacency detection event on the link identified by the ESI is performed by at least one of:

by way of standard first mile ethernet EFM technology;

the mode of operation, administration and maintenance TP OAM TMS technology is transmitted through standard Y.1731;

managing CFM technology through standard connectivity fault;

by detecting physical signals on the link identified by the ESI.

Optionally, the ESI adjacency detection event is encapsulated by at least one of the following formats: detecting a linkage path failure message of BFD (bidirectional forwarding detection); transmitting a client signal failure indication (CSF) message of the operation, administration and maintenance (TP) OAM session; an address resolution protocol ARP message; a neighbor request message of a Neighbor Discovery Protocol (NDP); internet control message protocol ICMP messages; and the media access control MAC Ping message.

Optionally, the fault identification information of the ESI includes at least one of: partial binary bits of ESI; an operator backbone bridging backbone MAC address PBB-MAC corresponding to ESI or a part of binary bits in PBB-MAC corresponding to ESI; an IP address corresponding to the ESI; ESI tags corresponding to ESI; the coding information is used for indicating that the main interface corresponding to the ESI has faults; the ESI sub-interface is used for indicating that the ESI sub-interface has fault, wherein the ESI sub-interface is a sub-interface of the main interface corresponding to the ESI; and node identification information used for indicating the node where the link failure identified by the ESI is located.

Optionally, encapsulating the ESI adjacency detection event by the ARP packet includes at least one of:

the ARP message is encapsulated into an EVPN message, wherein the EVPN message is encapsulated according to a data message format in an EVPN instance bound by an ESI subinterface of the ESI;

packaging the PDU part of the ARP message according to the PDU format of the ARP probe message, wherein the target protocol address in the PDU is a designated IP address;

setting a sender hardware address field of the ARP message as fault identification information carrying ESI;

setting an operation code of the ARP message as a preset value;

setting a sender protocol address field of the ARP message as fault identification information carrying ESI;

setting an Ethernet source MAC of the ARP message as an MAC address of the first PE;

setting the Ethernet source MAC of the ARP message as the MAC address of a main interface corresponding to ESI or an ESI sub-interface of ESI;

setting an Ethernet source MAC of an ARP message as an MAC address of an integrated routing bridging IRB interface of an EVPN instance bound by an ESI subinterface of the ESI;

setting an Ethernet source MAC of the ARP message as a specified value;

setting the Ethernet destination MAC address of the ARP message as a preset value;

setting a target protocol address in the ARP message as fault identification information carrying ESI;

setting a target hardware address in the ARP message to carry ESI fault identification information;

and encapsulating the ARP message into an EVPN data message by using a control word, wherein the channel type in the control word is set to be a specified value.

According to another embodiment of the present invention, a method for detecting and processing proximity of ethernet segment identifiers is provided, which includes: a second network side edge device PE receives a first message sent by a first PE, wherein the first message is used for notifying an ESI adjacency detection event on a link of an Ethernet segment identifier ESI detected by the first PE to the second PE, and the ESI adjacency detection event is used for indicating the change of a result of detecting the link failure identified by the ESI; and the first message carries fault identification information of the ESI, and the fault identification information is used for indicating the second PE to execute an updating process of a forwarding state corresponding to the ESI.

Optionally, the ESI adjacency detection event is encapsulated by at least one of the following formats: detecting a linked Path failure coordinated Path Down message of BFD by peer-to-peer bidirectional forwarding; transmitting a client signal failure indication (CSF) message of the operation, administration and maintenance (TP) OAM session; an Address Resolution Protocol (ARP) message; a neighbor request message of a Neighbor Discovery Protocol (NDP); an ICMP message; and the media access control MAC Ping message.

Optionally, the fault identification information of the ESI includes at least one of: partial binary bits of ESI; PBB-MAC corresponding to ESI or part of binary bits in PBB-MAC corresponding to ESI; an IP address corresponding to the ESI; ESI tags corresponding to ESI; the coding information is used for indicating that the main interface corresponding to the ESI has faults; the ESI sub-interface used for pointing out ESI has the coded information of the trouble, wherein, ESI sub-interface is the sub-interface of the main interface that ESI corresponds to; and the node identification information is used for indicating the node where the link failure identified by the ESI is located.

the ARP message is encapsulated into an EVPN message encapsulated according to a data message format in an EVPN instance bound by an ESI subinterface of the ESI;

the PDU part of the ARP message is packaged according to the PDU format of the ARP probe message, wherein the target protocol address in the PDU is a designated IP address;

the hardware address field of the sender of the ARP message carries the fault identification information of the ESI;

the operation code of the ARP message is a preset value;

the sender protocol address field of the ARP message carries the fault identification information of the ESI;

the Ethernet source MAC of the ARP message is the MAC address of the first PE;

the Ethernet source MAC of the ARP message is the MAC address of the main interface corresponding to ESI or the ESI sub-interface of ESI;

the Ethernet source MAC of the ARP message is the MAC address of an integrated routing bridging IRB interface of an EVPN instance bound by an ESI subinterface of the ESI;

the Ethernet source MAC of the ARP message is a specified value.

Optionally, the flow of executing the update of the forwarding state corresponding to the ESI includes at least one of: changing the appointed forwarding/non-appointed forwarding/backup appointed forwarding state corresponding to the ESI subinterface of the ESI; and changing the state of the corresponding next hop information in the forwarding information set corresponding to the ESI.

According to another embodiment of the present invention, an ethernet segment identifier adjacency detection processing apparatus is provided, including: the detection module is used for detecting an ESI adjacency detection event on a link of the Ethernet segment identification ESI, wherein the ESI adjacency detection event is used for indicating the change of the detection result of the link failure identified by the ESI;

a sending module, configured to send a first message to a PE on a side of a second network, where the first message is used to notify an ESI adjacency detection event to the second PE, where the first message carries fault identification information of the ESI, and the fault identification information is used to instruct the second PE to execute an update procedure of a forwarding state corresponding to the ESI.

Optionally, the detecting module is further configured to detect an ESI adjacency detection event on a link identified by the ESI by at least one of: by way of standard first mile ethernet EFM technology; the mode of operation, administration and maintenance TP OAM TMS technology is transmitted through standard Y.1731; by means of standard connectivity fault management CFM techniques; by detecting physical signals on the link identified by the ESI.

Optionally, the method further comprises: an encapsulation module to encapsulate the ESI adjacency detection event by at least one of the following formats: detecting a chain path failure message of BFD by peer-to-peer bidirectional forwarding; transmitting a client signal failure indication CSF message of the operation, administration and maintenance TP OAM session; media Access Control (MAC) Ping messages; an address resolution protocol ARP message; a neighbor request message of a Neighbor Discovery Protocol (NDP); internet control message protocol ICMP messages.

Optionally, the fault identification information of the ESI includes at least one of: partial binary bits of the ESI; an operator backbone bridging backbone MAC address PBB-MAC corresponding to ESI or a part of binary bits in PBB-MAC corresponding to ESI; IP address corresponding to ESI; ESI tags corresponding to ESI; encoding information for indicating that a primary interface of the ESI is malfunctioning; the ESI sub-interface used for pointing out ESI has the coded information of the trouble, wherein, ESI sub-interface is the sub-interface of the main interface that ESI corresponds to; and the node identification information is used for indicating the node where the link failure identified by the ESI is located.

Optionally, the encapsulating module is further configured to encapsulate the ESI adjacency detection event according to the ARP packet by using at least one of the following manners:

packaging the PDU part message of the ARP according to the PDU format of the ARP probe message, wherein the target protocol address in the PDU is a designated IP address;

setting an operation code of the ARP message as a preset value;

setting Ethernet source MAC of ARP message as MAC address of EVPN instance integrated route bridge IRB interface bound by ESI subinterface of ESI;

setting an Ethernet source MAC of the ARP message as a specified value;

and encapsulating the ARP message into an EVPN data message by using a control word, wherein the channel type in the control word is set to a specified value.

According to another embodiment of the present invention, an ethernet segment identifier adjacency detection processing apparatus is provided, including:

a receiving module, configured to receive a first packet sent by a first PE, where the first packet is used to notify, to the apparatus, an ESI adjacency detection event on a link of an ethernet segment identifier ESI detected by the first PE, where the ESI adjacency detection event is used to indicate a change of a result of detecting a link failure of the ESI identifier; wherein, the first message carries the fault identification information of the ESI;

and the updating module is used for executing the updating process of the forwarding state corresponding to the ESI according to the fault identification information.

Optionally, the receiving module is further configured to receive a control packet encapsulating the ESI adjacency detection event by using at least one of the following formats: detecting a chain path failure message of BFD by peer-to-peer bidirectional forwarding; transmitting a client signal failure indication CSF message of the operation, administration and maintenance TP OAM session; an address resolution protocol ARP message; a neighbor request message of a Neighbor Discovery Protocol (NDP); an ICMP message; and the media access control MAC Ping message.

Optionally, the fault identification information of the ESI includes at least one of: partial binary bits of the ESI; PBB-MAC corresponding to ESI or part of binary bits in PBB-MAC corresponding to ESI; an IP address corresponding to the ESI; ESI tags corresponding to ESI; the coding information is used for indicating that the main interface corresponding to the ESI has faults; the ESI sub-interface is used for indicating that the ESI sub-interface has fault, wherein the ESI sub-interface is a sub-interface of the main interface corresponding to the ESI; and the node identification information is used for indicating the node where the link failure identified by the ESI is located.

Optionally, the receiving module is further configured to receive a packet obtained by encapsulating the ESI adjacency detection event according to the ARP packet in at least one of the following manners:

the ARP message is a message encapsulated in an EVPN message in a data message format in an EVPN instance bound according to an ESI subinterface of the ESI;

the PDU part of the ARP message is a message encapsulated according to the PDU format of the ARP probe message, wherein a target protocol address in the PDU is a designated IP address;

the hardware address field of the sender of the ARP message carries ESI fault identification information;

the operation code of the ARP message is a preset value;

the Ethernet source MAC of the ARP message is the MAC address of the first PE;

the ethernet source MAC of the ARP packet is the specified value.

Optionally, the updating module is further configured to at least one of: changing the appointed forwarding/non-appointed forwarding/backup appointed forwarding state corresponding to the ESI subinterface of the ESI; and changing the state of the corresponding next hop information in the forwarding information set corresponding to the ESI.

According to another embodiment of the present invention, there is provided a network-side edge device, including any one of the foregoing ethernet segment identifier adjacency detection processing apparatuses.

According to another embodiment of the present invention, a storage medium is provided, where the storage medium includes a stored program, and the program executes any one of the above-mentioned ethernet segment identifier adjacency detection processing methods when running.

According to another embodiment of the present invention, a processor is provided, where the processor is configured to execute a program, and the program executes any one of the above-mentioned ethernet segment identifier adjacency detection processing methods.

By the invention, a first PE detects ESI adjacency detection events on links of Ethernet segment identifications ESI, wherein the ESI adjacency detection events are used for indicating changes of detection results of ESI identified link faults; the method comprises the steps that a first PE sends a first message to a second PE, wherein the first message is used for informing an ESI (authentication information) adjacency detection event to the second PE, the first message carries fault identification information of the ESI, and the fault identification information is used for indicating the second PE to execute an updating process of a forwarding state corresponding to the ESI; the problem that ESI adjacency detection events in the related technology only depend on BGP route propagation and convergence performance hardly reaches BFD level performance can be solved, and the effects of completing rapid forwarding path switching or specified forwarding/non-specified forwarding/backup specified forwarding state switching on a far-end PE and reducing packet loss time in the ES link failure convergence process are achieved.

Drawings

The accompanying drawings, which are included to provide a further understanding of the invention and are incorporated in and constitute a part of this application, illustrate embodiment(s) of the invention and together with the description serve to explain the invention without limiting the invention. In the drawings:

FIG. 1 is a physical topology diagram of RFC7432EVPN traffic according to an embodiment of the present invention;

fig. 2 is a flowchart (one) of a method for processing ethernet segment identity adjacency detection according to an embodiment of the present invention;

fig. 3 is a flowchart (ii) of a method for processing ethernet segment identity adjacency detection according to an embodiment of the present invention;

FIG. 4 is an OAM Mapping Channel Sub-TLV format for ESI OAM Mapping in accordance with an embodiment of the present invention;

fig. 5 is a BFD control packet format with extended generic OAM mapping channel capabilities according to an embodiment of the present invention;

FIG. 6 is a physical topology diagram of RFC7623PBB EVPN traffic according to an embodiment of the present invention;

FIG. 7 is an ESI OAM Mapping Channel Sub-TLV format for ESI OAM Mapping in PBB EVPN according to an embodiment of the present invention;

FIG. 8 is a Y.1731 extended CSF PDU format according to an embodiment of the invention;

fig. 9 is a block diagram (one) of the ethernet segment identity adjacency detection processing apparatus according to the embodiment of the present invention;

fig. 10 is a block diagram of the ethernet segment identifier adjacency detection processing apparatus according to the embodiment of the present invention;

fig. 11 is a block diagram (iii) of the ethernet segment identifier adjacency detection processing apparatus according to the embodiment of the present invention;

fig. 12 is a block diagram (iv) of the ethernet segment identity adjacency detection processing apparatus according to the embodiment of the present invention;

fig. 13 is a block diagram (v) of the ethernet segment identifier adjacency detection processing apparatus according to the embodiment of the present invention.

Detailed Description

The invention will be described in detail hereinafter with reference to the drawings and embodiments. It should be noted that the embodiments and features of the embodiments in the present application may be combined with each other without conflict.

Example one

The embodiment of the method for processing proximity detection of ethernet segment identifier provided in this embodiment may be implemented in a network edge device PE or a similar processing device. Taking the operation on the network side edge device PE as an example, fig. 2 is a flowchart of a method for detecting and processing proximity of ethernet segment identifiers according to an embodiment of the present invention, as shown in fig. 2, the flowchart includes the following steps:

step S202, the PE at the edge of the first network side detects an ESI adjacency detection event on a link of the ESI, where the ESI adjacency detection event is used to indicate a change of a result of detecting an ESI-identified link failure;

step S204, the first PE sends a first message to the second PE, where the first message is used to notify the ESI adjacency detection event to the second PE, where the first message carries fault identification information of the ESI, and the fault identification information is used to instruct the second PE to execute an update procedure of a forwarding state corresponding to the ESI.

Through the execution of the above steps, the first network-side edge device PE detects an ESI adjacency detection event on a link of the ethernet segment identifier ESI, where the ESI adjacency detection event is used to indicate a change in a result of detecting the link failure identified by ESI; the method comprises the steps that a first PE sends a first message to a second PE, wherein the first message is used for informing an ESI (authentication information) adjacency detection event to the second PE, the first message carries fault identification information of the ESI, and the fault identification information is used for indicating the second PE to execute an updating process of a forwarding state corresponding to the ESI; therefore, the problem that ESI adjacency detection events in the related technology only depend on BGP route propagation and convergence performance hardly reaches BFD level performance can be solved, and the effects of completing rapid forwarding path switching on a far-end PE and reducing packet loss time in the ES link fault convergence process are achieved.

Optionally, the ESI adjacency detection event on the link identified by the ESI is detected by at least one of:

by way of standard first mile ethernet EFM technology;

by means of standard connectivity fault management CFM techniques;

by detecting physical signals on the link identified by the ESI.

Optionally, the ESI adjacency detection event is encapsulated by at least one of the following formats: detecting a chain path failure message of BFD by peer-to-peer bidirectional forwarding; transmitting a client signal failure indication CSF message of the operation, administration and maintenance TP OAM session; an address resolution protocol ARP message; neighbor request messages of a neighbor discovery protocol NDP; internet control message protocol ICMP messages (e.g. Ping messages, see preferred embodiment 10); and the media access control MAC Ping message.

Optionally, the fault identification information of the ESI includes at least one of: partial binary bits of the ESI (e.g., fault identification information of the ESI includes partial binary bits of the ESI); an operator backbone bridging backbone MAC address PBB-MAC corresponding to ESI or a part of binary bits in PBB-MAC corresponding to ESI; IP address corresponding to ESI; ESI tags corresponding to ESI; the coding information is used for indicating that the main interface corresponding to the ESI has faults; the ESI sub-interface is used for indicating that the ESI sub-interface has fault, wherein the ESI sub-interface is a sub-interface of the main interface corresponding to the ESI; node identification information indicating a node (e.g., a first PE) at which the ESI identified the link failure.

Optionally, encapsulating the ESI adjacency detection event by the ARP packet includes at least one of the following ways:

encapsulating the ARP message into an EVPN message, wherein the EVPN message is encapsulated according to a data message format in an EVPN instance bound by an ESI subinterface of the ESI;

setting an operation code of the ARP message as a preset value;

setting an Ethernet source MAC of the ARP message to a specified value;

The invention organically combines the EVPN technology and an Operation Administration and Maintenance mapping (OAM mapping for short) mechanism, so that the packet loss time of an ESI (Ethernet Segment Identifier) failure convergence process in an ES dual-homing access scene is greatly reduced.

The first embodiment further provides an embodiment of a method for detecting and processing proximity of ethernet segment identifiers, which may be executed in a network edge device PE or a similar processing apparatus. Taking the operation on the network side edge device PE as an example, fig. 3 is a flowchart of a method for detecting and processing proximity of ethernet segment identifiers according to an embodiment of the present invention, as shown in fig. 3, the flowchart includes the following steps:

step S302, a PE at a side of a second network receives a first message sent by a first PE, where the first message is used to notify an ESI adjacency detection event on a link of an ethernet segment identifier ESI detected by the first PE to the second PE, and the ESI adjacency detection event is used to indicate a change of a result of detecting a link failure of the ESI identifier; the first message carries fault identification information of the ESI, and the fault identification information is used for indicating the second PE to execute an update process of a forwarding state corresponding to the ESI.

Through the execution of the above steps, the PE at the edge of the second network side receives a first message sent by the first PE, where the first message is used to notify the second PE of an ESI adjacency detection event on the link of the ethernet segment identifier ESI detected by the first PE, and the ESI adjacency detection event is used to indicate a change of a result of detecting a link failure identified by ESI; the first message carries fault identification information of ESI, and the fault identification information is used for indicating the second PE to execute an update process of a forwarding state corresponding to the ESI; by adopting the technical scheme, the problem that ESI adjacency detection events in the related technology only depend on BGP route transmission and convergence performance hardly reaches BFD level performance can be solved, and the effects of completing quick forwarding path switching on a far-end PE and reducing packet loss time in the ES link fault convergence process are achieved.

Optionally, the ESI adjacency detection event is encapsulated by at least one of the following formats: a chained Path failure (coordinated Path Down) message of the peer-to-peer bidirectional forwarding detection BFD; transmitting a client signal failure indication CSF message of the operation, administration and maintenance TP OAM session; an Address Resolution Protocol (ARP) message; neighbor request messages of a neighbor discovery protocol NDP; ICMP message; and the media access control MAC Ping message.

Optionally, the fault identification information of the ESI includes at least one of: partial binary bits of ESI; PBB-MAC corresponding to ESI or part of binary bits in PBB-MAC corresponding to ESI; IP address corresponding to ESI; ESI tags corresponding to ESI; the coding information is used for indicating that the main interface corresponding to the ESI has faults; the ESI sub-interface used for pointing out ESI has the coded information of the trouble, wherein, ESI sub-interface is the sub-interface of the main interface that ESI corresponds to; and the node identification information is used for indicating the node where the link failure identified by the ESI is located.

the ARP message is encapsulated into an EVPN message encapsulated in a data message format in an EVPN instance bound according to an ESI subinterface of the ESI;

the operation code of the ARP message is a preset value;

the sender protocol address field of the ARP message carries ESI fault identification information;

the Ethernet source MAC of the ARP message is the MAC address of the first PE;

the ethernet source MAC of the ARP packet is the specified value.

Optionally, the updating flow for executing the forwarding state corresponding to the ESI includes at least one of: changing the state of designated forwarding/non-designated forwarding/backup designated forwarding (DF/NDF/BDF) corresponding to the ESI subinterface of the ESI (the symbol "/" represents "OR", namely designated forwarding or non-designated forwarding or backup designated forwarding state, DF or NDF or BDF state); and changing the state of corresponding next hop information in the forwarding information set corresponding to the ESI.

The invention organically combines the EVPN technology with an Operation Administration and Maintenance mapping (OAM mapping for short) mechanism or an ARP proxy mechanism, so that the packet loss time of an ESI (Ethernet Segment Identifier) failure convergence process in an ES dual-homing scene is greatly reduced.

The first embodiment of the present invention will be described in further detail with reference to fig. 1:

a basic VXLAN EVPN service is deployed on PE1, PE2 and PE3, wherein CE1 is accessed to PE1 and PE2 in a dual-homing mode, the corresponding ESI is ESI1, an all-active mode is adopted, and CE2 is accessed to PE3 in a single-homing mode. So that the EVPN basic function defined by RFC7432 can work normally. After the step is completed, the EVPN control plane module and the EVPN forwarding table management module are deployed at the same time.

The ESI adjacency detection module is deployed on the link between PE1 and CE1, the ESI state mapping module is deployed on PE1, the ESI state demapping module is deployed on PE3, and the ESI state change propagation fast path is deployed between PE1 and PE3. The ESI adjacency detection module may include a link BFD, EFM, CFM, and other detection modules, and may specifically deploy the ESI adjacency detection module in the following manner: standard EFM techniques are deployed on the link and the ESI adjacency detection module may cause the EFM module to input state changes of the link to the ESI state mapping module at any time.

The deployment ESI state change propagation fast channel specifically is: an extended peer BFD session is deployed between PE1 and PE3, with the state change propagation of all ESIs on both nodes taking this peer BFD session as a fast path, instead of one BFD session per ESI.

Taking physical failure of a link between the PE1 and the CE1 as an example, the processing steps are as follows:

step 1, ESI adjacency detection module on PE1 detects link failure on ESI1, including physical link failure;

step 2, an ESI adjacency detection module on the PE1 informs the fault on the ESI1 to an ESI state mapping module;

step 3, an ESI state Mapping module on PE1 encodes the fault on ESI1 into ESIOAM Mapping Channel Sub-TLV format, and informs the ESI state change propagation fast Channel, specifically: the ESI state Mapping module on PE1 receives the detection state change event and determines the corresponding ESI, which is the ESI1 in this example, encapsulates the ESI1 state change event in the ESI oam Mapping Channel Sub-TLV format shown in fig. 4, and notifies the ESI state change propagation fast Channel. Wherein the ESI field is ESI1 filled, the Ethernet Tag ID (i.e. EtherMark ID) field is 0xFFFFFFFF filled, indicating that the global state of ESI1 is passed (the other non-0 values filled indicate that the state of ESI1 on which the Ethernet Tag is specified is passed); ESI Adjacent PE Address (namely ESI Adjacent PE Address) field is filled with the next hop Address used by the node for EAD-ES routing of ESI1 issued outside; the State (i.e., status) field pad 1 indicates Down and pad 3 indicates UP. The ESI (continue) field in fig. 4 is an ESI (continue) field.

Step 4, the peer BFD session between PE1 and PE3 uses a new version number, i.e. 5, to distinguish it from the standard BFD session defined by RFC 5880; except different version numbers, the message format and the use method of the BFD session are completely the same as those of a standard BFD session; a flag code is added to the BFD control message of the peer BFD session, namely, the BFD control message with 27 flag code does not reflect the state of the object detected by the BFD session to which the message belongs, but only serves as a general OAM mapping channel; the payload of the OAM Mapping Channel is filled in the Sub-TLV format, as shown in FIG. 5, the payload of the OAM Mapping Channel exists in the form of Generic OAM Mapping Channel Sub-TLV in the BFD control message; the ESI state change propagation fast path on PE1 propagates the ESI state Mapping module encapsulated Sub-TLV to PE3 through the generic OAM Mapping channel of the peer BFD session. Note that, in fig. 5, the Sta field is a status field, the Detect time multiple field is a Detect Mult field, the My Discriminator field is a self identifier field, the young Discriminator field is a counterpart identifier field, the Desired TX Interval minimum field is a Desired Min TX Interval field, and the Desired RX Interval minimum field is a Desired Min RX Interval.

And 5, on the PE3, the peer BFD session inputs the payload part of the general OAM mapping channel carried in the BFD control message identified by the Diag field 27 to the ESI state demapping module. For the present example, the payload format is the ESI OAM Mapping Channel Sub-TLV format, but the BFD session does not need to parse the payload format, but is directly submitted to the ESI state demapping module for parsing.

Step 6, an ESI state demapping module on PE3 receives OAM Mapping Channel Sub-TLV input by the ESI state change propagation fast Channel, analyzes corresponding ESI and Ethernet Tag ID, determines a corresponding EAD-ES route or EAD-EVI route, which is the EAD-ES route of ESI1, and then notifies an EVPN forwarding table management module on the basis of the name of EAD-ES route withdrawal, specifically: analyzing the state of ESI1, up or Down from the OAM Mapping Sub-TLV;

if ESI1 state is changed into Down, using the same API interface to input to EVPN transfer table management module when EAD-ES route withdrawal event corresponding to EVPN control surface input ESI 1; if the ESI1 state is changed into Up, the EVPN forwarding table management module is not influenced; therefore, the EVPN forwarding table management module can automatically support the function only by supporting the standard RFC7432 function;

step 7, the EVPN forwarding table management module on pe3 processes the received EAD-ES route withdrawal event according to the specification of RFC7432, and as a result, the forwarding path on ESI1 is switched.

And step 8, at the same time, the BGP EVPN control surface performs convergence of an ESI1 forwarding member list according to the inherent flow and finally completes the convergence, but when the step 7 is completed, the flow does not lose packets any more, so that the packet loss time in the ESI convergence process is greatly reduced. And the EVPN control plane module also issues a true EAD routing cancellation to the EVPN forwarding table management module, and at this time, because of the reason of step 7, the EVPN forwarding table management module does not have a corresponding forwarding path of the corresponding ESI, and can directly return.

In step 4, the peer BFD session encapsulates the ESI OAM Mapping Channel Sub-TLV input by the ESI state Mapping module into a BFD control packet, where a Vers field takes a value of 5, a flag field takes a value of 27, general OAM Mapping Channel Sub-TLV field takes a value of integrally copying the ESI OAM Mapping Channel Sub-TLV, and other field take values are identical to the same name field in RFC5880 when the flag field takes a value of 6. Only when the ESI state changes, the ESI related message needs to be issued on the peer BFD session, the ESI related message does not need to be periodically sent (in other words, each ESI session does not need to be established), and in a normal state, the peer BFD session does not have the ESI related message.

In step 5, the payload of the OAM Mapping channel is filled in a Sub-TLV format, and the BFD session does not analyze the content of the payload but directly passes the payload to the ESI state demapping module for analysis; as shown in fig. 5, the payload of the OAM Mapping Channel exists in the BFD control message in the form of Generic OAM Mapping Channel Sub-TLV.

Through the steps, on the basis of an ESI adjacency detection event propagation mechanism, the ESI adjacency detection event propagation mechanism is organically combined with an OAM mapping technology, so that a local ESI adjacency detection event can reach a far-end PE in advance of an EAD route through an ESI state change propagation fast channel, and therefore fast forwarding path switching is completed on the far-end PE, packet loss time in an ES link fault convergence process is reduced, and the problems that in the related technology, the ESI adjacency detection event only depends on BGP route propagation, and convergence performance hardly reaches BFD level performance are solved.

The above processing step may further include the steps of:

in step 9, when the UP of the adjacent link of ESI1 on PE1 is recovered, PE1 may also send a message of link UP of ESI1 to the general OAM Mapping channel, but the ESI OAM Mapping message notifying that the adjacent link becomes UP is not notified to the EVPN forwarding table management module. Meanwhile, the EVPN control surface on the PE3 resends the EAD-ES route corresponding to the ESI1 to be effective, and at the moment, the EVPN forwarding table management module is not influenced by the OAM Mapping message which informs the ESI1 link DOWN.

And step 10, the peer BFD session is interrupted, the EVPN forwarding table management module on the PE3 is not influenced, and the EVPN forwarding table management module only needs to be influenced by the EVPN control plane module during the interruption of the peer BFD session.

In step 11, after the peer BFD session is recovered, if the state of the adjacent link of ESI1 on PE1 is UP, PE1 may also send a message of link UP of ESI1 to the general OAM Mapping channel, but the ESI OAM Mapping message notifying that the adjacent link becomes UP has no influence on the EVPN forwarding table management module.

Optionally, PE1 sends a first message to PE3, where the first message is used to notify PE3 of the ESI adjacency detection event.

It will be understood by those skilled in the art that the present invention can be implemented not only on ESI in all-active mode, but also on ESI in single-active mode. The OAM Mapping channel can use not only the peer BFD but also TE BFD or TP OAM and other detection technologies. ESI adjacency detection may use not only EFM but also link detection techniques such as CFM.

Preferred embodiment 1

In the preferred embodiment 1, a method for transmitting and processing an ethernet segment identifier adjacency detection event is provided, and the following describes the preferred embodiment 1 in further detail with reference to fig. 6: as shown in fig. 6, a basic PBB EVPN service is deployed in PE1, PE2, and PE3, where CE1 is dual-homed to access PE1 and PE2, the corresponding ESI is ESI1, the corresponding B-MAC is BM1, an all-active mode is adopted, and CE2 is single-homed to access PE3. So that the PBB EVPN basic function defined by RFC7623 can work normally. After the step is completed, the EVPN control plane module and the EVPN forwarding table management module are deployed at the same time.

For convenience of description, without loss of generality, it is assumed that 20 PBB EVPN services are established in PE1, PE2, and PE3, and PBB I component examples thereof are respectively denoted as zteI1, zteI2 \8230 \ zteI20, wherein the PBB component examples corresponding to zteI1, zteI2 \8230 \ 8230, zteI10 are zteB1, zteI11, zteI12 \8230 \ and the PBB component examples corresponding to \8230 \ zteI20 are zteB2. Without loss of generality, it is assumed that ESI1 has the designated forwarding DF role on PE1 and the non-designated forwarding NDF role on PE2 in these I-component instances.

For convenience of description, and without loss of generality, an embodiment implementing PE1 to PE2 ESI adjacency detection event transmission is as follows: the ESI adjacency detection module is deployed on the link between PE1 and CE1, the ESI state mapping module is deployed on PE1, the ESI state demapping module is deployed on PE2, and the ESI state change propagation fast path is deployed between PE1 to PE 2.

The deployment ESI adjacency detection module specifically is: any port state detection technology (such as EFM, TP OAM TMS, etc.) may not be deployed on the physical link of the main interface corresponding to the ESI1, but to detect the physical signal of the link, the ESI adjacency detection module may input the physical state change of the link to the ESI state mapping module at any time.

The deployment ESI state mapping module specifically includes: generating an ARP Probe (ARP Probe) message when an ESI adjacency detection event input by an ESI state mapping module is received, wherein a target protocol address field of the ARP Probe message is filled as a specified IP address, a sender hardware address field is filled as ESI identification information of ESI corresponding to the ESI adjacency detection event, and then the ARP Probe message is submitted to an ESI state change propagation fast channel; and the ESI identification information is the PBB-MAC corresponding to the ESI.

The deployment ESI state change propagation fast channel specifically is: on PE1, for each subinterface of the main interface corresponding to the ESI, copying the ARP Probe message, broadcasting the ARP Probe message in an I component example bound to the subinterface, and adding an outer-layer (namely, an outer layer adjacent to an ARP layer) Ethernet header to the ARP Probe message before sending, wherein the source MAC of the added outer-layer Ethernet header is a designated MAC, and the destination MAC is a full FF; it is worth noting that the encapsulation outside the outer etherheader of the ARP Probe message that is eventually broadcast out will have the same format as when the BUM data message is broadcast in this EVPN instance; on PE2, ESI state change propagation fast channel identifies ARP Probe message in specified characteristic format received from network side, and delivers it to ESI state de-mapping module, and other ARP Probe message is still processed according to existing technique; the ARP Probe message with the specified characteristic format is an ARP Probe message with a target protocol address as a specified IP address, wherein the specified IP address has the same value as the specified IP address in the ESI state mapping module.

The deployment ESI state demapping module specifically is: and receiving an ARP message from an ESI state change propagation fast channel, reading the content of a hardware address field of a sender, interpreting the ARP message into a B-MAC address, converting the B-MAC address into a main interface corresponding to the corresponding ESI, and submitting the ESI and an identifier of an I component example receiving the ARP Probe message to the ESI forwarding table management module.

The deployment ESI forwarding table management module specifically includes: after receiving the ESI main interface and the I component instance identifier input by the ESI state demapping module, finding out the sub-interface bound with the I component instance on the main interface, and setting the sub-interface as a DF state;

taking physical failure of a link between the PE1 and the CE1 as an example, the processing steps of the flow part are as follows:

step 1, an ESI adjacency detection module on PE1 detects link faults on ESI1, including physical link faults;

step 3, an ESI state mapping module on the PE1 encodes the fault on the ESI1 into an ARP Probe message with a specified format;

step 4, ESI state change transmission fast channel on PE1 broadcasts ARP Probe message in each I component example accessed by ESI 1;

step 5, on PE2, the ESI state change propagation fast channel delivers the received ARP Probe message with the specified format to the ESI state demapping module;

step 6, on PE2, the ESI state demapping module notifies the forwarding table management module ESI1 that a remote failure occurs in a corresponding I component instance (taking a zte1 instance as an example); it is noted that in the preferred embodiment, all 20 instances of an I-component are notified of a remote failure of ESI1 in succession;

step 7, on PE2, the EVPN forwarding table management module sets a subinterface used in the case that ESI1 is accessed to zte1 as a DF state;

and step 8, meanwhile, the BGP EVPN control surface also performs DF election convergence of ESI1 according to the RFC7623 inherent flow and finally completes the DF election convergence, but when the step 7 is completed, the broadcast flow broadcasted to PE2 by PE3 is not discarded by PE2 any more, so that the packet loss time caused by slow DF election convergence of the control surface in the ESI convergence process is greatly reduced.

Through the steps, by combining the ARP Probe technology and the ARP proxy mechanism, the local ESI adjacency detection event can reach the far-end PE through the ARP Probe message before the RT-4 route, so that the quick DF/NDF state switching is completed on the far-end PE, the packet loss time in the DF election convergence process is reduced, and the problems that the ESI adjacency detection event only depends on BGP route transmission in the related technology and the DF election convergence performance hardly reaches BFD level performance in the related technology are solved; because the ARP message needs to be analyzed in the ARP proxy mechanism of the EVPN (see RFC7432 Section 10), the ARP Probe message is used as a transmission carrier of an ESI adjacent detection event instead of other messages, and meanwhile, the introduction of extra control message analysis in the EVPN forwarding flow is avoided, and the introduction of a detection session needing periodic interactive keep-alive is also avoided, because the ARP Probe message only needs to be temporarily inserted when the ESI fails, and meanwhile, even if the ARP Probe message is leaked to a CE, the ARP interaction between CEs cannot be seriously polluted, so that the function can be started in the butt-joint environment of a different manufacturer.

It should be noted that the ESI adjacency detection event may also be transmitted using an extended ARP message instead of the ARP Probe message in the following format: the operation code of the ARP message is a newly added value and is marked as TBD1; taking 10 bytes of ESI value as ESI1 ESI identification information, filling the first 6 bytes of ESI identification information into the sender hardware address field of ARP message, filling the last 4 bytes of ESI identification information into the target protocol address field of ARP message, and the other fields are consistent with the ARP Probe message filling method; this extended ARP message is denoted as ARP message of the first type.

It should be noted that instead of transmitting ESI adjacency detection events using extended ARP packets of the following format, the following format may also be used: compared with the first type of extended ARP message, the first 4 bytes of the ESI identification information are filled into the sender protocol address field, the second 6 bytes are filled into the target hardware address field, the target protocol address field and the sender hardware address field are both filled with specified values, and other fields are the same as the first type of extended ARP message; this extended ARP message is denoted as a second type extended ARP message.

It should be noted that, no matter the ESI state change fast propagation channel adopts the ARP Probe message, the first type extended ARP message, or the second type extended ARP message, the source MAC of the ethernet header of the outer layer (i.e. the outer layer next to the ARP layer) thereof may be filled with any one of the following values: specifying a value, an MAC address of a main interface corresponding to the ESI1, an MAC address of a sub-interface of the main interface corresponding to the ESI1, an MAC address of an IRB interface bound by an EVPN instance bound by the sub-interface of the main interface corresponding to the ESI1, and an MAC address of a rack of a node where the ESI1 fault exists; the destination MAC of the outer Ethernet header can be filled as any value as follows: the value is specified, the MAC address is broadcast.

It is worth noting that, when the ESI state change fast propagation channel sending end adopts the first or second type extended ARP packet transmission ESI adjacency detection event, the receiving end node also needs to perform the corresponding decoding adjustment, specifically, the interpretation adjustment of the ARP packet with the specified characteristic format is: the ARP message operation code value is the ARP message of TBD1; and when the destination MAC of the outer ethernet header of the ARP packet is a specified value, the destination MAC may also be directly used as an interpretation of the specified feature format at the receiving node, and at this time, the ARP packet does not need to satisfy the ARP Probe format or use an extended operation code. For convenience of description, all ARP messages used as ESI adjacency detection event transport bearers will be hereinafter collectively referred to as ARP insertion messages.

It should be noted that, after completing the corresponding flow of notifying the EVPN forwarding table management module, the ARP packet processed by the ESI state demapping module is discarded, and cannot be handed back to the EVPN forwarding table for forwarding.

It should be noted that the ARP insertion packet may also be broadcast only in a part of the I component instances accessed by the ESI1, specifically, only one I component instance needs to be selected from all I component instances bound to the same specific B component instance as a specific I component instance of the specific B component instance, and then the specific I component instance is responsible for broadcasting the ARP packet. By adopting the performance optimization scheme, an ESI state demapping module on an ESI state change rapid propagation channel receiving end node respectively informs an EVPN forwarding table management module of that ESI1 has a fault on a current DF node (at a far end) of the ESI1 one by one for members in an I component example set accessed by the ESI1, wherein the members are bound with the same B component example as an I component example to which a received ARP insertion message belongs. Moreover, with this implementation, it is necessary to ensure that the specified I-component instance also exists on each node where the specific B-component instance exists, and that all of the specified I-component instances are specified as the specified I-component instances of the specific B-component instance. By adopting the performance optimization scheme, the number of ARP insertion messages in the preferred embodiment is reduced from 20 to 2.

It is worth noting that the ARP insertion message is sent with the purpose of updating the ESI subinterface DF state of the receiving end, and on the node of the sending end, the ARP insertion message only needs to be sent in the I component example of which the corresponding ESI subinterface is in a DF role.

It will be understood by those skilled in the art that the present invention can be implemented not only on ESI in all-active mode, but also on ESI in single-active mode. ESI adjacency detection may use not only a physical signal but also a link detection technique such as EFM or TP OAM TMS.

Preferred embodiment 2

In the preferred embodiment 2, a method for detecting and processing the adjacency of ethernet segment identifiers is provided, and the following describes the preferred embodiment 2 in further detail with reference to fig. 6: as shown in fig. 6, a basic PBB EVPN service is deployed in PE1, PE2, and PE3, where CE1 is dual-homed to access PE1 and PE2, the corresponding ESI is ESI1, the corresponding B-MAC is BM1, an all-active mode is adopted, and CE2 is single-homed to access PE3. So that the PBB EVPN basic function defined by RFC7623 can work normally. After the step is completed, the EVPN control plane module and the EVPN forwarding table management module are deployed at the same time.

The ESI adjacency detection module is deployed on the link between PE1 and CE1, the ESI state mapping module is deployed on PE1, the ESI state demapping module is deployed on PE3, and the ESI state change propagation fast path is deployed between PE1 and PE3. The ESI adjacency detection module may be specifically deployed in the following manner: and standard Y.1731 transmission operation, administration and maintenance (TP) OAM TMS technology is deployed on the link to detect the state of the link, and the ESI adjacency detection module can enable the TP OAM TMS module to input the state change of the link to the ESI state mapping module at any time.

The deployment ESI state change propagation fast channel is specifically: deploying an extended PEER BFD session for TE tunnels from PE1 to PE3, wherein the state change propagation of all ESIs on the two nodes takes the PEER BFD session as a fast channel instead of one BFD session for each ESI; the PEERBFD session uses a new version number, 5, to distinguish it from the standard BFD session defined by RFC 5880. Except for different version numbers, the message format and the use method of the BFD session are completely the same as those of a standard BFD session.

step 3, an ESI state Mapping module on PE1 encodes the fault on ESI1 into PBB ESI OAM Mapping Channel Sub-TLV format, and informs the ESI state change propagation fast Channel, specifically: the ESI state Mapping module on the PE1 receives the detection state change event and determines the corresponding ESI, which is the ESI1 in this example, the ESI1 state change event is packaged in the PBB ESIOAM Mapping Channel Sub-TLV format shown in FIG. 7, and the ESI state change propagation fast Channel is notified. Wherein, the B-MAC field fills the B-MAC corresponding to ESI 1; the ESI Adjacent PE Address field is used for filling a next hop Address used when the node issues an MAC route corresponding to the B-MAC corresponding to the ESI 1; the State field padding 1 indicates Down and padding 3 indicates UP. Note that, in fig. 7, the B-MAC (continue) field is a B-MAC (continue) field, and the State field is a State field.

Step 4, a flag code is added in the BFD control message of the PEER BFD session, namely the BFD control message with the flag code of 27 does not reflect the state of the object detected by the BFD session to which the message belongs, but only serves as a general OAM mapping channel; the payload of the OAM Mapping Channel is filled in the Sub-TLV format, as shown in FIG. 5, the payload of the OAM Mapping Channel exists in the BFD control message in the form of Generic OAM Mapping Channel Sub-TLV; the PEER BFD session encapsulates the PBB ESIOAM Mapping Channel Sub-TLV input by the ESI state Mapping module into a BFD control message, wherein a Vers (version) field is 5, a Diag field is 27, and a general OAM Mapping Channel Sub-TLV field is wholly copied to the PBB ESI OAM Mapping Channel Sub-TLV, and other field values are completely the same as those of a same-name field when the Diag field value in RFC5880 is 6 (namely a linkage Path failure coordinated Path Down message), in the embodiment, only when the ESI state changes, the ESI-related message needs to be issued on the PEER session, and the ESI-related message does not need to be periodically sent (in other words, each ESI does not need to establish a BFD session), and in a normal state, the PEER BFD session does not have a per-ESI detection message; the Sub-TLV packaged by the ESI state Mapping module is transmitted to PE3 through a general OAM Mapping channel of the PEER BFD session;

and 5, on the PE3, the PEERFDD session inputs the payload part of the general OAM mapping channel carried in the BFD control message identified by the Diag field 27 to the ESI state demapping module. For the present example, the payload format is PBB ESI OAM Mapping Channel Sub-TLV format, but the BFD session does not need to analyze the payload format, but is directly submitted to the ESI state demapping module for analysis;

step 6, an ESI state demapping module on PE3 receives the PBB ESI OAM Mapping Channel Sub-TLV input by the ESI state change propagation fast Channel, analyzes the corresponding B-MAC, obtains a source node IP Address from an ESI Adjacent PE Address (Adjacent PE Address), determines a corresponding MAC route by < B-MAC, source node IP Address >, the current example is the MAC route issued by PE1 to the B-MAC corresponding to ESI1, and informs the EVPN forwarding table management module by the name of MAC route revocation, specifically: analyzing the state, up or Down, of the B-MAC from the OAM Mapping Sub-TLV;

if the B-MAC state is changed into Down, informing an EVPN forwarding table management module on the name of MAC route revocation, and inputting an MAC route revocation event corresponding to the B-MAC to the EVPN forwarding table management module by using the same API (application program interface) interface when the MAC route revocation event corresponding to the EVPN control plane is input; if the B-MAC state is changed into the Up, the EVPN forwarding table management module is not influenced; therefore, the EVPN forwarding table management module only needs to support the standard RFC7432 function to automatically support the function.

Step 7, the EVPN forwarding table management module on the PE3 processes the received MAC route revocation event according to the RFC7623, and the result results in the forwarding path switching of the corresponding B-MAC;

and 8, simultaneously, the BGP EVPN control surface also performs convergence of a forwarding member list corresponding to the B-MAC according to the inherent flow and finally completes the convergence, but when the step 7 is completed, the flow does not lose packets any more, so that the packet loss time in the ESI convergence process is greatly reduced. And, the EVPN control plane module also issues a true MAC route cancellation to the EVPN forwarding table management module, and at this time, because of the reason of step 7, the EVPN forwarding table management module does not have a corresponding forwarding path of the corresponding B-MAC, and can directly return.

Through the steps, on the basis of an ESI adjacency detection event propagation mechanism, the ESI adjacency detection event propagation mechanism is organically combined with an OAM mapping technology, so that a local ESI adjacency detection event can reach a far-end PE through an ESI state change propagation fast channel before an EAD route, fast forwarding path switching is completed on the far-end PE, packet loss time in an ES link fault convergence process is reduced, and the problems that the ESI adjacency detection event only depends on BGP route propagation in the related technology and convergence performance hardly reaches BFD level performance are solved.

The processing step may further include the steps of:

step 9, when the UP of the adjacent link of ESI1 on PE1 is recovered, PE1 may also send a message corresponding to the link UP of B-MAC to the general OAM Mapping channel, but the ESI OAM Mapping message notifying that the adjacent link becomes UP is not notified to the EVPN forwarding table management module. Meanwhile, the EVPN control plane on PE3 will resend the MAC route to take effect, and at this time, the EVPN forwarding table management module will not be affected by the OAM Mapping message that previously notified the B-MAC link DOWN corresponding to ESI 1.

Step 10, the Peer BFD session is interrupted, the EVPN forwarding table management module on the PE3 is not influenced, and the EVPN forwarding table management module only needs to be influenced by the EVPN control plane module during the interruption of the Peer BFD session;

after the step 11, after the peer BFD session is recovered, if the adjacent link state of ESI1 on PE1 is UP, PE1 may also send a message of link UP of B-MAC corresponding to ESI1 to the general OAM Mapping channel, but the ESI OAM Mapping message notifying that the adjacent link becomes UP has no influence on the EVPN forwarding table management module.

It will be understood by those skilled in the art that the present invention can be implemented not only on ESI in all-active mode, but also on ESI in single-active mode. The OAM Mapping channel not only can use peer BFD, but also can use TE BFD or TP OAM and other detection technologies. ESI adjacency detection may use not only EFM but also a link detection technique such as a physical signal.

Preferred embodiment 3

In this embodiment, a method for detecting and processing adjacency of ethernet segment identifiers is provided, and the following describes preferred embodiment 2 in further detail with reference to fig. 1: as shown in FIG. 1, a basic VXLAN EVPN service is deployed in PE1, PE2 and PE3, wherein CE1 is dually accessed to PE1 and PE2, corresponding ESI is ESI1, ethernet Tag used by the service on ESI1 is 100, ESI1 adopts single-active mode, CE2 is singly accessed to PE3. So that the EVPN basic function defined by RFC7432 can work normally. After this step is completed, the EVPN control plane module and the EVPN forwarding table management module are also deployed at the same time.

The ESI adjacency detection module is deployed on the link between PE1 and CE1, the ESI state mapping module is deployed on PE1, the ESI state demapping module is deployed on PE3, and the ESI state change propagation fast path is deployed between PE1 and PE3. The ESI adjacency detection module may include a linkBFD, EFM, CFM, and other detection modules, and may specifically deploy the ESI adjacency detection module in the following manner: deploying a standard connectivity fault management CFM technology on an AC interface of a VXLAN EVPN on a link, wherein the AC interface is a sub-interface, a VLAN encapsulated by the sub-interface is 100, and the VLAN encapsulated by the sub-interface is the same as an Ethernet Tag corresponding to a VXLAN EVPN service on ESI 1; the ESI adjacency detection module may cause the CFM module to input the state change of the AC interface to the ESI state mapping module at any time.

The deployment ESI state change propagation fast channel is specifically: a bidirectional TE tunnel is deployed between PE1 and PE3, an expanded TP OAM session is deployed on the TE tunnel, and the state change propagation of all ESIs on the two nodes takes the expanded TP OAM session as a fast channel instead of one TP OAM session for each ESI; compared with the TP OAM session of the y.1731 standard, the TP OAM session has a new CSF message format (as shown in fig. 8), where an OpCode used in the new CSF message format is different from that used in the standard CSF message, the OpCode of the standard CSF message format is 52, and the OpCode of the new CSF message format is 107. It should be noted that, in fig. 8, the management entity group level field is a MEL field, the Version field is a Version field, the identification field is a Flags field, the TLV Offset field (0) is a TLV Offset (0) field, and the Reserved (0) field is a Reserved (0) field.

step 3, an ESI state Mapping module on the PE1 encodes the fault on the ESI1 into an ESIOAM Mapping Channel Sub-TLV format, and informs an ESI state change propagation fast Channel, specifically: the ESI state Mapping module on PE1 receives the detection state change event and determines the corresponding ESI and Ethernet Tag, which is the ESI1 and the Ethernet Tag 100 thereon, encapsulates the ESI1 state change event in the ESI oam Mapping Channel Sub-TLV format shown in fig. 4, and notifies the ESI state change propagation fast Channel. Wherein the ESI field is filled in with ESI1, and the Ethernet Tag ID field is filled in with 100 to indicate that the state of the Ethernet Tag 100 on ESI1 is passed; the ESI Adjacent PE Address field is used for filling the next hop Address used by the node for externally issuing the EAD-EVI route corresponding to the Ethernet Tag 100 of the ESI 1; the State field pad 1 indicates Down, and pad 3 indicates UP;

step 4, transmitting the Sub-TLV to PE3 through a new CSF message of TP OAM conversation by an ESI state change transmission fast channel on the PE1; compared with the action of the standard CSF message, the only difference of the newly-added CSF message of the TP OAM session is that the newly-added CSF message carries a TLV, the type of the TLV is distributed by IANA, and the Value part of the TLV is an ESI OAM Mapping Channel Sub-TLV; at the transmitting end, the TP OAM session encapsulates the ESI OAM Mapping Channel Sub-TLV input by the ESI state Mapping module into a new CSF message in the format shown in fig. 8, where the filling and acting method of the fields with the same name as the standard CSF message is still the same as that in y.1731. Only when ESI state changes, it is necessary to publish ESI related message on TP OAM session, and there is no need to periodically send ESI related message (in other words, it is not necessary to establish a BFD session for each ESI), and in normal state, there is no ESI related message on TP OAM session;

step 5, on PE3, the TP OAM session identifies the ESI OAM Mapping Channel Sub-TLV carried by the new CSF message and inputs the identified ESI OAM Mapping Channel Sub-TLV to the ESI state demapping module, but the TP OAM session does not need to analyze the specific content of the ESI OAM Mapping Channel Sub-TLV; the TP OAM session does not resolve the Value part of the TLV, but is directly handed to the ESI state demapping module for processing, that is, the TP OAM session is only one Channel for transferring the ESI OAM Mapping Channel Sub-TLV;

step 6, an ESI state demapping module on the pe3 receives ESI OAM Mapping Channel Sub-TLV input by the ESI state change propagation fast Channel, analyzes that a corresponding ESI is ESI1, a corresponding Ethernet Tag is 100, a corresponding ESI Address is IP7, determines an EAD-EVI route which is issued by a PE node (i.e. PE 1) identified by the IP7 and corresponds to a binary set < ESI1,100>, and then notifies an EVPN forwarding table management module on the basis of a name of the EAD-EVI route withdrawal, specifically: analyzing the state of < ESI1,100>, up or Down from the OAM Mapping Sub-TLV; if the < ESI1,100> state is changed into Down, the EAD-EVI route withdrawal event corresponding to the EVPN control surface input < ESI1,100> is input to the EVPN forwarding table management module by using the same API interface; if the < ESI1,100> state changes to Up, the EVPN forwarding table management module is not affected. Therefore, the EVPN forwarding table management module only needs to support the standard RFC7432 function to automatically support the function.

Step 7, the EVPN forwarding table management module on the PE3 processes the received EAD-EVI route revocation event according to the RFC7432 specification, and results in the switching of the forwarding path on < ESI1,100 >;

and step 8, simultaneously, the BGP EVPN control surface also performs convergence of < ESI1,100> forwarding member lists according to the inherent flow and finally completes the convergence, but when the step 7 is completed, the flow does not lose packets any more, so that the packet loss time in the ESI convergence process is greatly reduced. And, the EVPN control plane module also issues a true EAD routing revocation to the EVPN forwarding table management module, and at this time, because of the reason of step 7, the EVPN forwarding table management module does not have a corresponding forwarding path of the corresponding ESI, and can directly return.

The above processing step may further include the steps of:

step 9, when UP is restored on the adjacent link of < ESI1,100> on PE1, PE1 may also send a message of link UP of < ESI1,100> to the general OAM Mapping channel, but the ESI OAM Mapping message notifying that the adjacent link becomes UP is not notified to the EVPN forwarding table management module. Meanwhile, the EVPN control surface on the PE3 can resend the EAD-ES route corresponding to ESI1 to take effect again, and at the moment, the EVPN forwarding table management module is not influenced by the OAM Mapping message informing < ESI1,100> link DOWN.

Step 10, the TP OAM session is interrupted, the EVPN forwarding table management module on the PE3 is not influenced, and in the period of the TP OAM session interruption, the EVPN forwarding table management module only needs to be influenced by the EVPN control surface module;

after step 11, after the tp OAM session is restored, if the adjacent link state of < ESI1,100> on PE1 is UP, PE1 may also send a message of link UP of < ESI1,100> to the general OAM Mapping channel, but the ESI OAM Mapping message notifying that the adjacent link becomes UP has no influence on the EVPN forwarding table management module.

It will be understood by those skilled in the art that the present invention can be implemented not only on ESI in all-active mode, but also on ESI in single-active mode. Not only on VXLAN encapsulated EVPN, but also on MPLS encapsulated EVPN. Not only the peer BFD but also the TE BFD or TP OAM can be used. ESI adjacency detection may use not only EFM but also link detection techniques such as CFM. The CSF message not only can use a new OpCode, but also can extend support for ESI OAM Mapping function on the basis of persisting to use an old OpCode, and is not limited to use ESI OAM Mapping Channel Sub-TLV to represent ESI adjacency detection events in the CSF message. The PEER IP address may not only be obtained from the TP OAM session, but also be carried in the CSF packet.

Preferred embodiment 4

Except where specifically noted, this preferred embodiment is the same as preferred embodiment 1.

Unlike the preferred embodiment 1, the preferred embodiment is the MPLS EVPN service established according to fig. 1, instead of the PBB EVPN service established according to fig. 6; therefore, the B-component is absent in the preferred embodiment.

The deployment ESI adjacency detection module specifically is: same as in preferred embodiment 1 except that CFM detection technique is used; thus, the preferred embodiment detects the state of the ESI subinterface rather than the ESI main interface.

The deployment ESI state mapping module specifically includes: the ESI tag is propagated to the ESI assigned by end nodes to the ESI in the fast path, except that ESI identification information is used to propagate ESI state changes.

The deployment ESI state change propagation fast channel specifically is: as in preferred embodiment 1.

The deployment ESI state demapping module specifically is: the same as in preferred embodiment 1, except that the ESI identification information is an ESI tag, and the corresponding ESI is found using the ESI tag.

The deployment ESI forwarding table management module specifically includes: the other steps are the same as those of the preferred embodiment 1 except that the EVPN example is an MPLS EVPN example;

except where otherwise specified, this step is the same as the corresponding step in preferred embodiment 1.

Unlike in preferred embodiment 1, in this step, the ESI identification information is an ESI tag, the EVPN instance is an MPLS EVPN instance, and there is no B component instance, but these are not directly embodied in the description text of the corresponding step in preferred embodiment 1, and the abstract degree of the text description is fully applicable to this preferred embodiment.

It will be understood by those skilled in the art that the present invention can be implemented not only on ESI in all-active mode, but also on ESI in single-active mode. ESI adjacency detection may use not only EFM but also a link detection technique such as CFM.

Preferred embodiment 5

This preferred embodiment is the same as preferred embodiment 4 except where specifically noted.

Unlike preferred embodiment 4, this preferred embodiment establishes a VXLAN EVPN service instead of an MPLS EVPN service.

It should be noted that there is no ESI tag in the data packet encapsulation of the VXLAN EVPN service, but an EAD-ES route of the control plane of the VXLAN EVPN service still has an ESI tag field, and may be filled with a value of a valid ESI tag, because one ESI may have multiple ESI subinterfaces, some ESI subinterfaces add MPLS EVPN, some ESI subinterfaces add VXLAN EVPN, and these subinterfaces may share one EAD-ES route, although the ESI subinterfaces that add VXLAN EVPN do not need ESI tags, the EAD-ES that add MPLS EVPN needs ESI tags, in this case, the EAD-ES route must carry a valid ESI tag value. Thus, where a valid ESI tag value is carried in the EAD-ES route, the ESI tag value can still be used as ESI identification information in the ESI state change propagation fast channel.

Thus, the format and processing flow of the ARP insertion packet of the preferred embodiment may be the same as those of the preferred embodiment 4, except that the encapsulation of the ethernet header of the ARP insertion packet is different from that of the preferred embodiment 4.

Preferred embodiment 6

This preferred embodiment is the same as preferred embodiment 5 except where specifically noted.

Unlike preferred embodiment 5, this preferred embodiment also deploys the ESI state change propagation fast-path and supporting ESI state demapping module between PE1 and PE3.

Different from preferred embodiment 5, in this preferred embodiment, 10-byte values of ESI are used as ESI identification information, and the first-type extended ARP packet described in preferred embodiment 1 is used as a format of an ARP insertion packet.

Different from the preferred embodiment 5, in the preferred embodiment, except that the PE2 node responds to the ARP insertion packet as in the preferred embodiment 5, the PE3 node also responds to the ARP insertion packet, and the ESI forwarding table management module on the PE3 node responds to the received ARP insertion packet according to the following rule: recording an EVPN instance to which the received ARP insertion message belongs as EVI1, recording a broadcast domain to which the ARP insertion message belongs in the EVI1 as BD1, and recording ESI decoded from the ARP insertion message as ESI1, then positioning a triple < ESI1, EVI1, BD1> to a group of EVPN load sharing forwarding information, further, recording an IP (virtual extensible local area network) tunnel source IP of the ARP insertion message as a BGP next hop address filled when PE1 issues an EVPN route, and recording the IP address as NH1, then the NH1 corresponds to a specific forwarding information in the group of load sharing forwarding information, and removing the forwarding information from the group of load sharing information.

It is noted that using the 10-byte value of ESI as ESI identification information relieves the preferred embodiment 5 of reliance on ESI tags and MPLS EVPN, and enables ESI adjacency detection event passing even if PE nodes only support VXLAN EVPN and do not distribute ESI tag information.

It is worth noting that the ARP insertion message is sent for a certain ESI in a specific EVPN instance aiming at updating the load sharing forwarding information, and the sending end is not affected by whether the ESI is in the DF state in the EVPN instance.

Preferred embodiment 7

This preferred embodiment is the same as preferred embodiment 6 except where specifically noted.

Unlike preferred embodiment 6, this preferred embodiment establishes MPLS EVPN services instead of VXLAN EVPN services.

Different from the preferred embodiment 6, the preferred embodiment uses the sender protocol address of the ARP insertion packet to fill in the BGP next hop address filled when the PE1 issues the EVPN route, and the remaining features of the ARP insertion packet are the same as those of the preferred embodiment 6.

Different from the preferred embodiment 5, in the preferred embodiment, the sender protocol address of the ARP insertion packet is taken as NH1, and the piece of forwarding information identified by NH1 in the load sharing forwarding information set identified by < ESI1, EVI1, BD1> is removed from the set.

It is worth noting that the PE3 node is not an adjacent node of ESI1, and it does not assign ESI tag to ESI1, so that when sending ARP insertion message to PE3, PE1 cannot adopt ESI tag as ESI identification information of ESI1 as it does when sending ARP insertion message to PE2, and adopts 10-byte ESI value of ESI1 as ESI identification information, which solves the problem of ESI identification between PE1 and PE3.

It should be noted that a field equal to the BGP next hop address filled when PE1 issues an EVPN route does not exist in an MPLS EVPN data packet sent by PE1 to PE3, and therefore, this field must be carried in an ARP insertion packet, and this field is carried by a sender protocol address, which solves this problem.

It should be noted that the ARP insertion packet may also be replaced by a neighbor solicitation packet of a neighbor discovery protocol NDP, where the role of the neighbor solicitation packet in IPv6 is the same as the role of the ARP packet in IPv 4; when the neighbor request message is used to replace the ARP insertion message, the value-taking rules of the fields can be performed by referring to the corresponding implementation mode of the ARP insertion message.

Preferred embodiment 8

This preferred embodiment is the same as preferred embodiment 1 except where specifically noted.

Unlike the preferred embodiment 1, the preferred embodiment establishes an EVPN service extended according to the preferred embodiment 18 of the patent 201711257639.8 instead of a PBB EVPN service.

It is worth noting that this extended EVPN service has similar technical effects as the PBB EVPN service, where ESI IP performs similar actions as the PBB-MAC, by which only one local ESI can be located; in addition, there are also I-component instances and B-component instances for this EVPN service, with the B-component instance being an IP-VRF and the B-component instance for the PBB EVPN being a MAC-VRF.

Different from the preferred embodiment 1, this preferred embodiment uses ESI IP as ESI identification information, and transmits in an ARP insertion message, and obtains a corresponding ESI value by ESI IP.

Unlike preferred embodiment 1, this preferred embodiment also deploys the ESI state change propagation fast channel and a supporting ESI state demapping module between PE1 and PE3.

Different from the preferred embodiment 1, the preferred embodiment uses the second type of ARP extension packet as the basic format of the ARP insertion packet, and then fills the target protocol address of the ARP extension packet as the BGP next hop address filled when the PE1 issues the EVPN route.

Different from preferred embodiment 1, in this preferred embodiment, except that the PE2 node responds to the ARP insertion packet similarly to preferred embodiment 1, the PE3 node also responds to the ARP insertion packet, and the ESI forwarding table management module on the PE3 node responds to the received ARP insertion packet according to the following rule: recording an I component example to which a received ARP insertion message belongs as EVI1, recording a B component example corresponding to the EVI1 as B _ EVI1, recording a VXLAN outer layer source IP of an ARP insertion message as ESI _ IP1, and recording a target protocol address field of the ARP insertion message as NH1, wherein the < B _ EVI1, ESI _ IP1> correspond to a group of EVPN load sharing information sets, and then removing the forwarding information corresponding to the NH1 in the sets.

It will be understood by those skilled in the art that the present invention can be implemented not only on ESI in all-active mode, but also on ESI in single-active mode. When implemented on ESI in single-active mode, all user MAC entries for VXLAN destination IP learned in the I-component instance EVI1 need only be cleared to be the ESI _ IP 1. Due to the similarity of such spread EVPN and PBB EVPN, one skilled in the art will readily refer to preferred embodiment 1 and the present preferred embodiment to migrate the present preferred embodiment to PBB EVPN.

Preferred embodiment 9

This preferred embodiment is the same as preferred embodiment 7 except where specifically noted.

Unlike the preferred embodiment 7, the ARP insertion packet in the preferred embodiment does not use an opcode field as a feature field, but uses a control word in EVPN data encapsulation and uses the control word as a feature field of the ARP insertion packet. Specifically, the control word format is the same as the PW-ACH format, and meanwhile, a new channel type value is TBD3, which indicates that ARP inserts a message. The above-mentioned characteristic field is used for distinguishing ARP insertion message from other ARP messages.

It is noted that instead of using a control word for MPLS EVPN, VXLAN EVPN may be treated as another control word for the first 4 bytes of the VXLAN-GPE header, and a B-component instance for PBB EVPN as a VPLS instance, a control word may be used.

It should be noted that the ARP insertion packet may also be replaced with an MAC-Ping insertion packet, where the MAC-Ping insertion packet has a format of an MAC Ping packet, the MAC Ping packet is a protocol packet for detecting whether a certain MAC address is reachable in the EVPN, and the MAC Ping packet may also be a protocol packet for detecting whether an outlet of a certain MAC entry is a local AC interface of the receiving end PE; when the MAC Ping message is used for replacing the ARP insert message, the characteristic field can select the mode that the destination MAC address is filled as the appointed value, and the PDU of the MAC Ping message carries ESI fault identification information.

Preferred embodiment 10

This preferred embodiment is the same as preferred embodiment 8 except where specifically noted.

Different from the preferred embodiment 8, in the preferred embodiment, the ESI fault identification information is transmitted without using an ARP insertion packet, but the ESI fault identification information is transmitted using a Ping packet, and the Ping packet is forwarded in the B component instance, but not in the I component instance; wherein, because the component B in the preferred embodiment 8 is an IP-VRF, the data plane encapsulation adopted by the Ping packet is the data packet encapsulation of the IP-VRF;

it is noted that both the B-component instance and the I-component instance are medium EVPN instances of the preferred embodiment 8, just as the B-component instance and the I-component instance are EVPN instances of PBB EVPN.

It is to be noted that the Ping message in the preferred embodiment is different from the ordinary Ping message in the IP-VRF, and the value of the ICMP type field of the Ping message is TBD5, which indicates a new Echo suggestion message, that is, a node where the destination IP address is requested to send an ICMP Echo message to the source IP (filled as the IP address corresponding to the failed ESI, that is, the ESI IP address), and meanwhile, receiving the Echo suggestion message means that the source IP has failed at the source node of the message.

It should be noted that the node where the destination IP of the ICMP Echo suggestion message is located may or may not respond to an ICMP Echo message, and if the node where the destination IP is located selects to respond to an ICMP Echo message, the node where the source IP is located does not guarantee to immediately respond to the corresponding ICMP Echo suggestion message, but replies to the corresponding ICMP Echo suggestion message after the IP is valid.

It is worth noting that ICMP Echo/Echo Reply message is also called Ping message, in PBB EVPN, B component is a VPLS instance, at this time, ping message format is MAC Ping message format, MAC Ping is protocol for detecting MAC address connectivity, each manufacturer has different message format, but all accords with Echo/Replay interaction mode, on this basis, one Echo suggestion message can be expanded. It should be noted that in the I component instance, the MAC Ping message may also be used to carry ESI fault identification information.

Example two

In this embodiment, an ethernet segment identifier adjacency detection processing apparatus is further provided, and the apparatus is used to implement the foregoing embodiments, and the description of the apparatus is omitted. As used below, the term "module" may be a combination of software and/or hardware that implements a predetermined function. Although the means described in the embodiments below are preferably implemented in software, an implementation in hardware, or a combination of software and hardware is also possible and contemplated.

Fig. 9 is a block diagram (i) of a device for detecting proximity detection of ethernet segment identifiers according to an embodiment of the present invention, as shown in fig. 9, the device includes:

a detection module 901, configured to detect an ESI adjacency detection event on a link of the ESI, where the ESI adjacency detection event is used to indicate a change in a result of detecting the ESI-identified link failure;

a notifying module 903, configured to send a first packet to a PE on a side of a second network, where the first packet is used to notify the second PE of an ESI adjacency detection event, where the first packet carries fault identification information of the ESI, and the fault identification information is used to instruct the second PE to execute an update procedure of a forwarding state corresponding to the ESI.

Through the action of the modules, detecting an ESI adjacency detection event on a link of the Ethernet segment identification ESI, wherein the ESI adjacency detection event is used for indicating the change of the detection result of the link failure identified by the ESI; sending a first message to a PE (provider edge) at the edge of a second network, wherein the first message is used for notifying an ESI (authentication information indicator) adjacency detection event to the second PE, and the first message carries fault identification information of the ESI, and the fault identification information is used for indicating the second PE to execute an updating process of a forwarding state corresponding to the ESI; therefore, the problem that ESI adjacency detection events in the related technology only depend on BGP route propagation and convergence performance hardly reaches BFD level performance can be solved, and the effects of completing rapid forwarding path switching on a far-end PE and reducing packet loss time in the ES link fault convergence process are achieved.

Optionally, the detecting module 901 is further configured to detect an ESI adjacency detection event on the link identified by the ESI by at least one of: by way of standard first mile ethernet EFM technology; the mode of operation, administration and maintenance TP OAM TMS technology is transmitted through standard Y.1731; managing CFM technology through standard connectivity fault; by detecting physical signals on the link identified by the ESI.

Optionally, the fault identification information of the ESI includes at least one of: partial binary bits of ESI; an operator backbone bridging backbone MAC address PBB-MAC corresponding to ESI or a part of binary bits in the PBB-MAC corresponding to ESI; IP address corresponding to ESI; ESI tags corresponding to ESI; encoding information for indicating that a primary interface of the ESI is malfunctioning; the ESI sub-interface used for pointing out ESI has the coded information of the trouble, wherein, ESI sub-interface is the sub-interface of the main interface that ESI corresponds to; and node identification information used for indicating the node where the link failure identified by the ESI is located.

Optionally, the encapsulating module 905 is further configured to encapsulate the ESI adjacency detection event according to the ARP packet by using at least one of the following manners:

setting an operation code of the ARP message as a preset value;

setting an Ethernet source MAC of the ARP message as an MAC address of a main interface corresponding to ESI or an ESI sub-interface of ESI;

setting an Ethernet source MAC of the ARP message to a specified value;

Optionally, fig. 10 is a block diagram (ii) of the structure of the apparatus for detecting proximity to ethernet segment identifier according to the embodiment of the present invention, as shown in fig. 10, further including: an encapsulation module 905 for encapsulating the ESI adjacency detection event by at least one of the following formats: detecting a chain path failure message of BFD by peer-to-peer bidirectional forwarding; transmitting a client signal failure indication (CSF) message of the operation, administration and maintenance (TP) OAM session; media Access Control (MAC) Ping messages; an address resolution protocol ARP message; neighbor request messages of a neighbor discovery protocol NDP; internet control message protocol ICMP messages.

packaging a PDU part message of the ARP according to a PDU format of the ARP probe message, wherein a target protocol address in the PDU is a designated IP address;

setting an operation code of the ARP message as a preset value;

setting an Ethernet source MAC of the ARP message to a specified value;

setting a target protocol address in an ARP message as fault identification information carrying ESI;

It should be noted that the above modules may be implemented by software or hardware, and for the latter, the following may be implemented, but not limited to: the modules are all positioned in the same processor; alternatively, the modules are respectively located in different processors in any combination.

Preferably, the ethernet segment identifier adjacency detection processing apparatus according to the embodiment of the present invention is described by the following embodiments, where the apparatus includes: an EVPN control surface module, which publishes and manages various EVPN routes according to RFC7432 (in fact, a BGP module is required to be arranged, the module can subdivide a plurality of sub-modules, but the module is not an innovative part of the invention and is only taken as one module in general), so that the EVPN control surface module has basic EVPN functions, wherein the EVPN control surface module comprises the management of RT-1 type EVPN routes having performance comparison relation with the invention; EVPN forwarding table management module: and forming an ESI forwarding member list according to RFC7432, and updating an ESI forwarding path according to an EAD routing validation message and a revocation message sent by an EVPN control plane module.

The device also includes:

c: ESI adjacency detection block (which may correspond to the function of the detection block 901 of the above-described embodiment): when an access link exists in a certain ESI at a node, fault detection on the link belongs to an ESI adjacency detection module, so that the ESI adjacency detection module usually embeds an existing detection module such as link BFD, EFM, CFM and the like. Compared with the prior detection modules, the ESI adjacent detection module can inform the detection result to an ESI state change propagation fast channel.

D: the ESI state mapping module: mapping refers to sending the ES detection state change event informed by the ESI adjacency detection module out of a corresponding ESI state change fast channel in a corresponding format;

e: ESI state change propagates fast channel: the propagation refers to that an event that a certain ESI fails in a corresponding link of the local node is transferred to a remote node through a fast channel such as BFD, and conversely, a remote ESI failure notification event transferred by the remote node is received and is also a function of the local module. Therefore, the ESI state change propagation fast channel is usually built in with an existing detection module such as a peer BFD and an IP BFD as a fast channel.

F: the ESI state demapping module: ganging refers to passing a remote ESI failure notification event notified by the E-module (i.e., ESI state change propagation fast channel) to the B-module (i.e., EVPN forwarding table management module), and is characterized in that its event source is not from the EAD route, but it appears to the B-module to have the same effect (even treated completely as the same event) as the transmission/cancellation of the EAD route notified by the a-module (i.e., EVPN control plane module), but to be temporally prior to the EAD route.

A. The relationships between B, C, D, E, and F are, as shown in fig. 11, the process from the event source to the final linkage with the RFC 7432-specific module (i.e., module B) in which the arrows indicate the order of event notification.

The method for detecting and processing the adjacency of the Ethernet segment identifier comprises the following steps:

the first step, ESI adjacency detecting module detects link failure on ES, including physical link failure;

secondly, the ESI adjacency detecting module notifies the failure to the ESI state mapping module;

thirdly, the ESI state mapping module informs the fault to an ESI state change propagation fast channel;

fourthly, the ESI state change propagation fast channel propagates the fault to the far-end PE in a special format through a peer BFD and other fast fault linkage channels;

fifthly, on a far-end PE, a peer BFD and other fast fault linkage channels receive fault transfer information in a special format, know that the fault transfer information is ESI adjacent detection event transmission information, and inform the ESI state demapping module of the information; analyzing which ESI corresponding ES has a fault on which far-end PE, and then informing a far-end ESI fault linkage module;

sixthly, the ESI fault demapping module learns that a certain ESI or a certain Ethernet Tag on the certain ESI has a fault, and notifies the fault to the EVPN forwarding table management module to switch the forwarding path.

EXAMPLE III

In this embodiment, an ethernet segment identifier adjacency detection processing apparatus is further provided, and the apparatus is used to implement the foregoing embodiments, and the description of the apparatus is omitted. As used below, the term "module" may be a combination of software and/or hardware that implements a predetermined function. Although the means described in the embodiments below are preferably implemented in software, an implementation in hardware or a combination of software and hardware is also possible and contemplated.

Fig. 12 is a block diagram (iv) of the ethernet segment identifier adjacency detection processing apparatus according to the embodiment of the present invention, and as shown in fig. 12, the apparatus includes:

a receiving module 131, configured to receive a first message sent by a first PE, where the first message is used to notify the device of an ESI adjacency detection event on a link of an ethernet segment identifier ESI detected by the first PE, where the ESI adjacency detection event is used to indicate a change of a result of detecting a link failure of the ESI identifier; wherein, the first message carries the fault identification information of the ESI;

and the updating module 133 is configured to execute an updating procedure of the forwarding state corresponding to the ESI according to the failure identification information.

Receiving a first message sent by the first PE through the function of the module, where the first message is used to notify the device of an ESI adjacency detection event on a link of an ethernet segment identifier ESI detected by the first PE, and the ESI adjacency detection event is used to indicate a change of a result of detecting a link failure of the ESI identifier; the first message carries fault identification information of the ESI; executing an updating process of the forwarding state corresponding to the ESI according to the fault identification information; therefore, the problem that ESI adjacency detection events in the related technology only depend on BGP route propagation and convergence performance hardly reaches BFD level performance can be solved, and the effects of completing rapid forwarding path switching on a far-end PE and reducing packet loss time in the ES link fault convergence process are achieved.

Optionally, the receiving module 131 is further configured to receive a control message encapsulating the ESI adjacency detection event through at least one of the following formats: detecting a linkage path failure message of BFD (bidirectional forwarding detection); transmitting a client signal failure indication CSF message of the operation, administration and maintenance TP OAM session; an address resolution protocol ARP message; a neighbor request message of a Neighbor Discovery Protocol (NDP); ICMP message; and the media access control MAC Ping message.

Optionally, the fault identification information of the ESI includes at least one of: partial binary bits of the ESI; PBB-MAC corresponding to ESI or part of binary bits in PBB-MAC corresponding to ESI; IP address corresponding to ESI; ESI tags corresponding to ESI; the coding information is used for indicating that the main interface corresponding to the ESI has faults; the ESI sub-interface is used for indicating that the ESI sub-interface has fault, wherein the ESI sub-interface is a sub-interface of the main interface corresponding to the ESI; and the node identification information is used for indicating the node where the link failure identified by the ESI is located.

Optionally, the receiving module 131 is further configured to receive a packet obtained by encapsulating the ESI adjacency detection event according to the ARP packet in at least one of the following manners:

the PDU part of the ARP message is a message packaged according to the PDU format of the ARP probe message, wherein the target protocol address in the PDU is a designated IP address;

the operation code of the ARP message is a preset value;

the Ethernet source MAC of the ARP message is the MAC address of the first PE;

the ethernet source MAC of the ARP packet is the specified value.

Optionally, the updating module is further configured to at least one of: changing DF/NDF/BDF states corresponding to ESI subinterfaces of the ESI; and changing the state of corresponding next hop information in the forwarding information set corresponding to the ESI.

Optionally, fig. 13 is a block diagram (five) of a structure of the ethernet segment identifier adjacency detection processing apparatus according to the embodiment of the present invention, and as shown in fig. 13, the updating module 103 includes:

a determining unit 1331, configured to determine, according to the ESI adjacency detection event, a routing type corresponding to the event to be cancelled; a generating unit 1333 for generating a predetermined route withdrawal event corresponding to the route type.

Optionally, as shown in fig. 13, the apparatus further includes: the parsing unit 135 is configured to parse the state of the adjacent link identified by the ESI from the control packet; and an input unit 137, configured to input, in a case where the state of the adjacent link is in failure, a predetermined route withdrawal event using the same application program interface API interface as that used when the ethernet virtual private network EVPN control plane inputs the predetermined route withdrawal event.

It should be noted that, the above modules may be implemented by software or hardware, and for the latter, the following may be implemented, but not limited to: the modules are all positioned in the same processor; alternatively, the modules are respectively located in different processors in any combination. The foregoing embodiment is merely an exemplary description, and in practical applications, the second PE may send the first packet to the first PE, and the first PE receives the first packet and performs an operation corresponding to the operation performed by the second PE in the foregoing embodiment.

Example four

The embodiment of the invention also provides a network side edge device, which comprises any Ethernet segment identifier adjacency detection processing device in the embodiment.

EXAMPLE five

The embodiment of the present invention further provides a storage medium, where the storage medium includes a stored program, and when the program runs, the method for detecting and processing the proximity of the ethernet segment identifier in any of the above embodiments is executed.

Optionally, in this embodiment, the storage medium may include, but is not limited to: various media capable of storing program codes, such as a usb disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a removable hard disk, a magnetic disk, or an optical disk.

Example six

The embodiment of the present invention further provides a processor, where the processor is configured to execute a program, where the program executes any method for detecting proximity to ethernet segment identifiers in the foregoing embodiments when running.

Optionally, the specific examples in this embodiment may refer to the examples described in the above embodiments and optional implementation manners, and this embodiment is not described herein again.

It will be apparent to those skilled in the art that the modules or steps of the present invention described above may be implemented by a general purpose computing device, they may be centralized in a single computing device or distributed across a network of multiple computing devices, and alternatively, they may be implemented by program code executable by a computing device, such that they may be stored in a memory device and executed by a computing device, and in some cases, the steps shown or described may be executed out of order, or separately as individual integrated circuit modules, or multiple modules or steps thereof may be implemented as a single integrated circuit module. Thus, the present invention is not limited to any specific combination of hardware and software.

The above description is only a preferred embodiment of the present invention and is not intended to limit the present invention, and various modifications and changes may be made by those skilled in the art. Any modification, equivalent replacement, or improvement made within the principle of the present invention shall be included in the protection scope of the present invention.

Claims

1. An Ethernet segment identifier adjacency detection processing method is characterized by comprising the following steps:

detecting ESI adjacency detection events on links of the ESI by the first PE, wherein the ESI adjacency detection events are used for indicating changes of detection results of ESI-identified link faults;

the first PE sends a first message to a second PE, the first message is used for notifying the ESI adjacent detection event to the second PE, wherein the first message carries fault identification information of the ESI, the fault identification information is used for indicating the second PE to execute an updating process of a forwarding state corresponding to the ESI, and the first message is an EVPN data message;

wherein the fault identification information of the ESI includes at least one of:

a partial binary bit of the ESI;

an operator backbone bridging backbone MAC address PBB-MAC corresponding to the ESI or a part of binary bits in the PBB-MAC corresponding to the ESI;

an IP address corresponding to the ESI;

ESI labels corresponding to the ESIs;

encoding information for indicating that the main interface corresponding to the ESI has a fault;

encoding information for indicating that an ESI sub-interface of the ESI has a fault, wherein the ESI sub-interface is a sub-interface of a main interface corresponding to the ESI;

and the node identification information is used for indicating the node where the link failure identified by the ESI is located.

2. A method in accordance with claim 1, wherein the ESI adjacency detection event is detected on the ESI-identified link by at least one of:

by way of standard first mile ethernet EFM technology;

managing CFM technology through standard connectivity fault;

by detecting physical signals on the link identified by the ESI.

3. The method of claim 1, further comprising: encapsulating the ESI adjacency detection event by at least one of the following message formats:

detecting a chain path failure message of BFD by peer-to-peer bidirectional forwarding;

transmitting a client signal failure indication CSF message of the operation, administration and maintenance TP OAM session;

an address resolution protocol ARP message;

a neighbor request message of a Neighbor Discovery Protocol (NDP);

internet control message protocol ICMP messages;

and the media access control MAC Ping message.

4. The method in accordance with claim 3, wherein encapsulating the ESI adjacency detection event via an ARP message comprises at least one of:

setting a sender hardware address field of the ARP message to carry fault identification information of the ESI;

setting the operation code of the ARP message as a preset value;

setting a sender protocol address field of the ARP message to carry fault identification information of the ESI;

setting an Ethernet source MAC of the ARP message as an MAC address of a main interface corresponding to the ESI or an ESI sub-interface of the ESI;

setting the Ethernet source MAC of the ARP message as the MAC address of an integrated routing bridging IRB interface of an EVPN instance bound by the ESI subinterface of the ESI;

setting the Ethernet source MAC of the ARP message to be a designated value;

setting a target protocol address in the ARP message as fault identification information carrying the ESI;

setting a target hardware address in the ARP message to carry the ESI fault identification information;

5. An Ethernet segment identifier adjacency detection processing method is characterized by comprising the following steps:

a second PE receives a first packet sent by a first PE, where the first packet is used to notify an ESI adjacency detection event on a link of an ethernet segment identifier ESI detected by the first PE to the second PE, and the ESI adjacency detection event is used to indicate a change of a result of detecting a link failure identified by the ESI; the first message carries fault identification information of the ESI, the fault identification information is used for indicating the second PE to execute an updating process of a forwarding state corresponding to the ESI, and the first message is an EVPN data message;

a partial binary bit of the ESI;

PBB-MAC corresponding to the ESI or part of binary bits in the PBB-MAC corresponding to the ESI;

an IP address corresponding to the ESI;

ESI labels corresponding to the ESIs;

encoding information used for indicating that a main interface corresponding to the ESI has faults;

encoding information used for indicating that an ESI sub-interface of the ESI has faults, wherein the ESI sub-interface is a sub-interface of a main interface corresponding to the ESI;

6. The method in accordance with claim 5, wherein the ESI adjacency detection event is encapsulated by at least one of the following formats:

detecting a linkage path failure message of BFD (bidirectional forwarding detection);

an Address Resolution Protocol (ARP) message;

a neighbor request message of a Neighbor Discovery Protocol (NDP);

internet control message protocol ICMP message;

and the media access control MAC Ping message.

7. The method in accordance with claim 6, wherein encapsulating the ESI adjacency detection event by ARP messaging comprises at least one of:

the operation code of the ARP message is a preset value;

the Ethernet source MAC of the ARP message is the MAC address of the first PE;

the Ethernet source MAC of the ARP message is the MAC address of the main interface corresponding to the ESI or the ESI sub-interface of the ESI;

the Ethernet source MAC of the ARP message is the MAC address of an integrated routing bridging IRB interface of an EVPN instance bound by the ESI subinterface of the ESI;

and the Ethernet source MAC of the ARP message is a specified value.

8. A method as described in claim 5, wherein performing an update flow of the forwarding state corresponding to the ESI comprises at least one of:

changing the appointed forwarding/non-appointed forwarding/backup appointed forwarding state corresponding to the ESI subinterface;

and changing the state of the corresponding next hop information in the unicast forwarding information set corresponding to the ESI.

9. An apparatus for detecting and processing proximity of ethernet segment identifiers, comprising:

the ESI adjacency detection event detection module is used for detecting ESI adjacency detection events on links of the ESI, wherein the ESI adjacency detection events are used for indicating changes of detection results of ESI-identified link faults;

a sending module, configured to send a first message to a second network-side edge device PE, where the first message is used to notify the ESI adjacency detection event to the second PE, where the first message carries fault identification information of the ESI, the fault identification information is used to instruct the second PE to execute an update procedure of a forwarding state corresponding to the ESI, and the first message is an EVPN data message;

a partial binary bit of the ESI;

an IP address corresponding to the ESI;

ESI labels corresponding to the ESIs;

encoding information for indicating that a primary interface of the ESI is faulty;

10. The apparatus as recited in claim 9, wherein the detection module is further configured to detect the ESI adjacency detection event on the ESI-identified link by at least one of:

by way of standard first mile ethernet EFM technology;

managing CFM technology through standard connectivity fault;

by detecting physical signals on the link identified by the ESI.

11. The apparatus of claim 9, further comprising:

an encapsulation module to encapsulate the ESI adjacency detection event by at least one of the following formats:

media Access Control (MAC) Ping messages;

neighbor request messages of a neighbor discovery protocol NDP;

internet control message protocol ICMP message;

an address resolution protocol, ARP, message.

12. The apparatus according to claim 11, wherein the encapsulating module is further configured to encapsulate the ESI adjacency detection event in accordance with an ARP packet in at least one of the following ways:

setting the operation code of the ARP message as a preset value;

setting an Ethernet source MAC of the ARP message as an MAC address of a first PE;

setting the Ethernet source MAC of the ARP message to be a designated value;

setting a target protocol address in the ARP message to carry fault identification information of the ESI;

13. An Ethernet segment identifier adjacency detection processing device, comprising:

a receiving module, configured to receive a first message sent by a first PE, where the first message is used to notify the device of an ESI adjacency detection event on a link of an ethernet segment identifier ESI detected by the first PE, and the ESI adjacency detection event is used to indicate a change of a result of detecting an ESI identified link failure; wherein, the first message carries the fault identification information of the ESI; the first message is an EVPN data message; the updating module is used for executing an updating flow of the forwarding state corresponding to the ESI according to the fault identification information;

the fault identification information of the ESI includes at least one of:

a partial binary bit of the ESI;

an IP address corresponding to the ESI;

ESI labels corresponding to the ESIs;

14. The apparatus according to claim 13, wherein the receiving module is further configured to receive a control packet encapsulating the ESI adjacency detection event by at least one of the following formats:

an address resolution protocol ARP message;

a neighbor request message of a Neighbor Discovery Protocol (NDP);

internet control message protocol ICMP messages;

and the media access control MAC Ping message.

15. The apparatus of claim 14, wherein the receiving module is further configured to receive a packet encapsulating the ESI adjacency detection event according to an ARP packet according to at least one of the following manners:

the ARP message is a message encapsulated in an EVPN message in an EVPN instance bound according to an ESI subinterface of the ESI;

the operation code of the ARP message is a preset value;

the Ethernet source MAC of the ARP message is the MAC address of the first PE;

the Ethernet source MAC of the ARP message is the MAC address of a main interface corresponding to the ESI or an ESI sub-interface of the ESI;

and the Ethernet source MAC of the ARP message is a specified value.

16. The apparatus of claim 13, wherein the update module is further configured to at least one of:

changing the appointed forwarding/non-appointed forwarding/backup appointed forwarding state corresponding to the ESI subinterface of the ESI;

17. A network-side edge device comprising the apparatus of any of claims 9 to 16.

18. A storage medium comprising a stored program, wherein the program when executed performs the method of any one of claims 1 to 4, or 5-8.