PERFORMANCE MONITORING SUPPORT FOR CFM OVER EVPN
FIG1 is a diagram of an example implementation described herein
FIG1 is a diagram of an example implementation 100 described herein. As shown in FIG1, example implementation 100 may include an EVPN associated with multiple CE devices, including CE1, CE2, CE3, and CE4, and multiple PE devices, including PE1, PE2, and PE3 configured to function as MEPs (e.g., MEP 1, MEP 2, and MEP 3). As shown, an attachment circuit 1, may be established between PE1 and CE1, an attachment circuit 2, may be established between PE1 and CE2, and an attachment circuit 3, may be established between PE2 and CE2. As further shown, an attachment circuit 4, may be established between PE3 and CE3, and an attachment circuit 5, may be established between PE3 and CE4. Here, CE2 may be multihomed to PE1 and PE2 in an all-active redundancy mode. As indicated above, FIG1 is provided merely as an example. Other examples are possible and may differ from what was described with regard to FIG1.
diagram
5
attachment circuit
14
clause clauses
1
attachment circuit
130
reference number
100
example implementation
4
attachment circuit
2
Type
110
reference number
3
attachment circuit
120
reference number
['1. A method, comprising: providing, by a first provider edge (PE) device, a route advertisement, the first PE device being part of an Ethernet virtual private network (EVPN), and being multihomed to by a first customer edge (CE) device, a first attachment circuit being established between the first PE device and the first CE device, the route advertisement including a media access control (MAC) address, corresponding to the first attachment circuit, that is utilized as a connectivity fault management (CFM) MAC address for a maintenance endpoint (MEP) configured on the first attachment circuit; receiving, by a second PE device, the route advertisement, the second PE device being part of the EVPN, and being communicatively coupled to a second CE device, a second attachment circuit being established between the second PE device and the second CE device, the second PE device being configured to monitor connectivity between the second attachment circuit and the first attachment circuit; and causing, by the second PE device, traffic, relating to monitoring the connectivity, to be directed to the first PE device and/or to the first attachment circuit based on the route advertisement, the traffic not being provided to any other PE device, on the EVPN, that is multihomed to by the first CE device.', '4. The method of any preceding claim, wherein the route advertisement includes a Type 2 route advertisement, and/or does not advertise reachability of the first attachment circuit based on an Ethernet segment identifier (ESI).']