Routing

Hi all,

Let me know if you have any test result/opinion about the following.

CE---|  EVPN Domain(MPLS/MPLS-PBB/VXLAN either will do) |---CE

|<---------------------------etherne CFM/OAM------------------------------>|

I think as VPLS can transport ether CFM/OAM frames, EVPN also can do the same.

http://www.juniper.net/documentation/en_US/junos/topics/example/layer-2-802-1ag-ethernet-oam-cfm-example-over-vpls-mx-solutions.html

 If you have any test result or opinion about this one please reply 🙂

Regards,

Hadi

I've not used EVPN as yet, but I can confirm that with VPLS and l2circuits you can setup CFM tests from devices on either side of the circuit and run a complete test on the set.

You do need to be sure that the maintenance domain settings used by the test set do not overlap any CFM that is configured on the devices as part of the service testing.  If they do match the packets can be caught by the service configuration instead of passing through to the test set.

Thanks for the reply and your recommendation 🙂

Looking forward to hear from others too 🙂

Regards,

Hadi

Hi Hadi.

CE to CE:

EOAM packets are transit packets to EVPN-MPLS, then they are treated as regular data packets and forwarded for CE to CE OAM.

If you would like to run CFM session between PEs of EVPN-MPLS not supported yet. you may need to wait for upcoming release.

Topology and results below:

CE---|                        EVPN Domain(MPLS/)                            |---CE

|<---------------------------etherne CFM/OAM------------------------------>|

Configuration and results for CFM between CE to CE via EVPN

CE01#

set protocols oam ethernet connectivity-fault-management maintenance-domain customer level 7
set protocols oam ethernet connectivity-fault-management maintenance-domain customer maintenance-association customer-site1 continuity-check interval 1s
set protocols oam ethernet connectivity-fault-management maintenance-domain customer maintenance-association customer-site1 mep 800 interface ge-0/0/1.0
set protocols oam ethernet connectivity-fault-management maintenance-domain customer maintenance-association customer-site1 mep 800 direction down
set protocols oam ethernet connectivity-fault-management maintenance-domain customer maintenance-association customer-site1 mep 800 auto-discovery

CE02#

root> show configuration protocols oam |display set
set protocols oam ethernet connectivity-fault-management maintenance-domain customer level 7
set protocols oam ethernet connectivity-fault-management maintenance-domain customer maintenance-association customer-site1 continuity-check interval 1s
set protocols oam ethernet connectivity-fault-management maintenance-domain customer maintenance-association customer-site1 mep 700 interface ge-0/0/1.0
set protocols oam ethernet connectivity-fault-management maintenance-domain customer maintenance-association customer-site1 mep 700 direction down
set protocols oam ethernet connectivity-fault-management maintenance-domain customer maintenance-association customer-site1 mep 700 auto-discovery

root> show oam ethernet connectivity-fault-management mep-database customer-site1 maintenance-domain customer
Maintenance domain name: customer, Format: string, Level: 7
Maintenance association name: customer-site1, Format: string
Continuity-check status: enabled, Interval: 1s, Loss-threshold: 3 frames
MEP identifier: 700, Direction: down, MAC address: 00:05:86:71:4d:01
Auto-discovery: enabled, Priority: 0
Interface status TLV: none, Port status TLV: none
Connection Protection TLV: no
Interface name: ge-0/0/1.0, Interface status: Active, Link status: Up

Remote MEP identifier: 800, State: ok
MAC address: 00:05:86:71:0f:01, Type: Learned
Interface: ge-0/0/1.0
Last flapped: Never
Continuity: 100%, Admin-enable duration: 60sec, Oper-down duration: 0sec
Effective loss threshold: 3 frames
Remote defect indication: false
Port status TLV: none
Interface status TLV: none

root> ...vity-fault-management interfaces ge-0/0/1.0 detail
Interface name: ge-0/0/1.0 , Interface status: Active, Link status: Up
Maintenance domain name: customer, Format: string, Level: 7, MD Index: 1
Maintenance association name: customer-site1, Format: string, MA Index: 1
Continuity-check status: enabled, Interval: 1s, Loss-threshold: 3 frames
Interface status TLV: none, Port status TLV: none
Connection Protection TLV: no
MEP identifier: 700, Direction: down, MAC address: 00:05:86:71:4d:01
MEP status: running
Defects:
Remote MEP not receiving CCM : no
Erroneous CCM received : no
Cross-connect CCM received : no
RDI sent by some MEP : no
Some remote MEP's MAC in error state : no
Statistics:
CCMs sent : 60
CCMs received out of sequence : 0
LBMs sent : 0
Valid in-order LBRs received : 0
Valid out-of-order LBRs received : 0
LBRs received with corrupted data : 0
LBRs sent : 0
LTMs sent : 0
LTMs received : 0
LTRs sent : 0
LTRs received : 0
Sequence number of next LTM request : 0
1DMs sent : 0
Valid 1DMs received : 0
Invalid 1DMs received : 0
Out of sync 1DMs received : 0
DMMs sent : 0
Valid DMMs received : 0
Invalid DMMs received : 0
DMRs sent : 0
Valid DMRs received : 0
Invalid DMRs received : 0
LMMs sent : 0
Valid LMMs received : 0
Invalid LMMs received : 0
LMRs sent : 0
Valid LMRs received : 0
Invalid LMRs received : 0
SLMs sent : 0
Valid SLMs received : 0
Invalid SLMs received : 0
SLRs sent : 0
Valid SLRs received : 0
Invalid SLRs received : 0
Remote MEP count: 1
Identifier MAC address State Interface
800 00:05:86:71:0f:01 ok ge-0/0/1.0

root>

Hope this helps

--------------------------------------------------------------------------------------------------------
If this post was helpful, please mark this post as an "Accepted Solution".
Kudos are always appreciated!
--------------------------------------------------------------------------------------------------------

Hi vvadivel,

Thank you for your reply and checking the behavior in Junos device.

Also thank you for your comment on PE-PE CFM session.

Regards,

Hadi.