WO2019201014A1

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

Info

Publication number: WO2019201014A1
Application number: PCT/CN2019/075769
Authority: WO
Inventors: 王玉保
Original assignee: 中兴通讯股份有限公司
Priority date: 2018-04-17
Filing date: 2019-02-22
Publication date: 2019-10-24
Also published as: CN110391951A; CN110391951B

Abstract

Provided in the present application are an Ethernet segment identifier adjacency detection processing method, a device, and a storage medium. The method comprises: a first network-side edge device (PE) detects on a link of an Ethernet segment identifier (ESI) an ESI adjacency detection event, where the ESI adjacency detection event is used for indicating a change in the result of a fault detection performed on the link identified by the ESI; and the first PE transmits a first packet to a second PE, the first packet being used for notifying the second PE of the ESI adjacency detection event, where the first packet carries fault identification information of the ESI, and the fault identification information is used for instructing the second PE to execute an update process of a forwarding state corresponding to the ESI. This solves the problem in the prior art in which an ESI adjacency detection event can only rely on BGP routing for transmission and the convergence performance can hardly reach a BFD-level performance.

Description

Ethernet segment identification adjacency detection processing method and device, storage medium

Technical field

The present application relates to the field of communications, and in particular, to an Ethernet segment identification adjacency detection processing method and apparatus, and a storage medium.

Background technique

The Ethernet Virtual Private Network (EVPN) technology is used as the next-generation Layer 2 Virtual Private Network (L2VPN) technology, including the carrier backbone bridge Ethernet Provider Backbone Bridge Ethernet. Virtual Private Network (referred to as PBB EVPN), Multi-Protocol Label Switching Ethernet Virtual Private Network (MPLS EVPN), and Virtual Extensible LAN Ethernet Virtual Private Network (VXLAN EVPN) . The IETF defines the control plane of EVPN in RFC7432 in detail, and defines the data plane of MPLS EVPN in detail. Subsequently, based on RFC7432, the IETF has defined the control plane and forwarding plane of VXLAN EVPN through RFC8365. The control plane and forwarding plane of PBB EVPN are defined in RFC7623. Whether it is MPLS EVPN, VXLAN EVPN or PBB EVPN, there are corresponding descriptions for scenarios where ES is connected to the PE. The typical networking is shown in Figure 1. The lower layer in Figure 1 is also called the underlay network. :

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

An ES is connected to a number of PEs. Each PE that is accessed by the ES is called a neighboring PE of the ES. The ES is said to have an adjacency with its neighboring PEs. The same ES has the same ESI on each of its neighboring PEs.

The physical link between the ES and its neighboring PE is called the adjacent link of the ES on the adjacent PE. The state change detection on the adjacent link includes physical state change detection, protocol state change detection, and detection state change. Detection, collectively referred to as ESI adjacency detection of the ES, changes in the ESI adjacency detection state are referred to as ESI adjacency detection events.

In an EVPN network, if a PE node is not a neighboring PE of an ES, it is called a non-contiguous PE of the ES. The non-contiguous PE can know the existence of the remote ESI, and which neighboring PEs are currently present in each remote ESI, and its forwarding information to each neighboring PE of each remote ESI.

RFC7432 defines five types of EVPN routes. The first type of EVPN route is called Ethernet Auto-discovery (EAD) route and is only used in MPLS/VXLAN EVPN. The second type of EVPN route is called MAC distribution. Routing, also known as MAC routing, is used in both PBB EVPN and MPLS/VXLAN EVPN, but with different roles.

PBB EVPN and MPLS/VXLAN EVPN are different in how non-contiguous PEs discover neighboring PEs: the former maps ESI to B-MAC (Backbone MAC), and then uses the issuance and revocation of MAC routes to indicate the ESI neighboring links. Valid/invalid; the latter directly issues ESI information to the remote PE through the EAD route.

In MPLS/VXLAN EVPN, the EAD route defined by RFC7432 has two granularities, one is Ethernet auto-discovery Ethernet segmentation (EAD-ES) route, and the other is Ethernet auto-discovery EVPN instance (EAD). EVPN Instance (EAD-EVI) routes are issued by neighboring PEs of each ES. The issuance and revocation of EAD-ES and EAD-EVI routes is affected by the ES's ESI adjacency detection event on the corresponding neighboring PE.

In PBB EVPN, non-contiguous PEs do not know ESI information. The protection technology based on ESI peer-to-peer bidirectional forwarding detection BFD cannot be implemented in PBB EVPN. In MPLS/VXLAN EVPN, EAD-ES and EAD-EVI routes are carried in In BGP packets, they rely on them to propagate ESI adjacency detection events. It is difficult for convergence performance to achieve BFD-level performance.

In the related art, the ESI adjacency detection event can only rely on BGP route propagation, and the convergence performance is difficult to achieve the performance of the BFD level, and an effective solution has not been proposed.

Summary of the invention

The embodiment of the present application provides an Ethernet segment identification adjacency detection processing method and device, and a storage medium, so as to at least solve the related art, the ESI adjacency detection event can only rely on BGP route propagation, and the convergence performance is difficult to achieve the performance of the BFD level. problem.

According to an embodiment of the present application, an Ethernet segment identification adjacency detection processing method is provided, including: an ESI adjacency detection event on a link of an Ethernet segment identifier ESI detected by a first network side edge device PE, where The ESI adjacency detection event is used to indicate a change in the result of detecting the link failure identified by the ESI;

The first PE sends a first packet to the second PE, where the first packet is used to notify the second PE of the ESI adjacency detection event, where the first packet carries the fault identification information of the ESI, and the fault identifier information is used. An update flow instructing the second PE to perform a forwarding state corresponding to the ESI.

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

Pass the standard first mile Ethernet EFM technology approach;

The way to manage and maintain TP OAM TMS technology through standard Y.1731 transport operations;

The way to manage CFM technology through standard connectivity faults;

By detecting the physical signal on the link identified by ESI.

Optionally, the ESI adjacency detection event is encapsulated by using at least one of the following formats: a peer-to-peer bidirectional forwarding detection BFD chain path failure message; a transmission operation management and maintenance TP OAM session client signal failure indication CSF message; address resolution Protocol ARP packet; neighbor discovery protocol NDP neighbor request message; Internet control message protocol ICMP message; media access control MAC ping message.

Optionally, the fault identification information of the ESI includes at least one of the following: a partial binary bit of the ESI; a carrier backbone bridge MAC address PBB B-MAC corresponding to the ESI or a partial binary bit in the PBB B-MAC corresponding to the ESI; Corresponding IP address; ESI label corresponding to ESI; coding information indicating that the main interface corresponding to the ESI is faulty; coding information indicating that the ESI sub-interface of the ESI is faulty, wherein the ESI sub-interface is the main interface corresponding to the ESI Sub-interface; the node identification information of the node where the link fault of the ESI identifier is indicated.

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

The ARP packet is encapsulated into an EVPN packet, where the EVPN packet is encapsulated according to the data packet format in the EVPN instance bound to the ESI sub-interface.

The PDU part of the ARP packet is encapsulated according to the PDU format of the ARP probe packet, where the target protocol address in the PDU is the specified IP address.

Set the sender hardware address field of the ARP packet to the fault identification information carrying the ESI.

Set the operation code of the ARP packet to a predetermined value;

Set the sender protocol address field of the ARP packet to carry the fault identification information of the ESI.

Set the Ethernet source MAC address of the ARP packet to the MAC address of the first PE.

Set the Ethernet source MAC address of the ARP packet to the MAC address of the ESI sub-interface corresponding to the ESI or the ESI.

Set the Ethernet source MAC address of the ARP packet to the MAC address of the integrated routing bridged IRB interface of the EVPN instance bound to the ESI sub-interface of the ESI.

Set the Ethernet source MAC address of the ARP packet to the specified value.

Set the Ethernet destination MAC address of the ARP packet to a predetermined value.

Set the target protocol address in the ARP packet to the fault identification information carrying the ESI.

Set the target hardware address in the ARP packet to carry the ESI fault identification information.

The control word is used to encapsulate the ARP packet into the EVPN data packet, where the channel type in the control word is set to the specified value.

According to another embodiment of the present application, an Ethernet segment identification adjacency detection processing method is provided, including: a second network side edge device PE receives a first packet sent by a first PE, where the first packet is used by Notifying the second PE of the ESI adjacency detection event on the link of the Ethernet segment identifier ESI detected by the first PE, where the ESI adjacency detection event is used to indicate a change in the result of detecting the link fault identified by the ESI; The first packet carries the fault identification information of the ESI, and the fault identifier information is used to indicate that the second PE performs an update process of the forwarding state corresponding to the ESI.

Optionally, the ESI adjacency detection event is encapsulated by at least one of the following formats: a peer-to-peer bidirectional forwarding detection BFD chain path failure Concatenated Path Down message; a transmission operation management maintenance TP OAM session client signal failure indication CSF message; Resolve protocol ARP packets; neighbor discovery protocol NDP neighbor request packets; ICMP packets; media access control MAC ping packets.

Optionally, the fault identification information of the ESI includes at least one of: a partial binary bit of the ESI; a PBB B-MAC corresponding to the ESI or a partial binary bit in the PBB B-MAC corresponding to the ESI; an IP address corresponding to the ESI; and an ESI corresponding The ESI tag is used to indicate the coding information of the main interface corresponding to the ESI; the coding information for indicating that the ESI sub-interface of the ESI is faulty, wherein the ESI sub-interface is a sub-interface of the main interface corresponding to the ESI; The node identification information of the node where the link fault of the ESI is located.

Optionally, the ESI adjacency detection event is encapsulated by the ARP packet, and at least one of the following is included:

The ARP packet is encapsulated in an EVPN packet encapsulated in the data packet format of the EVPN instance bound to the ESI sub-interface.

The sender hardware address field of the ARP packet carries the fault identification information of the ESI.

The operation code of the ARP packet is a predetermined value.

The sender protocol address field of the ARP packet carries the fault identification information of the ESI.

The Ethernet source MAC address of the ARP packet is the MAC address of the first PE.

The Ethernet source MAC address of the ARP packet is the MAC address of the ESI sub-interface corresponding to the ESI or the ESI sub-interface.

The Ethernet source MAC address of the ARP packet is the MAC address of the integrated routing bridge of the EVPN instance bound to the ESI sub-interface of the ESI.

The Ethernet source MAC address of the ARP packet is the specified value.

Optionally, the update process of performing the forwarding state corresponding to the ESI includes at least one of the following: changing the specified forwarding state of the specified forwarding/non-designated forwarding/backup corresponding to the ESI sub-interface of the ESI; changing the corresponding forwarding information set corresponding to the ESI The status of the next hop information.

According to another embodiment of the present application, an Ethernet segment identification adjacency detection processing apparatus is provided, including: a detection module configured to detect an ESI adjacency detection event on a link of an Ethernet segment identifier ESI, where ESI The adjacency detection event is used to indicate a change in the result of detecting the link failure identified by the ESI;

The sending module is configured to send the first packet to the second network side edge device PE, where the first packet is used to notify the second PE of the ESI neighboring detection event, where the first packet carries the fault identification information of the ESI. The fault identification information is used to indicate that the second PE performs an update process of the forwarding state corresponding to the ESI.

Optionally, the foregoing detecting module is further configured to detect an ESI adjacency detection event on the link identified by the ESI by at least one of: passing the standard first mile Ethernet EFM technology; transmitting through the standard Y.1731 The manner in which the management manages the TP OAM TMS technology; the way in which the standard connectivity fault management CFM technology is passed; and the manner in which the physical signals on the link identified by the ESI are detected.

Optionally, the method further includes: an encapsulating module, configured to encapsulate the ESI adjacency detection event by using at least one of the following formats: a peer-to-peer bidirectional forwarding detection BFD chain path failure message; and a transmission operation management and maintenance TP OAM session client signal The CSF packet is invalid, the media access control MAC ping packet, the address resolution protocol ARP packet, the neighbor discovery protocol NDP neighbor request packet, and the Internet control packet protocol ICMP packet.

Optionally, the fault identification information of the ESI includes at least one of the following: a partial binary bit of the ESI; a carrier backbone bridge MAC address PBB B-MAC corresponding to the ESI or a partial binary bit in the PBB B-MAC corresponding to the ESI; Corresponding IP address; ESI label corresponding to ESI; coding information indicating that the main interface of the ESI is faulty; coding information indicating that the ESI sub-interface of the ESI is faulty, wherein the ESI sub-interface is the main interface corresponding to the ESI Sub-interface; the node identification information of the node where the link fault of the ESI identifier is indicated.

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

Set the operation code of the ARP packet to a predetermined value;

Set the sender protocol address field of the ARP packet to the fault identification information carrying the ESI.

Set the Ethernet source MAC address of the ARP packet to the specified value.

According to another embodiment of the present application, an Ethernet segment identification adjacency detection processing apparatus is provided, including:

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

The update module is configured to perform an update process of the forwarding state corresponding to the ESI according to the fault identification information.

Optionally, the receiving module is further configured to: receive, by using at least one of the following formats, a control packet that encapsulates the ESI adjacency detection event: a peer-to-peer bidirectional forwarding detection BFD chain path invalidation message; a transmission operation management maintenance TP OAM session The customer signal invalidation indication CSF message; the address resolution protocol ARP message; the neighbor discovery protocol NDP neighbor request message; the ICMP message; the media access control MAC ping message.

Optionally, the receiving module is further configured to: receive the packet encapsulated by the ESI neighbor detection event according to the ARP packet according to at least one of the following manners:

The PDU part of the ARP packet is a packet encapsulated according to the PDU format of the ARP probe packet, where the target protocol address in the PDU is a specified IP address.

The operation code of the ARP packet is a predetermined value.

The Ethernet source MAC address of the ARP packet is the specified value.

Optionally, the update module is configured to be at least one of the following: changing the specified forwarding state of the specified forwarding/non-designated forwarding/backup corresponding to the ESI sub-interface of the ESI; changing the corresponding next hop information in the forwarding information set corresponding to the ESI status.

According to another embodiment of the present application, a network side edge device is provided, including any of the above Ethernet segment identification adjacency detection processing devices.

According to another embodiment of the present application, a storage medium is provided. The storage medium includes a stored program that executes any of the above-described Ethernet segment identification adjacency detection processing methods when the program is running.

In accordance with another embodiment of the present application, a processor is provided that is configured to execute a program that executes any of the above described Ethernet segment identification adjacency detection processing methods while the program is running.

With the embodiment of the present application, the first network side edge device PE detects an ESI adjacency detection event on the link of the Ethernet segment identifier ESI, where the ESI adjacency detection event is used to indicate that the link fault of the ESI identifier is detected. The first PE sends a first packet to the second PE, where the first packet is used to notify the second PE of the ESI adjacency detection event, where the first packet carries the fault identification information of the ESI. The fault identification information is used to indicate that the second PE performs the update process of the forwarding state corresponding to the ESI. The ESI neighbor detection event in the related art can only rely on the BGP route propagation, and the convergence performance is difficult to achieve the performance of the BFD level. The fast forwarding path switching or the specified forwarding/non-designated forwarding/backup specified forwarding state switching is performed on the remote PE to reduce the packet loss time in the ES link failure convergence process.

DRAWINGS

The drawings described herein are intended to provide a further understanding of the present application, and are intended to be a part of this application. In the drawing:

1 is a physical topology diagram of an RFC7432 EVPN service according to an embodiment of the present application;

2 is a flowchart (1) of an Ethernet segment identification adjacency detection processing method according to an embodiment of the present application;

3 is a flowchart (2) of an Ethernet segment identification adjacency detection processing method according to an embodiment of the present application;

4 is an OAM Mapping Channel Sub-TLV format for ESI OAM Mapping according to an embodiment of the present application;

FIG. 5 is a BFD control packet format that extends the capability of a universal OAM mapping channel according to an embodiment of the present application;

6 is a physical topology diagram of an RFC7623 PBB EVPN service according to an embodiment of the present application;

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

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

9 is a structural block diagram (1) of an Ethernet segment identification adjacency detection processing apparatus according to an embodiment of the present application;

10 is a structural block diagram (2) of an Ethernet segment identification adjacency detection processing apparatus according to an embodiment of the present application;

11 is a structural block diagram (3) of an Ethernet segment identification adjacency detection processing apparatus according to an embodiment of the present application;

FIG. 12 is a structural block diagram (4) of an Ethernet segment identification adjacency detection processing apparatus according to an embodiment of the present application; FIG.

FIG. 13 is a structural block diagram (5) of an Ethernet segment identification adjacency detection processing apparatus according to an embodiment of the present application.

detailed description

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

Embodiment 1

An embodiment of the Ethernet segment identification adjacency detection processing method provided in the first embodiment can be performed in a network side edge device PE or a similar processing device. For example, the method for processing the Ethernet segment identification adjacency detection processing according to the embodiment of the present application is as follows. As shown in FIG. 2, the process includes the following steps:

Step S202, the first network side edge device PE detects an ESI adjacency detection event on the link of the Ethernet segment identifier ESI, where the ESI adjacency detection event is used to indicate a change of the result of detecting the link fault identified by the ESI. ;

Step S204: The first PE sends a first packet to the second PE, where the first packet is used to notify the second PE of the ESI neighboring detection event, where the first packet carries the fault identification information of the ESI, and the fault identifier The information is used to instruct the second PE to perform an update process of the forwarding state corresponding to the ESI.

Through the execution of the foregoing steps, the first network side edge device PE detects an ESI adjacency detection event on the link of the Ethernet segment identifier ESI, wherein the ESI adjacency detection event is used to indicate that the link fault of the ESI identifier is detected. The first PE sends a first packet to the second PE, where the first packet is used to notify the second PE of the ESI adjacency detection event, where the first packet carries the fault identification information of the ESI. The fault identification information is used to indicate that the second PE performs the update process of the forwarding state corresponding to the ESI. Therefore, the ESI neighbor detection event in the related art can only rely on the BGP route propagation, and the convergence performance is difficult to achieve the performance of the BFD level. The problem is that the fast forwarding path switching is completed on the remote PE, and the packet loss time in the ES link failure convergence process is reduced.

Pass the standard first mile Ethernet EFM technology approach;

The way to manage CFM technology through standard connectivity faults;

By detecting the physical signal on the link identified by ESI.

Optionally, the ESI adjacency detection event is encapsulated by using at least one of the following formats: a peer-to-peer bidirectional forwarding detection BFD chain path failure message; a transmission operation management maintenance TP OAM session client signal failure indication CSF message; address resolution Protocol ARP packet; neighbor discovery protocol NDP neighbor request message; Internet control message protocol ICMP message (for example, ping message, see exemplary embodiment 10); media access control MAC ping message.

Optionally, the fault identification information of the ESI includes at least one of the following: a partial binary bit of the ESI (eg, the fault identification information of the ESI includes a partial binary bit in the ESI bit); the carrier backbone bridge MAC address corresponding to the ESI Partial binary bits in PBB B-MAC corresponding to PBB B-MAC or ESI; IP address corresponding to ESI; ESI label corresponding to ESI; coding information indicating that the main interface corresponding to ESI is faulty; ESI for indicating ESI The sub-interface has the coding information of the fault, where the ESI sub-interface is a sub-interface of the main interface corresponding to the ESI; and the node identifier information is used to indicate the node (for example, the first PE) where the link fault of the ESI is located.

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

Set the operation code of the ARP packet to a predetermined value;

Set the Ethernet source MAC address of the ARP packet to the specified value.

This application combines the EVPN technology with the Operation Administration and Maintenance Mapping (OAM mapping) mechanism to make the packet loss time of the ESI (Ethernet Segment Identifier) failure convergence process in the ES dual-homing access scenario. reduce.

The embodiment 1 further provides an embodiment of an Ethernet segment identification adjacency detection processing method, which can be executed in a network side edge device PE or a similar processing device. For example, the method for processing the Ethernet segment identification adjacency detection processing according to the embodiment of the present application is as follows. As shown in FIG. 3, the process includes the following steps:

Step S302: The second network side edge device PE receives the first packet sent by the first PE, where the first packet is used to detect the ESI adjacency on the link of the Ethernet segment identifier ESI detected by the first PE. The event notification is sent to the second PE, and the ESI adjacency detection event is used to indicate a change in the result of detecting the link failure identified by the ESI; wherein the first packet carries the fault identification information of the ESI, and the fault identifier information is used to indicate the The second PE performs an update process of the forwarding state corresponding to the ESI.

The second network side edge device PE receives the first packet sent by the first PE, where the first packet is used to detect the Ethernet segment identifier detected by the first PE on the link of the ESI. The ESI adjacency detection event is notified to the second PE, and the ESI adjacency detection event is used to indicate a change in the result of detecting the link failure identified by the ESI; wherein the first packet carries the fault identification information of the ESI, and the fault identification information An update procedure for instructing the second PE to perform a forwarding state corresponding to the ESI. The foregoing technical solution can solve the problem that the ESI adjacency detection event in the related art can only rely on BGP route propagation, and the convergence performance is difficult to achieve the performance of the BFD level. The problem is that the fast forwarding path switching is completed on the remote PE, and the packet loss time in the ES link failure convergence process is reduced.

Optionally, the ESI adjacency detection event is encapsulated by at least one of the following formats: a peer-to-peer bidirectional forwarding detection BFD CFD, a CEC message, and a CSF message Address resolution protocol ARP packet; neighbor discovery protocol NDP neighbor request message; ICMP message; media access control MAC ping message.

The operation code of the ARP packet is a predetermined value.

The Ethernet source MAC address of the ARP packet is the specified value.

Optionally, the update process of performing the forwarding state corresponding to the ESI includes at least one of the following: changing the specified forwarding/non-designated forwarding/backup designated forwarding (DF/NDF/BDF) state corresponding to the ESI sub-interface of the ESI (symbol “ /" indicates "or", that is, specifies the forwarding or non-designated forwarding or backup of the specified forwarding state, DF or NDF or BDF state); changes the state of the corresponding next hop information in the forwarding information set corresponding to ESI.

This application combines the EVPN technology with the Operation Administration and Maintenance Mapping (OAM mapping) mechanism or the ARP proxy mechanism to make the ES EI (Ethernet Segment Identifier) failure convergence process in the scenario. The package time is greatly reduced.

Embodiment 1 of the present application is further described in detail below with reference to FIG. 1 :

A basic VXLAN EVPN service is deployed on PE1, PE2, and PE3. CE1 is dual-homed to PE1 and PE2. The corresponding ESI is ESI1, and all-active mode is adopted. CE2 is connected to PE3. Enables the basic EVPN functions defined in RFC7432 to function properly. 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 channel is deployed between PE1 and PE3. The ESI adjacency detection module can be configured with a link BFD, EFM, CFM, and the like. The ESI adjacency detection module can be deployed in the following manner: a standard EFM technology is deployed on the link, and the ESI adjacency detection module can enable the EFM module to chain. The state change of the road is input to the ESI state mapping module at any time.

The deployment of the ESI state change propagation fast channel is as follows: an extended peer BFD session is deployed between PE1 and PE3. The state change propagation of all ESIs at the two nodes uses the peer BFD session as a fast channel instead of One BFD session per ESI.

Take the physical failure of the link between PE1 and CE1 as an example. The processing steps are as follows:

Step 1: The ESI adjacency detection module on the PE1 detects a link fault on the ESI1, including a physical link fault.

Step 2: The ESI adjacency detection module on the PE1 notifies the ESI status mapping module of the fault on the ESI1;

Step 3: The ESI state mapping module on PE1 encodes the fault on ESI1 into the ESI OAM Mapping Channel Sub-TLV format, and notifies the ESI state change propagation fast channel. Specifically, the ESI state mapping module on PE1 receives the detection state change. The event, and determine the corresponding ESI, in this case, the ESI1, encapsulates the state change event of ESI1, encapsulates it in the ESI OAM Mapping Channel Sub-TLV format shown in FIG. 4, and notifies the ESI state change propagation fast channel. The ESI field is filled with ESI1, and the Ethernet Tag ID field is filled with 0xFFFFFFFF to indicate that the global state of ESI1 is passed (filling other non-zero values indicates that the specified Ethernet Tag is passed on ESI1); ESI Adjacent PE Address The ESI Adjacency PE Address field fills in the next hop address used by the node to issue EAD-ES routes for ESI1; the State field is 1 for Down and 3 for UP. It should be noted that 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, that is, 5, to distinguish it from the standard BFD session defined by RFC 5880. The format, usage, and standard of the BFD session are different except the version number. The BFD session is the same. The BFD control packet in the peer BFD session adds a Diag code, that is, 27, and the BFD control packet whose Diag code is 27 does not reflect the state of the object itself detected by the BFD session to which the packet belongs. The payload of the OAM Mapping channel is filled in the Sub-TLV format. As shown in Figure 5, the payload of the OAM Mapping channel exists in the BFD control packet in the form of Generic OAM Mapping Channel Sub-TLV. The ESI state change propagation fast channel on PE1 propagates the Sub-TLV encapsulated by the ESI state mapping module to PE3 through the general OAM Mapping channel of the peer BFD session. It should be noted that the status field in FIG. 5 is the Sta field, the detection time multiple field is the Detect Mult field, the self identifier field is the My Discriminator field, the other identifier field is the Your Discriminator field, and the required minimum value of the TX interval field is Desired. Min TX Interval field, the required RX interval minimum field is Required Min RX Interval.

Step 5: On the PE3, the peer BFD session inputs the payload portion of the general OAM mapping channel carried in the BFD control packet identified by the Diag field to the ESI state demapping module. For this 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 parsed by the ESI state demapping module.

Step 6: The ESI state demapping module on the PE3 receives the OAM Mapping Channel Sub-TLV input by the ESI state change propagation fast channel, parses the corresponding ESI and Ethernet Tag ID, and determines the corresponding EAD-ES route or EAD-EVI route. This example is the EAD-ES route of the ESI1, and then the EVPN forwarding table management module is notified in the name of the EAD-ES route revocation. Specifically, the state of the ESI1 is resolved from the OAM Mapping Sub-TLV, Up or Down;

If the ESI1 status changes to Down, the EAD-ES route revocation event corresponding to the EVPN control plane input ESI1 is input to the EVPN forwarding table management module using the same API interface. If the ESI1 status is Up, the EVPN forwarding is not affected. Publish the management module; therefore, the EVPN forwarding table management module can automatically support this function only by supporting the standard RFC7432 function;

Step 7: The EVPN forwarding table management module on the PE3 considers that the EAD-ES route revocation event is received and is processed according to the RFC7432, and the result is that the forwarding path is switched on the ESI1.

Step 8: At the same time, the BGP EVPN control plane also performs the convergence of the ESI1 forwarding member list according to the inherent process, and finally completes the traffic. However, when the step 7 is completed, the traffic is no longer lost, thereby greatly reducing the ESI convergence. The time of packet loss in the process. In addition, the EVPN control plane module also sends a true EAD route revocation to the EVPN forwarding table management module. At this time, due to 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 the 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 the Vers field has a value of 5 and the Diag field has a value of 27, and the Generic OAM Mapping Channel The value of the Sub-TLV field is the same as that of the ESI OAM Mapping Channel Sub-TLV. The values of other fields are the same as those of the same-named field when the value of the Diag field in the RFC5880 is 6. Only when the ESI status changes, the ESI-related packets need to be advertised on the peer BFD session. You do not need to periodically send ESI-related packets. In other words, you do not need to establish a BFD session for each ESI. There are no ESI-related packets on the BFD session.

In step 5, the payload of the OAM Mapping channel is filled in the Sub-TLV format, and the BFD session does not parse the payload content, but is directly submitted to the ESI state demapping module for parsing; as shown in FIG. 5, the OAM Mapping channel The payload exists in the form of the Generic OAM Mapping Channel Sub-TLV in the BFD control packet.

Through the above steps, based on the ESI adjacent detection event propagation mechanism, combined with the OAM mapping technology, the local ESI adjacency detection event can propagate through the ESI state change fast channel prior to the EAD route to the remote PE, thereby being far away. The fast forwarding path switching is performed on the end PE to reduce the packet loss time in the ES link failure convergence process. The ESI neighbor detection event in the related art can only rely on BGP route propagation, and the convergence performance is difficult to achieve the performance of the BFD level. problem.

The above processing steps may further include the following steps:

In step 9, when the adjacent link of the ESI1 on the PE1 is restored to the UP, the PE1 may also send the message of the link UP of the ESI1 to the common OAM Mapping channel. However, the ESI OAM Mapping message notifying that the ESI neighboring link becomes UP does not notify. Forward the EVPN forwarding table management module. At the same time, the EVPN control plane on the PE3 will re-issue the EAD-ES route corresponding to the ESI1. In this case, the EVPN forwarding table management module will not be affected by the OAM mapping message that was previously notified to the ESI1 link.

Step 10: The peer BFD session is interrupted, and the EVPN forwarding table management module on PE3 is not affected. During the peer BFD session interruption, the EVPN forwarding table management module only needs to be affected by the EVPN control plane module.

Step 11: After the peer BFD session is restored, if the neighboring link status of ESI1 on PE1 is UP, PE1 may also send a message of the link UP of ESI1 to the general OAM Mapping channel, but notify the ESI that the adjacent link becomes UP. The ESI OAM Mapping message has no effect on the EVPN forwarding table management module.

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

Those skilled in the art can understand that the present application can be implemented not only on the ESI in the all-active mode but also on the ESI in the single-active mode. The OAM mapping channel can use not only peer BFD but also TE BFD or TP OAM. ESI adjacency detection can use not only EFM but also link detection techniques such as CFM.

Exemplary embodiment 1

An Ethernet segment identification adjacency detection event transmission and processing method is provided in the first exemplary embodiment. The exemplary embodiment 1 is further described in detail below with reference to FIG. 6. As shown in FIG. 6, at PE1 and PE2. A basic PBB EVPN service is deployed with PE3. CE1 is dual-homed to PE1 and PE2. The corresponding ESI is ESI1, and the corresponding B-MAC is BM1. All-active mode is used. CE2 is connected to PE3. The basic functions of PBB EVPN defined by RFC7623 can be operated 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.

For the convenience of description, without loss of generality, it is assumed that 20 PBB EVPN services are established in PE1, PE2 and PE3, and their PBB I component instances are respectively recorded as zteI1, zteI2, ... zteI20, where zteI1, zteI2, ... zteI10 are corresponding. The PBB B component instances are all zteB1, zteI11, zteI12...zteI20 corresponding PBB B component instances are all zteB2. It is assumed that the ESI1 is the designated forwarding DF role on PE1 and the non-designated forwarding NDF role on PE2.

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

The ESI adjacency detection module is specifically configured: no port state detection technology (such as EFM, TP OAM TMS, etc.) may be deployed on the physical link of the primary interface corresponding to the ESI1, but the physical signal of the link is detected, and the ESI adjacency detection is performed. The module can input the physical state changes of the link to the ESI state mapping module at any time.

The ESI state mapping module is configured to: generate an ARP probe (ARP Probe) packet, and fill in the target protocol address field of the ARP Probe packet to specify the ESI neighboring detection event. The IP address, the sender hardware address field is filled in as the ESI identification information of the ESI corresponding to the ESI adjacency detection event, and then the ARP Probe message is delivered to the ESI state change propagation fast channel; wherein the ESI identification information is the ESI corresponds to PBB B-MAC.

The deployment of the ESI state change propagation fast channel is specifically: on PE1, for each sub-interface of the primary interface corresponding to the ESI, copy the ARP Probe packet, and the I component instance bound to the sub-interface The ARP probe packet is broadcasted. The outer layer (that is, the outer layer of the ARP layer) is added to the ARP probe packet. The destination MAC address is the specified MAC address and the destination MAC address is All FFs; it is worth noting that the outer layer of the ARP probe packet that is finally broadcast out will have the same format as the BUM data packet in the EVPN instance; on PE2, the ESI state changes. The ARP probe packet of the specified feature format is received from the network side and is forwarded to the ESI state demapping module. The other ARP probe packets are still processed according to the prior art. The ARP probe packet, that is, the ARP probe packet whose destination protocol address is the specified IP address, wherein the specified IP address is the same as the value specified by the specified IP address in the ESI state mapping module.

The ESI state demapping module is configured to: receive an ARP packet from the ESI state change propagation fast channel, read the content of the sender hardware address field, and interpret it as a B-MAC address, and then convert the B-MAC address into Corresponding ESI corresponding to the primary interface, and submitting the ESI and an identifier of the I component instance that receives the ARP Probe message to the ESI forwarding table management module.

The ESI forwarding table management module is configured to: after receiving the ESI main interface and the I component instance identifier input by the ESI state demapping module, find a sub-interface bound to the I component instance on the main interface, and Set it to the DF state;

Take the physical failure of the link between PE1 and CE1 as an example. The processing steps in the process part are as follows:

Step 3: The ESI state mapping module on the PE1 encodes the fault on the ESI1 into an ARP Probe packet in a specified format.

Step 4: The ESI state change propagation fast channel on the PE1 broadcasts the ARP probe packet in each I component instance accessed by the ESI1.

Step 5: On the PE2, the ESI state change propagation fast channel delivers the received ARP Probe packet of the specified format to the ESI state demapping module.

Step 6, on the PE2, the ESI state demapping module notifies the forwarding table management module ESI1 that a remote fault has occurred in the corresponding I component instance (taking the zte1 instance as an example); it is noted that, in the present exemplary embodiment, All 20 I component instances will receive a notification that a remote fault has occurred in ESI1.

Step 7, on the PE2, the EVPN forwarding table management module sets the sub-interface used by the ESI1 to the zte1 instance to be in the DF state;

Step 8: At the same time, the BGP EVPN control plane is also convening the DF election of the ESI1 according to the inherent process of the RFC7623 and is finally completed. However, when the step 7 is completed, the broadcast traffic broadcasted by the PE3 to the PE2 is no longer discarded by the PE2. The degree of loss reduces the packet loss time caused by the slow convergence of the DF election of the control plane during the ESI convergence process.

Through the above steps, by combining with the ARP Probe technology and the ARP proxy mechanism, the local ESI adjacency detection event can reach the remote PE through the ARP probe packet before the RT-4 route, thereby completing the fast DF/ on the remote PE. The NDF state is switched to reduce the packet loss time in the DF election convergence process. The ESI neighbor detection event in the related art can only rely on BGP route propagation. The DF election convergence performance is difficult to achieve the BFD performance. In the ERP ARP proxy mechanism, it needs to be resolved (see RFC7432Section 10). The ARP probe packet is used as the transmission carrier for the ESI proximity detection event instead of other packets, and the extra scheme is introduced in the EVPN forwarding process. Controlling packet parsing also avoids the need to introduce a test session that requires periodic interaction and keep-alive. Because ARP probe packets need to be temporarily inserted in the event of an ESI fault, even if the ARP probe packet is leaked to the CE, The ARP interaction between CEs causes serious pollution, which makes this feature open in a different vendor docking environment.

It is noted that the ACS adjacency detection event may be transmitted by using the extended ARP packet in the following format instead of the ARP probe packet: the operation code of the ARP packet is newly added, and is recorded as TBD1; The ESI value is used as the ESI identification information of the ESI1, and the first 6 bytes of the ESI identification information are filled in the sender hardware address field of the ARP packet, and the last 4 bytes of the ESI identification information are filled in the In the target protocol address field of the ARP packet, the other fields are the same as the ARP probe packet. The extended ARP packet is recorded as the first type of ARP packet.

It should be noted that the extended ARP packet in the following format may be used instead of the first type of extended ARP packet transmission ESI adjacency detection event: compared with the first type of extended ARP packet, the ESI identification information is 4 bytes are filled in its sender protocol address field, and the last 6 bytes are filled in the target hardware address field. The target protocol address field and the sender hardware address field are filled in with the specified values. The other fields are the same as the first type of extended ARP packets. This extended ARP packet is recorded as the second type of extended ARP packet.

It is worth noting that the ESI state change fast propagation channel uses the ARP Probe packet, the first type of extended ARP packet, or the second type of extended ARP packet, and the outer layer (ie, the outer layer adjacent to the ARP layer) is the Ethernet header. The source MAC address can be filled in as follows: a specified value, a MAC address of the primary interface corresponding to the ESI1, a MAC address of a sub-interface corresponding to the ESI1, and a sub-interface corresponding to the ESI1 MAC address of the IRB interface bound to the EVPN instance bound to the interface. The MAC address of the node where the ESI1 fault is located. The destination MAC address of the outer Ethernet header can be filled in any of the following values: specified value, broadcast. MAC address.

It is worth noting that when the ESI state change fast propagation channel transmitting end uses the first type or the second type of extended ARP packet to transmit the ESI adjacency detection event, the receiving end node also needs to perform corresponding decoding adjustment, specifically, the corresponding The description of the specified feature format ARP packet is adjusted to: the ARP packet operation code takes the value of the ARP packet of the TBD1; and when the destination MAC address of the outer layer of the ARP packet is the specified value, the receiving end is On the node, the destination MAC address can be directly used as the specified value as the specified feature format. In this case, the ARP packet does not need to meet the ARP Probe format or use the extended operation code. For the convenience of description, all ARP messages used as the transmission carrier of the ESI adjacency detection event are collectively referred to as ARP insertion messages.

It is worth noting that the ARP packets processed by the ESI state demapping module are discarded after the corresponding EVPN forwarding table management module process is completed, and cannot be returned to the EVPN forwarding plane for forwarding.

It should be noted that the ARP insertion message may also be broadcast only in the part I component instance accessed by the ESI1. Specifically, only the I component instances bound to the same specific B component instance need to be selected. An I component instance is taken as the specified I component instance of the specific B component instance, and then the specified I component instance is responsible for broadcasting the ARP message, so that the number of B component instances is typically much smaller than the I component. As an example, the number of ARP insertion messages will be greatly reduced, thereby further improving performance. With this performance optimization scheme, the ESI state demapping module on the receiver node of the ESI state change fast propagation channel is the I of the I component instance set accessed by ESI1 and the I inserted into the received ARP packet. The component instance binds the members of the same B component instance to notify the EVPN forwarding table management module one by one that the ESI1 has failed on its current DF node (at the far end). Moreover, with this implementation, it is necessary to ensure that the specified I component instance also exists at each node where the specific B component instance exists, and is designated as the specified I component of the specific B component instance. Example. With this performance optimization scheme, the number of ARP insertion messages in this exemplary embodiment will be reduced from 20 to 2.

It is to be noted that the ARP insertion packet is sent for the purpose of updating the DES state of the ESI sub-interface of the receiving end, and only the instance of the I component in which the corresponding ESI sub-interface is in the DF role needs to be sent in the sending-side node. ARP inserts a message.

Those skilled in the art can understand that the present application can be implemented not only on the ESI in the all-active mode but also on the ESI in the single-active mode. ESI adjacency detection can use not only physical signals, but also link detection techniques such as EFM and TP OAM TMS.

Exemplary embodiment 2

An Ethernet segment identification adjacency detection processing method is provided in the exemplary embodiment 2, and the exemplary embodiment 2 is further described in detail below with reference to FIG. 6. As shown in FIG. 6, deployed in PE1, PE2, and PE3. A basic PBB EVPN service, in which CE1 is dual-homed to PE1 and PE2, the corresponding ESI is ESI1, the corresponding B-MAC is BM1, all-active mode is adopted, and CE2 is directly connected to PE3. The basic functions of PBB EVPN defined by RFC7623 can be operated 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 channel is deployed between PE1 and PE3. Specifically, the ESI adjacency detection module may be deployed in the following manner: a standard Y.1731 transmission operation management and maintenance TP OAM TMS technology is deployed on the link to detect the status of the link, and the ESI adjacency detection module can make the TP OAM TMS The module inputs the state change of the link to the ESI state mapping module at any time.

The deployment of the ESI state change propagation fast channel is as follows: an extended PEER BFD session is deployed to the TE tunnel of the PE1 to the PE3. The state change propagation of all the ESIs at the two nodes uses the PEER BFD session as the fast channel. Not a BFD session for each ESI; the PEER BFD session uses a new version number, 5, to distinguish it from the standard BFD session defined by RFC5880. The format and usage of the BFD session are the same as those of the standard BFD session.

Step 3: The ESI state mapping module on PE1 encodes the fault on ESI1 into the PBB ESI OAM Mapping Channel Sub-TLV format, and notifies the ESI state change propagation fast channel, specifically: the ESI state mapping module on PE1 receives the detection state. The event is changed, and the corresponding ESI is determined. In this example, the ESI1 is encapsulated by the PBB ESI OAM Mapping Channel Sub-TLV format shown in FIG. 7 and the ESI state change propagation is fast. aisle. The B-MAC field is filled with the B-MAC corresponding to the ESI1; the ESI Adjacent PE Address field is used to fill the next hop address used by the B-MAC corresponding to the ESI1 issued by the node; the State field is filled with 1 to indicate Down. Fill in 3 to indicate UP. It should be noted that the B-MAC (continue) field in FIG. 7 is a B-MAC (continue) field, and the status field is a State field.

In step 4, a new Diag code is added to the BFD control packet of the PEER BFD session, that is, 27, and the BFD control packet whose Diag code is 27 does not reflect the state of the object itself detected by the BFD session to which the packet belongs, but only The payload of the OAM Mapping channel is filled in the Sub-TLV format. As shown in Figure 5, the payload of the OAM Mapping channel exists in the BFD control packet in the form of a Generic OAM Mapping Channel Sub-TLV. The PEER BFD session encapsulates the PBB ESI OAM Mapping Channel Sub-TLV input into the BFD control packet. The Vers (version) field has a value of 5 and the Diag field has a value of 27. The Generic OAM Mapping Channel Sub- The value of the TLV field is the same as that of the PBB ESI OAM Mapping Channel Sub-TLV. The values of other fields are the same as those of the same name field when the value of the Diag field in the RFC5880 is 6 (that is, the Concatenated Path Down message is invalid). In this embodiment, only when the ESI state changes, the ESI-related packet needs to be advertised on the PEER BFD session, and the ESI-related packet does not need to be sent periodically (in other words, There is no need to establish a BFD session for each ESI. In the normal state, there is no per-ESI packet in the PEER BFD session. The Sub-TLV encapsulated by the ESI state mapping module is transmitted to the PE3 through the common OAM Mapping channel of the PEER BFD session.

Step 5: On the PE3, the PEER BFD session inputs the payload portion of the general OAM mapping channel carried in the BFD control packet identified by the Diag field to the ESI state demapping module. For this example, the payload format is the PBB 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, the ESI state demapping module on the PE3 receives the PBB ESI OAM Mapping Channel Sub-TLV of the ESI state change propagation fast channel input, parses the corresponding B-MAC, and obtains the source from the ESI Adjacent PE Address. End the IP address, and then determine the corresponding MAC route with <B-MAC, source node IP address>. In this example, PE1 advertises the MAC route advertised by B-MAC corresponding to ESI1, and then in the name of MAC route revocation. The EVPN forwarding table management module is configured to: parse the status of the B-MAC from the OAM Mapping Sub-TLV, Up or Down;

If the B-MAC status is Down, the EVPN forwarding table management module is notified in the name of the MAC route revocation, and the MAC address revocation event corresponding to the B-MAC input on the EVPN control plane is input to the EVPN forwarding table management module by using the same API interface; If the B-MAC status changes to Up, the EVPN forwarding table management module is not affected. Therefore, the EVPN forwarding table management module can automatically support this function only by supporting the standard RFC7432 function.

Step 7: The EVPN forwarding table management module on the PE3 considers that the MAC route revocation event is received and is processed according to the RFC7623, and the result is that the forwarding path of the corresponding B-MAC is switched.

Step 8: At the same time, the BGP EVPN control plane also performs the convergence of the forwarding member list corresponding to the B-MAC according to the inherent process, and finally completes, but when the step 7 is completed, the traffic is no longer lost, thereby greatly Reduced packet loss time during ESI convergence. In addition, the EVPN control plane module sends a true MAC route revocation to the EVPN forwarding table management module. In this case, the EVPN forwarding table management module does not have a corresponding forwarding path of the corresponding B-MAC. return.

The above processing steps may further include the following steps:

In step 9, when the adjacent link of ESI1 on PE1 is restored to UP, PE1 may also send a message of the link UP corresponding to the B-MAC to the general OAM Mapping channel, but notify the ESI that the adjacent link becomes UP. The message will not be notified to the EVPN forwarding table management module. At the same time, the EVPN control plane on PE3 will re-deliver the MAC address. In this case, the EVPN forwarding table management module will not be affected by the OAM mapping message of the B-MAC link DOWN that was previously notified to ESI1.

Step 10: The PEER BFD session is interrupted, and the EVPN forwarding table management module on PE3 is not affected. Moreover, during the PEER BFD session interruption, the EVPN forwarding table management module only needs to be affected by the EVPN control plane module.

Step 11: After the PEER BFD session is restored, if the status of the adjacent link of ESI1 on PE1 is UP, PE1 may also send a message of the link UP of the B-MAC corresponding to ESI1 to the general OAM Mapping channel, but notify the ESI adjacency chain. The ESI OAM Mapping message whose path becomes UP has no effect on the EVPN forwarding table management module.

Those skilled in the art can understand that the present application can be implemented not only on the ESI in the all-active mode but also on the ESI in the single-active mode. The OAM mapping channel can use not only peer BFD but also TE BFD or TP OAM. ESI adjacency detection can use not only EFM but also link detection techniques such as physical signals. Moreover, BFD control messages

Exemplary embodiment 3

An Ethernet segment identification adjacency detection processing method is provided in this embodiment. The exemplary embodiment 2 is further described in detail below with reference to FIG. 1. As shown in FIG. 1, a basic configuration is deployed on PE1, PE2, and PE3. VXLAN EVPN service, in which CE1 is dual-homed to PE1 and PE2, and the corresponding ESI is ESI1. The Ethernet tag used in ESI1 is 100, ESI1 is in single-active mode, and CE2 is connected to PE3. Enables the basic EVPN functions defined in RFC7432 to function properly. 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 channel is deployed between PE1 and PE3. The ESI adjacency detection module can be configured with a link BFD, EFM, and CFM detection module. The ESI adjacency detection module can be deployed in the following manner: A standard connectivity fault management CFM technology is deployed on the AC interface of the VXLAN EVPN on the link. The AC interface is a sub-interface. The sub-interface encapsulates the VLAN 100, which is the same as the Ethernet tag corresponding to the VXLAN EVPN service on the ESI1. The ESI adjacency detection module enables the CFM module to input the status change of the AC interface to the ESI status mapping module at any time. .

The deployment of the ESI state change propagation fast channel is specifically: deploying a bidirectional TE tunnel between PE1 and PE3, and deploying an extended TP OAM session on the TE tunnel, and all ESI state change propagations at the two nodes are The extended TP OAM session is used as a fast channel instead of a TP OAM session for each ESI. The TP OAM session has a new CSF packet format compared to the TP OAM session of the Y.1731 standard (as shown in Figure 8). The operation code (OpCode) used in the new CSF message format is different from 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 the management entity group level field in FIG. 8 is the MEL field, the version field is the Version field, the identification field is the Flags field, the TLV offset field (0) is the TLV Offset (0) field, and the reserved (0) field. That is, the Reserved (0) field.

Step 3: The ESI state mapping module on PE1 encodes the fault on ESI1 into the ESI OAM Mapping Channel Sub-TLV format, and notifies the ESI state change propagation fast channel. Specifically, the ESI state mapping module on PE1 receives the detection state change. The event, and determine the corresponding ESI and Ethernet Tag, in this example, the ESI1 and the Ethernet Tag 100 thereon, and encapsulate the state change event of the ESI1 in the ESI OAM Mapping Channel Sub-TLV format shown in FIG. 4, and Notifies the ESI state change propagation fast track. The ESI field is filled with ESI1, the Ethernet Tag ID field is filled with 100 to indicate the status of the Ethernet Tag 100 on the ESI1, and the ESI Adjacent PE Address field is used to fill the EAD-EVI route corresponding to the Ethernet Tag100 of the ESI1. Next hop address; the State field is filled with 1 for Down and 3 for UP;

Step 4: The ESI state change propagation fast channel on the PE1 propagates the new CSF packet of the Sub-TLV through the TP OAM session to the PE3. The new CSF packet of the TP OAM session is compared with the standard CSF packet. The only difference is that it carries a TLV. The type of the TLV is assigned by IANA. The Value part of the TLV is an ESI OAM Mapping Channel Sub-TLV. At the transmitting end, the ESI OAM session inputs the ESI OAM into the ESI Status Mapping Module. The mapping channel Sub-TLV is encapsulated into a new CSF packet in the format shown in Figure 8. The fields of the same name as the standard CSF packet are still filled and functioned in the same manner as in Y.1731. Only when the ESI status changes, the ESI-related packets need to be advertised on the TP OAM session. You do not need to periodically send ESI-related packets. In other words, you do not need to establish a BFD session for each ESI. Normally, TP There are no ESI related messages on the OAM session;

Step 5: On the PE3, the TP OAM session is identified by the ESI OAM Mapping Channel Sub-TLV carried in the new CSF message and input to the ESI state demapping module, but the TP OAM session does not need to be parsed by the ESI OAM Mapping Channel Sub- The specific content of the TLV; the TP OAM session itself does not parse the Value part of the TLV, but will directly hand it over to the ESI state demapping module. That is, the TP OAM session only passes the ESI OAM Mapping Channel Sub-TLV. One channel;

Step 6: The ESI state demapping module on the PE3 receives the ESI OAM Mapping Channel Sub-TLV of the ESI state change propagation fast channel input, and parses the corresponding ESI as ESI1, the corresponding Ethernet Tag is 100, and the ESI Adjacent PE Address is IP7, and Determining an EAD-EVI route corresponding to the dual group <ESI1, 100> issued by the PE node identified by the IP7 (ie, PE1), and then notifying the EVPN forwarding table management module in the name of the EAD-EVI route revocation. Specifically, the state of <ESI1, 100> is parsed from the OAM Mapping Sub-TLV, Up or Down; if the <ESI1, 100> state is Down, the EAD corresponding to the EESI control plane input <ESI1, 100> - EVI route revocation event is input to the EVPN forwarding table management module using the same API interface; if the <ESI1, 100> status is Up, the EVPN forwarding table management module is not affected. Therefore, the EVPN forwarding table management module can automatically support this function only by supporting the standard RFC7432 function.

Step 7: The EVPN forwarding table management module on the PE3 considers that the EAD-EVI route revocation event is received and is processed according to the RFC7432, and the result is a forwarding path switch on <ESI1, 100>;

Step 8: At the same time, the BGP EVPN control plane performs the convergence of the <ESI1,100> forwarding member list according to the inherent process, and finally completes the traffic. However, when the step 7 is completed, the traffic is no longer lost. Reduced packet loss time during ESI convergence. In addition, the EVPN control plane module also sends a true EAD route revocation to the EVPN forwarding table management module. At this time, due to 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 steps may further include the following steps:

Step 9. When the adjacent link of <ESI1, 100> on PE1 is restored to UP, PE1 may also send a message of <ESI1, 100> link UP to the general OAM Mapping channel, but notify the ESI adjacent link to become The ESI OAM Mapping message of the UP is not notified to the EVPN forwarding table management module. At the same time, the EVPN control plane on the PE3 will re-issue the EAD-ES route corresponding to the ESI1. In this case, the EVPN forwarding table management module will not be affected by the OAM mapping message that was previously notified to the <ESI1,100> link DOWN.

Step 10: The TP OAM session is interrupted, and the EVPN forwarding table management module on the PE3 is not affected. Moreover, during the TP OAM session interruption, the EVPN forwarding table management module only needs to be affected by the EVPN control plane module;

Step 11: After the TP OAM session is restored, if the neighboring link status of <ESI1, 100> on PE1 is UP, PE1 may also send a message of <ESI1, 100> link UP to the general OAM Mapping channel, but notify The ESI OAM Mapping message with the ESI adjacency link becoming UP has no effect on the EVPN forwarding table management module.

Those skilled in the art can understand that the present application can be implemented not only on the ESI in the all-active mode but also on the ESI in the single-active mode. It can be implemented not only on the EVPN of the VXLAN package but also on the EVPN of the MPLS package. You can use not only peer BFD but also TE BFD or TP OAM. ESI adjacency detection can use not only EFM but also link detection techniques such as CFM. CSF packets can not only use the new OpCode, but also extend the support of the ESI OAM mapping function based on the old OpCode. Moreover, the CSF message is not limited to the ESI OAM Mapping Channel Sub-TLV to represent the ESI. Adjacency detection event. The PEER IP address can be obtained not only from the TP OAM session but also in the CSF packet.

Exemplary embodiment 4

The present exemplary embodiment is the same as Exemplary Embodiment 1, except where specifically stated.

Unlike the exemplary embodiment 1, the present exemplary embodiment is the MPLS EVPN service established in accordance with FIG. 1, instead of the PBB EVPN service established in accordance with FIG. 6; therefore, there is no B component in the present exemplary embodiment.

The deployment of the ESI adjacency detection module is specifically the same as that of the exemplary embodiment 1 except that the CFM detection technique is used; therefore, the present exemplary embodiment detects the state of the ESI sub-interface instead of the state of the ESI main interface.

The deployment of the ESI state mapping module is specifically the same as the exemplary embodiment 1 except that the ESI identification information takes the ESI status change propagation fast channel receiving end node as the ESI label assigned to the ESI.

The deployment of the ESI state change propagation fast channel is specifically the same as in the exemplary embodiment 1.

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

The ESI forwarding table management module is specifically configured to be the same as the exemplary embodiment 1 except that the EVPN instance is an MPLS EVPN instance.

This step is the same as the corresponding step in Exemplary Embodiment 1, except where specifically stated.

Different from the exemplary embodiment 1, the ESI identification information is an ESI label in this step, the EVPN instance is an MPLS EVPN instance, and there is no B component instance, but these are not directly reflected in the corresponding step in the exemplary embodiment 1. Within the description text, the degree of abstraction described by the text is fully applicable to the present exemplary embodiment.

Those skilled in the art can understand that the present application can be implemented not only on the ESI in the all-active mode but also on the ESI in the single-active mode. ESI adjacency detection can use not only EFM but also link detection techniques such as CFM.

Exemplary embodiment 5

The present exemplary embodiment is the same as Exemplary Embodiment 4 except where specifically stated.

Unlike the exemplary embodiment 4, the present exemplary embodiment establishes a VXLAN EVPN service instead of an MPLS EVPN service.

It is worth noting that there is no ESI label in the data packet encapsulation of the VXLAN EVPN service. However, there is still an ESI label field in the EAD-ES route of the control plane, and the value of the valid ESI label can be filled in, because An ESI can have multiple ESI sub-interfaces. Some of the ESI sub-interfaces are added to the MPLS EVPN. Some ESI sub-interfaces are added to the VXLAN EVPN. These sub-interfaces can share an EAD-ES route. Although the ESI sub-interface of the VXLAN EVPN is not added. The ESI label is required. The EAD-ES that joins the MPLS EVPN requires the ESI label. In this case, the EAD-ES route must carry a valid ESI label value. Therefore, in the case where the EAD-ES route carries a valid ESI tag value, the ESI tag value can still propagate the ESI identification information in the fast channel as the ESI state change.

In this way, the format and processing flow of the ARP insertion message of the present exemplary embodiment can be different from that in the exemplary embodiment 4, except that the encapsulation other than the Ethernet header of the ARP insertion message is different from that in the exemplary embodiment 4. Are the same.

Exemplary embodiment 6

The present exemplary embodiment is the same as Exemplary Embodiment 5 except where specifically stated.

Unlike the exemplary embodiment 5, the present exemplary embodiment also deploys the ESI state change propagation fast channel and the associated ESI state demapping module between PE1 and PE3.

Unlike the exemplary embodiment 5, the present exemplary embodiment adopts a 10-byte value of ESI as the ESI identification information, and adopts the first-class extended ARP message described in the exemplary embodiment 1 as the format of the ARP insertion message.

Unlike the exemplary embodiment 5, in the present exemplary embodiment, in addition to the PE2 node responding to the ARP insertion message as in the exemplary embodiment 5, the PE3 node also responds to the ARP insertion message, on the PE3 node. The ESI forwarding table management module responds to the received ARP insertion packet according to the following rules: the EVPN instance to which the received ARP insertion packet belongs is recorded as EVI1, and the ARP insertion packet is recorded in the broadcast domain of the EVI1. For BD1, the ESI decoded from the ARP insertion message is recorded as ESI1, and the triplet <ESI1, EVI1, BD1> is located to locate a set of EVPN load sharing forwarding information, and further, the ARP insertion report The source IP address of the VXLAN tunnel is the BGP next hop address that is filled in when the PE1 advertises the EVPN route. If the IP address is recorded as NH1, the NH1 corresponds to a specific forwarding information in the load balancing information. The piece of forwarding information is removed from the set of load sharing information.

It is worth noting that using the 10-byte value of ESI as the ESI identification information removes the dependency of the exemplary embodiment 5 on the ESI label and the MPLS EVPN, even if each PE node only supports VXLAN EVPN and does not distribute ESI label information. Can complete the ESI adjacency detection event delivery.

It is worth noting that the ARP insertion message is sent to an ESI in a specific EVPN instance for the purpose of updating the load sharing forwarding information, and the sender is not affected by the DF state of the ESI in the EVPN instance.

Exemplary embodiment 7

The present exemplary embodiment is the same as Exemplary Embodiment 6, except where specifically stated.

Unlike the exemplary embodiment 6, the present exemplary embodiment establishes an MPLS EVPN service instead of a VXLAN EVPN service.

Different from the exemplary embodiment 6, the exemplary embodiment uses the sender protocol address of the ARP insertion message to fill in the BGP next hop address filled in when the E1 route is advertised by the PE1. The remaining features of the ARP insertion packet are the same as the exemplary embodiment. 6.

Different from the exemplary embodiment 5, in the present exemplary embodiment, the sender protocol address of the ARP insertion message is recorded as NH1, and the load sharing forwarding information set identified by <ESI1, EVI1, BD1> is The forwarding information identified by NH1 is removed from the set.

It is worth noting that the PE3 node is not an ESI1 adjacency node. It does not assign an ESI label to ESI1. Therefore, when PE1 sends an ARP insertion packet to PE3, it cannot use ESI as it sends an ARP insertion packet to PE2. As the ESI identification information of ESI1, the label uses ESI1's 10-byte ESI value as the ESI identifier to solve the ESI identification problem between PE1 and PE3.

It is worth noting that the MPLS EVPN data packet sent by PE1 to PE3 does not have the same BGP next hop address as the PE1 advertises the EVPN route. Therefore, the field must be carried in the ARP insertion packet. The sender protocol address carries this field, which solves this problem.

It is noted that the above-mentioned ARP insertion message can also be replaced by the neighbor discovery protocol NDP neighbor request message. The role of the neighbor request message in IPv6 is the same as that of the ARP message in IPv4; When a packet is substituted for an ARP insertion packet, the rules for the value of each field can be referred to the corresponding implementation of the ARP insertion packet.

Exemplary embodiment 8

Unlike the exemplary embodiment 1, the present exemplary embodiment establishes an EVPN service that is extended according to the exemplary embodiment 18 of the patent 201711257639.8 instead of the PBB EVPN service.

It is worth noting that this extended EVPN service has similar technical effects as the PBB EVPN service. Among them, ESI IP plays a similar role to PBB B-MAC, and it can uniquely locate a local ESI through ESI IP; The EVPN service also has an I component instance and a B component instance, the B component instance is IP-VRF, and the B component instance of the PBB EVPN is MAC-VRF.

Unlike the exemplary embodiment 1, the present exemplary embodiment adopts ESI IP as the ESI identification information, and transmits in the ARP insertion message, and acquires the corresponding ESI value with the ESI IP.

Unlike the exemplary embodiment 1, the present exemplary embodiment also deploys the ESI state change propagation fast channel and the associated ESI state demapping module between PE1 and PE3.

Different from the exemplary embodiment 1, the exemplary embodiment adopts the second type of ARP extended message as the basic format of the ARP insertion message, and then fills in the target protocol address as the BGP next hop address filled in when the PE1 advertises the EVPN route. .

Unlike the exemplary embodiment 1, in the present exemplary embodiment, in addition to the PE2 node responding to the ARP insertion message similarly to the exemplary embodiment 1, the PE3 node also responds to the ARP insertion message, the PE3 node The upper ESI forwarding table management module responds to the received ARP insertion message according to the following rules: the I component instance to which the received ARP insertion message belongs is recorded as EVI1, and the B component instance corresponding to the EVI1 is recorded as B_EVI1. The VXLAN outer source IP of the outer layer of the ARP insertion packet is recorded as ESI_IP1, and the target protocol address field of the ARP insertion packet is recorded as NH1, and <B_EVI1, ESI_IP1> corresponds to a set of EVPN load sharing information. The set is then removed from the forwarding information corresponding to NH1 in the set.

Those skilled in the art can understand that the present application can be implemented not only on the ESI in the all-active mode but also on the ESI in the single-active mode. When implemented on the ESI in the single-active mode, it is only necessary to clear all the user MAC entries of the VXLAN destination IP learned by the I component instance EVI1 to the ESI_IP1. Due to the similarity between such extended EVPN and PBB EVPN, those skilled in the art can easily refer to the exemplary embodiment 1 and the present exemplary embodiment to migrate the present exemplary embodiment into the PBB EVPN.

Exemplary embodiment 9

The present exemplary embodiment is the same as Exemplary Embodiment 7, except where specifically stated.

Unlike the exemplary embodiment 7, the present exemplary embodiment ARP insertion message does not use the opcode field as the feature field, but uses the control word in the EVPN data encapsulation as the feature field of the ARP insertion message. Specifically, the control word format is the same as the PW-ACH format. At the same time, a new channel type value is TBD3, indicating that the ARP inserts the message. The above feature field is used to distinguish between ARP insertion packets and other ARP packets.

It is worth noting that not only MPLS EVPN can use the control word, VXLAN EVPN can be regarded as another control word in the first 4 bytes of the VXLAN-GPE header. The B component instance of PBB EVPN can also be used as a VPLS instance. Use the control word.

It is worth noting that the above-mentioned ARP insertion packet can also be replaced by a MAC-Ping insertion packet. The MAC Ping insertion packet has a MAC ping packet format, and the MAC ping packet is used to detect a certain MAC address in the EVPN. If the protocol packet is reachable, the MAC ping packet can be used to detect whether the egress of a MAC entry is the protocol packet of the local AC interface of the receiving PE. When the MAC ping packet is used instead of the ARP insertion. In the case of a packet, the feature field can be configured to fill in the destination MAC address with the specified value, and carry the ESI fault identification information in the PDU of the MAC ping packet.

Exemplary embodiment 10

The present exemplary embodiment is the same as Exemplary Embodiment 8 except where specifically stated.

Unlike the exemplary embodiment 8, the present exemplary embodiment does not use the ARP insertion message to deliver the ESI failure identification information, but uses the ping message to deliver the ESI failure identification information, and the ping message is in the B. The component instance is forwarded instead of being forwarded in the I component instance; wherein, since the B component instance in the exemplary embodiment 8 is an IP-VRF, the data plane of the ping message is encapsulated into IP-VRF data. Message encapsulation

It should be noted that it is worth noting that both the B component instance and the I component instance are the EVPN instances in the exemplary embodiment 8, just like the B component instance and the I component instance are both EBB instances of PBB EVPN.

It is to be noted that the ping packet in the exemplary embodiment is different from the normal ping packet in the IP-VRF, and the ICMP type field has a value of TBD5, indicating a new Echo suggestion message, that is, the request destination IP address is located. The node sends an ICMP Echo message to the source IP (filled in the IP address corresponding to the failed ESI, that is, the ESI IP address). At the same time, receiving the Echo suggestion message means that the source IP has expired on the source node.

It is worth noting that the node where the destination IP address of the ICMP Echo message is sent can respond to an ICMP Echo message or not. If the node where the destination IP is located chooses to answer an ICMP Echo message, the source IP is at the node. The point does not guarantee that the corresponding ICMP Echo Reply message will be answered immediately, but the corresponding ICMP Echo Replay message will be returned after the IP recovery is valid.

It is worth noting that the ICMP Echo/Echo Reply message is also called a ping message. In the PBB EVPN, the B component is a VPLS instance. In this case, the format of the ping packet is the format of the MAC ping packet. Protocols used to detect connectivity of MAC addresses. Different vendors have different packet formats, but they all conform to the Echo/Replay interaction mode. On this basis, an Echo recommendation packet can be extended. It is worth noting that the MAC ping packet can also carry the ESI fault identification information in the I component instance.

Embodiment 2

In the embodiment, an Ethernet segment identification adjacency detection processing device is further provided, and the device is used to implement the foregoing embodiment, and details are not described herein. As used below, the term "module" may implement a combination of software and/or hardware of a predetermined function. Although the apparatus described in the following embodiments is preferably implemented in software, hardware, or a combination of software and hardware, is also possible and contemplated.

FIG. 9 is a structural block diagram (1) of an Ethernet segment identification adjacency detection processing apparatus according to an embodiment of the present application. As shown in FIG. 9, the apparatus includes:

The detecting module 901 is configured to detect an ESI adjacency detection event on the link of the Ethernet segment identifier ESI, where the ESI adjacency detection event is used to indicate a change of a result of detecting the link fault identified by the ESI;

The notification module 903 is configured to send a first packet to the second network side edge device PE, where the first packet is used to notify the second PE of the ESI adjacency detection event, where the first packet carries the fault identifier of the ESI. The information, the fault identification information is used to instruct the second PE to perform an update process of the forwarding state corresponding to the ESI.

The ESI adjacency detection event on the link of the Ethernet segment identifier ESI is detected by the function of the above module, wherein the ESI adjacency detection event is used to indicate a change in the result of detecting the link fault identified by the ESI; The network edge device PE sends a first packet, where the first packet is used to notify the second PE of the ESI adjacency detection event, where the first packet carries the fault identification information of the ESI, and the fault identifier information is used to indicate the first packet. The second PE performs the update process of the forwarding state corresponding to the ESI; therefore, the problem that the ESI adjacency detection event in the related art can only depend on the BGP route propagation, and the convergence performance is difficult to achieve the performance of the BFD level, reaches the remote PE. The fast forwarding path switching is completed to reduce the packet loss time during the ES link failure convergence process.

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: passing the standard first mile Ethernet EFM technology; transmitting through the standard Y.1731 The manner in which the management manages the TP OAM TMS technology; the way in which the standard connectivity fault management CFM technology is passed; and the manner in which the physical signals on the link identified by the ESI are detected.

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

Set the operation code of the ARP packet to a predetermined value;

Set the Ethernet source MAC address of the ARP packet to the specified value.

Optionally, FIG. 10 is a structural block diagram (2) of an Ethernet segment identification adjacency detection processing apparatus according to an embodiment of the present application. As shown in FIG. 10, the method further includes: a packaging module 905, configured to pass at least one of the following formats, The ESI adjacency detection event is encapsulated: the peer-to-peer bidirectional forwarding detection BFD chain path failure message; the transmission operation management and maintenance TP OAM session client signal failure indication CSF message; the media access control MAC ping message; the address resolution protocol ARP Packet; neighbor discovery protocol NDP neighbor request message; Internet control message protocol ICMP message.

The ARP packet is encapsulated in an EVPN packet. The EVPN packet is encapsulated according to the data packet format in the EVPN instance bound to the ESI sub-interface.

Set the operation code of the ARP packet to a predetermined value;

Set the Ethernet source MAC address of the ARP packet to the specified value.

It should be noted that each of the above modules may be implemented by software or hardware. For the latter, the foregoing may be implemented by, but not limited to, the foregoing modules are all located in the same processor; or, the above modules are in any combination. The forms are located in different processors.

Illustratively, an Ethernet segment identification adjacency detection processing apparatus according to an embodiment of the present application is described by using an A: EVPN control plane module, which distributes and manages various EVPN routes according to RFC7432 (thus A BGP module is built in. In fact, this module can subdivide many sub-modules, but since it is not an innovative part of this application, it is only used as a module here, so that it has basic EVPN functions, including performance comparison with this application. Management of the RT-type EVPN route; B: EVPN forwarding table management module: The ESI forwarding member list is formed according to RFC7432, and the ESI forwarding path update is performed according to the EAD route validation message and the revocation message delivered by the EVPN control plane module.

The device also includes:

C: ESI adjacency detection module (which may be equivalent to the function of the detection module 901 of the above embodiment): when an ESI has an access link at the node, the fault detection on the link belongs to the ESI adjacency detection module, therefore, The ESI Adjacency Detection Module usually has an existing detection module such as link BFD, EFM, or CFM. In the present application, the ESI adjacency detection module can notify the ESI state change propagation fast channel of the detection result compared to the existing detection modules.

D: ESI state mapping module: mapping refers to the ES detection state change event notified by the ESI neighbor detection module from the corresponding ESI state change fast channel in a corresponding format;

E: ESI state change propagation fast channel: Propagation refers to the event that a certain ESI is faulty on the corresponding link of this node is transmitted to the far-end node through a fast channel such as BFD, and in turn, receives the far-end node. The remote ESI fault notification event passed by the point is also a function of this module. Therefore, the ESI state change propagation fast channel usually has a built-in detection module such as peer BFD and IP BFD as a fast channel.

F: ESI state demapping module: Linkage refers to the remote ESI fault notification event notified by the E module (ie, the ESI state change propagation fast channel) to the B module (ie, the EVPN forwarding table management module), and, The source of the event is not from the EAD route, but in the view of the B module, it has the same effect as the EAD route delivery/revocation notified by the A module (ie, the EVPN control plane module) (even completely treated as the same event), but time It must be routed before EAD.

The relationship between A, B, C, D, E, and F, as shown in Figure 11, the arrow indicates the order of event notification, which is the process from the event source to the final interaction with the RFC7432 intrinsic module (ie, module B). .

The Ethernet segment identification adjacency detection processing method in this embodiment of the present application includes the following steps:

In the first step, the ESI adjacency detection module detects a link failure on the ES, including a physical link failure;

In the second step, the ESI adjacency detection module notifies the ESI status mapping module of the fault;

In the third step, the ESI state mapping module notifies the fault to the ESI state change propagation fast channel;

The fourth step, the ESI state change propagation fast channel passes the fault to the remote PE through a fast fault linkage channel such as peer BFD;

In the fifth step, on the remote PE, a fast fault linkage channel such as peer BFD receives a fault transfer message in a special format, and learns to propagate the message for the ESI adjacency detection event, and notifies the ESI state demapping module of the message; Parsing which ESI corresponding ES has failed on which remote PE, and then notifying the remote ESI fault linkage module;

In the sixth step, the ESI fault demapping module learns that a certain Ethernet tag on an ESI or an ESI has failed, and notifies the EVPN forwarding table management module of the fault to switch the forwarding path.

Embodiment 3

FIG. 12 is a structural block diagram (4) of an Ethernet segment identification adjacency detection processing apparatus according to an embodiment of the present application. As shown in FIG. 12, the apparatus includes:

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

The update module 133 is configured to perform an update flow of the forwarding state corresponding to the ESI according to the failure identification information.

Receiving, by using the foregoing module, the first packet sent by the first PE, where the first packet is used to notify the ESI adjacency detection event on the link of the Ethernet segment identifier ESI detected by the first PE to the foregoing The device, the ESI adjacency detection event is used to indicate a change in the result of detecting the link fault identified by the ESI; wherein the first packet carries the fault identification information of the ESI; and the forwarding corresponding to the ESI is performed according to the fault identifier information. The update process of the state; therefore, the problem that the ESI adjacency detection event in the related art can only rely on the BGP route propagation, the convergence performance is difficult to achieve the performance of the BFD level, and the fast forwarding path switching is completed on the remote PE. Reduce the effect of packet loss time during ES link failure convergence.

Optionally, the receiving module 131 is further configured to receive, by using at least one of the following formats, a control packet that encapsulates an ESI adjacency detection event: a peer-to-peer bidirectional forwarding detection BFD chain path invalid packet; a transport operation management and maintenance TP OAM The client signal of the session is invalid, indicating the CSF packet, the address resolution protocol ARP packet, the neighbor discovery protocol NDP neighbor request packet, the ICMP packet, and the media access control MAC ping packet.

Optionally, the receiving module 131 is further configured to: receive the packet encapsulated by the ESI neighbor detection event according to the ARP packet according to at least one of the following manners:

The operation code of the ARP packet is a predetermined value.

The Ethernet source MAC address of the ARP packet is the specified value.

Optionally, the update module is further configured to: change the DF/NDF/BDF state corresponding to the ESI sub-interface of the ESI; and change the state of the corresponding next hop information in the forwarding information set corresponding to the ESI.

Optionally, FIG. 13 is a structural block diagram (5) of an Ethernet segment identification adjacency detection processing apparatus according to an embodiment of the present application. As shown in FIG. 13, the update module 103 includes:

The determining unit 1331 is configured to determine a route type corresponding to the to-be-revoked event according to the ESI adjacency detection event; and the generating unit 1333 is configured to generate a predetermined route revocation event corresponding to the route type.

Optionally, as shown in FIG. 13, the apparatus further includes: a parsing unit 135 configured to parse a state of the adjacent link of the ESI identifier from the control packet; and the input unit 137 is configured to be in a state of the adjacent link. In the case of a failure, the predetermined application interface API interface is used to input a predetermined route revocation event when the predetermined route revocation event is input with the Ethernet virtual private network EVPN control plane.

It should be noted that each of the above modules may be implemented by software or hardware. For the latter, the foregoing may be implemented by, but not limited to, the foregoing modules are all located in the same processor; or, the above modules are in any combination. The forms are located in different processors. The foregoing embodiment is only an exemplary description. In an actual application, the second PE may send the first packet to the first PE, where the first PE receives the first packet and performs the second PE in the foregoing embodiment. The operation corresponding to the operation performed.

Embodiment 4

The embodiment of the present application further provides a network side edge device, which includes any of the Ethernet segment identification adjacency detection processing devices in the foregoing embodiments.

Embodiment 5

The embodiment of the present application further provides a storage medium, where the storage medium includes a stored program, wherein the foregoing program runs the method of performing any of the Ethernet segment identification adjacency detection processing in the foregoing embodiment.

Optionally, in the embodiment, the foregoing storage medium may include, but is not limited to, a USB flash drive, a Read-Only Memory (ROM), and a Random Access Memory (RAM). A variety of media that can store program code, such as a hard disk, a disk, or an optical disk.

Embodiment 6

The embodiment of the present application further provides a processor configured to run a program, where the foregoing program runs the method of performing any of the Ethernet segment identification adjacency detection processing in the foregoing embodiment.

For example, the specific examples in this embodiment may refer to the examples described in the foregoing embodiments and the optional embodiments, and details are not described herein again.

Obviously, those skilled in the art should understand that the above modules or steps of the present application can be implemented by a general computing device, which can be concentrated on a single computing device or distributed in a network composed of multiple computing devices. Alternatively, they may be implemented by program code executable by the computing device such that they may be stored in the storage device by the computing device and, in some cases, may be different from the order herein. The steps shown or described are performed, or they are separately fabricated into individual integrated circuit modules, or a plurality of modules or steps thereof are fabricated as a single integrated circuit module. Thus, the application is not limited to any particular combination of hardware and software.

The above description is only an exemplary embodiment of the present application, and is not intended to limit the present application, and various changes and modifications may be made to the present application. Any modifications, equivalent substitutions, improvements, etc. made within the principles of this application are intended to be included within the scope of this application.

Claims

An Ethernet segment identification adjacency detection processing method includes:

The first network side edge device PE detects an ESI adjacency detection event on the link of the Ethernet segment identifier ESI, wherein the ESI adjacency detection event is used to indicate a change in a result of detecting a link failure identified by the ESI;

The first PE sends a first packet to the second PE, where the first packet is used to notify the second PE of the ESI adjacency detection event, where the first packet carries The fault identification information of the ESI is used to indicate that the second PE performs an update process of the forwarding state corresponding to the ESI.
The method of claim 1, wherein the ESI adjacency detection event on the link identified by the ESI is detected, at least by one of:

Pass the standard first mile Ethernet EFM technology approach;

The way to manage and maintain TP OAM TMS technology through standard Y.1731 transport operations;

The way to manage CFM technology through standard connectivity faults;

By detecting the manner in which the physical signals on the link identified by the ESI.
The method of claim 1 further comprising: encapsulating the ESI adjacency detection event by at least one of the following message formats:

Peer-to-peer bidirectional forwarding detects BFD chain path invalidation packets;

The transmission operation management maintains a customer signal invalidation indication CSF message of the TP OAM session;

Address resolution protocol ARP packet;

Neighbor discovery protocol NDP neighbor request message;

Internet Control Message Protocol ICMP message;

Media access controls MAC ping messages.
The method of claim 1, wherein the fault identification information of the ESI comprises at least one of the following:

a partial binary bit of the ESI;

The operator backbone corresponding to the ESI bridges the backbone MAC address PBB B-MAC or a partial binary bit in the PBB B-MAC corresponding to the ESI;

The IP address corresponding to the ESI;

The ESI label corresponding to the ESI;

Encoding information indicating that the primary interface corresponding to the ESI has a fault;

Encoding information indicating that the ESI sub-interface of the ESI is faulty, wherein the ESI sub-interface is a sub-interface of the main interface corresponding to the ESI;

Node identification information indicating a node where the link of the ESI identifier is faulty.
The method according to claim 3, wherein encapsulating the ESI adjacency detection event by using an ARP packet includes at least one of the following manners:

Encapsulating the ARP packet into an EVPN packet, where the EVPN packet is encapsulated according to a data packet format in an EVPN instance bound to the ESI sub-interface of the ESI;

The PDU part of the ARP packet is encapsulated according to the PDU format of the ARP probe packet, where the target protocol address in the PDU is a specified IP address;

Setting a sender hardware address field of the ARP packet to the fault identifier information carrying the ESI;

Setting an operation code of the ARP packet to a predetermined value;

Setting a sender protocol address field of the ARP packet to carry fault identification information of the ESI;

Setting an Ethernet source MAC address of the ARP packet to a MAC address of the first PE;

Setting the Ethernet source MAC address of the ARP packet to the MAC address of the primary interface corresponding to the ESI or the ESI sub-interface of the ESI;

Setting the Ethernet source MAC address of the ARP packet to the MAC address of the integrated routing bridge IRB interface of the EVPN instance bound to the ESI sub-interface of the ESI;

Setting an Ethernet source MAC address of the ARP packet to a specified value;

Setting an Ethernet destination MAC address of the ARP packet to a predetermined value;

Setting the target protocol address in the ARP packet to the fault identifier information carrying the ESI;

Setting the target hardware address in the ARP packet to carry the ESI fault identification information;

The ARP packet is encapsulated into an EVPN data packet by using a control word, wherein a channel type in the control word is set to a specified value.
An Ethernet segment identification adjacency detection processing method includes:

The second network side edge device PE receives the first packet sent by the first PE, where the first packet is used to send the ESI adjacency on the link of the Ethernet segment identifier ESI detected by the first PE. Detecting an event notification to the second PE, where the ESI adjacency detection event is used to indicate a change in a result of detecting a link failure identified by the ESI; wherein the first message carries the fault identifier of the ESI And the fault identifier information is used to indicate that the second PE performs an update process of a forwarding state corresponding to the ESI.
The method of claim 6 wherein said ESI adjacency detection event is encapsulated by at least one of the following formats:

Peer-to-peer bidirectional forwarding detects BFD chain path invalidation packets;

The transmission operation management maintains a customer signal invalidation indication CSF message of the TP OAM session;

Address resolution protocol ARP packet;

Neighbor discovery protocol NDP neighbor request message;

Internet Control Message Protocol ICMP message;

Media access controls MAC ping messages.
The method of claim 6, wherein the fault identification information of the ESI comprises at least one of the following:

a partial binary bit of the ESI;

a partial binary bit in the PBB B-MAC corresponding to the ESI or the PBB B-MAC corresponding to the ESI;

The IP address corresponding to the ESI;

The ESI label corresponding to the ESI;

Encoding information indicating that the primary interface corresponding to the ESI has a fault;

Encoding information indicating that the ESI sub-interface of the ESI is faulty, wherein the ESI sub-interface is a sub-interface of the main interface corresponding to the ESI;

Node identification information indicating a node where the link of the ESI identifier is faulty.
The method according to claim 7, wherein the ESI adjacency detection event is encapsulated by the ARP packet and includes at least one of the following:

The ARP packet is encapsulated into an EVPN packet encapsulated in a data packet format in an EVPN instance bound to the ESI sub-interface of the ESI;

The PDU part of the ARP packet is encapsulated according to the PDU format of the ARP probe packet, where the target protocol address in the PDU is a specified IP address;

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

The operation code of the ARP packet is a predetermined value;

The sender protocol address field of the ARP packet carries the fault identification information of the ESI.

The Ethernet source MAC address of the ARP packet is a MAC address of the first PE;

The Ethernet source MAC address of the ARP packet is the MAC address of the primary interface corresponding to the ESI or the ESI sub-interface of the ESI;

The Ethernet source MAC address of the ARP packet is the MAC address of the integrated routing bridging IRB interface of the EVPN instance bound to the ESI sub-interface of the ESI;

The Ethernet source MAC address of the ARP packet is a specified value.
The method according to claim 6, wherein the update flow of performing the forwarding state corresponding to the ESI includes at least one of the following:

Changing the specified forwarding state of the specified forwarding/non-designated forwarding/backup corresponding to the ESI sub-interface of the ESI;

And changing a state of the corresponding next hop information in the unicast forwarding information set corresponding to the ESI.
An Ethernet segment identification adjacency detection processing device includes:

a detection module, configured to detect an ESI neighbor detection event on a link of the Ethernet segment identifier ESI, wherein the ESI adjacency detection event is used to indicate a change in a result of detecting a link failure identified by the ESI;

a sending module, configured to send a first packet to the second network side edge device PE, where the first packet is used to notify the second PE of the ESI adjacency detection event, where the first packet And carrying the fault identification information of the ESI, where the fault identifier information is used to indicate that the second PE performs an update process of a forwarding state corresponding to the ESI.
The apparatus according to claim 11, wherein the detecting module is further configured to detect the ESI adjacency detection event on the link identified by the ESI by at least one of:

Pass the standard first mile Ethernet EFM technology approach;

The way to manage and maintain TP OAM TMS technology through standard Y.1731 transport operations;

The way to manage CFM technology through standard connectivity faults;

By detecting the manner in which the physical signals on the link identified by the ESI.
The apparatus of claim 11 further comprising:

The encapsulating module is configured to encapsulate the ESI adjacency detection event by using at least one of the following formats:

Peer-to-peer bidirectional forwarding detects BFD chain path invalidation packets;

The transmission operation management maintains a customer signal invalidation indication CSF message of the TP OAM session;

Media access control MAC Ping message;

Neighbor discovery protocol NDP neighbor request message;

Internet Control Message Protocol ICMP message;

Address resolution protocol ARP packet.
The apparatus of claim 11, wherein the fault identification information of the ESI comprises at least one of the following:

a partial binary bit of the ESI;

The operator backbone corresponding to the ESI bridges the backbone MAC address PBB B-MAC or a partial binary bit in the PBB B-MAC corresponding to the ESI;

The IP address corresponding to the ESI;

The ESI label corresponding to the ESI;

Encoding information indicating that the main interface of the ESI is faulty;

Encoding information indicating that the ESI sub-interface of the ESI is faulty, wherein the ESI sub-interface is a sub-interface of the main interface corresponding to the ESI;

Node identification information indicating a node where the link of the ESI identifier is faulty.
The apparatus according to claim 13, wherein the encapsulating module is further configured to encapsulate the ESI adjacency detection event according to an ARP packet in at least one of the following manners:

Encapsulating the ARP packet into an EVPN packet, where the EVPN packet is encapsulated according to a data packet format in an EVPN instance bound to the ESI sub-interface of the ESI;

The PDU part of the ARP packet is encapsulated according to the PDU format of the ARP probe packet, where the target protocol address in the PDU is a specified IP address;

Setting a sender hardware address field of the ARP packet to the fault identifier information carrying the ESI;

Setting an operation code of the ARP packet to a predetermined value;

Setting a sender protocol address field of the ARP packet to the fault identifier information carrying the ESI;

Setting the Ethernet source MAC address of the ARP packet to the MAC address of the first PE;

Setting the Ethernet source MAC address of the ARP packet to the MAC address of the primary interface corresponding to the ESI or the ESI sub-interface of the ESI;

Setting the Ethernet source MAC address of the ARP packet to the MAC address of the integrated routing bridge IRB interface of the EVPN instance bound to the ESI sub-interface of the ESI;

Setting an Ethernet source MAC address of the ARP packet to a specified value;

Setting an Ethernet destination MAC address of the ARP packet to a predetermined value;

Setting the target protocol address in the ARP packet to the fault identifier information carrying the ESI;

Setting the target hardware address in the ARP packet to carry the ESI fault identification information;

The ARP packet is encapsulated into an EVPN data packet by using a control word, wherein a channel type in the control word is set to a specified value.
An Ethernet segment identification adjacency detection processing device includes:

The receiving module is configured to receive the first packet sent by the first PE, where the first packet is used to detect an ESI adjacency detection event on the link of the Ethernet segment identifier ESI detected by the first PE Notifying the device, the ESI adjacency detection event is used to indicate a change in a result of detecting a link failure identified by the ESI; wherein the first message carries the fault identification information of the ESI;

The update module is configured to perform an update process of the forwarding state corresponding to the ESI according to the fault identification information.
The apparatus according to claim 16, wherein the receiving module is further configured to receive a control message encapsulating the ESI adjacency detection event by using at least one of the following formats:

Peer-to-peer bidirectional forwarding detects BFD chain path invalidation packets;

The transmission operation management maintains a customer signal invalidation indication CSF message of the TP OAM session;

Address resolution protocol ARP packet;

Neighbor discovery protocol NDP neighbor request message;

Internet Control Message Protocol ICMP message;

Media access controls MAC ping messages.
The apparatus of claim 16, wherein the fault identification information of the ESI comprises at least one of the following:

a partial binary bit of the ESI;

a partial binary bit in the PBB B-MAC corresponding to the ESI or the PBB B-MAC corresponding to the ESI;

The IP address corresponding to the ESI;

The ESI label corresponding to the ESI;

Encoding information indicating that the primary interface corresponding to the ESI has a fault;

Encoding information indicating that the ESI sub-interface of the ESI is faulty, wherein the ESI sub-interface is a sub-interface of the main interface corresponding to the ESI;

Node identification information indicating a node where the link of the ESI identifier is faulty.
The apparatus according to claim 17, wherein the receiving module is further configured to receive a packet encapsulated by the ESI neighbor detection event according to an ARP packet according to at least one of the following manners:

The ARP packet is encapsulated in an EVPN packet encapsulated in a data packet format in an EVPN instance bound to the ESI sub-interface of the ESI;

The PDU part of the ARP packet is a packet encapsulated according to the PDU format of the ARP probe packet, where the target protocol address in the PDU is a specified IP address;

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

The operation code of the ARP packet is a predetermined value;

The sender protocol address field of the ARP packet carries the fault identification information of the ESI.

The Ethernet source MAC address of the ARP packet is a MAC address of the first PE;

The Ethernet source MAC address of the ARP packet is the MAC address of the primary interface corresponding to the ESI or the ESI sub-interface of the ESI;

The Ethernet source MAC address of the ARP packet is the MAC address of the integrated routing bridging IRB interface of the EVPN instance bound to the ESI sub-interface of the ESI;

The Ethernet source MAC address of the ARP packet is a specified value.
The apparatus of claim 16, wherein the update module is further configured to be at least one of:

Changing the specified forwarding state of the specified forwarding/non-designated forwarding/backup corresponding to the ESI sub-interface of the ESI;

And changing a state of the corresponding next hop information in the unicast forwarding information set corresponding to the ESI.
A network side edge device comprising the apparatus of any one of claims 11 to 20.
A storage medium, wherein the storage medium comprises a stored program, the program being executed to perform the method of any one of claims 1 to 5, or 6-10.
A processor, wherein the processor is configured to execute a program, the program executing the method of any one of claims 1 to 5, or 6-10.