Switching

Hello everyone,

I was wondering if anyone could help me figure out whats missing in my configuration. I am trying to setup a monitoring using CFM between a MX and LTS device from "Accedian" over a specific vlan (777). I tried labbing this up with an ACX instead of an MX and here is my configuration on the ACX:

set protocols oam ethernet connectivity-fault-management maintenance-domain MyLevel3 level 3
set protocols oam ethernet connectivity-fault-management maintenance-domain MyLevel3 maintenance-association V2xxxTowerIDX continuity-check interval 1s
set protocols oam ethernet connectivity-fault-management maintenance-domain MyLevel3 maintenance-association V2xxxTowerIDX continuity-check interface-status-tlv
set protocols oam ethernet connectivity-fault-management maintenance-domain MyLevel3 maintenance-association V2xxxTowerIDX mep 2 interface ge-0/1/0.777
set protocols oam ethernet connectivity-fault-management maintenance-domain MyLevel3 maintenance-association V2xxxTowerIDX mep 2 interface vlan 777
set protocols oam ethernet connectivity-fault-management maintenance-domain MyLevel3 maintenance-association V2xxxTowerIDX mep 2 direction down
set protocols oam ethernet connectivity-fault-management maintenance-domain MyLevel3 maintenance-association V2xxxTowerIDX mep 2 priority 0
set protocols oam ethernet connectivity-fault-management maintenance-domain MyLevel3 maintenance-association V2xxxTowerIDX mep 2 auto-discovery
set protocols oam ethernet connectivity-fault-management maintenance-domain MyLevel3 maintenance-association V2xxxTowerIDX mep 2 remote-mep 1

Here is the interface config:

set interfaces ge-0/1/0 description "Link To Accedian"
set interfaces ge-0/1/0 flexible-vlan-tagging
set interfaces ge-0/1/0 mtu 9192
set interfaces ge-0/1/0 encapsulation flexible-ethernet-services
set interfaces ge-0/1/0 unit 777 encapsulation vlan-ccc
set interfaces ge-0/1/0 unit 777 vlan-id 777

And this is What I see:

ACX1100-Lab> show oam ethernet connectivity-fault-management mep-database maintenance-domain MyLevel3 maintenance-association V2xxxTowerIDX

Maintenance domain name: MyLevel3, Format: string, Level: 3
  Maintenance association name: V2xxxTowerIDX, Format: string
  Continuity-check status: enabled, Interval: 1s, Loss-threshold: 3 frames
  MEP identifier: 2, Direction: down, MAC address: 00:00:00:00:00:00
  Auto-discovery: enabled, Priority: 0
  Interface status TLV: none, Port status TLV: none
  Connection Protection TLV: no
  Interface name: ge-0/1/0.777, Interface status: Active, Link status: Down
  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
    Alarm Indication Signal state                 : no
  Statistics:
    CCMs sent                                     : 0
    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           : 1859318674
    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
    Valid AISs generated                          : 0
    Valid AISs received                           : 0
  Remote MEP count: 1
    Identifier    MAC address        State    Interface
        1     ff:ff:ff:ff:ff:ff    start

This is my first time using OAM on juniper so please bear with me if I made any obvious mistakes. I also hooked the Accedian unit to another Accedian with the same config and everything works great. 

I am using MD Level3, ACX MEPID is 2, Accedian MEPID is 1.

What am I missing in my configuration?

Thanks in advance 🙂 

For whoever is in the same boat as me, I hooked up 2 ACX using below config (make sure to use different mep-id's on different ends) and it worked:

set protocols oam ethernet connectivity-fault-management maintenance-domain MyLevel3 level 3
set protocols oam ethernet connectivity-fault-management maintenance-domain MyLevel3 maintenance-association V2xxxTowerIDX continuity-check interval 1s
set protocols oam ethernet connectivity-fault-management maintenance-domain MyLevel3 maintenance-association V2xxxTowerIDX continuity-check interface-status-tlv
set protocols oam ethernet connectivity-fault-management maintenance-domain MyLevel3 maintenance-association V2xxxTowerIDX mep 2 interface ge-0/1/0.777

**********************************************
Notice I deleted vlan id from my initial config I posted on this thread, for whatever reason it was not allowing CCMs when I had this:
delete protocols oam ethernet connectivity-fault-management maintenance-domain MyLevel3 maintenance-association V2xxxTowerIDX mep 2 interface vlan 777
**********************************************

set protocols oam ethernet connectivity-fault-management maintenance-domain MyLevel3 maintenance-association V2xxxTowerIDX mep 2 direction down
set protocols oam ethernet connectivity-fault-management maintenance-domain MyLevel3 maintenance-association V2xxxTowerIDX mep 2 priority 0
set protocols oam ethernet connectivity-fault-management maintenance-domain MyLevel3 maintenance-association V2xxxTowerIDX mep 2 auto-discovery

Here is the output of what I was seeing at the time:

ACX1100-Lab> show oam ethernet connectivity-fault-management mep-database maintenance-domain MyLevel3 maintenance-association V2xxxTowerIDX

Maintenance domain name: MyLevel3, Format: string, Level: 3
  Maintenance association name: V2xxxTowerIDX, Format: string
  Continuity-check status: enabled, Interval: 1s, Loss-threshold: 3 frames
  MEP identifier: 2, Direction: down, MAC address: 7c:e2:ca:8a:a0:1c
  Auto-discovery: enabled, Priority: 0
  Interface status TLV: up, Port status TLV: none
  Connection Protection TLV: no
  Interface name: ge-0/1/0.777, Interface status: Active, Link status: Up
  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
    Alarm Indication Signal state                 : no
  Statistics:
    CCMs sent                                     : 263
    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           : 477723053
    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
    Valid AISs generated                          : 0
    Valid AISs received                           : 0
  Remote MEP count: 1
    Identifier    MAC address        State    Interface
        1     ec:13:db:ee:a2:1c       ok  ge-0/1/0.777

I then converted it back to 1 ACX and 1 Accedian, I immediately noticed this (IN BOLD) when using this command again:

ACX2200-Lab> show oam ethernet connectivity-fault-management mep-database maintenance-domain MyLevel3 maintenance-association V2xxxTowerIDX

Maintenance domain name: MyLevel3, Format: string, Level: 3
Maintenance association name: V2xxxTowerIDX, Format: icc
Continuity-check status: enabled, Interval: 1s, Loss-threshold: 3 frames
MEP identifier: 2, Direction: down, MAC address: 7c:e2:ca:8a:a0:1c
Auto-discovery: enabled, Priority: 0
Interface status TLV: up, Port status TLV: none
Connection Protection TLV: no
Interface name: ge-0/1/0.777, Interface status: Active, Link status: Up
Defects:
Remote MEP not receiving CCM : no
Erroneous CCM received : no
Cross-connect CCM received : yes
RDI sent by some MEP : no
Some remote MEP's MAC in error state : no
Alarm Indication Signal state : no
Cross-connect CCM session count: 1
Defect Type: Cross connect, Description: invalid maintenance association identifier
Maintenance domain name: MyLevel3, Format: string, Level: 3
Maintenance association name: V2xxxTowerIDX, Format: string
MEP identifier: 1, Continuity-check interval: 1s
Statistics:
CCMs sent : 34
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 : 1471296056
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
Valid AISs generated : 0
Valid AISs received : 0

The name format of MA was different between Accedian and ACX, created customer MA using name format of String and not ICCC-Based, and issue went away. I am seeing clean results. I also tested this on Level 0, 6 and 3 and all of them worked. Here is my last config on the ACX:

set interfaces ge-0/1/0 description "Link to Accedian"
set interfaces ge-0/1/0 flexible-vlan-tagging
set interfaces ge-0/1/0 mtu 9192
set interfaces ge-0/1/0 encapsulation flexible-ethernet-services
set interfaces ge-0/1/0 unit 0 vlan-id 0
set interfaces ge-0/1/0 unit 0 family inet address 10.10.10.2/30
set interfaces ge-0/1/0 unit 777 encapsulation vlan-ccc
set interfaces ge-0/1/0 unit 777 vlan-id 777

set protocols oam ethernet connectivity-fault-management maintenance-domain MyLevel3 level 3
set protocols oam ethernet connectivity-fault-management maintenance-domain MyLevel3 maintenance-association V2xxxTowerIDX short-name-format character-string
set protocols oam ethernet connectivity-fault-management maintenance-domain MyLevel3 maintenance-association V2xxxTowerIDX continuity-check interval 1s
set protocols oam ethernet connectivity-fault-management maintenance-domain MyLevel3 maintenance-association V2xxxTowerIDX continuity-check interface-status-tlv
set protocols oam ethernet connectivity-fault-management maintenance-domain MyLevel3 maintenance-association V2xxxTowerIDX mep 2 interface ge-0/1/0.777
set protocols oam ethernet connectivity-fault-management maintenance-domain MyLevel3 maintenance-association V2xxxTowerIDX mep 2 direction down
set protocols oam ethernet connectivity-fault-management maintenance-domain MyLevel3 maintenance-association V2xxxTowerIDX mep 2 priority 0
set protocols oam ethernet connectivity-fault-management maintenance-domain MyLevel3 maintenance-association V2xxxTowerIDX mep 2 auto-discovery

And here is the results:

ACX2200-Lab> show oam ethernet connectivity-fault-management mep-database maintenance-domain MyLevel3 maintenance-association V2xxxTowerIDX

Maintenance domain name: MyLevel3, Format: string, Level: 3
  Maintenance association name: V2xxxTowerIDX, Format: string
  Continuity-check status: enabled, Interval: 1s, Loss-threshold: 3 frames
  MEP identifier: 2, Direction: down, MAC address: 7c:e2:ca:8a:a0:1c
  Auto-discovery: enabled, Priority: 0
  Interface status TLV: up, Port status TLV: none
  Connection Protection TLV: no
  Interface name: ge-0/1/0.777, Interface status: Active, Link status: Up
  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
    Alarm Indication Signal state                 : no
  Statistics:
    CCMs sent                                     : 827
    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           : 2021808654
    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
    Valid AISs generated                          : 0
    Valid AISs received                           : 0
  Remote MEP count: 1
    Identifier    MAC address        State    Interface
        1     00:15:ad:44:b9:f4       ok  ge-0/1/0.777


ACX2200-Lab> show oam ethernet connectivity-fault-management interfaces
Interface                   Link      Status       Level  MEP         Neighbours
                                                          Identifier
ge-0/1/0.777                Up        Active       3      2           1

Hope this helps someone in the future 🙂 

You already figured out the part regarding the MA name format. I had similar issues earlier and once I converted the MA name to integer it solved it for me (not saying that is your solution).

Regarding the vlan-id, I am using the primary-vid statement, and its working correctly for me. I also noticed you have family ccc missing on the interface config under unit 777.

Here is my sample config -

set protocols oam ethernet connectivity-fault-management maintenance-domain random maintenance-association 5 primary-vid 61
set protocols oam ethernet connectivity-fault-management maintenance-domain random maintenance-association 5 continuity-check interval 1s
set protocols oam ethernet connectivity-fault-management maintenance-domain random maintenance-association 5 continuity-check interface-status-tlv
set protocols oam ethernet connectivity-fault-management maintenance-domain random maintenance-association 5 mep 1 interface xe-0/3/0.61
set protocols oam ethernet connectivity-fault-management maintenance-domain random maintenance-association 5 mep 1 direction up
set protocols oam ethernet connectivity-fault-management maintenance-domain random maintenance-association 5 mep 1 priority 1
set protocols oam ethernet connectivity-fault-management maintenance-domain random maintenance-association 5 mep 1 auto-discovery
set protocols oam ethernet connectivity-fault-management maintenance-domain random maintenance-association 5 mep 1 remote-mep 2

set interfaces xe-0/3/0 flexible-vlan-tagging
set interfaces xe-0/3/0 mtu 9172
set interfaces xe-0/3/0 encapsulation flexible-ethernet-services
set interfaces xe-0/3/0 unit 61 encapsulation vlan-ccc
set interfaces xe-0/3/0 unit 61 vlan-id 61
set interfaces xe-0/3/0 unit 61 family ccc

 REF: https://www.juniper.net/documentation/en_US/junos/topics/task/configuration/primary-vid-config.html

Maybe the primary-vid works for you.

=================================

Accept this solution if it helped.

Kudos are appreciated too 🙂

Pranavs,
Thanks for the info. I will try your config as well but here is what I am trying to accomplish.

MX2 ----(L2circuit over MPLS for VL777) ---- MX1 ----Flexible-ether-service vlan-ccc interface over VL777---- Accedian

-------------------------------------------------------------MD LEVEL 3 or 0-------------------------------------------------------------

CFM should be monitoring the whole circuit between MX2 and Accedian (End to End). I am also a bit confused about the direction (UP/DOWN). if you can shed some light on this one too it would be great

I am rebuilding my lab to match this setup right now, will update this thread shortly 

Hi Ali,

I am using primary-vid knob in my lab. Based on documentation this knob allows for increased flexibility when you have a trunk port with a vlan-range or list. **bleep** IS working correctly even when I have one vlan configured on the IFL.

The interface-status-tlv knob is recommended when the remote MEP is configured on a non-Juniper device. Here are the details in the docs -

Interface Status TLV (Type, Length, and Value)—You can enable connectivity fault management (CFM) monitoring between provider edge devices and customer edge devices when the customer edge device is not a Juniper device by using Interface Status TLV. When the interface is down, CFM propagates the status of the interface using interface status TLV. The Interface Status TLV indicates the status of the interface on which the MEP transmitting the CCM is configured, or the next-lower interface in the IETF RFC 2863 IF-MIB. Thus, the customer edge device is aware that the provider edge
device is down. To configure CFM monitoring using Interface Status TLV, use the interface-status-tlv statement at the [edit protocols oam ethernet connectivity-fault-management maintenance-domain maintenance-domainmaintenance-association maintenance-association continuity-check hierarchy level. This is the standard option.

CE ---interface-xe-0/3/0--- MX2 ----(L2circuit over MPLS for VL777) ---- MX1 ----Flexible-ether-service vlan-ccc interface over VL777---- Accedian

Also, in your scenario, you should be using direction UP on MX2. The logic here is that when the MEP is configured on xe-0/3/0, for example, configuring the direction as UP will ensure that CCMs are sent over the L2CKT towards Accedian device. On the Accedian, you can try to configure direction UP as well. I know that with some other vendor devices, direction UP works correctly. It depends on the vendor - when you configure UP on a Juniper MX, it wont send out CCMs over that interface, instead it sends the CCMs over L2CKT. Hence, if it is a Juniper device, on the CE you will need to configure direction DOWN.

>> This VPLS direction will help understand the MEP direction further -

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

>> Network Interfaces Guide contains complete CFM documentation

https://www.juniper.net/documentation/en_US/junos/information-products/pathway-pages/config-guide-network-interfaces/network-interfaces-ethernet.html

>> Docs on Interface-status-tlv

https://www.juniper.net/documentation/en_US/junos/topics/topic-map/interfaces-configuring-port-status-and-interface-status-tlv.html

Pranavs,
This is some great info here. I appreciate the help. I think I got it figured out. I deployed these on the MX's and all seems to  be working so far. The only thing I have to work on now is getting the MX to send SLM and DMM, and finally have it push these data to analyzer/collector for monitoring.